I have rooted 44s stock. It's been working very well since 44s came out. Last weekend I installed TWRP 2.8.3.0 and all seemed well. Yesterday I installed, via PS, minima red OnePlus boot animation, and flashed the boot logo.bin. The minima animation and logo look nice.
MTP file transfering no longer working reliably, for very long with my MAC, or PC, when the phone is booted into system. MTP breaks off after a very short time, so it is unpredictable if I can even copy small files before the MTP connection is lost. Flagging the MTP check box does no change the problem. On the MAC uninstalling AFT and reinstalling has had no effect. Now, the MTP issue does not occur while in recovery, as I can transfer files with no time or general size issues.
I flashed the stock 38 logo.bin and that solved the red minimum logo.
I can not say exactly if the install of the boot logo/boot animation was the cause of the MTP issues, but they were both in the same several days.
I'd like to solve the MTP connection issue.
Any thoughts would be appreciated.
Thank you.
JeffDC said:
I have rooted 44s stock. It's been working very well since 44s came out. Last weekend I installed TWRP 2.8.3.0 and all seemed well. Yesterday I installed, via PS, minima red OnePlus boot animation, and flashed the boot logo.bin. The minima animation and logo look nice.
MTP file transfering no longer working reliably, for very long with my MAC, or PC, when the phone is booted into system. MTP breaks off after a very short time, so it is unpredictable if I can even copy small files before the MTP connection is lost. Flagging the MTP check box does no change the problem. On the MAC uninstalling AFT and reinstalling has had no effect. Now, the MTP issue does not occur while in recovery, as I can transfer files with no time or general size issues.
I flashed the stock 38 logo.bin and that solved the red minimum logo.
I can not say exactly if the install of the boot logo/boot animation was the cause of the MTP issues, but they were both in the same several days.
I'd like to solve the MTP connection issue.
Any thoughts would be appreciated.
Thank you.
Click to expand...
Click to collapse
The reason you still have the red splash screen after restoring a TWRP backup is because that splash screen (the boot logo.bin) isn't backed up by TWRP, you're aware that TWRP only backs up system, data, and boot, right? The boot that's being backed up is the boot.img (the kernel). So if the logo.bin isn't backed up by TWRP therefore it cannot be restored by TWRP. So what you need to do is grab the stock logo.bin from the 44S fastboot images and flash it manually with fastboot.
In regards to your MTP issues, I'm not sure.
Transmitted via Bacon
timmaaa said:
The reason you still have the red splash screen after restoring a TWRP backup is because that splash screen (the boot logo.bin) isn't backed up by TWRP, you're aware that TWRP only backs up system, data, and boot, right? The boot that's being backed up is the boot.img (the kernel). So if the logo.bin isn't backed up by TWRP therefore it cannot be restored by TWRP. So what you need to do is grab the stock logo.bin from the 44S fastboot images and flash it manually with fastboot.
In regards to your MTP issues, I'm not sure.
Transmitted via Bacon
Click to expand...
Click to collapse
I was not aware of the less than full TWRP backup arena, thank you. I was thinking the logo info was somewhere contained within the various saved TWRP arena directories/caches. I flashed the logo bin and that has returned the correct logos. Interestingly, immediately following flashing the OEM logo.bin, both OPOs file transfer booted into system, as they should on the PC! Not on the Mac.
I'll likely restore both to OEM and reinstall. Mac MTP'ing is my main PC method for communication. Gotta have it working well. I'm guessing the MTP issues remain for the Mac as the (what ever they are) files are not part of the TWRP backup, and remain around (corrupted) somewhere.
edit: but as I discovered re: the MTP issues instead, two bad OPO USB cables. Disappointing. This is the first time I've had USB cables underperform to the point that the basic communication is compromised. Evidently the decrease of performance is less critical on the PC as compared to the Mac. I've been around USB cables since they have been on the market.
Thank you again, Timmaaa.
No problem, glad to help. If you'd like to perform a more thorough backup there's a script in section 10 of my guide thread.
Transmitted via Bacon
Related
HI,
I’ve been having problems with my OPO and I don’t know what to do next.
I was getting stuck in a boot loop – which appeared to be a common issue:
http://www.androidpolice.com/2014/1...den-death-bug-results-neverending-boot-loops/
I had to fastboot oem unlock to run this fix, so I decided whilst I was there to install a custom ROM (SultanROM).
A few days later I got the boot loop issue again, but this time, the fix linked above didn’t work. I thought it wasn’t applying correctly, and so I tried to reinstall the sultan ROM and re-run the Make_Ext4fs fix. Unfortunately, it hasn’t gone well!
The current position is I can now boot in to fastboot or to recovery (TWRP 2.8.7.0), but I think I might have deleted (adb erase) the system partition (because I thought I could easily reflash it, and it wasn’t booting). Now, if I try to boot in to system it gets stuck on the screen with the oneplus logo and doesn’t get any further. I can connect via fastboot (bootloader) or ADB (TWRP). I have used ADB sideload to flash a ROM and I have tried flashing a ROM.ZIP within TWRP but it doesn’t seem to work (most times it cannot mount/find system but sometimes if I “wipe” the phone in TWRP and then flash it *seems* to flash OK (“Operation successful”) but still won’t boot.
Is there a toolkit than can completely rewrite everything on the phone and could fix this? Or any other suggestions?
I don’t have a backup, idiotically as I wasn’t thinking I was doing anything permanent and wasn’t bothered about keeping any of my files.
Thanks!
James
PS – unfortunately my home broadband is broken so I can’t load/try many tools or easily find anything because the only internet access I have is at work, where many things are blocked. I am going over to a friend’s tonight (aprox 5 hours) to try and fix my phone at his house, so any suggestions before that greatly appreciated.
http://forum.xda-developers.com/showthread.php?t=2826541
I would suggest you try taking your phone back to stock COS12.1 and after its installed set it up normally, go back to fastboot and flash a custom recovery, boot TWRP make a backup then proceed to flash a custom ROM. Copy that back up to your computer just in case and also make EFS backups for a rainy day
Sent from my A0001 using Tapatalk
Any way to get "system profiles" tile back in quick settings panel?
Renosh said:
http://forum.xda-developers.com/showthread.php?t=2826541
I would suggest you try taking your phone back to stock COS12.1 and after its installed set it up normally, go back to fastboot and flash a custom recovery, boot TWRP make a backup then proceed to flash a custom ROM. Copy that back up to your computer just in case and also make EFS backups for a rainy day
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Thanks! This process worked and I am back to stock. Unfortunately, still suffering from the boot loop. Frustrating! I'm in touch with OPO Support now... Apparently they can be slow...
jamesking420 said:
Thanks! This process worked and I am back to stock. Unfortunately, still suffering from the boot loop. Frustrating! I'm in touch with OPO Support now... Apparently they can be slow...
Click to expand...
Click to collapse
You probably corrupted your EFS partition somehow. You can try this guide
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
And here I'll link what happened to me and it seems nothing could fix it but these commands from the guide above helped get me out of the bootloop
http://forum.xda-developers.com/showpost.php?p=63611589&postcount=914
Try this stuff if the support guys from OnePlus are unable to help
Renosh said:
You probably corrupted your EFS partition somehow. You can try this guide
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
And here I'll link what happened to me and it seems nothing could fix it but these commands from the guide above helped get me out of the bootloop
http://forum.xda-developers.com/showpost.php?p=63611589&postcount=914
Click to expand...
Click to collapse
Thanks,
That seems to indicate I just need to unlock, flash persist.img and then it should all be OK?
jamesking420 said:
Thanks,
That seems to indicate I just need to unlock, flash persist.img and then it should all be OK?
Click to expand...
Click to collapse
Well it should but if that doesn't work try the options in the second link I posted those worked for me
Sent from my A0001 using Tapatalk
Renosh said:
Well it should but if that doesn't work try the options in the second link I posted those worked for me
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Thanks! And if I erase them (as per second link), do I need to flash them again afterwards?
Reading it again, you mean to erase those two partitions, and then *after* run the flash command. (Initially I thought you meant you ran those two erase commands after you ran the flash command!)
Cheers!
Sorry for the possibly silly question!
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
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
Going to try to give as much information as possible so it will help me figure this out.
I have been working with Renovate module and rom/ Different magisk etc.
The display within the settings has been always messed up and crashes upon using.
So someone suggested a factory reset.
Pre-reset. I did a nandroid backup as well as Titanium backup , and google sync just in case.
Then everything was fine. But had some issues with Magisk installer. Basicly it was not correct and root didn't work correctly.
Flashing some module updates and newest Renovate update.
Then going back to reboot, all of a sudden it goes into fastboot mode.
Tried restarting in recovery , and it would not. It always wants to go to fastboot mode.
Posting and getting some advice (Thanks) they said I bricked my phone.
I tried everything I could to get data that I did a backup of off my phone (This is where I with it was micro SD)
Finally got into TWRP VIA fastboot boot ( had to change active slot) and it was encrypted.....
Booted again using Bluespark via fastboot (Think it was slot b this time) and was able to get a full SD backup onto PC.
Thinking this is going good, I flashed bluespark into slot b?.
Well it never took, and just showed a white light on top , the notification light.
Tried a few flashing VIA fastboot, and last thing I did was fastboot boot an official TWRP, to a slot that worked.
Tried Msmdownloadtool, and various other ways to get stuff going.
Tried Fastboot flashall and fails as well
Can anyone help me get the phone back so recovery works or help in any way?
eracet said:
Going to try to give as much information as possible so it will help me figure this out.
I have been working with Renovate module and rom/ Different magisk etc.
The display within the settings has been always messed up and crashes upon using.
So someone suggested a factory reset.
Pre-reset. I did a nandroid backup as well as Titanium backup , and google sync just in case.
Then everything was fine. But had some issues with Magisk installer. Basicly it was not correct and root didn't work correctly.
Flashing some module updates and newest Renovate update.
Then going back to reboot, all of a sudden it goes into fastboot mode.
Tried restarting in recovery , and it would not. It always wants to go to fastboot mode.
Posting and getting some advice (Thanks) they said I bricked my phone.
I tried everything I could to get data that I did a backup of off my phone (This is where I with it was micro SD)
Finally got into TWRP VIA fastboot boot ( had to change active slot) and it was encrypted.....
Booted again using Bluespark via fastboot (Think it was slot b this time) and was able to get a full SD backup onto PC.
Thinking this is going good, I flashed bluespark into slot b?.
Well it never took, and just showed a white light on top , the notification light.
Tried a few flashing VIA fastboot, and last thing I did was fastboot boot an official TWRP, to a slot that worked.
Tried Msmdownloadtool, and various other ways to get stuff going.
Tried Fastboot flashall and fails as well
Can anyone help me get the phone back so recovery works or help in any way?
Click to expand...
Click to collapse
UPDATE: When booting into TWRP 3.2.2.0 it gives me encrypted files. When booting into TWRP 3.2.3.0 it gives me non-encyrpted files and asks for password.
Booting anything to slot A gives me a load error. failed to authenticate.
Update2: Now I cannot get Bluspark TWRP or stock recovery to load VIA Fastboot. Only TWRP 3.2.3.0 works and loads correctly
Update 3: Keep having to do different versions of TWRP to get anything going, even tried OTA and did not work.
Update 4: Phone wants to boot into Qualcomm HS-USB Diagnostics mode when light is on.
Found you
Next time tag me
I'm the same guy on the oneplus forums
Send me a private message here or on the oneplus forums and I'll take it from there
Update: I have resolved the issue. Please do not post any further comments on this because
The issue is already resolved, duh
Hi, as the title explains I can flash and boot into lineage os but when I try to flash a stock OxygenOS signed flashable zip from this thread (https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244)
and when I boot to system, the screen doesn't show a boot logo, it just goes black for a few seconds before rebooting back to twrp (also if it helps, when it goes to twrp all the files are gibberish, I have to shut off the phone and boot into it from fastboot or I can't see any files).
This all started because I misunderstood the instructions and tried to flash an ota package which then broke the system, it's working now but I'd much rather use OOS as Lineage is missing a lot of the features I'm used to on Oxygen.
I've also tried the "flash-all-partitins-fastboot" from https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 but unfortunately that gave the same issue, it just went back to recovery and wouldn't load OOS.
If anyone has any ideas on how to get back to oxygen that'd be super helpful! I'm considering using the MSM tool but I'd rather not have to start from scratch and lose all my files.
I'm just guessing, but there might be something wrong with your TWRP, did you try re-flashing it?
mati11233 said:
I'm just guessing, but there might be something wrong with your TWRP, did you try re-flashing it?
Click to expand...
Click to collapse
I should've clarified in the post, I mean all the files are gibberish (as in not decrypted I think?) but when I
Code:
fastboot boot twrp.img
it works fine and I can see all the files.
I've probably tried flashing it 4 times through twrp but every time it just does the same thing, boot to system just shows a black screen for a few seconds then reboots to twrp.
I'd love to use blu_spark like everyone recommends but I can't find the blu_spark recovery for the op6, only their kernel.
The reason why it's gibberish is because your device is encrypted and you need to input the password in the twrp to be able to access it. Seems the twrp doesn't detect the encryption correctly so there might be something wrong with it.
Here is the bluespark twrp https://github.com/engstk/android_device_oneplus_enchilada/releases
mati11233 said:
The reason why it's gibberish is because your device is encrypted and you need to input the password in the twrp to be able to access it. Seems the twrp doesn't detect the encryption correctly so there might be something wrong with it.
Here is the bluespark twrp https://github.com/engstk/android_device_oneplus_enchilada/releases
Click to expand...
Click to collapse
I just tried with blu_spark and the same thing happens but I realised something else, twrp only doesn't work on slot A.
If I see that it didn't decrypt the files, I can set B to active, reboot to recovery, and it works perfectly.
I noticed after one of the failed boots it switched the active slot to B even though I had set it to A before flashing. So every time it doesn't show the logo or anything, it sets the active slot from A to B and reboots to recovery.
Also I just looked and from the Backup page, it shows 2.7 GB for system on slot A and 1.7GB on slot B so I'm going to try wiping both and reflashing the flashable signed zip on each then twrp.
UPDATE: Just did that and the twrp installer was giving an error saying unsupported android version so I looked and system is only 4MB after flashing that package (OnePlus6Oxgygen_22_OTA_034_all_...zip), I'm trying an older one (...OTA_026...zip) to see if that actually works.
So I tried with the older one and lineage and they both still left the system partition at 4MB and the blu_spark twrp installer isn't detecting an android version. The system image partition is at 2.6GB if that means anything.
Oh wait more update, I'm dumb and shut off the phone while taking the case off (got stuck and it was pushing the power button) and even though the twrp installer couldn't detect anything and twrp said No OS installed when trying to boot to system, lineage just started up, no problem. I am very confused I miss when there was one system partition.
How are you flashing the OS?
mati11233 said:
How are you flashing the OS?
Click to expand...
Click to collapse
I'm using twrp, blu_spark and normal, and both have the same result. They can flash lineage and it runs fine, but oxygen refuses to boot and just switches the active slot and goes to recovery instead.
I also tried the fastboot rom flashing thing from the thread I linked to in the OP and it's the same thing, just goes back to recovery and wont boot.
P.S. I'm currently copying over /sdcard to an external drive and if I can't figure out how to fix this by the time that's done, I'll just use MsmDownloadTool and start over.
And you are wiping each time before flashing it, right? If it is the case then the download tool is probably the easiest way to go about it, rather than spending days troubleshooting it.
mati11233 said:
And you are wiping each time before flashing it, right? If it is the case then the download tool is probably the easiest way to go about it, rather than spending days troubleshooting it.
Click to expand...
Click to collapse
I've tried it with and without wiping and it always seems to do the same thing either way, works with LOS not with OOS. Thanks for the help! but yeah I think I'm just going to end up using the download tool once everything's over.