[Q] TWRP 2.2.3.0 unable to mount, no OS, flashing errors - General Questions and Answers

I have a Nabi 2 that I am able to get into TWRP, but when I try to install any zip files, it gives me a flashing error. I also notice I that it shows unable to mount and when I power down from TWRP it states no OS installed. How can I reinstall the OS for a Nabi 2. Any help would be appreciated. Thanks.

ehscoto said:
I have a Nabi 2 that I am able to get into TWRP, but when I try to install any zip files, it gives me a flashing error. I also notice I that it shows unable to mount and when I power down from TWRP it states no OS installed. How can I reinstall the OS for a Nabi 2. Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Your TWRP version is too old. You need a newer one.
This is the general procedure to follow:
http://forum.xda-developers.com/showpost.php?p=51037177&postcount=21
Substitute this TWRP though
http://forum.xda-developers.com/showpost.php?p=59452953&postcount=2592

I followed the thread and updated the TWRP and now using 2.2.3.0 and still having the same problem. I try to go into the mount section and not able to click on anything. I tried flashing a zip that I was able to flash previously and that one does not work either.

ehscoto said:
I followed the thread and updated the TWRP and now using 2.2.3.0 and still having the same problem. I try to go into the mount section and not able to click on anything. I tried flashing a zip that I was able to flash previously and that one does not work either.
Click to expand...
Click to collapse
You should be using TWRP 2.6.3 or higher. The TWRP you are using has ICS kernel and can't read the device partitions. The second link I gave you is 2.8.5

I will try updating to s newer version and see if that works. Thanks for the info.

Related

How to update to newest bootloader and install custom ROM

I'm currently on a HYDRO ROM 4.1 and want to update to the newest bootloader and JB. I downloaded the latest ROM from ASUS but when I try to flash it via TWRP it just says failed before anything gets started. What steps to I have to take from where I am to get the latest and greatest?
Bagel Bear said:
I'm currently on a HYDRO ROM 4.1 and want to update to the newest bootloader and JB. I downloaded the latest ROM from ASUS but when I try to flash it via TWRP it just says failed before anything gets started. What steps to I have to take from where I am to get the latest and greatest?
Click to expand...
Click to collapse
Did u try using fastboot to flash it? Also dont forget to extract the ROM from the downloaded zip file.
I did not realize the ROM .zip file was inside the .zip file...
Thank you installing now. After that I just have to flash an updated recovery and then install an custom ROM, correct. You've been a great help.
Now TWRP says Successful but it didn't take but a couple of minutes and the log says "E:Unable to mount '/staging'
I assume it failed for some reason.
Bagel Bear said:
Now TWRP says Successful but it didn't take but a couple of minutes and the log says "E:Unable to mount '/staging'
I assume it failed for some reason.
Click to expand...
Click to collapse
Did you install the -42 TWRP since you are now on the 4.2 boootloader?
Ah I see. It did actually install the latest bootloader. I installed the latest TWRP but it seems that it can't see files from various partitions. I guess it can't mount them or something so I can't installed a custom ROM from my micro sd or anything. Any help for this problem?
Bagel Bear said:
Ah I see. It did actually install the latest bootloader. I installed the latest TWRP but it seems that it can't see files from various partitions. I guess it can't mount them or something so I can't installed a custom ROM from my micro sd or anything. Any help for this problem?
Click to expand...
Click to collapse
Did you mount the correct partition in the settings of TWRP. Try unmounting and then remounting what you need.
Even the log on TWRP says it is unable to mount anything on startup. When I try to exit TWRP it says that I am not rooted and prompts me if it can root for me. Can I do it this way?
Anyone know anything about this?
Bump

Need urgent help! Bricked for 2 days already!

