Help rooting LS990 - G3 Q&A, Help & Troubleshooting

First off please excuse any typos or long response times as i have a broken hand .
Okay, I have a Sprint Lg G3 ls990 I believe Software version LS990ZVA Build number LRX21Y.
I have tried a few different rooting methods with no sucess as of this moment. I do not know if because of user error or if its been patched..
The methods I have tried are:
1 - LG One-Click Root (Got to %90 and froze) (Manualy placed into download mode)
2 - LG Root Script (hangs after reboot) (reboots into normal mode)
3 - PurpleDrake (Got to a point and program closed itself)
4 - StumpRoot (Patched)
5 - TowelRoot (AKA Framaroot) (Nope)
Here is where I run into the problems. When executing the programs or scripts it will reboot the phone after pushing the first set of files and then it reboots into NORMAL mode
with the home screen and such while the script/program says looking for serial port. It does nothing at this point.
With one program if I manual go into download mode manually at this point it did detect port once and got to 90% complete but then again it just sat there.
Any help would be great, Thanks.
PS I need root to get my MSL so I can do a Rom install. The methods I have found shows you have to have root to get it.
If you know how to get this without root that would be great.

Solved the problem using this method: http://forum.xda-developers.com/sprint-lg-g3/general/one-click-root-zva-t3141390
Still neet to get my MSL though.

To load a rom all you need is to load custom recovery and then install the rom file via recovery.
Check out http://forum.xda-developers.com/sprint-lg-g3/general/apk-flash-twith-auto-rec-thanks-to-t3078517 to load custom recovery.

Related

[RECOVERY][UNOFFICIAL] CWM RECOVERY v5.0.2.8 for LG Optimus 3D Max P725 and P720H

