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.
Related
I have flashed the newer firm ware but when I installed a MM rom exodus and now I wasnt able to use the recovery any more. I have tried flashing other recoveries but the only one that worked is the stock recovery
Look for hybrid twrp 3.0.2.0 and flash. Boot into recovery and reflash image. Should hold then.
Curlypengling said:
I have flashed the newer firm ware but when I installed a MM rom exodus and now I wasnt able to use the recovery any more. I have tried flashing other recoveries but the only one that worked is the stock recovery
Click to expand...
Click to collapse
Hi, did you relock your bootloader.. Check it's status.
Check Boot Loader Status in developer Mod
After this, go in your fastboot Mod and flash TWRP (Modified) Recovery.
After flashing recovery, you have to boot into recovery as well otherwise your OS will replace your recovery with the STOCK one..
after using this command,
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
use
fastboot boot recovery.img
Click to expand...
Click to collapse
Reply if this doesnt work for you.
Few day earlier my home button died , so i decided to change rom . After some tries with different roms it started to work again (finally settled for oxygenos) . I used that rom for quite some time before i got bored of oxygenos and decided to change it . But to my surprise i won't boot into recovery no matter what i try. I tried to upgrade or change it using flashify and other app ,still nothing happened. Finally i tried to flash recovery using computer , still it won't boot in recovery .
My boot loader is having unlocked status. I tried flashing different types and versions of recovery . Everytime i write command error comes and it won't flash . I searched my threads with suggestions of using specific recovery for oneplus 2 but none of them works.
Please help , My battery drains like sand from hand. I get less than 2.5 hours of screen time
What version of Android/oxygen os are you using??
sivacharan92 said:
What version of Android/oxygen os are you using??
Click to expand...
Click to collapse
lollipop
Oos 2.2.1
Ok.. Go into Fastboot mode.. If your bootloader is unlocked, flash twrp recovery 3.0.2-0.img.. You can download it from twrp website.. Hope you know how to flash a twrp recovery.
sivacharan92 said:
Ok.. Go into Fastboot mode.. If your bootloader is unlocked, flash twrp recovery 3.0.2-0.img.. You can download it from twrp website.. Hope you know how to flash a twrp recovery.
Click to expand...
Click to collapse
Tried it but doesn't work ....
Some TWRP recoveries don't work with earlier rom firmware. Try finding Twrp 2.8.6 or 2.8.7 and try flashing. Also wich version of windows are you using. I've had my fair share of problems with windows 10.
Best of luck
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
I'm trying to revert my oneplus 5 back to stock. I done all the steps got stock recovery installed. When I attempt to sideload original oos through adb sideload it keeps failing at 46%. Any advice would be very appreciated.. I've read so much and tried so many different things. I am completely stuck.
TENlll423 said:
I'm trying to revert my oneplus 5 back to stock. I done all the steps got stock recovery installed. When I attempt to sideload original oos through adb sideload it keeps failing at 46%. Any advice would be very appreciated.. I've read so much and tried so many different things. I am completely stuck.
Click to expand...
Click to collapse
Which rom do you want to flash and from which rom are you coming? Maybe there are some updates between you're missing...
strongst said:
Which rom do you want to flash and from which rom are you coming? Maybe there are some updates between you're missing...
Click to expand...
Click to collapse
I got the phone from a friend and it has been completely wiped and formatted through TWRP. He did have a nougat custom ROM on it prior to that.
I tried to sideload to it with TWRP and it wouldn't work. I followed directions from a website that explains how to revert your op5 back to stock using stock recovery. I was trying to put the original oxygen OS ROM on it that came with the phone using the stock recovery and adb and fastboot. I'm thinking maybe I possibly downloaded the wrong OOS version. Who knows. Lol .
It had nougat Pure FusionOS 7.1.2. encrypted...SuperSU root and TWRP blue spark.
Now all it has is stock recovery with No OS
Would like to get OOS pie on it eventually.
TENlll423 said:
I got the phone from a friend and it has been completely wiped and formatted through TWRP. He did have a nougat custom ROM on it prior to that.
I tried to sideload to it with TWRP and it wouldn't work. I followed directions from a website that explains how to revert your op5 back to stock using stock recovery. I was trying to put the original oxygen OS ROM on it that came with the phone using the stock recovery and adb and fastboot. I'm thinking maybe I possibly downloaded the wrong OOS version. Who knows. Lol .
It had nougat Pure FusionOS 7.1.2. encrypted...SuperSU root and TWRP blue spark.
Now all it has is stock recovery with No OS
Would like to get OOS pie on it eventually.
Click to expand...
Click to collapse
Do you want to have root along with your new rom? And which rom do you want?
strongst said:
Do you want to have root along with your new rom? And which rom do you want?
Click to expand...
Click to collapse
New OOS 5.1 7. With Magisk v18 would be great.
TENlll423 said:
New OOS 5.1 7. With Magisk v18 would be great.
Click to expand...
Click to collapse
You need to flash 5.1.4 at first to create the vendor partition like described here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 then you can flash 5.1.7. If that fails you need to flash 5.1.5 and 5.1.6 after 5.1.4 and before 5.1.7. You'll find older versions here
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Also you need an actual(latest codeworkx for example) twrp recovery https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
Please report back
strongst said:
You need to flash 5.1.4 at first to create the vendor partition like described here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 then you can flash 5.1.7. If that fails you need to flash 5.1.5 and 5.1.6 after 5.1.4 and before 5.1.7. You'll find older versions here
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Also you need an actual(latest codeworkx for example) twrp recovery https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
Please report back
Click to expand...
Click to collapse
Thank you... can I do all that by installing TWRP with fastboot and then sideload 5.1.4?
TENlll423 said:
Thank you... can I do all that by installing TWRP with fastboot and then sideload 5.1.4?
Click to expand...
Click to collapse
There's no need of sideload anything when you flashed twrp through fastboot. Just copy the roms on the device and flash through twrp
strongst said:
There's no need of sideload anything when you flashed twrp through fastboot. Just copy the roms on the device and flash through twrp
Click to expand...
Click to collapse
Ok I'll give it a try thanks. And merry Christmas
strongst said:
There's no need of sideload anything when you flashed twrp through fastboot. Just copy the roms on the device and flash through twrp
Click to expand...
Click to collapse
How can I transfer 5.1.4 to phone from pc? My phone is completely wiped. Computer won t recognize phone in PC file explorer? Also, Will I have to fastboot flash recovery twrp img to get new twrp to work? Sorry for all the questions.
strongst said:
There's no need of sideload anything when you flashed twrp through fastboot. Just copy the roms on the device and flash through twrp
Click to expand...
Click to collapse
Keep getting failed to mount/system/ invalid argument in thwrp. Can't transfer rom from pc. Its showing up in PC file explorer but won't transfer
strongst said:
You need to flash 5.1.4 at first to create the vendor partition like described here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 then you can flash 5.1.7. If that fails you need to flash 5.1.5 and 5.1.6 after 5.1.4 and before 5.1.7. You'll find older versions here
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Also you need an actual(latest codeworkx for example) twrp recovery https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
Please report back
Click to expand...
Click to collapse
Can't copy anything to phone. says there's no system and I even tried sideloading rom and said it corrupt
I think it's done. It's beyond me.. I've read so much trying to get this thing fixed I can't even see straight.. lol
It lets me copy small files over like magisk v18. It works. When I attempt to copy 5.1.4 rpm over it says device stopped not responding. Crazy
TENlll423 said:
It lets me copy small files over like magisk v18. It works. When I attempt to copy 5.1.4 rpm over it says device stopped not responding. Crazy
Click to expand...
Click to collapse
You need to mount internal storage, not system. Is your twrp updated to latest codeworkx?
I'm redownloading 5.1.4
I tried to copy over another ROM I had and it started to copy over so it is the file that was corrupted.
Thanks again I really appreciate it ?
strongst said:
You need to mount internal storage, not system. Is your twrp updated to latest codeworkx?
Click to expand...
Click to collapse
Second to latest... I have
TWRP-3.2.3-0-20181031-codeworkx installed.
Latest one wouldn't boot.
It won't install no vendor to mount or something. I'm done... Thanks for everything anyway.
When I reboot to recovery. This what it says.
TENlll423 said:
Second to latest... I have
TWRP-3.2.3-0-20181031-codeworkx installed.
Latest one wouldn't boot.
Click to expand...
Click to collapse
I'm using twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img
You have the same? The vendor partition will be created with 5.1.4.
You can go(in twrp) to mount - > vendor. But the recovery should mount it automatically when it's created by flashing 5.1.4.
strongst said:
I'm using twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img
You have the same? The vendor partition will be created with 5.1.4.
You can go(in twrp) to mount - > vendor. But the recovery should mount it automatically when it's created by flashing 5.1.4.
Click to expand...
Click to collapse
Yeah that's the same one I'm using I'm thinking maybe I don't have TWRP setup right is there any settings I'm supposed to go into?
Even when I check off everything in advanced wipe and do a wipe it comes up fine all the way to the end and then it says failed to mount vendor (invalid argument)
I liked everything again in TWRP I went to flash 514 and it works all the way up to the end and fails to mount vendor invalid argument.
Somehow I need to activate the vendor partition or something.
well I'm going back to reading like a madman and figure out if anybody else had this problem online. Lol thanks