How to. Dirty flash os iam on stock 5.1.6 if i have problem with bootloops after tweaking system it gets messed up and i have to flash whole rom in fastboot and loose everything so is there any working method to dirty flash existing 5.1.6 without loosing data
Also help me with twrp
I have officiall twrp i have backed up all partions in a case i have bootloop will restoring all the partions i mean it all the partions restore will it help me to boot back and should i have to change slots after full restore
Related
Sorry if this has already been asked; I tried searching, but I couldn't find anything.
I'm running Exodus version 5.1-20150911-NIGHTLY-bacon, TWRP 2.8.6, Exodus stock kernel
I'm trying to update to a new nightly, but I always get stuck in a bootloop.
Here's what I do:
Reboot to recovery
Nandroid backup
Wipe data, system, cache, Dalvik
Flash the new ROM (I tried COS 12.1 once, but it didn't work; I mostly try flashing the latest Exodus nightly_
(sometimes) Flash xposed-v74-sdk22-arm-by-romracer (it doesn't make a difference if I don't flash it)
Restore only the data from the last nandroid
Now when I reboot I'll just be stuck in the boot animation or I'll be able to pass the animation and I'll just be stuck in a loop setting up the apps.
If I don't flash xposed, but still restore the nandroid I'll boot up faster, but I get System UI has Stopped and then the phone goes into a boot animation loop
If I don't restore the nandroid it works fine and boots up way faster.
How can I update while keeping my app data (my xposed data isn't that important to me if that'll make a difference)?
RustySpackleford said:
Sorry if this has already been asked; I tried searching, but I couldn't find anything.
I'm running Exodus version 5.1-20150911-NIGHTLY-bacon, TWRP 2.8.6, Exodus stock kernel
I'm trying to update to a new nightly, but I always get stuck in a bootloop.
Here's what I do:
Reboot to recovery
Nandroid backup
Wipe data, system, cache, Dalvik
Flash the new ROM (I tried COS 12.1 once, but it didn't work; I mostly try flashing the latest Exodus nightly_
(sometimes) Flash xposed-v74-sdk22-arm-by-romracer (it doesn't make a difference if I don't flash it)
Restore only the data from the last nandroid
Now when I reboot I'll just be stuck in the boot animation or I'll be able to pass the animation and I'll just be stuck in a loop setting up the apps.
If I don't flash xposed, but still restore the nandroid I'll boot up faster, but I get System UI has Stopped and then the phone goes into a boot animation loop
If I don't restore the nandroid it works fine and boots up way faster.
How can I update while keeping my app data (my xposed data isn't that important to me if that'll make a difference)?
Click to expand...
Click to collapse
Why are you bothering to wipe if you're restoring your nandroid data anyway? Restoring the data is just canceling the wipe you just did. If you want to flash and keep your data just dirty flash the ROM update (a dirty flash means installing the zip while only wiping cache and dalvik cache).
Heisenberg said:
Why are you bothering to wipe if you're restoring your nandroid data anyway? Restoring the data is just canceling the wipe you just did. If you want to flash and keep your data just dirty flash the ROM update (a dirty flash means installing the zip while only wiping cache and dalvik cache).
Click to expand...
Click to collapse
I didn't realize that.
Edit: How do you clean flash and keep your data?
RustySpackleford said:
I didn't realize that.
Edit: How do you clean flash and keep your data?
Click to expand...
Click to collapse
You can't, that would defeat the purpose of a clean flash.
Hi there
I have flashed stock ROM 8.0, with the last Odin
After that I flash TWRP
I erase data / swipe phone to give TWRP the right to modify the phone
It's ok, TWRP can flash .zip, I flash Magisk
The phone reboot like after a factory reset, but the problem is, the phone force encryption again, because when I go back to TWRP after that, the partitions are read only....
It was ok with the 7.0 stock rom btw, but I don't knox what to do with this problem on 8.0. I have try no-verity-opt-encrypt-6.0 and 5.1 but doesn't fix it.
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
I'm testing various custom rom so often I want to go back from the custom rom to OOS. I have a twrp backup of my OOS, the problem is that i cannot restore it properly. If, from the custom rom, I reboot to recovery and restore the backup, the phone bootloops. I've also tried to format data and rebooting to recovery before restoring the backup, but this doesn't work either.
The only way I've found to properly restore the backup is to completely reflash OOS via MSM tool (or fastboot), but this takes really a lot of time, because apart from the MSM tool installation itself, it relocks the bootloader so I have to wait for the system to boot up, toggle oem unlock, unlock again the bootloader, wait for the wipe and for another system boot up, boot in twrp using fastboot command, transfer 13GB of data to the phone and then FINALLY restore the backup.
Is there an easier, and most important, faster, way to restore the backup?
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3932943
On this link scroll down and read the "tips", if you have backed up rom the way it says you shouldn't have any problems in restoring, hope this helps, cheers
Hello everyone this afternoon i decided to flash evolutionx from xiaomi.eu rom so i do this:
1) Reboot in orangefox recovery
2) Wipe everything (Dalvik, Metadata, Data, Internal Storage, Cache) except usb otg and micro sd card
3) Format data and reboot
4) I transfered the rom zip into the phone
5) Flash and wipe dalvik cache and reboot
But after I reboot it goes in fastboot instead of the system, i tried another time the passages but i'm still stuck in fastboot, did I bricked my device? What can I do to unstuck/unbrick?
You did indeed soft brick your device. But don't worry, it rather easy to solve.
It can happen because TWRP has failed to decrypt you internal storage.
I can only think of 3 ways to solve this:
Format data and flash again (In TWRP: Wipe > Format Data), maybe using latest version of TWRP can help.
You can use dm-variety to decrypt then encrypt your internal storage. However use dm-verity at your own risk.
You can always just flash your stock image back through MiFlash, you can find your stock image here with guide on how to flash it as well. Here is a wider list of stock roms for Poco X3 NFC
Goodluck.
XDHx86 said:
You did indeed soft brick your device. But don't worry, it rather easy to solve.
It can happen because TWRP has failed to decrypt you internal storage.
I can only think of 3 ways to solve this:
Format data and flash again (In TWRP: Wipe > Format Data), maybe using latest version of TWRP can help.
You can use dm-variety to decrypt then encrypt your internal storage. However use dm-verity at your own risk.
You can always just flash your stock image back through MiFlash, you can find your stock image here with guide on how to flash it as well. Here is a wider list of stock roms for Poco X3 NFC
Goodluck.
Click to expand...
Click to collapse
Thanks for your answer but i already find the problem, it is the version 5.7 of evolution x that has a bug that made people stuck in fastboot, so with the help of the devs telegram channels they suggest me to do this:
1) Flash a stock miui a10 rom
2) Rewipe everything and format data
3) Flash the evolutionx 5.6 that dosn't have this bug
Only i have a few question of this process: for firmware did i need to flash an android 10 firmware? (because before trying flashing this bugged version i had xiaomi.eu miui a11, After i flash the stock miui did i need to go to all boot setup? Maybe you can tell me if this is correct and what i need to do for firmware
If it is a bug in the custom ROM then, just flash your backup ROM. Or if you didn't backup your ROM, then flash the same stock ROM you had on this device.
No, it isn't a must to flash A10 ROM. And actually if you attempt this I think you'll PERM-BRICK your device due to stupid anti-rollback that Xiaomi has. You can google it up.
Yes, clean flashing any ROM essentially has the same steps: Backup > Full Wipe > Format Data > Flash > Wipe dalvik.
XDHx86 said:
If it is a bug in the custom ROM then, just flash your backup ROM. Or if you didn't backup your ROM, then flash the same stock ROM you had on this device.
No, it isn't a must to flash A10 ROM. And actually if you attempt this I think you'll PERM-BRICK your device due to stupid anti-rollback that Xiaomi has. You can google it up.
Yes, clean flashing any ROM essentially has the same steps: Backup > Full Wipe > Format Data > Flash > Wipe dalvik.
Click to expand...
Click to collapse
Ok thanks, so now i will download the same rom that i had (xiaomi.eu miui a11) it's correct to do this?