[TWRP + Root] Galaxy J7 Refine (8.0) (Boost/Sprint) - Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth

[TWRP + Root] Galaxy J7 Refine (8.0) (Boost/Sprint) - Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth

TWRP has been successfully ported to the Galaxy J7 Refine (SM-J737P) (Oreo 8.0)ROOT METHOD POSTED BELOW IN POST #2Giving credit where credit is due:
@Dark98 for compiling the TWRP.img
@☆KØŁØЯΛĐØ☆ providing device files + testing/porting
@topjohnwu for Magisk
DISCLAIMER: This is NOT in Odin flashable .tar format. Due to sporadic updates in security & Oreo, Odin won't be much help here.
This has been tested & confirmed working on device build R16NW.J737PVPU1ARG3. It should work on other versions.
UPDATE: This will work on any Oreo version as well, including the new April 1, 2019 R16NW.J737PVPS3ASC2 update.
The patched_boot.img.tar I've attached will not work if you are on a different version of Oreo. You must provide your own patched_boot.img.tar that coincides with your respective version.
Proof of port is in the screenshot below (I've underlined the device build)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There is a downside & an upside:
- The downside is that after you flash TWRP & reboot, you will lose root.
- The upside is that TWRP will remain so all you need to do to regain root is flash the Magisk-v18.1.zip in Recovery.
Procedure:
- In order to flash, you need an app that will do so without booting into recovery. View attachment Flashify.apk is the ideal choice for this procedure.
- Flash TWRP in Flashify but do not reboot from the app itself. Power off your device & boot into [TWRP] Recovery manually.
PAY ATTENTION TO THESE NEXT FEW STEPS!!!
- Extract the twrp.img from View attachment J737P_TWRP.zip
- Flash through Flashify, then boot into TWRP for the first time
- Now that you have booted into TWRP the first time, Swipe to allow modifications
- Navigate to Wipe > Format Data > type yes when prompted (this will not delete any files you have in your Internal Storage)
- Once the format is completed, go to TWRP home screen & Reboot > Power Off
DO NOT REBOOT TO SYSTEM
- Once device powers off, reboot back into TWRP (yes you will boot into recovery twice)
If you fail to immediately boot back into TWRP, you will brick & have to start over. The fiirst reboot is to clear out (wipe) the /Data partition to make room for your new recovery. Wiping will not delete any internal storage items. However, it will return a value of 0 for /Data. The second boot is to secure TWRP as your new Recovery, as well as fix the /Data return value.
- Now that you have secured TWRP, go ahead & make a TWRP backup as a safety precaution before you reboot. The backup could be considered "stock" with TWRP as the Recovery. The reason being is that you will lose root after formatting /Data. No worries, you will get it back.
After creating the backup, follow these next steps very carefully!!
You will now flash Magisk-v18.1 to regain root. With the new security measures Samsung put in late 2017, you will need to flash 2 .zip files after to ensure that root sticks.
YOU NEED TO FLASH THESE FILES IN ORDER. DO NOT WIPE CACHE AFTER EACH FLASH. DO NOT REBOOT AFTER EACH FLASH. FLASH EACH PACKAGE ONE AT A TIME. WAIT UNTIL THE 3RD FLASH IS COMPLETE & THEN REBOOT DEVICE. IT WILL TAKE SEVERAL MINUTES SO BE PATIENT.
(Still in TWRP)
- Go to Home & select Instal
- In this order, flash one at a time:
View attachment Magisk-v18.1(18100).zip
View attachment no-verity-opt-encrypt-6.0.zip
View attachment RMM-State_Bypass_Mesa_v2.zip
DO NOT WIPE THE CACHE
Screenshots of proper installation (in order):
- Reboot device normally. If you do not flash the dm-verity & RMM .zip files in order, you will bootloop & have to start over.
- When you get to your home screen, you will receive a notification to update Magisk. Update by either selecting the notification or manually through Magisk Manager.
- Allow Magisk to install the update; do not update through TWRP.
ĐØΠΞ

[ROOT] Galaxy J7 Refine (SM-J737P) (Oreo 8.0)
FOLLOW THESE DIRECTIONS. I AM NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE.
View attachment 4733553 View attachment 4733552
I have given you a freebie by providing the patched_boot.img.tar, thus saving you a few steps
All files needed are uploaded to my Drive: https://drive.google.com/folderview?id=1-8CGkYef58I-DrkyOshRFniecO_0dBDc
NOTICE: Patched_boot.img.tar is solely for the J737PVPU1ARG3 software version. Any attempt to flash to a different version will result in a bootloop. You must patch + flash your own stock boot.img if you are on a different software version.
YOU MUST PAY ATTENTION TO THE FOLLOWING
- In the Bli5zkrieg.zip you extracted, load up Odin_v13.1 (non-patched)
- Load only the BL/AP/CP files from your stock firmware into Odin
- As soon as the flashing process ends, you must reboot quickly back into Download Mode. You have to be quick. If you allow the device to begin booting up, it makes the rooting process more difficult.
Assuming you followed directions...
- Close Odin_v13.1 & unplug your device while still remaining in Download Mode
- Launch Odin_v13.1 [Patched] & load up the patched_boot.img.tar in the AP slot
- Reconnect device & proceed to flash
- Device will reboot with "Verification Failure" so you must reset (this is part of root) (it does not activate FRP lock)
- When device reboots to Setup Wizard, skip through it. Do not add any accounts (Google or Samsung). Do not consent to giving any device data for whatever purposes (they will ask twice; look carefully)
- On the home screen, unlock Dev Options &allow USB Debugging. OEM should already have been unlocked
- Connect device to your pc & in the ZeeToolz folder you extracted, run CMD.exe
- Input adb devices to ensure proper connection
- Input adb install -r MagiskManager-v7.0.0.apk to install MM to your device
- Open MagiskManager & make sure everything is good to go (see attached screenshot)
- If everything is done properly then you will see a superuser tab in the left side-bar, indicating root access
ĐØΠΞ

Thanks for making / working on this man. Running butter smooth on my SM-j737P (J737PVPU2ARJ2.)
note: I had to use an sdcard to store the proper files to be able to flash in twrp. adb sideload nor mtp would not work while in twrp during the initial install.
I used the files below.
Root Files (patched boot image): https://drive.google.com/file/d/1xan3RfRs4x4As7ONxLtW-WXKh_KvjyXY/view
Unbrick Files (stock J737PVPU2ARJ2) : https://androidfilehost.com/?fid=11410932744536992025
Cheers!

kinehumane said:
Thanks for making / working on this man. Running butter smooth on my SM-j737P (J737PVPU2ARJ2.)
note: I had to use an sdcard to store the proper files to be able to flash in twrp. adb sideload nor mtp would not work while in twrp during the initial install.
I used the files below.
Root Files (patched boot image): https://drive.google.com/file/d/1xan3RfRs4x4As7ONxLtW-WXKh_KvjyXY/view
Unbrick Files (stock J737PVPU2ARJ2) : https://androidfilehost.com/?fid=11410932744536992025
Cheers!
Click to expand...
Click to collapse
No problem man. I didnt think to test sideload or mtp as I always use an SDcard (comes in handy lol). It was a tad bit tedious to get the whole process down due to Oreo. That being said, ensure that you have a backup. Editing any part of the system (ie. Build.prop) will result in failure. I installed the Time Zones update & it failed. As far as MagiskSU goes, I like the Modules but prefer SuperSU root. Will see about incorporating it in the near future

This is likely a silly question, but I downloaded and installed flashify, have put the TWRP.img on the SD Card, but for some reason, flashify won't go further than giving me the option of flashing a recovery... one tap and the app is frozen....
So, is there another app that will flash the image, so as to follow the directions in the OP? Flashify doesn't seem to be happening for me. Can't seem to find one that doesn't do a root-check first, refusing to do the deed if root isn't there yet?
Trying from square 1, to the point that I did a total backup, factory reset, and am starting with a reset phone.

pauljulian said:
This is likely a silly question, but I downloaded and installed flashify, have put the TWRP.img on the SD Card, but for some reason, flashify won't go further than giving me the option of flashing a recovery... one tap and the app is frozen....
So, is there another app that will flash the image, so as to follow the directions in the OP? Flashify doesn't seem to be happening for me.
Click to expand...
Click to collapse
I experienced the sluggish behavior as well. Manually go into Magisk Manager > SuperSU & make sure Flashify has been granted root access. I've noticed Magisk is rather slow when it comes to asking or granting root access on some apps. If you cannot get it to flash with Flashify, I'd suggest going with Root Essentials. Its an all-in-one root toolbox with a flashing mechanism
Root Essentials won't work as a secondary flasher bc it requires a custom recovery to be installed beforehand. Flashify will be your best bet so try all possibilities to get it to work

☆KØŁØЯΛĐØ☆ said:
I experienced the sluggish behavior as well. Manually go into Magisk Manager > SuperSU & make sure Flashify has been granted root access. I've noticed Magisk is rather slow when it comes to asking or granting root access on some apps. If you cannot get it to flash with Flashify, I'd suggest going with Root Essentials. Its an all-in-one root toolbox with a flashing mechanism
Click to expand...
Click to collapse
I'll give it a try... thanks... Just trying to follow the instructions to the letter, and I'm laboring under the assumption that the TWRP image has to be on there before going on to the next steps...

pauljulian said:
I'll give it a try... thanks... Just trying to follow the instructions to the letter, and I'm laboring under the assumption that the TWRP image has to be on there before going on to the next steps...
Click to expand...
Click to collapse
I revised my last comment. TWRP is to be flashed after you have rooted with Magisk. The posts are a little offputting due to the order they are in & I apologize for that lol Root with Magisk first & then you can install TWRP

pauljulian said:
I'll give it a try... thanks... Just trying to follow the instructions to the letter, and I'm laboring under the assumption that the TWRP image has to be on there before going on to the next steps...
Click to expand...
Click to collapse
Hmm... Root Essentials tells me it failed to install the image...
If flashify does work, but is just seriously sluggish, I can live with that if it's just a matter of setting it aside until it loads it up, that's cool... just trying to get the TWRP.img on there per instructions... Selecting the Install Recovery Image craps out... I have a copy of that image on both the emulated and the external SD, just to see if it was that... doesn't seem to work.
My understanding from the instructions is that I can't flash this particular TWRP image with Odin...
Does the patched boot image go on first, or what? I've been around here for a while, and have flashed other phones in the past, but this one is a challenge.
---------- Post added at 07:01 PM ---------- Previous post was at 06:58 PM ----------
☆KØŁØЯΛĐØ☆ said:
I revised my last comment. TWRP is to be flashed after you have rooted with Magisk. The posts are a little offputting due to the order they are in & I apologize for that lol Root with Magisk first & then you can install TWRP
Click to expand...
Click to collapse
OK... that makes more sense... I'll do that first, then go on to the other... Thanks, friend.

pauljulian said:
My understanding from the instructions is that I can't flash this particular TWRP image with Odin...
Does the patched boot image go on first, or what? I've been around here for a while, and have flashed other phones in the past, but this one is a challenge.
---------- Post added at 07:01 PM ---------- Previous post was at 06:58 PM ----------
OK... that makes more sense... I'll do that first, then go on to the other... Thanks, friend.
Click to expand...
Click to collapse
When you go to get root, you will need your stock firmware (BL/AP/CP files). My directions are pretty straight forward. Unzip the tools, load up Odin (non-patched), flash BL + AP + CP in their respective slots. Make sure that after you flash the stock, you instantly reboot back into Download Mode. Close the current Odin & open the patched Odin. Load the patched_boot.img.tar I provided to the AP slot & flash. It will reboot with a Verification Failure, thus forcing you to format your device. When your device reboots, skip through Setup Wizard, dont link any Google or Samsung accts. On the home screen, use cmd terminal on your pc to install the MagiskManager.apk. Once sideload, you will see root access & more than likely a toast notification asking you to update Magisk.
Rashr (View attachment de.mkrtchyan.recoverytools.apk) works as a good substitute for Flashify. You just need to move the TWRP.img to the root of your sdcard (/emulated/0/sdcard) & flash it through the Recovery from Storage option. Reboot into TWRP &continue following the instructions I've posted

pauljulian said:
Hmm... Root Essentials tells me it failed to install the image...
If flashify does work, but is just seriously sluggish, I can live with that if it's just a matter of setting it aside until it loads it up, that's cool... just trying to get the TWRP.img on there per instructions... Selecting the Install Recovery Image craps out... I have a copy of that image on both the emulated and the external SD, just to see if it was that... doesn't seem to work.
My understanding from the instructions is that I can't flash this particular TWRP image with Odin...
Does the patched boot image go on first, or what? I've been around here for a while, and have flashed other phones in the past, but this one is a challenge.
---------- Post added at 07:01 PM ---------- Previous post was at 06:58 PM ----------
OK... that makes more sense... I'll do that first, then go on to the other... Thanks, friend.
Click to expand...
Click to collapse
OK... one more silly question... the patched.boot file gets loaded into the AP slot in Odin, and not the BL slot? Reason I'm asking is that after flashing that from the AP slot, the device sits at the Boot logo, and sits there...
As I had tried a few other things, and needed to add my account info to grab the Root Essentials, I just said the hell with it, and re-flashed the stock files.. then without anything other than Dev mode enabled, I booted into download mode and flashed the patched.boot tar file in the AP slot, as directed, and here it sits.
I get this happening, you make it to Albuquerque, and I owe you a few beers...
---------- Post added at 08:09 PM ---------- Previous post was at 08:07 PM ----------
pauljulian said:
OK... one more silly question... the patched.boot file gets loaded into the AP slot in Odin, and not the BL slot? Reason I'm asking is that after flashing that from the AP slot, the device sits at the Boot logo, and sits there...
As I had tried a few other things, and needed to add my account info to grab the Root Essentials, I just said the hell with it, and re-flashed the stock files.. then without anything other than Dev mode enabled, I booted into download mode and flashed the patched.boot tar file in the AP slot, as directed, and here it sits.
I get this happening, you make it to Albuquerque, and I owe you a few beers...
Click to expand...
Click to collapse
OK... missed the immediately into download mode... Once more, with feeling.
When all else fails, go back and read the instructions CAREFULLY... <lol>
Reflashing the stock files and starting over...

pauljulian said:
OK... one more silly question... the patched.boot file gets loaded into the AP slot in Odin, and not the BL slot? Reason I'm asking is that after flashing that from the AP slot, the device sits at the Boot logo, and sits there...
As I had tried a few other things, and needed to add my account info to grab the Root Essentials, I just said the hell with it, and re-flashed the stock files.. then without anything other than Dev mode enabled, I booted into download mode and flashed the patched.boot tar file in the AP slot, as directed, and here it sits.
I get this happening, you make it to Albuquerque, and I owe you a few beers...
---------- Post added at 08:09 PM ---------- Previous post was at 08:07 PM ----------
OK... missed the immediately into download mode... Once more, with feeling.
When all else fails, go back and read the instructions CAREFULLY... <lol>
Reflashing the stock files and starting over...
Click to expand...
Click to collapse
Lol The directions are on point. They're solid. You just have to pay attention ?

Here's the old fart with another question....
After flashing the stock files as instructed, I immediately hit the download mode as soon as the screen went black. Flashed the patched boot as instructed, and, as you stated, it would go immediately into recovery due to verification error.
I wiped the cache and hit factory reset, then reboot.
It's now sitting at the boot logo screen, and has been there for more than 1/2 hour.
Honest! I followed your instructions to the letter, and I recall first boot after rooting taking a while to come up into the system on other devices I've had, but I don't recall first boot taking anywhere this long.
I'm stumped.

pauljulian said:
OK... one more silly question... the patched.boot file gets loaded into the AP slot in Odin, and not the BL slot? Reason I'm asking is that after flashing that from the AP slot, the device sits at the Boot logo, and sits there...
As I had tried a few other things, and needed to add my account info to grab the Root Essentials, I just said the hell with it, and re-flashed the stock files.. then without anything other than Dev mode enabled, I booted into download mode and flashed the patched.boot tar file in the AP slot, as directed, and here it sits.
I get this happening, you make it to Albuquerque, and I owe you a few beers...
---------- Post added at 08:09 PM ---------- Previous post was at 08:07 PM ----------
OK... missed the immediately into download mode... Once more, with feeling.
When all else fails, go back and read the instructions CAREFULLY... <lol>
Reflashing the stock files and starting over...
Click to expand...
Click to collapse
pauljulian said:
Here's the old fart with another question....
After following the instructions, yes, the phone went immediately into recovery mode, after flashing the error message you described.
I went ahead and did the factory reset, and told it to reboot... It's been sitting at the boot logo for about 25 minutes.
Should it take this long for first boot, after flashing the patched.boot.img.tar? I loaded the tar into the AP slot, as instructed. After flashing it, and the screen going to black, hit the download mode immediately... I flashed it, as said, at reboot, it went into recovery after a quick error message... I did factory reset, then rebooted normally.
I really have no idea... I'll let it keep sitting, to see if it finally boots, but this seems like a terribly long time that it's' at the bootscreen.
Click to expand...
Click to collapse
You seem to be rebooting into Recovery an awful lot. You shouldn't be booting into recovery mode at all when attempting to root. Recovery mode only needs entered during either process whenever you attempt to flash TWRP. Luckily for you, I dont have sh¡t to do tonight so I can help you until you get it right lol Shoot me an email at [email protected] & we can get started. I dont want to clutter up this feed with a revised how-to guide lol

Other Variants
I tried on my j737p ( rooting worked like a charm ) however your patched boot image had to be substituted in order for my j737 variant to go further than a boot loop.
for twrp the flash of the recovery image went over fine and booted into twrp nicely. however i flashed those 3 files one at a time and all 3 at once both in order each time a few different times to verify. regardless what i do it sends me into a boot loop upon leaving twrp.
do you have any recommendations on what to modify in your procedure for my variant?
my specs are as follows:
Model - SM-J737P
ROM - J737PVPS2ASA1
Android - 8.0
SDK - 26
Kernel - 4.4.13-14521356 [email protected] gcc 4.9.x 20150123
Processsor - armv8l
I have 2 of the same j737p phones so im using one as my test subject before i move each step to my daily j737p.
I am comfortable with beta experimentation within reason.
on a side note - If anyone has my variant and would like the root to work I can send you the patched boot image that I used to get the root to take and let you boot into android successfully.

fsceo said:
I tried on my j737p ( rooting worked like a charm ) however your patched boot image had to be substituted in order for my j737 variant to go further than a boot loop.
for twrp the flash of the recovery image went over fine and booted into twrp nicely. however i flashed those 3 files one at a time and all 3 at once both in order each time a few different times to verify. regardless what i do it sends me into a boot loop upon leaving twrp.
do you have any recommendations on what to modify in your procedure for my variant?
my specs are as follows:
Model - SM-J737P
ROM - J737PVPS2ASA1
Android - 8.0
SDK - 26
Kernel - 4.4.13-14521356 [email protected] gcc 4.9.x 20150123
Processsor - armv8l
I have 2 of the same j737p phones so im using one as my test subject before i move each step to my daily j737p.
I am comfortable with beta experimentation within reason.
on a side note - If anyone has my variant and would like the root to work I can send you the patched boot image that I used to get the root to take and let you boot into android successfully.
Click to expand...
Click to collapse
I have since revised my instructions for root, starting that my guide is very device specific & you will have to tweak instructions in order to accommodate your version.
As far as TWRP goes, did you boot into TWRP twice? Once for the initial install to format the /data partition & the second to secure TWRP along with flashing the files? You need to do it simultaneously & in order otherwise it won't work

It's a happenin' thang!!!!
Many thanks to Killer for all the help! Decent person stayed up with me troubleshooting until 6:30 this morning... It's working!!!!
(now, if I can find the damned SIM card that bounced off my desk into the carpeting, I'll have basically a laptop replacement! (well, for a lot of things, that is... <chuckle>)

pauljulian said:
It's a happenin' thang!!!!
Many thanks to Killer for all the help! Decent person stayed up with me troubleshooting until 6:30 this morning... It's working!!!!
(now, if I can find the damned SIM card that bounced off my desk into the carpeting, I'll have basically a laptop replacement! (well, for a lot of things, that is... <chuckle>)
Click to expand...
Click to collapse
Not a problem buddy. Was fun & if you have any more questions, you have my contact info

fsceo said:
I tried on my j737p ( rooting worked like a charm ) however your patched boot image had to be substituted in order for my j737 variant to go further than a boot loop.
for twrp the flash of the recovery image went over fine and booted into twrp nicely. however i flashed those 3 files one at a time and all 3 at once both in order each time a few different times to verify. regardless what i do it sends me into a boot loop upon leaving twrp.
do you have any recommendations on what to modify in your procedure for my variant?
my specs are as follows:
Model - SM-J737P
ROM - J737PVPS2ASA1
Android - 8.0
SDK - 26
Kernel - 4.4.13-14521356 [email protected] gcc 4.9.x 20150123
Processsor - armv8l
I have 2 of the same j737p phones so im using one as my test subject before i move each step to my daily j737p.
I am comfortable with beta experimentation within reason.
on a side note - If anyone has my variant and would like the root to work I can send you the patched boot image that I used to get the root to take and let you boot into android successfully.
Click to expand...
Click to collapse
Sent you a pm, but having trouble rooting the same variant

Related

[Q] Problem getting past the Recovery Screen in recovery mode

Phone Details
Motorola Atrix 4G AT&T (bought around June 2011 Time frame)
System Version
4.5.91.MB860.ATT.en.US
Model Number
MB860
Android Version
2.34
Baseband Version
N_01.77.30P
Webtop Version
WT-1.2.0-110
Kernel Version
[email protected] #2
Build Number
4.5.91
I am absolutely new to this Android ROM installs on the phones. Though I decided to install this ROM I absolutely didn’t’ have any idea how to proceed. As a beginner I started doing the following in order.
Download and Keep the CM7 ROM
1. Downloaded Ba2F.zip to my laptop
2. Downloaded and Installed the Motorola USB drivers MotoHelper_2.0.53_Driver_5.2.0.EXE
3. Connect the Atrix and set the USB option on the phone to “USB Mass Storage”
4. Copy both BaTF.zip as well as the Extracted one to Phone internal storage as well as the Ext-SDcard on the phone
Download ROM Manager and Titanium Backup
1. Downloaded both from Android Market (ROM Manager Pro and Titanium Backup Free Version)
2. Both Apps won’t open because I had not ROOTED the phone
Root the Phone
1. I used “Pete's Motorola Root Tools.EXE” file to ROOT the phone
2. Followed step by step as mentioned here http://www.androidauthority.com/how-to-root-motorola-atrix-4g-35233/
Flash ClockworkMod Recovery
1. I used ROM Manager to do this as when you try to do anything in ROM manager it prompts to do this. The version of this is 5.0.2.0 ( I am not sure what is this for why we have to do this)
Unlocking the Bootloader
1. What I learned is, to unlock the bootloader, we have to first flash the phone with the SBF file
a. Installed RSDLite5.3.1.msi
b. Loaded the file 4547-fix-try2.sbf (Downloaded from http://forum.xda-developers.com/showthread.php?t=1136261)
c. Boot the phone with Power+volume UPPER key pressed till "Starting RSD protocol support" comes up
d. Connect to the Laptop and Hit Start button in RSD Lite Program
e. It Did Throw an error saying “FAIL” after showing the following message
i. Failed to boot: error 0x1000'( not word for word). There will also be a list of boot options like Fastboot, RSD, Recovery, etc. And it says Starting Fastboot Protocol
2. Then comes unlocking the phone
a. Though I had the previous error message, it still had the Fastboot Protocol loaded
b. I went to the FASTBOOT folder in command prompt of my laptop executed the following to unlock the phone which worked perfectly as I see the “Unlock” on the left hand corner when phone boots
c. fastboot oem unlock (it gave me the code) then I used the code to unlock
d. fastboot oem unlock #######
e. fastboot reboot
3. Installing the recovery IMG
a. I had downloaded the Recovery IMG file (recovery-atrix5.img) from http://forum.xda-developers.com/showthread.php?t=1204500
b. Booted the phone into Fastboot mode (turn off phone, hold power and volume down key until 'fastboot' appears then use volume up to select so it says 'starting fastboot protocol support').
c. From the CMD promnt and FASTBOOT directory I used fastboot erase recovery
d. Then I executed fastboot flash recovery recovery-atrix5.img (Note: I didn’t rename the file to recovery as suggested by some people)
e. Then gave fastboot reboot to restart.
4. Booting into Recovery mode (This is where I have the problem)
a. The phone is not booting into recovery it’s not going past the Android and yellow Triangle screen
b. I re-flashed the phone same SBF file (this time it was a success showed in the RSD Lite Program), re-installed the same IMG file after renaming to recovery.img
c. Also tried with a different IMG from the same link (recovery-blue-atrix5.img) but no luck
d. Also deleted the file install-recovery.sh from ./etc/ folder (bought the app root manager to delete the file) and then push the recovery.img, no luck
e. Some people said to TAP the bottom right corner while on that screen, did that but nothing is happening
f. Then I saw a note to press both the Volume Keys at the same time, this works but in this mode the cursor (I mean the selection) on the phone doesn’t go to the First TWO (i and iii) shown below, it allows me to select any of the last FOUR (v, vi, vii, viii).
i. Android System Recovery <3e>
ii. <EMPTY LINE >
iii. Android System Recovery utility
iv. <EMPTY LINE >
v. Reboot System now
vi. Apply update from sdcard
vii. Wipe data/factory reset
viii. Wipe cache partition
g. Using the above option I did factory reset but sill no results.
5. Current condition of the phone
a. It boots in unlock mode and I can do all the daily tasks. But I want to install the CM7 ROM that’s my requirement
PLEASE HELP HELP HELP

First of all, I applaud your effort in giving the a very comprehensive description of your issue.
Second, it seems you are having issues with installing a custom recovery because the recovery you're describing is still the stock recovery. I'll look around and see if I can find something that might help.
jhakash said:
4. Booting into Recovery mode (This is where I have the problem)
a. It boots in unlock mode and I can do all the daily tasks. But I want to install the CM7 ROM that’s my requirement
PLEASE HELP HELP HELP
Click to expand...
Click to collapse
---------- Post added at 11:31 AM ---------- Previous post was at 11:28 AM ----------
Have you tried re-installing the CWM from RomManager through RomManager? And then boot into recovery from within the app?
---------- Post added at 11:40 AM ---------- Previous post was at 11:31 AM ----------
EDIT: This might seem trivial, but is "USB Debugging" turned on?

You are the Man, I just flashed the same CWM 5.0.2.0 and i am in the recovery mode. This gave me an error when i did last time hence i didn't try again.
Thanks a bunch

Glad I can help, also, I think it's recommended to use the RomManager recovery for CM7 so good thing it worked.
jhakash said:
You are the Man, I just flashed the same CWM 5.0.2.0 and i am in the recovery mode. This gave me an error when i did last time hence i didn't try again.
Thanks a bunch
Click to expand...
Click to collapse

Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?

If you downloaded the CWM zip file for the romracer recovery and as long as RomManager's recovery is working then, yes, you can.
jhakash said:
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
Click to expand...
Click to collapse

jhakash said:
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
Click to expand...
Click to collapse
See post#2 from romracer's thread. Read the Miscellaneous part. Probably need to get rid of, or backup, install-recovery.sh.

He has mentioned he already did that. In his OP, under the steps he took look at "Booting into Recovery Mode" - 4.d, he says he removed it.
Maybe he's not doing it in the right order? Do you happen to know which should be done first as far as installing recovery and removing said file?
ghost_og said:
See post#2 from romracer's thread. Read the Miscellaneous part. Probably need to get rid of, or backup, install-recovery.sh.
Click to expand...
Click to collapse

live4nyy said:
He has mentioned he already did that. In his OP, under the steps he took look at "Booting into Recovery Mode" - 4.d, he says he removed it.
Maybe he's not doing it in the right order? Do you happen to know which should be done first as far as installing recovery and removing said file?
Click to expand...
Click to collapse
Woops, I should have read more carefully. It's best to remove the file first and then flash the recovery.img, or else the script will install the stock recovery on boot. That would make stock recovery the current one on the phone at the time of the script getting deleted.
I would double check and make sure /system/etc does not have install-recovery.sh. If it is not there, then proceed to the fastboot steps and reflash the recovery.img again. It should stick this time.

@Ghost, yes i deleted the file multiple times however i didn't find the /system/etc folder on the Internal Storage. however I found the install-recovery.sh file under /etc folder. The thing i observed that whether i flash it with a new CWM or not if i reboot the phone then it was created by itself.

@Live4nyy, Thanks for your suggestion, I could able to install CM7 now and it looks awesome good so far, but looks like i need to install Google Apps separately to access the APP market, am I right?
The only thing that happens to me is, it allowed me to go to Recovery only ONCE after i Flashed it thru ROM Manager, if i exit out of recovery without doing anything then next time tried to go to Recovery, it will struck at the same old Android screen and i had to flash it again. But Many thanks for suggesting to flash it thru ROM Manager.
Now with CM7, under ROM Manager (I guess this comes default with CM7) I see there is no version listed under "Flash Clockworkmod Recovery" and it says i must have to install it in-order to Flash and restore ROMs, do i need to do that? I can go to Recovery mode after reboot without any issues. Please Advise.
------
Jhakash

jhakash said:
@Ghost, yes i deleted the file multiple times however i didn't find the /system/etc folder on the Internal Storage. however I found the install-recovery.sh file under /etc folder. The thing i observed that whether i flash it with a new CWM or not if i reboot the phone then it was created by itself.
Click to expand...
Click to collapse
I just checked out my girlfriend's stock, locked, unrooted Atrix and she actually has install-recovery.sh in both /etc and /system/etc. Her file manager does not alphabetize anything in either folder, so I almost overlooked the second one.
If you're already on CM7, then you probably won't need to worry anymore. They have an entirely different set of start up scripts in that folder. Welcome to the community!

At this point I do not know enough to help you any further with this issue. All I knew about is the file that needs to be removed that @ghost_og has mentioned. But if you can flash it from RomManager and access CWM from there as well then I guess that's a good enough workaround for now.
Does anyone else have any idea why the stock recovery cannot be removed?
jhakash said:
@Live4nyy, Thanks for your suggestion, I could able to install CM7 now and it looks awesome good so far, but looks like i need to install Google Apps separately to access the APP market, am I right?
The only thing that happens to me is, it allowed me to go to Recovery only ONCE after i Flashed it thru ROM Manager, if i exit out of recovery without doing anything then next time tried to go to Recovery, it will struck at the same old Android screen and i had to flash it again. But Many thanks for suggesting to flash it thru ROM Manager.
Now with CM7, under ROM Manager (I guess this comes default with CM7) I see there is no version listed under "Flash Clockworkmod Recovery" and it says i must have to install it in-order to Flash and restore ROMs, do i need to do that? I can go to Recovery mode after reboot without any issues. Please Advise.
------
Jhakash
Click to expand...
Click to collapse

I am good to go now, everything seems to be functioning well after flashing CM7 ROM, no more recovery issues, and the Stock recovery is gone now.
Appreciate for all the info you guys provided, it helped a lot. Have a great day and Merry Christmas.
Regards
Jhakash

Nabi 2 TWRP help

My brother has a Nabi 2 which was rooted, and we recently received an update from Jelly Bean to Kit Kat. We (more like I) tried to do this without unrooting, and it ended up boot looping for around 4 hours before I intervened. I downloaded the latest stock ROM I could find, and I went into TWRP to flash it. Every single time, it says "Unable to flash zip '/external_sdcard/246stock.zip', then tells me that there is no operating system installed. I tried upgrading TWRP, and got 2.8. Touch was very close to unresponsive. I also tried 2.7.1.0, and 2.7.0.0, and also every other version I could find. Every single version either couldn't flash it, couldn't mount anything, or touch was unresponsive. I downloaded all the recoveries from xda's Nabi 2 page. None of them work. Is there anything I can try to fix this?

wither719 said:
My brother has a Nabi 2 which was rooted, and we recently received an update from Jelly Bean to Kit Kat. We (more like I) tried to do this without unrooting, and it ended up boot looping for around 4 hours before I intervened. I downloaded the latest stock ROM I could find, and I went into TWRP to flash it. Every single time, it says "Unable to flash zip '/external_sdcard/246stock.zip', then tells me that there is no operating system installed. I tried upgrading TWRP, and got 2.8. Touch was very close to unresponsive. I also tried 2.7.1.0, and 2.7.0.0, and also every other version I could find. Every single version either couldn't flash it, couldn't mount anything, or touch was unresponsive. I downloaded all the recoveries from xda's Nabi 2 page. None of them work. Is there anything I can try to fix this?
Click to expand...
Click to collapse
You don't "install" that zip, you "restore" it.
Use TWRP 2.7.0
Download this 3.0.13 stock ZIP
Use an external SDcard and make a backup of just "boot"(this is a setup for next step)
Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 3.0.13 stock you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 3.0.13 ROM.
- Download this 3.0.13 bootloader
- Copy the zip to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Go to "restore tab", and find the backup under the "yourfolder" you made and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP "install tab", find the bootloader zip you downloaded and install it.
- Reboot

aicjofs said:
You don't "install" that zip, you "restore" it.
Use TWRP 2.7.0
Download this 3.0.13 stock ZIP
Use an external SDcard and make a backup of just "boot"(this is a setup for next step)
Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 3.0.13 stock you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 3.0.13 ROM.
- Download this 3.0.13 bootloader
- Copy the zip to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Go to "restore tab", and find the backup under the "yourfolder" you made and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP "install tab", find the bootloader zip you downloaded and install it.
- Reboot
Click to expand...
Click to collapse
ok, im in BIG trouble with my daughter... Yep, I managed to brick her Nabi 2 following this tutorial and I dont know really know where I went wrong. But now when the Nabi 2 is powered on, all I see is the nabi logo, but no OS...or TWRP!... eeek!
I had been trying for days to get a stable TWRP on and Gapps, I did get TWRP v2.3.3.0 up and running at one point, but no Gapps installed and no SuperSU to be found, it was as if it wasnt rooted at all. (even after reinstalling both within TWRP). Then of course i found a thread that said Gapps didnt work on nabi 2 version 2.1...!
I do have a TWRP backup folder saved but i dont seem to have any way to get it back onto the Nabi 2... as its no longer detected in windows like it was before..? (despite the ding sound windows makes when plugged in ?).
I can only get to the 1st bootmenu (holding Vol+ and Power ok. Selecting any options results in little (or nothing) happening... i.e. when selected;
Boot Normally - nothing happens, nabi logo only. And if i leave it too long, it freezes here and i have to reboot.
Fastboot Protocol - with usb connected to pc, i do get to the Bootloader menu with, Bootloader, Continue, Reboot-bootloader, Reboot and Poweroff , options. The Pc 'dings' to indicate detection, but is not detected by adb ?
Recovery Kernel - nothing happens, nabi logo only.
Forced Recovery - screen goes black, then nothing follows.
on Fastboot Protocol menu, if i select the options;
Bootloader - without touching anything, pc dings to indicate some connection...?
Continue - if selected, i hear windows drop whatever connection it had previous..?
Reboot-bootloader - nothing happens, nabi logo only.
Reboot - reboots, then nabi logo only.
Poweroff - nabi 2 shuts down.
As it stands , all i can access are these options above, but i dont seem to have a way of getting windows to communicate over the usb cable...? that said, with pdanet running, it does detect the nabi 2, but of course it cant talk to it as I cant get to pdanet on the nabi 2... just gives some weird error that im using wrong adb , or it just cant connect to the nabi.
Tried using Nabilab v2, but device is not detected...?
...so i would be most grateful if some nabi 2 guru could assist with any possible resurrection, otherwise I will remain "the worst daddy ever"...ugh!
cheers in advance

the_xlr8r said:
ok, im in BIG trouble with my daughter... Yep, I managed to brick her Nabi 2 following this tutorial and I dont know really know where I went wrong. But now when the Nabi 2 is powered on, all I see is the nabi logo, but no OS...or TWRP!... eeek!
I had been trying for days to get a stable TWRP on and Gapps, I did get TWRP v2.3.3.0 up and running at one point, but no Gapps installed and no SuperSU to be found, it was as if it wasnt rooted at all. (even after reinstalling both within TWRP). Then of course i found a thread that said Gapps didnt work on nabi 2 version 2.1...!
I do have a TWRP backup folder saved but i dont seem to have any way to get it back onto the Nabi 2... as its no longer detected in windows like it was before..? (despite the ding sound windows makes when plugged in ?).
I can only get to the 1st bootmenu (holding Vol+ and Power ok. Selecting any options results in little (or nothing) happening... i.e. when selected;
Boot Normally - nothing happens, nabi logo only. And if i leave it too long, it freezes here and i have to reboot.
Fastboot Protocol - with usb connected to pc, i do get to the Bootloader menu with, Bootloader, Continue, Reboot-bootloader, Reboot and Poweroff , options. The Pc 'dings' to indicate detection, but is not detected by adb ?
Recovery Kernel - nothing happens, nabi logo only.
Forced Recovery - screen goes black, then nothing follows.
on Fastboot Protocol menu, if i select the options;
Bootloader - without touching anything, pc dings to indicate some connection...?
Continue - if selected, i hear windows drop whatever connection it had previous..?
Reboot-bootloader - nothing happens, nabi logo only.
Reboot - reboots, then nabi logo only.
Poweroff - nabi 2 shuts down.
As it stands , all i can access are these options above, but i dont seem to have a way of getting windows to communicate over the usb cable...? that said, with pdanet running, it does detect the nabi 2, but of course it cant talk to it as I cant get to pdanet on the nabi 2... just gives some weird error that im using wrong adb , or it just cant connect to the nabi.
Tried using Nabilab v2, but device is not detected...?
...so i would be most grateful if some nabi 2 guru could assist with any possible resurrection, otherwise I will remain "the worst daddy ever"...ugh!
cheers in advance
Click to expand...
Click to collapse
Wow I havent been on here in ages, got an email about your quote though.
I have forgotten so much about these Nabis over the last decade?! So how did you get to the non-booting part? You were able to complete the steps above all successfully? or did it fail at some part?
If you successfully flashed 3.0.13 bootloader with install in TWRP then I don't think you will be able to boot the TWRP you had on the device. That would be my guess at this point why you can't get to recovery.
[NABI] General Information
Fuhu Nabi General information 1. Introduction It was only recently that the Nabi2 got it's own forum. This device has been out a couple of years so the information you may be looking for is spread all over XDA. The largest single chunk of...
forum.xda-developers.com
Read the above. You are pretty much stuck in having to use fastboot.(The driver must be installed if you keep hearing the ding). You will need a fastboot.exe if you don't have one. Search minimal ADB and fastboot. I'd download TWRP 2.8.7 and try to use section 7 to get it on device i.e "fastboot flash recovery recovery.img"
If you unsuccessfully flashed bootloader then you need to use TWRP 2.8.5 Files should be in that thread also or my AHF https://androidfilehost.com/?w=files&flid=41987.
Ill check back later

aicjofs said:
Wow I havent been on here in ages, got an email about your quote though.
I have forgotten so much about these Nabis over the last decade?! So how did you get to the non-booting part? You were able to complete the steps above all successfully? or did it fail at some part?
If you successfully flashed 3.0.13 bootloader with install in TWRP then I don't think you will be able to boot the TWRP you had on the device. That would be my guess at this point why you can't get to recovery.
[NABI] General Information
Fuhu Nabi General information 1. Introduction It was only recently that the Nabi2 got it's own forum. This device has been out a couple of years so the information you may be looking for is spread all over XDA. The largest single chunk of...
forum.xda-developers.com
Read the above. You are pretty much stuck in having to use fastboot.(The driver must be installed if you keep hearing the ding). You will need a fastboot.exe if you don't have one. Search minimal ADB and fastboot. I'd download TWRP 2.8.7 and try to use section 7 to get it on device i.e "fastboot flash recovery recovery.img"
If you unsuccessfully flashed bootloader then you need to use TWRP 2.8.5 Files should be in that thread also or my AHF https://androidfilehost.com/?w=files&flid=41987.
Ill check back later
Click to expand...
Click to collapse
Hi, thanks for getting back ...
Q. So how did you get to the non-booting part? You were able to complete the steps above all successfully? or did it fail at some part?
A. yes i followed the tut but once i rebooted that was the end and where my big problems began.
Q. If you successfully flashed 3.0.13 bootloader with install in TWRP then I don't think you will be able to boot the TWRP you had on the device. That would be my guess at this point why you can't get to recovery.
A. Yes, using TWRP i installed 3.013 bootloader.
Q. You are pretty much stuck in having to use fastboot. (The driver must be installed if you keep hearing the ding). You will need a fastboot.exe if you don't have one. Search minimal ADB and fastboot.
A. This may be the issue, i may be using older version of adb and fastboot. I already had minimal adb stored away, so i experimented by copying the adb files over to my NabiLabFull folder, this time it was green (detected) ... sort of...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ill have a read at the links you provided and will report back soon, thanks.

ok... getting somwehere but not where i expected....
i tried to install the 2 x TWRP versions you mentioned but it wouldnt load into either. So i reverted back to trying 2.3.3.0 and bingo , im in... but shouldnt 2.8.5 or 2.8.7 have worked since Im now showing Navi version as 3.0.13.. (was previously on 2.1.9) ?
im sitting at the TWRP 2.3.3.0 menu now , and still have Nabilab running but am afraid to do anything next lol.... where should i proceed to, from here ? Should I be installing any particular version of Root and Gapps now that im into TWRP 2.3.3.0 (or even try to update TWRP beforehand ?
PS. I am using a UK nabi 2 , in case that makes any difference to files im downloading to it ?
cheers

Im not at a location where I can look at the Nabilab script but as I recall the script is pulling it from build.prop on the system partition. This would indicate to me that the system partition flashed, and so likely the addon and boot. Also the fact that you can't boot another TWRP besides 2.3.3, and the normal boot hanging at the logo leads me to believe that the bootloader was not updated.
Again I'm trying to remember here....but as I recall the bootloader for the Nabi is passing a commandline to the kernel. You have a kernel in the 3.0.x ROM and an identical kernel in TWRP 2.8.7. The fact that neither boot would mean to me the bootloader is original and passing the old commandline to a newer kernel.
You have to get things in sync. The bootloader and the boot.img(kernel+ramdisk) have to match each other. The way that makes the most sense is to install the bootloader3013 zip through TWRP. You already tried that obviously and that's how you got here.
1) You could try the bootloader install inside TWRP again, seems like you can recover if it fails now. Of course if it works then 2.3.3 TWRP should no longer work(which is what I thought happened and why you couldn't boot TWRP initially) so you'd have to try the 2.8.7 at that point.
2) Since the bootloader is original(or Jellybean-ish) you could restore your backup and regroup.
When I get to a place I can look at the install script for the bootloader maybe I can jog my memory. I thought it just dd to mmcblock0

ok. thanks.
so i make no more mistakes, ill check I have all the correct files i need with you first...
I have saved to external sdcard, KK3013bootloader.zip containing;
META-INF
android-info.txt
blob
I have also saved to external sdcard, 3013stock.zip (unzipped)
I have also saved to external sdcard, some old Gapps.zip version (no idea if recent or not) ?
I have also saved to external sdcard, some old root.zip version, again, not sure if correct ?
I think I'm breaking it when i get to here...
1) You could try the bootloader install inside TWRP again, seems like you can recover if it fails now. Of course if it works then 2.3.3 TWRP should no longer work(which is what I thought happened and why you couldn't boot TWRP initially) so you'd have to try the 2.8.7 at that point.
....So, if im in TWRP 2330 now, and I install KK3013Bootloader.zip, it will then no longer boot to TRWP ... is that correct? If so, how then do i get TWRP 285 or 287 working ?
....think i'm getting a smidge lost at this bit lol
[update] - cannot install anything in TRWP 2330 as its not recognizing my 64gb sdcard (formatted to fat32) ... does it have to be a certain formatted type FAT/FAT32/EXT12/3/4 or other ?
Also, i couldnt find a working download link for anyone's scripts... many thanks

the_xlr8r said:
I think I'm breaking it when i get to here...
1) You could try the bootloader install inside TWRP again, seems like you can recover if it fails now. Of course if it works then 2.3.3 TWRP should no longer work(which is what I thought happened and why you couldn't boot TWRP initially) so you'd have to try the 2.8.7 at that point.
So, if im in TWRP 2330 now, and I install KK3013Bootloader.zip, it will then no longer boot to TRWP ? is that correct. If so, how then do i get TWRP 285 or 287 working ?
[update] - cannot install anything in TRWP 2330 as its not recognizing my 64gb sdcard (formatted to fat32) ... does it have to be a certain formatted type FAT/FAT32/EXT12/3/4 or other ?
Click to expand...
Click to collapse
For #1 You install the bootloader zip. Swipe install then reboot. It won't do anything at first because it installs the "blob" (which is the bootloader) to the staging partition. Reboots for 15 seconds and installs the blob. The only way at that point to get a newer TWRP is by booting bootloader to fastboot, and then fastboot flash the newer TWRP on to it.
No it should recognize fat32. There was something about storage being realigned between versions too. You could always use adb too I guess.
adb push bootloaderXXXX.zip /data/media ?
The end of this thread may be usefully too
[RECOVERY][NABI2] TWRP 2.3.3.0, 2.8.5.0 testing
This is an update to the TWRP recovery for the Nabi 2. At this point this recovery is still considered in testing. The normal disclaimers apply. Have a good backup moved to your computer from the previous recovery. Before starting this...
forum.xda-developers.com
The original TWRP posts
Nabi 2 Root and Gapps Install
#include /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features...
forum.xda-developers.com
Nabi 2 Root and Gapps Install
#include /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features...
forum.xda-developers.com

thanks, am i downloading the correct TWRP zip ?
TWRP 2.8.5.0 Released
TWRP 2.8.5.0 is out now for all currently supported devices.
twrp.me
Which version Gapps should i be using ?
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org

the_xlr8r said:
thanks, am i downloading the correct TWRP zip ?
TWRP 2.8.5.0 Released
TWRP 2.8.5.0 is out now for all currently supported devices.
twrp.me
Which version Gapps should i be using ?
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
Click to expand...
Click to collapse
No download the TWRP in one of the last 2 links I sent. First is 2.8.5, and other is 2.8.7
I thought on KitKat Fuhu actually has Gapps? You will let Playstore update it to whatever version they stopped with for KitKat support.
There is always NabiLabGUI2015 https://drive.google.com/file/d/1x_4btZE2VzYWJ_aag9U20ubIGY9NXjcN/view?usp=sharing
I never really finished the project but it might be easier as it has all the recoveries already in it. Stay away from NVflash/APX stuff for now.

ok , sorry i already went ahead and installed bootloader3103
then ADB'd on twrp-recovery-KKNV7AUS-287.zip
I can now get TWRP 2.9.7.0 loaded up, but still no OS booting once i have rebooted the nabi2...
maybe the OS is missing ..? how do i reinstall it ? (i tried doing a restore by using the old TWRP backup i had from the start , by pasting in the 3013stock files) but that didnt work.
....still stuck, but getting closer

the_xlr8r said:
maybe the OS is missing ..? how do i reinstall it ? (i tried doing a restore by using the old TWRP backup i had from the start , by pasting in the 3013stock files) but that didnt work.
....still stuck, but getting closer
Click to expand...
Click to collapse
No I think we are good, the plan was for you to flash bootloader to proper, and that seems to be the case.
It might not be missing the OS, it might need data/media wiped(factory reset). Of course the tablet is completely wiped during that, don't know if the daughter had stuff on there.
Either way it doesn't hurt to try and restore it again. When you say pasting the 3013 restore files, you mean in the folder with your backup? Over top the files or just a folder in the same folder as the backup?
The fact that Nabilab says 3.0.13 makes me think the system files were restored and not missing. You did all this through NabiLab or TWRP?

hi , tried every way i could
yes, i copied and pasted the 3013stock files over the top of the old backup and tried to restore, still didnt boot to OS.
tried your NabiLab2015 , UK menu didnt open so i just used the US menu.
tried to follow step.2 "Flash Full" , seemed to start ok , but then..... this happened...
Note: using NabiLab2015, I skipped using step 1. to download stock 3013, as it wouldnt do it, so i copied the 3013.zip i had downloaded earlier into this folder. which seemed to allow step 2 to work...
whats best option to use now that it failed at 30% install ? thanks

the_xlr8r said:
hi , tried every way i could
yes, i copied and pasted the 3013stock files over the top of the old backup and tried to restore, still didnt boot to OS.
tried your NabiLab2015 , UK menu didnt open so i just used the US menu.
tried to follow step.2 "Flash Full" , seemed to start ok , but then..... this happened...
Note: using NabiLab2015, I skipped using step 1. to download stock 3013, as it wouldnt do it, so i copied the 3013.zip i had downloaded earlier into this folder. which seemed to allow step 2 to work...
whats best option to use now that it failed at 30% install ? thanks
View attachment 5718161
Click to expand...
Click to collapse
Looks like the ADB connection reset. This step is copying the files to the tablet to data/media. It failed at addon. Either cable to computer had a glitch or maybe data/media(internal storage) is full. You can retry again, it didn't flash anything to device at all.
Maybe in TWRP, go to advanced, terminal and type bdf? See if filesystem looks ok. Seems like a cable issue right now though

[UPDATE]
thankyou sir for all your help.
after another try on a Flash Full , everything was installed and it rebooted and updated.
i'm so glad your email still worked after 10 years of not looking at this nabi stuff , otherwise this nabi of mine would be in the bin before now.. lol.... @)
..couple of things, now that its on android 4.4 etc , is it safe to perform any further updates ?
Its running as a US version now, will that affect anything with me being in the UK ?
still not able to get external sdcard detected in TWRP... any ideas ?
many thanks

the_xlr8r said:
[UPDATE]
thankyou sir for all your help.
after another try on a Flash Full , everything was installed and it rebooted and updated.
i'm so glad your email still worked after 10 years of not looking at this nabi stuff , otherwise this nabi of mine would be in the bin before now.. lol.... @)
one last thing, now that its on android 4.4 etc , is it safe to perform any further updates ?
Click to expand...
Click to collapse
No problem, havent thought about Nabi's in probably 2 years. Some of my favorite memories were helping people on Christmas Day, or this Dad from Brazil on his son's birthday, Mom from Italy etc, etc and imagining the kids didn't even know all the panic haha.
You are pretty much done at 4.4. Really no OS level updates to do. Fuhu never did anything else, the source code they gave us was worthless for kernel building, and honestly this Tegra chipset was at it end anyway. Like I said earlier Google play services will update to the latest for the kitkat version, and that will be it. Apps that still support Android this old will have updates of course.
EDIT: Its funny about NabiLabGUI2015. I get emails about my google drive link because link is so old and I have to manually share it the zip for it. I forgot that it would have been really useful if I ever finished it.

most of the trouble I was facing was working links on the forum, hardly any worked and I spent days searching.
even searching for NabiLab2015 proved impossible. Only for you providing a new link, i would never have found it... maybe you could update some old posts with fresh links, and that will make some old-timers like myself, feel young again trying this stuff lol.
but andyways, thank you again so much for your help. theres not many out there in this day and age, that would have bothered... so i salute you sir!
kind regards
stay safe
ps. my daughter says Im the best dad in the world again ... I told her the wizard on the tinterweb fixed it using some of Gandalf's magic....

[HOW TO] remove device encryption and get superSU

The below steps are only part of the solution since there are a couple of prerequisites (with solutions for those already on these forums and MIUI sites). I'm afraid since it's getting late here, I cannot provide detailed steps for everything, I'm assuming you are like me and only got so far, so already know what you're doing
I'm not responsible for hard bricks, however if any steps I've entered are entirely wrong, please do let me know. I'm only trying to help the community out.
What you need:
Unlocked bootloader, sadly you will have to wait for the permission from them (I don't like this process either)
Decent knowledge of TWRP menu system
no care for completely wiping the SD Card contents - please make a backup of pictures or anything else you want
adb and fastboot both working and recognising the phone properly
Gemini (Xiaomi Mi 5) TWRP - https://drive.google.com/file/d/0B95J_je8rRN0V1Y2T2o0Mlh2R1E/view?usp=docslist_api **Thanks to Nesquix for posting the link to this** it is in Chinese and the theme changing solution did not work for me - but this doesn't really matter if you know your way around TWRP
Latest SuperSU - https://download.chainfire.eu/924/SuperSU/BETA-SuperSU-v2.68-20160228150503.zip
Latest DEV Fastboot ROM - I cannot post the link however it can be found by searching for "mi 5 fastboot developer rom" on Google and selecting the link going to en.miui.com
STEPS to take:
Extract the contents of the fastboot ROM to a location of your choice. The only file you need is this one: \...\...\images\system.img (if someone can upload separately, I'll link in OP)
Place both the system.img from the fastboot ROM and twrp img file in the location of your fastboot folder
Enter fastboot mode (bootloader) on the Mi 5 via Power off --> volume down + power on --> let go once you see the MI logo
Check your device can be seen via the command, fastboot devices --> ENTER
Now input the following command, fastboot flash recovery twrp-mi5.img --> ENTER
Now enter in to recovery via volume up + power on - There appears to be a bug with TWRP whereby on some boots, touch isn't responsive, just keep booting back till it works (it will eventually)
Swipe on the first screen to enter the menu, tap the top right icon for wiping data, then the bottom right icon, you will see a text box with a warning - enter yes, then tick to fully wipe the SD card
Power off again, and reboot back to fastboot mode (bootloader)
Once there, input this command, fastboot flash system system.img --> ENTER
Once the system is flashed, input this command, fastboot reboot
Skip past initial steps for speed place the superSU zip on the root of the SD Card and then reboot back to recovery again
Flash SuperSU in recovery (top left option, find your zip, flash it
Reboot system
PROFIT - you now have an unencrypted system with working superSU and apps like Adaway work flawlessly - HAVE FUN and don't forget to say thanks if I did actually help you
Interesting notes.....
I'm not sure about anyone else, but I found web browsing to be alarmingly slow with no good explanation, the above steps completely resolved this
Google is now a search option in the default browser (it wasn't before!!)
Call it placebo all you want, but the phone really does seem a lot faster now.
Last but not least, I'm fairly certain to update to newer versions, you only have to extract same system.img from future fastboot ROM zips, and flash this on it's own to update the system.

To get the multilingual functionality of TWRP working, copy this file in TWRP\theme
You can also change the theme color in the advanced settings .
https://drive.google.com/file/d/0B95J_je8rRN0N19DLXdFYXV4NW8/view?usp=docslist_api

nesquix said:
To get the multilingual functionality of TWRP working, copy this file in TWRP\theme
You can also change the theme color in the advanced settings .
https://drive.google.com/file/d/0B95J_je8rRN0N19DLXdFYXV4NW8/view?usp=docslist_api
Click to expand...
Click to collapse
I think we dont need to copy TWRP theme. You can set language in first welcome screen or in Settings menu, and tap "world icon".
Here is the attachment of TWRP Screenshot :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 03:38 PM ---------- Previous post was at 03:26 PM ----------
kickassdave said:
The below steps are only part of the solution since there are a couple of prerequisites (with solutions for those already on these forums and MIUI sites). I'm afraid since it's getting late here, I cannot provide detailed steps for everything, I'm assuming you are like me and only got so far, so already know what you're doing
.
Click to expand...
Click to collapse
I think we dont need to flash system.img. check out my post here. After flashing TWRP via fastboot, format data and type yes in TWRP, all you need to do is reboot to system and swipe disable stock recovery flash. Setup your Mi5 and then copy SuperSU 2.65 or 2.68 beta to your Mi5. Next is reboot back to recovery, swipe allow modification, and then flash the SuperSU. Done. I tested out on Dev ROM and Stable ROM too, that there is no need to flash system.img again.

tomhtg90 said:
I think we dont need to copy TWRP theme. You can set language in first welcome screen or in Settings menu, and tap "world icon".
Here is the attachment of TWRP Screenshot :
---------- Post added at 03:38 PM ---------- Previous post was at 03:26 PM ----------
I think we dont need to flash system.img. check out my post here. After flashing TWRP via fastboot, format data and type yes in TWRP, all you need to do is reboot to system and swipe disable stock recovery flash. Setup your Mi5 and then copy SuperSU 2.65 or 2.68 beta to your Mi5. Next is reboot back to recovery, swipe allow modification, and then flash the SuperSU. Done. I tested out on Dev ROM and Stable ROM too, that there is no need to flash system.img again.
Click to expand...
Click to collapse
When I set to English in TWRP without the theme mod, it instantly reverts to Chinese.
With regards to flashing the system.img, I have a slight nagging issue with regards to the amount of files inside the fastboot image which WEREN'T required for full functionality.
I'm also concerned about where my data was going when browsing, as my browsing was slow no matter which browser I used - almost as if it was proxying via China.
Having only flashed system.img I no longer have this issue.

kickassdave said:
When I set to English in TWRP without the theme mod, it instantly reverts to Chinese.
With regards to flashing the system.img, I have a slight nagging issue with regards to the amount of files inside the fastboot image which WEREN'T required for full functionality.
I'm also concerned about where my data was going when browsing, as my browsing was slow no matter which browser I used - almost as if it was proxying via China.
Having only flashed system.img I no longer have this issue.
Click to expand...
Click to collapse
English languages in TWRP will not go back to chinese if you tap on "Never show this screen during boot again", "swipe to allow modification" and "Swipe disable recovery flash". But, if that's the only method that work for you, good then. Cheers

No need to flash again system here too

What exactly do the rest of the contents of the ROM contain then since I literally flashed on a single img from the entire zip!

I have mine Mi5 unlocked, with TWRP, root (SU) open encryption.
I'm on china dev rom 6.3.17 and would like to upgrade to 6.3.24, as I have some issues (camera force close after trying to get picture during video recording and some apps crashes).
Anyway, my question is: HOW should I update system and not lose all my setting, apps, data, etc and of course I can't lose root, open encryption and unlocked bootloader.
Please advise.

1myxomatosis1 said:
I have mine Mi5 unlocked, with TWRP, root (SU) open encryption.
I'm on china dev rom 6.3.17 and would like to upgrade to 6.3.24, as I have some issues (camera force close after trying to get picture during video recording and some apps crashes).
Anyway, my question is: HOW should I update system and not lose all my setting, apps, data, etc and of course I can't lose root, open encryption and unlocked bootloader.
Please advise.
Click to expand...
Click to collapse
this is what i'm trying to do now. but i'm on another base... not the 6.3.17 but the 7.2.7.0, anyway this is the same procedure.
when you have unlocked your bootloader, there is no way to encrypt all data again if you don't select "flash_all_lock.bat" with MiFlash windows app...
so you can play all TWRP partitions...except the SDCARD (called "data/media", don't mingle/mix up/confound with the "data" partition.... )
So since fastboot is still open with your unlocked bootloader are always able to reflash a recovery and do whatever you want again, don't panic !
i tried updating my rom 7.2.7.0 to 6.3.24 by flashing the system.img BUT there are some force close.... security center FC... wifi not working... i think they forgot to say that we need to manually flash the boot.img too (kernel.... who contain a lot of drivers and system links...)
so i just flashed the system.img and boot.img of the 6.3.24 on my 7.2.7.0 rom, i will report my feedback in some hours max. EDIT : WORKING !
but don't wory, since you don't wipe your SDCARD in the recovery (or use the flash_all_lock.bat with MiFlash), you will not loose your decrypted data partition
if my method of "simple updating" is not working by just flashing system.img and boot.img over the rom........ i suggest to reflash all partition with adb (system.img and boot.img), after that you can reboot to the twrp recovery, flash supersu 2.68 (or the last one) to be root, and setup your phone again... (you can do a MiBackup in the settings, and restore it later, this is working fine for your app, settings and so on)
:silly:
---------- Post added at 08:21 PM ---------- Previous post was at 08:13 PM ----------
UPDATE : WORKING.
Procedure to UPDATE since your phone have UNLOCKED BL, data decrypted and TWRP already flashed (or you can flash it before the procedure by adb) :
PROCEDURE
just flash the system.img AND the boot.img with adb in the CMD
(be sure your files are in the same folder of adb.exe and fastboot.exe)
"fastboot flash system system.img"
"fastboot flash boot boot.img"
then reboot to twrp recovery... flash supersu 2.68..
you don't need to wipe something.
just reboot and wait.
your phone is now updated, with root, twrp, decrypted data, and you don't loose your apps, settings and files. :good:

nesquix said:
[...]
PROCEDURE
[...]
Click to expand...
Click to collapse
Sound so easy and so fantastic that I can't just believe I'll try tomorrow as today I don't have power if something went wrong and I would have to start from a zero point:]

1myxomatosis1 said:
Sound so easy and so fantastic that I can't just believe I'll try tomorrow as today I don't have power if something went wrong and I would have to start from a zero point:]
Click to expand...
Click to collapse

I can't flash anything on TWRP, I can't mount the data... and so there's no file in sdcard

so at which point is the phone unencrypted? With installing SuperSU ?!
I also have the provlem, that TWRP changes the language instantly after changing it. And it also prompts me for password of encrypted partitions

Ivyn87 said:
I can't flash anything on TWRP, I can't mount the data... and so there's no file in sdcard
Click to expand...
Click to collapse
Because your phone is still encrypted.
So read all 3stpage and you will understand what you need to do.
http://forum.xda-developers.com/mi-5/help/rooting-mi-4-unlocking-bootloader-t3334677/page3
---------- Post added at 04:12 PM ---------- Previous post was at 04:11 PM ----------
p1nky said:
so at which point is the phone unencrypted? With installing SuperSU ?!
I also have the provlem, that TWRP changes the language instantly after changing it. And it also prompts me for password of encrypted partitions
Click to expand...
Click to collapse
After wiping all the phone 2 times in the twrp recovery.

nesquix said:
Because your phone is still encrypted.
So read all 3stpage and you will understand what you need to do.
http://forum.xda-developers.com/mi-5/help/rooting-mi-4-unlocking-bootloader-t3334677/page3
---------- Post added at 04:12 PM ---------- Previous post was at 04:11 PM ----------
After wiping all the phone 2 times in the twrp recovery.
Click to expand...
Click to collapse
Very thanks... now it work

Why can't TWRP write to encrypted partitions? I thought this is possible with TWRP 3.0. At least I have not heard from new Nexus owners that disabling encryption is necessary.

Hello,
I have Twrp already and a custom rom, i only want to decrypt . Am i right that i only< had to do this:
Swipe on the first screen to enter the menu, tap the top right icon for wiping data, then the bottom right icon, you will see a text box with a warning - enter yes, then tick to fully wipe the SD card.
And later to get root:
Skip past initial steps for speed place the superSU zip on the root of the SD Card and then reboot back to recovery again
Flash SuperSU in recovery (top left option, find your zip, flash it
Reboot system.
Kind regards gandalf

Thank you very much. !!!!:laugh::laugh:
I saved this tutorial, I had left the phone in the login screen.

Hello guys , I need some advice. I have a Mi5s already unlocked with TWRP and custom rom, but would like to get rid of encryption. My doubt is, if I format data and wipe everything, will I be able to move the rom zip in TWRP? And also, will I still have a system installed ? Thanks for your reply

christ-al said:
Hello guys , I need some advice. I have a Mi5s already unlocked with TWRP and custom rom, but would like to get rid of encryption. My doubt is, if I format data and wipe everything, will I be able to move the rom zip in TWRP? And also, will I still have a system installed ? Thanks for your reply
Click to expand...
Click to collapse
Yes ... U keep system...get blank data... Restart the phone... copy the zip/ROM again...or use USB otg

Le Eco Pro 3 X727 Twrp Backup : Clean Full Stock X727 recovery EUI 5.8.21s

Return to Un-modded Stock:
Bootloader unlocked and TWRP and Root included
The file is 4gb compressed to 2gb. Depending on your connection it will probably take 20 to 45 minutes to download.
Be Advised
Do your research before flashing anything, I am not responsible for any damage caused to your device, due to impatience and missed steps. However, rest assured this recovery is solid and will absolutely return your X720 or X727 to stock 5.8.21s (with the bootloader already unlocked, TWRP installed and rooted)
I was asked by several people if I would be willing to share a link to my Stock X727 recovery, I created this thread to provide the 5.8.21s recovery for anyone who is experiencing dire issues or is simply wanting to restore the last official x727 recovery, as a daily driver or as a means to troubleshoot their issues by returning to the fully stock rom, stock partitions and ready to start over.
Attached is my full stock TWRP Recovery for my Le Eco Pro 3, version: 5.8.21s (X727)
It is a clean TWRP backup recovery that I did not mod in any way other than unlocking the bootloader.
The link is to my Google Drive account. https://drive.google.com/open?id=19dtLHmE5bsx5mdtEXOns4Z5drpeY79Em
The file is compressed
Ensure that you perform a full wipe before applying this recovery, and that you know what you are doing before attempting to install.
Please note that any changes that you make to your device is done at your own risk.
Please use caution and make sure that you have TWRP recovery installed.
Be in the habit of booting back to recovery before booting to system....This is a good practice for ensuring TWRP stays installed
You must unpack the downloaded 7zip file, before it will be useable.
As long as you can boot into TWRP and have root access you will have the full permissions needed to install anything , and reverse any actions that do not workout as planned.
Personally, I make a backup of my existing installation prior to making any changes. I recommend that you do the same. If you buy an OTG adapter and a USB 3.0 drive it takes 5 minutes.
The steps provided on the following link can be used to install my recovery file. https://forum.xda-developers.com/le-pro3/how-to/guide-return-to-stock-lock-bootloader-t3539513
When clicking the link, Google will attempt to scan. Click download to see the file, and then choose download if wanted.
Flash the appropriate files below for which ever device you own. ( X727 - Not needed, I provided the files anyway just in case.)
Firmware - X720
https://mega.nz/#F!kDgFQJ6R!MDhxCFw5KjfB0CfxAWwr9w
Firmware - X727
https://drive.google.com/open?id=136-4UpUUsj3exNsTc3d5n2iQuYUxr00H
Modems
X720: https://mega.nz/#F!pZ4WGARZ
Key : !2oG3Z2LS_wP8BzcWUQjfHg
X727: https://mega.nz/#F!NJ5VHS7Z
Key : !p0iO7bDiZ4kXny03EiAlWw
Build Prop Fix Device ID Tool ( Credit to @Ascertion )
https://mega.nz/#F!oAZ3yC4b
Key: !MDwbHXNTRdrpgMvQ42yviw
EFS:
Warning : Use this only if you have unrepairable IMEI Issues! Otherwise its not needed, and you could forever lose your original IMEI info.
https://drive.google.com/open?id=10n2VjwBYHmrq_PllcWmTaGUtMIeYynZ7
[B ]Just for Fun[/B] - Boot Screens and Boot Animations -
https://mega.nz/#F!JB51zbwR
Key: !sG_wXTPqyKpugg5QIZFo9w
These splash-screens and animations came from various sources. If you created them contact me so i can give you credit.
The Red Splash came from the Couco modified EUI : version 5.9.028s VR4
Other Helpful Hints and Tips More to Come!
Unlock Bootloader and Flash Roms, Gapps and Magisk https://forum.xda-developers.com/showpost.php?p=75009966&postcount=692 ( If using original Stock
Viper Settings : https://forum.xda-developers.com/showpost.php?p=75449097
Installing Viper and Dolby: https://forum.xda-developers.com/showpost.php?p=76362493&postcount=19
Edit
October 8, 2018:
I uploaded the Leeco Full Stock Rom 5.8.26s to my MegaDrive.
If you are selling your phone and want it to have stock without TWRP and without root , just flash this Rom and your stock radio driver "firmware" for your device
Link for EUI 21S : https://mega.nz/#!FRhh1ArL
Key: V5ua3oj91kFtgvLYBhl1X6Oq3bsScyDFruN3UptkWN0

A late reply to my issue but I just got around to restoring my Pro3. This worked while the last backup did not! Thanks!

Soul0Reaper said:
A late reply to my issue but I just got around to restoring my Pro3. This worked while the last backup did not! Thanks!
Click to expand...
Click to collapse
Thats Awesome! I am glad that it helped you.

Great work just what I needed only one problem for me after I flash rom reboot system and then go back into TWRP there seems to be encryption on it and I can't install or backup or do much. Is there a password or way around this TWRP encryption?

dunas2331 said:
Great work just what I needed only one problem for me after I flash rom reboot system and then go back into TWRP there seems to be encryption on it and I can't install or backup or do much. Is there a password or way around this TWRP encryption?
Click to expand...
Click to collapse
Sorry, I didn't get a notification for your message. The encryption is your storage.
Follow the instructions here to resolve: https://www.google.com/amp/s/forum....return-to-stock-lock-bootloader-t3539513/amp/
The link has instructions for getting past and removing encryption.

tsongming said:
Sorry, I didn't get a notification for your message. The encryption is your storage.
Follow the instructions here to resolve: https://www.google.com/amp/s/forum....return-to-stock-lock-bootloader-t3539513/amp/
The link has instructions for getting past and removing encryption.
Click to expand...
Click to collapse
Can you elaborate on what to do here I keep getting encryption password too and can't do anything in twrp

Hi tsongming, you know if can work on a x720?
thanks

Toni Moon said:
Hi tsongming, you know if can work on a x720?
thanks
Click to expand...
Click to collapse
Yes x720 and x727 are practically identical phones.
Sent from my LEX720 using XDA Labs

Scruffdog1978 said:
Can you elaborate on what to do here I keep getting encryption password too and can't do anything in twrp
Click to expand...
Click to collapse
I don't have time at the moment to provide lengthy instructions. With respect, I am providing a working, clean unlocked recovery file and pointing the way to instructions already that exist all throughout the LeEco forums.
But here's a quick answer
First use TWRP to reset your phone with a clean wipe, like you would for any ROM. Set developer options to the standard settings.
Next, your storage is encrypted. So it needs to be formatted. Use TWRP format the storage only. Then reboot to recovery.
****Important****
Don't ever format the storage without ensuring that you have a TWRP recovery. Always check the boxes to check if TWRP is installed before swiping. If you don't have a recovery you have a soft brick.
For you information, TWRP recovery is installed on it's on it very own partition. Formatting the storage does not affect the TWRP partition. Nonetheless, if you see the check box option, make sure they are checked.
I would suggest that you install the all in one tool : https://www.google.com/amp/s/forum....pment/tool-tool-one-mauronofrio-t3580611/amp/
This tool helps a lot and makes this stuff easier if are new to flashing custom Roms.. The all in one tool will update the Google driver and ADB installation on your computer.
After you format your drive you will have to flash the recovery from the PC. The links provided show all of the steps, or you can use the all for one tool. When your storage is encrypted you have no choice but to format.
If you use the all in one tool , see their page for instructions.
Read the instructions, then read them again. when learning something new it's a good idea to take notes.
Do not deviate from those steps or you could brick your phone.
There have been many people that have messaged me by PM who successfully returned to stock using my recovery, so it will work as long as you are careful and follow the instructions verbatim and you will be fine. Plus, It's a great idea to create your own working recovery before you begin.
Reminder, you are restoring to stock under you own discretion, I am not responsible if you miss a key step, have a power outage, use faulty cables or brick your device.
One final suggestion, when you install the recovery make sure your phone is fully charged. Unplug all unneeded external peripherals from your desktop computer.
Temporarily, disable antivirus, insert USB cable into the back of your desktop PC. Those outlets provide more power.
Please look past any typos, I typed this on little keys.
One last suggestion
Read this
http://www.androidtipsz.com/top-5-things-to-do-before-installing-a-custom-rom-on-your-android-device
Sent from my LEX720 using XDA Labs

Will I keep twrp after restore? Thanks
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
meh4life321 said:
Will I keep twrp after restore? Thanks
Click to expand...
Click to collapse
Also, could I just restore the system?

Could I just flash this in TWRP and keep twrp as my recovery?

meh4life321 said:
Will I keep twrp after restore? Thanks
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
Also, could I just restore the system?
Click to expand...
Click to collapse
No it will not keep twrp. follow the instructions in the link I provided above, there was no reason to duplicate the instructions on my post.
The difference is that my backup will restore your phone to Eui 5.8.21s with bootloader unlocked. You will need to reflash Twrp and root the phone with Magisk if you want to keep Twrp recovery ( that is what I would do) You will not be able to get OTA updates. But that doesn't matter because there probably not be any more OTA updates for the x727

Thank you, sir! This is great work. I was able to restore back to stock.
On the strange side of thing, my TWRP was saved. Previously, I was running AICP, but having multiple sound issues with it.
Here are the steps I followed to restore:
1) Move the file to OTG flash drive
2) Restore through TWRP via Restore

For my 727, it just reboot on logo, and doesn't go past it.

rob_z11 said:
For my 727, it just reboot on logo, and doesn't go past it.
Click to expand...
Click to collapse
It takes a while.
For me, I had the quickest experience by flashing Magisk afterwards. The stock Rom , Rooted, and with Xposed is actually pretty sweet.

tsongming said:
It takes a while.
For me, I had the quickest experience by flashing Magisk afterwards. The stock Rom , Rooted, and with Xposed is actually pretty sweet.
Click to expand...
Click to collapse
Will try again. How long is while? ?

rob_z11 said:
Will try again. How long is while?
Click to expand...
Click to collapse
It should not take more than 10 minutes, and will usually startup in 5. I just now restored one of my X727's with this recovery, using the OTG method that the last person used and viola in worked so there's no doubt. I have always used ADB until now.
However, unlike the other poster, I did lose Twrp and had to reinstall it.
Always, Always Ensure Twrp is permanently installed
Make sure that you are on the latest version of Twrp : https://twrp.me/leeco/leecolepro3.html
Run Magisk, install Rom, Install Magisk again
Personally, I use the latest version of Magisk : https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
You want a fully clean install before you flash.
Instructions are redundant of XDA: if you want something other than what you have read already: Click on my account history to find detailed instructions, ( I type too much, too often) Under most thanked, you can quickly find detailed instructions for installing , Roms, Rooting, Installing Twrp, How to wipe to avoid any issues.
Finally, if for some reason it still doesn't work, the file may have been corrupted.
Worst Case scenario : there are other recoveries available on XDA. Beware of the edited versions, they do not work as well as an unadulterated recovery.

tsongming said:
It should not take more than 10 minutes, and will usually startup in 5. I just now restored one of my X727's with this recovery, using the OTG method that the last person used and viola in worked so there's no doubt. I have always used ADB until now.
However, unlike the other poster, I did lose Twrp and had to reinstall it.
Always, Always Ensure Twrp is permanently installed
Make sure that you are on the latest version of Twrp : https://twrp.me/leeco/leecolepro3.html
Run Magisk, install Rom, Install Magisk again
Personally, I use the latest version of Magisk : https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
You want a fully clean install before you flash.
Instructions are redundant of XDA: if you want something other than what you have read already: Click on my account history to find detailed instructions, ( I type too much, too often) Under most thanked, you can quickly find detailed instructions for installing , Roms, Rooting, Installing Twrp, How to wipe to avoid any issues.
Finally, if for some reason it still doesn't work, the file may have been corrupted.
Worst Case scenario : there are other recoveries available on XDA. Beware of the edited versions, they do not work as well as an unadulterated recovery.
Click to expand...
Click to collapse
It actually worked for second time without any issues. Just can't get the root, but will follow your instructions.

Hi just wondering does this rom pass safetynet out of the box?
what is the date of the security patch of this rom?
thanks

blanktape said:
Hi just wondering does this rom pass safetynet out of the box?
what is the date of the security patch of this rom?
thanks
Click to expand...
Click to collapse
This recovery is stock EUI 5.8.21s. The exception is that the bootloader is unlocked, and it has TWRP Recovery instead of EUI Recovery. I do not remember which version of Magisk I Installed. I would advise that you flash the newest version of Magisk and you will not have any safety net issues.
If you are wanting a complete return to stock, you should instead reflash the stock Full Rom, which will reinstall EUI recovery and lockdown the bootloader.

[TWRP][RECOVERY] Asus ZenPad 10 Z300M, Z301M & Z301MF (locked bootloader ok)

This is basically a copy of my Z380M TWRP thread adopted for the ZenPad 10. I decided to start a new one since the OP of justshaun's original recovery/rooting thread has gone stale, even as I had posted several new releases of TWRP over the months. Its instructions are also a little outdated. I've also compiled a version for the new Z301M(F) models and needed a place to post it. This is where I will be posting TWRP updates from now on.
In addition to this thread, referring to the Z380M TWRP thread and the original Z300M thread (links above) may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the others.
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
REQUIREMENTS
Windows or Linux PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)
MediaTek VCOM drivers (available through Windows Update)
ZenPad 10 scatter file for SPFT, attached (choose the one for your tablet)
Recovery image, attached (choose the one for your tablet)
ZenPad Z300M, Z301M or Z301MF tablet upgraded to Android N
This won't be a guide on how to use SP Flash Tool. There are plenty of good guides out there like this one on how to set up drivers, load scatter files, flash and make backups with SP Flash Tool. If you're not familiar with this software or how to flash MediaTek devices in general, please do your research before attempting this. I will just get straight to the specifics about the ZenPad 10.
FIRST TIME INSTALLATION
For a locked bootloader:
At this point you should have your tablet powered off, the drivers installed, all of your data backed up, and SP Flash Tool v5.1532's Download tab open and loaded with the tablet's scatter file. Open the download agent file DA_PL.bin, replacing the default MTK_AllInOne_DA.bin. (You can use the AllInOne DA if you want, but the procedure involves extra steps as described below.) Load the extracted TWRP recovery image for your device (twrp-3.2.1-0-z30*m.img) under the recovery partition line in the partition table. Click the Download button inside SPFT. Now just connect the USB cable to your tablet and your computer's USB port. It should start the download process automatically and disconnect when finished.
Alternative Method:
If you're using MTK_AllInOne_DA.bin, you have to hold the Volume Up key as you insert the cable, which puts the device into an emergency download mode. In addition, you will need to have the stock preloader*.bin file loaded inside SPFT for it to be able to communicate with your tablet. The preloader is available inside the official zip file download. Do not flash the preloader (untick the box) or any partitions other than recovery. You just need to have a valid bin file selected under the Preloader line.
For an unlocked bootloader:
If you have used the Asus unlock tool to unlock your device, you will still not be able to use fastboot flash to install a custom recovery. However, you can do a "hot boot" or a tethered boot of TWRP. This method doesn't require SP Flash Tool. Download the TWRP image, put your tablet in fastboot mode and connect to PC. Then run this command to boot TWRP dynamically:
fastboot boot twrp-3.2.1-0-z30*m.img
Once inside TWRP, flash twrp-3.2.1-0-z30*m.img to Recovery using Install -> Install Image. Then reboot to recovery. You may be able to use TWRP in the tethered boot mode, but that could result in glitches due to different parameters passed by the bootloader to the kernel. That's why flashing is recommended.
To update from your installed TWRP version to a new one, just transfer the image to your tablet, then boot to TWRP and install it by going to Install -> Install Image and flashing to Recovery.
START RECOVERY
With the tablet powered off, hold the Volume Up and Power keys together until you get to a menu where you can select "recovery". On the Z301M/Z301MF, that option is labeled Factory Reset. Use Vol. Up to scroll and Vol. Dn to select. If you have a locked bootloader, it will show a Yellow State message because the recovery is not signed by the OEM. Just press volume up to boot it. On the welcome screen of TWRP it will ask you about modifying the system partition, I suggest you go with Keep System Read-only. Doing otherwise will complicate your OTA updates.
WARNING: Never start the stock recovery from the bootloader menu on this device. It is programmed by the bootloader to instantly wipe your data without any warning. Also, be aware that Android installs the stock recovery at every normal boot cycle. So you either have to flash the TWRP every time you want to run it, or disable the automatic recovery installation in the stock firmware. Any kind of mod to the boot image will prevent the automatic recovery installation. If you're not sure which recovery you have installed, you can always do a 'adb reboot recovery' from Android without risk of data loss.
WARNING 2: Make sure you use the correct scatter file for your device (i.e. don't mix up the Z300 and Z301 files). For the initial flash, there is no check for scatter file correctness. If you use the wrong one, SP Flash Tool will alter and lock your GPT to that scatter file layout, possibly bricking your device. It will not be easy to restore it. Flashing with the correct scatter file later on will not work because Flash Tool will not allow you to use a different file than the one you used initially.
What works: Basically everything... access to major partitions, decrypted userdata partition, decrypted adoptable storage, external SD card, ADB, USB-OTG, touch interface, splash screen, installing stock Asus OTA/web FW updates
What doesn't work: (no known problems yet, but please report any)
Not guaranteed to work: factory reset
DOWNLOAD
SP Flash Tool v5.1532
Z300M Scatter file for all storage sizes (right click, Save link as...) -- do not use for other models
Z300M TWRP 3.2.1-0 image -- updated March 15, 2018
Z301M(F) series Scatter file for all storage sizes (right click, Save link as...) -- do not use for Z300M or other devices
Z301M TWRP 3.2.1-0 image -- updated March 13, 2018
Z301MF TWRP 3.2.3-0 image -- updated August 29, 2018
Development and experimental files
Source code
P.S. The thanks button doesn't bite.

Heya, thanks for the new thread..
Stupid question(coming from Samsung flashing)
Ive got Zenpad S3 10 P027, is this TRWP not ideal for this?
Currently, have some su (root) issues. Recovery shows Android icon chest with ! and says "No Command"
When running su in Terminal ADB via PC, says command not recognized.
Looks like I need to reflash recovery. When in TRWP (launched via fastboot boot twrp on PC) I flashed stock recovery but had system mounted read only. Could that be the problem?

Bro, I think you need to do some more homework on root, su, dm-verity, mods, etc. and read the instructions more carefully before applying these hacks. You are making a lot of simple mistakes and ending up shooting yourself in the foot for it. I don't think there's anything wrong with the Z500 TWRP. It can handle installing the stock firmware just fine. The problem is elsewhere. The unlock tool also works fine in TWRP as well in my testing.
The No Command screen is normal. That's been answered many times... you need to hold power+vol. up (or down) to get to the menu. There is no way the stock recovery image can be broken and still boot up.
The su thing, IDK what the problem is, but I'm sure if you install Magisk Manager and make your own patched image from your currently installed firmware, and fastboot-boot with it, you will have su functionality. Just like what it says in the unlock tool instructions.
Lastly and most important, never mount system in read-write mode, as I've repeated several times and exactly as it says in the directions:
7. At the TWRP welcome screen, do not select to modify the system partition and touch Keep System Read-only instead. Doing otherwise will render your tablet unbootable.
8. Mount system in TWRP (in read-only mode)
Click to expand...
Click to collapse
The only time you can mount it in read-write mode is when you are absolutely sure you have disabled dm-verity in your boot image.

I've successfully installed TWRP on Z301M using the instructions from the first post, but then I somehow managed to lose the system. Yes, I should have backed up like the OP suggests.
I thought I should be able to reinstall the original firmware downloaded from Asus (e.g. UL-ASUS_P028_1-WW-3.3.12.0-user.zip) but both the 'adb sideload' method and the TWRP failed to install that firmware zip. My device looks bricked. The only thing I can do is to boot into TWRP (I actually need to select Factory Reset on the bootloader screen to get into TWRP). The folder 'system' is empty.
Can anyone suggest what I am doing wrong when trying to restore the Asus firmware?
When I try to sideload the zip, setting TWRP in the sideload mode, the computer begins uploading but after a few seconds gives the message "Total xfer: 0.01x" and stops, while Android errors with "set boot part fail. can not open misc-sd".
When I install the firmware zip from TWRP it also starts installing fine but shortly gives the same error "set boot part fail. can not open misc-sd".
Thanks

@ahacker, first of all, thank you for the feedback on the Z301M platform. You are literally the first person to have said anything about that version of TWRP.
To see the files on system, you first have to mount the system partition. Did you do that? If not, I suggest mounting it read-only. If there was any corruption on it, then reinstalling the firmware should have fixed it. The "misc-sd" errors are normal. Pretty sure they happen on stock recovery too. The stock firmware does not have dm-verity enabled, so letting TWRP modify system to prevent overwriting recovery should not have caused any problems.
At which point did it stop booting? Also, did you use the scatter file from first post? And can you tell me if the touch screen works fine in TWRP on your tablet?
I'm not sure what the deal is with adb sideload. I don't think I've ever actually tried it....

diplomatic, thanks for replying!
diplomatic said:
[MENTION=4776997]
To see the files on system, you first have to mount the system partition. Did you do that?
Click to expand...
Click to collapse
I do mount the system partition. It appears empty. When I reboot into system TWRP says that the OS is not installed.
I don't remember the details of how I lost the system partition. First time I entered into TWRP it asked for a password, probably to mount some partition. I pressed cancel or something. Then I might have cleaned the caches. But I am sure I haven't wiped system. I might have pressed Factory Reset somewhere, because I don't have any data yet on the new tablet.
I would indeed try to mount the system read only. This is not the first Android system I rooted (maybe fifth), and I was always able to restore the system either from sideload or recovery. But here it seems Asus is making us jump extra hoops to do that.
diplomatic said:
[MENTION=4776997]
Reinstalling the firmware should have fixed it.
Click to expand...
Click to collapse
That seems to be my main problem now. I cannot reinstall the Asus firmware. It may look like I might be installing a wrong version, but I am positive that I have Z301M tablet. This is what I bought and what the boot-loader says. I download Z301M firmware from the Asus website (e.g.). So it must be a correct firmware.
diplomatic said:
[MENTION=4776997]
The "misc-sd" errors are normal. Pretty sure they happen on stock recovery too. The stock firmware does not have dm-verity enabled, so letting TWRP modify system to prevent overwriting recovery should not have caused any problems.
Click to expand...
Click to collapse
Thank you for the information.
diplomatic said:
[MENTION=4776997]
Also, did you use the scatter file from first post? Does the touch screen work fine in TWRP on that tablet?
Click to expand...
Click to collapse
Yes. I found that to be the only scatter file that worked. I tried scatter.txt from the firmware zip, but the Flash Tool refuses tio pick it up. TWRP seems to be working fine with touches working as expected.
diplomatic said:
[MENTION=4776997]
I'm not sure what the deal is with adb sideload. I don't think I've ever actually tried it....
Click to expand...
Click to collapse
This is the unbricking method described here. It probably does the same thing as the "Install Zip" from recovery, because the errors that both methods give are the same.
---------- Post added at 01:19 AM ---------- Previous post was at 12:57 AM ----------
Now system refuses to mount

ahacker said:
I don't remember the details of how I lost the system partition. First time I entered into TWRP it asked for a password, probably to mount some partition. I pressed cancel or something. Then I might have cleaned the caches. But I am sure I haven't wiped system. I might have pressed Factory Reset somewhere, because I don't have any data yet on the new tablet.
Click to expand...
Click to collapse
Er, the password should have been for decrypting your userdata. If you didn't have one set up, there might be something wrong there.... Or possibly just unformatted.
ahacker said:
That seems to be my main problem now. I cannot reinstall the Asus firmware. It may look like I might be installing a wrong version, but I am positive that I have Z301M tablet. This is what I bought and what the boot-loader says. I download Z301M firmware from the Asus website (e.g.). So it must be a correct firmware.
Click to expand...
Click to collapse
Yeah, that has to be the right one. The installation script has to match the model name reported by the recovery. Otherwise it would simply abort.
ahacker said:
Yes. I found that to be the only scatter file that worked. I tried scatter.txt from the firmware zip, but the Flash Tool refuses tio pick it up. TWRP seems to be working fine with touches working as expected.
Click to expand...
Click to collapse
Great! Guess my kernel patch was on the dot and the partition layout has not changed from the Z300.
ahacker said:
This is the unbricking method described here. It probably does the same thing as the "Install Zip" from recovery, because the errors that both methods give are the same.
Click to expand...
Click to collapse
When you installed the zip, did you unmount system completely? BTW, when you mentioned the errors, the installation does keep going for like 5 to 10 minutes afterwards, right?
If you still can't resurrect it, please post or send me the recovery & kernel log that has your installation attempt.

diplomatic said:
When you installed the zip, did you unmount system completely? BTW, when you mentioned the errors, the installation does keep going for like 5 to 10 minutes afterwards, right?
Click to expand...
Click to collapse
I've tried both ways, with and without system mounted, a few times. The installation would fail after something like 5 seconds.
diplomatic said:
If you still can't resurrect it, please post or send me the recovery & kernel log that has your installation attempt.
Click to expand...
Click to collapse
I think I am giving up on this cheap tablet. I cannot even format it in the Flash Tool: it says "To format code area is forbidden on this phone". Asus is forbidding too much for me to ever buy it again. Attached the logs.
Thanks, diplomatic

OK, found the problem. Check your PMs, ahacker.

diplomatic said:
OK, found the problem. Check your PMs, ahacker.
Click to expand...
Click to collapse
I have replied (twice), but the reply does not appear in my Sent Items. I hope it has reached you. If not, I'll paste the reply here, if you don't mind.

i not understand... i have Asus ZenPad 10 LTE Z301MFL.. a root method has been released ???

@diplomatic
Would this be compatible with Z0310M ? can't find anything for this damn model...

Hi, NeBouse,
Are you sure you have the correct information? It looks like just a misspelling of Z301M, aka P028....

I have z301m.
One thing that was a surprise for me is that the TWRP recovery flashed with the method described in the original post does not stick. You have to flash it each time you use it. If you are like me this information is important, because the original recovery plainly wipes your data without asking or warning.
After you have flashed TWRP on the device, to go to the recovery mode you have to chose "Factory Reset" in the bootloader. Then it will complain about wrong OS, which is the sign that flashing TWRP worked; choose 'yes'. The first thing you should do in TWRP is a ful nandroid backup. (Not listening the OP's advice about backing up when Installing TWRP with a wrong scatter file almost cost me the device. Thankfully diplomatic managed to remotely fix my problem, probably spending a lot of his personal time. The scatter file in the original post is a correct one now.)
Creating a nandroid backup in TWRP takes unusually long time, I even once decided that it hanged. Taking long time, like 10-30 minutes, for a full backup is normal.

Asus Z300M , Magisk 16.3 (beta) and FW 5.3.19 WW now works!

z301m, WW-3.3.12.0 firmware
For rooting I've installed in TWRP Magisk v15.3 (diplomatic warned against 16.x, someone else against 15.4) - link.
Installed in TWRP xPosed framework 88.2 - link, and xPosed Installer apk from within Android - link.
So far, so good.
What I've found is that TWRP seems to have problems with external sd cards (lots of fs corruption). I found it safer to unmount by hand by unticking the sd card checkbox in "Mount". Not very conclusive about this though.

Thanks, ahacker. Good feedback. Although to be fair, I didn't say to avoid Magisk 16.x. I said 16.0. I'm pretty sure whatever bug it had is already fixed in the latest version.
Now that you've installed root, TWRP will stick around on the emmc. The stock recovery only gets installed if you have the original unpatched boot image on it. I mean, this is not unique to these devices. That's been standard Android functionality since some 4.x or 5.x version. And this is essentially what's in the warning on the OP.
The backup I'm talking about in the installation method is done with the SP Flash Tool readback function. That will pull the partition tables and your device's "metadata" that's unique to your unit. I don't think nandroid covers that...
Oh, and what is this SD corruption you're talking about? What file system is it formatted in? Have you checked your card for errors in Windows?

Asus releases so many difference Z301M model, so I am curious if this also works on Z301MF model?
Notice Z300MF has the MTK8163BA (or MTK8163A?) CPU model while Z301M uses : 8163B
Anyone tested that already? Thanks.

my zenpad 10 has frp lock. it this a solution to remove the frp lock?

Pls help how i flash original software via fastboot ?????

Better Mobile App

welcome