Database Info

Corrupt internal SD Card

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.

[HELP!] Not booting after stagefright update!

Hi guys, can somebody help me? I received the stagefright update this morning and after downloading it and rebooting, the phone stopped working. It shows the logo animation for a few seconds then the screen goes black. It's a rooted and unlocked phone so i don't know if thats the cause. Also, i can access the recovery mode pressing power and down. Other than that nothing.

If you were rooted and updated ya..the rooting may be the reason
So as you can access the bootloader just flash the stock rom back and you will be done with it..

Jaydeep123 said:
So as you can access the bootloader just flash the stock rom back and you will be done with it..
Click to expand...
Click to collapse
I always forget how peacefull people with knowledge can be. Thanks mate, will do that.
But, just for curiosity: rooted phones tends to have problems after updates?

Yes It may get error or Somthing Else Thats Why I prefer if a update is avaiable flash back to stock and then proceed

Just a quick update. Flashed stock, worked fine. Thanks all.
Also, sorry for posting under general, i was so worried that i forgot to put this under HELP TROUBLESHOOTING.
Also, if I went there before i would find this thread here with the same problem and solution
http://forum.xda-developers.com/2015-moto-g/help/ota-caused-boot-loop-t3202322/
Thanks all again.

reinaldojr said:
Just a quick update. Flashed stock, worked fine. Thanks all.
Also, sorry for posting under general, i was so worried that i forgot to put this under HELP TROUBLESHOOTING.
Also, if I went there before i would find this thread here with the same problem and solution
http://forum.xda-developers.com/2015-moto-g/help/ota-caused-boot-loop-t3202322/
Thanks all again.
Click to expand...
Click to collapse
Mod will move or merge.
Sent from my MotoG3 using XDA Free mobile app

Technically, it should not install at all if it's been rooted. It's interesting that Moto has let this slip by.
In the future, if you have made a single change in the system partition...root, build.prop edit....anything...even custom recovery or kernel...you should reflash your current factory image, reboot, then flash your updated factory image. It's VERY IMPORTANT you reboot between flashing one factory image and the next, though. You may have more issues if you don't.

hp420 said:
Technically, it should not install at all if it's been rooted. It's interesting that Moto has let this slip by.
In the future, if you have made a single change in the system partition...root, build.prop edit....anything...even custom recovery or kernel...you should reflash your current factory image, reboot, then flash your updated factory image. It's VERY IMPORTANT you reboot between flashing one factory image and the next, though. You may have more issues if you don't.
Click to expand...
Click to collapse
Hello HP429; reflashin full factory image would effectively wipe phone

sunandoghosh said:
Hello HP429; reflashin full factory image would effectively wipe phone
Click to expand...
Click to collapse
Not if you only flash the system, boot and recovery image files

Recover the factory
I did the update and as mentioned previously on the thread stales after the logo. (bootloader is unlocked)
I can not find my oem backup. I tried twrp on recovery and was able to backup other stuff. Is there a way to generate the OEM so that i can flash or any other roms that are compatible with Moto G 3rd generation?

Try wiping cache, dalvik cache and data with TWRP. Don't use stock recovery for the data wipe or you will lose all the files stored on your internal partition, as well.

All EMUI backups are unbootable when restored to

Throughout my phone's lifetime, I've made a lot of backups, most of which have ended up saved on my hard drive. I recently wanted to go back to stock from a custom rom, so I copied one of the emui backups over and restored to it. Everything seemed to go smoothly, no error messages, but attempting to boot only got stuck on the blue honor boot animation. Tried several other backups, some rooted and heavily customized, some fresh unmodded installs, but all of them did the same thing. Meanwhile, all my custom rom backups work just fine. What gives?

I tried it too and it doesn't work. I think its because to install a custom ROM we format the data using twrp which also removes the encryption of some sorts, when we restore the backup that encryption is lost so it stays stuck at the blue Honor logo. That's my two sense on this. I don't know the real details.

asaditya379 said:
I tried it too and it doesn't work. I think its because to install a custom ROM we format the data using twrp which also removes the encryption of some sorts, when we restore the backup that encryption is lost so it stays stuck at the blue Honor logo. That's my two sense on this. I don't know the real details.
Click to expand...
Click to collapse
That does make more sense than anything I've thought of so far. So to restore from one of these backups, would I just have to reinstall emui from scratch first to get that encryption back? Is there another way to restore them without first having emui? Or are they just useless now?

