Database Info

Stucked on rebooting loop using Prime v 1.9.1

Hello everyone,
First i know this is the general Q&A but since i do not post often [ever] i can't post directly to the development forum for the Prime [ROM]
My Transformer is a B6 model
So here is my issue, I installed Prime about 4 days ago was working fine no problems, and just today (silly of me) i realized that the time zone for the table was at default (don't remember what it was) i think UTC - 0, in any case i went ahead and changed that to Eastern didn't install anything new other the amazon market app.
In any case the table was working fine but as soon as it went to sleep it got locked into a rebooting mode it will perform the mem check and POST, it completes initialization but when it reaches "Activating root access..." it reboots and the cycle repeats.
I can obviously re-flash it and get back to working order but is a rather a unusual error, by the way i do have APX access.
Any ideas?
Thank you very much

Cheers for posting in the correct section dude. You have a problem, you are asking a question.
Thanks for not cluttering up the DEV threads with this.
Have you tried a cold boot?
Also, boot into CWM and clear the caches
Still havin probs? then reinstall the rom and see what happens
Cheers
CaNsA

XRACER said:
Hello everyone,
First i know this is the general Q&A but since i do not post often [ever] i can't post directly to the development forum for the Prime [ROM]
My Transformer is a B6 model
So here is my issue, I installed Prime about 4 days ago was working fine no problems, and just today (silly of me) i realized that the time zone for the table was at default (don't remember what it was) i think UTC - 0, in any case i went ahead and changed that to Eastern didn't install anything new other the amazon market app.
In any case the table was working fine but as soon as it went to sleep it got locked into a rebooting mode it will perform the mem check and POST, it completes initialization but when it reaches "Activating root access..." it reboots and the cycle repeats.
I can obviously re-flash it and get back to working order but is a rather a unusual error, by the way i do have APX access.
Any ideas?
Thank you very much
Click to expand...
Click to collapse
Hi, I doubt that changing the timezone would have a negative effect on your transformer so I'm wondering if maybe something else causes this. Maybe some app that doesn't like the TZ to be changed or maybe even something completely unrelated. Can you get a logcat of the problem and it might help to shed some light on this problem you are experiencing?

you probably have a bad download. Redownload the Tom and try again.
Redownloading the Rom would be better though...oopps

Hello everyone,
thanks for the quick reply, although i am familiar with computers in general i am not very familiar with the android platform.
How do i get it if the system keeps rebooting every 5-7 seconds? or is by default created when the system reboots?
I have been reading through the android dev tools and it needs to be access via adb, i am not very familiar with this environment. Any guidance will be appreciated.

power on with power / vol - and when it says to hit vol up. Yhis will boot you into CWM. Clear dalvik and cache and reboot. If that doesnt work then just flash the rom again. If that doesnt work then wipe data.

thebadfrog said:
power on with power / vol - and when it says to hit vol up. Yhis will boot you into CWM. Clear dalvik and cache and reboot. If that doesnt work then just flash the rom again. If that doesnt work then wipe data.
Click to expand...
Click to collapse
Hello,
Thanks for the reply, i have already try, all of the above mentioned steps, except for the last one i am not really sure what you mean (If that doesnt work then wipe data)
Also i attempted to install another rom (revolver) in this case since it hides the POST procedures it just shows the eee Pad and Asus logo for about 7-10 secs and then reboots

There is an option in CWM that wipes data/factory reset. It wont wipe your personal folders or your external sdcards but it will reset the system back to the beginning and remove all your apps which you have to reinstall

thanks i also did that as a last ditch effort, yet nothing.
hmmm... i refuse to believe my tablet is bricked.
What i will try to do is restore to stock 3.1 and see if that works.
it just seems weird that it was working with no issues until i modified the TZ.
But thanks, and i will give the reset one more try.
----Update----
On a side note.
when in recovery mode i have tried the restore option, but it keeps giving me
E:Can't mount /sdcard
i do presume that is the internal memory where the recovery image is located am i right?
--------------------------Update 2--------------
So i went ahead and nvflash with stock 3.1 that got me back in to working mode, however when attempting to go into the recovery meny it seems something got messed up.
First the prime animation shows up (although i have flashed, revolver and stock on top of that)
then the android logo shows up with a warning triangle on his chest, i guess that is the typical something is wrong here logo.
and then nothing no access to recovery.
So i am trying to flash this one more time, let see if that fixes the issues.
---------------Update 3----------------
well that got me no where :S
i flashed the system with revolver 3.2 via nvflash and i am back to the rebooting loop.
I will wait to see if any of you guys have some ideas, in order to further proceed

Sorry to keep asking.
Does any one have any idea how to resolve this?
Also Roach you mention a log dump, could you please let me know how i can get this log.
thank you.

I know this doesn't help all of your problems, but people have reported having trouble with the nvflash version of Revolver. (myself included) I would recommend, because this is always what works for me when I soft-brick my tablet, nvflashing the latest version of Prime again. Assuming it boots successfully, you can always put the normal version of Revolver on your sdcard, reboot into Recovery, wipe data, and then install Revolver from there.
I hope something works for you soon
Sent from my DROIDX using Tapatalk

Well it seems that did the job.
Although weird why the issue happened in the first place, well i would like to thank everyone who replied. Next time i will keep a rom on my sdcard all the time :-D.
Also thanks XDA And all the community in here.
Sent from my transformer using XDA Premium. (Revolver ROM)

TF101 in boot loop

Guys, wondering if someone could give me some direction to restoring my TF101 to working conditions.
I have a rooted TF101 that was running 9.1.2.27.
This setup has been running great since .27 (not done OTA, Found here) came out, so I haven't bothered upgrading recently.
Fast forward to this week and it seems the Tablet started locking up at some point in the last couple days I hadn't used it. This would cause a battery drain until the device turned off. Upon rebooting I could get into the OS for maybe a minute before it would freeze again.
I decided to wipe the device, I went into CWM Recovery and wiped all caches and then tried to wipe all data/factory reset. It is at this time I get the following error:
Error removing /data/data/com.android.browser/databases/webview.db-wal!Error formatting /data!
Try starting back up and get a boot loop.
Upon reflashing the ROM, I find the TF101 in constant boot loop not making it 8 seconds into the bootup before rebooting.
I can still get into recovery so I try various kernels and roms with no success. Through searching I find CWM 6.0.1.4 and load it. Everything loads normally and I can now wipe data/factory reset, wipe all Cache even format all parts. I try to flash every ROM I can get my hands on from stock to older roms that I have ran succesfully to EOS Nighties, Every rom goes into Boot Loop after about 10 seconds.
Any Idea on where to go from here? I have been reading threads for hours now with no solution.
MODS: Putting in DEV since this is a Rooted TF, but if this should go to Q&A please move

This question should be in the QA section...
But your stock ROM was ICS and the newest EOS nightlies are based on JB which have different partitions. If you flash back and forth with ICS and JB you could be running into problems there.
Have you tried the option in CWM called "Fix Permissions"? This is supposed to reset the permissions correctly for the system apps area I believe which helped a lot of people with force close issues. It's worth a shot.
Are you installing ROM's from external SD card or the Internal SD card? That shouldn't matter but I have always stuck with the External SD card.
One thing you could also try is to wipe the big 3 several times a piece before installing the ROM. I found it had made some ROM's load better when I encountered a few issues. Also, stick with one ROM either ICS or JB. Going back and forth will cause problems.
Also, I remember that from ICS to JB, some ROM's required the ROM to be installed twice literally after it installs install it again or some ROM's may reboot themselves back into recovery to complete the install.
Try that with the ROM you pick to get things back on track.
There is also some "Super Wipe" scripts floating around but I believe they were for a specific ROM and I think it was ICS based. You should be able to search XDA for that here in the Dev section.

TomTcom said:
This question should be in the QA section...
But your stock ROM was ICS and the newest EOS nightlies are based on JB which have different partitions. If you flash back and forth with ICS and JB you could be running into problems there.
Have you tried the option in CWM called "Fix Permissions"? This is supposed to reset the permissions correctly for the system apps area I believe which helped a lot of people with force close issues. It's worth a shot.
Are you installing ROM's from external SD card or the Internal SD card? That shouldn't matter but I have always stuck with the External SD card.
One thing you could also try is to wipe the big 3 several times a piece before installing the ROM. I found it had made some ROM's load better when I encountered a few issues. Also, stick with one ROM either ICS or JB. Going back and forth will cause problems.
Also, I remember that from ICS to JB, some ROM's required the ROM to be installed twice literally after it installs install it again or some ROM's may reboot themselves back into recovery to complete the install.
Try that with the ROM you pick to get things back on track.
There is also some "Super Wipe" scripts floating around but I believe they were for a specific ROM and I think it was ICS based. You should be able to search XDA for that here in the Dev section.
Click to expand...
Click to collapse
The ICS to JB isn't the issue as the issue started happening randomly with a ICS Rom that has been working for 4+ months when it has never had anything put ICS (well HC when I got it last year). Trying the JB rom was a near last ditch effort
I tried Revolutions superwipe several times, didn't help.
I probably completely screwed it up now in frustration. Tried to load the stock rom and now Recovery is screwed and it is boot loop so I don't think I can connect it to the computer now.
Hosed you think?

So now the question is, with a Tab that won't stay on longer then 8 seconds and no longer has a recovery, is there any other hope? I'm guessing bricked.

Firehawkns said:
So now the question is, with a Tab that won't stay on longer then 8 seconds and no longer has a recovery, is there any other hope? I'm guessing bricked.
Click to expand...
Click to collapse
You held down pwr + volume down when turning on and no text appears at the top left?
If not follow this thread
http://forum.xda-developers.com/showthread.php?t=1688012&highlight=nvflash
or http://forum.xda-developers.com/showthread.php?t=1688447&highlight=bootloop

Firehawkns said:
Guys, wondering if someone could give me some direction to restoring my TF101 to working conditions.
I have a rooted TF101 that was running 9.1.2.27.
This setup has been running great since .27 (not done OTA, Found here) came out, so I haven't bothered upgrading recently.
Fast forward to this week and it seems the Tablet started locking up at some point in the last couple days I hadn't used it. This would cause a battery drain until the device turned off. Upon rebooting I could get into the OS for maybe a minute before it would freeze again.
I decided to wipe the device, I went into CWM Recovery and wiped all caches and then tried to wipe all data/factory reset. It is at this time I get the following error:
Error removing /data/data/com.android.browser/databases/webview.db-wal!Error formatting /data!
Try starting back up and get a boot loop.
Upon reflashing the ROM, I find the TF101 in constant boot loop not making it 8 seconds into the bootup before rebooting.
I can still get into recovery so I try various kernels and roms with no success. Through searching I find CWM 6.0.1.4 and load it. Everything loads normally and I can now wipe data/factory reset, wipe all Cache even format all parts. I try to flash every ROM I can get my hands on from stock to older roms that I have ran succesfully to EOS Nighties, Every rom goes into Boot Loop after about 10 seconds.
Any Idea on where to go from here? I have been reading threads for hours now with no solution.
MODS: Putting in DEV since this is a Rooted TF, but if this should go to Q&A please move
Click to expand...
Click to collapse
Try using NV flash to go back to stock if you can get into APX mode.
Sent from my DROID RAZR HD using xda premium

morphuex said:
You held down pwr + volume down when turning on and no text appears at the top left?
If not follow this thread
http://forum.xda-developers.com/showthread.php?t=1688012&highlight=nvflash
or http://forum.xda-developers.com/showthread.php?t=1688447&highlight=bootloop
Click to expand...
Click to collapse
Yea, I can do the power + vol down and then up and get the recovery android guy, then he goes on his back and a red exclamation comes up (which I believe means no recovery mode installed
I can also do the pwr + vol down and then wait 5 seconds and get the wipe device or android options, but it won't let me choose anything, 10 seconds later it reboots.
clouse2013 said:
Try using NV flash to go back to stock if you can get into APX mode.
Sent from my DROID RAZR HD using xda premium
Click to expand...
Click to collapse
Will try tonight, but I believe all of those involve the computer having time to recognize the device, which it doesn't stay on long enough for the computer to recognize is and it won't seem to connect USB when the android guy is up.

nice rom! going to check this out tonight, thanks!

So I got into APX mode, windows shows no drivers, but it does show in devices. Trying NVFLash it says it is doing something, but nothing on the TF changes. Is there another step I am missing?

Firehawkns said:
So I got into APX mode, windows shows no drivers, but it does show in devices. Trying NVFLash it says it is doing something, but nothing on the TF changes. Is there another step I am missing?
Click to expand...
Click to collapse
Have a search for universal naked driver in the dev section, that should sort the drivers out I believe then you should be good to go.
---------- Post added at 10:37 PM ---------- Previous post was at 10:34 PM ----------
http://forum.xda-developers.com/showthread.php?t=1514942&highlight=naked+driver
There you go

pops106 said:
Have a search for universal naked driver in the dev section, that should sort the drivers out I believe then you should be good to go.
---------- Post added at 10:37 PM ---------- Previous post was at 10:34 PM ----------
http://forum.xda-developers.com/showthread.php?t=1514942&highlight=naked+driver
There you go
Click to expand...
Click to collapse
Thanks for the info, truly! I had searched for Drivers, but not naked.
That worked and it allowed me to use Easyflasher to get CWM back on.
Now I am back where I started, I have tried loading several Roms. Everyone hangs up about 15 seconds into first boot while the setup splash screen is on (for example the dotted circle on stock Asus rom or the simon says color circle like the JB rom or what ever it was in the ICS rom I was using. Something in the tab is stopping it from booting on up.
But I can now format everything and wipe data. I can connect APX mode. Anything else I can try from there. Starting to seem like something Hardware is busted.

Firehawkns said:
Something in the tab is stopping it from booting on up.
But I can now format everything and wipe data. I can connect APX mode. Anything else I can try from there. Starting to seem like something Hardware is busted.
Click to expand...
Click to collapse
Did you fix permissions while you were in recovery? It's a long shot but that may help. You may have a folder that's chmod'ed incorrectly. If so that'll prevent the system from being able to write or read to that folder making it impossible to install to, or run from it. Fix permissions, re-flash and reboot.
I know TomTcom mentioned it already. I don't see if you tried it in your replies though.

grgmre said:
Did you fix permissions while you were in recovery? It's a long shot but that may help. You may have a folder that's chmod'ed incorrectly. If so that'll prevent the system from being able to write or read to that folder making it impossible to install to, or run from it. Fix permissions, re-flash and reboot.
I know TomTcom mentioned it already. I don't see if you tried it in your replies though.
Click to expand...
Click to collapse
Yea, I tried that first. Sorry forgot to mention.

Are you able to flash the stock firmware using Easyflasher?

cabraswell said:
Are you able to flash the stock firmware using Easyflasher?
Click to expand...
Click to collapse
yes, I am able to flash to stock rom I got from Asus and the one I took for Rooted with stock on the forum. The flash, and it gives you the initial progress bar on first boot, then reboots at the end of the progress bar and goes to the Asus with the moving circles for about 5 seconds then keeps rebooting from there.
In a PC world I would wonder Ram issues, Over heating, or insuffecent power supply at this point. Not sure what to think here.
Is there a way to use TWOP and delete everything you see on the system and then reflash?

Firehawkns said:
yes, I am able to flash to stock rom I got from Asus and the one I took for Rooted with stock on the forum. The flash, and it gives you the initial progress bar on first boot, then reboots at the end of the progress bar and goes to the Asus with the moving circles for about 5 seconds then keeps rebooting from there.
In a PC world I would wonder Ram issues, Over heating, or insuffecent power supply at this point. Not sure what to think here.
Is there a way to use TWRP and delete everything you see on the system and then reflash?
Click to expand...
Click to collapse
In Addition, I have tried several times using TWRP to format Data and it fails. Could this be a clue?

Firehawkns said:
In Addition, I have tried several times using TWRP to format Data and it fails. Could this be a clue?
Click to expand...
Click to collapse
Have you tried using nvflash that blasts everything, takes you back to as clean as clean can be.
I am starting to think hardware though but if you can sit in recovery of adb / apx mode without issue then maybe it is a software thing.
No probs wiith the drivers by the way, its not really the right website for searching for the word naked.... dam don't can't won't imagine what you could of found with the members in here...

SUCCESS!!
I am not totally sure what finally worked as I just kept trying to reset/wipe/format/ and reflash, but this last time finally worked it seems. I have the stock Asus rom back on and going through setup.
I do find that if I try to put EOS on it just sits at the color things that show loading and never moves forward, so I just put the stock rom back on for now. Try to get Root back on for Titanium backup and enjoy the tablet again and worry about JB later maybe.

Firehawkns said:
SUCCESS!!
I am not totally sure what finally worked as I just kept trying to reset/wipe/format/ and reflash, but this last time finally worked it seems. I have the stock Asus rom back on and going through setup.
I do find that if I try to put EOS on it just sits at the color things that show loading and never moves forward, so I just put the stock rom back on for now. Try to get Root back on for Titanium backup and enjoy the tablet again and worry about JB later maybe.
Click to expand...
Click to collapse
I'm glad you finally got it fixed. I had some issues a while back (two weeks after I bought it) and I panicked and caused more trouble. Finally after stepping away from it for a day or two and a wife encouraging me I was able to get it going again...but my gut was in knots for that day or two.

Tablet after redoing the original root does not go over the system.
Not have access to ADB DEVICE or by Windows or the Linux Ubuntu, no longer accepts update totally blocked.
Ask help for those who have been through this problem.

[Q] Tablet stuck with startup logo.

Hi,
Two months ago I ve unlocked, rooted and installed Cromi-x 5.2.4 on my TF700t. To this day everything was OK, tablet was fast&furous.
Tonight, after 2 weeks, I wanted to turn on TF700T, and I saw only startup screen with asus logo, and I waited a long time and nothing happens. I tryied to press a reset button and nothing again. I saw only asus logo and system doesnt want to start. Then I tryied to to recovery mode TWRP power button+volume up and RCK mode and Ive reinstalled new one Cromi-x 5.3, and again nothing, only asus logo on startup and system doesnt started. What is going on with it, everything was good and now something broken? But why, I do nothing wrong with it, in the meantime. Android was really fast to this day., I rebooted few times and nothing.
Please help me with it. I cant find similar problems on your forum.

Bootloop
mariunio30 said:
Hi,
Two months ago I ve unlocked, rooted and installed Cromi-x 5.2.4 on my TF700t. To this day everything was OK, tablet was fast&furous.
Tonight, after 2 weeks, I wanted to turn on TF700T, and I saw only startup screen with asus logo, and I waited a long time and nothing happens. I tryied to press a reset button and nothing again. I saw only asus logo and system doesnt want to start. Then I tryied to to recovery mode TWRP power button+volume up and RCK mode and Ive reinstalled new one Cromi-x 5.3, and again nothing, only asus logo on startup and system doesnt started. What is going on with it, everything was good and now something broken? But why, I do nothing wrong with it, in the meantime. Android was really fast to this day., I rebooted few times and nothing.
Please help me with it. I cant find similar problems on your forum.
Click to expand...
Click to collapse
What is the OS of your PC??
What Bootloader is your tablet on??
What version of TWRP are you using??
Do you have a stock Asus cable??
Let me know... Thx lj

mariunio30 said:
Hi,
Two months ago I ve unlocked, rooted and installed Cromi-x 5.2.4 on my TF700t. To this day everything was OK, tablet was fast&furous.
Tonight, after 2 weeks, I wanted to turn on TF700T, and I saw only startup screen with asus logo, and I waited a long time and nothing happens. I tryied to press a reset button and nothing again. I saw only asus logo and system doesnt want to start. Then I tryied to to recovery mode TWRP power button+volume up and RCK mode and Ive reinstalled new one Cromi-x 5.3, and again nothing, only asus logo on startup and system doesnt started. What is going on with it, everything was good and now something broken? But why, I do nothing wrong with it, in the meantime. Android was really fast to this day., I rebooted few times and nothing.
Please help me with it. I cant find similar problems on your forum.
Click to expand...
Click to collapse
First, you need to answer the post above me so we want to make sure that you have a compatible TWRP and bootloader..
Second, I think that you have a corrupted data. In order to solve it, you have to format your data partition and reinstall the Cromi v5.3 which I think it is better than V5.2.4.. lj50036 will get you up and running again...
Please answer lj50036 before proceeding, thanks and good luck...:fingers-crossed:

LetMeKnow said:
First, you need to answer the post above me so we want to make sure that you have a compatible TWRP and bootloader..
Second, I think that you have a corrupted data. In order to solve it, you have to format your data partition and reinstall the Cromi v5.3 which I think it is better than V5.2.4.. lj50036 will get you up and running again...
Please answer lj50036 before proceeding, thanks and good luck...:fingers-crossed:
Click to expand...
Click to collapse
Thanks for your help.
I hope everything will be OK with my asus.
I think it is very strange, my TF700T was good for a long time after installing about 2014/03/01 CROMI-X ODEX 5.2.3_Signed.zip. Before installing this ROM I choose TF700_10.6.1.14.10_US_Boot_TWRP_2610_Signed.zip (US_epad-10.6.1.14.10-20130801 A03 when I started TWRP right now), my asus is from US. ROM is US version too. When I was installing this ROM, I choose _that 10.6.1.14.10 Over Clocked Modded Stock Kernel with 1518 - Power Save option, I remember.
What is important I think. Before installing ROM, I used ASUS stock bootloader with newest version 10.6.1.14.10 and I ve done downgrading to ASUS Stock 10.6.1.14.8, because I couldnt rooted it after unloking. It was without problems. Ive done this compare to http://forum.xda-developers.com/showthread.php?t=2425383 site Scenario one.
I used PC with WIN7 x64 doing this with stock Asus cable. Like I said, last night I reinstall twice to new rom CROMI-X 5.3, installing finished with success, but tablet stuck with logo on startup and waiting. When tablet stuck on startup logo and waiting from time to time screen is brighter and so on, pulsing. That is everything I remember, let me know what to do, this is tough for me, because my english is not to good, sorry about it.
While installing a new CROMI-X again could I choose Cromi WW version (bootloader is US) I didnt find answer on forum about it ?
Please, send me procedure to recover TF700T functionality. I cant imagine, what was done with corrupted data, like you said. Tablet was quaite good few days ago, I used NFW most Wanted, Frisby, internet, and I do nothing special in the middle, to last night, when I tried to turn it ON.
Thank you.
Mario

I don't think you did anything wrong just you were unlucky. Did you disable fsync when installing and which kernel option did you choose?
Which version of TWRP are you using?
The fix will be to wipe or format data so it would be helpful if you had a nandroid backup on your external card first as you may be able to restore it.

mariunio30 said:
Thanks for your help.
I hope everything will be OK with my asus.
I think it is very strange, my TF700T was good for a long time after installing about 2014/03/01 CROMI-X ODEX 5.2.3_Signed.zip. Before installing this ROM I choose TF700_10.6.1.14.10_US_Boot_TWRP_2610_Signed.zip (US_epad-10.6.1.14.10-20130801 A03 when I started TWRP right now), my asus is from US. ROM is US version too. When I was installing this ROM, I choose _that 10.6.1.14.10 Over Clocked Modded Stock Kernel with 1518 - Power Save option, I remember.
What is important I think. Before installing ROM, I used ASUS stock bootloader with newest version 10.6.1.14.10 and I ve done downgrading to ASUS Stock 10.6.1.14.8, because I couldnt rooted it after unloking. It was without problems. Ive done this compare to http://forum.xda-developers.com/showthread.php?t=2425383 site Scenario one.
I used PC with WIN7 x64 doing this with stock Asus cable. Like I said, last night I reinstall twice to new rom CROMI-X 5.3, installing finished with success, but tablet stuck with logo on startup and waiting. When tablet stuck on startup logo and waiting from time to time screen is brighter and so on, pulsing. That is everything I remember, let me know what to do, this is tough for me, because my english is not to good, sorry about it.
While installing a new CROMI-X again could I choose Cromi WW version (bootloader is US) I didnt find answer on forum about it ?
Please, send me procedure to recover TF700T functionality. I cant imagine, what was done with corrupted data, like you said. Tablet was quaite good few days ago, I used NFW most Wanted, Frisby, internet, and I do nothing special in the middle, to last night, when I tried to turn it ON.
Thank you.
Mario
Click to expand...
Click to collapse
Your device is fine...:good: It needs some fixes and should be up running again.. BTW, welcome aboard... It looks like that you have the latest bootloader and TWRP v2.6.1.0. So this part is good..
First, I hope that you have a TWRP backup or nandroid backup because it will save you a lot of time for the setup..
Second, you need to save all your personal data and stuffs to your External SD so you will not loose anything when you format your data partition.
Third, you need to copy the Cromi v5.3 to your External SD so you can install it.
Fourth, this is the fun part and follow every steps so you have a clean installation..
1. Boot into the TWRP
2. Select Wipe button. Under Wipe, there are two selections. One is Advance Wipe. Another is Format.
3. You need to select Format button. You need to type "yes" to confirm and hit the Enter button to format your data partition.
4. When the format is successful, now you can install Cromi v5.3. Since you have a US bootloader, I recommend you to use the US ROM. During the installation process, these are my suggestions for the installation:
--Choose wipe dalvik and cache
--Choose _that's kernel V7
--Do Not select any ET tweaks
--Do Not select UV/OV
--Do Not select cache2sd or data2sd or rom2sd
--If you don't mind what launcher to use, please don't use the Stock launcher. I suggest using Apex launcher.. You need to make sure to Unckeck the Stock launcher check box. You don't want to install it at all..
--You are free to choose anything else that you like to install except the list above...
Fifth, since your system is not stable, I don't know if your backup is a good backup or not. So it would be better to start all your setup all over again. When you are happy with your new setup, you need to boot back into the TWRP so you can make a good backup for later to restore if you need to...
I think that should be good for now and please feel free to ask any question...Good luck...:fingers-crossed:
LMK

I ve done it, like you said.
TF700T alive again. I didnt think this will help me.
Thank you.
What can I do for you?
:victory:

mariunio30 said:
I ve done it, like you said.
TF700T alive again. I didnt think this will help me.
Thank you.
What can I do for you?
:victory:
Click to expand...
Click to collapse
I am glad that your device is up and running... You don't have to do anything for me.. I am here trying to help new users... You can try to help others next time if you know the answer...
Have fun with Cromi v5.3.. It should be more stabe and faster, IMHO...:good:
LMK

Thank you very much.
Mario.

Thumbs Up
mariunio30 said:
I ve done it, like you said.
TF700T alive again. I didnt think this will help me.
Thank you.
What can I do for you?
:victory:
Click to expand...
Click to collapse
Give a thumbs up.. Show your appreciation with a thumbs up...Thx lj:good:

:good:

[Q] Help with KitKat + CWM 6.0.4.6

Hi!
My P500 was originally Gingerbread 2.3.3, than I used CM 7.2 with AmonRa 3.0.6 recovery for a year.
So I tried to flash KitKat (http://forum.xda-developers.com/showthread.php?t=2589303), and got some issues.
I flashed ClockworkMod Recovery 6.0.4.6 (Jan/14), than the ROM (v8), and the installation worked well.
Before the reboot, CWM says:
"root access possibly lost. Fix?
this can not be undone"...
Whatever I choose, I got that black screen with
"fastboot mode started
udc_start()".
Thaaaan, I see this: http://forum.xda-developers.com/showthread.php?t=2439466
and tried to downgrade SU to v1.55. But the CWM got an error, and cannot install (even with AmonRa)...
After all, I can't get KitKat working, and got back to AmonRa recovery and CM 7.2.
To complete the "good vibe", my Android can't get AT ALL connect through USB, so I can't test any ADB command.
I don't know where I'm doing wrong... Any directions??
Thanks!!!!

SOS
This^. Exactly this is what I am suffering from right now and I am amazed how identical the issue is. I hope the OP doesn't mind if I added some more info since I didn't wanna create a new thread when one is already made recently.
Here is some info in brief regarding my issue.
Last OS: CynogenMod 7.2
Last CWM: 5.0.0.X
Target OS: Cynogen KittKat
Target CWM: 6.0.4.6 [January 2014 release]
Downloaded KittKat Rom from here: http://forum.xda-developers.com/showthread.php?t=2589303
Downloaded CWM from here: http://forum.xda-developers.com/showthread.php?t=2564767
Everything went fine when I flashed the CWM first and it entered the new recovery mode without a hitch. But the trouble began after I flashed the KittKatt Rom. Though initially everything installed just fine but in the end just before restart, this came:
"root access possibly lost. Fix?
this can not be undone"...
For safe measure I chose "Yes" and that's where my phone apparently got "soft-bricked" cause it rebooted into fastboot mode with this message
"fastboot mode started
udc_start()".
I looked around and found a "solution" for this kind of issue here: http://forum.xda-developers.com/showthread.php?t=1088046
I followed instructions to the letter but my the LG Mobile support tool refused to identify my phone. Since I figured it might have been a driver issue so I installed PDAnet instead to get stuff working. The only hitch was that PDAnet would hang on "Updating PDAnet to your phone" option. I sat their staring at it for an hour or so and figured something was wrong like my phone wouldn't allow to install anything on itself since my debugging wasn't enabled, though I am not sure about this one.
In any case I checked device manager and my ADB drivers were fine so I ran the three recovery commands in DOS anyway and they all executed without a hitch. I jumped for joy but my happiness was short lived since the phone booted back into recovery mode and now I am basically stuck up the creek without a paddle. I could really use some expert advice here just like the OP cause I really am not sure what went wrong and where. I would really like to fix this rather than flash and start the whole phone up from scratch if possible.
Regards,
LonerPrime
PS: Long time reader but this is my first post here so greetings to the xda community.

LonerPrime said:
This^. Exactly this is what I am suffering from right now and I am amazed how identical the issue is. I hope the OP doesn't mind if I added some more info since I didn't wanna create a new thread when one is already made recently.
Here is some info in brief regarding my issue.
Last OS: CynogenMod 7.2
Last CWM: 5.0.0.X
Target OS: Cynogen KittKat
Target CWM: 6.0.4.6 [January 2014 release]
Downloaded KittKat Rom from here: http://forum.xda-developers.com/showthread.php?t=2589303
Downloaded CWM from here: http://forum.xda-developers.com/showthread.php?t=2564767
Everything went fine when I flashed the CWM first and it entered the new recovery mode without a hitch. But the trouble began after I flashed the KittKatt Rom. Though initially everything installed just fine but in the end just before restart, this came:
"root access possibly lost. Fix?
this can not be undone"...
For safe measure I chose "Yes" and that's where my phone apparently got "soft-bricked" cause it rebooted into fastboot mode with this message
"fastboot mode started
udc_start()".
I looked around and found a "solution" for this kind of issue here: http://forum.xda-developers.com/showthread.php?t=1088046
I followed instructions to the letter but my the LG Mobile support tool refused to identify my phone. Since I figured it might have been a driver issue so I installed PDAnet instead to get stuff working. The only hitch was that PDAnet would hang on "Updating PDAnet to your phone" option. I sat their staring at it for an hour or so and figured something was wrong like my phone wouldn't allow to install anything on itself since my debugging wasn't enabled, though I am not sure about this one.
In any case I checked device manager and my ADB drivers were fine so I ran the three recovery commands in DOS anyway and they all executed without a hitch. I jumped for joy but my happiness was short lived since the phone booted back into recovery mode and now I am basically stuck up the creek without a paddle. I could really use some expert advice here just like the OP cause I really am not sure what went wrong and where. I would really like to fix this rather than flash and start the whole phone up from scratch if possible.
Regards,
LonerPrime
PS: Long time reader but this is my first post here so greetings to the xda community.
Click to expand...
Click to collapse
The way back home without buggy LG Mobile anything: Remove and replace batter, press home, volume-down and power keys simultaneously. Can be a bit tricky but will get you back in recovery. I assume you did that backup before playing. Restore it to get the phone back up.
Two ways to get your Kitkat:
1. Using the Version-8 install, do a clean install and be sure to choose an item in the various menu panes. Should work with this and then you need to reinstall and setup everything.
2. Take the "nightly" and install normally doing the requesite steps in the backup.

Thank you, but– Nvm fixed it.
@Dovidhalevi
Thank you for your amazing advice. I was able to get into recovery and restore from my nandroid backup. *Thank god I did that*
But kittkat ROM is still being a pain. I decided to read the logs of version 8 of the ROM a bit more closely and found this:
Upgrading from CM-10.2 or older / Fresh (First time) Installation: Now DON'T WIPE ANYTHING (Data/Factory reset, Wipe Cache partition, Dalvik Cache, Format System) everything have built in Aroma Installer. Simply flash through sdcard or adb sideload, Follow the Aroma Menu. Finish and Reboot device. Avoid Facebook, Whatsapp, Viber, Hangout apps while selecting apps to be flash, it may gives you fastboot mode. Done!!!
I decided to try my luck once more and disabled all those apps during the installation. But just before rebooting my phone lost root access again and asked if I wanted to fix it or not and then it froze again on LG logo afterwards. Another force restart and it went straight into fastboot mode. Had to do another restore to get my phone working on the older backup.
Now I know it isn't the CWD cause I am running that with my older Cynogen 7.2 OS and its rebooting without a hitch unlike kittkat which mysteriously loses root access...
I really apologize if I am being a bit noobish. Even though hardware/networking/linux[Red Hat] is like playing in my backyard, android itself is a new concept to me, hence I really appreciate all the help I can get on this to work.
MAJOR EDIT: I finally found the root of the problem and got my KitKat munching! The issue was, yep you definitely guessed it, human error... that human being me and if the original OP did everything like I did then I am guessing he made the same mistake.
What I did was, I didn't read the Aroma installer's text thoroughly enough during the installation process. At one point there comes a choice of partitions and the installer asks you to choose one of the following: *Please forgive me this is not the exact quote of the text but roughly along the same lines as memory serves*
A) Install if you are coming from a previous version of the ROM.
B) Install if you are coming from a different ROM all together.
Trust me, the way I put it makes me look like an idiot for not choosing the right choice but the actual text combined with reading carelessly on the fly ended up me botching up my initial attempts to install the new ROM. Point being you have to choose the second option and then install like usual. Following that method I wasn't faced with fastboot mode in the end and after 5 to 10 minutes of loading I was playing with the KittKat ROM. Once again I apologize for bothering you good folks and I am grateful for the guidance to the person above me.
Kind Regards,
LonerPrime

I'll try
LonerPrime said:
@Dovidhalevi
MAJOR EDIT: I finally found the root of the problem and got my KitKat munching! The issue was, yep you definitely guessed it, human error... that human being me and if the original OP did everything like I did then I am guessing he made the same mistake.
What I did was, I didn't read the Aroma installer's text thoroughly enough during the installation process. At one point there comes a choice of partitions and the installer asks you to choose one of the following: *Please forgive me this is not the exact quote of the text but roughly along the same lines as memory serves*
A) Install if you are coming from a previous version of the ROM.
B) Install if you are coming from a different ROM all together.
Trust me, the way I put it makes me look like an idiot for not choosing the right choice but the actual text combined with reading carelessly on the fly ended up me botching up my initial attempts to install the new ROM. Point being you have to choose the second option and then install like usual. Following that method I wasn't faced with fastboot mode in the end and after 5 to 10 minutes of loading I was playing with the KittKat ROM. Once again I apologize for bothering you good folks and I am grateful for the guidance to the person above me.
Kind Regards,
LonerPrime
Click to expand...
Click to collapse
Glad you fixed your phone!! I forgot to say what I did to "fix" it...
Read error... maybe???
I'll try as soon as I get home, with results!! Thanks!!!

I did that... =/
yes.. i was doing right. All the 6 times I tried...
And tried again now, just to be sure, and FASTBOOT again.
=/

jpesci said:
I flashed ClockworkMod Recovery 6.0.4.6 (Jan/14), than the ROM (v8), and the installation worked well.
Before the reboot, CWM says:
"root access possibly lost. Fix?
this can not be undone"...
Click to expand...
Click to collapse
All newer recoveries have this behavior. Because you are running a custom ROM and recovery, you should select "No" when prompted to disable recovery flashing.
Did you try the Key combos suggested by @Dovidhalevi to manually enter in to CWM?
As a worst case scenario, view this post to see how to restore your device to stock.

It's fixed, but no Kitkat...
shinobisoft said:
All newer recoveries have this behavior. Because you are running a custom ROM and recovery, you should select "No" when prompted to disable recovery flashing.
Did you try the Key combos suggested by @Dovidhalevi to manually enter in to CWM?
As a worst case scenario, view this post to see how to restore your device to stock.
Click to expand...
Click to collapse
Oh, sorry. Maybe bad explanation. I did get it fixed. All the "x" times, heheh =)
I just got in recovery by pressing home+vol up+power, and flashed back my older ROM. Now I'm trying CM 10 by Jenkins.
The problem isn't the "fastboot" message itself... but don't get Kitkat working =/
But thanks for the reply anyway!

