Develop Bugs

[GUIDE] Rooting AND Unrooting NS4G using a Mac

I’ve compiled this information, found elsewhere, in order to make it easier for Mac users with the Nexus S 4g. I’ve simply combined BuglessPete’s Instructions for Rooting/Unrooting on the NS4g, with kenvan19’s Guide to Root on a Mac. All credit goes to them and the sources they cited in their original threads. Any errors here are my own. This method worked for me. The only change I’ve made is to link to the most recent version of Clockwork Recovery.
[NOTE: If Pete prefers, this information can be incorporated into his original thread, and a Mod can delete this]
Warning: If you break your phone trying this, I am not responsible. I do not guarantee that the following is safe or that the steps are correct. Rooting your phone voids the warranty. I have no responsibility for anything that occurs as a result of your following these directions! I cannot provide any support nor guide you in undoing this process and restoring the phone to factory condition.
This process will wipe your phone. Ie, you will lose all your apps/data on your phone and have to reinstall them. It will also wipe your external storage, so back that up prior to proceeding if you want to keep anything.
1) Download this file and unzip it to your desktop (Inside you'll find all the files you need to proceed including "adb", "fastboot", "recovery-clockwork-3.0.0.5-crespo.img", and "su-2.3.6.1-ef-signed.zip"). Immediately delete "recovery-clockwork-3.0.0.5-crespo.img." You’ll replace it with the new version.
2) Download Clockwork 4.0.0.2 (****MAKE SURE YOU SELECT ONE OF THE NS4G VERSIONS*****) in the color of your choosing. Move the file into the adb-fastboot folder you created in Step 1.
3) On your phone, go to Menu>Settings>Applications. Select "Development" and check the box next to "USB debugging"
4) Connect the phone to your Mac via the USB cable
5) Open a Terminal window on your Mac (Applications>Utilities>Terminal), and copy/paste the following into the Terminal:
Code:
~/Desktop/adb-fastboot/adb reboot bootloader
Hit "Return" and wait for your phone to reboot into Bootloader/Fastboot mode
5) If your Bootloader screen says "LOCK STATE - UNLOCKED" then skip to Step 6. If it says "LOCK STATE - LOCKED" then copy/paste the following into the Terminal:
Code:
~/Desktop/adb-fastboot/fastboot oem unlock
Hit "Return" and on your phone will prompt you to confirm and warn you that you are going to lose everything. Confirm. At this point you will have an unlocked bootloader.
6) Copy/paste the following into the Terminal window (***Change the file name to the appropriate color***):
Code:
~/Desktop/adb-fastboot/fastboot flash recovery ~/Desktop/adb-fastboot/ns4g-4002-COLOR.img
Hit "Return" again and wait for recovery to boot.
For the following steps while in Recovery, use "Volume Down" to highlight a selection and "Power" to choose that selection:
8) Choose "mounts and storage"
9) Choose "mount USB storage". Your phone should now be mounted on the Mac as a Device called "NO NAME"
10) Move the zip file "su-2.3.6.1-ef-signed.zip" from the "adb-fastboot" folder to the "NO NAME" Device on you computer.
11) Eject/unmount your phone in the Finder on your Mac.
12) On your phone, choose "Unmount"
13) Choose "mount /system"
14) Choose "+++++Go Back+++++"
15) Choose "install zip from sdcard"
16) Choose "choose zip from sdcard"
17) Choose "su-2.3.6.1-ef-signed.zip"
Some people with new Nexus S' are finding that the file discussed in the following steps does not exist. If you cannot find it but can still reboot into Clock Work Recovery Mod then don't worry, you're still rooted and fine!
At this point you have root, but your phone will continue to replace ClockworkMod Recovery on reboot. To prevent this, do the following:
1) Reboot your phone, and download the app "Root Explorer" from the Market
2) Open Root Explorer and navigate to the "etc" directory.
3) Tap on the gray box that says "Mount R/W"
4) Tap and hold on the file "install-recovery.sh" and rename this file to "install-recovery.sh.old"
5) Download the app "ROM Manager"
6) Open ROM Manager and choose "Flash ClockworkMod Recovery". At this point you are all set.
To Unroot and Return to Stock:
1) Download Stock GRJ22 Software Images.
2) Unzip the files, and place the images into the adb-fastboot folder you created on your desktop above.
3) Open a terminal and use the following commands:
Code:
~/Desktop/adb-fastboot/adb reboot bootloader
4) Wait for bootloader to reboot on phone.
5) Then, in terminal use the following commands:
Code:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
~/Desktop/adb-fastboot/fastboot flash system ~/Desktop/adb-fastboot/system.img
~/Desktop/adb-fastboot/fastboot flash recovery ~/Desktop/adb-fastboot/recovery.img
~/Desktop/adb-fastboot/fastboot flash userdata ~/Desktop/adb-fastboot/userdata.img
~/Desktop/adb-fastboot/fastboot erase cache
~/Desktop/adb-fastboot/fastboot oem lock
6) Reboot to System, and you should be returned to Stock, Unrooted GRJ22.

hey i just rooted the phone. I can't see the install file in root explorer and I can't boot into the recovery anymore. what do i do?

nevermind i got it

Root explorer will not let me make /etc R/W. I press the gray button that says "Remount as R/W" but nothing happens

hmpm9 said:
Root explorer will not let me make /etc R/W. I press the gray button that says "Remount as R/W" but nothing happens
Click to expand...
Click to collapse
I'm not sure if you're reading the instructions correctly. You don't create /etc R/W.
In root explorer go to /etc directory and click on "Mount R/W" then rename the install file.
If there is a remount option, you probably already mounted.

