Database Info

[Q] DI18 OTA failed. How to remove CWM Recovery?

Hey guys, quick question:
I'm fully rooted/one-click CWM'd (stock everything, however), and I just got the OTA DI18 update notification. When I tried to install it, it booted to the stock recovery (blue text) and said something about verification of the signature failing...installation aborted.
Now, how would I go about either uninstalling CWM, or reflashing the stock recovery? I can't find anything that really goes into detail about any of this.
Any help would be most appreciated!

mooshubob said:
Hey guys, quick question:
I'm fully rooted/one-click CWM'd (stock everything, however), and I just got the OTA DI18 update notification. When I tried to install it, it booted to the stock recovery (blue text) and said something about verification of the signature failing...installation aborted.
Now, how would I go about either uninstalling CWM, or reflashing the stock recovery? I can't find anything that really goes into detail about any of this.
Any help would be most appreciated!
Click to expand...
Click to collapse
Same thing here, except I also had a overclocked kernel. What I did was use ODIN, there is a thread here. I downloaded the stock files full install.
1) Download full recovery image and Pit file
2) Open Odin and point to the PIT file downloaded and in PDA section point to the full firmware.
3) Check only Reboot and Debug in ODIN
4) Power on phone while holding 1 on the keyboard (it will go into download mode)
5) in ODIN press START and flash image
6) Then update to to the new image
7) Re root phone using 1 click
8) Install Clockwork Mod again 1 Click
9) update superuser
Have fun

mooshubob said:
Hey guys, quick question:
I'm fully rooted/one-click CWM'd (stock everything, however), and I just got the OTA DI18 update notification. When I tried to install it, it booted to the stock recovery (blue text) and said something about verification of the signature failing...installation aborted.
Now, how would I go about either uninstalling CWM, or reflashing the stock recovery? I can't find anything that really goes into detail about any of this.
Any help would be most appreciated!
Click to expand...
Click to collapse
well what i did is i download this file http://forum.xda-developers.com/showthread.php?t=786266 the i went to cwr and wipe data/factory reset thats only if u deleted any sprint apps... then flash it and u are good to go!!!

Whew. Worked with the full release (the zImage.tar failed and near-bricked my phone haha). Getting the DI07 update now, should hopefully see the new one soon-ish. Then I'll re-root and restore my backup.

4349 brick

I did the OTA update today, and attempted an install of CWM. I'm not sure if it went all the way through.
The tablet was still working fine.
When attempting to load an update of 4349 with market, the gtab gets stuck at "booting recovery kernal image".
Now the g-tab will not load at all. I attempted the NV Flash procedure but it failed at the final step during the batch where it could not find the file.
Any tips on what I should do next?

which method? Linux, windows?

windows version.

if you can, give us a list of files in your nvflash directory.

thank you, you got me in the right direction. i did not extract the gtablet file.

yea, with all these tools available, it's really hard (is it possible?) to brick g-tab . ..

210danielz,
Unless I misunderstood your first post, it sounds like you have a CWM problem.
Running CWM with 4349 will cause semi-bricks -- and several of us have tried
to post warnings to that effect all over the forum.
IMO, you probably should NVFlash back to stock and let the OTA update take
you back to 3588. Then you will be stock with a solid rom and can do what you
want.
http://forum.xda-developers.com/showthread.php?t=861950
Good Luck,
Rev

210danielz said:
I did the OTA update today, and attempted an install of CWM. I'm not sure if it went all the way through.
The tablet was still working fine.
When attempting to load an update of 4349 with market, the gtab gets stuck at "booting recovery kernal image".
Now the g-tab will not load at all. I attempted the NV Flash procedure but it failed at the final step during the batch where it could not find the file.
Any tips on what I should do next?
Click to expand...
Click to collapse
Here is more info on 4349.
http://forum.xda-developers.com/showthread.php?t=1035983
Roebeet ran a lot of tests and found that 4349 is not compatible with CWM.

210danielz,
When someone gets a bad NVFlash like that I always tell them to:
Take the procedure and go through and check everything. Make sure right
.zip files used. Check every little detail.
Re-run the NVFlash.
If previous step fails again, try nvflashing CWM only:
http://forum.xda-developers.com/showthread.php?t=1030042
If you get a good flash on CWM and get it up, the go to the
Advanced Menu and Partition (2048/0), Fix Permissions, Wipe
Dalvic Cache. Then Return to Main Menu and Wipe Cache
and Wipe/Reset Factory Data.
Having done the above, shut down and go back and NVFlash
to stock again (having cleaned out and repartitioned to
hopefully make it work right this time!)
Hopefully this will give you a working G-Tablet with Bekit 1105
or stock Version 2638 on it. If you set up wifi it will pretty
quickly offer you an OTA to 3588.
From there you can go where you want.
Hope this helps,
Rev