kitkat by mukulsoni... ui stops with multiple popupd
M stuck.. i have successfully flashed kitkat by mukulsoni.. thanks. BUT UI DOES NOT START... it starts with so many popups... eg. Unfortunately voice dialer has stopped. Unfortunately bluetooth share has stopped. Unfortunately com.google.process.gapps stopped. Unfortunately com.android.systemui has stopped . Unfortunately clock has stopped. Unfortunately kitkat+ launcher stopped....
what to do. Should i get back through backup 4m recovery.. or u can help me wid kitkat .. feeling so sad..

amit2411 said:
M stuck.. i have successfully flashed kitkat by mukulsoni.. thanks. BUT UI DOES NOT START... it starts with so many popups... eg. Unfortunately voice dialer has stopped. Unfortunately bluetooth share has stopped. Unfortunately com.google.process.gapps stopped. Unfortunately com.android.systemui has stopped . Unfortunately clock has stopped. Unfortunately kitkat+ launcher stopped....
what to do. Should i get back through backup 4m recovery.. or u can help me wid kitkat .. feeling so sad..
Click to expand...
Click to collapse
Boot in to your recovery and try wiping your cache and dalvik cache.

still no working
I wish I could get these popups.
Is there something else to do??? I tried everything, everyway... Always get "fastboot mode started / udc_start()".

