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?
Related
Hello,
I was trying to root my Nexus S, and in the mean time don't know what failed, but now I cannot boot.
If I boot normally, pressing the power button, it gets stucks in the screen showing "Google" and nothing happens.
I can access the recovery menu if I press the volume up button while pressing the power button. I tried to reload images and recover from them, but it always get stucks in the image of the android with the exclamation.
My question is, does any of you know how I can repair my booting? At this point I don't care if I lose the root or not.
Thank you!
The exclamation is probably the stock recovery do you know how to use ADB
Sent from my HTC Desire HD using XDA App
yes, I know how to use it, not an expert but i know how to use it.
try this
http://forum.xda-developers.com/showthread.php?t=1105892
duendecito_vivo said:
Hello,
I was trying to root my Nexus S, and in the mean time don't know what failed, but now I cannot boot.
If I boot normally, pressing the power button, it gets stucks in the screen showing "Google" and nothing happens.
I can access the recovery menu if I press the volume up button while pressing the power button. I tried to reload images and recover from them, but it always get stucks in the image of the android with the exclamation.
My question is, does any of you know how I can repair my booting? At this point I don't care if I lose the root or not.
Thank you!
Click to expand...
Click to collapse
seems like you never flashed to stock or bad flash try full wipe and flash either rooted stock or custom rom
Didn't help, no useful solution in that thread, however will keep an eye there if something new comes up.
Anyone experienced the same problem ?
sammael1069 said:
seems like you never flashed to stock or bad flash try full wipe and flash either rooted stock or custom rom
Click to expand...
Click to collapse
how to do it ?
duendecito_vivo said:
Didn't help, no useful solution in that thread, however will keep an eye there if something new comes up.
Anyone experienced the same problem ?
Click to expand...
Click to collapse
this guy pulled battery and wiped dalvik-cache
http://forum.xda-developers.com/showthread.php?t=1042452&highlight=boot+loop
duendecito_vivo said:
how to do it ?
Click to expand...
Click to collapse
in clockwork mod
-advanced-wipe dalvik cache
but from root and stuck on bootloop you might need to reflash the rooted stock rom. it is usually PDxx.IMG what root method did you use? did you get any errors?
I got no errors.
I already tried to flash with several differents .img, but none worked so far... I tried really a lot differents. Always get stuck at booting.
sammael1069 said:
this guy pulled battery and wiped dalvik-cache
http://forum.xda-developers.com/showthread.php?t=1042452&highlight=boot+loop
Click to expand...
Click to collapse
It didn't work
duendecito_vivo said:
I got no errors.
I already tried to flash with several differents .img, but none worked so far... I tried really a lot differents. Always get stuck at booting.
Click to expand...
Click to collapse
Hello!
If you see the triangle and ! when you go into recovery, then you just need to flash clockworkmod recovery. Then you can flash a ROM.
if your in clockwork do full wipe then flash new img i always do this order
-mounts and storage
-format /cache
-format /data
-format /system
-back to advanced
-wipe dalvik cache
-wipe battery stats
-*****go back****
-wipe data/factory reset
-now flash rom
already tried, didn't work... nothing happens
the same happens, still get stuck during booting....
after wipe do you see rom install
sammael1069 said:
if your in clockwork do full wipe then flash new img i always do this order
-mounts and storage
-format /cache
-format /data
-format /system
-back to advanced
-wipe dalvik cache
-wipe battery stats
-*****go back****
-wipe data/factory reset
-now flash rom
Click to expand...
Click to collapse
I did it, still getting stuck in Google screen during booting
duendecito_vivo said:
the same happens, still get stuck during booting....
Click to expand...
Click to collapse
how long is it in boot some can go 10 min.
first boot is always long
which rom are you flashing
sammael1069 said:
how long is it in boot some can go 10 min.
first boot is always long
Click to expand...
Click to collapse
Really, so long? Ok, I will wait
duendecito_vivo said:
Really, so long? Ok, I will wait
Click to expand...
Click to collapse
Ok, more than 10 mins booting, nothing happens.
Gents,
Was hoping you could help. I've gone to flash a kernel and during reboot, the tablet has displayed the "encryption unsuccessful" message that a lot of users are getting with ICS on other devices (example.
What this means is that although i never set up encryption, the device is expecting it for some reason (bad kernel flash possibly) and as a result has walled off and denied access to /data and /sdcard.
This means that im unable to flash anything from CWM as i get an error "e: can't mount /sdcard/"
So. I have got a semi bricked device. I do however have access to
- ADB (i can push to SD also)
- shell
- Download Mode
- some sort of android system when it shows the "encryption failure" message (volume can be changed etc) and USB is recognized
What i do not have access to is
- NV flash (b70k) model, so manual flash fails
- Anroid OS
- SD card through CWN
- /data
I've tried flashing blob, boot.img etc through ADB and have followed this guide which gives some pretty good shell commands but none of it has worked.
to me, it seems like the internal /data is corrupted and the only solution i have seen is someone who has installed the OS on a virtual drive inside a SD card which obviously isn't great
Ideas, thoughts? Ill try anything..
any ideas?
lowgoz said:
any ideas?
Click to expand...
Click to collapse
what hapen when you wipe by power and volume down ? (NOT cmw wipe ) ( keep in mind this will wipe data )
It attempts to reboot and wipe in CWM which fails due to it being unable to mount /data
Im also unable to mount /data through the shell
What about trying to push stock recovery and allow it to load any other stock ROM other than ICS?
I know this is a last-ditch effort because if you are successful in pushing a new recovery and that doesn't boot correctly, you have lost CWM and thus likely ADB into your device..so use ths advice with caution only as a last resort..thinking you may need to go back to stock in order to solve your issue, and start all over again, if possible even.
luna_c666 said:
What about trying to push stock recovery and allow it to load any other stock ROM other than ICS?
I know this is a last-ditch effort because if you are successful in pushing a new recovery and that doesn't boot correctly, you have lost CWM and thus likely ADB into your device..so use ths advice with caution only as a last resort..thinking you may need to go back to stock in order to solve your issue, and start all over again, if possible even.
Click to expand...
Click to collapse
I dont think that recovery is the issue, as my CWM recovery is working fine, its just not allowing me access to /data which i need to push / update / flash a new rom
to be able to do what your suggesting above, the system will need to access the /data/ partition which has been encrypted with a key that i don't know. Is there any way to low level format the /data/ partition using shell ?
Not cmw wipe > boot mode wipe what ever it may be calt dont go to recover but let it go to wipe or dont you have this option.
On my tf when holding vol down and power once displays oni need to press up for recoverybut if idont it wil start wipe in 5 sec
Verstuurd van mijn Transformer TF101 met Tapatalk
it happened to my transformer before... i nvflash the prime rom 2.10 and everything was fine again
He has no nvflash locked bootloader
Verstuurd van mijn Transformer TF101 met Tapatalk
Jhinta said:
Not cmw wipe > boot mode wipe what ever it may be calt dont go to recover but let it go to wipe or dont you have this option.
On my tf when holding vol down and power once displays oni need to press up for recoverybut if idont it wil start wipe in 5 sec
Verstuurd van mijn Transformer TF101 met Tapatalk
Click to expand...
Click to collapse
ya, im using that wipe and for some reason it says "rebooting into recovery to perform factory reset"
lowgoz said:
ya, im using that wipe and for some reason it says "rebooting into recovery to perform factory reset"
Click to expand...
Click to collapse
What about creating a blob for data only this sould wipe the whole data partition dont realy know how to create te img but sould be a option
Verstuurd van mijn HTC Desire HD met Tapatalk
luna_c666 said:
What about trying to push stock recovery and allow it to load any other stock ROM other than ICS?
I know this is a last-ditch effort because if you are successful in pushing a new recovery and that doesn't boot correctly, you have lost CWM and thus likely ADB into your device..so use ths advice with caution only as a last resort..thinking you may need to go back to stock in order to solve your issue, and start all over again, if possible even.
Click to expand...
Click to collapse
Sounds like this is the best option
Sent from my Transformer TF101 using Tapatalk
Any solution to this? I woke up today to an "encryption unsuccessful" and made the mistake of hitting the reset button. Revolution 3.1.0 rom. ****.
edit: I was able to use nvflash to flash an older rom and CWM and after that flashed ICS again. Let's see what happens
I had this happen a few days ago as well. Was on EOS, happened just as I inserted tablet into the dock. Was able to NVFlash to stock thankfully.
Backwardsblade said:
I had this happen a few days ago as well. Was on EOS, happened just as I inserted tablet into the dock. Was able to NVFlash to stock thankfully.
Click to expand...
Click to collapse
For people who have TF with SBK2 like myself, we cannot use NVFlash. That means we are screwed if it happens.
Just to be sure, if the unsuccessful encryption message appears, I should turn off the TF immediately. And then go into CWM to reflash a ROM as the second step. Am I right?
Jhinta said:
What about creating a blob for data only this sould wipe the whole data partition dont realy know how to create te img but sould be a option
Verstuurd van mijn HTC Desire HD met Tapatalk
Click to expand...
Click to collapse
I think data is partition 15 or UDA. Someone with an encrypted tf will have to try this to see if it works.
It looks correct, although the flash.cfg file give it too small a file size???
kokopopz said:
For people who have TF with SBK2 like myself, we cannot use NVFlash. That means we are screwed if it happens.
Just to be sure, if the unsuccessful encryption message appears, I should turn off the TF immediately. And then go into CWM to reflash a ROM as the second step. Am I right?
Click to expand...
Click to collapse
I'm unsure what options you guys have. Some have suggested pushing a stock recovery back to the TF, but I don't know if there was an option developed for SBKv2 guys... and if it would even work. Its a gamble to give up CWM and adb. I know it scared the hell out of me... you might want to hit up the irc channel and see if anyone else found a fix.
Sent from my Transformer TF101 using XDA Premium HD app
Backwardsblade said:
I'm unsure what options you guys have.
Click to expand...
Click to collapse
According to the Android device encryption specs, you should be able to restore the system to working order if (and that's a big "if") you're able to create ex-novo an ext4 filesystem for the /data partition.
If (again: big "if" here, I didn't check TF101's init.rc) the system manages to find a useable /data partition during a cold boot you should be in business.
I honestly don't know, though, how you can format the eMMC data partition as ext4 via CWM: you'll most likely need to hack your way with adb and/or an ad-hoc Edify updater-script.
sbiriguda said:
According to the Android device encryption specs, you should be able to restore the system to working order if (and that's a big "if") you're able to create ex-novo an ext4 filesystem for the /data partition.
If (again: big "if" here, I didn't check TF101's init.rc) the system manages to find a useable /data partition during a cold boot you should be in business.
I honestly don't know, though, how you can format the eMMC data partition as ext4 via CWM: you'll most likely need to hack your way with adb and/or an ad-hoc Edify updater-script.
Click to expand...
Click to collapse
Jhinta suggested a data blob. It could probably be just a few MB of zeros to destroy the ext4 partition table or maybe a small ext4 filesystem to replace the existing partition.
gee one said:
Jhinta suggested a data blob. It could probably be just a few MB of zeros to destroy the ext4 partition table or maybe a small ext4 filesystem to replace the existing partition.
Click to expand...
Click to collapse
How about Super wipe? It does erase/format the filesystems if I am not mistaken.
[Edit] I found the following in the superwipe log. Will it be the solution for sbk2?
4. Erasing & formatting EXT4 *DATA* partitionabout to run program [/sbin/edify] with 2 args
So I just wiped my cache and dalvik in TWRP and now I have no radio, no IMEI, no storage.. I think it borked my partitions. Tried flashing the factory image to no avail. It failed on the radio and I still have no storage.
Is there any way to recover from this?
EDIT: I was able to fix it as easily as I caused it. Check the 4th post. More detailed instructions on the 3rd post of page 2.
_MetalHead_ said:
So I just wiped my cache and dalvik in TWRP and now I have no radio, no IMEI, no storage.. I think it borked my partitions. Tried flashing the factory image to no avail. It failed on the radio and I still have no storage.
Is there any way to recover from this?
Click to expand...
Click to collapse
There is no way you simply wiped cache and dalvik. That doesn't even come close to touching your IMEI.
Why did you go to clear your cache / dalvik in the first place? Describe anything you did in terms of installing apps, flashing, wiping, etc.
leblvin said:
There is no way you simply wiped cache and dalvik. That doesn't even come close to touching your IMEI.
Why did you go to clear your cache / dalvik in the first place? Describe anything you did in terms of installing apps, flashing, wiping, etc.
Click to expand...
Click to collapse
All I did was flash a zip to change the dpi of my navbar. I've flashed the same zip a couple times before. Wiped cache + dalvik and it hung up for a while, screen went black for 5 minutes then the phone rebooted into its current state. I realize that wiping the caches doesn't touch the IMEI or anything like that, but what if the version of TWRP I have is buggy?
So knowing that yes, that is all I did, is there any way to fix it?
After a bit of googling I got it fixed. Apparently sometimes TWRP will cause some havok with the partitions when wiping cache. I just updated to the latest TWRP, wiped the cache again and everything came back up. Weird.
Always run the very recovery latest version.
a hammerhead wrote this.
Might be worth backing up your EFS partition to be on the safe side!
Nandroid backup is your best friend
beekay201 said:
Always run the very recovery latest version.
a hammerhead wrote this.
Click to expand...
Click to collapse
Yup, didnt bother to check before.
EddyOS said:
Might be worth backing up your EFS partition to be on the safe side!
Click to expand...
Click to collapse
Agreed. First thing I'm gonna do when I get home from work.
gd6noob said:
Nandroid backup is your best friend
Click to expand...
Click to collapse
I have a recent nandroid. What good is it though if recovery can't see my storage where the nandroid was saved?
Sent from my Moto X
_MetalHead_ said:
After a bit of googling I got it fixed.
Click to expand...
Click to collapse
Well, whatever you do, don't share your find here in case someone else ever has the same problem.
GldRush98 said:
Well, whatever you do, don't share your find here in case someone else ever has the same problem.
Click to expand...
Click to collapse
I did share it. Read the rest of the post you quoted. Derp.
Sent from my Moto X
_MetalHead_ said:
lApparently sometimes TWRP will cause some havok with the partitions when wiping cache
Click to expand...
Click to collapse
I don't know about you, but this is just what I look for in a recovery
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
I don't know about you, but this is just what I look for in a recovery
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
It's a TWRP exclusive feature.
_MetalHead_ said:
After a bit of googling I got it fixed. Apparently sometimes TWRP will cause some havok with the partitions when wiping cache. I just updated to the latest TWRP, wiped the cache again and everything came back up. Weird.
Click to expand...
Click to collapse
Big thank you for this, I thought I was boned. I was trying to flash 4.4.1 but forgot that I had modified the screen density in the build.prop and so I got an error, tried to wipe the cache, thought it had hung up, got impatient and VERY stupid and forced the phone to reboot. SDCard was entirely inaccessible, couldn't connect to AT&T, everything was screwed up and everything I could find told me that wiping everything back to stop and losing the data was my only option. I had a week-old TiBu on my dropbox, which isn't bad but not great either. Nandroid, of course, inaccessible along with the SDcard. Your trick of updating TWRP (I had 2.6.3.2, latest is 2.6.3.4) and then wiping the cache again worked perfectly.
To anyone who comes across this, here's a quick overview:
1. Download the latest TWRP at http://teamw.in/project/twrp2/205
2. Boot your phone into Fastboot mode (Vol Down + Power from off, I think...worked for me)
3. Make sure your phone is plugged in via USB.
4. Open a command prompt in the folder you put TWRP in (ADB needed, obviously), type:
fastboot flash recovery imagename.img
For example:
fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img
5. Only took a couple seconds until it was finished. Used the volume buttons to highlight Restart Recovery, hit power to reboot into recovery.
Wipe > Advanced Wipe, wipe what you need to wipe, viola, it was working at this point for me. Rebooted the phone, everything's back to normal. (it went through the "Optimizing apps" things on boot-up which took a few minutes, but everything is where I left it).
reynwrap582 said:
Big thank you for this, I thought I was boned. I was trying to flash 4.4.1 but forgot that I had modified the screen density in the build.prop and so I got an error, tried to wipe the cache, thought it had hung up, got impatient and VERY stupid and forced the phone to reboot. SDCard was entirely inaccessible, couldn't connect to AT&T, everything was screwed up and everything I could find told me that wiping everything back to stop and losing the data was my only option. I had a week-old TiBu on my dropbox, which isn't bad but not great either. Nandroid, of course, inaccessible along with the SDcard. Your trick of updating TWRP (I had 2.6.3.2, latest is 2.6.3.4) and then wiping the cache again worked perfectly.
To anyone who comes across this, here's a quick overview:
1. Download the latest TWRP at http://teamw.in/project/twrp2/205
2. Boot your phone into Fastboot mode (Vol Down + Power from off, I think...worked for me)
3. Make sure your phone is plugged in via USB.
4. Open a command prompt in the folder you put TWRP in (ADB needed, obviously), type:
fastboot flash recovery imagename.img
For example:
fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img
5. Only took a couple seconds until it was finished. Used the volume buttons to highlight Restart Recovery, hit power to reboot into recovery.
Wipe > Advanced Wipe, wipe what you need to wipe, viola, it was working at this point for me. Rebooted the phone, everything's back to normal. (it went through the "Optimizing apps" things on boot-up which took a few minutes, but everything is where I left it).
Click to expand...
Click to collapse
Yeah man, I was certain I was gonna need a new phone. Glad this helped you. I'm going to update the OP with a link to your post so more inexperienced users can benefit. Thanks for typing it out.
_MetalHead_ said:
So I just wiped my cache and dalvik in TWRP and now I have no radio, no IMEI, no storage.. I think it borked my partitions. Tried flashing the factory image to no avail. It failed on the radio and I still have no storage.
Is there any way to recover from this?
EDIT: I was able to fix it as easily as I caused it. Check the 4th post. More detailed instructions on the 3rd post of page 2.
Click to expand...
Click to collapse
I remember you from the HTC one forums! Figures you already messed up your Nexus 5... Lol
Sent from my Nexus 5 using Tapatalk
MrGriffdude said:
I remember you from the HTC one forums! Figures you already messed up your Nexus 5... Lol
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hey now, it wasn't my fault! Lol
Sent from my Nexus 5 using XDA Premium 4 mobile app
Now it's my turn. Pressed factory reset by accident in boot loader. Can get to TWRP but it says E: Unable to mount storage
e:Unable to mount /sdcard/TWRP/twps. when trying to read settings file. etc...
Advanced File manager in TWRP shows /sdcard/TWRP
Any ideas???? If I try to mount data in TWRP my Mac wants to initialize.
Thanks
TWRP shows internal storage 0 mb
I flashed the stock recovery, then ran it and somehow it booted right into CM11. Everything was lost, but it's working again.
Factory reset wipe everything! Including SD card.
null0seven said:
Factory reset wipe everything! Including SD card.
Click to expand...
Click to collapse
Possibly, but how come CM11 was still on there? I think that the Boot Loader in Moonshine's factory reset is not compatible with CM11. Luckily the stock recovery fixed things for me.
808phone said:
Possibly, but how come CM11 was still on there? I think that the Boot Loader in Moonshine's factory reset is not compatible with CM11. Luckily the stock recovery fixed things for me.
Click to expand...
Click to collapse
I had the same issue, pressed by mistake factory reset in bootloader some time ago. I was pressing vol down to reach recovery, there was a slight lag and I pressed it a second time the immediately I've pressed power...so cursor has jumped 2 rows then executed. I've solved it only by flashing stock recovery and resetting to factory settings again, then flashed TWRP.
Now why you still had CM11...well not 100% sure but in TWRP when you wipe to factory the system partition is not formatted. I've paid attention once to the messages during a wipe and it was formatting data, cache, dalvik and android secure but not system. A reason can be that while flashing any ROM, the install script formats system at the beginning so theres no need to do that with factory reset.
Now I can only think that the factory reset from bootloader does the same and system is not wiped. Theoretically it is correct...system is read only especially on a stock non rooted device and resetting it to factory practically means that any trace of personal settings/aps and so on should be erased. And those are not stored on the system partition. There is also no hidden place on the phone where a recovery image of the original android OS is kept so this is not like on the laptops where you reset to factory and Windows is reinstalled from the recovery partition. My guess is that the factory reset just wipes all partitions that contain personal data and settings and leave system intact. So after a wipe and reboot is like you first start it.
You still had CM11 cause the wipe didn't format system...If anyone has a better explanation I would be glad to hear it. So From my point of view nothing went wrong and has nothing to do with the Maximus recovery or it's compatibility with CM11. It would have happen the same if you have used any other stock recovery
Factory reset, resets youre phone to original settings.
Anyway, its good that the phone works.
null0seven said:
Factory reset, resets youre phone to original settings.
Anyway, its good that the phone works.
Click to expand...
Click to collapse
Yes. And it is not formatting system when doing this. So any os is installed will be kept
Sent from nowhere over the air...
Rapier said:
Yes. And it is not formatting system when doing this. So any os is installed will be kept
Sent from nowhere over the air...
Click to expand...
Click to collapse
I don't want to try it again but I wonder if moonshine's factory reset is incompatible with cm11?
Dont understand what do you mean by "incompatible". The factory reset from bootloader is not the same thing as the one from a custom recovery. You shouldn't do a factory reset from bootloader regardless of the ROM you're using
Moonshine is an S-Off method, I didn't used it myself so I don't know what factory reset option is in there
Sent from nowhere over the air...
I never said anything about the custom recovery. If you should never use it, why is it there and why does it make the SD card not available?
Wow, HTC says you can use it here:
http://www.htc.com/us/support/htc-one-x-att/howto/313779.html
I'm sure you know something others like me don't, but I when I mean "incompatible" I mean that I don't believe that it should make the sdcard unavailable and make the phone think it has zero MB. I think what you might have missed is that I used factory reset from the custom boot loader from moonshine. I was wondering if that factory reset was compatible - that's all.
Again, it was a mistake - it's not like I chose it on purpose. Thank you for the help.
808phone said:
I never said anything about the custom recovery. If you should never use it, why is it there and why does it make the SD card not available?
Wow, HTC says you can use it here:
http://www.htc.com/us/support/htc-one-x-att/howto/313779.html
I'm sure you know something others like me don't, but I when I mean "incompatible" I mean that I don't believe that it should make the sdcard unavailable and make the phone think it has zero MB. I think what you might have missed is that I used factory reset from the custom boot loader from moonshine. I was wondering if that factory reset was compatible - that's all.
Again, it was a mistake - it's not like I chose it on purpose. Thank you for the help.
Click to expand...
Click to collapse
The reset to factory from bootloader exists because on stock ROM there's no custom recovery that has that option....so it's in bootloader. For it to work properly though, you must have the stock recovery also. If you have a custom recovery like twrp/cwm and use the wipe from bootloader it'll mess your sd cause phone is not able to perform the wipe properly with that custom recovery. That's why, in order to get back to normal you should flash back stock recovery and perform the wipe from bootloader again.
Sent from nowhere over the air...
Thank you for the clarification. It makes sense. Too bad that reset is so close to the recovery command. It's pretty weird that I didn't have to run the wipe from the stock boot loader again. It ran and rebooted the phone into CM11. Anyway, I am glad I am back to running. Thanks.
I just got this phone and i have OEM Unlock enabled. I am due to sell my old phone in few days so i am in a bit panic mode right now :\
When i try to flash TWRP along with the instruction that were here (i tried with only applying both or only dm-verity) the phone started to "start" flashing the Samsung logo but nothing happened and after 15-25minutes i tried to install this ROM and it also shows "Starting up please wait" but it also seems to start up indefinately.
Can you tell what is wrong now? It seems i can flash the stock ROM and boot to it but cannot install TWRP/Root nor any custom ROM's :\
Hey bro follow this.
Install stock ROM.
Boot into it once.
And flash TWRP. Disable auto reboot in Odin.
Then boot into TWRP directly from there.
Now swipe to allow modifications.
THEN GO INTO WIPE ADVANCED WIPE AND CLICK FORMAT DATA AND TYPE YES.
After format reboot into recovery once again.
Now again swipe to allow mods.
Now only install Dm-verity.
Reboot.
Now the phone will boot.
Go back into recovery to install your ROM it'll root the phone.
njaya95 said:
Hey bro follow this.
Install stock ROM.
Boot into it once.
And flash TWRP. Disable auto reboot in Odin.
Then boot into TWRP directly from there.
Now swipe to allow modifications.
THEN GO INTO WIPE ADVANCED WIPE AND CLICK FORMAT DATA AND TYPE YES.
After format reboot into recovery once again.
Now again swipe to allow mods.
Now only install Dm-verity.
Reboot.
Now the phone will boot.
Go back into recovery to install your ROM it'll root the phone.
Click to expand...
Click to collapse
Sorry but still no dice (waited for ½hours to boot)
The data wipe did not even succeed. I attached screenshots of data wiping plus no-verity install if there is something anyone could use. I do not really understand how this is so hard... I have never encountered this kind of problem with common phone.
@DARKKi
Did You try to format data or just to wipe? You should click on format data and type "yes"
Dude I clearly mentioned, you have to click format data in advanced wipe. First try to read and understand then proceed. Click format data and then type yes and then you're good to go.
Domino5 said:
@DARKKi
Did You try to format data or just to wipe? You should click on format data and type "yes"
Click to expand...
Click to collapse
njaya95 said:
Dude I clearly mentioned, you have to click format data in advanced wipe. First try to read and understand then proceed. Click format data and then type yes and then you're good to go.
Click to expand...
Click to collapse
Damn. Sorry, i think that when going into advanced wipe there is no format there it's under normal wipe so i only thought that it meant that but yeah my mistake. I should have looked for format data and come to my own conclusions :\
Well first result of format resulted on loop boot and i could not even flash the stock rom with Odin (failed directly) but then i tried to flash TGP ROM via TWRP and it worked! So now i am using the phone as we speak!
Thanks a lot njaya95!
DARKKi said:
Damn. Sorry, i think that when going into advanced wipe there is no format there it's under normal wipe so i only thought that it meant that but yeah my mistake. I should have looked for format data and come to my own conclusions :\
Well first result of format resulted on loop boot and i could not even flash the stock rom with Odin (failed directly) but then i tried to flash TGP ROM via TWRP and it worked! So now i am using the phone as we speak!
Thanks a lot njaya95!
Click to expand...
Click to collapse
Sure no problem, I'm sorry about misleading you about that format data. Have fun with your phone.