Hi,
I wiped system on my oneplus 6 and now when i try to flash TWRP i see
downloading 'boot.img'...
OKAY [ 0.570s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.595s
Click to expand...
Click to collapse
Some one can help me install system on my phone?
I think you must re-install all rom/file...
If i was you i wipe Data, Cache/system and them re.install rom, and before reboot, TWRP.
Someone confirm this please.
Mord0rr said:
I think you must re-install all rom/file...
If i was you i wipe Data, Cache/system and them re.install rom, and before reboot, TWRP.
Someone confirm this please.
Click to expand...
Click to collapse
I found a solution.
https://www.google.com/amp/s/forum....downloadtool-v4-0-international-t3903272/amp/
Msm will help you, did the same mistake. But it's going to downgrade to oos 5.x.x
Related
This started with a brand new Boost Mobile Moto G (XT1031).
It was taken right from the box and unlocked using oem unlock.
After the unlock it booted to the stock image then was powered off and booted to fastboot.
Once in fastboot TWRP 2.7.1.0 recovery was flashed.
When trying to boot into recovery it would only loop.
Tried to boot normally and it would only loop.
Flashed the device back to stock using all the available firmwares from sbf.droid-developers.org for Boost US and it still wont boot.
Tried other recovery images and the only one I was able to get working was Philz Touch 6.55.
Wiped and formated everything and rebooted the phone and it went straight to recovery.
Using Philz recovery tried to install CyanogenMod 11 and bool loop proceeded.
I took another working Moto G and flashed Philz recovery and made a back up onto a usb drive using an otg cable.
On the broken device tried to restore from the backup and it said it was completed but it ran way to fast and didn't seem to restore completely and failed to boot.
I've gone through every method of recovery i could find and nothing seems to be working
This phone is kicking my butt, any help would be greatly appreciated.
manicresin said:
This started with a brand new Boost Mobile Moto G (XT1031).
It was taken right from the box and unlocked using oem unlock.
After the unlock it booted to the stock image then was powered off and booted to fastboot.
Once in fastboot TWRP 2.7.1.0 recovery was flashed.
When trying to boot into recovery it would only loop.
Tried to boot normally and it would only loop.
Flashed the device back to stock using all the available firmwares from sbf.droid-developers.org for Boost US and it still wont boot.
Tried other recovery images and the only one I was able to get working was Philz Touch 6.55.
Wiped and formated everything and rebooted the phone and it went straight to recovery.
Using Philz recovery tried to install CyanogenMod 11 and bool loop proceeded.
I took another working Moto G and flashed Philz recovery and made a back up onto a usb drive using an otg cable.
On the broken device tried to restore from the backup and it said it was completed but it ran way to fast and didn't seem to restore completely and failed to boot.
I've gone through every method of recovery i could find and nothing seems to be working
This phone is kicking my butt, any help would be greatly appreciated.
Click to expand...
Click to collapse
What did you use to flash? fastboot or mfastboot?
280
oversleeper said:
What did you use to flash? fastboot or mfastboot?
Click to expand...
Click to collapse
I used mfastboot.
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Try to use the bootloader refresh tool, for someone worked.:good:
oversleeper said:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Try to use the bootloader refresh tool, for someone worked.:good:
Click to expand...
Click to collapse
I ran the bootloader refresh after modifying the bat file for the correct cpu.
The boot loader version is showing it was updated but the device is still not booting.
[EDIT] I did try to reflash the stock frimware and there where some erros i wasnt getting before
Code:
C:\falcon_boost_user_4.4.2>mfastboot.exe flash aboot emmc_appsboot.mbn
sending 'aboot' (512 KB)...
OKAY [ 0.051s]
writing 'aboot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.335s
Code:
C:\falcon_boost_user_4.4.2>mfastboot.exe flash motoboot motoboot.img
sending 'motoboot' (1940 KB)...
OKAY [ 0.111s]
writing 'motoboot'...
Motoboot: Preflash validation for tz
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.407s
On a whim I decided to try the retail firmware and was able to get the phone to boot to stock, but I tried to load TWRP again and it went back to the boot looping state.
I really don't understand what is wrong with this phone because this are for the company I work for and we have flash about a thousand this exact same way and have never ran into this issue.
I am going to try philz recovery to see if it cause the normal boot process to break and if not I try loading the a custom rom from there.
manicresin said:
I ran the bootloader refresh after modifying the bat file for the correct cpu.
The boot loader version is showing it was updated but the device is still not booting.
[EDIT] I did try to reflash the stock frimware and there where some erros i wasnt getting before
Code:
C:\falcon_boost_user_4.4.2>mfastboot.exe flash aboot emmc_appsboot.mbn
sending 'aboot' (512 KB)...
OKAY [ 0.051s]
writing 'aboot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.335s
Code:
C:\falcon_boost_user_4.4.2>mfastboot.exe flash motoboot motoboot.img
sending 'motoboot' (1940 KB)...
OKAY [ 0.111s]
writing 'motoboot'...
Motoboot: Preflash validation for tz
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.407s
Click to expand...
Click to collapse
Pretty normal, you got errors because you upgraded the bootloader to the last version, so you can't downgrade it. Now you can: try to flash the 4.4.2 stock boost version (without flashing gpt.bin and motoboot.img) or if doesn't work due to upgraded bootloader, just wait few days until the 4.4.4 firmware for boost will be downloadable. It's already realeased don't worry, look https://motorola-global-portal.custhelp.com/app/answers/indevice_detail/a_id/100754/p/30,6720,9050
EDIT: It's a boost version, it's pretty different... You can't flash whatever you want so easily... search for some guide, I can't help about boost version.
The boost 4.4.2 stock firmware failed but the retail version worked, I'm try that with philz recovery to see if I can get CM 11 to work. If that fails ill wait for the 4.4.4 boost firmware.
Thanks for the help
I know some people love TWRP and only use TWRP and some people only use ClockWorkMod Recovery, but since you've been trying with TWRP humour me and flash this, it's the latest ClockWorkMod Recovery 6.0.5.0 compiled from source.
Flash it then try to flash a CM nightly or something like that...clear cache and dalvik cache first then do a factory reset then flash.
ClockWorkMod Recovery 6.0.5.0
CodyF86 said:
I know some people love TWRP and only use TWRP and some people only use ClockWorkMod Recovery, but since you've been trying with TWRP humour me and flash this, it's the latest ClockWorkMod Recovery 6.0.5.0 compiled from source.
Flash it then try to flash a CM nightly or something like that...clear cache and dalvik cache first then do a factory reset then flash.
Click to expand...
Click to collapse
I downloaded your recovery image and flashed it, wiped everything and reset.
Installed cm-11-20140903-NIGHTLY-falcon from usbdisk, it said completed only after ~20 seconds but there where no errors.
Rebooted the device and the cyanogenmod animated boot logo was displayed.
The phone booted fine was is working, now to try and see if I can get my image loaded.
Thanks for the recommendation, I didn't think to try CWM since Philz recovery is based on it, but it failed to load CM 11.
Hi, I currently have a Nexus 5 that doesn't get past the flying dots screen. I tried everything and can't get anything to write on it! Nothing can be done succesfully through twrp or fastboot nor adb (i don't think) and I keep getting errors when trying to write or flash anything onto it. My warranty expired November and LG is going to charge me a lot to get my logic board. The thing is, my phone just randomly shut off after updating to lollipop and it just suddenly ended up this way. I didn't do anything physically wrong to the phone for this to occur. Is there anyone out there that is experienced who can take me through fixing my phone?!!
THANK YOU!!
-Brian
You mention TWRP, so I assume you're rooted with custom recovery. First, are you on the latest version of TWRP (2.8.6.1)? If not, flash that first.
Code:
fastboot flash recovery twrp-2.8.6.1-hammerhead.img
Next, follow this guide to freshly flash 5.1 again. This will not clear your data. Report back with the results.
Hi, sorry for the late response, I have been busy with exams and hadnt had the time to respond.
Whenever I try to flash anything onto the phone I get this message:
sending 'bootloader' <2577 KB>...
OKAY [ 0.296s]
writing 'bootloader'...
FAILED <remote: flash write failure>
finished. total time: 0.478s
Anytime I try to write something it constantly fails...
but for some reason writing recovery worked....
I can't tell what's wrong. Any thoughts?
Thank You
fightonb3 said:
Hi, sorry for the late response, I have been busy with exams and hadnt had the time to respond.
Whenever I try to flash anything onto the phone I get this message:
sending 'bootloader' <2577 KB>...
OKAY [ 0.296s]
writing 'bootloader'...
FAILED <remote: flash write failure>
finished. total time: 0.478s
Anytime I try to write something it constantly fails...
but for some reason writing recovery worked....
I can't tell what's wrong. Any thoughts?
Thank You
Click to expand...
Click to collapse
If you can get into recovery, do you have any errors while you wipe you're data?
i.adrian said:
If you can get into recovery, do you have any errors while you wipe you're data?
Click to expand...
Click to collapse
Yes gIget E: unable to mount '/data'
Did you try a factory reset?
SENT BY ENTANGLEMENT
fightonb3 said:
Yes gIget E: unable to mount '/data'
Click to expand...
Click to collapse
/data partition probably corrupted. There's a thread on general forum on how to try and fix it.
beekay201 said:
/data partition probably corrupted. There's a thread on general forum on how to try and fix it.
Click to expand...
Click to collapse
Could you link me to that?
fightonb3 said:
Could you link me to that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447 you could have Google it
Go and do a lot of reading
ttps://forum.xda-developers.com/oneplus-6/themes/magisk-aod-lockscreen-weather-mods-oos-t3847008
OPENBETA3 I installed this module magiskden to my oneplus 6 device installed in rom. I installed the system backup from twrp (bluspark v9.85) before installing.
When I set up the module and restart it, the screen was opened and closed, it was not possible to enter magisk manager.
Twrpye and I said 'restore system'. When the Restore process was completed, I said reboot system and went into fastboot mode.
I can't boot to the phone and write twrp. Fastboot is entering mode every time I restart.
I need to save my data. I don't want to flash fastboot rum.
I think there is no way without msmtool. I had the same problem when I tried to restore backup.
Kollachi said:
I think there is no way without msmtool. I had the same problem when I tried to restore backup.
Click to expand...
Click to collapse
fastboot boot twrp-3.2.1-0-enchilada.img
downloading 'boot.img'...
OKAY [ 0.579s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.609s
have you received such an error?
This isn't related to the module and seems to happen whenever I try to restore /boot or /system using TWRP. This is easily fixable by flashing the original boot.img
Is there any other solution than flashing the factory rum? At least if I twrp, I would back up internal storage.
DevrimSeven60 said:
fastboot boot twrp-3.2.1-0-enchilada.img
downloading 'boot.img'...
OKAY [ 0.579s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.609s
have you received such an error?
Click to expand...
Click to collapse
Yes I had the same error
Kollachi said:
Yes I had the same error
Click to expand...
Click to collapse
what is the solution? Bluspark twrp flash I do not get error, but twrpye can not enter, although it is completed.
DevrimSeven60 said:
Is there any other solution than flashing the factory rum? At least if I twrp, I would back up internal storage.
Click to expand...
Click to collapse
You can try flash the boot.img like paphonb said. I didn't knew that and used msmtool. But I saved my data before restoring in twrp so I didn't lose anything just a lil bit time
paphonb said:
This isn't related to the module and seems to happen whenever I try to restore /boot or /system using TWRP. This is easily fixable by flashing the original boot.img
Click to expand...
Click to collapse
open beta 3 i have downloaded full rom zip. Is there an img I can use in zip?
I need help with my op6.
I was using LOS (Unlocked+rooted) until now and I accidentally brick my device, now it's stuck at the bootloader screen.
It doesn't matter if I'm trying to get into the system/recovery.
These are the steps that I did to get here (as far as I can remember):
Wipe system, data, and cache.
Flash latest OxygenOS (9.0.4) using TWRP (blu_spark_v9.96).
Flash TWRP.
Reboot to TWRP
This time it didn't ask me to unlock it with my pattern, and I saw that all of my files in the sdcard folder are encrypted.
I pressed the other partition (A) manually and reboot to TWRP.
It got stuck on the recovery screen.
I flashed TWRP via ADB.
Now the A partitions files are encrypted, I tried to manually move to partition B again, but stuck at crash dump after reboot.
I flashed TWRP via ADB, this time to B.
And now it's stuck at the bootloader...
I can't use the MsmDownloadTool because it's the bootloader and not the crashdump screen, the tool doesn't recognize the device in order to unbrick it.
I even tried to use this guide, but it didn't help, the msmtool still don't recognize it.
I tried to flash TWRP via ADB and this is what I got:
Code:
C:\Users\Folio\Downloads>fastboot flash recovery twrp-3.2.3-x_blu_spark_v9.96_op
6.img
target reported max download size of 536870912 bytes
sending 'recovery' (28892 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.625s
I also tried these commands:
Code:
C:\Users\Folio\Downloads>fastboot getvar current-slot
current-slot: b
finished. total time: -0.000s
C:\Users\Folio\Downloads>fastboot flash boot_b twrp-3.2.3-x_blu_spark_v9.96_op6.
img
target reported max download size of 536870912 bytes
sending 'boot_b' (28892 KB)...
OKAY [ 0.617s]
writing 'boot_b'...
OKAY [ 0.140s]
finished. total time: 0.773s
C:\Users\Folio\Downloads>fastboot boot twrp-3.2.3-x_blu_spark_v9.96_op6.img
downloading 'boot.img'...
OKAY [ 0.608s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.640s
But it didn't really do anything...
I'm out of ideas, what should I do next?
just go use the unbrick tool ?
I've been in your situation a lot of times in the beginning when I started to know about A/B partitioning.
Just fastboot the stock rom found here and you will boot easily in OOS.. Although your internal will be formatted every time you do this.
By the way, when you go to OOS from any ROM, you will always have to format internal storage to make OOS boot. (The step you didnt do in mentioned steps)
Fastboot ROM - https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Blunts47 said:
just go use the unbrick tool ?
Click to expand...
Click to collapse
As I mentioned.
Yes, I have tried that already.
Joyarup said:
I've been in your situation a lot of times in the beginning when I started to know about A/B partitioning.
Just fastboot the stock rom found here and you will boot easily in OOS.. Although your internal will be formatted every time you do this.
By the way, when you go to OOS from any ROM, you will always have to format internal storage to make OOS boot. (The step you didnt do in mentioned steps)
Fastboot ROM - https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Click to expand...
Click to collapse
I never saw in any other guide that It's necessary to also wipe the internal storage.
The OP6 imaging prosses is even more agonizing than I thought it is. :crying:
I'll try the guide that you sent me and will update, thanks for that.
lyor said:
As I mentioned.
Yes, I have tried that already.
I never saw in any other guide that It's necessary to also wipe the internal storage.
The OP6 imaging prosses is even more agonizing than I thought it is. :crying:
I'll try the guide that you sent me and will update, thanks for that.
Click to expand...
Click to collapse
I agree with you, the A/B partitioning is just a pain in the back.
Try that guide, just let your phone boot into fastboot, plug in pc and run the batch file in the zip of the rom and let it proceed.
Joyarup said:
I agree with you, the A/B partitioning is just a pain in the back.
Try that guide, just let your phone boot into fastboot, plug in pc and run the batch file in the zip of the rom and let it proceed.
Click to expand...
Click to collapse
WOW, how is this guide is not more popular?
Anyhow, you just saved my as5 man, thank you!
lyor said:
WOW, how is this guide is not more popular?
Anyhow, you just saved my as5 man, thank you!
Click to expand...
Click to collapse
Haha, glad to be useful. I know right, fastbooting ROMs are not popular these days. Everyone just follows the unbrick tool..
Enjoy!!
btw, can I now move freely to any other ROM without touching (flashing) the stock ROM?
lyor said:
btw, can I now move freely to any other ROM without touching (flashing) the stock ROM?
Click to expand...
Click to collapse
Yes, if you are booted to OOS once, you can flash any ROMs now. But remember while flashing back the OOS, you will need to wipe internals.
Joyarup said:
Yes, if you are booted to OOS once, you can flash any ROMs now. But remember while flashing back the OOS, you will need to wipe internals.
Click to expand...
Click to collapse
Oh yes, one last thing.
Will I be able to install them without flashing TWRP every time after them (for both of the A/B slots)?
lyor said:
Oh yes, one last thing.
Will I be able to install them without flashing TWRP every time after them (for both of the A/B slots)?
Click to expand...
Click to collapse
Always flash ROM zip + Twrp
Then reboot to TWRP then flash gapps and magisk(if any).
And never change boot partition through twrp, it will brick you. It's kinda buggy...
I keep trying to flash t.w.r.p via adb but it keeps failing. I try orange and Peter but they don't work and make me get stuck in bootloop. Official 3.3.1 recovery flashes but then when I boot to recovery it only shows the teamwin logo and I have no options to do anything, then on reboot when I trying booting into recovery again it boots into stock recovery like I never even flashed it.
Can someone tell me what I'm doing wrong or tell me correct recovery to flash with this rom? It should be straight forward process to flash t.w.r.p, but I am having trouble for some reason. Thank you.
toyspeed said:
I keep trying to flash t.w.r.p via adb but it keeps failing. I try orange and Peter but they don't work and make me get stuck in bootloop. Official 3.3.1 recovery flashes but then when I boot to recovery it only shows the teamwin logo and I have no options to do anything, then on reboot when I trying booting into recovery again it boots into stock recovery like I never even flashed it.
Can someone tell me what I'm doing wrong or tell me correct recovery to flash with this rom? It should be straight forward process to flash t.w.r.p, but I am having trouble for some reason. Thank you.
Click to expand...
Click to collapse
What's the message that appears in ADB when you flash it?
toyspeed said:
I keep trying to flash t.w.r.p via adb but it keeps failing. I try orange and Peter but they don't work and make me get stuck in bootloop. Official 3.3.1 recovery flashes but then when I boot to recovery it only shows the teamwin logo and I have no options to do anything, then on reboot when I trying booting into recovery again it boots into stock recovery like I never even flashed it.
Can someone tell me what I'm doing wrong or tell me correct recovery to flash with this rom? It should be straight forward process to flash t.w.r.p, but I am having trouble for some reason. Thank you.
Click to expand...
Click to collapse
Did u unlocked the bootloader?
Sent from my Redmi Note 7 Pro using XDA Labs
Naveenthemi said:
What's the message that appears in ADB when you flash it?
Click to expand...
Click to collapse
Just usual message such as:
PS C:\platform-tools> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.112s]
writing 'recovery'...
OKAY [ 0.355s]
finished. total time: 2.474s
I tried with Black Project also, same story. I don't understand this, I just want to root but I can't!
toyspeed said:
Just usual message such as:
PS C:\platform-tools> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.112s]
writing 'recovery'...
OKAY [ 0.355s]
finished. total time: 2.474s
I tried with Black Project also, same story. I don't understand this, I just want to root but I can't!
Click to expand...
Click to collapse
Ok someone else who's facing the same problem fixed this by formatting the data partition.
But idk why don't you try reinstalling MIUI(Flashboot it through MiFlash) and then try again?
Naveenthemi said:
Ok someone else who's facing the same problem fixed this by formatting the data partition.
But idk why don't you try reinstalling MIUI(Flashboot it through MiFlash) and then try again?
Click to expand...
Click to collapse
Ok, thanks for advice I'll try formatting data partition. That's exactly what I've been doing, flashing MIUI through MiFlash everything perfect. Then I run into problems after I try flashing recovery so I can root, very weird but I will keep trying.
toyspeed said:
Ok, thanks for advice I'll try formatting data partition. That's exactly what I've been doing, flashing MIUI through MiFlash everything perfect. Then I run into problems after I try flashing recovery so I can root, very weird but I will keep trying.
Click to expand...
Click to collapse
Did it work?
Naveenthemi said:
Did it work?
Click to expand...
Click to collapse
I actually decided to flash Superior OS instead, loving it so far!