So I wanted to try LOS 15.1 I found from this link and I flashed B32 modem and bootloader but it got stuck in the first boot animation (waited for 30 mins). So I tried going back to LOS 14, I flashed B15 modem and bootloader but the same thing is happening, stuck in the boot animation. Same thing if I try to restore from nandroid backup or clean flash of the ROM. Any ideas what to do?
Nicz14 said:
So I wanted to try LOS 15.1 I found from this link and I flashed B32 modem and bootloader but it got stuck in the first boot animation (waited for 30 mins). So I tried going back to LOS 14, I flashed B15 modem and bootloader but the same thing is happening, stuck in the boot animation. Same thing if I try to restore from nandroid backup or clean flash of the ROM. Any ideas what to do?
Click to expand...
Click to collapse
Which twrp are you using?
Sent from my ZTE A2017U using Tapatalk
lafester said:
Which twrp are you using?
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I'm was usingthe latest, TWRP 3.2.1-0. I got out of this issue by restoring full EDL and now looking into how to flash twrp with unlocked bootloader.
Nicz14 said:
I'm was usingthe latest, TWRP 3.2.1-0. I got out of this issue by restoring full EDL and now looking into how to flash twrp with unlocked bootloader.
Click to expand...
Click to collapse
Easiest way is to use the new edl tool.
Sent from my ZTE A2017U using Tapatalk
Related
I was on the last beta n4f26t, and flash TWRP successfully, then went to flash superSU from twrp, this when wrong and everything goes downhill from here. I tried flashing back the last update, in it's entirety following the Heisenberg guide for returning to stock didn't work, tried flashing twrp again still can't get into recovery (just boot loops) I tried a previous update NMF26F and got to the dead android recovery screen but when I tried to flash back the OTA nothing happened and went back to bootloop on reboot. I've used the nexus root kit and still nothing. What can I do to fix this? I've honestly looked up every resource I could think of before posting this here. really hoping I didn't perma brick my 6P
maddmarkk said:
I was on the last beta n4f26t, and flash TWRP successfully, then went to flash superSU from twrp, this when wrong and everything goes downhill from here. I tried flashing back the last update, in it's entirety following the Heisenberg guide for returning to stock didn't work, tried flashing twrp again still can't get into recovery (just boot loops) I tried a previous update NMF26F and got to the dead android recovery screen but when I tried to flash back the OTA nothing happened and went back to bootloop on reboot. I've used the nexus root kit and still nothing. What can I do to fix this? I've honestly looked up every resource I could think of before posting this here. really hoping I didn't perma brick my 6P
Click to expand...
Click to collapse
Edit I was on NPG47I the lastest beta update not n4f26t
Hello... So now you only have access to the bootloader Or bootloader and stock recovery?
If your bootloader is unlocked, you can try:
fastboot erase cache
fastboot format userdata
Of course it will wipe your internal storage...
maddmarkk said:
Edit I was on NPG47I the lastest beta update not n4f26t
Click to expand...
Click to collapse
I would concentrate on trying to get a working recovery first. Almost everyone who lost recovery mode never got their phone back- classic BLOD. First try fastboot FORMATTING recovery and then both fastboot flash twrp, and then fastboot boot twrp. If you can get a working recovery there may be hope. If you can never boot to recovery mode, I think you are done. From your bootloader screen, what is your bl version?
v12xke said:
I would concentrate on trying to get a working recovery first. Almost everyone who lost recovery mode never got their phone back- classic BLOD. First try fastboot FORMATTING recovery and then both fastboot flash twrp, and then fastboot boot twrp. If you can get a working recovery there may be hope. If you can never boot to recovery mode, I think you are done. From your bootloader screen, what is your bl version?
Click to expand...
Click to collapse
just updated it to 3.67 from the 7.1.2 beta image
maddmarkk said:
just updated it to 3.67 from the 7.1.2 beta image
Click to expand...
Click to collapse
Yes, but is that what is shown on your bootloader screen? How did you flash it? With flash-all.bat? Which 7.1.2 image did you flash and how did you do it?
v12xke said:
Yes, but is that what is shown on your bootloader screen? How did you flash it? With flash-all.bat? Which 7.1.2 image did you flash and how did you do it?
Click to expand...
Click to collapse
BL: angler-03.6.7
Baseband: angler-3.81
I see all normal BL options and I flashed it with the nexus root kit and used https://developer.android.com/preview/download-712.html this image
I know with older versions of TWRP there was a problem with the EFS partition that contains the IMEI info. What version of twrp are you using??? I thought I bricked my Nexus 6p after restoring a backup but it was actually just me screwing up my EFS partition. The newer versions of twrp (i think 3.0.3 and up) fixed this problem. Still though, if it is that, and you flash a new twrp version it won't fix your problem. If you have the time search through the forum for the EFS partition fix. I don't know the commands off the top of my head but I know this helped a lot of people. Worth a shot.
maddmarkk said:
BL: angler-03.6.7
Baseband: angler-3.81
I see all normal BL options and I flashed it with the nexus root kit and used https://developer.android.com/preview/download-712.html this image
Click to expand...
Click to collapse
OK, but when you try to boot to recovery, it bootloops? Never goes to recovery? Try the steps above to successfully flash the recovery partition using fastboot. I suppose you can use NRT, but download the latest version of TWRP and try both flashing and booting the twrp.img.
same boat
anxious to hear results: I can't get to recovery and am bootlooping - tried a bunch of things using Nexus Root Toolkit . Curiously enough earlier when I was trying to flash an older version or ressurection remix, even my TWRP would bootloop so I couldn't flash anything without it quitting - anyone ever hear of that happening?
mikeygeer said:
anxious to hear results: I can't get to recovery and am bootlooping - tried a bunch of things using Nexus Root Toolkit . Curiously enough earlier when I was trying to flash an older version or ressurection remix, even my TWRP would bootloop so I couldn't flash anything without it quitting - anyone ever hear of that happening?
Click to expand...
Click to collapse
Hello... Try looking here: https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
v12xke said:
OK, but when you try to boot to recovery, it bootloops? Never goes to recovery? Try the steps above to successfully flash the recovery partition using fastboot. I suppose you can use NRT, but download the latest version of TWRP and try both flashing and booting the twrp.img.
Click to expand...
Click to collapse
I have flashed TWRP 3.1 and I can not boot into recovery, I flashed it manually with fastboot flash recovery "image"
maddmarkk said:
I have flashed TWRP 3.1 and I can not boot into recovery, I flashed it manually with fastboot flash recovery "image"
Click to expand...
Click to collapse
Hey... Did you try to boot TWRP?
From bootloader: fastboot boot twrp.img
If this fails and you only have access to the bootloader, i think you are SOL.
Good luck...
5.1 said:
Hey... Did you try to boot TWRP?
From bootloader: fastboot boot twrp.img
If this fails and you only have access to the bootloader, i think you are SOL.
Good luck...
Click to expand...
Click to collapse
you meant do this in the fastboot CMD right? if so then it just boot loops :'C
maddmarkk said:
you meant do this in the fastboot CMD right? if so then it just boot loops :'C
Click to expand...
Click to collapse
Yep from bootloader:
fastboot boot TWRP.img
I don't have any other idea sorry...
You can try to contact Google or Huawei. Even being out of warranty, some people have had their device replaced.
Good luck...
maddmarkk said:
you meant do this in the fastboot CMD right? if so then it just boot loops :'C
Click to expand...
Click to collapse
Are you able to get into recovery and adb sideload a stock OTA from the google developer website? That's always saved me when I've had problems.
DEVILOPS 007 said:
Are you able to get into recovery and adb sideload a stock OTA from the google developer website? That's always saved me when I've had problems.
Click to expand...
Click to collapse
Guess you didn't read the rest of the the thread...
We don't need more posts about bootloop. There is a main topic that has been discussed for multiple pages:
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
I personally had the issue and had to RMA the phone. I suggest you do the same.
5.1 said:
Guess you didn't read the rest of the the thread...
Click to expand...
Click to collapse
Yeah honestly I couldn't be bothered to be perfectly truthful
so i'm going thru the same thing as OP.
I need help.
so i was on RR official rom and i wanted to try AEX so i flashed it as usual but i wanted to revert back to RR so i wiped everything and flashed the Oreo firmware zip and then restored the RR backup and rebooted the phone.....
but i was stuck on the boot logo so i clean flashed the rom zip file but no use
i also tried LOS15.1 zip file but still i was stuck on the boot logo
i tried to flash the 7.12.7 nougat fastboot rom through Mi flash the rom booted but started to reboot at the time of selecting network during setup
i did some research and found out many users had this issue and they flashed persist.img
i tried the same using the TWRP method but still no use
i even flashed the Oreo beta through the Jamflux tool but even that kept rebooting at the time of setup
plz help me out
TY in advance
clean all and lock option could be helpful !
leo_pard2331 said:
so i was on RR official rom and i wanted to try AEX so i flashed it as usual but i wanted to revert back to RR so i wiped everything and flashed the Oreo firmware zip and then restored the RR backup and rebooted the phone.....
but i was stuck on the boot logo so i clean flashed the rom zip file but no use
i also tried LOS15.1 zip file but still i was stuck on the boot logo
i tried to flash the 7.12.7 nougat fastboot rom through Mi flash the rom booted but started to reboot at the time of selecting network during setup
i did some research and found out many users had this issue and they flashed persist.img
i tried the same using the TWRP method but still no use
i even flashed the Oreo beta through the Jamflux tool but even that kept rebooting at the time of setup
plz help me out
TY in advance
Click to expand...
Click to collapse
Flash command fastboot userdata.img of rom stock oreo
laugeek57 said:
Flash command fastboot userdata.img of rom stock oreo
Click to expand...
Click to collapse
i extracted and flashed the userdata.img from the stock oreo rom but still the phone is rebooting i m on the latest stock rom
Custom rom 243 said:
clean all and lock option could be helpful !
Click to expand...
Click to collapse
i already have tried that but no use
leo_pard2331 said:
i already have tried that but no use
Click to expand...
Click to collapse
Have you tried with a stock rom getting installed in fastboot mode?
laugeek57 said:
Have you tried with a stock rom getting installed in fastboot mode?
Click to expand...
Click to collapse
yes i tried to install the stock Oreo 7.12.29 rom using mi flash tool
actually i am currently on the latest Oreo rom and my phone is restarting
laugeek57 said:
Have you tried with a stock rom getting installed in fastboot mode?
Click to expand...
Click to collapse
i flashed the firmware zip from this link:https://forum.xda-developers.com/mi-a1/development/xiaomi-mi-a1-tissot-firmware-flashable-t3759886
but i wasnt on 7.12.29 at that moment i was on the OPR1.170623.026.8.1.10-beta build flashed by Jamflux's tool do you think that might have caused the problem?
leo_pard2331 said:
i flashed the firmware zip from this link:https://forum.xda-developers.com/mi-a1/development/xiaomi-mi-a1-tissot-firmware-flashable-t3759886
but i wasnt on 7.12.29 at that moment i was on the OPR1.170623.026.8.1.10-beta build flashed by Jamflux's tool do you think that might have caused the problem?
Click to expand...
Click to collapse
I don't know Buddy i use last oreo stock 9.5.9 stable dev
Be careful when you flash a 8.1 I tested the Pixel Experience rom I flash userdata.img from oreo for my phone to restart ... otherwise bootloop
laugeek57 said:
I don't know Buddy i use last oreo stock 9.5.9 stable dev
Be careful when you flash a 8.1 I tested the Pixel Experience rom I flash userdata.img from oreo for my phone to restart ... otherwise bootloop
Click to expand...
Click to collapse
so basically this is my condition right now...
if i flash stock rom i get frequent reboots
and if i flash custom roms i get bootloop :crying:
can i claim my warranty if i flashed the stock rom and locked the bootloader?
leo_pard2331 said:
so basically this is my condition right now...
if i flash stock rom i get frequent reboots
and if i flash custom roms i get bootloop :crying:
can i claim my warranty if i flashed the stock rom and locked the bootloader?
Click to expand...
Click to collapse
Attempt to re-install through a newer Oreo image in either fastboot
https://forum.xda-developers.com/mi-a1/how-to/ota-xiaomi-mi-a1-ota-links-t3718542
laugeek57 said:
Attempt to re-install through a newer Oreo image in either fastboot
https://forum.xda-developers.com/mi-a1/how-to/ota-xiaomi-mi-a1-ota-links-t3718542
Click to expand...
Click to collapse
nevermind i was able to fix the issue by flashing the persist.img :laugh:
anyway thank you very much for your help
leo_pard2331 said:
nevermind i was able to fix the issue by flashing the persist.img :laugh:
anyway thank you very much for your help
Click to expand...
Click to collapse
Well done
What is the easiest way and saftest to return to stock I have the latest twrp version installed
Le pro 3 x727
I flashed back to 23s yesterday using stock rom from this site... http://www.androidiani.com/forum/le...-download-firmware-stock-leeco-lepro-3-a.html ... Flashed 23s from twrp but note twrp was lost after booting, easy to flash back on from the bootloader which was still unlocked.
Edit....Doh, you clearly state you have the 727, sorry about that lol
meangreenie said:
I flashed back to 23s yesterday using stock rom from this site... http://www.androidiani.com/forum/le...-download-firmware-stock-leeco-lepro-3-a.html ... Flashed 23s from twrp but note twrp was lost after booting, easy to flash back on from the bootloader which was still unlocked.
Click to expand...
Click to collapse
My device is x727 not x720 but thanks ?
Use my recovery to return to a clean EUI 5.8.21s with a unlocked bootloader, rooted and TWRP. Just search my profile under most thanked.
tsongming said:
Use my recovery to return to a clean EUI 5.8.21s with a unlocked bootloader, rooted and TWRP. Just search my profile under most thanked.
Click to expand...
Click to collapse
Can I do it with the latest twrp?
Also I'm kinda worried about doing it because I don't have a pc at the moment
Coconut tree said:
Can I do it with the latest twrp?
Also I'm kinda worried about doing it because I don't have a pc at the moment
Click to expand...
Click to collapse
If you read the post, you will see that people used Twrp with success. Personally, I would use ADB or the All in one tool., because the recovery was made with an earlier version of TWRP.
Whenever I'm flashing custom rom.
It reboots to crash dump or fastboot.
I tried latest twrp as well as bluspark's.
Sent from my ONEPLUS A6010 using Tapatalk
arifnasirshaikh said:
Whenever I'm flashing custom rom.
It reboots to crash dump or fastboot.
I tried latest twrp as well as bluspark's.
Flashing producer.
1. Complete wipe.(including vendor,data,internal)
2. Flash twrp installer
3. Flash skydragon and twrp installer
4. Reboot to twrp.
5. Install open gapps and magisk.
6. Reboot to system.
And it goes to crash dump or fastboot.
I tired with different versions of twrp.
Different rom.
I can flash oos without any trouble
Sent from my ONEPLUS A6010 using Tapatalk
Click to expand...
Click to collapse
Sent from my ONEPLUS A6010 using Tapatalk
Can you try booting to TWRP and flashing it to be permanant by itself, reboot into TWRP, THEN flash skydragon alone and see if you can boot?
hunterulmes said:
Can you try booting to TWRP and flashing it to be permanant by itself, reboot into TWRP, THEN flash skydragon alone and see if you can boot?
Click to expand...
Click to collapse
i did try that no success
arifnasirshaikh said:
i did try that no success
Click to expand...
Click to collapse
Bootloader is unlocked, correct?
hunterulmes said:
Bootloader is unlocked, correct?
Click to expand...
Click to collapse
yes
arifnasirshaikh said:
yes
Click to expand...
Click to collapse
And have you tried doing a FASTBOOT restore using the stock firmware?
hunterulmes said:
And have you tried doing a FASTBOOT restore using the stock firmware?
Click to expand...
Click to collapse
yes as mentioned i can flash oos without any issue and it boots normally.
Are you rooted because I was able to flash twrp's zip with elemental manager and I got recovery back
Edit :solved by changing boot slots
Sent from my ONEPLUS A6013 using Tapatalk
Hi guys, I'm on 8.1 right now wanting to go on 11 AOSP.
I flashed both orangefox and latest twrp, but I get black screen after going into recovery. System boots though.
What do? I have no recovery ATM. I can try going back to my latest version (2.8) but how do I actually manage to run latest versions without getting black screen?
I've been reading that It might be due to matching kernel that is missing, could it be? What should I do in this case?
Thanks!
Go to fastboot mode and
Fastboot flash recovery "twrp.img"
Via PC
or just type
fastboot boot "twrp.img"
That's how I flashed, through fastboot. Still getting black screen.
Haven't tried booting straight to IMG, I'll try when I get to
You said system is booting. Do you mean aosp11 or 8.1?
I didn't get to flash aosp11 yet, because I failed to boot into required recovery. So I'm still booting to my current 8.1 rom
Im sorry if this is too obvious, but do you have an unlocked bootloader?
SirRGB said:
Im sorry if this is too obvious, but do you have an unlocked bootloader?
Click to expand...
Click to collapse
Yes I do brother
HeLp Me
Same issue here
quick05 said:
Same issue here
Click to expand...
Click to collapse
It's the firmware bro, flash latest firmware and then flash recovery.
So you dirty flashed the latest oos ROM and then you flashed the recovery again ?
quick05 said:
So you dirty flashed the latest oos ROM and then you flashed the recovery again ?
Click to expand...
Click to collapse
I flashed latest working twrp for my device (was 3.2) from fastboot, booted to working recovery and then flashed android 10 firmware, then (before rebooting) flashed latest recovery. It then booted.
xradium said:
I flashed latest working twrp for my device (was 3.2) from fastboot, booted to working recovery and then flashed android 10 firmware, then (before rebooting) flashed latest recovery. It then booted.
Click to expand...
Click to collapse
Nice thank you ! I flashed 3.2 twrp and now it is booting in recovery
Another problem: when I try to flash the latest OTA of android 10 I can't: error 7 can't load vendor partition...
Any solution ?
quick05 said:
Nice thank you ! I flashed 3.2 twrp and now it is booting in recovery
Another problem: when I try to flash the latest OTA of android 10 I can't: error 7 can't load vendor partition...
Any solution ?
Click to expand...
Click to collapse
u need to flash the firmware that creates the vendor partition, and I guess that it's OOS 5.1.7 (Android 8)
afterwards u can flash whatever latest firmware.
please ask again, as I'm not so sure about which firmware that creates vendor partition.