I did all the steps to root the phone, 1 and 2, but got stuck in a bootloop. The sprint log stuff would come up, the the 4g, then back to sprint etc. I flashed the PC36IMG.zip of the shipped version, but now I can't get the RUU to take the phone into a fully factory state. It starts, then gets stuck waiting for bootloader with a black screen and htc on it. I really just want to make it factory again and start over with the root process. Any ideas?
Hold power and volume when turning on phone, then select fastboot and have the selection for bootloader highlighted, then start the RUU it should work then.
OK, so I tried the volume down + power btn deal, but still no dice. I really don't undestand wtf happened, cause before doing the 2nd part of root, I was able to load Damage ROM, now anything I load besides the PC36IMG.zip from part 1 just bootloops. Crazy
control_logic said:
I did all the steps to root the phone, 1 and 2, but got stuck in a bootloop. The sprint log stuff would come up, the the 4g, then back to sprint etc. I flashed the PC36IMG.zip of the shipped version, but now I can't get the RUU to take the phone into a fully factory state. It starts, then gets stuck waiting for bootloader with a black screen and htc on it. I really just want to make it factory again and start over with the root process. Any ideas?
Click to expand...
Click to collapse
ive seen this answered in the RUU threads. they mentioned the RUU doesn't automatically reboot the phone into the correct mode, i think it was bootloader? manually booting it into the correct mode, then connecting the USB, resolved the issue.
you might want to search/reference the RUU threads for more details as i never had the issue and am only recalling off the top of my head what ive read, which cant be 100% accurate!
When RUU stops/freezes and your phone has the black screen with "HTC" on it.... do not restart your phone or anything leave it the way it is. What you do is exit out of the RUU program by clicking "exit" when it freezes up. Then without doing anything to the phone, just restart the RUU program and it should pick up where it left off and complete the process. I found this fix in "Q and A" part of the Evo forum and it worked for me.
Sent from my PC36100 using Tapatalk
You need to format the phone rest and format cashe then install the rooted image and it will boot. I had the same problem.
Thanks for the responses, it is working again, YEAH!
Hi All,
OK, I am both new and stuck, I have read every page in the unlocking Atrix thread and the one click root thread but I still do not know what is wrong.
I started off by running the one click root listed here, the root went fine and seemed to work, so I proceeded to install ROM Manager but when I tried to back up my phone the process failed.
I googled the error and it turned out that I did not unlock the Boot Loader, so I followed all the instructions that explained how to do it and nothing worked.
Thinking something must have gone wrong I went back to the one click root tool and unrooted my phone, I checked and everything was working and the phone seemed fine.
So then I started down the longer process of unlocking/rooting here , following the steps to the letter and here is where I come unstuck.
I have a UK carrier free phone so after downloading and installing the RSD Lite software I used the SBF_Flash file but when I selected this file the “Start” button remained greyed out.
I researched this issue and found the international flash called intl-fix-try1.sbf, this file looked like it was going to work, the start button became clickable and the process looked ok.
Once I clicked start the flashing started and percentage done went straight up to 98% in a matter of seconds, then as per the instructions the phone reboots but starts to reboot fully, the process % resets and starts from zero going up in increments of 3%, by the time the process is at 65% my phone has fully booted and is sitting at the lock screen, if I leave it there the process will go up to 100% but the status will still say "in progress" until I swipe the lock screen and then it says complete.
I was doubtful that the root had worked but just to make sure I proceeded to move the phone into Fastboot mode and go through the OEM Unlock process but once I have typed in fastbook oem unlock and hit enter the command prompt just comes up with a message waiting for device to respond and nothing more.
Please help as I am really stuck, I followed your guide to rooting my Galaxy tab 10.1 and had it sorted in minutes, my ICS rom installed and everything backed up via ROM Manager so I am not a total dummy.
Any suggestions?
Kind Regards
Chris
when you tried to flash the sbf on rsd lite did you have the phone pluged into the pc and have it put into rsd lite mode
prolly not if you still seen the lock screen
turn phone off then turn on by holding power button down and volume down
when u see fastboot word on the atrix use volume down to scroll to rsd mode then hit volume up and proceed with rsd lite and the sbf
Here might explain it little more..
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
That is exactly what I did, I have just done it again now . . . .
I clicked start
The console/flash starts,
The phones screen goes black,
Then the Red Motorola M appears
The flash progress jumps to 98%
Console Status says something about USB Pass through/phone rebooting
Then reboots and the Red Motorola M appears again
Then progress carries on and goes up and at 16% by now the phone is now fully in its boot process and by 26% it is at the swipe screen
I have the phone in USB debug mode and the usb connection set to mass storage. Could I be using the wrong SBF file?
Thanks
I have tried that method as well as it is uses a different sbf file called zomgunocklite.sbf when I use that file I an error saying sec_exception: febe, 35, 35 I googled that and it came up with a similar issue but it did not help.
So since my first post I have been speaking to ltdanno360 on here, I just wanted to take the time out to say a MASSIVE THANK YOU.
He has taken me through getting my phone back to a usable state and then all the way through fixing up with the latest bits and pieces.
I have taken up a good few hours of his time and I am now a very, very happy Atrix owner.
It is people like ltdanno360 that make this forum and the internet community such an amazing place. Just imagine driving home from work one day and you car breaks down on the freeway, a stranger stops and spends two hours of his day fixing your car before sending you on your way.
Things like that do not happen often in the real world but people like Danno are great examples of what humanity often misses.
Big Thanks Bro
Awesome guy, awesome forum.
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 ?
I am in need of serious help! I dropped my phone off a 2nd story, smashed the screen completely. So I took my wife's old stylo 2 plus (exact same phone) stuck my Sim and SD into it, registered through metro pcs, and it worked great.
I did software update because I was really excited (my old stylo 2 was rooted and had many problems along with being unable to update android software).
Update took about an hour, then said failed. After that it has been unable to boot up. I tried recovery mode, it offers to factory reset. Again reboots and stuck at logo screen. Says error device is corrupt, cannot be trusted, will not boot. I press power it says press power again to boot anyway. Restarts and sticks at logo screen. Device is basically untouched. No oem unlock, no debugging, no developer options, nothing has been touched ever, the phone is 100% stock. I even did factory reset before I started using the phone.
Can someone please help me at the least flash trip so I can fix this??
I am not new to this, but has been 5 years since I flashed anything. The problem is, is that it's still locked, and can't boot up. The phones bricked and never been touched!
If I can get twrp flashed I can go from there, I need a way to unlock it, or flash without unlocking.
Please help me I need my phone for work. I'd rather not switch back to an old smashed screen
Cecil12 said:
I am in need of serious help! I dropped my phone off a 2nd story, smashed the screen completely. So I took my wife's old stylo 2 plus (exact same phone) stuck my Sim and SD into it, registered through metro pcs, and it worked great.
I did software update because I was really excited (my old stylo 2 was rooted and had many problems along with being unable to update android software).
Update took about an hour, then said failed. After that it has been unable to boot up. I tried recovery mode, it offers to factory reset. Again reboots and stuck at logo screen. Says error device is corrupt, cannot be trusted, will not boot. I press power it says press power again to boot anyway. Restarts and sticks at logo screen. Device is basically untouched. No oem unlock, no debugging, no developer options, nothing has been touched ever, the phone is 100% stock. I even did factory reset before I started using the phone.
Can someone please help me at the least flash trip so I can fix this??
I am not new to this, but has been 5 years since I flashed anything. The problem is, is that it's still locked, and can't boot up. The phones bricked and never been touched!
If I can get twrp flashed I can go from there, I need a way to unlock it, or flash without unlocking.
Please help me I need my phone for work. I'd rather not switch back to an old smashed screen
Click to expand...
Click to collapse
You need to download the kdz(device firmware) and flash it in download mode using lg up.
Sorry for the super long delay. I did what you said, and was able to use my phone again in no time. Thank you very much!
LG Stylo 2 Plus
Cecil12 said:
Sorry for the super long delay. I did what you said, and was able to use my phone again in no time. Thank you very much!
Click to expand...
Click to collapse
Hey would you be able to tell me which firmware worked or possibly even a link. I am having issues with getting one to work on the lg stylo 2 plus using lg up.