please help with my phone: can't update ROM, keep getting error msgs! - Nexus S Q&A, Help & Troubleshooting

Hi all, I recently rooted my NS4G and flashed my rom to the Brainmaster's MIUI 10.14.11. It worked great for a while and then I started having issues with it so I tried to update it to the 10.28.11 version and it wouldn't let me. I was finally able to reflash to GRJ06D, but no other custom rom would work. I'm using CWM 5.0.2.0. ROM Manager won't work either after it gets into recovery. I get the error message...
assert failed: getprop("ro.product.device") == "crespo4g" || getprop("ro.build.product") == "crespo 4g"
E: Error in /sdcard/
(Status 7)
Even trying to do an OTA system update via Sprint freezes and gives me the Android error message (triangle with exclamation). I've tried many many times to reflash and no success.
What do I need to do?

This issue has been reported a few times and there are a few ways to fix it;
1) Make sure you downloaded the right ROM; ie, the ROMs from the Nexus 4G Development section
2) If you're installing ROMs through ROM Manager, don't. Reboot into recovery mode, do a full data, cache and dalvik wipe and then flash the ROM zip while still in the CWM recovery mode
3) Else; try a different version of CWM, make sure it's compatible with your device and then do step 2 again.
Good luck.
Greetz

I think you should flash CWM again then wipe data, cache, dalvik, boot, then flash rom again and report your findings back to us.

I had this issue last week.. You've probably tried to flash the incorrect ROM originally or something..
The only way I could fix it was to boot into download mode, and flash the PDA, phone and modem via Odin. You can get the firmware from samfirmware.com

Thanks for the responses, its funny because I flashed the 4.0.1.0 CWM, which was for the GSM version and then reflashed to 5.0.2.0 (NS4G) in order for the MIUI rom to work. It was after flashing that and running MIUI for a while that I started having issues so I reflashed a new 5.0.2.0 and its still the same.
I haven't been able to flash back to the CWM 3 that it originally came with because I lost my micro USB cable. I hope to get this fixed soon! Thanks again, will keep you guys posted.

Related

ROM Manager error I NEED Help Plz

