Stucked in recovery - Samsung Galaxy SL i9003

Hi, i installed the bagaria cwm, then i wiped the all system, it was on 2.3, i wanted to install the new software slim bean, but im getting assert failed: run_program("tmp/updater/sh") ==0, so i have no idea what version of software it was, and i cannot move forward, what i should do?

Related

[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

please help with my phone: can't update ROM, keep getting error msgs!

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.

[Q] Updating to 4.1.1 OTA

I am trying to update my Nexus S i9020a (currently on stock 4.0.4) to stock Jelly Bean, but I'm running into some problems.
First, I got the notification that said there was an OTA update available for 4.1.1, so I started downloading it. After verification, it starting the countdown timer for restarting. When the counter reached 0, my phone did not update, but instead just told me that I was up to date.
I thought that was weird, so I used this thread to download the ota for manual installation. I rebooted into recovery and selected the update. I got the following:
Code:
Verifying current system...
assert failed: apply_patch_space(16570800)
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
I didn't mind losing my data since I have everything backed up, so I went to this page to download the official images. I followed the instructions to flash the stock bootloader, recovery, and 4.0.4 ROM.
The same thing happened. I got the OTA notification, it downloaded and nothing happened. I tried manual install, but got the Status 7 error.
I then downloaded Google's official Gingerbread image and flashed that. I got a notification for the 4.0.4 update. It installed without any problem. Once that was done, I got another notification for the 4.1.1 update. It didn't work, though. The countdown started, but the phone did not reset and it said the phone was up to date. I tried the manual update again and got another Status 7.
Sorry if this is a bit long, but I wanted to say everything I have tried. I have looked through other threads and they mention using CWM, but I would rather not use a custom recovery. I prefer to stay on stock for now.
Gregsaw said:
I am trying to update my Nexus S i9020a (currently on stock 4.0.4) to stock Jelly Bean, but I'm running into some problems.
First, I got the notification that said there was an OTA update available for 4.1.1, so I started downloading it. After verification, it starting the countdown timer for restarting. When the counter reached 0, my phone did not update, but instead just told me that I was up to date.
I thought that was weird, so I used this thread to download the ota for manual installation. I rebooted into recovery and selected the update. I got the following:
Code:
Verifying current system...
assert failed: apply_patch_space(16570800)
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
I didn't mind losing my data since I have everything backed up, so I went to this page to download the official images. I followed the instructions to flash the stock bootloader, recovery, and 4.0.4 ROM.
The same thing happened. I got the OTA notification, it downloaded and nothing happened. I tried manual install, but got the Status 7 error.
I then downloaded Google's official Gingerbread image and flashed that. I got a notification for the 4.0.4 update. It installed without any problem. Once that was done, I got another notification for the 4.1.1 update. It didn't work, though. The countdown started, but the phone did not reset and it said the phone was up to date. I tried the manual update again and got another Status 7.
Sorry if this is a bit long, but I wanted to say everything I have tried. I have looked through other threads and they mention using CWM, but I would rather not use a custom recovery. I prefer to stay on stock for now.
Click to expand...
Click to collapse
First to flash an update u need a custom recovery. if not u will get that error
second dont mind to use a custom recovery bcz after the update your recovery will be back to stock
if this helped dont forget to hit that thanks button
Cascabreu said:
First to flash an update u need a custom recovery. if not u will get that error
second dont mind to use a custom recovery bcz after the update your recovery will be back to stock
Click to expand...
Click to collapse
I didn't realize the update wrote over the recovery. Thanks
Gregsaw said:
I didn't realize the update wrote over the recovery. Thanks
Click to expand...
Click to collapse
on any stock rom, at each boot it will overwrite the recovery
So I could use fastboot/adb to install the custom recovery, then install the zip from sd and the phone would be exactly the same as it would be if I were to receive the update notification directly and installed it that way? Should I wipe cache and dalvik in this scenario?
TheIowaKid said:
So I could use fastboot/adb to install the custom recovery, then install the zip from sd and the phone would be exactly the same as it would be if I were to receive the update notification directly and installed it that way? Should I wipe cache and dalvik in this scenario?
Click to expand...
Click to collapse
yes it's exactly the same, if u want u can wipe cache and dalvik before flashing (that's even recomended from some devs )

(Status 7) Installation Aborted. What to do? [FIXED]

Hi there.
I have Samsung Galaxy S Plus (i9001). I rooted device, installed Clockworkmod. I did everything like is written here:
http://forum.xda-developers.com/showthread.php?t=1578821
Before instalation I full wiped. Mounted system. Everything what is written in above link.
But when I started installation I got "Status 7 Installation aborted". I thought that maybe Jelly Bean ROM was bad, so downloaded ICS ROM too. But the same happened with ICS ROM too.
I had no problems with Linux, Windows or Mac OS instalations, but with Android... Doh. I'm confused what to do next.
EDIT: FIXED
I installed CWM CM9 recovery (or something like this) and it worked.

TWRP Recovery

Hello, I am having some problems installing a working recovery, here is my story... So first the device was 10.6.1.27.5 and its unrootable, so i downgraded to 10.6.1.15.3, where I installed TWRP recovery, and flashed CM 10.2 ROM, but it was too glitchy, so i wiped all data, and fastbooted 10.6.1.15.3 build and stock ROM. So I am now stock,
I am rooted using MottoChop method, and I cant install a custom recovery... I tryed to install TWRP 2.5.0.0 thats the version I was on before, and also tied 2.6.3.0, when flashing the .blob My device turns unresponsive, even when rebooting it with fastboot.
So left with no choice i tried flashing the .img one for JB, (Note: It is currently NOT a OTA update, but manual, so i used the 4.2 first)
I was Able to Flash the custom recovery 2.6.3.0 JB.img and it booted up and worked fine, but then it couldnt mount anything,
I was getting error message:
E: Cant mount /data
and so on... I then tried to flash 2.5.0.0 and got the same result.
GooManager cant find a recovery script for this device...I flashed the TF300T, since thats the kind i have not TF300TG
Im really lost now... I tried ClockworkManager to find a recovery and it said the same thing, I dont want to flash a CWM with flashboot since i here It is terrible.
Any Help Is greatly Appreciated
I notice that alot of these problems, I end up fixing myself... I fixed the issue
But If anyone ever comes into the same situation, heres the fix...
UPDATE to 10.6.27.5 (Yes newest version) Im using US...
Install openrecovery-twrp-2.5.0.0-tf300t-4.2.blob IMPORTANT dont flash the JB version because its only for OTA updates
Open recovery and TWRP will prompt you to install, and beleive it or not, but apparently you can root the newest version,
Just not With MottoChopper and other quick root methods!
If you have any more question, post!

Categories

Resources