Related
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Mmmh, strange, I did a factory installation (latest 5.1.1 from Google) and started the same thing from scratch ... and guess what... the system is booting fine now.
No idea why it did not work on my first attempt .
Regards, mistersixt.
mistersixt said:
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Click to expand...
Click to collapse
Same here. Running stock until today, wanted to see a different ROM, flashed TWRP 3.0.0, it refused to boot anything else. Tried to flash DU, then tried Chroma. Did a full wipe, then an advanced wipe selecting everything, then a full format, same thing. Installed TWRP 2.8.7, same thing. Finally installed latest stock, it is now booting, optimizing apps. I don't know if installing a custom rom will work or not yet.
Edit: Yeap, after flashing stock 5.1.1 and installing TWRP 3 again, the phone is now booting into DU.
First time I did a wipe with TWRP, it complained that it couldn't mount /data. Since this is the first time doing it, I assumed it was normal. After going through a full format, it didn't complain about data anymore, but it did complain about something to do with /dev/zero and another file under /dev/. I assume it was trying to dd /dev/zero to a file under /dev/ that didn't exist.
+1
Done the whole process from scratch again and worked like a charm
Hello, same story here.
First I:
- unlocked bootloader
- flashed TWRP (last version)
- flashed Chroma and Gapps
- reboot
=> I consistently rebooted on TWRP. No way to properly install the ROM. No error message at all.
Then I found this thread, and did as described:
- flashed the latest stock ROM
- flashed TWRP again (took me ages to manage to do this: TWRP would not install. I don't know how I finally did it, but at some point it suddenly worked. Probably a driver problem)
- flashed Chroma and Gapps again
Bingo, this time it worked! I don't know why it didn't work the first time. Could it be linked to the bootloader unlock thing?
Hi there folks!
Sorry if i open a thread, probably you've discussed somewhere before about this problem that i'm experiencing.
My OnePlus 5 basically works only with omniROM, it doesn't boot at all when i try to install another one.
I tried with this:
https://forum.xda-developers.com/oneplus-6/development/rom-aospextended-rom-v5-7-t3825642
and this one:
https://forum.xda-developers.com/oneplus-5/development/rom-crdroid-android-5-0-t3836886
I followed every step (About CRAndroid), radio firmware 5.1.5 + TWRP 3.2.3 + Gapps + Magisk 17.1 and No Verity v3 (First try without noverity, second using it)
and i followed also every step neeeded in AOSPExtended rom.
When i try to boot the phone, after the OnePlus logo, nothing happens. The phone reboots in recovery mode, that's it.
If i repeat the same steps with OmniROM it works all fine, except Magisk. If i flash Magisk on the Omni it doesn't boot, if i flash SU it works.
Could it be something related to the encryption/Decription of the device?
When i go into TWRP it doesn't ask me for a pattern or a code. It should be decrypted, right? (i'm a bit confused about that).
I purchased the phone on Gearbest, could it be a particular version of the phone that doesn't allow me to work properly with roms?
Help
did you tried old stock ROMs, 4.* versions ? then 5.0.0 and then the others
Sometimes the partitions need to be wiped. Try a fastboot format userdata; fastboot format system.
azretier said:
did you tried old stock ROMs, 4.* versions ? then 5.0.0 and then the others
Click to expand...
Click to collapse
Actually when the phone arrived i've just unlocked the bootloader and installed a custom rom....what's the purpose of this?
moffa~ said:
Sometimes the partitions need to be wiped. Try a fastboot format userdata; fastboot format system.
Click to expand...
Click to collapse
You....you're a good guy.
I did the command you said, then i booted into TWRP, flashed AospExtended, Gapps Pico and Magisk 17.1 - after reboot it has been stuck @ 1+ logo, then it rebooted again (as always when it doesn't work) and i said "ok here we go again in the TWRP-loop" and INSTEAD it booted rom! Yes!
Good day! I am here asking for a few help as I seem to have trouble getting my phone back to life.
Earlier, I tried flashing android 9.0 pie beta rom I found on a certain group here locally in my country. The rom's link is as follows https://drive.google.com/file/d/15egbHONHGgm0AnvFYm2PCOmSyz0_utRR/view?fbclid=IwAR0I_akz9JcbpZxzitLNfm9OM2a-HH7FiDIDEHPM0-5wj0vIsuvz1TunrQQ. I came from Pixel Experience 9.0 Pie. I downloaded the rom above and rebooted my phone to fastboot mode without clearing data, etc through twrp first. Then I flashed the rom directly using Mi Flash. Once finished, the phone was not booting up properly and resulted in bootloop. Then, I downloaded the official stock rom and had it flashed directly to my phone. However, to no success, I only keep getting bootlooped. I then again tried to boot into fastboot and unlocked oem and flashed twrp and cleared dalvik, system, data and reinstalled pixel experience. Still no joy as upon rebooting, still bootloop.
Can anyone please help or assist on what further actions should I do? I'll greatly appreciate all the help I can get. Thank you!
**Update**
So I tried flashing the AEX Rom using this link https://forum.xda-developers.com/mi-a1/development/rom-aospextended-rom-v4-6-t3757436 and I can see the AEX logo and it stucks up there and just freezes my device.
First install 8.1 with MI Flash
https://forum.xda-developers.com/mi-a1/how-to/solution-bootloop-9-0-beta-t3876533
Necrodaemon said:
First install 8.1 with MI Flash
https://forum.xda-developers.com/mi-a1/how-to/solution-bootloop-9-0-beta-t3876533
Click to expand...
Click to collapse
You sir, just earned a fan! A million thanks!
Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
richstant said:
Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
Click to expand...
Click to collapse
Hi, I got Pie to install with TWRP_3.2.3-Pie_siankatabg_OP5 on my device.
Go to this link:
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
And follow my post on the part where it says:
" Notes for the Pie update: "
Let us know if those steps work for you. The firmware is linked to on there, pre-modified. Try flashing that pre-modified zip and see if your device boots.
richstant said:
Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
Click to expand...
Click to collapse
It sounds like you did not follow the detailed flashing instructions in the first post here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Is your device storage encrypted or decrypted? Have you flashed magisk? Have you used an older magisk(your end link leads to my post where I mention that)? Have you downloaded the rom file without compatibility.zip or did you removed it on your own?
strongst said:
It sounds like you did not follow the detailed flashing instructions in the first post here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Is your device storage encrypted or decrypted? Have you flashed magisk? Have you used an older magisk(your end link leads to my post where I mention that)? Have you downloaded the rom file without compatibility.zip or did you removed it on your own?
Click to expand...
Click to collapse
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
richstant said:
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
Click to expand...
Click to collapse
Maybe try backing your device up, and then locking the bootloader. Try updating with stock recovery on a locked bootloader. If that works, you can then unlock the bootloader and copy your data back
richstant said:
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
Click to expand...
Click to collapse
Please use an older recovery like twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img the actual pie recoveries require pie firmware(mentioned in last post of blue spark thread for example).
strongst said:
Please use an older recovery like twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img the actual pie recoveries require pie firmware(mentioned in last post of blue spark thread for example).
Click to expand...
Click to collapse
OK, I understand now - if I use an older TWRP, or the siankatabg version, it works fine. I can then flash the Pie ROM, however it still won't boot - I get the oneplus logo, then it just reboots. However having done the Pie flash, I can then flash the more recent TWRPs (codeworx or Bluespark), and can now get into recovery fine. However Pie still won't boot - I've even tried re-flashing the Pie ROM from within the newer TWRPs, but the result is the same - it gets to the oneplus logo, then reboots. At this stage I guess wiping system/vendor/data is the only way forwards?
*Edit* - OK, so wiping everything fixed the issue, I'm now on Pie. Flashing Magisk didn't work when flashing the ROM, but I'll try again once it's finished downloading all my apps etc.
Firstly, my phone isn't hard-bricked. I'm able to load different versions of the TWRP recovery and access Fastboot without any problems. I'm also pretty comfortable using adb to push, sideload, access fastboot, recovery , etc. so please feel free to throw out any suggestions that might help me resolve my issue. (Note:I'm unable to find the stock recovery on OnePlus's support page anymore, I recall they always had the option to download the stock recovery just below the download option for the stock ROM, so I haven't been able to try sideloading after formatting with the stock recovery.)
My OnePlus 5 was running stock Oreo and I'd been meaning to upgrade to Lineage 16.0 (Pie) or any other Pie ROM really. I booted into TWRP (3.2.3-0 - Oreo firmware) and wiped everything other than USB storage and formatted data too as my previous Oreo installation was encrypted. Then, I downloaded codeworkxx's 9.0.3 firmware for OnePlus 5 and pushed it to my phone using adb. I flashed the firmware successfully, rebooted into Bootloader/fastboot; and flashed the Android Pie version of TWRP recovery ( https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/ ) and was able to successfully boot back into the recovery. Since then, I've tried to flash multiple different Pie ROMs (Pixel Experience, Lineage 16.0, stock OOS official build - 9.0.3 , Beta OOS build OpenBeta26) (clean flashing always) but always ended up with a bootloop with the boot animations in all the ROMs. I've even tried flashing them with Magisk-v18.0 but that doesn't help either. I've waited for 15 min with each boot for the different ROM's (ending up in bootloops) and on rebooting back to TWRP, I've always found that irrespective of ROMs, the only folder that's created in Internal Storage is 'obb' and it is an empty folder. I've even tried sideloading OOS 9.0.3 (official build) via TWRP and that still ends up in a bootloop with the obb folder in Internal Storage being the only thing created. Also, flashing the boot.img recovery in the stock ROM zip files leads to a blank screen with a white LED that tries to install Qualcom drivers, so I just reflashed TWRP and am back to where I started.
That pretty much sums up my problem here. Kindly throw suggestions at me to help fix my problem' I've searched the forums but most of the bootloop issues I've found and read are about unsuccessful firmware flashes (not the case with me as I've explained above) or dirty flashes (again, not the case with me as I always cleanflash).
Thanks!
You should be focusing on getting stock OOS back on before trying custom rom. Have you tried rolling back to 5.1.7 Oreo? Sometime it better to go back to square 1 and try again.
Z-Blade said:
You should be focusing on getting stock OOS back on before trying custom rom. Have you tried rolling back to 5.1.7 Oreo? Sometime it better to go back to square 1 and try again.
Click to expand...
Click to collapse
Thank you for replying!
I successfully flashed the 5.1.7 firmware and Oreo-TWRP-recovery and was able to install Lineage OS 15.1 and boot it up properly. I'm unable to find a link for previous versions of OOS to test whether or not 5.1.7 would work. Do you know where I can find a link?
Thanks again!
BigTurboSkipper said:
Thank you for replying!
I successfully flashed the 5.1.7 firmware and Oreo-TWRP-recovery and was able to install Lineage OS 15.1 and boot it up properly. I'm unable to find a link for previous versions of OOS to test whether or not 5.1.7 would work. Do you know where I can find a link?
Thanks again!
Click to expand...
Click to collapse
It's within the guides section https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
strongst said:
It's within the guides section https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Click to expand...
Click to collapse
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
BigTurboSkipper said:
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
Click to expand...
Click to collapse
What was your LAST stock oxygenOS version that was installed your device prior to 5.1.7?
strongst said:
What was your LAST stock oxygenOS version that was installed your device prior to 5.1.7?
Click to expand...
Click to collapse
I can't recall exactly, but it was most probably OB23/24 (Oreo)
BigTurboSkipper said:
I can't recall exactly, but it was most probably OB23/24 (Oreo)
Click to expand...
Click to collapse
Can you please try to flash 5.1.4 stock oxygenOS rom and the 5.1.7 after it, then magisk and reboot to the os?
Make sure you have an old Oreo compatible recovery like this https://drive.google.com/file/d/1DrEMydZfQxC_eWx1W-OlASo8H7okXNTQ/view?usp=drivesdk
strongst said:
Can you please try to flash 5.1.4 stock oxygenOS rom and the 5.1.7 after it, then magisk and reboot to the os?
Make sure you have an old Oreo compatible recovery like this https://drive.google.com/file/d/1DrEMydZfQxC_eWx1W-OlASo8H7okXNTQ/view?usp=drivesdk
Click to expand...
Click to collapse
Successfully flashed but still results in a bootloop
BigTurboSkipper said:
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
Click to expand...
Click to collapse
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
My only suggestion ...
BigTurboSkipper said:
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
Click to expand...
Click to collapse
Greetings! I got your private message, but I haven't read it yet. Sorry, very busy today. However, I can make the following suggestion to get your device back into original working order.
Have a look at this link on xda. It's for an unbrick tool, which I've used numerous times with great success.
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
This tool will put your device back into its original condition, with original OOS.
Let me know if it works for you.
Peter
BigTurboSkipper said:
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
Click to expand...
Click to collapse
OxygenOS also needs a formatted internal storage, otherwise bootloop will pop up
strongst said:
OxygenOS also needs a formatted internal storage, otherwise bootloop will pop up
Click to expand...
Click to collapse
Definitely! I've always been clean flashing ROMs (Wiping Internal Storage, Data, System, Dalvik Cache, Cache + Wiping/Formatting Data to factory reset ) for each trial!
BigTurboSkipper said:
Definitely! I've always been clean flashing ROMs (Wiping Internal Storage, Data, System, Dalvik Cache, Cache + Wiping/Formatting Data to factory reset ) for each trial!
Click to expand...
Click to collapse
Wiping system, data, cache, Installing 5.1.4, then magisk, then format internal storage, then boot os should not cause a bootloop
What's your twrp recovery? Did you tried mine?
strongst said:
Wiping system, data, cache, Installing 5.1.4, then magisk, then format internal storage, then boot os should not cause a bootloop
What's your twrp recovery? Did you tried mine?
Click to expand...
Click to collapse
That's exactly what I'm doing. I've tried using codeworkxx 's versions, blu_spark TWRP versions and yours too!
PeterGuru said:
Greetings! I got your private message, but I haven't read it yet. Sorry, very busy today. However, I can make the following suggestion to get your device back into original working order.
Have a look at this link on xda. It's for an unbrick tool, which I've used numerous times with great success.
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
This tool will put your device back into its original condition, with original OOS.
Let me know if it works for you.
Peter
Click to expand...
Click to collapse
Thank you for replying!
The tool doesn't detect my device whatsoever - I have system-wide adb & fastboot set up (to use from any folder or path) yet the device is not detected in fastboot mode or recovery mode.
How do you use it?
Thanks!
BigTurboSkipper said:
Thank you for replying!
The tool doesn't detect my device whatsoever - I have system-wide adb & fastboot set up (to use from any folder or path) yet the device is not detected in fastboot mode or recovery mode.
How do you use it?
Thanks!
Click to expand...
Click to collapse
You need to put your device into MSM Download mode. It's simple. Power off your device. Press and hold the Volume UP key for about 8-10 seconds and, while continuing to hold the Volume UP key, plug in your device to your computer via USB. Open the MSM Tool and press Start.
That's it.
It takes about 3-5 minutes for the tool to complete the unbrick process.
Peter
Thank you! I was able to successfully use the unbrick tool to reset to OOS 4.5.8 Nougat. I'm going to try stepping all the way up to Pie now!