Database Info

Recovery Issue with both CWM and TWRP

I posted this in Q&A, but no replies led me to post here as well.
Hi. I've been using this Xoom for a couple weeks now, and just started having this problem yesterday.
Before I noticed the promblem I was on EOS 3 Wingman. I had TWRP 2.2.2.0 as recovery.
I wanted to give CM10 nightlies a shot. Downloaded the ROM and GAPPS through Goo. I tried to flash the CM10 ROM and GApps zip through the Goo interface. Xoom rebooted and instead of installing, I just got a contantly repeating error saying the install failed.
Eventually I rebooted the xoom and went into recovery. I tried to wipe data and it said it couldn't be mounted. Same error for wiping system, cache, etc...
Rebooted xoom and the EOS 3 rom was still working fine, I downloaded [Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]" and flash via adb. rebooted to recovery and tried wipe. same issue. nothing could be wiped. everything said "failure mounting <applicable partition>".
I tried flahing rogue recovery and got the same thing. I said screw it and rebooted back into EOS and it's been working fine. EOS was updated last night to 143, so i downloaded and tried to install through goo. I got the repeating errors again. Rebooted into recovery and still got the errors where it seems like none of the partitions are writeable.
I WAS able to install the EOS update directly through recovery.
Has anyone ever seen this behavior before and know how to fix it? I can't even export logs in the 2 CWM recoveries because they fail when trying to write the log file.
If I try to install an update through goo, it reboots to recover and just keeps scrolling "An Update Error has occured".
I can reboot to recovery and install the zip from there directly with no issue.
Here is the log for the failed data wipe...
I:mke2fs command: mke2fs -t ext4 -m 0 /dev/block/mmcblk0p10
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p10 is apparently in use by the system; will not make a filesystem here!
E:Unable to format data.
* Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid, command: 'blkid'.
* Verifying partition sizes...
Ievice has /data/media
I:Total used space on /data is: 5122715648
I:Total in /data/media is: 3962468352
I:Actual data used: 1160247296
du: /data/media/.android_secure: No such file or directory|
once in recovery, if I try to format data, it says "Unable to format data". Log

Well I can't help, I'm in the same boat...hoping to get some insight from any responses you might get.

grey.ghost said:
Well I can't help, I'm in the same boat...hoping to get some insight from any responses you might get.
Click to expand...
Click to collapse
It's extremely unusual to get no responses to an issue like these here at XDA. leads me to believe it might be a very uncommon problem. The folks here are usually on the ball about any issue that has even arisen before.
That being said, I am going to try to flash the stock RUU back on from this link...
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard
After I finish, I re-root/unlock.
I'll let you know how it goes.

I'll let you know if I come up with something as well. So far I've managed to erase the sd card and maintain a constant boot loop.

Flashing all of the stock img, relocking, and unlocking again didn't do ****.
Found an original MZ600 SBF, which is what I need for verizon 3g xoom, I'm installing this via RSD Lite to see if it blows away whatever is causing the issue.

I was able to wipe the entire system and use adb to repeat the unlock and root steps. So far so good. I'm using the CWM 3.2.0.0 recovery image right now though. I have at least been able to get into a clean copy of a ROM and no bootloops yet. Can't restore data off old Nandroids, so I'm about to update to the newer CWM based recovery image and see if that will help.

I think I'm OK now.
I installed the SBF. Let all of the OTA updates come in including the ICS update where my 3g stops.
flashed the ROGUE recovery from fastboot.
I was able to format all partitions and install and boot CM9 nightly.

Me too, i was sweating hard for a bit, but was able to go through the entire process from stock, unlock, root, rogue recovery and then flashed CNA. Got that working without boot loops or fc and then advance restored data from a previous nandroid through rogue to get it back. A couple of apps had to be redownloaded from the market, but it looks as if I'm back in business. I want to try TWRP, but every time I do something screws up, so I think I'll stop trying.
Thanks for the help.

