Related
Now it's my turn. Pressed factory reset by accident in boot loader. Can get to TWRP but it says E: Unable to mount storage
e:Unable to mount /sdcard/TWRP/twps. when trying to read settings file. etc...
Advanced File manager in TWRP shows /sdcard/TWRP
Any ideas???? If I try to mount data in TWRP my Mac wants to initialize.
Thanks
TWRP shows internal storage 0 mb
I flashed the stock recovery, then ran it and somehow it booted right into CM11. Everything was lost, but it's working again.
Factory reset wipe everything! Including SD card.
null0seven said:
Factory reset wipe everything! Including SD card.
Click to expand...
Click to collapse
Possibly, but how come CM11 was still on there? I think that the Boot Loader in Moonshine's factory reset is not compatible with CM11. Luckily the stock recovery fixed things for me.
808phone said:
Possibly, but how come CM11 was still on there? I think that the Boot Loader in Moonshine's factory reset is not compatible with CM11. Luckily the stock recovery fixed things for me.
Click to expand...
Click to collapse
I had the same issue, pressed by mistake factory reset in bootloader some time ago. I was pressing vol down to reach recovery, there was a slight lag and I pressed it a second time the immediately I've pressed power...so cursor has jumped 2 rows then executed. I've solved it only by flashing stock recovery and resetting to factory settings again, then flashed TWRP.
Now why you still had CM11...well not 100% sure but in TWRP when you wipe to factory the system partition is not formatted. I've paid attention once to the messages during a wipe and it was formatting data, cache, dalvik and android secure but not system. A reason can be that while flashing any ROM, the install script formats system at the beginning so theres no need to do that with factory reset.
Now I can only think that the factory reset from bootloader does the same and system is not wiped. Theoretically it is correct...system is read only especially on a stock non rooted device and resetting it to factory practically means that any trace of personal settings/aps and so on should be erased. And those are not stored on the system partition. There is also no hidden place on the phone where a recovery image of the original android OS is kept so this is not like on the laptops where you reset to factory and Windows is reinstalled from the recovery partition. My guess is that the factory reset just wipes all partitions that contain personal data and settings and leave system intact. So after a wipe and reboot is like you first start it.
You still had CM11 cause the wipe didn't format system...If anyone has a better explanation I would be glad to hear it. So From my point of view nothing went wrong and has nothing to do with the Maximus recovery or it's compatibility with CM11. It would have happen the same if you have used any other stock recovery
Factory reset, resets youre phone to original settings.
Anyway, its good that the phone works.
null0seven said:
Factory reset, resets youre phone to original settings.
Anyway, its good that the phone works.
Click to expand...
Click to collapse
Yes. And it is not formatting system when doing this. So any os is installed will be kept
Sent from nowhere over the air...
Rapier said:
Yes. And it is not formatting system when doing this. So any os is installed will be kept
Sent from nowhere over the air...
Click to expand...
Click to collapse
I don't want to try it again but I wonder if moonshine's factory reset is incompatible with cm11?
Dont understand what do you mean by "incompatible". The factory reset from bootloader is not the same thing as the one from a custom recovery. You shouldn't do a factory reset from bootloader regardless of the ROM you're using
Moonshine is an S-Off method, I didn't used it myself so I don't know what factory reset option is in there
Sent from nowhere over the air...
I never said anything about the custom recovery. If you should never use it, why is it there and why does it make the SD card not available?
Wow, HTC says you can use it here:
http://www.htc.com/us/support/htc-one-x-att/howto/313779.html
I'm sure you know something others like me don't, but I when I mean "incompatible" I mean that I don't believe that it should make the sdcard unavailable and make the phone think it has zero MB. I think what you might have missed is that I used factory reset from the custom boot loader from moonshine. I was wondering if that factory reset was compatible - that's all.
Again, it was a mistake - it's not like I chose it on purpose. Thank you for the help.
808phone said:
I never said anything about the custom recovery. If you should never use it, why is it there and why does it make the SD card not available?
Wow, HTC says you can use it here:
http://www.htc.com/us/support/htc-one-x-att/howto/313779.html
I'm sure you know something others like me don't, but I when I mean "incompatible" I mean that I don't believe that it should make the sdcard unavailable and make the phone think it has zero MB. I think what you might have missed is that I used factory reset from the custom boot loader from moonshine. I was wondering if that factory reset was compatible - that's all.
Again, it was a mistake - it's not like I chose it on purpose. Thank you for the help.
Click to expand...
Click to collapse
The reset to factory from bootloader exists because on stock ROM there's no custom recovery that has that option....so it's in bootloader. For it to work properly though, you must have the stock recovery also. If you have a custom recovery like twrp/cwm and use the wipe from bootloader it'll mess your sd cause phone is not able to perform the wipe properly with that custom recovery. That's why, in order to get back to normal you should flash back stock recovery and perform the wipe from bootloader again.
Sent from nowhere over the air...
Thank you for the clarification. It makes sense. Too bad that reset is so close to the recovery command. It's pretty weird that I didn't have to run the wipe from the stock boot loader again. It ran and rebooted the phone into CM11. Anyway, I am glad I am back to running. Thanks.
Hi,
I have tested the liquidremix rom which is great, but I still wanted to go back to my stock OSS
So I started TWRP, hit restore, everything seem to work fine, but when I reboot the system I'm stuck at the boot animation.
When I reboot the device to TWRP and check the file manager or my backup folder there are only cryptic and weird letters...
How do I restore my backup properly ?
Try to go back to TWRP 3.2.1.0 i think that that works
everything is gone, you will have to restore with the brick tool, happened to me last week and still not sure why, apparently backing up with TWRP you only need to ticket DATA and that's it.
You need to do two things whenever you restore with TWRP. First is factory reset in TWRP before the restore (that will wipe data). Second is restore system, boot, and data ONLY.
The weird file names and cryptic letters is from the encryption from the old rom. I strongly recommend that you invest in an OTG flash drive so you can store TWRP backups on it. Then you can properly wipe the phone. On the plus side this has happened to me before and I never needed anything special like the unbrick tool to get my TWRP backup up and running smoothly.
and there is a better twrp than twrp. The official is by Dees Troy and the un-official one by Joe Moss Jr. is here. https://forum.xda-developers.com/oneplus-6/development/recovery-twrp-3-2-2-0-touch-recovery-t3813317
Joe's big improvement is a usable 'mtp', ie. access that thumb drive.
Also puts the vibration back in to the key press.
First if you r seeing weired letters in twrp like xdjdhdhdhd folders. Then go to fastboot mode flash newest twrp. Img then ij recovery first flash your liquid remix furst, then flash twrp installer zip niw reboot to recovery.
Now factory reset your phone.
Now if you have oos backup. Then restore everything except system.
And then restore system alone at last now reboot it will work.
your gonna need the flashable oos 5.1x which is one here
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
fastboot to twrp
abd push the stock.zip to the phone <-assuming you know this.
and flash it from twrp.
reboot
fastboot twrp again and flash twrp.
this is where decryption comes in handy
Restoring backups with twrp will fail almost all the time. I've yet to do a successful restore and I've tried every method. You're gonna have to flash back to stock OOS and start over.
If anyone has successfully restored more than one backup then I would start a new thread with the exact method you used.
That worked.
I still wonder why not to restore system.
If I take a nandroid backup should one backup
system or system image, data or data image ?
I was trying a new rom the Resurection Remix V6.2.0 Android 8.1.0. i wanted to go back to my TWRP Backup of OOS 5.11 . I wiped data/cache/System . Tried to restore rom . it restored successfully but i didnt do wipe data thing. when i tried to reboot twrp blu, the recovery was lost. then i had to fastboot boot reovery. and lot of wierd folders were created on my phone internal memory. All data lost.
i had to flash the full 5.11 stock zip via twrp. tried to reboot again lost in bootloop. Switched back to stock recovery and make a factory reset then it booted.
switched off the phone back to Blu spark TWRP. again wipe data cache and system. Then restore the TWRP Backup previously double saved on a usb drive. This Time it restored successfully and booted as well fine.
i think i should have made a factory reset or format data before restoring from A Lineage OS Rom OS to OOS TWRP Backup
thats what made the whole internal drive mess and to be formatted as well
My Question is it only important to format data and then restore twrp or also backup and make restore of system.img of OOS backup as well
Something happened to my phone and I succeeded to flash it all new with Android 9.0 which I was on.
But when I try restore twrp backup (data and/or System) I always end up with bootloop.
Tried to reflash Magisk too but doesn't help.
Bootloops right back to TWRP after 2 minutes.
Anyone have any ideas on how I can get my data back from the twrp backup?
Tried to official twrp and bmu_sparks.
Thanks.
timebandi said:
Something happened to my phone and I succeeded to flash it all new with Android 9.0 which I was on.
But when I try restore twrp backup (data and/or System) I always end up with bootloop.
Tried to reflash Magisk too but doesn't help.
Bootloops right back to TWRP after 2 minutes.
Anyone have any ideas on how I can get my data back from the twrp backup?
Tried to official twrp and bmu_sparks.
Thanks.
Click to expand...
Click to collapse
Same thing happened to me yesterday. If you still have access to TWRP, enter it and wipe everything and install newest oxygen pie zip. TWRP is broken for our devie and backups cannot be trusted I'm afraid. Wish I knew this before.
timebandi said:
Something happened to my phone and I succeeded to flash it all new with Android 9.0 which I was on.
But when I try restore twrp backup (data and/or System) I always end up with bootloop.
Tried to reflash Magisk too but doesn't help.
Bootloops right back to TWRP after 2 minutes.
Anyone have any ideas on how I can get my data back from the twrp backup?
Tried to official twrp and bmu_sparks.
Thanks.
Click to expand...
Click to collapse
After restore is complete do not reboot, try the following, it might work,
1-Do not do any wipe,
2-Flash exactly the same ROM which is backed up,
3-Flash twrp,
4-Reboot twrp.
5-Flash Magisk,
8-Reboot system,
In case you are trying to go back from pie to oreo you have to flash roll back rom.
All the best, hope this helps., cheers.
Have tried all that with no luck. But if I do a Factory reset any time after the data restore the phone works but then I dont have any data
This sucks big time.
Have installed all from scratch. Luckly fastboot was working all the time
Some data I could restore with Titanium Backup but not so much I needed/wanted.
Too bad we cant rely on TWRP and its backup/restore feature.
timebandi said:
Have tried all that with no luck. But if I do a Factory reset any time after the data restore the phone works but then I dont have any data
This sucks big time.
Have installed all from scratch. Luckly fastboot was working all the time
Some data I could restore with Titanium Backup but not so much I needed/wanted.
Too bad we cant rely on TWRP and its backup/restore feature.
Click to expand...
Click to collapse
Its good only in the case if you are decrypted, since the time I'm decrypted no such problems, if you want you can try it,
https://forum.xda-developers.com/oneplus-6/how-to/tutorial-decrypt-flash-rom-pie-oreo-roms-t3838643
timebandi said:
Something happened to my phone and I succeeded to flash it all new with Android 9.0 which I was on.
But when I try restore twrp backup (data and/or System) I always end up with bootloop.
Tried to reflash Magisk too but doesn't help.
Bootloops right back to TWRP after 2 minutes.
Anyone have any ideas on how I can get my data back from the twrp backup?
Tried to official twrp and bmu_sparks.
Thanks.
Click to expand...
Click to collapse
Using TWRP backups on this phone is fun but not impossible. This process works for me.
1. Store backups on something other than the phone (I use an OTG card reader and 128 GB SD card)
2. Use a Fastboot Rom of THE EXACT SAME ROM as the backup and let it do it's thing flashing the phone (it will also wipe the phone in the process, which is why you need to store the backup elsewhere)
3. Boot up the phone and go through the whole process of setting it up. Don't worry about installing all your apps.
4. Install TWRP and Magisk if you used it on the backup.
5. Now restore your TWRP backups - just restore system, data, and boot.
I have done this at least 100 times and it has always worked.
I presume the fastboot rom is not only gonna wipe the internal drive but will also lock the bootloader, thats a lot of hassle to do every time you want to restore, but thanks for your suggestions, cheers.
vtec303 said:
I presume the fastboot rom is not only gonna wipe the internal drive but will also lock the bootloader, thats a lot of hassle to do every time you want to restore, but thanks for your suggestions, cheers.
Click to expand...
Click to collapse
The fastboot rom wipes the internal drive but DOES NOT lock the bootloader. Besides, I haven't seen or heard of another way to use TWRP backups without decrypting the phone, and I have security concerns with decrypting the phone.
tabletalker7 said:
The fastboot rom wipes the internal drive but DOES NOT lock the bootloader. Besides, I haven't seen or heard of another way to use TWRP backups without decrypting the phone, and I have security concerns with decrypting the phone.
Click to expand...
Click to collapse
ohh ok, I thought it locks it but thanks for the info, yes thats why I decrypted my device, lets hope in this thread we could find a easy way out to restore sucessfully while encrypted, have you tried just backing up boot, system and data and than restoring it ? cheers
vtec303 said:
ohh ok, I thought it locks it but thanks for the info, yes thats why I decrypted my device, lets hope in this thread we could find a easy way out to restore sucessfully while encrypted, have you tried just backing up boot, system and data and than restoring it ? cheers
Click to expand...
Click to collapse
Yes I tried. Without the fastboot rom to reset everything that stupid encryption bites you in the butt.
Yep. I just restored an entire nandbackup, and now my phone boots to a quailcomm dump screen only, can't fastboot into recovery or anything. Guess my new plans tonight involve fixing this thing.
I also got a bootloop after restoring 8.1 android with twrp 3.3.1 by nemo nemo on my leagoo xrover.
factory reset and wiping everything exept microsd card didnt help...
thanks for some help
vtec303 said:
After restore is complete do not reboot, try the following, it might work,
1-Do not do any wipe,
2-Flash exactly the same ROM which is backed up,
3-Flash twrp,
4-Reboot twrp.
5-Flash Magisk,
8-Reboot system,
In case you are trying to go back from pie to oreo you have to flash roll back rom.
All the best, hope this helps., cheers.
Click to expand...
Click to collapse
Thanks a lot, man. it worked for me
Can anybody help?
My HTC U11 still run on Nougat.
Yesterday I want to update with the newer version of Nougat (Not Oreo)
I already make a data backup with TWRP, big backup 22Gb.
Then I update the new stock Rom from PC, it had no problem.
Go to download mode, and then install TWRP again with ADB from PC.
Go to TWRP Recovery, it still works.
The last thing I do is to try to restore the 22Gb data back to my phone.
And it always get error on 9% with "extractTarFork() process ended with ERROR: 255"
I already change with difference TWRP from 3.1.1.0 to 3.2.3.0, still the same.
Restore to previous version of Nougat with TWRP (system, system image, boot image, recovery). Try to restore backup data again with no luck.
Try to check MD5 with the backup data, and it said matched, no corrupt.
Already try searching in the web, but with no solution too.
Do anyone ever have the same problem and solved it?
A San said:
Can anybody help?
My HTC U11 still run on Nougat.
Yesterday I want to update with the newer version of Nougat (Not Oreo)
I already make a data backup with TWRP, big backup 22Gb.
Then I update the new stock Rom from PC, it had no problem.
Go to download mode, and then install TWRP again with ADB from PC.
Go to TWRP Recovery, it still works.
The last thing I do is to try to restore the 22Gb data back to my phone.
And it always get error on 9% with "extractTarFork() process ended with ERROR: 255"
I already change with difference TWRP from 3.1.1.0 to 3.2.3.0, still the same.
Restore to previous version of Nougat with TWRP (system, system image, boot image, recovery). Try to restore backup data again with no luck.
Try to check MD5 with the backup data, and it said matched, no corrupt.
Already try searching in the web, but with no solution too.
Do anyone ever have the same problem and solved it?
Click to expand...
Click to collapse
Did u try a format in twrp before installing the backup? Just thought
No, not format anything. Afraid did something would make the phone brick.
A San said:
Can anybody help?
My HTC U11 still run on Nougat.
Yesterday I want to update with the newer version of Nougat (Not Oreo)
I already make a data backup with TWRP, big backup 22Gb.
Then I update the new stock Rom from PC, it had no problem.
Go to download mode, and then install TWRP again with ADB from PC.
Go to TWRP Recovery, it still works.
The last thing I do is to try to restore the 22Gb data back to my phone.
And it always get error on 9% with "extractTarFork() process ended with ERROR: 255"
I already change with difference TWRP from 3.1.1.0 to 3.2.3.0, still the same.
Restore to previous version of Nougat with TWRP (system, system image, boot image, recovery). Try to restore backup data again with no luck.
Try to check MD5 with the backup data, and it said matched, no corrupt.
Already try searching in the web, but with no solution too.
Do anyone ever have the same problem and solved it?
Click to expand...
Click to collapse
Try to restore os without data , restart system, and if it works restore data
fabrizio b92 said:
Try to restore os without data , restart system, and if it works restore data
Click to expand...
Click to collapse
I have 2 backup. One is for system and one is data. I can restore system feom TWRP recovery, but can't restore data
After restore system,reboot to twrp and restore data
I had this problem and it took me two days to resolve it. I had a good backup and I know it was good because I had used it several times and it worked. But then after doing some system installs I got the error 255 when I tried to restore it. I tried several things to fix it and nothing worked and I really did not want to lose my backup. What did work for me was to use TWRP wipe function to FORMAT the phone. Wiping or factory reset did not work. I lost the contents of my internal SD card but I was able to transfer most to my external SD card. You could also connect the phone with a cable to a computer and use the pull command in ADB to backup the contents f the internal SD card. Given the choice between losing the SD card and the data files I come to lose some of the SD card. Anyway, a FORMAT worked when nothing else did. I read that this error is caused by a lack of space. When I checked the log it seemed that the restore was failing with a particular file which misled me to thinking I had to remove the corrupt file, but since after the format I was able to restore without any problem, it would seem that there was no corrupt data. Hope this helps someone.
Hey guys,
I have a oneplus 6red rooted with magisk and twrp running oreo 5.1.11, today I decided to enter twrp and reset my phone by whiping dalvic, cache and data.
After reboot, phone screen is totall dark but the light indicator was flashing constantly, entering twrp is no succes, twrp screen is stuck like more then 10 mins. I believe that I cant enter twrp to do something about it. I have downloaded the stock 5.1.11 which is an oreo version
Did I do really something wrong ? if yes or no please let me know how to fix this.
abati said:
Hey guys,
I have a oneplus 6red rooted with magisk and twrp running oreo 5.1.11, today I decided to enter twrp and reset my phone by whiping dalvic, cache and data.
After reboot, phone screen is totall dark but the light indicator was flashing constantly, entering twrp is no succes, twrp screen is stuck like more then 10 mins. I believe that I cant enter twrp to do something about it. I have downloaded the stock 5.1.11 which is an oreo version
Did I do really something wrong ? if yes or no please let me know how to fix this.
Click to expand...
Click to collapse
Try bluespark TWRP and flash your OOS zip again and report back. Maybe a magisk flash will help too.
mikex8593 said:
Try bluespark TWRP and flash your OOS zip again and report back. Maybe a magisk flash will help too.
Click to expand...
Click to collapse
thnx, I entered into fastboot mode, then from my pc I when into the fastboot folder to open cmd and boot twrp from there on my device, from there I followed a tutorial how to adb sideload and flash a rom from your pc. Now its working
But I dont understand why a simpel factory whipe through twrp caused all of this, I only wiped dalvic, cache and data.
abati said:
thnx, I entered into fastboot mode, then from my pc I when into the fastboot folder to open cmd and boot twrp from there on my device, from there I followed a tutorial how to adb sideload and flash a rom from your pc. Now its working
But I dont understand why a simpel factory whipe through twrp caused all of this, I only wiped dalvic, cache and data.
Click to expand...
Click to collapse
This may be a side effect of A/B partitioning and no longer having a recovery partition. Remember TWRP is a part of the boot partition now
tabletalker7 said:
This may be a side effect of A/B partitioning and no longer having a recovery partition. Remember TWRP is a part of the boot partition now
Click to expand...
Click to collapse
what would be an alternative sollution to factory reset your phone without all the troubles i witnessed.
abati said:
after whiping data, phone is stuck and twrp does nothing
Click to expand...
Click to collapse
After a whipping I wouldn't be inclined to do much either!
croques said:
After a whipping I wouldn't be inclined to do much either!
Click to expand...
Click to collapse
what do you mean, could you be more clear and specifiek ?
abati said:
what would be an alternative sollution to factory reset your phone without all the troubles i witnessed.
Click to expand...
Click to collapse
Use a fastboot rom. That will wipe EVERYTHING - and guarantee that you have a usable phone afterwards
abati said:
thnx, I entered into fastboot mode, then from my pc I when into the fastboot folder to open cmd and boot twrp from there on my device, from there I followed a tutorial how to adb sideload and flash a rom from your pc. Now its working
But I dont understand why a simpel factory whipe through twrp caused all of this, I only wiped dalvic, cache and data.
Click to expand...
Click to collapse
You probably wiped system that's why you had nothing to boot into
yldlj said:
You probably wiped system that's why you had nothing to boot into
Click to expand...
Click to collapse
i am almost sure that it was data and dalvic cahce and not system, that is what i also explained in my first post.
But how are you sure that it was system wipe ? did you factory reset your op6 multiple times without issue through twrp ?
phone is fixed btw
abati said:
i am almost sure that it was data and dalvic cahce and not system, that is what i also explained in my first post.
But how are you sure that it was system wipe ? did you factory reset your op6 multiple times without issue through twrp ?
phone is fixed btw
Click to expand...
Click to collapse
Its the easy answer, say that you wiped system or such.
If you wiped Data with Magisk installed, without flashing the stock kernel, you won't be able to boot, since Magisk stores stuff necessary to boot on Data.
Usually, people is stuck on a infinite bucle on TWRP after this, you couldn't even enter TWRP? that's new. The issue you're telling sounds like you changed slot in TWRP somehow to an unused one or something like that, never heard of that.
abati said:
i am almost sure that it was data and dalvic cahce and not system, that is what i also explained in my first post.
But how are you sure that it was system wipe ? did you factory reset your op6 multiple times without issue through twrp ?
phone is fixed btw
Click to expand...
Click to collapse
Yeah I have wiped data in twrp with no issues. TBH it just sounds like there was no system to boot into. Wiping data is just that and shouldn't make the phone unbootable. Also you fixed the issue by flashing OOS which makes me believe this also. If you want to factory reset your phone the best way is to do it through settings.