Database Info

[Q] TF101 Installing Custom ROM on Encrypted device

I recently managed to successfully root my TF101.
I installed CWM (Via ROM Manager) and downloaded CM9
I boot into CWM and attempt to do a nandroid...can't find path.
I attempt to just install from SDCard...can't find path
Realization (and research) hits that CWM can't see the external sd, and the system doesn't see it as SDCARD but EXT-.
CWM can't see the internal SDCard because apparently on the Tablet the ICS encryption locks that down (but doesn't on my EVO since the SC Card isn't part of the internal storage)
I attempt to perform a factory data wipe to clear out the encrtyption , but upon reboot CWM loads. I try to perform the boot-launcher data wipe, but then CWM loads.
I try to use CWM to factory reset but since it can see the damned SDCard because of the encryption, no dice.
My machine is not bricked, as I can still boot into the previous install but I can't seem unable to format the thing to install CM9.
What to do, and thanks.

It has been said multiple times before DO NOT USE ROM MANAGER.
Either use Thing O Doom's peri to install a different CWM or Gnufabio's Recovery installer or NVFlash a rom to completely wipe. And don't use encryption there is no point 99% of the time

I didn't check here first, which is obviously what was my first mistake.
Will any of those recoveries be able to access and format the SD Card area?
Also, I use encryption as I do have sensitive things on my machine that I don't want exposed in case the machine is stolen. First time I've ever had it give me a problem, as the phone encrypts differently.

Team roug's recovery has internal and external sd support and i think the encryption is an ics/tegra 2 bug more than anything

