Hello,
I have an issue with my phone and any help or insight is appreciated!
I have a Oneplus One. Rooted with TWRP and MultiROM installed. I have two CyanogenMod ROMs installed. One is my primary one where I have all my apps, and another one that is almost empty (has few apps).
Few days ago, my battery drained and I charged it. Then when I turned it on, the phone started booting, passed through the MultiROM window (where you choose the booting ROM), then passed through the Boot animation, and then a screen appears where it says "Preparing Apps x of xxx". After the phone goes through all of my apps (optimizing/preparing them), it shuts down and starts all over again.
This was random. I didn't install a new update or anything. Note, that this only happens with my primary ROM. When I boot to my secondary ROM everything works fine. I had a backup of all my app data (~ 6GB) using Titanium Backup. However, I was running out of space and I deleted the backup from Google Drive few days earlier. I am very unlucky.
I tired the following to fix this issue and nothing helped:
1. Cleared chase and Dalvik chase.
2. Installed a CyanohenMod update. Apparently, my phone wasn't up to date.
3. Drained the battery completely and charged the phone.
4. Booted the phone while charing and while not charging.
I just want to get my apps data back. So is there anyway to fix this issue so that I can boot to my primary ROM?
If not, is there a way to fully backup my apps data in the primary ROM (the one that is not booting) and transfer this backup (install these apps with their data) to another ROM?
I can't back up my apps data using TWRP and save the backup in Internal Storage, because I don't have enough space. Maybe I can back up my apps data to my laptop somehow? Also, if I do a backup through TWRP, will the issue still persist when I do a restore (I am backing up a broken ROM)? I am afraid to do this step because in order to restore through TWRP (after backing up the ROM), I have to delete this broken Primary ROM first due to insufficient amount of space. If it ends up not working I will lose all my data! So I prefer to fix the ROM if possible instead of going through all of this.
Any help is appreciated. Sorry for the long post.
Thank you in advance.
@ali282h
Sorry for the delay and for the issue you are having at the first place.
I read your post completely.
I will answer Your Questions in points:
1)You can take Apps backup , dont worry if the roms works or not.
2)i will suggest you to use a single rom first , dont use multi rom that can make it difficult to analyse the root cause of the bootloop,
3)Use a toolkit called Wug fresh and flash a stock firmware and then check if itss booting correctly or not.If not ???
Follow the 4 step
4)U can boot into the Twrp, then use ADB commands.
Fastboot erase persist
fastboot flash persist persist.img
Again If you have problem You can follow the next step
5)You can type these commands in adb
adb shell
make_ext4fs /dev/block/mmcblk0p15
Report back..... Gudluk
Hello.. I actually ended factory resetting my phone. Thanks for taking the time to write a very helpful answer.
adarsh58 said:
@ali282h
Sorry for the delay and for the issue you are having at the first place.
Report back..... Gudluk
Click to expand...
Click to collapse
Hey thanks for the reply. I am also facing the same issue. Where can I get this persist.img to flash it from fastboot?
This issue keep on popping every week and almost every week I am wiping everything completely and installing new ROM. Kindly help. I am currently using Resurrection Remix 5.7.4 MM. No MutiRom.
Thanks.
i had it, but i dont think it is related to persist as after each update i flash i erase wipe persist folder, tho i did a titanium backup and wiped data/cache/dalvik/system and flashed it all over again.
badboy4a2 said:
Hey thanks for the reply. I am also facing the same issue. Where can I get this persist.img to flash it from fastboot?
This issue keep on popping every week and almost every week I am wiping everything completely and installing new ROM. Kindly help. I am currently using Resurrection Remix 5.7.4 MM. No MutiRom.
Thanks.
Click to expand...
Click to collapse
Hi ali,
Follow this link and get to the post no 8, u will find
https://forums.oneplus.net/threads/afx-zip-containing-persist-img-reserve4-img.198286/
guidoido004 said:
i had it, but i dont think it is related to persist as after each update i flash i erase wipe persist folder, tho i did a titanium backup and wiped data/cache/dalvik/system and flashed it all over again.
Click to expand...
Click to collapse
Ya You may be right :angel::angel:, but correct me if i am wrong
Persist partition is not like other partitions in android like /system,/data,/cache etc.
so integrity checks wont run on it ,results into
"if its get corrupted it will remain corrupted"
in that case we need erase and flash it all over again,
You can do it by typing one line cmd in ur twrp terminal emulator
make_ext4fc /dev/block/mmcblk0p15.
:good::good::good:
LINKS:
http://droid-bug.blogspot.in/2014/10/oneplus-one-boot-loop-0mb-no.html
adarsh58 said:
Ya You may be right :angel::angel:, but correct me if i am wrong
Persist partition is not like other partitions in android like /system,/data,/cache etc.
so integrity checks wont run on it ,results into
"if its get corrupted it will remain corrupted"
in that case we need erase and flash it all over again,
You can do it by typing one line cmd in ur twrp terminal emulator
make_ext4fc /dev/block/mmcblk0p15.
:good::good::good:
LINKS:
http://droid-bug.blogspot.in/2014/10/oneplus-one-boot-loop-0mb-no.html
Click to expand...
Click to collapse
i use commands in the Recovery terminal to do so, as theres not a easy way to do it on the recovery itself
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!
first some back story:
it's been a long time since i did a lot of rooting so i lost a lot of knowledge.
I got the phone close to release in the EU.
There was only BETA stage twrp at the time.
So i flashed this unstable twrp and rooted with magisk.
And i run stock Oxy Rom.
But the main problem is, whenever i boot into recovery, twrp ask me for a password. (i have none) so i press continue.
And it then ask for unmodified system partition. (not sure what to select here)
But when i swipe to allow modification, i can't find the root of the phone? i cannot find the download folder where i flash updates or other modified apk's.
It's all just numbers and random letter. i have no idea on how to proceed or how to update twrp safely without falling into boot loop and other problems.
Some help would be appriciated. Thank you.
saitek1911 said:
first some back story:
it's been a long time since i did a lot of rooting so i lost a lot of knowledge.
I got the phone close to release in the EU.
There was only BETA stage twrp at the time.
So i flashed this unstable twrp and rooted with magisk.
And i run stock Oxy Rom.
But the main problem is, whenever i boot into recovery, twrp ask me for a password. (i have none) so i press continue.
And it then ask for unmodified system partition. (not sure what to select here)
But when i swipe to allow modification, i can't find the root of the phone? i cannot find the download folder where i flash updates or other modified apk's.
It's all just numbers and random letter. i have no idea on how to proceed or how to update twrp safely without falling into boot loop and other problems.
Some help would be appriciated. Thank you.
Click to expand...
Click to collapse
Boot to bootloader, flash original boot img than follow the guide to flash original twrp
Hitman478™ said:
Boot to bootloader, flash original boot img than follow the guide to flash original twrp
Click to expand...
Click to collapse
and which of my problems does this solve?
First of all flash official TWRP now. Makes no sense to use the unofficial version because its not stable.
Enter PW -> decrypt data for TWRP
No PW -> hieroglyphs
I successfully used official twrp, version 3.2.2 and then did a "format data" and then used fastboot again to install the full rom.
Kollachi said:
First of all flash official TWRP now. Makes no sense to use the unofficial version because its not stable.
Enter PW -> decrypt data for TWRP
No PW -> hieroglyphs
Click to expand...
Click to collapse
ok i figured it out, added a password. and now it shows correct folder names etc. thanks.
saitek1911 said:
first some back story:
it's been a long time since i did a lot of rooting so i lost a lot of knowledge.
I got the phone close to release in the EU.
There was only BETA stage twrp at the time.
So i flashed this unstable twrp and rooted with magisk.
And i run stock Oxy Rom.
But the main problem is, whenever i boot into recovery, twrp ask me for a password. (i have none) so i press continue.
And it then ask for unmodified system partition. (not sure what to select here)
But when i swipe to allow modification, i can't find the root of the phone? i cannot find the download folder where i flash updates or other modified apk's.
It's all just numbers and random letter. i have no idea on how to proceed or how to update twrp safely without falling into boot loop and other problems.
Some help would be appriciated. Thank you.
Click to expand...
Click to collapse
U have corrupted u r data partation u have to factory reset along with wiping internal storage and then transfer u r rom File through MTP in sd card of phone and then flash rom.
Or u can flash fastboot flashable rom via fastboot mode.
Then install your official twrp via fastboot mide after installing rom.
Now twrp will detect all data from sd card
pankspoo said:
U have corrupted u r data partation u have to factory reset along with wiping internal storage and then transfer u r rom File through MTP in sd card of phone and then flash rom.
Click to expand...
Click to collapse
Thank you, all i did was add a four digit code when twrp asked me for a password. now the folders are showing up correctly. not just random numbers and letters.
still need to update twrp safely. can i flash a new twrp within twrp or do i need to update via computer?
saitek1911 said:
Thank you, all i did was add a four digit code when twrp asked me for a password. now the folders are showing up correctly. not just random numbers and letters.
still need to update twrp safely. can i flash a new twrp within twrp or do i need to update via computer?
Click to expand...
Click to collapse
U can directly flash new twrp installer in current recovery no problem
saitek1911 said:
and which of my problems does this solve?
Click to expand...
Click to collapse
All of your problems i presume
Can Anyone help me, please? I have somehow the same problem. The phone literally itself without doing anything started doing a download(odin) mode loop. So I deleted data, dalvik, cache, system partitions without internal storage since it has very very important files for me and a lot of projects for the university!!! and before and after the folders in internal storage in twrp shows as random numbers and letters. I don't know why since when the phone was working normally I was protecting it by fingerprint and a password. And when I installed a stock ROM after it without wiping the internal storage. The storage is showing in negative. If anyone can help me this would be super appreciated and helpful. Thank you!
Hitman478™ said:
Boot to bootloader, flash original boot img than follow the guide to flash original twrp
Click to expand...
Click to collapse
Can you help please?
Madara818181 said:
Can Anyone help me, please? I have somehow the same problem. The phone literally itself without doing anything started doing a download(odin) mode loop. So I deleted data, dalvik, cache, system partitions without internal storage since it has very very important files for me and a lot of projects for the university!!! and before and after the folders in internal storage in twrp shows as random numbers and letters. I don't know why since when the phone was working normally I was protecting it by fingerprint and a password. And when I installed a stock ROM after it without wiping the internal storage. The storage is showing in negative. If anyone can help me this would be super appreciated and helpful. Thank you!
Click to expand...
Click to collapse
If it is already showing folders with random file names in the internal storage it means it needs to format data (to remove file encryption) which deletes all files in the internal storage.
Don't wipe system because it removes your OS.
Always secure backup before messing your device.
Hitman478™ said:
Boot to bootloader, flash original boot img than follow the guide to flash original twrp
Click to expand...
Click to collapse
You may try this boot.img just rename to boot.img only.
Credits to RR10 TG channel by Enzo #CatGang.
tiga016 said:
If it is already showing folders with random file names in the internal storage it means it needs to format data (to remove file encryption) which deletes all files in the internal storage.
Don't wipe system because it removes your OS.
Always secure backup before messing your device.
You may try this boot.img just rename to boot.img only.
Credits to RR10 TG channel by Enzo #CatGang.
Click to expand...
Click to collapse
Thanks Man. All my university stuff is in the phone's internal storage so wiping it is no no for me and I need the files today!!! I flashed the boot.img file you attached using TWRP but now the phone is in a boot loop and it did not solve anything!!! Sorry for this but what the f**k should I do man. All my important files are on the phone!!!
Madara818181 said:
Thanks Man. All my university stuff is in the phone's internal storage so wiping it is no no for me and I need the files today!!! I flashed the boot.img file you attached using TWRP but now the phone is in a boot loop and it did not solve anything!!! Sorry for this but what the f**k should I do man. All my important files are on the phone!!!
Click to expand...
Click to collapse
Sorry I thought you are also literally same issues with OP but then it's not. Are you able to reboot to twrp? And what is the whole story of you device? I mean if you are rooted, what ROM you came from and all that you did before the issues occur. And did you tried to switch slot? Since you wiped everything with system included then you have no OS installed. Did you tried to flash OS via OTG? Or flash via fastboot.
I flashed another os without deleting the internal storage but the storage is now showing in negative values. Story is The phone literally itself without doing anything started doing a download(odin) mode loop. So I deleted data, dalvik, cache, system partitions without internal storage since it has very very important files for me and a lot of projects for the university!!! and before and after the folders in internal storage in twrp shows as random numbers and letters. I don't know why since when the phone was working normally I was protecting it by fingerprint and a password. And when I installed a stock ROM after it without wiping the internal storage. The storage is showing in negative and yes I can still boot into twrp
tiga016 said:
Sorry I thought you are also literally same issues with OP but then it's not. Are you able to reboot to twrp? And what is the whole story of you device? I mean if you are rooted, what ROM you came from and all that you did before the issues occur. And did you tried to switch slot? Since you wiped everything with system included then you have no OS installed. Did you tried to flash OS via OTG? Or flash via fastboot.
Click to expand...
Click to collapse
This is the story
Madara818181 said:
This is the story
Click to expand...
Click to collapse
I know that but it seems incomplete. It did not mention what I ask recently. It is always a need for detailed story.
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
Edit: Since I am the impatient guy of course I still meddled with the backup after posting this thread. By chance I found a solution that finally worked for me. Latest Oxygen Os 9.0.2 stable without root.
Note that I will list every step even it may be that it hasn't contributed anything to the solution:
1. From fastboot I booted into latest blu_sparc TWRP.
2. I plugged the phone into USB and copied all files from my backup into the usual TWRP folder.
3. I flashed only DATA, nothing else.
4. From TWRP I rebooted directly into bootloader/fastboot.
5. Then I ram the flash-all-partitions.bat from Mauronofrio provided by this thread https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 .
6. Crucial step: At the beginning, it asks "Wipe all data?". SELECT NO. It will start "restoring" all other partitions.
7. Reboot the phone and it should work as you left it before creating the backup.
Note that this method worked the restoration of backup data from the same OS and same version. Feel free to try it out on other system images. It's ugly and inconvenient, but it seems to work.
Hey guys,
is there a fail safe way to restore data from a clean twrp backup without soft bricks or PIN error?
I tried to restore a very recent TWRP backup but had serious trouble. At first, it rebooted just fine but upon trying to unlock the device with 4-digit pin it suddenly told me that my usual pin isn't working.
Then I tried deleting the lockscreen.db and other related files. Rebooted and got into the OS, but it got stuck at "starting up device".
The I did a complete wipe without internal storage and tried it again. Then it wouldn't even boot and I had to use the flash-all.bat to flash all partitions "manually" to get it working again.
Now I am afraid of using Oneplus 6 if it's impossible to make a seamless backup/recovery. Is there a guide on how to do this?
Thank you in advance!
This is a known issue though. If you want to make a usable backup in TWRP: Remove the PIN (screen lock), do the backup, and then activate the screen lock again.
efex said:
This is a known issue though. If you want to make a usable backup in TWRP: Remove the PIN (screen lock), do the backup, and then activate the screen lock again.
Click to expand...
Click to collapse
I remember having read a thread with this hint too and disabled my security pin in a temporary working OS. Then I did the flashing stuff and I just noticed that my now working restored phone doesn't have a pin anymore. So basically removing this pin on a data backup will make things go smooth? I will keep this in mind, thank you
Hi, i just got my old 5 year old (now retired) device to bootup because someone had made a kernel for the device which supports overclocking so for the fun I wanted to try it
but there was one weird problem, it seemed that though the root permissions from years ago remained just like they were but magisk manager itself had lost root permissions though I was still able to grant root permissions to other applications normally
I was on an unofficial Lineage OS build and thought of returning to original Miui for the device, got the fastboot rom, got Mi flash, flashed it, booted up
but there was a catch, it would always throw an error on the login Miui account screen at startup saying "Couldn't check device security, please try again"
I had tried everything possible including:
adding a Xiaomi account
skipping sign in
Inserting a sim
None of them seemed to do anything so i flashed twrp recovery again as using mi flash to flash ur device's stock rom gets rid of custom recovery
Now here is the mistake I made
**I wiped the device clean using TWRP**
now i tried going into adb sideload mode, no matter what I did my PC wouldn't detect my device, tried going into fastboot mode and still my PC wouldn't recognise the device and same goes for Mi flash tool
additionally the device would automatically exit out of fastboot mode within 2 minutes and go on to the power off screen
I do have charge on the device it says it's at 87% on the TWRP menu
I can no longer bootup, im stuck at the MI logo on bootup
Device: Mi Max 2
Additional notes: I am not in a hurry as that is not my primary device so it is okay if you want to take your time to reply, even if there's no way i can get my phone to see the light of day again it's alright as the phone was retired and sitting collecting dust for 2 years now
I do not wish to visit a service center as it's not worth it for a device I'm just gonna use for a few hours then put it back into its grave again
just download that same, or another custom ROM, and flash it via TWRP (just put ROM in SD card).
Nothing is gone, i mean if you delete system via twrp of course it will bootloop as it don't have system.
And for reverting back to original stock ROM , i think it have to do something with encryption, or maybe just the fact you unlocked bootloader.
Best is to stay away from stock ROM, find some custom ROM which have similar to MIUI (stock rom) , somewhat improved, if you want to get as much stock ROM experience.
kraken-gz said:
just download that same, or another custom ROM, and flash it via TWRP (just put ROM in SD card).
Nothing is gone, i mean if you delete system via twrp of course it will bootloop as it don't have system.
And for reverting back to original stock ROM , i think it have to do something with encryption, or maybe just the fact you unlocked bootloader.
Best is to stay away from stock ROM, find some custom ROM which have similar to MIUI (stock rom) , somewhat improved, if you want to get as much stock ROM experience.
Click to expand...
Click to collapse
Hi, thanks for the reply, I tried using an SD card and unfortunately it wouldn't detect that too, what i found was I didn't wipe System it still shows that it's taking up some place (3597 MB)
i would be fine getting a custom rom on the device infact i have crdroid ready to be installed
could it be that the TWRP i installed (yes I downloaded the latest version and didn't flash the old one i had years ago) have some bugs? (I did install it from official TWRP website)
also note: though you see a Senior Member title below my name, im a complete and utter noob
BR4UTAL said:
Hi, thanks for the reply, I tried using an SD card and unfortunately it wouldn't detect that too, what i found was I didn't wipe System it still shows that it's taking up some place (3597 MB)
i would be fine getting a custom rom on the device infact i have crdroid ready to be installed
could it be that the TWRP i installed (yes I downloaded the latest version and didn't flash the old one i had years ago) have some bugs? (I did install it from official TWRP website)
also note: though you see a Senior Member title below my name, im a complete and utter noob
Click to expand...
Click to collapse
Lol I thought I was the only proper noob here on xda but nice to meet other noobs here too .
I think Kraken-gz is right, once the older devices are OEM off-support its best to stay away from OEM servers, I lost couple of old lesser-known-brand devices to OEM mischief i'd say coz it happened twice to me when I reloaded the original ROMs and tried to connected to the net they went dead on the next bootup, I think the OEMs have something going on there to boot out the older devices so newer ones could be pushed in the market sooner than they were supposed to. Possible.
so, first, in twrp, try to completely format it, follow this to do it
Just, a note: in advanced wipe delete system, data, dalvik cache and cache.
When trying to reboot into system, make sure twrp complains that it have no system. (that way, you know you deleted it)
reboot it, again in twrp.
try to flash custom ROM, should work as it have clean memory.
If it doesnt flash, then make sure to note all log file from twrp while flashing, and post it here, in order to see, what failed in flashing. If it succeds, it should load custom rom . If custom rom dont work, try another one, maybe older, or one that you had previous time (before trying to go into stock rom) (just, to try to boot it somehow. But before trying another custom rom, if one fails, do proper wiping described above.
If that fails try to download oldest stock ROM, and flash it. Maybe newest is blocking it.
If that fails, there is something called EDL mode, when fastboot is not available (for hard brick, like this).
here is video just to give you overview how to do it
and text also
Edit:
WAIT, try to format it, without wiping system. maybe it will boot again.
If not, other solutions are not applicable, if you dont find way to detect that sd card. Only EDL remains.
kraken-gz said:
so, first, in twrp, try to completely format it, follow this to do it
Just, a note: in advanced wipe delete system, data, dalvik cache and cache.
When trying to reboot into system, make sure twrp complains that it have no system. (that way, you know you deleted it)
reboot it, again in twrp.
try to flash custom ROM, should work as it have clean memory.
If it doesnt flash, then make sure to note all log file from twrp while flashing, and post it here, in order to see, what failed in flashing. If it succeds, it should load custom rom . If custom rom dont work, try another one, maybe older, or one that you had previous time (before trying to go into stock rom) (just, to try to boot it somehow. But before trying another custom rom, if one fails, do proper wiping described above.
If that fails try to download oldest stock ROM, and flash it. Maybe newest is blocking it.
If that fails, there is something called EDL mode, when fastboot is not available (for hard brick, like this).
here is video just to give you overview how to do it
and text also
Edit:
WAIT, try to format it, without wiping system. maybe it will boot again.
If not, other solutions are not applicable, if you dont find way to detect that sd card. Only EDL remains.
Click to expand...
Click to collapse
Tried wiping data, cache and dalvik cache and formatting data, none seemed to help
and still no sd card being detected
Now edl mode
I would love to boot into edl mode but the thing is my device isn't being recognised by adb nor is it being recognised by fastboot commands
so that's where I'm stuck for now
OldNoobOne said:
Lol I thought I was the only proper noob here on xda but nice to meet other noobs here too .
I think Kraken-gz is right, once the older devices are OEM off-support its best to stay away from OEM servers, I lost couple of old lesser-known-brand devices to OEM mischief i'd say coz it happened twice to me when I reloaded the original ROMs and tried to connected to the net they went dead on the next bootup, I think the OEMs have something going on there to boot out the older devices so newer ones could be pushed in the market sooner than they were supposed to. Possible.
Click to expand...
Click to collapse
Perhaps that is true