I had been using Sultan's 6.0 ROM for a long time now. but it was causing issues and I wanted to try something new. I downloaded Tugapower (7.1) which I used before, and stock OxygenOS 2.1.4 flashable.
I did a nandroid backup of Sultan's ROM, I installed 7.1 which worked fine, and then wanted to test OxygenOS, which didn't boot, and then i proceeded to restore the backup. I left the phone to charge during restore, and I came back to see the phone massively hot and won't boot, not even into recovery. I checked fastboot and that worked.
I've tried a lot of stuff but none failed to boot.
Things I've tried:
1. Fastboot restore of CM11S - gets stuck at rom boot animation first try then bootloops at boot.
2.Fastboot restore of OxygenOS/CyanogenOS - same as above. Once it booted after i "Fixed Selinux" thingy from TWRP because I remembered that was an issue when i went back to 6.0 from 7.1 a few months back, but mobile data didnt work and it rebooted and started boot looping within seconds.
3. Fastboot restore of CM11s and then CM13 snapshot by recovery - bootloop
Recovery does not work by Power-UP-Vol. Only works once after flashing TWRP via OnePlus One Toolbox. and then bootloop if i try again.
ADB works in TWRP, i can also see my internal storage
4. Tried re enabling /persist partition using make_ext4fs
5. Tried MSMDownloadTool, drivers are fine, it flashes fine, but still says a lot of .img like recovery persist system userdata64 failed.
6. Tried Qualcom QSIF tool to restore ColorOS, same, flashes correctly, but still ROM does not boot.
7. Tried MiFlash to restore ColorOS, same as above.
Is my beloved OPO really gone? Or can i fix this somehow without taking it to Customer Care?
Fastboot works perfectly, also recovery works well when ColorOS is flashed. But just nothing makes the ROM boot. Also sometimes the battery starts counting down from 0 to the exact battery percentage
naeem76 said:
I had been using Sultan's 6.0 ROM for a long time now. but it was causing issues and I wanted to try something new. I downloaded Tugapower (7.1) which I used before, and stock OxygenOS 2.1.4 flashable.
I did a nandroid backup of Sultan's ROM, I installed 7.1 which worked fine, and then wanted to test OxygenOS, which didn't boot, and then i proceeded to restore the backup. I left the phone to charge during restore, and I came back to see the phone massively hot and won't boot, not even into recovery. I checked fastboot and that worked.
I've tried a lot of stuff but none failed to boot.
Things I've tried:
1. Fastboot restore of CM11S - gets stuck at rom boot animation first try then bootloops at boot.
2.Fastboot restore of OxygenOS/CyanogenOS - same as above. Once it booted after i "Fixed Selinux" thingy from TWRP because I remembered that was an issue when i went back to 6.0 from 7.1 a few months back, but mobile data didnt work and it rebooted and started boot looping within seconds.
3. Fastboot restore of CM11s and then CM13 snapshot by recovery - bootloop
Recovery does not work by Power-UP-Vol. Only works once after flashing TWRP via OnePlus One Toolbox. and then bootloop if i try again.
ADB works in TWRP, i can also see my internal storage
4. Tried re enabling /persist partition using make_ext4fs
5. Tried MSMDownloadTool, drivers are fine, it flashes fine, but still says a lot of .img like recovery persist system userdata64 failed.
6. Tried Qualcom QSIF tool to restore ColorOS, same, flashes correctly, but still ROM does not boot.
7. Tried MiFlash to restore ColorOS, same as above.
Is my beloved OPO really gone? Or can i fix this somehow without taking it to Customer Care?
Fastboot works perfectly, also recovery works well when ColorOS is flashed. But just nothing makes the ROM boot. Also sometimes the battery starts counting down from 0 to the exact battery percentage
Click to expand...
Click to collapse
Change the battery. U are not only one... There are lots of people had this issue after 2.5+ year including me. I changed battery two days ago (not original) now its work normal.
https://forum.xda-developers.com/showthread.php?t=3565871
https://forum.xda-developers.com/showthread.php?t=3610933
Sent from my A0001 using Tapatalk
naeem76 said:
I had been using Sultan's 6.0 ROM for a long time now. but it was causing issues and I wanted to try something new. I downloaded Tugapower (7.1) which I used before, and stock OxygenOS 2.1.4 flashable.
I did a nandroid backup of Sultan's ROM, I installed 7.1 which worked fine, and then wanted to test OxygenOS, which didn't boot, and then i proceeded to restore the backup. I left the phone to charge during restore, and I came back to see the phone massively hot and won't boot, not even into recovery. I checked fastboot and that worked.
I've tried a lot of stuff but none failed to boot.
Things I've tried:
1. Fastboot restore of CM11S - gets stuck at rom boot animation first try then bootloops at boot.
2.Fastboot restore of OxygenOS/CyanogenOS - same as above. Once it booted after i "Fixed Selinux" thingy from TWRP because I remembered that was an issue when i went back to 6.0 from 7.1 a few months back, but mobile data didnt work and it rebooted and started boot looping within seconds.
3. Fastboot restore of CM11s and then CM13 snapshot by recovery - bootloop
Recovery does not work by Power-UP-Vol. Only works once after flashing TWRP via OnePlus One Toolbox. and then bootloop if i try again.
ADB works in TWRP, i can also see my internal storage
4. Tried re enabling /persist partition using make_ext4fs
5. Tried MSMDownloadTool, drivers are fine, it flashes fine, but still says a lot of .img like recovery persist system userdata64 failed.
6. Tried Qualcom QSIF tool to restore ColorOS, same, flashes correctly, but still ROM does not boot.
7. Tried MiFlash to restore ColorOS, same as above.
Is my beloved OPO really gone? Or can i fix this somehow without taking it to Customer Care?
Fastboot works perfectly, also recovery works well when ColorOS is flashed. But just nothing makes the ROM boot. Also sometimes the battery starts counting down from 0 to the exact battery percentage
Click to expand...
Click to collapse
Did you tried flashing stock Cos13.1.x through fastboot?
Mr.Ak said:
Did you tried flashing stock Cos13.1.x through fastboot?
Click to expand...
Click to collapse
Yup I've tried that
naeem76 said:
Yup I've tried that
Click to expand...
Click to collapse
So,what happens after that? Does it boots?
Mr.Ak said:
So,what happens after that? Does it boots?
Click to expand...
Click to collapse
2.Fastboot restore of OxygenOS/CyanogenOS - same as above. Once it booted after i "Fixed Selinux" thingy from TWRP because I remembered that was an issue when i went back to 6.0 from 7.1 a few months back, but mobile data didnt work and it rebooted and started boot looping within seconds.
Here this one, it was weird, it never booted afterwards
Bump.
Update: The phone doesn't reboot anymore constantly, it just powers off after the initial oneplus logo
twrp sometimes shows symlinks error, and won't reboots if i Flash anything, cwm flashes fine but no system is booted
naeem76 said:
Bump.
Update: The phone doesn't reboot anymore constantly, it just powers off after the initial oneplus logo
twrp sometimes shows symlinks error, and won't reboots if i Flash anything, cwm flashes fine but no system is booted
Click to expand...
Click to collapse
Device works fine when it is in TWRP? Like,no reboots or power off(s) whatsoever? Battery works fine in TWRP? Like,charging and stuff? If it does,then this is unlikely a battery issue,however,I would suggest you to remove battery(go through tutorials on youtube) and attach it again.
This has happened to me before,like if I'm not able to flash anything from TWRP then I just change/update recovery to unofficial/newer versions of it(did you tried this?) or,I just flash Cos13 through fastboot then it boots up fine and I flash TWRP again and boom,everything is back to normal.In cases where I'm even fail to flash Cos13(shows system error/system partition corrupt) or I'm not even able to boot to fastboot i.e.,hardbrick,I just use Cm11S restore tool(modified version of color os toolkit,you can find on general thread) and it flashes perfectly fine and boom,device is back!
I hope it helps!
Ps- This is the tool I'm talking about,
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
I always use this because after flashing from color os tool,I used to get bootloop,though fastboot mode was accessible then so I could just flash Cos13 through fastboot and I no longer get any system errors and it boots up fine.
naeem76 said:
Bump.
Update: The phone doesn't reboot anymore constantly, it just powers off after the initial oneplus logo
twrp sometimes shows symlinks error, and won't reboots if i Flash anything, cwm flashes fine but no system is booted
Click to expand...
Click to collapse
I think it's a battery issue. There are so many people facing the same issue. Trust me,just change your battery.
It happened to me once. I had to erase every partition via fastboot, not only system data and cache, but also modem, efs, recovery ecc. Then I flashed stock COS13.1 partitions images and it worked. Just remember: do NOT turn off or reboot your phone between the erase and the flash, it could hard brick the device!
edit: You should also backup your existing efs partition via recovery.
Fixed my device. For future reference, it was a battery issue, Just couldn't retain enough charge, enough to boot into recovery but not enough to boot any ROM, Changed battery and everything is back to normal
Fixed it Guys, Battery issue, had enough charge for recovery, but just couldn't boot a rom. Changed battery and everything's fine now
naeem76 said:
Fixed it Guys, Battery issue, had enough charge for recovery, but just couldn't boot a rom. Changed battery and everything's fine now
Click to expand...
Click to collapse
@psxda97
Mr.Ak said:
@psxda97
Click to expand...
Click to collapse
psxda97 said:
I think it's a battery issue. There are so many people facing the same issue. Trust me,just change your battery.
Click to expand...
Click to collapse
psxda97 said:
Click to expand...
Click to collapse
My trust on you
naeem76 said:
My trust on you
Click to expand...
Click to collapse
LOL!
I'm glad it worked
Related
Hello! I've been running the CM13 nightly from Dec 26.
Today i downloaded the Dec 30 nightly.
I had the phone in airplane mode when I rebooted into TWRP to flash the nightly along with the xposed v78 sdk23.
After rebooting my simcard wasn't detected anymore.
It clearly is a software problem, and rebooting or wiping cache/dalvik didn't solve my problem.
I hope you can help me
Same boat. No SIM
No SIM card detected here as well after the 123015 update. I am not using the custom kernel nor was I in airplane mode when I flashed.
Tried rebooting a couple times. Removed SIM card and replaced. Couldn't get it to recognize.
Same problem here with the 123015 update. Reverting to old roms did not work.
just use search ...
you probably use twrp 2.8.6.1 or greater, so new modem firmware in 30/12 nightly is not updated correctly, if you use cm, use cm recovery too or twrp 2.8.6.0! and update rom again
reflash old firmware and it will be back.
its a combination of bad luck and bad flash on the recovery you are using.
use twrp 2.8.7.6.0.
That one is not prone to bad flashes of firmware
no need to restore efs cause the bad flash can be corrected
Sent from my A0001 using Tapatalk
Startlinger said:
reflash old firmware and it will be back.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Where do I find the 'old firmware'
deleted
just back to 29/12 nightly, flash correct recovery and again flash 30/12
I'm also having this issue, but it happened under different circumstances:
I was using the last CM12.1 nightly (2015-11-21).
On a previous occasion I had clean-flashed the CM13 nightly (2015-12-10), however it was freezing and crashing quite a lot so I decided to wait a bit, and restored my CM12.1 build (after making a nandroid back-up of my CM13 build).
Yesterday (2015-12-30) I thought I'd see how the CM13 builds were going, so restored my CM13 backup... This is when my phone refused to recognise my sim card. On top of this, it would randomly reboot for no apparent reason. I updated to the latest CM13 nightly (2015-12-30) but these problems weren't fixed.
I then decided to restore my CM12.1 build (which was backed up right before I attempted any of this), however the problems remained. It wouldn't recognise my sim card and would reboot at random.
Since then I have wiped cache + dalvik, cache + dalvik + data, cache + dalvik + system + data + internal memory, done a fresh install, and still the problems persist.
After reading the above posts I'm going to try and roll back my TWRP to 2.8.6.0, but needless to say it's been a very frustrating experience!
If anyone can see anything I'm doing amazingly wrong, please let me know.
twrp-2.8.6.0
NoSyt15 said:
I'm also having this issue, but it happened under different circumstances:
I was using the last CM12.1 nightly (2015-11-21).
On a previous occasion I had clean-flashed the CM13 nightly (2015-12-10), however it was freezing and crashing quite a lot so I decided to wait a bit, and restored my CM12.1 build (after making a nandroid back-up of my CM13 build).
Yesterday (2015-12-30) I thought I'd see how the CM13 builds were going, so restored my CM13 backup... This is when my phone refused to recognise my sim card. On top of this, it would randomly reboot for no apparent reason. I updated to the latest CM13 nightly (2015-12-30) but these problems weren't fixed.
I then decided to restore my CM12.1 build (which was backed up right before I attempted any of this), however the problems remained. It wouldn't recognise my sim card and would reboot at random.
Since then I have wiped cache + dalvik, cache + dalvik + data, cache + dalvik + system + data + internal memory, done a fresh install, and still the problems persist.
After reading the above posts I'm going to try and roll back my TWRP to 2.8.6.0, but needless to say it's been a very frustrating experience!
If anyone can see anything I'm doing amazingly wrong, please let me know.
Click to expand...
Click to collapse
in your case your efs may have gotton corrupt, next to a bad flash. Do if flashing old firmware doesnt fix it, restore the backup of efs if you made one to make more confusing you may need a special twrp version to have made the backup on in first place. to make more confusing.
Try this first,official twrp doesnt backup the firmware, so chance is highest you are running cm13firmware and cm12 rom. flash and reboot on recovery official 2.8.6.0, clean and repair system, data, cache. Flash old cm13 and let it boot. Note you should have no(maybe just 2) lines which state after "Writing radio image...")"already up to date
All functioning then score! Proceed with latest nightly
All not functioning efs restore should help. Never made one, follow above and flash back the cm12 rom you have. Same case with firmware updating and booting
Sent from my A0001 using Tapatalk
fronzinator said:
Hello! I've been running the CM13 nightly from Dec 26.
Today i downloaded the Dec 30 nightly.
I had the phone in airplane mode when I rebooted into TWRP to flash the nightly along with the xposed v78 sdk23.
After rebooting my simcard wasn't detected anymore.
It clearly is a software problem, and rebooting or wiping cache/dalvik didn't solve my problem.
I hope you can help me
Click to expand...
Click to collapse
Use 2.8.6.0 of twrp to update modem
Startlinger said:
in your case your efs may have gotton corrupt, next to a bad flash. Do if flashing old firmware doesnt fix it, restore the backup of efs if you made one to make more confusing you may need a special twrp version to have made the backup on in first place. to make more confusing.
Try this first,official twrp doesnt backup the firmware, so chance is highest you are running cm13firmware and cm12 rom. flash and reboot on recovery official 2.8.6.0, clean and repair system, data, cache. Flash old cm13 and let it boot. Note you should have no(maybe just 2) lines which state after "Writing radio image...")"already up to date
All functioning then score! Proceed with latest nightly
All not functioning efs restore should help. Never made one, follow above and flash back the cm12 rom you have. Same case with firmware updating and booting
Click to expand...
Click to collapse
I restored my twrp to 2.8.6.0 (after wiping the entire phone previously... urgh), and then flashed the latest nightly. Everything worked again!
I ended up going back to my CM12.1 backup as the TrueCaller CM app keeps crashing in CM13. I could just keep the stock dialer, but I have grown accustomed to knowing who's calling me!
Thanks for your help all!
I get this issue as well.
IVIatty said:
I get this issue as well.
Click to expand...
Click to collapse
ok, thanks for informing us.
bastard79 said:
ok, thanks for informing us.
Click to expand...
Click to collapse
Thank your for thanking him for informing us
Sent from my A0001 using Tapatalk
Hi, I'm stuck. I have tried flashing the twrp-2.8.6.0-bacon.img recovery image file I got from dl.twrp.me. The file matches the MD5 I got from the TWRP website (f69fa503419644851822d883c2388bb8), and I don't see any errors when I do a fastboot flash recovery twrp-2.8.6.0-bacon.img command.
However, when I have tried to boot back into Recovery Mode, my phone just ends up booting into Normal Mode (until my phone gets hung). Doing a fastboot boot twrp-2.8.6.0-bacon.img command didn't get me into Recovery Mode, either. If I go back and do a fastboot flash recovery twrp-2.8.7.0-bacon.img, I can boot back into the 2.8.7.0 TWRP Recovery Mode, but that won't let me get my modem back.
Can anybody help (maybe with a different copy of the twrp-2.8.6.0-bacon.img recovery image)?
Thanks.
¿GJ?
Startlinger said:
use twrp 2.8.7.6.0.
Click to expand...
Click to collapse
Hi, Startlinger - Do you mean 2.8.6.0? That's a little confusing ...
¿GotJazz? said:
Hi, I'm stuck. I have tried flashing the twrp-2.8.6.0-bacon.img recovery image file I got from dl.twrp.me. The file matches the MD5 I got from the TWRP website (f69fa503419644851822d883c2388bb8), and I don't see any errors when I do a fastboot flash recovery twrp-2.8.6.0-bacon.img command.
However, when I have tried to boot back into Recovery Mode, my phone just ends up booting into Normal Mode (until my phone gets hung). Doing a fastboot boot twrp-2.8.6.0-bacon.img command didn't get me into Recovery Mode, either. If I go back and do a fastboot flash recovery twrp-2.8.7.0-bacon.img, I can boot back into the 2.8.7.0 TWRP Recovery Mode, but that won't let me get my modem back.
Can anybody help (maybe with a different copy of the twrp-2.8.6.0-bacon.img recovery image)?
Thanks.
¿GJ?
Hi, Startlinger - Do you mean 2.8.6.0? That's a little confusing ...
Click to expand...
Click to collapse
Download again via different browser, double check filesize of what you downloaded. It was a bad download sir
You can download on your phone also, same check download size. From twrp where when flashing you can select img. Then select recovery, reboot recovery and your on the one that works
Sent from my A0001 using Tapatalk
Startlinger said:
Download again via different browser, double check filesize of what you downloaded. It was a bad download sir
You can download on your phone also, same check download size. From twrp where when flashing you can select img. Then select recovery, reboot recovery and your on the one that works
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Hi, @Startlinger - I've downloaded twrp-2.8.6.0-bacon.img with three different browsers (Chrome, MS IE, and Firefox). All three images acted the same way: They all matched the MD5 posted on TWRP, and they were all unbootable (either by flashing, or with a fastboot boot twrp-2.8.6.0-bacon.img command). I couldn't download the image to the phone via the internet, because I can't get an internet connection on my OPO anymore - probably because the modem is corrupted. I did copying one of the computer-downloaded 2.8.6.0 images to the phone, and tried flashing the image through TWRP 2.8.7.0, but the results were exactly the same ... it wouldn't boot into Recovery Mode after that.
Is the f69fa503419644851822d883c2388bb8 MD5 value correct? (I suspect it is)
One thing I've noticed is that I can't just power-off my phone anymore when 2.8.6.0 is loaded. If I try to power off, it comes back up in Normal Mode. This may be related to the corrupted 2.8.6.0 Recovery Mode.
Update: I've also noticed something else - I tried doing a fastboot boot twrp-image-file with other versions of TWRP (2.84.1 and 2.8.5.1). None of these boot into Recovery Mode - just the 2.8.7.0 image works.
Is there something else I need to recover on my phone (if it's even possible)? Is there any other way I can reinstall a workable Lollipop 5.0.2 Modem Image onto the phone?
well, thats a first gotjazz.
I would recommend 2.8.7.05 from here https://www.androidfilehost.com/?fid=24269982087010524
if same results, perhaps best to download latest fastboot rom from cyanogen. Then fastboot your way back to a complete stock situation. Before doing so wipe everything in 2.8.7.0, and repair all partitions that allow repairing.
when fastbooting everything take care in using the 64 if you got 64 gb
After let it boot, check if you can get reception. If that works, fastboot flash recovery of 2.8.6.0. or 2.8.7.05 and go back to whatever rom you want
Sent from my A0001 using Tapatalk
I was on 5.1.8 and updated to 5.1.9 but for some reason the phone boots, goes to the OS but immediately shows the shutting down dialog box and reboots the phone to recovery.
I tried reinstalling 5.1.9 with and without root but have the same result. I have tried with and without permanent twrp. The only thing I haven't tried is a factory reset as I am abroad and cannot afford to lose all my info (especially whatsapp as I won't be able to set it back up until 2 weeks when I return home).
Has anyone encountered anything like this or know how to fix it?
toyanucci said:
I was on 5.1.8 and updated to 5.1.9 but for some reason the phone boots, goes to the OS but immediately shows the shutting down dialog box and reboots the phone to recovery.
I tried reinstalling 5.1.9 with and without root but have the same result. I have tried with and without permanent twrp. The only thing I haven't tried is a factory reset as I am abroad and cannot afford to lose all my info (especially whatsapp as I won't be able to set it back up until 2 weeks when I return home).
Has anyone encountered anything like this or know how to fix it?
Click to expand...
Click to collapse
Share this with OnePlus team on Twitter too until someone help you here too.
If MTP supported by your TWRP then copy the data? If TWRP is still there.
mjp93 said:
Share this with OnePlus team on Twitter too until someone help you here too.
If MTP supported by your TWRP then copy the data? If TWRP is still there.
Click to expand...
Click to collapse
MTP doesn't work but adb works. I have reinstalled 5.1.9 after doing a full wipe and still the phone reboots to recovery after trying to boot normally.
Can anyone help me please :crying::crying::crying::crying:
toyanucci said:
I was on 5.1.8 and updated to 5.1.9 but for some reason the phone boots, goes to the OS but immediately shows the shutting down dialog box and reboots the phone to recovery.
I tried reinstalling 5.1.9 with and without root but have the same result. I have tried with and without permanent twrp. The only thing I haven't tried is a factory reset as I am abroad and cannot afford to lose all my info (especially whatsapp as I won't be able to set it back up until 2 weeks when I return home).
Has anyone encountered anything like this or know how to fix it?
Click to expand...
Click to collapse
Just dirty flash 5.1.8 system update in TWRP, reflash TWRP, reboot recovery, flash magisk. You shouldn't have to wipe data if there were no problems in previous OS and forcing a shutdown shouldn't be due to data anyway. You could also try to dirty flash 5.1.9 again with those steps. Has to be the full ROM.
mikex8593 said:
Just dirty flash 5.1.8 system update in TWRP, reflash TWRP, reboot recovery, flash magisk. You shouldn't have to wipe data if there were no problems in previous OS and forcing a shutdown shouldn't be due to data anyway. You could also try to dirty flash 5.1.9 again with those steps. Has to be the full ROM.
Click to expand...
Click to collapse
I'm travelling and the hotel wifi is super slow. I have the full 5.1.9 and I've tried dirty flashing and clean flashing (I did a nandroid backup first). With a dirty flash the phone boots to the lockscreen but immediately says shutting down and reboots, after the reboot it goes to recovery (stock or twrp whichever is installed). After a clean flash it seems to try to boot then just shuts off and reboots to whichever recovery is installed.
I've set 5.1.8 to download which will take HOURS so I'll report back with any update. I pray this fixes it...
toyanucci said:
MTP doesn't work but adb works. I have reinstalled 5.1.9 after doing a full wipe and still the phone reboots to recovery after trying to boot normally.
Can anyone help me please :crying::crying::crying::crying:
Click to expand...
Click to collapse
In thw worst case, since ADB works, you can backup your entire internal storage to your computer and factory reset. Use adb-sync for this.
Pat123 said:
In thw worst case, since ADB works, you can backup your entire internal storage to your computer and factory reset. Use adb-sync for this.
Click to expand...
Click to collapse
I did a factory reset (didn't wipe internal storage) after doing the nandroid backup and it had the same issue where it tried to boot then screen went black and it rebooted to recovery
mikex8593 said:
Just dirty flash 5.1.8 system update in TWRP, reflash TWRP, reboot recovery, flash magisk. You shouldn't have to wipe data if there were no problems in previous OS and forcing a shutdown shouldn't be due to data anyway. You could also try to dirty flash 5.1.9 again with those steps. Has to be the full ROM.
Click to expand...
Click to collapse
5.1.8 should be flashed again over current 5.1.8?
Why not just tell twrp to switch back to other slot with working oos. I am missing something that this was not tried yet?
MrSteelX said:
Why not just tell twrp to switch back to other slot with working oos. I am missing something that this was not tried yet?
Click to expand...
Click to collapse
I tried changing slots in twrp. Slot A boots to lockscreen then powers off and boots to recovery. Slot B doesn't boot at all and just shows a light blue notification LED.
toyanucci said:
I did a factory reset (didn't wipe internal storage) after doing the nandroid backup and it had the same issue where it tried to boot then screen went black and it rebooted to recovery
Click to expand...
Click to collapse
I meant take backup through ADB, format everything including data, internal storage, then fastboot flash full ROM zip.
I am having the same exact issue.
Can't restore a nandroid backup. All I get is light blue notification LED. I tried 5.1.8 and 5.1.9. With TWRP right after and without it. Without even magisk. It just bootloops forever. If I install 5.1.9/5.1.8 full zips, twrp, reboot recovery, magisk. It just reboots into twrp. I can't even install any of the full ota zips. It wont get past the android boot animation when I just want to flash the ota zip only. Can't get out of twrp. Luckily I was able to backup everything, but don't know how to proceed further allowing me to regain usage of my phone.
To me, this is sounding like something did not flash right with vendor partition.
if a full wipe of System, data, internal storage, the whole 9 yards doesn't work. The only option I see that should work is the mega unbrick thread. https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
MrSteelX said:
To me, this is sounding like something did not flash right with vendor partition.
Click to expand...
Click to collapse
Any suggestions how to fix this. I am hoping I dont have to use the MSM tool and start all the way from scratch.
garz said:
Any suggestions how to fix this. I am hoping I dont have to use the MSM tool and start all the way from scratch.
Click to expand...
Click to collapse
Did you make sure the download was not corrupt before flashing? OnePlus6Oxygen_22_OTA_013_all_1807130145_92ea1c670c0fae.zip MD5 61EAE0DA48C6B3914F48F3E6EA99A74B
Yes, everything matched up. I guess I need to start from scratch.
---------- Post added at 10:25 AM ---------- Previous post was at 10:08 AM ----------
This guy's tool worked like a champ for me. Didn't have to delete everything in storage.
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665/
garz said:
Yes, everything matched up. I guess I need to start from scratch.
---------- Post added at 10:25 AM ---------- Previous post was at 10:08 AM ----------
This guy's tool worked like a champ for me. Didn't have to delete everything in storage.
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665/
Click to expand...
Click to collapse
Funny, I was about post that link but i see you found it first. It is also good that it fixed it for you.
As far as TWRP backups, you only need to backup data. You can just install the full ROM zip file and restore data to get everything back if you have issues with nandroid restore. Just don't forget to flash TWRP before rebooting or you will need to fastboot it again.
Maybe an issue with battery calibration. Try checking the battery when the phone just boots. If it says low battery and because of that its shutting down then its just a software error and just try to turn in the phone with charger connected to check if tgats the problem. If that dosent work try the oneplus 6 mega unbrick guide and return to stock oos 5.1.5 using snapdragon msm recovery tool. For detailed info see tge OP6 unbrick guide on xda. Tell me if it works
toyanucci said:
I tried changing slots in twrp. Slot A boots to lockscreen then powers off and boots to recovery. Slot B doesn't boot at all and just shows a light blue notification LED.
Click to expand...
Click to collapse
One question, when you manually change to slot B, you're in a black screen with blue notification LED right? If that doesn't even go fastboot, how do you get out of that slot into the other one again to the boot-recovery loop?
Hello, i'm a bit in trouble with my internal storage.
Yesterday i wanted to update to newest havoc os so i prepared as usual and wiped system and data under advanced wipe in TWRP ( twrp-3.2.3-0-enchilada(mtp) from joemossjr ).
Then things went strange... op6 reboots itself and since there was no system installed got stuck. i rebooted to TWRP and it started like first time install.
I wanted to do the TWRP Setup but TWRP freezes everytime and after some seconds the device reboots.
I tried different TWRP (joemossjr, eng.stck), tried flashing manually with fastboot flash boot_a twrp.img fastboot flash boot_b twrp.img and even with Tool All In One from mauronofrio
but only recovery that doesn't freeze is newest official TWRP 3.2.3.0.
But now i can't get access to my internal storage. The TWRP filemanager and adb shell are showing weird folders ( see attached jpg ).
It seems something is corrupted... i also tried to flash stock op6 rom in fastboot "OnePlus6Oxygen_22_OTA_015_all_1808102118_770880-FASTBOOT" with flash-all-partitions-fastboot.bat.
Seems to work but got stuck at bootanimation...
flashed back official TWRP and i think i have to install magisk now but don't know how to do because i have no access to my internal storage.
at this point i wish they would have included a sdcard slot
suggestion anyone?
It's not corrupted, but it's encrypted, when you flashed the havoc rom you kinda ****ed up with the encryption method so now you got files that are encrypted and that you can't decryp, so your solution is to format your internal storage, sorry for you, and if anyone have another solution i would take it
do an adb sideload for magisk zip , that should help
adb sideload sadly doesn't work, just "Starting ADB Sideload feature" ...
and on cmd when i try to adb sideload i got an "error: closed"
can't figure out why the files should be encrypted... makes no sense to me
now i flashed flash-system-boot-vendor.bat
phone boots till startup wizard and then after few seconds freeze and reboot
gdre said:
now i flashed flash-system-boot-vendor.bat
phone boots till startup wizard and then after few seconds freeze and reboot
Click to expand...
Click to collapse
Format data. Problem fixed. This is the ONLY SOLUTION that will work.
Yup, you need to format the data and start all clean and i hope you did a full twrp backup
yes i do always make a backup before flashing something... my problem is i don't have access to files on internal storage.
Data partition is not my problem because all my apps are stored with titanium backup but in the freaking internal memory.
i wiped data partition but it doesnt help... now i have all folders like after complete reset. but i dont know how to get access to my old files in /sdcard folder.
i think of deleting internal storage also and start from scratch and try some data recovery tools... maybe i have some luck.
use Tool all in one
gdre said:
yes i do always make a backup before flashing something... my problem is i don't have access to files on internal storage.
Data partition is not my problem because all my apps are stored with titanium backup but in the freaking internal memory.
i wiped data partition but it doesnt help... now i have all folders like after complete reset. but i dont know how to get access to my old files in /sdcard folder.
i think of deleting internal storage also and start from scratch and try some data recovery tools... maybe i have some luck.
Click to expand...
Click to collapse
Did you ever actually try to flash the Havoc update? What's going on is that you flashed a rom on the August security patch and OOS is still on July. You can't roll back to an earlier patch. Only a rom on the current patch will work.
If it doesn't work, as several have said, you have to format data, not just wipe. That will unfortunately, erase everything on your phone, but there's no other way to go back to OOS.
ok iElvis... things start getting interesting
hmm i want to try that but how should i be able to do that...
how does it work flashing the havoc with all in one tool or could it be done in fastboot mode per cmd?
the phone came with oos 5.1.5 and used that a while then with xXx NoLimits 2.4 over it for a few weeks.
after that havoc os from 6.8.18 for a month or so and i want that as daily driver.
then yesterday updated with fresh install to version from 28.8.18 and setup everything then after reboot wifi was complete dead and SIM also.
flashed newest smurf kernel over and all worked again till next reboot.
i decided to install again from scratch and thats the point where things getting weird...
gdre said:
ok iElvis... things start getting interesting
hmm i want to try that but how should i be able to do that...
how does it work flashing the havoc with all in one tool or could it be done in fastboot mode per cmd?
the phone came with oos 5.1.5 and used that a while then with xXx NoLimits 2.4 over it for a few weeks.
after that havoc os from 6.8.18 for a month or so and i want that as daily driver.
then yesterday updated with fresh install to version from 28.8.18 and setup everything then after reboot wifi was complete dead and SIM also.
flashed newest smurf kernel over and all worked again till next reboot.
i decided to install again from scratch and thats the point where things getting weird...
Click to expand...
Click to collapse
Yep, that's the security patch issue. Once you're on a patch, going back to an earlier one will break encryption. I don't believe there's any other option beyond formatting data.
iElvis said:
Yep, that's the security patch issue. Once you're on a patch, going back to an earlier one will break encryption. I don't believe there's any other option beyond formatting data.
Click to expand...
Click to collapse
ok... formated whole storage and installed OnePlus6Oxygen_22_OTA_012_all_1806140300_e4bacf-FASTBOOT_5.1.8.
but while first setup stll freeze and reboot. also wiped again with stock recovery with no change.
bootloader is unlocked... should i now flash patched boot image with magisk for 5.1.8?
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Using this will save you time before you **** something up
gdre said:
Hello, i'm a bit in trouble with my internal storage.
Yesterday i wanted to update to newest havoc os so i prepared as usual and wiped system and data under advanced wipe in TWRP ( twrp-3.2.3-0-enchilada(mtp) from joemossjr ).
Then things went strange... op6 reboots itself and since there was no system installed got stuck. i rebooted to TWRP and it started like first time install.
I wanted to do the TWRP Setup but TWRP freezes everytime and after some seconds the device reboots.
I tried different TWRP (joemossjr, eng.stck), tried flashing manually with fastboot flash boot_a twrp.img fastboot flash boot_b twrp.img and even with Tool All In One from mauronofrio
but only recovery that doesn't freeze is newest official TWRP 3.2.3.0.
But now i can't get access to my internal storage. The TWRP filemanager and adb shell are showing weird folders ( see attached jpg ).
It seems something is corrupted... i also tried to flash stock op6 rom in fastboot "OnePlus6Oxygen_22_OTA_015_all_1808102118_770880-FASTBOOT" with flash-all-partitions-fastboot.bat.
Seems to work but got stuck at bootanimation...
flashed back official TWRP and i think i have to install magisk now but don't know how to do because i have no access to my internal storage.
at this point i wish they would have included a sdcard slot
suggestion anyone?
Click to expand...
Click to collapse
This was happens every day after when i try to mod my device.
When i see weired Folder. I boot to fastboot then flash fastboot twrp. Img.(this will shows all folders with normal names)
Then flash liquid remix rom(its my saviour)
Then flash twrp.Installer.
Then reboot to Recovery and restore my liquid rom backup and boom its boot to everything normal.
Here i want to say that keep one liquidremix rom in otg pendrive.
After fastboot twrp command when u gets working twrp.
Install that rom via otg, and flash twrp installer and then reboot back to twrp and then clean flash rom u want it will work without doing formatting or fastboot flashing stock rom which erase everything everytime
@ whizeguy... did that as mentioned before and gave me the freeze after first time reboot
@ pankspoo... ok i cant understand what is causing this issue but if you say that did the trick for you than i will buy me a otg adapter and check that out.
silly that i already deleted everything and sadly with no affort...
but i dont understand why im not able to boot anymore even after deleting everything
gdre said:
@ whizeguy... did that as mentioned before and gave me the freeze after first time reboot
@ pankspoo... ok i cant understand what is causing this issue but if you say that did the trick for you than i will buy me a otg adapter and check that out.
silly that i already deleted everything and sadly with no affort...
but i dont understand why im not able to boot anymore even after deleting everything
Click to expand...
Click to collapse
Fastboot method of installing rom will work 100%, have u used flash all. Bat (just unzip ur downloaded fastboot rom, connect phone to comp in fastboot mode and click on flash all bat file) command while installation.
Use that command because u have soft bricked u r device.
That installation will boot to normal oos rom.
I think u r doing something wrong.
Hmm thats exactly what i did.
In cmd there are some errors like sparse blabla but finally it completes but with freeze and reboots during startup assistent.
I bought an otg adapter today. Flashed liquid remix and that worked! All seems fine no freezes and reboots but wifi and signal still broken...
Very confusing
gdre said:
Hmm thats exactly what i did.
In cmd there are some errors like sparse blabla but finally it completes but with freeze and reboots during startup assistent.
I bought an otg adapter today. Flashed liquid remix and that worked! All seems fine no freezes and reboots but wifi and signal still broken...
Very confusing
Click to expand...
Click to collapse
U have u r efs backup? If have then restore it via twrp.
That will give u ur signal and wifi
That is what im thinking of...in fastboot there are no infos at bootloader and baseband Version. unfortunately my efs Backup is gone since internal storage messed up.
If i could recover some data that could help but 2 tools i tried yet didnt work.
Tomorrow ill try making raw dump and see If this would help.. still looking for the best guide or method
I got my OnePlus 7 Pro today and tried to install Magisk by patching the boot.img. After trying to flash the patched image, I now have an issue where rebooting the devices leads me straight back to the bootloader. Trying to enter recovery also leads me straight back to the bootloader. I tried flashing the original boot.img I extracted from the OTA update file provided by OnePlus, but it still isn't working. I do not have TWRP or any custom recovery installed. Any help would be much appreciated. I noticed similar threads, however they all installed twrp, though I haven't yet as trying to run "fastboot boot twrp.img" always resulted in it booting to a screen saying "fastboot mode" which wasn't terribly helpful.
Edit: Its not the tmobile/5g/carrier version. I purchased it through OnePlus' website though I forget the exact model number.
Well, "fastboot boot twrp.img" does not work on all devices, sometimes you have to use: fastboot flash boot insert_twrp_img_name_here.imgLearned that the hard way, also use the unofficial twrp from mauronofrio.
Had the same problem as you have, and fixed it with that unofficial twrp.
Faith1105 said:
Well, "fastboot boot twrp.img" does not work on all devices, sometimes you have to use: fastboot flash boot insert_twrp_img_name_here.imgLearned that the hard way, also use the unofficial twrp from mauronofrio.
Had the same problem as you have, and fixed it with that unofficial twrp.
Click to expand...
Click to collapse
Did you need to completely revert to stock after the issue, or did flashing twrp fix the fastboot loop?
Edit: Trying to flash the stock fastboot rom currently as flashing twrp did nothing probably because me trying to fix it broke everything. Hopefully the stock rom will get everything back to a working state where I can try again, just this time flashing twrp.
Also using windows this time instead of linux....
mnbvcxzl90 said:
Did you need to completely revert to stock after the issue, or did flashing twrp fix the fastboot loop?
Edit: Trying to flash the stock fastboot rom currently as flashing twrp did nothing probably because me trying to fix it broke everything. Hopefully the stock rom will get everything back to a working state where I can try again, just this time flashing twrp.
Also using windows this time instead of linux....
Click to expand...
Click to collapse
Ok, so, trying to restore stock seems to have failed miserably.... any advice is most welcomed qq
OK.... so trying to unbrick the device using the msm stuff, I couldn't even make it to the downloader screen. After holding volume +/- and powering off, my screen is now black HOWEVER the phone gets detected by windows when I plug & unplug it. I have no idea what to do anymore. Someone please help
Figured I'd give the solution here in case someone else is in the same exact problem as me:
Follow the instructions over at https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I tried to de-brick it using the fastboot roms and all that, no dice. The only thing that seems to have worked was following the above and using the msm tool. Everything wiped, but hey, at least the phone is bootable again and now I have a way to fix it should this happen again. Yay for happy endings.
Edit: Also, following Faith1105's advice, flashing twrp to boot instead of trying to just boot it first worked successfully and from there I was able to install magisk.
Edit 2: Now wifi isn't working.... why life, why...
Edit 3: OK: EVERYTHING IS GOOD NOW. Twrp ran into a boot loop issue, used twrp to flash the most recent android 10 zip, rebooted and was greeted by stock recovery, then used that to wipe absolutely everything and reboot. After skipping through initial setup and making use wifi was working I rebooted again and this time tried booting twrp the way the usual instructions say to, this time it worked for whatever reason so once that started I used twrp to flash twrp's installer and magisk. It looks like everything is working correctly now. If you have the same issue maybe this stuff will work for you or maybe not: I don't know, and honestly I'm now brain dead lol.
My Phone was running Android 11 perfectly fine. Has been for about a week and a half, and I've decided that I don't like the OS. I was going to flash a custom ROM and went to create a nandroid before flashing. Literally all I did was boot into recovery and TWRP got stuck in a bootloop, the TWRP splash screen appears, crashes and then reappears about 2 seconds later, now when I try to boot back into system, TWRP appears instead and continues to bootloop. I can enter fastboot mode but that's all.
So far I've tried
Booting TWRP through fastboot. Failed another bootloop.
Rebooting through ADB. Boots into TWRP.
Rebooting Bootloader. Seems to do nothing.
Does anyone have any ideas on how to fix this ? It seems strange to me that something as simple as booting recovery could do this much harm. I also have a nandroid backup stored on the device from about a month ago, so the data loss wouldn't be THAT major, but I'm also not sure how I could access it without system or recovery access.
Hi , Which version of TWRP use? I think there is an update a new version TWRP 3.5.2 , Try to flash it. if its still not booting try to boot the original Boot of OOS11.
May be this threads will help you.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
humood96 said:
Hi , Which version of TWRP use? I think there is an update a new version TWRP 3.5.2 , Try to flash it. if its still not booting try to boot the original Boot of OOS11.
May be this threads will help you.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
Click to expand...
Click to collapse
New version does not work as well. Flash the stock boot img to get out of bootloop.
Jacobo123 said:
My Phone was running Android 11 perfectly fine. Has been for about a week and a half, and I've decided that I don't like the OS. I was going to flash a custom ROM and went to create a nandroid before flashing. Literally all I did was boot into recovery and TWRP got stuck in a bootloop, the TWRP splash screen appears, crashes and then reappears about 2 seconds later, now when I try to boot back into system, TWRP appears instead and continues to bootloop. I can enter fastboot mode but that's all.
So far I've tried
Booting TWRP through fastboot. Failed another bootloop.
Rebooting through ADB. Boots into TWRP.
Rebooting Bootloader. Seems to do nothing.
Does anyone have any ideas on how to fix this ? It seems strange to me that something as simple as booting recovery could do this much harm. I also have a nandroid backup stored on the device from about a month ago, so the data loss wouldn't be THAT major, but I'm also not sure how I could access it without system or recovery access.
Click to expand...
Click to collapse
Did your problem got solved?As i updated to A11 a few days ago and am facing the same problem since.Did flashing the new version of twrp worked for you?
Jacobo123 said:
My Phone was running Android 11 perfectly fine. Has been for about a week and a half, and I've decided that I don't like the OS. I was going to flash a custom ROM and went to create a nandroid before flashing. Literally all I did was boot into recovery and TWRP got stuck in a bootloop, the TWRP splash screen appears, crashes and then reappears about 2 seconds later, now when I try to boot back into system, TWRP appears instead and continues to bootloop. I can enter fastboot mode but that's all.
So far I've tried
Booting TWRP through fastboot. Failed another bootloop.
Rebooting through ADB. Boots into TWRP.
Rebooting Bootloader. Seems to do nothing.
Does anyone have any ideas on how to fix this ? It seems strange to me that something as simple as booting recovery could do this much harm. I also have a nandroid backup stored on the device from about a month ago, so the data loss wouldn't be THAT major, but I'm also not sure how I could access it without system or recovery access.
Click to expand...
Click to collapse
At first.- Stable TWRP is not available til now for OOS11
For TWRP to work your device must be decrypted.
This link will help you, will get full details
- https://forum.xda-developers.com/t/...-oneplus-7-pro.3931322/page-152#post-84727891
For more questions and help, please post in that twrp thread only
Regards