grey.ghost said:
Me too, i was sweating hard for a bit, but was able to go through the entire process from stock, unlock, root, rogue recovery and then flashed CNA. Got that working without boot loops or fc and then advance restored data from a previous nandroid through rogue to get it back. A couple of apps had to be redownloaded from the market, but it looks as if I'm back in business. I want to try TWRP, but every time I do something screws up, so I think I'll stop trying.
Thanks for the help.
Click to expand...
Click to collapse
Are you installing Twrp from goo manager. Cause I have not had any issues with the goo manager download. But did have issues with the zip file here on xda. I dont kknow if it is worth a try but that is how I did it.
Sent from my Xoom using xda app-developers app

Well sense this is a twrp related issue I would think u would have asked in my thread where I released the port for twrp to Xoom,
Having said that, at one point n time there was a note n the open about open script recovery. But its is also buried in the thread too. So I will answer your question and also presume a few things... and please correct me if I am wrong anywhere.
Once u set the download path in goo app to /data/media/goomanager/ and downloaded a ROM, clicked flash ROM, and entered recovery once u saw all the E/ update error u manually rebooted the Xoom and did not let the script finish installing the ROM? If I am correct that so far. That's what cause your additional problems. You basically rebooted recover while mid install of a ROM.
Now as stated it the twrp thread for Xoom, these errors are false errors and should be ignored. To add it the reassurance that they are intact false errors, from goo app select to flash a ROM again and simple allow the script to finish and then the tablet will reboot on its own when it is finished with the script. And you will be greeted with your new ROM you just successfully flashed.
Again let me know if I am wrong on assuming you forced a reboot mid install ( aka while u saw all the errors)
Sent from my Nexus 7 using Tapatalk 2

runandhide05 said:
Well sense this is a twrp related issue I would think u would have asked in my thread where I released the port for twrp to Xoom,
Having said that, at one point n time there was a note n the open about open script recovery. But its is also buried in the thread too. So I will answer your question and also presume a few things... and please correct me if I am wrong anywhere.
Once u set the download path in goo app to /data/media/goomanager/ and downloaded a ROM, clicked flash ROM, and entered recovery once u saw all the E/ update error u manually rebooted the Xoom and did not let the script finish installing the ROM? If I am correct that so far. That's what cause your additional problems. You basically rebooted recover while mid install of a ROM.
Now as stated it the twrp thread for Xoom, these errors are false errors and should be ignored. To add it the reassurance that they are intact false errors, from goo app select to flash a ROM again and simple allow the script to finish and then the tablet will reboot on its own when it is finished with the script. And you will be greeted with your new ROM you just successfully flashed.
Again let me know if I am wrong on assuming you forced a reboot mid install ( aka while u saw all the errors)
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
No, after pushing the TWRP recovery to the Xoom using adp, I would clean install a ROM and get one of two results....1) the ROM would run for a few seconds and then reboot, or 2) the ROM would run, but everything would fc. Fixing permissions, wiping everything, etc., wouldn't help the issue. No matter what I tried under TWRP, those were the results. I ended up having to start from scratch to negate whatever it was that was making the xoom go funky. Once I pushed rogue and followed the same process, I was back in business.
Sent from my Xoom using Tapatalk 2

DEV help, or experienced tweakers (MIUI, CleanROM)

Trying various ROMs before i decide on one to get settled in to.
1. MIUI 2012.09.14
- flashed ok, rebooted, stuck on startup animation doesnt boot.
(downloading 2012.09.29)
2. CleanROM
- flashed ok, rebooted ok, error; "com.android.phone has stopped working" before i get past lock screen.
This happens another 2 - 4 times while im trying to get thru phone setup.
Before eventually it boots back to startup animation, and repeats the process.
3. CNA
- flashed ok, rebooted ok, loaded semi ok before multiple errors;
Unfortunately phone has stopped.
Messaging has stopped.
System UI has stopped working.
Any ideas? I was kinda keen to see all of of these ROMs operate.

