What's up everyone. So I unlocked the bootloader of my Verizon pixel OK. I then went to root it and after it rebooted once it seems to be stuck at the jumping dots screen. It's been like 5 minutes. Not sure what I should do.
Any suggestions?
From bootloader:
Using stock boot.img from your version's factory image from Google. (In a zip inside the main zip).
Fastboot flash boot_a boot.img
Fastboot flash boot_b boot.img
Fastboot reboot
Then after setting up your phone try rooting again. You have to boot once stock after unlocking bootloader initially.
If still no dice, use flash-all.bat or .sh to go fully stock, then boot and set device up then reboot to root as per normal directions for your firmware.
Rooting won't cause a second wipe. Just unlocking or flashing factory image.
Do NOT relock bootloader (potential brick).
Sent from my sailfish using XDA Labs
Got it!! Holy Crap brother thank you!!!
Just so I don't do that again, which root files should I be using? I read it may have been caused from using outdated files
Which method did you use to gain root? Fastboot boot boot-to-root.img caused me to bootloop. I restored the factory image, installed TWRP alpha2, then flashed SuperSU 2.78 SR5 from TWRP and all was fine.
yeah i tried the boot boot method. I guess I should try the twrp method. Just so I don't screw up again, do you remember where you got the files. Figure I'll use those if they worked for you.
Everything is in the Pixel ROMs, Kernels, Recoveries, and Other Development Forum.
FernBch said:
Everything is in the Pixel ROMs, Kernels, Recoveries, and Other Development Forum.
Click to expand...
Click to collapse
Thanks! OK so i downloaded the twrp file I'm getting a failed error message. I've renamed the file twrp.img and am using this commmand to flash it fastboot flash recovery twrp.img
What am I doing wrong?
RC1 or Alpha2? RC1 kept giving me md5 mismatch errors. On the TWRP download page both Alpha2 files are also available.
I'm trying to flash alpha 2 and it keeps saying Failed remote partition recovery doesnt exist
Haven't seen that one before. When I tried the boot-to-root method I had to restore a factory image before I could try again.
FernBch said:
Haven't seen that one before. When I tried the boot-to-root method I had to restore a factory image before I could try again.
Click to expand...
Click to collapse
Yeah I'm totally stumped. I did have to reflash the boot image and am back up and running. just can't seem to get twrp to flash!! I've followed the steps from multiple threads and just can't get it to work.
Any suggestions are welcome
Boot twrp Img, not flash. Then install the twrp zip if you want it to replace the stock recovery.
Which guide says flash..theres a new rc1 out but haven't checked it. You made 2 posts regarding inability to flash but did you Google for the answer?
I kept trying to flash it cause the threads and sites I saw kept using that command. I finally used fastboot boot twrp.img and it worked fine. Also many of the guides don't say you need to have the zip on your phone to flash.
No prob, I worked it out!! Thanks for everyone's responses!!!
Related
All,
Long time lurker, first time poster. I've been doing a bunch of reading for the past few hours, I think my phone isn't completely f***, I'm just missing something simple.
So basically, I started with a stock HTC One XL with Telstra. Updated to the latest firmware version (3.17) and bootloader 2.14.
1. I unlocked the bootloader using htcdev. Installed CM10.1 smoothly, booted into the ROM and realised the touch screen didnt work (now I realise that's the new firmware problem).
2. Booted back into recovery (TWRP 2.4.1) and accidently wiped my SD card along with everything else (including backups).
3. Mounted SD card, and formatted it with FAT32. Put Viper 3.2.7 on it and installed it via recovery ---> Stuck in a boot loop. Phone boots to the Viper screen, does a bit of loading, and then re-boots. (I have also tried this with various other sense based ROMs, with the same problem).
4. After a bit of reading, I tried to manually load the boot.img file via fastboot. I get the following error message: FAILED: <remote: signature verify fail>.
So now I turn to you for help! After 3 years with Android, I have never had trouble flashing new ROMs following the instructions on this awesome site. I hope you guys can help me out on this one. All my phone content is backed up on my PC, so my only concern is getting a working ROM again.
So in summary, what I am able to do is:
- Boot to bootloader (which is unlocked)
- I DO NOT have s-off
- I can boot to TWRP recovery and mount my SD to copy any file across
I have not tried running RUU yet, leaving that as a last resort.
brad.cap said:
All,
Long time lurker, first time poster. I've been doing a bunch of reading for the past few hours, I think my phone isn't completely f***, I'm just missing something simple.
So basically, I started with a stock HTC One XL with Telstra. Updated to the latest firmware version (3.17) and bootloader 2.14.
1. I unlocked the bootloader using htcdev. Installed CM10.1 smoothly, booted into the ROM and realised the touch screen didnt work (now I realise that's the new firmware problem).
2. Booted back into recovery (TWRP 2.4.1) and accidently wiped my SD card along with everything else (including backups).
3. Mounted SD card, and formatted it with FAT32. Put Viper 3.2.7 on it and installed it via recovery ---> Stuck in a boot loop. Phone boots to the Viper screen, does a bit of loading, and then re-boots. (I have also tried this with various other sense based ROMs, with the same problem).
4. After a bit of reading, I tried to manually load the boot.img file via fastboot. I get the following error message: FAILED: <remote: signature verify fail>.
So now I turn to you for help! After 3 years with Android, I have never had trouble flashing new ROMs following the instructions on this awesome site. I hope you guys can help me out on this one. All my phone content is backed up on my PC, so my only concern is getting a working ROM again.
So in summary, what I am able to do is:
- Boot to bootloader (which is unlocked)
- I DO NOT have s-off
- I can boot to TWRP recovery and mount my SD to copy any file across
I have not tried running RUU yet, leaving that as a last resort.
Click to expand...
Click to collapse
FAILED: <remote: signature verify fail> means your bootloader is locked.
exad said:
FAILED: <remote: signature verify fail> means your bootloader is locked.
Click to expand...
Click to collapse
But it says **** UNLOCKED **** (as well as **** TAMPERED ****) at the top of the bootloader?
brad.cap said:
But it says **** UNLOCKED **** (as well as **** TAMPERED ****) at the top of the bootloader?
Click to expand...
Click to collapse
what is the command you used to load the boot.img and where did the boot.img come from?
on an unrelated note. flash twrp 2.3.3.1 instead every version above has issues wiping leading to issues not unlike yours.
after flashing 2.3.3.1 dont forget to do fastboot erase cache.
exad said:
FAILED: <remote: signature verify fail> means your bootloader is locked.
Click to expand...
Click to collapse
exad said:
what is the command you used to load the boot.img and where did the boot.img come from?
on an unrelated note. flash twrp 2.3.3.1 instead every version above has issues wiping leading to issues not unlike yours.
after flashing 2.3.3.1 dont forget to do fastboot erase cache.
Click to expand...
Click to collapse
I use "fastboot flash flash boot.img", the boot.img is extracted from the zip of the Viper ROM that is installed on my phone.
Will do! Will this help with the situation at hand? I'd rather keep as many factors static as possible. I'll flash twrp 2.3.3.1 once everything is resolved (unless it can help now?)
brad.cap said:
I use "fastboot flash flash boot.img", the boot.img is extracted from the zip of the Viper ROM that is installed on my phone.
Will do! Will this help with the situation at hand? I'd rather keep as many factors static as possible. I'll flash twrp 2.3.3.1 once everything is resolved (unless it can help now?)
Click to expand...
Click to collapse
Flash it now then try flashing again after wiping everything on 2.3.3.1
Sent from my HTC One X using xda app-developers app
brad.cap said:
I use "fastboot flash flash boot.img", the boot.img is extracted from the zip of the Viper ROM that is installed on my phone.
Will do! Will this help with the situation at hand? I'd rather keep as many factors static as possible. I'll flash twrp 2.3.3.1 once everything is resolved (unless it can help now?)
Click to expand...
Click to collapse
the command is fastboot flash boot boot.img btw.
but yes flash 2.3.3.1 first then fastboot erase cache then the boot img.
if you experience bugs that are not discussed in the ROMs op do a fresh wipe everything and reflash the rom because wiping with 2.4 probably wasn[t a clean wipe.
exad said:
the command is fastboot flash boot boot.img btw.
but yes flash 2.3.3.1 first then fastboot erase cache then the boot img.
if you experience bugs that are not discussed in the ROMs op do a fresh wipe everything and reflash the rom because wiping with 2.4 probably wasn[t a clean wipe.
Click to expand...
Click to collapse
Thanks. Will try that now.
Edit: Yep. That worked. Viper booted up fine and everything is working!
I'm going to make a back-up of this working ROM now, and have another go at getting CM10.1 to work.
Thanks for your help guys, really appreciate it. Especially exad.
Hi everyone, I have the mha-l29 and successfully updated to the latest Oreo for the US version. I then unlocked the bootloader, flashed TWRP, flash Superuser and everything was working fine. I then got an error message while doing a backup in TWRP and foolishly edited a file which caused the system to not boot. I then Flashed the hwoa7 instead of 8 to fix it and now my phone is bricked. The only thing I can do is get into fastboot. Everything else throws an error. Is ee a func no: 11 error. Please see attached pictures. Please let me know how I can fix it. I've already tried reflashing the ramdisk as well as TWRP bet I can't boot into TWRP.
Thanks so much
C:\>fastboot oem lock-state info
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ 0.008s]
finished. total time: 0.012s
Do you mean you flashed RECOVERY_nocheck from Nougat to Recovery of Oreo?
If so you should only need to flash recovery_ramdisk.
I guess you could extract ramdisk, recovery_ramdisk and kernel and flash to the partitions of the same name.
See what error it gives after you flash back stock recovery_ramdisk
Thank you for your help ante. I ended up fixing it by using DC unlocker. That Basically got me to where I could boot into erecovery. It also allowed me to use ADB to flash TWRP. From there I just flashed the entire hwota8 package. I'm back up and running thankfully. Once again, I really appreciate you and people like you who help others on this forum.
saw this to late , TWRP caused this i had the same thing earlier and reinstalled different TWRP
seti007 said:
Thank you for your help ante. I ended up fixing it by using DC unlocker. That Basically got me to where I could boot into erecovery. It also allowed me to use ADB to flash TWRP. From there I just flashed the entire hwota8 package. I'm back up and running thankfully. Once again, I really appreciate you and people like you who help others on this forum.
Click to expand...
Click to collapse
DC-Unlockr allowed you to use adb to flash twrp? How were you able to do that exactly?
I was able to flash the entire update package using DC Unlocker. That should have gotten me up fully but it did not. Before using DC unlocker, I was not able to even boot into TW RP or erecovery. I was able to get into fastboot but could not install anything. I did not get any errors in ADB and installations were successful but I could not boot into TWRP. After using DC Unlocker, I went back into fastboot and used ADP to install TW RP. I was then able to boot into TW RP. So the difference that DC unlocker made was that it allowed me to use ADB to successfully install TWRP.
I had the very same issue previously with another device. It was running an old version of TWRP. Regardless of what I flashed, it would give errors, etc.
However, using ADB, I flashed the very latest recovery and voila! Flashed a rom successfully as well as other apps without any issues.
It's always best to use the latest possible recovery to avoid issues with flashing.
Glad you solved your problem
Wirmpolter said:
DC-Unlockr allowed you to use adb to flash twrp? How were you able to do that exactly?
Click to expand...
Click to collapse
Good sir, can you link me to a working twrp? I tried several twrps, but i cant seem to boot into recovery. TIA
marktheripper said:
Good sir, can you link me to a working twrp? I tried several twrps, but i cant seem to boot into recovery. TIA
Click to expand...
Click to collapse
Were you running Android Nougat or Oreo? I've just used the TWRP's found here on the xda forums. However, I didn't use TWRP nor dc-unlockr to fix my issue. Have you tried the hardware button combo of volume up And power to boot into it?
Oreo. I tried using the twrps available, but i cant seem to boot into twrp. It goes directly to error mode. Im using the power + vol up btw.
Hi. I just unlocked my bootloader and was trying to flash twrp. Every time I do that the phone goes into infinite bootloop. I tired different twrp img but having the same problem. Please guide me how to flash twrp and which to use. Also I want to flash magisk to gain root.
si1233 said:
Hi. I just unlocked my bootloader and was trying to flash twrp. Every time I do that the phone goes into infinite bootloop. I tired different twrp img but having the same problem. Please guide me how to flash twrp and which to use. Also I want to flash magisk to gain root.
Click to expand...
Click to collapse
How are you flashing TWRP? What version are you trying?
Have you tried to go into recovery after flashing?
Sometimes you may need to go into recovery to correct the permissions before anything will work.
Have you tried flashing a fixed kernel for your build?
More information please.
I have just unlocked the bootloader and did not do anything else. I am on g8141. I used the flash tool to flash twrp. I used latest version of twrp, also tried 3.1.1. I also tried dragging the twrp to the command window via adb.
si1233 said:
I have just unlocked the bootloader and did not do anything else. I am on g8141. I used the flash tool to flash twrp. I used latest version of twrp, also tried 3.1.1. I also tried dragging the twrp to the command window via adb.
Click to expand...
Click to collapse
Try following the instructions on janjan's kernel thread, it's very detailed with links to files.
It suggests using ADB to push TWRP.
I would avoid flashtool.
I've use fastboot to flash TWRP.
I've used the version 3.2.3.0 (offical marple version for the G8141)
I am currently on OOS 10 OB2/31 and can't seem to find a way to install TWRP and Magisk. Found ways to install TWRP and Magisk via patched boot images on OOS 10 stable but not for OB2/31.... anyone know why it's not as simple as flashing TWRP via fastboot?
I also have a problem
'OOS10beta31' Root
XcutionerX said:
[...] anyone know why it's not as simple as flashing TWRP via fastboot?
Click to expand...
Click to collapse
Because OnePlus upgraded the bootloader in their OOS10 release. One of the changes was disabling the fastboot boot command that you usually needed to boot to TWRP. Without that command, you had to flash the TWRP img files onto the boot partition first in order to be able to boot TWRP.
There are many -- maybe a bit too many -- guides on how to install TWRP on OOS10. Here and here are some I found.
The gist of it is to boot to TWRP by running the fastboot flash boot twrp_file.img command, rebooting to recovery, then flashing the twrp zip file. And that's pretty much it.
PS In my case, I wasn't able to reboot to TWRP by using mauronofrio's twrp-3.3.1-14 version, and had to use his twrp-3.3.1-11 instead.
adeklipse said:
Because OnePlus upgraded the bootloader in their OOS10 release. One of the changes was disabling the fastboot boot command that you usually needed to boot to TWRP. Without that command, you had to flash the TWRP img files onto the boot partition first in order to be able to boot TWRP.
There are many -- maybe a bit too many -- guides on how to install TWRP on OOS10. Here and here are some I found.
The gist of it is to boot to TWRP by running the fastboot flash boot twrp_file.img command, rebooting to recovery, then flashing the twrp zip file. And that's pretty much it.
PS In my case, I wasn't able to reboot to TWRP by using mauronofrio's twrp-3.3.1-14 version, and had to use his twrp-3.3.1-11 instead.
Click to expand...
Click to collapse
Thank you for your help, gonna try following those. Hopefully I don't f up and have to do a msm restore. But why would they disable that command?... Just to make everything complicated? Guess I will not stick to Oneplus next year.
XcutionerX said:
But why would they disable that command?
Click to expand...
Click to collapse
Security? Deprecated or soon-to-be-deprecated command? Dunno really, lol.
XcutionerX said:
... Just to make everything complicated?
Click to expand...
Click to collapse
To be fair, the only difference between this method and the old method is just one word and manually rebooting to recovery. You still have to flash the twrp.zip after flashing from bootloader file to install TWRP, so it's not too radically different.
this can help
https://forum.xda-developers.com/showpost.php?p=80897567&postcount=332
adeklipse said:
Because OnePlus upgraded the bootloader in their OOS10 release. One of the changes was disabling the fastboot boot command that you usually needed to boot to TWRP. Without that command, you had to flash the TWRP img files onto the boot partition first in order to be able to boot TWRP.
There are many -- maybe a bit too many -- guides on how to install TWRP on OOS10. Here and here are some I found.
The gist of it is to boot to TWRP by running the fastboot flash boot twrp_file.img command, rebooting to recovery, then flashing the twrp zip file. And that's pretty much it.
PS In my case, I wasn't able to reboot to TWRP by using mauronofrio's twrp-3.3.1-14 version, and had to use his twrp-3.3.1-11 instead.
Click to expand...
Click to collapse
I have successfully installed TWRP and Magisk with the help of those links. Thank you again for your help.
quizzina said:
this can help
https://forum.xda-developers.com/showpost.php?p=80897567&postcount=332
Click to expand...
Click to collapse
Thank your for the in-depth explanation.
Just download oxygen updater and install 10.0.1 and be done with it
I ended up flashing TWRP over my boot slot (B) and now I just boot into TWRP. I have already installed TWRP on boot slot (a). I can't remember which version of oxygenOS I have installed and couldn't find a way to confirm. How can I fix this? Also want to update to latest version of oxygenOS and android. No data on phone yet. phone still connects to computer, adb sideloader and fastboot commands still work work. Thanks
Are you saying you did fastboot flash boot of the TWRP img? You should be doing fastboot boot TWRP img, then flash the TWRP installer zip.
You can get the OS back up and running by flashing the correct boot.img via fastboot. Or use one of the fastboot stock ROMs.
redpoint73 said:
Are you saying you did fastboot flash boot of the TWRP img? You should be doing fastboot boot TWRP img, then flash the TWRP installer zip.
You can get the OS back up and running by flashing the correct boot.img via fastboot. Or use one of the fastboot stock ROMs.
Click to expand...
Click to collapse
ya, I fastboot flash boot the TWRP img following this video youtu.be/3oSycujvmP8?t=296
I guess I'll start flashing boot images until I land on the correct OS version, thanks
doctor_whooves said:
ya, I fastboot flash boot the TWRP img following this video youtu.be/3oSycujvmP8?t=296
I guess I'll start flashing boot images until I land on the correct OS version, thanks
Click to expand...
Click to collapse
never follow youtube guides...
follow the guides that are up to date here on XDA.
Look for the TWRP thread and follow the steps there.
boot to fastboot
boot TWRP image
Flash TWRP installer
success
plasticarmyman said:
never follow youtube guides...
follow the guides that are up to date here on XDA.
Look for the TWRP thread and follow the steps there.
boot to fastboot
boot TWRP image
Flash TWRP installer
success
Click to expand...
Click to collapse
But to recover his phone, the OP will need the original boot.img from his OS version.
OP has already messed up the boot partition.
That has to be fixed first.
tech_head said:
But to recover his phone, the OP will need the original boot.img from his OS version.
OP has already messed up the boot partition.
That has to be fixed first.
Click to expand...
Click to collapse
in this case the best thing to do is just unbrick using MSM
plasticarmyman said:
in this case the best thing to do is just unbrick using MSM
Click to expand...
Click to collapse
Yes, I had to unbrick using msm. It worked. Was able to get phone rooted and stock recovery replaced with TWRP but it was a much bigger pain than I expected.
doctor_whooves said:
Yes, I had to unbrick using msm. It worked. Was able to get phone rooted and stock recovery replaced with TWRP but it was a much bigger pain than I expected.
Click to expand...
Click to collapse
Glad you got it recovered.
There is an application called "Partitions Backup".
It allows you to back up all the phone partitions. The one you really want to backup from now on is the boot_a and boot_b.
Since you are rooted when you do an upgrade, grab the boot_a and boot_b before installing Magisk after the install.
This allows you to go back to stock. After you back them up, copy them to a computer.
hey guys. Not able to flash oos through twrp.
getting "error flashing zip".
tech_head said:
Glad you got it recovered.
There is an application called "Partitions Backup".
It allows you to back up all the phone partitions. The one you really want to backup from now on is the boot_a and boot_b.
Since you are rooted when you do an upgrade, grab the boot_a and boot_b before installing Magisk after the install.
This allows you to go back to stock. After you back them up, copy them to a computer.
Click to expand...
Click to collapse
Doesn't TWRP back up everything including boot partitions?
Is there nothing that will take the entire internal storage and just make a 'bare metal' image of it for restoring.. the whole entire thing, byte for byte? If not, why doesn't this exist? It just seems so logical to me and would be so incredibly useful. Phone borked? No problem. Just re-image it form the archive you made. To me, that is what TWRP is all about, at least conceptually if not technically.