Awesome thanks.

This is great, thanks. Is anyone having success? I have to wait until after work to do this.

hmpm9 said:
Root explorer will not let me make /etc R/W. I press the gray button that says "Remount as R/W" but nothing happens
Click to expand...
Click to collapse
Some root apps require BusyBox in order to work properly.
Edit: I think nandroid backup and BusyBox install should be part of every proper root guide.

FYI: The second steps 1-6 are ONLY necessary if clockwork recovery doesn't stick.
I didn't have to use these steps myself.
To see if it stuck, turn phone off. Then hold Volume UP + Power to enter bootloader. Then enter recovery, if it enters Clockwork Recovery. You're fine, and you don't need to do the second steps 1-6.
-Nick

Thanks man, just unrooted my phone to return it for the e3d. Worked absolutely flawlessly. Great write up.

Worked to unroot. Had to give it a couple tries but got it to work. Thanks for the great tutorial!

Thank you, It took me 5 mins and I now have root on my NS4G!!!

2) Download Clockwork 4.0.0.2 (****MAKE SURE YOU SELECT ONE OF THE NS4G VERSIONS*****) in the color of your choosing. Move the file into the adb-fastboot folder you created in Step 1.
Im not able to download this file... I tried all three... and it keeps saying Mounting Failed.
What am I doing wrong?
PLEASE HELP!!!! Im new to rooting... Im tired of paying people to do the rooting for me I want to learn on my own...
Thank you.

Lokario90 said:
2) Download Clockwork 4.0.0.2 (****MAKE SURE YOU SELECT ONE OF THE NS4G VERSIONS*****) in the color of your choosing. Move the file into the adb-fastboot folder you created in Step 1.
Im not able to download this file... I tried all three... and it keeps saying Mounting Failed.
What am I doing wrong?
PLEASE HELP!!!! Im new to rooting... Im tired of paying people to do the rooting for me I want to learn on my own...
Thank you.
Click to expand...
Click to collapse
You can see that as giving back to the economy in one way...

I could swear when i rooted early this morning on my virgin NS4G, it was 3.0.something and now i see it is now 4.0.something. Anyway i had to get inventive as the SD card would not mount on my Mac when i got to that part. Basically rebooted normally to reg Android, transferred SU to SD card(it mounted then) and got back to the step to flash SU. Did that manually, got a hold of ROM manager and all's well.
Only issue is that more often than not it still boots to the blue recovery and not CWM, and sometimes the Android guy with yellow rectangle. When that happens, i connect to Mac via USB and get to CWM via terminal.
But on the whole, ROM manager is a saviour. Been playing with MIUI rom now and it's impressive.
I assume the right way to boot into CWM is to hold down volume key and power key at the same time?

Trying to unroot to send it back for a replacement. At "~/Desktop/adb-fastboot/adb reboot bootloader" I'm getting "error: device not found." It's driving me bat****. Any ideas?

jckeyser - I know it might sound stupid but did u try a different usb cable? i just came across same issue as you. was unable to get my device to show up. Turns out cable i was using for some reason wasn't working with NS4G. It was my old Palm Pre cable. i swapped my cable for one that came with my kindle and device immediately showed up without any problems

jckeyser said:
Trying to unroot to send it back for a replacement. At "~/Desktop/adb-fastboot/adb reboot bootloader" I'm getting "error: device not found." It's driving me bat****. Any ideas?
Click to expand...
Click to collapse
You're missing a dash. It's
adb reboot-bootloader
.
Or you could boot into fastboot by powering on using volumeUp+Power.

2.3.5
Hey guys, just got the NS4G yesterday and want to root using this method. The best buy associate updated me from 2.3.4 to 2.3.5 without my knowledge and I was curious if this method would still work. If not, is there one that will.
Thanks

techdude54 said:
Hey guys, just got the NS4G yesterday and want to root using this method. The best buy associate updated me from 2.3.4 to 2.3.5 without my knowledge and I was curious if this method would still work. If not, is there one that will.
Thanks
Click to expand...
Click to collapse
Yes it will work just fine.
Sent from my Nexus S 4G using XDA App

TWRP for Asus Zenfone 5

TWRP v2.6.3.0
Requirement
"Rooted phone"
"Computer" (I used Windows)
How to Install
**Download the attached zip file on your computer and extract it.
1. Turn OFF USB Debugging.
2. Connect the phone to the computer.
3. Open 'install.bat' on the extracted folder on your computer.
4. You'll see 'adb wait-for-device' in command window on your computer.
5. Now turn on USB Debugging, you'll get a promt on your phone asking to allow the computer. Tap OK.
6. Now you'll again get a prompt, this time from Superuser asking for ADB shell access. Allow it.
7. Now wait some seconds. The phone will restart.
8. Unplug USB cable from phone. Done!!
9. Once the phone is turned on, reboot your phone.
10. Keep eyes on the notification LED. When the LED is Red, keep holding VOLUME DOWN button.
Now your're in TWRP
##TWRP is a bit laggy, but works perfect
If not working
Use any Root Explorer on your phone to go to the folder "system"
and rename the file recovery-from-boot.p to recovery-from-boot.bak
or just move the file to SDcard.
Hit the Thanks button if it worked, bros.
And comment below if there's any problem.

