hia all! I need a big help! I was following the procedure toi get the root to the stock rom. First strage thing was my usb debuggig option under developer option was gray so not selectable. I decided to proceed anyway and I've unlocked the bootloader (with the proper command I've checked and it was unlocked). hte first strange thing was that i did't get the reboot after unlocking as reported in the guide. but i've rebooted manually and then I've installed TWRP and everything was ok; then I've proceeded with installing SUper SU to get the root permission and here came the problem; after installed the zip via TWRP, during the reboot I realize I was stuck in the boot logo the rotating square/traingle and circle. PANIC. I've tried almost everything, also trying a adb sideload flash with latest oxygen but seems not working...(maybe usb debugging not enalbe is the reason for all my problems?) what went wrong? and what do I have to do now? please help!
Andrea
Find an OTG cable, place the full 2.0.2 OOS rom on a USB key, go to recovery and don't forget to mount USB-OTG then flash the rom...
I have bricked my OPO several times by tweaking it^^
So I keep an usb key with rom, Xposed, Ti backup etc... and if there is a problem, just plug your key, it's easier than using fastboot commands from a computer...
I'm currently waiting for my OTG cable for OPT especially for this use.
******************Root Recovery Doogee X5 max pro*******************
Your waiting Time IS Now Finished Here is Complete Guide to Root Doogee X5 Max Pro install twrp And More,
Hit :good:
ADB & Fastboot
Before doing most things mentioned below you will need "adb" and "fastboot" installed. Two of your options are to install the Android SDK Tools or the Minimal ADB and Fastboot tool. If you are somewhat new to this I highly recommend the second one. Go here, download the latest version (1.3.1 as of this writing), and install it. When setup is complete you should have an icon for the Minimal ADB and Fastboot tool.
Note: I highly recommend you add "C:\Program Files (x86)\Minimal ADB and Fastboot" to your PATH variable in Windows. This way you can open a Command Prompt anywhere and use adb or fastboot.
1) Unlock Bootloader
Power on the phone and skip through all of the setup options
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly
Type fastboot oem unlock
Press Volume Up to say Yes and wait for this to finish
Type fastboot getvar all and look for (bootloader) unlocked: yes
Type fastboot reboot
You should see your phone reboot a couple times as it erases the phone
Install twrp-
Power on the phone
You can configure your phone now or just skip through all of the setup options and do that later
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt to wherever you extracted the .img file
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly, rename twrp to recovery.img
type fastboot flash recovery recovery.img to flash recovery
Type fastboot reboot
Rooting-
Download BETA-SuperSU.zip and save it to the phone's internal memory or an inserted microSD card
Plug the phone in to your PC
Open a Command Prompt
Type adb reboot recovery
You should now be in twrp. Go to Install zip, find SuperSU.zip, and install it
When it finishes go to Go Back -> Reboot Phone -> No
Once the phone boots up launch SuperSU and configure it as you like
Other Solutions-
i have doogee x5 max-s (i geuss limited editon in algeria ) with mtk6735 . i do evrything and all steps but when i reboot to recovery mode i have ( no command ) in the screen .... how to fix that ? sorry for my ****ty english XD
I had the same Issue but i have found a solution!
After you have flashed the twrp recovery, dont reboot the phone! the "recovery.sh" will replace the twrp on every boot!
Just pull off the battery after flashing, disconnect usb and put the battery back in to the phone.
Now get in to the recovery by pressing volume up and power button together until the select bootmode menue appears.
select recovery with the volume up button and enter with the volume down button.
and now you should be in the twrp main menue.
i hope it works for you too!
greetz from the lizard
It does not work from step 12, all the drives are correctly installed and windows recognizes the cell, the recovery image is in the internal memory and also in the sd but of the error "can not load Recovery.img". I tried all the tutorials on the net to do root and nothing worked.The flash does not recognize to pass the recovery also the installed drivers because windows recognizes the cell phone.
pitro1 said:
It does not work from step 12, all the drives are correctly installed and windows recognizes the cell, the recovery image is in the internal memory and also in the sd but of the error "can not load Recovery.img". I tried all the tutorials on the net to do root and nothing worked.The flash does not recognize to pass the recovery also the installed drivers because windows recognizes the cell phone.
Click to expand...
Click to collapse
use sp flash tools to flash recovery, scatter also added with twrp
Flash does not pass the file in the download only option, the process does not start. I reinstalled ROM by firmware mode all ok, but the process of passing recovery on command 12 and 13 of the error message. I manually copied the recovery to the sd and internal memory but also from the error. Does not find the file speaks that it is not a command found.
pitro1 said:
It does not work from step 12, "can not load Recovery.img".
Click to expand...
Click to collapse
Don't use Capital R's
fastboot flash Recovery Recovery.img
Code:
fastboot flash recovery recovery.img
Doogee X5 Max Pro - Update 01/16/2017 + TWRP-3-0-2 & SuperSU-v2.79
Working root for Update 01/16/2017
Title: Doogee X5 Max Pro
Listed: 01/19/2017 11:21 pm
ROM Version: ROM Android 6.0
Doogee X5 Max Pro - Update 01/16/2017
TWRP-3-0-2 + SuperSU-v2.79
Use This Version Flashtool
SP_Flash_Tool_v5.1620.00.000
XN Logos said:
use sp flash tools to flash recovery, scatter also added with twrp
Click to expand...
Click to collapse
Until today I could not do root on x5 max pro. In the method below even downloading the twrp when starting with the power + volume down button start with a menu in Chinese and if you start with volume up + power goes in the default recovery mode.
Same as Pitro1 I am on 16.01 update and I cannot install twrp no matter what I try.
I tried x32 and x64. I tried rebooting directly on recovery or first load system and then adb reboot recovery. I tried to format all first (now I lost my Imei and so on lol). I downgraded and updated again. Downgrading works only with 26.12 version. All others are giving me Colorado lines on the screen and nothing else...
OEM unlock, file transfer, adb, fastboot, drivers detection, are all working good. Only I cannot install twrp...
Also I cannot write nvram nor with SN Writer 2.1504 nor with Imei & SN Writer 1.7.2, MetaAP mode fails all the time...
I'm just about to send it back...
How i rooted my Doogee X5 Max Pro
How i rooted my Doogee X5 Max Pro
- Unlock Bootloader tutorial in the first post By XN Logos.
- Updated ROM to Android 6 with SP FLASH TOOLS V.5.16.20
- boot phone for 1st start and activate Developer and USB debugging
- Installed TWRP-32x + SuperSu with SP FLASH TOOLS V.5.16.20
i returned the phone as i had no imei anymore.
i got a new one, i did not put any sim or whatsoever, i just unlocked bootloader, and updated to 16.01 version
then i tried to install twrp via fastboot and it did not work, i did it with sp flash tools as advised and removing the battery prior (don't forget to!). it worked !
Stripe_nl said:
How i rooted my Doogee X5 Max Pro
- Unlock Bootloader tutorial in the first post By XN Logos.
- Updated ROM to Android 6 with SP FLASH TOOLS V.5.16.20
- boot phone for 1st start and activate Developer and USB debugging
- Installed TWRP-32x + SuperSu with SP FLASH TOOLS V.5.16.20
Click to expand...
Click to collapse
How old is your phone and what build version was it at before you started? Because this doesn't work on mine. Which of the "Android 6" ROMs did you flash to start with as I've tried flashing mine back to an earlier one in case it's something with the later stuff that my phone has come with but they either don't make a difference or they won't even boot.
I tried the method in the first post here and the phone wouldn't even boot (switch on and you get the Doogee logo in silver for a few seconds then it reboots and does the same again). I had to flash the stock ROM from NeedROM to get it working again.
I've tried flashing TWRPx32 and x64 available NeedROM both with SPFlash tools and with ADB. Generally flashing it with ADB from the command line leaves the phone in that boot-loop. If I flash it with SPFlash when you try to boot into Bootloader afterwards you get the Doogee logo in silver for a few seconds then it seems to reboot again on it's own and boot normally - you don't even get the menu to choose Fastboot, Recovery or Normal. From then on trying to boot to the Bootloader gives you the menu but choosing Recovery gives you the standard recovery.
It's almost as if something is overwriting the recovery partition with the original after I flash TWRP onto it.
Anyone got any suggestions about where I might be going wrong or a way around whatever additional security they might have put in there?
Hi. I have tried to root my x5 max pro with flash tools to load TWRP, but it always restarts normally and the TWRP does not come out. I found you and I started to try this method to load the TWRP. Does everything good, unload bootloader and load recovery, but loading the TWRP gives me error .:
Device unauthorized.
This adb's $ ADB_VENDOR_KEYS is nor set; Try adb kil-server if that seems wrong
what I do?
rooting X5 Max pro in Ubuntu 16.04
Hi all, this is my first china phone and I basically bought it only to experiment, I'm a linux power user but this is the first time I 'play' with an android OS.
thanks to multiple guides and posts on this and other forums I'm getting somewhere and learning a lot about how to manage an android OS, I'm sharing a bit of info I unovered about doing this under ubuntu but I'm also stuck and in need of guidance, please help me.
Linux specific issues:
I'm running ubuntu 16.04 LTS, installed fastboot and adb tools from ubuntu repos, with these tools and no other modification to my system I could follow the tutorial on how to unlock the OEM bootloader with adb and fastboot.
accordingly to this post about SP flash tool in linux you might need to blacklist a modem manager module in order for SP flash tool to connect to the phone, you also need to install usb development tools (package libusb-dev) and check through dmesg that your linux OS can actually properly read mediatek usb devices.
After following the above mentioned instructions (both the linux sp flash tool tutorial and the bootloader unlocking howto) I could get SP flash tool linux (multiple version) to see the phone after you connect it while SP flash is downloading the new recovery image and flash it with an ok message.
If you get stuck with a BROM error 1013 remember to start sp flash tool with root privileges.
Phone specific issues:
I can get SP flash tool to flash my phone recovery with an ok message confirmation but the phone keeps rebooting with doogee recovery and not twrp. I'm on the newest stock ROM update (20170116) as of current post date. I've been using 32 bit TWRP images from multiple sources and linux version 5.1620 of spflash tool from their website
so my questions are as following:
1) after reading other posts I think I might have to play with different versions of SP flash tool and TWRP until I get the right combination, I think I might be using 64bit spflash tool for linux to flash a 32bit rom or something like that, can anybody confirm precise version number of the stock rom, TWRP and SP flash tool that worked out for you?
2) should I try to install the whole stock ROM posted in this chinadevices thread before trying to flash only TWRP recovery? please also check the linked thread for multiple custom ROM being ported to this phone, please also note that the full stock rom this poster uploaded (it's in the "all firmware" link) contains another flashing tools with chinese instruction called MultiDownloadTool.
www.china-devices.com/forum/index.php?threads/doogee-x5-max-pro-mt6737-custom-roms.20527/
3) I don't have access to a windows installation right now, but I do have a Win10 VM under Vmware workstation 12 pro, so I could try windows version of sp flash tool, do you guys think that USB passthrough would work?
ibrooks said:
How old is your phone and what build version was it at before you started? Because this doesn't work on mine. Which of the "Android 6" ROMs did you flash to start with as I've tried flashing mine back to an earlier one in case it's something with the later stuff that my phone has come with but they either don't make a difference or they won't even boot.
I tried the method in the first post here and the phone wouldn't even boot (switch on and you get the Doogee logo in silver for a few seconds then it reboots and does the same again). I had to flash the stock ROM from NeedROM to get it working again.
I've tried flashing TWRPx32 and x64 available NeedROM both with SPFlash tools and with ADB. Generally flashing it with ADB from the command line leaves the phone in that boot-loop. If I flash it with SPFlash when you try to boot into Bootloader afterwards you get the Doogee logo in silver for a few seconds then it seems to reboot again on it's own and boot normally - you don't even get the menu to choose Fastboot, Recovery or Normal. From then on trying to boot to the Bootloader gives you the menu but choosing Recovery gives you the standard recovery.
It's almost as if something is overwriting the recovery partition with the original after I flash TWRP onto it.
Anyone got any suggestions about where I might be going wrong or a way around whatever additional security they might have put in there?
Click to expand...
Click to collapse
Same here. May a work around would be finding out the oem commands in fastboot. I have seen a tutorial to get them, but you have to be root: https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/
I search a simple method
Why all so complicate? I am searching for a simple way to root.
For my old Doogee X5, I discovered just
update-ROOT-DOOGEE_X5.zip
Copy the zip to the micro-SD-card
Settings -> Phone info -> Update -> menu "update local" -> choose zip from micro-SD-card.
Start update.
That's all!
Now I search for such a simple solution for my new Doogee X5 MAX pro.
I do not want any methods with "volume down power", because my X5 MAX pro has the menus after "Volume down power" start in Chinese language.
Recovery TWRP x32
http://www.needrom.com/download/twrp-x32-rom/
http://www.needrom.com/category/doogee/serial-x-doogee/x5-max-pro/
This version finally works ! Thank you
Neaw said:
Recovery TWRP x32
http://www.needrom.com/download/twrp-x32-rom/
http://www.needrom.com/category/doogee/serial-x-doogee/x5-max-pro/
Click to expand...
Click to collapse
Hi there,
I just tried the first file you posted, (twrp-x32-rom), and this one works for me after all previous attempts to boot up TWRP failed. Thanks for the link !
What I had tried before:
I have a relatively new X5 Max Pro, which I ordered a week ago. I updated the firmware to the newest version (20170116) using the OTA update function.
Then I tried to flash TWRP using the files from "needrom.com" which seem to have worked on older versions of the phone/firmware, but did not work for the newer versions.
I tried 32bit and 64bit TWRP versions and flashed them with SP flash tool, but when pressing Vol+/Power the phone would not boot into TWRP recovery. Insted, when selecting "Recovery" from the boot menu, the phone would show the Doogee logo in silver, then blink once, then boot up normally. When repeating this process, then phone boots into Stock recovery, indicating that the TWRP I flashed was replaced by stock recovery.
However, I just flashed the recovery.img from "TWRP LATEST" (the first file posted by Neaw) with SP flash tools and was finally able to boot into TWRP. I installed the superSU-zip 2.79 included in the link, and I am now rooted. Once again, thanks for posting this :good:
Greetz, Ollek74
Doogee X5 MAX! SERIUS PROBLEM......
Hello Guys i have a serious problem with my phone.....i have Malware on it and i cant uninstall it or anything alse.....the worst thing is that my phone not responding in any connection except that charging.....i can't have access on my storage cause this is not allowed or gives the choice! i tried everything but nothing nor the usb debugging or anything else please give me your help!!!!
Hey guys, I'm at a lost here. I don't think I'm that stupid but I am following all steps from the guides to install TWRP without luck. I already managed to unlock my bootloader with Axon7Toolkit. I already certified that QUSB_Bulk driver is installed, I did it with Zadig, but when in EDL mode, even after killing adb, the axon7tool can't find it. I tried installing a zip with the toolkit but when I choose the package, the toolkit simply closes. Is that me? My phone?
Thank you!
gibawatts said:
Hey guys, I'm at a lost here. I don't think I'm that stupid but I am following all steps from the guides to install TWRP without luck. I already managed to unlock my bootloader with Axon7Toolkit. I already certified that QUSB_Bulk driver is installed, I did it with Zadig, but when in EDL mode, even after killing adb, the axon7tool can't find it. I tried installing a zip with the toolkit but when I choose the package, the toolkit simply closes. Is that me? My phone?
Thank you!
Click to expand...
Click to collapse
What software version are you on?
I was at latest nougat but I downgraded to B10
Doing it via fastboot never fails for me.
Get to fastboot put two img in adb folder (I rename it for ease of typing since I suck) rename to recovery.img
Type this cmd in adb
Fastboot flash recovery recovery.img
Reboot to recovery and root. Done deal
download 3.1.0.0 twrp into your download folder on your desktop enter fastboot into your phone open up your command prmt type fastboot devices, your phone should appear then type fastboot flash recovery then go to the twrp right click drag it into the command prmt air page and place it there. you should see the file then hit enter. It'll take like 5 seconds it's really fast then reboot t recovery. when in twrp it'll ask you to install it again say no and uncheck the to options. DONE.
After loads of stress and bangs on the table I managed to unlock, install TWRP, LOS and root. I removed every driver related to my cell phone, deleted everything I download from it and started from scratch. I installed TWRP via fastboot but wasn't able to enter recovery mode, than I mase the stupidity to lock the bootloader back and got stuck in that password screen. Then I gave another go with the toolkit, unlocked it again and, I don't know how or why, it finally booted TWRP. Now everything is OK. Glad to be back to "Nexus mode" after so many time.
Thank you!
I have a Axon 7 A2017U, bootloader unlocked. My recovery is corrupted after attempting to flash a older version of TWRP in recovery. I can no longer reboot into TWRP via recovery, it hangs at the ZTE powered by screen. I can't boot into the o/s, it too was corrupted while attempting to restore to stock using the DrakenFX's guide.
Booting into fastboot is a no go either, it just hangs at bootloader screen.
Any suggestions on where to go from here or how to fix the corrupted recovery?
You need to go into EDL mode and use MiFlash and flash a back to stock package. You can find a package here: https://androidfilehost.com/?w=files&flid=160532
Hello maybe i have same problem here. I have A2017G and maybe i have only woked unlocked bootloader. I dont think my EDL is working becouse i cant connect with ADB. Dont have any acces to recovery... i messed up step by step remember.
1. downloaded toolkit and woked fine - 2 installed drivers and working fine with EDL. 3 unlocked with no problems , 4 flashed TWRP with no problems and then i wanted to install lineage os. Downloaded last version lineage , and google apps and one file "A2017G_N_Modem.zip" and put all 3 files on my SD card. I wipe everything and then first installed modem file OK, but on second try with Lineage OS i have any errors and i just cant continue. After this i wanted to go back to original OS and i just locked my bootloader with axon toolkit and after restart i have acces only to Unlocked Bootloader. tryed everithing with axon7toolkit but nothing working. If i try to EDL mode when press volumeUP+volumeDOWN+power my phone have black screen and i thing is powered OFF.
OMFG i just typed "fastboot oem unlock" 5-6 time when i started phone to my bootloaders and now it unlocked and have acces to my TWRP.
Teet1 said:
You need to go into EDL mode and use MiFlash and flash a back to stock package. You can find a package here: https://androidfilehost.com/?w=files&flid=160532
Click to expand...
Click to collapse
Thanks, I flashed it with A2017U_B19-NOUGAT_FULL_EDL and was able to flashed twrp recovery. I was hoping the o/s would be fixed too but I get this error message as soon as o/s load "settings keeps stopping, close app". It appears it's a bad or incorrect stock file. I had to format data in TWRP recovery as the drive was encrypted. So now i'm back at square one.
Bad o/s but working recovery, so I attempted to flash these files to get back to stock but was unsuccessful. It would flash halfway and then just restarts and hung at the bootloader unlock screen.
A2017UV1.0.0B29_RollBackModded.zip
A2017UV1.1.0B32_bootstack_by_DrakenFX.zip
A2017UV1.1.0B32_StockSystem_by_DrakenFX.zip
Am I on the right track? Or should I be flashing with a different os variant?
freeb0rn said:
Hello maybe i have same problem here. I have A2017G and maybe i have only woked unlocked bootloader. I dont think my EDL is working becouse i cant connect with ADB. Dont have any acces to recovery... i messed up step by step remember.
1. downloaded toolkit and woked fine - 2 installed drivers and working fine with EDL. 3 unlocked with no problems , 4 flashed TWRP with no problems and then i wanted to install lineage os. Downloaded last version lineage , and google apps and one file "A2017G_N_Modem.zip" and put all 3 files on my SD card. I wipe everything and then first installed modem file OK, but on second try with Lineage OS i have any errors and i just cant continue. After this i wanted to go back to original OS and i just locked my bootloader with axon toolkit and after restart i have acces only to Unlocked Bootloader. tryed everithing with axon7toolkit but nothing working. If i try to EDL mode when press volumeUP+volumeDOWN+power my phone have black screen and i thing is powered OFF.
OMFG i just typed "fastboot oem unlock" 5-6 time when i started phone to my bootloaders and now it unlocked and have acces to my TWRP.
Click to expand...
Click to collapse
So you didn't read all of the hurdles and warnings about locking the bootloader with non-stock firmware?
Plus you also didn't find out about the Universal Bootloader? Did you even read the installation steps???
You had an error 7, which is that you forgot to install the Universal Bootloader. Do so this time.
EDL has nothing to do with ADB. You can access it with the phone completely off... (volume up and down, and insert usb)
Problems with rooting, loading ROM then recovery & download images -some solutions
I started with stock LG v20 T-Mobile H91810P and followed this step by step & the original threads. I loaded the latest stock Oreo from H91820H from here instead of latest Nougat H91810U - Pie & some other versions had too many things not working.
In the process there were a few problems -the major ones are following with solutions, some from here:
1) The file H91810p rom (H91810p_00_0717.kdz) downloaded from here.
2) I lost root several times, but had TWRP. So I used adb sideload like:
Boot/start TWRP and the start ADB Sideload
Download Magisk-v16.0.zip and copy to adb directory.
On Windows PC connect Cell with USB and in CMD window type (copy/paste):
adb start-server
adb sideload "Magisk-v16.0.zip"And never update migisk after installing from above or will lose root. Also no need for SU.
3. Camera did not work and people could not hear me nor could I hear them when I picked up a call - A reboot/restart fixed it.
4. No need to download UPPERCUT (that is hard to download), because LGUP works fine without UPPERCUT.
I have 4 problems remaining -any help for solutions here is appreciated - especially exact type help please:
1) On LAF/Boot (original download) partition: Vol+ & connect to USB caused the download mode to come on for about 2 seconds and then TWRP (however I am glad that TWRP is here) -Prefer this to be the original download mode.
2) On Recovery patition: Vol- & connect to USB causes fastboot to come up. Flashed the recovery-twrp-h918-2018-10-18.img (renamed to recovery.img) to recovery partition using flashify and TWRP unsuccessfully. -Prefer this to be TWRP.
3) TWRP cannot access the Data partition. Rebuilt and reformatted Data from TWRP without success. -Prefer access to Data from TWRP.
4) At boot time: I like to get rid of the warning that my bootloader is unlocked. -I can live with this one.
After thoughts: Now that I am rooted on the latest stock Oreo H91820H -I am not sure what I want to load that I could not before?! overclocking the CPU or changing the hue on the display is not a big deal for me at all. & Yes I will uninstall some bloatware - but that is not so bad on this phone anyhow. Any good ideas or a better/later rom than H91820H that has all things working, do please let me know. I am glad that I rooted, ahh the challenge, but if I have no other reason such as to load a program then I think I will revert back to stock and unlock the bootloader & let the ROM updates come from T-Mobile & LG.
-Shahin
shahinman said:
I started with stock LG v20 T-Mobile H91810P and followed this step by step & the original threads. I loaded the latest stock Oreo from H91820H from here instead of latest Nougat H91810U - Pie & some other versions had too many things not working.
In the process there were a few problems -the major ones are following with solutions, some from here:
1) The file H91810P that needs to be reloaded was missing in original links - I think I downloaded from here.
2) I lost root several times, but had TWRP. So I used adb sideload like:
Boot/start TWRP and the start ADB Sideload
Download Magisk-v16.0.zip and copy to adb directory.
On Windows PC connect Cell with USB and in CMD window type (copy/paste):
adb start-server
adb sideload "Magisk-v16.0.zip"
And never update migisk after installing. Also no need for SU.
3. Camera did not work and people could not hear me nor could I hear them when I picked up a call - A reboot/restart fixed it.
I have 4 problems remaining -any help for solutions here is appreciated - especially exact type help please:
1) On LAF/Boot (original download) partition: Vol+ & connect to USB caused the download mode to come on for about 2 seconds and then TWRP (however I am glad that TWRP is here) -Prefer this to be the original download mode.
2) On Recovery patition: Vol- & connect to USB causes fastboot to come up. Flashed the recovery-twrp-h918-2018-10-18.img (renamed to recovery.img) to recovery partition using flashify and TWRP unsuccessfully. -Prefer this to be TWRP.
3) TWRP cannot access the Data partition. Rebuilt and reformatted Data from TWRP without success. -Prefer access to Data from TWRP.
4) At boot time: I like to get rid of the warning that my bootloader is unlocked. -I can live with this one.
After thoughts: Now that I am rooted on the latest stock Oreo H91820H -I am not sure what I want to load that I could not before?! overclocking the CPU or changing the hue on the display is not a big deal for me at all. & Yes I will uninstall some bloatware - but that is not so bad on this phone anyhow. Any good ideas or a better/later rom than H91820H that has all things working, do please let me know. I am glad that I rooted, ahh the challenge, but if I have no other reason such as to load a program then I think I will revert back to stock and unlock the bootloader & let the ROM updates come from T-Mobile & LG.
-Shahin
Click to expand...
Click to collapse
You can restore download mode by flashing the zip in the original lafexploit thread, but make sure you have twrp on the recovery partition. Make sure you are on the latest version of twrp, when you flashed twrp, you were supposed to format the data partition before flashing the rom.
Sent from my LG-H910 using XDA Labs
For access to Data in TWRP: In the original thread there is nothing about formatting, but in step by step guide there is and I followed - however it does not specify what partition to format. I also ran ./step2.sh script per instructions.
Anyhow as I mentioned above I rebuilt and reformatted the Data partition and that did not give me access. I am on the TWRP 3.2.1-3. What partitions do I need to reformat anyhow?
To flash recovery: I used TWRP and flashify to flash recovery-twrp-h918-2018-10-18.img and it flashes but does not work - I get to fastboot with Vol- & USB.
shahinman said:
Problems with rooting, loading ROM then recovery & download images -some solutions
I started with stock LG v20 T-Mobile H91810P and followed this step by step & the original threads. I loaded the latest stock Oreo from H91820H from here instead of latest Nougat H91810U - Pie & some other versions had too many things not working.
In the process there were a few problems -the major ones are following with solutions, some from here:
1) The file H91810p rom (H91810p_00_0717.kdz) downloaded from here.
2) I lost root several times, but had TWRP. So I used adb sideload like:
Boot/start TWRP and the start ADB SideloadDownload Magisk-v16.0.zip and copy to adb directory.On Windows PC connect Cell with USB and in CMD window type (copy/paste):adb start-serveradb sideload "Magisk-v16.0.zip"
And never update migisk after installing from above or will lose root. Also no need for SU.
3. Camera did not work and people could not hear me nor could I hear them when I picked up a call - A reboot/restart fixed it.
4. No need to download UPPERCUT (that is hard to download), because LGUP works fine without UPPERCUT.
I have 4 problems remaining -any help for solutions here is appreciated - especially exact type help please:
1) On LAF/Boot (original download) partition: Vol+ & connect to USB caused the download mode to come on for about 2 seconds and then TWRP (however I am glad that TWRP is here) -Prefer this to be the original download mode.
2) On Recovery patition: Vol- & connect to USB causes fastboot to come up. Flashed the recovery-twrp-h918-2018-10-18.img (renamed to recovery.img) to recovery partition using flashify and TWRP unsuccessfully. -Prefer this to be TWRP.
3) TWRP cannot access the Data partition. Rebuilt and reformatted Data from TWRP without success. -Prefer access to Data from TWRP.
4) At boot time: I like to get rid of the warning that my bootloader is unlocked. -I can live with this one.
After thoughts: Now that I am rooted on the latest stock Oreo H91820H -I am not sure what I want to load that I could not before?! overclocking the CPU or changing the hue on the display is not a big deal for me at all. & Yes I will uninstall some bloatware - but that is not so bad on this phone anyhow. Any good ideas or a better/later rom than H91820H that has all things working, do please let me know. I am glad that I rooted, ahh the challenge, but if I have no other reason such as to load a program then I think I will revert back to stock and unlock the bootloader & let the ROM updates come from T-Mobile & LG.
-Shahin
Click to expand...
Click to collapse
I had this same situation and ended up bricking the phone, can't get into recovery, stuck in boot loop. This was months ago, just got another v20 and ready to try again. Previously I'd successfully done 3 v20's.