Related
I have a problem restoring my backups. All my recent TWRP backups get stuck in bootloop when I try to restore them. Is there any remedy fopr that?
I'm currently on v 2.7.1.0
Upgrade your version of TWRP. Current on twrp.me is 2.8.7.0, but in the forums here you can find version 2.8.7.2 by @AntaresOne, with F2FS support.
ro-mann said:
I have a problem restoring my backups. All my recent TWRP backups get stuck in bootloop when I try to restore them. Is there any remedy fopr that?
I'm currently on v 2.7.1.0
Click to expand...
Click to collapse
I created the .tar file to flash TWRP 2.8.7.0 for the GT-I9505 via ODIN. Download it: HERE.
Thanks guys!
Will I be able to use my old backups with the new version?
Yes. If you still have issues, the backups are likely corrupt, for reasons unknown.
Regardless of what recovery I used, (yash28, regalstreak, official twrp) or even starting from the scratch( flashing stock OxygenOS using the Oneplus tools) and then reflashing the recovery, my attempts to succesfully load into a ROM has been futile. As of now, I am pretty much unable to boot into any recovery, and I am stuck using the stock OxygenOS. I tried flashing modem, first attempt was clean flashing the new modem, then flashing it dirty after flashing my rom, I tried doing the same thing with the old modem, my attempts have been futile. If anyone could shed light in this situation, it would be great, I would hate to be stuck using the stock OxygenOS rom, and not try out the great roms that are developed. I can however flash oxygenOS stock rom.
i have the same problem and i cant find any solution i thought of starting fromt he scratch as it didnt help u it might not help me too
Have the same, I've done everything. I've made the phone full stock again and still won't boot.
I have finally found the solution to my own problem
Apparently what made this impossible was due to sensors, as I noticed some of my sensors werent working. That could have made me unable to flash anything but OOS. Anyway, the solution is to fastboot erase persist, and reflash persist.img (Instructions are here: http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591). I hope this fixes your guys problem.
abhisek1994 said:
Apparently what made this impossible was due to sensors, as I noticed some of my sensors werent working. That could have made me unable to flash anything but OOS. Anyway, the solution is to fastboot erase persist, and reflash persist.img (Instructions are here: http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591). I hope this fixes your guys problem.
Click to expand...
Click to collapse
So now youre able to flash CM13 without bootloops?
yousuf.shareef said:
So now youre able to flash CM13 without bootloops?
Click to expand...
Click to collapse
Yep! Also make sure you are using official TWRP (https://dl.twrp.me/oneplus2/) Good luck.
abhisek1994 said:
Apparently what made this impossible was due to sensors, as I noticed some of my sensors werent working. That could have made me unable to flash anything but OOS. Anyway, the solution is to fastboot erase persist, and reflash persist.img (Instructions are here: http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591). I hope this fixes your guys problem.
Click to expand...
Click to collapse
FINALLY! Thank you!! Ive been stuck all day without getting ANY MM ROM to boot,. and this ...thing...fixed it! Thanks again
Finally someone found the answer! Unfortunately I wiped whole internal memory and forgot to take backup of whatsapp backup so i lost that. Oh well, all works good now, thank you!
JudderArts said:
Finally someone found the answer! Unfortunately I wiped whole internal memory and forgot to take backup of whatsapp backup so i lost that. Oh well, all works good now, thank you!
Click to expand...
Click to collapse
Dont forget to thank people.
abhisek1994 said:
Dont forget to thank people.
Click to expand...
Click to collapse
JudderArts said:
thank you!
Click to expand...
Click to collapse
That's exactly what I did.
I think i faced the same problem, im using h2os 6.0.1 close beta, with twrp 3.0, but without rooting. I can restore my rom tru twrp without problem. But my try to flash grarak cm13 and new mokee os 6.0 ended up with bootloops, both stuck at oneplus logo
abhisek1994 said:
Apparently what made this impossible was due to sensors, as I noticed some of my sensors werent working. That could have made me unable to flash anything but OOS. Anyway, the solution is to fastboot erase persist, and reflash persist.img (Instructions are here: http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591). I hope this fixes your guys problem.
Click to expand...
Click to collapse
Do you have to go back to the stock rom before flashing persist and then install cm13? or can i do it while i am on the boot logo screen...i tried going into fastboot while stuck on the boot logo (which i was able to) and flashed persist and rebooted but it is still stuck on the boot logo screen
muthukumarc said:
Do you have to go back to the stock rom before flashing persist and then install cm13? or can i do it while i am on the boot logo screen...i tried going into fastboot while stuck on the boot logo (which i was able to) and flashed persist and rebooted but it is still stuck on the boot logo screen
Click to expand...
Click to collapse
You have to downgrade fastboot/bootloader to the Lollipop one (just flash the usual revert_to_lollipop.zip found in these forums as usual).
Title explains it all, I recently installed TWRP so I could edit build.prop to get the google assistant. It worked btw, but I wanted to flash the pixel launcher and when I did, I rebooted and it gave me: encryption unsuccessful. I read online that i should just say yes and just wipe cache in twrp. It asked for a password in TWRP so i pressed cancel and I wiped cache. Boom! I was stuck in a TWRP bootloop. Now I tried to wipe everything but I wiped /system. Somebody please please please help me!
As long as you have access to TWRP you should be able to recover. If you need to restore the system partition you could use this DEODEX version. Follow thread instructions (download RAR, extract system.img, load to SD and flash via TWRP).
http://forum.xda-developers.com/v20/development/h918-stock-deodex-debloat-t3499423
Nope
jaysonic88 said:
As long as you have access to TWRP you should be able to recover. If you need to restore the system partition you could use this DEODEX version. Follow thread instructions (download RAR, extract system.img, load to SD and flash via TWRP).
http://forum.xda-developers.com/v20/development/h918-stock-deodex-debloat-t3499423
Click to expand...
Click to collapse
I flashed it via TWRP and that didn't work. I also tried another stock boot and system .img but that didn't work either. Please help!
ScottFlysPlanes said:
I flashed it via TWRP and that didn't work. I also tried another stock boot and system .img but that didn't work either. Please help!
Click to expand...
Click to collapse
I'm stuck In the same situation idk what to do I've tried everything I'm getting hopeless. have you resolved your issue yet?
ricosuave88 said:
I'm stuck In the same situation idk what to do I've tried everything I'm getting hopeless. have you resolved your issue yet?
Click to expand...
Click to collapse
I FIXED IT! I am making a thread later on how I did it!
Fixed this by restoring stock recovery.img.
Of course I lost TWRP and root, but it's progress.
http://forum.xda-developers.com/v20/how-to/how-fixed-bricked-lg-v20-t3501310
Hi,
I rooted my s7 edge, everything worked well. I made a nandrodi backup with TWRP 3.2.
So I try some new cfw, and I tryed to do a recovery and get this red letters
E receive error on event
someone had this problem already?
pufnasti said:
Hi,
I rooted my s7 edge, everything worked well. I made a nandrodi backup with TWRP 3.2.
So I try some new cfw, and I tryed to do a recovery and get this red letters
E receive error on event
someone had this problem already?
Click to expand...
Click to collapse
Install TWRP 3.1.1-0 and then restore your backup - worked for me! On 3.2 are errors while flashing or restore a backup - hope it will be fixed soon.
Redmanha said:
Install TWRP 3.1.1-0 and then restore your backup - worked for me! On 3.2 are errors while flashing or restore a backup - hope it will be fixed soon.
Click to expand...
Click to collapse
Tnx
Can I downgrade the TWRP without reflashing my phone?
pufnasti said:
Tnx
Can I downgrade the TWRP without reflashing my phone?
Click to expand...
Click to collapse
Yes, you dont need to reflash you phone - flash twrp 3.1.1-0 via image install in twrp and reboot recover, then you're on 3.1.1-0
Redmanha said:
Yes, you dont need to reflash you phone - flash twrp 3.1.1-0 via image install in twrp and reboot recover, then you're on 3.1.1-0
Click to expand...
Click to collapse
You're right, TWRP 3.20 was buggy, downgrade went well, backup, restore everything is working fine now.
Thx again
When I install the latest oreo rom and recommended recovery, there are always problems
for example: error 7, Can't mount vendor, unable to mount storage...
When I install Pixel Experience and RR oreo rom, this error is happening and I can not install a different rom or another zips, using different recovery not the solution. I tried some suggestions here but the result has not changed
I installed a stock rom with QPST and problems improved
Exactly what we should do, Can you explain in detail
thanks to those who contributed :good:
Which recovery you using
poyraz4558 said:
When I install the latest oreo rom and recommended recovery, there are always problems
for example: error 7, Can't mount vendor, unable to mount storage...
When I install Pixel Experience and RR oreo rom, this error is happening and I can not install a different rom or another zips, using different recovery not the solution. I tried some suggestions here but the result has not changed
I installed a stock rom with QPST and problems improved
Exactly what we should do, Can you explain in detail
thanks to those who contributed :good:
Click to expand...
Click to collapse
Please provide specifics of ROM and TWRP Version. Did you load mods? Did you use custom kernel?
I installed this recovery for bootleggers 8.1 rom,
https://androidfilehost.com/?fid=673956719939820462 (twrp 3.2.1.0 It works well),
then I've installed Orangefox recovery for try and I used for long time without any problem,
later I flashed this recovery for Pixel Experience rom
https://androidfilehost.com/?fid=1322778262904027766 (twrp 3.2.3.0),
installed without a problem but a long time stuck in google logo, I rebooted three times a long press power button and the phone opened normally
No problem when using the phone but all times error on recovery.. such as 'vendor, invalid argument, mount error.
Always these errors during the rom installation and wiping..
Now is stock rom installed, I think there are some changes in the new rom because such problems did not happen before,
thank you for your answers and developers
poyraz4558 said:
I installed this recovery for bootleggers 8.1 rom,
https://androidfilehost.com/?fid=673956719939820462 (twrp 3.2.1.0 It works well),
then I've installed Orangefox recovery for try and I used for long time without any problem,
later I flashed this recovery for Pixel Experience rom
https://androidfilehost.com/?fid=1322778262904027766 (twrp 3.2.3.0),
installed without a problem but a long time stuck in google logo, I rebooted three times a long press power button and the phone opened normally
No problem when using the phone but all times error on recovery.. such as 'vendor, invalid argument, mount error.
Always these errors during the rom installation and wiping..
Now is stock rom installed, I think there are some changes in the new rom because such problems did not happen before,
thank you for your answers and developers
Click to expand...
Click to collapse
Okay... I'd recommend one thing.
Install the custom ROM. Then follow flashing procedure and do read the new FAQ posted by the devs. And after that... Try to reflash the recovery.img by pressing install image option. After this... If the problem persists, try to follow the procedure again and check if your recovery image isn't corrupt. Plus don't use the recovery from TWRP.ME
I have a recovery that can solve this problem but you can't restore ROMs you backed up
Phantom Slayer04 said:
Okay... I'd recommend one thing.
Install the custom ROM. Then follow flashing procedure and do read the new FAQ posted by the devs. And after that... Try to reflash the recovery.img by pressing install image option. After this... If the problem persists, try to follow the procedure again and check if your recovery image isn't corrupt. Plus don't use the recovery from TWRP.ME
Click to expand...
Click to collapse
thanks, I understand
I did actually try a second time, just flashed pixel experience rom and twrp 3.2.3.0 recovery on the stock rom - recovery.. same errors are happening and this problems improve only when I install stock rom with QPTS.. I will do clean installation in a short time again, just wonder why there is so much vendor error on recovery...
poyraz4558 said:
thanks, I understand
I did actually try a second time, just flashed pixel experience rom and twrp 3.2.3.0 recovery on the stock rom - recovery.. same errors are happening and this problems improve only when I install stock rom with QPTS.. I will do clean installation in a short time again, just wonder why there is so much vendor error on recovery...
Click to expand...
Click to collapse
Did you wipe the partitions? Did you format data partition?
Phantom Slayer04 said:
Did you wipe the partitions? Did you format data partition?
Click to expand...
Click to collapse
yes I did, including vendor..Today I searched the topics in the forum; return to old rom is not recommended after installing the new rom, I see similar troubles in rom forums..
poyraz4558 said:
yes I did, including vendor..Today I searched the topics in the forum; return to old rom is not recommended after installing the new rom, I see similar troubles in rom forums..
Click to expand...
Click to collapse
If you want to install latest update roms then read this FAQ:https://forum.xda-developers.com/showpost.php?p=77872447&postcount=2325:confused:
if you want to revert to old roms then you have to flash stock nougat rom using qfil and install twrp 3.2.1.0 and install old roms
don't do it wrongly otherwise you will get updater error 7 or can't mount vendor, etc,
Sudhar123 said:
If you want to install latest update roms then read this FAQ:https://forum.xda-developers.com/showpost.php?p=77872447&postcount=2325:confused:
if you want to revert to old roms then you have to flash stock nougat rom using qfil and install twrp 3.2.1.0 and install old roms
don't do it wrongly otherwise you will get updater error 7 or can't mount vendor, etc,
Click to expand...
Click to collapse
Thank you, I learned later that.. That's why i'm using an old rom because sometimes I can't any process on recovery, There are too many errors..
poyraz4558 said:
When I install the latest oreo rom and recommended recovery, there are always problems
for example: error 7, Can't mount vendor, unable to mount storage...
When I install Pixel Experience and RR oreo rom, this error is happening and I can not install a different rom or another zips, using different recovery not the solution. I tried some suggestions here but the result has not changed
I installed a stock rom with QPST and problems improved
Exactly what we should do, Can you explain in detail
thanks to those who contributed :good:
Click to expand...
Click to collapse
You should be on latest nougat that is with november security patch. All rom after 14/10/2018 should flash with latest twrp that is 3.2.3.0. all roms before that should be flashed with twrp 3.2.1.0.
sk.vyshak said:
You should be on latest nougat that is with november security patch. All rom after 14/10/2018 should flash with latest twrp that is 3.2.3.0. all roms before that should be flashed with twrp 3.2.1.0.
Click to expand...
Click to collapse
Ok..Which sections will be deleted on twrp 3.2.3.0 during wipe, is vendor partition included ?
poyraz4558 said:
Ok..Which sections will be deleted on twrp 3.2.0.3 during wipe, is vendor partition included ?
Click to expand...
Click to collapse
The thing is with new twrp there is decryption support which was lacked in old. Vendor partition is present in both i think. All the new roms are encrypted by default