Wobzy said:
Trying various ROMs before i decide on one to get settled in to.
1. MIUI 2012.09.14
- flashed ok, rebooted, stuck on startup animation doesnt boot.
(downloading 2012.09.29)
2. CleanROM
- flashed ok, rebooted ok, error; "com.android.phone has stopped working" before i get past lock screen.
This happens another 2 - 4 times while im trying to get thru phone setup.
Before eventually it boots back to startup animation, and repeats the process.
3. CNA
- flashed ok, rebooted ok, loaded semi ok before multiple errors;
Unfortunately phone has stopped.
Messaging has stopped.
System UI has stopped working.
Any ideas? I was kinda keen to see all of of these ROMs operate.
Click to expand...
Click to collapse
1) you must be on newer hboot and need to flash boot.IMG via fast boot manually.
2) you need to do a factory data reset then reflash.
3) Same as number 2.
Sent from my One X using xda app-developers app

h8rift said:
1) you must be on newer hboot and need to flash boot.IMG via fast boot manually.
2) you need to do a factory data reset then reflash.
3) Same as number 2.
Click to expand...
Click to collapse
Cheers bud, awesome.
The steps only said wipe, and someone had told me factory reset only works on stock ROM?
Incorrect?
And forgive my ignorance, hboot?

Ok heres where im at;
- reset to bootloader
- factory reset
- booted to twrp
- wipe system (not sdcard)
- install (no roms, no backup of stock - sdcard is wiped)
kinda panicked a little.
- mounted as usb
- copied roms from laptop back to sdcard
- install (still no roms)
getting more panicked.
- create partition intending to copy roms over again
- roms mysteriously just appear on sdcard after partition created
- installed cna, had one error of unfortunately system ui has stopped working, but no reoccurence.

Never factory reset or clear storage or any of that in hboot. You were supposed to factory reset in twrp. Factory reset in twrp clears data,cache,dalvik it does not wipe your storage.

All of those must of been dirty flashes ...just USB mount in twrp. And copy a rom over

DvineLord said:
Never factory reset or clear storage or any of that in hboot. You were supposed to factory reset in twrp. Factory reset in twrp clears data,cache,dalvik it does not wipe your storage.
Click to expand...
Click to collapse
****. Thanks.
The partition i created to backup and hold roms was 2gb.
In file manager & when mounted as usb i can see the files i copied over as well as the standard sdcard folders.
But i cant see any evidence of a partition.
Only when i check my available space my total sdcard is now 24gb.
Can u help me understand also how i couldnt see the copied files until i created the partition in recovery?

I did some bootloader wipes and recovery wipes, ended up messing up storage bad. Had to ruu in the end.

DvineLord said:
I did some bootloader wipes and recovery wipes, ended up messing up storage bad. Had to ruu in the end.
Click to expand...
Click to collapse
Ok i searched and downloaded the RUU based on my hboot info;
- RUU Evita UL Telstra WWE 1.89. 841.9 Radio 0.18c.32.09.01 10.9 3a.32.20L release 266699 signed .exe
Just in case i've left anything out or anyone wants to jump in, this is the story;
Brand new stock Telstra HTC One XL (Australia)
Unlocked & rooted, TWRP recovery.
Backed up stock.
Installed a few different ROMs before deciding on one.
Accidentally reset factory from hboot instead of twrp.
Lost stock ROM back up.
Mounted USB & copied custom ROMs back across to sdcard.
Files did not appear on sdcard.
Decided to partition and try again.
On sucessful partition, suddenly all files became visible, despite partition warning "all files will be deleted"
Flashed Viper XL successfully.
SDcard total storage reading as 24gb (32gb stock)
1. if i have done anything to reduce my available storage i want to get it back.
2. id like to go back to stock rom and basically start from scratch with clean stock backup and clean storage.
I found a link to the ATT One X stock rom on the US HTC support site.
I cant find anything similar on the AU site for the One XL.
On the xda thread the link was located on, i read that i have to re-lock my bootloader, thats fine theres a tutoriall, but i need to find the stock rom.
That tutorial however didnt mention anything about RUU.
Will ruu enable me to do this internally?
Thanks in advance.

