Related
Hey all, completely new to this forum and my Oneplus Two that I've had for a little over two weeks.
I recently got a OTA update for Oxygen 2.2.0 but I can't seem to install it. Everytime I download it and click the "install" option, the phone reboots (probably to go to recovery) but after a very brief splash screen and a vibration, it vibrates again and displays the standard boot splash screen, boots into the OS and offers me to download the update again.
I've done a little troubleshooting in the past two-three days and from what I understand, the phone doesn't seem to be able to boot into recovery or fastboot. I've enabled the advanced options in the "reboot" menu and when selecting "recovery" the phone reboots and does the same behavior described above. I tried powering off the phone and booting with the volume up button pressed (while pressing power) and the phone boots and displays a "Fastboot Mode" splash screen but it seems to hang there forever until I actually shut it off again and power it back on. Also, I've tried booting it into recovery from ADB, connected to my PC and I get the same behavior: brief splash screen with a vibrate and then the phone seems to reboot again normally.
I haven't tampered with the phone yet, it is brand new out of the box, not rooted and nothing other than simply installing a few games, Nova Launcher, changing the wallpaper and using it as you would normally use your phone.
Anyone has an idea how I could actually get the Recovery functioning on this phone?
Best regards and thanks in advance for any help!
redbay1 said:
Hey all, completely new to this forum and my Oneplus Two that I've had for a little over two weeks.
I recently got a OTA update for Oxygen 2.2.0 but I can't seem to install it. Everytime I download it and click the "install" option, the phone reboots (probably to go to recovery) but after a very brief splash screen and a vibration, it vibrates again and displays the standard boot splash screen, boots into the OS and offers me to download the update again.
I've done a little troubleshooting in the past two-three days and from what I understand, the phone doesn't seem to be able to boot into recovery or fastboot. I've enabled the advanced options in the "reboot" menu and when selecting "recovery" the phone reboots and does the same behavior described above. I tried powering off the phone and booting with the volume up button pressed (while pressing power) and the phone boots and displays a "Fastboot Mode" splash screen but it seems to hang there forever until I actually shut it off again and power it back on. Also, I've tried booting it into recovery from ADB, connected to my PC and I get the same behavior: brief splash screen with a vibrate and then the phone seems to reboot again normally.
I haven't tampered with the phone yet, it is brand new out of the box, not rooted and nothing other than simply installing a few games, Nova Launcher, changing the wallpaper and using it as you would normally use your phone.
Anyone has an idea how I could actually get the Recovery functioning on this phone?
Best regards and thanks in advance for any help!
Click to expand...
Click to collapse
That is the norm for fastboot, it doesn't go past that screen.
It may not make a difference, did you try to boot to recovery via Power+Volume Down buttons?
Greetings Khaos64,
Yes, I've tried booting with Vol-Down+Power but the phone does not start.
With volume-up+power, I get the Fastboot splash screen but the phone does not respond to any input.
I tried selecting "bootloader" from the reboot menu but I get the same thing: Reboots and after a second, the phone reboots again normaly and into OxygenOS.
Is there a way to verify if the bootloader or recovery is corrupt and maybe reflash the stock recovery onto the phone?
Thanks for your input!
You may just want to go straight to oneplus support since everything is stock and only 2 weeks they should be able to get you updated or replace it.
If you'd like to be more hands on... maybe something below can help.
So your phone isn't recognized/no commands acceptred from your computer when booted to fastboot?
Such as unlocking your bootloader and booting into twrp... "fastboot boot yourfilename.img" or maybe flashing it.
Make sure OEM unlocking is selected in Developer options.
If you can't do that then this may not work but is worth a shot.
http://forum.xda-developers.com/showpost.php?p=62973446&postcount=2
These may also be something to look into:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
I did try to contact Oneplus for support but I am not the one who purchased the phone. Long story short, it was a gift from my girlfriend that she bought off of someone. The phone was new in box and was a warranty replacement. I would have to contact the seller and go trough him for support unfortunately.
Thanks for the different suggestions!, I will fiddle around with it this afternoon while the kids are having their mid-day nap and I'll get back with the results
Thanks again for the help, it's greatly appreciated!
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Congratulations hope you enjoy the phone
Sent from my ONE A2005 using Tapatalk
redbay1 said:
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Click to expand...
Click to collapse
Glad one was able to help you do it. :good:
redbay1 said:
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Click to expand...
Click to collapse
HI there,
I am having the exact same issue with my oneplus 2. Unfortunately i know almost nothing regarding these android thingy. I know it has been almost 2 years, would you mind guide me through the steps? I would appreciate it so much.
Thanks.
Basically my phone fails to boot or do anything, power button is broken, it turns on when conneted to a charger. When its connected it vibrates and thats it, screen doesn't turn on nothing happens.
So basically the following happened I accidentally deleted "system/usr" but i had a copy and tried to copy back but was unable to do so. So i rebooted the phone, seemed to boot up normally however on the att boot up screen the phone froze.
I removed the battery and booted up the phone but it would freeze in the same att screen (I repeated this about 3 times)
After no results I booted my phone up in Safestrap recover which worked perfectly, in recovery I used the file manager to supposedly copy "usr" to "system" which supposedly did go through So i reboted the phone using reboot system option .
(Repeated this process about 3 times) still got stuck at last boot screen on the att logo.
So after this I repeated the process of copying "usr" to "system". But this time i rebooted to recovery thinking it would boot back to Safestrap,however it booted to stock android recovery.
In stock recovery I was able to navigate but I couldnt select anything (due to broken power button) so I removed the battery. This is when it all went bad the phone now wont boot. Only vibrates when connected to charger but the screen remains black.
EDIT: the phone boots back up to safestrap, however it still wont boot up. Still gets stuck on att boot screen (im suspecting because of the removed "usr" file) is there a way i can use The command terminal in safestrap to copy back the "usr" file.
DaFrenchTaco said:
Basically my phone fails to boot or do anything, power button is broken, it turns on when conneted to a charger. When its connected it vibrates and thats it, screen doesn't turn on nothing happens.
So basically the following happened I accidentally deleted "system/usr" but i had a copy and tried to copy back but was unable to do so. So i rebooted the phone, seemed to boot up normally however on the att boot up screen the phone froze.
I removed the battery and booted up the phone but it would freeze in the same att screen (I repeated this about 3 times)
After no results I booted my phone up in Safestrap recover which worked perfectly, in recovery I used the file manager to supposedly copy "usr" to "system" which supposedly did go through So i reboted the phone using reboot system option .
(Repeated this process about 3 times) still got stuck at last boot screen on the att logo.
So after this I repeated the process of copying "usr" to "system". But this time i rebooted to recovery thinking it would boot back to Safestrap,however it booted to stock android recovery.
In stock recovery I was able to navigate but I couldnt select anything (due to broken power button) so I removed the battery. This is when it all went bad the phone now wont boot. Only vibrates when connected to charger but the screen remains black.
EDIT: the phone boots back up to safestrap, however it still wont boot up. Still gets stuck on att boot screen (im suspecting because of the removed "usr" file) is there a way i can use The command terminal in safestrap to copy back the "usr" file.
Click to expand...
Click to collapse
Maybe, and just maybe, you could use ADB.
Otherwise you might have to somehow try and get download mode booting and re-flash stock rom.
DaFrenchTaco said:
Basically my phone fails to boot or do anything, power button is broken, it turns on when conneted to a charger. When its connected it vibrates and thats it, screen doesn't turn on nothing happens.
So basically the following happened I accidentally deleted "system/usr" but i had a copy and tried to copy back but was unable to do so. So i rebooted the phone, seemed to boot up normally however on the att boot up screen the phone froze.
I removed the battery and booted up the phone but it would freeze in the same att screen (I repeated this about 3 times)
After no results I booted my phone up in Safestrap recover which worked perfectly, in recovery I used the file manager to supposedly copy "usr" to "system" which supposedly did go through So i reboted the phone using reboot system option .
(Repeated this process about 3 times) still got stuck at last boot screen on the att logo.
So after this I repeated the process of copying "usr" to "system". But this time i rebooted to recovery thinking it would boot back to Safestrap,however it booted to stock android recovery.
In stock recovery I was able to navigate but I couldnt select anything (due to broken power button) so I removed the battery. This is when it all went bad the phone now wont boot. Only vibrates when connected to charger but the screen remains black.
EDIT: the phone boots back up to safestrap, however it still wont boot up. Still gets stuck on att boot screen (im suspecting because of the removed "usr" file) is there a way i can use The command terminal in safestrap to copy back the "usr" file.
Click to expand...
Click to collapse
Just reflash the rom you are on without wiping. That should fix it.
Is the phone an i337? If it is, you're in the wrong s4 forum.
GDReaper said:
Maybe, and just maybe, you could use ADB.
Otherwise you might have to somehow try and get download mode booting and re-flash stock rom.
Click to expand...
Click to collapse
Okay and suppose i could get adb working how would i copy the "usr" file back to the "/system"
audit13 said:
Is the phone an i337? If it is, you're in the wrong s4 forum.
Click to expand...
Click to collapse
Yea it is the i337 my bad i didnt noticed can it be moved?
Contact a moderator and ask him or her to move your thread.
Lennyz1988 said:
Just reflash the rom you are on without wiping. That should fix it.
Click to expand...
Click to collapse
Thank you this seemed to work, however my sd card wont mount.
Nor does my wifi turno on.
DaFrenchTaco said:
Thank you this seemed to work, however my sd card wont mount.
Nor does my wifi turno on.
Click to expand...
Click to collapse
In cases like this it's best to backup everything you want and then perform a full wipe.
ps if you are still on 4.2.2. that means you don't have an locked bootloader right? Then why are you using safestrap? I thought that's only for when you have a locked bootloader.
Lennyz1988 said:
In cases like this it's best to backup everything you want and then perform a full wipe.
ps if you are still on 4.2.2. that means you don't have an locked bootloader right? Then why are you using safestrap? I thought that's only for when you have a locked bootloader.
Click to expand...
Click to collapse
I think AT&T and Verizon phones always had locked bootloaders, just that the earlier versions were easier to hack.
if its hard bricked, try jtag
thnx to everyone in this thread you were all of help my phone is now working even better then it did before much appreciated
Back story and Issue
Soo when I first got my Axon 7, I've first rooted my phone and got TWRP (but it was stuck with a password) and later on around 1-2 weeks later, a new update came out (Build 29) just not too long today so what I did was try to install it but failed and I couldn't back it up anyways due to a password issue that people were having so later, I saw this post thinking it could removing the password issue by flashing the image with TWRP in the "Install" and press "Install Images" or something like that and and it ask where to install it, I installed it in recovery and proceed to install it. Later on, my phone booted into Android and I decided to go back to TWRP to see if it worked and when I turned off my phone and press Up Volume + Power, it goes to the ZTE boot logo for 1 sec and black screened with a red light or 1 sec and turned off immediately which scared me a lot because I think I just my recovery. So what I did was going back to the original post on where I installed my original TWRP and root and being following the steps by going to adb reboot edl and first enter this command axon7backup.exe -p 4 -d and later use the recovery from Unjustified Dev's post (TWRP 3.0.2-2) and used that for the recovery and typed in axon7root.exe -p 4 -r and when I try to boot my phone, the logo shows up for 1 sec and turns off and when I try the Up Volume and power, same thing and when I try Down and Power, same thing, nothing. Doing adb devices doesn't do anything BUT my Qualcomm Drivers and still see COM5 so when I unplugged my phone and plug it back in, my desktop literally froze up in the worst possible situation I've ever seen and I had to replug my desktop and once I booted my computer, I tried again with axon7root.exe -p 5 -b ( or was it -r.. I forgot) and somehow fixed my phone and my phone was able to boot but the recovery problem still persist. someone help
https://www.youtube.com/watch?v=e9sjILIiFFU
xDaDeevellopar said:
Back story and Issue
Soo when I first got my Axon 7, I've first rooted my phone and got TWRP (but it was stuck with a password) and later on around 1-2 weeks later, a new update came out (Build 29) just not too long today so what I did was try to install it but failed and I couldn't back it up anyways due to a password issue that people were having so later, I saw this post thinking it could removing the password issue by flashing the image with TWRP in the "Install" and press "Install Images" or something like that and and it ask where to install it, I installed it in recovery and proceed to install it. Later on, my phone booted into Android and I decided to go back to TWRP to see if it worked and when I turned off my phone and press Up Volume + Power, it goes to the ZTE boot logo for 1 sec and black screened with a red light or 1 sec and turned off immediately which scared me a lot because I think I just my recovery. So what I did was going back to the original post on where I installed my original TWRP and root and being following the steps by going to adb reboot edl and first enter this command axon7backup.exe -p 4 -d and later use the recovery from Unjustified Dev's post (TWRP 3.0.2-2) and used that for the recovery and typed in axon7root.exe -p 4 -r and when I try to boot my phone, the logo shows up for 1 sec and turns off and when I try the Up Volume and power, same thing and when I try Down and Power, same thing, nothing. Doing adb devices doesn't do anything BUT my Qualcomm Drivers and still see COM5 so when I unplugged my phone and plug it back in, my desktop literally froze up in the worst possible situation I've ever seen and I had to replug my desktop and once I booted my computer, I tried again with axon7root.exe -p 5 -b ( or was it -r.. I forgot) and somehow fixed my phone and my phone was able to boot but the recovery problem still persist. someone help
Click to expand...
Click to collapse
ok what is the problem? if it is TWRP asking for that password I only got away from that by unlocking the phone
tabletalker7 said:
ok what is the problem? if it is TWRP asking for that password I only got away from that by unlocking the phone
Click to expand...
Click to collapse
Well, I can't boot into recovery as it would boot into the ZTE logo for 1 second and turn off but when I boot it up to system or android, it works. Added a YouTube link in the post.
xDaDeevellopar said:
Well, I can't boot into recovery as it would boot into the ZTE logo for 1 second and turn off but when I boot it up to system or android, it works. Added a YouTube link in the post.
Click to expand...
Click to collapse
Mine did that when I tried to re-lock my bootloader (don't ask). I used the goodies in here http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204 to install TWRP and then used TWRP to do a factory reset.
tabletalker7 said:
Mine did that when I tried to re-lock my bootloader (don't ask). I used the goodies in here http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204 to install TWRP and then used TWRP to do a factory reset.
Click to expand...
Click to collapse
Can you tell me the exact steps? I'm not too good at doing stuff like this though I do have a basic understanding.
nevermind, I fixed it lol but I still have the password issue in TWRP help?
xDaDeevellopar said:
Can you tell me the exact steps? I'm not too good at doing stuff like this though I do have a basic understanding.
nevermind, I fixed it lol but I still have the password issue in TWRP help?
Click to expand...
Click to collapse
I noticed that password on TWRP - it is caused by the factory encryption. I wanted to unlock my bootloader and when I did the unlock, it did away with that problem. http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 just go slow, the directions are pretty straight forward (if you want to unlock)
tabletalker7 said:
I noticed that password on TWRP - it is caused by the factory encryption. I wanted to unlock my bootloader and when I did the unlock, it did away with that problem. http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 just go slow, the directions are pretty straight forward (if you want to unlock)
Click to expand...
Click to collapse
What does it mean by "navigate to your adb location."?
Damn, just encounter another problem... wifi...
It's ain't turning on and when I go to the Wifi settings in Settings, all it show is it is turned off with no networks and doesn't say anything beside the 3 dots, Wifi, back button, and the off button for wifi. help?
xDaDeevellopar said:
Damn, just encounter another problem... wifi...
It's ain't turning on and when I go to the Wifi settings in Settings, all it show is it is turned off with no networks and doesn't say anything beside the 3 dots, Wifi, back button, and the off button for wifi. help?
Click to expand...
Click to collapse
Do yourself a huge favor - there is a giant box in the top left of the screen as you read this. It is called a search bar. Everything (and I mean EVERY SINGLE THING) you have asked about thus far has been gone over to COMPLETE EXHAUSTION many times over. I am trying to be nice and help you through this whole process but wow, come on already. http://forum.xda-developers.com/axon-7/how-to/please-check-wifi-flashing-bootloops-t3451544 read this post from front to back, then back to front, and then if you still have questions the people over there odds are have your solution
xDaDeevellopar said:
Back story and Issue
Soo when I first got my Axon 7, I've first rooted my phone and got TWRP (but it was stuck with a password) and later on around 1-2 weeks later, a new update came out (Build 29) just not too long today so what I did was try to install it but failed and I couldn't back it up anyways due to a password issue that people were having so later, I saw this post thinking it could removing the password issue by flashing the image with TWRP in the "Install" and press "Install Images" or something like that and and it ask where to install it, I installed it in recovery and proceed to install it. Later on, my phone booted into Android and I decided to go back to TWRP to see if it worked and when I turned off my phone and press Up Volume + Power, it goes to the ZTE boot logo for 1 sec and black screened with a red light or 1 sec and turned off immediately which scared me a lot because I think I just my recovery. So what I did was going back to the original post on where I installed my original TWRP and root and being following the steps by going to adb reboot edl and first enter this command axon7backup.exe -p 4 -d and later use the recovery from Unjustified Dev's post (TWRP 3.0.2-2) and used that for the recovery and typed in axon7root.exe -p 4 -r and when I try to boot my phone, the logo shows up for 1 sec and turns off and when I try the Up Volume and power, same thing and when I try Down and Power, same thing, nothing. Doing adb devices doesn't do anything BUT my Qualcomm Drivers and still see COM5 so when I unplugged my phone and plug it back in, my desktop literally froze up in the worst possible situation I've ever seen and I had to replug my desktop and once I booted my computer, I tried again with axon7root.exe -p 5 -b ( or was it -r.. I forgot) and somehow fixed my phone and my phone was able to boot but the recovery problem still persist. someone help
https://www.youtube.com/watch?v=e9sjILIiFFU
Click to expand...
Click to collapse
hey, could u please tell me how u managed to boot up ur device again... i've also bricked my a2017g to a point where i can't even boot into edl mode...
i submitted this post - https://forum.xda-developers.com/axon-7/help/a2017g-totally-bricked-t3537990#post70561874
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 ?
Hello Fellows,
First I'd like to explain my situation in details.
my phone fell while i was walking on the street and it got some dirt on it, so ( foolishly ) I decided to clean it.... and yeah... i washed my phone like washing a dish... i like rinsed the phone in water and in other cleaning liquids for no more than 3 seconds it was all quick thingy... anyway after washing it.... i directly powered it ON and it powered but the screen was OFF ( so i decided to power it OFF, solder it and to remove any clues of water inside on the board or something... after that i used a hairdryer ( which is not recommended ) but i used it at a descent distance so that no harm would be caused to the board... as i was only subjecting air to let water if any existed to dry..
i put the phone in rise and kept it for 1 day... after 1 day i wanted to check out how stuff went.. so i powered it ON and the screen actually turned ON and the vibrator, even the hardware back-light lighted up perfectly but here's the problem I'm facing.
the phone only boots into TWRP 3.1.0.0 no matter what i do.. things i tried:
1- flashed some ROM, through TWRP
2- used "Fixed Contexts" in TWRP
3- Repair File System "System partition" through TWRP
4- used file manager inside TWRP and checked if the internal storage is working and indeed i can show all my files, through TWRP
5- also used the file manager to access "System" Partition and everything was there, through TWRP
6- change File System into EXT4 "System partition" through TWRP
7- Resize File System "System partition" through TWRP
8- Wiping all Partitions "Excluding the internal storage"
and NON WORKED..
note that whenever i attempt to flash a ROM the result shows successful with no errors ..
so whats the problem in here?
i have a guess but i need help in order to apply it.. i think the VOL- is pressed and stuck somehow Electrically on the board ( but no physically as i can press the volume down and hear its tap or whatever you call it.. i even managed to boot into fast-boot and it worked.
is there anyway i can disable the vol- button temporary to see if its causing the problem?
the only thing is i cant see my ROM booting... not even the boot animation showing... just the boot-loader and automatically it goes into the recovery
also i have kernel log attached below followed by the recovery log
EDIT: i also forgot to mention that my PC recognize the phone and i have access to my internal storage.. no problems with transfer speed as well
after tons of attempts and searching online and flashing stuff and blablabla... (i flashed every recovery image op2 support )
FINALLY
I found the solution my self, and everything is back to normal...
the phone was stuck at the early stage of the booting process and maybe couldn't find the boot image in order to boot up the android OS, so all i did was i plugged in the phone into the PC, i started everything in fastboot mode on phone and on PC then i just sent the following command to my phone.
Code:
fastboot continue
fastboot then(meaning after the command) wasnt able to recognize the phone anymore so i knew that its now trying to search for partitions other than recovery.. i waited like 10 seconds and booom it booted into the best ROM i've ever used ( and actually missed ) which is Official RR from our great maintainer "nicesoni_ash"
P.S: the vol- as i said was really stuck and i noticed it not working while on RR ROM, so i just clicked it many times and tried mixing vol+ with vol- .. after many many attempts vol- worked and i then rebooted to make sure if everything is back to normal and no recovery auto boots and indeed it smoothly booted up :laugh:
thanks a lot for all who tried to help out in here or on oneplus forums :highfive:
#back_to_resurrect_and_will_always_remix
Did you try reverting to stock ?
Try getting files from here..
https://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
I would consider it as bricked, after all attempts failed and go with the unbrick guide here on xda or oneplus forums, maybe this way it can be ressurected.
You probably have already backed up your data..
Damn, that hurts..
mithu.creative said:
Did you try reverting to stock ?
Try getting files from here..
https://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
Click to expand...
Click to collapse
sorry for this late reply but yes i have tried flashing every ROM from stock to Custom ones even i flashed EVERY SINGLE RECOVERY IMAGE OUR PHONE SUPPORTS XD and non worked... first aid.. qualcomm toolkit... non...
hello bro, i updated a magisk module v4android and when i reboot, it boots up in twrp. and since then it keeps booting into twrp. So, i used fastboot continue and when it boot int the home i deleted that module.
but fastboot continue only works once. After that if i switch-off and switch-on the phone, it goes into twrp. it needs fastboot continue everytime.
please provide me a permanent solution. few other users are facing this too. plz reply i'm waiting.
Hey,
with the help of some others in a Discord server (thanks @thesanjayp#6251 on discord) i managed to find the issue. Appearantly there was a change in /dev/block/bootdevice/by-name/misc for some reason. There was a similar problem on the old LG Optimus G Pro which i owned, so i remembered this.
As I'm not sure if we can just wipe the partition or not, i got a working misc.img attached.
In any terminal (adb shell, twrp terminal or an terminal app in a rom) make sure you have su rights, and then execute the following command:
Code:
dd if=/path/to/misc.img of=/dev/block/bootdevice/by-name/misc
Make sure to adapt the path to the misc.img though to the location you saved it to.
The misc.img I used is attached to this post.
PS: Im not responsible for any broken phones if this didnt work for you.