Database Info

[Q] Help! Think I bricked my TF101!

I have one of the newer TF101's (B90). I had the Revolver ROM installed on it. I encrypted the tablet. I attempted to install the stock ROM back on the device, which also wiped out CWM and reinstalled the stock recovery. Here's the thing: The original password I had does not work on the device anymore, and the tablet is seemingly still encrypted. I cannot boot into UPX (probably due to the HW version), and the recovery ROM only displays the ! graphic.
Is there anything I can do?

whatexcusenow said:
I have one of the newer TF101's (B90). I had the Revolver ROM installed on it. I encrypted the tablet. I attempted to install the stock ROM back on the device, which also wiped out CWM and reinstalled the stock recovery. Here's the thing: The original password I had does not work on the device anymore, and the tablet is seemingly still encrypted. I cannot boot into UPX (probably due to the HW version), and the recovery ROM only displays the ! graphic.
Is there anything I can do?
Click to expand...
Click to collapse
You need to wipe the data partition. This isn't windows. This is android. In windows, you have 1 big partition so reinstalling the OS kills everything. In android, there are over a dozen different partitions. Installing a new OS doesn't touch the data partition. And since revolver is based on the stock, some data will still work in the stock, like your encryption.
You need to nvflash in the cwm and use it to wipe the data.

goodintentions said:
You need to nvflash in the cwm and use it to wipe the data.
Click to expand...
Click to collapse
but he has a B90 so no NVFlash

Oh, didn't see that part.
I am constantly amazed at people refusing (for religious reason or whatever reason) to wipe data before flashing another rom and then complain that something is wrong.
Someone else might be able to help. In the mean time, let me think about this one.

You can follow the Unroot Process, which will wipe /Data (also your /SDCARD) - you're already through the first part since you have the stock recovery installed.
Just download the stock firmware from Asus' website and follow the instructions in the "Updated Version of SOP" manual (also from Asus' website) - it involves using an micro-sd card and extracting the stock firmware to it, then booting to Recovery. The stock recovery should automagically find the firmware update and flash it.
Edit: Edited for clarity, and added a link to the download's page - http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+TF101&p=20&s=16

hold vol down, wait until it asks about data wipe, press vol up, wait a few minutes while it does the datawipe

Corrupt internal SD Card

Hi Folks.
Ok here is my situation, I have a rooted and unlocked TF700.
I flashed Zeus 4 and all worked well, then flashed (after full wipe) PARANOIDANDROID 2.15 and again everything was great,
Yesterday I flashed Baked Bean 4 (again after a full wipe) and apart from some SD issues all seemed ok,
I then decided to restore my TWRP backup of Zeus as I needed to use my 64gig msd card.
After a full wipe and restore Zeus started up but the dpi was messed up (160) I think (way small)
I was seeing loads of FC's and file manager showed my internal SD as being empty. Rebooted to recovery and tried the "Format Data" option
It failed right away with this message "E: Unable to format data."
I have tried flashing the stock .26 rom via TWRP and I have the same issue, dpi set to 160 and internal sd not mounted.
It seems my Internal sd is corrupt
What is the procedure to reformat it via ADB or fastboot? (I have searched but the results I found relate to other devices and I dont want to simply follow instructions that might cause further harm to my TF700)
I have followed the NVflash brick proof procedure and have all relevant files backed up (I did this before flashing the last 2 roms)
Please can some one point me in the right direction
Thanks a lot
Jules

I always wipe cache, system, internal, davic and then do a factory reset.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app

When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right? What rom you have on your device right now?

Pretoriano80 said:
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right. What rom you have on your device right now?
Click to expand...
Click to collapse
Yip extracted the zip from the zip file and copied it to my ext sd and flashed it via TWRP
I have an unusable Zeus4,
Im about to try a full wipe again and then flash .26 again
EDIT
After flashing .26 and selecting reboot I get the "No OS installed! Are you sure you wish to reboot?" message

Looks like the system partition is corrupted, but i'm not sure. I think you should come here on IRC and maybe someone with more experience will help you - - http://webchat.freenode.net/?channels=asus-transformer

Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:

ZaJules said:
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
Click to expand...
Click to collapse
This same thing happened to me with my Prime when I was getting ready to send it off for RMA because of a broken HDMI port. Since I was unlocked I was advised to restore to stock before sending it in. However, before I got the chance to do that I started getting the "E: Unable to format data." error that you were. I ended up erasing all partitions from fastboot and putting a note in the box that it wouldn't boot after an OTA. I managed to get away with it and wasn't charged for fixing it
For future reference it would be really helpful to know how you fixed this. Did you do something like what is in this thread: http://forum.xda-developers.com/showthread.php?t=1803343.
Did you ever figure out how CM10 messed up your Infinity? I was running CM9 on my Prime when I got this error. Thanks!