hey guys i had andromeda installed but messed the flash up by disabling lots of system stuff so i one clicked back to stock, rooted, installed rom manager like normal but every time i try to flash clockwork recovery mod it keeps telling me "An error occurred while downloading your recovery." and i cant install it so i can re-flash the rom plz help me i dont know what to do thx ahead of time
praramis said:
hey guys i had andromeda installed but messed the flash up by disabling lots of system stuff so i one clicked back to stock, rooted, installed rom manager like normal but every time i try to flash clockwork recovery mod it keeps telling me "An error occurred while downloading your recovery." and i cant install it so i can re-flash the rom plz help me i dont know what to do thx ahead of time
Click to expand...
Click to collapse
Put this on your internal SD card along with your ROM of choice. Reboot in to recovery and install packages 2 times. The second time it will be in clockwork recovery and you can flash your ROM.
I just had the same problem after doing countless ROM flashes in the past. Perhaps its something in their server preventing the download of CWM? Anyways, thanks for the .zip. Worked like a charm!
yes thank you very much for that zip u saved my life well appreciated
Keep that .zip on your HDD and you can bypass Rom Manager (and all the associated problems) altogether.
I have my phone rooted and unlocked. It's the AT&T Captivate but I'm using it on T-Mobile. I've had no problems so far with it.
I downloaded Clockwork's Rom Manager (v3.0.0.7) and tried to Flash ClockworkMod Recovery to begin experimenting with ROMs.
When I click on that it tells me "An error occurred while downloading your recovery."
I have over 4 gigs of memory left and I have 3 bars on 3g and WiFi going. No internet connection problems (i checked the net using market and using the browser, it works fine.)
What else could be causing the problems.
I'm just wanting to get a good stable rom going which ditches all the junk AT&T put on the phone.
Jonathan
lanternslight456 said:
I have my phone rooted and unlocked. It's the AT&T Captivate but I'm using it on T-Mobile. I've had no problems so far with it.
I downloaded Clockwork's Rom Manager (v3.0.0.7) and tried to Flash ClockworkMod Recovery to begin experimenting with ROMs.
When I click on that it tells me "An error occurred while downloading your recovery."
I have over 4 gigs of memory left and I have 3 bars on 3g and WiFi going. No internet connection problems (i checked the net using market and using the browser, it works fine.)
What else could be causing the problems.
I'm just wanting to get a good stable rom going which ditches all the junk AT&T put on the phone.
Jonathan
Click to expand...
Click to collapse
Read the above solution...
I Can't get the update.zip file to work. After I reinstall packages is says E:Can't open /sdcard/update.zip (No such file or derectory) Installation aborted. I've tried it probably 20 times today with no luck.
Thank You
Nothing like flashing to find out it wasn't working. Thanks for making my day go better.
Noobie Mistakes
Just like everyone in this forum I'm having the same problem, I followed your instructions posted, but every time I reinstall packages in recovery mode a whole list of new problems comes up..... see below.
---Install from sdcard---
Finding update package...
Opening update package....
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
PLZ Help.......
Thanks
i have been fight this same thing for 2 days. im going to try the update.zip he posted i hope it works
npe didnt work. still says error downloading
tat2messiah said:
npe didnt work. still says error downloading
Click to expand...
Click to collapse
if the update.zip is already on your /sdcard/ then there is no reason to try and download/flash clockwork recovery.....thats what the update.zip IS
thats what i thuoght but not true. even goin in normal recovery and selecting to install packages gets a error some about no such directory or something even though updat.zip is there even fix permissions gives a error
I'm having the exact same problem. After reading the development section I have decided to flash a custom rom from my stock rom. Installed "Rom manger" from market, then tried to run the "recovery" got the same error msg. Also uploaded the update.zip to my /sdcard the I got the below errors:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
tat2messiah said:
thats what i thuoght but not true. even goin in normal recovery and selecting to install packages gets a error some about no such directory or something even though updat.zip is there even fix permissions gives a error
Click to expand...
Click to collapse
Did you flash back to stock JF6 first not JI6?
try this cuz this is what i did and the update.zip worked just fine for me
1. one click back to stock jf6
2. master clear
3. root with galaxy s one click root
(after the root there should be an update.zip in your sdcard)
4. replace the update.zip in the root of your sd card with the one here posted which is the clockwork recovery one and if you want while u do that you can throw in the rom that you want to flash in there as well to kill 2 birds with one stone
(i will re post the update.zip for cwm just in case)
5. power off the phone and boot into stock recovery and hit reinstall packages two times
6. you should now be in clockwork mod recovery and can now flash the rom of your choice
this is what i did and everything went smoothly but this is just me if this helps someone else plz let me know if this works for you
p.s. i will make a video if needed just ask
Try This
After flashing back to stock do a master clear from Odin3
Put update.zip onto internal sd
Boot into recovery
Reinstall packages
After boot enable USB debugging and mock locations
Get Rom Manager from market
Start Rom Manager
Flash ClockworkMod Recovery
Flash away
jhernand1102 said:
Put this on your internal SD card along with your ROM of choice. Reboot in to recovery and install packages 2 times. The second time it will be in clockwork recovery and you can flash your ROM.
Click to expand...
Click to collapse
You guys are making it harder then necessary, the update zip I posted is the clockwork recovery MOD, just flash stock, reboot into recovery and reinstall packages 2 times and you will be in the green clockwork recovery then you can install zip from sd and choose your ROM you placed on your internal sd card. No need to root every again as long as you keep this update zip handy.
I too am having problems with Rom Manager. I just wanted to change modems. No go. So I used the power button to go into Recovery mode, picked the modem file, flashed it then told the menu to reboot system.
Sent from my Samsung Captivate with Perception 10.3, Firebird2 v0.8 #77 Kernel, Firmware 2.2.1, Modem T9000UGJL2 using XDA App

[Q] Trouble with 2.3.6 update on I9020a.

