Database Info

Cant update ROM. What am I doing wrong

I have a NS unlocked and rooted. I have ROM Manager, busybox etc. I followed all the instructions but I can't update ROMs or the 2.3.3 update or CM7 nothing. Each time it starts to unpack or whatever it gets about 1/3 the way and aborts. Something about verifying signatures or something.
Very frustrating.
Thanx in advance
I Love The Smell Of Burnt Rubber Anytime

try to download the ROM again
sounds like the zip file is corrupted

What version Clockwork Recovery are you using? Try reverting back to a older version or something.
Verify the ROM's MD5 Hash using HashTab (Google it)

I've tried several times with downloads and now the latest clockwork and the version prior.
Samething always aborts, can't verify signature. Tried manual and through rom manager.
When using rom manager is that suppose to do the whole install? Cuz that only gets me to the little droid and the triangle. I have to get myself into bootloader and continue manually from there.
Thanks
I Love The Smell Of Burnt Rubber Anytime

hllywd said:
I've tried several times with downloads and now the latest clockwork and the version prior.
Samething always aborts, can't verify signature. Tried manual and through rom manager.
When using rom manager is that suppose to do the whole install? Cuz that only gets me to the little droid and the triangle. I have to get myself into bootloader and continue manually from there.
Thanks
I Love The Smell Of Burnt Rubber Anytime
Click to expand...
Click to collapse
what's the latest clockwork recovery? did you try 3.0.0.5?

Ya. The new ver is 3.0.2.4
I Love The Smell Of Burnt Rubber Anytime

hllywd said:
I've tried several times with downloads and now the latest clockwork and the version prior.
Samething always aborts, can't verify signature. Tried manual and through rom manager.
When using rom manager is that suppose to do the whole install? Cuz that only gets me to the little droid and the triangle. I have to get myself into bootloader and continue manually from there.
Thanks
I Love The Smell Of Burnt Rubber Anytime
Click to expand...
Click to collapse
Hmm... It sounds like clockwork isn't properly installed. ROM Manager should take you directly to clockwork recovery without you having to do anything.

the problem you are facing is that you are still on stock rom. so even if you flash clockwork recovery and then reboot to recovery, you'll always end up going to the stock recovery. this is a new feature implemented by google.
what you should do is...
1) go to bootloader
2)flash the clockwork recovery using fastboot
3)DO NOT reboot the phone or quit bootloader. immediately after flashing the rec. using fastboot, just enter recovery (through bootloader)
4)flash you new rom
just for u to have an idea. the recovery should be orange in colour.
option 2.
you also have the option of using a file manager with moun/root functions such as root explorer and rename the recovery script in etc folder but i guess step 1 is much easier for now.

OK I played alot today and this is what happened.
After fixing permissions and flashing the new CWM and wiping data/cache it finally worked. Unfortunately titanium and my backup didnt bring everything over. So I went back and forth between stock and CM7 several times but I just couldnt get all my stuff back in CM7. So I thought Id try the 2.3.3 update but not wiping stuff. That didnt work. Then I tried one more time with CM7 but not wiping. I couldnt get pastthe little CM7 droid on the skateboard. So went back to stock for now. Ill have more time on Sat to give things another try.
At least I can get in it now.
Any ideas/thoughts/
Thanks and sorry for the long post.

[Q] Please help: I think I'm soft-bricked.

Well, okay, technically I'm not actually even totally sure what soft-bricked means, but while I can get to both a fastboot screen and into what appears to be CWM (orange recovery with more options than blue), my phone is hanging on the Google boot screen.
Here's what I did.
I have a rooted Nexus S that was running 2.3.3 stock. The OTA update notification came up today, so I allowed it. But then it seemed to hang for, like, half an hour.
So I pulled the battery and allowed it to reset. Which was fine, no biggie. I still had 2.3.3, but no longer had root. So I flashed the GRI40 superboot. Still fine. But I no longer had an update, and it was still 2.3.3.
So I flashed CWM and went to the 2.3.3 stock image. CWM downloaded said image, didn't seem to have any problems, and I clicked to wipe the cache and dalvik.
And now it won't boot beyond the Google screen. But like I said, I'm on fastboot screen now (unlocked) and seem to still have clockwork. Nothing else, though, and there's nothing on my sd card. I know, I know, the lack of back up is a noob mistake.
Help? I'd really just like to get to stock but rooted 2.3.4.

