Hi,
I backed up my kernel using TWRP by fastbooting into the Pixel 3 blueline TWRP image. When I then tried to reboot the phone I get following error:
"Android Recovery
google/blueline/blueline
9/PI/gucheng0719045
userdebug/dev-keys
...
Can't load Android system."
I tried both options "try again" and "factory data reset" but both brought me back to this screen. I also tried booting into recovery mode and doing "Wipe data factory reset"; this also brought me back to the above error.
Finally, I tried installing OTA using sideload but the signature verification failed since I have an unlocked bootloader and had custom ROM running on the device.
How can I get the device into a usable state again? I don't care about keeping the data. Also note that I still have the TWRP kernel backup saved.
gardeimasei said:
Hi,
I backed up my kernel using TWRP by fastbooting into the Pixel 3 blueline TWRP image. When I then tried to reboot the phone I get following error:
"Android Recovery
google/blueline/blueline
9/PI/gucheng0719045
userdebug/dev-keys
...
Can't load Android system."
I tried both options "try again" and "factory data reset" but both brought me back to this screen. I also tried booting into recovery mode and doing "Wipe data factory reset"; this also brought me back to the above error.
Finally, I tried installing OTA using sideload but the signature verification failed since I have an unlocked bootloader and had custom ROM running on the device.
How can I get the device into a usable state again? I don't care about keeping the data. Also note that I still have the TWRP kernel backup saved.
Click to expand...
Click to collapse
Flash factory image with fastboot.
wangdaning said:
Flash factory image with fastboot.
Click to expand...
Click to collapse
Where can I get the factory image? And how do I use fastboot to flash the device? Like so?:
Code:
fastboot boot <image name>.img
I am able to fastboot boot into the blueline TWRP image. Selecting the "Fix bootloop" didn't work however
So I tried doing:
Code:
fastboot flash boot bootloader-blueline-b1c1-0.1-5578427.img
I got following error though:
Sending 'boot_a' (8493 KB) OKAY [ 0.130s]
Writing 'boot_a' (bootloader) Flashing Pack version b1c1-0.1-5578427
FAILED (remote: '(boot_a) No such partition')
fastboot: error: Command failed
Any suggestions on how to proceed?
gardeimasei said:
So I tried doing:
Code:
fastboot flash boot bootloader-blueline-b1c1-0.1-5578427.img
I got following error though:
Sending 'boot_a' (8493 KB) OKAY [ 0.130s]
Writing 'boot_a' (bootloader) Flashing Pack version b1c1-0.1-5578427
FAILED (remote: '(boot_a) No such partition')
fastboot: error: Command failed
Any suggestions on how to proceed?
Click to expand...
Click to collapse
That command flashes only the boot loader, not the factory image. The factory image and instructions for flashing are at https://developers.google.com/android/images
What android version were you on when you started? TWRP does not run on a Pixel 3 with Android 10.
Also, the boot partition is not the bootloader partition. Just run the flash-all script that google provides with the factory image download.
dcarvil said:
That command flashes only the boot loader, not the factory image. The factory image and instructions for flashing are at https://developers.google.com/android/images
What android version were you on when you started? TWRP does not run on a Pixel 3 with Android 10.
Click to expand...
Click to collapse
I was using Android 9. I tried running the flash-all script (i.e., follow the official instructions) but the fastboot commands would hang. Maybe I just didn't wait for long enough.
I wiped system,data,cache using TWRP following some online guide and now I can't boot into recovery mode. I can get into the bootloader menu though. When I try to boot into TWRP using:
Code:
fastboot boot twrp-3.3.0-0-blueline.img
I get the following error on the PC: Booting FAILED (remote: 'Error calling AvbLoadAndVerifyBootImages Load Error')
When I try to enter recovery mode the screen turns black indefinitely.
I still have the TWRP .win files from my backup on my PC. Is there a way out of this?
EDIT:
Weirdly, after trying the flash-all.sh script again it worked basically instantly. Possibly it took so long the first time i ran it because it was wiping data (which i then did manually).
Was able to get the factory image on there. Thanks a lot!
Related
Need some help here as I am in a bit of a bind. Was on 5.1.11 and attempted to update to stable Pie. Used Blu_Spark TWRP v2 and upon rebooting got the error about device being corrupted. Continued booting but was stuck on boot animation. Rebooted to TWRP and attempted to restore nandroid. Upon restoring and reboot, boots immediately to TWRP. Attempt to change slots (which might have been an error on my part) and rebooted. Now stuck in fastboot! I attempt to flash TWRP.img via fastboot and get the following error:
Code:
PS D:\OnePlus 6\adb> fastboot boot twrp-3.2.1-0-enchilada_official.img
downloading 'boot.img'...
OKAY [ 0.628s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.650s
If I try and switch to slot _b, I get the following error:
Code:
PS D:\OnePlus 6\adb> fastboot --set-active=_b
C:\Android\fastboot.exe: unknown option -- set-active=_b
PS D:\OnePlus 6\adb>
At the moment, my phone is bricked, so any help is GREATLY appreciated.
Thanks!!!!
https://www.androidfilehost.com/?fid=746163614322268882
Tool
https://www.androidfilehost.com/?fid=889964283620777981
Qualcomm drivers
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Watch video on clicking 5T in thread
@azsl1326
I had the same, fixed it using this: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Choose the Andriod PIE fastboot rom.
After that you can boot into PIE again, and if you want to go back to Oreo, use this Rollback procedure
https://www.theandroidsoul.com/rollback-oneplus-6-from-android-pie-to-android-oreo/
PS: You will lose ALL your data and Internal files
My Honor View10 is stuck at 'Your device is booting now', cannot enter recovery. I tried rectifying my twrp that couldn't unmount anything and wiped up almost everything, but ended up with a boot loop.
Now my device is stuck at 'Your device has been unlocked and can't be trusted. Your device is booting now' screen. I tried using the dload method to restore everything back but the device won't go past this screen.
I tried flashing it using fastboot mode by flashing system, ramdisk and what not, did get a success every time, still, the device won't go past this.
I need genuine help on this, please. Anyone? @2WildFirE? @Einwod? @shashank1320 @oreopie
All this perhaps happened because I tried changing the file system of data and system from twrp.
ankan1993 said:
My Honor View10 is stuck at 'Your device is booting now', cannot enter recovery. I tried rectifying my twrp that couldn't unmount anything and wiped up almost everything, but ended up with a boot loop.
Now my device is stuck at 'Your device has been unlocked and can't be trusted. Your device is booting now' screen. I tried using the dload method to restore everything back but the device won't go past this screen.
I tried flashing it using fastboot mode by flashing system, ramdisk and what not, did get a success every time, still, the device won't go past this.
I need genuine help on this, please. Anyone? @2WildFirE? @Einwod? @[email protected]
All this perhaps happened because I tried changing the file system of data and system from twrp.
Click to expand...
Click to collapse
Why you tried changing filesystem on data?
Twrp isn't ready for pie ? atm
Flash stock recovery and erecovery, then boot to erecovery and restore from there
2WildFirE said:
Why you tried changing filesystem on data?
Twrp isn't ready for pie ? atm
Flash stock recovery and erecovery, then boot to erecovery and restore from there
Click to expand...
Click to collapse
Because custom recovery wouldn't mount anything.
Had no idea that twrp isn't ready for pie.
For both stock and ereccovery, do I use ramdisk_recovery command?
2WildFirE said:
Flash stock recovery and erecovery, then boot to erecovery and restore from there
Click to expand...
Click to collapse
How exactly would one go about this?
fastboot flash erecovery_ramdisk ERECOVERY_RAMDI.img for example only results in FAILED (remote: 'Command not allowed').
Bootloader is unlocked.
If I'm right, try fastboot flash erecovery erecovery.img
2WildFirE said:
If I'm right, try fastboot flash erecovery erecovery.img
Click to expand...
Click to collapse
Sadly there is no erecovery.img and if i try to flash either of the many erecovery files into what i assume would be their respective partitions i get the same error.
Which i thought was a good sign because that might have meant that i couldn't have ****ed them up. But maybe it isn't.
OK try erecovery ramdisk and erecovery kernel to flash
PHP:
fastboot flash erecovery_kernel ERECOVERY_kerne.img
Sending 'erecovery_kernel' (24576 KB) OKAY [ 0.587s]
Writing 'erecovery_kernel' FAILED (remote: 'Command not allowed')
Finished. Total time: 0.614s
for example, the result is always the same.
2WildFirE said:
Why you tried changing filesystem on data?
Twrp isn't ready for pie ? atm
Flash stock recovery and erecovery, then boot to erecovery and restore from there
Click to expand...
Click to collapse
UPDATE: When I reboot the smartphone it displays "Data partition was damaged seriously! and you are recommended to format it to recover your phone".
Smartphone works, but even after a factory reset it still displays that message when it boots up it gets stuck at 'Booting up'.
What can I do @2WildFirE?
180190 said:
PHP:
fastboot flash erecovery_kernel ERECOVERY_kerne.img
Sending 'erecovery_kernel' (24576 KB) OKAY [ 0.587s]
Writing 'erecovery_kernel' FAILED (remote: 'Command not allowed')
Finished. Total time: 0.614s
for example, the result is always the same.
Click to expand...
Click to collapse
Because this is not the right command to give. I am not sure what the right command would be though.
Okay, so I have recovered my phone after spending a sleepless night working on it.
Tried several combinations to see this resolved.
But, what really worked out for me was that I discharged my device twice and kept trying flashing stock rom and several relative recoveries.
After flashing stock recovery I discharged my device. Once it came back, it took me to erecovery.
From there, I started downloading the file from the recovery and did a reboot after the installation.
My Honor is working fine now.
ankan1993 said:
But, what really worked out for me was that I discharged my device twice and kept trying flashing stock rom and several relative recoveries.
After flashing stock recovery I discharged my device.
Click to expand...
Click to collapse
What exactly have you done?
Sinerty said:
What exactly have you done?
Click to expand...
Click to collapse
Flashed the 9.0 full ota files several times, flashed full otas of 8.0. Flashed a random recovery from an older ota. I then discharged my device as I was totally out of options. When I put it on charge it turned back on and after few minutes took me to erecovery.
And now I cannot root my device as twrp isn't there for pie yet. Honor sucks.
Thread closed since it's a duplicate.
Please read here: https://forum.xda-developers.com/honor-view-10/help/honor-view10-stuck-device-booting-enter-t3889376
Hello guys I need some help. I'm stuck in fastboot mode with no recovery or OS too l, let me retrace my steps.
I had my px3 rooted on stock but I was bored with stock and tried to flash bootleggers rom and followed instructions to wipe "everything" but internal storage, so I did including storage under internal storage and flashed the ROM and twrp with it. After it just rebooted back to recovery every time I tried normal boot. (I'm assuming I F'd up by wiping storage). So I googled what to do about looping recovery and one suggestion was to factory reset so I did; I can no longer access recovery. I've tried flashing factory image, flashing the twrp zip, trying to boot straight to twrp, I can't get to adb sideload and it says "no valid slot to boot" on fastboot screen any suggestions?
Got another on fastboot, "error booting boot.img"
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
fury683 said:
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
Click to expand...
Click to collapse
Yes it does and I've got everything from twrp .zip and .IMG, factory images and ota zip.
I did make progress just now and switched to slot B and got TWRP to show up:laugh: might just sideload OTA and pretend this never happened
Update, adb sideload taking too long to start
wergrun said:
Yes it does and I've got everything from twrp .zip and .IMG, factory images and ota zip.
I did make progress just now and switched to slot B and got TWRP to show up:laugh: might just sideload OTA and pretend this never happened
Update, adb sideload taking too long to start
Click to expand...
Click to collapse
You need to get back to fastboot, and run the flash all bat file from the full factory image.
TonikJDK said:
You need to get back to fastboot, and run the flash all bat file from the full factory image.
Click to expand...
Click to collapse
I tried that but I keeps giving me an error, I'll post it when I get the chance
Problem SOLVED! used video by MaowDroid "Pixel 2 (XL): Un-root and return to stock using factory images"
fury683 said:
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
Click to expand...
Click to collapse
I have the same issue, except my computer will not recognize the device in fastboot. I tried two different computers, Windows 10 and laptop running Linux.
wergrun said:
Problem SOLVED! used video by MaowDroid "Pixel 2 (XL): Un-root and return to stock using factory images"
Click to expand...
Click to collapse
Followed the video, but I get an error:
'FAILED (remote: Failed to write to partition Not Found)'
I've tried: bootloader, bootloader_a, bootloader_b and bootloader_other and get the same error.
I'm stuck....
SS823 said:
Followed the video, but I get an error:
'FAILED (remote: Failed to write to partition Not Found)'
I've tried: bootloader, bootloader_a, bootloader_b and bootloader_other and get the same error.
I'm stuck....
Click to expand...
Click to collapse
I did get that too but it was because I forgot to put a space after "bootloader_a ", are you Stuck at around the 9 minute steps?
Yes, right around the end at 9 minutes. Everything works fine - bootloader, radio, etc. When I get to the end of the img zip file I get this message:
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.360s
I am at a loss.
Dear community. I screwed up.
I purchased my new OP7P and in all my excitement, logically, the first thing I went to do was to unlock the bootloader, install TWRP and root it, which I did successfully because I am pretty familiar with this on multiple phones. Long story short, here's what I did, and where my problem lies:
1. Went to install the Havoc Custom ROM by following their installation instructions, went ahead and booted to TWRP recovery
2. As instructed, wiped dalvik and /data
3. Flashed Havoc ROM and here is the part where I was supposed to flash TWRP installer
4. Forgot to reflash TWRP installer and rebooted to the now nonexisting recovery. - getting the dead android icon with the message "NO COMMAND"
5. After holding VOLUP + POWER managed to turn it off and then turn it on again with just POWER to be greeted with a message warning me that I am in a bootloop
and that I have two options; to try again or to "reset to factory settings", which I did, which booted me into the HavocOS.
The main problem here is that for some reason whenever I try to repeat the TWRP installation process using fastboot, by entering "fastboot boot twrp.img", it gives me the following error:
downloading 'boot.img'...
OKAY [ 1.340s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.343s
I have tried this on both Linux & Windows, same deal. The TWRP website has mentioned that if this happens I need root, but how do I root my phone without TWRP or "fastboot boot", and how do I install TWRP on the OP7P without livebooting TWRP?
Any help at all is truly appreciated. Thanks guys.
Download the MSM tool here and restore your phone. I've never used it but it gets everyone out of a brick.
I've used this tool a few times and it has gotten me out of a jam, just be sure to download the correct version for your phone. AFA your fastboot error, I got that until I let the OTA update to 9.5.11, then it worked again. https://forum.xda-developers.com/oneplus-7-pro/development/tool-tool-one-driversunlocktwrpfactory-t3930862
x3lade said:
The main problem here is that for some reason whenever I try to repeat the TWRP installation process using fastboot, by entering "fastboot boot twrp.img", it gives me the following error:
downloading 'boot.img'...
OKAY [ 1.340s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.343s
Click to expand...
Click to collapse
Try to fastboot boot the TWRP build -70 from here: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
It fixes the problem with "fastboot boot" not working on the official Android Q update. Not sure why that would apply to your case (custom ROM after already successfully installing TWRP). But it's very easy to try, and certainly can't hurt. And the error message you are getting is exactly the same as the official Android Q problem.
I wiped my OS and was having issues installing a custom ROM through TWRP. My phone rebooted and now I'm stuck in the bootloader and unable to get back into TWRP. I've tried using fastboot, but that also fails:
Code:
~\Downloads\TWRP>fastboot boot twrp-3.5.2_9-0-enchilada.img
Sending 'boot.img' (32604 KB) OKAY [ 0.823s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
Is there some way I can recover (even if back to stock), or am I screwed?
Thanks
zodac01 said:
I wiped my OS and was having issues installing a custom ROM through TWRP. My phone rebooted and now I'm stuck in the bootloader and unable to get back into TWRP. I've tried using fastboot, but that also fails:
Code:
~\Downloads\TWRP>fastboot boot twrp-3.5.2_9-0-enchilada.img
Sending 'boot.img' (32604 KB) OKAY [ 0.823s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
Is there some way I can recover (even if back to stock), or am I screwed?
Thanks
Click to expand...
Click to collapse
You are not screwed,2 choices you have-flash fastboot stock Rom or use MSM tool,for me personally i always use fastboot roms.Good luck
zodac01 said:
I wiped my OS and was having issues installing a custom ROM through TWRP. My phone rebooted and now I'm stuck in the bootloader and unable to get back into TWRP. I've tried using fastboot, but that also fails:
Code:
~\Downloads\TWRP>fastboot boot twrp-3.5.2_9-0-enchilada.img
Sending 'boot.img' (32604 KB) OKAY [ 0.823s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
Is there some way I can recover (even if back to stock), or am I screwed?
Thanks
Click to expand...
Click to collapse
You can revive any ROM mate. All you need is patience and a small knowledge in debugging the error.
If you are stuck on Bootloader. Try flashing rom on both slots from bootloader directly
Below link has process to do so
[ROM][STOCK][FASTBOOT][OP6] Stock Fastboot ROMs for OnePlus 6
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via stock recovery (with twrp is possible but not recommended). The updates will be done on the slot not used for example...
forum.xda-developers.com
If you can boot to recovery, try flashing roms directly by downloading stock roms. If you get stuck, try postng error message with screenshot using another mobile.