I was trying to revert to Sense today after flashing some of the AOSP roms that were newly released. I downloaded one of the stock Nandroid backups from the RUU thread and tried to restore from it: "System is mounted read-only". Okay, so then I mounted it with write permissions and proceeded to restore. The restore went fine except when it finished I got the error message "could not mount system (Structure needs cleaning)". Now when I try to reboot in twrp, it says I don't have an OS installed. Any idea how to recover from this? I have never encountered this error before :/.
Download the same stock firmware.zip as what was on it before you messed with it. Rename it to whatever it needs to be.. Begins with P.. Not sure what it actually is, and place it on the external sdcard.
Boot to download mode and flash it.
Do not relock your bootloader. Do not s-on.
Related
I need some help with something. I am trying to restore a backup of one of my ROMs that I created a backup of with CW and I am getting this message after Restoring system "Error while formatting /system!" So now if I reboot it gets stuck at the White screen with the HTC.
Does anyone know what this is all about? Why would I get a formatting system error? If I am stuck how do I get back to original state?
I just tried a test with a different back up and same result.
Finally! Someone with the same issue as me!
It sucks.
Even tried flashing the shipped RUU and rooting/S-OFF from scratch. No dice.
Happens with any version of CWM I use.
ProTekk what are you doing now with the phone? Has anyone else given you an explanation? Have you tried to go original out of the box state?
Just reflashed the custom RUU and re-rooted.
Not ideal, but it keeps S-OFF and gives me a working phone.
Grab the RUU file, rename it to PG05IMG.zip, and place on the root of your sd card. UNPLUG the phone and turn it off. Restart the phone UNPLUGGED while holding the volume down toggle. It will flash the RUU to your phone and return it to stock, unrooted, S-On.
Reroot using the instructions from the team.
Been there, done that, got the t-shirt...
This happened to me today too... i reflashed the last ruu file in the rooting directions, reran the last few lines of code and went from there. Then after having superuser installed, and rom manager installed, i verified root and then rebooted into clockwork and installed my old backup. No big issues. Just sucks i had to go through that again.
This happened to me when i tried getting rid of that new virus rom. Not that it was bad, just didnt like the 'flavor'. So i went into cwr cleared data then tried to install my previous backup. That's where it all went to hell.
/\\/\\orlince
Just wanted to let you know I was successful is just flashing a .zip of any ol rom that you can find on the site, I used Lightning v1.2 to flash CWM and then rebooted into recovery and recovered from one of my backups. Hope this helps!
-Justin
Here is the history
NS4G
Rooted in early January and flashed an ICS rom (Vgomez)
Then flashed CM9 alpha 20 and made a couple of Nandroid backups over the course of the month.
Briefly flashed the Stock 4.0.4 rom. Didn't like it.
Restored via Nandroid to the CM9 alpha 20
everything was great.
Yesterday I went to make a call and the phone locked. I tried to power down...no luck. So I pulled the battery.
It never came back. (got some type of 'android lost encryption' error)
I power up the phone and it brings me to a brand new user page where I would have to login with my gmail creds.
Then it starts throwing errors like calander stopped working, google settings app stopped working, android.process.acore stopped working. etc...
I can boot to CWM and but it will not allow me to recover to anything other than what I described above.
I can mount the USB partition and it appears to allow me to copy files into that partition. However, if I try to flash a ROM, Kernel, etc. It terminates the operation and says the file is bad.
When I reboot CWM and go to view the USB partition again, those files that I had just moved into the partition are now missing.
It is as though I have not copied the file at all.
Without access to the allow USB debug setting, I cannot adb anything.
I have tried the Samsung yellow boot/restore (odin?) when I click the 'Download files' button it throws a generic error and halts the process.
At this point, I don't care if the phone is put back to stock because I won't lose anything important. I just want to get my phone working again.
edit: I do have access to fastboot. I have wiped everything and tried to boot and it sticks in the bootloader (good?) I assume that when I try to flash one of the ROMs that I do have in the USB partition...it will go back to the way it was. (errors and all)
I suspect that the Kernel is corrupt. How would I fix this without being able to write to the USB partition?
deralaand said:
Here is the history
NS4G
Rooted in early January and flashed an ICS rom (Vgomez)
Then flashed CM9 alpha 20 and made a couple of Nandroid backups over the course of the month.
Briefly flashed the Stock 4.0.4 rom. Didn't like it.
Restored via Nandroid to the CM9 alpha 20
everything was great.
Yesterday I went to make a call and the phone locked. I tried to power down...no luck. So I pulled the battery.
It never came back. (got some type of 'android lost encryption' error)
I power up the phone and it brings me to a brand new user page where I would have to login with my gmail creds.
Then it starts throwing errors like calander stopped working, google settings app stopped working, android.process.acore stopped working. etc...
I can boot to CWM and but it will not allow me to recover to anything other than what I described above.
I can mount the USB partition and it appears to allow me to copy files into that partition. However, if I try to flash a ROM, Kernel, etc. It terminates the operation and says the file is bad.
When I reboot CWM and go to view the USB partition again, those files that I had just moved into the partition are now missing.
It is as though I have not copied the file at all.
Without access to the allow USB debug setting, I cannot adb anything.
I have tried the Samsung yellow boot/restore (odin?) when I click the 'Download files' button it throws a generic error and halts the process.
At this point, I don't care if the phone is put back to stock because I won't lose anything important. I just want to get my phone working again.
edit: I do have access to fastboot. I have wiped everything and tried to boot and it sticks in the bootloader (good?) I assume that when I try to flash one of the ROMs that I do have in the USB partition...it will go back to the way it was. (errors and all)
I suspect that the Kernel is corrupt. How would I fix this without being able to write to the USB partition?
Click to expand...
Click to collapse
If you have access to fastboot and assuming your flash storage isn't damaged, you should be able to flash over /boot with a boot.img and over /system with a system.img... But you might have to search around for them. Sorry i can't be more help.
kernels ; battery ; ROM ; gov/sched
http://www.mediafire.com/?wg9krukqp43nq1i theres a link to the boot.img for the apex bigxie rom (ics 4.0.3), try flashing that through fastboot i think the command is "fastboot flash boot %imglocation%.img" so just put the img in the folder you usually flash stuff with the fastboot bat in it, then try and flash this boot and tell me what happens.
ps, the %imglocation% should be the name of the img wherever you put it, so it will probably be boot.img.
I've just rooted a Showcase and I followed Cyanogen mod guide for installing their rom. Everything went smooth. Minutes later I started having problems with signal. Since I did a nandroid backup I decided to restore. Everything said completed successfully. When I reboot it stuck into boot loop.
I went back into recovery and tried to wipe cache and dalvik. Error mounting cache. Error mounting system. Error mounting /datadata
I tried to go back to cyanogen and the same Error mounting cache. Error mounting system. Error mounting /datadata. I changed into various clockwork mod versions and the same.
I tried restoring on two versions with Odin and I dont get any logo at all but straight into recovery. saying invalid argument and the same Error mounting cache. Error mounting system. Error mounting /datadata
Did cyanogen changed partition ext (MTD/BML?)? Im out of ideas. I spent the entire day yesterday checking different forums and trying out anything within the showcase area to make this phone boot.
I even tried to find a way to manually restore with the nandroid backup but the partitions wont mount. The only ones that does are /boot and /data and the /sdcard.
The nandroid backup is there. All i need is to be able to restore. The clockworkmod 4 I have now doesn't activate adb so I cant access the phone via command prompt.
UPDATE: I managed to restore my phone. After trying different tars and making tar with nandroid images I found a tar file of {EI20} 2.3.5. I tried it an it boot up well. I install a voodoo CWM and let me restore! Though the phone is not activated on the cdma network, at least its on factory state with the own carrier's software. Its only a matter of them activating the phone back.
UPDATE: I managed to boot it up with a Verizon Odin tar but the Phone is from another carrier so it wont go past the activate screen. I tried flashing the clockworkmod and restoring but im getting the same error mount on system. Any ideas?
lilizblack said:
I've just rooted a Showcase and I followed Cyanogen mod guide for installing their rom. Everything went smooth. Minutes later I started having problems with signal. Since I did a nandroid backup I decided to restore. Everything said completed successfully. When I reboot it stuck into boot loop.
I went back into recovery and tried to wipe cache and dalvik. Error mounting cache. Error mounting system. Error mounting /datadata
I tried to go back to cyanogen and the same Error mounting cache. Error mounting system. Error mounting /datadata. I changed into various clockwork mod versions and the same.
I tried restoring on two versions with Odin and I dont get any logo at all but straight into recovery. saying invalid argument and the same Error mounting cache. Error mounting system. Error mounting /datadata
Did cyanogen changed partition ext (MTD/BML?)? Im out of ideas. I spent the entire day yesterday checking different forums and trying out anything within the showcase area to make this phone boot.
I even tried to find a way to manually restore with the nandroid backup but the partitions wont mount. The only ones that does are /boot and /data and the /sdcard.
The nandroid backup is there. All i need is to be able to restore. The clockworkmod 4 I have now doesn't activate adb so I cant access the phone via command prompt.
UPDATE: I managed to boot it up with a Verizon Odin tar but the Phone is from another carrier so it wont go past the activate screen. I tried flashing the clockworkmod and restoring but im getting the same error mount on system. Any ideas?
Click to expand...
Click to collapse
Which carrier is the Showcase from? You are correct, CyanogenMod changes the partition ext to MTD.
You're probably going to need stock Odin files for your carrier, so that you can repartition back to stock.
Did you take a look at the guide HERE? A lot of info, but explains everything.
jbreakfield said:
Which carrier is the Showcase from? You are correct, CyanogenMod changes the partition ext to MTD.
You're probably going to need stock Odin files for your carrier, so that you can repartition back to stock.
Did you take a look at the guide HERE? A lot of info, but explains everything.
Click to expand...
Click to collapse
The carrier is Open Mobile; its a local carrier on PR. The is no way to get an odin tar of this company unless you take another showcase and via command prompt extract it directly from the phone or another user who did it share it over the internet. The only way I can make the restore say completed is flashing verzon odin tar, flashing CWM 4, flashing cyanogen and rebooting into recovery via cyanogen. I noticed the flashed CWM via odin is only good for flashing cyanogen. It would give allot of error. If I boot into recovery via cyanogen rom I get a CWM 5.0 instead of 4 (when booting on key commands). The CWM 5.0 allow me to restore nandroid and mount partitions but when i reboot device Im stuck at the samsung logo. I left it a few minutes and nothing.
Do you think an MTD to BML converter in a flashable zip will help booting my restore?
jbreakfield said:
Which carrier is the Showcase from? You are correct, CyanogenMod changes the partition ext to MTD.
You're probably going to need stock Odin files for your carrier, so that you can repartition back to stock.
Did you take a look at the guide HERE? A lot of info, but explains everything.
Click to expand...
Click to collapse
I already tried it and get the invalid argument error. no boot image and straight to recovery
lilizblack said:
The carrier is Open Mobile; its a local carrier on PR. The is no way to get an odin tar of this company unless you take another showcase and via command prompt extract it directly from the phone or another user who did it share it over the internet. The only way I can make the restore say completed is flashing verzon odin tar, flashing CWM 4, flashing cyanogen and rebooting into recovery via cyanogen. I noticed the flashed CWM via odin is only good for flashing cyanogen. It would give allot of error. If I boot into recovery via cyanogen rom I get a CWM 5.0 instead of 4 (when booting on key commands). The CWM 5.0 allow me to restore nandroid and mount partitions but when i reboot device Im stuck at the samsung logo. I left it a few minutes and nothing.
Do you think an MTD to BML converter in a flashable zip will help booting my restore?
Click to expand...
Click to collapse
When you flash the verizon odin tar file, are you using an .pit file, and checking repartition? This will get you converted back to BML. The tar file must be a full flash for the repartition to work.
So I am probably breaking a rule but you need help go over to www.rootwiki.com . Go to there forums and look there they have a bunch of people over there developing for the showcase.
Sent from my SCH-I500 using Xparent Blue Tapatalk 2
Okay. Here's the deal.
My friend gave me a used HTC One S. My idea was to flash a new custom ROM on it (preferably something like CM12). He told me it was rooted, so it seemed like it was no problem. Although, it was S-On.
When I turned out on the phone, I first noticed some things. It stayed on the "HTC: Quietly Brilliant" logo, however, it had that red "This build is for development purposes only" text underneath it. After waiting almost an hour, I realized something was up. After a few attempts, I was able to get into bootloader and loaded up TWRP recovery. I poked around in the files to see what the issue could be, when I realized something. The phone was Romless! The /sdcard folder was completely empty, besides a TWRP folder. If I moved up one level, the only folders were:
and-sec
boot
cache
data
dev
devlog
etc
sdcard
license
proc
recovery
res
root
sbin
supersu
sys
system
tmp
usb-otg
and they were all empty.
Okay, so it didn't have a ROM. No big deal, right?
My first idea was to use the CM12 installer. It didn't work; for some reason it thought the device was a Samsung galaxy S2?!
So my next idea was to connect it to my pc and transfer files. Unfortunately, since it was in TWRP, it wouldn't show up on my PC so I could edit the files. So, first I tried mounting storage, but it failed, saying "E: Can't mount /sdcard". So, my next idea was to use USB OTG. After putting the CM12 file on my flash drive and connecting it to the phone, it showed up and I was able to browse the files to install CM12. On my first try, I flashed it straight from the flash drive and rebooted. When this happened, it was on the HTC logo for a good minute, then it rebooted again straight into TWRP. After that, I decided that maybe I'd have to create folders inside /sdcard. So, after a few minutes, I created the empty folders Android, Download, DCIM, Pictures, etc. in /sdcard. I copied CM12 into download and flashed it. Instant failure, giving the same "Can't mount scard" errors.
I tried rebooting. But when I did, all the folders I made as well as CM12.zip were gone!
I also tried using adb push and sideload commands. It still did not work. Still got sd card mounting errors.
Interesting. With that, I turned to XDA for help. After reading a few forums, I downloaded Hasson's All-In-One-Toolkit and tried reinstalling TWRP recovery. No luck. After that, I switched the recovery to PhilZ Touch 5. Still, once again, got internal sd errors for mounting.
Not knowing what else to do, I settled on one other option. RUU. After doing some searching online and finding the right RUU, which was RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2 .exe.
I followed instructions online about RUU and looked for a temp file. While I expecting only one ROM.zip, there were two files called rom_01.zip and rom_02.zip. They both had the same files with the same file names in them, the only difference was rom_01. zip was 35 Mb, while rom_02 was 681 mb. I tried both. They'd give me the same "please flush again immediately" the first time, but after flashing again, every time it would give me "signature verify fail."
With that, I am unsure what else to do. The only thing on the phone at the moment is PhilZ touch 5. Mounting storage does not work, and installing via sideload doesn't either. Any help with this situation is very, very appreciated.
I apologize for how long this post was.
http://forum.xda-developers.com/showthread.php?t=1630459
In order to see anything on system in TWRP, you should have mounted it before (go to Mount and check system). But that's not the point.
You didn't say anything about which One S do you have (S4/Ville or S3/Ville C2),which version of TWRP you have and most important which hboot you're on.
For most ROMs you'll need 2.15 hboot, also because you're S-On you must flash kernel in fastboot after you flash the ROM. You flashed CM12 so I presume you have 2.15 hboot but you never said you flashed also the kernel in fastboot mode. That's why phone don't boot
Sent from nowhere over the air...
Rapier said:
In order to see anything on system in TWRP, you should have mounted it before (go to Mount and check system). But that's not the point.
You didn't say anything about which One S do you have (S4/Ville or S3/Ville C2),which version of TWRP you have and most important which hboot you're on.
For most ROMs you'll need 2.15 hboot, also because you're S-On you must flash kernel in fastboot after you flash the ROM. You flashed CM12 so I presume you have 2.15 hboot but you never said you flashed also the kernel in fastboot mode. That's why phone don't boot
Sent from nowhere over the air...
Click to expand...
Click to collapse
The phone is S4/Ville.
It's on 2.15 hboot as well.
The TWRP version it had was 2.5.0.0.
Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So, I have years of experience rooting and flashing Samsung phones with minimal adb experience. My buddy from work asks me if I can try to fix his shield tab that he F'd up trying to flash a rom on. Come to find out he never unlocked the bootloader or flashed a recovery or rooted the dang thing, just tried to flash the rom over stock like a numbskull. We thought it was dead forever because the only thing that would mount or connect in adb was the side load through the stock recovery. So, I finally got it to connect to fastboot (don't ask me how, I don't know), unlocked the bootloader, and flashed twrp. Now it won't flash supersu in adb sideload, so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent even though it says "success" at the top after flashing. I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so, which one? I have no idea which version bootloader, kernel, or os is, or was, on this device, I'm not familiar with any of the roms for it, and I'm not sure what prerequisites there may be for some of them....
Thanks for the help!
rom fiend said:
it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent even though it says "success" at the top after flashing. I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so, which one?
Click to expand...
Click to collapse
I had the same Problem with the partitions you discribed, have tried wipe them, change the file format and change it back?
I flashed a lot of Roms from the external SD Card and it worked every time.
I think you should go with Bliss Rom. ( Just try Lollipop and Marshmallow)
OverBit said:
I had the same Problem with the partitions you discribed, have tried wipe them, change the file format and change it back?
I flashed a lot of Roms from the external SD Card and it worked every time.
I think you should go with Bliss Rom. ( Just try Lollipop and Marshmallow)
Click to expand...
Click to collapse
I can't wipe them because they won't mount. It's as if the partitions were erased completely. Not like the partitions were wiped, but like they don't exist at all anymore...
What do you mean by changing the file format? Format of what?
rom fiend said:
What do you mean by changing the file format? Format of what?
Click to expand...
Click to collapse
TWRP, wipe ,Advanced wipe
If that doesn't work just try installing a rom, boot it
If that doesn't work try this
Tried all recovery options and tried flashing bliss 6.2 with no luck. It says that it flashes successfully but also shows some errors about not being able to mount the system and data partitions. Then when I try to reboot it gets stuck at the nvidia logo (this is the closest that I've gotten to booting a rom). I can provide pictures if you want. I'm going to try the steps that you linked to as soon as the files download.