http://forum.xda-developers.com/showthread.php?t=947950
Use this i have got the same problem
that solved

prad1po said:
http://forum.xda-developers.com/showthread.php?t=947950
Use this i have got the same problem
that solved
Click to expand...
Click to collapse
A couple of the other threads by people with hard bricks (problem today?) mentioned Odin as problematic. It's okay to use?

Also, I have to admit, I see a lot of discussion of Odin in the forums, and have Googled it, but I don't actually know what it is or how to use it.

willentrekin said:
Also, I have to admit, I see a lot of discussion of Odin in the forums, and have Googled it, but I don't actually know what it is or how to use it.
Click to expand...
Click to collapse
Odin is the Fkash program from samsung to flash the lhine first time
you have CWM? no need of odin!
reboot into cwm --> mounts & storage --> mount usb
search a the deoxed 2.3.4 rom and download it..
also search the forum for superuser binary to flash
then wipe system and cache
flash zip first the rom then superuser
reboot
have fun

Okay. Almost there, I think.
You're right about CWM. I got it mounted okay, and get a drive on my computer, into which I can copy a zip and then unmount. At which point I get:
Installing {whichever zip I try. So far, I've tried Nandroid Stock 2.3.4_rooted and 2.3.2 GRH78c}
Finding update package...
Opening update package...
Installing update...
Installation aborted.
That's as far as I get right now. And I'm not touching anything. I wiped the data and cache. Do I have to further mount/unmount anything?

willentrekin said:
Okay. Almost there, I think.
You're right about CWM. I got it mounted okay, and get a drive on my computer, into which I can copy a zip and then unmount. At which point I get:
Installing {whichever zip I try. So far, I've tried Nandroid Stock 2.3.4_rooted and 2.3.2 GRH78c}
Finding update package...
Opening update package...
Installing update...
Installation aborted.
That's as far as I get right now. And I'm not touching anything. I wiped the data and cache. Do I have to further mount/unmount anything?
Click to expand...
Click to collapse
wipe system too? :/
do you have the latest recovery?
maybe you have a nandroid backup anywhere?
else download one at the dev section i think are enough backups
copy one to /clockwork/backup/***DATE***
hope that fixes your problem :S
Sent from my Nexus S using XDA App

willentrekin said:
Well, okay, technically I'm not actually even totally sure what soft-bricked means, but while I can get to both a fastboot screen and into what appears to be CWM (orange recovery with more options than blue), my phone is hanging on the Google boot screen.
Here's what I did.
I have a rooted Nexus S that was running 2.3.3 stock. The OTA update notification came up today, so I allowed it. But then it seemed to hang for, like, half an hour.
So I pulled the battery and allowed it to reset. Which was fine, no biggie. I still had 2.3.3, but no longer had root. So I flashed the GRI40 superboot. Still fine. But I no longer had an update, and it was still 2.3.3.
So I flashed CWM and went to the 2.3.3 stock image. CWM downloaded said image, didn't seem to have any problems, and I clicked to wipe the cache and dalvik.
And now it won't boot beyond the Google screen. But like I said, I'm on fastboot screen now (unlocked) and seem to still have clockwork. Nothing else, though, and there's nothing on my sd card. I know, I know, the lack of back up is a noob mistake.
Help? I'd really just like to get to stock but rooted 2.3.4.
Click to expand...
Click to collapse
Just download the 2.3.4 (stock rooted) file on here...in the de section...
its a nandroid back up
then just put it in the clockworkdmod/ folder on your phone
reboot into recovery and restore it
viola!
thats what i did to get mine rooted...its way easier than trying to actually root it!
edit: yeah what the post above mine said...lol..didnt see that posted yet!

Okay. Followed guidance. Still hanging but maybe getting closer.
I made a backup of the borked system, and then went into the clockwork folder and created a new folder within the backups. I unzipped the 2.3.4root ROM and renamed the folder to almost the same name as the borked system. I then tried to restore that.
I got an MD5 fail? I'm not sure what that means.
Maybe I should replace all the files in the legit-made backup with the files from 2.3.4?

Awesome! I got it! I went and got Axura's 2.3.3 stock/rooted and installed that from the zip. I don't know why the other two aborted, but this one worked. So it looks like I've got rooted stock 2.3.3 again!
I'm not so sure I'm going to try for 2.3.4 now.
Thanks for the help!

Flashing new rom

My buddy has the inspire 4g. He bought it rooted by somebody else. I've flashed cynogenmod for him aqnd several updates over the past few months. We are trying to flash new roms and its constantly aborting. Ive rooted my droids and always flash roms and never run into this problem.
He has the newest clockwork mod should we possible get a different recovery?
I don't do anything with flashing a new radio, is that necesary and whats causing the problem?
I am trying to flash core droid or revolution, he wants the best sense rom any suggestions?
I would appreciate any help. If there is no way to fix it I planned to totally reset and unroot and then root it myself and make sure everything is done right, does that sound right?

dieseldank said:
If there is no way to fix it I planned to totally reset and unroot and then root it myself and make sure everything is done right, does that sound right?
Click to expand...
Click to collapse
Though probably not necessary, the peace of mind that comes with knowing what's been done to the phone from the ground up might be worth it.
As for a fix to your current issue, please provide a little more detail as to the error.

It clears the cache and everything like that but it has a line that says installing update then the next line is installation aborted. That happens very quickly when I try to apply the update.zip

dieseldank said:
It clears the cache and everything like that but it has a line that says installing update then the next line is installation aborted. That happens very quickly when I try to apply the update.zip
Click to expand...
Click to collapse
Is this the same SD card for every try? It might be a flakey SD card. Try a different card if you can.

I have several sd cards so will try the one I use. Am going over to help him in a few hours. Anyone have other suggestions? Should I be able to just flash a rom or do I have to flash a new radio also? <Because Ive only done cynogen on his which didnt have a radio.
Thanks again.

dieseldank said:
I have several sd cards so will try the one I use. Am going over to help him in a few hours. Anyone have other suggestions? Should I be able to just flash a rom or do I have to flash a new radio also? <Because Ive only done cynogen on his which didnt have a radio.
Thanks again.
Click to expand...
Click to collapse
Radio is not usually flashed as part of the ROM. As long as you have a valid radio, it should work. If you somehow managed to get an invalid radio flashed, then you've have bigger problems that you indicate (i.e. hard bricked).
The fact that you can boot into recovery indicates that all it well with the device from that perspective. That leaves only the ROM zip to be flashed which is why I suggested trying a different SD card (since you tried several, it's not likely that you always got a bad download).
If it still messes up with a new SD card, try complete wipe, then format system from nandroid before running the update.zip. System partition doesn't get formatted during a complete wipe, but most ROMs should format it as a matter of course before installing. It's unlikely, but it could be a corrupt system partition which should clean up with a format.

dieseldank said:
I have several sd cards so will try the one I use. Am going over to help him in a few hours. Anyone have other suggestions? Should I be able to just flash a rom or do I have to flash a new radio also? <Because Ive only done cynogen on his which didnt have a radio.
Thanks again.
Click to expand...
Click to collapse
Wanna Save yourself some time and maybe some future headaches? Like posted above It helps when you know what has been done. I would start from the ground up. Get back to a stock base and go from there, this way you are not trying to track down something you may not have done but was done before he got it.
As for your issue, If a radio is recommended then it will/should state so in the thread.

I have threads on how to root his inspire but can anyone forward a link of how to completely unroot and reset. When i reset in recovery it still keeps cynogenmod on.

dieseldank said:
I have threads on how to root his inspire but can anyone forward a link of how to completely unroot and reset. When i reset in recovery it still keeps cynogenmod on.
Click to expand...
Click to collapse
There's no good reason to go through all that trouble. If you have S-OFF, then you're good to go as far as being rooted is concerned. Since you appear to have recovery too, then you're 95% rooted no matter what the current ROM is doing.
If you have S-OFF already, then going back to stock and rerooting is just going to waste time.

dieseldank said:
It clears the cache and everything like that but it has a line that says installing update then the next line is installation aborted. That happens very quickly when I try to apply the update.zip
Click to expand...
Click to collapse
In cwm are you trying to "apply update from sdcard" or "install zip from sdcard"
install zip is what you want.... then choose the ROM. IF you're applying update.... it's gonna abort.
You could also try reflashing recovery in Rom Manager or flashing an older version of recovery.
Sent from my time waster.

Gene Poole said:
There's no good reason to go through all that trouble. If you have S-OFF, then you're good to go as far as being rooted is concerned. Since you appear to have recovery too, then you're 95% rooted no matter what the current ROM is doing.
If you have S-OFF already, then going back to stock and rerooting is just going to waste time.
Click to expand...
Click to collapse
Since it has s-off and is rooted correctly what do you advise I do to fix my abort problem? Didn't see an answer in there, thanks.
Nickovtyme said:
In cwm are you trying to "apply update from sdcard" or "install zip from sdcard"
install zip is what you want.... then choose the ROM. IF you're applying update.... it's gonna abort.
You could also try reflashing recovery in Rom Manager or flashing an older version of recovery.
Sent from my time waster.
Click to expand...
Click to collapse
I tried both ways and its aborts both ways. And Ive reflashed recovery in rom manager, should I maybe try a different recovery?

Since you are already rooted and having trouble flashing thru rom manager, why not try flashing to stock rooted thru bootloader? It's my understanding that attn1's Ace_Cingular_US rom will automatically do a full wipe and take you to the latest stock rom and radio. If that works, then you can install the latest rom manager and flash a custom rom. It's worth a shot.
Sent from my Desire HD using Tapatalk

dieseldank said:
Since it has s-off and is rooted correctly what do you advise I do to fix my abort problem? Didn't see an answer in there, thanks.
I tried both ways and its aborts both ways. And Ive reflashed recovery in rom manager, should I maybe try a different recovery?
Click to expand...
Click to collapse
It's not gonna hurt. it sounds like the recovery is having issues with the script so it's aborting... an older recovery may resolve that issue.
But that's a good idea also... flash the lastest stock rooted ROM thru hboot. Then reflash recovery. see If that don't solve it
Sent from my time waster.

[Q] Failed to Use CWM and ICS on phone and now I have a problem

Hi guys, I'm relatively new to this forum.
I've been trying to upgrade my Tmobile LG G2x phone to ICS by using an AOKP ROM that I found online. I followed the instructions on how to use a CWM from this site and all of that worked. However as I was copying the AOKP file to the phone, I realized that I had already extracted that file to my phone instead of leaving it as a zip.
When I booted my phone in CWM I tried to access the install zip from Sd card> choose zip from Sd card> then select the aokp_p999-test2.zip to start flashing the AOKP ROM (ICS). However, all I saw were a bunch of files.
The real problem: I followed these instructions earlier:
Now do a full wipe by selecting Mount and Storage then wipe the following:
Format System
Format Data
Format Cache
Go back to main menu and select advance then wipe dalvik-cache.
Apparently I didn't have a backup, so when I wiped all these formatting files and tried to boot back to my phone to recopy the files, I'm stuck on a blinking screen during boot... I have no way of returning back to my phone and I'm freaking out right now...
Tried using a Flash Stock Recovery option, but I get stuck on the page and can't click on Reboot System now.
HELP ME PLEASE...WHAT DO I DO

AOKP has not been updated for this phone in some time, there are a couple of links to the builds on page 102 of that thread if you insist on trying that out. I'd suggest trying a different ROM from the the development section that has been more recently updated though.
Can you not boot into CWM again hold down the Power & VOL down buttons when you turn your phone on? If not try this: ROM for recovery G2X under the NVFLASH

xBkKx said:
AOKP has not been updated for this phone in some time, there are a couple of links to the builds on page 102 of that thread if you insist on trying that out. I'd suggest trying a different ROM from the the development section that has been more recently updated though.
Can you not boot into CWM again hold down the Power & VOL down buttons when you turn your phone on? If not try this: ROM for recovery G2X under the NVFLASH
Click to expand...
Click to collapse
I can boot into CWM, but apparently I never backed up any files from my phone...
Also, will the new ROM for recovery let me boot into my main screen?
Thanks

Chokachilds said:
I can boot into CWM, but apparently I never backed up any files from my phone...
Also, will the new ROM for recovery let me boot into my main screen?
Thanks
Click to expand...
Click to collapse
The directions in that thread should get your phone to boot back up with the stock ROM installed but since you could still try to just boot into CWM after downloading a different ROM and flash it. There are nandroid backups of the stock ROMs HERE that you can download and unzip the folder into your Clockworkmod/backup folder to have a backup
Sent from my LG-P999

Alright that worked! Now I want to try again to get a ROM for ICS. Since you said that the AOPK one is outdated, do you have any suggestions or links to new ones that work well? I know it's off-topic, but thank you!

Chokachilds said:
Alright that worked! Now I want to try again to get a ROM for ICS. Since you said that the AOPK one is outdated, do you have any suggestions or links to new ones that work well? I know it's off-topic, but thank you!
Click to expand...
Click to collapse
ICS is all.sorts of broken as well as jelly bean. but go look in development section and read and read and read.
than choose!
G2x-CM7 Nightly 11/18/12 Build, Trinity ELP Kernel

Moved to proper forum.

Android Revolution HD 7.3

Hey guys,
Having some problems with this ROM. I downloaded the ZIP, used Titanium backup to back it all up, and flashed the Rom with no problems at all...got through all the screens and whatnot, and upon launching for the first time it's stuck on the "Beats Audio" screen. Not really sure why or what happened. I'm coming from MIUI ROM and haven't had issues with flashing any other ROM before.
One thing I noticed is on the HD 7.3 first page there is a firmware update that you apparently need before you flash the ROM but all links are 404/not found.
Wondering if any of you pros can offer a hand?
-Cain

Cainsmoker said:
Hey guys,
Having some problems with this ROM. I downloaded the ZIP, used Titanium backup to back it all up, and flashed the Rom with no problems at all...got through all the screens and whatnot, and upon launching for the first time it's stuck on the "Beats Audio" screen. Not really sure why or what happened. I'm coming from MIUI ROM and haven't had issues with flashing any other ROM before.
One thing I noticed is on the HD 7.3 first page there is a firmware update that you apparently need before you flash the ROM but all links are 404/not found.
Wondering if any of you pros can offer a hand?
-Cain
Click to expand...
Click to collapse
post the output of this command
fastboot getvar all
don't show your imei and serial number
and what recovery do you have?

rzr86 said:
post the output of this command
fastboot getvar all
don't show your imei and serial number
and what recovery do you have?
Click to expand...
Click to collapse
In looking at my Hboot, it's old as sin....I'm using Revolutionary Hboot 1.17.1111 and Radio 10.14.9035.01_M
I run clockwork recovery mod v5.0.2.0 as well. This could be an issue causing the problem. I've been using the MIUI ROM for probably 2 years or so because I enjoyed it but I'm ready for a change. Apparently my phone doesn't agree. lol.
You want me to connect via USB and run the cmd prompt for the getvar command and let you know what it says?

Cainsmoker said:
In looking at my Hboot, it's old as sin....I'm using Revolutionary Hboot 1.17.1111 and Radio 10.14.9035.01_M
I run clockwork recovery mod v5.0.2.0 as well. This could be an issue causing the problem. I've been using the MIUI ROM for probably 2 years or so because I enjoyed it but I'm ready for a change. Apparently my phone doesn't agree. lol.
You want me to connect via USB and run the cmd prompt for the getvar command and let you know what it says?
Click to expand...
Click to collapse
there is no need to do it now
you gave me exactly what i need
you still have gb firmware that's why you can't boot ARHD 7.3(ics rom)
see this thread
http://forum.xda-developers.com/showthread.php?t=1459767
flash 3.33 universal
follow the instructions to the letter
and before flashing check md5 sums(important)

The speedy reply is much appreciated.
I'll go ahead and update the firmware and see where that lands me. I figured it could have been a problem from the get go but in the original thread for the HD 7.3 Rom the firmware link has been removed (likely since it was from 2011)
Thanks for the point in the right direction Rzr, and I'll let you know how it goes!
rzr86 said:
there is no need to do it now
you gave me exactly what i need
you still have gb firmware that's why you can't boot ARHD 7.3(ics rom)
see this thread
http://forum.xda-developers.com/showthread.php?t=1459767
flash 3.33 universal
follow the instructions to the letter
and before flashing check md5 sums(important)
Click to expand...
Click to collapse

Hmmm....the firmware update didn't work.
I can verify that I'm on the firmware 3.3, Hboot is 1.27.1100, Radio is 11.24A.3504.31_M.
Each time Hboot is run it asks if I want to start the update. If I select yes, I've got 9 on screen options that it runs through and tells me "Update complete. Press power to reboot" The only way to do anything at all is to take out the SD card so it does not try to load up the firmware zip
Pushing power reboots the phone on an endless boot loop. Regardless of what ROM is being used (I also downloaded cyanogenmod) I can not make it past the spash screen.
Could it be that I'm just flashing the ROM incorrectly? To my knowledge I've followed instructions for both and have backed up my phone and it's contents and done everything from a factory reset/wipe to wiping the dalvik cache, etc. I didn't have this many problems rooting my phone and putting on MIUI to begin with and have flashed ROMS before with no trouble....not really sure where I'm going wrong on this one.
Anyway, I'll await your reply.
Thank you!
-Cain
Update: awww frick. So now it looks like this will be more difficult....I hope you like a challenge. I can now no longer get into my phone. It appears that it's soft bricked. I have tried going to a clockwork mod recovery from my first MIUI in 2012, it goes through the entire process of factory resetting restoring the boot image, system and data information. It asks for a reboot which I do. It goes to the white HTC splash screen and the MIUI initializes and goes black immediately. There doesn't seem to be a way to get my phone connected to my computer to get into the SD card to troubleshoot from inside the phone. Hopefully one of you guys has the answer for me. Is there any way to get into it via bootloader usb?

Cainsmoker said:
Hmmm....the firmware update didn't work.
I can verify that I'm on the firmware 3.3, Hboot is 1.27.1100, Radio is 11.24A.3504.31_M.
Each time Hboot is run it asks if I want to start the update. If I select yes, I've got 9 on screen options that it runs through and tells me "Update complete. Press power to reboot" The only way to do anything at all is to take out the SD card so it does not try to load up the firmware zip
Pushing power reboots the phone on an endless boot loop. Regardless of what ROM is being used (I also downloaded cyanogenmod) I can not make it past the spash screen.
Could it be that I'm just flashing the ROM incorrectly? To my knowledge I've followed instructions for both and have backed up my phone and it's contents and done everything from a factory reset/wipe to wiping the dalvik cache, etc. I didn't have this many problems rooting my phone and putting on MIUI to begin with and have flashed ROMS before with no trouble....not really sure where I'm going wrong on this one.
Anyway, I'll await your reply.
Thank you!
-Cain
Update: awww frick. So now it looks like this will be more difficult....I hope you like a challenge. I can now no longer get into my phone. It appears that it's soft bricked. I have tried going to a clockwork mod recovery from my first MIUI in 2012, it goes through the entire process of factory resetting restoring the boot image, system and data information. It asks for a reboot which I do. It goes to the white HTC splash screen and the MIUI initializes and goes black immediately. There doesn't seem to be a way to get my phone connected to my computer to get into the SD card to troubleshoot from inside the phone. Hopefully one of you guys has the answer for me. Is there any way to get into it via bootloader usb?
Click to expand...
Click to collapse
remove the pg58img.zip from your sdcard so it won't scan and identify any pg58img.zip file
and don't restore your miui rom because probably is a gb one and now you have an ics firmware installed
just download an ics or jb rom
put it on your sdcard
full wipe from recovery
flash the rom
done

rzr86 said:
remove the pg58img.zip from your sdcard so it won't scan and identify any pg58img.zip file
and don't restore your miui rom because probably is a gb one and now you have an ics firmware installed
just download an ics or jb rom
put it on your sdcard
full wipe from recovery
flash the rom
done
Click to expand...
Click to collapse
With the phone being in a boot loop I can't get it detected by my computer to remove/add anything from the SD card. I do have the HD 7.3 ROM on and the Gapps that's required but it never makes it past the "beats audio" splash screen. I have no idea what's going on with it but will try any suggestions you've got up your sleeve.

Ahhhhh....I've gotten a fix for this!
I was unable to do anything because of the update zip which wanted me to update every time bootloader was initiated. By keeping my case off I removed my SD card to be able to boot in recovery and then put the SD card back in to load the HD 7.3 zip from the card. This seemed to take care of the problem.
Thanks for the help Rzr