Ok, so I managed to get the new recovery on via Thing O Doom's peri. And I was able to install Revolver via the ext card...but upon boot I was prompted for my encryption pin and got the message that android was updating...My Build number is now Revolver but everything is the same as it was. I still can't factory wipe this damned thing.
Upon request to wipe, it boots back to recovery and says formatting data and cache, data wipe failed.
Tis site states http ://0xfeedface.org/blog/lattera/2012-06-04/installing-cm9-encrypted- android-tablet
The dilemma
When you encrypt your Android device, the /data partition is what gets encrypted. The partition in full is encrypted and cannot be mounted within CWM. CWM also cannot perform a wipe, since it cannot mount the /data partition. And CWM cannot mount the external SD card. This is our dilemma. No access to the internal SD. No access to the external SD. No way to perform a wipe and format the internal SD from CWM.
The Solution
What we need to do, then, is use adb while the tablet is in recovery mode to reformat the internal SD card, thereby removing the encryption. On the US Transformer Prime, the internal SD card is at /dev/block/mmcblk0p8. The partition for our spare SD card will be at /dev/block/mmcblk1p1. You will need to replace those device entries for any other device you might attempt this on. After formatting the internal SD card, we will mount it and then mount the external SD card at /data/media:
In CWM, wipe cache
adb shell
mke2fs -t ext4 /dev/block/mmcblk0p8 # Warning: This can take a while. Be patient.
mount /data
mount /dev/block/mmcblk1p1 /data/media
Now go back to CWM on your device, then go ahead and flash your CM9 and gapps zips like normal. You now have CM9 installed! The /data partition is not encrypted. If you do not need to flash any other ROMs (unlikely if you're reading this article), feel free to re-encrypt your device.
Click to expand...
Click to collapse
I don't know the block numbers for the TF01

you need to undo the encryption before you can wipe anything

You can't. Hence my problem. I cannot mount,delete, or format the SDCard. It sounds like the process in the above post is the solution, but I don't know how to find out what block numbers the tf101 uses.

If you don't mine losing your data NVflashing a rom will resolve all the problems

Yep nvflash will do the trick otherwise as the solution you found yourself explains
Use adb in recovery ( in other words hook it up on a pc ) for this you will need android sdk runnin on your pc
More info about adb u can find here
http://forum.xda-developers.com/showthread.php?t=1751439&highlight=adb+help
Good luck

Thanks to all, I have resolved my issue!
I had to download the stock rom, extract the blob, and use Wheelie for PC to NVFlash everthing abck to stock. I was then able to update over OTA, and use the excellent Thing O Doom's peri to re-root and flash the working recovery.
There should be several items in the Root FAQ up top, such as:
If you are encrypted and going to root, factory reset to get rid of the encryption FIRST since the encryption locks down the SDCARD partition (Unlike on the phone)and none of the recoveries can access it to mount. DON"T use ROM manage on the TF101 and always, always check XDA first.
:good:

darthrater said:
Thanks to all, I have resolved my issue!
I had to download the stock rom, extract the blob, and use Wheelie for PC to NVFlash everthing abck to stock. I was then able to update over OTA, and use the excellent Thing O Doom's peri to re-root and flash the working recovery.
There should be several items in the Root FAQ up top, such as:
If you are encrypted and going to root, factory reset to get rid of the encryption FIRST since the encryption locks down the SDCARD partition (Unlike on the phone)and none of the recoveries can access it to mount. DON"T use ROM manage on the TF101 and always, always check XDA first.
:good:
Click to expand...
Click to collapse
That FAQ is sadly pretty outdated, I wish I could liberate the OP
Glad all is working now though.

How to format encrypted /data in CWM

Here's the scenario: say you try out encryption on a ROM, either because your employer makes you or because you want the extra security. What happens when you can root your phone, like we can (easily) with the S3, and you want to flash a different ROM? The problem you will find yourself in very quickly is that you cannot do a successful wipe. You can't format an encrypted /data in CWM or any other recovery. If you cannot format /data, you can't flash a ROM - it fails, because /data is encrypted, and it cannot proceed. It turns out none of the recoveries can format an encrypted /data. You also cannot reverse encryption once you've done it. You're stuck, all because you flipped the switch on encryption.
I found myself in this problem as others have in many other forums (like this one for the GNex) (and another one, more detailed).
I also tried, admittedly somewhat out of desperation, the soft-brick instructions here. That didn't work because Nand Erase All fails. You can flash on top, and luckily you can use your same password to decrypt your /data (which I did) but you're still not going to have a clean ROM. Dirty flashes = lots of problems down the road.
I finally found a simple way to do this and wanted to save anyone else the trouble of digging. You can do it using CWM and adb and a few commands. Credit goes Shawn Webb's blog and utkanos on FreeNode's irc at #cyanogenmod.
Here is how to do this on our Verizon S3:
In CWM, wipe cache
adb shell
mke2fs -t ext4 /dev/block/mmcblk0p15
mount /data
mount /dev/block/mmcblk1p1 /data/media
If adb doesn't work in CWM, reboot recovery. You might need to create /data/media after mounting /data in order to do the last step, which I opted not to do. I hope this saves someone else a few hours of frustration, and I also hope that someday one of our recoveries can handle formatting encrypted data. Until then... I'm just not using encryption, period. There already is a lot of documentation against it, and this is one more reason in my book.

Thanks for this. I fell into the same scenario yesterday but after reading a lot of helpful posts from people like yourself I have managed to solve the issue. Basically I found two ways of doing it, one is as you have suggested and the other is by just replacing the custom recovery with the stock recovery. The SGS3 toolkit available on XDA made the 2nd option just slightly simpler for me and by spending less than 10 mins (excluding time for backups and downloads) the issue was resolved.
Just to share this option to save others from the headache of looking for a solution:
1) Get the toolkit
2) Install drivers as recommended and follow instructions to choose the build, or closest build, for your S3
3) Restore stock recovery with toolkit via ODIN (follow instructions)
4) After rebooting, go into Android and reset to factory settings, this would bring you to the stock recovery and wipe
5) Restore custom recovery with toolkit via ODIN (follow instructions)
6) Restore your system (luckily for me I had a nandroid backup before I encrypted)
Note: I did "lose" my internal sdcard files (pictures/documents). But I backed that up on my external sdcard before starting the process. My sdcard was not encrypted.

