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.

NS4G Wont boot need help!

I can flash clockworks recovery through adb and can get in but I'm getting some errors:
E: Can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
And a bunch few more which seem to repeat
I also tried to run the restore to stock from here but get an error right when I have to click to write the image.
When I just boot all I see is the unlocked lock and google. It used to boot into storage so I can mount it but not anymore. The only thing I have on the SD is the super user app, Netarchy kernel for 4G, CM7 latest stable for NS and thats it.
Need help

I can push something to the phone through the sdk but I don't know how to mount the sd card to do it.

ufff.... nevermind. I tried the factory restore one more time on another machine 32 bit and it works. It's restoring the image again. Will be locked again so I'll have to try again tomorrow. But the steps on rooting the NS4G don't really work well.
There is a bunch of stuff missing. Like the recovery gets overwritten each time. There are some links missing and dead.
Someone should fix that before we brick some phones.

OK, it restored but only gave me the sd card mount thing. I tried going back to fastboot and unlocked was still there. So I flashed recovery again and wanted to see if I can put the stock rom for 4G from here on it.
No go. I get:
assert failed: write_raw_image("/tmp/netharchy.img", "boot")
Installation aborted.
Help

ok, I'm not sure what ROM I have but I unplugged the cable and bam... sign in screen came in so I'm sighing in. Once I can get to the main menu I'll check versions and kernel but it looks like I have root. It's just that recover is not working well. I have 3.0.0.5. should I get a different one?

OK, I restored again because wifi didn't work. I think it was because I was trying to flash after the first restore and it wouldn't take. So now I checked and the lock when I boot showes up as unlocked but none of the root apps work so I don't think I have root. Not sure.
I also have to figure out what's up with that recovery. I know I need to rename the original so it doesn't flash it every time on boot but I think I need a new version. Anyone know which one is the latest and which one works on NS4G?

3005 is the problem. Use 3024. I don't know for sure but are you absolutely sure cm7 is compatible with the ns4g? Isn't a lot of stuff still not working? Isn't 4g still not working? If flashing the wrong rom is what happened here then this problem isn't going away. Many people are doing this and almost bricking their phones. I read one post recently that pointed to a doc that said the gsm and cdma are two separate versions of the same os. I thought I read something that said kernels might be cross compatible but roms aren't yet.
Here are the correct recovery files for the ns4g
I think I remember seeing recovery ***** about cache when I was nandroid for the first time. I think after that I chose factory reset and clear dalvik and some other cache and might have rebooted then came back and flashed cwm again and tried nandroid and it worked that time. This was the very last step for me after I had managed to get the su file to the root of the card, flashed it in cwm, rebooted and changed the filename of the script to check and reinstall stock recovery in system/etc. I forget the name but it was a .sh file. It's name was in the guides somewhere...

I think that's backwards. Roms might be compatible but kernels which these roms come with are not. So I believe that it I just flash netarchys kernel which now supports NS4G all should work ok.
Like I said, I'm back to stock and all looks like exactly like it was before ie. no root but the weird part is that fast boot menu says "unlocked". And I also get the lock which looks unlocked with the google sign during boot.
So how is that possible? Anyone?
When trying any app with root it tels me it has no access or it failed. Ie, su cmd says access denied.
BTW, why you attached two files? What is the difference between the two?

herbthehammer said:
3005 is the problem. Use 3024. I don't know for sure but are you absolutely sure cm7 is compatible with the ns4g? Isn't a lot of stuff still not working? Isn't 4g still not working? If flashing the wrong rom is what happened here then this problem isn't going away. Many people are doing this and almost bricking their phones. I read one post recently that pointed to a doc that said the gsm and cdma are two separate versions of the same os. I thought I read something that said kernels might be cross compatible but roms aren't yet.
Here are the correct recovery files for the ns4g
I think I remember seeing recovery ***** about cache when I was nandroid for the first time. I think after that I chose factory reset and clear dalvik and some other cache and might have rebooted then came back and flashed cwm again and tried nandroid and it worked that time. This was the very last step for me after I had managed to get the su file to the root of the card, flashed it in cwm, rebooted and changed the filename of the script to check and reinstall stock recovery in system/etc. I forget the name but it was a .sh file. It's name was in the guides somewhere...
Click to expand...
Click to collapse
Thanks for your help. I'm rooted and recovery is sticking ok. It was the old recovery. As soon as I flashed it all was good.

