Nexus 10 soft bricked, can't mount cache etc - Nexus 10 Q&A, Help & Troubleshooting

Hi everyone,
I've been scouring the forums for days and it's been really helpful but I just can't crack my problem.
My parent's Nexus 10 was having problems but due to the lockdown I couldn't go to help them out, my mum messed around and a factory reset went wrong.
At the moment, the tablet boots only as far as the Google logo. I can get into the bootloader, have unlocked it and tried flashing various stock Roms including the newest one (lmy49j) I'd get this message:
Erase successful, but not automatically formatting.
File system type raw not supported.
Boot up only as far as the Google logo still.
I tried using the flash-all.bat and manually line by line which seemed to give less errors but still no luck.
I've now been messing around with the Nexus Root toolkit v2.1.9 which allows me to boot into twrp and I can push files onto the sdcard. The problem is I can't mount the cache/data/storage so it still fails. I tried changing the file system to EX2 but it won't let me do that. They all show as 0mb. I can't wipe Data or Cache for the same reason, Davlik won't wipe either.
This link is my most promising lead left but I'm running out of ideas, I could be running a c:\Smash fist through tablet.bat command soon lol.
[HOWTO] [GUIDE] Repairing corrupted /data partition
I had an experience the other night that I found rather frightening and enlightening, and felt the need to contribute my learning. I attempted to install a new ROM on my Nexus 5 and encountered a freeze during the /system write process. I waited...
forum.xda-developers.com
Any help/ideas would be most appreciated,
Cheers

Did you ever fix this? I've the same problem.

I was able to get mine working again. One of the partitions had been corrupted. When in TWRP I looked under 'mounting' and the one that wouldn't mount was the problem. So I deleted then recreated that partition using the instructions and version of twrp found here.
[ROM][LineageOS][17.1][UNOFFICIAL][Nexus10]
LineageOS lineage-17.1-20230404-UNOFFICIAL-manta.zip Known issues: - Pls disable "Adaptive brightness" in display settings -> sensor service problems. - GPS is not working and has been disabled completely - NFC is not working and has been...
forum.xda-developers.com
While in parted, display sector values for partitions. Then when you delete that partition recreate it using the same values, reformat it as described in the same post above, and your device should be ready for an installation.
Hope this helps.
Melogibbo said:
Hi everyone,
I've been scouring the forums for days and it's been really helpful but I just can't crack my problem.
My parent's Nexus 10 was having problems but due to the lockdown I couldn't go to help them out, my mum messed around and a factory reset went wrong.
At the moment, the tablet boots only as far as the Google logo. I can get into the bootloader, have unlocked it and tried flashing various stock Roms including the newest one (lmy49j) I'd get this message:
Erase successful, but not automatically formatting.
File system type raw not supported.
Boot up only as far as the Google logo still.
I tried using the flash-all.bat and manually line by line which seemed to give less errors but still no luck.
I've now been messing around with the Nexus Root toolkit v2.1.9 which allows me to boot into twrp and I can push files onto the sdcard. The problem is I can't mount the cache/data/storage so it still fails. I tried changing the file system to EX2 but it won't let me do that. They all show as 0mb. I can't wipe Data or Cache for the same reason, Davlik won't wipe either.
This link is my most promising lead left but I'm running out of ideas, I could be running a c:\Smash fist through tablet.bat command soon lol.
[HOWTO] [GUIDE] Repairing corrupted /data partition
I had an experience the other night that I found rather frightening and enlightening, and felt the need to contribute my learning. I attempted to install a new ROM on my Nexus 5 and encountered a freeze during the /system write process. I waited...
forum.xda-developers.com
Any help/ideas would be most appreciated,
Cheers
Click to expand...
Click to collapse

GhostMachine7 said:
I was able to get mine working again. One of the partitions had been corrupted. When in TWRP I looked under 'mounting' and the one that wouldn't mount was the problem. So I deleted then recreated that partition using the instructions and version of twrp found here.
[ROM][LineageOS][17.1][UNOFFICIAL][Nexus10]
LineageOS lineage-17.1-20230404-UNOFFICIAL-manta.zip Known issues: - Pls disable "Adaptive brightness" in display settings -> sensor service problems. - GPS is not working and has been disabled completely - NFC is not working and has been...
forum.xda-developers.com
While in parted, display sector values for partitions. Then when you delete that partition recreate it using the same values, reformat it as described in the same post above, and your device should be ready for an installation.
Hope this helps.
Click to expand...
Click to collapse
Thanks man, I will give it a go!

Melogibbo said:
Thanks man, I will give it a go!
Click to expand...
Click to collapse
Do you have a stock PIT file for the manta available? I want to go back to stock but I repartitioned mine for a custom install and didn't get the PIT beforehand as I didn't expect to be going back. I like the newer version, but it's too slow for many uses. I know the stock image doesn't have security updates, but since I use it only on my LAN and sometimes for streaming sites, I don't see it being a big risk and it should be a lot more responsive.
Thanks

GhostMachine7 said:
Do you have a stock PIT file for the manta available? I want to go back to stock but I repartitioned mine for a custom install and didn't get the PIT beforehand as I didn't expect to be going back. I like the newer version, but it's too slow for many uses. I know the stock image doesn't have security updates, but since I use it only on my LAN and sometimes for streaming sites, I don't see it being a big risk and it should be a lot more responsive.
Thanks
Click to expand...
Click to collapse
Hey, no I don't sorry. I'm still having trouble even loading up the version of twrp mentioned in the thread let alone flashing a rom onto it. I can only get into twrp if I use the nexus root toolkit otherwise it just gives me errors relating to not being able to mount cache, very frustrating.
I can only look at it now and again as it sucks all my time up and pisses me off, I'll have another stab at it next week maybe.