kitleon said:
Thanks for this. I fell into the same scenario yesterday but after reading a lot of helpful posts from people like yourself I have managed to solve the issue. Basically I found two ways of doing it, one is as you have suggested and the other is by just replacing the custom recovery with the stock recovery. The SGS3 toolkit available on XDA made the 2nd option just slightly simpler for me and by spending less than 10 mins (excluding time for backups and downloads) the issue was resolved.
Just to share this option to save others from the headache of looking for a solution:
1) Get the toolkit
2) Install drivers as recommended and follow instructions to choose the build, or closest build, for your S3
3) Restore stock recovery with toolkit via ODIN (follow instructions)
4) After rebooting, go into Android and reset to factory settings, this would bring you to the stock recovery and wipe
5) Restore custom recovery with toolkit via ODIN (follow instructions)
6) Restore your system (luckily for me I had a nandroid backup before I encrypted)
Note: I did "lose" my internal sdcard files (pictures/documents). But I backed that up on my external sdcard before starting the process. My sdcard was not encrypted.
Click to expand...
Click to collapse
You just saved my month. Drop me a message if I can get you a beer via paypal for this.
Cheers!

THANKS!
olm3ca said:
Here's the scenario: say you try out encryption on a ROM, either because your employer makes you or because you want the extra security. What happens when you can root your phone, like we can (easily) with the S3, and you want to flash a different ROM? The problem you will find yourself in very quickly is that you cannot do a successful wipe. You can't format an encrypted /data in CWM or any other recovery. If you cannot format /data, you can't flash a ROM - it fails, because /data is encrypted, and it cannot proceed. It turns out none of the recoveries can format an encrypted /data. You also cannot reverse encryption once you've done it. You're stuck, all because you flipped the switch on encryption.
I found myself in this problem as others have in many other forums (like this one for the GNex) (and another one, more detailed).
I also tried, admittedly somewhat out of desperation, the soft-brick instructions here. That didn't work because Nand Erase All fails. You can flash on top, and luckily you can use your same password to decrypt your /data (which I did) but you're still not going to have a clean ROM. Dirty flashes = lots of problems down the road.
I finally found a simple way to do this and wanted to save anyone else the trouble of digging. You can do it using CWM and adb and a few commands. Credit goes Shawn Webb's blog and utkanos on FreeNode's irc at #cyanogenmod.
Here is how to do this on our Verizon S3:
In CWM, wipe cache
adb shell
mke2fs -t ext4 /dev/block/mmcblk0p15
mount /data
mount /dev/block/mmcblk1p1 /data/media
If adb doesn't work in CWM, reboot recovery. You might need to create /data/media after mounting /data in order to do the last step, which I opted not to do. I hope this saves someone else a few hours of frustration, and I also hope that someday one of our recoveries can handle formatting encrypted data. Until then... I'm just not using encryption, period. There already is a lot of documentation against it, and this is one more reason in my book.
Click to expand...
Click to collapse
Just wanted to say thanks very much for this. I'd tried the method of reloading the stock ROM as described by a previous poster, but this way worked.
I did run into a small issue I was wondering if you could shed some light on. When I entered "mount /data", I got the following:
Code:
~ # mount /data
mount: mounting /dev/block/mmcblk0p37 on /data failed: Invalid argument
I bullied ahead and entered the last line "mount /dev/block/mmcblk1p1 /data/media" and got this:
Code:
~ # mount /dev/block/mmcblk1p1 /data/media
mount: mounting /dev/block/mmcblk1p1 on /data/media failed: No such file or directory
However after doing this, I was able to perform a complete wipe of /data using CWM and load a new ROM without issue.
I'd curious to know what might be causing these Invald argument responses.
My Device: HTC One (GSM)
Thanks again! :laugh:

