Database Users

[HOW TO] Revert to latest stock ROM (GRI40)

I personally have tried lots of ROM's but all I really want is the stock ROM with the option to root if I want. After lots of research, I couldn't find a comprehensive tutorial on how to do this. There is of course the GRI40 image available in update.zip format for custom recoveries which is helpful for most. However, if your a bit anal like me, and want the official update directly from Google servers, follow this guide. This might also be helpful for people who can't get into the custom recovery any more.
NOTE: I will not provide help for anybody. This guide assumes you have the Android SDK in order to use adb. There may be other ways of doing this, I am not an experienced programmer, this works for me, it will work for you.
[GUIDE]
Download the following files:
Stock Froyo Image (Contains stock recovery image)
Stock GRI40 Image
Instructions
You first have to revert to stock Froyo image to get the stock recovery back. This is needed to install the GRI40 update ZIP
1. Disable backup my settings under privacy settings.
2. Unzip the original Froyo shipping ROM and put it somewhere you can find
3. Plug in Nexus One with USB to computer (enable USB Debugging)
4. Open command prompt, navigate to SDK folder which contains adb. Type
Code:
adb reboot bootloader
(which will boot into the bootloader)
5. Confirm fastboot connection with
Code:
fastboot devices
6. Type
Code:
fastboot erase userdata
7. Type
Code:
fastboot erase cache
*If step 6 and 7 does not work, and if you have a custom recovery installed, you can do a factory data wipe from there. Also perform a dalvik-cache wipe.
Alternately, you can also do a factory data wipe within Android. Settings => Privacy Settings => Factory Data Reset.
8. Go to the directory that you stored your unzipped files from the official Froyo ROM, for ease of use, copy these into the directory containing adb.exe
9. Type
Code:
fastboot flash userdata userdata.img
10. Type
Code:
fastboot flash boot boot.img
11. Type
Code:
fastboot flash system system.img
12. Type
Code:
fastboot flash recovery recovery.img
13. Type
Code:
fastboot reboot
14. Once phone has started, skip all account setup. Copy the new GRI40 .zip from Google servers to the root of your SD card. Ensure it has been renamed to update.zip if necessary.
15. Reboot into bootloader mode (hold trackball when switching on), select recovery, you will see an exclamation mark with a little green Android.
16. Hold power button and press Vol. Up to see recovery menu. Select 'Apply: Update.zip'
17. After the system boots up and while setting up skip setting up with the google account and you can setup accounts later. This will prevent the phone from pulling down the previous settings (downloaded apps, wallpaper etc) from google.
18. You are done. Enjoy.
If you want to root:
Download the following:
Latest Clockworkmod Recovery
su.zip
Instructions
How to root the stock ROM
1. Download su.zip and copy to root of your SD card
2. Download a recovery image file and for ease of use, copy into same directory containing fastboot on your PC
3. Turn on USB debugging and connect phone to PC
4. Open command prompt, navigate to SDK folder which contains adb. Type
Code:
adb reboot bootloader
(which will boot into the bootloader)
5. Type
Code:
fastboot flash recovery recovery.img
where 'recovery.img' is the name of your recovery image file (easy thing to do is rename the file to 'recovery.img'!)
6. It will upload, once complete, disconnect you phone from computer
7. On your phone, select Bootloader, then Recovery to boot into your new recovery
8. Now select ‘Apply Update.zip’ and find the su.zip file (Turn off signature verification if using Amon RA)
Note:Custom recovery will be overwritten with the stock recovery on reboot but root privelages will still be in place.

No need to do that. Flash the stock rom. Done.
Sent from my Nexus One using XDA App

albundy2010 said:
No need to do that. Flash the stock rom. Done.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
You mean you can flash the official GRI40 zip from Google server with a custom recovery?

Iggy82 said:
You mean you can flash the official GRI40 zip from Google server with a custom recovery?
Click to expand...
Click to collapse
Yes!
Make sure it's the full image (80+meg), and not just the update (40+ meg). Recovery should restore to stock after a reboot...
Sent from my Nexus One using XDA Premium App

Well that serves me right for assuming Google would not allow an official update zip to install from a custom recovery!
Did the official update ZIP from Google come out after dsixda made his own update zip then?
The link above is for the full update zip from Google (80MB or so)
Sent from my Nexus One using Tapatalk

usually the official updates come out and people edit them to allow root, busybox, etc.
or just a stock rom that won't over write your custom recovery, etc.

Thanks for this. I have been looking for a stock image all morning!

