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
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
Hi Folks.
Ok here is my situation, I have a rooted and unlocked TF700.
I flashed Zeus 4 and all worked well, then flashed (after full wipe) PARANOIDANDROID 2.15 and again everything was great,
Yesterday I flashed Baked Bean 4 (again after a full wipe) and apart from some SD issues all seemed ok,
I then decided to restore my TWRP backup of Zeus as I needed to use my 64gig msd card.
After a full wipe and restore Zeus started up but the dpi was messed up (160) I think (way small)
I was seeing loads of FC's and file manager showed my internal SD as being empty. Rebooted to recovery and tried the "Format Data" option
It failed right away with this message "E: Unable to format data."
I have tried flashing the stock .26 rom via TWRP and I have the same issue, dpi set to 160 and internal sd not mounted.
It seems my Internal sd is corrupt
What is the procedure to reformat it via ADB or fastboot? (I have searched but the results I found relate to other devices and I dont want to simply follow instructions that might cause further harm to my TF700)
I have followed the NVflash brick proof procedure and have all relevant files backed up (I did this before flashing the last 2 roms)
Please can some one point me in the right direction
Thanks a lot
Jules
I always wipe cache, system, internal, davic and then do a factory reset.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right? What rom you have on your device right now?
Pretoriano80 said:
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right. What rom you have on your device right now?
Click to expand...
Click to collapse
Yip extracted the zip from the zip file and copied it to my ext sd and flashed it via TWRP
I have an unusable Zeus4,
Im about to try a full wipe again and then flash .26 again
EDIT
After flashing .26 and selecting reboot I get the "No OS installed! Are you sure you wish to reboot?" message
Looks like the system partition is corrupted, but i'm not sure. I think you should come here on IRC and maybe someone with more experience will help you - - http://webchat.freenode.net/?channels=asus-transformer
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
ZaJules said:
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
Click to expand...
Click to collapse
This same thing happened to me with my Prime when I was getting ready to send it off for RMA because of a broken HDMI port. Since I was unlocked I was advised to restore to stock before sending it in. However, before I got the chance to do that I started getting the "E: Unable to format data." error that you were. I ended up erasing all partitions from fastboot and putting a note in the box that it wouldn't boot after an OTA. I managed to get away with it and wasn't charged for fixing it
For future reference it would be really helpful to know how you fixed this. Did you do something like what is in this thread: http://forum.xda-developers.com/showthread.php?t=1803343.
Did you ever figure out how CM10 messed up your Infinity? I was running CM9 on my Prime when I got this error. Thanks!
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Pretoriano80 said:
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Click to expand...
Click to collapse
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
paddycr said:
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
Click to expand...
Click to collapse
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Pretoriano80 said:
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Click to expand...
Click to collapse
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
okantomi said:
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
Click to expand...
Click to collapse
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Pretoriano80 said:
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Click to expand...
Click to collapse
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
okantomi said:
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
Click to expand...
Click to collapse
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Pretoriano80 said:
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Click to expand...
Click to collapse
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
okantomi said:
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
Click to expand...
Click to collapse
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Pretoriano80 said:
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Click to expand...
Click to collapse
I'm using TWRP 2.2.2.1, I back up boot, system and data only, and I don't use compression.
HI, i have been having isues with my asus tf101 baterry, about one month ago it suddenly charge and discharges, like: 10%-25%-40%-70%-80%-100%...I made a factory reset but nothing. 2 weeks ago, it solved alone, without do anything, and was ok for 2 weeks, now again i have the problem..
i have installed cwm recovery, i want to change to android revolution rom, to see if the problem finish:
1 question: How i change from cwm to twrp recovery? installing twrp from cwm using a zip? is there no problem?? or downloading goomanager, installing recovery script?? Is there any problem to use cwm or twrp( i have read, to instal kk i dont use cwm)?
2 question, what rom is stable to try to solve this? i see kk 4.3 etc, but i just one my baterry works ok...
3 question, is there any way to clean absolutely the stock rom? i tried wipe cache, dalvik, factory reset(again) but nothing solve.
4 question, is possible to wipe ALL including system, and install the asus stock rom using zip¿?
Thanks for your atention, please be the most specifically possible because i am new on this, and i just one my tablet for study(read books).
I have a asus tf101 b70 root, with CWM recovery is a old version 5.0.26 something..
cesar_cjx said:
HI, i have been having isues with my asus tf101 baterry, about one month ago it suddenly charge and discharges, like: 10%-25%-40%-70%-80%-100%...I made a factory reset but nothing. 2 weeks ago, it solved alone, without do anything, and was ok for 2 weeks, now again i have the problem..
i have installed cwm recovery, i want to change to android revolution rom, to see if the problem finish:
1 question: How i change from cwm to twrp recovery? installing twrp from cwm using a zip? is there no problem?? or downloading goomanager, installing recovery script?? Is there any problem to use cwm or twrp( i have read, to instal kk i dont use cwm)?
2 question, what rom is stable to try to solve this? i see kk 4.3 etc, but i just one my baterry works ok...
3 question, is there any way to clean absolutely the stock rom? i tried wipe cache, dalvik, factory reset(again) but nothing solve.
4 question, is possible to wipe ALL including system, and install the asus stock rom using zip¿?
Thanks for your atention, please be the most specifically possible because i am new on this, and i just one my tablet for study(read books).
I have a asus tf101 b70 root, with CWM recovery is a old version 5.0.26 something..
Click to expand...
Click to collapse
Q1: I think you can just flash the new recovery via the current recovery if you have the new recover zip file.
Q2: Kat Kiss works fine for me.
Q3: If you want to completely return to stock, you would have to use NVFlash. There are tons of instructions on the Dev thread. I primarily use Tubuntu for flashing with NVFlash. [http://forum.xda-developers.com/showthread.php?t=1995157]
You can find other images as well. I used a stock image once to RMA the tablet but now I'm not sure where I got it. This method will ensure that every bit in your memory is exactly as it left the factory. Including the bootloader, recovery partition and everything else.
Q4: Refer Q3.
Download flashable TWRP 2.6.3.11 zip for TF101:
http://forum.xda-developers.com/devd...ct/dl/?id=3280
You should use TWRP for KatKiss ROMs, do not use CWM
Flash that Zip from CWM then reboot fully into your current ROM, then reboot into Recovery to check it has flashed properly
From TWRP you can wipe everything and flash KatKiss & Gapps
*Detection* said:
Download flashable TWRP 2.6.3.11 zip for TF101:
http://forum.xda-developers.com/devd...ct/dl/?id=3280
You should use TWRP for KatKiss ROMs, do not use CWM
Flash that Zip from CWM then reboot fully into your current ROM, then reboot into Recovery to check it has flashed properly
From TWRP you can wipe everything and flash KatKiss & Gapps
Click to expand...
Click to collapse
Is this the same process for going from TWRP to TWRP? just "install" the newest version from recovery and do the reboots?
stache12 said:
Is this the same process for going from TWRP to TWRP? just "install" the newest version from recovery and do the reboots?
Click to expand...
Click to collapse
Yep, so long as you reboot into your ROM after flashing the new TWRP before booting back into recovery
Thanks for your reply, i will tray soon. So i want to clean the asus stock room to see if battery goes ok, i tried wipe data, cache, dalvik, with cwm, but nothing.
If i install twrp what more options can i try before change the rom? what more wipe do i need?? and finally, if i change the rom, is possible to go back to asus stock just flashing from recovery? or how should i do?
Apart from wiping the ROM (SYSTEM) there's not much else you can wipe, you could try wiping the same as you have already done, but from TWRP, see if that makes any difference, maybe the battery is coming to the end of its life
You can flash stock ASUS ROMs back again from TWRP yes, but you will wipe your recovery & ROM back to 100% stock by doing it
Best thing to do is to make a full Nandroid Backup from TWRP before flashing any custom ROMs, save it to MicroSD Card, then if you want to go back to the way it is now, just restore the backup from TWRP
That way you keep TWRP and can switch between as many ROMs as you like and always have your stock backup to go back to whenever you want
46999589
*Detection* said:
Apart from wiping the ROM (SYSTEM) there's not much else you can wipe, you could try wiping the same as you have already done, but from TWRP, see if that makes any difference, maybe the battery is coming to the end of its life
You can flash stock ASUS ROMs back again from TWRP yes, but you will wipe your recovery & ROM back to 100% stock by doing it
Best thing to do is to make a full Nandroid Backup from TWRP before flashing any custom ROMs, save it to MicroSD Card, then if you want to go back to the way it is now, just restore the backup from TWRP
That way you keep TWRP and can switch between as many ROMs as you like and always have your stock backup to go back to whenever you want
Click to expand...
Click to collapse
Thanks!! I will try, but apart from wipe system(rom) what more wipes can i try without erase the rom?..I think not, because a week ago the battery was perfect working...i hope so.
CACHE,
DALVIK CACHE,
FACTORY RESET,
INTERNAL STORAGE,
FORMAT DATA
Only other 2 options are SYSTEM & EXTERNAL STORAGE
Hello!
I bought a Moto G falcon 2 mounts ago. Running CM12 everything was good.
I flashed a cm12.1, then my falcon started to crash randomly (mostly because i didn't flash the proper Gapps). So I wanted to revert back to KitKat to make a proper flash since the beginning, wich was ofc a bad idea. So I flashed the 4.4.4 stock ROM and now am in soft brick. I'm stuck at boot logo (The boot loader unlocked one). I tried to flash a stock 5.1 ROM (GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip) without any success.
My bootloader is updated to 4118, I can boot in recovery/bootloader.
Any ideas how to boot again? Thank you!
I_HAVE_NO_IDEA said:
Hello!
I bought a Moto G falcon 2 mounts ago. Running CM12 everything was good.
I flashed a cm12.1, then my falcon started to crash randomly (mostly because i didn't flash the proper Gapps). So I wanted to revert back to KitKat to make a proper flash since the beginning, wich was ofc a bad idea. So I flashed the 4.4.4 stock ROM and now am in soft brick. I'm stuck at boot logo (The boot loader unlocked one). I tried to flash a stock 5.1 ROM (GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip) without any success.
My bootloader is updated to 4118, I can boot in recovery/bootloader.
Any ideas how to boot again? Thank you!
Click to expand...
Click to collapse
Well if you can boot into the recovery and if its custom (TWRP) wipe all the data on your phone. Second I would try to flash a ROM onto your device such as Resurrection Remix and see if that works. Update on your progress.
Thank you for your answer.
I tried to wipe data/factory reset, but twrp throws some error messages.
Unable to mount /data, /cache, /system and all derivatives.
I tried to flash a ROM through twrp but I think I can't because of that partition mess. I can't adb push to /sdcard, or sideload (seems to require /data).
I think that my issue is that I flashed the 4.4.4 gpt.bin, and I shouldn't have. If I'm right, is there any way to recover from this?
I_HAVE_NO_IDEA said:
Thank you for your answer.
I tried to wipe data/factory reset, but twrp throws some error messages.
Unable to mount /data, /cache, /system and all derivatives.
I tried to flash a ROM through twrp but I think I can't because of that partition mess. I can't adb push to /sdcard, or sideload (seems to require /data).
I think that my issue is that I flashed the 4.4.4 gpt.bin, and I shouldn't have. If I'm right, is there any way to recover from this?
Click to expand...
Click to collapse
I crashed my S3 using camera on old cm12.1 and got into loop with services stopped. Try and D/L the new 4 22 and Slim ggaps 20150422 wipe chache and devik and reinstall cm and ggaps get it working this is what I did but I haven't read any info except to find a file for Odin but don't think you can use Odin. It be nice to have stable way to downgrade. The flash will hopefully get your phone working.
vtails said:
I crashed my S3 using camera on old cm12.1 and got into loop with services stopped. Try and D/L the new 4 22 and Slim ggaps 20150422 wipe chache and devik and reinstall cm and ggaps get it working this is what I did but I haven't read any info except to find a file for Odin but don't think you can use Odin. It be nice to have stable way to downgrade. The flash will hopefully get your phone working.
Click to expand...
Click to collapse
Thank you. But I can't flash a cm12.1 atm (see my post below). I can only flash through fastboot. I'm not sure I properly understood you, what do you call 4 22 ?
FYI I managed to boot again. Here's what I did:
Flash a 5.x ROM, try to boot to let the system make partitions and stuff (I think)
Boot in TWRP and saw that system and cache were not mountable, so I wiped them.
Flash a cm12.1 (+ Gapps) and here we go!
Thank you for your help!