olm3ca said:
Here is how to do this on our Verizon S3:
In CWM, wipe cache
adb shell
mke2fs -t ext4 /dev/block/mmcblk0p15
mount /data
mount /dev/block/mmcblk1p1 /data/media
If adb doesn't work in CWM, reboot recovery. You might need to create /data/media after mounting /data in order to do the last step, which I opted not to do. I hope this saves someone else a few hours of frustration, and I also hope that someday one of our recoveries can handle formatting encrypted data. Until then... I'm just not using encryption, period. There already is a lot of documentation against it, and this is one more reason in my book.
Click to expand...
Click to collapse
I'm trying to follow your instructions but fail at finding out my mount points.
Sorry for the noob question, but who do I find out what the mount points of internal and external SD card are on my device (Samsung Galaxy S4 Mini International 4G)? I found this post
stackoverflow. /questions/6824463/how-to-get-all-the-mount-point-information-for-android-device
which seems to include the answer but I don't know what tool / software they use. I'm no programmer.
My phone is encrypted and doesn't turn on, it doesn't accept my password saying it's wrong, though I know it's correct. OS is Cyanogenmod 10.1 stable. Booting into CWM v6.0.3.7 is possible though.
I appreciate everyone's help.
Stephan

[Q] Help! TWRP Won't Mount /sdcard for flashing!

I ran a recovery in TWRP to get my phone back to the phones original rom after being on AOKP JB Build 4 on my AT&T One X, but now it stays on the HTC boot screen with the red legal warning on it and TWRP can't mount /sdcard to flash back to another rom. I really hope that this isn't a brick but can someone shine some light on this issue and a possible fix? Help would be greatly appreciated!
Update: Was able to get AOKP flashed back by mounting /data as /sdcard, phone boots into it and I can use it, but the internal storage (/sdcard) is nonexistent and won't mount.

format sdcard in your computers os. make sure not to factory reset or clear storage in bootloader or it will corrupt sdcard.

DvineLord said:
format sdcard in your computers os. make sure not to factory reset or clear storage in bootloader or it will corrupt sdcard.
Click to expand...
Click to collapse
I can't get the phone to mount as a removable drive because of the problem with /sdcard, so I can't format it from my computer.

c_h0use said:
I can't get the phone to mount as a removable drive because of the problem with /sdcard, so I can't format it from my computer.
Click to expand...
Click to collapse
Don't worry about the red text. We all have that. And it is not bricked.
Can you turn the phone on with the stock ROM you flashed? If so, can you mount the SD card while it is on, booted up in phone mode? If, mount it there, then move your new rom to your phone.

Hello,
I have a similar issue, i can get into TWRP recovery, but i am not able to mount sdcard. My mistake was that i did fastboot flash boot boot.img but i neglected to actually flash the room and i didn't put the rom in the sdcard, so now i need to mount the sdcard to load the rom to flash it, but that is where i am stuck, is there a way to copy files into the sdcard via adb or any other way?
Any help will be greatly appreciated it.
Thank you.

XRACER said:
Hello,
I have a similar issue, i can get into TWRP recovery, but i am not able to mount sdcard. My mistake was that i did fastboot flash boot boot.img but i neglected to actually flash the room and i didn't put the rom in the sdcard, so now i need to mount the sdcard to load the rom to flash it, but that is where i am stuck, is there a way to copy files into the sdcard via adb or any other way?
Any help will be greatly appreciated it.
Thank you.
Click to expand...
Click to collapse
I think what you need to do then is flash the ROM from your bootloader. I found this guide with directions explaining how to flash from the bootloader by googling How To Flash Rom from Bootloader in the XDA Wiki. Here are the steps
ROM Flashing
Obtain a ROM of your choice, and note the location on your computer.
reboot your device into fastboot mode via one of the following options.
adb reboot bootloader (requires USB debugging to be turned on).
power off the device then back on with 'vol up' + power button.
Wipe your device.
fastboot -w
Update your ROM.
fastboot update </path/to/your/RomFile.zip>
Your phone will update and automatically reboot into the new ROM.
ROM update without SDcard
If you don't have an sd card, or your slot is broken you can try this trick, but you will need a custom recovery like Clockwork.
Boot up your phone to recovery. And move your rom file to the adb directory, and start a command line ( cmd )
adb shell
mount data
adb push D:\custom_rom.zip /data/
Wait until the push finised, and restart your device to recovery again with "adb reboot-bootloader"
mount data
mount /data /sdcard ( mount the data folder into your sdcard folder, so your recovery will think that you have an sdcard installed )
Locate the ROM .Zip file you wish to flash.
Confirm the flash by following the on-screen instructions (ie: pressing the trackball, pressing the call button, etc.)
If no errors arise during the flashing process then the ROM flash was successful, Reboot the device.
With some root file explorer, remove the rom file if you don't need it anymore, to free up space.
Or use adb to remove the custom recovery
adb shell rm data/custom_rom.zip

