Related
This may be a weird question, but instead of trying to get into fastboot, I've got problems getting out of fastboot. Here's the situation:
I installed Villianrom 3.1 without any trouble, and downloaded the 3.2 update to my SD. I went into recovery and, without wiping first, tried to install the update. It reported an error on line 5, and cancelled. Since I didn't feel like wiping and having to setup the phone again, I decided to stick with 3.1 and rebooted the phone. I happened to be connected to my pc at the time.
All I got was the black boot screen with the silver HERO logo, and "FASTBOOT USB" in red in the top left corner.
"Fastboot devices" returns the device, so fastboot is active.
"Fastboot reboot" returns "Rebooting.." but has no effect on the phone.
"Fastboot reboot-bootloader" gives me "rebooting into bootloader.. FAILED <Command write failed <unknown error>>"
Since I have a recent nandroid backup, all I want to do is get back to the recovery screen, but I don't see how I can do that from here. I'm reluctant to pull the battery, since that is how I bricked my HTC Magic.
Any help is greatly appreciated.
EDIT: never mind, after about 3 hours of waiting the device shut itself down. I booted into recovery and it's restoring right now.
never had a problem from pulling the battery in fastboot, but "reset device" just reboots iirc.
So I have had this US beta streak since around January, the one that says 'Dell Confidential' at boot up, but it's never really worked correctly. I purchased it from a person that I know that got it through some sort of beta testing; the details weren't provided and I didn't press him for them. Anyways, I am currently trying to get the clockwork recovery flashed and able to be booted into, although the streak is giving me every possible problem I can imagine. I'll try to provide as much background info as I possibly can.
Firmware: 1.5
Baseband Version AUS_090716_01_BOSS_EVT2_3135
Kernel Version 2.6.27
Build Number QTC_3135
OEM Version: AustinBuild_090724_03_boss_evt2_3135_FixTouchSuspend
Under About Phone > Status
IMEI 011954000020995
IMEI SV 00
Service Tag FF8R6K1 (which dell.com cannot find)
The Problems:
When I try to get into bootloader to get into fastboot, by holding the camera button down while hitting the power button, rather than going into the screen that is shown in all of the different tutorial threads, I instead go into some sort of a diagnostic menu that doesn't have an option for fastboot, as much as I have seen. There is a picture attached below.
I (think) that I can get the phone recognized by adb, although I am not totally positive. When in cmd in windows, and I type adb devices, instead of getting the proper serial number of my devices, it shows instead 0123456789ABCDE (I may not have that exact, but it does start at 0 and ends in hex at E or F, I can't remember right now and don't have it connected at the moment.)
There was one time where I was able to flash recovery.clockwork.img to where it said that it successfully flashed the img, but when I go to try and boot into recovery by holding both volume up and down at the same time, and then hitting power, the phone just hangs at a blank, black screen. It will stay there for 30 minutes and not do a thing, I can't see it via adb or fastboot.
So I then gave recovery.alt.img a shot, was able to successfully flash that, or so it told me that it was successful, but still the same problem: just a black screen.
The reason that I think that it actually was working was that after flashing the recovery image both times, I sent the command adb reboot recovery, and the phone reboots, but not into recovery, just into android. adb reboot-bootloader doesn't work at all and returns an error or nothing, I can't remember.
I then focused my attention on trying to get fastboot to work, assuming that adb was not working at all. This is where fastboot gets strange. The only way for me to get the command 'fastboot devices' to show anything at all is by holding the volume down button prior and then hitting the power button to start it. This puts the phone into essentially a 'soft brick', which my friend calls 'safe mode', where it gets totally stuck at the 'Dell Confidential' screen and will not progress past it no matter what.
So, once I am in 'safe mode', I am able to then issue a 'fastboot devices' command, which ... partially works? I hope that my totally unsure tone of voice was able to be conveyed through that message, because the info returned once that command is sent is totally confusing to me. Unlike before, where I feel as though the Streak is just lying to me by saying 0123...DEF for the device ID, for fastboot devices it just gives me a question mark .. yes, simply a ?
The weird thing is that it will follow commands. I was able to flash recovery.clockwork.img to the streak, it gave me a read out that said successful, and I got very excited. And then I pulled the battery, put it back in, held both the volume buttons, and .... the same result, the black screen. So, not allowing myself to be deterred, I got right back into fastboot, or at least my quasi working version of fastboot which may not be working at all, and flashed recovery.alt.img, which turned around and told me that it was successful as well. This time, not allowing myself to get excited, I pulled the battery and, with both volume buttons held down, hit power to try to get into recovery.
Again, I was let down and found only a blank screen. At this point, I have no idea what else to try. With the bootloader not being where it's suppose to be, not really being able to get into fastboot or adb (I think), I turn to xda to try and find some answers. Does anyone have a suggestion as to what I am doing wrong or might be missing. I am hoping that it is something that is really obvious that I feel very stupid, like I'm hitting the wrong set of volume buttons, but ... I don't think it's that easy.
Again, I feel as though the phone was getting the commands from fastboot because I sent fastboot reboot recovery, and the phone rebooted, just not into recovery but android. Same thing for bootloader, it just didn't work at all
Also, as for android 1.5 itself, almost nothing works. This appears to be running a very early edition of android where most apps just end up with: Sorry! No applicatons can perform this action, so the One touch root is kind of out of the question.
I was able to do the dialer unlock method to get EMList, but the similarities end there. I don't have the Unknown sources option or anything else after leaving dialer.
Any and all suggestions are appreciated and will be accepted and followed (within reason). I'm just at the point where I'm hoping that it's not totally broken and that with determination and hard work and some critical thinking I (we) will be able to get it working again. Hopefully it isn't a paperweight.
Thanks,
Thursday
I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
Yeah, it was because the stock recovery doesn't exist as a menu, when you're running stock and enter the adb command "adb reboot recovery" it will reboot to the "factory reset mode" and the actual file of this mode is stored on partition named "recovery". Choosing the factory reset option boots the custom recovery because it replaces the said " factory reset mode" and that's the trick.
You can access recovery from the powered off state by holding volume down and power on until you see the lg sign. Without letting go of volume down, depress on the power button before clicking it back in and holding both buttons in until you see twrp pop up.
If you reboot to recovery now, it''ll probally say secure booting error. Simply go to the Developer options and enable OEM Unlock and that'll make you boot to it
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
kruc Ire said:
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
Click to expand...
Click to collapse
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
kruc Ire said:
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
Click to expand...
Click to collapse
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
duffycop said:
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
Click to expand...
Click to collapse
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
kruc Ire said:
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
Click to expand...
Click to collapse
I dunno, I have the H340AR, with this phones happens the same that with the Samsung Galaxy Ace 3, there are, 3G versions, 4G versions, regional versions, etc.. GA3 have 7275R, 7275B, 7272L, 7272T, I dunno, maybe if we could get a device tree for a H340 and an H320 we could make some TWRP and CM compiling, but I just can't figure it out how to make a device tree or even where to begin..
I successfully rooted my H340AR with Kingroot, it works like a charm. I haven't tried fastboot and I tried to install TWRP in this link https://dl.twrp.me/c50/ but I get that F error "Secure booting error". I guess I have my bootloader locked, so I'm trying to figure out how to unlock my bootloader.
I'm trying to contact with some developers and see if anyone can help me build a device tree.
]
Hi, I have that same phone H340AR LTE. I rooted it with Kingroot and also tried to use TWRP to gen into recovery and got that Security error. I only pulled out the baterry and turn it on again so it booted normally. I made a factory reset because I read that it could be a problem of OTA firmware update. Then I installed TWRP and BusyBox again and tried to get into recovery from TWRP option. When I did that, it showed up the Android lying in his back with a red triangle. I pulled a out the battery again and yes, it seems very dumb and simple but it worked and could reboot the phone.
However, I can't get into recovery from TWRP yet. I read that the problem with us not being able to unlock the bootloader(we don't have the OEM option) is because Leon has Lollipop 5.0.1 and OEM is for 5.1.1
pedrovay2003 said:
I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
Click to expand...
Click to collapse
when i pressed factory reset all it did was to a factory reset even though i flashed twrp.img successfully... help?
lg leon h345 lollipop 5.1.1
This device has a locked bootloader. If you flash a custom recovery on it, it will not boot into recovery, but will report a security issue. You will lose all recovery functionality, including factory reset, adb, fastboot. If your phone fails to boot, you have a brick.
I got the new T-mobile LG V20 I went thru the the whole proccess step by step of how to root and install twrp on my device the last step of having to encrypt it failed now its stuck in a bootloop. screen pops up saying encryption is unsuccessful,then resets to twrp and flashes back to the previous screen. over and over. Please help
jessiemougeot said:
I got the new T-mobile LG V20 I went thru the the whole proccess step by step of how to root and install twrp on my device the last step of having to encrypt it failed now its stuck in a bootloop. screen pops up saying encryption is unsuccessful,then resets to twrp and flashes back to the previous screen. over and over. Please help
Click to expand...
Click to collapse
same problem here and cant find solution ...
I had the same issue. when you press to reset button when the phone boots it should reboot and for a short time go to recovery and try to write some commands, right? if it does like mine did then what i did to fix it was boot up the phone and wait for the page saying encryption unsuccesful to popup and on the computer have the adb reboot recovery ready to go so when you press the reset button and the recovery menu pops up press enter on the computer before it goes away and it should send you to the regular recovery menu. from there you should go back to wipe and press the format data button where you have to type yes to erase everything. let me know how it went.
you will have to reflash the supersu but it should now be working like it should
Flash the latest su and your fine.
ErickF said:
I had the same issue. when you press to reset button when the phone boots it should reboot and for a short time go to recovery and try to write some commands, right? if it does like mine did then what i did to fix it was boot up the phone and wait for the page saying encryption unsuccesful to popup and on the computer have the adb reboot recovery ready to go so when you press the reset button and the recovery menu pops up press enter on the computer before it goes away and it should send you to the regular recovery menu. from there you should go back to wipe and press the format data button where you have to type yes to erase everything. let me know how it went.
you will have to reflash the supersu but it should now be working like it should
Click to expand...
Click to collapse
did that but my adb says no devices or emulators?
jo4mvp24 said:
did that but my adb says no devices or emulators?
Click to expand...
Click to collapse
Make sure your on charging mode and you have adb debug enabled
send the adb reboot recovery command as soon as the twrp connects to the computer. as soon as you hear it connect to the computer it should work if your drivers are working.
charlieb620 said:
Make sure your on charging mode and you have adb debug enabled
Click to expand...
Click to collapse
how do i do that when phone stuck on encryption unsuccessful screen?
exactly my issue
ErickF said:
I had the same issue. when you press to reset button when the phone boots it should reboot and for a short time go to recovery and try to write some commands, right? if it does like mine did then what i did to fix it was boot up the phone and wait for the page saying encryption unsuccesful to popup and on the computer have the adb reboot recovery ready to go so when you press the reset button and the recovery menu pops up press enter on the computer before it goes away and it should send you to the regular recovery menu. from there you should go back to wipe and press the format data button where you have to type yes to erase everything. let me know how it went.
you will have to reflash the supersu but it should now be working like it should
Click to expand...
Click to collapse
Ya that is exactly what happend give me a few minutes ill try it out and let you know....THANKS...THANKS....THANKS...It worked, i got it on my first try. Your right ...you have to be quick. thank u so much you saved me along night of downloads! :victory:
This method WORKS!!!! Same situation happened to me. THANK YOU 500x!! you saved my brick!
ErickF said:
I had the same issue. when you press to reset button when the phone boots it should reboot and for a short time go to recovery and try to write some commands, right? if it does like mine did then what i did to fix it was boot up the phone and wait for the page saying encryption unsuccesful to popup and on the computer have the adb reboot recovery ready to go so when you press the reset button and the recovery menu pops up press enter on the computer before it goes away and it should send you to the regular recovery menu. from there you should go back to wipe and press the format data button where you have to type yes to erase everything. let me know how it went.
you will have to reflash the supersu but it should now be working like it should
Click to expand...
Click to collapse
This works 100% thank you so much. Just have patience as it has to be at the right time....WORKS WORKS WORKS!!!!!
Help
Can someone explain the commands and how to do this please thanks in advance
I did the data reset and im still in the bootloop. Worst thing is now i cant seem to get into recovery
epr2175 said:
I did the data reset and im still in the bootloop. Worst thing is now i cant seem to get into recovery
Click to expand...
Click to collapse
What screen are you stuck in? Do you have adb up and running?
Same as before Encryption unsuccessful. I was able to do the trick, got into two and wiped data. Then rebooted to system and it went right back to that screen. I've tried 100 times or so to get back into twrp with no luck. I hear the computer recognize the device when it goes into twrp for 2 seconds after you click reset. Not sure if that means add is up and running or not.
jessiemougeot said:
Ya that is exactly what happend give me a few minutes ill try it out and let you know....THANKS...THANKS....THANKS...It worked, i got it on my first try. Your right ...you have to be quick. thank u so much you saved me along night of downloads! :victory:
Click to expand...
Click to collapse
Well it booted then got stuck on the lg boot screen again. Adb does not recognize my device, can only boot into Fastboot. Fastboot does see my device, tried lgup, lg bridge, and lg update none see my device, tried relocking bootloader after oem lock bootloader rebooted said my device was corrupted and shut itself off went back into Fastboot unlocked bootloader again and back to the same lg screen help?
This did not work for me, my phone reboots back into TWRP whenever I install a system image it still gives me the encryption message.
---------- Post added at 02:06 PM ---------- Previous post was at 01:11 PM ----------
crazyc78 said:
This did not work for me, my phone reboots back into TWRP whenever I install a system image it still gives me the encryption message.
Click to expand...
Click to collapse
Now I don't even have the encryption screen it just reboots back to TWRP very frustrating!!
fixed!
jessiemougeot said:
I got the new T-mobile LG V20 I went thru the the whole process step by step of how to root and install twrp on my device the last step of having to encrypt it failed now its stuck in a bootloop. screen pops up saying encryption is unsuccessful,then resets to twrp and flashes back to the previous screen. over and over. Please help
Click to expand...
Click to collapse
Had the same problem and could not for the life of me do the adb thing. Someone here stated something that I thought I'd try: Press volume down while plugging in the phone to get into fastboot. In a command window issue "fastboot oem lock" (this will relock the boot) > Let the phone reset and you'll see the "Phone corrupt message" > Plug the phone in again to do a fastboot and issue "fastboot oem unlock" > Take the battery out let the phone boot and BAM-E WHAM success!
btw. I followed the steps here to do the whole root thing with Android . how (google "how to root the v20")
I think the "data" wipe did this and according to this site it's not a necessary step so skip it.
This option works!
SyHusky said:
Had the same problem and could not for the life of me do the adb thing. Someone here stated something that I thought I'd try: Press volume down while plugging in the phone to get into fastboot. In a command window issue "fastboot oem lock" (this will relock the boot) > Let the phone reset and you'll see the "Phone corrupt message" > Plug the phone in again to do a fastboot and issue "fastboot oem unlock" > Take the battery out let the phone boot and BAM-E WHAM success!
btw. I followed the steps here to do the whole root thing with Android . how (google "how to root the v20")
I think the "data" wipe did this and according to this site it's not a necessary step so skip it.
Click to expand...
Click to collapse
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I go my T-mobile LG V20 H918 on 11/23/16 and sure enough, I followed the same thread as listed above where it added the step of "data wipe" crap. I was caught in a bootloop, where phone kept bootlooping back to the "reset to factory." The other method of entering the adb command at the right time was more frustrating than anything. (I never got it to work). I spent all day yesterday trying to get this phone working. I re-read (x30) the above thread and on the first attempt it worked. I did not get the "Phone Corrupt Message," but I went ahead and entered the "fastboot oem unlock" and the F#$king phone finally reboot to the setup initial screen. It wiped everything, but having a phone working rather than a nice $800 paperweight, I wanted to kiss SkyHusky for sharing this simple method. YOU ARE AWESOME!!!!
By the way, since I am a glutton for punishment, I followed the steps to root again. After flashing the SuperUser, I rebooted to System. I was at the initial setup screen. My phone is rooted, has TWRP, and SuperUser! As soon as I got the phone working, I went back to TWRP and made a BACKUP!!!!
It is amazing that every time I f-up a phone, I can always come to XDA and get a solution. THANKS GUYS!
jay_h_jacob said:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I go my T-mobile LG V20 H918 on 11/23/16 and sure enough, I followed the same thread as listed above where it added the step of "data wipe" crap. I was caught in a bootloop, where phone kept bootlooping back to the "reset to factory." The other method of entering the adb command at the right time was more frustrating than anything. (I never got it to work). I spent all day yesterday trying to get this phone working. I re-read (x30) the above thread and on the first attempt it worked. I did not get the "Phone Corrupt Message," but I went ahead and entered the "fastboot oem unlock" and the F#$king phone finally reboot to the setup initial screen. It wiped everything, but having a phone working rather than a nice $800 paperweight, I wanted to kiss SkyHusky for sharing this simple method. YOU ARE AWESOME!!!!
By the way, since I am a glutton for punishment, I followed the steps to root again. After flashing the SuperUser, I rebooted to System. I was at the initial setup screen. My phone is rooted, has TWRP, and SuperUser! As soon as I got the phone working, I went back to TWRP and made a BACKUP!!!!
It is amazing that every time I f-up a phone, I can always come to XDA and get a solution. THANKS GUYS!
Click to expand...
Click to collapse
No problem!! Also I forgot to add I only rooted afterward and didn't try to install a ROM or anything. I would think you risk danger with some ROMs without that decryption thing turned off. So maybe in the short future there will be better fixes.
Hi, I don't have enough posts to ask this in the actual DirtySanta thread.
I meticulously followed the steps in the DirtySanta thread making sure I had all the correct software, all the pre-requisites, all files in my ADB folder (except SuperSU zip, which is on the SD card on the phone). Suffice it to say that I did all the steps exactly as written in the guide. I was prompted when to run the next batch files each time, etc. Entered the proper commands in the terminal utility, and so on. Everything as written.
After clicking on step3.bat, the phone immediately rebooted to a Fastboot screen. In the meantime, the batch files disappeared off my desktop.
So, for the past 15 minutes or so the phone has been sitting on Fastboot and vibrating away.
Here's what I see in the small Fastboot screen:
Fastboot Mode (in red)
stuff like Product_name, Variant, HW_Version, etc. up until it says LOCK_STATE.
Ok, after all of that basic stuff, it says:
[1090]
[1140] Fastboot mode started
[1670] fastboot: processing commands
[17600] usb_read() transaction failed; txn_status= -1
[17650] usb_read: DONE: ERROR len=64
[1700] fastboot: oops!
[17750] fastboot: processing commands
And that's where it sits, doing seemingly nothing and vibrating away.
Can anyone assist?
Try a different usb port. then rerun step 3.
me2151 said:
Try a different usb port. then rerun step 3.
Click to expand...
Click to collapse
Will do...was just thinking of doing that since it said "usb read error". Will report back.
Heyitsrick said:
Will do...was just thinking of doing that since it said "usb read error". Will report back.
Click to expand...
Click to collapse
First off, a big thanks for helping me.
Update: OK, changing the USB port worked I re-ran Step3.bat. I have made it through getting to TWRP, and have done these steps:
Verizon(VS995) and ATT(H910):
4.1) Flash SuperSU.zip
4.2) Go back to Main-menu > Wipe > [Format Data] > Type ?Yes?
4.3) Go back to Wipe > Advanced > Check Dalvik, Data and Cache > Slide to wipe
4.4) Go back to Main-menu > Reboot > System
So, with that all complete, it's rebooted to a Verizon screen (horizontal progress dots) and a low buzzing.
I did try what you mentioned in the guide to get over the wait time by pulling the battery, reinserting with vol down key pressed and re-attaching the USB to flash boot2.img via fastboot, but it didn't get back to fastboot after the battery/voldown/usb. It went back to the same Verizon screen after the obligatory "Corrupt" screen came on.
Can I assume that I can wait this out for 20 minutes, or did I miss something in how to interrupt this waiting period for first setup? I do want to (and know I have to) flash boot2.img.
EDIT: wasn't holding vol key down long enough to get into fastboot. Doh. Just flashed boot2.img and rebooted.
Looks like I made it! It's at the "Prepare your Phone Screen". Fingers crossed.
Heyitsrick said:
Looks like I made it! It's at the "Prepare your Phone Screen". Fingers crossed.
Click to expand...
Click to collapse
Are you still stuck?
I ran into this EXACT same issue on my brand new Verizon v20 on step 3 (both 13a and 12a firmware gave me this issue) and I had to figure out my own solution, even tho I read that 'dirty santa root' thread a thousand times front to back.... (no disrepsect to the OP/Devs of that thread btw!)
Anyways, below, is the link to my solution on my brand new Verizon v20, in case you're still stuck. I've actually reflashed (via LGUP) back to stock a couple times, then re-root/unlock to test out 13a and 12a firmwares to benchmark various battery life/performance markers for a tech site I write for. Ultimately, I have to go through the exact same steps everytime for my Verizon v20.
I know I wasn't too specific in my post below... but if you have any questions, don't hesitate to ask
https://forum.xda-developers.com/showpost.php?p=71371141&postcount=24
NegativeX said:
Are you still stuck?
I ran into this EXACT same issue on my brand new Verizon v20 on step 3 (both 13a and 12a firmware gave me this issue) and I had to figure out my own solution, even tho I read that 'dirty santa root' thread a thousand times front to back.... (no disrepsect to the OP/Devs of that thread btw!)
Anyways, below, is the link to my solution on my brand new Verizon v20, in case you're still stuck. I've actually reflashed (via LGUP) back to stock a couple times, then re-root/unlock to test out 13a and 12a firmwares to benchmark various battery life/performance markers for a tech site I write for. Ultimately, I have to go through the exact same steps everytime for my Verizon v20.
I know I wasn't too specific in my post below... but if you have any questions, don't hesitate to ask
https://forum.xda-developers.com/showpost.php?p=71371141&postcount=24
Click to expand...
Click to collapse
I read your "fix" post to see exactly where you got stuck, as I got stuck first due to the USB port not being able to work correctly and had to switch USB ports on my pc before I could re-run step3.bat.
I see now that you're talking about the long Verizon logo screen with progress dots issue after rebooting post-running step3.bat that I ran into, as well.
OK, what worked for me was much easier in the end than what you did. After step3.bat and the reboot, it would just sit there on the Verizon logo with the progress dots, as you know. There is a notation on the first page of the DirtySanta thread that in order to get around this, unplug the USB cable and remove the battery.
This is the actual note from the DirtySanta thread for Verizon users with the long Logo screen issue:
*****VERIZON USERS******
It has come to my attention that some users have encountered abnormally long first boot time(over 20 minutes before first time setup)
To resolve this issue:
Boot into bootloader by pulling the battery and reinserting it and holding VOL- and phugging in the phone. then typing:
Code:
fastboot flash boot boot2.img
fastboot reboot
**************
Click to expand...
Click to collapse
Once I removed the battery and usb cable, the phone was completely off, of course. Then, I just needed to get it back into "fastboot" on the phone, itself, in order to flash boot2.img via ADB on the PC. When the phone was on the never-ending Logo screen with progress dots, I found that ADB could see the phone ok via the adb devices command, but if I tried to flash anything at that point, it would just say something like "pending", as if it were waiting for the device to be free to flash. So, that wasn't going to work, obviously. I needed the phone to be in the flashboot screen, not the logo screen. I did a ctrl-c to cancel out of the adb flash command, and then set out to pull the battery/usb cable and then reconnect the battery, and while holding the Vol Down button reinserting the USB cable.
The first time I tried this, it booted up fine, but it went right back to the Logo screen. Doh! I figured perhaps I wasn't waiting long enough with the Volume Down button so I tried it again. What happened the first time when it rebooted to the Logo screen is I released the Volume Down button the moment the phone started to turn on (you feel the vibration). That's when it booted back to the Logo. This second time, I removed the battery again while it was on that never-ending Logo screen to power it off and disconnected the USB cable again. I put the battery back in, then with the Volume Down button pressed down, I reconnected the USB cable. The difference this time is that I did not release the Volume Down button this time UNTIL I saw it was in the Fastboot screen and not the Verizon Logo.
So, at this point the phone was on the Fastboot screen and I saw it was it was ready to go, so I initiated the ADB command to flash boot2.img. It went through its paces and once it got back to the ADB command prompt, I did an ADB Fastboot Reboot command. It rebooted, first with the obligatory corrupt warning, then the Verizon Logo and progress dots, but then after a short while I got the "Hello" screen in red and I knew it was actually going to finish. Whew! Relief! At that point I was eventually at the phone's setup screen for a new user, and I finished setting up the phone, reinstalling apps, etc.
One caveat in this: I don't know why, but even though I had gone through all the steps in "4" section of the instructions, when I checked Root, I wasn't rooted! Huh?
In other words, I had already gone through this part:
Verizon(VS995) and ATT(H910):
4.1) Flash SuperSU.zip
4.2) Go back to Main-menu > Wipe > [Format Data] > Type ?Yes?
4.3) Go back to Wipe > Advanced > Check Dalvik, Data and Cache > Slide to wipe
4.4) Go back to Main-menu > Reboot > System
Click to expand...
Click to collapse
After setting up the phone and reinstalling my apps, I opened up the SuperSU app, and it said there was no executable installed. In other words, it didn't recognize that I had flashed it in step 4.1. Perhaps flashing boot2.img overwrote that? Not sure, but at this point, I set about to figure out how to boot into TWRP Recovery on the phone (not fastboot) to flash it from there (again).
It took me a while to find the instructions on how to boot into TWRP, lol, and it's a little unnerving that before it boots to TWRPyou are warned that all your data is going to be overwritten before you can boot to it, but it did get me back into TWRP. Once in TWRP, I re-flashed Supersu-blahblah.zip and rebooted via the system reboot. (did not wipe any caches again, though).
After reboot, I checked root again, and this time after a bit SuperSu brought up the permissions screen for the Root app that I had to allow, and it brought back a successful Root message.
I then set about to do what I really wanted to do with root - bypass the Verizon entitlement check for hotspot usage, and got that working fine.
All in all, I have to say this was the diciest rooting I've ever had to go through. I guess that's because of Nougat and that there can't be (at least not yet) a "one-click" root. But man, was I worried when I was at the point where I first posted in this thread. I bought this phone as a "new-resale" (never used) phone from Swappa.com for $450, so if I bricked it, I was out of luck. But it seems to be ok now.
Heyitsrick said:
I read your "fix" post to see exactly where you got stuck, as I got stuck first due to the USB port not being able to work correctly and had to switch USB ports on my pc before I could re-run step3.bat.
I see now that you're talking about the long Verizon logo screen with progress dots issue after rebooting post-running step3.bat that I ran into, as well.
OK, what worked for me was much easier in the end than what you did. After step3.bat and the reboot, it would just sit there on the Verizon logo with the progress dots, as you know. There is a notation on the first page of the DirtySanta thread that in order to get around this, unplug the USB cable and remove the battery.
This is the actual note from the DirtySanta thread for Verizon users with the long Logo screen issue:
Once I removed the battery and usb cable, the phone was completely off, of course. Then, I just needed to get it back into "fastboot" on the phone, itself, in order to flash boot2.img via ADB on the PC. When the phone was on the never-ending Logo screen with progress dots, I found that ADB could see the phone ok via the adb devices command, but if I tried to flash anything at that point, it would just say something like "pending", as if it were waiting for the device to be free to flash. So, that wasn't going to work, obviously. I needed the phone to be in the flashboot screen, not the logo screen. I did a ctrl-c to cancel out of the adb flash command, and then set out to pull the battery/usb cable and then reconnect the battery, and while holding the Vol Down button reinserting the USB cable.
Click to expand...
Click to collapse
I saw that 'fix' and it never worked for me at the point in the rooting process I was in... sadly. You have to be able to even get to TWRP, do the SU install then format/wipe, then you can flash the boot2.img to speed up the booting process. In my case, I was never able to even get to TWRP. Trying to flash boot2.img before being able to get to TWRP, would soft brick my phone with the 'password' screen on bootup and I was never able to get around it, requiring me to LGUP back to stock and try again. Luckily I was able to still figure it out.
As you said, definitely the 'diceist' rooting process I've ever encountered... and I've been rooting phones since the original Motorola Droid 1/Milestone phone. Good times tho! Haha
NegativeX said:
I saw that 'fix' and it never worked for me at the point in the rooting process I was in... sadly. You have to be able to even get to TWRP, do the SU install then format/wipe, then you can flash the boot2.img to speed up the booting process. In my case, I was never able to even get to TWRP. Trying to flash boot2.img before being able to get to TWRP, would soft brick my phone with the 'password' screen on bootup and I was never able to get around it, requiring me to LGUP back to stock and try again. Luckily I was able to still figure it out.
As you said, definitely the 'diceist' rooting process I've ever encountered... and I've been rooting phones since the original Motorola Droid 1/Milestone phone. Good times tho! Haha
Click to expand...
Click to collapse
Late response - sorry.
There must be something we each did differently, as we both have the same phones, same carrier, same software revision (13a). I was able to get to TWRP via the button method on the phone. Didn't use ADB for that. I was presented with an ominous white screen about all files will be wiped/deleted, but when accepting that (and hoping for the best, lol), it just went to TWRP. So, again...something or some step(s) must be done differently to get to that point on your end from what I did.
I'm guessing you're through with doing the flashing on this thing, so this is all moot now.
Hey guys i actually was having the same issues as you were now however after the SU install the wipe etc i reboot to TWRP no matter what i do even when i restart through bootloader or take the battery off it keeps booting to the same place instead to the verizon wizard help please
kratos380 said:
Hey guys i actually was having the same issues as you were now however after the SU install the wipe etc i reboot to TWRP no matter what i do even when i restart through bootloader or take the battery off it keeps booting to the same place instead to the verizon wizard help please
Click to expand...
Click to collapse
Called a twrp loop. Easy fix. Been posted a lot. Look around for it
me2151 said:
Called a twrp loop. Easy fix. Been posted a lot. Look around for it
Click to expand...
Click to collapse
I have been looking for 2 days haha literally have like 30 tabs open shifting through i dont know what to do next, i backed up wiped my cache data etc installed SU which had no problems wiped again/ rebooted system and back to twrp, i read that you might need to flash a system.img but i dont know where to find one, would appreciate the help kind sir
kratos380 said:
I have been looking for 2 days haha literally have like 30 tabs open shifting through i dont know what to do next, i backed up wiped my cache data etc installed SU which had no problems wiped again/ rebooted system and back to twrp, i read that you might need to flash a system.img but i dont know where to find one, would appreciate the help kind sir
Click to expand...
Click to collapse
Look at team digitals ROM thread. Stockish one. Look at post 3. If you still can't find it I'll quote it directly later. I'm busy right now
me2151 said:
Look at team digitals ROM thread. Stockish one. Look at post 3. If you still can't find it I'll quote it directly later. I'm busy right now
Click to expand...
Click to collapse
Couldnt find it sorry im new to this forum please link it when you are free thanks again for the help much appreciated
kratos380 said:
Couldnt find it sorry im new to this forum please link it when you are free thanks again for the help much appreciated
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=70393155&postcount=3
Sorry for the constant posts but i followed the steps on that thread, deleted the misc/fota files and it stopped it going to twrp and booted to the lg logo with the black screen, i waited there for about 2-3 hours to no avail rebooted into bootloader tried the fastboot img 2 and the same thing happened it was just stuck at the lg logo now when it boots to the fastboot screen however adb doesnt recognize the device anymore but fastboot does. Is it time to kdz and start over ?