Related
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.
Let me start out by saying your help is very much appreciated. I was on stock rom 4.4.2 and really never bothered with updating. I'm rooted(w/unlocked bootloader) and have made backups in TWRP and restored them without issue in the past.
I wanted to try installing the Chroma ROM, but I think i made a mistake by ticking off all the boxes and deleting everything first. I have 2 full backups on my USB-OTG drive along with the Chroma ROM. At the moment, I can't flash the ROM and I cant restore the backups I have on my USB-OTG drive. I try to restore them and it just goes back to the TWRP homescreen after one second. There's no OS, but I can boot into TWRP version 2.6.3.4. I suppose I shouldn't have wiped system before flashing the ROM? Did this happen because I tried flashing the ROM from my USB-OTG that it didn't flash? Should I have kept it on the root my SD Card?
What's the easiest way to get my backup up and running? Do I have to get a factory image back on the device? I'm so lost with what to do next.
Thank you all for your assistance.
Just fastboot the android system img of your choice
Sent from my Android M Nexus 5 yo!
Please Help
I was in miui ROM then I tried flashing Metallium ROM, after I flashed it, it booted up but, it wasn't restoring my previous apps, so I skip that part, but then when I got to the home screen I wasn't able to access my stuffs in my phone memory.
So I thought maybe I need to change the data to f2fs, so I went to the recovery and did and flashed the Metallic ROM again, but this time it didn't boot at all, there was a bootloop and I could get past the start up screen.
I tried my older ROMs the one that I had, but it's all giving me the same response now, I have switch before but I never have had this problem. Please help, how do I flash other lollipop ROM again.
Maybe changing to f2fs and doing a factory reset. If that doesn't help, flash stock ROM via fastboot.
kennylrmsailo said:
Please Help
I was in miui ROM then I tried flashing Metallium ROM, after I flashed it, it booted up but, it wasn't restoring my previous apps, so I skip that part, but then when I got to the home screen I wasn't able to access my stuffs in my phone memory.
So I thought maybe I need to change the data to f2fs, so I went to the recovery and did and flashed the Metallic ROM again, but this time it didn't boot at all, there was a bootloop and I could get past the start up screen.
I tried my older ROMs the one that I had, but it's all giving me the same response now, I have switch before but I never have had this problem. Please help, how do I flash other lollipop ROM again.
Click to expand...
Click to collapse
Anyone out there? Need help desperately.
Anyone?
samuelcr93 said:
Maybe changing to f2fs and doing a factory reset. If that doesn't help, flash stock ROM via fastboot.
Click to expand...
Click to collapse
Yeah that might work but I'm kinda looking for a solution where I don't have to flash the stock again because I lost all my moto g stuffs some months back.
And another thing is that when I flash MIUI its working fine again and I'm able to access all the file in my phone storage also. Any suggestions?
Mmmm if you are using TWRP you could connect the phone to the PC and make a backup while you are in recover mode. Then format again data partition to f2fs and make a factory reset including internal storage and finally flash your ROM and restore your files.
But if that is not working then the only option is flashing Stock ROM
If MIUI is still booting it means that your data partition is still ext4
I'm using the original shield tablet WiFi and considering flashing cyanogenmod. What I wanted to know before is what exactly does the custom ROM write to when flashing, bootloader, recovery? Thanks for the help guys!
RunicGamer said:
I'm using the original shield tablet WiFi and considering flashing cyanogenmod. What I wanted to know before is what exactly does the custom ROM write to when flashing, bootloader, recovery? Thanks for the help guys!
Click to expand...
Click to collapse
The only partitions it should write to is /system and /boot (kernel) and possibly userdata
Custom ROMs (for nearly all android devices) won't touch firmware such as recovery or bootloader
demkantor said:
The only partitions it should write to is /system and /boot (kernel) and possibly userdata
Custom ROMs (for nearly all android devices) won't touch firmware such as recovery or bootloader
Click to expand...
Click to collapse
Does that mean that I should make a backup of the Boot partition? Also, If I wanted or needed to restore from Cyanogenmod to Stock android 5.1.1 on the Shield Tablet. Would I have to restore the boot partition along with the system and data partitions, or just the System and Data partitions. Lastly, does that mean that Cyanogenmod won't/doesn't touch the bootloader on the Nvidia Shield Tablet? Sorry for asking so many questions. I want to try it but and very worried of accidentally bricking the bootloader, since it is my first and only tablet. Thanks again for the help!!!!
RunicGamer said:
Does that mean that I should make a backup of the Boot partition? Also, If I wanted or needed to restore from Cyanogenmod to Stock android 5.1.1 on the Shield Tablet. Would I have to restore the boot partition along with the system and data partitions, or just the System and Data partitions. Lastly, does that mean that Cyanogenmod won't/doesn't touch the bootloader on the Nvidia Shield Tablet? Sorry for asking so many questions. I want to try it but and very worried of accidentally bricking the bootloader, since it is my first and only tablet. Thanks again for the help!!!!
Click to expand...
Click to collapse
I have rarely seen issues of bricks on these, so you shouldn't have much to worry about
Nvidia is nice enough to give us full stock bootloader flashable images (similar to what google gives with nexus line) which helps in case of issue
Flashing custom ROMs is very similar as with most other android devices
General scenario goes as such
(Assuming bootloader is unlocked and custom recovery installed)
Boot to recovery, do a full nandroid backup
Save this backup to PC
From recovery wipe all
Flash ROM of choice (along with gapps or anything else you need)
Reboot
Now you are running cm, or whatever
In case you want to restore
Boot to recovery,
Wipe clean
Restore the earlier nandroid backup you had made
Reboot
Now all is the same as before you flashed
demkantor said:
The only partitions it should write to is /system and /boot (kernel) and possibly userdata
Custom ROMs (for nearly all android devices) won't touch firmware such as recovery or bootloader
Click to expand...
Click to collapse
demkantor said:
I have rarely seen issues of bricks on these, so you shouldn't have much to worry about
Nvidia is nice enough to give us full stock bootloader flashable images (similar to what google gives with nexus line) which helps in case of issue
Flashing custom ROMs is very similar as with most other android devices
General scenario goes as such
(Assuming bootloader is unlocked and custom recovery installed)
Boot to recovery, do a full nandroid backup
Save this backup to PC
From recovery wipe all
Flash ROM of choice (along with gapps or anything else you need)
Reboot
Now you are running cm, or whatever
In case you want to restore
Boot to recovery,
Wipe clean
Restore the earlier nandroid backup you had made
Reboot
Now all is the same as before you flashed
Click to expand...
Click to collapse
OK now for now one last thing. Should In backup the boot partition from twrp, the when I want to go back to stock android I restore system, data, and boot? Or just leave boot?
RunicGamer said:
OK now for now one last thing. Should In backup the boot partition from twrp, the when I want to go back to stock android I restore system, data, and boot? Or just leave boot?
Click to expand...
Click to collapse
Backup all partitions
When you want to restore
Wipe all, then be sure to restore system, userdata and boot
If you don't restore boot it probably will bootloop as you will be using the wrong kernel
Hi,
I flashed Twrp but I can't backup, because it can't mount data.
I thought, I'd try to revert back to stock recovery and then flash twrp again.
Does anybody know how to do that without flashing an entire stock Rom?
Thanks
nearlygod said:
Hi,
I flashed Twrp but I can't backup, because it can't mount data.
I thought, I'd try to revert back to stock recovery and then flash twrp again.
Does anybody know how to do that without flashing an entire stock Rom?
Thanks
Click to expand...
Click to collapse
Hi
Why you just flash TWRP again and start from begining?
Anyhow if you wish to reflash your stock recovery You need to reflash a stock boot.img
Here you have 2 ways to do it:
http://forum.xda-developers.com/showpost.php?p=66934553&postcount=218
http://forum.xda-developers.com/showpost.php?p=66922116&postcount=215
In those threads the point was to re root but the principle is valid you can use them as guides
nearlygod said:
Hi,
I flashed Twrp but I can't backup, because it can't mount data.
I thought, I'd try to revert back to stock recovery and then flash twrp again.
Does anybody know how to do that without flashing an entire stock Rom?
Thanks
Click to expand...
Click to collapse
I had this problem and found out in my case, at least, it was because when I rooted, I didn't "format data" during the process. I've been told that if you don't format data during the process, you leave the data partition encrypted, and thus it can't be mounted (at least by non-system apps and processes). No guarantees here as always, but If you back everything up and redo the root process and do the data format, then you may be able to mount data. At that point you can restore your apps and info. I've also read (but haven't tried this!) that you can do a nandroid backup and restore ALL your data from that nandroid after you reset your phone (which the data format will do). You should google everything I have suggested and see if you can get what you need in this way, without having to reflash the ROM entirely or try to revert to stock recovery.
kettir said:
I had this problem and found out in my case, at least, it was because when I rooted, I didn't "format data" during the process. I've been told that if you don't format data during the process, you leave the data partition encrypted, and thus it can't be mounted (at least by non-system apps and processes). No guarantees here as always, but If you back everything up and redo the root process and do the data format, then you may be able to mount data. At that point you can restore your apps and info. I've also read (but haven't tried this!) that you can do a nandroid backup and restore ALL your data from that nandroid after you reset your phone (which the data format will do). You should google everything I have suggested and see if you can get what you need in this way, without having to reflash the ROM entirely or try to revert to stock recovery.
Click to expand...
Click to collapse
+1
Hi. Yes, I had to format everything. Now it works. Also the issues I had with Titanium Backup are gone. I flashed the ExtSdFix and I'm almost running like on Kitkat, yeah