thanks for the reply but the procedure is not working,
when in fastboot through cmd i get
fatsboot -w
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.003s
I made sure i am in fastboot USB

elphiz
XRACER said:
thanks for the reply but the procedure is not working,
when in fastboot through cmd i get
fatsboot -w
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.003s
I made sure i am in fastboot USB
Click to expand...
Click to collapse
Lol this just happen toe last night what u need to do is boot into bootloader then plug it USB cable to ur phone and format your sdcard it make sure u download a Rom to your computer before this it can be any tom you like after you format you can put the Rom on ur sdcard and flash and u will be golden

loading into bootloader doesn't allow the computer to read/access the sdcard keep in mind this is the HOX so the sdcard is the internal memory, i could get into the recovery and then try to mount it that way and format from there but for some reason i can't select the option mount sdcard.

This works:
How to Fix corrupt/unmountable internal storage on the HTC One X/XL
http://forums.team-nocturnal.com/sh...storage-on-the-HTC-One-X-XL?p=13552#post13552

perfect thanks that did the job. now time to install the ROM!!!!
thanks a lot
hmmmm.... one more question would i need to flash the boot image as well before installing the ROM???
EDIT: i went ahead and just flashed the ROM, and everything is working fine.
Thank you to everyone

XRACER said:
perfect thanks that did the job. now time to install the ROM!!!!
thanks a lot
hmmmm.... one more question would i need to flash the boot image as well before installing the ROM???
EDIT: i went ahead and just flashed the ROM, and everything is working fine.
Thank you to everyone
Click to expand...
Click to collapse
If you're not on Hboot 1.14 then you don't have to flashboot flash boot.img. just flash the .zip from your sd card
Sent from my HTC One XL cellular device over clocked to 1.9Ghz

thank you sir!
king200 said:
This works:
How to Fix corrupt/unmountable internal storage on the HTC One X/XL
Click to expand...
Click to collapse
ok this did work and i appreciate the link. ive bookmarked it for future use. what sux is i assumed i bricked and have already had a new phone shipped. oh well guess i got a back up

will this work because my microsims card unable to mount /sdcard which i assume is the internal one will it work even if its blank/empty via computer because i have no working os on my phone i have incredible 4g so i hope you can help me

XRACER said:
loading into bootloader doesn't allow the computer to read/access the sdcard keep in mind this is the HOX so the sdcard is the internal memory, i could get into the recovery and then try to mount it that way and format from there but for some reason i can't select the option mount sdcard.
Click to expand...
Click to collapse
I did it. Apparently you can install a zip ROM from SD card once you repartition it from the recovery. There is an option to partition the SD card in the Recovery.
After that, restart the phone, go into recovery again, connect to the PC using a USB cable, and use the USB mount option if you want to copy the ROM without removing the microSD card from the phone. Copy the zip ROM to the sdcard and try installing the ROM again. It worked for me !
I was installing the Pico ROM from this tutorial:
www (dot) rootlord.com/2013/08/revert-htc-explorer-back-to-stock-rom (dot) html
I

TWRP Mounting SD card
DvineLord said:
format sdcard in your computers os. make sure not to factory reset or clear storage in bootloader or it will corrupt sdcard.
Click to expand...
Click to collapse
So I think I may have currupted my sdcard. I'm running CM-12 4/21/15 nightly. I'm a nubie at this stuff and have read everywhere I can think of on the forums. When I try to reboot to bootloader from TWRP recovery if goes immediately to the do no remove USB connection FIRMWARE Update. I am worried that this will un-root me with AT&T being jerks and fixing the bumped bootloader. So, I have always just pulled the battery, plus it never has any progress on the %downloaded bar.
To try to fix the issue I may have just made it worse and created too many partitions or corrupted the SD by doing exactly what you said not to do above. Before I did a TWRP wipe (not the advanced version) the SD card was mounted, but some apps like google play music kept saying external storage removed. I did the wipe and saw the factory reset screen and said ok. I had to download all my apps again and then switched to Google Now launcher I orginally rooted and bootloader unlocked with bump on a different smaller external SD card. I wasn't sure if that had anything to do with it.
I'm almost unsure what to ask you or other more experienced users what to do.