All sorted, RUU is at 15% thx for the help.

There is a 1.89 being hosted in the football ruu collection and other places if you havent found it already, dont run the at&t 2.20 ruu.

[Q] ViperOneS 2.2.0 OTA

Hey guys, since my post count is too low to post my problems with this OTA update in the development section of this rom, ill do it here. Sorry for that.
I think im having no problems with flashing the 2.1. ROM yet but i have my concerns if i did that right.
First problem with flashing it, is the question if im having a custom kernel. I flashed ViperOneS a several times but made a fullwipe before.
So am i having a custom kernel or not?
Next issue is that im only able to flash this ROM with CWM. TWRP 2.5 doesnt work and even 2.3.3.0, which should work, but does not for me...
Well with CWM i ll do it that way:
1. Doing Fullwipe in CWM (Factory reset, Wipe Cache, Wipe Dalvik and System).
2. Flashing the ROM and choosing HTC Theme > Custom Kernel? > not sure sometimes "yes" sometimes "no".
3. Flash finished? > asks me if i want to reboot (into system) or save the logs. Since the instruction tells me to flash the boot.img first before rebooting...
4. ... im going into bootloader via adb which works
5. flash the boot.img
6. fastboot erase cache
7. reboot system
8. before doing the first setup i go into recovery and wipe cache.
I think 2.1 works but i want to be sure if i did everything right, especially with the custom kernel question and that i reboot into bootloader right after aroma says that the flash is finished.
Now i want to flash the 2.2.0 OTA because the update function through the ROM didnt work for me last time (it downloads the OTA but wasnt able to flash)
Im not sure how to flash the OTA right via recovery. Everytime i did that the ROM was kinda messed up, like when im turning the screen off and on Sense keeps loading and it takes some sec to unlock. And the venom tweaks app is totally laggy, even with the "trick" to go into app settings and wipe the cache and data which found on any other site (not xda...).
The problem is that they dont keep their instructions up-to-date (+ how to flash the OTA... right)
It looks to my like there are 100 different ways to flash 2.1.0 and 2.2.0 and only 1 is the right way which lets the ROM being amazing...
Hope you can help me. Thanks in advance!

turnschuh said:
Now i want to flash the 2.2.0 OTA because the update function through the ROM didnt work for me last time (it downloads the OTA but wasnt able to flash)
Im not sure how to flash the OTA right via recovery. Everytime i did that the ROM was kinda messed up, like when im turning the screen off and on Sense keeps loading and it takes some sec to unlock. And the venom tweaks app is totally laggy, even with the "trick" to go into app settings and wipe the cache and data which found on any other site (not xda...).
Click to expand...
Click to collapse
All you have to do ist to flash the OTA with your custom recovery like any other flashable zip if this isn't done automatically. You can simply copy it to your device from your pc or flash it from your mobiles download folder, it doesn't matter which way.
The 'trick' is very well known here at xda, but simply nobody wants to repeat it a hundred times... Here at xda there is even included the fact, that after rebooting you should change your skin once to get things going besides wiping cache and data in venom tweaks and hub.
What EXACTLY doesn't work with TWRP 2.3.3.0?