One is stock and the other is cwm that works with the ns4g. It wouldn't hurt to have the stock laying around. There might be a time when you need it.

Thanks for the stock recovery.
Sent from my Nexus S 4G using XDA App

[Q] Attempted to root my i727r

Have a rogers S2LTE, running ICS 4.04.
I ran Odin and used cwm recovery, and used what I found to be the most recent TAR file for the i727r.
during the download procedure to put superuzer on the phone, I had one error aborted installation, but success the second time.
Everything seemed normal, albeit aside from a slightly slower speed in the operation of the phone.
The only reason I noticed something was wrong was the fact that superuzer didnt really do anything, I couldnt add any apps or get past the initial screen.
Also, titanium back up didnt work, stating it couldn't get root permissions.
At this point, I installed root checker and got a negative response on my phone being rooted.
I'm posting here as I'm not sure how to progress, and as the phone is running normally, and im not sure if any real damage is done.
Do I simply try to flash the phone with Odin once more? Or do I flash it back to stock, and factory reset, and then try to root again?
Thanks in advance.

Me[kk]A said:
Have a rogers S2LTE, running ICS 4.04.
I ran Odin and used cwm recovery, and used what I found to be the most recent TAR file for the i727r.
during the download procedure to put superuzer on the phone, I had one error aborted installation, but success the second time.
Everything seemed normal, albeit aside from a slightly slower speed in the operation of the phone.
The only reason I noticed something was wrong was the fact that superuzer didnt really do anything, I couldnt add any apps or get past the initial screen.
Also, titanium back up didnt work, stating it couldn't get root permissions.
At this point, I installed root checker and got a negative response on my phone being rooted.
I'm posting here as I'm not sure how to progress, and as the phone is running normally, and im not sure if any real damage is done.
Do I simply try to flash the phone with Odin once more? Or do I flash it back to stock, and factory reset, and then try to root again?
Thanks in advance.
Click to expand...
Click to collapse
which cwm did u use
wich su file did u use
read this on rooting http://forum.xda-developers.com/showthread.php?t=1340526
but use this cwm http://forum.xda-developers.com/showthread.php?t=1566613

Me[kk]A said:
Have a rogers S2LTE, running ICS 4.04.
I ran Odin and used cwm recovery, and used what I found to be the most recent TAR file for the i727r.
during the download procedure to put superuzer on the phone, I had one error aborted installation, but success the second time.
Everything seemed normal, albeit aside from a slightly slower speed in the operation of the phone.
The only reason I noticed something was wrong was the fact that superuzer didnt really do anything, I couldnt add any apps or get past the initial screen.
Also, titanium back up didnt work, stating it couldn't get root permissions.
At this point, I installed root checker and got a negative response on my phone being rooted.
I'm posting here as I'm not sure how to progress, and as the phone is running normally, and im not sure if any real damage is done.
Do I simply try to flash the phone with Odin once more? Or do I flash it back to stock, and factory reset, and then try to root again?
Thanks in advance.
Click to expand...
Click to collapse
download procedure?
just put superuser on sd and install from cwm.
no root access means no su binary's installed. su binary's will not install from the superuser in the market that's just a front end.

wouldn't you also require busy box and then fix permissions using rom manager?

SeraldoBabalu said:
wouldn't you also require busy box and then fix permissions using rom manager?
Click to expand...
Click to collapse
no. busy box has nothing to do with su. and rom manager sucks and you will have nothing but trouble if you use it. just download odin and cwm and superuser thats all you need to root that expensive phone.

Try the super user file located here: http://forum.xda-developers.com/showthread.php?t=1565126
I had a similar issue as you and the su in the link worked fine. If it fails keep trying, took me like 3 tries.
Sent from my SAMSUNG-SGH-I727 using xda premium

vincom said:
which cwm did u use
wich su file did u use
read this on rooting http://forum.xda-developers.com/showthread.php?t=1340526
but use this cwm http://forum.xda-developers.com/showthread.php?t=1566613
Click to expand...
Click to collapse
I used this guide: http://forum.xda-developers.com/showthread.php?t=1340526
but used the newest tar file provided on one of the rogers ics rooting threads.
As nothing is visibly wrong at this point, could I simply retry to root? Or should I wipe everything first?