ask
Inquiad Raad said:
TWRP v2.6.3.0
Requirement
"Rooted phone"
"Computer" (I used Windows)
How to Install
**Download the attached zip file on your computer and extract it.
1. Put phone in "USB Debugging"
2. Connect it to the computer and let the drivers be installed.
3. Keep the phone screen on.
4. Now go to the extracted folder and open "install.bat"
#. You'll see a prompt on your phone asking you to allow your computer. Allow it/ tap ok.
5. Then you'll see a Superuser prompt on your phone. Allow it.
6. The phone should reboot automatically. Remove USB cable from phone. TWRP is installed :good: :good:
7. Once the phone is turned on, then reboot your phone.
8. Keep eyes on the notification LED. When the LED is Red, keep holding VOLUME DOWN button.
9. Now your're in TWRP
10.
##TWRP is a bit laggy, but works perfect
If not working
Use any Root Explorer on your phone to go to the folder "system"
and rename the file recovery-from-boot.p to recovery-from-boot.bak
or just move the file to SDcard.
Hit the Thanks button if it worked, bros.
And comment below if there's any problem.
Click to expand...
Click to collapse
Why in my phone not prompt a dialig to allow that adb, n in command promt just stop in tke adb wait-for-device?

gumelaragum said:
Why in my phone not prompt a dialig to allow that adb, n in command promt just stop in tke adb wait-for-device?
Click to expand...
Click to collapse
Please read the how to install again, bro. It has been edited and should work fine for everyone now. Sorry for the inconvenience anyways.

Does this in any way allow us to install custom ROMS? As far as I know the Zenfone 5 does not have a custom ROM, since the bootloader is locked, right?

There is something called Asus unlock app in ww 17 firmware. I am guessing it has something to do with unlocking the bootloader. I am not on ww 17, so i cannot vouch for it.
I also saw a ROM called Sphinx for zenfone on a website.

great work. is rhere any sub-forum for asus zen5 ?

The installation is succesfull, but when I reboot it to recovery mode just display no comment, then I rename the system file to .bak, reboot it, just display no comment again bro. . . Can you fix it? Please. . .

gumelaragum said:
The installation is succesfull, but when I reboot it to recovery mode just display no comment, then I rename the system file to .bak, reboot it, just display no comment again bro. . . Can you fix it? Please. . .
Click to expand...
Click to collapse
idk what's wrong with yours. It worked for everyone else I assume and worked on mine too. So, there's nothing to fix, bro.
sorry
MRasri said:
great work. is rhere any sub-forum for asus zen5 ?
Click to expand...
Click to collapse
Nope, not any kind of forum for Zenfone 5, I'm afraid.

Is it possible to install TWRP via fastboot? Im in a bootloop now.. and my usb debugging is turned off so i can't use adb.

hristcroixqwerty said:
Is it possible to install TWRP via fastboot? Im in a bootloop now.. and my usb debugging is turned off so i can't use adb.
Click to expand...
Click to collapse
not in my knowledge at least.
but hey, nothing is impossible, play around with it. maybe you can find a way out
or maybe fix the bootloop and install it in the above mentioned way. good luck :good:

Inquiad Raad said:
not in my knowledge at least.
but hey, nothing is impossible, play around with it. maybe you can find a way out
or maybe fix the bootloop and install it in the above mentioned way. good luck :good:
Click to expand...
Click to collapse
okay after some digging, installing TWRP is possible via fastboot.. i just need the image file of it. May I know where did u get the this files and procedure? Did you make it?

hristcroixqwerty said:
okay after some digging, installing TWRP is possible via fastboot.. i just need the image file of it. May I know where did u get the this files and procedure? Did you make it?
Click to expand...
Click to collapse
extract the recovery.tar located in the attached zip and rename the extracted file named "recovery" to "recovery.img". There you go. you got your desired image file. :good::good:
Idk if this would work though. I wouldn't try it on my phone.

I've tried booting recovery.img via fastboot but it doesn't work.

Has anyone flash any MOD with a successful result?
I don't know if all that MOD are not compatible with x86 CPU or it's a problem with TWRP itself but I tried several of them and no succeed. It always say "error executing updater binary in zip"
You guys have any comment ?

itraceyou said:
Has anyone flash any MOD with a successful result?
I don't know if all that MOD are not compatible with x86 CPU or it's a problem with TWRP itself but I tried several of them and no succeed. It always say "error executing updater binary in zip"
You guys have any comment ?
Click to expand...
Click to collapse
It's pretty confusing that twrp can't install zips. Well this twrp is basically for system and data backup.
There's a CWM, with that you can install zip files only by adb sideload. But backing up isn't working there.
I can upload the CWM for Zenfone 5 if you guys want me to

