Dear everyone,
I managed to install Cromi with the guides provided on this website. The first time it reboots from TWRP it was a pure joy to see it function.
However, the frist time I shut down the Tf700 and rebooted, it just hangs in the bootloader, the same animation over and over again.
And I followd each step exactly. Luckily I had made a backup of my system, so when I enter TWRP it just reinstalls my stock Asus software, so no biggie. But just like yourself I to want to enjoy Cromi.
So what the hell am I doing wrong? Please help, I couldn't find the answer with the search engine. I am probably using the wrong search keywords...
tf700tTRANSF said:
Dear everyone,
I managed to install Cromi with the guides provided on this website. The first time it reboots from TWRP it was a pure joy to see it function.
However, the frist time I shut down the Tf700 and rebooted, it just hangs in the bootloader, the same animation over and over again.
And I followd each step exactly. Luckily I had made a backup of my system, so when I enter TWRP it just reinstalls my stock Asus software, so no biggie. But just like yourself I to want to enjoy Cromi.
So what the hell am I doing wrong? Please help, I couldn't find the answer with the search engine. I am probably using the wrong search keywords...
Click to expand...
Click to collapse
You may need to format your data partition and do a clean installation with the Cromi again. Good luck....:fingers-crossed:
tf700tTRANSF said:
Dear everyone,
I managed to install Cromi with the guides provided on this website. The first time it reboots from TWRP it was a pure joy to see it function.
However, the frist time I shut down the Tf700 and rebooted, it just hangs in the bootloader, the same animation over and over again.
And I followd each step exactly. Luckily I had made a backup of my system, so when I enter TWRP it just reinstalls my stock Asus software, so no biggie. But just like yourself I to want to enjoy Cromi.
So what the hell am I doing wrong? Please help, I couldn't find the answer with the search engine. I am probably using the wrong search keywords...
Click to expand...
Click to collapse
"Each step exactly" meaning including a Factory Wipe in TWRP prior to installing the rom?
If not, that's what you should try first. Formatting data would be another, if radical, option.
Naturally you would have to re-install the rom after either....
Did you by any chance reboot from the Cromi Control app?
And if you know how, can you grab a logcat of the boot process before you do a data wipe or format? sbdags described the procedure in the CROMi-X thread a few pages back from the last post.
If memory serves me right:
Connect your tablet to your PC and open a command prompt from the same directory your adb.exe is in
Boot the tablet, give a minute or two and type
Code:
adb devices
It should return the serial number of your tablet - just to make sure you have a connection... Then type
Code:
adb logcat > logcat.txt
and let it run for 3 - 5 minutes. Hit Ctrl + C to stop the capturing process.
Post the logcat (which you should find in the same directory)
Related
firsth of all hi to everyone, im new here , so be patient.
i was searching on the forum and try to solve my problem, but no succes.
all the methods ive tried are a no go
my problem here is that im already rooted (razorclaw tool), superuser installed aswell, so i dont know what else do i need to enter on the recovery mod (i know i have to press down power button and volume - , at the same time), no succes either, the TF just restar as always or the little android with an exclamation sign appears and i have to restart the TF again
my problem is that i cant install custom ROMS, because it always skip to home screen or to the android with the exclamation.
i cant see all those options that lot of people tallk(install from zip, backup current rom, install X rom)because i never get to that part....
so my problem again, how to install some tool that will allow me to enter in clockwork mode (??) ??, and enable those option at the intial boot (power button & vloume - at same time ) to be abble to access the install from zip, backup current rom, wipe data , etc etc
please if someone can help me with another step by step i will be really happy
I am having the same problem
Sent from my Transformer TF101 using xda premium
i think i have this problem since i got the " FIX the problem with DOWNGRADE from .21 to .19", something along those lines, with the method someone posted before (add both files to SD card but rename one of those and then apply update)
jesesystem said:
my problem here is that im already rooted (razorclaw tool), superuser installed aswell,
please if someone can help me with another step by step i will be really happy
Click to expand...
Click to collapse
but have you installed CWM recovery?
User RecoveryInstaller to install CWM.
http://forum.xda-developers.com/showthread.php?t=1346180
/agree with @baseballfanz
Check that you have CWM installed. Then you should hold volume down + power button till you see in the screen something like (push vol+ to enter recovery). It will appear on the top of the screen. You have to wait a little since it first appears the ASUS screen and if you stop pushing the buttons at that time, the TF starts normally. You have to hold them a little longer till the text appears in the screen.
AzureusPT said:
/agree with @baseballfanz
Then you should hold volume down + power button till you see in the screen something like (push vol+ to enter recovery). It will appear on the top of the screen. You have to wait a little since it first appears the ASUS screen and if you stop pushing the buttons at that time, the TF starts normally. You have to hold them a little longer till the text appears in the screen.
Click to expand...
Click to collapse
OR you can install 'transformer reboot to recovery' from market
Pepecillo said:
OR you can install 'transformer reboot to recovery' from market
Click to expand...
Click to collapse
If they don't have CWM installed, that will only reboot the TF, not get them to recovery.
AzureusPT said:
If they don't have CWM installed, that will only reboot the TF, not get them to recovery.
Click to expand...
Click to collapse
This is 100%. We've already told you this, in this thread This Thread.
You need to install a recovery image access recovery.
If you are this unsure of what you are doing i HIGHLY suggest stepping back and reading all about SU access and the rooting procedures again.
The "flash a new ROM to ________ device" steps are pretty much the same for every Android device w/o a locked bootloader.
Root
make sure SU access can be obtained
flash a custom recovery image
reboot into recovery
do a nandroid back up
wipe
flash
reboot
If you cannot get to where you want. You are doing something wrong. millions of people have followed these same step on millions of devices w/o any problems.
neidlinger said:
This is 100%. We've already told you this, in this thread This Thread.
You need to install a recovery image access recovery.
If you are this unsure of what you are doing i HIGHLY suggest stepping back and reading all about SU access and the rooting procedures again.
The "flash a new ROM to ________ device" steps are pretty much the same for every Android device w/o a locked bootloader.
Root
make sure SU access can be obtained
flash a custom recovery image
reboot into recovery
do a nandroid back up
wipe
flash
reboot
If you cannot get to where you want. You are doing something wrong. millions of people have followed these same step on millions of devices w/o any problems.
Click to expand...
Click to collapse
Thank you¡¡¡¡¡¡¡
Thats the step i was mising , all the instructions are for ppl that actually had cwm recovery, and i was taking advices from posts about installing custom roms and not the 1sth root
Its solved now ,thank you all for your help.
sorry, my bad for asking for help
Sent from my Transformer TF101 using xda premium
Bobsinclair25 said:
sorry, my bad for asking for help
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
In essence there is nothing wrong with asking for help. Heck even the smartest of android hackers started somewhere, asking questions the selves.
The problem lays in the fact that is is pretty common knowledge and a simple search would of gave you the answers you wanted.
Keep in mind nothing i say is meant to come across rude. Sharp maybe, rude? no. If you take what i say as rude. I'm sorry.
No problem. I have been trying very hard to learn on my own. The problem I had with this was trying to find information specific to the transformer. I have done quite a bit with my other android devices and the transformer is new to me and since I use it at work every day I am probably a bit more cautious about it. Thanks, I am working on it.
Sent from my Transformer TF101 using xda premium
Hi everyone, hate for my first to be a call for assistance, but here goes. Bought an Asus tf300t earlier today. I unlocked the device, then attempted to begin walking through this guide(http://forum.xda-developers.com/showthread.php?t=1845377) in order to have root+jb. In order to install clockworkmod, set up fastboot. After getting an error of "cannot load" in fasboot for the recovery image, I gave up, used the cmd prompt to reboot the device. On reboot, the touch screen no longer responded. I went to recovery, wiped data, to no avail. Now its simply showing the welcome screen, where you choose english, but can't select start. I've rebooted, wiped, and swore. A lot. My OS is windows 7, if that helps. Thanks everyone.
Shourisha1 said:
Hi everyone, hate for my first to be a call for assistance, but here goes. Bought an Asus tf300t earlier today. I unlocked the device, then attempted to begin walking through this guide(http://forum.xda-developers.com/showthread.php?t=1845377) in order to have root+jb. In order to install clockworkmod, set up fastboot. After getting an error of "cannot load" in fasboot for the recovery image, I gave up, used the cmd prompt to reboot the device. On reboot, the touch screen no longer responded. I went to recovery, wiped data, to no avail. Now its simply showing the welcome screen, where you choose english, but can't select start. I've rebooted, wiped, and swore. A lot. My OS is windows 7, if that helps. Thanks everyone.
Click to expand...
Click to collapse
Do I understand correctly that you've never successfully installed a custom recovery on your tab? So how did you wipe data? You chose the fourth option in the stock recovery?
graphdarnell said:
Do I understand correctly that you've never successfully installed a custom recovery on your tab? So how did you wipe data? You chose the fourth option in the stock recovery?
Click to expand...
Click to collapse
There were only 3 options--Wipe Data, usb, and android. I'd had success rooting the tablet earlier, but believed I'd made an error somewhere so followed that guide to try and begin again from the beginning. The wipe wasn't what caused the issue. It was working fine, until the reboot using the cmd line. Thats what makes so little sense to me.
Shourisha1 said:
There were only 3 options--Wipe Data, usb, and android. I'd had success rooting the tablet earlier, but believed I'd made an error somewhere so followed that guide to try and begin again from the beginning. The wipe wasn't what caused the issue. It was working fine, until the reboot using the cmd line. Thats what makes so little sense to me.
Click to expand...
Click to collapse
You didn't have the RCK option on your recovery? You said the wipe wasn't the culprit and it was working fine. Did you get to reboot the tab successfully after the wipe? Now everything seems to work fine on your PC monitor doesn't mean it is so. Lots of people using NVflash derivatives witness a smooth transition on papers until they find out it isn't so. Reboot command from ADB doesn't do anything special. I can't think of it doing any damage to the firmware if successfully installed earlier.
graphdarnell said:
You didn't have the RCK option on your recovery? You said the wipe wasn't the culprit and it was working fine. Did you get to reboot the tab successfully after the wipe? Now everything seems to work fine on your PC monitor doesn't mean it is so. Lots of people using NVflash derivatives witness a smooth transition on papers until they find out it isn't so. Reboot command from ADB doesn't do anything special. I can't think of it doing any damage to the firmware if successfully installed earlier.
Click to expand...
Click to collapse
Uhm, well, its simply started registering touch again. Like nothing had happened. Makes me worry about the tablet itself. But, its working fine now, and I didn't do a thing. Sigh. I'm not sure. Not I just have to figure out why fastbooter keeps giving me the "cannot load recovery.img" error. Thanks for the help!
Sounds like you are on the old bootloader. Be careful about wiping.
I'd update to the latest Asus Stock ROM for your device from their website which will bring you up to the latest bootloader.
Right, I searched on numerous pages on these wonderful forums, but couldn't quite find what I was looking for. So I'll try my luck here. I'll describe my problem.
My TF101 was rooted using the CWM recovery. After doing more research I found out I shouldn't be doing this. But, unfortunately the damage has already been done. After several succesful ROM installations I wasn't quite happy with, I tried one last CM10 install. That's when it all went to ****. My TF101 has been stuck on the Eee Pad splash screen for nearly 2 months now.
Normally when going into the recovery mode I can simply select install from SD card and install a new rom. Now it can't seem to mount and displays E:Can't mount \SD card or whatever.
Further on, I tried using the ADB tools to manually restore system files. Without luck. After which I tried to install the naked USB drivers using http://forum.xda-developers.com/showthread.php?t=1426502. Without luck as well. I simply ran out of ideas.
The thing is, in Device manager I do see a device called Android. But, for some reason I can't seem to install any drivers for it. I guesse this would be the first step towards getting it back to work? Or perhaps I should just get it fixed at the computer store?
Any sugestions would be more than welcome!
Easy Flasher will get you back to stock as long as you can access APX. You will lose all data however.
1st mistake read forum before you do something, coz you would have learnt abt CWM issues, anyway thatsvan old story
You got Two options, find an flash able twrp.zip and flash it using current recovery if its still working otherwise as the other guy says easyflasher
To use easy flash you need
Easy flash software from forum
Universal naked driver installed
Asus firmware and PATIENCE
Follow the steps given in the forum and you should get back a tablet running stock rom, then if you want then use easy flash to root your device again but this time use TWRP recovery.....
Sent from my Transformer TF101 using xda app-developers app
Right, so far I've done everything I could find. I have installed the naked ADB files and thus was able to make a connection through USB. However, I wasn't able to push any files onto the tablet through ADB commands.
I entered the (what I assumed to be) APX mode and tried to use EasyFlasher. It seemed to have worked, because a DOS screen asked me whether or not I wanted to overwrite several files. After ending the procedure I rebooted my tablet. And guesse what: CWM is still there and the tab is still stuck on the Splash screen. Also the internal SD still can't be mounted.
What am I doing wrong. I'm slowly but surely going mad here....
hmmm, easyflasher should not prompt you to overwrite anything, it should just wipe it clean. The only prompt is when you select SBK1 or SBK2.
Can you post screenshots? It'd help us understand what exactly is going on...
Lethe6 said:
hmmm, easyflasher should not prompt you to overwrite anything, it should just wipe it clean. The only prompt is when you select SBK1 or SBK2.
Can you post screenshots? It'd help us understand what exactly is going on...
Click to expand...
Click to collapse
Right. Apparently I didn't put it in APX mode correctly. Windows asked me to install APX drivers. Which I now did. I then (I assume) was able to install the new recovery. The screen says !!!!phone update succes!!!!!. As we speak I am trying to install the stock ROM. Fingers crossed.....
AlbertGJBos said:
Right. Apparently I didn't put it in APX mode correctly. Windows asked me to install APX drivers. Which I now did. I then (I assume) was able to install the new recovery. The screen says !!!!phone update succes!!!!!. As we speak I am trying to install the stock ROM. Fingers crossed.....
Click to expand...
Click to collapse
I'll just sum up what I've been doing so far, because it still ain't working for me....
1) Put the TF101 in APX mode using POWER + VOLUME UP
2) Started up EasyFlasher 0.8.3 and selected "Flash Asus stock zip / Unbrick"
3) When prompted "file ..\temp\META-INF\MANIFEST.MF" already exists I selected "A(u)to rename all"
4) And then starts doing it's thing
5) Stuck at creating and formatting 15 partitions with several three letter codes.
I've ran the program three times now, but without luck. Any sugestions?~
[EDIT]Alright, managed to get it to work! Ended the tasks in through task manager about 4 times, but the 5th time was a charm. Exactly work as said. All thanks to EasyFlasher![/EDIT]
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
I am trying to resurrect my tf101. This is my starting point. Some time ago I installed cm10-20130929-NIGHTLY-tf101 into my tf101 using twrp. That installed fine but in the process something happened and I cannot boot into twrp I can now only boot into CM by holding the power button and volume up. I was not able to install gapps . Also I think my bootloader is corrupted because if I try to boot into it I just get a blank screen. I was able to install the Official TWRP App and can run it but it crashes every time "Unfortunately the app has stopped".
I am about ready to throw this laptop out because I have tried many options on this board and nothing worked. I can connect the tf101 to my computer and I can see it in device manager and I can open the laptop in file manager. I would even be willing to wipe the entire laptop and start from scratch but I don't know enough how to do this.
Any help or suggestions would be welcome.
Hi. First, I'll explain to you that for 10 years I had no contact with flashing phones. I didn't have any problems with the previous models. So I stopped somewhere at the level of the Samsung Galaxy S3-S4. Some time ago I decided that I would bring two Asus tf101s back to life and install a new KitKiss ROM on them. I set to work confidently. Turns out it's not that simple. I can do nothing. Some of the links have expired and the tips seem outdated. I can not upload a new recovery or even root the device. Strange things are happening. First of all, after turning on the device in recovery mode, after some time it goes into system boot and exits recovery. I've tried many ways and I don't understand any of it anymore. In the command line (CMD) it seems to see the device but does not want to respond to any commands, even to "adb reboot fastboot". I can do like this :
1. Ask for simple instructions for a "boy" and current links to the necessary files.
2. Look for someone who will perform a miracle and install the required Android for me.
Will someone help me?