So i tried to reflash again and use the new hercules file in odin.
All went well until I went into cwm recovery to make a back up, it said the it couldn't mount and aborted.
I backed up onto the SD card and it proceeded, however, when trying to load the superuser file from the external sd, it also said it couldn't mount, and aborted there.
any way around this?

Me[kk]A said:
So i tried to reflash again and use the new hercules file in odin.
All went well until I went into cwm recovery to make a back up, it said the it couldn't mount and aborted.
I backed up onto the SD card and it proceeded, however, when trying to load the superuser file from the external sd, it also said it couldn't mount, and aborted there.
any way around this?
Click to expand...
Click to collapse
dont use a touch recovery, flash a non touch recovery then install superuser. or put the superuser zip on the emm(internal sd).

popcorn900 said:
dont use a touch recovery, flash a non touch recovery then install superuser. or put the superuser zip on the emm(internal sd).
Click to expand...
Click to collapse
use this touch from tpmullan http://forum.xda-developers.com/showthread.php?t=1566613
u used this one from sk8erwitskil, u have to mount the sdcard first, but he has fixed it now(in testing) http://forum.xda-developers.com/showthread.php?t=1472954&highlight=sk8erwitskils
dont read my sig

vincom said:
use this touch from tpmullan http://forum.xda-developers.com/showthread.php?t=1566613
u used this one from sk8erwitskil, u have to mount the sdcard first, but he has fixed it now(in testing) http://forum.xda-developers.com/showthread.php?t=1472954&highlight=sk8erwitskils
dont read my sig
Click to expand...
Click to collapse
That's the one I used, the one from tpmullan. Couldn't mount a back up, and wouldn't read superuser either.

Me[kk]A said:
That's the one I used, the one from tpmullan. Couldn't mount a back up, and wouldn't read superuser either.
Click to expand...
Click to collapse
weird, which method did u use to flash cwm
where is backup located, int or ext sdcard, which cwm version did u make backup
what do u mean it wouldnt read superuser, maybe redownload su and check the md5, running su in cwm has to b done a few times until it states that it has completed sucessfully
edit:try to mount sdcard from within cwm in "mounts and storage/mount sdcard" also mount emmc, i never had to do that but it might b that u have to do it once

Me[kk]A said:
That's the one I used, the one from tpmullan. Couldn't mount a back up, and wouldn't read superuser either.
Click to expand...
Click to collapse
well if you would just try a non touch recovery you might be surprised.
http://forum.xda-developers.com/showthread.php?t=1725221
this recovery works and this is all the help i can muster up. so now if you cant figure it out then i guess you shouldn't be flashing phones.

I have the same phone this is what I did
Flash phone with CWM use this one
Clockworkmod Touch 5.8.1.3 Odin tar http://forum.xda-developers.com/show....php?t=1566613
Then wipe data/factory reset, format- system, data and cache, and clear the partition and dalvik caches, do that to all of them 3 times each, using touch cwm.
Then odin ICS download it from here http://www.sammobile.com/firmware/
(make sure only Auto Reboot is checked nothing else)
Once the phone loads go through the setup then leave it alone, let it sit for about 20min then flash back the CWM. Then download Superuser from here and put it on the root of your SD card then flash it in CWM if it fails just keep doing it until it works, it worked the second time for me.
Once superuser is installed install busybox from the market and everything will work.
This method worked perfect for me I was having the same problem like you. The key is to wait about 20min after you flashed ICS before you do anything else.
Hope this helps you.

Well, the final superuser file worked, everything backed up perfectly.
Wanted to thank you all for you assistance. Vincom, if I knew who you were in Bolton, id buy you a beer, as I'm in your town 3 times a week.
lol Cheers everyone.

Me[kk]A said:
Well, the final superuser file worked, everything backed up perfectly.
Wanted to thank you all for you assistance. Vincom, if I knew who you were in Bolton, id buy you a beer, as I'm in your town 3 times a week.
lol Cheers everyone.
Click to expand...
Click to collapse
cool, what was the solution? bad download

vincom said:
cool, what was the solution? bad download
Click to expand...
Click to collapse
I'm not entirely sure. After not being able to back up, I grabbed an external sd, put superuser on that.
The back up went through with no problems. Also, superuser installed on the 2nd try and all went well with permissions from there.
Friend of mine had picked a zip file labelled "root" to use with Odin, and I'm suspecting the tar files I had attempted with in the past weren't correct and this file was.
Either way, I have lots more reading to do to fully understand what is available to me now. Busybox, nandroid, ROM toolbox installed.