Gannondalf said:
That does make more sense than anything I've thought of so far. So to restore from one of these backups, would I just have to reinstall emui from scratch first to get that encryption back? Is there another way to restore them without first having emui? Or are they just useless now?
Click to expand...
Click to collapse
I haven't been able to find a solution to this. What I do is use firmware finder to download the firmware+region zip and then install them together in any order via twrp. By this process you lose the data and twrp too as it is replaces by stock recovery. Before booting you must try to get into the stock recover and hit factory reset. You'll get EMUI back but no matter what you do you won't get your data back. Twrp backup is helpless I think because I've tried all sorts of things to get my data back.

asaditya379 said:
I haven't been able to find a solution to this. What I do is use firmware finder to download the firmware+region zip and then install them together in any order via twrp. By this process you lose the data and twrp too as it is replaces by stock recovery. Before booting you must try to get into the stock recover and hit factory reset. You'll get EMUI back but no matter what you do you won't get your data back. Twrp backup is helpless I think because I've tried all sorts of things to get my data back.
Click to expand...
Click to collapse
I've tried flashing emui firmware through twrp before and the region zip always works, but I've never gotten it to load the update.zip (using adb sideload for everything). But I'll try a few different things and see if I can get that to work. Getting back to emui is my primary focus since most of my data is backed up somewhere else, but if I find a way to successfully restore data from backups I'll let you know.

Gannondalf said:
I've tried flashing emui firmware through twrp before and the region zip always works, but I've never gotten it to load the update.zip (using adb sideload for everything). But I'll try a few different things and see if I can get that to work. Getting back to emui is my primary focus since most of my data is backed up somewhere else, but if I find a way to successfully restore data from backups I'll let you know.
Click to expand...
Click to collapse
What I'm telling is probably the easiest way let me break it down for you again.
1. Download firmware+region zip file from firmware finder.
2. Go to twrp, clear everything (format data).
3. Install the two downloaded zip I usually flash firmware and then the region zip.
4. After installation is over don't reboot go back to twrp home screen and reboot to recovery, which will be stock.
5. Format data using stock recover and then clear cache.
6. Restart and everything should work.
And if you find a way to get the twrp backups do post here.

What and how to backup before Ubuntu Touch install?

Hi everyone,
I'm a noob to the OPO and also a bit of a noob to backing up and restoring individual partitions, although I have some experience with flashing the Nexus 5 and Z3C with B2GOS and /e/.
I'd like to put Ubuntu Touch on my OPO. I'd like to make sure I can return the phone to stock afterwards, if needed (e.g., I want to sell it as stock). I was thinking of taking partition images with TWRP first, will this be sufficient? I see there's a tool for backing up the EFS as well, so I suppose I should do that.
Or maybe I need to do nothing! Will it be sufficient just to reflash stock firmware when I want to return to stock? If a combination of both flashing stock firmware and TWRP images, EFS backup, what order does it need to be done in?
Thanks for your help in advance.
Cheers

