Database Info

[Q] What does "Wipe Data" from JB bootloader menu actually do?

I have been unsuccessfully trying to find an answer to this question for the last hour!
I know you better don't use this option if you have a custom recovery installed, but never learned: Why?
What does the stock bootloader wipe if you execute 'Wipe Data"?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

berndblb said:
I have been unsuccessfully trying to find an answer to this question for the last hour!
I know you better don't use this option if you have a custom recovery installed, but never learned: Why?
What does the stock bootloader wipe if you execute 'Wipe Data"?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
It tells the recovery to wipe the data. The issues exist where older versions of recoveries don't understand what a newer version of the bootloader told it to do. I don't know if it gets stuck in a loop at this point as the bootloader is now waiting for the recovery to finish or the recovery actually wipes the wrong partition?
If the bootloader and recovery are compatible there shouldn't be a problem. But why take the risk?
_that can probably offer more technical detail.......

sbdags said:
It tells the recovery to wipe the data. The issues exist where older versions of recoveries don't understand what a newer version of the bootloader told it to do. I don't know if it gets stuck in a loop at this point as the bootloader is now waiting for the recovery to finish or the recovery actually wipes the wrong partition?
If the bootloader and recovery are compatible there shouldn't be a problem. But why take the risk?
_that can probably offer more technical detail.......
Click to expand...
Click to collapse
Thanks sbdags!
I guess my question is: does 'Wipe data' from the BL menu on a stock system wipe only /data or also /system and ... anything else? Or is it just the same (in terms of result) as a format data in TWRP?
I am trying to help someone on the Transformer forum who seems to have a seriously messed up tablet: Lots of random reboots and freezes, Factory Reset from the Settings menu causes a restart and nothing else...
On a stock system Wipe Data from the BL should be ok to use, right?
I just don't want to send him down a path I don't fully understand....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

sbdags said:
It tells the recovery to wipe the data.
Click to expand...
Click to collapse
Correct.
sbdags said:
The issues exist where older versions of recoveries don't understand what a newer version of the bootloader told it to do. I don't know if it gets stuck in a loop at this point as the bootloader is now waiting for the recovery to finish or the recovery actually wipes the wrong partition?
If the bootloader and recovery are compatible there shouldn't be a problem. But why take the risk?
_that can probably offer more technical detail.......
Click to expand...
Click to collapse
The following is what I know - it might not be 100% corrrect because I've never tried it myself:
When the user chooses "wipe data" from the bootloader menu, the bootloader writes some information to the "misc" partition (mmcblk0p3) and starts the recovery. The recovery finds a command in the misc partition and formats (?) the data partition. When it is finished, it removes the command from the misc partition so that the bootloader can again boot Android. When it is interrupted in any way, after a reboot the bootloader will automatically enter the recovery directly.
The problem with this is if your recovery is broken or incompatible. I've read somewhere in this forum that the incompatibility is from enabling something called TF (Trusted Foundation) in the bootloader since JB, which requires a corresponding option in the (Android and recovery) kernel. If the kernel does not have this enabled, it cannot access the eMMC at all.
Now if your recovery cannot access the eMMC, you can't reset the information in the misc partition, and the bootloader will stubbornly try to boot the recovery to wipe data. The fact that not even the boot menu or fastboot works in this case makes this a hard brick.
berndblb said:
I guess my question is: does 'Wipe data' from the BL menu on a stock system wipe only /data or also /system and ... anything else? Or is it just the same (in terms of result) as a format data in TWRP?
Click to expand...
Click to collapse
It should only delete /data because if it wiped /system you could not boot Android anymore. It's called "ROM" for a reason.
berndblb said:
I am trying to help someone on the Transformer forum who seems to have a seriously messed up tablet: Lots of random reboots and freezes, Factory Reset from the Settings menu causes a restart and nothing else...
On a stock system Wipe Data from the BL should be ok to use, right?
Click to expand...
Click to collapse
I believe that "factory reset" from the Settings menu should do something similar as "wipe data" from the bootloader - instruct the recovery to wipe data and reboot. If that reboot does not enter the recovery, something seems wrong.
Wiping data from the bootloader *should* be safe on a stock system, but I'd check before if entering the stock recovery manually (Volume-down) works. I believe it even has a menu (try the Power button) that you can use for wiping data too, but maybe I am confusing this with early versions of CWM.