How to Root without flashing custom recovery

HOW TO ROOT YOUR DEVICE WITHOUT FLASHING RECOVERY
This can be done with two methods.
ADB or FASTBOOT.
I have tested both methods and they worked for me.
I tested this on JSS15J. I am not sure about any other versions but I guess it should work.
SOME BASIC INFORMATION
Usually when you want to root your device, you must have UNLOCKED BOOTLOADER.
A CUSTOM RECOVERY is usually used to flash SuperSU to gain root access.
CUSTOM RECOVERIES ARE USUALLY FLASHED (they permanently replace your stock recovery)
In this guide, You BOOT into custom recovery by going into BOOTLOADER and then using fastboot/adb tools to flash SuperSU .
Booting is temporary and thus once you restart from recovery, the custom recovery will be gone
Make sure, you have USB debugging mode enabled. To go into bootloader you can either use adb commands ( Type [adb reboot bootloader] in cmd in platform tools directory with your device connected) or do it manually by turning it off and then holding power and volume down.
You must also have platform tools of SDK (Fastboot and ADB) for this to work. MAKE SURE YOU OPEN CMD into the folder where platform tools are present.
Try it on OWN risk. I will not be responsible for bricked devices or any damage.
ADB METHOD
Connect to your PC and make sure USB debugging is on.
COMMANDS IN BRACKETS. DON'T WRITE THEM. COMMAND WOULD BE LIKE : fastboot boot recovery.img
MAKE SURE YOUR DEVICE HAS UNLOCKED BOOTLOADER
(fastboot boot [recovery.img])--------------------- Name of recovery to be here
Mount /system and push the necessary files once the recovery has started:
(adb push su /system/xbin)
(adb push Superuser.apk /system/app)
Set correct permissions:
(adb shell)------------------------------ You have got into your device's shell
(chmod 06755 /system/xbin/su)
(chmod 0644 /system/app/SuperSU.apk)
(exit)
Reboot:
(adb reboot)
FASTBOOT METHOD
This is relatively easier as you will boot into custom recovery temporarily and then flash ZIP of SuperSU. Afterwards I recommend to clear davik cache and restart.
UNLOCKED BOOTLOADER REQUIRED
Boot into bootloader.
Type these commands to boot into custom recovery. This will not flash recovery and you will have stock recovery once you restart.
fastboot boot recovery recovery.img where recovery.img will be the file name of recovery
(After 4.4, use this command "fastboot boot recovery.img" instead of above mentioned)
After booting into reccovery, flash SuperSU and you are done.
I recommend clearing dalvik cache before leaving and restart.
And you are done.
YOU CAN ALSO USE A PREROOTED KERNEL WHICH YOU CAN FLASH VIA FASTBOOT. I AM NOT SURE IF THERE IS ANY
For information on how to retain root after OTA, please refer to this :
Update Super SU is also taken from this guide.
http://forum.xda-developers.com/showthread.php?t=2415497
For Recovery/SuperSU/TWRP
http://forum.xda-developers.com/showthread.php?t=2382051
CWM
http://forum.xda-developers.com/showthread.php?t=2381544
PLATFORM TOOLS:
http://www.androidfilehost.com/?fid=9390355257214632011
If you are stuck in a bootloop, make sure you have cleared dalvik cache in custom recovery.
I got bootloop when i tried with fastboot method as I was new to twrp, I explored it a bit and tried to remove system and tried overwriting data to see how it is different from CWM and check its strength. I got an error clearing cache so I rebooted into custom recovery to clear dalvik and my nexus booted fine (DON'T TRY THIS, JUST CLEAR CACHE AND WIPE DATA and restart)
REMEMBER, UNLOCKING BOOTLOADER WILL DELETE ALL YOUR DATA AND DOING WIPES WILL ALSO DELETE ALL YOUR DATA.
DALVIK WON'T DELETE YOUR DATA BUT
MAKE SURE YOU HAVE MADE A BACKUP using BACKUP PRO (non rooted) or Helium (non rooted) and Titanium Backup Pro (Daah, you are not rooted so this won't work)
GOOD LUCK

Booting into custom recovery to install root works fine.
As you mentioned unlocking bootloader is still a prerequisite.
You may want to just use the SuperSU install zip though. Though I haven't tried Superuser on this tablet, it is my understanding it hasn't been modified to work with 4.3 security. That may have changed since I last looked so if you find differently please post. SuperSU added a daemon mode to deal with 4.3 security changes.

sfhub said:
Booting into custom recovery to install root works fine.
As you mentioned unlocking bootloader is still a prerequisite.
You may want to just use the SuperSU install zip though. Though I haven't tried Superuser on this tablet, it is my understanding it hasn't been modified to work with 4.3 security. That may have changed since I last looked so if you find differently please post. SuperSU added a daemon mode to deal with 4.3 security changes.
Click to expand...
Click to collapse
I got bootloop but then realised it might due to trying to wipe system in twrp. Clearing dalvik worked fine .SuperSU used

So you don't replace stock recovery if you boot into a custom recovery using fastboot?
Sent from my Nexus 7 (2013)

Muikkuman said:
So you don't replace stock recovery if you boot into a custom recovery using fastboot?
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
The trick here is to BOOT into custom recovery BUT not FLASH recovery permanently. Once you restart, the CUSTOM recovery will be gone.
You can use simple commands if using Fastboot
fastboot boot recovery [recovery name.img]
This way you will install SuperSU using recovery which is relatively easier than ADB commands.
You will only go into recovery temporarily.
I also read a forum where you can preserver root even after OTA/ Updates.
[UPDATE]
http://forum.xda-developers.com/showthread.php?t=2415497
Do check that out as well.
I tried this with Twrp and superSU.
I got bootloop as I have been always CWM person so I accidently tried to delete system too with dalvik cache and hard reset and I got an error
However, I boot again into recovery and cleared wipes and the bootloop was gone

Hnk1 said:
The trick here is to BOOT into custom recovery BUT not FLASH recovery permanently. Once you restart, the CUSTOM recovery will be gone.
You can use simple commands if using Fastboot
fastboot boot recovery [recovery name.img]
This way you will install SuperSU using recovery which is relatively easier than ADB commands.
This way you will only go into recovery temporarily.
I also read a forum where you can preserver root even after OTA/ Updates.
Do check that out as well.
I tried this with Twrp and superSU.
I got bootloop as I have been always CWM person so I accidently tried to delete system too with dalvik cache and hard reset and I got an error
However, I boot again into recovery and cleared wipes and the bootloop was gone
Click to expand...
Click to collapse
Thanks for your reply I'll make sure to check everything out.
Sent from my Nexus 7 (2013)

Muikkuman said:
Thanks for your reply I'll make sure to check everything out.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Anytime mate

How do we clear dalvik without a custom recovery?

Master619 said:
How do we clear dalvik without a custom recovery?
Click to expand...
Click to collapse
You restart your device. Boot into bootloader and use fastboot to Boot into custom recovery(command given in post above).Once Into recovery, you can easily clear dalvik cache.
And remember, it might not require clearing cache because I was exploring twrp n overwriting data n tried To delete system to see how powerful the recovery is. I will update guide now

muikkuman said:
so you don't replace stock recovery if you boot into a custom recovery using fastboot?
Sent from my nexus 7 (2013)
Click to expand...
Click to collapse
master619 said:
how do we clear dalvik without a custom recovery?
Click to expand...
Click to collapse
guide updated. Check it.
Platform tools are being attached

The "fastboot boot recovery recovery.img" command is not working anymore. The command prompt returns with a "cannot load recovery" error. At least that's what it does on my Nexus 7 running Android 4.4.2.
This seems to affect Android 4.3 and upwards according to this Nexus 4 thread: http://forum.xda-developers.com/nexus-4/help/solved-fastboot-boot-recovery-img-t2380675
There's a workaround with a different fastboot command line as mentioned in the thread. I wonder if there's also a fix for the Nexus 7. Any replies would be greatly appreciated.

gunner49 said:
The "fastboot boot recovery recovery.img" command is not working anymore. The command prompt returns with a "cannot load recovery" error. At least that's what it does on my Nexus 7 running Android 4.4.2.
This seems to affect Android 4.3 and upwards according to this Nexus 4 thread: http://forum.xda-developers.com/nexus-4/help/solved-fastboot-boot-recovery-img-t2380675
There's a workaround with a different fastboot command line as mentioned in the thread. I wonder if there's also a fix for the Nexus 7. Any replies would be greatly appreciated.
Click to expand...
Click to collapse
Did you try: fastboot boot recovery.img ?

mdamaged said:
Did you try: fastboot boot recovery.img ?
Click to expand...
Click to collapse
That worked a treat! Thanks a lot mate!

Those who finding difficulty in rooting Nexus 7 (2013) can use Wugfresh Nexus Root Toolkit. It is so powerful that you would find every function you would like to do on your Nexus 7, from the comfort of your PC. Also watch qbking77 's video on using the Toolkit for further information.

Asus zenfone 5 not start

I install twrp and accidentally wipe all system data there is no backup
when i install new firmware it says unknown file system osip.
when i go to recovery it says there is no os
my phone is not start?
plz help me

Just flash the rom you want. The osip thing is dosen't matter. Just flash the rom and you are golden

How to flash rom?

Magan Mittal said:
How to flash rom?
Click to expand...
Click to collapse
What kind of recovery are you using? If you are using stock recovery. Just use add sideload. If you are using TWRP. Then go to fastboot and flash the stock recovery. You can find the stock recovery in the rom downloaded from Asus : https://www.asus.com/Phone/ZenFone_5_A500CG/HelpDesk_Download/. Version 2.22.40.540 is recommended

i use twrp and adb sideload and recovery mode not working

Magan Mittal said:
i use twrp and adb sideload and recovery mode not working
Click to expand...
Click to collapse
Step 1: Flash recovery I'm via fastboot with "Fastboot flash recovery recovery.img"
Step 2: boot to recovery.
Step 3: Chose Adb sideload option in recovery.
Step 4: use command 'adb sideload (rom). zip

Install Stock Recovery Meizu M2 Mini

Step :
Install driver adb
USB Debugging - ON
Root device
Install Rootexplorer-3.3.8.apk
Install Rebootmanager.apk
Take the file system/bin/install-recovery.sh from stock rom.zip
Customize with its version Flyme
Copy the file install-recovery.sh to sdcard (mmc internal)
Rename root/system/ recovery-from-boot.bak
Into root/system/recovery-from-boot.p
Seting permission recovery-from-boot.p into rw-r-r
Execution using adb
adb shell
sh /sdcard/install-recovery.sh
reboot recovery​
Or execution with terminal emulator.apk
su
sh /sdcard/install-recovery.sh
reboot recovery​
Finished :laugh:
Install Custom Recovery with fastboot, flashify, etc.
Bootloop solution after unlock the bootloader because the data can not be mounted:
Press and hold the key (vol+ & power) a bit longer to actually able to enter recovery mode (twrp/cwm/philztouch/etc)
Wipe factory reset
Flash stock rom.zip
Finished
* Thanks to Allah SWT.

zround said:
Step :
Install driver adb
Root device
Install Rebootmanager.apk
Customize with its version Flyme
Rename root/system/ recovery-from-boot.bak
Seting permission recovery-from-boot.p into rw-r-r
Or execution with terminal emulator.apk
su
sh /sdcard/install-recovery.sh
reboot recovery
Press and hold the key (vol+ & power) a bit longer to actually able to enter recovery mode (twrp/cwm/philztouch/etc)
Flash stock rom.zip
Finished
* Thanks to Allah SWT.
Click to expand...
Click to collapse
in terminal command it shows that recovery.sh not found

My mini M2 condition:
1. It's UBL
2. Custom recovery TWRP
3. Custom ROM Lineages 14.1
Problem: GAPPS error. Google play services keep stopped.
Steps you've tried:
1. install GAPPS with OpenGapps for Lineages 14.1
2. install using f-droid (Gapps replacement)
3. install Google installer.apk with ROM Flyme 6
the problem remains the same as above.
is it can solve my problem wanna get back to Flyme Os and also GAPPS problem?
or flashing use the firmware via flashtool?
I tried looking at the XDA Forum, and Google has not found it.
.
thank you

zround said:
Step :
Install driver adb
USB Debugging - ON
Root device
Install Rootexplorer-3.3.8.apk
Install Rebootmanager.apk
Take the file system/bin/install-recovery.sh from stock rom.zip
Customize with its version Flyme
Copy the file install-recovery.sh to sdcard (mmc internal)
Rename root/system/ recovery-from-boot.bak
Into root/system/recovery-from-boot.p
Seting permission recovery-from-boot.p into rw-r-r
Execution using adb
adb shell
sh /sdcard/install-recovery.sh
reboot recovery
Or execution with terminal emulator.apk
su
sh /sdcard/install-recovery.sh
reboot recovery
Finished :laugh:
Install Custom Recovery with fastboot, flashify, etc.
Bootloop solution after unlock the bootloader because the data can not be mounted:
Press and hold the key (vol+ & power) a bit longer to actually able to enter recovery mode (twrp/cwm/philztouch/etc)
Wipe factory reset
Flash stock rom.zip
Finished
* Thanks to Allah SWT.
Click to expand...
Click to collapse
By the way,you don't need to do all these. If you need to replace twrp to stock. Just flash flyme update.zip inside twrp or any recovery you have now. It may get replaced to stock automatically.

Guys, you can just flash the stock recovery using fastboot

Installing TWRP and LineageOS ROM over stock ROM

My phone is wt86047 with stock ROM, and I want to install TWRP then LineageOS. The process I do is the following:
1. From fastboot, flash latest TWRP twrp-3.6.1_9-0-wt88047.img using fastboot flash recovery twrp-3.6.1_9-0-wt88047.img
2. Boot into recovery, flash resize_wt88047x_v6.zip
3. Reboot into fastboot, enter fastboot -w
4. Phone goes into bootloop.
5. Flash stock ROM again with MiFlash.
6. I'm now back to step #1.
What am I doing wrong?

bomberb17 said:
What am I doing wrong
Click to expand...
Click to collapse
Skip step "3. Reboot into fastboot, enter fastboot -w" and try again. Are you executing fastboot -w because the flash script wants you to do this?

WoKoschekk said:
Skip step "3. Reboot into fastboot, enter fastboot -w" and try again. Are you executing fastboot -w because the flash script wants you to do this?
Click to expand...
Click to collapse
Yes, that is what the flash script tells me. If I skip step #3, then the partition containing lineage-19.1-20220323-UNOFFICIAL-wt88047x.zip is lost. Also TWRP recovery no longer works after the partition script.

bomberb17 said:
Yes, that is what the flash script tells me. If I skip step #3, then the partition containing lineage-19.1-20220323-UNOFFICIAL-wt88047x.zip is lost. Also TWRP recovery no longer works after the partition script.
Click to expand...
Click to collapse
what about using lineage recovery as recommended in this thread?
[ROM][12.1][UNOFFICIAL][wt88047x] LineageOS 19.1
Important information: This thread is for LineageOS 19.1 opensource builds for Wingtech WT88047, marketed as Redmi 2 by Xiaomi. The following will not be supported in this thread: Custom Kernels Mods Modified system files Xposed Magisk What's...
forum.xda-developers.com
Instead of flashing any zip you have to sideload them with ADB

Lineage recovery link is broken..
And what is the way to sideload lineage-19.1-20220323-UNOFFICIAL-wt88047x.zip? And after which step?

So after I install resize_wt88047x_v6.zip, I get:
"WARNING - TWRP DETECTED
Please reboot to fastboot and run the following:
fastboot -w
Done!"
I didn't reboot to fastboot this time, and I followed this process for the lineage rom
How to Install Custom ROM on Android via ADB Sideload
In this comprehensive tutorial, we will show you the detailed steps to install a Custom ROM on Android using ADB Sideload feature of TWRP.
www.droidwin.com
and the log says:
"..
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 1
mount -o bind '/data/media/0' '/sdcard' process ended with signal: 6"
Thoughts?

bomberb17 said:
So after I install resize_wt88047x_v6.zip, I get:
"WARNING - TWRP DETECTED
Please reboot to fastboot and run the following:
fastboot -w
Done!"
I didn't reboot to fastboot this time, and I followed this process for the lineage rom
How to Install Custom ROM on Android via ADB Sideload
In this comprehensive tutorial, we will show you the detailed steps to install a Custom ROM on Android using ADB Sideload feature of TWRP.
www.droidwin.com
and the log says:
"..
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 1
mount -o bind '/data/media/0' '/sdcard' process ended with signal: 6"
Thoughts?
Click to expand...
Click to collapse
You need to sideload it only in Lineage recovery and not in TWRP.
Try this:
1. flash resize_wt88047x_v6.zip
2. reboot into fastboot and run fastboot -w
3. start TWRP and go to Wipe > Format Data
4. reboot into TWRP
5. flash the ROM
If error still exists do not reboot and start ADB. Then run adb pull /tmp/recovery.log recovery.txt. This will save a copy of the TWRP log named recovery.txt inside your ADB folder. Then upload this file here.

bomberb17 said:
Lineage recovery link is broken..
Click to expand...
Click to collapse
Extract the lineage 19.1 rom and find recovery.img
put it into platform tools folder and execute fastboot command
fastboot flash recovery recovery.img
fastboot reboot
then you have lineage recovery

I finally managed to install lineage rom by sideloading resize_wt88047x_v6.zip, then formatting data, cache and system partitions, then adb reboot recovery then sideload lineage rom.
Phew!