madb1lly said:
Hi everyone,
I'm a noob to the OPO and also a bit of a noob to backing up and restoring individual partitions, although I have some experience with flashing the Nexus 5 and Z3C with B2GOS and /e/.
I'd like to put Ubuntu Touch on my OPO. I'd like to make sure I can return the phone to stock afterwards, if needed (e.g., I want to sell it as stock). I was thinking of taking partition images with TWRP first, will this be sufficient? I see there's a tool for backing up the EFS as well, so I suppose I should do that.
Or maybe I need to do nothing! Will it be sufficient just to reflash stock firmware when I want to return to stock? If a combination of both flashing stock firmware and TWRP images, EFS backup, what order does it need to be done in?
Thanks for your help in advance.
Cheers
Click to expand...
Click to collapse
Hi,
I don't have much time at the moment. I tested Ubuntu Touch just a few weeks ago. Some (not all) bacon users have broken Wlan. I'm one of them. Because of that I went back to Android. So it's possible.
It was a bit tricky. Of course I recommend a full nandroid backup. Copy it to a save place (for example your PC). Don't change any partitions on your phone during installation.
To go back (if I'm remembering wright):
- flash latest recovery via fastboot
- reboot in recovery (for me it was still the Ubuntu recovery)
- anywhere there was an option to boot Android
- take this option and you will reboot in the Android recovery
- there you can restore your previous backup
Hope I could help. If you try Ubuntu Touch, please report, of Wlan works for you.
Good luck. And add said: I don't really remember the whole procedure, so at your own risk.

Hi!
Gaukler_Faun said:
Hi,
I don't have much time at the moment. I tested Ubuntu Touch just a few weeks ago. Some (not all) bacon users have broken Wlan. I'm one of them. Because of that I went back to Android. So it's possible.
It was a bit tricky. Of course I recommend a full nandroid backup. Copy it to a save place (for example your PC). Don't change any partitions on your phone during installation.
To go back (if I'm remembering wright):
- flash latest recovery via fastboot
- reboot in recovery (for me it was still the Ubuntu recovery)
- anywhere there was an option to boot Android
- take this option and you will reboot in the Android recovery
- there you can restore your previous backup
Hope I could help. If you try Ubuntu Touch, please report, of Wlan works for you.
Good luck. And add said: I don't really remember the whole procedure, so at your own risk.
Click to expand...
Click to collapse
Thanks for the tip about WLAN, I didn't know about that. If I have any issues I'll post here and in the UBPorts forum.
Okay, a full Nandroid backup I can do. But don't I have to flash TWRP to the recovery partition to do that? If so, do I need to backup the recovery partition somehow first?
Thanks

madb1lly said:
Hi!
Thanks for the tip about WLAN, I didn't know about that. If I have any issues I'll post here and in the UBPorts forum.
Okay, a full Nandroid backup I can do. But don't I have to flash TWRP to the recovery partition to do that? If so, do I need to backup the recovery partition somehow first?
Thanks
Click to expand...
Click to collapse
No, I don't think you need. It would be good to have the original recovery file... But I never backed up my original recoveries. One of the first things I make with a new phone is flashing twrp. So I would just download the latest image for Bacon and flash it via fastboot.
I recommend to back up your personal data (pictures, documents, ...) ton tour PC. Who knows.

Gaukler_Faun said:
No, I don't think you need. It would be good to have the original recovery file... But I never backed up my original recoveries. One of the first things I make with a new phone is flashing twrp. So I would just download the latest image for Bacon and flash it via fastboot.
I recommend to back up your personal data (pictures, documents, ...) ton tour PC. Who knows.
Click to expand...
Click to collapse
Thanks, that's helpful. I don't actually know how to backup the recovery partition other than using root access and presumably some ADB command, so if it's not needed then that's good news. I will of course backup my data first, but a reminder is always a good thing!
Cheers

How do I backup / restore using TWRP on the OP7P?

Hi - I did a TWRP System/Data/Boot backup of my OP7P about a month ago, and decided this weekend that I needed to go back to that image.
When I did a TWRP restore, everything looked fine, but after rebooting ... I was stuck in Fastboot Mode (just like in this thread). Fortunately, I was able to get my OP7P again, but I was panicking for a while!
Since that TWRP backup / restore didn't work, I wanted to find out what I did wrong.
How do I properly do a TWRP backup / restore on the OP7P without bricking my phone?
Thanks!

Take note of the statement on the TWRP thread: "For the Backups use always "system_image" and "vendor_image" instead of "system" and "vendor"."
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
I also believe there is some trick to the Slot A/B thing. Like you need to flash to both slots? Never had to restore a TWRP backup on this device yet. So I'm just passing on what I can remember reading.

Could someone please give a little detailed reply / help.
I tried to update from 10.3.1 to 10.3.2.
After update I lost wifi.
Fortunately I made a twrp backup
Unfortunately the restore failed (stuck at restore boot).
First I have to revitalize with guac recov tool.
Later I want to restore backup - how?

Yup, fastboot loop after twrp restore as well.

Ist there really no option to restore?
Gesendet von meinem GM1913 mit Tapatalk

It happened to me too recently. Actually I'm on Beta5 on my 7Tpro McLaren and want to try a rollback to stable release due to some problems (black crush and bad dark levels), just to know if they are software related because I have no memory about how it was when on Stable ROM.
Now I'm unlocked, rooted (Magisk) thanks to All in ONE Tool. Recovery is stock because I'm not confident on flashing TWRP. Differently from my old OP5T there are two partitions and I don't know how to handle them.
Furthermore, when I boot TWRP it doesn't find all partition. For example it says data partition is 0MB.
Any suggestion?
Thanks guys!

franzkekko said:
It happened to me too recently. Actually I'm on Beta5 on my 7Tpro McLaren and want to try a rollback to stable release due to some problems (black crush and bad dark levels), just to know if they are software related because I have no memory about how it was when on Stable ROM.
Now I'm unlocked, rooted (Magisk) thanks to All in ONE Tool. Recovery is stock because I'm not confident on flashing TWRP. Differently from my old OP5T there are two partitions and I don't know how to handle them.
Furthermore, when I boot TWRP it doesn't find all partition. For example it says data partition is 0MB.
Any suggestion?
Thanks guys!
Click to expand...
Click to collapse
I am able to backup and restore on my OP7T HD1910 with TWRP now. If anyone needs some advice/help feel free to message me and I'll try and help you out. It took me a lot of testing to figure out and it's not easiest thing to do or the quickest but it is possible!