eee. how about on my samsung galaxy j5 sm j500h? i wanted to mount my phone to pc but i cant. was planning to fix my phone cause im stucked on bootlogo due to flashing xposed-v72-sdk22-arm.zip. Hoping that you guys can help me out.

partitions seem to be locked, cant format

i had a recent soft brick in which for some reason, i couldnt decrypt, with this, i couldnt load anything on android besides twrp and fastboot.. when i try reformatting and wiping data, it seems to fail.. for example, i go to format with twrp and it hangs, if i try installing anything itll fail to load any data onto that partition.. if i could reformat that partition back to its useful state, without the encryption issue i could reinstall a rom and fix this issue
any ideas?
when i attempt to do anything in twrp.. i get this error
Updating partition details
E: error opening ' /data/media '
E: error: No such file or directory
just a test, i tried to create a new folder in /data, and it says its a read-only filesystem

jason41987 said:
i had a recent soft brick in which for some reason, i couldnt decrypt, with this, i couldnt load anything on android besides twrp and fastboot.. when i try reformatting and wiping data, it seems to fail.. for example, i go to format with twrp and it hangs, if i try installing anything itll fail to load any data onto that partition.. if i could reformat that partition back to its useful state, without the encryption issue i could reinstall a rom and fix this issue
any ideas?
when i attempt to do anything in twrp.. i get this error
Updating partition details
E: error opening ' /data/media '
E: error: No such file or directory
just a test, i tried to create a new folder in /data, and it says its a read-only filesystem
Click to expand...
Click to collapse
Your partition is probably encrypted. The only way to access to your data is to decrypt it before you can do anything. Do you have a password for it?

LetMeKnow said:
Your partition is probably encrypted. The only way to access to your data is to decrypt it before you can do anything. Do you have a password for it?
Click to expand...
Click to collapse
no, any way i can erase all the data, the partition and start fresh?

jason41987 said:
no, any way i can erase all the data, the partition and start fresh?
Click to expand...
Click to collapse
"Format data" should do this. In which way doesn't it work for you?

_that said:
"Format data" should do this. In which way doesn't it work for you?
Click to expand...
Click to collapse
when i attempt to format data, format fails, it will not let me touch the /data partition, when it does mount, it mounts as read-only.. the partition itself, possibly partition table or something is damaged because it cannot be formatted and nothing can be written to it
it would seem like the internal storage is screwed.. but the other partitions seem to work fine, even able to use command-line from twrp to check fstab and try to mount manually... im not sure how to completely delete and recreate a partition in fdisk, if possible on here

jason41987 said:
when i attempt to format data, format fails
Click to expand...
Click to collapse
No error message? No log file? Just "fails"?
You could try running "/sbin/make_ext4fs /dev/block/mmcblk0p8" manually from adb shell.
jason41987 said:
it would seem like the internal storage is screwed.. but the other partitions seem to work fine, even able to use command-line from twrp to check fstab and try to mount manually... im not sure how to completely delete and recreate a partition in fdisk, if possible on here
Click to expand...
Click to collapse
You can't use fdisk on the internal storage - it uses a combination of GPT and a proprietary partition table.

_that said:
No error message? No log file? Just "fails"?
You could try running "/sbin/make_ext4fs /dev/block/mmcblk0p8" manually from adb shell.
You can't use fdisk on the internal storage - it uses a combination of GPT and a proprietary partition table.
Click to expand...
Click to collapse
the errors i receive are above..trying different things ive received the error that the partition is write one... are there any tools for redoing the entire internal storage?