berndblb said:
Thanks sbdags!
I guess my question is: does 'Wipe data' from the BL menu on a stock system wipe only /data or also /system and ... anything else? Or is it just the same (in terms of result) as a format data in TWRP?
I am trying to help someone on the Transformer forum who seems to have a seriously messed up tablet: Lots of random reboots and freezes, Factory Reset from the Settings menu causes a restart and nothing else...
On a stock system Wipe Data from the BL should be ok to use, right?
I just don't want to send him down a path I don't fully understand....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Who is brave enough to try to test it? It may do what TWRP calls a factory wipe. I.e., it doesn't touch /data/media but does the rest of the data partition, it may do the full data partition.
Have a look in the TF101 forums for different types of bricks - there is a thread there describes two ot three types of bricks and solutions. You may find an answer there. Also look here for busters solution
http://forum.xda-developers.com/showthread.php?p=45120193#post45120193

sbdags said:
Who is brave enough to try to test it? It may do what TWRP calls a factory wipe. I.e., it doesn't touch /data/media but does the rest of the data partition, it may do the full data partition.
Click to expand...
Click to collapse
If something is called "factory reset" or "wipe data", I expect it to remove *all* user data. I don't know why TWRP is broken in this regard - OK, the feature to preserve /data/media is useful but then they shouldn't call it "factory reset".

_that said:
If something is called "factory reset" or "wipe data", I expect it to remove *all* user data. I don't know why TWRP is broken in this regard - OK, the feature to preserve /data/media is useful but then they shouldn't call it "factory reset".
Click to expand...
Click to collapse
I agree. They should call it "Almost Wipe Data" or "Kinda Wipe Data" :sly:
You are as always a treasure of knowledge! Thanks a million!
And I'll see if this bloke is desperate enough to give it a try - with full disclosure naturally...
I think he's still under warranty...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

sbdags said:
Who is brave enough to try to test it? It may do what TWRP calls a factory wipe. I.e., it doesn't touch /data/media but does the rest of the data partition, it may do the full data partition.
Have a look in the TF101 forums for different types of bricks - there is a thread there describes two ot three types of bricks and solutions. You may find an answer there. Also look here for busters solution
http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Click to expand...
Click to collapse
No, wipe from the bootlloader also wipe your personal data. I have been there and done that.

With " Wipe Data" only /system will survive, all other partitions will be wiped and personal data will be lost. Personally i can say that i tried every possible combination to brick this device (getting to a state where only APX could help - yes i have Nvflash blobs) but i always failed. Certainly the test were made with compatible bootloader - recovery.... and please don't try that at home if your device is not NvFlash capable.

Pretoriano80 said:
With " Wipe Data" only /system will survive, all other partitions will be wiped and personal data will be lost. Personally i can say that i tried every possible combination to brick this device (getting to a state where only APX could help - yes i have Nvflash blobs) but i always failed. Certainly the test were made with compatible bootloader - recovery.... and please don't try that at home if your device is not NvFlash capable.
Click to expand...
Click to collapse
+1 Good advice. You may get into more mess than you think..

Have a small issue i am running a custom recovery but used the factory reset option in cromi-x and now my tab is stuck in what i pressume is the wipe function described here it always boots straight into a recovery wipe cant access fastboot or anything any help?
However adb interface still works

Techpenguin5 said:
Have a small issue i am running a custom recovery but used the factory reset option in cromi-x and now my tab is stuck in what i pressume is the wipe function described here it always boots straight into a recovery wipe cant access fastboot or anything any help?
Click to expand...
Click to collapse
So what is the problem? You wanted to do a factory reset, and it does a factory reset. Wait until it is finished and it should reboot to Android.

_that said:
So what is the problem? You wanted to do a factory reset, and it does a factory reset. Wait until it is finished and it should reboot to Android.
Click to expand...
Click to collapse
it hasnt for half an hour so i rebooted manually and its stuck

Techpenguin5 said:
it hasnt for half an hour so i rebooted manually and its stuck
Click to expand...
Click to collapse
If you always reboot before it's finished it won't ever finish...

_that said:
If you always reboot before it's finished it won't ever finish...
Click to expand...
Click to collapse
how long is it supposed to take the progress bar is just moving like not even started the actual process

Techpenguin5 said:
how long is it supposed to take the progress bar is just moving like not even started the actual process
Click to expand...
Click to collapse
you have not told us yet which custom recovery you have it also depends on the storage size of your device and probably what you had installed your posts are really hard to read you should use some punctuation

_that said:
you have not told us yet which custom recovery you have it also depends on the storage size of your device and probably what you had installed your posts are really hard to read you should use some punctuation
Click to expand...
Click to collapse
I apologize for the bad punctuation i am just freaking out therefore not thinking when i type.
So here is a summary
Recovery=CWM
ROM=Cromi-x
Unlocked bootloader
Stuck in cwm recovery wipe which is not initiating for whatever reason
adb works
Thank you for you time , perhaps all i need to do is use an adb command to stop the wipe