jpesci said:
I wish I could get these popups.
Is there something else to do??? I tried everything, everyway... Always get "fastboot mode started / udc_start()".
Click to expand...
Click to collapse
Maybe I can help... Are you flashing the same download every time? It's possible that your download managed to get corrupted. Try redownloading the ROM. I'd suggest redownloading the newest recovery also.
Now I'm going to list my ROM installation method for comparison. I personally have NEVER had an issue installing a ROM on any Optimus One variant. And I have 3 of them...
Boot device to your current recovery. CWM 6.0.45+ is compatible with CM10 - CM11 only. If you are currently running an older recovery, make a backup of your ROM with your current recovery first. Now if running an older recovery, Select "Install from zip" and install CWM 6.0.4.5+ or equivalent. Then go to "Advanced" and select "Reboot Recovery". We should now be in your new recovery. 1) Select "Wipe data/factory reset". This will wipe cache, data, .android_secure, and sd-ext.
2) Select "Advanced" then "Wipe Dalvik Cache". When done, return to recovery main menu.
3) Select "Mounts and storage". Choose "Format /system" and then confirm the action. Go back to main menu.
4) Select "Install from zip". Now we can install KitKat. Browse to and select your KitKat ROM and confirm installation.
5) If your device was old baseband ( originally running Android 2.2.2 or older ) then you will also need to flash the old baseband patch found here.
6) If you wish to flash a GApps package, that should be done now, or optionally after booting the device and letting it boot in to the ROM for the first time.
7) Go back to the main menu and select "Reboot device". If prompted to disable recovery flashing, select "NO". First boot will take 3 - 5 minutes. ​