It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.

Pretoriano80 said:
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Click to expand...
Click to collapse
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?

paddycr said:
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
Click to expand...
Click to collapse
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.

Pretoriano80 said:
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Click to expand...
Click to collapse
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.

okantomi said:
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
Click to expand...
Click to collapse
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...

Pretoriano80 said:
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Click to expand...
Click to collapse
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.

okantomi said:
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
Click to expand...
Click to collapse
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.

Pretoriano80 said:
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Click to expand...
Click to collapse
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.

okantomi said:
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
Click to expand...
Click to collapse
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...

Pretoriano80 said:
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Click to expand...
Click to collapse
I'm using TWRP 2.2.2.1, I back up boot, system and data only, and I don't use compression.

[Q] stuck in boot with CM rom and with back-up rom

Hello,
my tf700 doesn't finish the boot after I've installed CM.
Before flashing a new rom I've tried to make a system back-up from GooManager.
I don't know if the back-up is fully functional because in the "Breaking back-up in multiple archives" it has remained stuck at 100% (or complete progress bar) for like an hour.
After an hour or so I've interrupted the back-up process and entered the TWRP Recovery v2.5 (which I'm still able to access at the moment) and tried to flash a ROM downloaded by GooManager (cm-10.0.0-tf700t.zip). I've wiped the Dalvik cache and Cache in the process.
The flash seemed to be successful but the reboot doesn't finish, even though I've let it for two hours or so.
After that I've reentered the TWRP and tried a different rom cm-10.1-20130513-NIGHTLY-tf700t.zip, but with similar result, after installation it doesn't finish the boot.
I've reentered the TWRP and tried restoring the back-up. It did restored the system, passed the "configuring application" stage and gave the message "Finishing boot" and nothing afterwards, it just stuck in the process.
Right now I'm still able to enter TWRP, and navigate through the folders on the tablet, but I don't have a functional rom.
Can you please help me with some advices?
Thank you.

Which ROM did you have before, and which bootloader version?

_that said:
Which ROM did you have before, and which bootloader version?
Click to expand...
Click to collapse
Before that I had the stock ROM with the latest OTA firmware from Asus.
I don't know what was the initial version of the bootloader.
I've unlocked the device using Asus apk
I've pushed the TWRP on the tablet using the TF700T-ADB- Tool v3
I've granted super user rights from TWRP, I think using SuperUser application.
Ive installed from market GooManager and after that I've done what I've described in the previous message.
Thanks for your prompt answer.

Maybe CM is confused by existing data - did you wipe data (factory reset) as written in the CM instructions?

_that said:
Maybe CM is confused by existing data - did you wipe data (factory reset) as written in the CM instructions?
Click to expand...
Click to collapse
No, I didn't. I've just wiped the Dalvik cache and Cache.
If I do wipe data, I will still have user data, like downloaded ZIP ROMs or GAPPS zip?
I mean, at the moment I'm still able to try different ROMs and kind of operate the tablet. If I do wipe the data and is something wrong with the flash will I be able the try something else? Before I wipe existing data should I take other precautions?

Mihai_Preda said:
No, I didn't. I've just wiped the Dalvik cache and Cache.
If I do wipe data, I will still have user data, like downloaded ZIP ROMs or GAPPS zip?
I mean, at the moment I'm still able to try different ROMs and kind of operate the tablet. If I do wipe the data and is something wrong with the flash will I be able the try something else? Before I wipe existing data should I take other precautions?
Click to expand...
Click to collapse
From what I've read (but never tried myself), a "Factory Reset" is supposed to delete all your apps, app data and system-specific data, but not the contents of your internal emulated SD card. Your ROM and recovery are definitely not affected. But I'd wait until someone else can confirm.

It seems strange that the back-up isn't fully working either, it gets stuck after "Finishing boot".
I've noticed somtheing while flashing the two CM ROMs. On the instalation, of each of the two, it was a message that the MD5 is being checked, and after that that MD5 is missing and the check is being skipped. The instalation did continued and the message "Instalation succesful" was given.
But I don't know if it's alright not findind the MD5.

