Hi. After using this method to fix dozens of G4's and 5X's, I bumped on one bootlooping V10. As there's no modified kernels that would boot V10 on only 4 cores, I present to you:
V10 kernel that will resurrect your bootlooping beauty!
Requirements and Guide:
1: Working ADB and Fastboot
2A: If you already checked OEM unlock in developer options, try booting to fastboot using this method:
Remove battery from phone
Insert USB cable from PC to phone (with battery removed)
On your phone screen there should now be battery icon with question mark inside
Hold volume down, and while holding, insert the battery in the phone, you should be inside fastboot
From there, unlock bootloader, if you haven't already, and flash 4cores kernel for your version of phone and software
- or -
2B: If you previously didn't enable OEM unlocking, AND/OR you can't boot directly to fastboot:
You must be able to boot the phone at least for 30 seconds to do this
Go to developer options and check OEM Unlocking and USB Debugging
Go to LG site and follow instructions on how to unlock bootloader
After unlocking bootloader, while still on fastboot screen, flash my custom 4cores kernel
Code:
fastboot flash boot boot.img
NOTE: As of now, I only modified 30b and 20e versions for H960a variant, and 20e for H901... It might work on others versions, but I'm not sure. I tested 30B and 20e for H960, H901 is untested at the moment. If you have other software, feel free to contact me and I will make the kernel for specified software version, or use LGUP to flash software version that has 4cores kernel...
Now you have a kernel with max 4 CPUs and the faulty CPUs disabled. Enjoy your resurrected phone.
NOTE: For anyone that didn't have OEM unlock checked at the time of bootloop, I guess you have trouble booting your phone to tick that option. You have few options, and here are only few of them... You can try refrigerator or freezer for 30 minutes to 1 hour, and try to boot your phone. In most cases it will boot long enough to go to developer options and tick the boxes, and then boot to Fastboot. Also, you can try hairdryer for around 10 minutes, it is also confirmed that this method has worked for some people...
If this method helps fixing your phone, feel free to hit thanks button
Donations are not expected or required, but are welcome:
Donate Me!
EDIT:
Added TWRP booting on 4 cores!
Credits:
Big thanks to following people for making this method possible:
@XCnathan32
@steadfasterX
@XeniX_Force
@rudi666
stojshic said:
Hi. After using this fix for few G4's and 5X's, I bumped on V10 with the same problem, but as I found out, no one still made modified kernel that would boot on 4 cores only, so, here it is:
Requirements and Guide:
Working ADB and Fastboot
Unlocked device with access to fastboot (if that's possible on V10?)
- or -
You must be able to boot the phone at least for 30 seconds to do this
Go to developer options and check OEM Unlocking and USB Debugging
Go to LG site and follow instructions on how to unlock bootloader
After unlocking bootloader, while still on fastboot screen, flash my custom 4cores kernel
Code:
fastboot flash boot boot_30b.img
NOTE: As of now, I only modified 30b kernel for h960a variant... It might work on others versions, but I'm not sure. I tested it on my V10 with 30B software installed. If you have other software, feel free to contact me and I will make the kernel for specified software version, or use LGUP to flash 30B, and after that flash this kernel.
Now you have a kernel with max 4 CPUs and the faulty CPUs disabled. Enjoy your resurrected phone.
NOTE: Considering you have bootlooping phone, I guess it's the question how to enter fastboot, as to my knowledge LG disabled booting directly to fastboot. If you know the way to boot directly to fastboot, than you are fine (and please share how), and for everyone else, you must manage to boot the phone somehow. You can try refrigerator or freezer for 30 minutes to 1 hour, and try to boot your phone. In most cases it will boot long enough to go to developer options and tick the boxes, and then boot to Fastboot. Also, you can try hairdryer for around 10 minutes, it is also confirmed that this method has worked for some people...
If this method helps fixing your phone, feel free to hit thanks button
Donations are not expected or required, but are welcome: Donate Me!
Credits:
Big thanks to following people for making this method possible:
@XCnathan32
@steadfasterX
@XeniX_Force
Click to expand...
Click to collapse
this kernel is from V10 or from G4? i mean my V10 is work perfect with Nougat but i want to do as much as i can to keeping it so, can i flash this on H960A International Model? i have unlocked bootloader and i can boot into fastboot...
sun_is_shinning said:
this kernel is from V10 or from G4? i mean my V10 is work perfect with Nougat but i want to do as much as i can to keeping it so, can i flash this on H960A International Model? i have unlocked bootloader and i can boot into fastboot...
Click to expand...
Click to collapse
It's modified V10 kernel that utilizes only 4 cores. You can't use G4 kernel on V10. If you have 30b software on your H960A, you should be safe to boot in fastboot and flash this kernel. After that, you can install cpu-z and verify that only 4 cores are online
Sent from my ZTE Axon 7 using Tapatalk
stojshic said:
It's modified V10 kernel that utilizes only 4 cores. You can't use G4 kernel on V10. If you have 30b software on your H960A, you should be safe to boot in fastboot and flash this kernel. After that, you can install cpu-z and verify that only 4 cores are online
Sent from my ZTE Axon 7 using Tapatalk
Click to expand...
Click to collapse
very very thanks...its working!!! NOW I ONLY HAVE 4 CORES active and the crappy ones is gone!
EDIT: i lose root when flash this, and need to flash TWRP again and supersu again, but root is not working now...i try it twice but nothing, it keep giving error!
can you help?
DISCLAIMER TO THIS THREAD: If you flash this Kernel you will lose the hability to flash SuperSU, and so you wont be able to have root on your device.
P.S.: Dev should put a SELinux Permissive right in Kernel and some add ons like KCAL display calibration and core control. This only disable the little cores and the battery will be more hungry now...
i know this only are made to rescue your V10 from bootloop but i think it deserve some devlopment because this can be a great Kernel.
Thanks for suggestion. For now, this is, like it is stated, pure stock kernel with disabled cores, for those in bootloop. I will think about modified versions in the future, but until further testing, it's going to stay stock...
Sent from my ZTE Axon 7 using Tapatalk
stojshic said:
NOTE: As of now, I only modified 30b kernel for h960a variant... It might work on others versions, but I'm not sure. I tested it on my V10 with 30B software installed. If you have other software, feel free to contact me and I will make the kernel for specified software version, or use LGUP to flash 30B, and after that flash this kernel.
Click to expand...
Click to collapse
Great work. 30b KDZ is easily available here. I think one should flash it and use this boot image instead of asking for developing a boot image for their specific firmwares.
However, I would suggest to kindly release a custom boot image for H901 20e. Because H901 (Tmobile) is also bootloader unlockable and its 20e KDZ is also easily available here. This way both unlockable variants of V10 i.e. H960A and H901 will be covered. :angel:
NOTE: Considering you have bootlooping phone, I guess it's the question how to enter fastboot, as to my knowledge LG disabled booting directly to fastboot. If you know the way to boot directly to fastboot, than you are fine (and please share how).
Click to expand...
Click to collapse
I myself booted to fastboot easily on a bootlooped LG V10 H961N (HongKong) by:
1. Turning the phone off.
2. Pressing Vol down.
3. Connecting the phone with computer with data cable.
4. Releasing the Vol down upon seeing the phone booted into fastboot.
Dont know if the same would work on other variants or not.
rizkhan999 said:
Great work. 30b KDZ is easily available here. I think one should flash it and use this boot image instead of asking for developing a boot image for their specific firmwares.
However, I would suggest to kindly release a custom boot image for H901 20e. Because H901 (Tmobile) is also bootloader unlockable and its 20e KDZ is also easily available here. This way both unlockable variants of V10 i.e. H960A and H901 will be covered. :angel:
I myself booted to fastboot easily on a bootlooped LG V10 H961N (HongKong) by:
1. Turning the phone off.
2. Pressing Vol down.
3. Connecting the phone with computer with data cable.
4. Releasing the Vol down upon seeing the phone booted into fastboot.
Dont know if the same would work on other variants or not.
Click to expand...
Click to collapse
Yeah, I heard about that way of booting, but never managed to boot to fastboot using that method. I will edit my post to include it... Also, thanks for the link for the software, will edit that kernel soon, and post 4cores version of it here...
Sent from my ZTE A2017U using Tapatalk
I never had bootloop on my h960a. how is that possible?
stojshic said:
Yeah, I heard about that way of booting, but never managed to boot to fastboot using that method. I will edit my post to include it... Also, thanks for the link for the software, will edit that kernel soon, and post 4cores version of it here...
Click to expand...
Click to collapse
Someone whom I know has h901 software on his vs990. I asked him to follow this procedure. And he also successfully booted into fastboot mode and shared this image with me which I have uploaded here. Means its working on other models too.
rizkhan999 said:
Someone whom I know has h901 software on his vs990. I asked him to follow this procedure. And he also successfully booted into fastboot mode and shared this image with me which I have uploaded here. Means its working on other models too.
Click to expand...
Click to collapse
Thanks for info! I Added it to first post...
Also, I just uploaded two new versions of kernel:
h901 version 20e
h960a version 20e
stojshic said:
Thanks for info! I Added it to first post...
Also, I just uploaded two new versions of kernel:
h901 version 20e
h960a version 20e
Click to expand...
Click to collapse
Awesome work.:good::victory:
stojshic said:
Thanks for info! I Added it to first post...
Also, I just uploaded two new versions of kernel:
h901 version 20e
h960a version 20e
Click to expand...
Click to collapse
Can we also get the TWRP recoveries with big cores disabled?
For H901 it is available here and here. And for H960A it is available here.
I would really be grateful.
rizkhan999 said:
Can we also get the TWRP recoveries with big cores disabled?
For H901 it is available here and here. And for H960A it is available here.
I would really be grateful.
Click to expand...
Click to collapse
I'll try to make them one of these days. I'm really busy ATM, but will try to find some time to modify the images
Sent from my ZTE A2017U using Tapatalk
I can get into fastboot, but any fastboot commands like
Code:
fastboot flash boot boot.img
or
Code:
fastboot boot recovery twrp.img
or
Code:
fastboot boot twrp.img
fail with unknown command error. My bootloader is unlocked so it can't be that. Any ideas on how to flash this with that it mind?
galaxymover said:
I can get into fastboot, but any fastboot commands like
Code:
fastboot flash boot boot.img
or
Code:
fastboot boot recovery twrp.img
or
Code:
fastboot boot twrp.img
fail with unknown command error. My bootloader is unlocked so it can't be that. Any ideas on how to flash this with that it mind?
Click to expand...
Click to collapse
with the phone off, volume up key pressed connect the phone into pc and keep pressed the volume up key, then go to "minimal adb and fastboot" - its a cmd dedicated to use for this - and there do the follow command:
adb devices
(you should see yours saying conected, then do the follow)
adb reboot fastboot
(and now you are in fastboot, if you want to boot in bootloader do the command bellow)
adb reboot bootloader
- and thats it. if you are trying to flash TWRP you need to download the img of TWRP in some thread in V10 section and put it on the root of the fastboot tool you are using and to install it when in fastboot do the follow command:
fastboot flash recovery (name-of-twrp-file).img
and you done.
sun_is_shinning said:
with the phone off, volume up key pressed connect the phone into pc and keep pressed the volume up key, then go to "minimal adb and fastboot" - its a cmd dedicated to use for this - and there do the follow command:
adb devices
(you should see yours saying conected, then do the follow)
adb reboot fastboot
(and now you are in fastboot, if you want to boot in bootloader do the command bellow)
adb reboot bootloader
- and thats it. if you are trying to flash TWRP you need to download the img of TWRP in some thread in V10 section and put it on the root of the fastboot tool you are using and to install it when in fastboot do the follow command:
fastboot flash recovery (name-of-twrp-file).img
and you done.
Click to expand...
Click to collapse
I tried doing those commands and got the same error that I mentioned in my previous post.
galaxymover said:
I tried doing those commands and got the same error that I mentioned in my previous post.
Click to expand...
Click to collapse
Do you see the device when execute "fastboot devices" command? Also try it on linux after installing "adb" or "android-tools". Because it may be drivers issue on windows. If nothing works, flash a different KDZ. May be this firmware has some limitations in its fastboot.
EDIT: Also check if you have unlocked the bootloader or not. These commands will work if it is unlocked. Although commands should still be recognized but still, just a check.
---------- Post added at 11:05 AM ---------- Previous post was at 10:45 AM ----------
stojshic said:
I'll try to make them one of these days. I'm really busy ATM, but will try to find some time to modify the images
Click to expand...
Click to collapse
Thanks. I have TWRP with big cores disabled in my G4 H815. But when I boot into TWRP and execute cat /sys/devices/system/cpu/cpuX/online from its terminal, I see that only the online file of cpu0 core has the value of 1, while the online files of all the rest cpu cores has 0 value. So if TWRP works on only 1 core by default (just like Download Mode), we may not have to make a TWRP with big cores disabled! But the question is that does TWRP really work on only 1 core by default, as also seem to be the case with that TWRP on my phone?
I would also request you to kindly make a custom boot image with big cores disabled for H901 with 30b firmware from its KDZ. I have attached its boot.img herewith, after extracting it with this tool, so that you may not have to download the whole 30b KDZ for that.
I am sorry to bother you so much but the reason why I am requesting for a 30b custom boot image in presence of 20e for the same model (H901) is that 20e is on ARBv1 while 30b is on ARBv2, and I cannot flash 20e over 30b using LGUP.
hi all, so with htis methode even with the h961n we can getout from the bootloop?, does the undercloked way helps? thanks a lot!!
rizkhan999 said:
Do you see the device when execute "fastboot devices" command? Also try it on linux after installing "adb" or "android-tools". Because it may be drivers issue on windows. If nothing works, flash a different KDZ. May be this firmware has some limitations in its fastboot.
EDIT: Also check if you have unlocked the bootloader or not. These commands will work if it is unlocked. Although commands should still be recognized but still, just a check.
Click to expand...
Click to collapse
While I can see the device in
Code:
fastboot devices
, I cannot see it in LGUP/LG Bridge/LG PC Suite. I will fire up a Linux VM and see if that helps. Also, I have definitely unlocked the bootloader.
Related
I tried to root my phone and install TWRP via the tungkick method, but I forgot to do the ADB fastboot oem unlock before I flashed the modified TOT file, so when I tried to boot into TWRP it got stuck in a bootloop.
Ive downloaded the stock 10D files, but am having issues getting the phone into DL mode so I can reflash the stock files via LGUP. Ive looked though many XDA threads, and have seen a few people post the same issue, but I have yet to find a solution to my issue. Can anyone offer up some assistance?
FluXX66 said:
I tried to root my phone and install TWRP via the tungkick method, but I forgot to do the ADB fastboot oem unlock before I flashed the modified TOT file, so when I tried to boot into TWRP it got stuck in a bootloop.
Ive downloaded the stock 10D files, but am having issues getting the phone into DL mode so I can reflash the stock files via LGUP. Ive looked though many XDA threads, and have seen a few people post the same issue, but I have yet to find a solution to my issue. Can anyone offer up some assistance?
Click to expand...
Click to collapse
To get to download mode try removing battery for a couple seconds, putting it back in and then press and hold volume up while plugging in the USB cable to the computer. Also, you may want to download the 20A kdz and use the recowvery method instead of using the 10D tot file (unless you're wanting to stay on MM for some reason).
Remove battery, insert again. Hold Volume- and connect phone to PC via cable. It will take you to fastboot mode. Write command (make sure drivers & minimal fastboot and adb is installed)
fastboot oem unlock
fastboot reboot
phone will boot to system if everything is fine.
The end goal for the root process is to install TWRP and then CM or a variant of CM. I hate stock software.
Follow this guide to flash 20a firmware then
Follow this guide for rooting+twrp and you are good to flash any custom rom built for this
FluXX66 said:
The end goal for the root process is to install TWRP and then CM or a variant of CM. I hate stock software.
Click to expand...
Click to collapse
If you're wanting something customizable, fast and stable, I'd check out Resurrection Remix after following those guides listed to get 20A, root and TWRP. You may also want to check the dual boot thread and use that to try multiple ROMs at a time and see what you like the best
I got a rca voyager 3 model RCT6973W43 and I need to flash a new rom which I cannot find anywhere. Can you send me a ROM and the flash tool? I got it free and I want to try it get it working. It’s stuck at the voyager 3 logo
kapicarules said:
I got a rca voyager 3 model RCT6973W43 and I need to flash a new rom which I cannot find anywhere. Can you send me a ROM and the flash tool? I got it free and I want to try it get it working. It’s stuck at the voyager 3 logo
Click to expand...
Click to collapse
Hey bro, I've used these guys. Good luck
https://www.needrom.com
Sent from my HTC One M9 using Tapatalk
No RCA I might need to find a similar tablet and dump the firmware
kapicarules said:
No RCA I might need to find a similar tablet and dump the firmware
Click to expand...
Click to collapse
It's been a while since I played with RCA devices, which version of Android is it running?
NepoRood said:
It's been a while since I played with RCA devices, which version of Android is it running?
Click to expand...
Click to collapse
Android 6.0
kapicarules said:
Android 6.0
Click to expand...
Click to collapse
Sorry, not on the Chinese site we used for Viking and Maven firmware, it may show up eventually though...
link me to that chinese website
kapicarules said:
I got a rca voyager 3 model RCT6973W43 and I need to flash a new rom which I cannot find anywhere. Can you send me a ROM and the flash tool? I got it free and I want to try it get it working. It’s stuck at the voyager 3 logo
Click to expand...
Click to collapse
Bro,the device hasn't even been rooted yet. I just purchased one today. There is supposedly a bootloader unlock but no custom recovery yet and no root yet
DMon04 said:
Bro,the device hasn't even been rooted yet. I just purchased one today. There is supposedly a bootloader unlock but no custom recovery yet and no root yet
Click to expand...
Click to collapse
I want to compile AOSP for it and not just root it. Have done it for my pixel but its easier with begin provided propitiatory blobs.
I found this other post on a similar device https://forum.xda-developers.com/general/general/guide-rca-voyager-rct6873w42-unlock-t3582973
Got into fastboot via usb debugging adb reboot fastboot (There doesn't appear to be a button shortcut to boot into it so you may be SOL even if a rom does come out)
Successfully Unlocked the bootloader
Was able to get a root shell via booting the cwm recovery
Dumped the boot.img, recovery.img via CWM but system failed
Was able to dump system via dd command
Still new to ROM building trying to understand vendor trees and device trees for building an AOSP ROM for it, noticed the system doesn't have a /device folder so a lot of tutorials don't seam too helpful.
Flashing the CWM recovery image from the above link breaks the recovery, had to flash back to old recovery, my next steps are to try and modify the stock recovery to enable adb so if i bork system i can button boot to recovery and use adb to get to fastboot otherwise it will be bricked...
Getting anywhere on this?
darkvoxels said:
I want to compile AOSP for it and not just root it. Have done it for my pixel but its easier with begin provided propitiatory blobs.
I found this other post on a similar device https://forum.xda-developers.com/general/general/guide-rca-voyager-rct6873w42-unlock-t3582973
Got into fastboot via usb debugging adb reboot fastboot (There doesn't appear to be a button shortcut to boot into it so you may be SOL even if a rom does come out)
Successfully Unlocked the bootloader
Was able to get a root shell via booting the cwm recovery
Dumped the boot.img, recovery.img via CWM but system failed
Was able to dump system via dd command
Still new to ROM building trying to understand vendor trees and device trees for building an AOSP ROM for it, noticed the system doesn't have a /device folder so a lot of tutorials don't seam too helpful.
Flashing the CWM recovery image from the above link breaks the recovery, had to flash back to old recovery, my next steps are to try and modify the stock recovery to enable adb so if i bork system i can button boot to recovery and use adb to get to fastboot otherwise it will be bricked...
Click to expand...
Click to collapse
You get anywhere on dev for this device? I found one at work and was wanting to give it a shot.. unfortunately it's barren here and supa old hah.. AOSP would be nice for this though.
BA_Flash_GOD said:
You get anywhere on dev for this device? I found one at work and was wanting to give it a shot.. unfortunately it's barren here and supa old hah.. AOSP would be nice for this though.
Click to expand...
Click to collapse
Unfortunately I did not. Mine is still a brick sitting on a shelf, been playing with GSI/Treble for oneplus 6 lately.
darkvoxels said:
I want to compile AOSP for it and not just root it. Have done it for my pixel but its easier with begin provided propitiatory blobs.
I found this other post on a similar device https://forum.xda-developers.com/general/general/guide-rca-voyager-rct6873w42-unlock-t3582973
Got into fastboot via usb debugging adb reboot fastboot (There doesn't appear to be a button shortcut to boot into it so you may be SOL even if a rom does come out)
Successfully Unlocked the bootloader
Was able to get a root shell via booting the cwm recovery
Dumped the boot.img, recovery.img via CWM but system failed
Was able to dump system via dd command
Still new to ROM building trying to understand vendor trees and device trees for building an AOSP ROM for it, noticed the system doesn't have a /device folder so a lot of tutorials don't seam too helpful.
Flashing the CWM recovery image from the above link breaks the recovery, had to flash back to old recovery, my next steps are to try and modify the stock recovery to enable adb so if i bork system i can button boot to recovery and use adb to get to fastboot otherwise it will be bricked...
Click to expand...
Click to collapse
I realize this is an old post but I'm hoping you may be able to help me.
I just got this device and was wondering how you got the bootloader unlocked. When I try to select OEM unlock in settings it just jumps back to off. And fastboot flashing unlock gives me an error.
Any help would be appreciated.
Isrgish said:
I realize this is an old post but I'm hoping you may be able to help me.
I just got this device and was wondering how you got the bootloader unlocked. When I try to select OEM unlock in settings it just jumps back to off. And fastboot flashing unlock gives me an error.
Any help would be appreciated.
Click to expand...
Click to collapse
Hi yeah it's been a while since I bricked mine.. still sitting on a shelf as brick.. If I remember correctly when you do the OEM unlock from fastboot it flashes very briefly the screen to the unlock with instructions and button combination. What I did was run the command while using my phone to record the screen so see the instructions, then I went back watched the video to see what they were
I then went back to fastboot got the command ready again got my fingers in position before hitting enter and just tried to be as fast about it as possible and it worked for me.
darkvoxels said:
Hi yeah it's been a while since I bricked mine.. still sitting on a shelf as brick.. If I remember correctly when you do the OEM unlock from fastboot it flashes very briefly the screen to the unlock with instructions and button combination. What I did was run the command while using my phone to record the screen so see the instructions, then I went back watched the video to see what they were
I then went back to fastboot got the command ready again got my fingers in position before hitting enter and just tried to be as fast about it as possible and it worked for me.
Click to expand...
Click to collapse
Thanks for the reply.
How did you do a record the screen? Is there such an option while in fastboot?
Thank You,
darkvoxels said:
... using my phone to record the screen so see the instructions, then I went back watched the video to see what they were ...
Click to expand...
Click to collapse
Can you please tell me how you recorded the screen while in fastboot?
Thanks
I managed to get the bootloader unlocked on my Alco RCA Voyager III and just never got around to finding recovery or anything for it, this device a lost cause or am I just missing something? I don't think I can pull off making a recovery or rom yet but I can give it a shot if no one else is bothering with this device now a days.
@Trolldizzle How did you get it unlocked?
Thanks
@Isrgish I used fastboot flashing unlock command if I remember correctly, been a little bit since I did the unlock but I am like 90% sure that was the command.
i had get link here : findrom.info/rca-rct6973w43
you can try
Here you can find thr ROM. http://detonnot.com/3Xt3
Compatible Devices:
LG K8+
LG Aristo 2, 2+
LG K9
LG Phoenix 4
Thanks to @AustinGarrick1818 who discovered that this TWRP originally started and developed for the Aristo 2, by @messi2050 and @armandop_, then later updated to the latest version by @tecknight, was able to be flash on the Phoenix 4 leading to the idea that any cv1 device is cable of a ROOT method/TWRP Recovery.
Pre-Requisites:
USB Debugging Enabled
OEM Unlock Enabled
ADB/Fastboot Device Drivers
Your Phone/Brain
Hey guys! Just a heads up, I'm not responsible for any bricked devices or broken devices. So flash at your own risk! This TWRP has the Oreo Kernel from the Aristo 2's Oreo Firmware release.
Downloads
Latest Recovery by @tecknight Here --> https://www.androidfilehost.com/?fid=11410963190603906754Latest USB Drivers --> https://www.lg.com/us/support/software-firmware-drivers
Instructions:
1. Install the ADB Drivers from above. If you have them don't bother. Just move on. If you don't then make sure to install them somewhere easily accessible, as your gonna want to get to them easily.
2. Place the TWRP image in the ADB Folder for later use and plug your phone into your PC. Then press (Shift+Right Click) and select "Open Command Prompt Here".
3. After that type the next few lines of code:
Code:
adb devices
Code:
adb reboot bootloader
4. It should boot into fastboot mode. From there type:
Code:
fasboot devices
Code:
fastboot flashing unlock
5. To prevent fastboot from encrypting cache and data type:
Code:
fastboot erase userdata
Code:
fastboot erase cache
6.Remember the Recovery image? Rename it to rec.img and flash it like this:
Code:
fastboot flash recovery rec.img
7. Now that you've flashed TWRP test it:
Code:
fastboot reboot recovery
NOTE: Anytime you boot up your phone you will get a message saying that the bootloader is locked and you need to lock it. Don't do it. If you do then you phone will soft brick and get stuck in a bootloop. Just let it boot.
8. If you did everything right you should be brought to TWRP.
PLEASE LEAVE A THANKS! THANKS!
Downgrade?
Hey man thanks for pointing out that this will work with the all cv1 devices... I have the Aristo 2 on Metro... Is it possible to flash twrp while on the official Oreo firmware or do I have to downgrade to Nougat?
Last time I was on xda it was stated that you couldn't flash in fastboot while on official Oreo...
tdawgg777 said:
Hey man thanks for pointing out that this will work with the all cv1 devices... I have the Aristo 2 on Metro... Is it possible to flash twrp while on the official Oreo firmware or do I have to downgrade to Nougat?
Last time I was on xda it was stated that you couldn't flash in fastboot while on official Oreo...
Click to expand...
Click to collapse
Yah, it's still like that unfortunately. But you can downgrade to Nougat with LG Uppercut. You should just flash the TWRP on Nougat firmware because it's not locked. So when you downgrade just follow these steps to get Oreo. Also don't install Tec's version of Oreo Firmware. Just jump to my other thread for my Custom Stock ROM. Tec's flashes Oreo Firmware with Oreo Stock Rooted. But mine just flashes the nesassary Oreo Boot and System. The links on my signature.
By the way for anyone wondering the LG Phoenix 4 can be Rooted this way to.
NonStickAtom785 said:
Compatible Devices:
LG K8+
LG Aristo 2, 2+
LG K9
LG Phoenix 4
Thanks to @AustinGarrick1818 who discovered that this TWRP originally started and developed for the Aristo 2, by @messi2050 and @armandop_, then later updated to the latest version by @tecknight, was able to be flash on the Phoenix 4 leading to the idea that any cv1 device is cable of a ROOT method/TWRP Recovery.
Pre-Requisites:
USB Debugging Enabled
OEM Unlock Enabled
ADB/Fastboot Device Drivers
Your Phone/Brain
Hey guys! Just a heads up, I'm not responsible for any bricked devices or broken devices. So flash at your own risk! This TWRP has the Oreo Kernel from the Aristo 2's Oreo Firmware release.
Downloads
Latest Recovery by @tecknight Here --> https://www.androidfilehost.com/?fid=11410963190603906754
Latest USB Drivers --> http://tool.cdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Instructions:
1. Install the ADB Drivers from above. If you have them don't bother. Just move on. If you don't then make sure to install them somewhere easily accessible, as your gonna want to get to them easily.
2. Place the TWRP image in the ADB Folder for later use and plug your phone into your PC. Then press (Shift+Right Click) and select "Open Command Prompt Here".
3. After that type the next few lines of code:
4. It should boot into fastboot mode. From there type:
5. To prevent fastboot from encrypting cache and data type:
6.Remember the Recovery image? Rename it to rec.img and flash it like this:
7. Now that you've flashed TWRP test it:
NOTE: Anytime you boot up your phone you will get a message saying that the bootloader is locked and you need to lock it. Don't do it. If you do then you phone will soft brick and get stuck in a bootloop. Just let it boot.
8. If you did everything right you should be brought to TWRP.
PLEASE LEAVE A THANKS! THANKS!
Click to expand...
Click to collapse
If fastboot flashing unlock fails try fastboot oem unlock
tdawgg777 said:
Hey man thanks for pointing out that this will work with the all cv1 devices... I have the Aristo 2 on Metro... Is it possible to flash twrp while on the official Oreo firmware or do I have to downgrade to Nougat?
Last time I was on xda it was stated that you couldn't flash in fastboot while on official Oreo...
Click to expand...
Click to collapse
As long as your bootloader is unlocked it won't be a problem at least on the LG Phoenix 4 it can have TWRP with Oreo
hello good night I can not enter bootloader mode I always reboot in normal mode the phone, I do it this way c: adb / adb reboot bootloader but I started normal tengop a lg k9 x210em I do not understand the truth any suggestion excuse my English
hello good night I can not enter bootloader mode I always reboot in normal mode the phone, I do it this way c: adb / adb reboot bootloader but I started normal, a lg k9 x210hm I do not understand the truth any suggestion
tazlooney89 said:
hello good night I can not enter bootloader mode I always reboot in normal mode the phone, I do it this way c: adb / adb reboot bootloader but I started normal, a lg k9 x210hm I do not understand the truth any suggestion
Click to expand...
Click to collapse
on my device is the same
Problem!!!
I do what you write in tutorial but my phone dont run on fastboot mode Please HELP!!!
Do we know anything about unbricking these phones? I've got a US Cellular K8+ (LG-X210ULM) that my wife accidentally bricked a while back while trying to flash TWRP (not this particular build, obviously). I think she said everything seemed fine and then on reboot...well, it just never turned on again. PC doesn't pick it up at all, no Qualcomm mode or anything. Based on that, I had assumed it was a lost cause that would take JTAG to bring back, and it may well be...
...but then I noticed something unusual the other day. For the hell of it, I decided to plug it into a charger and let it sit for a while. I got what I expected, which was nothing at all. Oh well. Anyway, I happened to be working with another X210 at the time but only had one battery handy, so I just popped the one out of the "dead" phone without unplugging it and went about with what I was doing. After about 5-10 minutes, something caught my eye - sure enough, the dead phone's screen was now on, displaying the "?" battery screen. I put the battery back into the phone and got unceremoniously dumped straight back to black nothingness. Oh well.
So yeah, the phone still doesn't seem to respond to anything when connected to the PC with no battery, so it's probably a no-go, but the fact that it still shows the no-battery screen tells me it's not quite *as* bricked as I thought it was at least. Any ideas? Are we lucky enough to do a boot-from-SD trick on this phone?
Lmx210cm twrp
Do you happen to have anything for the lmx210cm?
Ausboz said:
Do you happen to have anything for the lmx210cm?
Click to expand...
Click to collapse
Just created a whole EDL firmware for the Aristo 2 aka Phoenix 4. PM me for the links if you'd like a copy. I also found our prog_emmc_firehose_8917_ddr.mbn to flash with (it works)
---------- Post added at 05:16 AM ---------- Previous post was at 05:13 AM ----------
tdawgg777 said:
Hey man thanks for pointing out that this will work with the all cv1 devices... I have the Aristo 2 on Metro... Is it possible to flash twrp while on the official Oreo firmware or do I have to downgrade to Nougat?
Last time I was on xda it was stated that you couldn't flash in fastboot while on official Oreo...
Click to expand...
Click to collapse
I tested oreo and it works file
AustinGarrick1818 said:
Just created a whole EDL firmware for the Aristo 2 aka Phoenix 4. PM me for the links if you'd like a copy. I also found our prog_emmc_firehose_8917_ddr.mbn to flash with (it works)
---------- Post added at 05:16 AM ---------- Previous post was at 05:13 AM ----------
I tested oreo and it works file
Click to expand...
Click to collapse
Hi would mind telling how to flash that firmware amd whats the prog_+++++++ddr.mbn to flash i have aristo 2 android 8.1 metro and i cant do any flash in fastboot or root it anything you know about it will be appreciated so much...
@NonStickAtom785 Any solution to start fastboot mode, the phone? Whenever I try to start it from CMD the phone restarts normally, there is no way to get into fastboot mode.
I already probe manually, with combination of buttons, and it does not work either, the model is the LX210HM
tazlooney89 said:
@NonStickAtom785 Any solution to start fastboot mode, the phone? Whenever I try to start it from CMD the phone restarts normally, there is no way to get into fastboot mode.
I already probe manually, with combination of buttons, and it does not work either, the model is the LX210HM
Click to expand...
Click to collapse
Have you tried installing the Aristo 2 firmware on your phone? In theory these phones have the same build and processors. Also in theory, but proven to work on some other cv1 devices (LG Phoenix 4), you should be able to flash Aristo 2 firmware and unlock your phone that way. I would also check your system.img to see if anything such as a security patch is in place to keep your phone from rebooting to the bootloader. You can backup the system.img manually and send me the img and I will look for anything that different from the Aristo 2 system.img.
Also by backing up the system.img and sending it to me, I can retrieve any "extra" carrier settings and add them to the cv1 img. I'm working on a full stock cv1 firmware img that will work on all the cv1 devices as a root strategy.
I have Lg K9 ( lmx210em ) and it's IMPOSSIBLE enter in fastboot mode, either with key combinations, either with adb command... The phone always boot in normalk mode !!!
Download mode and recowery mode work properly, but fastboot mode DID NOT !!!
urgent
i need the firmware the phoenix 4 please
NonStickAtom785 said:
Compatible Devices:
LG K8+
LG Aristo 2, 2+
LG K9
LG Phoenix 4
Thanks to @AustinGarrick1818 who discovered that this TWRP originally started and developed for the Aristo 2, by @messi2050 and @armandop_, then later updated to the latest version by @tecknight, was able to be flash on the Phoenix 4 leading to the idea that any cv1 device is cable of a ROOT method/TWRP Recovery.
..............
[/COLOR][/SIZE]
Click to expand...
Click to collapse
I'm assuming this will not work on the LG Aristo 2 Verizon PrePaid LM-X210VPP ? Or am i wrong? I have one here in inventory that just needs a new LCD and Digitizer ($20) and I was thinking about fixing it and modding it but worried about Verizon and the bootloader being locked. Have not found a lot of info on this device just yet so debating whether or not to keep / fix or get rid of it.
---------- Post added at 01:24 AM ---------- Previous post was at 01:22 AM ----------
AustinGarrick1818 said:
Just created a whole EDL firmware for the Aristo 2 aka Phoenix 4. PM me for the links if you'd like a copy. I also found our prog_emmc_firehose_8917_ddr.mbn to flash with (it works)
---------- Post added at 05:16 AM ---------- Previous post was at 05:13 AM ----------
I tested oreo and it works file
Click to expand...
Click to collapse
Did anyone get this guys debrick package? And does it have the xml's already created? Either way I would like a copy. If someone can pm me a link to a download or email me it that would be awesome.
i installed twrp and rooted the lmx210cm however now when i boot i shows a black bar at bottom of screen... top of image is cut off and touch screen is unresponsive.... works fine in twrp... what did i do wrong?
jdthomas4181 said:
i installed twrp and rooted the lmx210cm however now when i boot i shows a black bar at bottom of screen... top of image is cut off and touch screen is unresponsive.... works fine in twrp... what did i do wrong?
Click to expand...
Click to collapse
The issue you describe appears to be caused by kernel incompatibilities between certain partitions of the phone.
The fact that TWRP does not have the screen glitching issue implies that the kernel embedded in the TWRP image you flashed IS compatible, but perhaps the kernel within your boot image is NOT.
My first question would be:
You mention that you rooted your phone from fastboot.
Did you:
1. patch the stock boot image on your phone or
2. flash a pre-rooted boot image to your boot partition or
3. Flash a pre rooted ROM to your phone
If you answered #2 or #3, then my secondary question would be:
Specifically which boot image or ROM did you flash to your phone ?
---------- Post added at 08:35 PM ---------- Previous post was at 08:32 PM ----------
noidodroid said:
I'm assuming this will not work on the LG Aristo 2 Verizon PrePaid LM-X210VPP ? Or am i wrong? I have one here in inventory that just needs a new LCD and Digitizer ($20) and I was thinking about fixing it and modding it but worried about Verizon and the bootloader being locked. Have not found a lot of info on this device just yet so debating whether or not to keep / fix or get rid of it.
---------- Post added at 01:24 AM ---------- Previous post was at 01:22 AM ----------
Did anyone get this guys debrick package? And does it have the xml's already created? Either way I would like a copy. If someone can pm me a link to a download or email me it that would be awesome.
Click to expand...
Click to collapse
I did not get the edl package, but I really want it and of course his account is suspended.
Anybody have it ?
Also this method should be capable of working on your phone, as it is a cv1 device.
You may have to downgrade the firmware to Nougat before proceeding if the device is currently running Oreo.
If the device is currently running Oreo or later, you can downgrade the phone to Nougat using the LGUP utility
New From A-TEAM: lehmancurtis147
ALCATEL IDOL 5 : 6060CACCESS FASTBOOT
UNLOCK BOOTLOADER
INSTALL TWRP
Special thanks to the mVirus Team for the reboot tool.
Ok, here we go!!!
Start fastboot:
1.*Unpack and launch the boot mode tool.
2.*Power off your 6060C.
3.*While holding vol- plug in device to PC.
4.*While continuing to hold vol- press power until the device starts and release power (not vol-).
5.*Once you see fastboot at the bottom of the device you can release vol-.
Unlock Bootloader:
Now that you are in fastboot mode, we need to unlock the bootloader.
Code:
fastboot oem unlock
Install Custom Recovery:
I forgot to mention I also built a working TWRP.img for this device.
1.*Unzip the recovery.zip.
2.*To install it.
Code:
fastboot flash recovery recovery.img
3.*then...
Code:
fastboot oem reboot-recovery
4.*Welcome to team win recovery!
DOWNLOADS:
This is the boot-mode tool:
https://androidforums.com/attachments/mtk-bootmode-tool-zip.153347/
twrp link:
https://drive.google.com/file/d/1teI23ASm2IbIy_r4xV0jlzz_TzS3cvTc/view?usp=sharing
NOTE:
Unless you remove verity (and a handful of other annonyances) you will loose twrp. Luckily, I've already built a replacement system.img to solve this. Once its working right I'll share it.
I have the system image working, but it's huge. Probably why system and vendor were split in android 8. It's a 4.6 gigabyte image so as soon as I decide the best way to host it I will post it.
In the mean time, the way to keep updated is our telegram group.
A-Team General Discussion
Anything Alcatel, AIO ToolKit, Android, CricketRom
https://t.me/Android_General_Chat
Recoveries
!!!ANNOUNCEMENT!!!
New Recovery Options Available
I now have managed to build a fully functional Pitch Black Recovery Image and and Orange Fox Recovery Image (the later is built from mostly 9.0 branch) and will be making them available soon if I see that anyone is actually interested.
The recovery image files are compiled from source and not a Frankenstein type. So I can address any recovery issues (within the scope of reason).
Thanks for the thread!! I don't have this device but to my amazement, this utility booted my Alcatel 3t 8 tablet into fastboot mode and I was bootloader unlocked in seconds! I can't thank you enough. This tool should be shared around. It may just be the key to unlocking the bootloader on a plethora of 2018+ MTK devices.
mickeybeats said:
Thanks for the thread!! I don't have this device but to my amazement, this utility booted my Alcatel 3t 8 tablet into fastboot mode and I was bootloader unlocked in seconds! I can't thank you enough. This tool should be shared around. It may just be the key to unlocking the bootloader on a plethora of 2018+ MTK devices.
Click to expand...
Click to collapse
Hi mickeybeats, I happen to have the Alcatel 3t 8 as well! I've been looking for a copy of the stock ROM/firmware everywhere and I'm unable to find it. Is it possible that you have a copy/know where I could download it? My tablet starting throwing up the feared "System UI has stopped" error and it seems reflashing stock ROM is the only way to fix it
I can confirm that the bootloader thing works for the 6058D model (MTK 6753)
For stock ROMs on Alcatel mtk devices, you need Sugar-mtk from Alcatel. It goes through the reflash process and as a bonus you can grab the firmware file from inside the flash tools program folders. The files don't use human readable formatting for the names but they end in either .bin or .mbn. A once over with a hexeditor should be enough to get a general idea of what they are. All the ones I've delt with had the boot.img label with a b at the beginning of the name and r for recovery, but gets a bit scattered from there.
stevegsames said:
I can confirm that the bootloader thing works for the 6058D model (MTK 6753)
Click to expand...
Click to collapse
Post your boot.img if you don't already have a custom recovery and I will build one for yours.
lehmancurtis said:
Post your boot.img if you don't already have a custom recovery and I will build one for yours.
Click to expand...
Click to collapse
I did make one, thank you though. If anyone's interested, here it is:
Idol 5 6058D TWRP
So, I recently revisited this phone and saw that there was a new exploit to access the bootloader. I tried it and it worked. After some time of trial and error, I was able to dump the stock recovery. With this, I started to port TWRP to it. This...
forum.xda-developers.com
stevegsames said:
I did make one, thank you though. If anyone's interested, here it is:
Idol 5 6058D TWRP
So, I recently revisited this phone and saw that there was a new exploit to access the bootloader. I tried it and it worked. After some time of trial and error, I was able to dump the stock recovery. With this, I started to port TWRP to it. This...
forum.xda-developers.com
Click to expand...
Click to collapse
Good to hear.
Hi all!
Is there anything similar to 'boot-mode too'l for Linux machines?
What would be a proper command-foo for this task?
The usual method with adb/fastboot obviously doesn't work with
Alcatel IDOL 5 (6058D/MT6753).
To install TWRP on Alcatel Idol 5, you first need to unlock the bootloader.The process is a bit more involved for this device than it is on most others.
Click to expand...
Click to collapse
Thanks!
elocnix said:
Hi all!
Is there anything similar to 'boot-mode too'l for Linux machines?
What would be a proper command-foo for this task?
The usual method with adb/fastboot obviously doesn't work with
Alcatel IDOL 5 (6058D/MT6753).
Thanks!
Click to expand...
Click to collapse
I don't know if it will work with wine. But you should be able to run it from a VM.
Don't be a idiot like me and accidently flash the recovery image on the Alcatel 3T 8. it will permanently brick the device and sugar-mtk will not restore .
So I purchased a tmobile op8 and it arrived yesterday, after setting up the phone and network unlocking (which happened basically instantaneously after applying for it which i found odd), I am currently trying to unlock bootloader in the hopes of converting it to the international firmware. I am on software version 11.0.5.7.IN55CB
The problem I am facing is that whenever i try to do "adb devices" while the phone is powered on it works and lists it, but when the phone is in fastboot mode it does not list the device. Also when i do "fastboot oem get_unloock_code" it gets stuck at waiting for devices. I have read through numerous posts both here and on the op forums talking about this and some listed solutions such as going into windows optional updates and updating google bootloader or something, while others said to check that bootloader is unlocked (i did both and didnt work). Any tips? Also, could someone please link to the correct adb and driver downloads as I am getting mixed results when searching which is the correct download.
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Thanks, worked like a charm. Now to wait 7 business days fml
if you just want the bootloader unlocked there's another way to do it instantly using EDL it's how I unlocked mine , instructions and files are here.. only works on Android 11 btw https://androidfilehost.com/?fid=7161016148664833753 if you really don't feel like installing edl and what not there is a Linux live distro that's already ready to go on the edl GitHub page you can download but just forewarning it's extremely glitchy and not used friendly lol if you need help , I can help you tho just lmk
PrivyetCyka said:
if you just want the bootloader unlocked there's another way to do it instantly using EDL it's how I unlocked mine , instructions and files are here.. only works on Android 11 btw https://androidfilehost.com/?fid=7161016148664833753 if you really don't feel like installing edl and what not there is a Linux live distro that's already ready to go on the edl GitHub page you can download but just forewarning it's extremely glitchy and not used friendly lol if you need help , I can help you tho just lmk
Click to expand...
Click to collapse
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
DamianF7 said:
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
Click to expand...
Click to collapse
i have t-m version and i have converted it to international software firmware also gets changed but by your self you won't be able to get 2 sim support because there is only one imei in phone. all the rom's work exacly the same as they do on global version not a single difference currently running a12 aex rom no problems at all
DamianF7 said:
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
Click to expand...
Click to collapse
don't forget to backup your persist.img there is some % chance it may get lost and you will have to recalibrate firngerprint sensor also back up the modem.img from twrp beacause that's has imei of your phone and if somehow you get your phone hardbricked that would be nice thing to have as a peace of mind
d.tat said:
don't forget to backup your persist.img there is some % chance it may get lost and you will have to recalibrate firngerprint sensor also back up the modem.img from twrp beacause that's has imei of your phone and if somehow you get your phone hardbricked that would be nice thing to have as a peace of mind
Click to expand...
Click to collapse
Can this be done without TWRP or does this have to be done after I root?
DamianF7 said:
Can this be done without TWRP or does this have to be done after I root?
Click to expand...
Click to collapse
you can backup persist without twrp. i'm sure modem could be backed up without twrp too but that's how i did it even tho i did not need persist nor modem image but i would suggest you do it anyways just to be safe booting into twrp in not hard at all you have to do is go info fastboot and through adb file boot into recovery ( fastboot boot "recovery" ) device will reboot in twrp and from there you just backup persist and modem take that file and save it on your computer
also important note for android 10 use twrp 3.4 and for android 11 use 3.6 and most importantly if you read the instructions on converting to global or installing twrp or custom rom carefully it will work 100% i was lazy and did it old way i used to do it on some other android phones and bricked few times but it was all good with msm tool you could restore phone from almost every state that's what made oneplus great
DamianF7 said:
Can this be done without TWRP or does this have to be done after I root?
Click to expand...
Click to collapse
no root needed to install or boot into twrp
d.tat said:
you can backup persist without twrp. i'm sure modem could be backed up without twrp too but that's how i did it even tho i did not need persist nor modem image but i would suggest you do it anyways just to be safe booting into twrp in not hard at all you have to do is go info fastboot and through adb file boot into recovery ( fastboot boot "recovery" ) device will reboot in twrp and from there you just backup persist and modem take that file and save it on your computer
also important note for android 10 use twrp 3.4 and for android 11 use 3.6 and most importantly if you read the instructions on converting to global or installing twrp or custom rom carefully it will work 100% i was lazy and did it old way i used to do it on some other android phones and bricked few times but it was all good with msm tool you could restore phone from almost every state that's what made oneplus great
Click to expand...
Click to collapse
Ok, thanks for clarification
FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Ive run into an issue with edl mode and you seem knowledgeable. I tried to flash the international firmware with an unlocked bootloader but it turned out to be an older build and now my phone is in crash dump mode. I planned on using msmtool to downgrade to android 10 and just restart but my phone isnt detected by my pc even though i have the qualcomm drivers installed. Any tips?
edit: btw can still access fastboot mode (download mode)
so phone is recognized in fastboot but not as qhusnhub or whatever its supposed to be, its just called oneplus android bootloader interface
DamianF7 said:
Ive run into an issue with edl mode and you seem knowledgeable. I tried to flash the international firmware with an unlocked bootloader but it turned out to be an older build and now my phone is in crash dump mode. I planned on using msmtool to downgrade to android 10 and just restart but my phone isnt detected by my pc even though i have the qualcomm drivers installed. Any tips?
edit: btw can still access fastboot mode (download mode)
so phone is recognized in fastboot but not as qhusnhub or whatever its supposed to be, its just called oneplus android bootloader interface
Click to expand...
Click to collapse
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery. Make sure you put it in your fastboot/platform-tools folder.
2. Flash that recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery lineage-18.1-20211218-recovery-instantnoodle.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Make sure you're plugged in and use this command on your PC. "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
FoxyDrew said:
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery.
2. Flash recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery NAMEOFFILE.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Use this command "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
Click to expand...
Click to collapse
Thanks for the reply man. Believe it or not this is exactly what I did lol. Got it working again and am now rooted on international oos 11.
FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Just wanted to say that this solved my issue of not being able to make it past the reboot into fastboot when flashing from TMo to Global using the flash-all.bat guides. I ran the batch file on a newly MSM'd 10.5.22 and when it got stuck at "waiting for device" I followed these steps and as soon as the driver was installed the batch file kicked back in and finished the flashing. Cheers!
SilverZero said:
Just wanted to say that this solved my issue of not being able to make it past the reboot into fastboot when flashing from TMo to Global using the flash-all.bat guides. I ran the batch file on a newly MSM'd 10.5.22 and when it got stuck at "waiting for device" I followed these steps and as soon as the driver was installed the batch file kicked back in and finished the flashing. Cheers!
Click to expand...
Click to collapse
Glad you got it man, worth all the trouble to get to a clean version of OOS without T-MO's junk and spying xD
FoxyDrew said:
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery. Make sure you put it in your fastboot/platform-tools folder.
2. Flash that recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery lineage-18.1-20211218-recovery-instantnoodle.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Make sure you're plugged on and use this command on your PC. "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
Click to expand...
Click to collapse
Thanks SO MUCH for this!! This is the only thing that allowed me to get into EDL Mode. I'm a bit stuck using MSM though. It shows my device as connected, but when I click the "Target" dropdown O2 is not an option. The only option I see is TMO. Any ideas?
UPDATE: i was able to get MSM going. Selecting the target was not needed, just needed to reboot the phone into EDL again and quickly press Start.
I'm back to stock now and just unlocked my bootloader again.
I now have a follow up question: My goal is to install Pixel Experience on my OPO8. Do I need to flash the Global ROM first or can I go straight into Pixel Experience?
UPDATE 2: no matter what I try flashing to my device I always end up getting "not allowed" errors with the critical partition. I've done the fresh MSM process three times already and always end up hitting these critical partition errors when trying to flash the global rom (or any other rom for that matter). any ideas?
nmuntz said:
Thanks SO MUCH for this!! This is the only thing that allowed me to get into EDL Mode. I'm a bit stuck using MSM though. It shows my device as connected, but when I click the "Target" dropdown O2 is not an option. The only option I see is TMO. Any ideas?
UPDATE: i was able to get MSM going. Selecting the target was not needed, just needed to reboot the phone into EDL again and quickly press Start.
I'm back to stock now and just unlocked my bootloader again.
I now have a follow up question: My goal is to install Pixel Experience on my OPO8. Do I need to flash the Global ROM first or can I go straight into Pixel Experience?
UPDATE 2: no matter what I try flashing to my device I always end up getting "not allowed" errors with the critical partition. I've done the fresh MSM process three times already and always end up hitting these critical partition errors when trying to flash the global rom (or any other rom for that matter). any ideas?
Click to expand...
Click to collapse
Do you have a T-Mobile device? If so you SHOULD be selecting "TMO" from the dropdown in MSM. Not O2 or leaving it blank. If you don't have a T-Mobile device, your using the wrong MSM tool as TMO shouldn't be an option.
Did you unlock your bootloader after MSMing back to stock? MSM Tool will automatically lock your bootloader. Also what recovery are you using to try to flash ROMs?
Also PixelExperience is dead for op8 it stopped getting updates. I'd recommend HavocOS for a "Pixel Experience". Also a well polished ROM in general.
FoxyDrew said:
Do you have a T-Mobile device? If so you SHOULD be selecting "TMO" from the dropdown in MSM. Not O2 or leaving it blank. If you don't have a T-Mobile device, your using the wrong MSM tool as TMO shouldn't be an option.
Did you unlock your bootloader after MSMing back to stock? MSM Tool will automatically lock your bootloader. Also what recovery are you using to try to flash ROMs?
Also PixelExperience is dead for op8 it stopped getting updates. I'd recommend HavocOS for a "Pixel Experience". Also a well polished ROM in general.
Click to expand...
Click to collapse
I'm pretty sure that this is a T-Mobile device. It registers as IN2017 which matches the description of the phone I bought off amazon but not exactly sure how else can i verify this.
I did unlock the bootloader after MSMing back to stock. One thing I noticed is that the stock image that MSM flashed has Sprint branding and not T-Mobile. maybe i'm using the wrong MSM tool? I'm using the one from this guide
I just re-did MSM; this time selecting TMO and I still got Sprint branding. is this expected?
I've been trying with multiple recoverys: the stock one, TWRP and the one that pixelexperience had. The LineageOS one you provided I only used for doing the ADB thing to boot into EDL. What recovery do you recommend I use?
I did read about PixelExperience being dead so downloaded Havoc.
can you please confirm if I should be flashing the Global ROM before flashing HavocOS? regarding the critical partition errors any ideas whats causing those?
last question is regarding adb/fastboot - been reading different things about what version to use. been doing all my last experiments using the ones from https://developer.android.com/studio/releases/platform-tools but got the same results. sorry to spam you with so many questions - appreciate your help!
nmuntz said:
I'm pretty sure that this is a T-Mobile device. It registers as IN2017 which matches the description of the phone I bought off amazon but not exactly sure how else can i verify this.
I did unlock the bootloader after MSMing back to stock. One thing I noticed is that the stock image that MSM flashed has Sprint branding and not T-Mobile. maybe i'm using the wrong MSM tool? I'm using the one from this guide
I just re-did MSM; this time selecting TMO and I still got Sprint branding. is this expected?
I've been trying with multiple recoverys: the stock one, TWRP and the one that pixelexperience had. The LineageOS one you provided I only used for doing the ADB thing to boot into EDL. What recovery do you recommend I use?
I did read about PixelExperience being dead so downloaded Havoc.
can you please confirm if I should be flashing the Global ROM before flashing HavocOS? regarding the critical partition errors any ideas whats causing those?
last question is regarding adb/fastboot - been reading different things about what version to use. been doing all my last experiments using the ones from https://developer.android.com/studio/releases/platform-tools but got the same results. sorry to spam you with so many questions - appreciate your help!
Click to expand...
Click to collapse
I've never seen that MSM tool, but the one I use doesn't have any Sprint files at all. Not sure where you found that MSM but use this one for future reference.
No you don't need to flash global before a ROM.