iv flashed my phone so many times that flashing stock and rooting seem tedious to me. glad you got it rooted, now make a nand backup so you don't have to do it again.
my 32 gig sd is filled with nand dumps lol i don't even have a game on it to play.

Can't get my Charge to update to FP5 after rooting

I can't seem to update my rooted Charge to FP5.
Here's the background:
I installed ROM Manager and flashed on CWM Recovery for the Charge. I'm guessing it wiped out the recovery partition (I could be wrong, but isn't that how it works?), so when I hit "update now" to update my phone to FP5, it tries to reboot to the package installer for the update, but it errors out with a triangle exclamation mark thing.
I tried booting into CWM to install the update.zip which I downloaded manually but that seems to error out with this message (don't remember what it was, I can maybe find it again), but it basically amounted to "I cant update with this update.zip file"
What can I do to fix this?

evets90 said:
I can't seem to update my rooted Charge to FP5.
Here's the background:
I installed ROM Manager and flashed on CWM Recovery for the Charge. I'm guessing it wiped out the recovery partition (I could be wrong, but isn't that how it works?), so when I hit "update now" to update my phone to FP5, it tries to reboot to the package installer for the update, but it errors out with a triangle exclamation mark thing.
I tried booting into CWM to install the update.zip which I downloaded manually but that seems to error out with this message (don't remember what it was, I can maybe find it again), but it basically amounted to "I cant update with this update.zip file"
What can I do to fix this?
Click to expand...
Click to collapse
Your phone must be factory stock (no root) to do the update.

Unless I'm mistaken ROM manager will not work with the Droid charge... I could be wrong, but from what I've been told, to never install that mess on my phone. Sorry, but you might want to uninstall that apk if possible. I know it will Bork the charge.
Charged withTweaked 3.0b & TrICS5.0

ROM Manager is very, very bad for this phone. You'll need to revert to a stock ROM before you can get FP5. Use my instructions (check the development section) after you're on FP5.
Sent from my SCH-I510 using xda premium

Interesting...I didn't know it was that bad for it, considering how nicely CWM installed onto it...would updating allow me to get the stock recovery partition back on it?
(Just to clarify, I know updating while rooted removes the root, I was gonna re-root after updating to FP5)
I'll check out that guide though.

Accepting the OTA while rooted or on a custom anything will turn your phone into a temporary paperweight.
Sent from my SCH-I510 using xda premium

Also, am I boned if i CWM'd the phone? Pretty sure I overwrote the recovery partition.

evets90 said:
Also, am I boned if i CWM'd the phone? Pretty sure I overwrote the recovery partition.
Click to expand...
Click to collapse
If you can get into download mode you can flash cwm in odin

You need to go to the development forum and check out the thread: [ODIN][ROM][EP4D][FACTORY]. Go back to EP4D stock then take the two OTA updates.
Sent from my SCH-I510 running Tweaked 3.0 using Tapatalk 2

kvswim said:
Accepting the OTA while rooted or on a custom anything will turn your phone into a temporary paperweight.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
It won't do anything but possibly put you in a recovery boot loop, but I doubt that. If it fails any of the assert checks, it ends the update. It checks literally every file on /system and also will check anything else that gets patched except for possibly the radios. Odds are better that by "installing CWM" via ROM Manager, something else was screwed up that caused the check to fail. It could also be that the zip that is attempting to be flashed is incomplete, or the wrong one for the version the OP is on.

[Q] Odin can't flash stock, boot hangs at logo

Good morning...
Right now, my phone (Galaxy S III on Verizon) will not boot past the "Galaxy S III" logo. Odin will not flash a stock Jelly Bean ROM from StockRoms.net. It gets stuck on the first .img, boot.img. I am downloading a new stock ROM right now and will try a full wipe.
Being silly and ambitious, I do not have a nandroid before it wouldn't boot. On Monday (two days ago) I rooted it. I flashed the VRALEC boot chain, rebooted, flashed ClockworkMod recovery, and installed the SuperSU bootloader and root patch through recovery. I rebooted, allowing CWM to disable the automatic re-flashing of the recovery. With my newly rooted phone, I jumped at trying to install Google Wallet. I went with the route of using Wallet Installer as found on the app store. And, being silly, I checked all three OS options (JB, ICS, and one other). After authorizing the superuser request, my phone almost immediately shut off. I think I made a nandroid through CWM after that, but not one that would run.
I thought it was going to be just build.prop having issues, so I went on a wild quest trying to find a working one online and get it on the device. I worked it into the updater script of my SuperSU patch. Nonetheless, nothing there fixed it. I've tried a bunch of things, including (get this) extracting the stock system.img.ext4 image, mounting it, tarring the device, creating an MD5 for it, and wrapping it up like a nandroid to "restore" with CWM.
I'm thinking I'm going to try and wipe the entire device, maybe leave /recovery, and flash a new I-535 ROM with Odin, see if that works. I don't know if it will. Any advice?
My flash counter is at about 5 after many attempts to get back to something that will boot, so warranty is not an option. Not that they've ever been a whole lot of help anyways.

Sounds like you can still enter recovery. If so adb push a custom ROM to your phone to flash.
Sent from my SCH-I535 using Tapatalk 2

What I have done in the past when flashing a completely stock unrooted ROM through Odin is remove the battery, replace it, boot to stock recovery, and do a factory reset plus wipe cache! This will make my phone boot every time, because flashing a stock makes it boot loop!
Sent from my SCH-I535 using xda app-developers app

joaquinla1 said:
What I have done in the past when flashing a completely stock unrooted ROM through Odin is remove the battery, replace it, boot to stock recovery, and do a factory reset plus wipe cache! This will make my phone boot every time, because flashing a stock makes it boot loop!
Click to expand...
Click to collapse
My phone has CWM recovery on it, but I don't see any reason CWM's factory reset and cache wipe would be any different. I'll give it a shot.
mentose457 said:
Sounds like you can still enter recovery. If so adb push a custom ROM to your phone to flash.
Click to expand...
Click to collapse
I may try this if I can't upload one through Odin after a complete wipe, like above. Also, I've only used adb push to upload individual files. How would I use it to push a ROM?
Thanks for all your help. The ROM I'm going to try and flash now is the official stock from stockroms.net. I can't post the link as I'm new but it's I535BLK_nowipe.zip. I'll keep this updated.

sworld said:
I may try this if I can't upload one through Odin after a complete wipe, like above. Also, I've only used adb push to upload individual files. How would I use it to push a ROM?
Click to expand...
Click to collapse
When you download a ROM, say Beans 11, it will be a zip file. Push that single file to the internal storage. Do not unzip it. Then boot into recovery and flash the zip.
Sent from my SCH-I535 using Tapatalk 2

mentose457 said:
When you download a ROM, say Beans 11, it will be a zip file. Push that single file to the internal storage. Do not unzip it. Then boot into recovery and flash the zip.
Click to expand...
Click to collapse
That makes more sense.
UPDATE: I "factory reset" the data partition and formatted /system and /cache through ClockworkMod. Turned it off, flashed VRALEC through Odin, rebooted, flashed the stock ROM, and then CWM. I'm restoring my nandroid of /data right now, and I'm awaiting an OTA firmware update to bring it up to the latest VZW JB. Then I'll root.. finally.

The thing with Odin is that after you reset you have to do a factory reset through stock recovery to finish the process. Otherwise you will get stuck in a boot loop like you did.
Sent from my GeeEssThree

z06mike said:
The thing with Odin is that after you reset you have to do a factory reset through stock recovery to finish the process. Otherwise you will get stuck in a boot loop like you did.
Sent from my GeeEssThree
Click to expand...
Click to collapse
Really? I've only odined once on the s3 and didn't have to wipe. On the fascinate and an older version of Odin after the flash before it booted it would automatically wipe.
Sent from my SCH-I535 using Tapatalk 2

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

So, the phone is functioning now. Of course, I am running a slightly older version and once I connect to a solid Wi-Fi network I'll request the newest update again.
However, I did already try to download the software update from Verizon, and it seemed to work fine. It rebooted into recovery and CWM seemed to handle it okay, although it claimed the signature was bad. It installed though, rebooted, and updated some app databases. And then, it said the update failed with "Code 401."
Right now I'm not too worried. Hopefully I can apply the update properly soon. It is worth noting that simply using CWM "advanced restore" on only the /data partition, without exactly matching the ROM build, has seemed to leave it hanging at the "4G LTE" logo.
Thanks for all of your help!

The phone will not install a Verizon update with a custom recovery installed.