Okay so I recently got this phone more or less as a toy and have been playing with its hardware and software to get it up to par and usable. I've been very impressed by this thing. I ended up with Trackball optional recovery and CM7 Condemned running very well. I seen Gin-sen-tazz and decided to give it a whirl.
Booted into recovery, did a nandroid then wiped data cache and dalvik and then went to flash the rom. It wouldn't go, told me to do something via adb. So I went to restore the backup of cm7 and get a new download ( didnt verify any md5's )
The back up restore gave me the same sort of error, then told me to do something else via adb. I was pretty peved off at this point and went into rom manager and flashed cwr and made a back up of the fresh cm7 install via cwr, and then tried to install the rom via rom manager and then manually in cwr and it still failed.
I'm still downloading my second copy of the rom and I'll be reporting back, but is there any harm in having both recovery's? I really would prefer to run cwr but I have heard of a few bricks, how wide spread is the epidemic? Boot loader still pushes me into trackball optional recovery when selected.
Just kinda sucks that I have two recoveries and neither will work. I am not very new at the whole rom flashing thing but I am not an expert by any means, and have not yet taken the time to learn my adb skills which I know I should
Alright downloaded and put the new rom on the sd card, booted into trackball optional and it flashed just fine.
I also used cwr to back up cm7 and then restore cm7 just to see if that backup indeed worked, and it did. Now I'm concerned that I don't have a stock back up, I made one in trackball recovery but it wont restore... The only back up I have that's working is the cm7 one via cwr... what would you guys recommend i do?
If you decide you want to flash back to stock 2.1 at some point, there's a couple simple options.
Flashback21 will get you back to the latest OTA(March 2011)...unrooted completely stock 2.1.
http://forum.xda-developers.com/showthread.php?t=792026
This other also gives you the latest March 2011 unrooted stock OTA but leaves your custom recovery.
http://forum.xda-developers.com/showthread.php?t=984274
Dunno if this is what was going on, but the Nandroid restore in Amon_RA for the Eris (and derivatives including the trackball-free recovery, I presume) have a 30% battery charge requirement.
If your battery isn't charged above that level, you'll just get a cryptic message about running nandroid-mobile.sh from adb; it won't say "charge your battery, please".
It pays to read Amon_RA's original post, where he points out that you should always check the recovery log file - the exact reason that you could not run the restore operation is reported in that log file. Rather than complaining about an unknown problem on a forum, you would instead know exactly what the problem was.
You can get at the file ( /cache/recovery/log ) via adb while the same recovery session is running, or you can use the Amon_RA menus to copy it to your SD card for later review. It's just a plain text file. Every time you boot the recovery, it gets overwritten - so you need to either review it right away after a problem occurs, or save it to the SD card.
bftb0
Related
So i'm going to consolidate and give everyone a brief recap on how I fixed my phone since it required the use of SEVERAL posts. I figured someone will eventually get caught in the same situation I was.
This is by no means the best way, or the correct way to fix any phone, do this at your own pace and liability. I am, and no one mentioned in this thread is liable for your phone.
Please excuse any of my grammar mistakes, this is spewing out as I type.
History: Stock DI01 update w/ JT's Voodoo .2 OC Kernel.
Flashed JT's Super Clean ROM V.4 & Remix Incognito Theme.
** Market would no longer work. I had this issue before updating to the 2.2 market after the DI01 update, so I uninstalled and worked again, however, that option wasn't available with the ROM Flash.
I couldn't find a single fix that would work to get the market to work, even ADB pushing older market apk's to the system wouldn't fix it. I decided to do a flash of JT's Super Clean ROM V.2, that didn't fix the issue either.
**I was clearing data and wiping dalvik after each flash**
With nothing seeming to work, I decided to try Deodexe's Zinc ROM, and this is where **** hit the fan. After doing this, I sent my phone into FC boot loop hell. I was getting the process.acore FC everytime I pressed a key. I rebooted back into Clockwork, tried to recover from an old ROM I had backed up the previous day, notta. Damage was done. I was getting FC bootloop hell with a very crappy performance.
I decided it was time to Odin restore and start over. These aren't the exact steps I took, but if I had to do it over again, this is how I would do it. If at any point you're getting a process.media FC, remove your SD Card, and leave it out until you need it for CWM.
STEP ONE:
If you installed Voodoo (at any point, removed or not, do this step)
Thanks to adrynalyne
http://forum.xda-developers.com/showthread.php?t=804784
This was the main culprit behind my phone not working correctly after a complete restore. I moved this to the top of the list, because after that, it's downhill.
STEP TWO:
Completely Restore with Odin Restore Files
Thanks to fallingup
http://forum.xda-developers.com/showthread.php?t=782204
The instructions are a little un-clear, but do this. First, Only use the PDA option, and flash each backup one at a time along with the PIT file. You're not out of the clear yet. Read on.
STEP THREE:
Flash CWM Recovery (read my notes below)
Thanks to fallingup
http://forum.xda-developers.com/showthread.php?t=788099
After you've flashed CWM. Boot into CWM Recovery, Boot back in Stock Recovery and wipe data and cache. Boot back to CWM (select sd:update.zip) and do the exact same thing there. Reboot phone.
STEP FOUR:
Do a data factory reset
Even though you have just restored the **** out of your phone, you're still not there. Get through all the account setup fields and go to Settings > Privacy > Factory Data Reset.
After a reboot, you should be on your way to a completely 100% stock fixed phone. At this point, I would suggest making a ROM back up of this point before moving ahead with flashing again.
LAST STEP (for me anyway):
Restore apps via Titanium Backup
This restored most my apps and settings that I had already saved, including LauncherPro and the backups I had for that. If you haven't used Ti, then use whatever app backup app you do have, if you do indeed have one.
I decided to re-flash JT's Super Clean ROM V.4 found here. Thanks to JT
http://forum.xda-developers.com/showthread.php?t=796171
I am also running the Remix Incognito Theme here: Thanks to frostman89
http://forum.xda-developers.com/showthread.php?t=801867
Right now I'm mixed on updating a new Voodoo Kernel, I haven't decided if I want to do that again or wait for something else.
Thanks again for all the DEV support, hopefully someone searching will find this thread useful.
Pretty much my standard routine when trying new kernels.
I have a nandroid with my basic rooted setup (apps and data intact), so this doesn't set me back by a huge amount.
Just a few differences...
I use:
Odin (System, then kernel) (step only needed if things are *really* messed up...won't boot)
Boot into Recovery
flash update.zip to get into CWM
Wipe Data/Cache/Davlik
Reboot into recovery
run jt's voodoo_uninstall (flashes stock.zip and replaces mbr with stock mbr)
reboot into recovery
restore nandroid image.
This has yet to fail me and usually takes under 10 minutes. The nandroid image is key. Most of the time, I can skip the Odin step completely if I am not seeing anything truly, staggeringly horrific going on.
Again, jt's voodoo-uninstall seems to solve a lot more than just voodoo issues. This thing should get it's own topic/forum/entry in ROM Manager/zip code/nobel award...you get the picture.
PhoenixPath said:
Again, jt's voodoo-uninstall seems to solve a lot more than just voodoo issues. This thing should get it's own topic/forum/entry in ROM Manager/zip code/nobel award...you get the picture.
Click to expand...
Click to collapse
+1 I agree
Nice write up! I'm sure this will help many people.
Thanks
This along with several other threads allowed me to recover from my own mental retardation.
Gotta remember to remove voodoo before doing stuff. I should know better.
Thanks again.
This is not working for me. I removed voodoo (using the uninstaller). I then did odin and my phone boots but I cant do anything past the unlock bc of all the fcs I get. I wiped the cache and data. CWM is not working, when I try to do the update.zip I get a "failed to verify whole-file signiture". - I deleted the voodoo folder from the sd-card after uninstalling voodoo, dont know if that contributed to the problem. Any ideas?
Ke1evraTi said:
This is not working for me. I removed voodoo (using the uninstaller). I then did odin and my phone boots but I cant do anything past the unlock bc of all the fcs I get. I wiped the cache and data. CWM is not working, when I try to do the update.zip I get a "failed to verify whole-file signiture". - I deleted the voodoo folder from the sd-card after uninstalling voodoo, dont know if that contributed to the problem. Any ideas?
Click to expand...
Click to collapse
Sounds like you need to re-flash ClockworkMod through Odin. I'm guessing it got wiped out when you went back to stock.
Tuesday night I loaded CM7, and then the Market wouldn't update my apps so I decided I would restore BAMF 1.5. After doing so, the Market just gave me "Fails" trying to update, and I could not access recovery, as I was going to do a complete wipe and reflash. Most of Wednesday, an extremely helpful & knowledgable member, Mattgyver83, tried diligently to help me rectify the situation, but to no avail. We tried to Fastboot, tried flash_image, tried fix permissions...shoot, I practically wore out adb..anyway, I ended up reverting back to stock and unrooted. I used jcase's method to revert back to stock, and that was painless, and successful. I decided last night to try rooting again, thinking a fresh root would solve my issue of not being able to access recovery. Root was successful, but I still cannot access recovery, through rom manager, or through bootloader. When I attempt it my Tbolt goes to white HTC screen, and stays there. All functions of my phone now work, and all aspects of root work, except I cannot flash anything. Rom manager shows I have clockwork recovery, but I just can't get to it.
Sorry for the long ramble. If anyone has had this issue, or if anyone knows a fix, I would appreciate it. Otherwise, I wait for Gingerbread.
Thanks
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
travishamockery said:
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
Click to expand...
Click to collapse
Tried that, but thanks. Still just goes to white HTC screen, and stays there until I do battery pull.
jr4000watts said:
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
Click to expand...
Click to collapse
I can get to bootloader, just not able to get into recovery.
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
monolithic said:
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
Click to expand...
Click to collapse
Thanks, but that didn't work. I think something in my os got lost when I restored BAMF from CM7.
Yea I spent a good few hours yesterday trying to help Orio out and we attempted a ton of things to try and fix the recovery issue, this post should offer a bit more insight to the methods used, this is running off memory;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Not once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
monolithic said:
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Click to expand...
Click to collapse
I recall the same thing and its a good thought however that was mostly a generic error due to a CWM update and CM6 (I think) but either way flashing an RUU should override this shortcoming and im pretty sure that issue was worked out in CWM as well.
Not to be rude, but I don't think this question belongs in the development section.
Orio56 said:
I can get to bootloader, just not able to get into recovery.
Click to expand...
Click to collapse
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
hogowner said:
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
Click to expand...
Click to collapse
Thanks, but no, I deleted that after loading it. I actually reverted back to stock/unrooted last night and rerooted and the problem still remains. It's quite strange.
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
shelooga said:
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
Click to expand...
Click to collapse
That is what I was going to suggest. In ROM Manager at the very bottom try and flash an older version.
Sent from my ADR6400L using XDA Premium App
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
GREAT NEWS!!!! CONGRATULATIONS!!
THANKS FOR REPORTING BACK!
This may help out other members with the same problem!!
now go ahead and start playing with your T-BOLT again!
That's a very odd solution. My first two things to try would have been:
1) fastboot:
fastboot erase recovery
fastboot flash recovery C:\some\local\path\recovery.img
You can't, well, probably shouldn't, flash a recovery from the /sdcard. When in fastboot mode I don't think the sdcard is even mounted. Either way, I think fastboot needs the img file on the local file system.
2) Create a PG05IMG.zip file with the recovery.img file in it, and flash that through HBOOT. Although this should have been done in some form or fashion when you downgraded or re-rooted, so YMMV.
Guys,
I have tried several roms and decided to odin back to 2.1, updated to 2.2 and just clean it up a bit and leave it as is for a while.
Everything went just fine, but yet again this damn clockwork recovery issue which I knew I would get but thought maybe it would be solved by now on rom managers side.
So, in rom manager, it shows that current recovery is 2.5.1.2 which matches the latest, however, when I reboot into recovery, I am still getting the standard 2.2 recovery console.
I tried searching but not sure what the issue is, of course I get the signature issue when I try to update package.
It's wierd that it's showing it's installed but it's not actually booting into the correct recovery console.
Thanks.
kero4 said:
Guys,
I have tried several roms and decided to odin back to 2.1, updated to 2.2 and just clean it up a bit and leave it as is for a while.
Everything went just fine, but yet again this damn clockwork recovery issue which I knew I would get but thought maybe it would be solved by now on rom managers side.
So, in rom manager, it shows that current recovery is 2.5.1.2 which matches the latest, however, when I reboot into recovery, I am still getting the standard 2.2 recovery console.
I tried searching but not sure what the issue is, of course I get the signature issue when I try to update package.
It's wierd that it's showing it's installed but it's not actually booting into the correct recovery console.
Thanks.
Click to expand...
Click to collapse
delete whatever update.zip you
http://forum.xda-developers.com/showthread.php?t=849028
get the 1 from there, reinstall packages twice and it should go to clockwork recovery
Okay, obviously option b would be better, however, will I have to reroot after if I use option B?
Nadda, same results, it's okay though, I'll live with it for now since I'll keep 2.2 with all the crud removed for now.
Please read that guide. You've missed some key points. I'd explain more, but I'm hanging with my kid.. Read the guide.
had the same problem i used this method and it worked for me
http://forum.xda-developers.com/showthread.php?t=833423&highlight=recovery
Was able to unlock on HTC Dev after doing the jcase exploit and then flashed the CWR 6.0.1.2 with the larger font, unsecured kernel, then got Superuser on it and my phone runs great!
Being somewhat lazy, I like being able to access CWR as the program on the phone, not having to power down and boot into it using Vol Down + Power...so I installed CWR 6.0.1.5 and all seemed fine.
After tweaking all my programs and getting my phone exaclty how I like it I attempted to do a Nandroid backup and about halfway the backup in CWR the phone just stopped and rebboted...no finishing up message, no generating MD5 sum etc that Im used to.
The final backup had 2034 files and was approx 1.2 GB in size.
That didn't seem rigtht so I uninstalled CWR on the phone, then reflashed through fastboot the CWR 6.0.1.2 I originally had....and the phone was then able to do a complete backup....5131 files and about 2.3 GB in size.
I'm pretty sure I was right in not trusting the 6.0.1.5 ROM backup, but any reason why? Is there a version that installs as a program on the phone that will work, or until S-Off is achieved is the proper way into CWR done through powering down and doing the proper reboot to get into recovery?
Sorry for the long winded question...lol but I figure the exact details/methodology will stop any questions back and forth in terms of what I did and why I am asking the question.
From what I've read/heard the version you had was very unstable. Which is why most devs went with TWRP. The fixed version is back up now if you want to give it a shot.
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
nashdude said:
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
Click to expand...
Click to collapse
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
I ran into something similar when I tried installing CWM 6.x.x. I chickened out and decided to run CM10 from SD instead, and I'm so happy on the performance now that I do!
I did the "unbrick" thing with "repart.img" to get the Tablet back to "out of the box" state and sighed of relief when it worked!
Yeah, I was afraid of that. I really didn't wanna go through the process of unbricking, but I guess there's no help for it.
troy9829 said:
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
Click to expand...
Click to collapse
Power + 'n' doesn't work on my NT either, I have to turn the device off, insert the SD with CWM, then plug in the (still turned-off) NT to a wall charger and allow it to boot up that way - then (and only then) do I boot into recovery, and without touching any buttons. Hopefully that helps
Dang, whoever thought this would be such a booger of a deal?!?
Okay, first off, let me apologize for coming off like a noob, but it seems there's so much information out there that everything's kinda bleeding together, so let me tell you where I'm at.
I've unbricked and restored the NT to stock 1.4.2
I tried rooting, but the only root I can find that is flashable from SD is the 5.5 CWM which is older than the CWM 6.xxx that every CM10 version calls for. So I went ahead and did the root, so now I have a stock NT with root access. This is where I'm getting stuck...
I'm at this point...
http://forum.xda-developers.com/showthread.php?t=1640958&highlight=cwm+1+4+2
...and it apparently requires you to reboot into CWM in order to install CWM?!?
I've found the CWM 6+ files I think I need, but when I try to follow the instructions, my NT won't kick over into recovery---it keeps booting straight to the rooted 1.4.2 stock rom. I've found guides that take you from stock 1.4.3 to CM10, some that take you from 1.4.2 to root, and I even found Indirect's CM7 (without the instructions on how to get CWM on there in the first place!). I even downloaded Rom Manager and tried to boot into recovery that way, but it said there was my device wasn't supported.
I've been staring at this dang screen for three hours, trying to find a step by step, and I'm coming up empty. Maybe I'm just too frustrated at this point and need a breather.
What I need to know is how to install CWM 6+ on a NT that's either rooted or stock 1.4.2 (I still have the unbrick SD card) so that I can boot into CWM. From there, I can make my way through installing CM10. Help. Please. Am about to chew the lining out of my cheek.
I don't know if this might be helpful? http://forum.xda-developers.com/showthread.php?t=2037368
Sent from my NookColor using Tapatalk 2
Not yet. I was expecting OTA to kick in, updating my current 1.4.2 to 1.4.3, but it hasn't. Honestly starting to think my NT doesn't want to be rehacked LOL
Okay, so here's what I'm doing at the moment...
I'm at rooted stock. I moved CWM 6.0.1.2, CM10, and gapps over to internal SD.
I booted into recovery with an older version CWM SD card (SD card image with Win32 > turned off NT > insert SD > plug in USB to autoboot)
While in recovery (from SD), I flashed CWM 6.0.1.2 , CM10 (meghd00t), and gapps-jb-20121011.
I reboot...
WE HAVE JOY!
Now to check to see if the thing's gonna run right (got a whole lotta "XYZ has stopped" error messages upon boot up)
Dangit, keep getting those error messages about Gapps stopping and Google Play, and other stuff. Not allowing me to do hardly anything I need to. I can't even boot into recovery from the home page---it still loads straight to the Rom. In order to get into recovery, I need to use the SD that I made to get into recovery in the first place. Going to wipe dalvik and the other caches to see if that helps...
After wiping the caches, I boot into CM10 with no error messages. I DL'd a game from my Gmail account, and it appears to be working properly. Thanks for the suggestions and for letting me vent
I just went thru this similar ordeal too. It took me over 3 weeks to finally find a recovery & cm10 combo. What I found is that I couldn't get ANY version of twrp to act right. Indirect's flashing tool was invaluable. I finally used it to flash a cwm 6.x from Laverne's thread. It seems that not all versions of cwm 6.x are compatible with certain cm10 roms too & by chance I hit a combo that finally worked! I'm staying with what I got for a while!
Sent from my Nexus 7 using Tapatalk 2