All you have to do ist to flash the OTA with your custom recovery like any other flashable zip if this isn't done automatically. You can simply copy it to your device from your pc or flash it from your mobiles download folder, it doesn't matter which way.
Click to expand...
Click to collapse
yea i did it like that. i just flashed it in the recovery, but im not sure if i have to wipe caches after or before doing that.
The 'trick' is very well known here at xda, but simply nobody wants to repeat it a hundred times... Here at xda there is even included the fact, that after rebooting you should change your skin once to get things going besides wiping cache and data in venom tweaks and hub.
Click to expand...
Click to collapse
about finding such "tricks": the problem is that those ROM release threads have tons of post (500+ sites of them) and it seems like 90% are from people who didnt even flash the ROM... i think you ll excuse me if i say i got tired of searching for my problems there^^
well can u tell me which skin i have to change? on venom tweaks or the htc skin on personalization? and app settings > venom tweaks > wipe cache and data right?
What EXACTLY doesn't work with TWRP 2.3.3.0?
Click to expand...
Click to collapse
when i flash it with 2.3.3.0 (or 2.5... its the same), the flash process doesnt even take up to 2 seconds and it says its finished and that causes a bootloop but doesnt make me wonder.
dont you have problems with TWRP flashing sense roms either?
ah and another one: did i flash the version 2.1 right and what about the custom kernel question?
well thanks for ur time.
edit: well this time flashing with twrp 2.3.3.0 worked somehow, but i choosed flashing without wipe (made it in recovery) and not to delete apps with aroma installer (which i did before)... just strange.

new problem. dont know whats wrong with my phone but:
wanted to make a backup of my ViperOneS 2.1 with TWRP 2.3.3.0 after lets say 70% of progress it starts turning off my phone and restarts into system. i flashed 2.5.0.0 but its the same issue (edit#1: with CWM too...). strange is that TWRP turned out my phone before when i wiped something there.
i think somethings really messed up atm...
edit#2: had to run a ruu over the system again, flashed twrp and backups seem work again..strange ****

[Q] Factory reset doesn't unmodify so I can update my software

Way back when, I modified my 4.1.2 tab so I could use the Switchme app. Since it hasn't had a software update since then, I need to unmodify my system, so I did a hard reset but that doesn't seem to unmodify it so I can get it updated. Do I have to flash to a stock ROM, or won't that help either? I've done a hard reset twice now and restoring my Samsung account does seem to work either. Help PLEASE!

Nope it does not.
Stoney60 said:
Way back when, I modified my 4.1.2 tab so I could use the Switchme app. Since it hasn't had a software update since then, I need to unmodify my system, so I did a hard reset but that doesn't seem to unmodify it so I can get it updated. Do I have to flash to a stock ROM, or won't that help either? I've done a hard reset twice now and restoring my Samsung account does seem to work either. Help PLEASE!
Click to expand...
Click to collapse
Factory reset only Clears out use added content apps and Personal Settings. To get back to stop you will ..
1 Download the Correct Latest Version Of Android From Sam-mobile or Samsung For your Device.
2. Download odin for your device
3. Make sure you can access your device from windows or os your using.
4. Follow instructions for getting into download mode and flashing the samsung firmware with odin from your computer.
5 . Reboot the device and Leave it be..
Never flash anything on any Device until you know how to get back.
There are many Threads with step by step details on the above. even many youtube videos..
Good Luck

Hey,
I don't think you have to flash back to a stock ROM in order to upgrade to a different ROM. I was able to upgrade my tab with 4.1.2 (I can't remember what ROM it was) right to GNABO then a few hours later to Carbon, and a few hours later to Hyperdive and I'ts running fine with no issues besides the Aroma freezing, but what else is new...
You shouldn't have to flash back to a stock ROM to flash to a modified ROM, reason being is the modified ROM Flashes over the current ROM on the device, so the original ROM will be deleted anyways. The new ROM contains the updates for you, that's the advantage of androids. I recommend trying a few OS's before you pick the one for you stick with it. If you want to go stock there is a thread somewhere in the DEV section with the stock ROM just do some searching.
Make sure when you install a ROM to ;
Backup your device and make sure to keep a copy of the backup to your pc!
Boot into CWM Recovery or TWRP
Wipe data / factory reset
Wipe cache
Wipe dalvik cache
Install ROM from SD
Good Luck

[Q] I have messed up my phone