_that said:
From what I've read (but never tried myself), a "Factory Reset" is supposed to delete all your apps, app data and system-specific data, but not the contents of your internal emulated SD card. Your ROM and recovery are definitely not affected. But I'd wait until someone else can confirm.
Click to expand...
Click to collapse
I've checked on other sources and the wipe data seems to leave intact the user data.
But I'm still wondering at what state the tablet will be reseted since I've tried flashing to different ROMs and the back-up restore didn't work quite properly.
The last functioning ROM is still available from other means that restore back-up (which doesn't work) even though I've tried flashing new ROMs over it?

Mihai_Preda said:
On the instalation, of each of the two, it was a message that the MD5 is being checked, and after that that MD5 is missing and the check is being skipped. The instalation did continued and the message "Instalation succesful" was given.
Click to expand...
Click to collapse
The missing MD5 file is not a problem. If it says "installation successful", you can assume that it is.
Mihai_Preda said:
I've checked on other sources and the wipe data seems to leave intact the user data.
But I'm still wondering at what state the tablet will be reseted since I've tried flashing to different ROMs and the back-up restore didn't work quite properly.
The last functioning ROM is still available from other means that restore back-up (which doesn't work) even though I've tried flashing new ROMs over it?
Click to expand...
Click to collapse
Your backups not working is somewhat strange, but that's another area where I have very limited experience.
You said you were on the "latest OTA" stock ROM. Was that 10.4.4.25 (Android 4.1) or 10.6.1.14.4 (Android 4.2)? Also check the bootloader version - boot into the bootloader menu with holding volume-left, then read the tiny text near the top of the screen. It should contain the build number of your bootloader, which is identical to the build number of the stock ROM until you flash one of them separately.

_that said:
You said you were on the "latest OTA" stock ROM. Was that 10.4.4.25 (Android 4.1) or 10.6.1.14.4 (Android 4.2)? Also check the bootloader version - boot into the bootloader menu with holding volume-left, then read the tiny text near the top of the screen. It should contain the build number of your bootloader, which is identical to the build number of the stock ROM until you flash one of them separately.
Click to expand...
Click to collapse
It's Android 4.2.1: "Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.4-20130329" A03"
Right now the tablet is left with the attempted back-up recovery. Should I enter TWRP and do the wipe data or wipe data from the bootloader menu?
Or is something else that I should do first?

Ok, I did wipe the data, and even though it erased the user data too (media, docs, zip files etc) it restore the tablet to cyanogen mode not the original stock ROM. It finished the boot restore my gmail account. SuperUser is updated. And it seems the overall responsiveness is better.
Thank you for your time and advice!

Mihai_Preda said:
It's Android 4.2.1: "Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.4-20130329" A03"
Right now the tablet is left with the attempted back-up recovery. Should I enter TWRP and do the wipe data or wipe data from the bootloader menu?
Or is something else that I should do first?
Click to expand...
Click to collapse
OK, your bootloader is the latest one, and it works with Android 4.1 and 4.2 ROMs. There have been several reports of unrecoverable bricks after using "wipe data" from the bootloader menu with a broken or incompatible recovery - so even if your recovery works fine, I would not recommend to take any unnecessary risk.
If you have any important data on your device it would be a good idea to store a backup on an external microSD card, just in case you do wipe all data by accident or something unexpected happens.

_that said:
OK, your bootloader is the latest one, and it works with Android 4.1 and 4.2 ROMs. There have been several reports of unrecoverable bricks after using "wipe data" from the bootloader menu with a broken or incompatible recovery - so even if your recovery works fine, I would not recommend to take any unnecessary risk.
If you have any important data on your device it would be a good idea to store a backup on an external microSD card, just in case you do wipe all data by accident or something unexpected happens.
Click to expand...
Click to collapse
I'm surprised that after wipe data procedure it restored the system to a cyanogen mode not the original rom. I'm surprised by this because the last functional ROM was the stock one and because after flashing the last zip with CM ROM I've tried to restore the back-up ROM. Even though it didn't finish the boot, this back-up seemed to be installed over the previous CM ROMs. I'm not sure what happened, why I do have a CM ROM functioning, even though I did tried to install it I don't know why it managed to be installed.
If you have little more time and you know what happened here please let me know.
Thank you again!

Mihai_Preda said:
I'm surprised that after wipe data procedure it restored the system to a cyanogen mode not the original rom. I'm surprised by this because the last functional ROM was the stock one and because after flashing the last zip with CM ROM I've tried to restore the back-up ROM. Even though it didn't finish the boot, this back-up seemed to be installed over the previous CM ROMs. I'm not sure what happened, why I do have a CM ROM functioning, even though I did tried to install it I don't know why it managed to be installed.
Click to expand...
Click to collapse
The ROM and your data are completely separate. If you install a ROM and it says "install successful", the ROM is installed. "Wipe data" does not touch the ROM. However your data can prevent the ROM from starting up correctly. Apparently the restore fixed something in your data partition so that the last ROM that you installed can now boot.

_that said:
The ROM and your data are completely separate. If you install a ROM and it says "install successful", the ROM is installed. "Wipe data" does not touch the ROM. However your data can prevent the ROM from starting up correctly. Apparently the restore fixed something in your data partition so that the last ROM that you installed can now boot.
Click to expand...
Click to collapse
That means the TWRP didn't actually restore the ROM from back-up even if it did say the restore was successful...The last installed ROM was a CM one.
Thanks for the help!

[Q] I can't get any 4.3 roms to work.

Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.

ajh305 said:
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
Click to expand...
Click to collapse
you tried 6.0.3.5 cwm also?
i had the same problem and this was the only one i could get to work.

bweN diorD said:
you tried 6.0.3.5 cwm also?
i had the same problem and this was the only one i could get to work.
Click to expand...
Click to collapse
Ya i tried every cwm including 6.0.3.6 and twrp 2.0.6.1

ajh305 said:
Ya i tried every cwm including 6.0.3.6 and twrp 2.0.6.1
Click to expand...
Click to collapse
not sure if it will help but this is the exact process i used:
-rts using matts utility found here http://batakang.com/dr_utility.php
-put stock recovery back on using the above utility
-root with the above utility and protect with voodoo
-take the ota to get the latest baseband back (will likely fail but still update the bb)
-restore root
-install cwm 6.0.3.5 from this utility http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
-flash your 4.3 rom of choice
-profit (hopefully lol)

ajh305 said:
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
Click to expand...
Click to collapse
keep in mind the second boot on 4.3 roms seems to take a while, how long is it hanging on the boot screen? I remember the first 4.3 I flashed hung for about 5-8 minutes before it booted up. it seems to be the second one that hangs consistently for me, but it does always boot. All following reboots after the 2nd are normal with no hangs.

bjoostema said:
keep in mind the second boot on 4.3 roms seems to take a while, how long is it hanging on the boot screen? I remember the first 4.3 I flashed hung for about 5-8 minutes before it booted up. it seems to be the second one that hangs consistently for me, but it does always boot. All following reboots after the 2nd are normal with no hangs.
Click to expand...
Click to collapse
I think I have waited for about 10 minutes before. I'll try again and see if it does actually boot. Does your hang on the bootloader unlocked screen or the boot animation screen?
EDIT: I tried another 4.3 rom and booted it up. Set some things up then updated su binaries and restarted and let it sit there at the unlocked bootloader warning for 15 minutes with no changes.

bweN diorD said:
not sure if it will help but this is the exact process i used:
-rts using matts utility found here http://batakang.com/dr_utility.php
-put stock recovery back on using the above utility
-root with the above utility and protect with voodoo
-take the ota to get the latest baseband back (will likely fail but still update the bb)
-restore root
-install cwm 6.0.3.5 from this utility http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
-flash your 4.3 rom of choice
-profit (hopefully lol)
Click to expand...
Click to collapse
I did actually restore it back to completely stock, recovery and everything. I downloaded the OTA after rooting and using voodoo. The update failed but I installed cwm 6.0.3.6 and then restored my backup. Then I flashed twrp 2.0.6.1 to try that and flashed a 4.3 rom and same issue came up.

ajh305 said:
I think I have waited for about 10 minutes before. I'll try again and see if it does actually boot. Does your hang on the bootloader unlocked screen or the boot animation screen?
Click to expand...
Click to collapse
Yeah, mine hangs at the bl unlocked screen on that second boot, though I flashed a different logo to get rid of that annoying message 10 minutes seems a bit excessive but not unheard of-longest I clocked was around 8. Does yours ever make it to the boot animation? If so, it should go into a full boot eventually. I think the hang has something to do with the rom building cache on that second boot Also, whichever 4.3 your using, I would make sure it's a more recent release as they have come a very far since the early releases which hung for longer periods of time. I'm currently running pa rc2 by cj and it went smoothly using cwm 6.0.3.2.

bjoostema said:
Yeah, mine hangs at the bl unlocked screen on that second boot, though I flashed a different logo to get rid of that annoying message 10 minutes seems a bit excessive but not unheard of-longest I clocked was around 8. Does yours ever make it to the boot animation? If so, it should go into a full boot eventually. I think the hang has something to do with the rom building cache on that second boot Also, whichever 4.3 your using, I would make sure it's a more recent release as they have come a very far since the early releases which hung for longer periods of time. I'm currently running pa rc2 by cj and it went smoothly using cwm 6.0.3.2.
Click to expand...
Click to collapse
It never reaches the boot animation just sits at that screen. I have tried several 4.3 roms within the last few days so they are the newest versions I can find. Could I clear the cache to get it to boot?

ajh305 said:
It never reaches the boot animation just sits at that screen. I have tried several 4.3 roms within the last few days so they are the newest versions I can find. Could I clear the cache to get it to boot?
Click to expand...
Click to collapse
http://www.droidrzr.com/index.php/topic/27682-having-issues-with-43-roms-is-it-me/ check out the last post on the page in that link. It seems to have worked for that guy. If you don't mind, try that and let me know if it works. In the meantime, I'm going to try and find some more solutions. I'm assuming his method worked, as he hasn't posted back.

bjoostema said:
http://www.droidrzr.com/index.php/topic/27682-having-issues-with-43-roms-is-it-me/ check out the last post on the page in that link. It seems to have worked for that guy. If you don't mind, try that and let me know if it works. In the meantime, I'm going to try and find some more solutions. I'm assuming his method worked, as he hasn't posted back.
Click to expand...
Click to collapse
By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot

ajh305 said:
By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot
Click to expand...
Click to collapse
Awesome man! I'm glad it booted up for you welcome to the 4.3 side!

ajh305 said:
I did actually restore it back to completely stock, recovery and everything. I downloaded the OTA after rooting and using voodoo. The update failed but I installed cwm 6.0.3.6 and then restored my backup. Then I flashed twrp 2.0.6.1 to try that and flashed a 4.3 rom and same issue came up.
Click to expand...
Click to collapse
glad you got it fixed but i have to ask, in the sequence above why are you restoring a backup? you should be going right from stock to 4.3. also, some people have issues with twrp and 4.3, thats why i suggested cwm.

I'm not sure why I restored the backup. I didn't think coming from stock would work for some reason.
Sent from my XT926 using xda app-developers app

I am having the same problem. I have followed the steps but still no joy . Any thoughts?

sgtslaughter64 said:
I am having the same problem. I have followed the steps but still no joy . Any thoughts?
Click to expand...
Click to collapse
This was the only thing that worked for me. You could maybe try updating to the most current recovery instead of the one listed.

the only 2 issues i have seen to cause this problem are covered in the post a few below, and fixed it every time. my only suggestion would be to install cwm after rooting, then reboot, then continue with the steps. just my preference, it may not matter.

[Q] TF700 Cromi-x crash - need steps to restore

Thanks for your help. First time tab crash.
I was cruising along fine still on Cromi-x 5 and that's Kernel, just the very basic stuff.
For unknown reason tabled stuck on boot after first run of Ccleaner, don't think technically it's a boot loop. I can get to TWRP menu. Tried backup, wipe and re-installed last save cromi-x version I had on micro sd, 4.3 or whatever.
Seemed to install ROM fine as I got to home screen and then PlayStore wanted to reinstall 50 million apps which would take a day or two. I tried to restore Data from backup but no joy as this was probably bad idea.
Anyway, assuming I can get to TWRP what "This Than That" Steps do I take to get up and running from TWRP menu?
Possibly time to go with KK or Zombi I imagine. Dont care about lost data of tablet.
I downloaded TWRP 2.6.3 to PC as well as Cromi-KK and ASUS Apps just now. I also have all Cromi-X ROMS thru 5.2.4 on PC if easier to go there vs KK or whatever.
Basic explaination/path appreciated.
Thanks very much

First you need to make sure that your bootloader is 10.6.1.14.10 or .8
Then you need to flash TWRP 2.8.x
Then you go to Wipe > Advanced in TWRP and select everything except the microSD.
Then you flash CROMBi-KK or ZOMBi-X or whatever you desire.
Profit

OK, thank you much. I'll give it a go.

Thanks, managed to work on prev twrp ver. Couldnt sort out how to flash 2.8
Flashed Zombi and asus apps and trying it out. Havent read much on it so have homework.
Where is setting to keep screen on when power plugged in.?