Hello. I was using recently official LegionOS. I wanted to try Havoc so i've flashed it using OrangeFox Recovery. The device didn't boot, got stuck on Xiaomi logo, vibrated and rebooted to recovery. I tought it was maybe faulty file so i've flashed other rom that I was using before - Fluid. Same result here, I tried now to restore my backup (all partitions without internal) with EvolutionX. Still nothing, phone has rebooted to recovery and I saw that all files have been encrypted. Now i can't do anything other than full wipe. Is there any option to rescue these files from internal storage? I've tried TWRP but it didn't help.
tvv0rus said:
Hello. I was using recently official LegionOS. I wanted to try Havoc so i've flashed it using OrangeFox Recovery. The device didn't boot, got stuck on Xiaomi logo, vibrated and rebooted to recovery. I tought it was maybe faulty file so i've flashed other rom that I was using before - Fluid. Same result here, I tried now to restore my backup (all partitions without internal) with EvolutionX. Still nothing, phone has rebooted to recovery and I saw that all files have been encrypted. Now i can't do anything other than full wipe. Is there any option to rescue these files from internal storage? I've tried TWRP but it didn't help.
Click to expand...
Click to collapse
format data and flash
Related
Been using twrp since rooting note II. I wanted to try out 4.4 PA but they said to only use cwm. It was late so I decided to be lazy and since I used to use rom manager all the time I installed it to flash cwm recovery then booted into recovery to install touch version. It wasn't showing the touch version so selected to restart to check to see where I saved it to it would not boot past the first "note II" splash screen. Battery pull then back into recovery and went ahead and flashed PA 4.4 and now it will get past the splash screen then shows boot animation but then starts all over.
Is this a rom manager issue?
can I flash twrp from within cwm recovery?
will I have to basically reroot it?
Any suggestions on how to get back to twrp and to a usable phone?
thanks
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
cadavjo said:
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Nope did my standard wipe cache, wipe dalvik, and factory reset then flashed rom then gapps. Going to go back to twrp and wait for 4.4 to be more stable before I try it out again and maybe then I can use twrp to flash it.
thanks for the help
cadavjo said:
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
that didn't work. flashed newest twrp then rebooted into it and tried to flash tweaked and sticks at the splash screen again
jdpeck said:
that didn't work. flashed newest twrp then rebooted into it and tried to flash tweaked and sticks at the splash screen again
Click to expand...
Click to collapse
Have you wiped data at all? You need to wipe data / factory reset when switching roms, and it sounds like you havent.
fallingup said:
Have you wiped data at all? You need to wipe data / factory reset when switching roms, and it sounds like you havent.
Click to expand...
Click to collapse
As stated above, on both cwm and twrp I wiped caches and did factory reset and still having the issues. Once back on twrp I even formatted internal memory thinking maybe rom manager messed something up on it and still can't get passed the splash screen.
jdpeck said:
As stated above, on both cwm and twrp I wiped caches and did factory reset and still having the issues. Once back on twrp I even formatted internal memory thinking maybe rom manager messed something up on it and still can't get passed the splash screen.
Click to expand...
Click to collapse
Copy a ROM to your SD card (external not internal)
Install cwm and format data (actually full format, where /data/media gets wiped) and system
Install rom
Reboot
TWRP has some issues randomly with corrupting /data, that's why I no longer use it.
fallingup said:
Copy a ROM to your SD card (external not internal)
Install cwm and format data (actually full format, where /data/media gets wiped) and system
Install rom
Reboot
TWRP has some issues randomly with corrupting /data, that's why I no longer use it.
Click to expand...
Click to collapse
Finally got it. Thought using odin to flash back to root 66 and start fresh would work but after that it was still going to the splash screen then black and a battery pull had to be done. TWRP back ups would fail when trying to restore, so I reverted back to an older version of twrp and it finally let a back up be installed and it booted up just fine!!
thanks for all the suggestions
Im having a similar problem to yours, I am using twrp and flashed PA 3.99 the phone works great, but if my battery dies or i restart the phone or shut it down it automatically wont get passed the samsung logo, or sometimes the PA logo, the only work arounds ive seen to it is to wipe the cache and dalvik to boot, but when that fails i have to install the whole rom over again. any ideas?
I recently formatted my internal storage because I felt like I needed a clean wipe. After doing so, flashing anything and rebooting into it will make it hang on the Samsung logo. I flash everything through TWRP v2.5.0.2 and I never had problems until I formatted. Now to get anything to work, I have to "format data" through TWRP and flash after that in order to boot into anything (every single time). And even after booting into it, I can't flash anything (or even simply reboot) without having to see the stuck screen again. Any ideas? My phone is MDK.
You need to update TWRP. Latest is 2.6.3.1. Older twrp doesn't use the proper symlinks for the internal data partition that changed in 4.3.
WhoNeedszzz said:
You need to update TWRP. Latest is 2.6.3.1. Older twrp doesn't use the proper symlinks for the internal data partition that changed in 4.3.
Click to expand...
Click to collapse
Thanks! I think that worked
Hi all,
I am on 4.4.4 and used TWRP in past, now I am on Philz Touch latest recovery.
I first cleaned data and system and tried to flash a different rom, it flashed fine but when I tried to flash 4.4.4 Gapps recovery restarted and it kept restarting if I tried to flash that Gapps so I cleaned again and only flashed the Rom this time, rebooted and my system restarted to recovery.
I manually tried to format all partitions but got
"E:format_volume: make_ext4fs failed on /dev/block/mmcblk0p10
E:Error formatting /preload!"
while formatting preload partition.
I google about this and search in xda too and found few threads suggesting to format /preload partition using TWRP recovery so I tried to flash TWRP but it stuck on it's flash screen. I tried to flash old version using Odin as well as new one but it keeps hanging on the it's flash screen. Flashing Philz via odin works every time but not TWRP.
So it looks like I am not able to format /preload partition, I am not able to flash any rom or gapps and not able to flash any version of TWRP recovery.
I am able to take a backup of my phone and restore it without any problem including my internal sd card using Philz Touch though just for the info.
So any suggestions friends?
Thanks.
Edit:
Flashing normal cwm and flashing TWRP after removing TWRP folder from internal memory helped to boot into TWRP. Also I was able to format /preload using normal CWM recovery however flashing anything using any recovery whether it's TWRP or Philz Touch simply boot my phone back into recovery itself and nothing works.
Even a clean flash doesn't work and flashing only a simply rom file will not work and boot my phone directly into recovery so it looks like my memory is corrupted or something similar.
I would appreciate any kind of suggestions related to my problem. Thanks.
Update :
Thankfully it was only my memory card which got corrupted and thus corrupted my rom files too so changing those files fixed my issue..
Sent from my "GT-I9300/1+1" powered by Carbon Rom & Boeffla/ak Kernel
Fueled by 7000mAh ZeroLemon Battery
I own the Nexus 9 (Wi-fi model) and am running Android 6.0 MRA58N, rooted with the TWRP recovery. I wanted to to update to android 6.0.1 so downloaded the latest factory image (MMB29R) from Google's website. I rebooted to TWRP so I could flash the new image. When I realized that you cannot flash system.img through TWRP I had already flashed the boot.img. I attempted to reboot only to get stuck in a bootloop. "Luckily me" I had taken a backup through TWRP previously (boot, data and system). So I went again in TWRP, factory reset and restored (successfully as per the message) the backup. Now every time I boot I see Google's logo, then the "Your device is corrupt" message, that I'm seeing since I installed TWRP (it doesn't seem to affect anything) and then a blank screen that goes on forever.
I had this backup moved to my hard drive and the moved it back to my device. Tried the "fix permissions" option in TWRP as well. No go.
Any suggestions?
I managed to fix it by installing the system, cache, boot and vendor partitions from the new build and the data partition from my nandroid backup.
same happen to me yesterday..what i did is,reboot into fastboot.and then flash vendor, system, boot, cache and also recovery..i have twrp install,but it show 0mb on internal storage.flash stock recovery fix that problem..and after that i flash twrp,supersu and elementalx again..it fix my problem
Sent from my Nexus 9 using Tapatalk
Hi,
My current problems are: my internal storage is completely deleted somehow and when I try to start the device it's bootlooping.
What happened before that was:
1. I was in MIUI 10 globe rom and had the regular TWRP (before treble thing I think)
2. I installed orangefox recovery so I could install a treble RR rom.
3. I backed up my MIUI rom and installed the RR rom without problems
4. Then I wanted to go back to MIUI rom
5. First I installed normal TWRP img into my recovery, because I couldn't recover the MIUI rom in orangefox (couldn't find the file)
6. Then I tried to recover the MIUI rom, but I didn't factory reset before i recovered. I thought that would happen anyway if i recovered a rom. But my recovery file didn't include bootloader and firmware. I had 2 recovery files in my internal storage. One of everything except the bootloader and firmware and the other recovery file was of the bootloader and firmware (i forgot to include them the first time i backed up)
7. So anyway, I recovered the first file and everytrhing was fine, but then immediately i also recovered the second file (the bootloader and firmware only). But the second file failed to recover.
8. I tried to boot the device, but it bootlooped at the MI globe image, then went back to MI logo, then mi globe image, etc. And finally it goes back to TWRP automatically.
9. Went back to recovery to see what's wrong. First I did a normal factory reset (only system, cache and dalvik, no internal storage) so I could install the RR rom I still had in my storage
10. Suddenly I see NOTHING in my internal storage in TWRP. Shows 0 gb.
So can anyone tell me what went wrong??? I never touched the 'format internal storage/data' thing in TWRP, but somehow it deleted it??? Wth happened?
And more importantly, what do I do now? Do I treat this as a bootloop or a bricked device? I know I have to use ADB and stuff to reset the device, right? Or Do I have to do something else?
Anyway, thanks in advance!
Edit: wait, i formatted /data now in TWRP and it booted into MIUI 10 after but with internal storage gone now of course. But I'd still like to know what went wrong.