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
I waited 2 nights to register so I could wade through fixes and tips and have seem to come up with little to nothing. I have CWM flashed on my phone through ROM Manager with the recovery file replaced in the system/bin and the update zip in the root of the SD card.
When I access CWM and click on Wipe Data/Factory reset it breezes through the first few steps pretty quickly and then gives me this error:
E: format_volume: rfs format failed on /dev/block/mmcblk0p2
It continues past this and then goes on to "formatting sd_card" and then just freezes. I left it on for 30mins and there was absolutely no progress. I've tried battery pulls and re-attempting the wipe with the same result. Have re-flashed CWM, ODIN'ed back to stock, etc etc and still run into the same snag. I'm beyond frustrated because since it never gets past this part I can't install the custom ROM I'm eying and it wipes enough data to have to ODIN every single time and re-root all over again. Just to be clear this error is NOT popping up on bootup but only during Data Wipe/Factory Reset and the only way out of the freeze is to do a battery pull which results in a soft brick.
If it helps any here is what I did prior to ever having run into this problem.
Rooted with SuperOneClick V.2.3.3
Installed ROM Manager
Installed RootBrowser Lite
Downloaded recovery and update zip
Placed both into root of SD card
Used RootBrowser Lite to move recovery file into system/bin
Booted into recovery mode
Attempted to Wipe Data/Factory Reset
Ran into snag on first try and every try thereafter
Can someone please tell me what I'm doing wrong, how to fix it or a workaround?
If possible a very detailed walk through would be appreciated as this is my first ROM flashing. Your help is greatly appreciated!
MidniteKitten said:
I waited 2 nights to register so I could wade through fixes and tips and have seem to come up with little to nothing. I have CWM flashed on my phone through ROM Manager with the recovery file replaced in the system/bin and the update zip in the root of the SD card.
When I access CWM and click on Wipe Data/Factory reset it breezes through the first few steps pretty quickly and then gives me this error:
E: format_volume: rfs format failed on /dev/block/mmcblk0p2
It continues past this and then goes on to "formatting sd_card" and then just freezes. I left it on for 30mins and there was absolutely no progress. I've tried battery pulls and re-attempting the wipe with the same result. Have re-flashed CWM, ODIN'ed back to stock, etc etc and still run into the same snag. I'm beyond frustrated because since it never gets past this part I can't install the custom ROM I'm eying and it wipes enough data to have to ODIN every single time and re-root all over again. Just to be clear this error is NOT popping up on bootup but only during Data Wipe/Factory Reset and the only way out of the freeze is to do a battery pull which results in a soft brick.
If it helps any here is what I did prior to ever having run into this problem.
Rooted with SuperOneClick V.2.3.3
Installed ROM Manager
Installed RootBrowser Lite
Downloaded recovery and update zip
Placed both into root of SD card
Used RootBrowser Lite to move recovery file into system/bin
Booted into recovery mode
Attempted to Wipe Data/Factory Reset
Ran into snag on first try and every try thereafter
Can someone please tell me what I'm doing wrong, how to fix it or a workaround?
If possible a very detailed walk through would be appreciated as this is my first ROM flashing. Your help is greatly appreciated!
Click to expand...
Click to collapse
Did you hit apply update.zip after booting into recovery the first time I don't see that listed in your steps
Sent from my Team Nightmare Amaze4G with Sense 4.0
azcledel said:
Did you hit apply update.zip after booting into recovery the first time I don't see that listed in your steps
Sent from my Team Nightmare Amaze4G with Sense 4.0
Click to expand...
Click to collapse
No, actually, I didn't. I haven't seen a guide point it out or a video that went through this step. Lemme' give this a shot and see if that helps with the problem I'm running into Thanks for the quick response, hoping this is what I was missing!
azcledel said:
Did you hit apply update.zip after booting into recovery the first time I don't see that listed in your steps
Sent from my Team Nightmare Amaze4G with Sense 4.0
Click to expand...
Click to collapse
Unfortunately this didn't seem to fix my problem. Still encountering:
E:format_volume: make_ext4fs failed on /dev/block/mmblk0p2
Formatting /sdcard/ .android_secure...
And frozen again -_- It's bad enough that the sidekick sucks as stock (took me this long to finally want to do something about it) and that it's being difficult and resisting change.
Hmmm was your phone stock before you did anything to it? Or did you get the phone used or something?
My advice would be Odin to stock and start over try redownloading the recovery.zip to make sure it wasn't a bad download. And try again go slow and tripple check to make sure your following the instructions word for word. I've messed them up a few times cuz I got cocky but I got everything down from doing it so much and checking my work. The first time I rooted my sk4g I did it with adb not superoneclick and it was my first android phone it took me 2 hours of reading and following steps perfectly.
Sent from my Team Nightmare Amaze4G with Sense 4.0
go back to stock with odin,
Then root http://forum.xda-developers.com/showthread.php?t=1100513
Flash cwm http://forum.xda-developers.com/showthread.php?t=1124453
And them flash this kernel http://forum.xda-developers.com/showthread.php?t=1663622 (dont freak out with the first boot with this kernel let it convert the partitions to ext4 and a loud voice will tell you what is going on)
Ive had that problem from flashing recovery from rom manager, and when it comes up i just return to stock. try to save and remove the update.zip from the sd card and see if you can get into recovery again and just flash the kernel(if cwm come up)
ultraprimeomega said:
go back to stock with odin,
Then root http://forum.xda-developers.com/showthread.php?t=1100513
Flash cwm http://forum.xda-developers.com/showthread.php?t=1124453
And them flash this kernel http://forum.xda-developers.com/showthread.php?t=1663622 (dont freak out with the first boot with this kernel let it convert the partitions to ext4 and a loud voice will tell you what is going on)
Ive had that problem from flashing recovery from rom manager, and when it comes up i just return to stock. try to save and remove the update.zip from the sd card and see if you can get into recovery again and just flash the kernel(if cwm come up)
Click to expand...
Click to collapse
You are my saviour! I seriously love you! This worked PERFECTLY! I'm now running Glorious Overdos v3.3 and loving every single second of it. Because of you my phone is no longer a nightmare. You deserve a thanks
Using ROM Manager and the latest version of CWM I tried installing today's (12-08) nightly build of CM11 to try it out. After doing a complete backup and then wipe data/cache the install failed. I'm not sure why but it said it was aborted and to check log and report the error to ROM Manager.
After that it asked if I wanted to reboot and I wanted to make sure I restored from my backup so I backed out of the screen but then it booted up on its own. It did not get past the S3 loading screen with the CM Android/alien guy it just turned off, back to that screen again and then back into recovery.
At this point I went to recover from my backup file and it said MD5 mismatch and won't load. I've since tried wiping data/cache/dalvik cache all manually and then boot up, or wipe everything and try to install the rom again... every time it just loops back to recovery mode. The last time I tried installing the rom again it told me I might have lost root access and asked if I wanted to repair it... I'm not sure what that means.
Any suggestions? I am lost at this point. I have no experience with ADB (I'm not sure if that's my only option) but I've used ODIN mode a few times. Easiest solution would be best.
bejahu said:
Using ROM Manager and the latest version of CWM I tried installing today's (12-08) nightly build of CM11 to try it out. After doing a complete backup and then wipe data/cache the install failed. I'm not sure why but it said it was aborted and to check log and report the error to ROM Manager.
After that it asked if I wanted to reboot and I wanted to make sure I restored from my backup so I backed out of the screen but then it booted up on its own. It did not get past the S3 loading screen with the CM Android/alien guy it just turned off, back to that screen again and then back into recovery.
At this point I went to recover from my backup file and it said MD5 mismatch and won't load. I've since tried wiping data/cache/dalvik cache all manually and then boot up, or wipe everything and try to install the rom again... every time it just loops back to recovery mode. The last time I tried installing the rom again it told me I might have lost root access and asked if I wanted to repair it... I'm not sure what that means.
Any suggestions? I am lost at this point. I have no experience with ADB (I'm not sure if that's my only option) but I've used ODIN mode a few times. Easiest solution would be best.
Click to expand...
Click to collapse
I had the exact same issue when trying to flash that same CM11 nightly build but with TWRP...
I just pulled the battery took my SD card out and reinserted it and I just kept booting into recovery and turning the phone off until it let me reflash a rom or backup. Obviously this isnt the most legitimate solution but that could work for you! It did for me!...
This could have been caused by needing an update of CWM or TWRP to better support 4.4 perhaps?
Badouken said:
I had the exact same issue when trying to flash that same CM11 nightly build but with TWRP...
I just pulled the battery took my SD card out and reinserted it and I just kept booting into recovery and turning the phone off until it let me reflash a rom or backup. Obviously this isnt the most legitimate solution but that could work for you! It did for me!...
This could have been caused by needing an update of CWM or TWRP to better support 4.4 perhaps?
Click to expand...
Click to collapse
I tried that to no avail. I unfortunately had to revert to stock unrooted via ODIN mode and it got me to boot back up. I can just reroot now. Luckily I made a backup with Titanium and uploaded it to my Google Drive.
Hi guys,
I'm running my Moto G 16GB on Kitkat 4.4.2 system version 175.44.1.falcon_umts.Retail.en.DE. Today it offered to download and install the latest OTA update (called 176.44.1.en.DE). I started the download and tried to install it.
After downloading the update was placed in /cache. The file name was 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE.zip', which surprised me. I was expecting something like 'Blur_Version.176.44.1.falcon_umts.Retail.en.DE.zip'.
When I tried to install it without removing root and without going back to stock recovery it ended with a signature error in CWM. Installing the untrusted zip manually didn't work as well - as expected.
Then I tried to follow advise from other threads and went back to stock recovery (extracted from a full install package 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE' - 444MB) That seemed to work and the install of the OTA update went fine before getting stuck on the boot animation on the first boot. It sat there for 10 minutes before I rebooted and restored a CWM backup.
I'm running out of ideas. Some say it's sufficient to go back to stock recovery temporarily. Others say you need to go back to full stock.
I have to repeat that I'm rooted and that I've de-activated a few unused apps (mainly harmless google stuff (hangout, search, music and so on) and Motorola Assist, Migrate and 'Context Services') .
Are there further findings about what stops the OTA from succeeding?
Many thanks in advance,
Kleo2
Kleo2 said:
Hi guys,
I'm running my Moto G 16GB on Kitkat 4.4.2 system version 175.44.1.falcon_umts.Retail.en.DE. Today it offered to download and install the latest OTA update (called 176.44.1.en.DE). I started the download and tried to install it.
After downloading the update was placed in /cache. The file name was 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE.zip', which surprised me. I was expecting something like 'Blur_Version.176.44.1.falcon_umts.Retail.en.DE.zip'.
When I tried to install it without removing root and without going back to stock recovery it ended with a signature error in CWM. Installing the untrusted zip manually didn't work as well - as expected.
Then I tried to follow advise from other threads and went back to stock recovery (extracted from a full install package 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE' - 444MB) That seemed to work and the install of the OTA update went fine before getting stuck on the boot animation on the first boot. It sat there for 10 minutes before I rebooted and restored a CWM backup.
I'm running out of ideas. Some say it's sufficient to go back to stock recovery temporarily. Others say you need to go back to full stock.
I have to repeat that I'm rooted and that I've de-activated a few unused apps (mainly harmless google stuff (hangout, search, music and so on) and Motorola Assist, Migrate and 'Context Services') .
Are there further findings about what stops the OTA from succeeding?
Many thanks in advance,
Kleo2
Click to expand...
Click to collapse
If your phone is rooted or there is a CWM installed or there is any change in system files then ota will fail till you flash stock rom. You can't just bring back stock recovery. You have to "delete" root as well.
There is some info http://forum.xda-developers.com/showpost.php?p=47495650&postcount=6
I will post my case here, I had the same problem, I had CWM and root and when I rebooted to update I get installation failed and boot loop.
Then I just flashed stock recovery (only) rebooted and now I already have the update installed
CromoPT said:
I will post my case here, I had the same problem, I had CWM and root and when I rebooted to update I get installation failed and boot loop.
Then I just flashed stock recovery (only) rebooted and now I already have the update installed
Click to expand...
Click to collapse
Hi, thanks for your replies. Because of your report and others, who state the same (installing stock recovery only to get the update working) I was hoping to get around going back to full stock. It always takes a lot of time to configure the phone the way it was configured before essentially wiping.
Just to repeat what I did: when I try to install the OTA while CWM is installed there's just an error message in CWM, the update fails, but the phone is working normally afterwards. It's just not updated.
When I try with stock recovery the update process finishes without errors, but the phone get stuck during the boot animation.
Maybe there's a way to fix the boot loop?
Looking forward to any suggestions
Cheers, Kleo2
I tried again and found a way without going back to full stock.
1. flashed stock recovery from full 175.44.1 image
2. let the phone download the OTA and restart to install it
3. ota install in stock recovery went fine
4. reboot -> stuck on boot animation again
5. flashed CWM and wiped cache AND dalvik cache
6. next boot took longer than normal but got past the boot animation
7. android optimized/cached my apps and then started normally
8. version is now 176.44.1 and the phone seems to work normally (after 30 minutes of usage)
Hope that helps someone and that I won't have issues going forward because I did it this way.
Cheers, Kleo2
Kleo2 said:
I tried again and found a way without going back to full stock.
Click to expand...
Click to collapse
Thanks. :good: Did 1 to 3 and phone booted just fine (not stuck on boot animation)
My phone: No logo fix, root, Xposed Framework
After update root was still there, Xposed needed a new install
total noob
i would so much like to update my rooted moto g.. because of my card reader.
does anyone know a step-by-step-for-complete-noobs-post and could provide a link?
i'm just starting.. and so happy and proud that i got my phone rooted.. and that i got rid of this rebooting problem by erasing the cache.
but i'm already lost when i read "flashed stock recovery".. yeah i know: that much noob!
help would be much appreciated!
Papshmir
Papshmir said:
i would so much like to update my rooted moto g.. because of my card reader.
does anyone know a step-by-step-for-complete-noobs-post and could provide a link?
i'm just starting.. and so happy and proud that i got my phone rooted.. and that i got rid of this rebooting problem by erasing the cache.
but i'm already lost when i read "flashed stock recovery".. yeah i know: that much noob!
help would be much appreciated!
Papshmir
Click to expand...
Click to collapse
I UPDATED my rooted Kitkat Tesco version SUCCESFULLY! and still rooted.
What I did:
1. install Motorola Device Manager (RESTART computer and telephone)
2. downloaded MotoTool
3. Made a Nandroid backup in CMW, made a backup with MotoTool too. Just in case
And deactived (did not uninstall) my Xposed framework modules (if you dont have it, you dont need to)
I have some system apps disabled, but didnt re-activate it. (was too lazy haha)
4. downloaded the correct ROM from: http://sbf.droid-developers.org/phone.php?device=14 (Tesco UK 4.4.2)
5. unzipped the ROM and rename and overwrite the recovery.img to the exact name as in the MotoTool All In One 2.6\Data\KitKat\StockKitKatrecovery.img (Just for sure it's the same as my ROM, I dont know if all the ROMs have the same recovery sooo )
6. started MotoTool, unplug&replug device. Checked KitKat option in the program, did a connection check, it was okay. Did a NORMAL restart via progam. You have to grant permisson on your phone.
7. after reboot, rebooted the phone to FASTBOOT.
8. Checked Stock Fastboot in the program, it flashed succesfully. Then I went into recovery (1×down volume, then 1× up volume) checked if the recovery was working. It was working (android logo+ no command error message)
9. reboot (long press power button)
10. Updeted OTA, settings/inf./update.. blabla okay okay next next. Wait until it downloads (only 7.9 MB )
11. wait for the update to be done, then it reboots, then apps are being updated. Everything looks fine and working
+1 flash CMW or other recovery again.
Hope this helps! I was afraid to do it too. I'm not used to MotoTool and other Motorola stuff because I had a HTC Desire, it was much simplier with that. But no risk here either! Good luck!
So I am trying to put back my stock recovery so I can take the OTA, but after I flash the recovery and try to reboot to it, it says "No Command". I have reflashed TWRP and then the stock recovery again with the same result. The phone itself will boot fine, but I can't install the OTA as it gets an error part of the way into the install. Any ideas? I have the 1034.
EDIT: Well I remembered I did the H+ mod, so after reverting that the OTA flashed I had Faux Kernel before hand, but after reflashing it my wi-fi wont enable, any ideas?
Thanks!
Kleo2 said:
I tried again and found a way without going back to full stock.
1. flashed stock recovery from full 175.44.1 image
2. let the phone download the OTA and restart to install it
3. ota install in stock recovery went fine
4. reboot -> stuck on boot animation again
5. flashed CWM and wiped cache AND dalvik cache
6. next boot took longer than normal but got past the boot animation
7. android optimized/cached my apps and then started normally
8. version is now 176.44.1 and the phone seems to work normally (after 30 minutes of usage)
Hope that helps someone and that I won't have issues going forward because I did it this way.
Cheers, Kleo2
Click to expand...
Click to collapse
Thanks,
Wiping cache and dalvik cache did the trick for me. You saved my day
Please please help
I have the same problem. I've tried to update the new OTA and failed. After restoring full stock rom, the system simply doesn't boot!
I had Faux Kernel and GravityBox but I didn't revert anything. I thought that a full stock rom would clear all system settings.
This is my version of stock (Blur_Version.174.44.9.falcon_umts.Retail.en.GB) and I tried to flash it several times now. No success. I get stuck on the boot logo.
I tried to downgrade to 4.3 using version Blur_Version.14.71.8.falcon_umts.Retail.en.GB. I was able to boot and see the initial setup but I have no WIFI! I was trying to install 4.3 then try to update via OTA but OTA only works with WIFI so I'm stuck.
I also tried installing the 24th Feb nightly build of Cyanogen and the device also booted but with no WIFI.
I really don't know what to do! Please help me. I've tried other stock images out of despair but none with sucess.
Does anyone have a clue to what might be to problem and how to revert it?
Thank you
draco259 said:
So I am trying to put back my stock recovery so I can take the OTA, but after I flash the recovery and try to reboot to it, it says "No Command". I have reflashed TWRP and then the stock recovery again with the same result. The phone itself will boot fine, but I can't install the OTA as it gets an error part of the way into the install. Any ideas? I have the 1034.
EDIT: Well I remembered I did the H+ mod, so after reverting that the OTA flashed I had Faux Kernel before hand, but after reflashing it my wi-fi wont enable, any ideas?
Click to expand...
Click to collapse
Before flashing stock ROM try to clear/format all your partitions with a custom recovery!
Sent from my XT1032 using xda app-developers app
I installed the OTA update using the CWM recovery but not root, I changed the update-script to not give error during installation
Hui91 said:
I UPDATED my rooted Kitkat Tesco version SUCCESFULLY! and still rooted.
What I did:
1. install Motorola Device Manager (RESTART computer and telephone)
2. downloaded MotoTool
3. Made a Nandroid backup in CMW, made a backup with MotoTool too. Just in case
And deactived (did not uninstall) my Xposed framework modules (if you dont have it, you dont need to)
I have some system apps disabled, but didnt re-activate it. (was too lazy haha)
4. downloaded the correct ROM from: http://sbf.droid-developers.org/phone.php?device=14 (Tesco UK 4.4.2)
5. unzipped the ROM and rename and overwrite the recovery.img to the exact name as in the MotoTool All In One 2.6\Data\KitKat\StockKitKatrecovery.img (Just for sure it's the same as my ROM, I dont know if all the ROMs have the same recovery sooo )
6. started MotoTool, unplug&replug device. Checked KitKat option in the program, did a connection check, it was okay. Did a NORMAL restart via progam. You have to grant permisson on your phone.
7. after reboot, rebooted the phone to FASTBOOT.
8. Checked Stock Fastboot in the program, it flashed succesfully. Then I went into recovery (1×down volume, then 1× up volume) checked if the recovery was working. It was working (android logo+ no command error message)
9. reboot (long press power button)
10. Updeted OTA, settings/inf./update.. blabla okay okay next next. Wait until it downloads (only 7.9 MB )
11. wait for the update to be done, then it reboots, then apps are being updated. Everything looks fine and working
+1 flash CMW or other recovery again.
Hope this helps! I was afraid to do it too. I'm not used to MotoTool and other Motorola stuff because I had a HTC Desire, it was much simplier with that. But no risk here either! Good luck!
Click to expand...
Click to collapse
At part 8, I am getting an image of the android guy with his stomach open with a big red '!'. That's 'no command' right?
Any ideas? I have no idea what I am doing
Guys, a really easy way to update is:
1. Install Philz recovery - http://forum.xda-developers.com/showthread.php?t=2639583
2. Reboot and then download the OTA update when prompted - select Install when prompted
3. It will now reboot into Philz recovery, install the update and reboot
4. You'll see Android is Upgrading...
5. Re-boot back into recover and re-install faux kernel
I have just upgraded my XT1032 on 174.44.9 en GB (rooted + faux008) to 176.44.1 using this... worked like a dream! All I had to do was re-install faux kernel as that was overwritten by the OTA, but Root was in-tact...
i have root, twrp recovery and faux kernel, the problem is only faux kernel? Or I must remove all? (root recovery etc)
everything was working fine for almost a year. twrp, magisk, everything was working as intended. decided to update to the july stable build (walleye-pq3a.190705.001) and decided id like a fresh start. ok cool, easy enough, just boot into the bootloader/fastboot mode and use the flash-all script, done. flash TWRP 3.3.0 using "TOOL ALL IN ONE". installs fine, reboots fine, cool. reboot to recovery to install the magisk 19.3 zip. wait what? password not accepted? it works in system, and is the same password i always use for the phone (i just use one to prevent butt dialing). ok fine whatever lets just reboot and completely remove all security for now, and figure that one out later. reboot into twrp, no password this time. excellent. lets flash this zip (same zip that i downloaded directly from magisk manager before starting any of this, also tried an old copy that i used to root the first time). everything looked like it was fine, so i rebooted to system. waited about 3 - 5 minutes, and it rebooted to recovery. hmm, odd, maybe just a bad cache or something. rebooted again. same thing, kicked back to recovery. ok, lets do dalvik/cache. nope, same problem. redid flash-all, and manually installed TWRP using fastboot to boot an img, push the twrp installer zip, flash that. same problems. changed slots, flash-, manual twrp flash, same problem. factory reset, repeat flashing, same problem. format system and data partition to get rid of everything, reflash, same problem. theres other stuff that ive tried that i dont remember too.
EDIT: also tried restoring an old TWRP backup from feb. and got the yellow auth error on the bootloader
where i currently sit is i can get a factory image on there and can get twrp on there, and even flashed lineage just for ****s and giggles, and that even worked (esim manager kept crashing, didnt test much else, but it booted and was functional for what little i tested).
TLDR: twrp wont accept pin, and when i disable the pin and flash magisk i can no longer boot even though these are the same files that have been on my E drive since the day i got it, which worked fine back then. it almost feels like theres some kind of corruption somewhere.