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
Related
Got to the point in the How-to guide that says "Navigate to ‘wipe data/factory reset’ and select it.
Navigate to the ‘yes -- delete all user data’ and select it."
Trouble is I get "E: format volume: make_extf4fs failed on /dev/block/mmcblk0p2" and "Formatting /sdcard/ .android_secure..." and a non-functioning progress bar at the bottom.
Is this a battery pull, power off, reboot into recovery? Phone has been stuck like this for more than 30 minutes.
Edit:
Ok, after an hour I powered off and back on, seems like I have a brand new SK stock ROM again >.<
Another edit:
Tried again, same exact thing on wipe data/factory reset: "E: format volume: make_extf4fs failed on /dev/block/mmcblk0p2."
Do I need to flash the kernel like on this video? (https://www.youtube.com/watch?v=W33fcnWAgQg) If so, I'm not sure which kernel to use. I was hoping to flash to the JB ROM which says it contains Bali kernel.
This is no longer fun and all of my data is wiped. LOL even the Play Store is now Android Market like way back when and won't update!
kelltech said:
Got to the point in the How-to guide that says "Navigate to ‘wipe data/factory reset’ and select it.
Navigate to the ‘yes -- delete all user data’ and select it."
Trouble is I get "E: format volume: make_extf4fs failed on /dev/block/mmcblk0p2" and "Formatting /sdcard/ .android_secure..." and a non-functioning progress bar at the bottom.
Is this a battery pull, power off, reboot into recovery? Phone has been stuck like this for more than 30 minutes.
Edit:
Ok, after an hour I powered off and back on, seems like I have a brand new SK stock ROM again >.<
Another edit:
Tried again, same exact thing on wipe data/factory reset: "E: format volume: make_extf4fs failed on /dev/block/mmcblk0p2."
Do I need to flash the kernel like on this video? (https://www.youtube.com/watch?v=W33fcnWAgQg) If so, I'm not sure which kernel to use. I was hoping to flash to the JB ROM which says it contains Bali kernel.
This is no longer fun and all of my data is wiped. LOL even the Play Store is now Android Market like way back when and won't update!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1197533
Also, when flashing a custom ROM, use this CWM file in the root of your SD card (called update.zip)
shadowscott said:
http://forum.xda-developers.com/showthread.php?t=1197533
Also, when flashing a custom ROM, use this CWM file in the root of your SD card (called update.zip)
Click to expand...
Click to collapse
AWESOME. Thank you very much for the help, flashed and running neXus JB 1.3.2.
One more question if you don't mind:
* Do I need to flash the CWM you linked every time I want to flash a custom ROM, or once it's done that it?
kelltech said:
AWESOME. Thank you very much for the help, flashed and running neXus JB 1.3.2.
One more question if you don't mind:
* Do I need to flash the CWM you linked every time I want to flash a custom ROM, or once it's done that it?
Click to expand...
Click to collapse
Once you have CWM on your phone, you don't need to run the update.zip file every you want to flash a ROM. That's it unless you go back to stock via Odin or Heimdall.
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?
So I just went into recovery (buck's twrp) to flash me some aosp, it worked fine but I forgot to get a gps lock in sense before I flashed so I went into recovery to restore a nandroid and I got the dreaded "unable to mount /data, and unable to mount internal storage. Tried reflashing buck's twrp in fastboot and no dice. I have the RUU downloading although I would hate to have to go through that. Any recommendations? I;m going to try flashing philz recovery right now
wtoj34 said:
So I just went into recovery (buck's twrp) to flash me some aosp, it worked fine but I forgot to get a gps lock in sense before I flashed so I went into recovery to restore a nandroid and I got the dreaded "unable to mount /data, and unable to mount internal storage. Tried reflashing buck's twrp in fastboot and no dice. I have the RUU downloading although I would hate to have to go through that. Any recommendations? I;m going to try flashing philz recovery right now
Click to expand...
Click to collapse
Just plugged it into my pc to try to flash philz and a pop up came up saying that the file system is currupt. Ugh. I'm so p/o'd right now. Is RUU my only choice right now to repair this if any?
Just flashed RUU. Same thing. Going to dry formatting in windows device manager now
wtoj34 said:
So I just went into recovery (buck's twrp) to flash me some aosp, it worked fine but I forgot to get a gps lock in sense before I flashed so I went into recovery to restore a nandroid and I got the dreaded "unable to mount /data, and unable to mount internal storage. Tried reflashing buck's twrp in fastboot and no dice. I have the RUU downloading although I would hate to have to go through that. Any recommendations? I;m going to try flashing philz recovery right now
Click to expand...
Click to collapse
In TWRP go to Wipe < Format Data and do that and it should fix your /data problem. Before doing that I recommend just using the advanced wipe and ticking /data /cache /boot & /system and then re-trying. Also afterwards a good ROM to start with would be Cyanogenmod, I've had the least number of problems with that than any other, especially when helping people with issues like this. I actually had someone who's only way of fixing his issue was flashing that.... odd I know but that is why I always recommend it after having this issue.
Edit: just seen you've did an RUU and your problem is still persisting, I still recommend doing the 'Format Data' option in TWRP, this is known (at least to me) to fix most if not all problems with mounting...
S1L3nTShaDoWz said:
In TWRP go to Wipe < Format Data and do that and it should fix your /data problem. Before doing that I recommend just using the advanced wipe and ticking /data /cache /boot & /system and then re-trying. Also afterwards a good ROM to start with would be Cyanogenmod, I've had the least number of problems with that than any other, especially when helping people with issues like this. I actually had someone who's only way of fixing his issue was flashing that.... odd I know but that is why I always recommend it after having this issue.
Edit: just seen you've did an RUU and your problem is still persisting, I still recommend doing the 'Format Data' option in TWRP, this is known (at least to me) to fix most if not all problems with mounting...
Click to expand...
Click to collapse
Thanks a bunch dude, appreciate it. Restoring a nandroid now, had no issues with data yet. Phew. That was an exciting night
Yep its a stressful problem when it happens.
Sent from my One M8 using Xparent BlueTapatalk 2
no power button problem
without any reason the phone rebbot itself and stuck in boot loop animation....stock MMB29V Marshmallow , no root, only unlocked
tried:
-wipe cache and data
-reinstalling all singles images files
-reinstalling with flash all bat and finally it works...
what's the problem???
and now? there is something to check? have to change the phone???
tnx
Manually flash each partition again, including userdata.img partition. After flashing the last partition, boot directly to recovery using the power and volume keys (don't reboot the phone at all after flashing the last partition), perform a factory wipe, and reboot.
Ok but i need ti know if is possible to check the health device status
What do you mean by health? You mean each component?
I mean if is possible that something hardware is defective or going to be defective.
can I run some tests?
I know of no tests that are available to the public.
Ok
audit13 said:
Manually flash each partition again, including userdata.img partition. After flashing the last partition, boot directly to recovery using the power and volume keys (don't reboot the phone at all after flashing the last partition), perform a factory wipe, and reboot.
Click to expand...
Click to collapse
I have a similar problem with my N5, it was originally a power-button issue, and after some "whacking" the phone no longer "repeatedly reset" but now it just sits on the "Google" boot screen forever. Probably something got messed up during all the unintended reboots. I already went into recovery and did a factory reset, no luck. Tried flashing to older ROMs, no luck. Started hitting up forums, saw this post, tried your suggestion (flash each partition manually, did a "fastboot reboot-bootloader", enter recovery, wipe, and reboot), and still no luck.
I can get into fastboot/recovery, and even tried loading custom ROMs (CM13 to be exact). No matter what I tried, the phone will power-up, and stuck at the "Google" screen. Note that I've always waited at least an hour after flashing each version before I reboot from the "Google" screen.
I've read somewhere there is a "persist(?)" partition which will throw some error if corrupted, but it will require USB debugging enabled to fix. Unfortunately, I can't boot into any ROM to enable USB debugging...
Am I SOL or is there anything else I can try?
Thanks,
Wallace
WallaceLau said:
I have a similar problem with my N5, it was originally a power-button issue, and after some "whacking" the phone no longer "repeatedly reset" but now it just sits on the "Google" boot screen forever. Probably something got messed up during all the unintended reboots. I already went into recovery and did a factory reset, no luck. Tried flashing to older ROMs, no luck. Started hitting up forums, saw this post, tried your suggestion (flash each partition manually, did a "fastboot reboot-bootloader", enter recovery, wipe, and reboot), and still no luck.
I can get into fastboot/recovery, and even tried loading custom ROMs (CM13 to be exact). No matter what I tried, the phone will power-up, and stuck at the "Google" screen. Note that I've always waited at least an hour after flashing each version before I reboot from the "Google" screen.
I've read somewhere there is a "persist(?)" partition which will throw some error if corrupted, but it will require USB debugging enabled to fix. Unfortunately, I can't boot into any ROM to enable USB debugging...
Am I SOL or is there anything else I can try?
Thanks,
Wallace
Click to expand...
Click to collapse
Are you getting any errors when performing a factory wipe? Does the factory wipe happen very quickly? You flashed the userdata.img partition too?
audit13 said:
Are you getting any errors when performing a factory wipe? Does the factory wipe happen very quickly? You flashed the userdata.img partition too?
Click to expand...
Click to collapse
First time I did a wipe it took over an hour, then the phone rebooted to the dead android screen. So I tried to wipe again, and it seems like all subsequent wipe took anywhere between 3-5 minutes. No error on each wipe (can't say on the first one, since by the time I got back to the phone it has already rebooted). And yes, I did flashed everything - boot, cache, recovery, system, userdata, bootloader, radio - not exactly in that sequence, but all of those partitions are flashed with the image that comes with the Google download package. Then factory reset and reboot.
Thanks,
Wallace
Maybe try erasing cache and data using fastboot commands? If this doesn't work, it's possible that there is a hardware problem with the phone's internal memory.
audit13 said:
Maybe try erasing cache and data using fastboot commands? If this doesn't work, it's possible that there is a hardware problem with the phone's internal memory.
Click to expand...
Click to collapse
Did a "fastboot format cache" and "fastboot format userdata", no error. Still won't boot... are those the commands you are referring to?
Yup, or fastboot erase cache or fastboot erase data.
Sounds like the emmc may be messed up.
audit13 said:
Yup, or fastboot erase cache or fastboot erase data.
Sounds like the emmc may be messed up.
Click to expand...
Click to collapse
Tried all those, and yes same result... also, I flashed a different recovery (TWRP) and thereafter I can't even flash new ROMs anymore. ADB Sideload error our (forgot to write down the error message), and if I copy the file to internal storage and flash from there, TWRP will get stuck for hours.
How common are eMMC corruptions?
W.
The emmc problem is not that common, but it does happen. I'm not sure if it is partition or software corruption or a physical defect.
Other xda members have encountered emmc problems too that could only be fixed through a motherboard swap.
I am running into a situation emmc. the problem is I tried below action so far
1. Attempted to flash recovery partition which failed immediately after first reboot . it never got flashed correctly
2. Attempted to format all the partitions but I could format boot partition I could format no other partition it clearly says that can't mount
3. Then I tried to boot using fastboot command into recovery partition my command is
Fastboot boot recovery.img
I tried cwm I tried TWRP . only 2.6 dot x x worked in twrp. Cwm was not so helpful because it does not give me many features likewise TWRP
Once I boot in the recovery it asks for password if I click cancel it shows me all the interfaces but nothing works I don't have any local storage available it clearly fails to read it and everything shows is encrypted I don't know not sure what is going on there
When I attempt to format I get a error message as no partition available for this operation. No file system available
About phone but I think I am still searching for options but so far I could see that this is e MMC issue and there is no partitions available on this memory I am not able to format this internal memory I am new to the Linux environment and not sure what to do to format this internal emmc...
Can someone suggest any options to format and Re partition the emmc?
Sent from my AO5510 using Tapatalk
Sarvesh.huddedar said:
I am running into a situation emmc. the problem is I tried below action so far
1. Attempted to flash recovery partition which failed immediately after first reboot . it never got flashed correctly
2. Attempted to format all the partitions but I could format boot partition I could format no other partition it clearly says that can't mount
3. Then I tried to boot using fastboot command into recovery partition my command is
Fastboot boot recovery.img
I tried cwm I tried TWRP . only 2.6 dot x x worked in twrp. Cwm was not so helpful because it does not give me many features likewise TWRP
Once I boot in the recovery it asks for password if I click cancel it shows me all the interfaces but nothing works I don't have any local storage available it clearly fails to read it and everything shows is encrypted I don't know not sure what is going on there
When I attempt to format I get a error message as no partition available for this operation. No file system available
About phone but I think I am still searching for options but so far I could see that this is e MMC issue and there is no partitions available on this memory I am not able to format this internal memory I am new to the Linux environment and not sure what to do to format this internal emmc...
Can someone suggest any options to format and Re partition the emmc?
Sent from my AO5510 using Tapatalk
Click to expand...
Click to collapse
The password thing means your encrypted...Unencrypt and you can see all your storage..
Sent from my Nexus 6P using Tapatalk
---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------
My friend as a n5 that kerps bootlooping too..No roit but unlocked..Never rooted and has no clue how to root or mod a phone...It keeps bootlooping foe no resean 100% stock..It will only stop when i get it to go into bootloader mode and that takes a while...
Sent from my Nexus 6P using Tapatalk
The constant boot looping could be a power button problem?
kenbrownstone said:
The password thing means your encrypted...Unencrypt and you can see all your storage..
Sent from my Nexus 6P using Tapatalk
---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------
My friend as a n5 that kerps bootlooping too..No roit but unlocked..Never rooted and has no clue how to root or mod a phone...It keeps bootlooping foe no resean 100% stock..It will only stop when i get it to go into bootloader mode and that takes a while...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I dont think anyone has encrypted the phone ever.
Sent from my AO5510 using Tapatalk
Sarvesh.huddedar said:
I dont think anyone has encrypted the phone ever.
Sent from my AO5510 using Tapatalk
Click to expand...
Click to collapse
Maybe im mistaken but evertime i had to put in a password in ttwrp i had gotten encrypted...you get it fixed? My friends started bootlooping for no reason and wouldnt stop til the battery was dead.. Never seen a stock phone do that..
Sent from my Nexus 6P using Tapatalk
---------- Post added at 10:00 PM ---------- Previous post was at 09:59 PM ----------
Reasearch it.... It totally sounds like what happened to me...
Sent from my Nexus 6P using Tapatalk
I have flashed android 8.0 with odin then flashed twrp with odin (making sure to disable auto reboot) and rebooted straight into twrp. I then flashed dm verity disabler and now i was able to boot back into my os. The problem is i am now unable to mount my data partition. I have tried formatting my data and this works, but whenever i boot back into my os and set up android, tge problem comes back. Can anyone help with this?
Jack_Rickwood said:
I have flashed android 8.0 with odin then flashed twrp with odin (making sure to disable auto reboot) and rebooted straight into twrp. I then flashed dm verity disabler and now i was able to boot back into my os. The problem is i am now unable to mount my data partition. I have tried formatting my data and this works, but whenever i boot back into my os and set up android, tge problem comes back. Can anyone help with this?
Click to expand...
Click to collapse
i have the same thing, only difference is that i was stupid enough to wipe everything off my system including the system.
now it only boots to recovery and twrp
Now the fool seeks to return to the past and undo the future that is no phone
edit:
I found this it worked
watch?v=Rs4zcryNt5Y
SharinganSensei said:
i have the same thing, only difference is that i was stupid enough to wipe everything off my system including the system.
now it only boots to recovery and twrp
Now the fool seeks to return to the past and undo the future that is no phone
edit:
I found this it worked
watch?v=Rs4zcryNt5Y
Click to expand...
Click to collapse
Thanks, ill try it!
Jack_Rickwood said:
Thanks, ill try it!
Click to expand...
Click to collapse
This Worked for me too. It's a simple trick but it's working. Via TWRP, modify EXT4 to EXT2, then again to EXT4 ;-)
Thanks guys
I'm sure it will be useful to many who are going through the same issue
bebou said:
This Worked for me too. It's a simple trick but it's working. Via TWRP, modify EXT4 to EXT2, then again to EXT4 ;-)
Click to expand...
Click to collapse
It works only 1 time... and after you lose all data the error come back next boot...
I am planning to install a custom ROM on my S7 and now looking for a way to backup the /data/ partition, which is encrypted.
My preferred solution would be to create a full backup of the old system using twrp, but that doesn't seem to be feasible due to encryption. As the device is not rooted, I cannot pull /data over adb, remove encryption, then restore /data. Any ideas how to solve this?