Hello Guyzzz!!!!!
A Great Newzz for ALL!!!!! First the recovery was not compiled by me!
But NOW I am BACK with a FULLY WORKING RECOVERY AND FULLY COMPILED BY ME :good:
We have now a FULLY WORKING CLOCKWORKMOD RECOVERY v5.0.2.8.
The CLOCKWORKMOD RECOVERY is TESTED on :-
1. LG OPTIMUS 3D MAX P725
2. LG OPTIMUS 3D MAX P720H
I HELD NO RESPONSIBILITIES FOR BRICKED PHONES. YOU MAY TRY ON P720 BUT AT YOUR OWN RISK.
Credit Goes to :-
1. I, Me and Myself ( For taking the initiative,compiling testing and removing all bugs )
2.. Cynogenmod for the SOURCES.
3. P720H tester ZOOM.
According to me, the CWM RECOVERY is fully working.
HERE ARE THE STEPS TO INSTALL THE CWM RECOVERY :-
Download the CWM RECOVeRY FINAL.zip from the link given below :
http://www.mediafire.com/?p59d9ppjlhkcp67
Copy the cwm5.0.2.8.img on the ROOT OF THE SDCARD not the External SDCARD ( Root of SDCARD means not in any folder )
The BIGGEST REQUIREMENT IS YOUR OPTIMUS 3D MAX should be ROOTED!!!
Now download ANY TERMINAL EMULATOR from the GOOGLE PLAY!!!!!
You can try this :-
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
And install it.
Type the following commands in TERMINAL EMULATOR :-
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
dd if=/sdcard/cwm5.0.2.8.img of=/dev/block/mmcblk0p6 bs=4096
Once complete.
Turn off your phone.
1st hold 3d key then volume down button and at last power button.
Keep holding till the LG LOGO appears and leave when it appears.
You will enter the CWM Recovery
Proof of the Recovery :-
Worked like a charm! First I couldn't get the # to appear (the phone WAS rooted) so I just used the terminal emulator you specified, and that solved it.
lordasphyxia said:
Worked like a charm! First I couldn't get the # to appear (the phone WAS rooted) so I just used the terminal emulator you specified, and that solved it.
Click to expand...
Click to collapse
Happy to help you.
"HITTING THANKS WILL ENCOURAGE ME MORE":good:
Eklovya said:
IT TOOK MORE TIME TO DEVELOP THIS RECOVERY THAN THE TIME YOU WILL TAKE TO JUST " HIT THANKS".
Click to expand...
Click to collapse
dude you are not developed this recovery, it's created by me, you only unpacked my recovery using kitchen , that not call develop
Where did i mentioned that I DEVELOPED???
I clear mentioned that you compiled and i removed all bugs...
Sent from my LG-P725 using xda premium
Thread for this exists from original dev
http://forum.xda-developers.com/showthread.php?t=1889468
Thread closed
Edit: Thread reopened for a newly compiled version
HELP!!!!
After downloading an update from LG it allways boots to recovery!!
TommyX235 said:
HELP!!!!
After downloading an update from LG it allways boots to recovery!!
Click to expand...
Click to collapse
Try doing a factory reset.!!!
Sent from my LG-P725 using xda premium
tryed everything .. factory reset .. i have a backup from my original rom.. when i restore it i also boot into cwm.
i can start sw update mode (vol +) but either there nor in cwm i have adb access..
i tryed kdz but i don't know the dev type .. i tryed TI / 3GQCT etc. the program crashes
its breaking my heart .. i have this device the first day and now its broken!
ARRGG!!!
I still have the backup of the mmcblk0p6.backup
can i do anything with it?
maybe it is possible to install it via zip in cwm?
TommyX235 said:
tryed everything .. factory reset .. i have a backup from my original rom.. when i restore it i also boot into cwm.
i can start sw update mode (vol +) but either there nor in cwm i have adb access..
i tryed kdz but i don't know the dev type .. i tryed TI / 3GQCT etc. the program crashes
its breaking my heart .. i have this device the first day and now its broken!
ARRGG!!!
I still have the backup of the mmcblk0p6.backup
can i do anything with it?
maybe it is possible to install it via zip in cwm?
Click to expand...
Click to collapse
Install LG SUPPORT TOOL IN PC.
KEEP YOUR PHONE IN DOWNLOAD MODE.
CONNECT TO PC.
OPEN LG SUPPORT TOOL.
IN TOOLS SELECT RECOVER PHONE.
INPUT YOUR IMEI.
AND WAIT FOR THE RECOVEY PROCESS TO FINISH.
ALL WILL BE DONE SAFELY AND YOU WILL GET THE PHONE WORKING
Sent from my LG-P725 using xda premium
this damn tool doesn't recognize my IMEI also when i enter my device type p720 & Serial a small window pops open showin my device and my serial .. when i click ok .. another popup telling .. please check your device or something.
---------- Post added at 08:36 AM ---------- Previous post was at 07:42 AM ----------
also why is adb not working?
Is there a way to get it workin in CWM?
In CWM in section advanced you can do show log.
CWM-based Recovery v5.0.2.8
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=omap4430
ro.revision=7
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running
I:checking for extendedcommand...
I:Skipping execution of extendedcommand file not found...
Does this mean something?
Also this lg Tool only worked for me when adb also was working.
TommyX235 said:
this damn tool doesn't recognize my IMEI also when i enter my device type p720 & Serial a small window pops open showin my device and my serial .. when i click ok .. another popup telling .. please check your device or something.
---------- Post added at 08:36 AM ---------- Previous post was at 07:42 AM ----------
also why is adb not working?
Is there a way to get it workin in CWM?
In CWM in section advanced you can do show log.
CWM-based Recovery v5.0.2.8
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=omap4430
ro.revision=7
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running
I:checking for extendedcommand...
I:Skipping execution of extendedcommand file not found...
Does this mean something?
Also this lg Tool only worked for me when adb also was working.
Click to expand...
Click to collapse
is it somehow possible to activate nable adb access in CWM 5.0.2.8?
or can i flash a zip to do this?
Again .. i can enter S/W Upgrade Mode
There i only see S/W Upgrade
Please wait
while upgrading....
(NO ADB ACCESS! But the Tool recognize the phone but won't let me start the sw upgrade.)
In CWM i can mount & unmount storage and flash zip files or backup / Restore.
BUT no ADB access and Restoring the backup i made doesnt work either)
What breaking my head is that the LG Update must had set a flag to boot into recovery after i downloaded it so mindless.
Since then i stuck in cwm bootloop. There mus be a way to reset this flag. Somehow!!!)
Its over .. i flashed CWM-Loop-DeLooper -> now i stuck @ LG Logo.. also vol+ to enter S/W Upgrade not working anymore. Now its bricked! ARGH!
TommyX235 said:
is it somehow possible to activate nable adb access in CWM 5.0.2.8?
or can i flash a zip to do this?
Again .. i can enter S/W Upgrade Mode
There i only see S/W Upgrade
Please wait
while upgrading....
(NO ADB ACCESS! But the Tool recognize the phone but won't let me start the sw upgrade.)
In CWM i can mount & unmount storage and flash zip files or backup / Restore.
BUT no ADB access and Restoring the backup i made doesnt work either)
What breaking my head is that the LG Update must had set a flag to boot into recovery after i downloaded it so mindless.
Since then i stuck in cwm bootloop. There mus be a way to reset this flag. Somehow!!!)
Its over .. i flashed CWM-Loop-DeLooper -> now i stuck @ LG Logo.. also vol+ to enter S/W Upgrade not working anymore. Now its bricked! ARGH!
Click to expand...
Click to collapse
Can you come on chat? So that i can help you!!
Sent from my LG-P725 using xda premium
can this tutorial work on ICS su870?
joseph168 said:
can this tutorial work on ICS su870?
Click to expand...
Click to collapse
Nop this will not work. As the bootloader is locked for su870
Sent from my LG-P725 using xda premium
LG P725 CWM Problem
Hi guys need help, i installed this cwm recovery with no problems, when i start it i see menu, can move up and down but i can`t launch anything. I read at different sites that i should to use shutdown key or 3d key but they don`t work. Also i install newer version 6.... but there are this problem too. I have LG 3D max (P725) version o firmware v10f.
Andrelius1 said:
Hi guys need help, i installed this cwm recovery with no problems, when i start it i see menu, can move up and down but i can`t launch anything. I read at different sites that i should to use shutdown key or 3d key but they don`t work. Also i install newer version 6.... but there are this problem too. I have LG 3D max (P725) version o firmware v10f.
Click to expand...
Click to collapse
use volume keys to move up and down.
and capacutive keys to select
Sent from my LG-P725 using xda premium
CWM problem
Eklovya said:
use volume keys to move up and down.
and capacutive keys to select
Sent from my LG-P725 using xda premium
Click to expand...
Click to collapse
Thanks a lot! Its strange that in any instruction not says this way of use CWM, i read a lot differents cwm instructions, but the always the same - use power off key ot use 3d button.
Who don`t how to use CWM menu :
"properties button" - up
"home button" - down
"back button" - back
"search button" - ENTER
Cannot select options in cwm
Hi Eklovya,
Brilliant job done!!
I have successfully rooted and installed CWM following your method.
However, when i go boot to CWM, I can use the volume buttons to highlight the options (I wanted to backup), but I am not able to select the options. i tried the power button and the 3D button, no go. What do i do?
I just exchanged my P920 and got myself this P725 today!!!
schubeir
EDIT: my bad!!! found the solution in the post just above!!!!
schubeir
(possibly long post , I will try to make a post at least a little fun to read).
Guys, I humbly come before you, kneeling and desperate, trying to solve my problem .
I've serarched XDA and a lot (!!) of others forums and comunities to revive my P720H (LG optimus 3D Max in Brazil).
I am not a complete noob in custom firmwares for Android, but this time, the LG phone gave me a hell of a headache (and almost a divorce, for the 3 days going too late to bed, trying to solve it).
I will explain what happened and what I've already tried to do and the results.
Causes:
I've tried to install ClockworkMod in my P720H because it still was in Android 2.3.6 (I think).
I've successfully rooted the phone using this thread: http://forum.xda-developers.com/showthread.php?t=1886057 with the SuperSU app on GooglePlay.
When I asked CWM app to reboot in recovery mode (to wipe things and install the .zip file on the sdcard root) things got bad.
My phone could not get passed the LG logo anymore.
So far we have a cause: CWM app did something to the phone. I am not able to boot the recovery menu nor to pass the LG logo on the screen.
Over the communities we may find that it's a common issue.
It is important to say that I am able to enter the 'S/W updating' state. When I connect the phone to the computer, holding VOL+ and placing the battery, I got the S/W screen.
What can I do? In several posts (even here in xda) we may find 3 or 4 different solutions to restore the phone. I think I've already tried everything, but I am sure that the steps became fuzzy in my read and I mixed the solutions in the end.
Drivers:
- I have already the drivers installed: When I connect the phone (with or without battery and with or without vol+ pressed) my Device Manager recognizes everything. I don't have any component marked as 'unknown device' or with exclamations points or anything. This is a good thing, I guess. I had to install more than one thing to solve every driver problem. I don't remember exactly, but I think that the LGDriver-something and the omap4430 something too.
Solutions:
- I have tried the LG Support Tool and so far it appears to be the closest to a solution that I've reached. With the phone connected (in S/W mode or no), I insert the IMEI and the software recognizes the model and starts downloading something (500mb approx.). But after decompressing, during the installation phase, it gets stuck at 4%. I waited for more than 20min and still got nothing better than 4%. It appears to be a common issue too.
- The LG_FlashTool (version 1.2) does not work either. In fact, it does not even recognizes the phone. I've changed the COMport to 41 (according to some guide) on Windows Device Manager and chose the port 1 on LGFlashTool. Even after selecting the kdz, bin and fls files, the software does not connect to the phone. I don't have a screenshot here, but I've seen here in xda that the software displays the model of the phone on the top and a READY message on port 1. Mine does not do it.
- KKDZ_FW_UPD_EN: I've tried this one but it does not even start working. The interface is not that good, so I don't know where I may be failing. I need to 'read phone information' or not? What do I have to chose on each combobox? How to proceed?
And why the hell is there so much .exe on this thing? Do I have to run a apache server to do something?!
- OMAP4BOOT: This one connects to the phone and works, I think. But I don't know its purpose. It's just to place the phone on 'S/W updating' mode? If so, it's useless, because I can enter it easily. If no, maybe I am missing something. Either way, I don't have a version for the P720H. If I remeber correctly, it proposes P999, P760, P870, ... I choose P760 to test it and it works (apparently, again).
- SmartFlashTool: I don't remember if I have already tried this one. As I said, it was too much already.
- NVFlash: I've found it only to G2X, so I didn't know if I should try forcing it to my model. I can give it a try if you help me.
Other softwares and downloads:
KDZ:
- V10B_00 and V1A_00: found today and downloaded for my model and country (will try to extract things and use it later).
- LG_P725_V10F_00: I was using this one until yesterday, because I didn't have the one to P720H
- LGP700AT-01-V10d-232-03-SEP-11-2012+0.dz : Found in an indian repository of some kind of LG data leak. Apparently is useless. DZextract gave me nothing.
DLL: LGP720_20120330_LGFLASHv1377: Needed in some of the softwares above (LG FLashTool? I don't remeber).
BIN and FLS: LGP725_LG_P725_V10F_00_AP.bin and LGP725_LG_P725_V10F_00_CP.fls, extracted from LG_P725_V10F_00.kdz. I don't know, but I should try extracting these from the V10A_00, because apparently is the correct one for my model/country (I am not in my house right now).
Well... :crying:
tl;dr version:
I am facing a LG logo boot loop in P720H. I've tried to reboot CWM in recovery mode but it didn't work. I've tried several approaches but I don't even know what is the point of each one. I found that this is the best topic to use, because is one of the fews that covers the P720H.
I have all those softwares and almost 5gb of downloaded material (kdz, img, bin, exe, ...) but I don't know what I am supposed to use.
In the end, I want my P720H in android 4.x if possible. If not, I just want the crap 2.3.6 again. :crying:
Can you help me? I am not a total noob in custom firmwares and roms, and I am willing to pass all the information that I can :fingers-crossed:

[Q] help me to get root my htc desire 820 dual sim..

Dear Sir,
I have followed all the steps but still not rooted my htc desire 820 dual sim
http://forum.xda-developers.com/desire-820/general/htc-desire-820-root-easily-t2913064..............this link I have followed.....
but didn't sucess.......
plz....help...Sir
HTC Desire 820 can be easily rooted with few simple steps.
I am not responsible for your warranty loss or device not functioning properly.
Steps
1] Unlock Bootloader if you don't know how to do it visit this page
2] Download TWRP Recovery from here
3] Download Super Su from Here and transfer it to your device
4] Reboot to Fastbboot mode using Volume Down and Power Key
5] Connect Phone to PC
6] Extract files from Recovery.zip in one location and simply click on flash-recovery.bat
7] After Step 6 is finished Using volume keys navigate and select recovery option and go to recovery
8] After rebooting in recovery select Install zip > and selecting supersu.zip transferred in first step to obtain root access.
9] Reboot
Very much urgent.......plz. reply...........
subinoy.bose said:
Dear Sir,
I have followed all the steps but still not rooted my htc desire 820 dual sim
http://forum.xda-developers.com/desire-820/general/htc-desire-820-root-easily-t2913064..............this link I have followed.....
but didn't sucess.......
plz....help...Sir
HTC Desire 820 can be easily rooted with few simple steps.
I am not responsible for your warranty loss or device not functioning properly.
Steps
1] Unlock Bootloader if you don't know how to do it visit this page
2] Download TWRP Recovery from here
3] Download Super Su from Here and transfer it to your device
4] Reboot to Fastbboot mode using Volume Down and Power Key
5] Connect Phone to PC
6] Extract files from Recovery.zip in one location and simply click on flash-recovery.bat
7] After Step 6 is finished Using volume keys navigate and select recovery option and go to recovery
8] After rebooting in recovery select Install zip > and selecting supersu.zip transferred in first step to obtain root access.
9] Reboot
Very much urgent.......plz. reply...........
Click to expand...
Click to collapse
Try thishttp://forum.xda-developers.com/attachment.php?attachmentid=2784451&d=1402084843
Please let us know what is the exact message your getting are you not able to get to Recovery ???
I have been able to successfully root my device by following the steps outlined did not face any challenges hence wanted to check.
Same Probleam here pls help me
I AM SUFFERING FROM SAME PROBLEAM.
i am using desire 820q.
bootloader unlocked.
but when i enter in recovery then that says entering recovery then come back.
pls help me...
problem with htc 820q root
mukulatri said:
Try thishttp://forum.xda-developers.com/attachment.php?attachmentid=2784451&d=1402084843
Click to expand...
Click to collapse
I'm following this instruction and could not root my device,
My HTC 820q is unlock but when I want read SuperU.zip from Sd card at fastboot>recovery my mobile goes to restart and procedures been uncompleted.
Please help me, is this instruction only for HTC 820?
How we can root HTC 820q?
tah3r said:
I'm following this instruction and could not root my device,
My HTC 820q is unlock but when I want read SuperU.zip from Sd card at fastboot>recovery my mobile goes to restart and procedures been uncompleted.
Please help me, is this instruction only for HTC 820?
How we can root HTC 820q?
Click to expand...
Click to collapse
http://forum.xda-developers.com/desire-820/general/htc-desire-820-root-easily-t2913064
mukulatri said:
Try thishttp://forum.xda-developers.com/attachment.php?attachmentid=2784451&d=1402084843
Click to expand...
Click to collapse
Well I have the same issue, recovery looks installed after pressing power button to launch it goes to a screen and go back almost instantly on fastboot screen. I also tried last version of framaroot, does not help either... just get a failed message
尚雷諾 said:
Well I have the same issue, recovery looks installed after pressing power button to launch it goes to a screen and go back almost instantly on fastboot screen. I also tried last version of framaroot, does not help either... just get a failed message
Click to expand...
Click to collapse
Hi there, let's go step by step without "shortcuts" that are typically working on PC/WIn.
1. Unlock bootloader of your phone at HTCdev[dot]com [replace 'dot' with . - sorry for confusion I haven't earned reputation to post external links yet]. All necessary tools (fastboot) will be provided to download during process as well as necessary instructions. You need Windows/Linux or OS X computer to complete this step.
2. Download custom recovery .img file and save it to same directory you have fastboot files (e.g. from step 1) on you computer
3. Start phone in fastboot mode (mind fast boot option in Power settings must be unchecked if you using VolDown [-] start option (not necessary if you use adb reboot bootloader). Battery must be charged over 10% (I suggest 30% to stay secure); connect to computer (phone shall display Fastboot USB)
4. Navigate command/terminal window on your computer to location of recovery image file from step 2 (fastboot files must be there or have a correct path specified).
5. On computer terminal window run command: fastboot flash recovery filename_of_recovery.img . Red section must be exact custom recovery file name.
6. You'll get some communication in terminal. If completed OK will be among them, if failure, there will be FAIL with description of reason (e.g. low_power). If only "waitng for device" dislays, check connection with phone.
7. Navigate phone to HBOOT, then select recovery. If recovery don't start, check step 1 and restart from step 3. If only icon with red ! appears, it means you have stock recovery installed. Please verify from step 1.
8. Once custom recovery is installed and working, use it to flash SuperSU or any other superuser app (must be flashable .zip to be applied). Install just 1 root application, to avoid problems. At this point, you may consider flashing busybox also if you plan extensive file modification, but it's not necessary for root. For any sake, clear cache befor restart.
9. Restart the phone - you shall view SuperSU application or any other superuses app you've flashed i step 8.
Hope now works.
T0ark said:
Hi there, let's go step by step without "shortcuts" that are typically working on PC/WIn.
1. Unlock bootloader of your phone at HTCdev[dot]com [replace 'dot' with . - sorry for confusion I haven't earned reputation to post external links yet]. All necessary tools (fastboot) will be provided to download during process as well as necessary instructions. You need Windows/Linux or OS X computer to complete this step.
2. Download custom recovery .img file and save it to same directory you have fastboot files (e.g. from step 1) on you computer
3. Start phone in fastboot mode (mind fast boot option in Power settings must be unchecked if you using VolDown [-] start option (not necessary if you use adb reboot bootloader). Battery must be charged over 10% (I suggest 30% to stay secure); connect to computer (phone shall display Fastboot USB)
4. Navigate command/terminal window on your computer to location of recovery image file from step 2 (fastboot files must be there or have a correct path specified).
5. On computer terminal window run command: fastboot flash recovery filename_of_recovery.img . Red section must be exact custom recovery file name.
6. You'll get some communication in terminal. If completed OK will be among them, if failure, there will be FAIL with description of reason (e.g. low_power). If only "waitng for device" dislays, check connection with phone.
7. Navigate phone to HBOOT, then select recovery. If recovery don't start, check step 1 and restart from step 3. If only icon with red ! appears, it means you have stock recovery installed. Please verify from step 1.
8. Once custom recovery is installed and working, use it to flash SuperSU or any other superuser app (must be flashable .zip to be applied). Install just 1 root application, to avoid problems. At this point, you may consider flashing busybox also if you plan extensive file modification, but it's not necessary for root. For any sake, clear cache befor restart.
9. Restart the phone - you shall view SuperSU application or any other superuses app you've flashed i step 8.
Hope now works.
Click to expand...
Click to collapse
Thanks for your answer, I have to say I properly unlocked the phone so I do not think there is a way I messed up with this step as when I start bootloader it clearly shows on the top of the screen ''UNLOCKED".
When I flashed recovery on my phone I had no errors prompted or any message of failure. The process went well until a success notification.
Now when I start my phone into bootloader I repeat, I clearly see that recovery has been installed but when I attempt to start it then I'll be almost instantly brought back to the bootloader screen... now I started to wonder if... if an update of android could cause this kind of issue? The point is my phone is using android 4.4.4 and not the factory version 4.4.2. I remember having updated my android version which was perhaps a mistake as this phone is not very old and I was planning to root it in the next days... Now I'm not expert just try to figure it out.
I tried different system to auto root via different apps, some using the PC some using directly the phone, I never get any success...
尚雷諾 said:
Thanks for your answer, I have to say I properly unlocked the phone so I do not think there is a way I messed up with this step as when I start bootloader it clearly shows on the top of the screen ''UNLOCKED".
When I flashed recovery on my phone I had no errors prompted or any message of failure. The process went well until a success notification.
Now when I start my phone into bootloader I repeat, I clearly see that recovery has been installed but when I attempt to start it then I'll be almost instantly brought back to the bootloader screen... now I started to wonder if... if an update of android could cause this kind of issue? The point is my phone is using android 4.4.4 and not the factory version 4.4.2. I remember having updated my android version which was perhaps a mistake as this phone is not very old and I was planning to root it in the next days... Now I'm not expert just try to figure it out.
I tried different system to auto root via different apps, some using the PC some using directly the phone, I never get any success...
Click to expand...
Click to collapse
Ok, please try twrp from Original Android Development tread (it works for me, mind, I'd question it's stability) or Philz recovery (sorry, I found only Chinese, but it's for verivication only: h...ps://drive.google.com/file/d/0BygOvRquk4z8S05kRC1XMXdSbXM/view?usp=sharing - please adjust tt in address - rookie rules).
I'd suggest test running from Fastboot: fastboot boot custom_recovery.img - replace with actual file name from directory you're running terminal.
This shall verify if it's problem with recovery file or any remaining protection...
T0ark said:
Ok, please try twrp from Original Android Development tread (it works for me, mind, I'd question it's stability) or Philz recovery (sorry, I found only Chinese, but it's for verivication only: h...ps://drive.google.com/file/d/0BygOvRquk4z8S05kRC1XMXdSbXM/view?usp=sharing - please adjust tt in address - rookie rules).
I'd suggest test running from Fastboot: fastboot boot custom_recovery.img - replace with actual file name from directory you're running terminal.
This shall verify if it's problem with recovery file or any remaining protection...
Click to expand...
Click to collapse
Does having S-ON bother? I was also wondering about that but all tutorials I found no one mentions anything about the S-ON or S-OFF thing.
But I do have a S-ON under UNLOCKED
what is stock recovery.img name
i dont know what is the real stock recovery.img name.
htc desire 820q dualsim
I can't root my htc desire 820q by this method, is any alternative way?
I just root my phone with same procedure but my phone still show s-on..... How can i s-off my phone.....

LG G4 H815 stuck, download mode only, no adb

Hello hello,
I unlocked bootloader, installed TWRP 2.8.7.0 (adb -> fastboot method) and then I flashed SuperSU 2.46 zip. After reboot from TWRP my phone stuck.
I can't access TWRP or i don't know how to…
System isn't starting BUT sometimes after few minutes of seeing LG logo i see standard wallpaper and suddenly animation freezes. That's all.
When i go to recovery mode (voldown+power, release power and press power again) I can "do" factory reset. I choose 2xYES and i see green android. Then phone is restarting but i should enter to TWRP, right?
I tried to flash stock system (kdz, tot, dz) via:
- LG Flash Tool 2014
- LG Flash Tool 1.8.6.527
- LGUP
- LG Bridge
but nothing…
My phone PID and IMEI is null :/ (and "CUMSS" to :?)
I tried fix that with QPST (2 different versions) but in device manager my phone is only detected as COM port. No "Android Device". I can't read and write anything…
adb isn't working
I tried all USB 2.0 ports, different drivers, roms (even not for 815), dlls.
I fought 3 days and still have brick, not smartphone
I have only download mode working.
I can send commands to com port (Send_Command.exe) but sometimes nothing happen, sometimes i see "fail" after sent command.
Any ideas? Can I install recovery through download mode? Or maybe somebody know how to send files to phone in download mode but without adb?
I had stock rom MM V20L. What else you need to know?
Thanks for any suggestions, sorry for chaos in post and my english.
After trying different roms in different programs with 3 versions of dlls and different drivers…
I found solution: just reinstalled .NET Framework and then finally i flashed by LGUP (refurbish, v20L, kdz, dll 0.0.3.23)!
Welcome back H815
2 0 said:
After trying different roms in different programs with 3 versions of dlls and different drivers…
I found solution: just reinstalled .NET Framework and then finally i flashed by LGUP (refurbish, v20L, kdz, dll 0.0.3.23)!
Welcome back H815
Click to expand...
Click to collapse
where did you founf v20L kdz i need it because my phone wont flash any kdz i think its to prevent downgrades
https://lg-firmwares.com/lg-h815-firmwares/
Try some from skdubg's link. This is probable the same as mine
PLS Europe PL/Poland H81520l_00_0928.kdz 1.68 G 2016-11-25
Click to expand...
Click to collapse
download-file/?fileId=4325 I can't post links
This is MD5 of my file 8f685baf42869c50ec5f1b7770aa3957 *H81520l_00_0928.kdz
If you still can't flash then i will upload my kdz somewhere. GL
LG G4 Model F500L Stuck on download mode After Downgrade
Hi
i have a problem with my LG G4 Model F500L i try to downgrade from Marsmallow to Lolilpop By Flashing with LGUP Tool when i flash it. it error at 16% boot fail. So i disconnect USB and pull out battery and when i turn on it stuck on download mode.. i have try to flash with any firmware and any LG Tools but it's still fail at writing boot step i had try with Optopus box but it's still fail at wrting boot fail what is the problem . i need help now.... i just bought my phone for a week. Thanks for your helping ....

Blackview BV9000 Pro-F ROOT SUCCESS [TWRP + Magisk v16 + Stock Rom]

EDIT: included rough procedures for OEM unlocking, and updated link to recovery-verified.img (Sorry for uploading the wrong file ><)
Hi all bv9000 pro Users!
Recently I went on a journey to root this awesome rugged phone with one purspose: to remove that F*@(#&$ god awful loud annoying sound triggered by the OS when you use a camera app to take a picture + the boot startup sound (A bug blackview hasn't gotten around to fixing).
I successfully managed to port TWRP 3.1.1 from the Blackview bv8000 Pro and run it on the Blackview bv9000 Pro-f!
I've then managed to flash in Magisk to gain root access.
DISCLAIMER: I do not take responsibility for any bricked phones caused by the process, do so at your own risk (yadayadayada).
NOTE 1: Although I've got it running on the bv9000 Pro-F, this image should also work for the non-fullHD version, if someone can test this I'd be happy.
The link to the stock ROM (with the modified recovery img) can be found in the post below.
NOTE 2: No need to download anything other than what I've listed, Magisk is included in my custom recovery to circumvent the need to load the devices encrypted storage (or any other external storage) nothing stops you from mounting external usb storage.
What you'll need:
- USB Mouse (As there is no touchscreen input support, your device should have come with a usb-c otg cable so there's no problem here!)
- MediaTek SP Flash tools (I'd recommend the latest version) https://spflashtool.com/
- unlocked bootloader (You should be able to do this via the developer settings -> unlock OEM Bootloader)
EDIT: To unlock the boot loader, do the following:
1) Go to settings -> unlock OEM Bootloader (tick)
2) plug your device in (assuming you have ADB installed), use adb to access fastboot via. command prompt:
"adb reboot bootloader"
Then once the device is rebooted into fastboot mode
"fastboot oem unlock"
KEEP IN MIND THIS WILL REMOVE ANY FILES, so back them up
- I've done this with windows, but you should be able to repeat with linux no problems!
- A little patience
Pre-preparation:
First install any updates and back up your data (it's just easiest to use the google cloud backup as restoring becomes easy as pie, updating also fixes the setup wizard crashing on first setup). This is necessary because OTA updates cannot be performed with TWRP recovery, and flashing TWRP before doing OTA updates will flick the device into a recovery boot loop.
Install the SP Flash tools, and the MediaTek VCOM Drivers
(I won't link the specifics here, a quick google search should be able to help you, just note you might need to disable driver signature enforcement)
Two options for flashing:
1)
My Full Stock ROM already pre-prepared for flashing:
Patched ROM
No need for extra prep here! you should just be able to load the scatter
2)
My custom patched TWRP stock rom: recovery-verified.img
Blackiew's stock rom: stock rom
- Download the stock rom, backup the recovery-verified.img in the R06 folder, and then replace it with my custom patched TWRP stock rom (file name should be the same).
- Run "CheckSum_Gen.exe" once you replaced the file, it will generate the necessary checksum to allow SP flash tools to successfully flash recovery.
Once you've done with the pre-prep, switch off your device, take a deep breath and you're ready to go!
Steps!
1) Load up SP Flash Tools, select the android scatter file you've downloaded in the R06 folder
2) Select Download Only (I MEAN IT, FORMATTING WILL REMOVE YOUR IMEI AND RENDER THE PHONE USELESS)
3) Deselect everything but recovery (You only want to flash this)
4) Hit download
https://pasteboard.co/HkufwZZ.png
5) Hold volume up + power and plug in your phone, keep the volume up button held
6) very quickly the flash should be complete, and you should be greeted with a big ol' green tick to verify
https://pasteboard.co/HkuiTBB.png
7) Once you're done, remove your USB cable, plug in the OTG then we proceed to flash magisk
8) Hold power + volume up until you reach the bootloader, then use the menu to select recovery
9) You *should* be greeted with the TWRP recovery screen (Which is great success! )
DON'T PANIC IF YOU CANNOT USE THE TOUCH SCREEN, the kernel I've patched is missing this, seems the driver is different between touch screens, just plug in your OTG mouse to continue from here!
10) Use your mouse to first hit cancel, we don't need to decrypt the user data storage.
11) But oh no! it's all in Russian (no problem, Next step sorts that)
12) Use your mouse to navigate the menus as shown here to change to English! (or your preferred language) Change Language
13) Click install, then navigate up folder levels until you are in the root directory
14) scroll down and click on Magisk.zip, install it, allow it to install any apps as system apps (because this will then install to the system image, not the userdata)
15) reboot the phone (if it hasn't rebooted already)
16) You should be able to boot into your usual phones OS, if you don't see Magisk listed in your phone apps, just download it from here:
Magisk Manager
17) Congratulations! You should have complete root access :laugh::laugh::laugh:
Feel free to express your thanks, or list any problems you have, but keep in mind my studies take all my life, so I may not be able to help with all the problems you have
Congrats! Would it work on the BV9000 HD version?
Hi!
From what I've seen they both run the helio p25 chip
(Just a difference in RAM size) so it should.
You're more than welcome to try.
Just keep a backup of the original ROMs recovery. If something goes wrong during the boot to recovery you can easily re flash
hi i tried both optinos but they didn't work for me
I tried the first and the second options and it was showed me same error:
ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
I tried download only, format all and download, if i install original ROM its installing without problems!
In settings-> developer options -> OEM unlocking is enabled
can someone give me tips if I'm doing something wrong. thanks
My phone is Blackview BV9000PRO-F
Hello,
i have the blackview 9000 pro Hd (not full hd)
i first tried your prepared patched rom = not working (get erorrers in step 6)
then i chose step 2 and i was thinking to use the stock rom from the NOT full hd rom
now i get a green screen from the flashing: but after rebooting in recovery nothing happens, just normal reboot then
perhaps this is not so clair for me:
- Download the stock rom, backup the recovery-verified.img in the R06 folder, and then replace it with my custom patched TWRP stock rom (file name should be the same).
- Run "CheckSum_Gen.exe" once you replaced the file, it will generate the necessary checksum to allow SP flash tools to successfully flash recovery.
the file name you posted here " My custom patched TWRP stock rom: recovery-verified.img" is ramdisk-recovery.img
i replaced the ramdisk-recovery.img... it is not clair need to replace recovery-verified.img to?
>I tried the first and the second options and it was >showed me same error:
>ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
> tried download only, format all and download, if i install >original ROM its installing without problems!
>can someone give me tips if I'm doing something wrong. >thanks
>My phone is Blackview BV9000PRO-F
Hi, you need to unlock the OEM bootloader, if this is still locked it will prevent the flashing of custom ROMS.
I might've missed this step, will update post as necessary.
>
dingsje said:
Hello,
>i have the blackview 9000 pro Hd (not full hd)
>i first tried your prepared patched rom = not working >(get erorrers in step 6)
>then i chose step 2 and i was thinking to use the stock >rom from the NOT full hd rom
>now i get a green screen from the flashing: but after >rebooting in recovery nothing happens, just normal >reboot then
>perhaps this is not so clair for me:
>- Download the stock rom, backup the recovery->verified.img in the R06 folder, and then replace it with >my custom patched TWRP stock rom (file name should >be the same).
>- Run "CheckSum_Gen.exe" once you replaced the file, >it will generate the necessary checksum to allow SP >flash tools to successfully flash recovery.
>the file name you posted here " My custom patched >TWRP stock rom: recovery-verified.img" is ramdisk->recovery.img
>i replaced the ramdisk-recovery.img... it is not clair >need to replace recovery-verified.img to?
Click to expand...
Click to collapse
Hi,
I've uploaded the wrong file, the uploaded file should be recovery-verified.img.
I'm uploading a new file and will correct the link now,
Please accept my apologies ><
hyperlethalvector92 said:
>I tried the first and the second options and it was >showed me same error:
>ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
> tried download only, format all and download, if i install >original ROM its installing without problems!
>can someone give me tips if I'm doing something wrong. >thanks
>My phone is Blackview BV9000PRO-F
Hi, you need to unlock the OEM bootloader, if this is still locked it will prevent the flashing of custom ROMS.
I might've missed this step, will update post as necessary.
Click to expand...
Click to collapse
I already did this step:
Enable developer options-> OEM unlocking is enabled
Is that enough for this MTK phone to be unlocked the bootloader ?
And tried the both options but the results are same.
I have been unlocking bootloaders on many phones but first time MTK phones. If i try with adb commands it recognize when is in the android with command adb devices and show my device but if I try reboot bootloader and check in device manager in windows its show its connected and drives are correct but if i try to show the devices, it doesn't show any device connected
Hi,
You need to install fastboot drivers once it's in bootloader mode,
then use fastboot, not adb.
"fastboot oem unlock"
Then follow instructions.
simply doing settings -> oem unlock won't unlock the bootloader, it allows you to do so later via. fastboot
Check the original post, I've added the extra instructions sorry about the confusion!
Thanks a lot. I finally succeeded to unlock the bootloader and root my phone and install the magisk.. I did without use your rom just I unlocked the bootloader and install your twrp file and after in the recovery mode i format the data and istall magic and i still have the last updated android.
I hope this it ill help to other people. Cheers
zlatkomas said:
Thanks a lot. I finally succeeded to unlock the bootloader and root my phone and install the magisk.. I did without use your rom just I unlocked the bootloader and install your twrp file and after in the recovery mode i format the data and istall magic and i still have the last updated android.
I hope this it ill help to other people. Cheers
Click to expand...
Click to collapse
I'm glad ^______^
Enjoy your rooted phone
I used this video to root my bv9000 pro hd
much easier than this above, i think it works to on bv9000 pro fhd
https://www.youtube.com/watch?v=c48ISLPjn4Q
Congratulations .... I need a tip,.
And, brother, thank you very much. Worked perfectly.
But first I would like to get you a tip ..
One of the main reasons I have done all this complicated process was to be able to disable the crap of the loud music that plays when the device is started.
I want complete silence at startup.
How do I disable this ****?
Code for Huawei mobile Wi-Fi e5577s-321
Pls help unlock my Huawei mobile Wi-Fi e5577s-321
Imei
860782038163889
TWRP looping after OTA update
My dear, the procedure worked very well, until an OTA update was downloaded.
You are now looping on TWRP. How do I get out of this?
:crying:
help!
i missed to run wireless software update,so ROM clashed.
How can i re-install custom ROM?
mackie_ma said:
help!
i missed to run wireless software update,so ROM clashed.
How can i re-install custom ROM?
Click to expand...
Click to collapse
Hi guys, lemme apologize for disappearing, life and whatnot!
For those stuck in a TWRP boot loop, simply restoring the original recovery then restarting the phone will be enough to fix the problem.
(Actually you really don't need TWRP after the phone is rooted, maybe I should update the guide?)
Many Thanks
First off, thank you for your hard work. Loved the "**** it we have an OTG cable let's use it" haha. It works fine for me.
Second, do you happen to know if someone has ported Oreo on our bv9000 ? Or do you know of any ETA ?
Thanks again,
Cheers
Anyone tried on the BV9000 Pro? Don't think mine is 'F' OR 'Fhd'.... I must have first model brought out...
Ugh.. Windows and Drivers?!?!
I keep getting Driver not Recognized in Windows 7 Pro X86.
I installed the latest vcom/usb drivers, in legacy also. No Go.
I installed from several other sources the drivers, including the Automatic Mediatek driver install. No Go.
So if anyone has a tip for me, please let me know because once more Windows is proving itself ridiculous. I can't even get to the storage of my phone. Did something change with a Windows Update that it's not allowed anymore?
I put my BV9000 Pro in OEM Unlock and USB Debugging. I backupped everything. My phone is ready for it. It's as ready as Amy having coitus with Sheldon for the first time.

How To Guide Asus ROG Phone 6 / 6 Pro [ROOT GUIDE/SUP]

Hey, I have rooted a few of these and helped a few people as well and feel confident I can help most anyone with the problems they face rooting this beast. Also I'm posting this to have a place I can send people I help so I don't have to keep retyping stuff. From what I can tell the steps to root this phone are almost the same as the last model.
For now I will just post rough steps and use this as a place to provide support to people.
STEPS: (Rough guide/ please use other sources of information also)
1.) Fully update your phone
2.) Download the bootloader unlock app from asus official website. Also download and install Magisk. I recommend canary release.
3.) Get a patched boot.img or learn with a search engine how to extract the boot.img from payload.bin which can be found inside the large firmware zip files on the asus website (same link as unlock app but click firmware). Follow a tutorial.
4.) Turn on adb settings, and roboot into fastboot. adb reboot bootloader
For me for windows I needed to download fastboot drivers and go to device manager and install/update them.
5.) Unlock the bootloader with: fastboot flashing unlock
6.) Flash the patched boot image with: fastboot flash boot magisk_patched####.img
7.) Download safteynetfix and go to Magisk -> Modules and install safteynetfix.zip. Then go to Magisk -> Settings and enable Zygisk, and Enforce Denylist. Then turn on airplane mode and click on Configure deny list. add apps that are not working with root here, then delete their storage in App->Settings and reboot, remove airplane mode, and force close the apps in question.
For example select Show -> system apps. and add Google Play Store and Google play services to the deny list. Then go to App->Settings and delete both of those app's storage. Then when you reboot and remove airplane mode and force close google play and reopen it and go to Google Play -> Settings -> About you should see at the bottom "Device is certified".
If this last step does not show certified you did something wrong or I described it bad, check with a tutorial how to set up safteynet + configure deny list. Or post here and I will help you.
FINAL NOTE: After this the OTA updates that ASUS pushes will not be downloaded by our phone. We need to go to the same website we downloaded the unlock app from and we need to download the firmware files (WW for me) and put them in /sdcard/UL-ASUS-Al2201....zip and reboot. We then need to repeat the root process and the Magisk module process. Also I think we need to do this for every update along the way and cannot skip to the most recent update but not sure.
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
leathan said:
Hey, I have rooted a few of these and helped a few people as well and feel confident I can help most anyone with the problems they face rooting this beast. Also I'm posting this to have a place I can send people I help so I don't have to keep retyping stuff. From what I can tell the steps to root this phone are almost the same as the last model.
For now I will just post rough steps and use this as a place to provide support to people.
STEPS: (Rough guide/ please use other sources of information also)
1.) Fully update your phone
2.) Download the bootloader unlock app from asus official website. Also download and install Magisk. I recommend canary release.
3.) Get a patched boot.img or learn with a search engine how to extract the boot.img from payload.bin which can be found inside the large firmware zip files on the asus website (same link as unlock app but click firmware). Follow a tutorial.
4.) Turn on adb settings, and roboot into fastboot. adb reboot bootloader
For me for windows I needed to download fastboot drivers and go to device manager and install/update them.
5.) Unlock the bootloader with: fastboot flashing unlock
6.) Flash the patched boot image with: fastboot flash boot magisk_patched####.img
7.) Download safteynetfix and go to Magisk -> Modules and install safteynetfix.zip. Then go to Magisk -> Settings and enable Zygisk, and Enforce Denylist. Then turn on airplane mode and click on Configure deny list. add apps that are not working with root here, then delete their storage in App->Settings and reboot, remove airplane mode, and force close the apps in question.
For example select Show -> system apps. and add Google Play Store and Google play services to the deny list. Then go to App->Settings and delete both of those app's storage. Then when you reboot and remove airplane mode and force close google play and reopen it and go to Google Play -> Settings -> About you should see at the bottom "Device is certified".
If this last step does not show certified you did something wrong or I described it bad, check with a tutorial how to set up safteynet + configure deny list. Or post here and I will help you.
FINAL NOTE: After this the OTA updates that ASUS pushes will not be downloaded by our phone. We need to go to the same website we downloaded the unlock app from and we need to download the firmware files (WW for me) and put them in /sdcard/UL-ASUS-Al2201....zip and reboot. We then need to repeat the root process and the Magisk module process. Also I think we need to do this for every update along the way and cannot skip to the most recent update but not sure.
Click to expand...
Click to collapse
Sorry, I messed with the reply: it's my previous post.
fux1976 said:
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
Click to expand...
Click to collapse
I cant really help as I can't reproduce those problems. My phone was originally WW, but did you try to apply the non latest update? Then work your way up to 160?
fux1976 said:
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
Click to expand...
Click to collapse
To answer some other stuff, did you try looking in Device manager and maker sure your android device/asus rog is listed without an exclamation? I was having similar issues on windows until I installed the usb drivers. You should be able to run fastboot devices from within the bootloader menu.
leathan said:
I cant really help as I can't reproduce those problems. My phone was originally WW, but did you try to apply the non latest update? Then work your way up to 160?
Click to expand...
Click to collapse
Hi there! I flashed raw .134 and then the magisk patched boot .img as dedcribed in one forums guide, then tried to upgrade to .160 when I saw it on the asus support page. I was thinking of using edl and hard reset the phone and start again (in the next few days as it take times). I found a guide and tools (don't know if I can post the external link here). Do you think that could work? I downloaded raw .160 from the asus site (then i'll reflash the magisk patched boot).
To be honest it tickles me to try out this things (hoping not to end up with a brick of course)
leathan said:
I cant really help as I can't reproduce those problems. My phone was originally WW, but did you try to apply the non latest update? Then work your way up to 160?
Click to expand...
Click to collapse
Hi there! I flashed raw .134 and then the magisk patched boot .img as dedcribed in one forums guide, then tried to upgrade to .160 when I saw it on the asus support page. I was thinking of using edl and hard reset the phone and start again (in the next few days as it take times). I found a guide and tools (don't know if I can post the external link here). Do you think that could work? I downloaded raw .160 from the asus site (then i'll reflash the magisk patched boot).
To be honest it tickles me to try out this things (hoping not to end up with a brick of course
leathan said:
To answer some other stuff, did you try looking in Device manager and maker sure your android device/asus rog is listed without an exclamation? I was having similar issues on windows until I installed the usb drivers. You should be able to run fastboot devices from within the bootloader menu.
Click to expand...
Click to collapse
I fortunately have several pcs so i switched to the one with no drivers issues. As written I can only use fastboot commands when the phone is in fastbootd mode (sort of recover looking screen). The bootloader mode (one line, capital letters) is not recognized by pc..that's why I was thinking about EDL and reflashing the first level boot. Is it hazardous?
fux1976 said:
Hi there! I flashed raw .134 and then the magisk patched boot .img as dedcribed in one forums guide, then tried to upgrade to .160 when I saw it on the asus support page. I was thinking of using edl and hard reset the phone and start again (in the next few days as it take times). I found a guide and tools (don't know if I can post the external link here). Do you think that could work? I downloaded raw .160 from the asus site (then i'll reflash the magisk patched boot).
To be honest it tickles me to try out this things (hoping not to end up with a brick of course
I fortunately have several pcs so i switched to the one with no drivers issues. As written I can only use fastboot commands when the phone is in fastbootd mode (sort of recover looking screen). The bootloader mode (one line, capital letters) is not recognized by pc..that's why I was thinking about EDL and reflashing the first level boot. Is it hazardous?
Click to expand...
Click to collapse
I would continue to try to get my PC to recognize my Phone in bootloader mode using the drivers I linked. After helping 2 people who had windows, on both of their machines, I had to install the drives. On linux is just worked.
Also the raw image that I linked is of 93 so you should have needed to download 95, 97, 134, and 160 from asus. Then after 160 I repatched the boot img and re-rooted.
There is another person who said after tencent -> WW she was able to update to 134 where she had some problem. But I don't know how to reproduce that stuff Hope you figure it out though.
leathan said:
I would continue to try to get my PC to recognize my Phone in bootloader mode using the drivers I linked. After helping 2 people who had windows, on both of their machines, I had to install the drives. On linux is just worked.
Also the raw image that I linked is of 93 so you should have needed to download 95, 97, 134, and 160 from asus. Then after 160 I repatched the boot img and re-rooted.
There is another person who said after tencent -> WW she was able to update to 134 where she had some problem. But I don't know how to reproduce that stuff Hope you figure it out though.
Click to expand...
Click to collapse
Phone looks certified, country WW, safetynet passed and upgraded to .160. Only 2 problema left: voice dictation of GBoaed and Android auto not working.
I tried several ways but they didn't solve. Voice dictation worked and then stopped: I guess something interferes... Android Auto app crashes although phone connects to car and is recognised.
Very strange behaviour...
Do you have any idea on how to reflash last .160 zip without twrp? Once installed it gets ignored by system when saved in home directory...
Everything else is working properly.
Isn't Android Auto no more (i.e discontinued).....?
elmor0 said:
Isn't Android Auto no more (i.e discontinued).....?
Click to expand...
Click to collapse
what?!? where did you hear that? It'just something causing problems (compatibility issues with app or setting: magisk, modules, adaway, skipad, disabled system apps and so on). If I could manage to reflash the stock rom it'll work again (I hope)
fux1976 said:
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
Click to expand...
Click to collapse
Keep spamming flashall_aft.cmd until it works or try flashing other raw.
This worked for me if your able to get fastboot devices listed in adb firstly
finallau said:
Keep spamming flashall_aft.cmd until it works or try flashing other raw.
This worked for me if your able to get fastboot devices listed in adb firstly
Click to expand...
Click to collapse
I only have raw for .143 but I updated to .160*...can I use the previous version or do I get bricked? I don't trust anti roll back mechanism. I can live with this 2 "limitations" waiting for twrp and then be able to flash zip with no hassle.
*I downloaded source code from the Asus site but not sure how to use it (and unzipped is around 10 gb )
Thank you for this! I've been out of the root game for years but noticed with your post that I can hide root from Google Pay and my banking apps, so thinking of trying this. One question though - you mentioned that official updates need to be manually downloaded and the phone re-rooted. Would this wipe the phone each time?
fastboot driver doesnt support win64
Will the phone do a factory reset after unlocking the bootloader?
Anyone know if I root my phone following these instructions, will it factory reset or wipe my data partition? Sorry it's been a while since I rooted any phone, and I am excited about going this route
MrKioFLow said:
Anyone know if I root my phone following these instructions, will it factory reset or wipe my data partition? Sorry it's been a while since I rooted any phone, and I am excited about going this route
Click to expand...
Click to collapse
Yes, if you unlock the bootloader using the bootloader unlock app (which is a step that is missing in the original post), your phone will perform factory reset.
Troubleshooting​
Once you boot into the bootloader with the adb reboot bootloader command, stay on the screen with the green START. Do not navigate to the fastbootd.
Use the side USB port to connect to your computer - not the bottom one.
Run the adb and fastboot commands in Command Prompt as Administrator.
Before you reboot into bootloader, remove Lock screen in Settings.
If you execute fastboot flashing unlock and you got FAILED (remote: 'permission denied'), just ignore it.
It's always better to install the latest updates, then download the firmware to your PC from ASUS Webpage and extract the boot.img and patch it in Magisk in the phone using this tutorial.
Thanks for the guide! Should add that you have to use the side port for fastboot to see the device. Was stuck for a while trying to figure out why neither mac nor pc couldn't find it when it was in bootloader mode - it was because I was using the bottom port lol!
Also if you want to disable verity and verification for the verified boot images, you have to do for both vbmeta.img and vbmeta_system.img. Didn't boot for me until I did that, and had to do an additional factory reset from recovery because of this.

Categories

Resources