Related
In Brief:
Got New Phone due to light leak. Finally after 2 months
Came with 2.2 on it.
Used the new 2.2 Root Guide with Unrevoked. Worked great.
Installed VirusROMX - working great.
Wanted to try out the Final 6.0 ROM from Cyan.
NanDroided the ViruxROMX
Got an error 7? So I found this link that was to correct that issue.
http://forum.xda-developers.com/showthread.php?t=752832
Flashed the new Hboot and it allowed me to install the CYAN R6.0.
CYAN ROM - Keep on Rebooting and Reloading the CYAN Boot Screen after setup and scrolling some apps.
Removed it and went for a Nandroid Restore.
I get the MD5 Checksum message and then trying to reload boot image. And Boot Image cannot load.
I have tried to reflash the recovery(Clockwork) and still no good.
My working Daily with all my updates and apps are on the Nandroid. I would hate to lose it.
Any help would be appreciated.
Anyone?
Sent from my DROIDX using XDA App
instead of re-flashing the recovery, have you tried to do a restore via a nand recovery, or is that what your talking about that you did.
tomh1979 said:
instead of re-flashing the recovery, have you tried to do a restore via a nand recovery, or is that what your talking about that you did.
Click to expand...
Click to collapse
That's is what I tried to do. It would say boot image unloadable and spits me out to the HBOOT options. With no ROM loaded and messes up my current ROM in place.
At least for me when I restored in the past and I have done it often is that I would just restore and not wipe or anything since the restore does all of that for me. Well in this case it does not and when it cannot restore I have to reload a new ROM again in recovery and start the process all over again. I have tried the NANDROID again after going through the entire ROM reload again and still a no go.
I can't nandroid restore my old daily which has text messages and everything that I wanted to reference. I can live without it but the inability to restore any Nandroid is driving me crazy.
It happened when I flashed that HBOOT update on the link I provided in OP. I am just trying to figure out how to reflash the old image back so I don't have to worry about it. The only reason I did it in the first place is to test out the Cyanogen R6 and that wasn't a good experience.
I guess I could post in the thread that started all of this to ask. But I thought I would keep the SECTION POLICE from hounding me about posting in the wrong section
about the hboot, did you try the PC36IMG.zip, or did you do the flashable zip file through recovery?
I did the flashable file though recovery last night had no issue with that, maybe that's the problem, what is it showing for you current hboot.
tomh1979 said:
about the hboot, did you try the PC36IMG.zip, or did you do the flashable zip file through recovery?
I did the flashable file though recovery last night had no issue with that, maybe that's the problem, what is it showing for you current hboot.
Click to expand...
Click to collapse
The PC36IMG.zip - I will try the flash.
The Hboot through PC36IMG.zip worked fine. It's the nandroid thats fuxored. Will try later on and see. Thanks for the suggestion.
I had to redo the second part of the Froyo 2.2 update with the Rooted Froyo and the 2.2 unrevoked. It finally worked and I was able to restore. I really want to try out the CM 6.0 again in the future but not at the expense of time to restore to get it back.
got my evo about a month ago. rooted lastnight since unrevoked finally pushed out their 3.3 version which is updated for my version of hboot (2.02). the root went very smoothly. i installed the latest cyanogenmod rom, only to discover there was no market or gmail app with the rom! wish i had known that before. after doing some research online, i found out i needed to flash or install a "gapps" apk. so, looked around for that for a couple hours and couldn't find it. i downloaded what i thought would be the right .zip file to get the market on my phone (a vending.apk that was listed in another thread having to do with this same issue). so anyway... downloaded that, moved it to the root of my sd card, flashed it through clockworkmod recovery (by the way, everything up until this point was perfect) and finally rebooted my phone... only it never rebooted. the white htc EVO 4G screen was there. then, black screen, as if it was about to begin the cyanogenmod boot screen and fully boot. but, no. it went from white evo screen to black screen... to OFF. after this, i couldn't even turn it on to get it into hboot or access recovery. tried to do that for two hours. and finally i was able to get in... so i tried doing a factory/data reset through recovery, then a cache clear, then reboot. nothing. same thing. went back into recovery, tried reflashing cyanogenmod rom again. nothing. tried flashing myn's rom. nothing. all i get is installation aborted.
i am pretty sure that this is not a complete brick since i am now able to access hboot and recovery. but if i can't flash anything... and i'm stuck in hboot and recovery and cant boot my phone... what the hell do i do now? please help me figure this out!! anybody have any good advice or a known fix...??
Boot into recovery. Do a factory reset. then wipe cache and dalvik catch. Re flash cynagon and let it boot. You then need to find gapps.zip. Boot into recovery flashing gapps.zip.
i did all that. step by step. and when i reflashed the rom, that is when it wouldn't install, saying installation aborted. but, i'm gonna do it again. let's see if my phone wants to play nice now...
brtnygrey said:
i did all that. step by step. and when i reflashed the rom, that is when it wouldn't install, saying installation aborted. but, i'm gonna do it again. let's see if my phone wants to play nice now...
Click to expand...
Click to collapse
If that does not work! you are going to have to update with sprint lovers rom, that is in a PCM36IMG.ZIP. Install it by holding the _vol and th power button, boot into boot loader, than it will search for the zip file and ask you if you want to update, say yes ans just weigh for it to be done. Its going to take few minutes first boot! just hold on. I hope this helps in anyway.
evolishesh said:
If that does not work! you are going to have to update with sprint lovers rom, that is in a PCM36IMG.ZIP. Install it by holding the _vol and th power button, boot into boot loader, than it will search for the zip file and ask you if you want to update, say yes ans just weigh for it to be done. Its going to take few minutes first boot! just hold on. I hope this helps in anyway.
Click to expand...
Click to collapse
do you think that sprintlovers rom will install even if no other rom will install? because... i was able to install Gapps.zip file just fine. but every rom i install is unsuccessful.
brtnygrey said:
do you think that sprintlovers rom will install even if no other rom will install? because... i was able to install Gapps.zip file just fine. but every rom i install is unsuccessful.
Click to expand...
Click to collapse
The springlovers rom gets flashed the same way sprint flashes there upgrades so it should
Sent from my SPH-D700 using Tapatalk
mysteryemotionz said:
The springlovers rom gets flashed the same way sprint flashes there upgrades so it should
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
ok is the install through recovery supposed to be almost instantaneous? it didn't take a minute like every other rom. and after reboot (10 minutes ago) i'm still sitting on the white htc EVO 4G screen. i don't think this is working either. but i really do appreciate your help. any other suggestions? is there anything else through recovery that I can do (since i cant make it past that) that might fix my system? anything in partition? i'm so stuck!
mysteryemotionz said:
The springlovers rom gets flashed the same way sprint flashes there upgrades so it should
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
and also... when i go into hboot, and it runs through the "checking sd" thing before i can select options... it says "no image or wrong image". what?
Nothing is working!!
Did you try a rooted RUU yet?
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs
Wipe everything twice first (just to be safe). Are you using Amon RA or Clockwork, by the way? The only other thing I can think of would be that your SD card isn't formatted properly, but that would have to mean you intentionally formatted it or put in a new one that didn't have the right files on it.
SilverZero said:
Did you try a rooted RUU yet?
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs
Wipe everything twice first (just to be safe). Are you using Amon RA or Clockwork, by the way? The only other thing I can think of would be that your SD card isn't formatted properly, but that would have to mean you intentionally formatted it or put in a new one that didn't have the right files on it.
Click to expand...
Click to collapse
i am using clockwork. i've wiped so many times... but i can't make anything happen. and, i did format the sd card eventually, but not until a couple of hours ago... and only as a last resort because nothing else worked and i've been trying to fix this since last night, so i figured it couldn't hurt. but if that is part of the problem... how can i fix it? thanks for your response. i don't know what else to do other than take it in for a switch.l but if i can get into hboot... then sprint can too... and they will see that i'm rooted and void warranty. so am i completely screwed?
I had same issue.
I just reflashed the sprintlover rom (PC36IMG.ZIP) which came with Amon_RA recovery.
Then i installed the CM6 with Amon_RA recovery and everything works fine now.
Good that i did Titanium backup few days before
This is happening to me too. Almost everything he's describing is the same. Except I installed a gapps.zip and then it wouldn't boot after that. No matter what I flash, it either gives me a status 7 error and aborts the install or it may "install successfully" but it never boots. Also tried the pc36img.zip as well. I had a nandroid backup and tried to restore that, but that aborts saying cannot flash boot image. Tried a rooted and also an unrooted stock ruu, they won't work and the .exe version on a pc can't find my phone when I plug it in and power it on. Anyone have any Ideas for me. I can get more specific error messages and hboot numbers, etc. if needed.
I think you should get Amon recovery PCIMG zip file and change recovries and try everything again... IMO
Edit: I posted the Amon file and all you have to do is rename it to PCIMG.zip. Also I think the gapps you were looking for you can find on the cm site itself or within that thread. Sorry if it sounds like I a being negative but I see alot of people get on noob and I wondered why but unfortunately its because things like this happen. In the OP for CM6 it says to use Amon and backup your keys. Now if you get your phone backup you got to first check and make sure your RSA keys are in tact unless you backed them up already.
Joeykrim has a app on the market to check or there are numerous threads on what to do. Sorry and hope it works out for you if not INS is your friend
View attachment PC36IMG-Amon-V2.2.1.zip
playya said:
I think you should get Amon recovery PCIMG zip file and change recovries and try everything again... IMO
Click to expand...
Click to collapse
some people dont like clockwork with the evo's...thats just the general feeling im getting from the boards. i just got my evo rooted and what not. i use clockwork and it has worked well for what i need.
op, try amon like has been suggested.
tailsthecat3 said:
some people dont like clockwork with the evo's...thats just the general feeling im getting from the boards. i just got my evo rooted and what not. i use clockwork and it has worked well for what i need.
op, try amon like has been suggested.
Click to expand...
Click to collapse
Yea but have you tried Amon and from what I read and this is from developers Amon has a much better handle on things as far as backing stuff up, partitions and protection of keys.
I ran Clockwork on my wifes phone because to me its simple and works with Rom manager but after a while I just said F it and switched since it was messing up my backups. Hey to each his own..
Ok, I don't believe that your device is bricked. You may have flash the wrong gapps or something, but is should be easy to fix.
First, download these 3 files and put them on the root of your SD card:
Cyanogen 6 stable for evo
Latest gapps for HDPI
Calkulin's format all
Red through first, then follow my instructions EXACTLY:
1.) Boot into recovery.
2.) Flash Calkulin's all format. This will wipe everything that needs wiping. (everything but the SD card)
3.) Without exiting recovery immediately flash the CM6 .zip. Do not flash the gapps yet.
4.) Reboot the device now. It will boot into cyanogen, but will not have market or anything. Once fully booted, reboot to recovery.
5.) Do not wipe or anything, just flash the gapps HDPI.
6.) Boot the phone and enjoy.
Evo won't load any roms, can only get into clockwork recovery
Okay, so if I try your steps, just like before The install gets almost to the end, then I get:
"assert failed: write_raw_image ("/tmp/boot.img","boot")
E:Error in /sdcard/update-cm-6.1.2-supersonic-signed.zip
(Status 7)
Installation aborted.
Sorry Playya, I wanted to try this one more time first. I'm going to try loading Amon Ra now. do I need to rename it to pcimg.zip or should i just flash the current file name?
In case it helps anyone, I have
ClockworkMod Recovery v2.5.0.1
my boot loader screen shows
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-2.10.0001
MICROP-041f
TOUBH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Oct 15 2010
Awesome, Amon Ra Worked, and now i'm up and running on cyanogen mod with google apps as well. My only problem now, is I can't backup, when I try it says oops... something went wrong! Please check the recovery log!
hcavlnch said:
Awesome, Amon Ra Worked, and now i'm up and running on cyanogen mod with google apps as well. My only problem now, is I can't backup, when I try it says oops... something went wrong! Please check the recovery log!
Click to expand...
Click to collapse
it may say oops if you battery level is low... I think Amon is so much better its just that Unrevoked puts Clockwork in with their root so people get lazy and leave it in... Amon - its the way to go.
1. Charge your battery and try again
2. Backup your wimax keys - then check how big the file is and hopefully its like 12 megs... If so keys may be ok
Hi all. I am a noob at this rooting and flashing business, and I probably did something stupid so bear with me.
The other night I rooted my Evo with Unrevoked. That same night I flashed Baked Snack 1.9 using ROM Manager. Prior to the flash, I backed up my phone using ROM Manager. It was fast and everything but I decided I wanted Gingerbread (a la Salvagemod). I backed up my phone in a similar fashion, and flashed the ROM once using ROM Manager. When rebooting, my phone became caught in a boot loop. After searching through Google for a few minutes, I learned that I simply needed to clear my cache and my dalvik cache. After clearing cache, flashing, and attempting to boot several times (all in clockworkmod... or recovery... or whatever it is called (yeah i suck)...or whichever one is orange!), I gave up and decided to restore to my second ROM Manager backup - that of Baked Snack. Error! "No files found!" I tried my previous backup. Same message.
Looking back on that, I chose "install zip from sdcard" instead of "nandroid". That was a fail.
So I decided to re-use unrevoked. Everything went fine on the PC end, but the only thing that changed on my phone, is that when it boots, it gets stuck on "htc evo" in the white screen. That and clockworkmod is now teal. I disovered the nandroid option on the recovery menu. I navigate to that, then to restore, then to my Baked Snack backup. This gave me the message "Error while flashing boot image". I tried it one more time, except instead of picking recover, I accidentally picked backup (stupid stupid careless, i know). It failed and said "Can't mount /data/!".
Then I decided to go onto xda-developers and here I am now. If you are through facepalming, I would appreciate it if anybody could help me recover my data. I believe I can still flash a completely new ROM (But what do I know? I haven't proven to be the smartest Android guy), and I don't know about you guys, but I like keeping my data.
So, uh, yeah. That's that. Help please.
I'm sorry to hear you are having issues with your phone. It looks like you still have a nandroid backup, unless you formated your SDcard. Clear data, dalvik cache, and cache then run do a restore. When using clockworks recovery clear out the data, dalvik, and cache three times.
Hope this helps.
I have performed all three wipes. After that it reads
Code:
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Error while flashing boot image!
Same as before... Any thoughts? Could the boot.img file be corrupted?
***bump***
Edit: Ive read around some more and heard 2 things. 1) If I just try recovering over and over again, nandroid will eventually give in. 2) the battery has to be 70% or higher or nandroid will just keep giving error messages.
Either way, I'll juice up my battery and report back later.
Have you tried to just do a wipe and reflash the ROM.
Have you tried to use Amon recovery? That seems to work better than clockworks. You can get that here: http://forum.xda-developers.com/showthread.php?t=705026
bccbryan said:
Have you tried to just do a wipe and reflash the ROM.
Click to expand...
Click to collapse
Yes. I tried it again just now because I was feeling lucky. Salvage Mod went smoothly, except it got stuck on the white htc screen when I rebooted. Baked Snack gave me an error message:
Code:
E:Can't open /sdcard/download/BakedSnack1.9.evo.zip
(bad)
Installation aborted
Have you tried to use Amon recovery? That seems to work better than clockworks. You can get that here: http://forum.xda-developers.com/showthread.php?t=705026
Click to expand...
Click to collapse
I'll try that tomorrow morning. Right now I'm gonna get some sleep before I do any more damage to my phone lol. Expect more questions from me about WiMAX and what to do with that .img file (if anything at all).
Do you have the latest radio/wimax? If not run Calkulin radio combo. http://forum.xda-developers.com/showthread.php?t=715485
I believe if you don't update your radio and are running a certain kernel you will get a bootloop, but don't quote me on that.
Does Hboot say s-off or s-on? Here is a rooting info and faqs. http://forum.xda-developers.com/showthread.php?t=865204
bccbryan said:
Do you have the latest radio/wimax? If not run Calkulin radio combo. http://forum.xda-developers.com/showthread.php?t=715485
Click to expand...
Click to collapse
I'm 95% sure that I do, I got my EVO in December.
Does Hboot say s-off or s-on? Here is a rooting info and faqs. http://forum.xda-developers.com/showthread.php?t=865204
Click to expand...
Click to collapse
It says S-OFF, so that's good news.
And as to Amon_RA, because I'm doing "the bootloader way", then I don't need the recovery-RA-supersonic-v2.3.img file?
When I try to recover, it givese me an error saying that the nandroid directory could not be found. I have my backups in a folder called /sdcard/clockworkmod/backup/NameOfTheRecoveryFolder/. Should I just copy the files in the backup folder to a folder on the root of the card called "nandroid"?
And as to Amon_RA, because I'm doing "the bootloader way", then I don't need the recovery-RA-supersonic-v2.3.img file?
Click to expand...
Click to collapse
Yep...just need the PC36IMG.zip and boot to the bootloader.
Since you got your phone last December I think you need to run a rom that is based off the latest code. If you are running htc sense it should be based off 3.70.651.1. For ASOP run the lastest ones.
Here is a nice wiki of the ROMs for the EVO http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs
Forgot to mention for the zip files you place on your sdcard for flashing check the MD5 hash before flashing your phone.
When I got my EVO the SD card went bad in about 2 months. Fortunately for me Sprint was nice enough to replace my sdcard. Since, then I have upgraded my sdcard to a 32GB sandisk.
bccbryan said:
Forgot to mention for the zip files you place on your sdcard for flashing check the MD5 hash before flashing your phone.
When I got my EVO the SD card went bad in about 2 months. Fortunately for me Sprint was nice enough to replace my sdcard. Since, then I have upgraded my sdcard to a 32GB sandisk.
Click to expand...
Click to collapse
This would be the file called "nandroid.md5"? I'm confused.
OK so I boot into recovery, go to Nandroid restore > BackupName
I am presented with a list of options:
boot.img
recovery.img
wimax.HT0CRHL08393.img
system.img
data.img
cache.img
nandroid.md5
Do I just run each of these individually or am I doin it wrong?
Don't do a nandroid restore. Flash a ROM onto your phone.Fresh EVO or Myn’s Warm TwoPointTwo are good ones to try.
Works great! I lost all my data but I'd rather have a wiped phone than a dead one!
Thanks!
When you used Unrevoked to root your phone it also downloaded Clockwork Mod recovery v. 2.6.0.1. This is what you probably used to do your original backup right after you rooted your phone (http://forum.xda-developers.com/showthread.php?t=895208). You need to go back to this version so you can restore any backups you may have made right after you rooted your phone. Here is an article by Koush explaining why you may be having problems. At the bottom he has v.2.6.0.1. Install it on your phone and then proceed restoring your backup.
Also, I'm going to suggest to you that you read the articles below to get you familiar with rooting, and then I suggest you read some more on these and other forums. Learn the rooting vocabulary and processes involved (rooting, nandroid backup, recoveries, flashing ROMs, kernels, etc.). Also, try and read up on problems people have rooting, flashing ROMs, and troubleshooting should something go wrong. You want to be able to get yourself out of a mess should problems arise. Most importantly, you want to know what you're doing so you don't brick your phone.
http://forum.xda-developers.com/showthread.php?t=865204
http://forum.xda-developers.com/showthread.php?t=790427
http://forum.xda-developers.com/showthread.php?t=881747
http://htcevorooting.x10.mx/wiki/ind...itle=Main_Page
http://androidforums.com/evo-4g-all-...g-dummies.html
hello all, noob here. searched the forums already, not quite the same problem here.
I just rooted my phone with unrevoked 3.32, had zero problems. I confirmed that i had nand unlocked in hboot (says S-OFF). I started up my phone without problems after rooting, checked and I had superuser permissions in the app drawer. i then proceeded to download busybox, rom manager, my backup for root, and titanium backup from the market, but I did NOT open any of them. I thought I would do a nandroid backup first.
I rebooted into hboot, went to recovery. this started up clockworkmod (that came with unrevoked 3.32), went to backup and restore, and hit nandroid backup. It completed, said done, then i selected "go back" and selected the first option, reboot system now.
I then tried to turn my phone on, just regular power on not into hboot, and i get stuck at the white htc evo 4g screen, it then reboots, and continues to cycle up to that point.
I have NOT flashed anything other than rooting my phone. i haven't wiped anything, done anything else than what i have there.
Hboot version is 2.10
radio version says 2.15.00.11.19
clockworkmod version is 2.6.0.1
EVO is from June 2010, not a new evo.
I can get into hboot and recovery, no problems, but i can't startup the phone.
Please help! i just want to start up the phone, don't want to flash anything yet. Thanks in advance.
Maybe its the busybox that you downloaded. You should hit up recovery and do a full wipe! The start up again. What rom are you running, most roms have busybox included so when you download it I've seen phones get the white screen of death. Grab a rom and reflash it. Since you put busybox that nandroid you made probably is no good. Reason I'm telling you all this is because has happened to me before. Good luck
Sent from my PC36100 using XDA Premium App
ravissimo said:
hello all, noob here. searched the forums already, not quite the same problem here.
I just rooted my phone with unrevoked 3.32, had zero problems. I confirmed that i had nand unlocked in hboot (says S-OFF). I started up my phone without problems after rooting, checked and I had superuser permissions in the app drawer. i then proceeded to download busybox, rom manager, my backup for root, and titanium backup from the market, but I did NOT open any of them. I thought I would do a nandroid backup first.
I rebooted into hboot, went to recovery. this started up clockworkmod (that came with unrevoked 3.32), went to backup and restore, and hit nandroid backup. It completed, said done, then i selected "go back" and selected the first option, reboot system now.
I then tried to turn my phone on, just regular power on not into hboot, and i get stuck at the white htc evo 4g screen, it then reboots, and continues to cycle up to that point.
I have NOT flashed anything other than rooting my phone. i haven't wiped anything, done anything else than what i have there.
Hboot version is 2.10
radio version says 2.15.00.11.19
clockworkmod version is 2.6.0.1
EVO is from June 2010, not a new evo.
I can get into hboot and recovery, no problems, but i can't startup the phone.
Please help! i just want to start up the phone, don't want to flash anything yet. Thanks in advance.
Click to expand...
Click to collapse
Well, I'm not sure what exactly went wrong for ya, but I might suspect it was something to do with some of the apps you downloaded prior to making your backup. The first thing to try, would be to boot to recovery, and wipe cache, and then go to 'advanced' and wipe dalvik cache. Then try to reboot. If that fails, then you're next option (without flashing a new ROM) is to do a data/factory reset. You will however lose all of your apps, settings, contacts, texts, etc. You unfortunately don't really have any other options, unless wiping cache's helps you out. If a factory reset doesn't allow you to boot, then you're most likely going to have to flash a new ROM. And also, I thought that Unrevoked flashed the latest clockwork recovery, which would be 3.0 or somehting like that, no?
Hi k2buckley,
So I tried wiping the cache and the dalvik cache then rebooted, no luck. Does this mean the nandroid backup I made is also corrupt? Restoring that won't do anything will it? So the options are to do a factory reset or flash a new rom? If I lost everything anyway, I might as well try to flash a new rom.
However, to clarify, I didn't "install" busybox. I downloaded the app but I didn't open it up and click install. So even if I flash a new rom, then I install busybox and do a nandroid backup it will work? If so, why didn't it work this time? If I do a factory reset, then do the same thing and install busybox, will the same thing happen? Is busybox incompatible with the sense froyo that comes from the sprint OTA?
ravissimo said:
Hi k2buckley,
So I tried wiping the cache and the dalvik cache then rebooted, no luck. Does this mean the nandroid backup I made is also corrupt? Restoring that won't do anything will it? So the options are to do a factory reset or flash a new rom? If I lost everything anyway, I might as well try to flash a new rom.
However, to clarify, I didn't "install" busybox. I downloaded the app but I didn't open it up and click install. So even if I flash a new rom, then I install busybox and do a nandroid backup it will work? If so, why didn't it work this time? If I do a factory reset, then do the same thing and install busybox, will the same thing happen? Is busybox incompatible with the sense froyo that comes from the sprint OTA?
Click to expand...
Click to collapse
You don't need to download busy box, I would delete that app. If you flash a rooted rom it should already have busybox; if you just rooted your phone and want to download busybox on your current stock rom then it will be ok. I would wipe and flash a new rom just to be safe.
Sent from my PC36100 using XDA Premium App
ravissimo said:
Hi k2buckley,
So I tried wiping the cache and the dalvik cache then rebooted, no luck. Does this mean the nandroid backup I made is also corrupt? Restoring that won't do anything will it? So the options are to do a factory reset or flash a new rom? If I lost everything anyway, I might as well try to flash a new rom.
However, to clarify, I didn't "install" busybox. I downloaded the app but I didn't open it up and click install. So even if I flash a new rom, then I install busybox and do a nandroid backup it will work? If so, why didn't it work this time? If I do a factory reset, then do the same thing and install busybox, will the same thing happen? Is busybox incompatible with the sense froyo that comes from the sprint OTA?
Click to expand...
Click to collapse
Well, I'm not exactly sure why you want to download busy box so badly. Any rom comes with busy box cooked in. I have only once installed busy box. The only time i remember having to do it, was Immediately after I rooted with Unrevoked, i went to use Titanium, and had some error. I hit the problems button and that updated busy box from there. Other than that, I've never messed with it.
And yes, most likely your nandroid backup is not going to be of any value to you. You could try restoring it if you'd like, but I predict it would be a waste of time. And I'm not sure that it matters that you didn't 'open' and click install on busy box. If you downloaded it from the market, wouldn't it just download and install itself automatically? I would just flash a rom, and be done with it. Roll with whatever version of busy box comes with the ROM you flash. As you said, you're only option is a factory reset now, and if you're going to do that, you certainly may as well flash a custom rom at the same time. You just need to download a rom, and put it on your sd card. You can mount the sd card as a disk drive to your computer from within recovery. I use amon ra, and its called USB MS TOGGLE. I'm not sure what it's called in clockwork, but the option is there. So put the rom on your sd card, perform a complete wipe, (i'd flash calkulin's format all.zip as well), flash a rom, reboot, and forget about anything with busy box. It will be installed on the rom already.
If you download busybox from the market and it already has it built in the rom you might bork the rom and get a bootloop. Try it and see for yourself !
Sent from my PC36100 using XDA Premium App
Well, the only reason I download busybox was because I wanted to use titanium backup and it is required. Other than that, I could care less about it. It does not install automatically after downloading. You have to go into the app and choose which version you want to install and I didn't install it. The thing is I didn't want to install any roms in the first place. I wanted to just root the phone for the purpose of wifi tethering. So basically my better option is doing a factory reset.
I won't be able to do this til I get home in a few hours, so if anyone else has any suggestions on how to fix this without losing my data, I would appreciate any tips. Thanks.
If you can get a logcat that should show what is causing it to bootloop. It's 'adb logcat > logcat.txt' to do it, run that and wait for it to loop 3 or 4 times before pushing Ctrl+C to stop it.
Busybox isn't included in the ROM because I didn't flash a ROM! I'm using the sense 2.2 froyo Ron that comes from sprint and HTC. I didn't flash anything as I stated in the title. I just did a nandroid backup and now my phone won't boot.
ravissimo said:
Well, the only reason I download busybox was because I wanted to use titanium backup and it is required. Other than that, I could care less about it. It does not install automatically after downloading. You have to go into the app and choose which version you want to install and I didn't install it. The thing is I didn't want to install any roms in the first place. I wanted to just root the phone for the purpose of wifi tethering. So basically my better option is doing a factory reset.
I won't be able to do this til I get home in a few hours, so if anyone else has any suggestions on how to fix this without losing my data, I would appreciate any tips. Thanks.
Click to expand...
Click to collapse
Right. But unfortunately now, your data seems to be lost. Did a factory reset help anything? If not, you got to wipe and reflash a rom.
Sent from my PC36100 using XDA App
ravissimo said:
Busybox isn't included in the ROM because I didn't flash a ROM! I'm using the sense 2.2 froyo Ron that comes from sprint and HTC. I didn't flash anything as I stated in the title. I just did a nandroid backup and now my phone won't boot.
Click to expand...
Click to collapse
I understand that. As I stated, I'm not sure what's causing your problem. As xhausx said, try getting a logcat
Sent from my PC36100 using XDA App
What method of rooting did you use? What recovery do you have right now? As hausx said you could do a logcat and he'll check it out!
Sent from my PC36100 using XDA Premium App
Hi xHausx,
I will have to wait til I get home to try that, but how do I get into the prompt to type that in dos. Do I need to run anything in hboot or clockworkmod before connecting my Phone and trying that? I am a noob, so even though I've read a lot before rooting, I don't know much. Please assume I need a step by step. Thanks again.
ravissimo said:
Hi xHausx,
I will have to wait til I get home to try that, but how do I get into the prompt to type that in dos. Do I need to run anything in hboot or clockworkmod before connecting my Phone and trying that? I am a noob, so even though I've read a lot before rooting, I don't know much. Please assume I need a step by step. Thanks again.
Click to expand...
Click to collapse
You can use the root tools zip from the link in my sig to get to adb, there is a script in there called OpenShell that will bring up a dos prompt in the right folder. Rooting should have enabled adb during boot so you should be ok on that end.
xHausx said:
You can use the root tools zip from the link in my sig to get to adb, there is a script in there called OpenShell that will bring up a dos prompt in the right folder. Rooting should have enabled adb during boot so you should be ok on that end.
Click to expand...
Click to collapse
OK, so I downloaded and extracted the auto-root tools only zip from your sig, and then ran OpenShell.bat and typed as you said "adb logcat > logcat.txt" with my phone plugged in. said "waiting for device" and then i turned on my phone and let it boot 4-5 times before ctrl+c and pulling the usb. all the logcat.txt says is...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
am i doing something wrong?
my apologies, i've only throughly read on how to root, i hadn't gotten into flashing or anything else yet. just been on xda site for a few days now reading all i could about rooting (which went fine, but now i'm screwed).
dirkyd3rk said:
If you download busybox from the market and it already has it built in the rom you might bork the rom and get a bootloop. Try it and see for yourself !
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
For the hell of it I did just that and it did bork it.... lmao
chefdave12118 said:
For the hell of it I did just that and it did bork it.... lmao
Click to expand...
Click to collapse
Did it really? Lol It did it to me man I was pissed!
chefdave12118 said:
For the hell of it I did just that and it did bork it.... lmao
Click to expand...
Click to collapse
man, for the life of me, i can't believe i didn't do a nandroid before i downloaded the app. for some reason i thought only downloading an app from the market, not flashing anything or whatever, would not screw up my phone.
anyway, since my data is lost, i wanted to try again. can i flash the unrevoked S-ON utility and then the latest Sprint RUU and then re-root? i read somewhere else that it won't remove my wimax/RSA keys or SD card, is that correct? is there a way to backup my RSA keys before I do anything else? should i do that, re-root, then nandroid, then mess with stuff? i basically wanted a stock Sprint EVO but one that's rooted so i can run root-based apps, that's what I want to get to.
Flash the Amon Ra recovery via the AR pc36img.zip file in hboot method, then reboot to recovery, do a full wipe/factory reset and try to boot to system.
T989 without any SD card in it, the one I had died apparently new one on order. Went to flash the latest PA rom but kept getting error 7 using CWM. I updated my recovery to the latest TWRP and still will not flash. I tried updating to the newest radio UVMC6, but that wont flash. I am currently on CM10.1 nightly. My process for flashing is recovery, superwipe, flash, which is when the flash errors out and I re wipe and then I can flash my CM10 back on. So I can flash CM10 all day long but nothing else. I searched on here and found that the ATT version of this phone has this problem and you have to flash an AOKP and then flash whatever you want, other phones with similar problems say use ODIN and flash stock and then go from there. I am just looking for any advice on this situation. I could not find anything specific enough in my search to help me and I am hoping someone here can. Thanks in advance.
Note: I have also tried flashing CM10.1 RC5 and has the same problems.
moebawlz said:
T989 without any SD card in it, the one I had died apparently new one on order. Went to flash the latest PA rom but kept getting error 7 using CWM. I updated my recovery to the latest TWRP and still will not flash. I tried updating to the newest radio UVMC6, but that wont flash. I am currently on CM10.1 nightly. My process for flashing is recovery, superwipe, flash, which is when the flash errors out and I re wipe and then I can flash my CM10 back on. So I can flash CM10 all day long but nothing else. I searched on here and found that the ATT version of this phone has this problem and you have to flash an AOKP and then flash whatever you want, other phones with similar problems say use ODIN and flash stock and then go from there. I am just looking for any advice on this situation. I could not find anything specific enough in my search to help me and I am hoping someone here can. Thanks in advance.
Note: I have also tried flashing CM10.1 RC5 and has the same problems.
Click to expand...
Click to collapse
For onw those superwipe scripts are not needed with twrp, u might be getting the error from that, are u trying to flash from internal SD card since ur external died? That might cause it but I don't think so, I would suggest trying a manual wipe of all partitions, data, system, cache, dalvik, 2x , then flash, if that doesn't work try using Odin, go back to stock and start over, that should fix it definetly
Sent from my SGH-T989 using xda premium
soupysoup said:
For onw those superwipe scripts are not needed with twrp, u might be getting the error from that, are u trying to flash from internal SD card since ur external died? That might cause it but I don't think so, I would suggest trying a manual wipe of all partitions, data, system, cache, dalvik, 2x , then flash, if that doesn't work try using Odin, go back to stock and start over, that should fix it definetly
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Thank you... I wasnt sure about superwipe on TWRP since I just put it on and came from CWM. I am trying to flash from the internal card and the new external card will be at my doorstep tomorrow so I will drop that in as well. I will drop back in once I get all this done and hopefully all goes well.
Again thanks.
moebawlz said:
Thank you... I wasnt sure about superwipe on TWRP since I just put it on and came from CWM. I am trying to flash from the internal card and the new external card will be at my doorstep tomorrow so I will drop that in as well. I will drop back in once I get all this done and hopefully all goes well.
Again thanks.
Click to expand...
Click to collapse
Good glad I can help, let me know how it all goes, now I'm interested lol
Sent from my SAMSUNG-SGH-T989 using xda premium
Ok so I got my new SD card. Tossed that in, just figured I would try flashing from the external, no luck there. Same issues.
Odin back to stock using this tutorial http://forum.xda-developers.com/showthread.php?t=1513359&page=3
Used http://forum.xda-developers.com/showthread.php?t=2195283 this to regain root.
Got CWM back on but now I cannot flash SuperUser
When I go to flash Superuser it says
Mounting System
Deleting System:bin/su...
Deleting System:xbin/su
Extracting files to SYSTEM
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
E: Error in /emmc/Superuser-3.0.7-efghi-signed.zip
(Status 0)
Installation aborted
So on the plus side I didn't brick the phone... downside now I am back to Gingerbread and currently stuck here...
Possibly a bad zip file?
Any ideas on this?
Quick update... I am a moron... Did not realize that root is kept with this restore... Got Superuser from market and am good to go.
Installing TWRP now and will have an update on the flash soon.
OK... the fun seems to have just begun
I cannot install TWRP from GooManager. No clue why, looking on here and I found //techerrata.com/browse/twrp2/hercules (cant link too new of a member)
So as it seems I can download the .img and GooManager should see it and if that doesnt happen I can install it through the terminal with these commands
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
OR flash it with ODIN... Which I would assume I get the .tar file and follow the same process as putting the recovery files in?
Aside from TWRP being an issue, I tried installing the PA rom with CWM and I got this:
Installing update
set_perm:some changes failed
E:Error in /sdcard/pa_hercule...zip
(Status 7)
Installation aborted
The same error I had in the first place
moebawlz said:
OK... the fun seems to have just begun
I cannot install TWRP from GooManager. No clue why, looking on here and I found //techerrata.com/browse/twrp2/hercules (cant link too new of a member)
So as it seems I can download the .img and GooManager should see it and if that doesnt happen I can install it through the terminal with these commands
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
OR flash it with ODIN... Which I would assume I get the .tar file and follow the same process as putting the recovery files in?
Aside from TWRP being an issue, I tried installing the PA rom with CWM and I got this:
Installing update
set_perm:some changes failed
E:Error in /sdcard/pa_hercule...zip
(Status 7)
Installation aborted
The same error I had in the first place
Click to expand...
Click to collapse
I'm not sure what your overall problem is, but if you are going to install TWRP do not use Goo Manager or the img file. They have been messing up peoples phones. Odin the tar or try the zip from the TWRP thread.
meekrawb said:
I'm not sure what your overall problem is, but if you are going to install TWRP do not use Goo Manager or the img file. They have been messing up peoples phones. Odin the tar or try the zip from the TWRP thread.
Click to expand...
Click to collapse
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Along with that after I got TWRP working through Goo Manager again I tried flashing PA again and I had the same error as I did in the first place.
Maybe my phone just hates anything but the nightly I had before...
moebawlz said:
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Click to expand...
Click to collapse
If you can boot into TWRP, then they must have fixed the Goo problem.
It seems like you have tried most everything. Maybe you should Odin back to stock. If you are comfortable doing it, that is.
i went to flash with goo last night and it bricked the phone kind of, i had to ODIN and reflash the CWM again and bam the phone rebooted no problem
meekrawb said:
If you can boot into TWRP, then they must have fixed the Goo problem.
It seems like you have tried most everything. Maybe you should Odin back to stock. If you are comfortable doing it, that is.
Click to expand...
Click to collapse
I did Odin back to stock before. I am still on stock gingerbread right now with root access and am getting the errors I have been. I followed the tutorials in the sticky thread that I posted before that got me back to stock.
Within TWRP I tried installing the newest Cyanogen Mod and got
E:Error executing updater binary in zip
Error flashing zip
When I try installing the PA rom I get the same error
Any thoughts? Would going back to stock through Odin and doing this again potentially fix it? or is that a shot in the dark?
Lucky for me I kept a backup saved on my PC from before I did anything here. So I am back to the CM 10.1 Nightly I started on for the time being.
Is there any other method of flashing a rom that I might be able to try?
moebawlz said:
I did Odin back to stock before. I am still on stock gingerbread right now with root access and am getting the errors I have been. I followed the tutorials in the sticky thread that I posted before that got me back to stock.
Within TWRP I tried installing the newest Cyanogen Mod and got
E:Error executing updater binary in zip
Error flashing zip
When I try installing the PA rom I get the same error
Any thoughts? Would going back to stock through Odin and doing this again potentially fix it? or is that a shot in the dark?
Click to expand...
Click to collapse
It would be a shot in the dark. I did a Google search for your error and a couple of people said they were able to fix it by using TWRP 2.3. That was for different phones though. Maybe try that before going stock.
I am by no means a pro at this and am still learning as I go. Just to make sure of what I am doing, can I Odin TWRP 2.3? I also found this
http://forum.xda-developers.com/showthread.php?t=1639673
or
http://forum.xda-developers.com/showthread.php?t=1658418
Just a thought here... I keep gettin emmc errors... I was reading about upgrading and downgrading TWRP through the Terminal Emulator and it said use emmc or sdcard depending on what the phone reads it as.
When I first got the phone i recall seeing emmc when i would go into any file browser. Now it just says sdcard0 (internal) & sdcard1 (external)
So how can I get recovery to stop looking for emmc and start looking for sdcard0?
Unless I am way off in left field here with this.
moebawlz said:
I am by no means a pro at this and am still learning as I go. Just to make sure of what I am doing, can I Odin TWRP 2.3?
Click to expand...
Click to collapse
Yes, use Odin and the 2.3.3.0 tar from the techerrata website. I like using the Odin method because I have never had a problem upgrading recovery that way. I don't know about the emmc errors because I have only used the dd method like twice.
Edit: Maybe your internal memory is corrupted? I'm not sure how to test for that though.
moebawlz said:
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Along with that after I got TWRP working through Goo Manager again I tried flashing PA again and I had the same error as I did in the first place.
Maybe my phone just hates anything but the nightly I had before...
Click to expand...
Click to collapse
I think u must be getting bad DL then because none of that sounds right lol, if u got twrp to load into your device and all is working fine then the only other option is a bad DL, try checking the DL with a root browser or something to see the size of the file, status 7 errors are from the zip, usually bad install script in the ROM, which could be caused by a bad DL, check the DL size and let me know
Sent from my SGH-T989 using xda premium
went back to 2.3.3 and still having the same error.
Is there a way to correct any possible errors in my internal memory?
moebawlz said:
went back to 2.3.3 and still having the same error.
Is there a way to correct any possible errors in my internal memory?
Click to expand...
Click to collapse
If the DL is good, I don't know what else to tell u that is very strange indeed, but interesting too, I've never not been able to install at all, I'm curious..
Sent from my SGH-T989 using xda premium