I want a nandroid backup so I can play with the system with a chance of fixing it. The bootloader is locked up tighter than a drum... Until this phone gets unlocked (it will be cold by then) or "bump'd" (more likely), does anyone think they can get a tethered TWRP working on our device? The H815 has an official working TWRP (courtesy of @Dees_Troy) on it. Could this version somehow be used via a tether? My Intel Baytrail tablet's bootloader is locked and we are loading TRWP from a PC - http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 .
Related
LG GPad - V50020a...
Rooted w/ towelroot.apk
Recovery installed w/ Flashify
Trying to reboot into TWRP gives ==>>> Secure booting error! Cause : boot certification verify
Questions:
*If I unlock bootloader will I be able to boot into TWRP recovery?
*Is the locked bootloader actually preventing me from having a soft brick?
*Can V50020a (4.4.2) actually have a custom recovery/rom?
NB, through searching and reading, I've come across one person claiming to have TWRP working on 4.4.2 V50020a. (No guide/instructions were provided though)
Also, there doesn't look like any roms are available for my version...
*If there aren't any roms etc. for my variant, there probably isn't much point going to all this trouble.
King_Rat said:
LG GPad - V50020a...
Rooted w/ towelroot.apk
Recovery installed w/ Flashify
Trying to reboot into TWRP gives ==>>> Secure booting error! Cause : boot certification verify
Questions:
*If I unlock bootloader will I be able to boot into TWRP recovery?
*Is the locked bootloader actually preventing me from having a soft brick?
*Can V50020a (4.4.2) actually have a custom recovery/rom?
NB, through searching and reading, I've come across one person claiming to have TWRP working on 4.4.2 V50020a. (No guide/instructions were provided though)
Also, there doesn't look like any roms are available for my version...
*If there aren't any roms etc. for my variant, there probably isn't much point going to all this trouble.
Click to expand...
Click to collapse
Search aboot in TWRP thread. You need to downgrade, should be a script by id10terror to make it easy.
Hi all,
I have my g4 rooted on stock. Locked bootloader. And still on LP. When i check to see if there is a system update it says i am on the latest version (im in the uk). Is there a way to spoof where i am to get a system update?
You can use LGUP to install a new version of android (6.0). But you will lose root access.
For this method (LGUP) you don't need to unlock your botloader.
The way to install kdz is on this forum. Good luck
I was looking for a way that i dodnt have to use a pc. (due to lack of time at home) also why are all these tools windows tools? No linux love? If a pc is needed i will just unlock the bootloader and put a custom rom on
Hey everyone,
I apologize in advance if this is breaking any forum rules or if it's a super noob question, but here goes.
I've got a stock AT&T V410 running Lollipop (had I known it would be such a hassle to root, I would've stayed on KitKat).
It's no longer under warranty so I'm thinking about rooting. Unfortunately, the only option that might work is KingRoot. Taking into consideration the possible "shadiness" of KingRoot, here is my idea:
1) Remove microSD and factory reset my V410. This is to have as little info on my V410 as possible before running KingRoot. If I can, I'll even skip adding my Google account.
2) Run KingRoot and see if the root is successful.
3) If successful, install Flashify and flash TWRP (which version should I flash?)
4) If not successful, do another factory reset and continue using my V410 like before.
5) After successfully flashing TWRP, I'll probably do another factory reset, if necessary, to have a clean OS without KingRoot.
6) With TWRP installed, I should be able to make a backup of my current V410 OS, right? I'd like to have this in case I try out CM and want to go back.
I think that's it. Assuming KingRoot can root my V410, does everything here seem viable? I know when I unlocked the bootloader on my OPO it basically did a factory reset anyway, but I want to be safe with KingRoot.
TL;DR
Will a factory reset remove KingRoot? Can I install TWRP and keep the original LG OS?
Won't work. The lollipop bootloader can't be unlocked, and I'm not aware of any exploits. TWRP won't boot. Stay on the lollipop bootloader and you're stuck with kingroot, stock rom, and stock recovery to the best of my knowledge.
I have heard of some methods to try to swap kingroot for supersu once you gain root, but I've also heard of that making a colossal mess with this tablet. Never dug into it, but I suspect supersu attempts to patch the boot image, messes up the signature, then the tab won't boot due to the locked bootloader.
The kitkat bootloader was locked too, but it was susceptible to the bump exploit that let us sign our own boot images.
If you're interested in TWRP and custom roms there is a route to downgrade back to the kitkat bootloader, but it sounds like a giant hassle.
Another random thought, there is a way to enable fastboot on this tablet (you would need root to do it). This method is for the LG G2, but it works fine on my V410. Maybe you could extract the partition images from the kdz in that thread linked above and flash them manually with fastboot instead of LG Flashtool, and get back to kitkat without making such a mess of the internal storage. Disclaimer: I haven't tried this and it could end poorly!!! :silly:
jason2678 said:
Won't work. The lollipop bootloader can't be unlocked, and I'm not aware of any exploits. TWRP won't boot. Stay on the lollipop bootloader and you're stuck with kingroot, stock rom, and stock recovery to the best of my knowledge.
I have heard of some methods to try to swap kingroot for supersu once you gain root, but I've also heard of that making a colossal mess with this tablet. Never dug into it, but I suspect supersu attempts to patch the boot image, messes up the signature, then the tab won't boot due to the locked bootloader.
The kitkat bootloader was locked too, but it was susceptible to the bump exploit that let us sign our own boot images.
If you're interested in TWRP and custom roms there is a route to downgrade back to the kitkat bootloader, but it sounds like a giant hassle.
Another random thought, there is a way to enable fastboot on this tablet (you would need root to do it). This method is for the LG G2, but it works fine on my V410. Maybe you could extract the partition images from the kdz in that thread linked above and flash them manually with fastboot instead of LG Flashtool, and get back to kitkat without making such a mess of the internal storage. Disclaimer: I haven't tried this and it could end poorly!!! :silly:
Click to expand...
Click to collapse
Thanks for the reply jason2678
Good to know that even if I could root my V410, I wouldn't be able to unlock the bootloader, which is my whole reason for rooting. And yeah, current methods to downgrade to KitKat seems like a real pain; for the time being it seems like I shouldn't mess with what works
Hello,
I bought a Zenfone 2 in 2015 and have loved it ever since. Back then it was simple to root, unlock the bootloader, and neither required the other.
To root, just enable ADB and run this.
To unlock the bootloader, just download this from azus.
Now, buying a phone fresh, to remove all the bloat is becoming a challenge.
To root, you need an unlock the bootloader. To unlock the bootloader, you need to downgrade to an early 5.0 image.
So I downgrade, unlock the bootloader, and root. To get back on 6, I need to upgrade to a newer version of 5.0, so I do. Root gone, bootloader still unlocked, splash screen is normal. Fine, I root again.
Finally, after upgrading to 6.0 (using adb sideload) both root and the bootloader unlock are gone. So I have to start again, and either live with unbloated 5.0, or unrooted, bloated 6.0.
As far as I can tell the only way around this is downgrade to 5.0, unlock my bootloader, then flash a pre rooted unsigned system.img.
Sadly I cannot find a recent pre rooted unsigned system.img, and have no way of knowing how to create one. If someone could help me make one I would greatly appreciate it.
Am I doing this all wrong? Is there a better way?
Because now I have a phone that I'm either stuck with a buggy 5.0 or a bloated 6.0; and the original, two year old zenfone is stuck in the bootloader because I was experimenting with various tools from around here.
I am well aware that I could just nuke the old phone with xFSTK to get out, but I refuse to. I have no such problems nuking the new one though.
Any and all help would be greatly appreciated, the Zenfone 2 is still a great device and is fantastic value for money, so if I can sort out all this I will happily make a full, comprehensive guide with my new knowledge to replace the errors in the outdated one here, and to add far more comprehensive knowledge about unbricking:
https://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Thank you all for your time
assuming you are already on MM version ww4.21.10.233... if no update to this version and download the following tool..
https://drive.google.com/open?id=0B72QQTXqZSRwTDNtU1N6OEdMdmM
reboot phone in fastboot mode. now extract the downloaded zip and double click unlock.bat phone will reboot 2 times. then you will get white screen and stuck there. when you see white screen. simply turn off mobile. reboot in fastboot mode with volume plus and power button. and run restore.bat from extracted zip.
now download twrp from official twrp website version 3.1.1.0. and flash it in fastboot mode. hope you know how to ( place twrp image in adb fastboot tool and open command windows in same folder reboot phone in fastboot mode and connect to pc. run the following command
fastboot flash recovery twrp-3.1.1-0-Z00A.img
then use volume button to find recovery mode and click power button to boot into twrp.
now download super su from following link use this version only as i have just tested it few minutes ago.
https://download.chainfire.eu/1114/SuperSU/SR1-SuperSU-v2.82-SR1-20170608224931.zip
place superuser zip on internal memory or sd card and click install in twrp and install super userzip. alternatively you can sideload supersu zip as well. then wipe cache and dalvik cache and reboot system. note phone may bootloop or restart 2,3 times. don't interrupt it. it will boot itself into system.
this is 100 percent safe way.
---------- Post added at 11:12 PM ---------- Previous post was at 11:05 PM ----------
x86fanboy said:
Hello,
I bought a Zenfone 2 in 2015 and have loved it ever since. Back then it was simple to root, unlock the bootloader, and neither required the other.
To root, just enable ADB and run this.
To unlock the bootloader, just download this from azus.
Now, buying a phone fresh, to remove all the bloat is becoming a challenge.
To root, you need an unlock the bootloader. To unlock the bootloader, you need to downgrade to an early 5.0 image.
So I downgrade, unlock the bootloader, and root. To get back on 6, I need to upgrade to a newer version of 5.0, so I do. Root gone, bootloader still unlocked, splash screen is normal. Fine, I root again.
Finally, after upgrading to 6.0 (using adb sideload) both root and the bootloader unlock are gone. So I have to start again, and either live with unbloated 5.0, or unrooted, bloated 6.0.
As far as I can tell the only way around this is downgrade to 5.0, unlock my bootloader, then flash a pre rooted unsigned system.img.
Sadly I cannot find a recent pre rooted unsigned system.img, and have no way of knowing how to create one. If someone could help me make one I would greatly appreciate it.
Am I doing this all wrong? Is there a better way?
Because now I have a phone that I'm either stuck with a buggy 5.0 or a bloated 6.0; and the original, two year old zenfone is stuck in the bootloader because I was experimenting with various tools from around here.
I am well aware that I could just nuke the old phone with xFSTK to get out, but I refuse to. I have no such problems nuking the new one though.
Any and all help would be greatly appreciated, the Zenfone 2 is still a great device and is fantastic value for money, so if I can sort out all this I will happily make a full, comprehensive guide with my new knowledge to replace the errors in the outdated one here, and to add far more comprehensive knowledge about unbricking:
https://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Thank you all for your time
Click to expand...
Click to collapse
do you state that you have an old device which you are unable to revive with xFSTK. what error do you get? put device on charge for 5,6 hours with original charger and use the following guide. use correct gp flag value use 4 zeros not 5
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
wow, no need to do all this... just use one of the available tool, my prefered one is this one:
https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293
very easy to use, to unlock, it will temporaly downgrade your boot to 5.0, unlock bootloader, then reflash boot 6.0.
Once there, just flash TWRP recovery and Magisk, from the tools.
I also had a locked ZF2 in MM 6.0 and using this tool it took less than 5 minutes to have an unlocked rooted phone, and I haven't wiped or lost anything.
I wasn't fully stock and relocked the bootloader (stupid thing to do, i know) and now it seems like it's bricked as I can't boot to recovery or anything.
Is there ANY way I can fix this without replacing the phone? Or is it destroyed?
You can try using these Lineage OS installation instructions to see if you can get the bootloader unlocked again before you can attempt to start over getting the phone working again.
Install LineageOS on taimen | LineageOS Wiki
wiki.lineageos.org
Trixelit said:
I wasn't fully stock and relocked the bootloader (stupid thing to do, i know) and now it seems like it's bricked as I can't boot to recovery or anything.
Is there ANY way I can fix this without replacing the phone? Or is it destroyed?
Click to expand...
Click to collapse
Without a working recovery there is no way to restore the unit short of paying Google for the privilege. The LineageOS instructions provided will not work as they require the bootloader to be unlocked. Flashing an OTA image from Google also will not work as it requires the stock recovery be present.
Strephon Alkhalikoi said:
Without a working recovery there is no way to restore the unit short of paying Google for the privilege. The LineageOS instructions provided will not work as they require the bootloader to be unlocked. Flashing an OTA image from Google also will not work as it requires the stock recovery be present.
Click to expand...
Click to collapse
That sucks, at least I know not to do that again. (I'm glad that I only did that on my backup phone, not my main phone)