I was on stock 4.3 and i decided to upgrade to the [ROM][9.15.14] LikeWise Galaxy S5 | TouchWiz 4.4.2 | NE4 | Version 4.1.
It didn't work. It gets stuck on the s5 samsung logo boot. I decided to return to 4.3 but it doesn't work it gives the status 7 error.
Files i have
1. d2att_I747UCUEMJB_modem.zip
2. I747UCUEMJB_bootloader.............. I am not able to flash this
3. att-LikeWise-v4.1-NE4-9-15-14
4. update43
Please I need help

can you please elaborate as to the steps you took, how this event occured, please be as detailed as you can.

MadHakker said:
can you please elaborate as to the steps you took, how this event occured, please be as detailed as you can.
Click to expand...
Click to collapse
My device is Samsung S3 I747
I was running 4.3 without root for a while before i rooted it. Before i installed the likewise ROM, i wiped my phone - Lost some data but that's irrelevant now. Then i flashed the likewise v4.1 ROM using philz_touch_6.07.9 recovery after twrp didn't work... after it reboots it hangs on the S5 boot animation.
I tried this a couple of times and still the outcome was the same. Then i tried to fallback to my 4.3 and then it gave me the status 7 error. In frustration, i tried downgrading from 4.3 - knowing well that it wouldn't work- that also failed.
I have flashed these ROMs a number of times now and still the outcome hasn't changed.

Slemgen07 said:
My device is Samsung S3 I747
I was running 4.3 without root for a while before i rooted it. Before i installed the likewise ROM, i wiped my phone - Lost some data but that's irrelevant now. Then i flashed the likewise v4.1 ROM using philz_touch_6.07.9 recovery after twrp didn't work... after it reboots it hangs on the S5 boot animation.
I tried this a couple of times and still the outcome was the same. Then i tried to fallback to my 4.3 and then it gave me the status 7 error. In frustration, i tried downgrading from 4.3 - knowing well that it wouldn't work- that also failed.
I have flashed these ROMs a number of times now and still the outcome hasn't changed.
Click to expand...
Click to collapse
did you wipe everything and perform a clean install?
anyway try this from cwm touch:
from the recovery menu, go to mounts and storage and make sure you format the following partitions:
> system
> data
> cache
> sd-ext (if you have a parted sdcard, this is the ext4 partition for your link2sd. do NOT format the sdcard because that where your files are)
go back to the main cwm screen afterwards then do the "Wipe Dalvik Cache" option.
try installing the new ROM you are trying to install.
NOTE: Please read This. If you need information on the CWM menu options. It will help a lot i tell ya.

MadHakker said:
did you wipe everything and perform a clean install?
anyway try this from cwm touch:
from the recovery menu, go to mounts and storage and make sure you format the following partitions:
> system
> data
> cache
> sd-ext (if you have a parted sdcard, this is the ext4 partition for your link2sd. do NOT format the sdcard because that where your files are)
go back to the main cwm screen afterwards then do the "Wipe Dalvik Cache" option.
try installing the new ROM you are trying to install.
NOTE: Please read This. If you need information on the CWM menu options. It will help a lot i tell ya.
Click to expand...
Click to collapse
Hey! :laugh: it's working now. I installed the CM11 d2lte and it installed with no break. Thing now is that, like in was 3 days ago, i'm still interested in installing the Likewise S5 v4.1 ROM, how do i go about that considering my current configuration?

oh i'd like to help you on that but the best i can do is advice you of making sure you follow the correct SOPs of installing roms and bootloaders. make sure you are following the steps given by the rom dev or the uploader, if it still does not work, maybe there's some issue with the signature of the rom or something wrong with your config. usually the best way is to flash the boot.img (if provided) from the rom dev's rom and use their recovery mode method and version (e.g. cwm/twrp) to flash their rom. reason i can't really help is that i haven't got my hands on an S5 yet because i can't afford it. if i could or had my hands on one and have the freedom to tinker around with it, i may be able to help you (in the future that is, if i get my hands on one to experiment) as i cook roms and code myself.