[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!

Root, EP OTA?

I just finished putting on Clockwork recovery after the OTA and then flashed Imosyen's 4.0 kernel. During the process I heard the Voodoo stuff take place, but upong rebooting my phone I don't have root. I read in these boards on the EE4 OTA that this should have worked, any ideas and has anyone got thier phone rooted on the new OTA?
Thanks.

luckdog said:
I just finished putting on Clockwork recovery after the OTA and then flashed Imosyen's 4.0 kernel. During the process I heard the Voodoo stuff take place, but upong rebooting my phone I don't have root. I read in these boards on the EE4 OTA that this should have worked, any ideas and has anyone got thier phone rooted on the new OTA?
Thanks.
Click to expand...
Click to collapse
Try getting back into CW recovery and let me know how that goes. If so then just download superuser and you got it.

No root
I can boot into CWR after using ODIN to put it on once and under voodoo controls app it shows my phone as being voodoo on all partitions, just don't have root. I knew the OTA would kill root, was just hoping thier was a quick fix out there like just flashing a kernel. The phone is pretty snappy though with imoysens kernel running voodoo and using ADW as the launcher. Like what I see so far.

luckdog said:
I can boot into CWR after using ODIN to put it on once and under voodoo controls app it shows my phone as being voodoo on all partitions, just don't have root. I knew the OTA would kill root, was just hoping thier was a quick fix out there like just flashing a kernel. The phone is pretty snappy though with imoysens kernel running voodoo and using ADW as the launcher. Like what I see so far.
Click to expand...
Click to collapse
Someone didn't read the instructions for properly installing the leaked OTA?
BEFORE YOU ODIN BACK TO EE4, MAKE SURE YOU HAVE THE SU FLASHABLE ZIP, THE OTA UPDATE AND IMOSEYON'S KERNEL ON YOUR SDCARD!
Make sure the update file is renamed to "update" and that it's on the root of your sdcard. (not in any folders or anything)
Odin back to EE4. Reboot normally.
Turn the phone off, then reboot into Stock Recovery and run the update.
Once the update finishes and the phone boots regularly. Reboot into Download Mode and plug the phone into the computer.
Start Odin, Uncheck "Auto Reboot", select PDA, NOT PHONE!
Click on the PDA tab and find your recovery file then click "start."
Once it is done and you see the word "PASS" on Odin, unplug the usb cable and press down all three buttons to boot into recovery (volume up, home, power)
Once in recovery, wipe cache, wipe dalvik, mount /system and flash the SU flashable zip.
Go back and wipe cache and dalvik again, mount /system again and flash the kernel.
After that, your recovery will stick and you're good to go. You are now rooted and running on EP4D.
Here is the flashable Super User zip. http://www.multiupload.com/V6R1RZJPXV

luckdog said:
I just finished putting on Clockwork recovery after the OTA and then flashed Imosyen's 4.0 kernel. During the process I heard the Voodoo stuff take place, but upong rebooting my phone I don't have root. I read in these boards on the EE4 OTA that this should have worked, any ideas and has anyone got thier phone rooted on the new OTA?
Thanks.
Click to expand...
Click to collapse
Did you install superuser? I bet you are rooted, but you don't have the tools installed to use it.
Sent from my SCH-I510 using Tapatalk

Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to Q&A

Thanks!!! Rooted
spc_hicks09,
Thanks sir, I started from CWR and followed the instructions and it worked! The original instructions I got yesterday didn't have any information on rooting, just on how to install the update. I appreciate the help and if the "spc" in your username represents a military rank, thanks for serving!

luckdog said:
spc_hicks09,
Thanks sir, I started from CWR and followed the instructions and it worked! The original instructions I got yesterday didn't have any information on rooting, just on how to install the update. I appreciate the help and if the "spc" in your username represents a military rank, thanks for serving!
Click to expand...
Click to collapse
You're very welcome for the instructions! Yes the Spc in my name is my rank and thank you for your support!

most if not all root issues can be fixed by simply flashing superuser in CWM (you can get the latest .zip from the dev ChainsDD's superuser site), then downloading/updating it in the market if it doesn't show up
blazing through on my 4G Droid Charge

If interested, the CWM version found here is already rooted.

[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 )