maybe this could work.. since the other partitions seem to work just fine, as they were not encrypted, what if i edited fstab to mount partitions on a MicroSD card pre-partitioned to act as /data and /cache, then install a rom... unless there are ROMs designed to utilize an external SD for installation?... either way if i can work around these two partitions i could get into a working android system where i can find more tools to assist in removing and recreating those broken partitions
ive considered trying to use fastboot to replace the twrp recovery with a stock asus recovery partition and try to fix the issue from that, but i doubt that would be of any use

jason41987 said:
ive considered trying to use fastboot to replace the twrp recovery with a stock asus recovery partition and try to fix the issue from that, but i doubt that would be of any use
Click to expand...
Click to collapse
Instead you should try it cause i'm pretty sure it will fix your partition.Just install the stock recovery and do a Wipe Data first. If all goes well you can go ahead and flash a stock rom from MicroSD or install the TWRP again and check if it's working.
Here you can find the latest stock recovery - - > http://forum.xda-developers.com/showthread.php?p=44280630

Pretoriano80 said:
Instead you should try it cause i'm pretty sure it will fix your partition.Just install the stock recovery and do a Wipe Data first. If all goes well you can go ahead and flash a stock rom from MicroSD or install the TWRP again and check if it's working.
Here you can find the latest stock recovery - - > http://forum.xda-developers.com/showthread.php?p=44280630
Click to expand...
Click to collapse
are you saying write over twrp with the stock recovery partition with fastboot, then boot into the recovery partition from the power + volume down menu and see if that recovery image will reset to factory defaults?... if so, where would i even get that recovery image?.. and if you mean just try installing a stock rom through TWRP, ive already been there, done that, and it hangs on formatting

