Database Develop

[Q] How to get back to vanilla from rooted FRF91 with custom recovery?

A couple of months ago I rooted my N1 FRF91 with Universal Androot. Later I flashed psfMod (based on CMW) custom recovery using flash_image recovery.
Now I don't have any use for custom recovery or a rooted device anymore, and want to get back on track to be prepared OTA 2.3.
I have received notifications for 2.2.1 OTA (2-part update), but the device just locks up during the upgrade and gets back to rooted 2.2 after a reboot.
So how do I apply the 2.2.1 update? Could I just flash the original recovery with flash_image (and what file should I get in that case), unroot with androot and just use the OTA? Or is there any better/easier way?
The question feels kinda nooby, but the only guides I find is to get back to shipping conditions (Which I don't want to keep my settings and so on),using fastboot which I can't since my bootloader still is locked or assumed that you are using a custom ROM which I don't.
Thanks for your help!

There is no need to get rid of a custom recovery or root to apply those updates. This has been covered in many threads.
This is what I would do. Use flash_image to flash Amon_RA 1.9.0 recovery. Then download the update (make sure you download the correct one: there is one that is FRG83D from FRF91, which is what you will need if you are running FRF91)and save it to the root of your sdcard. Then boot into recovery, and flash the update. (You will lose root and your custom recovery, but just root again if you want.) That covers part 2 of 2 of the update.
If you want to flash the first part, dowload the HBOOT 0.35 update file (floating around the forums) and place it in the root of your sdcard. Boot into recovery and flash that. You may have problems flashing certain custom recoveries after you flash the 0.35 HBOOT.

Thanks for your reply. If I follow your steps, the 2.3 OTA will work when it eventually comes?

F-Forward said:
Thanks for your reply. If I follow your steps, the 2.3 OTA will work when it eventually comes?
Click to expand...
Click to collapse
If you keep a custom recovery, you will still get the notification, but you will have to manually apply it. If you keep the stock recovery, it should be able to apply it automatically. No word yet on if the newer HBOOT is a requirement for 2.3 or not.

[Q] Booting PAST recovery...cannot apparently root.

Been flashing ROMs for months.Going back to stock then update..
With this last flash to Stock and after applying Update through recovery the phone will not root.
After reinstall packages after Update was applied the phone just boots and does not go into second recovery screen.
SU was never installed.
Any ideas what mucked up the Stock flash tp where One click or update root does not work?

Found the solution
New Update file

[Q] Froyo to GRJ22 question

Hi all,
I think I have to finally update my rooted Nexus 2.2.1 to the latest GB because the update nagging is driving me crazy :-(
So anyhow, can somebody tell me if this will work as expected (outcome should be rooted GB 2.3.4)
1. I have latest ClockworkMod Recovery installed
2. I grabbed the official update from /cache. Build.prop says it's GRJ22. Size is 89MB. The zip contains the update plus boot.img and radio.img
3. Renamed the file to update.zip and placed on root of sdcard
4. placed su.zip and fix-recovery.zip in the root of sdcard
So the plan is to reboot into recovery, flash the update.zip. Flash su.zip. Flash fix-recovery.zip and finally reboot.
The outcome should be a rooted GB 2.3.4 with all my apps and settings still present. Will this process work?
Thanks
Raf

Edit zip file and remove recovery image.

i wanna know if the wonk issue in grj22 has been solved..
anyone know?

Flash as a zip from sd, not as an update...

Thanks it worked
And special thanks to bohlool for saving my butt. Per his suggestion I removed the recovery image from the zip file prior to installing and it saved my root because the update rebooted the phone after installing it without giving me a chance to install su.zip.
Thanks again.
Raf

If you flash as a zip from SD, instead of as an update, your phone doesn't reboot...

I did just that, in CWM I selected flash zip, selected the file on SD, and confirmed. I started flashing, then rebooted once, then rebooted a second time and finally booted in the OS. Because I removed the recovery from the update, it did not reflash the recovery and I was able to reboot into CWM recovery and apply the su.zip update (and this time it did not reboot on it's own).
Btw, my GRJ22 update was 89MB vs 6MB what has been posted here as an official update.
Raf

Yeah, removing the recovery from the zip is possibly an easier way. My comment was for anyone who didn't know how to remove the recovery, our didn't feel comfortable doing it, etc...

You are welcome
raf1hh said:
And special thanks to bohlool for saving my butt. Per his suggestion I removed the recovery image from the zip file prior to installing and it saved my root because the update rebooted the phone after installing it without giving me a chance to install su.zip.
Thanks again.
Raf
Click to expand...
Click to collapse
I apply any update like this, full updates you need to remove image file, and partial updates, you need to remove recovery folder. This way, you will keep your recovery and can flash su and other zips later.
cheers.

[Q] cant update from ClockworkMod 3.0.0.5

I want to put a decent new ROM on this old thing but I'm have real trouble. I updated from Android 2.35 to 2.36 as I was having issues (and also as most tutorials point from 2.36). I've rooted and using Odin and and that had CWM Manager 2.0 installed on it. I added ROM Manager from the play market so I could update to the latest ClockworkMod as I understand I need that to put on a new ROM such as 4.4 - before updating it has ClockworkMod version 3.0.0.5 on it. So using ROM Manager I try and update to the latest ClockworkMod and all seems to work ok (it downloads etc) and on rebooting with the CWM Manager app it gives this error:
-- Installing package...
Finding update package...
Verifying update package...
E:failed to verify whole file signature
E:signature verification failed
Installation aborted.
A old thread on here says this: I had that problem 2 when I started. Turned out to be a recovery bug. With some batches of our phone it seems that you can only enter android recovery v3 and not cwm after rooting. Most kernels are not compatible with v3 only 2.
Source: http://forum.xda-developers.com/showthread.php?t=1995831
Is this correct/up to date? Or have I just done something wrong/missed out an important step? Do I need to flash a different kernal or something?
thanks alot

http://www.addictivetips.com/mobile/how-to-install-clockworkmod-recovery-on-samsung-galaxy-s-i9000/

pryerlee said:
http://www.addictivetips.com/mobile/how-to-install-clockworkmod-recovery-on-samsung-galaxy-s-i9000/
Click to expand...
Click to collapse
thanks man. Looks just the ticket. I have XXJU 2.36 so I am going to try this file CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS.zip - do I need to reset to factory again before I do this (as its currently rooted)? or will that be ok?

No should be fine just to flash, no need to factory reset, CF-Root is a stock kernel with root and cwm recovery included (it's ok that you already have root) just flash the zip file and reboot. good luck

pryerlee said:
No should be fine just to flash, no need to factory reset, CF-Root is a stock kernel with root and cwm recovery included (it's ok that you already have root) just flash the zip file and reboot. good luck
Click to expand...
Click to collapse
This still isn't playing ball. I've tried a couple of times, although the instructions aren't that great: eg: To fix this, you will need to use the stock recovery option that says ‘apply update.zip from SD card’ or something similar
When the new kernal is applied a a new CWM Manager 2.0 app a Tweaks app and Superuser is added. I have downloaded ROM manager and downloaded and installed what is I assume to be the latest CWM. No new CWM app appears as an app. I then reboot into recovery using the 2nd option in ROM Manager and the same error message comes up and it is still the Android system recovery 3e.
The instructions say "you will need to do this twice when attempting to enter ClockworkMod Recovery for the first time"
Its not clear at all exactly that update needs applying but when I have tried the relevant ones it hasn't worked.
When entering CWM 3.0.0.5 (via volume up power boot) and selecting apply update from sdcard it then ended up with entering CWM version 2.1.5.2! – then there is another option to apply apply the update and it reverts back to CWM 3.0.0.5!
This is a mare!

ok another option is to flash with mobile odin (free in market) then install the flash kernel here http://bit.ly/17kEetk unzipped CF-Root and placed it in Mobile ODIN, when you open mobile ODIN it'll say you need to download extra data, but it's only if you're flashing firmware, you don't need to download the extra data just for flashing kernels so ignore it, flash it and Mobile ODIN will install CF-Root then it'll auto reboot, once rebooted, go into recovery mod and you should now have CWM as well as Root access.

pryerlee said:
ok another option is to flash with mobile odin (free in market) then install the flash kernel here http://bit.ly/17kEetk unzipped CF-Root and placed it in Mobile ODIN, when you open mobile ODIN it'll say you need to download extra data, but it's only if you're flashing firmware, you don't need to download the extra data just for flashing kernels so ignore it, flash it and Mobile ODIN will install CF-Root then it'll auto reboot, once rebooted, go into recovery mod and you should now have CWM as well as Root access.
Click to expand...
Click to collapse
Does that process get around the android recovery v3 error problem and get me to the latest version of CWM? (Is it not just flashing the same files using a different method?)
Also I understand the need to download and install Mobile Odin but I am confused though as you have linked to the following files:
MobileODIN_FlashKernel_I9000-v1.0.zip
MobileODIN_FlashKernel_I9000-v2.0.zip
unzipped these are APKs (not kernals? or are they and I'm missing something?) so do I download (presumably verison 2) and install these as an app as well? Do I then run the MobileODIN_FlashKernel app or something?
I have read this guide on Mobile Odin, which makes sense, its just the extra APK is confusing me!
http://www.shetalksandroid.com/2012...din-install-firmwares-flash-kernels.html.html
thanks

Unzip MobileODIN_FlashKernel_I9000-v2.0.zip and you'll get MobileODIN_FlashKernel_I9000-v1.0.apk, FlashKernels are special kernels used by Mobile ODIN to help flash the selected firmware if it cannot be done with the kernel you are currently running. The FlashKernel is used temporarily, it does not remain on the device after the firmware flashing is complete. Click on it to install it as a normal apk then install Mobile ODIN, next open Mobile ODIN select your CF-Root kernel (it needs to be unzipped) and flash it, after it has flashed the phone will reboot, once it has rebooted power off and boot into recovery mode, you should now be on CWM Recovery.

whatagonad said:
This still isn't playing ball. I've tried a couple of times, although the instructions aren't that great: eg: To fix this, you will need to use the stock recovery option that says ‘apply update.zip from SD card’ or something similar
When the new kernal is applied a a new CWM Manager 2.0 app a Tweaks app and Superuser is added. I have downloaded ROM manager and downloaded and installed what is I assume to be the latest CWM. No new CWM app appears as an app. I then reboot into recovery using the 2nd option in ROM Manager and the same error message comes up and it is still the Android system recovery 3e.
The instructions say "you will need to do this twice when attempting to enter ClockworkMod Recovery for the first time"
Its not clear at all exactly that update needs applying but when I have tried the relevant ones it hasn't worked.
When entering CWM 3.0.0.5 (via volume up power boot) and selecting apply update from sdcard it then ended up with entering CWM version 2.1.5.2! – then there is another option to apply apply the update and it reverts back to CWM 3.0.0.5!
This is a mare!
Click to expand...
Click to collapse
Try flashing a zImage via Heimdall. You could try this

Unable to flash from 4.4.2 to stock or rooted Lollipop

I tried what I was advised here: http://forum.xda-developers.com/not...pgrading-stubborn-software-t3228423?nocache=1
I can successfully flash it but Kit Kat still boots up every time. I don't know what to do. Maybe twrp? How do I do that.
May also be relevant that I cannot seem to boot into recovery to do the fixes after I flash. 4.4.2 stil comes up.
Cheers!

You could just use Odin to go back to stock, always worked for me. The only reason I could think that you could have problems is that you have a custom rom already that changes your build and model.
Sent from my SAMSUNG-SM-N900A using Tapatalk

If you need to install stock rom you need to make sure build number is N900AUCUCNC2 and then use odin to install .
If you need to install root rom install Towelroot from play store and make sure wifi or data network is on during root then install SuperSU
BusyBox (open BusyBox and install from inside ), "Safestrap-HLTEATT-NC2-3.75-B03" recovery from fourm put your prerooted rom in sd card open Safestrap and boot to recovery you will be able to install rooted rom from there .