I successfully rooted and achieved an unlocked bootloader with S-OFF on my Verizon HTC One M8 and also flashed TWRP 2.7.0.2. I downloaded a rom (without an SD card). I booted into recovery and i made a backup (not noticing that one of the lines read "unable to mount '/system". I then wiped and attempted to flash the rom only to find out that i can't find it in my file system. So i put the rom on an SD card and mounted it and tried to flash it, i get this message:
E: Unable to mount '/system'
E: Unable to open zip file.
Error Flashing zip '/external_sd/Roms?ViperOneM*_1.2.0.zip'
Updating partition details...
E: Unable to mount '/system'
So i'm stuck with a boot loader, an unmountable file system, and unable to flash a rom.
I've tried Fix permissions, I've tried mounting the "system" but all that mounts is 'cache' 'data' and 'micro SDcard'.
I hope my nerves are getting the best of me and i can't see something that's right in front of me!
Edit: Flashed CWM Recovery. Trying to install ROM from SD Card results in "Installation Aborted". When i try to side load it hangs at 81%.
Did you flash TWRP using terminal emulator mode as described on the official website for 2.7.0.2? If so you overwrote the system partition. Try flashing the recovery using the fastboot method as this will put the recovery in the right place. Then boot into the bootloader, choose recovery. I think this will get you TWRP in the recovery partition. Once there try flashing a ROM (although o would suggest something closer to stock like Skyfall).
I think what is happening is since the instructions for flashing TWRP via terminal emulator list the wrong partition, when you boot up to system it seems like you are booting to recovery because TWRP shows up. But you're actually on the system partition so when you try to flash a ROM you get an error because you can't mount the partition you're in.
I'm far from an expert in any of this so anyone who is please correct me.
dsEVOlve said:
Did you flash TWRP using terminal emulator mode as described on the official website for 2.7.0.2? If so you overwrote the system partition. Try flashing the recovery using the fastboot method as this will put the recovery in the right place. Then boot into the bootloader, choose recovery. I think this will get you TWRP in the recovery partition. Once there try flashing a ROM (although o would suggest something closer to stock like Skyfall).
I think what is happening is since the instructions for flashing TWRP via terminal emulator list the wrong partition, when you boot up to system it seems like you are booting to recovery because TWRP shows up. But you're actually on the system partition so when you try to flash a ROM you get an error because you can't mount the partition you're in.
I'm far from an expert in any of this so anyone who is please correct me.
Click to expand...
Click to collapse
I did flash TWRP as described. I used Terminal from my Macbook. I did some researching and i did try flashing using the fast boot method. I'm just so stumped!
First of all you aren't bricked. Have you tried using side load to flash the ROM? Try flashing another recovery too.
Sent from my HTC6525LVW using Tapatalk
SimplyNando said:
I did flash TWRP as described. I used Terminal from my Macbook. I did some researching and i did try flashing using the fast boot method. I'm just so stumped!
Click to expand...
Click to collapse
The above suggestion to try and Sideload the ROM install is a good idea. Basically, put the ROM zip file in your platform-tools folder of adb. Then boot to TWRP recovery, choose "sideload" and then issue the command "adb sideload [filename.zip]" (Instructions are found HERE.)
If that doesn't work, have you tried flashing Clockwork Recovery? You may have better luck with that in regards to mounts and/or flashing the ROM...
There's always USB OTG as well
Sent from my HTC6525LVW using Tapatalk
I found THIS thread (for ASUS Transformer though).
What may have happened (if I'm reading the above thread correctly) is that your /system doesn't exist.
Taking a complete stab at a fix, you may be able to use fastboot to flash a working "system.img" file. (Anyone with more expertise, please confirm or refute this...)
EDIT: Found THIS post in the "Official" TWRP release 2.7.0.0 thread I wonder if perhaps this is what happened to you?
WorldOfJohnboy said:
I found THIS thread (for ASUS Transformer though).
What may have happened (if I'm reading the above thread correctly) is that your /system doesn't exist.
Taking a complete stab at a fix, you may be able to use fastboot to flash a working "system.img" file. (Anyone with more expertise, please confirm or refute this...)
EDIT: Found THIS post in the "Official" TWRP release 2.7.0.0 thread I wonder if perhaps this is what happened to you?
Click to expand...
Click to collapse
That does seem like it could be the problem. I just flashed CWM recovery instead but it's still the sam problem. Still can't flash a rom, i also tried using sideboot.
SimplyNando said:
That does seem like it could be the problem. I just flashed CWM recovery instead but it's still the sam problem. Still can't flash a rom, i also tried using sideboot.
Click to expand...
Click to collapse
You might have to find a factory image, an RUU I am not sure if one exists but it will write the partitions. I think somehow your actual system partition was erased which is why it cannot be mounted. Pretty much, your only hope is an RUU or a zipped factory image.
123421342 said:
You might have to find a factory image, an RUU I am not sure if one exists but it will write the partitions. I think somehow your actual system partition was erased which is why it cannot be mounted. Pretty much, your only hope is an RUU or a zipped factory image.
Click to expand...
Click to collapse
I wouldn't be able to get that from the system dump located http://forum.xda-developers.com/showthread.php?t=2695171 ? Is there any other possible explanation??
SimplyNando said:
I wouldn't be able to get that from the system dump located http://forum.xda-developers.com/showthread.php?t=2695171 ? Is there any other possible explanation??
Click to expand...
Click to collapse
no because it is not a flashable zip. Factory image or RUU means the bootloader will literally write the partition. Recovery will mount the partition and write information to it. It cannot create the partition itself which I think is your issue.
Assuming your recovery is fine..this is what I did to fix my self inflicted "soft brick" on Saturday...I mistakenly hit format system instead of just data and cache while trying to start over.
I am running cwm 6047..and for whatever reason the sideload failed with an error trying to sideload flash sky fall.
So I did an adb push skyfall.zip /sdcard/0 and was then able to flash the zip from internal storage.
Hope that helps with your situation.
bakemcbride21 said:
Assuming your recovery is fine..this is what I did to fix my self inflicted "soft brick" on Saturday...I mistakenly hit format system instead of just data and cache while trying to start over.
I am running cwm 6047..and for whatever reason the sideload failed with an error trying to sideload flash sky fall.
So I did an adb push skyfall.zip /sdcard/0 and was then able to flash the zip from internal storage.
Hope that helps with your situation.
Click to expand...
Click to collapse
Yep. You have a bad download. Download a new ROM on your computer...boot to recovery and do a adb sideload or push
Sent from my HTC One M8
Just had a thought... did you flash the insecure Kernel (found HERE) ever? You may not have a writeable /system?
Flash the Kernel, then reflash the official TWRP (both in Fastboot) and see if that works...
WorldOfJohnboy said:
Just had a thought... did you flash the insecure Kernel (found HERE) ever? You may not have a writeable /system?
Flash the Kernel, then reflash the official TWRP (both in Fastboot) and see if that works...
Click to expand...
Click to collapse
Kernel runs inside the rom and the system becomes writeable in the ROM so that won't do anything. I'm pretty convinced he is missing the partition.
Sent from my HTC6525LVW using Tapatalk
Hi did you manage to sort this issue out as i'm having the same issue. it won't install backups or open zip files of the rom's. no matter what i do it won't flash the rom's. i've tried side loading on both cwm and TWRP - as i just said swapped from both recoveries. Managed to mount the sd card and put a new rom on it but won't flash from there and I've tried to move it to internal but fails.
I can't find my stock recovery an a nandroid back up either. Any help would be great
thanks
---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------
Oh it does let me flash a Kernal zip tho?
jerico9 said:
Hi did you manage to sort this issue out as i'm having the same issue. it won't install backups or open zip files of the rom's. no matter what i do it won't flash the rom's. i've tried side loading on both cwm and TWRP - as i just said swapped from both recoveries. Managed to mount the sd card and put a new rom on it but won't flash from there and I've tried to move it to internal but fails.
I can't find my stock recovery an a nandroid back up either. Any help would be great
thanks
---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------
Oh it does let me flash a Kernal zip tho?
Click to expand...
Click to collapse
did you try formatting internal yet?
Just for anyone withthe same issue. It ended up being not dnough memory to flash the recovery or the new rom....deerrrrrrr!!!
Haha, cant believe it had me stumped for 5 days trying everything and anything. Formatting would have helped aswell So thanks for the suggestion
jerico9 said:
Just for anyone withthe same issue. It ended up being not dnough memory to flash the recovery or the new rom....deerrrrrrr!!!
Haha, cant believe it had me stumped for 5 days trying everything and anything. Formatting would have helped aswell So thanks for the suggestion
Click to expand...
Click to collapse
I have an HTC version of fastboot/adb that will work on a low memory pc. It's posted in my ruu thread.
dottat said:
I have an HTC version of fastboot/adb that will work on a low memory pc. It's posted in my ruu thread.
Click to expand...
Click to collapse
I mean the device memory was low, so couldn't flash as no room on the device

[Q&A] [RECOVERY][TF101][TF101G][SL101] TWRP 2.8.1.1 Unofficial [2014-11-06]

Q&A for [RECOVERY][TF101][TF101G][SL101] TWRP 2.8.1.1 Unofficial [2014-11-06]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][TF101][TF101G][SL101] TWRP 2.8.1.1 Unofficial [2014-11-06]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Update from TWRP 2.3 to 2.8
The easiest way please. I could not find this info on the web.
Thanks
Arenamar
Arenamar said:
The easiest way please. I could not find this info on the web.
Thanks
Arenamar
Click to expand...
Click to collapse
Just download the appropriate zip and flash from twrp, reboot to Android, then reboot to twrp.
sidneyk said:
Just download the appropriate zip and flash from twrp, reboot to Android, then reboot to twrp.
Click to expand...
Click to collapse
Thanks, very easy. Goo manager or flashily no good. This worked great.
problems flashing TWRP 2.8.1
Hi. I have 2.3.2.3 version (the last version flashable using the app "TWRP manager") of TWRP recovery and I have to update to the version above to install Lollipop into my asus tf101. How can I flash this version 2.8.1.1 to my tablet? simply flashing it as .rar file with the recovery I still have (as a ROM)?
thank you!
tot92 said:
simply flashing it as .rar file with the recovery I still have
Click to expand...
Click to collapse
I don't know where you downloaded the recovery. It is a .zip not a .rar.
And while reading the op you will notice the word flashable.
Just download the .zip to your device and flash it with your current recovery
Download flashable TWRP 2.8.1.1 zip for TF101:
signed_twrp-2.8.1.1_tf101.zip
TWRP 2.8.1.1 MD5 sum for TF101:
signed_twrp-2.8.1.1_tf101.zip.md5
Installation
Hello all,
Is it me or there is no guide on how to flash this? I'm running stock recovery and Android 4.0.3 and I'm root. There is no flash option on stock recovery.
Can anyone help?
Thanks in advance!
TedManowar said:
Is it me or there is no guide on how to flash this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=57218372
I can't seem to get this recovery working. I'm flashing it from TWRP 2.3.2.3 on a tf101g but, although the it reports a successful flash and I observe the blue-green bar on the next boot, if I try to boot into the new recovery, it just hangs. I do see an error regarding being unable to mount /staging immediately after the flash mind. Given that this is where the blob is flashed to, is that indicative of problems and can anyone suggest how I might resolve them?
If not, I wondered what the *oldest* twrp it's possible to flash the latest KatKiss from is and where I might find it?
snbutler said:
I can't seem to get this recovery working. I'm flashing it from TWRP 2.3.2.3 on a tf101g but, although the it reports a successful flash and I observe the blue-green bar on the next boot, if I try to boot into the new recovery, it just hangs. I do see an error regarding being unable to mount /staging immediately after the flash mind. Given that this is where the blob is flashed to, is that indicative of problems and can anyone suggest how I might resolve them?
If not, I wondered what the *oldest* twrp it's possible to flash the latest KatKiss from is and where I might find it?
Click to expand...
Click to collapse
Are you flashing a version built for tf101g? The main one is for tf101.
Sent from my SM-N900T using XDA Premium HD app
sidneyk said:
Are you flashing a version built for tf101g? The main one is for tf101.
Sent from my SM-N900T using XDA Premium HD app
Click to expand...
Click to collapse
Yes, I'm using signed_twrp-2.8.1.1_tf101g.zip from the first post on the main thread.
snbutler said:
Yes, I'm using signed_twrp-2.8.1.1_tf101g.zip from the first post on the main thread.
Click to expand...
Click to collapse
Did you also download the corresponding MD5 file to the same directory to verify you have a good download? A corrupt file might still flash but won't work necessarily. It should be recognizing your tf101g as such unless I missed something.
Sent from my SM-N900T using XDA Premium HD app
sidneyk said:
Did you also download the corresponding MD5 file to the same directory to verify you have a good download? A corrupt file might still flash but won't work necessarily. It should be recognizing your tf101g as such unless I missed something.
Sent from my SM-N900T using XDA Premium HD app
Click to expand...
Click to collapse
Hmmm. Interesting. I had downloaded the md5 file and had checked that it matched manually by running md5sum on the zip file and comparing the result to the contents of the md5 file. However, if I force md5 verification in twrp, it says that the two don't match and aborts the procedure. Redownloading provides me with the same version of the file each time, as checked with diff.
Another thought: could the blob itself be corrupted? Would you be able to supply an md5sum for the blob for to me compare against? Thanks!
snbutler said:
Another thought: could the blob itself be corrupted? Would you be able to supply an md5sum for the blob for to me compare against? Thanks!
Click to expand...
Click to collapse
The MD5 supplied is for the zipped package, before it left my machine. If you, move both files to ext sdcard, or wherever you intend to flash from, and double check that md5sum matches the MD5 inside the MD5 file, after they are both in final flash from directory. I could extract the package and do an md5sum on just the blob, but if it's corrupted that won't really help you. You could also extract the blob to internal /sdcard directory and flash with adb shell per the rescue instructions from the first post of the thread.
Sent from my SM-N900T using XDA Premium HD app
I'm boot looping after merely doing a nandroid. How does that even happen? wiping cache/dalvik cache did nothing and restoring that backup or the last did nothing. I guess I'll try reflashing katkis 5.1 again. Kind of a pain.
Boot Loops With TWRP 2.8.1
Hi,
I have just installed TWRP 2.8.1 and with in flashed KatKiss 5.1.1 ROM on my TF101.
After I finished flashing everything and rebooted the device, I am stuck in a Boot Loop. Tried Cold Reset but it didn't work.
I did get the green progress bar at start up, but keep returning to the eee pad splash screen. cant boot to android.
Any advise?
Install TWRP recovery
Hi,
I downloaded "signed_twrp-2.8.1.1_tf101.zip", but I don't understand how to install it.
When I use TWRP manager, I get a list of TWRP version up to 2.3 only.
When I try to use adb & fastboot command tools, it seems I cannot enable fastboot on the TF101 : Running "adb reboot bootloader" actually restarts the device in the normal mode.
Can you please help me with this? How can I install TWPR 2.8?
Thanks!
how to install twrp in TF101G
Hi I have i TF101G but doesn't work 3G, the sim card is not dectected. Any Help?
I have root and Cmw recovery? How I install TWRP recovery? I need a guide, help me!
To those guys who were having issues getting twrp 2.8.1 on their tf101, I was having same problem. Here is how I got it to work.
1. Download all the 5.1 Roms, Gapps, SuperSu onto your SD Card
2.Download the tf101 TWRP 2.8.1 onto your SD Card.
3. Use Easy Flasher Unbrick/Flash Stock and Boot into Android. Shut down.
4. Use Easy Flasher to load the older version of TWRP that works.
5. Boot into Android, shutdown at the start screen again.
6. Boot into Recovery, and flash the latest TWRP 2.8.1
7. Make sure your tablet is disconnected from USB, and reboot into Android, it should say optimizing App 1 of 1.
8. After you're in the start screen, reboot again into recovery. It should now be 2.8.1.
9. Install the 5.1 Rom off your SD.

[Q&A] [RECOVERY][TF700T] TWRP 2.8.3.0 touch recovery [2014-12-22]

Q&A for [RECOVERY][TF700T] TWRP 2.8.3.0 touch recovery [2014-12-22]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][TF700T] TWRP 2.8.3.0 touch recovery [2014-12-22]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
where is the link?
1122qqww said:
where is the link?
Click to expand...
Click to collapse
Here: http://www.teamw.in/project/twrp2/105
I strongly recommend installation using the fastboot method, as the apps are reported to work poorly or not at all.
TWRP 2.8.5.0 Won't Boot
I just installed TWRP 2.8.5.0 on my TF700T via the fastboot method (since TWRP Manager fails to install it). However, when I attempt to boot the recovery, the device locks up. This is different behavior than 2.8.4.0, which had a kernel panic and rebooted the device. Any idea how to go about debugging, or should I simply try older recoveries / wait until a newer one comes out?
N1FFO said:
I just installed TWRP 2.8.5.0 on my TF700T via the fastboot method (since TWRP Manager fails to install it). However, when I attempt to boot the recovery, the device locks up. This is different behavior than 2.8.4.0, which had a kernel panic and rebooted the device. Any idea how to go about debugging, or should I simply try older recoveries / wait until a newer one comes out?
Click to expand...
Click to collapse
My self-built one works fine. Can anyone else reproduce this problem with TWRP 2.8.5?
_that said:
My self-built one works fine. Can anyone else reproduce this problem with TWRP 2.8.5?
Click to expand...
Click to collapse
Nope!
Just dd'd 2.8.5.0 onto tf700. Flashed and works tadellos.
Works Now
das chaos said:
Nope!
Just dd'd 2.8.5.0 onto tf700. Flashed and works tadellos.
Click to expand...
Click to collapse
Naturally, the dd method is the one method I didn't try. So I just did, and it works now. I did have to perform a normal reboot to complete the installation (as opposed to rebooting directly into recovery), but the instructions mentioned that (although they didn't specify that the reboot needed to be a normal one). So all is well now, and I can move on to installing ZOMBi-Pop, my main goal all along.
Makes me wonder why TWRP and fastboot failed, but oh well.
N1FFO said:
Makes me wonder why TWRP and fastboot failed, but oh well.
Click to expand...
Click to collapse
These methods also require reboot to system not to recovery.
das chaos said:
These methods also require reboot to system not to recovery.
Click to expand...
Click to collapse
I can believe that for fastboot, but TWRP Manager claimed that the flashing failed. On my OnePlus One, TWRP Manager flashed the recovery just fine. Is the claimed failure just a caveat of flashing on the TF700T, and the new recovery will actually work despite it if you perform a system reboot afterwards? I think I'll try that next when the next version comes out, just to see.
N1FFO said:
I can believe that for fastboot, but TWRP claimed that the flashing failed. On my OnePlus One, TWRP flashed the recovery just fine. Is the claimed failure just a caveat of flashing on the TF700T, and the new recovery will actually work despite it if you perform a system reboot afterwards? I think I'll try that next when the next version comes out, just to see.
Click to expand...
Click to collapse
Did you try to flash the twrp.blob in recovery?
That won't work unless you put the blob into a flashable zip.
Oh, re-reading your post you probably mean it failed in TWRP Manager. You take your chances with these apps. Don't use them...
berndblb said:
Did you try to flash the twrp.blob in recovery?
That won't work unless you put the blob into a flashable zip.
Oh, re-reading your post you probably mean it failed in TWRP Manager. You take your chances with these apps. Don't use them...
Click to expand...
Click to collapse
You're right, I meant TWRP Manager. Thanks for pointing that out, I edited the previous post to reflect that.
berndblb said:
Oh, re-reading your post you probably mean it failed in TWRP Manager. You take your chances with these apps. Don't use them...
Click to expand...
Click to collapse
That bricked my first tf300t!
Repeat:
Don't ever use TWRP Manager or Goo Manager for flashing recovery.
das chaos said:
That bricked my first tf300t!
Repeat:
Don't ever use TWRP Manager or Goo Manager for flashing recovery.
Click to expand...
Click to collapse
+1
add Flashify to the list. Or make that: apps in general
Fastboot or dd command is the way to go
Never mind, thanks
Never mind
Bgecko
USB OTG not working on htc one m7
USB keyboards not work on htc one m7 that support USB host mode via a USB OTG cable noooooooot work
openrecovery-twrp-2.8.5.0-m7.img
Can anyone turn this into a zip for me?
TLR - I think if I can get a zip of the latest TWRP I can get myself out of a nasty bootloop
I seem to have gone and bricked my Infinity while under the influence...
Installed new rom.
Decided to factory reset.
During format there was an error, and E: data no longer mountable (didn't realize this at the time)
Bootloop
Read some things online and thought maybe I didn't have the right TWRP
Installed a new recovery that was "compatible" with the rom I was installing
It was Philz cwm (freaked out)
Read a post that said I could force the tablet to re-format the :data partition from TWRP by using the terminal command "mke2fs -T ext4 /dev/block/mmcblk0p8" BUT can't run a terminal command from cwm
Can't find a way to enter fastboot to put twrp back onto transformer (No option for usb)
jbjcurly said:
Can't find a way to enter fastboot to put twrp back onto transformer (No option for usb)
Click to expand...
Click to collapse
Read this:
http://forum.xda-developers.com/showthread.php?t=2688891
Problem solved!
_that said:
Read this:
http://forum.xda-developers.com/showthread.php?t=2688891
Click to expand...
Click to collapse
Thanks _that! I actually used a flashable version of your twrp recovery (2.6.3 maybe?) that I found, followed the plan I outlined above, and all is now well.
Where to get TWRP 2.8.6.0 for TF700T
Does anyone know where a TWRP 2.8.6.0 .img for the TF700T can be found? It's not available on the official website (actually, NOTHING for the TF700T is available on the offcial website).
Alternatively, does anyone know where a patched version of 2.8.50 that supports f2fs can be found? Or should I revert to 2.8.4.0?
Eh, maybe I'll just build 2.8.6.0 myself. How hard can it be?
Slightly harder than finding the Kang TWRP 2.8.6 by lj in the dev section I would think....

At&t 1.27.502.5 Stock system.img or Stock system twrp backup needed!!!

I could really use either one of these files to fix my phone, anybody out there able to help me out? I'm more than willing to pay you for your time/effort!
d34thbl00m said:
I could really use either one of these files to fix my phone, anybody out there able to help me out? I'm more than willing to pay you for your time/effort!
Click to expand...
Click to collapse
Have a look there. You can fin a complete RUU from AT&T
http://www.htc.com/us/support/rom-downloads.html
ouioui01 said:
Have a look there. You can fin a complete RUU from AT&T
http://www.htc.com/us/support/rom-downloads.html
Click to expand...
Click to collapse
I know where to find the RUU files, however that is NOT what I need. Hence the thread title.
d34thbl00m said:
I know where to find the RUU files, however that is NOT what I need. Hence the thread title.
Click to expand...
Click to collapse
I
You can extract from RUU the system.img with RUU decrypt tool from there: http://forum.xda-developers.com/one-a9/development/decrypt-ruu-ruu-decryption-script-htc-t3282562
cheers
ouioui01 said:
I
You can extract from RUU the system.img with RUU decrypt tool from there: http://forum.xda-developers.com/one-a9/development/decrypt-ruu-ruu-decryption-script-htc-t3282562
cheers
Click to expand...
Click to collapse
That thread said you need linux, I have a Surface Pro and can't dual boot, so not sure how to run a linux distro? I have made some progress, I was able to pull rom.zip from an RUU and rename that to 2PQ9IMG.zip and put it on the root of my sdcard. When I rebooted into download mode much to my surprise the RUU ran and was successful. So I reinstalled twrp, but it STILL will not let me wipe data to remove encryption. My /data is unmountable, and every time I try to do a wipe in twrp it returns the error "unable to mount storage". Twrp is also still giving me the "No OS Installed" message when I go to reboot. Is there another way to remove encryption without using linux? Or a way I can setup linux on my Surface? I just need to get root so I can s-off...
d34thbl00m said:
That thread said you need linux, I have a Surface Pro and can't dual boot, so not sure how to run a linux distro? I have made some progress, I was able to pull rom.zip from an RUU and rename that to 2PQ9IMG.zip and put it on the root of my sdcard. When I rebooted into download mode much to my surprise the RUU ran and was successful. So I reinstalled twrp, but it STILL will not let me wipe data to remove encryption. My /data is unmountable, and every time I try to do a wipe in twrp it returns the error "unable to mount storage". Twrp is also still giving me the "No OS Installed" message when I go to reboot. Is there another way to remove encryption without using linux? Or a way I can setup linux on my Surface? I just need to get root so I can s-off...
Click to expand...
Click to collapse
Did you try flashing the A9 boot patcher which is in the TWRP recovery thread (5 in second post). which version of TWRP are you using ?
Cheers
ouioui01 said:
Did you try flashing the A9 boot patcher which is in the TWRP recovery thread (5 in second post). which version of TWRP are you using ?
Cheers
Click to expand...
Click to collapse
No I haven't, I'll check it out. I'm using TWRP 3.0.0.
ouioui01 said:
Did you try flashing the A9 boot patcher which is in the TWRP recovery thread (5 in second post). which version of TWRP are you using ?
Cheers
Click to expand...
Click to collapse
Boot patcher failed, like just about everything I try, and returned with an "unable to mount storage" error. I'm stumped. I think it's weird that an official RUU fails with "os-version in Android-file is missing or invalid" error but rom.zip pulled from an official RUU goes through just fine.
If want get root , device boot into twrp "Wipe/Format Data" then back to "Reboot/recovery" install root.zip.
Sorry my bad english!!
d34thbl00m said:
No I haven't, I'll check it out. I'm using TWRP 3.0.0.
Click to expand...
Click to collapse
There was a bug in twrp 3.0.0. The last release is: Current Stable Version: 3.0.0-1
Install the last release and then try in twrp :Wipe/Format Data. Hope it will work for you...
Cheers

Categories

Resources