So this was sort of a 3 part process that I need to detail to see if anyone has any clues on how to help. I tried to search the forums but had no luck coming across anything. Basically here is what I did, as I'm using a Mac I took a back door route.
1. Rooted phone using UnRevoked3. This worked fine I was using it for a day or two but then wanted to install Cyanogenmod so I could use Froyo. I wasn't able to install and it appeared the consensus was that the way unrEVOked works does not allow the proper access to install cyanogenmod. According to theunlockr.com/2010/07/20/how-to-root-the-htc-evo-4g-unrevoked-method/ it appeared that after installing unrevoked one still needed to unlock the NAND as seen here theunlockr.com/2010/07/20/how-to-unlock-nand-on-the-htc-evo-4g/
2. As this process did not work on Mac I scoured the forums and found this process forum.xda-developers.com/showthread.php?t=705113 and went through all the steps. Everything worked fine until the end when I installed the Radio an then the ROM (this was backwards from their instructions, ROM then radio which may have cause the problem). Regardless I ran Radio update, but then didn't reboot and installed Cyanogenmod update linked to from here forum.xda-developers.com/showthread.php?t=729367&highlight=brick
3. Everything appeared to work fine. After installing Cyanogenmod it asked if I wanted to reboot. I said yes, it said updating radio then rebooted. This may have been where I made the true mistake. It gave me a thing with an exclamation point after rebooting. At this point I waited for a little while then tried restarting, I took the battery out and tried to press a button. After this it wouldn't turn on. Am I totally screwed? My guess is that I probably am and feel like a total moron... Please let me know if there is anything worth doing...
Thanks,
Greg
also http portions were left out of links due to the fact that xda won't let me post links as a new member
Related
Hi all.
I'll start by saying I have gotten in way over my head. I rooted my Evo with unrEVOked's one-click method, and then began to experience some problems with my 3g. Thinking I had somehow botched the rooting process, I tried to unroot using the two-step method I also found on xda (cannot post link.. further proof I am a noob ). More problems sprang up, one thing led to another, various fixes were tried (HUGE thanks to everyone in the IRC channel last night that tried to help my sorry ass..) but to no avail.
Here is where my phone is at now: booting using vol down+power shows me S-ON. Trying to flash mtd-eng.zip results in an error, so I am seemingly stuck with S-ON. Normally I would be happy about this (that's one step closer to unrooted, right?) but I notice I still have Superuser in my apps. My 3g is working again for whatever reason (no complaints here! maybe it was a Sprint-side problem in my area.. what timing!) but I'm confused as to whether my phone is rooted or not.
Ideally, I would like to go back to unrooted, since I have made it abundantly clear to myself that I am not yet prepared to embark in rooting. If anyone could guide me in the right direction, I would be very thankful.
You no longer have root access. Nothing you do at this point will allow you to run a .img on your own.
Your best bet would be to try and run one of the RUU programs to get it all back to stock.
I don't know if the Superuser application will be removed by this but you can try it:
Go to Settings>SD & Phone Storage>Factory Data Reset
Your phone should reboot and may have erased the Superuser app.
Jim M said:
You no longer have root access. Nothing you do at this point will allow you to run a .img on your own.
Your best bet would be to try and run one of the RUU programs to get it all back to stock.
I don't know if the Superuser application will be removed by this but you can try it:
Go to Settings>SD & Phone Storage>Factory Data Reset
Your phone should reboot and may have erased the Superuser app.
Click to expand...
Click to collapse
I did this, and my phone is now in RA-evo-v1.8.0 (it rebooted into recovery). Should I reboot the system now? I find it strange that it took me here in the first place.
The current PC36IMG that is flashed to the Evo is one with Amon Ra built into it.
The only RUU program that I am allowed to run (from the list that was given out in one of the unrooting evo threads) gives me the 170 error before anything happens.
You don't have root access, but your phone still has a custom recovery (Amon_RA) right now. No way to get rid of the custom recovery now except through an official update that replaces the recovery file.
Like I said you can try to run one of the RUU Official updates found in the Developer forum.
Don't know your location, but if you post it, someone close to you might try to help you out in person.
Jim M said:
You don't have root access, but your phone still has a custom recovery (Amon_RA) right now. No way to get rid of the custom recovery now except through an official update that replaces the recovery file.
Like I said you can try to run one of the RUU Official updates found in the Developer forum.
Don't know your location, but if you post it, someone close to you might try to help you out in person.
Click to expand...
Click to collapse
With a little digging and poking and reading, I found the proper RUU, ran it, and I believe I am now back to fully unrooted. Thank you very much for your help!
Hope that someone can shed some light on this for me...
Wednesday evening, I decided to root my brand new MyTouch 3G Slide. I had barely had it a week and I couldn't ignore the itch. So I did my research and finally settled on the instructions set on the Cyanogenmod Wiki page using the Exploid method. After a couple of blunders, I got it to work and installed CyanogenMod 6.1.1 for the Slide. It worked great for the most part. There were a couple of issues that I had that ended up being deal breakers (Unable to install Flash, dock at the bottom of screen randomly disappeared, etc.). I decided I'd had my fun and wanted to go back to a stock image. Stupid me, I didn't do a Nandroid back up first. Luckily, I found a near stock image in with Champion build. After 2 long hours, and thinking that I had bricked my phone, I got it back on and everything seems to be working normally. I found out this afternoon at work that this flashed the Champion build but actually put the radio version into a lower version than was current. So I started looking into doing the manual update, which led me to finding the 1.35.531 OTA ROM from CR. Since I was at work, I couldn't attempt the update.
I've now been at this over an hour again and cannot get it to reroot to install this image. I followed the exploid rooting instructions again and everything seemed to be working fine until I load into the bootloader. It looks for the ESPRIMG.zip but doesn't find it, though I've verified 3 times that it is there on the root of the SD Card. So I went into Android System Recovery and attempted the Update.zip, to which I received the "E:failed to verify whole-file signature" and the install aborts.
I've searched and searched and followed all sorts of directions to correct the issue. Maybe one of the experts can tell me what I'm doing wrong
Valorendk said:
Hope that someone can shed some light on this for me...
Wednesday evening, I decided to root my brand new MyTouch 3G Slide. I had barely had it a week and I couldn't ignore the itch. So I did my research and finally settled on the instructions set on the Cyanogenmod Wiki page using the Exploid method. After a couple of blunders, I got it to work and installed CyanogenMod 6.1.1 for the Slide. It worked great for the most part. There were a couple of issues that I had that ended up being deal breakers (Unable to install Flash, dock at the bottom of screen randomly disappeared, etc.). I decided I'd had my fun and wanted to go back to a stock image. Stupid me, I didn't do a Nandroid back up first. Luckily, I found a near stock image in with Champion build. After 2 long hours, and thinking that I had bricked my phone, I got it back on and everything seems to be working normally. I found out this afternoon at work that this flashed the Champion build but actually put the radio version into a lower version than was current. So I started looking into doing the manual update, which led me to finding the 1.35.531 OTA ROM from CR. Since I was at work, I couldn't attempt the update.
I've now been at this over an hour again and cannot get it to reroot to install this image. I followed the exploid rooting instructions again and everything seemed to be working fine until I load into the bootloader. It looks for the ESPRIMG.zip but doesn't find it, though I've verified 3 times that it is there on the root of the SD Card. So I went into Android System Recovery and attempted the Update.zip, to which I received the "E:failed to verify whole-file signature" and the install aborts.
I've searched and searched and followed all sorts of directions to correct the issue. Maybe one of the experts can tell me what I'm doing wrong
Click to expand...
Click to collapse
I can't think of why the bootloader wouldn't see the esprimg file unless it wasn't on the root of your sd card. But you should follow the new rooting guide in the android development section for this phone by nbetcher, supposed to be much easier to follow. Try that, although that ALSO requires esprimg.zip. So yeah is ESPRIMG.zip on the root of your sd card? It has to be there.
Sent from my T-Mobile myTouch 3G Slide
I never got around to doing this again. I was without my new smart phone for days while I wiped, rooted, installed, rinsed, repeated. I stuck with the Champion build and have moved on from the root. I know I had that esprimg.zip on the root of the drive but it wouldn't read so I just gave up. I'm pretty happy with the stock interface. Thanks for the help though MusicMan.
Hello everyone, first off, I read these two posts in their entirety:
http://forum.xda-developers.com/showthread.php?t=1009969
and
http://forum.xda-developers.com/announcement.php?f=943
I apologize if this might not be the best forum to post in, but as I just signed up I didn't have enough posts to post in the first thread like other people.
So I kinda have a good understanding of what I need to do with my phone, but need someone to recommend the best thing for me to do to change my firmware to 6.05.6 or 6.05.9, so allow me to share my rooting experience:
First off, I am running Windows 7 64-bit and I have never rooted a phone before and my Thunderbolt was my first droid device that I got 5 days ago on April 2nd, but I have plenty experience with flashing firmware for other devices such as routers, DVD drives etc. Initially I was not going to bother rooting my phone because of how complicated it looked, but then I found the one-click method and was becoming increasingly annoyed by not being able to get rid of the bloatware such as the Blockbuster app, Bitbop, Lets Golf 2, Rockband, Peep, and a couple others, so I decided to give the one-click method a shot.
Initially I had an issue with the ADB driver as Windows failed to install it successfully, after many agonizing minutes and a couple forums later, I installed HTC Sync and that fixed the issue, so now my batch file was working thus far. My second problem was the hbooteng.nb0 file. I had extracted the files from the exploits.zip correctly to the platform-tools folder, but my mistake was that instead of using the RUU filed and renaming it for the first flash, I initially flashed it with the one that was already name PG05IMG, so basically I thought I had done it correctly until I ran into the hbooteng.nb0 issue and realized I had flashed with the wrong file, leaving my phone basically unchanged and unrooted, but working perfectly fine.
Sooo I started over, this time knowing for sure I was using the correct files, and the process went pretty smoothly and the oneclick method told me my phone was rooted and to install the SU and ROM Manager so I did. Also did the clockworkmod thing as well.
But here is where my current problem is: My firmware is the 605.10 version and I would like it to either be back at the stock 605.6 or the newer 605.9. My phone works modestly well with the 605.10 so far EXCEPT it isn't correctly detecting my location. I live in Indiana, but the clock keeps setting itself to Rio de Janeiro. Also if I try to use Google Earth and do "find my location" with the GPS enabled, it takes me to Rio de Janeiro!
So here is my question: Which method of getting to the 605.6 or 605.9 firmware is the safest for me to use? And will using the one-click batch file to flash to either of those firmwares be safe since in the beginning it says that method does not work unless it is already at 605.6 or 605.9? Or should I attempt to do the option of factory resetting my phone through the SDcard settings, and what will I lose, and will I be back at 605.6, OR am I somehow supposed to use the ROM Manager app to flash to 605.6 or 605.9?
Many thanks in advance!
Ok so I ended up using ROM Manager and flashed to the 1.12.605.06 and it worked successfully but now my phone is no longer rooted since the ShootMe app doesn't work.
...because as an avid forum user, I can't stand when someone writes a new post when all of the information is right at their fingertips. BUT WAIT! This isn't one of those situations! Well sorta. The last time I was on this forum was probably when I was tapping this great resource when I got my S3 and wanted to root it. I read and read until I was fully versed on how to go about doing so. Haven't been back since. The phone has been great until about a month ago.
When the kitkat OTA update became available, I along with many other naive fools, decided to go for it only to softbrick the device. I came here and found THIS thread. I have been having some major difficulties getting through the process due to my general lack of knowledge.
I digress...when in recovery mode, my phone shows Clockwork Mod 6.0.1.4 at the top. When trying to boot normally, I get stuck on the AT&T splash screen and it goes no further.
Can anyone point me to a simple guide other than the one I linked in this post? Should I even be following that method? Any help is MUCH MUCH appreciated as I am stuck with my old Skyrocket (which isn't half bad still, except i have a lot of app compatibility problems).
I might add that I don't use custom ROMs (never got that far into it) and would like to be able to use the latest ATT rom if possible. Keeping the root would be ideal but at this point I just need my phone to WORK.
Have you tried wiping cache, dalvik, and data in recovery? Just remember that doing all 3 will wipe out any data and apps on your phone.
Before flashing anything at this point, what exactly happened when using the ota? Did it fail after a certain percentage, did it fail immediately? Error messages?
Also, that method needs to be followed EXACTLY, from using twrp to flashing back to 4.3 stock before the ota.
I don't know about cwm, but tarp has a built in terminal emulator. Go there and enter this,
getprop ro.bootloader
Let us know what it returns before doing anything else.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
After tinkering with my Androids over the years, (Infuse, Captivate, G2, and now G3) I have finally decided to become a member of the forum that I primarily use as a source of information and links to downloads. I'd like to first say thank you to all those that have unknowingly help me over the years with my roots. Great place you've got here.
Now the fun part, after two days of ownership, I have experienced the first issue was not able to resolve on my own, what appears to be a hard brick. I downloaded Flashify after my initial root, installed TWRP Manager, ran the patch for writing to the SDcard, and installed TWRP Recovery from AutoRec. All appeared to go well and it said the instal was successful. I followed the instructions I found online that had great results for my particular model and version 5.0.1. Well, when I went to boot into recovery to make my initial backup, the phone shut down and would not come back up. No response at all. It wont power up by any method, tried letting the capacitors drain, still no go. After tinkering with it for a few hours (I've owned this phone for a total of 2 days now), I finally came to the conclusion that it would need JTAG and the original boot image flashed over the one that I mucked up.
Any ideas on where I made my mistake? I'm near 100% certain I downloaded the proper files for my phone model.
Also forgot to mention, I have not changed anything else on the phone. Only installed apps and root browsers I planned on using. So stock kernel, stock ROM, nothing until I started getting ready to make myself a save point, ironic really!
jamguitarist said:
After tinkering with my Androids over the years, (Infuse, Captivate, G2, and now G3) I have finally decided to become a member of the forum that I primarily use as a source of information and links to downloads. I'd like to first say thank you to all those that have unknowingly help me over the years with my roots. Great place you've got here.
Now the fun part, after two days of ownership, I have experienced the first issue was not able to resolve on my own, what appears to be a hard brick. I downloaded Flashify after my initial root, installed TWRP Manager, ran the patch for writing to the SDcard, and installed TWRP Recovery from AutoRec. All appeared to go well and it said the instal was successful. I followed the instructions I found online that had great results for my particular model and version 5.0.1. Well, when I went to boot into recovery to make my initial backup, the phone shut down and would not come back up. No response at all. It wont power up by any method, tried letting the capacitors drain, still no go. After tinkering with it for a few hours (I've owned this phone for a total of 2 days now), I finally came to the conclusion that it would need JTAG and the original boot image flashed over the one that I mucked up.
Any ideas on where I made my mistake? I'm near 100% certain I downloaded the proper files for my phone model.
Also forgot to mention, I have not changed anything else on the phone. Only installed apps and root browsers I planned on using. So stock kernel, stock ROM, nothing until I started getting ready to make myself a save point, ironic really!
Click to expand...
Click to collapse
Post the guide that you followed
You would have to kick your phone into Qualcomm USB Loader 9008 in order to fix it
http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-all-variants/