shinobisoft said:
Maybe I can help... Are you flashing the same download every time? It's possible that your download managed to get corrupted. Try redownloading the ROM. I'd suggest redownloading the newest recovery also.
Now I'm going to list my ROM installation method for comparison. I personally have NEVER had an issue installing a ROM on any Optimus One variant. And I have 3 of them...
Boot device to your current recovery. CWM 6.0.45+ is compatible with CM10 - CM11 only. If you are currently running an older recovery, make a backup of your ROM with your current recovery first. Now if running an older recovery, Select "Install from zip" and install CWM 6.0.4.5+ or equivalent. Then go to "Advanced" and select "Reboot Recovery". We should now be in your new recovery. 1) Select "Wipe data/factory reset". This will wipe cache, data, .android_secure, and sd-ext.
2) Select "Advanced" then "Wipe Dalvik Cache". When done, return to recovery main menu.
3) Select "Mounts and storage". Choose "Format /system" and then confirm the action. Go back to main menu.
4) Select "Install from zip". Now we can install KitKat. Browse to and select your KitKat ROM and confirm installation.
5) If your device was old baseband ( originally running Android 2.2.2 or older ) then you will also need to flash the old baseband patch found here.
6) If you wish to flash a GApps package, that should be done now, or optionally after booting the device and letting it boot in to the ROM for the first time.
7) Go back to the main menu and select "Reboot device". If prompted to disable recovery flashing, select "NO". First boot will take 3 - 5 minutes. ​
Click to expand...
Click to collapse
Thanks for explanation!! But... still nothing.
I did EVERY SINGLE STEP like you said. Except for baseband, cause my phone was originally 2.3.3. But all new downloads...
After flashing, try to reboot... DAMN! "root access possibly lost..." YES/NO, gives me same problem. I read another thread about this erros, people said about SU. Can it be? I tried to flash another SU version, but CWM return an error too =/

