Related
Hello everyone,
(Note, I did do a nandroid backup before I did ANYTHING, right after rooting)
I was having some issues with Modaco 1.0 when it was first put out, and like everyone else, got trapped in a reboot loop. Once I saw that the fix was repartitioning to FAT32, I did so, re-flashed the ROM, and I was back in. All was good.
But when 1.1 came out, I really wanted to restore to my backup to start fresh with the new ROM, but it did not work out. When I tried to do so in the recovery console, I got this error - Error: "nandroid-mobile.sh restore" from console! -
What am I supposed to do with that? I went ahead and went through with 1.1, but I am worried I accidentally closed my backdoor at some point. I noticed I lost some things from the basic ROM (such as the default wallpapers, and I had issues with Google Maps), and I am just generally worried something is fishy in there.
Any suggestions?
lorsoblu said:
Hello everyone,
(Note, I did do a nandroid backup before I did ANYTHING, right after rooting)
I was having some issues with Modaco 1.0 when it was first put out, and like everyone else, got trapped in a reboot loop. Once I saw that the fix was repartitioning to FAT32, I did so, re-flashed the ROM, and I was back in. All was good.
But when 1.1 came out, I really wanted to restore to my backup to start fresh with the new ROM, but it did not work out. When I tried to do so in the recovery console, I got this error - Error: "nandroid-mobile.sh restore" from console! -
What am I supposed to do with that? I went ahead and went through with 1.1, but I am worried I accidentally closed my backdoor at some point. I noticed I lost some things from the basic ROM (such as the default wallpapers, and I had issues with Google Maps), and I am just generally worried something is fishy in there.
Any suggestions?
Click to expand...
Click to collapse
Your Nandroid backup was on that SDcard...I don't suppose you saved it before formatting it?
lorsoblu said:
Hello everyone,
(Note, I did do a nandroid backup before I did ANYTHING, right after rooting)
I was having some issues with Modaco 1.0 when it was first put out, and like everyone else, got trapped in a reboot loop. Once I saw that the fix was repartitioning to FAT32, I did so, re-flashed the ROM, and I was back in. All was good.
But when 1.1 came out, I really wanted to restore to my backup to start fresh with the new ROM, but it did not work out. When I tried to do so in the recovery console, I got this error - Error: "nandroid-mobile.sh restore" from console! -
What am I supposed to do with that? I went ahead and went through with 1.1, but I am worried I accidentally closed my backdoor at some point. I noticed I lost some things from the basic ROM (such as the default wallpapers, and I had issues with Google Maps), and I am just generally worried something is fishy in there.
Any suggestions?
Click to expand...
Click to collapse
nah. The happens sometimes. Could be your nandroid backup got corrupted or you are low on battery power. Two most common causes. I would make sure the nandroid backup is on the sd card. if so, simply try plugging it in to a power supply. Let us know if you get it working.
All right... I did not want to admit it but I believe what you said is probably true, and I either corrupted or simply deleted the nandroid backup during all the flashing and repartitioning. I am not seeing it at all when I mount the SD card. It crossed my mind a little too late that I should have pulled it off the card.
What are my options here? On the one hand, it is working fine for now. I had just got the Hero earlier that day (did an exchange due to dead pixels and network issues), so it was not like I lost anything important. Is there an easy way for me to go all the way back, such as flashing the original ROM to the phone, and essentially starting over, like I just opened the box and turned the phone on? That way I can do it right from the very beginning. I just worry that in all my partitioning things got scrambled, and I am not seeing the repercussions from it yet, other than Google Maps.
ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe
if at first you try and fail.... try try agian
Thanks for the link.
Is there some process to this? I mean, I understand the whole update.zip concept of flashing the ROM, but would I also need to do a complete wipe of the SD card to achieve the fresh start I am looking for? Should I partition it at only FAT32, or go ahead and setup the ext2 partition before flashing the original ROM?
lorsoblu said:
Thanks for the link.
Is there some process to this? I mean, I understand the whole update.zip concept of flashing the ROM, but would I also need to do a complete wipe of the SD card to achieve the fresh start I am looking for? Should I partition it at only FAT32, or go ahead and setup the ext2 partition before flashing the original ROM?
Click to expand...
Click to collapse
convert sd card to "SDPART:fat32 only" from custom recovery
et the official RUU wipe your phone
enable USB debugging in settings>applications
reroot your phone using asroot exploit
make any partition changes you want
do a nandroid backup
do a nandroid restore to verify it works
backup on your workstation /sdcard/nandroid
DO NOT TOUCH YOUR SD PARTITION TYPE AT THIS POINT
get to modding in confidence
johnsongrantr said:
convert sd card to "SDPART:fat32 only" from custom recovery
et the official RUU wipe your phone
enable USB debugging in settings>applications
reroot your phone using asroot exploit
make any partition changes you want
do a nandroid backup
do a nandroid restore to verify it works
backup on your workstation /sdcard/nandroid
DO NOT TOUCH YOUR SD PARTITION TYPE AT THIS POINT
get to modding in confidence
Click to expand...
Click to collapse
All right, I am having issues already, from the very beginning.
The RUU ROM .exe will not recognize the HTC Hero. It throws an error 170 at the step where it is trying to pull information from the phone. I think this has something to do with ADB, and the fact the computer did not have the SDK on it. (I originally set up the root with my Mac.)
So, where do I go? I have a Boot Camp partition and another computer both running Windows 7, but my attempts to put the SDK on those computers and then have the phone drivers properly recognized failed on both, and the .exe still cannot complete. Is there something I am missing here, or can I somehow do this on the Mac side? I'll take anything!
Edit: Just cause I can see someone asking, yes, I tried to do this on both of my Windows 7 computers, not the Mac. I recognized that the .exe would not run on OSX pretty quickly.
can you put your phone into fastboot (power+vol down) and get to the point where windows basically sees your phone
what you are looking for is when you type adb devices it shows your hero
fastboot might not work because it's a seperate program but try custom recovery main menu.... enable usb.... or something to that extent
I appologize I don't have my main computer in front of me so I can't tell you EXACTLY where to go
once I do, I'll find which one to hit.... it does work though because I had to do the same thing with my godly preaching of backups :blush:
it's one of the recovery areas though i promise
fastboot will see the hero as the same device as adb will in fastboot
adb will see the hero as recovery device in custom recovery
attempt both of these I'm certain one of these work
if absolutely all else fails.... after you "install" sprint ruu search your computer for rom.zip it should be in your START>RUN>%TEMP% in here somewhere
rename rom.zip it to HERCIMG.ZIP and put it at root of your sd card and boot into hboot and it should automatically find it and press action to flash it
I'll give some of that a shot. I can confirm that adb devices was not showing the hero connected cause I tested that, so I have a feeling correcting that is my primary concern. What happened when I connected the Hero the first time was that it applied the drivers, but it could not find the ADB one, even after I added the SDK. So if anyone knows what that means (Windows 7 doesn't really give you an easy way to point and say, "Hey, I know what you are looking for, it's right here!" apparently, at least I haven't found it) it would be appreciated.
lorsoblu said:
I'll give some of that a shot. I can confirm that adb devices was not showing the hero connected cause I tested that, so I have a feeling correcting that is my primary concern. What happened when I connected the Hero the first time was that it applied the drivers, but it could not find the ADB one, even after I added the SDK. So if anyone knows what that means (Windows 7 doesn't really give you an easy way to point and say, "Hey, I know what you are looking for, it's right here!" apparently, at least I haven't found it) it would be appreciated.
Click to expand...
Click to collapse
go to htc's website and get htc sync under support>sprint hero it has the drivers built in.... should fix driver issue
johnsongrantr said:
go to htc's website and get htc sync under support>sprint hero it has the drivers built in.... should fix driver issue
Click to expand...
Click to collapse
Hey, that did the trick! Currently flashing with the official ROM right now. Thanks for all the help! FINALLY, I will get to do this right!
lorsoblu said:
Hey, that did the trick! Currently flashing with the official ROM right now. Thanks for all the help! FINALLY, I will get to do this right!
Click to expand...
Click to collapse
glad to be of assistance
johnsongrantr said:
glad to be of assistance
Click to expand...
Click to collapse
Actually, I do have one more question.
Following your instructions back on page 1, wouldn't I want to make the nandroid backup BEFORE repartition to fat32+ext2, so I could recover it all the way back to the standard ROM without partition alterations? Or is it necessary for me to repartition before creating a backup?
lorsoblu said:
Actually, I do have one more question.
Following your instructions back on page 1, wouldn't I want to make the nandroid backup BEFORE repartition to fat32+ext2, so I could recover it all the way back to the standard ROM without partition alterations? Or is it necessary for me to repartition before creating a backup?
Click to expand...
Click to collapse
you'd think so.... but from my own experience if you do a backup on a partititon then convert it... it screws with the backup and you can't recover from it.... just in case... do 2 backups.... store the normal fat32 nandroid backup on your workstation (the entire nanddroid folder) and copy it back to sd after you convert it to fat32+ext2 .... you'll see what I'm talking about....
I don't quite understand why it does that... but for me I was only successful in recovering from a partition that I made a backup to not copied to (if that makes any sence)
also if you don't want to experiement yet... just leave it fat32... you can always change it later after you see it working (sorta confidence builder before tinkering)
lorsoblu said:
Actually, I do have one more question.
Following your instructions back on page 1, wouldn't I want to make the nandroid backup BEFORE repartition to fat32+ext2, so I could recover it all the way back to the standard ROM without partition alterations? Or is it necessary for me to repartition before creating a backup?
Click to expand...
Click to collapse
Think about it this way, you do a nandroid backup...it places it on the sdcard.
Then you go and change the format of the sd card (potentially blowing away or corrupting any data on it, including the nandroid backup you just made).
Thus why it's better to do it afterwards (besides, nandroid doesn't back up your sd card, just your phone's OS and such)
solved for me
i had that problem its cuz the back up is brocken get anthoer copy of it if u hav 1 then restore it again it worked for me
I have looked high and low for a similar thread (detailing my specific problem) so I apologize if it exists and I was unable to locate it. I attempted to flash the PRIMEE ROM on my Acer with all apparently going well until the end. Messages were displayed saying that data, cache, etc. could not mount or something to that effect. I foolishly rebooted only to find that the Iconia will only display "Unrecoverable Bootloader Error (0x000000004)"
That's it. It is completely unresponsive to any other attempts to factory reset. Power/volume does nothing. I have looked extensively for some solution to this problem (attempted Reset button, moving lock screen slider/power-volume combination). You name it, I've tried it. It was briefly recognized by my PC when connected via USB but the AXP drivers were not found and did not install. I'm really flummoxed here.
Again, apologies if this is a duplicate thread but it seems fairly unique in that I cannot get any response at all. I fear that I've really done it this time. Any help would be greatly appreciated.
You DID install the custom clockworkmod app from the dev section, right? Not the one from the market...
Clockwork.....
No, unfortunately I did not. Didn't even realize there was a difference. I did install the Acer Recovery App as well, but otherwise, I think I'm pretty well screwed....
Well mate,now thats a huge problem you got there. If you would've screwed the /system partition np, /data partition,also np.....But uhh,bootloader error...i got the feeling your flashing has screwed up the internal Kernel of the Device,which is connected to the Bootloader,and without a Bootloader...well as its name says,you cant boot anything. Its like a Bios to a normal Computer,if you screw up the Bios,basically you can throw your Motherboard away...and sadly,the tablet comes all together,also i dont think Acer's Warranty will do anything about it aswell since you flashed an unofficial ROM/Kernel.
Your only solution is to send it to Acer,and see if your lucky enough and they fix it for free,if not ...well pay or get another one.
Goodluck with your problem mate.
Respect.
Yeah - kinda figured as much. Very disappointed that I lost it but I suppose I can make one last ditch effort to get it to Acer and see if they'll replace it but I'm skeptical at this point. Oh well - first time for everything. Lesson learned. Thanks for the help all the same.
First, congratulations. You managed to get the unrecoverable bootloader error
--> PM me with your UID, I may help you.
..............Edited..............
You should talk with sc2k I was in the same position you're in with the Unrecoverable Bootloader Error. Sent sc2k the UID for my A500 and he was able get my A500 back up and running again.
first of all, make sure you have a sd-card.
second. dl a stock rom to your PC 1.10.42 for instance, extract with decrypter and put the update.zip on the sd-card using a card reader or maybe your phone.
the put the sd-card back on your ICONIA.
after do the following:
hit VOLUME + (volume up) and power, until it vibrates, keep you finger on volume + and toggle the screen toggle switch.
it will then say formating data and formating cache, and the will start to flash the update.zip
once finished you should be ok.
Hi,
i have the same probplem, can anyone help me?
i have installed a custom firmware from thor and enabled the 3g option, my a500 will only vibrate after reboot with the error "Unrecoverable Bootloader Error (0x000000004)"
i cant read out the UID or anything else ... can anyone help me???
APX Mode runs but i cant recover with nvflash ...
I am unable at the moment with TWRP to mount my /system partition, which therefore has lead me not to have the ability to flash a custom ROM, but also at the same time I am ROMless, I have access to Recovery, at the moment, I'm attempting to sideload a Stock Rooted zip of my AT&T G2 ROM. However, I believe it won't have any progress, but I'm attempting anything at the moment in order to get my phone running.
Currently stuck on TWRP flashing a ROM and stuck on "Formatting" once again.
Any help would be appreciated. Quite frankly, I am scared out of my wit that I have bricked my phone, however there is some hope left in me with the fact that I have Recovery still running.
Kenchi* said:
I am unable at the moment with TWRP to mount my /system partition, which therefore has lead me not to have the ability to flash a custom ROM, but also at the same time I am ROMless, I have access to Recovery, at the moment, I'm attempting to sideload a Stock Rooted zip of my AT&T G2 ROM. However, I believe it won't have any progress, but I'm attempting anything at the moment in order to get my phone running.
Currently stuck on TWRP flashing a ROM and stuck on "Formatting" once again.
Any help would be appreciated. Quite frankly, I am scared out of my wit that I have bricked my phone, however there is some hope left in me with the fact that I have Recovery still running.
Click to expand...
Click to collapse
Im having the same issue too
Kenchi* said:
I am unable at the moment with TWRP to mount my /system partition, which therefore has lead me not to have the ability to flash a custom ROM, but also at the same time I am ROMless, I have access to Recovery, at the moment, I'm attempting to sideload a Stock Rooted zip of my AT&T G2 ROM. However, I believe it won't have any progress, but I'm attempting anything at the moment in order to get my phone running.
Currently stuck on TWRP flashing a ROM and stuck on "Formatting" once again.
Any help would be appreciated. Quite frankly, I am scared out of my wit that I have bricked my phone, however there is some hope left in me with the fact that I have Recovery still running.
Click to expand...
Click to collapse
Try this? http://forum.xda-developers.com/showthread.php?t=2451696
I finally solved the issue, miraculously, nothing was working so I just left the phone to continuing formatting for an hour so, came back, and it seemed to have done it, I installed Custom ROM, and it booted up normally, I'm not sure what triggered the phone to accept the system mount, but I am sure as hell happy it did. I was worried I was going to have a bricked device on my hands.
Hold strong, just allow the phone to continue doing what it needs to do I guess. Leave TWRP in all STOCK settings, I tried to modify multiple settings based on Devs saying to get a faster formatting to enable RM-F but I have no clue why and what didn't work.
Anyhow, problem resolved!
On another note, I would never use the recommended method from Droid_<3er as they would completely brick your phone unless you're specifically in the situation listed in that thread. As you would put your phone into a state where you lose both access to Recovery and ROM access, rendering your phone to a piece of plastic and metal. But it's definitely worth mentioning, I just had to do some research on the method cause I had the same thinking as well.
I can confirm by using normal make_ext4fs while formatting /system is the best way to avoid this. Was afraid of having a 5.2 inch brick, but thankfully, disabling the quick way to format has fixed it and allowed /system to be remounted.
I think (<-- that's the disclaimer) that it's OK to use the fast formatting method for Dalvik Cache and Cache, but not for System.
in my opinion it's best to use rm -rf /system aka delete_recursive("/system"); than formatting
I'm having the same issue, and I'd be willing to try this one. How would I do this?
I have the same issue with CWM and now got over to twrp with the same outcome.
Right here I see solutions that worked so far, but it seems like this was rather accidentially.
I want to try some of these, but in the thread posted above
"Try this? http://forum.xda-developers.com/show....php?t=2451696"
it says "Do it the wrong way and your phone might get nuked"
unfortunately it doesn't say what the commands in there mean...
Can anybody be of assistence which method will properly work without nuking the phone?
I have the MOTO G 2014 (2nd Gen)
It is an updated bootloader
i got the latest twrp
and some titan roms.
only stock rom will work so far,
custom roms will result in a bootloop.
I installed TWRP and tried to flash SuperSU according to the guide by ashyx here: https://forum.xda-developers.com/showthread.php?t=3475381
So, from what I can tell by reading this thread: https://forum.xda-developers.com/galaxy-tab-a/help/samsung-galaxy-tab-10-1-mount-data-t3544561, the problem is that my device was encrypted. I tried restoring the full image that I made using TWRP, before trying to flash the boot. Stuck on Samsung logo now. I should have seen this coming when I was getting "failed to mount /data" errors.
So I suppose I need to flash that zip https://www.androidfilehost.com/?fid=24591000424951049, but I thought I better ask specifically about my device and situation before blindly flashing yet another zip.
What steps do I need to take now?
thanx
update :: it sounds like my last resort option is to flash the stock ROM (can I do this in Odin?)
BUT I noticed that SuperSU saved a "stock_boot_*.img.gz" file, which I copied to SD root and also to my PC. Now I imagine that if I flash this, I might be able to regain access to the OS... that would be the best at this time. Then I can do more research and try root again later.
Is this true, and how should I flash the stock_root file?
I absolutely love doing research and answering my own questions! no sarcasm. after reading a whole bunch of general info about the Android system, partitions, boot process, TWRP... I forged ahead with 90% confidence, unpacking the "stock_boot_*.img.gz" and feeling for a way to flash it with TWRP... and more importantly, with 99.9% confidence that it won't wreck anything if I try.
So next time, I will first decrypt the system before trying to root, and pay attention to the log output, and only proceed when confident that I know what's happening next... this is all basic IT procedure. I should know this! Guess I was in a rush to get root. Still in a rush in a way tho.... want to recover deleted photos and can't do it without root. Anybody know if Android device encryption is proper full-disk? Like if the empty space will be decrypted just the same?
trefrog said:
I absolutely love doing research and answering my own questions! no sarcasm. after reading a whole bunch of general info about the Android system, partitions, boot process, TWRP... I forged ahead with 90% confidence, unpacking the "stock_boot_*.img.gz" and feeling for a way to flash it with TWRP... and more importantly, with 99.9% confidence that it won't wreck anything if I try.
So next time, I will first decrypt the system before trying to root, and pay attention to the log output, and only proceed when confident that I know what's happening next... this is all basic IT procedure. I should know this! Guess I was in a rush to get root. Still in a rush in a way tho.... want to recover deleted photos and can't do it without root. Anybody know if Android device encryption is proper full-disk? Like if the empty space will be decrypted just the same?
Click to expand...
Click to collapse
It doesn't really decrypt it, it does a full format using either no encryption or new encryption. I'm sorry, but the files are gone. To answer your question though, I believe the encryption is full-disk.
Going forward, check out TitaniumMediaSync. You can mirror your internal storage to a computer via FTP, so when these things happen (and they do happen), you won't lose anything. I'm sorry you lost your files in this.
actually I didn't lose my files! I was able to restore the backed up boot partition that twrp made and tucked into a folder.
happy af :laugh:
... so are you saying that the decrypt function in the Android settings just wipes everything? Then why is it even there, if it's basically a factory reset?
hmm associated with Titanium Backup? I have a license for that, and as soon as I root this, I'll be installing it. Currently, all my important stuff (just photos), are backed up to my PC via QuicPic's cloud backup feature.
I think i have found myself in the same situation as you. I dont have any files or data to lose. managed to do first step in using odin to install twrp. tried to follow additional steps of installing super su, then padded boot. now the tablet wont load past the first screen. I can still get into twrp. how can i get this fixed, rooted and a custom image installed? any help in the right direction would be appreciated.
find that "stock_boot_*.img.gz" using the twrp file browser thing. copy it to the root of your SD for safe keeping (even if the SD is encrypted, it seems that it does so only at the file level, rather than partition/disk level, so it will be written unencrypted). if ur plugged to PC, you can copy it across for even safer keeping
then... I don't recall how I found it, but it's in twrp. a way to flash that file. worked for me, because as far as I made it, only the boot partition was affected
So I've finally mustered up some courage to flash something fancy into my X720, and this is what happened. Up until flashing the ROM itself ([ROM] [TREBLE] [8.1] [Official] AICP 13.1 (Pro3 aka zl1, zl0, X727,X720,X722) by mosimchah) it went relatively well, but then I got twrp error 7. After some tweaking error message changed to "failed to mount '/system' (invalid argument). Can it be because I've wiped "system" before flashing? I think instructions said to do so... Anyway now I'm stuck, because even though I made a twrp backup, I was smart enough to remove it from the phone and now I can't put it back, because one of the files is 4gb in size, and I get error message when trying to copy it to phone storage (file system indicates "generic" or something along those lines). I'm new with this kind of stuff, so I really could use some advice. Should I flash stock rom? If so, which version? I can't remember exactly which was mine. I wonder if there's something to be done with that 4gb recovery file? And how did twrp mess up like that? Shouldn't it be calculated more carefully?
TheOkMan said:
So I've finally mustered up some courage to flash something fancy into my X720, and this is what happened. Up until flashing the ROM itself ([ROM] [TREBLE] [8.1] [Official] AICP 13.1 (Pro3 aka zl1, zl0, X727,X720,X722) by mosimchah) it went relatively well, but then I got twrp error 7. After some tweaking error message changed to "failed to mount '/system' (invalid argument). Can it be because I've wiped "system" before flashing? I think instructions said to do so... Anyway now I'm stuck, because even though I made a twrp backup, I was smart enough to remove it from the phone and now I can't put it back, because one of the files is 4gb in size, and I get error message when trying to copy it to phone storage (file system indicates "generic" or something along those lines). I'm new with this kind of stuff, so I really could use some advice. Should I flash stock rom? If so, which version? I can't remember exactly which was mine. I wonder if there's something to be done with that 4gb recovery file? And how did twrp mess up like that? Shouldn't it be calculated more carefully?
Click to expand...
Click to collapse
You can use a SD card or a USB otg and a flash drive for your backup
Sent from my PH-1 using Tapatalk
clsA said:
You can use a SD card or a USB otg and a flash drive for your backup
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Thanks for the tip, clsA. Gave me quite a push. However, here what happened next: with USB OTG I was able to move the missing 4gb file to the phone storage and recovered my phone to a fully working state (wasn't able to recover directly from USB - anyone knows why? Maybe because it's ntfs?). Thinking I've established a good pivoting point I proceeded flashing custom ROMs. First time I did everything the same. The result was same, obviously. Then recovery. Then I tried leaving *system* out of wiping process and switched my ROM from AICP to DotOS. Installation went through without errors, but the ROM wasn't working correctly. SIM card wasn't recognized, HOME and DETAILS capacitive buttons wasn't working, couldn't download apps from play store, some crashing here and there. I though I had enough, and decided to recover for the time being, but when I did that upon boot up I got *ENCRYPTION UNSUCCESSFUL* error. There's restore system option under it, but it doesn't help. Tried recovering again - same. Reflashed DotOS - got my SIM recognized, but all other bugs remained. I think I'm doing something wrong when flashing, but can't figure out what. There isn't that many steps, and I followed them through... Even tried removing first lines of that script file (in ROM zip file) to get rid of that error 7 at the beginning of AICP installation, which didn't do anything (there's also a chance I've deleted wrong lines, or not all of them..). Maybe someone had similar problems and could share some ideas? And that Encryption error is very strange. Nothing changed after first recovery, so why I'm getting it? All the directories are in ex4 format. Any thoughts about this one?
TheOkMan said:
Thanks for the tip, clsA. Gave me quite a push. However, here what happened next: with USB OTG I was able to move the missing 4gb file to the phone storage and recovered my phone to a fully working state (wasn't able to recover directly from USB - anyone knows why? Maybe because it's ntfs?). Thinking I've established a good pivoting point I proceeded flashing custom ROMs. First time I did everything the same. The result was same, obviously. Then recovery. Then I tried leaving *system* out of wiping process and switched my ROM from AICP to DotOS. Installation went through without errors, but the ROM wasn't working correctly. SIM card wasn't recognized, HOME and DETAILS capacitive buttons wasn't working, couldn't download apps from play store, some crashing here and there. I though I had enough, and decided to recover for the time being, but when I did that upon boot up I got *ENCRYPTION UNSUCCESSFUL* error. There's restore system option under it, but it doesn't help. Tried recovering again - same. Reflashed DotOS - got my SIM recognized, but all other bugs remained. I think I'm doing something wrong when flashing, but can't figure out what. There isn't that many steps, and I followed them through... Even tried removing first lines of that script file (in ROM zip file) to get rid of that error 7 at the beginning of AICP installation, which didn't do anything (there's also a chance I've deleted wrong lines, or not all of them..). Maybe someone had similar problems and could share some ideas? And that Encryption error is very strange. Nothing changed after first recovery, so why I'm getting it? All the directories are in ex4 format. Any thoughts about this one?
Click to expand...
Click to collapse
follow instructions posted here > https://forum.xda-developers.com/showpost.php?p=77813881&postcount=793
clsA said:
follow instructions posted here > https://forum.xda-developers.com/showpost.php?p=77813881&postcount=793
Click to expand...
Click to collapse
Thanks again, clsA. Looks like this could be it. Will try it soon. For now I have flashed [ROM][X72X][7.1.X][OFFICIAL] LineageOS 14.1 (which is now 8.1 somehow...) and it works without any issues so far.
Any insights on why I'm getting *Encryption unsuccessful* error after restoring my original system image via TWRP (first recovery was fluent, error appeared following my later attempts for recovery)?