Unbricking for dummies

MasterTec · 07-18-2011, 12:44 PM

OK so I installed Chainfire3d 2.8 and now my PE won't boot. I've tried reverting to ermine and I've tried doing the factory restore (with dingo). Doing either shows the "updating" screen for about five seconds and then nothing.. it just hangs on the Pocket eDGe boot screen for about 10-15 minutes and then goes blank.

This may have something to do with my renaming my phone.apk and telephony.apk files. I didn't think Chainfire would brick this because others have installed it without problems.

I was reading the other unbricking thread and they mentioned restoring the build.prop file and while I don't think that is the case with me, I'd like to at least find a way to access the phone/telephony.apk files and rename them. Maybe it'll take a restore once I do that.

I can connect the USB to my PC and it shows two drives on my PE but I cannot access them (please insert disk type message). So where do I go from here? How do I access the file system on my PE?

emusan · 07-18-2011, 12:59 PM

you will want to install the android sdk to get the adb tools on your pc, you can get it all from here: http://developer.android.com/sdk/index.html

once you've got that installed, open up a command prompt(windows button+R then type cmd.exe), then navigate to the folder that the android sdk installed to then go to the platform tools folder(all within the command prompt, you can use cd to change directories and dir to list the directories in the current folder). Once there connect your edge and type "adb devices" and let me know what it says.

kennyminot · 07-18-2011, 02:56 PM

Try this:

https://www.mobileread.com/forums/sho...d.php?t=143035

MasterTec · 07-18-2011, 03:38 PM

WHOA! KENNY! Thanks for that link! It's not working yet but it's actually taking the time to copy files now! I made some progress at least!

So it looks like I have to wait for it to time out (20-30 min) and then apply the update again and then it should be reverted back to factory!

I'll let you guys know soon! Thanks!

MasterTec · 07-18-2011, 03:46 PM

EMU it came up blank. It would pause for a few seconds then show LIST OF DEVICES: and then be blank after that.

From what I was reading in the thread Kenny linked to it looks like something changed and the UPDATE file didn't recognize the PE as the correct hardware anymore. I don't know if that's because of the video driver or because of me deleting the PHONE/TELEPHONY.apk.. <shrug> I'm just not knowledgeable with droid (and BARELY knowledgeable with Linux).

So apparently applying a modified UPDATE with the hardware checks removed is doing the trick. At least it's hung on "updating software" instead of just flashing that screen real quick and then getting hung on the boot screen now.

I have to say that I agree.. it's pretty asinine for entourage to have not included any kind of recovery mode with things. I understanding that rooting and all this is risky but come on, what did they expect? I guess that's a big part of the reason why they went under, huh?

emusan · 07-18-2011, 04:01 PM

Quote:

Originally Posted by MasterTec

EMU it came up blank. It would pause for a few seconds then show LIST OF DEVICES: and then be blank after that.

From what I was reading in the thread Kenny linked to it looks like something changed and the UPDATE file didn't recognize the PE as the correct hardware anymore. I don't know if that's because of the video driver or because of me deleting the PHONE/TELEPHONY.apk.. <shrug> I'm just not knowledgeable with droid (and BARELY knowledgeable with Linux).

So apparently applying a modified UPDATE with the hardware checks removed is doing the trick. At least it's hung on "updating software" instead of just flashing that screen real quick and then getting hung on the boot screen now.

I have to say that I agree.. it's pretty asinine for entourage to have not included any kind of recovery mode with things. I understanding that rooting and all this is risky but come on, what did they expect? I guess that's a big part of the reason why they went under, huh?

did you end up modifying the file yourself or did you download my pre-modified one?

MasterTec · 07-18-2011, 04:04 PM

I downloaded the pre-modified one. I got impatient trying to figure out what to edit in the file.

It's still hanging at the updating screen right now. Just waiting the 20-30 minutes or so...

emusan · 07-18-2011, 04:12 PM

Quote:

Originally Posted by MasterTec

I downloaded the pre-modified one. I got impatient trying to figure out what to edit in the file.

It's still hanging at the updating screen right now. Just waiting the 20-30 minutes or so...