jpesci said:
I wish I could get these popups.
Is there something else to do??? I tried everything, everyway... Always get "fastboot mode started / udc_start()".
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2559363 try this.

voltaire23 said:
http://forum.xda-developers.com/showthread.php?t=2559363 try this.
Click to expand...
Click to collapse
Ah, thanks man! But my problem isn't the "brick" itself, but the frustration of can't get kitkat working, hehe.
By the way, I think KDZ method dangerous, by many reports that you can find all through the web. In all 217897254179 times I tried Kitkat without success, I just rebooted in recovery mode (hold HOME+VOL UP+POWER button), and recovered the last CWM backup.
But thanks to the effort =)

jpesci said:
Ah, thanks man! But my problem isn't the "brick" itself, but the frustration of can't get kitkat working, hehe.
By the way, I think KDZ method dangerous, by many reports that you can find all through the web. In all 217897254179 times I tried Kitkat without success, I just rebooted in recovery mode (hold HOME+VOL UP+POWER button), and recovered the last CWM backup.
But thanks to the effort =)
Click to expand...
Click to collapse
I am considering the jenkins build from here: http://download.androidarmv6.org/_builds/
can anyone help with finding the smallest gapps that will fit?
Edit:No need

TF300T Stuck in a Infinite Loop (HELP)

