Related
Download the zip from this link http://s000.tinyupload.com/index.php?file_id=70581848454313738691 . After that mount USB in PhilZ and copy over the zip file to your phone. Then flash the zip file and your boot loop should be fixed. The fix is originally by @fosunite and was posted on the PhilZ page.
Why is the file size so big?
arifqur said:
Why is the file size so big?
Click to expand...
Click to collapse
I put several ROMs in it that I modified to work with the old recovery which I also modded...all is in the zip make sure to read the readme
or you could just keep a twrp recovery zip on your sdcard and flash it like i did when philz recover kept booting into recovery.
rob219 said:
or you could just keep a twrp recovery zip on your sdcard and flash it like i did when philz recover kept booting into recovery.
Click to expand...
Click to collapse
That's basically what the tutorial says but it also has modified CM11 zips that will be flashable in twrp 2.6.1.0
This is a simpler guide for those who have trouble with terminal based solutions
Sent from my LG-E980 using Tapatalk
philz bootloop
rob219 said:
or you could just keep a twrp recovery zip on your sdcard and flash it like i did when philz recover kept booting into recovery.
Click to expand...
Click to collapse
I am having this same issue. everything was going fine with it when I booted into recovery from rom toolbox, but the first time I booted into philz with the power vol up and home it looped and I cant get out of it. This TWRP method that you mention what version of TWRP should I dl and please someone help soon my phone is out of commission.
rjmxtech said:
Hi all,
I recently figured out how to get an LG E980 back to a usable state after being stuck in a recovery loop due to a user or random system error from the PhilZ Touch Recovery (CWM/TWRP combo) and put CyanogenMod on it instead of having to flash back to stock.....the following link is directed to a zip file with a read me inside of it along with some files that have been modified to work with the recovery I have included in the zip file.
------HERE IS THE ZIP FOLLOW THE README INSIDE IT OR RISK BRICKING YOUR DEVICE------
******I am not responsible for anything that may happen to your device while following this guide, before following it, and after following it.......by downloading the zip file and following the steps you take all responsibility for anything that may possibly happen to your device at any time before, after, or while following this guide!!!!!!!!!!!!!!!!!!!!!!******
Click to expand...
Click to collapse
I successfully installed TWRP 2.6.1.0. Not sure oif it is related but when I try to flash the cm11 zip file it says "no MD5 file found". It still says the flashing was successful. I then flash the pa-gapps file and it says "successful".
so I reboot to system and i get the "secure booting error. Cause: Device Unlock, so Boot Successful" then it boots right back into TWRP.
Please help.
droidbrain said:
I successfully installed TWRP 2.6.1.0. Not sure oif it is related but when I try to flash the cm11 zip file it says "no MD5 file found". It still says the flashing was successful. I then flash the pa-gapps file and it says "successful".
so I reboot to system and i get the "secure booting error. Cause: Device Unlock, so Boot Successful" then it boots right back into TWRP.
Please help.
Click to expand...
Click to collapse
did the flashing take a few seconds? are the files you are flashing on the SD card? if the answer is yes to both, you need to move the files you want to flash to the internal storage, then flash them. Personally i prefer CWM to flash and go back to TWRP if i ever get stuck on a recovery bootloop(reboot to system, fix root when prompted).
I did fix that issue without his files.
droidbrain said:
so I reboot to system and i get the "secure booting error. Cause: Device Unlock, so Boot Successful" then it boots right back into TWRP.
Please help.
Click to expand...
Click to collapse
What you guys might need is a command which should put your phone on usable state.
In this case of a bootloop into recovery you just need 6 steps.
1. Download the aroma file manager. It has a build in terminal console. Get this one here:
http://forum.xda-developers.com/attachment.php?attachmentid=2231581&d=1378202418
2. Place the zip file on anywhere you like. On external sd it s easier to find. Let s put it on the root of external sd.
3. In the recovery please flash that zip file from step 1
4. After aromafm has started, press menu->open console .
5. A console appeared. Type this command all at once:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 count=1088
6. Confirm this command by pressing enter. You see something displayed about copied with 1,1 kb or something. That was its process. To reboot your phone type in the console:
Code:
reboot
And confirm this by pressing enter again.
Info1: be sure that you didnt cause this boot loop by applying the OTA update from LG software update. If u did, the only way is to flash back with kdz!
Info2: Also if you flashed something what has caused an error loki ifying it and then bootloop, dont panic, use the command and flash something else working.
This command is handy, so write it down on paper or memorize it:.
Info3: If you enter the recovery by using POWER+volume up , ofc u need to enter the mentioned command in step 5 afterwards:::. Else you ll get a bootloop to recovery again.
Info4: If you are using philz touch recovery and have the aromafm zip file: Rename this file to "aromafm.zip" and place this into your external SD card into the clockworkmod/aromafm/aromafm.zip This way you can doubletap your recovery screen in philz touch and start your aromafm in a faster way.
Sent from my LG-E986 using XDA Free mobile app
fosunite said:
What you guys might need is a command which should put your phone on usable state.
In this case of a bootloop into recovery you just need 6 steps.
1. Download the aroma file manager. It has a build in terminal console. Get this one here:
http://forum.xda-developers.com/attachment.php?attachmentid=2231581&d=1378202418
2. Place the zip file on anywhere you like. On external sd it s easier to find. Let s put it on the root of external sd.
3. In the recovery please flash that zip file from step 1
4. After aromafm has started, press menu->open console .
5. A console appeared. Type this command all at once:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 count=1088
6. Confirm this command by pressing enter. You see something displayed about copied with 1,1 kb or something. That was its process. To reboot your phone type in the console:
Code:
reboot
And confirm this by pressing enter again.
Info1: be sure that you didnt cause this boot loop by applying the OTA update from LG software update. If u did, the only way is to flash back with kdz!
Info2: Also if you flashed something what has caused an error loki ifying it and then bootloop, dont panic, use the command and flash something else working.
This command is handy, so write it down on paper or memorize it:.
Info3: If you enter the recovery by using POWER+volume up , ofc u need to enter the mentioned command in step 5 afterwards:::. Else you ll get a bootloop to recovery again.
Info4: If you are using philz touch recovery and have the aromafm zip file: Rename this file to "aromafm.zip" and place this into your external SD card into the clockworkmod/aromafm/aromafm.zip This way you can doubletap your recovery screen in philz touch and start your aromafm in a faster way.
Sent from my LG-E986 using XDA Free mobile app
Click to expand...
Click to collapse
When I flashed zip it went into file manager and I had to acess the terminal from the menu. After the command string was entered I did get the 1,1 kb file message. When I tried to enter reboot, I got sh: reboot: not found. I exited console and closed file manager. It put me back into twrp. I then reboot back to system but I got the same secure boot message and back into twrp.
droidbrain said:
When I flashed zip it went into file manager and I had to acess the terminal from the menu. After the command string was entered I did get the 1,1 kb file message. When I tried to enter reboot, I got sh: reboot: not found. I exited console and closed file manager. It put me back into twrp. I then reboot back to system but I got the same secure boot message and back into twrp.
Click to expand...
Click to collapse
What did u do before u got in a bootloop?
Sent from my LG-E988 using XDA Free mobile app
droidbrain said:
When I flashed zip it went into file manager and I had to acess the terminal from the menu. After the command string was entered I did get the 1,1 kb file message. When I tried to enter reboot, I got sh: reboot: not found. I exited console and closed file manager. It put me back into twrp. I then reboot back to system but I got the same secure boot message and back into twrp.
Click to expand...
Click to collapse
You don't reboot from the console, you exit the console and also exit Aroma file manager back to CWM and then you just reboot system from Philz CWM and that should end your bootloop. Done it a bunch of times and always gets me out of the bootloop.
Erik
fosunite said:
What did u do before u got in a bootloop?
Sent from my LG-E988 using XDA Free mobile app
Click to expand...
Click to collapse
I was installing the OTA ATT update. When the phone restarted it booted into twrp been stuck there since. I can get into download mode but thats about it.
---------- Post added at 05:28 PM ---------- Previous post was at 05:19 PM ----------
ricco333 said:
You don't reboot from the console, you exit the console and also exit Aroma file manager back to CWM and then you just reboot system from Philz CWM and that should end your bootloop. Done it a bunch of times and always gets me out of the bootloop.
Erik
Click to expand...
Click to collapse
That is exactly what I did. Only boots into twrp.
droidbrain said:
I was installing the OTA ATT update. When the phone restarted it booted into twrp been stuck there since. I can get into download mode but thats about it.
---------- Post added at 05:28 PM ---------- Previous post was at 05:19 PM ----------
That is exactly what I did. Only boots into twrp.
Click to expand...
Click to collapse
Then your problem is not the recovery, your phone is booting to recovery only because your ROM fails to boot. Try installing another ROM using TWRP to see if it fixes your problem.
Erik
ricco333 said:
Then your problem is not the recovery, your phone is booting to recovery only because your ROM fails to boot. Try installing another ROM using TWRP to see if it fixes your problem.
Erik
Click to expand...
Click to collapse
I have tried multiple roms and have had the same problem. The only rom that seemed to be successful is the one attached to the link in the beginning of the thread. Except it still gave me the secure boot message and booted into twrp.
droidbrain said:
I have tried multiple roms and have had the same problem. The only rom that seemed to be successful is the one attached to the link in the beginning of the thread. Except it still gave me the secure boot message and booted into twrp.
Click to expand...
Click to collapse
What I would do in your case is restore back to stock using LG Flash Tools and then start over with FreeGee and install the recovery from there and see if your trouble clears.
Erik
Read info1 from my post.
U aplied the update and then u cannot boot. So u must flash kdz back to stock.
Sent from my LG-E988 using XDA Free mobile app
fosunite said:
Read info1 from my post.
U aplied the update and then u cannot boot. So u must flash kdz back to stock.
Sent from my LG-E988 using XDA Free mobile app
Click to expand...
Click to collapse
How do I do that?
droidbrain said:
How do I do that?
Click to expand...
Click to collapse
Better is that u should read this topic on the OP in the following link:
http://forum.xda-developers.com/showthread.php?p=44983841
[Guide][Stock Roms] Return Back To Stock AT&T & International
Sent from my LG-E988 using XDA Free mobile app
Even simpler root than Invisiblek's method for the older versions: If you have already tried that method and now have broken wireless, see Post #2.
Note: A more detailed and user-friendly version of these instructions can be found at: http://www.oppoforums.com/threads/n5206-international-root-instructions.24159
Download http://lum.uk/n3/files/recmodn3.img and http://lum.uk/n3/files/Root_ColorOS_by_tantrums_v2.zip
Copy the rooter onto your SD card.
Boot into fastboot by holding volume up while powering on the phone.
fastboot oem unlock
fastboot flash recovery recmodn3.img
fastboot boot recmodn3.img
Flash the root coloros zip file, reboot and you're rooted.
Note: This is a modified stock recovery that can flash OTAs as well as zips not signed by Oppo. If you prefer TWRP then that is available here: https://dl.twrp.me/n3/. Note that at the time of writing TWRP is unable to flash OTAs.
Thanks to [email protected] for the original root method, Arvin A. [email protected] for the fixing SuperSU to work on ColorOS, and [email protected] for providing the modified N3 recovery.
Restoring stock firmware
Download your chosen firmware and recovery from this thread
Copy the firmware to the root of the internal storage
Take a nandroid backup using TWRP
Reboot to bootloader from within TWRP
Code:
fastboot flash recovery recovery_N3.img
fastboot reboot
adb reboot recovery
Use the stock recovery to flash your chosen firmware
If you are downgrading then wipe data and cache (you did remember to take a nandroid, right?)
Reboot
You are now on stock fimware. Follow the rooting instructions in post #1, and if you wiped you may optionally restore only the data partition from your nandroid backup.
Will memory be erased?
Hi,
So i'm looking forward to root my beautiful Oppo N3.
On my last Phones memory (data and so on) was erased alongside with unlocking the phone.
Will it be the same on this phone so that I have to backup all my data?
Your data will not be erased when rooting or unlocking. Also your warranty will not be invalidated like it is with other manufacturers.
It is, however, always wise to take a backup before anything like this, just in case something does go wrong.
Hi,
I tried rooting my N3 now but i made a mistake by not executing the commands after falshing SuperSU.
That's why my phone is always booting into TWRP. There i tried executing your commands, but apparently the shell refuses to su by throwing exception: "command not found"
Going on with mount-command, it is also giving back an error: "can't find /system in /proc/mounts"
Hope sb could help me now...
EDIT: Solved by installing stock recovery, booting system, and the reflash twrp.
Lum_UK said:
Even simpler root than Invisiblek's method for the older versions: If you have already tried that method and now have broken wireless, see Post #2
Download http://teamw.in/project/twrp2/282 and http://download.chainfire.eu/supersu
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery openrecovery-twrp-2.8.4.0-n3.img
fastboot reboot
adb reboot recovery
Flash Super SU from within TWRP. Then boot the OS
adb shell
su
mount -o remount,rw /system
echo "/system/xbin/su --daemon &" >> /system/etc/init.qcom.post_boot.sh
Reboot and you're rooted.
By default ColorOS doesn't let apps auto-start themselves, so go into security centre and allow SuperSU to auto-start, otherwise you won't get prompts for root when other apps need it.
Thanks to invisiblek for the original root method and babelmonk for the fix. I have shamelessly copied these and adapted them for the new firmware.
Click to expand...
Click to collapse
Quoted from your post in oppo forum
Wait for the phone to boot:
adb reboot recovery
It should boot into TWRP recovery flash the SuperSU zip you downloaded but do not reboot as we need to fix a small bug in SuperSU due to Oppo not using the expected startup scripts.
adb shell
su
mount -o remount,rw /system
echo "/system/xbin/su --daemon &" >> /system/etc/init.qcom.post_boot.sh
Reboot and congratulations. You are now rooted.
Sorry , quite new in fastboot command so i apologize if I misunderstood you but I'm running on N5206_EX_23_150208 , which should i follow ? to boot up after flashing SuperSU or not to boot up ?
It doesn't matter which way around you do it, just that root won't work outside of ADB until it's done.
I assume that XDA folk are more familiar with ADB etc. than on the Oppo forums so the instructions skip over more detail here.
Updated the method to use fastboot boot instead of fastboot flash.
This should work around the issue with phones that can't flash twrp, and also leave the stock recovery in place which is more useful to have until we get some custom roms.
Lum_UK said:
Updated the method to use fastboot boot instead of fastboot flash.
This should work around the issue with phones that can't flash twrp, and also leave the stock recovery in place which is more useful to have until we get some custom roms.
Click to expand...
Click to collapse
I was using modified boot.img to get root and then edit init.qcom.post_boot.sh. Now my wi-fi is broken. Can I fix it without wiping? Maybe flash some other boot img?
Anilexis said:
I was using modified boot.img to get root and then edit init.qcom.post_boot.sh. Now my wi-fi is broken. Can I fix it without wiping? Maybe flash some other boot img?
Click to expand...
Click to collapse
Fixed it by flashing boot.img from 150208, root still there due to script edit.
Updated the OP to use the modified stock recovery (Wmjan's recovery for the N5207) as this will be friendlier to noobs and also make it easier to install OTAs.
Anyone know where to get the root coloros file? Link doesn't seem to work for me...
http://www.oppoforums.com/attachment..._v2-zip.31142/
cowabunga said:
Anyone know where to get the root coloros file? Link doesn't seem to work for me...
http://www.oppoforums.com/attachment..._v2-zip.31142/
Click to expand...
Click to collapse
Sorry for the delay in replying. I've re-hosted the file for you.
http://lum.uk/n3/files/Root_ColorOS_by_tantrums_v2.zip
You could also try this. It worked on my girlfriend's R5 running a similar version of ColorOS. Didn't need modified recovery or anything, install it, run, click the root button, and it'll reboot to recovery and root for you.
http://lum.uk/n3/files/ForceRoot.apk
can this root work with Chines n5207
Hello,
I'm from Malaysia,
I got problem with my N3 / N5206 after update the newest version of software...now it cannot detect any line signal and open a wifi...what the problem,can u help me...
I can't make the WiFi to work again. Installed all versions of firmware and no luck....
Update: I was using the wrong tool to flash the firmware.
Don't update the phone with Msm8974DownloadTool !!!!
You have to download and install QPST_2.7.460 and place the phone in download mode by pressing volume + and power button and then in QPST load the firmware N5206EX_11_A.11_150528_SVN6225 or Oppo_N3_N5206_EX_11_A.13_151230 or N5206EX_11_A.10_150519_SVN6196
After flashing the wifi is working but you gonna loose the NV ram backup for the IMEI numbers..
Then you have to open dealpad with *#801# and anable Full-port ON
In QFIL(QPST) click on Tools then click QCN Backup Restore
Choose the qcn file and press restore.
Everything will work again after reboot the phone...
I had TWRP 2.7.1 and Android 5.1 (adriano's AOSP rom), and then I did volume up + power button to go into the recovery, did my thing (I don't even remember what it was), true is, after that it only reboot's to TWRP, so way I can go into system.
I've wiped/formated everything I could, but it always goes to TWRP no matter what.
I've tried to go back to stock through LG Tool, but I'm having connection to server fail issues.
http://forum.xda-developers.com/showthread.php?t=2451696
On step two I have "no space left on device". Not sure if it's an error or not, true is, it does nothing. Also, I don't have USB storage access, my drivers have probably some other problem (strangely adb it's ok as mentioned).
I'm trying to back to stock, but I can't go into download mode because it goes straight to TWRP.
http://forum.xda-developers.com/showthread.php?t=2590185
Any help please? Completely desperate!
Do you have an SD card in your device? When I was stuck on TWRP on another device, removing the SD card solved the problem then.
Sent from my LG-V500 running CM12
GXGOW said:
Do you have an SD card in your device? When I was stuck on TWRP on another device, removing the SD card solved the problem then.
Sent from my LG-V500 running CM12
Click to expand...
Click to collapse
Nop.
Maxxd01 said:
Nop.
Click to expand...
Click to collapse
You will need an SD card to install a new ROM. Otherwise since you are on TWRP 2.7.x, you cannot add files to the tablet inside TWRP.
im_high_tech said:
You will need an SD card to install a new ROM. Otherwise since you are on TWRP 2.7.x, you cannot add files to the tablet inside TWRP.
Click to expand...
Click to collapse
That was not a problem because I already had a custom ROM on the internal storage.
The problem was no matter how many times I wiped/formatted everything, and applied the custom ROM, it was always booting to TWRP.
i had the same problem
i was stuck on recovery
i fixed it by enter this in terminal comand
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
enter then
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
i did reboot recovery and then flashed a rom and it worked
l'irlandais said:
i had the same problem
i was stuck on recovery
i fixed it by enter this in terminal comand
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
enter then
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
i did reboot recovery and then flashed a rom and it worked
Click to expand...
Click to collapse
I tried something like that, not sure if it was exactly that though.
Anyway I managed to revert back to stock 4.4.2 through the LG tool, which solved my problem, thanks anyway!
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
Hi there,
I'm trying to install TWRP onto my Xiaomi mi6 in order to keep backups and flash custom ROMs.
Last night I tried to install TWRP via ADB. I flashed the .img file, and was careful to hold down the 'volume up' button as I hit the command 'fastboot reboot' to ensure I didn't boot into stock recovery.
This brought me into the TWRP recovery. I selected READ-WRITE option (as opposed to read only) and tried rebooting to system. After this I tried rebooting into recovery to access TWRP once again, but was brought back to the stock recovery. TWRP couldn't be accessed.
I tried to reflash TWRP and to follow the suggestion posted here: https://forum.xda-developers.com/mi-6/development/recovery-twrp-xiaomi-mi-6-t3619822
The file: /system/bin/install-recovery.sh present in stock system is responsible for that.
You can simply stop this from happening by deleting it or renaming it to install-recovery.sh.bak using any root explorer or via TWRP (Advanced -> File Manager).
Click to expand...
Click to collapse
However, I could not find the file /system/bin/install-recovery.sh using the TWRP file explorer.
Any suggestions you could offer would be much appreciated.
My current miui version is: global 8.2.2.0 (NCAMIEC) and the phone has not been rooted (bootloader is unlocked).
spraggzilla said:
Hi there,
I'm trying to install TWRP onto my Xiaomi mi6 in order to keep backups and flash custom ROMs.
Last night I tried to install TWRP via ADB. I flashed the .img file, and was careful to hold down the 'volume up' button as I hit the command 'fastboot reboot' to ensure I didn't boot into stock recovery.
This brought me into the TWRP recovery. I selected READ-WRITE option (as opposed to read only) and tried rebooting to system. After this I tried rebooting into recovery to access TWRP once again, but was brought back to the stock recovery. TWRP couldn't be accessed.
I tried to reflash TWRP and to follow the suggestion posted here: https://forum.xda-developers.com/mi-6/development/recovery-twrp-xiaomi-mi-6-t3619822
However, I could not find the file /system/bin/install-recovery.sh using the TWRP file explorer.
Any suggestions you could offer would be much appreciated.
My current miui version is: global 8.2.2.0 (NCAMIEC).
Click to expand...
Click to collapse
After the twrp recovery installation is installed in the twrp recovery you install the " no-verity-opt-encrypt-5.1.zip" .
This will keep the twrp recovery,after restarting the system.
trifos said:
After the twrp recovery installation is installed in the twrp recovery you install the " no-verity-opt-encrypt-5.1.zip" .
This will keep the twrp recovery,after restarting the system.
Click to expand...
Click to collapse
Thanks for the response. May I ask, where I find this zip?
spraggzilla said:
Thanks for the response. May I ask, where I find this zip?
Click to expand...
Click to collapse
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.1.zip
Similarly when I install tarp in my Redmi 5 it gets install but shows 0mb internal storage and after that if I press reboot to recovery or reboot to system then twrp get deleted and mi stock recovery replace it .
Pls any body help me to install it