Related
So yeah I accidentally wiped my partitions as if I were installing a rom. Am I screwed until I get to a pc?
P.s. Out of all days to delete my backup rom file ?
Just set it to boot loader mode and flash stock images...I'm sure there's a tutorial on how to do it..I have the program installed on my computer ready for any time I brick my phone lol but I don't remember the name of the program right now
Edit: heres the link to the method I use http://forum.xda-developers.com/showthread.php?t=3258493
I'm assuming the OP doesn't have a PC due to the last statement he made. I would say yes, nothing you can do until you can get to a PC and flash stock images via Fastboot. Unless you have a ROM zip on your phone that is....which I'm assuming you don't.
You're kinda stuck, you need a PC to flash the factory images. TWRP can't flash OTA's anyway, so don't try that again either. I'd strongly recommend not using a toolkit to flash the factory images too. I have a detailed guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Hey guys, having a similar issue than zachbuilds. While rooting my nexus 6p on NRD9M, I formatted to system partition for root to stick and noticed twrp stated I have no OS installed. At that point I was going to flash stock image file when my nexus reverted from default MTP to charge only and now my Mac is unable to recognize my device Ann's now adb is non operable. I tried to fastboot adb commands but that isn't working either. Any one have any suggestions. I'm on stock with twrp custom recovery, no other changes were made to my device. Also, recovery and bootloader are accessible. Thanks for any help given.
Snakielols1984 said:
Hey guys, having a similar issue than zachbuilds. While rooting my nexus 6p on NRD9M, I formatted to system partition for root to stick and noticed twrp stated I have no OS installed. At that point I was going to flash stock image file when my nexus reverted from default MTP to charge only and now my Mac is unable to recognize my device Ann's now adb is non operable. I tried to fastboot adb commands but that isn't working either. Any one have any suggestions. I'm on stock with twrp custom recovery, no other changes were made to my device. Also, recovery and bootloader are accessible. Thanks for any help given.
Click to expand...
Click to collapse
Can fastboot see your device when you're in bootloader?
Yes fastboot is able to reconize my device.
Snakielols1984 said:
Yes fastboot is able to reconize my device.
Click to expand...
Click to collapse
Best just to flash back to factory images. Be cautious if you've flashed the Android N OTA though, there are some strange things going on with people trying to flash back to M. Read up before you flash.
I've actually tried flashing stock images but every time I tried to run fastboot command I get these errors, "command not found" and I believe the other erro is "file path not found". There's another error that I can't remember off the top of my head what it. When I get home I'll try to run the commands again and see what errors I get
---------- Post added at 11:09 PM ---------- Previous post was at 11:08 PM ----------
elfrosto said:
Best just to flash back to factory images. Be cautious if you've flashed the Android N OTA though, there are some strange things going on with people trying to flash back to M. Read up before you flash.
Click to expand...
Click to collapse
on another note I have not flashed Android N OTA. I downloaded that and install via OTA.
wrong thread
so just attempted to flash stock images and I get an error "cannot load bootloader-angler-angler-03.54.img". the tutorial I am using is Heisenberg's How-To Guide For Beginners. I followed the instructions step by step. Please is anyone can chime in, please do. Greatly appreciated!
Snakielols1984 said:
so just attempted to flash stock images and I get an error "cannot load bootloader-angler-angler-03.54.img". the tutorial I am using is Heisenberg's How-To Guide For Beginners. I followed the instructions step by step. Please is anyone can chime in, please do. Greatly appreciated!
Click to expand...
Click to collapse
What bootloader version are you on currently? Although updated bootloader is recommend, you should be able to skip this step without any issues.
Sorry for late response but currently I am bootloader: angler-3.58
---------- Post added at 12:27 AM ---------- Previous post was at 12:19 AM ----------
This is the error I get when using fastboot commands to flash stock images "error: cannot load 'MacintoshHD/angler/images/radio-angler-angler-03.61.img'". I received same error when trying to flash bootloader
Snakielols1984 said:
Sorry for late response but currently I am bootloader: angler-3.58
---------- Post added at 12:27 AM ---------- Previous post was at 12:19 AM ----------
This is the error I get when using fastboot commands to flash stock images "error: cannot load 'MacintoshHD/angler/images/radio-angler-angler-03.61.img'". I received same error when trying to flash bootloader
Click to expand...
Click to collapse
Please post the entire command you are using, as written in your terminal prompt. "No command" sounds like an unrecognized command is being issued. We must use ./ in addition to the fastboot or adb command in order for OSX to execute the action. If following Heisenberg's guide for fastboot, the lone change you need to make for OSX is:
./fastboot devices
./fastboot flash
./fastboot reboot
./ADB devices
Try this out and post your results.
Sent from my Nexus 5X using Tapatalk
Just throwing this out there, it is possible to flash an OTA in TWRP. You still need a PC but its do-able.... I flashed Android N Final to my 6P yesterday by copying the OTA zip (uploaded thanks to another member) to SD, Wiped device as I normally would with any other ROM (left SD intact obviously), Flashed OTA ZIP, rebooted straight to bootloader after flash, fastboot erase boot, fastboot erase recovery, fastboot flashed DECRYPTED BOOT.img (which can be found easily), fastboot flashed TWRP 3.0.2-1 (version just released for N), fastboot format userdata, fastboot format cache, reboot from bootloader directly into TWRP, flashed superSU 2.74, reboot system..... Phone runs beautifully. Not a single issue. Entire process from start to finish was less than 10 minutes.
Its not the most practical route but it does indeed work. OTA just hes to contain the entire Image. I should also mention that this was a jump from a Marshmallow based rom (RR) so you don't have to be on an N preview in order to do this....
I need help! Here’s the story. Sorry for the lengthy post. TL;DR at the bottom..
- Was on B32, unlocked BL, TWRP installed, rooted with SuperSU
- Updated to B35, but lost TWRP and root (I don’t know how, but I assume I must have wiped the wrong things? - system? - I’m clearly a novice)
- Now I’m on B35 with an unlocked BL, but despite days of searching and researching, I can’t for the life of me figure out how to get TWRP reinstalled. I want to have TWRP before trying Magisk (have never used Magisk before, but would like to try it this time instead of SuperSU)
- From my Mac, using terminal, adb recognizes my devices.
- “adb reboot boot loader” gets me to a list of options “power off, restart, recovery, fastboot, back to previous page”. Choosing fastboot simply restarts the phone. What should “fastboot mode” look like?
- I tried flashing TWRP via adb while on this page and terminal stopped at “waiting for any device” and did nothing
My conclusion is that I need to downgrade to whatever latest version allows fastboot commands to work properly? Is this B15? If so, is the only available B15 zip the one that is on the ZTE website? Do I just wipe data/dalvick/cache and flash this zip?
Do I not need a Bootstock and Systemstock like @DrakenFX usually posts? That’s how I’m used to doing any updates.
Thank you all for your help, both past and present!
TL;DR: Would like to downgrade from B35 to B15 so that I can install twrp and root again. What’s the best way to do this and where can I find the appropriate files?
alajoy said:
I need help! Here’s the story. Sorry for the lengthy post. TL;DR at the bottom..
- Was on B32, unlocked BL, TWRP installed, rooted with SuperSU
- Updated to B35, but lost TWRP and root (I don’t know how, but I assume I must have wiped the wrong things? - system? - I’m clearly a novice)
- Now I’m on B35 with an unlocked BL, but despite days of searching and researching, I can’t for the life of me figure out how to get TWRP reinstalled. I want to have TWRP before trying Magisk (have never used Magisk before, but would like to try it this time instead of SuperSU)
- From my Mac, using terminal, adb recognizes my devices.
- “adb reboot boot loader” gets me to a list of options “power off, restart, recovery, fastboot, back to previous page”. Choosing fastboot simply restarts the phone. What should “fastboot mode” look like?
- I tried flashing TWRP via adb while on this page and terminal stopped at “waiting for any device” and did nothing
My conclusion is that I need to downgrade to whatever latest version allows fastboot commands to work properly? Is this B15? If so, is the only available B15 zip the one that is on the ZTE website? Do I just wipe data/dalvick/cache and flash this zip?
Do I not need a Bootstock and Systemstock like @DrakenFX usually posts? That’s how I’m used to doing any updates.
Thank you all for your help, both past and present!
TL;DR: Would like to downgrade from B35 to B15 so that I can install twrp and root again. What’s the best way to do this and where can I find the appropriate files?
Click to expand...
Click to collapse
I'm not sure where you read all that BS, but if your bootloader is unlocked then you can install TWRP via EDL (Or fastboot if you have it). No need to downgrade for anything :laugh: in the past you would have needed to downgrade in order to unlock the bootloader, now it's not even needed
Download EDL Tool by djkuz and install TWRP with that one. Or you can use axon7tool by tennear, but it's much more finicky and ran entirely by commands (no UI).
And just to avoid more trouble, DO NOT LOCK THE BOOTLOADER! You do that with the system even barely modified and you brick the phone. A bunch of people tried to do something, got scared because they made a simple correctable mistake and just locked the bootloader thinking everything would get restored to stock - doesn't work that way.
Not saying you will do this, but I've seen about 4 or 5 people that started just like you and ended up doing that
Choose an username... said:
I'm not sure where you read all that BS, but if your bootloader is unlocked then you can install TWRP via EDL (Or fastboot if you have it). No need to downgrade for anything :laugh: in the past you would have needed to downgrade in order to unlock the bootloader, now it's not even needed
Download EDL Tool by djkuz and install TWRP with that one. Or you can use axon7tool by tennear, but it's much more finicky and ran entirely by commands (no UI).
And just to avoid more trouble, DO NOT LOCK THE BOOTLOADER! You do that with the system even barely modified and you brick the phone. A bunch of people tried to do something, got scared because they made a simple correctable mistake and just locked the bootloader thinking everything would get restored to stock - doesn't work that way.
Not saying you will do this, but I've seen about 4 or 5 people that started just like you and ended up doing that
Click to expand...
Click to collapse
Wow, thanks so much for responding to this. Sounds like this should be easy! A couple of questions before I go about following your advice:
1). Do I download EDL Tool to my computer or phone??
2). If I'm downloading it to my computer, does it matter that I'm using a mac?
Thanks again for your help!
alajoy said:
Wow, thanks so much for responding to this. Sounds like this should be easy! A couple of questions before I go about following your advice:
1). Do I download EDL Tool to my computer or phone??
2). If I'm downloading it to my computer, does it matter that I'm using a mac?
Thanks again for your help!
Click to expand...
Click to collapse
Oh, skipped that part. EDL Tool is a .bat. I'm pretty sure you won't be able to run it on a Mac. If you can find a Windows PC somewhere to do this, it'd be much better...
But there's another way.
Issuing "adb reboot bootloader" effectively sends you into fastboot. That list you mentioned is fastboot (if it says "Start" in green, and you can scroll that, it is fastboot). Just use fastboot from the pc: Put TWRP on the fastboot folder on the PC, then issue "fastboot flash recovery twrp.img" with "twrp.img" being whatever the twrp file name is. After that issue "fastboot reboot recovery". And as soon as you are on TWRP, DON'T GET OUT OF IT. Just wipe data, system, caches; then flash a system (e.g. b10 bootstack and stocksystem), then also flash Magisk, and THEN boot to system
Choose an username... said:
Oh, skipped that part. EDL Tool is a .bat. I'm pretty sure you won't be able to run it on a Mac. If you can find a Windows PC somewhere to do this, it'd be much better...
But there's another way.
Issuing "adb reboot bootloader" effectively sends you into fastboot. That list you mentioned is fastboot (if it says "Start" in green, and you can scroll that, it is fastboot). Just use fastboot from the pc: Put TWRP on the fastboot folder on the PC, then issue "fastboot flash recovery twrp.img" with "twrp.img" being whatever the twrp file name is. After that issue "fastboot reboot recovery". And as soon as you are on TWRP, DON'T GET OUT OF IT. Just wipe data, system, caches; then flash a system (e.g. b10 bootstack and stocksystem), then also flash Magisk, and THEN boot to system
Click to expand...
Click to collapse
"adb reboot bootloader" takes me to the start up screen that says "your device software cannot be checked for corruption..." etc. and gives you 5 sec to either press up or down on volume keys to get to list: “power off, restart, recovery, fastboot, back to previous page”, but the list is all white. If I select "fastboot" it reboots the phone and starts that cycle over again at the "your device software cannot be checked for corruption..." etc page.
Nowhere am I given a chance to use fastboot commands. I'm never on the page with the green "Start".
..This all seemed a lot simpler on my Nexus 5..
Thanks for your help/patience.
alajoy said:
"adb reboot bootloader" takes me to the start up screen that says "your device software cannot be checked for corruption..." etc. and gives you 5 sec to either press up or down on volume keys to get to list: “power off, restart, recovery, fastboot, back to previous page”, but the list is all white. If I select "fastboot" it reboots the phone and starts that cycle over again at the "your device software cannot be checked for corruption..." etc page.
Nowhere am I given a chance to use fastboot commands. I'm never on the page with the green "Start".
..This all seemed a lot simpler on my Nexus 5..
Thanks for your help/patience.
Click to expand...
Click to collapse
I thought you had fastboot since you described the 5 seconds screen and both are very similar. It's normal not to have it though.
I think there's some version of axon7tool for Linux but I'm not sure at all. The best way would be to find a Windows computer.
I wonder how you actually installed TWRP the first time? Via fastboot?
As soon as you get TWRP you should be able to run a few commands to get fastboot back just to have it around.
Choose an username... said:
I thought you had fastboot since you described the 5 seconds screen and both are very similar. It's normal not to have it though.
I think there's some version of axon7tool for Linux but I'm not sure at all. The best way would be to find a Windows computer.
I wonder how you actually installed TWRP the first time? Via fastboot?
As soon as you get TWRP you should be able to run a few commands to get fastboot back just to have it around.
Click to expand...
Click to collapse
I have adb and fastboot installed on my Mac and I can't remember how I got it working on my phone in the first place, but I've only ever used a Mac for all this. Terminal recognizes my device and responds to commands until I try "fastboot flash recovery twrp.img" then it says "<waiting for any device>" and does nothing.
Thanks again for the help. I'll keep hunting though. I don't have access to any Windows computer.
Cheers
Hi,
I’ve got an older Verizon LG V20 that’s been bricked. I hid it in a drawer for the past year or so, and stumbled across it again. If I can get this fixed, I’d love to update it and give it as a gift to an older friend who has a 6 yr old crap android phone. But first, some history…
-bought used in great shape and rooted with Dirty Santa to run on TMobile. I don't recall which ROM I used, but it was very stock minus the carrier apps. My wife had a chance to go to Italy, so we bought a 3rd party european SIM with 30 days of data and voice from Three UK. Short story is that the phone never recognized the SIM, but she used it to take some great pics during her stay.
-once back in the US, I decided to try a different ROM and I think I flashed the wrong files or something… it’s my fault but I honestly can’t recall if I loaded a Samsung image instead, or what exactly happened.
Currently, the phone boots ONLY into fastboot mode. ADB does not recognize the device, and I’m thinking that I’ve lost TWRP Recovery since I can’t enter Recovery Mode at all.
If I do hold Vol Down + Power, I get a Hard Reset menu, but nothing in there helps.
I tried using LGUP, but the device is "not recognized."
I’m at a loss as to what to do at this point. If there IS a way to un-brick this, I think it would make a great phone for a good friend.
If anyone has any suggestions, I’d love any ideas that you may have. I tried looking to see if any other threads cover this, but I’m not seeing anything with specifics or pointers to How-Tos. If I missed the relevant links, I’d appreciate being pointed to them.
Also…
-if I can return to Stock condition, I can then unlock the bootloader and flash a more current ROM again. Would I need to pick a new radio so it better matches TMobile vs the Verizon setup it originally came with?
thanks for reading!
motionmonk
Since you can get to fastboot why not flash a twrp to see if you will get recovery
0x0null said:
Since you can get to fastboot why not flash a twrp to see if you will get recovery
Click to expand...
Click to collapse
When I run fastboot in Terminal, I get a blank response-- that is, a simple carraige return with no info listed.
This is on a fresh Win10 install with the latest Platform Tools package (Justt adb & fastboot) from the Android Studio website.
Are there other drivers that I need? When I installed LGUP, I did install the LGMobileDriver_WHQL_Ver_4.1.1.exe installer as well.
-motionmonk
motionmonk said:
When I run fastboot in Terminal, I get a blank response-- that is, a simple carraige return with no info listed.
This is on a fresh Win10 install with the latest Platform Tools package (Justt adb & fastboot) from the Android Studio website.
Are there other drivers that I need? When I installed LGUP, I did install the LGMobileDriver_WHQL_Ver_4.1.1.exe installer as well.
-motionmonk
Click to expand...
Click to collapse
That is bad, can you try it ona windows 7 PC?
0x0null said:
That is bad, can you try it ona windows 7 PC?
Click to expand...
Click to collapse
I could... I need to find my Win7 install disks for an old laptop.
I'll report back by tomorrow.
I don't do this often... what makes WIndows 7 a better method than Win 10?
-motionmonk
motionmonk said:
I could... I need to find my Win7 install disks for an old laptop.
I'll report back by tomorrow.
I don't do this often... what makes WIndows 7 a better method than Win 10?
-motionmonk
Click to expand...
Click to collapse
issues with drivers
It took longer than I thought to find my Win7 installers... I'm in the middle of the reinstall now.
I plan to load the Android Platform Tools, LG Mobile Drivers, LGUP framework... is there anything else I should install?
thanks for any suggestions; I don't root often at all and am rusty at this
-motionmonk
Win 7 update
Ok, I've installed WIN7, Android Platform Tools (just ADB & Fastboot), LG drivers and LGUP.
Now when I do the fastboot command, I get a true response:
fastboot devices
VS995aa11a111 fastboot (where a=letters, 1=numbers)
YAY!
So at this point, if I load a TWRP.zip, would I be able to boot into Recovery, instead of fastboot mode?
I checked the official TWRP website, and the latest is TWRP 3.2.3-0.
EDIT: I looked in the LG Section, and it appears that there is not an official TWRP for the LG V20. Is that right?
Having gotten to the point where the laptop recognizes the phone, I really don't want to make a dumb mistake :silly:
thanks for getting me this far!
-motionmonk
motionmonk said:
Win 7 update
Ok, I've installed WIN7, Android Platform Tools (just ADB & Fastboot), LG drivers and LGUP.
Now when I do the fastboot command, I get a true response:
fastboot devices
VS995aa11a111 fastboot (where a=letters, 1=numbers)
YAY!
So at this point, if I load a TWRP.zip, would I be able to boot into Recovery, instead of fastboot mode?
I checked the official TWRP website, and the latest is TWRP 3.2.3-0.
EDIT: I looked in the LG Section, and it appears that there is not an official TWRP for the LG V20. Is that right?
Having gotten to the point where the laptop recognizes the phone, I really don't want to make a dumb mistake :silly:
thanks for getting me this far!
-motionmonk
Click to expand...
Click to collapse
There is no official twrp build for the V20, search for Phoenix's unofficial twrp thread
Sent from my LG-H910 using XDA Labs
cnjax said:
There is no official twrp build for the V20, search for Phoenix's unofficial twrp thread
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Thank you cnjax... I think I got it now:
recovery-twrp-vs995-2018-10-18
Now that I have the TWRP Installer, I connect the phone (in perma-fastboot mode), and verify that it is connected by using fastboot devices. I get a recognition string in reply. So now I move on...
-rename recovery-twrp-vs995-2018-10-18.img as TWRP.img
-move TWRP.img to my platform-tools folder
-issue flashing command fastboot flash recovery TWRP.img
Here's what I get:
Sending 'recovery' (25984 KB)
OKAY [ 0.889s]
Writing 'recovery'
FAILED (REMOTE: 'unknown command'}
Finished. Total time: 1.092s
I'm pretty sure I have the syntax correct, and the TWRP.img file is being recognized, but -something- isn't working.
Have I missed something here?
thanks for any suggestions,
motionmonk
fastboot help pages
motionmonk said:
Now that I have the TWRP Installer, I connect the phone (in perma-fastboot mode), and verify that it is connected by using fastboot devices. I get a recognition string in reply. So now I move on...
-rename recovery-twrp-vs995-2018-10-18.img as TWRP.img
-move TWRP.img to my platform-tools folder
-issue flashing command fastboot flash recovery TWRP.img
Here's what I get:
Sending 'recovery' (25984 KB)
OKAY [ 0.889s]
Writing 'recovery'
FAILED (REMOTE: 'unknown command'}
Finished. Total time: 1.092s
I'm pretty sure I have the syntax correct, and the TWRP.img file is being recognized, but -something- isn't working.
Have I missed something here?
thanks for any suggestions,
motionmonk
Click to expand...
Click to collapse
Hi
I'm just a noob but I am interested in the problem you are having and am following it to see what comes up with it.
There is a good fastboot thread here:
https://forum.xda-developers.com/showthread.php?t=2277112
On the first page you have options to wipe before flashing - i.e. system, boot, data, RECOVERY etc,
Maybe give those pages a read while waiting for someone more knowledgeable to fix your phone...
Since you are not sure what happened maybe the modem was affected which I think is bad...
I think doing a "fastboot getvar all" might give you a status of what you are dealing with .... since it gives you versions
of things...
Anyhow, good luck reviving the phone - "rooting" for you haha!
---------- Post added at 10:33 PM ---------- Previous post was at 10:05 PM ----------
This link might also be a good read
https://forum.xda-developers.com/v20/how-to/guide-lg-v20-to-life-t3827732
secondhand2 said:
There is a good fastboot thread here:
https://forum.xda-developers.com/showthread.php?t=2277112
. . .
I think doing a "fastboot getvar all" might give you a status of what you are dealing with .... since it gives you versions
of things...[/url]
Click to expand...
Click to collapse
secondhand2,
THX for the links! Those were very helpful!
No need to call yourself a noob... I think I outrank you in that department at this point!
I did try your suggestion of fastboot getvar all, and found something interesting...
when I did the command it returned (bootloader) unlocked:no
which I thought was WEIRD, since the phone -was- unlocked with a custom ROM before I messed things up.
I have attached a screenshot to this msg with the full info report.
So now I'm wondering if that's why my previous attempt at flashing TWRP failed?
Does this mean I have a soft-brick or a hard-bricked phone at this point?
I"m learning more through everyone's help and input, but I'm still lost as to where to go from here.
Hi,
I have a US996 and I unlocked it using the lg web site - they send a bin file that you can use to unlock the phone.
There are different exploits on different versions of V20 phones. THere are also versions of Nougat that have an anti rollback that stop you from going from a recent OTA update back to an older one that can be exploited to get root. For example, on the US996 I have., if I had bought it and it had been patched with 10p (not 100% sure which version was the cutoff point) even if the phone was unlocked, I might not be able to get root. So the versions of the ROMs/firmware are imnportant. As it happened I had the 10f version so rooting was possible - but I followed the threads on this site for my specific phone and stuck to STOCK rom's.
So I'm not sure about what ROM you have - i..e which version of the vs995 is rootable after you unlock the phone. And the unlocking method to use - I'm not familiar with dirty santa or lafsploit (might not have spelled that correctly). There is a tool called LGUP and a good thread on that below that I was reading but it is long read which is good for learning.
I can only point you to some threads - but unlocking is the next hurdle.
You might also want to use the latest TWRP and Magisk if you do get to root the phone. I used PHOENIX591's TWRP
- there is a good thread on that. https://forum.xda-developers.com/v2...-t3720239/post78529520?nocache=1#post78529520
Sorry I can't help you more with this - you do need to get the phone unlocked first. Some of these things are very device specific
I'm still keeping an interested eye on this...
Here is the other thread
https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
Good Luck!
secondhand2 said:
Hi,
I have a US996 and I unlocked it using the lg web site - they send a bin file that you can use to unlock the phone.
There are different exploits on different versions of V20 phones. THere are also versions of Nougat that have an anti rollback that stop you from going from a recent OTA update back to an older one that can be exploited to get root. For example, on the US996 I have., if I had bought it and it had been patched with 10p (not 100% sure which version was the cutoff point) even if the phone was unlocked, I might not be able to get root. So the versions of the ROMs/firmware are imnportant. As it happened I had the 10f version so rooting was possible - but I followed the threads on this site for my specific phone and stuck to STOCK rom's.
So I'm not sure about what ROM you have - i..e which version of the vs995 is rootable after you unlock the phone. And the unlocking method to use - I'm not familiar with dirty santa or lafsploit (might not have spelled that correctly). There is a tool called LGUP and a good thread on that below that I was reading but it is long read which is good for learning.
I can only point you to some threads - but unlocking is the next hurdle.
You might also want to use the latest TWRP and Magisk if you do get to root the phone. I used PHOENIX591's TWRP
- there is a good thread on that. https://forum.xda-developers.com/v2...-t3720239/post78529520?nocache=1#post78529520
Sorry I can't help you more with this - you do need to get the phone unlocked first. Some of these things are very device specific
I'm still keeping an interested eye on this...
Here is the other thread
https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
Good Luck!
Click to expand...
Click to collapse
You're incorrect arb hasn't been incremented on the 996
Sent from my LG-H910 using XDA Labs
Hi cnjax
The thread I used discussed arb but from what I remember it was never clear how to know which arb ( 0 or 1 ) a particular update was at. Are you saying there is never an increment for the us996?
Thank you for clarifying
secondhand2 said:
Hi cnjax
The thread I used discussed arb but from what I remember it was never clear how to know which arb ( 0 or 1 ) a particular update was at. Are you saying there is never an increment for the us996?
Thank you for clarifying
Click to expand...
Click to collapse
Was just pointing out that through the 996 oreo release lg hasn't incremented arb on the 996
Sent from my LG-H910 using XDA Labs
Hi cnjax
It is a bit difficult to read everything n get a clear picture sometimes. I'm hoping you would clarify something
If TWRP is not installed and the phone is unlocked but not rooted which method could be used to install oreo 20f?
Would you be forced to install 10f (nougat) to root and install twrp first before moving on to oreo?
In this scenario I assumed nougat was on the phone originally and it seems the phone is locked from the fastboot info given...but let's say it gets unlocked
Is there a method to install oreo first instead of starting with nougat and version 10f? If there is that would be awesome
Thank you!
secondhand2 said:
Hi cnjax
It is a bit difficult to read everything n get a clear picture sometimes. I'm hoping you would clarify something
If TWRP is not installed and the phone is unlocked but not rooted which method could be used to install oreo 20f?
Would you be forced to install 10f (nougat) to root and install twrp first before moving on to oreo?
In this scenario I assumed nougat was on the phone originally and it seems the phone is locked from the fastboot info given...but let's say it gets unlocked
Is there a method to install oreo first instead of starting with nougat and version 10f? If there is that would be awesome
Thank you!
Click to expand...
Click to collapse
If his bootloader is locked he'll need to downgrade, root and unlock the bootloader with dirty santa, flash updated twrp, flash a rom and magisk
Sent from my LG-H910 using XDA Labs
Post #71 about dumping contents/partitions with lgup seems a good idea -
Then I would try fastboot oem unlock to see what happens but not sure if that can break the bootloader or not. I think you would be in a deeper hole if it went south on you. I'm not sure if doing fastboot oem unlock can be risky at this point
Sooo.... I was attempting to root the lenovo m8 fhd, attempted typical magisk install. It failed. I thought I was clever, used lenovo moto smart assistant, downloaded the firmware, swapped out the downloaded boot.img for a modified one, and used the rescue function to flash it.
Well, I missed the fact that there were checksums in another file, and the device is stuck in bootloop, and won't load the modified firmware ?.
I'm attempting to flash the stock firmware with Lmsa, but it hangs at 40%. Anyone familiar with these issues? I gave up on root, functioning unrooted tab is bette than soft brick any day. Suggestions?
Yeah you can put it in Fastboot mode and flash each component individually with the firmware from lenovo rescue site via terminal (Linux) or power shell (win)
https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/
I have recovered from same boot loop and successfully rooted w magisk... I needed to flash all components... Boot, system, vendor, etc, even cache
konchog uma said:
Yeah you can put it in Fastboot mode and flash each component individually with the firmware from lenovo rescue site via terminal (Linux) or power shell (win)
https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/
I have recovered from same boot loop and successfully rooted w magisk... I needed to flash all components... Boot, system, vendor, etc, even cache
Click to expand...
Click to collapse
Are you talking about TB-8705F? If YES how did you unlock the bootloader? The "fastboot oem unlock-go" command is rejected by my tablet. Or is it possible to root without unlocking the bootloader? Thank you!
---------- Post added at 08:00 PM ---------- Previous post was at 07:57 PM ----------
FabulousTooth said:
Sooo.... I was attempting to root the lenovo m8 fhd, attempted typical magisk install. It failed. I thought I was clever, used lenovo moto smart assistant, downloaded the firmware, swapped out the downloaded boot.img for a modified one, and used the rescue function to flash it.
Well, I missed the fact that there were checksums in another file, and the device is stuck in bootloop, and won't load the modified firmware .
I'm attempting to flash the stock firmware with Lmsa, but it hangs at 40%. Anyone familiar with these issues? I gave up on root, functioning unrooted tab is bette than soft brick any day. Suggestions?
Click to expand...
Click to collapse
I did exactly the same (haha, same assumptions and same bad memory). My tablet was in a very short boot loop, like 5 sec per loop. I did recover it with Lenovo Rescue and Smart Assitant. Had to do it twice but it worked.
G0bl1n said:
Are you talking about TB-8705F? If YES how did you unlock the bootloader? The "fastboot oem unlock-go" command is rejected by my tablet. Or is it possible to root without unlocking the bootloader? Thank you!
Yes. Goblin, try "fastboot oem flashing"... Look into it, there is a newer command than unlock, I don't have a lot of time now but do a quick search and you'll find the info you need
Click to expand...
Click to collapse
Thanks for the responses! I actually managed to fix it. LMSA kept hanging, and if the tablet was on it went into a bootloop.
I fixed it completely on accident, by plugging it in while off, starting the firmware flash, and shortly after it started "flashing" the firmware, i pressed the power button to turn it on. from there it worked like a charm!
Has anyone been able to eliminate or properly modify the firmware hashes to successfully root this device? magisk was a no go, and the (i thought) slick sh*t i pulled soft-bricked it. Regardless, Ill take a working unbricked tablet over a brick anyday.
konchog uma said:
G0bl1n said:
Are you talking about TB-8705F? If YES how did you unlock the bootloader? The "fastboot oem unlock-go" command is rejected by my tablet. Or is it possible to root without unlocking the bootloader? Thank you!
Yes. Goblin, try "fastboot oem flashing"... Look into it, there is a newer command than unlock, I don't have a lot of time now but do a quick search and you'll find the info you need
Click to expand...
Click to collapse
Thanks man, I was able to unlock my bootloader! Here is the info:
https://source.android.com/setup/build/running#unlocking-recent-devices
Click to expand...
Click to collapse
Nice work goblin
Check out the other thread on this tablet here on xda... There's no dedicated device page but there are a few threads and the other has rooting instructions, and instructions to get viper4android working
---------- Post added at 12:46 AM ---------- Previous post was at 12:04 AM ----------
FabulousTooth said:
Thanks for the responses! I actually managed to fix it. LMSA kept hanging, and if the tablet was on it went into a bootloop.
I fixed it completely on accident, by plugging it in while off, starting the firmware flash, and shortly after it started "flashing" the firmware, i pressed the power button to turn it on. from there it worked like a charm!
Has anyone been able to eliminate or properly modify the firmware hashes to successfully root this device? magisk was a no go, and the (i thought) slick sh*t i pulled soft-bricked it. Regardless, Ill take a working unbricked tablet over a brick anyday.
Click to expand...
Click to collapse
Yeah I had the same with LSMA recovery it froze at 40% or something
Then bootloop lol
There's a map file in the factory image that LSMA let's you download... I'm actually on my tab right now and the archive is on another computer so I can't see what its called but it's like a txt file I think maybe the only one. If you install all the parts to their respective partitions, you can get the tab back. So if you bork it again just flash manually.
I successfully rooted with magisk, but don't follow the instructions on magisk site, they'll tell you to patch the recovery.img... I did it by patching boot.img and it did work but not on the first try lol... I did it again and it worked.
My advice is definitely stay at it mate, it's doable... Without struggle there is no victory lol
Hey everyone,
I've been looking for options to Install a custom Rom or root since I bought the Tablet several month ago. It seems like there are some options for the Full Hd Version, but I have a hard time finding anything useful for the 125FU. Are there any recommendations like compatible GSI roms or TWRP/magisk?
Thanks in advance for your help!
You should just be able to install matiek form my understanding
I need some information, too. Bootloader unlock is different. Device doesn't respond to bootloader commands with Minimal ADB Fastboot 1.4.3.
holmesmalone said:
I need some information, too. Bootloader unlock is different. Device doesn't respond to bootloader commands with Minimal ADB Fastboot 1.4.3.
Click to expand...
Click to collapse
I just got an tb125fu
Bootloader unlock was no problem, maybe it works for you now with the latest versions?
art99 said:
I just got an tb125fu
Bootloader unlock was no problem, maybe it works for you now with the latest versions?
Click to expand...
Click to collapse
The issue I had, and resolved, was the lack of the latest fastboot drivers. Gained root with Magisk successfully.
holmesmalone said:
The issue I had, and resolved, was the lack of the latest fastboot drivers. Gained root with Magisk successfully.
Click to expand...
Click to collapse
I installed corvus os gsi on it. i have no custom recovery.
peteonu said:
I installed corvus os gsi on it. i have no custom recovery.
Click to expand...
Click to collapse
TWRP is convenient, but not absolutely necessary. Would like a Lineage rom though.
holmesmalone said:
TWRP is convenient, but not absolutely necessary. Would like a Lineage rom though.
Click to expand...
Click to collapse
Agreed. I've been looking into compiling TWRP myself but this is all new to me. The only device with TWRP with this chipset is the Redmi 9. I've compared both boot.img's and they are both setup differently. If I had more knowledge ont he subject I could easily achieve this I believe.
If I have time I'll compare Gen 2 vs Gen 3 boot.img's, that may help understand the folder and file structure better.
holmesmalone said:
The issue I had, and resolved, was the lack of the latest fastboot drivers. Gained root with Magisk successfully.
Click to expand...
Click to collapse
What process did you use with magisk to gain root after bootloader unlock? was it as simple as installing magisk manager and flashing root through the manager?
Thanks
el7145 said:
What process did you use with magisk to gain root after bootloader unlock? was it as simple as installing magisk manager and flashing root through the manager?
Thanks
Click to expand...
Click to collapse
The same process worked for me.
holmesmalone said:
The same process worked for me.
Click to expand...
Click to collapse
How did you obtain the boot.img to patch??? I cant find the stock firmware anywhere, and im not clear on pulling the stock boot.img (getting permission denied errors when attempting via adb)
el7145 said:
How did you obtain the boot.img to patch??? I cant find the stock firmware anywhere, and im not clear on pulling the stock boot.img (getting permission denied errors when attempting via adb)
Click to expand...
Click to collapse
Select and download your preferred rom. Then unzip the rom and in the unzipped folder select the boot.img file and use it.
With some devices and roms, under some circumstances, the vbmeta.img file can and should be used. If I can recall correctly, Magisk will specify.
holmesmalone said:
Select and download your preferred rom. Then unzip the rom and in the unzipped folder select the boot.img file and use it.
With some devices and roms, under some circumstances, the vbmeta.img file can and should be used. If I can recall correctly, Magisk will specify.
Click to expand...
Click to collapse
ok, so ur just pulling the boot img from one of the GSI roms...im just trying to pull the stock boot img...do you happen to know where one can download the stock firmware for this device, this is my 1st lenovo tablet
el7145 said:
ok, so ur just pulling the boot img from one of the GSI roms...im just trying to pull the stock boot img...do you happen to know where one can download the stock firmware for this device, this is my 1st lenovo tablet
Click to expand...
Click to collapse
LMSA. https://pcsupport.lenovo.com/us/en/downloads/ds101291-rescue-and-smart-assistant-lmsa
Use this tool. Install and explore the file and folder structure it creates. Interrupt the process before it flashes your tablet for it will erase the files you need from your computer if you don't. Use trial and error here.
Since the original question was about root, Ill keep this going
I was able to download the most recent ROM from Lenovo rescue which was super simple, it downloads the ROM first and wont start the flash till you click the button. I did retrieve the stock boot.img, patched it, and flashed it, rebooted and had root. Heres where the many hours of fun started...I realized my wifi wasnt working (good sign something was messed up during flash). I realize the ROM downloaded from the Lenovo Rescue was newer then my old ROM. So I had flashed the newer boot.img over the old ROM (not good). I went back to Lenovo rescue to actually make use of the rescue and flash a full ROM. After completion I became stuck in fastboot mode. I could boot to recovery but not system and every restart or shutdown and restart would go straight to fastboot.
I did try to manually flash the ROM using what i thought was the right files and order (using flashinfo.txt as the order and MT6768_Android_scatter.txt for the partition names for each image). Everything flashed successfully, but upon reboot I was still stuck in fastboot mode. I tried everything I could think of and even ran the Lenovo Rescue a few times.
After many hours, I came across this command for fastboot..."fastboot set_active a" which finally allowed me to boot into system. I assume this tablet uses the A/B slot partitions, but I think they only make use of the A for boot? Thats my thought
So next is too try to patch the correct disc.img for my current rom (which is the latest from Lenovo Rescue) and flash again making sure to flash to the boot_a partition and hopefully everything goes like it should
Hopefully that command helps someone save many hours if they find themselves stuck in fastboot mode while rooting and/or flashing.
el7145 said:
Since the original question was about root, Ill keep this going
I was able to download the most recent ROM from Lenovo rescue which was super simple, it downloads the ROM first and wont start the flash till you click the button. I did retrieve the stock boot.img, patched it, and flashed it, rebooted and had root. Heres where the many hours of fun started...I realized my wifi wasnt working (good sign something was messed up during flash). I realize the ROM downloaded from the Lenovo Rescue was newer then my old ROM. So I had flashed the newer boot.img over the old ROM (not good). I went back to Lenovo rescue to actually make use of the rescue and flash a full ROM. After completion I became stuck in fastboot mode. I could boot to recovery but not system and every restart or shutdown and restart would go straight to fastboot.
I did try to manually flash the ROM using what i thought was the right files and order (using flashinfo.txt as the order and MT6768_Android_scatter.txt for the partition names for each image). Everything flashed successfully, but upon reboot I was still stuck in fastboot mode. I tried everything I could think of and even ran the Lenovo Rescue a few times.
After many hours, I came across this command for fastboot..."fastboot set_active a" which finally allowed me to boot into system. I assume this tablet uses the A/B slot partitions, but I think they only make use of the A for boot? Thats my thought
So next is too try to patch the correct disc.img for my current rom (which is the latest from Lenovo Rescue) and flash again making sure to flash to the boot_a partition and hopefully everything goes like it should
Hopefully that command helps someone save many hours if they find themselves stuck in fastboot mode while rooting and/or flashing.
Click to expand...
Click to collapse
I'm trying to solve the fastboot issue but I can't find fastboot drivers for the tablet. Have any suggestions?
Siege9929 said:
I'm trying to solve the fastboot issue but I can't find fastboot drivers for the tablet. Have any suggestions?
Click to expand...
Click to collapse
im assuming in device manager, you have a yellow exclamation by "Android"? you need the mediatek drivers.
Go here https://developer.android.com/studio/run/oem-usb
scroll down, dont make the misake of clicking on "Lenovo", you are clicking on the section labeled "MTK" download the zip, go to device manager and manually update the driver, once updated fastboot should work
at cmd run "fastboot devices" to make sure your device is recognized
el7145 said:
im assuming in device manager, you have a yellow exclamation by "Android"? you need the mediatek drivers.
Go here https://developer.android.com/studio/run/oem-usb
scroll down, dont make the misake of clicking on "Lenovo", you are clicking on the section labeled "MTK" download the zip, go to device manager and manually update the driver, once updated fastboot should work
at cmd run "fastboot devices" to make sure your device is recognized
Click to expand...
Click to collapse
Manually selecting the "Android Bootloader" driver fixed it. Thanks!
I just got my TB125FU to replace my 7-year-old Google Pixel C on its last legs.
Its Hardware ID is USB\VID_0E8D&PID_201C&REV_0100
I found a pack of Mediatek drivers here.
It's a bloated pack, so I extracted just the files needed for the TB125FU and attached to this post.
Once installed, my tablet appeared with a "fastboot devices" command.
I have also had good luck with the latest firmware for Motorola/Lenovo devices here.
hugehead83 said:
I have also had good luck with the latest firmware for Motorola/Lenovo devices here.
Click to expand...
Click to collapse
just an fyi: thats not the most recent firmware, the lenovo rescue tool had the latest, which at the moment for my device a few days ago was TB125FU_S000118_220927_ROW