hello everyone im having a issue with my ASUS Tablet...
I got it off some guy from Kijiji for $100 It was working fine untill i noticed that the dock was not charging... So i did some reading online and people said that a Hard reset made it work for them and to do a cold boot.... So i did all that Via TWRP.... I did a full wipe of everything it could not even find the Partitions anymore... But all partitions are back and now its stuck in a Boot Loop... I can Access TWRP Just fine ( Power/Volume down ) all that works...
I tryed to Downlode a few Roms i tred all US Factory roms but they all Instantly Fail...
I downloaded KatKiss for the TF300T and it Would flash for about 5-10min then fail... This is the farthest one i have had flash... all others are instant fail...
I put the ROM on my SD Card and go to install on TWRP and select the rom and hit Flash...
Nothing is working....
What do i do... it was working fine.... all i did was a Wipe But i think i wiped to much lol....
Any advice on what to do ? Im not to sure what Version its on or anything...

stupid me i dint do any research lol... Using TWRP to reset is vary bad... Please can anyone help me...
I live in edmonton ,AB so if there are any pro ASUS Firmware people that would like to help me that would be great
also it says THIS DEVICE IS UNLOCKED on the top left

is this what i did ????? hears a Post from XpLoDWilD
- I wiped everything but didn't put a ROM on my sdcard, what to do?!
Calm down, you're not bricked, you're just a bit dumb. Go in "Install zip from sdcard" until you reach list files, so the sdcard is mounted. Then, open a command prompt, and do "adb push c:\path\to\the\rom.zip /sdcard/". Wait, and once done your rom.zip will appear in the files list when you go back and forth in files list.

found out all i need is a rom now.... i had time to do some research and i installed TWRP/Fastboot/ADB And im just trying to find a rom that will work

FIXED The Issue PLEASE REMOVE ADD....
Figured all of this out on my own....