Related
Last night, I decided to try out the Trinity kernel. I downloaded and flashed, and everything went without error. After that, I pushed a custom boot animation over ADB. The first one didn't work, and after the splash screen disappeared it was simply a black screen, but then I pushed one I downloaded from XDA and it was fine.
Now, though, I want to make a nandroid, but CWM is running into some issues. I started the ROM manager app, entered a name for the nandroid as usual, and hit OK, but when it rebooted into nandroid, it gave me an error saying "Error mounting /system" and rebooted back into CM7. That's odd, I thought, I never had any problems like that before. So I rebooted into CWM myself by holding down power+vol down and tried making a nandroid there. No luck. Then I went to mounts and storage and tried to manually mount /system. CWM gave me the error again.
I'm not really sure what's causing this. I thought it might be because now I'm using an ext4 filesystem because of Trinity (right? haha I'm new to kernels and such) and CWM might not support reading it, but if that's the case, I think I would not be the first to have this issue. Yet I searched, on that thread, on Google, on XDA general search, and didn't see anything. I also doubt it's the boot animation.
My last nandroid was yesterday. The only changes to the system I remember right now is that I flashed CM7 nightly 101, then flashed Trinity, rebooted, and flashed the boot animation mentioned. I installed apps since then but none of them had root so I doubt that's it. I would reflash CM7 to overwrite Trinity, but I read on the Trinity thread that if I did that without restoring an old CM7 kernel nandroid first, I'd be stuck in a bootloop because of ext4...?
So, what should I do? I don't want to make anything worse than it already is by tinkering with this myself, I no longer have a current nandroid, that's why I'm asking XDA. Does anyone have an idea why this might be happening? I'm sorry if a thread like this already exists or if this is in the wrong forum (if so mods please move it), this is my first time posting and my search skills could suck (although I looked in all the places I could think of)
Thanks for your help! My G2x is running CM7 nightly 101. Both the nvflashed CWM in recovery and the CWM started by the rom manager app are version 3.0.2.7.
I got the same problem as you bro right after flashing trinity
Sent from my LG-P999 using XDA App
ritthyhang said:
I got the same problem as you bro right after flashing trinity
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Good, so I'm not the only one! I thought that was too odd to be true.
Here's what I've done. I reflashed cm7 nightly 101 to get my CM kernel back and rebooted. Sure enough, bootloop. Or it never got past the splash screen to the CM7 android skateboard boot animation. I went back in recovery, though, and was able to mount /system. Odd. So I flashed trinity again and tried mounting /system again and no go. So this definitely has something to do with Trinity... I restored my nandroid, reflashed 101,and that's where I am now. Tomorrow, I will make an up-to-date nandroid and do some tinkering to try to figure out what's going on. Maybe it has something to do with the boot animation, maybe not, exactly what's going on is what I am going to try to figure out if no dev shows up here.
Could you give me a few details about your case? Were you coming from cm7 too? Did you do any boot animation tinkering like me?
Sent from my LG-P999 using XDA App
Okay so I was eaglesblood 1.6 and flashed trinity the other day. Before trinity I was on miui and made plenty of nandroid backup. So today and 1.7 got released so before update I try to backup then behold Our Problem. So after I confirm that I can flash 1.7 over 1.6 I decided to take that risk and flashed anyways. On 1.7 the Superuser was updated I notice, so I decided to make a backup and it Work. So I think the problem was had to do with the outdated Superuser. I think I might be wrong that's just my experience.
Sent from my LG-P999 using XDA App
ritthyhang said:
Okay so I was eaglesblood 1.6 and flashed trinity the other day. Before trinity I was on miui and made plenty of nandroid backup. So today and 1.7 got released so before update I try to backup then behold Our Problem. So after I confirm that I can flash 1.7 over 1.6 I decided to take that risk and flashed anyways. On 1.7 the Superuser was updated I notice, so I decided to make a backup and it Work. So I think the problem was had to do with the outdated Superuser. I think I might be wrong that's just my experience.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Hmm. So to clarify: You were running MIUI, then you flashed eb followed by trinity. Then, eb 1.7 was released and you went to nandroid, but you couldn't mount /system, so you took the risk and upgraded anyways. The new be came with a new version of superuser, and you were able to make nandroids once again. Is this correct?
One very important question if it is. Did you flash trinity again after flashing the eb 1.7 update?
Also, could I ask what version of superuser came in this update? I am using version 2.3.6.3, which is the latest according to Superuser check for updates, but ROM Manager lists a 3.0 beta version and I'm wondering if you're using that. To check, open Superuser, go to the settings tab, and scroll all the way down. It's the second to last option for me. It's unlikely that superuser is making the difference, since it works as a part of Android and our problem is in recovery, before Android loads, but I can see how it might be possible. If you're using the 3.0 beta, I will flash to that and see if it fixes.
I will look into this some more tomorrow, specifically right now I want to know what filesystem eb's kernel recommends.
Sent from my LG-P999 using XDA App
G2X here same problem.
I think they key here is MIUI. I tried to load MIUI image and it didnt go well. I formatted and CWR to restore and its been giving me issues same cant mount system errors.
Right now I downloaded CM7 and installed it from scratch and I can use the phone but it wont backup my ROMs anymore.
Have you guys found anything new ?
lithivm said:
I think they key here is MIUI. I tried to load MIUI image and it didnt go well. I formatted and CWR to restore and its been giving me issues same cant mount system errors.
Right now I downloaded CM7 and installed it from scratch and I can use the phone but it wont backup my ROMs anymore.
Have you guys found anything new ?
Click to expand...
Click to collapse
Update cwm to latest recovery 5.0.2.0 i believe.
fcisco13 said:
Update cwm to latest recovery 5.0.2.0 i believe.
Click to expand...
Click to collapse
+1 cwmr 5.0.2 is the first to officially support ext4 partitions
Sent from my LG-P999 using xda premium
lithivm said:
I think they key here is MIUI. I tried to load MIUI image and it didnt go well. I formatted and CWR to restore and its been giving me issues same cant mount system errors.
Right now I downloaded CM7 and installed it from scratch and I can use the phone but it wont backup my ROMs anymore.
Have you guys found anything new ?
Click to expand...
Click to collapse
I just stopped using Trinity and went back to the stock CM kernel. I don't think it's just miui, I never used that. But...
fcisco13 said:
Update cwm to latest recovery 5.0.2.0 i believe.
Click to expand...
Click to collapse
squish099 said:
+1 cwmr 5.0.2 is the first to officially support ext4 partitions
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
YESS! Looks good. I did hear about that. Looks like it's time to give Trinity another try
Error mount/system!
I can't restore my stock rom,i've tried to fully wipe but got:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
and cant restore
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error mounting /system!
Skipping format
Can't mount /system!
and cm7 doesnt boot,now im just stuck in ClockworkMod Recovery v4.0.0.5
is there any ways to flash stock rom in clockworkmod??
asn_86 said:
I can't restore my stock rom,i've tried to fully wipe but got:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
and cant restore
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error mounting /system!
Skipping format
Can't mount /system!
and cm7 doesnt boot,now im just stuck in ClockworkMod Recovery v4.0.0.5
is there any ways to flash stock rom in clockworkmod??
Click to expand...
Click to collapse
Update your recovery, both, fake and nvflash.
i was also having the can't load system issue. upgrading to latest clockwork mod via rom manager to v5.0.2.0 resolved the issue and i was able to take a backup of my current system.
jblah said:
i was also having the can't load system issue. upgrading to latest clockwork mod via rom manager to v5.0.2.0 resolved the issue and i was able to take a backup of my current system.
Click to expand...
Click to collapse
Where do I find the latest clockwork mod and how do I install it? I currently have a soft bricked phone, and I can't seem to get it unbricked. I tried using the pit files with the stock rom, the dbdata stuff and everything else. What happened was the the system was in ICS, but something happened and I couldn't load into CWM 4 and the system wouldn't boot. So to fix, I used odin to install the stock rom (v2.3.3), but the stock rom came with CWM 3.0, so now I'm at 3.0 and can't mount the file system and it's not booting. I'm assuming that if I upgraded the CWM back to a newer version, I'll be able to restore the system and gain access to the file system again.
reboot problem
i jus flashed ext4 converter for kernel update every think went fine but i couldnt mount system coz it was showing error i neglected dat nd flashed every thing was done nd when i rebooted it gt stuck in d samsung galaxy y logo...plzzz help meee wat to do..plzzz help
Abizer98 said:
i jus flashed ext4 converter for kernel update every think went fine but i couldnt mount system coz it was showing error i neglected dat nd flashed every thing was done nd when i rebooted it gt stuck in d samsung galaxy y logo...plzzz help meee wat to do..plzzz help
Click to expand...
Click to collapse
I'd ask in the samung galaxy forums bud.
"my mind draws lots of blanks actually"
Solution
asn_86 said:
I can't restore my stock rom,i've tried to fully wipe but got:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
and cant restore
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error mounting /system!
Skipping format
Can't mount /system!
and cm7 doesnt boot,now im just stuck in ClockworkMod Recovery v4.0.0.5
is there any ways to flash stock rom in clockworkmod??
Click to expand...
Click to collapse
actually yes. the /system folder is corrupt and it need to be formatted. so all you need to do is format / system then it will work as it should
hope that helps
Ok
I know i'm sorry if this has been posted quite a lot but i can't find a proper answer. I installed the leaked sense 3.0 rom and everything went fine. But suddenly the phone switched off and everytime i boot i get stuck on the white htc screen. i can get into recovery but when i do i get
E: can't find cache.... (will have to check error later properly)
Anyway i've tried factory reset, installing a new rom, installing recovery again and also running the RUU software. The RUU software was my last option and i'm getting stuck at rebooting to bootloader. Is this a faulty eMMC chip or do i still have other options. My device is S-OFF and rooted, so is there anyway to change it back for warranty purposes?
Any help will be appreciated a lot!!!!!
dan-fish said:
i can get into recovery but when i do i get
E: can't find cache.... (will have to check error later properly)
Click to expand...
Click to collapse
I'm afraid that it does sound very like the symptoms of the fried eMMC chip problem. Did you at any point pull the battery?
If you attempt to go into RECOVERY and try to format the CACHE partition what errors do you get?
Do you have any Full Nandroid backups on your SD card that you can attempt to restore?
i have taken the battery out many times to get into recovery when i have boot loops and what not. Also have done it a lot now to get into recovery
i didn't have a backup so i copied one over from my brothers desire s which i had hoped would still work. I'm not sure if it was because it was from my brother's phone or it was because everything refuses to work, but the restore didn't work.
also clockworkmod is just really slow.
when i wipe the cache it says
-- Wiping cache
Formatting /cache...
Cache wipe complete
Then shows the original error again which is
E:Can't mount /cache/recovery/log
E:can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
So the cache wiping is a success but does that help in any way. Is the eMMC chip still most likely fried?
I tried installing cm7 and it gave me the error
E:Error in /sdcard/update-cm-7.1.0-RC1-DesireS-Nexx-signed.zip
(Status 1)
Installation aborted
I know for a fact the rom is fine because my brother has the rom on his desire s.
dan-fish said:
i have taken the battery out many times to get into recovery when i have boot loops and what not. Also have done it a lot now to get into recovery
i didn't have a backup so i copied one over from my brothers desire s which i had hoped would still work. I'm not sure if it was because it was from my brother's phone or it was because everything refuses to work, but the restore didn't work.
also clockworkmod is just really slow.
when i wipe the cache it says
-- Wiping cache
Formatting /cache...
Cache wipe complete
Then shows the original error again which is
E:Can't mount /cache/recovery/log
E:can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
So the cache wiping is a success but does that help in any way. Is the eMMC chip still most likely fried?
I tried installing cm7 and it gave me the error
E:Error in /sdcard/update-cm-7.1.0-RC1-DesireS-Nexx-signed.zip
(Status 1)
Installation aborted
I know for a fact the rom is fine because my brother has the rom on his desire s.
Click to expand...
Click to collapse
I'm afraid that it does seem to be yet another fried eMMC chip...see this thread that I only answered yesterday that exhibits exactly the same problem and has a couple of linked threads in it. Although I'm by no means an expert, so dig around through the various related threads on this subject to confirm this for yourself. I have seen a thread a while back within this forum, although can't find it now that shows commands and then the results returned from a bricked (fried eMMC chip) device and a non bricked device that will enable you to confirm 100%.
Although, it does look like service centre will be your next stop, if you're lucky they may fail to notice the S-OFF state of the device.
so there is absolutely no way to go back to s-on? Is there at least a way to make sure they don't realise it's S-OFF?
dan-fish said:
so there is absolutely no way to go back to s-on? Is there at least a way to make sure they don't realise it's S-OFF?
Click to expand...
Click to collapse
I would also like to know this information incase it ever happened to me
daveys4 said:
I would also like to know this information incase it ever happened to me
Click to expand...
Click to collapse
Right now i would prefer it if my phone were actually bricked!
Can i just send them the phone without the battery or sd card?
Also how does fastboot work?
I want to try something like this http://forum.xda-developers.com/showthread.php?t=1231249
But when i type in fastboot oem lock in cmd nothing happens
dan-fish said:
so there is absolutely no way to go back to s-on? Is there at least a way to make sure they don't realise it's S-OFF?
Click to expand...
Click to collapse
I'll be honest I don't know.
Does adb recognise your device still? So question is does adb or fast boot function?
Now the post that I mentioned earlier may be of some use at this point.
I'm about to PM you something.
Swyped from HTC Desire S using XDA Premium
dan-fish said:
Right now i would prefer it if my phone were actually bricked!
Can i just send them the phone without the battery or sd card?
Also how does fastboot work?
I want to try something like this http://forum.xda-developers.com/showthread.php?t=1231249
But when i type in fastboot oem lock in cmd nothing happens
Click to expand...
Click to collapse
You need the adb and fast boot exe on your PC which you can get online, afraid that I'm away from a PC now so will have to add more tomorrow
I've send you a pm (a last resort)
Swyped from HTC Desire S using XDA Premium
i most likely will not have time today but tomorrow i'll try and get the hang of adb and fastboot. Explore my options with it. If nothing happens i'll just have to call htc.
I was thinking if i can't do anything else, i should just drain the battery by swapping the battery with my brother's desire s, drain the battery and then swap them back. Maybe that'll help?
dan-fish said:
i most likely will not have time today but tomorrow i'll try and get the hang of adb and fastboot. Explore my options with it. If nothing happens i'll just have to call htc.
I was thinking if i can't do anything else, i should just drain the battery by swapping the battery with my brother's desire s, drain the battery and then swap them back. Maybe that'll help?
Click to expand...
Click to collapse
You'll see in my Signature the links to get both ADB and FASTBOOT, you'll also need HTC drivers installed.
This is the usefull THREAD that I was talking about.....in determining whether you are indeed suffering from fried eMMC chip, even though at this stage we're reasonably confident.
ben_pyett said:
I'm afraid that it does seem to be yet another fried eMMC chip...see this thread that I only answered yesterday that exhibits exactly the same problem and has a couple of linked threads in it. Although I'm by no means an expert, so dig around through the various related threads on this subject to confirm this for yourself. I have seen a thread a while back within this forum, although can't find it now that shows commands and then the results returned from a bricked (fried eMMC chip) device and a non bricked device that will enable you to confirm 100%.
Although, it does look like service centre will be your next stop, if you're lucky they may fail to notice the S-OFF state of the device.
Click to expand...
Click to collapse
That is not a fried chip! If he can get into recovery and wipe cache it definately isn't a fried chip, i had this 2 days ago. I sorted it somehow..... been drinking tonight so don't expect an answer until late tomorrow
Malooga said:
That is not a fried chip! If he can get into recovery and wipe cache it definately isn't a fried chip, i had this 2 days ago. I sorted it somehow..... been drinking tonight so don't expect an answer until late tomorrow
Click to expand...
Click to collapse
@Malooga
It would obviously be quality if it's not and the device is recoverable from this position. Any clues how you sorted this out, using what approach?
@dan-fish
Do you have EXT4 recovery installed?
If you do great. If not then 1) download this FILE 2) copy it onto your SD card 3) enter recovery 4) flash the EXT4 ZIP file 5) then Reboot Recovery.
Using EXT4 recovery, look at what format the existing CACHE partition and the other partitions are in? this can be done using the EXT3 - 4EXT - 4EXT option of the EXt4 recovery main screen.
I'd also try to download a custom ROM WIPE script and then run this from recovery (reporting back any errors).
Then try to flash a custom ROM also again also from recovery having downloaded it to your SD card like LBC using the flash ZIP from SD card option in recovery.
Will try later today. Please do try and help malooga
Sent from my HTC Desire S using XDA Premium App
dan-fish said:
Will try later today. Please do try and help malooga
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
Although Malooga might be suffering today from the morning after (we've all been there)
I'll be online most of the day, as I'm currently off work sick...as I've somehow knackered my back - so XDA is keeping me sane
installing 4ext recovery
assert failed: write_raw_image (" /tmp/recovery.img" , "recovery"
E:Error in /sdcard/4EXTRecovery_v2.1.3RC2.zip
(Status 7)
Installation aborted.
Ran full wipe script:
E:Error in /sdcard/FULL_WIPE_1.5_EXT4-for-saga_.zip
(Status 1)
Installation aborted
Seriously running out of options.
I had this happen I just wiped data factory reset wipe cache wipe dalvik then go into mounts and format data format cache format system then flashed my backup the phone then booted up if u don't have a backup download a rom zip and flash that if you have tried the above then I'm all out of ideas good look
Sent from my HTC Desire S using xda premium
As you don't have any Backups.....we should attempt to move forward.
As we know that you can format/wipe partitions (eg CACHE appeared to work) you should try to manually format/wipe DATA, SYSTEM and CACHE.
Download a custom ROM to your SD card ie LBC like LBC v0.5.3
Then try to flash this Custom ROM from RECOVERY using the flash ZIP from SD card option.
Report back any errors and progress.
ok will try now and update in 10-15 mins.
also i haven't explored my options with fastboot mainly because i don't really understand it yet but if there are any options available through there (excluding the last resort which right now is looking like our only option) i will be happy to try
dan-fish said:
ok will try now and update in 10-15 mins.
also i haven't explored my options with fastboot mainly because i don't really understand it yet but if there are any options available through there (excluding the last resort which right now is looking like our only option) i will be happy to try
Click to expand...
Click to collapse
I'm by no means an expert either and fastboot is something that I've yet to master..so before you try that EVIL one.....lets try some other stuff and look for advice from others.......
I'm online tonight for next couple of hours, we'll until the England Football game kick offs anyway!
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
[Deleted]
johnfocker said:
Hey guys!
I've been trying to factory reset my tf700t to install a fresh CM10.1 but I had the (very) bad idea to try this ****ty encryption feature before and now everytime I try to factory reset or wipe /data, the recovery throws me an error like "Unable to mount /data".
Tried with TWRP as well as Clockworkmod, same result.
I don't want to mount it, it just want to get rid of it and start fresh.
Is there a way to do it?
Is there an official tool to flash a stock rom or am I stuck with those recoveries that can't work with encrypted partitions?
Cheers
Click to expand...
Click to collapse
As I recall there is a superwipe script somewhere the will completely remove and recreate the partitions. Don't recall where I found it though, but it will fix that.
johnfocker said:
I don't want to mount it, it just want to get rid of it and start fresh.
Is there a way to do it?
Click to expand...
Click to collapse
"Format /data" in TWRP should do it.
johnfocker said:
Hey guys!
I've been trying to factory reset my tf700t to install a fresh CM10.1 but I had the (very) bad idea to try this ****ty encryption feature before and now everytime I try to factory reset or wipe /data, the recovery throws me an error like "Unable to mount /data".
Tried with TWRP as well as Clockworkmod, same result.
Cheers
Click to expand...
Click to collapse
Did you try the Format Option in the TWRP? It wipes everything on your internal SD. I use it every time that I want a clean install.
Flash the TWRP recovery through fastboot mode and then u 'll be fine to wipe data/factory reset.
Sent from my ASUS Transformer Pad TF700T using xda premium
[Deleted]
johnfocker said:
I only just noticed I never replied to you guys...
So first of all, thank you for taking the time to answer me back then, if you ever read this
From what I can recall, I ended up doing a full format through CWM or TWRP. This takes a long time (because the nand is so slow I gues) and the first time I tried I thought the tablet was frozen, that's probably why I thought I was screwed...
So after I let the full format finish, I was able to sideload a fresh rom and it worked again
BTW just installed crombikk rom : AWESOME
I only wish I tried it earlier!
The encryption feature seems to be broken but... Who cares, my tablet as never been so fast (usable? Lol)
Click to expand...
Click to collapse
You got your first thanks
I like good news stories!!
Hey there!
I'm hoping that someone can help me out. My nephew who's a wanna-be geek was going to update my ROM (which didn't to be done really, but he wanted to show me what he was able to do). He went and downloaded the latest CM 11, rebooted and went into TWRP 2.7.0.1, did a factory reset, an advanced wipe, and did the Format Data. When he did that, it got stuck in a loop. Nothing happened. He tried to install the ROM he downloaded, and NOTHING! Long story short, by him doing the Format Data, he wiped out my partitions. TWRP, no matter what I try to do tells me it's unable to mount 'data' or 'media' etc. etc. Which is leading me to believe I have no partitions left. I've tried installing the latest update from Asus, and no dice. I've tried restoring backups that I have on my micro SD, and that's not working.
Can someone please help me and tell me how to fix this? Can I get my partitions back? I'm really hoping that I don't have to send this tablet off to Asus in Dallas, TX to have it repaired.
I'm using a loaner tablet from a rental store, hoping I can get my TF 300 fixed.
Any help is deeply and sincerely appreciated.
Omega
Sent from my SM-P600 using Tapatalk
I was about to suggest you look in the correct forum, but I see you posted there as well. Anyway, your partitions are probably okay, they have just been wiped out, that doesn't mean you lost them. Have you tried reflashing the recovery? Were you able to flash anything with said recovery before that? Wiping the partitions in the recovery shouldn't have any effect on the flashing functionality, no matter which partitions were selected (except for sdcard, since that's where the ZIPs are stored), so there might be a problem with the recovery itself. Are you sure you have the correct one for your device?
Duchman said:
I was about to suggest you look in the correct forum, but I see you posted there as well. Anyway, your partitions are probably okay, they have just been wiped out, that doesn't mean you lost them. Have you tried reflashing the recovery? Were you able to flash anything with said recovery before that? Wiping the partitions in the recovery shouldn't have any effect on the flashing functionality, no matter which partitions were selected (except for sdcard, since that's where the ZIPs are stored), so there might be a problem with the recovery itself. Are you sure you have the correct one for your device?
Click to expand...
Click to collapse
Hey there Duchman ...
Thanks for your reply. I have tried reflashing the recovery like you suggested. And after that tried to reinstall CM11.Afterwards reflashing the recovery it says “Unable to mount data." I don't know if I need to flash a more recent version of TWRP, if that would even help.
Before all of this happened I could flash almost any ROM of my choice as long as it was KitKat supported. All of my backups and restores are kept on my micro SD so they aren't accidentally deleted. As far as I know it's the correct version of TWRP. It's worked for me so far, ever since I updated to KitKat.
Sent from my SM-P600 using Tapatalk
Omega Recon said:
Hey there Duchman ...
Thanks for your reply. I have tried reflashing the recovery like you suggested. And after that tried to reinstall CM11.Afterwards reflashing the recovery it says “Unable to mount data." I don't know if I need to flash a more recent version of TWRP, if that would even help.
Before all of this happened I could flash almost any ROM of my choice as long as it was KitKat supported. All of my backups and restores are kept on my micro SD so they aren't accidentally deleted. As far as I know it's the correct version of TWRP. It's worked for me so far, ever since I updated to KitKat.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
You could try flashing a newer recovery first, I think 2.7.1.0 is available for your device. Also try doing a hard reset by cold booting - here's a how-to: https://www.youtube.com/watch?v=oTU38Ewh8qo (wipe the cache afterwards)
If that doesn't help, reverting to stock is probably your best option. Try this: http://forum.xda-developers.com/showthread.php?t=1757077 (be sure to grab the correct firmware and back up your files)
Have you tried installing any other custom ROM? Does it give you the same error when you try to restore your backup?
Here's what I've come across so far. I did the reset, and that did nothing.
Tried to flash the stock version, after a few seconds, TWRP popped up with FAILED.
I've tried flashing Omni ROM. It will flash, load up, and gets stuck at the boot screen or boot animation. This happens with just about every ROM I try to flash.
Been looking for TWRP 2.7.1.0. I'm not seeing it listed on TWRPs site. Where can I get a copy? Thanks!
Sent from my SM-P600 using Tapatalk
Here you go: http://forum.xda-developers.com/showthread.php?t=2772093
Also do try flashing another recovery, PhilZ for instance: http://forum.xda-developers.com/showthread.php?t=2597860
Did you try wiping all of the partitions again?