Related

Removing encryption on Galaxy Tab

I encrypted my 10.1 yesterday without thinking all the way though. I found out that I could no longer flash kernels while the tablet is encrypted, since the SD card is not accessible in CWR.
I've tried doing a factory reset on my tab and each time, it boots up like nothing happened. I've also tried removing the pin that I put on it and the option to remove it is grayed out.
Do any of you know of a way to do a full wipe on the 10.1? Or could I reflash it using ODIN?
Thanks in advance.
id like to know this as well
still nothing? im starting to think this is an easy fix that nobody has posted about yet
there has to be something that im missing
try post # 6 in the linked thread, restore with unmodified vanilla version image from second link provided in the post, after booting from fastboot into recovery with clockworkmod recovery img; pushing it into the device sd with adb commandline, check the post for modifications and the link for details.
http://forum.xda-developers.com/showthread.php?t=1161325
whenever i try to reset to factory defaults, it just reboots like nothing happened
re-flash a stock firmware via odin as tar or fastboot/nandroid as img (backup restore)
Ones the tab is encrypted, there's no way to un do it. Unless you do what mughalgxt suggested. Good luck
Thanks guys, I went through some of these steps and found some other good tutorials to get me back up and running. All i wanted was to try the new kernel/bonsai rom out and I'm now able to do that
**** encryption, put a lockscreen password and be done with it.
I'm still struggling with this, as well: off to read some of the linked threads, because even with flashing a stock image with ODIN I'm still not able to recover the device. At least I managed to proceed past the boot loop I WAS in (when attempting to flash from CWM) - but now, I can get to the point where the device prompts me for the decryption key (meaning, it's clearly not yet restored to factory defaults) - but can't get it boot to completion. I also note that I've still got CWM Recovery, not stock.
It seems, at some point, encryption-key be damned, right? Meaning, if I don't care about recovering the contents of the encrypted partition - surely these low-level tools have the ability to simply format the partitions? Perhaps not - at least, not CWM - as attempts to format /data continue to fail.
Off to review the linked threads to try to gain some additional insight.
I ran into this same issue a long while back. As I recall (and it's been a while), you won't be able to wipe from CWM, but you can wipe from Settings / Privacy / Factory Data Reset. I could be wrong, but I know that I didn't have to do any adb pushing or anything with special images.
Hi SacTilt-
Thanks for the reply - and agreed: Had I actively started the effort from a functioning device, I think I could have selected that option.
As it turns out - I ran CWM, rebooted into recovery, and... next thing I knew, I was in boot loop hell.
I've tried flashing a variety of files via ODIN: Some at least allow the device to boot to the point where I get the initial password prompt - which I can provide, and proceed past... but then the device just 'goes blank'.
What I'm looking for is a 'start-from-scratch', no concern for data loss, delete the dang encrypted /data folder already, will ya?... approach.
As I've mentioned, a variety of ODIN files from a myriad of sources haven't seemed to quite do the trick. I feel like I'm missing something obvious - but can't find the right angle to spot it.
Perhaps fastboot might be what I'm looking for?
FWIW: the device was rooted when I started, so I've got full Titanium backups, with which I can restore, once I recover the actual device / OS.
Thanks for any insight.
Hey guys...if anybody finds a solution to this, please let me know...I am stuck with this same damn experimental ROM I've had from day one...it's getting really old. All I want is to get rid of this stupid encryption. Thanks for any help. Tried ODIN flashing, wiping data from security screen, wiping from CMR, etc.
Have you tried formatting the sd? Whenever i had my ns4g i accidentially did the same thing and i wiped the SD and it removed the encryption.
Sent from my GT-P7510 using XDA Premium HD app

[Q] Semi-brick internal memory issue

Hi everyone, sorry to post but I'm at wits end.
I've searched and googled all over for the past week and have found problems similar to mine but none of the fixes have worked.
If this has already been asked I apologise and will remove but here goes:
I rooted my phone and using the latest cwm flashed the rc1 of cm10, this didnt flash properly so I tried again, no joy.
I read around and decided to try with a different recovery, twrp.
So I tried flashing with that, again no joy. so i used twrp to do factory reset and cache wipes. As I was unfamiliar with the layout of twrp I'm under the impression I've deleted or wiped the cache/system and data partitions.
I've since flashed a PIT file to restore the original partitions, gone back to stock tried reflashing new roms. Its been a nightmare.
The issue itself is no recovery can mount the ext-sd which is actually the internal memory and cannot access the cache/log etc.
The phone itself shuts down randomly and then will not boot up.
Adb can't write or push anything to the device either, the strange thing is when the phones working for brief periods of time I can read and write to device memory?so at this point I'm flat out of ideas.
Any help/ideas or advice would be gratefully received, once again thanks guys
kingbob134 said:
Hi everyone, sorry to post but I'm at wits end.
I've searched and googled all over for the past week and have found problems similar to mine but none of the fixes have worked.
If this has already been asked I apologise and will remove but here goes:
I rooted my phone and using the latest cwm flashed the rc1 of cm10, this didnt flash properly so I tried again, no joy.
I read around and decided to try with a different recovery, twrp.
So I tried flashing with that, again no joy. so i used twrp to do factory reset and cache wipes. As I was unfamiliar with the layout of twrp I'm under the impression I've deleted or wiped the cache/system and data partitions.
I've since flashed a PIT file to restore the original partitions, gone back to stock tried reflashing new roms. Its been a nightmare.
The issue itself is no recovery can mount the ext-sd which is actually the internal memory and cannot access the cache/log etc.
The phone itself shuts down randomly and then will not boot up.
Adb can't write or push anything to the device either, the strange thing is when the phones working for brief periods of time I can read and write to device memory?so at this point I'm flat out of ideas.
Any help/ideas or advice would be gratefully received, once again thanks guys
Click to expand...
Click to collapse
Try and root your phone again with this http://forum.xda-developers.com/showthread.php?t=2219803
Thanks for the suggestion, this is the root file I've been flashing already
kingbob134 said:
The issue itself is no recovery can mount the ext-sd which is actually the internal memory and cannot access the cache/log etc.
Click to expand...
Click to collapse
Ext sd is your sdcard.Internal memory is the system and data.
The pit file was not needed after you formatted the system.Its only for repartition.
My suggestion is to format system flash stock rom do a factory reset then reboot.
Sent from my GT-I9500 using Tapatalk 4
Sorry thats my mistake, I can't mount ext-sd in recovery to format it and nothing can be acessed in cache or cache/logs, hence I thought it was an issue with the partitions. I've tried your suggestion but will try again.
Thankyou
kingbob134 said:
Sorry thats my mistake, I can't mount ext-sd in recovery to format it and nothing can be acessed in cache or cache/logs, hence I thought it was an issue with the partitions. I've tried your suggestion but will try again.
Thankyou
Click to expand...
Click to collapse
Is your phone booting fine ? I didn't understand your actual problem.I just checked the recovery.Sd-ext is the second partion for the sdcard./external sd is the sdcard.
If cache can't be mounted just format it.
Sent from my GT-I9500 using Tapatalk 4
Hi again. Cache can be mounted and formatted but recovery can't access cache/logs. My biggest issue is that the phone will randomly close when under stress and hit a bootloop that can only be cured by attaching the charger. The phone does boot I'm currently running pacman ROM. Tbh I'm fairly certain I wiped something important but flashing stock and even a pit file hasn't corrected it
kingbob134 said:
Hi again. Cache can be mounted and formatted but recovery can't access cache/logs. My biggest issue is that the phone will randomly close when under stress and hit a bootloop that can only be cured by attaching the charger. The phone does boot I'm currently running pacman ROM. Tbh I'm fairly certain I wiped something important but flashing stock and even a pit file hasn't corrected it
Click to expand...
Click to collapse
Weired.Did you try other recoveries ? Unfortunately I don't have any idea of what else you can do.
I've tried cwm, twrp and am currently running philztouch recovery as this seems to be the most stable on my phone, I can mount every directory but sd-ext and it also cant format that directory.
I installed AParted app to it this afternoon during a shortlived moment of clarity, phone not me, and tried fixing partitions/blocks. the only viewable were /dev/block/mmcblk0 and /dev/block/mmcblk1
the former, blk1 had 4 pieces of varying sizes but no registered file system whilst the latter was fat32. Could it be that the unacessable sd-ext is in the wrong file format? I've read for cwm and philz it needs to be ext4 but I may be mistaken.
also the crashing seems to occur when an app or process attempts to write to our unaccesable area and leaves me in a bootloop stating the battery is dead. So weird...
beginning to lose hope of solving this and fixing my buggy phone
Anyone with any ideas/experience please help, I'm willing to try almost anything at this point
thanks again guys
ext-sd?
Have no idea about this, but who cares
Many TWRP and CWM first releases break /data and /cache when you format them in recovery
Only known fix for is to flash a full STOCK rom (sammobile tar.md5) using odin + PIT (the right one, memory wise)
All my last recovery releases fully support all format options on S4
By the way, internal storage = sdcard = /data
Thanks for your quick reply Phil. I've flashed back to stock multiple times using a pit file and the sammobile firmware for my device. No joy unfortunately. And your recovery brings back an error when trying to mount or format sd-ext. I don't know what the issue could be but its crashing my phone near constantly
kingbob134 said:
Thanks for your quick reply Phil. I've flashed back to stock multiple times using a pit file and the sammobile firmware for my device. No joy unfortunately. And your recovery brings back an error when trying to mount or format sd-ext. I don't know what the issue could be but its crashing my phone near constantly
Click to expand...
Click to collapse
Hi,
try to fix it tru kies recovery.
Have you tried formating your Ext SD card in a PC? maybe its corrupt?
Also the boot loop you mentioned, only being fixed by attaching a charger sounds like a faulty battery. Is it swollen in the middle?
I would try new SD card and/or battery and see if that helps.
I've tried lies and no joy. The sd-ext is a partition in the internal memory not the external SD card, confusing I know. Battery appears fine. During my reading someone mentioned it may be inaccessible due to it being in the wrong format also that it could've corrupted blocks of memory and the crash occurs when the phone tries to access said block. Any thoughts?
kingbob134 said:
I've tried lies and no joy. The sd-ext is a partition in the internal memory not the external SD card, confusing I know. Battery appears fine. During my reading someone mentioned it may be inaccessible due to it being in the wrong format also that it could've corrupted blocks of memory and the crash occurs when the phone tries to access said block. Any thoughts?
Click to expand...
Click to collapse
Hhhhmmm have you tried running a e2fsck on the sd-ext block?
Sd-ext is the second partition of the SD card while /external-sd is the primary.If you don't have a second partition that's normal if it can't get mounted.
Sent from my GT-I9500 using Tapatalk 4
sd-ext is in external_sd
If that's only error you get, it is not an error, it is normal
Google for sd-ext
ijnegea jessie
Well that clears that issue but still leaves me with the crashes and bootloop.
When I try to flash a ROM via recovery it isn't 100percent successful and it then says it can't access cache and cache/recovery/log even though when the phone is running they are visible so I know they're there. This is driving me to despair now. Thanks for the input guys
kingbob134 said:
Well that clears that issue but still leaves me with the crashes and bootloop.
When I try to flash a ROM via recovery it isn't 100percent successful and it then says it can't access cache and cache/recovery/log even though when the phone is running they are visible so I know they're there. This is driving me to despair now. Thanks for the input guys
Click to expand...
Click to collapse
Did you try a factory reset with philz recovery ? Technically that should format cache and data with a compatible filesystem
Sent from my GT-I9500 using Tapatalk 4
Styrke said:
Did you try a factory reset with philz recovery ? Technically that should format cache and data with a compatible filesystem
Sent from my GT-I9500 using Tapatalk 4
Click to expand...
Click to collapse
Yeah I tried that. Still nothing

[Q] boot loop after updaing rooted 4.3 to 4.4

Hi
I record updating to 4.3 without removing root (I just lost it and the recovery asked if I wanted to redo it), so I decided to try the samething with 4.4. Well, things got very bad.
After I got the notification that 4.4 was available, I clicked to download it, the phone then rebooted and I installed it via the recovery.
Then Android booted and got stuck after Google's logo (balls moving) for more than 5 minutes, so I decided something was wrong and shut it down.
So far I tried going to adb shell and mounting sdcard (so I could make a backup), but apparently fstab had /sdcard datamedia /dev/null (huh?)
Then I tried to adb sideload 4.3 and 4.4 (from https://developers.google.com/android/nexus/images ), and both failed for different reasons (4.3 just said "(bad)", 4.4 said something with "set_meta_recursive").
Then I did a "fastboot oem unlock" (please don't tell me this lose all the data - including sdcard) and retried that. Also didn't work.
(I cleaned cache before trying)
Then I found some tutorials telling to "fastboot flash bootloader/radio/...", but those versions (4.3 and 4.4) from the site above doesn't have files named "bootloader-mako-makoz20i.img" or so. I could find it for 4.2 (makoz10), so I tried with that and it apparently worked. Except also got on boot loop (different logo).
Then I downloaded an image that was on a link for 4.3 that had makoz20, so I tried with that and got the same result (it worked, but got on boot loop).
Now even recovery isn't working anymore.
I was careful to not run "fastboot -w" (or flash-all.sh) and/or to delete userdata.img from the .zip, so I have some hope I didn't lose all data.
Any hints on how to proceed from here?
thanks!
Lem0nHead said:
Hi
I record updating to 4.3 without removing root (I just lost it and the recovery asked if I wanted to redo it), so I decided to try the samething with 4.4. Well, things got very bad.
After I got the notification that 4.4 was available, I clicked to download it, the phone then rebooted and I installed it via the recovery.
Then Android booted and got stuck after Google's logo (balls moving) for more than 5 minutes, so I decided something was wrong and shut it down.
So far I tried going to adb shell and mounting sdcard (so I could make a backup), but apparently fstab had /sdcard datamedia /dev/null (huh?)
Then I tried to adb sideload 4.3 and 4.4 (from https://developers.google.com/android/nexus/images ), and both failed for different reasons (4.3 just said "(bad)", 4.4 said something with "set_meta_recursive").
Then I did a "fastboot oem unlock" (please don't tell me this lose all the data - including sdcard) and retried that. Also didn't work.
(I cleaned cache before trying)
Then I found some tutorials telling to "fastboot flash bootloader/radio/...", but those versions (4.3 and 4.4) from the site above doesn't have files named "bootloader-mako-makoz20i.img" or so. I could find it for 4.2 (makoz10), so I tried with that and it apparently worked. Except also got on boot loop (different logo).
Then I downloaded an image that was on a link for 4.3 that had makoz20, so I tried with that and got the same result (it worked, but got on boot loop).
Now even recovery isn't working anymore.
I was careful to not run "fastboot -w" (or flash-all.sh) and/or to delete userdata.img from the .zip, so I have some hope I didn't lose all data.
Any hints on how to proceed from here?
thanks!
Click to expand...
Click to collapse
You may have missed this.. http://www.xda-developers.com/android/how-to-fix-a-broken-rom-flash-in-certain-kitkat-roms/
ravindrank said:
You may have missed this.. http://www.xda-developers.com/android/how-to-fix-a-broken-rom-flash-in-certain-kitkat-roms/
Click to expand...
Click to collapse
I am facing the same problem. The bootloader is stuck in a loop. Is there any way to recover the stock android??
true! It's interesting how google doesn't show results if you put it on quotes ("set_metadata_recursive: some changes failed")
gonna try that, thanks!
hm, well
I tried flashing using fastboot now (following method D on http://forum.xda-developers.com/showthread.php?t=2010312 ), so I guess set_metadata_recursive or something like that doesn't matter
it flashed correctly, but it still doesn't work (now I get stuck in black screen after google's logo)
oops, sorry. not black screen (I forgot to flash system), not it's stuck on the 4 balls animation, as it was right after the update ;(
you did a factory reset prior to booting and after flashing?
playya said:
you did a factory reset prior to booting and after flashing?
Click to expand...
Click to collapse
no, I'm trying to avoid losing data
since nexus 4 sdcard isn't removable (and now I'm regretting have accepted that), is there anyway to save my data?
as I said, I tried mounting it, but for some reason /sdcard is pointing to /dev/null no fstab.
Now I already flashed the stock recovery, so maybe I need to flash something else to try that again, but is there anything I can do differently?
thanks
Lem0nHead said:
no, I'm trying to avoid losing data
since nexus 4 sdcard isn't removable (and now I'm regretting have accepted that), is there anyway to save my data?
as I said, I tried mounting it, but for some reason /sdcard is pointing to /dev/null no fstab.
Now I already flashed the stock recovery, so maybe I need to flash something else to try that again, but is there anything I can do differently?
thanks
Click to expand...
Click to collapse
stock recovery wipe data and may I ask you what do you think you are going to lose? You are only going to lose apps and app data not photos or files which honestly you should have a free dropbox and save everything on there for the reason mentioned before... NO SDCARD
hm, maybe it's related with encryption I'd set from Security? I know the password, but it doesn't ask me for it anywhere
Lem0nHead said:
hm, maybe it's related with encryption I'd set from Security? I know the password, but it doesn't ask me for it anywhere
Click to expand...
Click to collapse
man just do a wipe...
playya said:
man just do a wipe...
Click to expand...
Click to collapse
I think currently I'm more worried with not losing data than with getting my phone back working.
Sorry, but I find it ridiculous that it isn't easy to extract data from your phone easily. Even if it's encrypted, as long as I know the password there should be a tool to help with that.
Apparently there might be something like "recovery --set_encrypted_filesystem=off" (on adb shell), but I'm getting "sh: /sbin/postrecoveryboot.sh: not found", so no luck yet
Lem0nHead said:
I think currently I'm more worried with not losing data than with getting my phone back working.
Sorry, but I find it ridiculous that it isn't easy to extract data from your phone easily. Even if it's encrypted, as long as I know the password there should be a tool to help with that.
Apparently there might be something like "recovery --set_encrypted_filesystem=off" (on adb shell), but I'm getting "sh: /sbin/postrecoveryboot.sh: not found", so no luck yet
Click to expand...
Click to collapse
what data are you trying to save?
playya said:
what data are you trying to save?
Click to expand...
Click to collapse
encrypted files on /sdcard
Lem0nHead said:
encrypted files on /sdcard
Click to expand...
Click to collapse
wipe/data factory reset from custom recovery has nothing to do with sdcard based files. Its only going to delete any files in your data portion of your rom and not your sdcard. area... two completely different things, have you done your research on android and how everything works. Its good to search and read up on this stuff especially since its interesting and you apparently need a few answers to your questions
playya said:
factory reset has nothing to do with sdcard based files. Its only going to delete any files in your data portion of your rom and not your sdcard area
Click to expand...
Click to collapse
are you sure this stands for nexus 4, which have just an internal sdcard?
Lem0nHead said:
are you sure this stands for nexus 4, which have just an internal sdcard?
Click to expand...
Click to collapse
come on man this aint my first rodeo and do you think every time you did a factory reset it was going to delete your music? Do some research my man there are multiple wipes and an Internal SD Card wipe will delete everything but a factory reset with a custom recovery or factory will only reset your settings to factory
playya said:
Its good to search and read up on this stuff especially since its interesting and you apparently need a few answers to your questions
Click to expand...
Click to collapse
well, as I said before, I was following http://forum.xda-developers.com/showthread.php?t=2010312
it says "this command will wipe your device (including /sdcard)"
maybe this isn't true, but I guess it's a trusted thread
Lem0nHead said:
well, as I said before, I was following http://forum.xda-developers.com/showthread.php?t=2010312
it says "this command will wipe your device (including /sdcard)"
maybe this isn't true, but I guess it's a trusted thread
Click to expand...
Click to collapse
hold on let me take a look now that might be a different procedure I am referring to a wipe from recovery but in your case a full wipe may be necessary
hm, I didn't try any kind of wipe
so which one is safe (so I can try at least)? "wipe data / factory reset" from recovery?

[Q] Freezing, rebooting, and can't flash stock rom (reverts to previous state)

Okay, so I feel like I've looked everywhere and tried everything for this problem with my Nexus 7. The closest thing I found was this:
(Google: Nexus 7 2012 rebooting reverts back to previous state)(I can't post outside links as I am a new member)
and there was no followup reply, and the thread was closed.
Here's my problem (I want to be very detailed in case I missed something):
I've had Cyanogenmod 11 on my Nexus 7 for a long time (I think I started with M1 release). I recently installed the M7 release after previous nightly and it was working so smooth that I had finally decided there was no need to install nighties anymore. Everything was going fine until the night after when I noticed it kept rebooting, so I reverted it back to the nightly I had before (June 11th?) because I assumed it was probably something bad with the update. Except it did the same thing, rebooting after a couple minutes, which is weird because it never did that with this nightly. There was never enough time to download the nightlies before it reboots so I tried downloading them on my laptop and then just transferring them to my nexus via usb. I put it in the cmupdate folder so that I could quickly go to settings and press install (as it can see the update from there). It rebooted to install, but it went into cwm with what appears that nothing happened, and I usually never see cwm when updating this way. So I figured, while I'm here, I could just "install zip" and find that zip I just transferred and install, right? Nope. The zip mysteriously vanished, yet the other two updates were still there (M7 and the previous nightly). So I just rebooted just to try the process again, maybe the file transfer didn't work. Same thing happened. So I went to cwm and tried wiping cache, nothing. Wiped dalvik cache, nothing. So I went and did it, wiped data/factory reset, that did NOTHING, as in I rebooted and everything was still there.
So I got to the point where I just wanted to see if I could just revert back to stock so I have a place to start from, maybe contemplate on just staying there for a while where there shouldn't be problems. So I got that all set up with fastboot, got the latest 4.4.3 image, unarchived until I could get to the flashall.bat I ran that and it was successful. Okay now I can just boot into that, right? Suddenly I see the cyanogenmod boot graphic. What happened? Even all of my apps are still there. Still freezing and rebooting.
I tried reverting to stock manually by erasing then formating everything that I can, flashed bootloader (grouper 4.23), flashed zip, locked bootloader, unlocked bootloader (trying to erase as much as I can). This did nothing, still cyanogenmod. I tried a third time while rebooting to bootloader with each step. Nothing. I tried doing a factory reset within cyanogenmod, but when I press the "erase everything" button it doesn't lead anywhere, so I could never get that to start the process. I also tried doing the erasing and formatting from cwm (which isn't being overwritten, as it seems, by all the attempts at flashing stock?), nothing.
I was curious. I uninstalled Netflix because it was right there in my dock. Then I rebooted myself. When it came back up, Netflix was still there. I tried various things, also going back to locking the bootloader and rebooting the bootloader, it still said it was unlocked. So I came to the conclusion that literally nothing was being written or committed to the sdcard no matter what I do.
I did some more research and found that article up top. So I tried uninstalling some apps because it said it may have something to do with a third-party app misbehaving (seems a bit extreme, I'll do it anyways), but there's never enough time to erase everything before it reboots. It also said to try to get it into safemode. I think I might have gotten there once but it still rebooted (which makes me think that it didn't get to safemode), the rest of the times it wouldn't even get to the lockscreen.
What I'm currently attempting is to see if I can get it into safemode, or I'm trying to uninstall or stop/clear data for every single app with an intentional reboot each time.
Anyone got any idea what's going on? Is it maybe a bad sector, or worse, bad sdcard?
Gonna bump this. Still no luck on my part.
Anyone have any idea?
Perhaps somehow something got triggered to prevent anything being written to the sdcard? (Kinda like the lock switch on actual sdcards?) Is everything I've been doing going straight to memory since everything reverts back after a reboot? That's the only explanation I can think of.
Perhaps there's more I could try. I'm only moderately knowledgeable with things like fastboot and roms, so maybe someone with more experience might have more insight. Please, chime in.
Thanks in advance,
JM
Same problem here....
Flash factory image
USBhost said:
Flash factory image
Click to expand...
Click to collapse
Although you flash the factory image, the previously ROM boots again, that is precisely the problem.
Amd64bits said:
Although you flash the factory image, the previously ROM boots again, that is precisely the problem.
Click to expand...
Click to collapse
O ok
Amd64bits said:
Same problem here....
Click to expand...
Click to collapse
Curious, how did you get to the point where it boots the previous rom? Same as me or something else? Are you using cyanogenmod? I want to try and rule out some possibilities.
I'm at the same point since last time. Trying to nuke the hell out of cyanogenmod but it won't go away!
This just outright baffles me!
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
USBhost said:
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
Click to expand...
Click to collapse
I have clockworkmod recovery v6.0.4.3 probably from installing cyanogenmod, however formating any of those partitions does literally nothing. I'm not sure what file system it formats it to, but the process seemed too quick for a full format.
I cannot flash a different recovery because... well... it doesn't remember me flashing a recovery (even when nothing "fails" when flashing). So I'm stuck with whatever is already on my internal storage. Nothing is writing to the sdcard, and nothing is being deleted.
violoncellemuse said:
I have clockworkmod recovery v6.0.4.3 probably from installing cyanogenmod, however formating any of those partitions does literally nothing. I'm not sure what file system it formats it to, but the process seemed too quick for a full format.
I cannot flash a different recovery because... well... it doesn't remember me flashing a recovery (even when nothing "fails" when flashing). So I'm stuck with whatever is already on my internal storage. Nothing is writing to the sdcard, and nothing is being deleted.
Click to expand...
Click to collapse
Boot twrp temporary from the bootloader
USBhost said:
Boot twrp temporary from the bootloader
Click to expand...
Click to collapse
I'm unfamiliar with this, how do I boot temporarily?
violoncellemuse said:
I'm unfamiliar with this, how do I boot temporarily?
Click to expand...
Click to collapse
1 set getting on computer
Okay, so I was able to boot twrp and change the partitions to f2fs. No dice. Still cyanogenmod.
violoncellemuse said:
Okay, so I was able to boot twrp and change the partitions to f2fs. No dice. Still cyanogenmod.
Click to expand...
Click to collapse
then you did boot twrp temporary
USBhost said:
then you did boot twrp temporary
Click to expand...
Click to collapse
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
violoncellemuse said:
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
Click to expand...
Click to collapse
thats not normal
ok i know why its a new cyanogenmod feature
no matter what you do cyanogenmod is now unkillable lol
this is such a strage problem
USBhost said:
thats not normal
ok i know why its a new cyanogenmod feature
no matter what you do cyanogenmod is now unkillable lol
this is such a strage problem
Click to expand...
Click to collapse
Do you have any more info? Perhaps my sdcard is "softlocked" or something.
violoncellemuse said:
Do you have any more info? Perhaps my sdcard is "softlocked" or something.
Click to expand...
Click to collapse
i have been noticing CWMR is the root of all the problems
i dont sorry but your not the only one i think there are 3+ people that have this same problem
formating should have fixed it
USBhost said:
i have been noticing CWMR is the root of all the problems
i dont sorry but your not the only one i think there are 3+ people that have this same problem
formating should have fixed it
Click to expand...
Click to collapse
I do thank you for trying to help me out.
I found a thread with someone with the same problem I'd like to direct people towards: http://forum.xda-developers.com/showthread.php?t=2800064
violoncellemuse said:
Curious, how did you get to the point where it boots the previous rom? Same as me or something else? Are you using cyanogenmod? I want to try and rule out some possibilities.
I'm at the same point since last time. Trying to nuke the hell out of cyanogenmod but it won't go away!
This just outright baffles me!
Click to expand...
Click to collapse
Well, I have Paranaoid Android 4.4.4, not Cyanogen, and everything seemed ok until I installed Cloudmagic (and maybe Busybox?) that poped up a Play Store error (I don't remember which one), and suddenly all the problems began. It started to reboots, rebooted so many times that I decided to flash another ROM... but this wasn't possible.
My recovery is TWRP, so we can discard Cyanogen, ParanoidAndroid, CMW and TWRP as guilty, I think.
USBhost said:
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
Click to expand...
Click to collapse
Tried that, nothing happened, still with Paranoid Android.
violoncellemuse said:
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
Click to expand...
Click to collapse
Same here.

HELP!! I am stuck inside of TWRP and cannot boot into the system

Hey everyone, I have a really frustrating problem, I am currently able to boot into TWRP via hardware method and ADB can see my device as well. However I have tried to install a stock system image through TWRP and I have also tried to install another TWRP backup that a user had posted in the Q&A forum. At one time I was able to successfully boot into the system but my device said encryption unsuccessful. After wiping the system partition and trying to install these images through TWRP I am still unable to boot into the system. Whenever I install them my phone will reboot into TWRP. I am at a loss as to what to do. If anyone has any ideas or suggestions I would appreciate it.
crazyc78 said:
Hey everyone, I have a really frustrating problem, I am currently able to boot into TWRP via hardware method and ADB can see my device as well. However I have tried to install a stock system image through TWRP and I have also tried to install another TWRP backup that a user had posted in the Q&A forum. At one time I was able to successfully boot into the system but my device said encryption unsuccessful. After wiping the system partition and trying to install these images through TWRP I am still unable to boot into the system. Whenever I install them my phone will reboot into TWRP. I am at a loss as to what to do. If anyone has any ideas or suggestions I would appreciate it.
Click to expand...
Click to collapse
I saw your other post in the other thread, but couldn't reply for some reason.. did you wipe the internal storage before restore?
Yes I did wipe the internal storage, I actually wiped everything the first time I tried to get everything in order and that was my original problem by wiping the system. I didn't realize that wiping internal storage would cause issues but that could have been one of the culprits. I think what finally solved my issue is I installed a deodexed rom and then powered down my device instead of rebooting and it booted up the rom. I had to flash SuperSU from a zip because for some reason the one that was preinstalled with that rom didn't install properly. So I installed the SuperSU zip and I am now officially rooted. Lesson learned DON'T WIPE SYSTEM OR INTERNAL STORAGE lol. I should have known better I have been rooting for awhile now, I just wasn't paying attention it happens to the best of us sometimes. Thanks for your help.
crazyc78 said:
Yes I did wipe the internal storage, I actually wiped everything the first time I tried to get everything in order and that was my original problem by wiping the system. I didn't realize that wiping internal storage would cause issues but that could have been one of the culprits. I think what finally solved my issue is I installed a deodexed rom and then powered down my device instead of rebooting and it booted up the rom. I had to flash SuperSU from a zip because for some reason the one that was preinstalled with that rom didn't install properly. So I installed the SuperSU zip and I am now officially rooted. Lesson learned DON'T WIPE SYSTEM OR INTERNAL STORAGE lol. I should have known better I have been rooting for awhile now, I just wasn't paying attention it happens to the best of us sometimes. Thanks for your help.
Click to expand...
Click to collapse
I've been rooting for a while myself but messed up I'm stuck in twrp and don't know how to get it the phone back on! your help would be glady appreciated .
ricosuave88 said:
I've been rooting for a while myself but messed up I'm stuck in twrp and don't know how to get it the phone back on! your help would be glady appreciated .
Click to expand...
Click to collapse
I used the deodexed ROM that is in the development forum. If I can upload it here I will if not just download it put it on your SD card and flash it. It may take a couple tries though I would suggest powering down your phone instead of rebooting it. Then turn it on and it should boot into the new rom. It's basically the same stock rom that our phone comes with. You may have to flash Chainfires SUPERSU zip that's in one of the threads. These steps should get you up and running again. Also if you can see your internal storage you're not encrypted. Hopefully that works for you. Let me know how it goes.
I wasnt able to upload the file from my phone. Just download it from here.
http://forum.xda-developers.com/v20/development/h918-stock-deodex-debloat-t3499423/page5
crazyc78 said:
I wasnt able to upload the file from my phone. Just download it from here.
http://forum.xda-developers.com/v20/development/h918-stock-deodex-debloat-t3499423/page5
Click to expand...
Click to collapse
Thanks for responding back. Man I'm still stuck in twrp I'm losing all hope at this point been at all day and can't figure out what Im doing wrong . I know you was stuck in the same situation did flashing that twrp back up help you out?
ricosuave88 said:
Thanks for responding back. Man I'm still stuck in twrp I'm losing all hope at this point been at all day and can't figure out what Im doing wrong . I know you was stuck in the same situation did flashing that twrp back up help you out?
Click to expand...
Click to collapse
Flashing the rom helped me out. It's a system image file. It's basically the stock rom for our device just deodexed. What exactly happened what did you wipe after your phone booted into
TWRP? If you still have TWRP you're not bricked. If you can flash that image from the thread I copied above then you should be good. You may have to flash SUPERSU to get root back. Also after you flash make sure you're not encrypted if you can see your internal storage partition then you're not encrypted.
crazyc78 said:
Flashing the rom helped me out. It's a system image file. It's basically the stock rom for our device just deodexed. What exactly happened what did you wipe after your phone booted into
TWRP? If you still have TWRP you're not bricked. If you can flash that image from the thread I copied above then you should be good. You may have to flash SUPERSU to get root back. Also after you flash make sure you're not encrypted if you can see your internal storage partition then you're not encrypted.
Click to expand...
Click to collapse
when I flashed the rom from your link above it just booted me into twrp again . I don't know what exactly I'm suppose to wipe. I can see internal storage tho so I guess that's a good sign but what's not good is that I can't use my phone :/ I've been rooting for years and can't seem to figure this one out.
ricosuave88 said:
when I flashed the rom from your link above it just booted me into twrp again . I don't know what exactly I'm suppose to wipe. I can see internal storage tho so I guess that's a good sign but what's not good is that I can't use my phone :/ I've been rooting for years and can't seem to figure this one out.
Click to expand...
Click to collapse
When you flashed the rom did you power the phone down and then try to boot into the rom? That's what I did and it worked for me. So don't select reboot into system, I'm not sure why it doesn't work that way. I had to power my device down and then boot into the room. Also if you can see your internal partition in TWRP then you should be good and encryption is not enabled. I know how frustrating this is. Just keep trying eventually that rom should stick.
crazyc78 said:
When you flashed the rom did you power the phone down and then try to boot into the rom? That's what I did and it worked for me. So don't select reboot into system, I'm not sure why it doesn't work that way. I had to power my device down and then boot into the room. Also if you can see your internal partition in TWRP then you should be good and encryption is not enabled. I know how frustrating this is. Just keep trying eventually that rom should stick.
Click to expand...
Click to collapse
Man, I have tried everything as well and I can't seem to get pass TWRP. Has anyone found a way around this problem? I have been looking around for an answer for 2 days and nothing has worked so far, any help will be greatly appriciated.
Thank you
kaiser10 said:
Man, I have tried everything as well and I can't seem to get pass TWRP. Has anyone found a way around this problem? I have been looking around for an answer for 2 days and nothing has worked so far, any help will be greatly appriciated.
Thank you
Click to expand...
Click to collapse
There a stock rom that I posted a link to a few posts back when I trying to help someone else. Download it put it on your SD card and install it. You don't need to wipe anything it will format things for you. After it installs don't reboot, power down the device and then turn it back on it should boot into the rom. That's what worked for me. I believe there was another way then what I just described it's in the same thread that I linked a few posts back. Good luck!!
crazyc78 said:
There a stock rom that I posted a link to a few posts back when I trying to help someone else. Download it put it on your SD card and install it. You don't need to wipe anything it will format things for you. After it installs don't reboot, power down the device and then turn it back on it should boot into the rom. That's what worked for me. I believe there was another way then what I just described it's in the same thread that I linked a few posts back. Good luck!!
Click to expand...
Click to collapse
Thanks for the help brother. However, it did not work for me. I flash the stock system, boot, turn device off and turn back on but I am still stock on TWRP. I will continue reading and hopefully I will find the answer soon.
thank you,:crying:
kaiser10 said:
Thanks for the help brother. However, it did not work for me. I flash the stock system, boot, turn device off and turn back on but I am still stock on TWRP. I will continue reading and hopefully I will find the answer soon.
thank you,:crying:
Click to expand...
Click to collapse
Np don't give up, I almost lost hope and then it worked for me.
Like I said there was another method that was discussed that worked for someone else. Try this thread, I know someone had the same issue that you and I had and they finally got it working.
http://forum.xda-developers.com/v20/development/h918-stock-deodex-debloat-t3499423
I'm here to the rescue! Follow this to the T! It worked for me! Let me know. http://forum.xda-developers.com/showthread.php?p=69685809
Sent by using the battery of my LG V20
im on the same boat as you. I am stuck in TWRP
tried all the methods i found so far and still stuck in twrp. i would greatly appreciate if someone can get me out of this bootloop!
hslayer said:
tried all the methods i found so far and still stuck in twrp. i would greatly appreciate if someone can get me out of this bootloop!
Click to expand...
Click to collapse
Same. Though I am on US996. Not sure what I did, was exploring some behind the scenes stuff using 'hidden codes' but didn't change any values as I didn't know what they meant in most cases. I rebooted my phone and it went straight to TWRP (3.0.2-1) and it will not boot past TWRP. Occasionally after I've flashed something, it will boot into TWRP and the screen will be unresponsive to touch so I have to pull the battery, but then it will be fine again.
I was in your position not to long ago, I'm currently working on getting a .kdz recovery file for the H918. My progress will continue on it later when finals are over.
netgar post 134
Restore H918 to 100% Stock (!!REQUIRES TWRP!!)

Categories

Resources