Techpenguin5 said:
I apologize for the bad punctuation i am just freaking out therefore not thinking when i type.
So here is a summary
Recovery=CWM
ROM=Cromi-x
Unlocked bootloader
Stuck in cwm recovery wipe which is not initiating for whatever reason
adb works
Thank you for you time , perhaps all i need to do is use an adb command to stop the wipe
Click to expand...
Click to collapse
No - just listen to _that and let it finish! It can take 6 hours+. Connect it to a power source and leave it alone.
Sent from my K00C using Tapatalk

berndblb said:
No - just listen to _that and let it finish! It can take 6 hours+. Connect it to a power source and leave it alone.
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Thank you sooooooo much for this worked like a charm. Cant thank you enough, was scared it was gone.
again thanks

Techpenguin5 said:
Thank you sooooooo much for this worked like a charm. Cant thank you enough, was scared it was gone.
again thanks
Click to expand...
Click to collapse
well.. i am the guy who messed it up.. wipe data from bootloader.. now stuck in twrp loop aaaand fastboot/adb dont recognize the device! any word before the transformer meet its creator?

[Q] [A510]Boot loop

Hi,
I installed CM 10.2 on my A510 to try it out, did a full wipe, and got stuck in a boot loop. Wiped again and reinstalled but had the same issue. I have tried again with CM 10.1.3 and the AOKP roms but have the same issue, full wipe before each install. Right now I cannot get past the boot screen where the tablet restarts and tries again and again and again etc....
Any help would be welcome.
Thanks

When you say Full Wipe, it means Factory reset ?
Did you try to restore a Backup with CWM or TWRP ?

Yes factory reset. I tried restoring with CWM but each of my backups fail to restore either failing to restore /data or /system.
Sent from my GT-I9300 using Tapatalk

Did you try to copy your zip file both on internal and external sd card ?
checked MD5sum ?
Did you try to flash a stock ROM from Acer ?

Shreps said:
Did you try to copy your zip file both on internal and external sd card ?
checked MD5sum ?
Did you try to flash a stock ROM from Acer ?
Click to expand...
Click to collapse
Yes to all the above. Did the stock ROM one hour ago and doesn't boot loop buts just sticks at the iconia tab logo. Also when I try to get recovery now I just get a dead Android picture.
Edit: Using Stock ROM I get a message that Android is upgrading Optimizing aa 1 of 46, 2 of 46, 3 of 46 and it then retorns to the iconia tab logo and stays there

I finally got the tablet working again by installing the original ROM using fastboot for each of system, flexrom, boot and recovery. I then installed 10.2 which works OK apart from the fact that when using Titanium to restore my apps the tablet reboots randomly. So far I've only managed to restore 10% of my apps.
EDIT: Constant reboots now regardless of what I'm doing, downloading, installing etc. Going to try another ROM, 10.1 or AOKP. On 10.1 now, restoring apps from Google works for a while but after a certain stage random reboots starts again.
Lastest, back in endless boot loop. Tried restoring by fastboot but flexrom restore fails every time.

I have a similar problem on my A700... Installed 10.2 and then suddenly did not boot anymore. Tried to flash the nighly before the newest one but id did not change. Then i made a backup in CWM and formatted DATA. Now i boots but if i restore the backup, it won't boot. I can find my files in a 0\0\0\0\0 Folder or something like that. So nothing is lost, but it's not in the running system.
How to restore these files and apps?

After at least 25 wipes and flashing various roms 10.1 10.2 and AOKP I think my tablet is reasonably stable now. I formatted - /data /system /flexrom internal storage, everything except the external sd a few times then installed and have only had one random reboot since 2am. Instead of restoring from titanium or direct from Google I reinstalled all my apps individually and the restored my data from titanium. Hopefully this will be the end of this.
Sent from my GT-I9300 using Tapatalk

Bootloop after Factory reset

Hi guys,
got my nexus 5 yesterday and wanted to flash AOSP. But at some time, something might have broken, because now I get a bootloop after factory reseting via Kwongger Nexus5 Toolkit, ADB sideload via CWM, via zip, ... I tried everything, wiped everything, erased anything via fastboot. When I boot into CWM, there are messages like "E: cant mount cache, invalid argument", so my prediction is, that something bad happened to partition table or likely.
Does anyone have any idea how I can fix this? I searched the whole internet up and down, comparing to other devices like nexus 4 which I use right now.
Every idea is well-appreciated ALOT :good:

Natural_born_chilla said:
Hi guys,
got my nexus 5 yesterday and wanted to flash AOSP. But at some time, something might have broken, because now I get a bootloop after factory reseting via Kwongger Nexus5 Toolkit, ADB sideload via CWM, via zip, ... I tried everything, wiped everything, erased anything via fastboot. When I boot into CWM, there are messages like "E: cant mount cache, invalid argument", so my prediction is, that something bad happened to partition table or likely.
Does anyone have any idea how I can fix this? I searched the whole internet up and down, comparing to other devices like nexus 4 which I use right now.
Every idea is well-appreciated ALOT :good:
Click to expand...
Click to collapse
Best thing to do imo atm is to flash a factory image in fastboot and reroot afterwards bro.

gee2012 said:
Best thing to do imo atm is to flash a factory image in fastboot and reroot afterwards bro.
Click to expand...
Click to collapse
Tried that like 500x times with different factory images, right from google, from toolkit etc., tried using fastboot, flash-all.bat from google factory images and flashed via adb sideload. Same thing everytime. Boot loop and it won't work ...
Edit: found this a minute ago http://forum.xda-developers.com/showpost.php?p=47170893&postcount=291

Natural_born_chilla said:
Tried that like 500x times with different factory images, right from google, from toolkit etc., tried using fastboot, flash-all.bat from google factory images and flashed via adb sideload. Same thing everytime. Boot loop and it won't work ...
Edit: found this a minute ago http://forum.xda-developers.com/showpost.php?p=47170893&postcount=291
Click to expand...
Click to collapse
Go into recovery and clear the caches and do a data factory reset and see if it boots, if it doesn`t go into fastboot and flash a Google factory image. A good advice = DO NOT USE TOOKITS. Good luck bro

[Q] TRansformer 101 in loop help

I had katkiss 4.3 running on my pad and tried to update to ktkiss 4.4 and it came up with error . Then when I rebooted it hung in start up screen. So I rebooted into twrp recovery and reinstalled the backup I had made before I started . all seemed to go ok until I rebooted now all I get is
First the asus startup screen comes on then the twrp screen comes up but I get no menu its on a couple of seconds then goes blank I then get the following come up in bottom corner.
Verifying file system
Verifying partition size
Formatting/ data
wiping data without wiping /Data/media
Formatting cache
It then keeps repeating this again in a loop. I have tried to use easy flasher but because it keeps restarting it will not recognise the drivers on my pc. Can anybody help or have I bricked it
With thanks
Mickr

Easyflasher uses APX mode, did you make sure the TF was in APX mode first ? (Volume Up & Power)
If it is rebooting even in APX mode, sounds like a more serious hardware error

*Detection* said:
Easyflasher uses APX mode, did you make sure the TF was in APX mode first ? (Volume Up & Power)
If it is rebooting even in APX mode, sounds like a more serious hardware error
Click to expand...
Click to collapse
I have managed to reinstall twrp recovery and now want install the katkiss rom , do I have install the standard asus rom first and then reroot it before I can install the katkiss rom
with thanks

No, just flash any custom ROM you like from TWRP, forget about stock ROMs now
Just make sure you wipe everything first if your coming from Stock, then flash ROM & Gapps, then wipe Cache & Dalvik Cache, then reboot

*Detection* said:
No, just flash any custom ROM you like from TWRP, forget about stock ROMs now
Just make sure you wipe everything first if your coming from Stock, then flash ROM & Gapps, then wipe Cache & Dalvik Cache, then reboot
Click to expand...
Click to collapse
Thanks for that now up and running
Mickr

Good stuff

Stuck on factory reset.

so my tablet tf300 is stuck on the factory reset android. i can not access the recovery. keeps rebooting to the factory reset android. i was updating cm when it prompted my wife to factory reset encryption did not match. wtf man. i can not get to fast boot no recovery. what do i do? i have the files from unbrickable. but i cant get fast boot.

kaos420 said:
so my tablet tf300 is stuck on the factory reset android. i can not access the recovery. keeps rebooting to the factory reset android. i was updating cm when it prompted my wife to factory reset encryption did not match. wtf man. i can not get to fast boot no recovery. what do i do? i have the files from unbrickable. but i cant get fast boot.
Click to expand...
Click to collapse
If you have your nvflash blobs you mean then you can follow this guide here - just think TF300.
http://forum.xda-developers.com/showthread.php?t=2538028

After about 2 hrs it rebooted and loaded.... So weird.
Sent From My 0x1 Note 3.i love tep....