Inquiad Raad said:
It's pretty confusing that twrp can't install zips. Well this twrp is basically for system and data backup.
There's a CWM, with that you can install zip files only by adb sideload. But backing up isn't working there.
I can upload the CWM for Zenfone 5 if you guys want me to
Click to expand...
Click to collapse
I did tried also CWM but no luck because it cannot mount the sdcard and i couldnt find any zip file (even if it's exist in my phone). Really has no idea what's happening ..

itraceyou said:
I did tried also CWM but no luck because it cannot mount the sdcard and i couldnt find any zip file (even if it's exist in my phone). Really has no idea what's happening ..
Click to expand...
Click to collapse
as I said, you have to use adb sideload to install zip with CWM. This is the only way you can flash zips.
SD card won't mount for some reason.

Inquiad Raad said:
as I said, you have to use adb sideload to install zip with CWM. This is the only way you can flash zips.
SD card won't mount for some reason.
Click to expand...
Click to collapse
If it's like what you mentioned, what's "install from zip file" in CWM does? Why i cant just flash directly from zip file.
Thank you.
Sent from my Nexus 7 using XDA Free mobile app

itraceyou said:
If it's like what you mentioned, what's "install from zip file" in CWM does? Why i cant just flash directly from zip file.
Thank you.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Come on, bro. It's because CWM isn't mounting the sd card, but when you push the zip by adb sideload method, the CWM doesn't have to mount sd card and that's why it works.
Try it. It worked for me. :fingers-crossed:

Perfectly working bro. just replaced the recovery to the latest twrp 2.7.0

Did anyone make a copy of the stock system partition before rooting?

I, foolishly, forgot to do so after flashing the TWRP recovery and rooting with SuperSU for Wear. I was just experimenting and don't really need to have the watch rooted. I'd kind of like to go back to stock, if only for any future updates. Please tell me someone has a copy of the stock system partition.

If you used SuperSU you can try this using the file explorer on twrp or adb from twrp. Make sure you backup your current system first. Make sure you remove the su binary from \system\bin, \system\xbin, or \system\sbin... wherever it ended up. You also want to follow the directions here to remove the SuperSU apk.
http://forum.xda-developers.com/showpost.php?p=26027562&postcount=2

hecksagon said:
If you used SuperSU you can try this
Click to expand...
Click to collapse
Oh, I can and have removed SuperSU, but for some reason there was no install-recovery.sh backup to restore. I really just want to re-flash the system partition, but no one seems to have a copy.

I will make a backup for you if you teach me how to root my zenwatch. im not usually a noob like this but its been a while since ive rooted anything, and ive never rooted a smartwatch.

yes_thisis_joey said:
I will make a backup for you if you teach me how to root my zenwatch.
Click to expand...
Click to collapse
I think the following is right. It's been a few months since I rooted mine.
The first step will be to unlock the bootloader. This will wipe the watch, but of course there's probably not anything there that won't be automatically restored when you set it back up. Unlocking the bootloader (and really this whole process) is just like doing it on a phone.
Fastboot mode on the watch:
Restart the watch. At the Asus logo, swipe from top-left to bottom-right. That should get you to fastboot mode, then you swipe up and down to change menu items, and swipe right to select. Alternatively, if you already have developer options enabled on the watch and have up-to-date USB drivers and ADB working on your PC, you can use "adb reboot-bootloader" to get to fastboot mode on the watch.
Install TWRP on the watch:
See http://forum.xda-developers.com/zenwatch/orig-development/recovery-twrp-2-8-7-0-t3205196
Swipe up/down/right to start TWRP from the fastboot menu. Use TWRP to make a backup of the system partition. And share it here, please!
Push this Wear version of SuperSU to the watch, and flash it with TWRP:
http://rootjunkysdl.com/getdownload.php?file=LG G Watch/Root/Wear-SuperSU-v2.40.zip
Reboot the watch. It should now be rooted!

help need my zenwatch!!!
did you ever make a copy of the stock system.. as really need one can you help!!

Blu Advance 4.0 L2 (A030U) - Custom Recovery TWRP and root

Hi all,
First of all be carefull, Nobody will be responsible for bricking your device but yourself.
I compiled twrp 3.0 for blu advance 4.0 l2 (A030U) https://drive.google.com/open?id=0Bw48RaTkRMm_eTRXVk84aWJTUjA here the sources https://github.com/contrerasojuanc/device_blu_advance_l2_A030U, thanks to @Dees_Troy and its guide on https://forum.xda-developers.com/showthread.php?t=1943625. So, in order to install it on this device, we will need to unlock bootloader (Factory reset needed), and flash TWRP recovery on recovery partition.
Settings -> About device -> Compilation number click multiple times to get new developer options menu.
Enable Unlock OEM.
On terminal:
Code:
adb reboot bootloader
On terminal:
Code:
fastboot oem unlock
On terminal:
Code:
fastboot flash recovery twrp_a030u.img
On terminal:
Code:
fastboot reboot
(Immediately press and hold Volumen + on device until custome recovery shows up.)
In order to achieve root on this device, we need to install from TWRP a Supersu system-mode, available thanks to @mauam, it can be get at https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120 (I used SR3-SuperSU-v2.79-SYSTEMMODE.zip).
Note that maybe /system need to be mounted as writeable, so first mount System and then, on TRWP's terminal:
Code:
/system/bin/mount -o remount,rw /system
Hope, it can be useful somehow. Any questions, please let me know.

I did everything right but I can not get root

Could you give more detail on how you installed supersu in system mode? I used the command mount -o remount,rw /system (replacing /system with the actual system folder path I found using the mount command in twrp temrinal) BUT discovered system remained read-only and everywhere I searched says you need to have root access to mount it as re-writeable.
I installed the zip you used anyways but am now stuck at the BLU logo screen. What should I do now?

talesgs said:
I did everything right but I can not get root
Click to expand...
Click to collapse
Please give me more details of what was done, in order to try to help

4mand said:
Could you give more detail on how you installed supersu in system mode? I used the command mount -o remount,rw /system (replacing /system with the actual system folder path I found using the mount command in twrp temrinal) BUT discovered system remained read-only and everywhere I searched says you need to have root access to mount it as re-writeable.
I installed the zip you used anyways but am now stuck at the BLU logo screen. What should I do now?
Click to expand...
Click to collapse
The command I used for get writable /system was
Code:
/system/bin/mount -o remount,rw /system
exactly that one, remember that if you are in TWRP you have root access in recovery partition, so /system can be set as writeable from there. Probably you need to flash recovery and system partition again. I have those partitions from my stock device, let me know if want to give it a try.

Did you type any commands before that? I get the error "sh: /system/bin/mount: not found".
It would be great if you could link the stock partitions.

4mand said:
Did you type any commands before that? I get the error "sh: /system/bin/mount: not found".
It would be great if you could link the stock partitions.
Click to expand...
Click to collapse
No command before, this is what I did:
1. In TWRP tap Mount menu, then check "Mount system partition read-only" then check "System", then middle bottom button (Home). (So now we have /system partition mount but as RO)
2. Tap Advance menu, Terminal and type
Code:
/system/bin/mount -o remount,rw /system
3. Now if all goes alright, we should have /system writeable.
4. With /system writeable, tap on Install menu, select the Supersu file (Only this worked for me SR3-SuperSU-v2.79-SYSTEMMODE.zip).
5. Deviced rooted.
Ok, I'll try to upload the partitions tonight, while you could search the rom in web.

contrerasojuanc said:
No command before, this is what I did:
1. In TWRP tap Mount menu, then check "Mount system partition read-only" then check "System", then middle bottom button (Home). (So now we have /system partition mount but as RO)
2. Tap Advance menu, Terminal and type
Code:
/system/bin/mount -o remount,rw /system
3. Now if all goes alright, we should have /system writeable.
4. With /system writeable, tap on Install menu, select the Supersu file (Only this worked for me SR3-SuperSU-v2.79-SYSTEMMODE.zip).
5. Deviced rooted.
Ok, I'll try to upload the partitions tonight, while you could search the rom in web.
Click to expand...
Click to collapse
Yes, what you describe is exactly what I did on a previously stock device, but with the same issue on terminal I posted before. After ignoring that, and sideloading the supersu .zip you used, the device gets stuck on the second BLU logo screen on boot, no hope getting back to system. Hopefully it works the second time around with stock partitions...

4mand said:
Yes, what you describe is exactly what I did on a previously stock device, but with the same issue on terminal I posted before. After ignoring that, and sideloading the supersu .zip you used, the device gets stuck on the second BLU logo screen on boot, no hope getting back to system. Hopefully it works the second time around with stock partitions...
Click to expand...
Click to collapse
Also here
;-;

Blu Advance 4.0 L2 (A030U) rom partitions
Blu Advance 4.0 L2 (A030U) stock rom partitions
HTML:
https://ufile.io/j6925
Inside there is a scatter file to use with flashtools

contrerasojuanc said:
Blu Advance 4.0 L2 (A030U) rom partitions
HTML:
https://ufile.io/j6925
Inside there is a scatter file to use with flashtools
Click to expand...
Click to collapse
rooted? or stock?

talesgs said:
rooted? or stock?
Click to expand...
Click to collapse
Stock

I have a Blu Advance 4.0 L2 (A030L) device, I know it is different, but I dared, now I have a bricking device with this twrp 3.0. Anybody knows somethings about reverse it or if it is possible??

I already gave up doing root does not work

doni.zeti said:
I have a Blu Advance 4.0 L2 (A030L) device, I know it is different, but I dared, now I have a bricking device with this twrp 3.0. Anybody knows somethings about reverse it or if it is possible??
Click to expand...
Click to collapse
Hi, the only way I know would be to flash stock partitions of that device. If you manage to find them in the web, I could tell you how to flash it.

contrerasojuanc said:
Hi, the only way I know would be to flash stock partitions of that device. If you manage to find them in the web, I could tell you how to flash it.
Click to expand...
Click to collapse
thank you for your attention, I'm already trying your recommend, but no success yet. I have the stock, sp-flash and drivers (for win). I think it is any problem with drivers or sp-flash (v5.1712)...

Not working
Hi, I have a BLU Advance 4.0 L2 (A030U) and the TWRP doesn't work in my phone, it boots but the touchscreen isn't working, any suggestion?
UPDATE: I was booting twrp from fastboot because I wasn't able to flash it like is explained here, I think that is why my touchscreen wasn't working, anyways I managed to flash it through SP Flash Tools and It worked but now the root doesn't work, it softbrick the phone everytime I try, I'm able to mount system and all that stuff, everything is successfull but the phone does not boot.

Thank you
.It successfully helped root my Advance 4.0 L 2 A030L in yesterday.
I bad English.
I tried flash superuser.zip(superuser.phh.me_2016-09-23), Magisk-v14.0.zip, SR3-SuperSU-v2.79-SYSTEMMODE.zip, they could root my A030L(stock-V05_GENERIC）
if not fastboot reboot"(Immediately press and hold Volumen + on device until custome recovery shows up.)" , devices will replace your custom recovery automatically during first boot.
Other unimportant: Recovery in A030L also need remount / system, there is not read SDcard (update.zip can be imported in TWRP or OS to internal storage),can't backup userdate.can't input password to read userdate after Encrypted.
update:2017-1007 22:16
SR3-SuperSU-v2.79-SYSTEMMODE.zip looks not work...try next time
2017-1012
SuperSU. ---- Both of these are need: SuperSU-v2.76(or2..79).zip and SuperSU-v2.76(or2.79)-SYSTEMMODE.zip
BLU_A030L_V05_GENERIC i find it in
HTML:
https://plus.google.com/collection/cnwFTB
Ver-V05 can root both ok. Ver-V12 look like something wrong in boot.img,it can only root by Magisk. Maybe you should flash boot.img from ver-V05 if you want use V12.

i have a030u v12 rom. v5generic not work, after install result crash bootlogo loop same make option format... recovery not work! same press up button! after all process not enter in twrp. i test magisk not work customize boot.img flash to sp flash result crash boot! mtk droid not detect my phone too please help me.... very hard root this device!
TianNian said:
Thank you
.It successfully helped root my Advance 4.0 L 2 A030L in yesterday.
I bad English.
I tried flash superuser.zip(superuser.phh.me_2016-09-23), Magisk-v14.0.zip, SR3-SuperSU-v2.79-SYSTEMMODE.zip, they could root my A030L(stock-V05_GENERIC）
if not fastboot reboot"(Immediately press and hold Volumen + on device until custome recovery shows up.)" , devices will replace your custom recovery automatically during first boot.
Other unimportant: Recovery in A030L also need remount / system, there is not read SDcard (update.zip can be imported in TWRP or OS to internal storage),can't backup userdate.can't input password to read userdate after Encrypted.
update:2017-1007 22:16
SR3-SuperSU-v2.79-SYSTEMMODE.zip looks not work...try next time
2017-1012
SuperSU. ---- Both of these are need: SuperSU-v2.76(or2..79).zip and SuperSU-v2.76(or2.79)-SYSTEMMODE.zip
BLU_A030L_V05_GENERIC i find it in
HTML:
https://plus.google.com/collection/cnwFTB
Ver-V05 can root both ok. Ver-V12 look like something wrong in boot.img,it can only root by Magisk. Maybe you should flash boot.img from ver-V05 if you want use V12.
Click to expand...
Click to collapse
[/COLOR]
TianNian said:
Thank you
.It successfully helped root my Advance 4.0 L 2 A030L in yesterday.
I bad English.
I tried flash superuser.zip(superuser.phh.me_2016-09-23), Magisk-v14.0.zip, SR3-SuperSU-v2.79-SYSTEMMODE.zip, they could root my A030L(stock-V05_GENERIC）
if not fastboot reboot"(Immediately press and hold Volumen + on device until custome recovery shows up.)" , devices will replace your custom recovery automatically during first boot.
Other unimportant: Recovery in A030L also need remount / system, there is not read SDcard (update.zip can be imported in TWRP or OS to internal storage),can't backup userdate.can't input password to read userdate after Encrypted.
update:2017-1007 22:16
SR3-SuperSU-v2.79-SYSTEMMODE.zip looks not work...try next time
2017-1012
SuperSU. ---- Both of these are need: SuperSU-v2.76(or2..79).zip and SuperSU-v2.76(or2.79)-SYSTEMMODE.zip
BLU_A030L_V05_GENERIC i find it in
HTML:
https://plus.google.com/collection/cnwFTB
Ver-V05 can root both ok. Ver-V12 look like something wrong in boot.img,it can only root by Magisk. Maybe you should flash boot.img from ver-V05 if you want use V12.
Click to expand...
Click to collapse
---------- Post added at 07:13 AM ---------- Previous post was at 07:13 AM ----------
[/COLOR]
TianNian said:
Thank you
.It successfully helped root my Advance 4.0 L 2 A030L in yesterday.
I bad English.
I tried flash superuser.zip(superuser.phh.me_2016-09-23), Magisk-v14.0.zip, SR3-SuperSU-v2.79-SYSTEMMODE.zip, they could root my A030L(stock-V05_GENERIC）
if not fastboot reboot"(Immediately press and hold Volumen + on device until custome recovery shows up.)" , devices will replace your custom recovery automatically during first boot.
Other unimportant: Recovery in A030L also need remount / system, there is not read SDcard (update.zip can be imported in TWRP or OS to internal storage),can't backup userdate.can't input password to read userdate after Encrypted.
update:2017-1007 22:16
SR3-SuperSU-v2.79-SYSTEMMODE.zip looks not work...try next time
2017-1012
SuperSU. ---- Both of these are need: SuperSU-v2.76(or2..79).zip and SuperSU-v2.76(or2.79)-SYSTEMMODE.zip
BLU_A030L_V05_GENERIC i find it in
HTML:
https://plus.google.com/collection/cnwFTB
Ver-V05 can root both ok. Ver-V12 look like something wrong in boot.img,it can only root by Magisk. Maybe you should flash boot.img from ver-V05 if you want use V12.
Click to expand...
Click to collapse

Hi, in order to know what can be happening, first let's try to flash recovery partition, for that, please follow these steps:
Settings -> About device -> Compilation number click multiple times to get new developer options menu.
Enable Unlock OEM.
On terminal:
Code:
adb reboot bootloader
On terminal:
Code:
fastboot oem unlock
On terminal:
Code:
fastboot flash recovery twrp_a030u.img
On terminal: After write the next command, press enter on your computer and immediately press and hold Volumen + on device until custom recovery shows up.
Code:
fastboot reboot

[GUIDE][TWRP] for TWRP and ROM installation

Thought I'd post my experiences in case it helps anyone else out. Following this procedure will completely wipe your phone. As usual, I take no responsibility for bricks, headaches, wasted hours at the keyboard, etc. Do your research first. Please feel free to post corrections, improvements, etc, I will edit and add them. This post assumes your bootloader is already unlocked. If you're not unlocked, make sure you read all the various articles and warnings about Xiaomi's downgrade/relock protection which can result in a brick if you flash an older build with a locked bootloader. Unlocked is the safest way to go.
I installed the Xiaomi.eu rom, but this should work for any other rom in a flashable zip, downloads for the rom, TWRP and Magisk can be found here.
Install ADB and the relevant drivers. If you're on Linux or MAC, the easiest way I know of to do this is to use Corbin's excellent tool by running a single curl command.
Download TWRP, the ROM and Magisk (optional) into the same desktop folder as your ADB installation.
Boot into Fastboot (Vol- and Power).
fastboot flash recovery twrp.img
-> Boot to TWRP by holding Vol+ and Power.
Once you've booted to TWRP, change the language to English by touching the third button down in the second column (right above the button in the lower right), then touch the globe icon at on the right in the blue bar, then select English and hit the button in the lower right corner.
From the Wipe menu in TWRP, press Format Data, this will remove encryption (and wipe your phone, obviously, including everything in storage, photos, documents, everything).
While there, swipe to do a Factory Reset (which will also wipe your phone).
-> At this point, I repeated the recovery reboot procedure to be sure that TWRP would still boot, Vol+ and Power, or reboot recovery from TWRP menu. Not sure this is strictly necessary.
(For some reason, I couldn't get MTP to work in TWRP, it wouldn't copy files from the desktop. If you can get MTP to work you can simply drag and drop the rom and Magisk, otherwise you can do what I did and use ADB instead.)
From the desktop, push the rom you want to use, and Magisk, to the phone, this syntax (Linux) assumes your rom is in the adb folder, otherwise you need to provide the path:
adb push xiaomi.eu_multi_MIMix3_V10.0.12.0.PEECNFH_v10-9.zip /sdcard/Download
adb push Magisk-v17.1.zip /sdcard/Download
From TWRP, install the rom followed by Magisk from /sdcard/Download on the phone.
Reboot System.
Drink beer, preferably something hoppy and top fermented.
Note for AMD Ryzen machines: There appears to be a USB2.0 bug associated with Ryzen CPUs which prevent the fastboot flash from working. If the flashing process starts then fails, try a different machine.

ROM File and TWRP not listed
invisiblewave said:
Thought I'd post my experiences in case it helps anyone else out. Following this procedure will completely wipe your phone. As usual, I take no responsibility for bricks, headaches, wasted hours at the keyboard, etc. Do your research first. Please feel free to post corrections, improvements, etc, I will edit and add them. This post assumes your bootloader is already unlocked. If you're not unlocked, make sure you read all the various articles and warnings about Xiaomi's downgrade/relock protection which can result in a brick if you flash an older build with a locked bootloader. Unlocked is the safest way to go.
I installed the Xiaomi.eu rom, but this should work for any other rom in a flashable zip, downloads for the rom, TWRP and Magisk can be found here.
Install ADB and the relevant drivers. If you're on Linux or MAC, the easiest way I know of to do this is to use Corbin's excellent tool by running a single curl command.
Download TWRP, the ROM and Magisk (optional) into the same desktop folder as your ADB installation.
Boot into Fastboot (Vol- and Power).
fastboot flash recovery twrp.img
fastboot boot twrp.img
-> At this point, my phone would reboot to MIUI recovery. To solve this, as soon as the screen goes black after the previous command, boot to TWRP by holding Vol+ and Power.
Once you've booted to TWRP, change the language to English by touching the third button down in the second column (right above the button in the lower right), then touch the globe icon at on the right in the blue bar, then select English and hit the button in the lower right corner.
From the Wipe menu in TWRP, press Format Data, this will remove encryption (and wipe your phone, obviously).
While there, swipe to do a Factory Reset (which will also wipe your phone).
-> At this point, I repeated the recovery reboot procedure to be sure that TWRP would still boot, Vol+ and Power, or reboot recovery from TWRP menu. Not sure this is strictly necessary.
(For some reason, I couldn't get MTP to work in TWRP, it wouldn't copy files from the desktop. If you can get MTP to work you can simply drag and drop the rom and Magisk, otherwise you can do what I did and use ADB instead.)
From the desktop, push the rom you want to use, and Magisk, to the phone, this syntax (Linux) assumes your rom is in the adb folder, otherwise you need to provide the path:
adb push miui_MIMIX3Global_V10.0.11.0.PEEMIFH_9761b07e78_9.0.zip /sdcard/Download
adb push Magisk-v17.1.zip /sdcard/Download
From TWRP, install the rom followed by Magisk from /sdcard/Download on the phone.
Reboot System.
Drink beer, preferably something hoppy and top fermented.
Click to expand...
Click to collapse
---
Hi, thanks for the guide, the ROM files and TWRP are not available on the link

fahdsuleman said:
---
Hi, thanks for the guide, the ROM files and TWRP are not available on the link
Click to expand...
Click to collapse
Yes they are, you need to look again

Mackay53 said:
Yes they are, you need to look again
Click to expand...
Click to collapse
Thanks, found them.

fahdsuleman said:
---
Hi, thanks for the guide, the ROM files and TWRP are not available on the link
Click to expand...
Click to collapse
They're right below the ROM table.

invisiblewave said:
Thought I'd post my experiences in case it helps anyone else out. Following this procedure will completely wipe your phone. As usual, I take no responsibility for bricks, headaches, wasted hours at the keyboard, etc. Do your research first. Please feel free to post corrections, improvements, etc, I will edit and add them. This post assumes your bootloader is already unlocked. If you're not unlocked, make sure you read all the various articles and warnings about Xiaomi's downgrade/relock protection which can result in a brick if you flash an older build with a locked bootloader. Unlocked is the safest way to go.
I installed the Xiaomi.eu rom, but this should work for any other rom in a flashable zip, downloads for the rom, TWRP and Magisk can be found here.
Install ADB and the relevant drivers. If you're on Linux or MAC, the easiest way I know of to do this is to use Corbin's excellent tool by running a single curl command.
Download TWRP, the ROM and Magisk (optional) into the same desktop folder as your ADB installation.
Boot into Fastboot (Vol- and Power).
fastboot flash recovery twrp.img
fastboot boot twrp.img
-> At this point, my phone would reboot to MIUI recovery. To solve this, as soon as the screen goes black after the previous command, boot to TWRP by holding Vol+ and Power.
Once you've booted to TWRP, change the language to English by touching the third button down in the second column (right above the button in the lower right), then touch the globe icon at on the right in the blue bar, then select English and hit the button in the lower right corner.
From the Wipe menu in TWRP, press Format Data, this will remove encryption (and wipe your phone, obviously).
While there, swipe to do a Factory Reset (which will also wipe your phone).
-> At this point, I repeated the recovery reboot procedure to be sure that TWRP would still boot, Vol+ and Power, or reboot recovery from TWRP menu. Not sure this is strictly necessary.
(For some reason, I couldn't get MTP to work in TWRP, it wouldn't copy files from the desktop. If you can get MTP to work you can simply drag and drop the rom and Magisk, otherwise you can do what I did and use ADB instead.)
From the desktop, push the rom you want to use, and Magisk, to the phone, this syntax (Linux) assumes your rom is in the adb folder, otherwise you need to provide the path:
adb push miui_MIMIX3Global_V10.0.11.0.PEEMIFH_9761b07e78_9.0.zip /sdcard/Download
adb push Magisk-v17.1.zip /sdcard/Download
From TWRP, install the rom followed by Magisk from /sdcard/Download on the phone.
Reboot System.
Drink beer, preferably something hoppy and top fermented.
Click to expand...
Click to collapse
I'm doing all the things that you've said but it still boots me to miui receovery, what should i do ?

Lumpka21 said:
I'm doing all the things that you've said but it still boots me to miui receovery, what should i do ?
Click to expand...
Click to collapse
Boot to TWRP using the buttons instead of the fastboot boot twrp.img command. I had the same problem. Also, make sure you're not installing the stock rom, that appears to also overwrite TWRP (that's what it looked like to me, I didn't bother to confirm for sure).

invisiblewave said:
Boot to TWRP using the buttons instead of the fastboot boot twrp.img command. I had the same problem. Also, make sure you're not installing the stock rom, that appears to also overwrite TWRP (that's what it looked like to me, I didn't bother to confirm for sure).
Click to expand...
Click to collapse
You can use stock ROM and twrp. Twrp is replaced if you boot the OS

Mackay53 said:
You can use stock ROM and twrp. Twrp is replaced if you boot the OS
Click to expand...
Click to collapse
Ok, so once you've flashed TWRP, there are two recoveries on the device and booting into the stock OS changes the bootloader to boot to the MIUI recovery?

Hello, i found this very useful. thank you

Hi, I followed your instructions and I flashed TWRP, but I just can't reach it. When I give the ADB command to boot I immediately try to start in TWRP recovery mode by pressing vol up+power, but at the beginning the phone doesn't do anything, then it boots to Android and I can only access MIUI recovery. Have you worked out another way or am I wrong in doing smth?
(Also pardon my ignorance, but I turned USB debugging on, am I right?)

Alexdruso said:
Hi, I followed your instructions and I flashed TWRP, but I just can't reach it. When I give the ADB command to boot I immediately try to start in TWRP recovery mode by pressing vol up+power, but at the beginning the phone doesn't do anything, then it boots to Android and I can only access MIUI recovery. Have you worked out another way or am I wrong in doing smth?
(Also pardon my ignorance, but I turned USB debugging on, am I right?)
Click to expand...
Click to collapse
You don't need ADB for flashing twrp so having usb debugging on is irrelevant.
Flash twrp In fastboot and once it's done and without giving any more commands just hold power and volume up. Eventually it will boot into twrp.

Did anyone wipe system before flashing the global zip over the Chinese rom? I didn't wipe data (which is not smart, I know this) and I have noticed some of the system apps have duplicates with different versions. I also have a few weird behaviors with Google Play store and some other items now. Debating installing TWRP, wiping both, and reflashing.
Nevermind, I can't do that. I don't have another activation for Google Play Music, and I can't set the device ID without root, and I can't root the global version so I can't wipe data. GG

PWn3R said:
Did anyone wipe system before flashing the global zip over the Chinese rom? I didn't wipe data (which is not smart, I know this) and I have noticed some of the system apps have duplicates with different versions. I also have a few weird behaviors with Google Play store and some other items now. Debating installing TWRP, wiping both, and reflashing.
Nevermind, I can't do that. I don't have another activation for Google Play Music, and I can't set the device ID without root, and I can't root the global version so I can't wipe data. GG
Click to expand...
Click to collapse
You never ever need to wipe the System so it won't be that, wipe would be recommended if you can do it

Which version of twrp should I use?

Herrick1209 said:
Which version of twrp should I use?
Click to expand...
Click to collapse
The only one there is for the MM3.

invisiblewave said:
The only one there is for the MM3.
Click to expand...
Click to collapse
I couldn't find it on the twrp website??

Herrick1209 said:
I couldn't find it on the twrp website??
Click to expand...
Click to collapse
You can't find one for the Mix 2s there either.
You can find one for the Mix1 there, but it is non- functional.
. . .
DYODD

Herrick1209 said:
I couldn't find it on the twrp website??
Click to expand...
Click to collapse
That's why I posted the link in the OP.

Thanks, does this apply to the Xiaomi MI Mix 3 Forbidden City Edition?