jason41987 said:
are you saying write over twrp with the stock recovery partition with fastboot, then boot into the recovery partition from the power + volume down menu and see if that recovery image will reset to factory defaults?... if so, where would i even get that recovery image?.. and if you mean just try installing a stock rom through TWRP, ive already been there, done that, and it hangs on formatting
Click to expand...
Click to collapse
If you follow the link i posted previously you will find the stock recovery (from the latest asus firmware) as an attachment to that post.
After you flash it via Fastboot, do a Wipe Data from the bootloader menu (the one with the 3 icons) after that just follow "restore with stock recovery" procedure from my All in One Thread (it's a sticky post under General Forum).
That should fix your issue and get you to a new clean starting point.

Pretoriano80 said:
If you follow the link i posted previously you will find the stock recovery (from the latest asus firmware) as an attachment to that post.
After you flash it via Fastboot, do a Wipe Data from the bootloader menu (the one with the 3 icons) after that just follow "restore with stock recovery" procedure from my All in One Thread (it's a sticky post under General Forum).
That should fix your issue and get you to a new clean starting point.
Click to expand...
Click to collapse
well, ill try that as soon as i wake up.. if it doesnt work though i am prepared to install something thatll run those partitions of an external microsd though.. wonder why no roms exist specifically for that?... seems like an ultra-secure rom for the ultra-paranoid to be able to pop out their microsd and hide it with all user data stored on it

jason41987 said:
well, ill try that as soon as i wake up.. if it doesnt work though i am prepared to install something thatll run those partitions of an external microsd though.. wonder why no roms exist specifically for that?... seems like an ultra-secure rom for the ultra-paranoid to be able to pop out their microsd and hide it with all user data stored on it
Click to expand...
Click to collapse
Data2SD already exists.
Did you already try to format your data partition from adb shell?

data2sd seems to be something thats applied after a rom is successfully installed, not sure that would help me
anyway, i tried the stock recovery image and it just hangs on an android graphic with a rotating blue wireframe inside its chest and a blue progress bar, but it doesnt actually do anything else
edit: wait a minute.. i see how this goes with the data2sd... i download a data2sd kernal, since i install cleanrom i can add this to the installations list of kernals, the data2sd kernal will mount external SD cards as the /data, cache, and sdcard partitions, allowing me to bypass the issue im having completely and use a 64gb microsd card as my primary storage... very interesting indeed

aah, fantastic, cant even get into fastboot mode to put twrp back on for the data2sd method.. so it would seem now my tablet is COMPLETELY toast

jason41987 said:
aah, fantastic, cant even get into fastboot mode to put twrp back on
Click to expand...
Click to collapse
What happens when you try?

_that said:
What happens when you try?
Click to expand...
Click to collapse
when i hold power and volume down it goes straight to the robot with the blue spinning wireframe graphic,, i dont get an option to go to fastboot.. i can also use power and volume up to go into apx mode but no idea what thats even used for as i find very little reference to it online

jason41987 said:
when i hold power and volume down it goes straight to the robot with the blue spinning wireframe graphic,, i dont get an option to go to fastboot..
Click to expand...
Click to collapse
I see, that's forced boot to recovery because of "wipe data" selected from the bootloader menu.
I don't know how long wiping data takes, maybe you are just not patient enough to let it finish?

_that said:
I see, that's forced boot to recovery because of "wipe data" selected from the bootloader menu.
I don't know how long wiping data takes, maybe you are just not patient enough to let it finish?
Click to expand...
Click to collapse
no, it finished, then said it was booting the recovery image afterwards, then i let it sit for about 2 hours when i went to do something else and it hanged on that screen... no way to fix this from apx mode?

jason41987 said:
no way to fix this from apx mode?
Click to expand...
Click to collapse
APX mode is only useful if you have nvflash, the wheelie tool, and the blob file for your device, which you'd have needed to create with firmware 9.4.5.26 or earlier and the hacked bootloader from androidroot.mobi.

Softbricked flashing recovery with TWRP Manager App

Hello. I seem to have softbricked my nexus 5 with the twrp manager app when flashing new recovery thinking I was taking a shortcut so I didn't have to boot my laptop up for 4.4.3. update. Guess I had to anyway because recovery did not get updated to 2.7.1.1! I was going to update to paranoidandroid 4.4.3rc1, elementalx.44 and also new radio but never got that far because recovery failed to mount /sdcard, and also /data, /cache I have no idea if the path to the recovery partition block (?) from the twrp app was correct but i assumed so because it was mentioned as a preferred way of installing the recovery.
The problem is that there is no sd card detected , no camera, crashes in google play services and general system wobbliness and no identifications and a different wifi mac address, no network signal but wifi is working. /data, /cache and /sdcard is not mountable in recovery.. can't get adb to work in other mode than ptp either but that's probably just my pc.
I was thinking about flashing the images from https://developers.google.com/android/nexus/images but I hope there is a chance to backup my sdcard please! Could I perhaps flash the images one by one and see if it gets better? perhaps flashing the kernel again? :silly:
------
oh well apparently forgot I had to still format /cache. ooops. thread closed?

StrongOneX said:
Hello. I seem to have softbricked my nexus 5 with the twrp manager app when flashing new recovery thinking I was taking a shortcut so I didn't have to boot my laptop up for 4.4.3. update. Guess I had to anyway because recovery did not get updated to 2.7.1.1! I was going to update to paranoidandroid 4.4.3rc1, elementalx.44 and also new radio but never got that far because recovery failed to mount /sdcard, and also /data, /cache I have no idea if the path to the recovery partition block (?) from the twrp app was correct but i assumed so because it was mentioned as a preferred way of installing the recovery.
The problem is that there is no sd card detected , no camera, crashes in google play services and general system wobbliness and no identifications and a different wifi mac address, no network signal but wifi is working. /data, /cache and /sdcard is not mountable in recovery.. can't get adb to work in other mode than ptp either but that's probably just my pc.
I was thinking about flashing the images from https://developers.google.com/android/nexus/images but I hope there is a chance to backup my sdcard please! Could I perhaps flash the images one by one and see if it gets better? perhaps flashing the kernel again? :silly:
------
oh well apparently forgot I had to still format /cache. ooops. thread closed?
Click to expand...
Click to collapse
Try adb to backup your sdcard or flashing the factory images EXCEPT userdata.img should do the trick.