Ok, so I managed to unlock bootloader by accident. I flashed a theme on TWRP 2.8.3.1 blastagator, and it bricked my device, theme was for a earlier version of TWRP, but I flashed it anyway. Phone would only boot into fastboot mode, so since I was in that mode, I decided to try " fastboot oem unlock " and was successful in unlocking the bootloader. I had to use a flash tool to flash back to stock LS980 ZVE, so that relocked the bootloader. I wanted to try downgrading to the OS that the phone shipped with when it dropped, to see if my bootloader would remain unlocked. Or, a modified version of a TOT file, to flash once bootloader is unlocked. Maybe one of these bad azz devs could accomodate us, and help gain full root on this device. I'm willing to test it out if someone could modify a TOT or boot.img or something. Just an idea!!!!!!!!
Stump Root works fine on the G2 with ZVE, you just have to do the brute force method - Stump Root will try to do the typical root first (press the button to "Grind" it which will fail), then it'll say "press button to brute force" or something like that, press it and then wait maybe 1-2 mins, just leave it alone till it's done. When it is done it'll say "reboot to root" so reboot immediately at that point, don't even bother closing Stump Root or anything - press the power button, choose restart, and when it reboots it'll start up twice (it will start, then reboot, then start again and finish at the lock screen) and after that you'll be rooted.
Update SuperSU if necessary and you'll be good to go. Install AutoRec to get recovery in place (older version 2.7.0.0) then update that to the latest (2.8.4.0) and you're ready for a custom ROM or whatever at that point.
I've done this a few times on my G2 so it's a non-issue process anymore.
Hello, already rooted. Talking about unlocking bootloader to run fastboot commands. Without fastboot, we're only half rooted. Read up on full root.
Related
i have been searching these forums for the past few days and have come up dry.. i have an htc rezound and I want the OTA BUT i have perm rooted it and removed most (if not all) the bloat... how do i go about rebloat and relocking my phone? i have tried using cleantool and it keeps waiting for the phone or it just fails all over itself repeatedly
edit: i have it set to charge only, sync is off and closed, and it is in fastboot mode. I have also tried something I found on here which seems like it is very similar to cleantools with less functionality and it just says <waiting for device> indefinitely
twich12 said:
i have been searching these forums for the past few days and have come up dry.. i have an htc rezound and I want the OTA BUT i have perm rooted it and removed most (if not all) the bloat... how do i go about rebloat and relocking my phone? i have tried using cleantool and it keeps waiting for the phone or it just fails all over itself repeatedly
edit: i have it set to charge only, sync is off and closed, and it is in fastboot mode. I have also tried something I found on here which seems like it is very similar to cleantools with less functionality and it just says <waiting for device> indefinitely
Click to expand...
Click to collapse
There are a few different ways to do it. Easiest way I did it to make it foolproof, is flash stock recovery if your on a custom recovery and relock phone and run the RUU. It will put you back to stock and you can just download the OTA and update it, then Unlock and flash Amon Ra recovery and from the developer menu install SU and superuser to reroot.
If you need more instructions , just ask otherwise to me that was the easiest way.
P.S. Just be aware the internal SD card gets wiped after you unlock again so move anything off the internal SD to the external SD that you want to save prior to unlocking again.
I didnt take the ota, I used cons ota rom.. this was my steps for that
1) download rom from here http://forum.xda-developers.com/showthread.php?t=1467329
2) boot into recovery, flash rom....
here you can go two ways, if you dont want the new baseband, it will flash the ph98img and not do anything, if you want the new radios I will tell you how I did it, then tell you where you need to start if you wont want them.
3)perform nandroid
4)via adb (thing you used to unlock originally) fastboot oem lock YOU ARE NOW LOCKED.
5)boot into hboot it will flash the ph98img
6) Unlock bootloader (find the email with the unlock.bin code and follow those instructions)
7)Reboot phone
8)connect to pc, charge only usb debugging enabled
9)run one click root
Proceed with this if you get the mainver error ONLY otherwise if having wifi issues, proceed to step 13
10) after rooted follow this post http://forum.xda-developers.com/showthread.php?t=1467099 NOTE, op in the thread supplied his miscnew.img USE IT!
11)Read this thread http://forum.xda-developers.com/showthread.php?t=1459347&highlight=mainver it will explain how to get the ph98s to work.
11a) do the ph98 file thing to the ph98 img in amon ra to get it to flash in bootloader
12) after amon ra is restored, perform restore nandroid.
If wifi is not working, even if you dont have mainver issues do step 13
13) If having wifi issues as in not working go to this thread http://forum.xda-developers.com/showthread.php?t=1467793 and follow instructions EXACTLY!!!
Now you should be running new radios, hb2.11, the 2.6 kernel etc.
You will have to follow the post in step 11 to get any ph to work from now on.
I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE, BURN YOUR HOUSE DOWN OR ABDUCTED BY ALIENS BY FOLLOWING THE ABOVE INSTRUCTIONS.
im having some trouble getting into recovery because clockworkmod says it does not have an officially supported recovery... how do i manually install one?
Assuming you installed a recovery, just boot to Hboot. Pull the battery, then hold the power button and volume down button. Once in Hboot you can choose Recovery.
twich12 said:
im having some trouble getting into recovery because clockworkmod says it does not have an officially supported recovery... how do i manually install one?
Click to expand...
Click to collapse
To flash a recovery do the above steps to get into hboot (power down, pull battery, hold volume down and power buttons) and once you are in hboot, choose fastboot. Then connect to your pc and in the pc cmd prompt type:
fastboot flash recovery nameofrecovery.img (name of stock recovery you need to download, trying to find a link for you...)
That will put the stock recovery on the phone, then you can run RUU to get the rest back to stock and you can then accept the OTA.
feralicious said:
To flash a recovery do the above steps to get into hboot (power down, pull battery, hold volume down and power buttons) and once you are in hboot, choose fastboot. Then connect to your pc and in the pc cmd prompt type:
fastboot flash recovery nameofrecovery.img (name of stock recovery you need to download, trying to find a link for you...)
That will put the stock recovery on the phone, then you can run RUU to get the rest back to stock and you can then accept the OTA.
Click to expand...
Click to collapse
got it! OTA and everything.. debating on rerooting for a bit thanks a lot everyone! +rep
All you have to do to reroot now is flash Amon Ra and then install su from within that. So it's super easy at this point.
su seems to have remained installed.... no root but su is definitely still installed! the only reason i am going to wait on rerooting is so i can learn more about it before i flash or anything
Yeah, it will show up in your apps but it doesn't work properly until you reinstall. I thought I had remained rooted but when I went to use Titanium Backup it couldn't get root access, then after I reinstalled su it worked fine.
But yeah, if you don't need it yet don't worry about it. The only good reason to do it is to use TiBU to save all your settings and if you have Amon Ra you can make a nandroid of your phone so that if something happens you have a backup image of everything and can restore it very easily via Amon Ra. You can still stay on stock ROM etc... the only thing you would need to flash is the Amon Ra recovery.
ya i see what you mean... I also want to get rid of this unbelievable amount of bloat... geez their are a ton of useless verizon apps never mind the stupid games
Ok so after getting 4.5.141 to load via motos update I attempted to root the phone. Which by all accounts looked like it worked however....
My phone does not appear to still be BL unlocked, and there are no apps in the list under superuser. I downloaded CWM and tried flashing then going into recovery and that fails even through prompted for SU by the apps it says it work etc.
Now I cannot even get into recovery via any method. Via CWM it errors with a message cannot boot 2 error then loads rsd mode. Via power on/vol dwn it just gives the android dude with ! in the triangle.
Ok so how do I fix this? I need to be able to root, unlock the BL (if even possible) and fix my recovery partition. (any command used from fastboot fails I suspect its still a permissions root issue)
Any help is appreciated.
NVM I fixed it.
I re-ran the unlock process what was funny is when I flashed the sbf to unlock the BL the screen immediately showed the "unlocked" in the upper left hand corner. When I went to do the fastboot oem unlock part it said already unlocked. (I tried this earlier and it kept failing I think cause I forgot the sbf.
I then went through the steps to re-root it, then re-flashed the newer CWM and now I am able to get into recovery etc.
So I am a first time rooter, so I'll try my best to use the proper terms and whatnot.
Anyways, I have an unlocked HTC One X+ that I am trying to root. I was using the AIO kit by Hasoon2000. I had my bootloader successfully unlocked, and so I proceeded to continue with rooting. I thought I pushed the SuperSU.zip to the device, because the cmd line said it was successful. So I booted into recovery mode, made a backup, and then when to flash the SuperSU.zip file. However, I could not find it in the file explorer in recovery mode.. so I went to push the file to the phone again, but now it says device not found. The only thing I can think that's happened is my USB debugging got turned off... which is bad. So is SuperSU.zip in my phone somewhere, or am I stuck with a phone that can only go into recovery mode?
Thanks for any help!
I have now similar problem too...
actually I had rooted successfully, but after many failed CM11 installation attempts, I decided to relock the bootloader, in order to update the Firmware. But it didn't work too and I came the way back again, in which I unlocked the bootloader with Unlock Token etc. again. Now the bootloader is unlocked but apparently not rooted!?! I can't push superuser via adb because **Device is not found** and I can only go to TWRP Recovery and bootloader...
COULD SOMEONE HELP??!
PS: when i press the reboot in TWRP, it says that "the phone seems not to be rooted, do you want to install the SuperUser? and when I accept it... it reboots only and nothing does change!
well... im not sure what I did differently but it finally recignized the device!! And now I managed to get everything installed... weird!
Hi, I followed thew rooting instructions and got to the part where you flash the recovery after flashing I've tried to boot into recovery and all I get is your device software cannot be checked screen then it reboots or loads the factory reset screen and resets back to factory settings.
I have checked the phone is unlocked and it says it is
Jonnibravo said:
Hi, I followed thew rooting instructions and got to the part where you flash the recovery
after flashing I've tried to boot into recovery and all I get is your device software cannot be checked screen
then it reboots or loads the factory reset screen and resets back to factory settings.
I have checked the phone is unlocked and it says it is
Click to expand...
Click to collapse
Ignore the scary bootloader unlock warning. That's not preventing you from booting to TWRP.
What's preventing you from booting to TWRP is you didn't fully install TWRP and activate it. You still have stock recovery because you flashed TWRP but didn't finish the TWRP installation/activation process. So TWRP didn't stick and you have stock recovery still.
Read the instructions again. Post #193 of the WTF bootloader unlock and root thread.
WHICH instructions did you follow? Because with my instructions I cleary tell how to immediately boot to TWRP with fastboot flash commands after installing it -- and to NOT do any anything else (even rebooting the phone) before finishing TWRP installation and activation. You either didn't use my instructions or didn't carefully follow them?
People should really PRINT out the instructions before starting the process so they can carefully read it. It's very easy to skip over an important part or skip over a part you don't think is important?
It's all there for a reason.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Ignore the scary bootloader unlock warning. That's not preventing you from booting to TWRP.
What's preventing you from booting to TWRP is you didn't fully install TWRP and activate it. You still have stock recovery because you flashed TWRP but didn't finish the installation process. So TWRP didn't stick and you have stock recovery still.
Read the instructions again. Post #193 of the WTF bootloader unlock and root thread.
WHICH instructions did you follow? Because with my instructions I cleary tell how to immediately boot to TWRP with fastboot flash commands after installing it -- and to NOT do any anything else before finishing TWRP installation and activation. You either didn't use my instructions or didn't carefully follow them?
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
I have installed using fastboot command and used the boot twrp.img command, the corruption message shows then the screen goes blank and it goes from the lg v30 logo back to corruption logo then reboots. What stage have I missed.
Jonnibravo said:
I have installed using fastboot command and used the boot twrp.img command, the corruption message shows then the screen goes blank and it goes from the lg v30 logo back to corruption logo then reboots. What stage have I missed.
Click to expand...
Click to collapse
From my instructions:
TLDR:
flash twrp: fastboot flash TWRP.img (TWRP-3.2.1-joan-v0.1.img re-named as just "TWRP.img")
boot twrp: fastboot boot TWRP.img (TWRP-3.2.1-joan-v0.1.img re-named as just "TWRP.img")
swipe to allow modifications (do NOT leave read-only, TWRP NEEDS to be able to make changes to your system.)
select WIPE, then FORMAT DATA, then write yes
wipe cache, dalvik, data
flash magisk
flash encryption disabler
flash root disabler
reboot
STRONG SUGGESTION: After successfully doing all this, when you finally boot back to LG Oreo, install an app like this to easily facilliate rebooting to TWRP recovery in the future: Recovery Reboot
Even if you didn't actually install TWRP, you would still be able to boot to TWRP using the boot command ( fastboot boot TWRP.img) as long as you were connected to your computer and had TWRP.img in your ADB folder.
I've done it to make TWRP backups of "stock" systems where TWRP is not installed on purpose.
People who never finished activating TWRP have been able to do it, as they really don't have TWRP installed --- they are booting to "temporary" TWRP from their computer using fastboot boot TWRP.img. If they try to boot to TWRP from their phone, using an app they get the Android on his back which is a clue they REALLY don't have TWRP installed... but they are still able to fastboot boot TWRP.img when connected from their computer.
If you can't do that, something is very wrong. It's just that's the easiest way to get into TWRP after flashing it, so you can then "activate" it, make the installation stick.
Thanks for that its installed and I have installed a rom however I still cant boot into recovery, I have to reflash to get back in, and is there any way to get rid of the corruption message
Jonnibravo said:
is there any way to get rid of the corruption message
Click to expand...
Click to collapse
Not really. The "corruption message" is just LG's scary bootloader unlock warning to discourage you from rooting your phone. It's really a sign of freedom. Ignore it.
It's going to show up when you boot to TWRP or even when to boot to regular OS. It's just an image, a picture for LG to try to scare you. It stays up a few seconds then goes away.
Some Verizon users have found if they flash part of the Verizon firmware back it replaces the bootloader unlock warning with a few seconds of black:
datechnerd said:
I did have to wipe to reflash US998. But while I was fighting that I discovered what partition holds the bootloader warning!!!! It's rawresources. I moved the VS996 rawresources over to my US998 /dev/block/bootdevice/by-name/ and no longer have the warning. Granted it's a short black screen pause,
Click to expand...
Click to collapse
While that is very interesting, for now I would just ignore the warning. It's not preventing you from booting to TWRP. What's preventing you from booting to TWRP is somehow you haven't finished the entire TWRP installation/activation process.
Jonnibravo said:
Thanks for that its installed and I have installed a rom however I still cant boot into recovery, I have to reflash to get back in
Click to expand...
Click to collapse
If you installed the Recovery Reboot app I recommended (requires root access) you can boot to TWRP from there on your phone, IF you REALLY have TWRP installed. If you are having to boot to "temp" TWRP via ADB from your computer every time, then TWRP is not really installed on your phone. If you use that Recovery Reboot app, and it boots to Android on his back, then you still have stock recovery installed.
You need to reflash (reinstall) TWRP, then boot to TWRP immediately and go through the steps I posted to make it writable -- so it will stick as your custom recovery.
RTFM Myself
ChazzMatt said:
Ignore the scary bootloader unlock warning. That's not preventing you from booting to TWRP.
What's preventing you from booting to TWRP is you didn't fully install TWRP and activate it. You still have stock recovery because you flashed TWRP but didn't finish the TWRP installation/activation process. So TWRP didn't stick and you have stock recovery still.
Read the instructions again. Post #193 of the WTF bootloader unlock and root thread.
WHICH instructions did you follow? Because with my instructions I cleary tell how to immediately boot to TWRP with fastboot flash commands after installing it -- and to NOT do any anything else (even rebooting the phone) before finishing TWRP installation and activation. You either didn't use my instructions or didn't carefully follow them?
People should really PRINT out the instructions before starting the process so they can carefully read it. It's very easy to skip over an important part or skip over a part you don't think is important?
It's all there for a reason.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
I just had the same issue, had it all ready went to Pie, lost Magisk root, played with it until lost it all.. so had to start again.. missed the important part after intalling TWRP.. thanks again :good::good::good:
I found (on this website) an LGUP tool (version) that is for the MS330. So it works (albeit not so consistently). The LGUP tool was able to flash a .kdz file after several trials. Apparently when LGUP connects, it puts the MS330 in bootloader mode, waits 15 seconds for the device to respond and then begins flashing.
Now, here's the problem. I have a .tot file I'd like to flash. When trying to flash a .tot file, 15 seconds is not enough time for the device to respond, and I get an error for what appears to be an asynch error. That is to say, the MS330 took a second or two more that the 15 seconds to respond saying, yes I'm in bootloader mode.
Is there any way to give it a bit more time? Surely the members who use LGUP tool would have encountered this behavior, and would have found a solution.
Tried changing ports, cables, computers. No improvement
Words of wisdom, anyone?
BigZ1 said:
I found (on this website) an LGUP tool (version) that is for the MS330. So it works (albeit not so consistently). The LGUP tool was able to flash a .kdz file after several trials. Apparently when LGUP connects, it puts the MS330 in bootloader mode, waits 15 seconds for the device to respond and then begins flashing.
Now, here's the problem. I have a .tot file I'd like to flash. When trying to flash a .tot file, 15 seconds is not enough time for the device to respond, and I get an error for what appears to be an asynch error. That is to say, the MS330 took a second or two more that the 15 seconds to respond saying, yes I'm in bootloader mode.
Is there any way to give it a bit more time? Surely the members who use LGUP tool would have encountered this behavior, and would have found a solution.
Tried changing ports, cables, computers. No improvement
Words of wisdom, anyone?
Click to expand...
Click to collapse
What is going on? Wierd error/problem here.
OK! All of this above is OBE. I managed to get the bootloader unlocked, so I am now free to load custom roms. Well, sort of. I rooted the system, and tried to install TWRP from the playstore. When I got to the part about flashing recovery with the TWRP image, it fails. Just says Flash failed.
So, I went back to using adb and fastboot. I used "flashboot flash recovery TWRPfilename". That worked. Then "adb reboot recovery" took me to TWRP. So far, so good. When I shut down the phone and use the power/volume keys to boot into recovery, I get the stock rom recovery, not TWRP. If I connect the usb cable and use "fastboot reboot recovery" I get TWRP
What is going on here? Anybody who has a clue, please share your thought of the problem and/or possible fixes.
Thanks!
BigZ1 said:
What is going on? Wierd error/problem here.
OK! All of this above is OBE. I managed to get the bootloader unlocked, so I am now free to load custom roms. Well, sort of. I rooted the system, and tried to install TWRP from the playstore. When I got to the part about flashing recovery with the TWRP image, it fails. Just says Flash failed.
So, I went back to using adb and fastboot. I used "flashboot flash recovery TWRPfilename". That worked. Then "adb reboot recovery" took me to TWRP. So far, so good. When I shut down the phone and use the power/volume keys to boot into recovery, I get the stock rom recovery, not TWRP. If I connect the usb cable and use "fastboot reboot recovery" I get TWRP
What is going on here? Anybody who has a clue, please share your thought of the problem and/or possible fixes.
Thanks!
Click to expand...
Click to collapse
One more tidbit of info. I tried flashing TWRP (installed from the playstore) several times. At first all I got was Flash Failed. Now (for no apparent reason) it was able to flash the TWRP file. So I thought I'd test it out. No change. Still can't boot into recovery by using vol-and pwr. Still takes me to stock rom recovery. But (same as before) adb reboot recovery takes me right to TWRP, and it's working fine.
I am not doing any data wipes, formatting, changing permissions, etc. . Anybody have any experience with this problem, or any thoughts on how to fix it????
BTW, this is for an LG K7 MS330m1.