If you think that it would be any more help I could try and send you one with even fewer checks(I have one already made, but I think it will need to be manually reset once its done due to the amount of stuff I've removed lol)...

MasterTec · 07-18-2011, 04:25 PM

Well she just booted up! I'm back to stock 1.6! I'll let you know if I have any problems!

WOOHOO! Thanks guys!

emusan · 07-18-2011, 04:32 PM

good to hear its all working out in the end!

Filark · 07-18-2011, 04:32 PM

Congratulations!

Now go buy one just for your GF!

kennyminot · 07-19-2011, 03:18 PM

Cheers to darkgrue and emusan!

Yellowman1 · 07-20-2011, 05:42 AM

Quote:

Originally Posted by emusan

you will want to install the android sdk to get the adb tools on your pc, you can get it all from here: http://developer.android.com/sdk/index.html

once you've got that installed, open up a command prompt(windows button+R then type cmd.exe), then navigate to the folder that the android sdk installed to then go to the platform tools folder(all within the command prompt, you can use cd to change directories and dir to list the directories in the current folder). Once there connect your edge and type "adb devices" and let me know what it says.

@Emusan (or whoever else can help): I am also trying to get to my EE's hard drive (I can see it when I attach my EE to my PC but it is grayed out, Windows cannot access it) in an attempt to revive my EE. I have installed the Android SDK tools followed the basic commands in Emusan post quoted here, but only as far as listing the directories. I don't know the syntax to navigate to the platform tools folder on my D: drive (that's where I installed the jdk files), can anyone jelp me with the syntax to get me to the platform tools so that I can connect my EE and type "adb devices" to see what happens next?

Thank you all for your help.

Yellowman1 · 07-20-2011, 11:23 AM

Quote:

Originally Posted by emusan

once you've got that installed, open up a command prompt(windows button+R then type cmd.exe), then navigate to the folder that the android sdk installed to then go to the platform tools folder(all within the command prompt, you can use cd to change directories and dir to list the directories in the current folder). Once there connect your edge and type "adb devices" and let me know what it says.

So, I did the above (got one of my friends to help me with the syntax) ran the adb.exe and this is what I got.

Directory of D:\Program Files (x86)\Android\android-sdk\platform-tools

07/20/2011 05:59 AM <DIR> .
07/20/2011 05:59 AM <DIR> ..
07/20/2011 05:59 AM 5,465,938 aapt.exe
07/20/2011 05:59 AM 410,942 adb.exe
07/20/2011 05:59 AM 96,256 AdbWinApi.dll
07/20/2011 05:59 AM 60,928 AdbWinUsbApi.dll
07/20/2011 05:59 AM 1,344,051 aidl.exe
07/20/2011 05:59 AM 423,585 dexdump.exe
07/20/2011 05:59 AM 2,682 dx.bat
07/20/2011 05:59 AM <DIR> lib
07/20/2011 05:59 AM 16,046,592 llvm-rs-cc-2.exe
07/20/2011 05:59 AM 15,424,512 llvm-rs-cc.exe
07/20/2011 05:59 AM 241 llvm-rs-cc.txt
07/20/2011 05:59 AM 332,494 NOTICE.txt
07/20/2011 05:59 AM 301 source.properties
12 File(s) 39,608,522 bytes
3 Dir(s) 12,190,531,584 bytes free

D:\Program Files (x86)\Android\android-sdk\platform-tools>adb
Android Debug Bridge version 1.0.26

-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.

If -p is not specified, the ANDROID_PRODUCT_OUT

environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this ocmmand with no additional arguments

will disconnect from all connected TCP/IP devic
es.

device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport

adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.

adb help - show this help message
adb version - show version num

DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition

scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns

adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:

- If <directory> is not specified, both /system and /data partitions will be u
pdated.

- If it is "system" or "data", only the corresponding partition
is updated.

environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.

So now what do I do (my friend is a Windows guy, has no clue about Android systems)? The drive is still hidden in Windows and it is being shown has having 0% space.

ivanjt · 07-20-2011, 04:45 PM

Yellowman1, what exactly are you trying to achieve?

If all you want to do is transfer files to and from your EE via USB then you need the EE running before you plug it into the PC. The PC will see the USB device but you also have to enable the USB on the EE. If you are using Ermine then the LCD screen will show USB attached with a botton near the bottom of the screen that will activate it. When you have done this you will be able to see what is on the EE.

Don't forget to correctly disconnect the USB from your PC and shut down the USB on the EE.

In fact it is all in the manual.

07-18-2011, 12:44 PM	#1
MasterTec Connoisseur Posts: 98 Karma: 14416 Join Date: Jul 2011 Device: enTourage eDGe Pocket	Unbricking for dummies OK so I installed Chainfire3d 2.8 and now my PE won't boot. I've tried reverting to ermine and I've tried doing the factory restore (with dingo). Doing either shows the "updating" screen for about five seconds and then nothing.. it just hangs on the Pocket eDGe boot screen for about 10-15 minutes and then goes blank. This may have something to do with my renaming my phone.apk and telephony.apk files. I didn't think Chainfire would brick this because others have installed it without problems. I was reading the other unbricking thread and they mentioned restoring the build.prop file and while I don't think that is the case with me, I'd like to at least find a way to access the phone/telephony.apk files and rename them. Maybe it'll take a restore once I do that. I can connect the USB to my PC and it shows two drives on my PE but I cannot access them (please insert disk type message). So where do I go from here? How do I access the file system on my PE?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Help Unbricking PE	vicinc	enTourage eDGe	113	07-16-2011 12:40 AM
PRS-350 Unbricking from boot loop?	Analogus	Sony Reader	19	06-16-2011 03:35 PM
Hacks Any advice on unbricking the Kindle 2?	synapse	Amazon Kindle	5	01-20-2010 08:45 PM
Help unbricking my 505!!!	StanleyPhang	Sony Reader Dev Corner	1	07-07-2009 04:05 PM
Even unbricking reset is not working !!!	alaya129	Sony Reader	25	09-14-2008 11:11 AM

07-18-2011, 12:59 PM	#2
emusan lol Posts: 472 Karma: 1031 Join Date: May 2011 Device: eDGe	you will want to install the android sdk to get the adb tools on your pc, you can get it all from here: http://developer.android.com/sdk/index.html once you've got that installed, open up a command prompt(windows button+R then type cmd.exe), then navigate to the folder that the android sdk installed to then go to the platform tools folder(all within the command prompt, you can use cd to change directories and dir to list the directories in the current folder). Once there connect your edge and type "adb devices" and let me know what it says.

07-18-2011, 02:56 PM	#3
kennyminot Groupie Posts: 183 Karma: 90022 Join Date: May 2011 Location: Louisville, KY Device: HTC EVO View 4G, HTC Wildfire S, Asus T91MT	Try this: https://www.mobileread.com/forums/sho...d.php?t=143035

07-18-2011, 03:38 PM	#4
MasterTec Connoisseur Posts: 98 Karma: 14416 Join Date: Jul 2011 Device: enTourage eDGe Pocket	WHOA! KENNY! Thanks for that link! It's not working yet but it's actually taking the time to copy files now! I made some progress at least! So it looks like I have to wait for it to time out (20-30 min) and then apply the update again and then it should be reverted back to factory! I'll let you guys know soon! Thanks!

07-18-2011, 03:46 PM	#5
MasterTec Connoisseur Posts: 98 Karma: 14416 Join Date: Jul 2011 Device: enTourage eDGe Pocket	EMU it came up blank. It would pause for a few seconds then show LIST OF DEVICES: and then be blank after that. From what I was reading in the thread Kenny linked to it looks like something changed and the UPDATE file didn't recognize the PE as the correct hardware anymore. I don't know if that's because of the video driver or because of me deleting the PHONE/TELEPHONY.apk.. <shrug> I'm just not knowledgeable with droid (and BARELY knowledgeable with Linux). So apparently applying a modified UPDATE with the hardware checks removed is doing the trick. At least it's hung on "updating software" instead of just flashing that screen real quick and then getting hung on the boot screen now. I have to say that I agree.. it's pretty asinine for entourage to have not included any kind of recovery mode with things. I understanding that rooting and all this is risky but come on, what did they expect? I guess that's a big part of the reason why they went under, huh?

07-18-2011, 04:04 PM	#7
MasterTec Connoisseur Posts: 98 Karma: 14416 Join Date: Jul 2011 Device: enTourage eDGe Pocket	I downloaded the pre-modified one. I got impatient trying to figure out what to edit in the file. It's still hanging at the updating screen right now. Just waiting the 20-30 minutes or so...

07-18-2011, 04:25 PM	#9
MasterTec Connoisseur Posts: 98 Karma: 14416 Join Date: Jul 2011 Device: enTourage eDGe Pocket	Well she just booted up! I'm back to stock 1.6! I'll let you know if I have any problems! WOOHOO! Thanks guys!

07-18-2011, 04:32 PM	#10
emusan lol Posts: 472 Karma: 1031 Join Date: May 2011 Device: eDGe	good to hear its all working out in the end!

07-18-2011, 04:32 PM	#11
Filark Armed with a smile :) Posts: 1,421 Karma: 2463560 Join Date: Sep 2009 Location: California, USA Device: enTourage eDGe & Pocket eDGe, Samsung Galaxy Note II	Congratulations! Now go buy one just for your GF!

07-19-2011, 03:18 PM	#12
kennyminot Groupie Posts: 183 Karma: 90022 Join Date: May 2011 Location: Louisville, KY Device: HTC EVO View 4G, HTC Wildfire S, Asus T91MT	Cheers to darkgrue and emusan!

07-20-2011, 04:45 PM	#15
ivanjt Guru Posts: 858 Karma: 1027478 Join Date: Aug 2010 Location: South of France Device: kindle dx; eDGe	Yellowman1, what exactly are you trying to achieve? If all you want to do is transfer files to and from your EE via USB then you need the EE running before you plug it into the PC. The PC will see the USB device but you also have to enable the USB on the EE. If you are using Ermine then the LCD screen will show USB attached with a botton near the bottom of the screen that will activate it. When you have done this you will be able to see what is on the EE. Don't forget to correctly disconnect the USB from your PC and shut down the USB on the EE. In fact it is all in the manual.

Advert

Advert