I've been in and out of these forms for hours now, and I still can't figure this out. I have an I9020a from Fido (Canadian). I flashed the stock ROM & modem from this post (http://forum.xda-developers.com/showthread.php?t=1056062&page=68). When I try to flash the 2.3.6 update through CWM 5.0.2.3 I get the following
-- Installing: /sdcard/7d11404284c0.signed-soju-
GRK39F-from-GRJ22.7d114042.zip
Finding update package...
Opening update package...
Installing update...
assert failed: file_getprop("/system/build.prop"
. "ro.build.fingerprint") == "google/soju/crespo
:2.3.4/GRJ22/121341:user/release-keys" ||
file_getprop(/system/build.prop". "ro.build.fin
gerprint") == "google/soju/crespo:2.3.6/GRK39F/1
89904:user/release-keys"
E:Error in /sdcard/7d11404284c0.signed-soju-GRK3
9F-from-GRJ22.7d114042.zip
(Status 7)
Installation aborted.
Now I know that some people say I need to use the stock recovery, however there doesn't seem to be any way to get that back. The post (http://forum.xda-developers.com/showthread.php?t=1033269) that everyone mentions has dead links in it, so I cannot download the stock recovery from it.
Can anyone help?
Wolfgar2k
Have you renamed the file to update.zip. placed it on the root of the sd ard and flashed it by selecting the install update.zip option in clockwork. You cannot use the flash zip from sdcard option.
Sent from my Nexus S 4G using xda premium
I tried renaming it to update.zip, but got the same results. I tried with Clockwork 4.0.0.2 and 5.0.2.3. Both of these are missing the install from update.zip option for some reason. I also tried to flash a recovery.img file that was supposed to be stock recovery from post (http://forum.xda-developers.com/showthread.php?t=1033269&page=4) but all it did was make the phone go to the screen with the ! in a triangle with the android logo beside it.
Have you been on stock the whole time? These errors usually mean that there is some different configuration than expected on your phone when using an update package. It could be your radio or your recovery and I have read that even different versions of google apps can cause this. I have seen this myself. Your best bet is to flash the full rom package for your I9020A with clockwork recovery to get you to 2.3.6 you can download here. http://android.clients.google.com/p...8148de0d.signed-sojua-ota-189904.0b9c8148.zip You won't receive any errors because it's a full rom package. You will however have to re flash clockwork recovery aftewards.
Had same issue coming from 2.3.4 I was rooted . Flash the full ROM 2.3.6 you shouldn't have to wipe. after flashing you lose cwr and root
Sent from my Nexus S using XDA Premium App
I tried flashing that ROM with CWM. It made my phone go into a boot loop. I even tried using the NAND 2.3.1 backup. That didn't work, nor did it replace my recovery with the stock one. I did manage to flash to a full 2.3.6 ROM that was pre-rooted, though that's not quite what I was going for. I was trying to get back to pure stock with the 2.3.6 update.
Wolfgar2k said:
I tried flashing that ROM with CWM. It made my phone go into a boot loop. I even tried using the NAND 2.3.1 backup. That didn't work, nor did it replace my recovery with the stock one. I did manage to flash to a full 2.3.6 ROM that was pre-rooted, though that's not quite what I was going for. I was trying to get back to pure stock with the 2.3.6 update.
Click to expand...
Click to collapse
2.3.1 was never designed for the i9020a the first release was 2.3.3. A nand backup will never get you to stock recovery. when making a backup it doesnt save a recovery.img because you make the nand using the fastboot flashed clockwork recovery.img.
The link I provided for you is the full rom which is pure stock 2.3.6 for the i9020a Nexus S straight from Google. This is the update presented to me when going from 2.3.3 up to 2.3.6. If you flashed that you are completly stock including radio, kernel and recovery.
After if you want cwm and root back you have to fastboot flash cwm again and then from cwm I flash su.
I am in the same boat as Wolfgar2k. I am also in Canada and have a Nexus S I9020A with Fido. I wanted to ditch CyanogenMod and go back to the stock 2.3.6 version.
I tried installing the build that blowtorch provided (copy to SD card, rename to Update.zip, select "Install from SDCard"). The install completed without error but when I boot the phone, it gets to the loading animation (colourful X-shaped particle system), the animation then freezes and restarts, over and over.
Anyone know what could be going wrong here?
I have (finally) solved my problem. It turns out all I had to do was use fastboot to erase the cache (fastboot -w) and the phone no longer crashed on boot. Tons of thanks to blowtorch for posting that 2.3.6 build, which does in fact work just fine. I have my phone back!
So happy.
Cooper39,
can you guide me how can i do "use fastboot to erase the cache (fastboot -w)" on my nexus .. I am having the same problem
Ahmed

[Q] Installation Aborted(Status 7)while Flashing GingerBread

HI,
I have recently compiled and flashed the 2.3.4-r1 Ginger Bread on my Nexus S
using these commands
$ ./out/host/linux-x86/bin/fastboot erase userdata
$ ./out/host/linux-x86/bin/fastboot erase cache
$ ./out/host/linux-x86/bin/fastboot flash boot out/target/product/crespo/boot.img
$ ./out/host/linux-x86/bin/fastboot flash system out/target/product/crespo/system.img
$ ./out/host/linux-x86/bin/fastboot flash userdata out/target/product/crespo/userdata.img
But now I want to go back and load the default image-2.3.6 Gingerbread (GRK39F) (which was there at the time of purchasing Nexus S).Is there a way to do this.I downloaded the ROM for it from somewhere on the net and stored it internally on my Nexus S but when I am going into the fastboot mode and then recovery and when trying to install from sd card option by selecting the downloaded ROM I am getting this error(error Attached)
--Install /sdcard
Finding update package ...
Opening update package...
Verifying update package...
Installing update ...
assert failed : file_getprop("/system/build.prop". "ro.build.fingerprint" ) == "google/soju/crespo:2.3.3/GRI40/102588:user/release-keys"|| file_getprop("/system/build.prop","ro.build.fingerprint")=="google/soju/crespo:2.3.4/GRJ22/102588:user/release-keys"
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation Aborted
This is the error snapshot : http://www.freeimagehosting.net/86b7d
PLz advice.I am so tensed !!!
Rgds,
Softy
It seems the package you downloaded is for upgrading from 2.3.3 to 2.3.6. Try the full OTA ROM for your phone model from the link in my signature
suksit said:
It seems the package you downloaded is for upgrading from 2.3.3 to 2.3.6. Try the full OTA ROM for your phone model from the link in my signature
Click to expand...
Click to collapse
OK I will try the 2.3.6 .I will use the same procedure as used earlier.
Copying the ROM to internal memory and then select the ZIP file from the sd card.I hope wipe data/cache will be optional.
Thanks suksit !! It worked.I have my previous ROM now.I am happy !
Could you plz tell that why I didnt get more options in the Android Recovery Mode?I saw somethign clockwork Recovery , do I need to install such ROM?
RGds,
Softy
TRy downloading the correct rom from the below link. Make sure you check your phone model (9020/23 3G/4G etc)
http://forum.xda-developers.com/showthread.php?t=1063664
Edit: I see that it is resolved now.. enjoy
You need an older recovery. Had the same issue but when using 3.x instead of 5.0.2.x the status 7 issue went away.
Sent from my Nexus S using XDA App
softy007 said:
Thanks suksit !! It worked.I have my previous ROM now.I am happy !
Click to expand...
Click to collapse
You're welcome
softy007 said:
Could you plz tell that why I didnt get more options in the Android Recovery Mode?I saw somethign clockwork Recovery , do I need to install such ROM?
Click to expand...
Click to collapse
You have to install ClockworkMod recovery in order to get those options. It's not a ROM, it's a recovery image that you flash to replace the stock recovery.
You'll need it if you want to flash custom ROM, custom kernel, or other modifications that comes in an unsigned zip file. Otherwise you can just stick to the stock recovery.
Other benefits of CWM recovery are backup and restore functions, mount options, and the ability to wipe cache, dalvik-cache, battery stats, etc.
To install CWM recovery, you'll have to unlock the bootloader and flash it using fastboot command. I'd recommend you to follow the guides in Nexus S General section if you want to do it.

[Q] Not able to flash rom and phone is completely wiped including no OS

Basically I am unable to flash any roms using twrp. Whenever i do try to flash a rom i get a assert failed getprop( ro.bootloader ) error flashing zip message. I wiped my phone including the OS because i wanted to de clutter the phone. I need to flash a rom to get my phone up and working again. It is the One S S4 variant .
Any help would be appreciated. Please reply. Thanks.

[Q] STUCK ON CM 9.1 r13/CANT FLASH OTHER ROMS

Hi,
I need some help. Firstly I'm quite a noob so please go easy on me, have only flashed/rooted a couple of phones before this...both with pretty much no issues.
I flashed the CM 9.1 A while back to improve it, and decided I wanted to change it due to few bugs annoying me too much...such as the restarts, crazy battery life and most annoyingly of all calls only being able to be heard on loudspeaker! Buts can't seem to get any other rom to flash - tried 2 - samsation v6.0 kerneldev101 & MikTouch- 0.7-signed.
When trying to flash firstly 'samsation v6.0' i encountered an error code '"assert failed: getprop("ro.product.device") == "pyramid"
E:\Error in /storage/sdcard0/samsation v6.0.zip
(status 7)
Installation aborted.
and to try and overcome this I opened the updater script from rom zip and deleted the line 'assert(getprop("ro.product.device") == "pyramid" || getprop("ro.build.product") == "pyramid");'.....after reading in forums it could be this. After this line is deleted the flash attempt is 'opening update package...installing update...installation aborted'
I then tried MikTouch 0.7 and it came up with the 'status 7' error, so I deleted the first line of the updater script and now I am getting a 'status 4' error...even if I try to flash thru rom manager - CWM app.
Driving me crazy! Any help much appreciated.
even tried a different SD card to see if that makes a difference....and nope
installed new CWM - V6.0.4.6 after reading that may be the prob. no difference
To be honest it all P'd me off so much just went and bought myself the Moto G instead...but would still like to fix this one and get it even back to a stock like ROM so at least it functions properly but without all the bloatware.
Use TWRP instead of CWM. This should fix the issue.
Tried it thru the twrp app and it just launches into cwm recovery and does same status 4 error
Thanks for replying though!
Sent from my XT1032 using xda app-developers app
'Cwm-based recovery v6.0.4.6
--Installing: /storage/sdcard0/MikTouch-0.7-signed.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /storage/sdcard0/MikTouch-0.7-signed. Zip
(Status 4)
Installation aborted
Sent from my XT1032 using xda app-developers app
I didn't mean the app found on Play Store. I meant the actual TWRP recovery.
You'll have to connect your phone to your PC, boot into bootloader, and flash the TWRP recovery, which will replace the existing CWM recovery.
Moto g looks like a great phone for the price, but I would want to fix my double shot too.
First off, the getprop errors you were getting were saying you were trying to flash a ROM for sensation on your doubleshot, not a good idea, don't delete getprop from updater-script no matter what the internet says, this is a good warning
Don't use an app for flashing, use recovery
But before you proceed any further I would suggest to boot into bootloader and write down every thing from that screen here, word for word
Then you will be sure to get the exact links and info, I wouldn't do anything until then, not to say @abe5 is having you bad info, he is correct, but I have a feeling there may be more info needed here
Sent from my Nexus 7 using XDA Premium 4 mobile app
Bootloader info
Hi,
OK thanks to both of you for your help! ...I guess I would rather check/be sure than do something worse to my phone.
Your right Moto G is great phone..I am pretty impressed so far...for the price. Only let down is the camera....I miss the doubleshot great camera...but you cant have it all....well not for £130
OK SO INTO BOOTLOADER..... (front screen reads as follows - hope this is what you mean?!)
***UNLOCKED***
DOUBLESHOT PVT SHIP S-OFF RL
HBOOT-1.45.0013
MICROP-0353
RADIO-11.16.3504.20_2
eMMC-boot
NOV 21 2011,20:20:47
FASTBOOT
VOL UP.... ETC ETC
.....
fickleama said:
Hi,
I need some help. Firstly I'm quite a noob so please go easy on me, have only flashed/rooted a couple of phones before this...both with pretty much no issues.
I flashed the CM 9.1 A while back to improve it, and decided I wanted to change it due to few bugs annoying me too much...such as the restarts, crazy battery life and most annoyingly of all calls only being able to be heard on loudspeaker! Buts can't seem to get any other rom to flash - tried 2 - samsation v6.0 kerneldev101 & MikTouch- 0.7-signed.
When trying to flash firstly 'samsation v6.0' i encountered an error code '"assert failed: getprop("ro.product.device") == "pyramid"
E:\Error in /storage/sdcard0/samsation v6.0.zip
(status 7)
Installation aborted.
and to try and overcome this I opened the updater script from rom zip and deleted the line 'assert(getprop("ro.product.device") == "pyramid" || getprop("ro.build.product") == "pyramid");'.....after reading in forums it could be this. After this line is deleted the flash attempt is 'opening update package...installing update...installation aborted'
I then tried MikTouch 0.7 and it came up with the 'status 7' error, so I deleted the first line of the updater script and now I am getting a 'status 4' error...even if I try to flash thru rom manager - CWM app.
Driving me crazy! Any help much appreciated.
even tried a different SD card to see if that makes a difference....and nope
installed new CWM - V6.0.4.6 after reading that may be the prob. no difference
To be honest it all P'd me off so much just went and bought myself the Moto G instead...but would still like to fix this one and get it even back to a stock like ROM so at least it functions properly but without all the bloatware.
Click to expand...
Click to collapse
Don't use CWM above 6.0.2.5 for flashing an older ROM. 6.0.4.6 is designed for KitKat and will fail older ROMs.
everything looks good on bootloader so the issue is with recovery or rom.zip
personally i think its the rom.zip, but I also recommend TWRP recovery
so i would download twrp (without dumblock) from HERE
and flash with fastboot, also do some erasing in fastboot for good mesure
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
the md5sum for recovery is listed next to download, be sure it matches use command line on linux or this for windows
but what i really think is the problem is the roms, bad download or whatever, the status 4 and status 7 are related to updater script, so either you playing with them messed them up or they were corrupt from the start
md5sum for MikTouch-0.7-signed.zip should be BAE9153946B02251621547DBFB537387
if not re download
now it is possible that the newer recoveries f\wont flash older roms, like Fuzi0719 said, but in theory they should and i have not had issues myself
but if need be weekends has posted older recoveries HERE be sure to thank him
flash with fastboot if you TWRP fails you
also when i see this --Installing: /storage/sdcard0/MikTouch-0.7-signed.zip
make me wonder, if i am correct the path on this phone is just /sdcard/MikTouch-0.7-signed.zip
but i cant recall as it has been months since i used my doubleshot, its just how i remember even the newer recoveries find sdcard path here
so maybe for good measure take everything important off sdcard and format to fat32
then put new rom on the root freshly formatted sdcard (not in any folders) before you flash
hope it all works out, if there is an issue let us know!
well I spent the whole evening mucking about with it and I have conquered it. Thanks guys for all the help...couldn't have done it without you!
After firstly having to switch to an older laptop as win 8.1 not compatible with htc drivers ...
I flashed TWRP and tried to flash new rom (miktouch 0.7) again through that, said failed. then tried to install the current ROM CM9.1 just out of interest which it also 'failed'
then considered the cwm comment about version, so flashed cwm 5.5.0.4. thru Hasoon 2000's ALL in 1 kit I still had. I then tried to reflash the current CM9.1 again, and it went through.....At the same time it occurred to me about me having 'messed' with the script files of MikTouch 0.7 ...maybe being the cause, so luckily, I had an original copy of the rom zip (kept justin kase lol) and then tried this method.
I now don't know if it was the script file or the cwm version number but hallelujah it WORKED. I honestly thought I was stuck on cm9.1 forever, I've spent so much time reading/trying to flash anything else!
Can't thank you all enough, whatever it was, I think I have overcome it now! phew.
:cyclops: :victory:

Categories

Resources