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.
Hi,
My mom has an Asus TF300T running JB 4.2.1. She tried to root and flash OmniROM by herself and borked it somehow. Unfortunately, she didn't do any backup...
She entered the fastboot screen and there she selected wipe. Then she flashed openrecovery-twrp-2.6.3.0-tf300tg-JB.blob using fastboot.
Now I am trying to help her rescue it.
It's operational, the OS loads up fine and she can use it, install apps etc.
I can get to the fastboot screen and from there to the TWRP no problem, but TWRP can't mount anything besides system.
No dalvik partition, no data partition, not even the SD or external SD.
Naturally, I can't flash another rom...
Tried executing "fix permissions" from the TWRP menu, it didn't help.
Downloaded the latest official Asus blob file TF300T-US_epad-10_6_1_27_5-UpdateLauncher.zip and flashed it using fastboot, hoping it will restore the missing partitions but it didn't make any difference.
Also tried CWM - same issue.
Any ideas?
Thanks,
Sefi
chompy18 said:
Hi,
My mom has an Asus TF300T running JB 4.2.1. She tried to root and flash OmniROM by herself and borked it somehow. Unfortunately, she didn't do any backup...
She entered the fastboot screen and there she selected wipe. Then she flashed openrecovery-twrp-2.6.3.0-tf300tg-JB.blob using fastboot.
Now I am trying to help her rescue it.
It's operational, the OS loads up fine and she can use it, install apps etc.
I can get to the fastboot screen and from there to the TWRP no problem, but TWRP can't mount anything besides system.
No dalvik partition, no data partition, not even the SD or external SD.
Naturally, I can't flash another rom...
Tried executing "fix permissions" from the TWRP menu, it didn't help.
Downloaded the latest official Asus blob file TF300T-US_epad-10_6_1_27_5-UpdateLauncher.zip and flashed it using fastboot, hoping it will restore the missing partitions but it didn't make any difference.
Also tried CWM - same issue.
Any ideas?
Thanks,
Sefi
Click to expand...
Click to collapse
You are flashing the wrong TWRP. Flash: openrecovery-twrp-2.6.3.0-tf300tg-42.blob
Also If you are installing the KitKat OmniROM, you need TWRP 2.7+
cmendonc2 said:
You are flashing the wrong TWRP. Flash: openrecovery-twrp-2.6.3.0-tf300tg-42.blob
Also If you are installing the KitKat OmniROM, you need TWRP 2.7+
Click to expand...
Click to collapse
Wow! I missed that completely!!
That actually sounds promising.
Yeah, I want to flash KitKat OmniROM, so does the TWRP2.7+ also have a 42 version like the 2.6.30 or just flash TWRP 2.7+ ?
Thanks for your reply!
Sefi
chompy18 said:
Wow! I missed that completely!!
That actually sounds promising.
Yeah, I want to flash KitKat OmniROM, so does the TWRP2.7+ also have a 42 version like the 2.6.30 or just flash TWRP 2.7+ ?
Thanks for your reply!
Sefi
Click to expand...
Click to collapse
Actually, looking in the TWRP site here: http://techerrata.com/browse/twrp2/tf300t, there is no 2.7 version..
So, I'm just making sure, I should flash openrecovery-twrp-2.6.3.0-tf300t-4.2.blob and that should allow TWRP to mount the partitions, right?
What if I want to flash OmniROM KitKat (4.4)? Should I just flash 2.7 over openrecovery-twrp-2.6.3.0-tf300t-4.2.blob?
Thanks,
Sefi
chompy18 said:
Actually, looking in the TWRP site here: http://techerrata.com/browse/twrp2/tf300t, there is no 2.7 version..
So, I'm just making sure, I should flash openrecovery-twrp-2.6.3.0-tf300t-4.2.blob and that should allow TWRP to mount the partitions, right?
What if I want to flash OmniROM KitKat (4.4)? Should I just flash 2.7 over openrecovery-twrp-2.6.3.0-tf300t-4.2.blob?
Thanks,
Sefi
Click to expand...
Click to collapse
This guide has all the links, just flash omnirom instead of cm. There's only a 42 version, so make sure your bootloader is stock V10.6.1.27.1 or V10.6.1.27.5 or V10.6.1.15.3 . upgrade your bootloader if you are on V10.6.1.8.
http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
cmendonc2 said:
This guide has all the links, just flash omnirom instead of cm. There's only a 42 version, so make sure your bootloader is stock V10.6.1.27.1 or V10.6.1.27.5 or V10.6.1.15.3 . upgrade your bootloader if you are on V10.6.1.8.
http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
Click to expand...
Click to collapse
Thanks man! it worked!!!
I had to flash openrecovery-twrp-2.6.3.0-tf300t-4.2 and after it, upgrade to TWRP-TF300T-2_7_0_1 for complete SELinux support, only then could I flash omni-4.4.2-20140416-tf300t-NIGHTLY.
You rock!
Sefi
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
Hey guys I'm new to owning this device and just wanted to know if I have to reflash my firmware after clean flash?
This is what I do
Wipe System/Data/Art/Cache
From there I Flash Firmware/ROM/gapps
Is the firmware step required? Or can I just skip that step once I alreday flashed it previously?
I'm asking this question because I've been having some major issues flashing roms where they flash successfully but frankly just don't boot. I'm just not sure if I'm doing this correctly.
ChainFires Son said:
Hey guys I'm new to owning this device and just wanted to know if I have to reflash my firmware after clean flash?
This is what I do
Wipe System/Data/Art/Cache
From there I Flash Firmware/ROM/gapps
Is the firmware step required? Or can I just skip that step once I alreday flashed it previously?
I'm asking this question because I've been having some major issues flashing roms where they flash successfully but frankly just don't boot. I'm just not sure if I'm doing this correctly.
Click to expand...
Click to collapse
Clean flash involves wiping
/system /data /dalvik /cache
Then flash ROM + gapps
If you flash current firmware it should show 241 baseband in About Phone. Only need to do it once. No need to do every time you flash. CM nightlies do include firmware in their zips so by default will flash the firmware or at least check if its updated every nightly.
Use TWRP 2.8.6.0 or 3.0.0-1 which are versions known to flash firmware correctly.
If you flashed COS12.1.1 fastboot zip at any point in time your data and cache partitions will be F2FS and only certain ROMs will work with that. AOSP based ROMs most likely won't boot.
Sent from my A0001 using Tapatalk
Renosh said:
Clean flash involves wiping
/system /data /dalvik /cache
Then flash ROM + gapps
If you flash current firmware it should show 241 baseband in About Phone. Only need to do it once. No need to do every time you flash. CM nightlies do include firmware in their zips so by default will flash the firmware or at least check if its updated every nightly.
Use TWRP 2.8.6.0 or 3.0.0-1 which are versions known to flash firmware correctly.
If you flashed COS12.1.1 fastboot zip at any point in time your data and cache partitions will be F2FS and only certain ROMs will work with that. AOSP based ROMs most likely won't boot.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Appreciate the the reply! I'm going to restore to stock, and do it all over and update the baseband/firmware from there. Just to be safe ?
Hey guys, so I'm waiting for the OnePlus 6t and figured this is the best place to ask these questions since the 6 also has an A/B partition scheme.
1) Does advanced wiping with TWRP and then flashing stock rom flash both system partitions?
2) Does flashing stock rom also reflash the stock recovery to both partitions since the recovery now resides in the boot partition?
3) Can OnePlus devices receive OTA updates with TWRP installed and bootloader unlocked?
4) Can Google's adb and fastboot drivers work for the OnePlus 6? Or does it HAVE to be the universal drivers here on XDA?
I've done a lot of reading about A/B partition devices, but it's a new animal to me entirely.
Thanks guys!
H4X0R46 said:
Hey guys, so I'm waiting for the OnePlus 6t and figured this is the best place to ask these questions since the 6 also has an A/B partition scheme.
1) Does advanced wiping with TWRP and then flashing stock rom flash both system partitions?
2) Does flashing stock rom also reflash the stock recovery to both partitions since the recovery now resides in the boot partition?
3) Can OnePlus devices receive OTA updates with TWRP installed and bootloader unlocked?
4) Can Google's adb and fastboot drivers work for the OnePlus 6? Or does it HAVE to be the universal drivers here on XDA?
I've done a lot of reading about A/B partition devices, but it's a new animal to me entirely.
Thanks guys!
Click to expand...
Click to collapse
2) don't think so unless it comes with a recovery file to restore from
4) I believe the universal drivers work fine, the op6 comes with drivers when you connect it to your PC. I installed YouTube dark theme through adb a month or more ago but I have no experience with A/B partitions.
H4X0R46 said:
Hey guys, so I'm waiting for the OnePlus 6t and figured this is the best place to ask these questions since the 6 also has an A/B partition scheme.
1) Does advanced wiping with TWRP and then flashing stock rom flash both system partitions?
2) Does flashing stock rom also reflash the stock recovery to both partitions since the recovery now resides in the boot partition?
3) Can OnePlus devices receive OTA updates with TWRP installed and bootloader unlocked?
4) Can Google's adb and fastboot drivers work for the OnePlus 6? Or does it HAVE to be the universal drivers here on XDA?
I've done a lot of reading about A/B partition devices, but it's a new animal to me entirely.
Thanks guys!
Click to expand...
Click to collapse
1) It flashes the chosen rom to the other non-booted slot, the same goes with OOS (to b if you are booted to a) though other zip files flash to the current partitions. Both a and b slots share the same data partition.
3) Possibly, but it will unroot you and possibly wipe internal storage (that happened to me once).
H4X0R46 said:
Hey guys, so I'm waiting for the OnePlus 6t and figured this is the best place to ask these questions since the 6 also has an A/B partition scheme.
1) Does advanced wiping with TWRP and then flashing stock rom flash both system partitions?
2) Does flashing stock rom also reflash the stock recovery to both partitions since the recovery now resides in the boot partition?
3) Can OnePlus devices receive OTA updates with TWRP installed and bootloader unlocked?
4) Can Google's adb and fastboot drivers work for the OnePlus 6? Or does it HAVE to be the universal drivers here on XDA?
I've done a lot of reading about A/B partition devices, but it's a new animal to me entirely.
Thanks guys!
Click to expand...
Click to collapse
1) Already Answered
2) Yes. If you want to retain TWRP you have to flash it immediately after flashing any rom.
3) Already Answered but be cautious.
4) Yes, I have done tons of adb and fastboot commands on my OP6 just using the same abd and Fastboot setup leftover from my Pixel 2 XL. I have never installed anything OP6 related.