Hi All,
I flashed oreo to my Mate 9 today, all was well until I tried to root.
Now it won't boot, stuck in bootloop. I can get to Fastboot and TWRP Recovery.
Tried to reflash, but now no bootloop - just got fastboot and TWRP.
When in TWRP device is not showing up in ADB devices, so can't push anything.
Any ideas as to how to come back from this?
Thanks.
Things are worse now... it won't reboot to recovery. Can still get fastboot though.
When reboot to recovery it just sits on "your device is booting now..." and doesn't seem to progress. I have re-flashed TWRP via fastboot... but still the same.
Wallace44 said:
Hi All,
I flashed oreo to my Mate 9 today, all was well until I tried to root.
Now it won't boot, stuck in bootloop. I can get to Fastboot and TWRP Recovery.
Tried to reflash, but now no bootloop - just got fastboot and TWRP.
When in TWRP device is not showing up in ADB devices, so can't push anything.
Any ideas as to how to come back from this?
Thanks.
Click to expand...
Click to collapse
Device shows phone and FRP as unlocked.
I have extracted the oreo update using a Perl script i found on another thread. Flashing system, kernel, recovery_ramdisk has made no difference.
Anyone able to help please?
What root did u use magisk or su?
Why don't you use this method?
Its safe and no more side effects.
Then after you can root with magisk.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Thanks
[email protected]@n
Mate-10
Related
Hello, i've got a big problem:
i've tried to install 8.1 Oreo, but it asked for password, i've tried to format data and it showed me an error, i've tried to reboot recovery but it stuck on splash TWRP screen... And also fastboot mode from bootloader can't be launched - it just starting system which i can't access. I have a2017g btw.
Hoping for help and happy new year to everybody!
kingracer said:
Hello, i've got a big problem:
i've tried to install 8.1 Oreo, but it asked for password, i've tried to format data and it showed me an error, i've tried to reboot recovery but it stuck on splash TWRP screen... And also fastboot mode from bootloader can't be launched - it just starting system which i can't access. I have a2017g btw.
Hoping for help and happy new year to everybody!
Click to expand...
Click to collapse
uuhh.. MiFlash?
If you can get TWRP 3.2.1-0 to work, try to format data again. If it fails follow raystef66's method on how to get rid of the 5 second screen (you'd be doing it only to restore fastboot) then boot to fastboot and issue 'fastboot erase userdata'
Choose an username... said:
uuhh.. MiFlash?
If you can get TWRP 3.2.1-0 to work, try to format data again. If it fails follow raystef66's method on how to get rid of the 5 second screen (you'd be doing it only to restore fastboot) then boot to fastboot and issue 'fastboot erase userdata'
Click to expand...
Click to collapse
Where can i find that method? I've already got it figured out but i still can't install Oreo because after using the instruction I've had the same problem
kingracer said:
Where can i find that method? I've already got it figured out but i still can't install Oreo because after using the instruction I've had the same problem
Click to expand...
Click to collapse
On the guides section of course
FIXED, Just type this adb command when you are in recovery mode....
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
Click to expand...
Click to collapse
Hi guys, i have an issue....
Moto g5 plus XT1680 LATAM
I flashed with Flash Fire (security patch) in my moto g5 plus rooted with SuperSU systemless and BL unlocked, but i reboot phone and it starts on recovery TWRP, then, i tried for 3 times but keeps starting on recovery mode.
After that, i tried to power up phone on booloader and then select START And it works, it's the only way that i can start phone normally, or wait for recovery starts and select reboot in bootloader mode because if i select reboot system ... keeps starting on recovery mode.
So, if i dont use bootloader and Select START, phone into recovery mode.
PLEASE, help me i tried with fastboot cmd [fastboot oem fb_mode_clear] not works, wipe /cache doesn't work too, i dont want to flash stock firmware. Can i fix this with a cmd or flashing stock img like boot.img / bootloader.img or something?
Thanks guys. :good:
BunnyHoo said:
Hi guys, i have an issue....
Moto g5 plus XT1680 LATAM
I flashed with Flash Fire (security patch) in my moto g5 plus rooted with SuperSU systemless and BL unlocked, but i reboot phone and it starts on recovery TWRP, then, i tried for 3 times but keeps starting on recovery mode.
After that, i tried to power up phone on booloader and then select START And it works, it's the only way that i can start phone normally, or wait for recovery starts and select reboot in bootloader mode because if i select reboot system ... keeps starting on recovery mode.
So, if i dont use bootloader and Select START, phone into recovery mode.
PLEASE, help me i tried with fastboot cmd [fastboot oem fb_mode_clear] not works, wipe /cache doesn't work too, i dont want to flash stock firmware. Can i fix this with a cmd or flashing stock img like boot.img / bootloader.img or something?
Thanks guys. :good:
Click to expand...
Click to collapse
I have the same problem when i select factory mode on bootloader then the phone starts only...
Otherwise it boots into twrp recovery
I have the same problem. Only boots into system via bootloader.
Otherwise it boots into twrp recovery.
After successfully booting into system it told me "system update failed".
I guess its because the system update routine is to be flashed via stock recovery and therefore its booting into recovery until it is flashed? Just guessing, but if so could I just flash the update manually?
Thanks in Advance :good:
same here, ps. thanks for the tip of boatloader !!
bubo23 said:
same here, ps. thanks for the tip of boatloader !!
Click to expand...
Click to collapse
np, i still w8 for a solution!, i try some methods but not seems to work
Xt1687 here - same issue. Can I get confirmation that flashing the stock firmware fixes it?
Sorry if I'm wrong you cannot update when bootloader unlock ,have to wait some one make a fash zip so we can fash on twrp
Same here, I have to go to Mount then check System and then Reboot, Bootloader and finally Start. It's very annoying. I tried some ADB commands but nothing seemed to work.
Update: So I got annoyed enough by it to finally flash a different rom, wiped /data /system /cache and installed
Cosmic-OS 3.1 Universe but still can only boot via bootloader...
Any suggestions? Do I have to reformat the whole phone in bootloader via Computer?
Thanks in advance :good:
Finally found a fix, might not work for everyone though. Thanks to @aughtnaut:
https://forum.xda-developers.com/showpost.php?p=74109609&postcount=65
jcags said:
Finally found a fix, might not work for everyone though. Thanks to @aughtnaut:
https://forum.xda-developers.com/showpost.php?p=74109609&postcount=65
Click to expand...
Click to collapse
I'll try bro, thanks.:good:
jcags said:
Finally found a fix, might not work for everyone though. Thanks to @aughtnaut:
https://forum.xda-developers.com/showpost.php?p=74109609&postcount=65
Click to expand...
Click to collapse
IT WORKS!!!!, THANKS A LOT!.
Just TYPE FIRST CODE and see the magic!
It worked, thanks for the link!
Hello i have a probleme twrp in my moto g5 plus i unlock bootloader i install twrp but if i want to make a reboot into twrp didnt work . The one methode for reboot into twrp is reboot bootloader and press star , plz i need a solution for normal reboot
Just unlocked my bootloader using Tuliptool. When tried booting to bootloader to flash TWRP to recovery. It just restarted my phone. I also tried getting to the bootloader by using the ADB command ADB boot bootloader and it also just restarted my phone.
Do you guys have any idea on how to fix this?
Any assistance in this matter is greatly appreciated.
Edit: Figured it out. I had tried to flash TWRP using Tuliptool without having the TWRP img in the correct folder. At least that's what I think caused the problem.
I fixed it by reattempting to flash TWRP using Tuliptool this time with it in the correct spot.
Not sure, if I can delete thread or not... I'm a complete newb here ヽ(ヅ)ノ
my nexus 6p is not booting into rom, recovery (stock and custom).
i have a unlocked bootloader, flashed custom recovery(twrp) by fastboot but can't get in to twrp as i wanted to flash blod patch to use 4cores to work.
i tried flashing stock images of MM, Nougat, Oreo using platform tools by google but getting an error like see in the attachment:crying:.
i tried it with fastboot by manually entering commands it will flash but not use still bootlooping.
i tried toolkits like NRT & all in one toolkit by XDA member this toolkits can flash stock rom successfully but cant get boot into system, stock recovery.
help me with your answers. my status is "unlocked bootloader, fastboot working, can access bootloader but can't get into recovery from it".
getting couldn't parse partition size 0x when booting boot img through platform tools.
tell me if i did any mistake. Thank you.
You tried stock images. Does that include factory images? That erases and reflashes quite literally everything (bootloader, recovery, system, etc.)
Find them here for 6P: https://developers.google.com/android/images#angler
Santhosh Jangamgari said:
my nexus 6p is not booting into rom, recovery (stock and custom).
i have a unlocked bootloader, flashed custom recovery(twrp) by fastboot but can't get in to twrp as i wanted to flash blod patch to use 4cores to work.
i tried flashing stock images of MM, Nougat, Oreo using platform tools by google but getting an error like see in the attachment:crying:.
i tried it with fastboot by manually entering commands it will flash but not use still bootlooping.
i tried toolkits like NRT & all in one toolkit by XDA member this toolkits can flash stock rom successfully but cant get boot into system, stock recovery.
help me with your answers. my status is "unlocked bootloader, fastboot working, can access bootloader but can't get into recovery from it".
getting couldn't parse partition size 0x when booting boot img through platform tools.
tell me if i did any mistake. Thank you.
Click to expand...
Click to collapse
You didn't mention which custom recovery you flashed. Did you try the one in this thread? https://forum.xda-developers.com/t/...-death-blod-workaround-flashable-zip.3819515/
If you did and you still can't get into it, your device is likely dead from the BLOD. But to make sure you have the BLOD, flash the latest factory image first (Dec. 2018) with the latest platform tools to see if it boots... https://developer.android.com/studio/releases/platform-tools
Lughnasadh said:
You didn't mention which custom recovery you flashed. Did you try the one in this thread? https://forum.xda-developers.com/t/...-death-blod-workaround-flashable-zip.3819515/
If you did and you still can't get into it, your device is likely dead from the BLOD. But to make sure you have the BLOD, flash the latest factory image first (Dec. 2018) with the latest platform tools to see if it boots... https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
firstly i already cant boot into stock recovery from my bootloader i'm on stock os 8.1.
and now i've flashed twrp for angler from twrp website but cant boot into custom recovery too.
now i've flashed twrp image of 4cores but still can't get into recovery.
so what's the problem of this phone if my mobile cant get even into twrp i can't do blod patch if we think my device is suffering from blod issue.
do you think it may be the problem of hardware like ram,emmc, or the SD 810?
Santhosh Jangamgari said:
firstly i already cant boot into stock recovery from my bootloader i'm on stock os 8.1.
and now i've flashed twrp for angler from twrp website but cant boot into custom recovery too.
now i've flashed twrp image of 4cores but still can't get into recovery.
so what's the problem of this phone if my mobile cant get even into twrp i can't do blod patch if we think my device is suffering from blod issue.
do you think it may be the problem of hardware like ram,emmc, or the SD 810?
Click to expand...
Click to collapse
As I said in my previous post, if you can't boot into the 4core custom recovery, your device is likely dead because of the BLOD, unfortunately. If you are on stock with nothing else on your phone that might be preventing you from booting (e.g. mods, Substratum overlays, etc.) there's not much else you can do.
Is your device recognized in fastboot?
marianodelfino said:
Is your device recognized in fastboot?
Click to expand...
Click to collapse
Hi, I am havin same problem as the user above....I am on stock 7.1.2 right now. Unable to boot into TWRP, i flashed twrp-3.2.1-0-fbe-4core-angler.img and then entered recovery from bootloader screen. nothing! i also tried to do a temporary boot to my recovery via fastboot command. didn't work! I dont think my phone is that dead...but I don't see why it isnt booting into twrp...i did the flash all of stock firmware from the Google website. Any assistance? Currently I have a Pixel 2 thats not working, so i thought I would try to revive the 6P, but no luck so far.
DaKoin said:
Hi, I am havin same problem as the user above....I am on stock 7.1.2 right now. Unable to boot into TWRP, i flashed twrp-3.2.1-0-fbe-4core-angler.img and then entered recovery from bootloader screen. nothing! i also tried to do a temporary boot to my recovery via fastboot command. didn't work! I dont think my phone is that dead...but I don't see why it isnt booting into twrp...i did the flash all of stock firmware from the Google website. Any assistance? Currently I have a Pixel 2 thats not working, so i thought I would try to revive the 6P, but no luck so far.
Click to expand...
Click to collapse
thanks but no assistance required as i have sold it to another nexus 6p user for using it's spare parts.
Attempted to update from the latest stable 10.3.12 to 11 by flashing the full OTA zip in TWRP.
Install failed and phone locked up.
Attempting to boot to recovery or system results in Qualcomm Crashdump Mode.
I can get to Fastboot, but I'm not sure if I should try flashing twrp.img or pull boot.img from the OTA or what.
Anyone have any suggestions?
SMcC2 said:
Attempted to update from the latest stable 10.3.12 to 11 by flashing the full OTA zip in TWRP.
Install failed and phone locked up.
Attempting to boot to recovery or system results in Qualcomm Crashdump Mode.
I can get to Fastboot, but I'm not sure if I should try flashing twrp.img or pull boot.img from the OTA or what.
Anyone have any suggestions?
Click to expand...
Click to collapse
An attempt to flash TWRP and reflashing should go.
Hi,
I'm having kinda same issue.
I'm on stable A11 oneplus 6t,
i'm trying to boot into twrp in order to install new recovery and root with magisk.
when fasboot boot twrp.img i'm getting a qualcomm crashdump.
tried different twrp img's with no success..
maybe someone figure it out?
thanks
BenoMosko said:
Hi,
I'm having kinda same issue.
I'm on stable A11 oneplus 6t,
i'm trying to boot into twrp in order to install new recovery and root with magisk.
when fasboot boot twrp.img i'm getting a qualcomm crashdump.
tried different twrp img's with no success..
maybe someone figure it out?
thanks
Click to expand...
Click to collapse
I did not have time to wait so before bed I just reset everything.
I ended up using the MSM tool located here:
The Complete Guide to Unbrick OnePlus 6/6T from a Hard-Brick using MSMDownload Tool
Unlocked bootloader, installed TWRP & Magisk, installed A11 zip, everything is working again now.
Good luck!
BenoMosko said:
Hi,
I'm having kinda same issue.
I'm on stable A11 oneplus 6t,
i'm trying to boot into twrp in order to install new recovery and root with magisk.
when fasboot boot twrp.img i'm getting a qualcomm crashdump.
tried different twrp img's with no success..
maybe someone figure it out?
thanks
Click to expand...
Click to collapse
Hey, I'm having the same issue. Did you end up figuring out how to solve this?
Artificial_Intelligence said:
Hey, I'm having the same issue. Did you end up figuring out how to solve this?
Click to expand...
Click to collapse
Flash temporary recovery first ( lineage recovery ) then from fastboot.. boot into recovery.
You will see lineage recovery.
Select apply update - > update from adb ....
Then "adb sideload <twrp image>.img...
(probably it ask to verify choose yes)
Go back select advanced restart ( not sure the right word ) -> reboot to recovery.
Then you will have twrp installed.
If you only want to root why not flash magiskpatched image there no need TWRP just to root.
s.seila said:
Flash temporary recovery first ( lineage recovery ) then from fastboot.. boot into recovery.
You will see lineage recovery.
Select apply update - > update from adb ....
Then "adb sideload <twrp image>.img...
(probably it ask to verify choose yes)
Go back select advanced restart ( not sure the right word ) -> reboot to recovery.
Then you will have twrp installed.
If you only want to root why not flash magiskpatched image there no need TWRP just to root.
Click to expand...
Click to collapse
Hm but how would I install lineage recovery? Flashing recovery through fastboot doesn't work on the new devices anymore right?
I also tried booting lineage recovery without flashing but that also didn't work (although it didn't get stuck on crashdump but booted into the regular OS instead).
I did notice that it seems to be related to OOS 11 firmware. On 10 booting into TWRP works just fine and as soon as I upgrade to 11 it stops working (maybe this means it's fixable?). What I used as a workaround for now is to have 10 firmware in one slot, upgrade other slot to 11 and flash TWRP to both slots from the 10 slot. Seems to work so far but is not ideal IMO. I'm not a developer sadly but maybe someone smarter than me will come up with a solution.
What do you mean by "new device"?? New OOS version right??
I use this method all the time with oos 11.x.x.x.x to install TWRP so i can install Custom ROM later.
no need to go to oos 10 you can flash it from newest oos11.
---------------------------------------------------------------------------------------------------------------
First boot into fastboot mode.
to install lineage recovery
fastboot flash boot <lineage recovery image>.img
download from here https://download.lineageos.org/fajita
menualy select and boot to recovery. It will boot to lineage recovery.
lmao it appear in two posts. deleted 1.