Hello guys,
I've started yesterday messing with my transformer
Root is done and TWRP is flashed.
Now, I want to flash EOS 4 and KatKernel but I have some doubts.
1. The last version of TWRP is compatible with 4.2.1, right?
2. What do I install in first place? Kernel or ROM?
3. If I got a brick/bootloop, how can I solve it?
Thanks in advance. I'm used to change ROMs in my Xperia Arc S, but not in my TF
You should be running TWRP 2.3.2.3.
Be sure you wipe the following before flashing:
(Backup your data first)
Cache
Davlik
System
Factory Reset (in recovery)
Then flash the ROM first.
The rest don't matter, but flash GAPPS, Kernel and any patches.
I always wipe cache and Davlik again.
Reboot.
Enjoy
frederuco said:
You should be running TWRP 2.3.2.3.
Be sure you wipe the following before flashing:
(Backup your data first)
Cache
Davlik
System
Factory Reset (in recovery)
Then flash the ROM first.
The rest don't matter, but flash GAPPS, Kernel and any patches.
I always wipe cache and Davlik again.
Reboot.
Enjoy
Click to expand...
Click to collapse
Thanks mate!
What if I get into a bootloop?
Chances are you will not get a bootloop.
If you do, boot to recovery, wipe and reinstall. To boot to relcovery, hold VOL DOWN and POWER for 12-15 seconds until you see small white text. Release both and tap VOL UP quickly.
If you brick it to where you cannot get to recovery (which I think you will be hard pressed to do) use EasyFlasher to reinstall recovery or flash the stock ROM again.
Oh btw, I tried several times to enter recovery the way you said and the TF never turns on.
I always have to connect the charger and press the VOL DOWN for it turn on by itself, and then the small text appears
Sorry about my english man
Sounds like a faulty power button on boot.
frederuco said:
Sounds like a faulty power button on boot.
Click to expand...
Click to collapse
But it works fine if I don't try to boot to recovery.
I am not sure, but at least you can get to recovery with the power cord.
Hi, I did like you said and all went perfect, thank you Just one more thing, its safe to update the ROM using goo manager?
I noticed that the virtual keyboard closes after I type the first letter (in browser, games, play store, etc) and that after unplug my headphones, theres no sound, only with a reboot.
Any way to fix this?
ricardocardoso said:
Hi, I did like you said and all went perfect, thank you Just one more thing, its safe to update the ROM using goo manager?
Click to expand...
Click to collapse
Yes
Sent from my Transformer TF101 using xda app-developers app
ricardocardoso said:
I noticed that the virtual keyboard closes after I type the first letter (in browser, games, play store, etc) and that after unplug my headphones, theres no sound, only with a reboot.
Any way to fix this?
Click to expand...
Click to collapse
Turn off autocorrect in the AOSP keyboard.
Or go grab a new keyboard from the play store.
frederuco said:
Turn off autocorrect in the AOSP keyboard.
Or go grab a new keyboard from the play store.
Click to expand...
Click to collapse
I did that already.
I downloaded Kii Keyboard and at the beggining I had no problems. Then, I changed the theme in the options and now it closes again :/
Last I read in the EOS thread the theme manager had some issues. A different one was listed to use instead somewhere in the thread.
Could be related to that.
Ok, i'll search a bit. And what about the sound issue? Never heard about it?
Sent from my Transformer TF101 using XDA Premium HD app
Oops, missed that.
Try using the K.A.T Toolbox and open it, go to the audio tab and hit the FM34 DSP Reinit button.
Also, if you tick the CASCADE box, it will give you louder volume with the speakers.
That worked, thanks a lot
Sent from my Transformer TF101 using XDA Premium HD app
reboot
ricardocardoso said:
I noticed that the virtual keyboard closes after I type the first letter (in browser, games, play store, etc) and that after unplug my headphones, theres no sound, only with a reboot.
Any way to fix this?
Click to expand...
Click to collapse
you can also use this and other apps to reboot to recovery. Quick Reboot - at the play store.
scott
EDIT I use Transformer Reboot To Recovery
If you are running EOS, why use an app to reboot to recovery?
Just hold the lock button for 3 seconds, choose REBOOT, then on the next popup choose RECOVERY
Good thread, just bookmarked so I can ask some questions in here instead of cluttering up the development thread..
Related
Hi. i just went from virtuos rom to CyanogenMod 7.1 RC1 (v1.0.4).
But now when im waking up the phone it takes about 3-5 sec for it to wake. It took like max 1 sec on virtuos. But 5 on cyanogen. Anyway to fix this?
Thanks in advance
jullejul said:
Hi. i just went from virtuos rom to CyanogenMod 7.1 RC1 (v1.0.4).
But now when im waking up the phone it takes about 3-5 sec for it to wake. It took like max 1 sec on virtuos. But 5 on cyanogen. Anyway to fix this?
Thanks in advance
Click to expand...
Click to collapse
This sounds like you are using setCPU and have a sleep/screen off mode.
Where as VU has a special O/C daemon which is much quicker at switching CPU modes and speeds and is known to have a faster wake time.
ben_pyett said:
This sounds like you are using setCPU and have a sleep/screen off mode.
Where as VU has a special O/C daemon which is much quicker at switching CPU modes and speeds and is known to have a faster wake time.
Click to expand...
Click to collapse
no. Setcpu is not installed
When you say "5 seconds to wake up" what exactly do you mean? Do you mean:
Switch screen off
Switch screen back on again
5 second pause
Lock screen displayed
???
For me the above process is literally instant (even with SetCPU underclocking the CPU to ~350MHz when the screen is off).
If you mean something different, I'm not understanding.
LaKraven said:
When you say "5 seconds to wake up" what exactly do you mean? Do you mean:
Switch screen off
Switch screen back on again
5 second pause
Lock screen displayed
???
For me the above process is literally instant (even with SetCPU underclocking the CPU to ~350MHz when the screen is off).
If you mean something different, I'm not understanding.
Click to expand...
Click to collapse
Ye, i went to play some video game and when i tried to use the phone later the problem was gone
but the problem was Switch screen back on again 5 sec delay. but it's no delay now
jullejul said:
Ye, i went to play some video game and when i tried to use the phone later the problem was gone
but the problem was Switch screen back on again 5 sec delay. but it's no delay now
Click to expand...
Click to collapse
If out only happened once I wouldn't sorry about it
Swyped from HTC Desire S using XDA Premium
Ah... I've seen this before!
Some games don't quit (or even pause) when you press the HOME button, or even when you "quit" them via the game's own menus. This means they're open in the background, sucking up CPU.
The result is it appears as though your phone has inexplicably "slowed down" a lot.
This only stops (of its own accord) when Android's app management stuff determines that the game is no longer needed, and closes it for you.
Easiest ways to ensure this doesn't happen:
1) If you're just pressing the HOME button to leave the game, don't! Keep pressing back, and look for any "are you sure you want to quit" type dialogs (obviously pressing the affirmative button should you see one). If you don't see one, hopefully the game has quit properly.
2) If you notice your phone is running unnaturally slow... go into "Manage Running Services" (I think that's what it's called) in the "Applications" options menu, find the last game you played, click on it, and do a "Force Close". With luck, your phone will run at "full speed" again immediately thereafter!
Hope it helps!
Okay. Thanks
But I found another problem. When I try to start market it says that I need to add an account. But when I press add the app just fc. :-( I tried to start gmail. To. Add an account but gmail just fc. And I went to the account and sync in setting.
But I couldn't add any gmail account
Sent from my HTC Desire S using XDA Premium App
jullejul said:
Okay. Thanks
But I found another problem. When I try to start market it says that I need to add an account. But when I press add the app just fc. :-( I tried to start gmail. To. Add an account but gmail just fc. And I went to the account and sync in setting.
But I couldn't add any gmail account
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
When you wiped the data, cleared the cache, flashed your ROM, flashed the kernel (assuming you put a custom kernel on), did you then flash the Google Apps package (http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip) as well?
If not, download it, stick it on an SD card, reboot into recovery (remember the beloved "adb reboot recovery" command), clear the cache again, then flash the google apps package onto your phone.
Should solve your problem!
LaKraven said:
When you wiped the data, cleared the cache, flashed your ROM, flashed the kernel (assuming you put a custom kernel on), did you then flash the Google Apps package (http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip) as well?
If not, download it, stick it on an SD card, reboot into recovery (remember the beloved "adb reboot recovery" command), clear the cache again, then flash the google apps package onto your phone.
Should solve your problem!
Click to expand...
Click to collapse
Okay. No I didn't install an custom kenel.but I will try to flash the zip
Sent from my HTC Desire S using XDA Premium App
jullejul said:
okay. No i didn't install an custom kenel.but i will try to flash the zip
sent from my htc desire s using xda premium app
Click to expand...
Click to collapse
don't forget to erase your cache before flashing the zip, or you'll "soft-brick" your phone!
LaKraven said:
When you wiped the data, cleared the cache, flashed your ROM, flashed the kernel (assuming you put a custom kernel on), did you then flash the Google Apps package (http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip) as well?
If not, download it, stick it on an SD card, reboot into recovery (remember the beloved "adb reboot recovery" command), clear the cache again, then flash the google apps package onto your phone.
Should solve your problem!
Click to expand...
Click to collapse
ty works
jullejul said:
ty works
Click to expand...
Click to collapse
Happy to help
Enjoy CM7!
LaKraven said:
Happy to help
Enjoy CM7!
Click to expand...
Click to collapse
Ye i will.
Sent from my HTC Desire S using XDA Premium App
Ok, so I did my first root last night with my G2x and flashed CM7 onto it using the instructions here for GB. The process didn't seem to go through at first because it kind of froze for awhile, but when I took out the battery and put it back in it loaded up. (I understand I may have made a mistake here.)
I thought all was good but then I tried to boot up Clockwork recovery to flash the GAPPs zip and everytime I tried it wouldn't go through the screens it is supposed to.
I'd hold the down volume and power buttons and the first LG (white) would show. Then it would bring up a cyan colored horizontal loading bar under the LG. I continue to hold the buttons hoping to see the cyan LG but then screen changes to a box with an orange arrow pointing to an android logo. There is a loading bar under this as well. If I let go here it loads up CM7 but if I continue holding on it takes me to the S/W screen.
I've tried this multiple times but I've kinda given up. I even tried individually installing the apks from the GAPPS zip but only a few of them successfully installed.
At a loss .Please let me know what I can do.
Let me guess. You flashed CWM via ROM manager?
Follow he guide here and let us know how it goes:
http://forum.xda-developers.com/showthread.php?t=1056847
Also, before you install the ROM use the wipe tool in my sig.
I appreciate the response but I did use that thread to flash it.
ae2012 said:
Ok, so I did my first root last night with my G2x and flashed CM7 onto it using the instructions here for GB. The process didn't seem to go through at first because it kind of froze for awhile, but when I took out the battery and put it back in it loaded up. (I understand I may have made a mistake here.)
I thought all was good but then I tried to boot up Clockwork recovery to flash the GAPPs zip and everytime I tried it wouldn't go through the screens it is supposed to.
I'd hold the down volume and power buttons and the first LG (white) would show. Then it would bring up a cyan colored horizontal loading bar under the LG. I continue to hold the buttons hoping to see the cyan LG but then screen changes to a box with an orange arrow pointing to an android logo. There is a loading bar under this as well. If I let go here it loads up CM7 but if I continue holding on it takes me to the S/W screen.
I've tried this multiple times but I've kinda given up. I even tried individually installing the apks from the GAPPS zip but only a few of them successfully installed.
At a loss .Please let me know what I can do.
Click to expand...
Click to collapse
When it get to the point where "the cyan colored horizontal loading bar" let go of the volume and power button and see if it boots into CWM.
Ok, I tried that and it went to that android logo screen again. Then it went to a black screen and then the cyan LG logo screen. From there it booted up CM7.
I just noticed when I try to boot into Clockwork it erases everything I added to it including contacts and apps I installed.
ae2012 said:
Ok, I tried that and it went to that android logo screen again. Then it went to a black screen and then the cyan LG logo screen. From there it booted up CM7.
I just noticed when I try to boot into Clockwork it erases everything I added to it including contacts and apps I installed.
Click to expand...
Click to collapse
Try rooting process all over again... just make sure battery have plenty of charge and make sure during any of the process there's no interruptions... let us know what happen after that...
Sent from my LG-P999 using xda premium
I will unroot and try again. A few questions though:
I'm reading and it looks like I need to be able to boot into CWR to be able to unroot...is using ROM Manager a safe alternative?
And also, while I followed the instructions for flashing through the thread you provided last time, I read that I may need to erase/wipe certain types of data before I do so to avoid the market problems. Can someone provide me information on that?
I just want to make sure I do this right a second time.
ae2012 said:
I will unroot and try again. A few questions though:
I'm reading and it looks like I need to be able to boot into CWR to be able to unroot...is using ROM Manager a safe alternative?
And also, while I followed the instructions for flashing through the thread you provided last time, I read that I may need to erase/wipe certain types of data before I do so to avoid the market problems. Can someone provide me information on that?
I just want to make sure I do this right a second time.
Click to expand...
Click to collapse
No need to unroot... as long as your computer still detect your phone... just flash everything again... I mean since you want to root... I would just do all the rooting process again... and reflash clock work... don't use rom manager to flash clockwork mod...
Or
And since you can't get into clockwork... you can just try flashing clockwork again... no rom manager
Sent from my LG-P999 using xda premium
Sweet, so I reflashed CWR and CM7 and I got my contacts back and several other minor issues were corrected.
I am experiencing a new problem now though. Whenever I try to download from the market it tells me "[App name] could not be downloaded due to an error."
What can be done to fix this?
ae2012 said:
Sweet, so I reflashed CWR and CM7 and I got my contacts back and several other minor issues were corrected.
I am experiencing a new problem now though. Whenever I try to download from the market it tells me "[App name] could not be downloaded due to an error."
What can be done to fix this?
Click to expand...
Click to collapse
Try flashing Google apps again. Cm7 doesn't include them in their builds.
Sent from my LG-P999
Worked like a charm. Thanks, yall are the best.
ae2012 said:
I will unroot and try again. A few questions though:
I'm reading and it looks like I need to be able to boot into CWR to be able to unroot...is using ROM Manager a safe alternative?
And also, while I followed the instructions for flashing through the thread you provided last time, I read that I may need to erase/wipe certain types of data before I do so to avoid the market problems. Can someone provide me information on that?
I just want to make sure I do this right a second time.
Click to expand...
Click to collapse
Rom Manager is not a safe alternative. Stay with Nvidia ClockworkMod.
Its should be a blue lg logo when you have to let go of the buttons.
Sent from my LG-P999 using xda premium
ae2012 said:
I will unroot and try again. A few questions though:
I'm reading and it looks like I need to be able to boot into CWR to be able to unroot...is using ROM Manager a safe alternative?
And also, while I followed the instructions for flashing through the thread you provided last time, I read that I may need to erase/wipe certain types of data before I do so to avoid the market problems. Can someone provide me information on that?
I just want to make sure I do this right a second time.
Click to expand...
Click to collapse
Every time before you re- flash a rom I would recommend doing a data/factory reset within clockwork recovery. then Wipe your cache. And then even a wipe of the dalvic cache under advanced settings. Then flash the rom then gapps. Then reboot. Its called doing a clean install. It just makes everything smoother when re- flashing. And if your apps ever not update like that again just fix the permissions in clockworkmod then reboot. It usually fixes it. And i don't recommend flashing directly from the rom manager. Do it from recovery instead. Hope this helps.:thumbup:
Sent from my LG-P999 using XDA
[edit]
Sent from my G2X.
Rocking stock CM 7.2.0-RC1
Similar issue, totally different outcome...
Ladies and Gentlemen (and low-lifes),
I have found myself in a similar situation, after recently flashing a ROM, to where I am now unable to boot into CW Recovery. The ROM flashed is working fine but when I attempt to boot into recovery I get a black screen and it never progresses beyond that. I have attempted to reflash of course via NVFlasher and from all indications it's been a successful flash. That said, the results remain the same... black screen.
FYI: I have not yet attempted to flash back to Stock Recovery.
•Current Rom - Owain's Domination v77 (a great ROM by the way)
•Current kernel - Harsh's 3.0.32
•Used Nullifier to prep device for ROM install (as I have been doing for sometime now)
If anyone has any experience w/this issue or any advice going forward I would greatly appreciate it.
UPDATE: (that was fast huh?) .................................................................................................................................................................................................
So I went ahead and flashed the Stock Recovery, tested and got access. I then flashed CWM 5.0.2.0 and to my delight was able to see the CWM console. I let go of the power and volume down buttons and the phone rebooted. Now the ROM will not boot, just sits in a forever cycle on the splash screen and the results continue to be the same as recently mentioned for attempting to get into the freshly flashed recovery.
dark ma++er said:
UPDATE: (that was fast huh?) .................................................................................................................................................................................................
So I went ahead and flashed the Stock Recovery, tested and got access. I then flashed CWM 5.0.2.0 and to my delight was able to see the CWM console. I let go of the power and volume down buttons and the phone rebooted. Now the ROM will not boot, just sits in a forever cycle on the splash screen and the results continue to be the same as recently mentioned for attempting to get into the freshly flashed recovery.
Click to expand...
Click to collapse
Ok, I will bring my concerns to an end now. I forced CWM to remain in play by not letting go of the power and vol. down buttons then using my thumb to see if I could stroll through options in CWM. Once I accessed a few it remain stable. I nullified and re-flashed my ROM and all seems ok in my personal corner of the universe. I am now able to boot into CWM without issue.
I posted a thread a few days ago about not being able to power off or restart my Samsung Galaxy s2 skyrocket on ATT. I am using SKy's ICS rom http://forum.xda-developers.com/showthread.php?t=1602216 with the newest update and I still cannot turn it off. The response I got was to use the Darkside Wipe, I tried that, loaded the base rom, then rebooted (it rebooted on its own) flashed the update, and now im back to it not being able to turn off.... I have searched every where and everyone says the issue is resolved, but its not working. Please point me in the right direction to fix this issue.
Pull the battery
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Ive lived without if i need to reboot then hold power till it reboots and if i need recovery then do the same but press volume buttons right as it shuts down
Sent from my SAMSUNG-SGH-I727 using xda premium
Thank you! Did't want to have to pull the battery anytime I needed to restart my phone. Holding the power button in for 10-15 seconds even when its froze forces it to restart. At least now I can put my case back on it....
I was wondering if anyone knew a way to stop it from freezing up? Or at least know whats causing it?
I had this problem too with the Ics roms. If you use the touch recovery to wipe factory data reset it should work. I used to one recommended in the sky Ics thread and had no problems after that.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
irtnerapleasure
Do you have a link to it? I have been looking for options and I must be missing it.
I did do the Dark Side complete wipe, and after it worked, it stopped working when I applied the update.
perkinsjm said:
Do you have a link to it? I have been looking for options and I must be missing it.
I did do the Dark Side complete wipe, and after it worked, it stopped working when I applied the update.
Click to expand...
Click to collapse
Just factory wipe, wipe cache, dalvik in whatever cwm you have
Ill try that again, and redownload the patch and see if that fixes it. Is there anyway to get an error log to see whats FCing or crashing?
perkinsjm said:
Ill try that again, and redownload the patch and see if that fixes it. Is there anyway to get an error log to see whats FCing or crashing?
Click to expand...
Click to collapse
Logcat with adb
Hi, last night my wifi seemed to cut off while using my tablet. I tried to cut it back on and it got stuck in the "trying to connect to wifi" stage. I cant press the button and it wont turn back on. I was running Chromi X 4.6.6 at the time. Today, I flashed 4.6.8, hoping it would reset and fix the problem, but the problem still is there. I am really nervous I broke my wifi chip or something. Here is a screenshot of what is happening. I hope someone can help me.
Thank you.
wl123 said:
Hi, last night my wifi seemed to cut off while using my tablet. I tried to cut it back on and it got stuck in the "trying to connect to wifi" stage. I cant press the button and it wont turn back on. I was running Chromi X 4.6.6 at the time. Today, I flashed 4.6.8, hoping it would reset and fix the problem, but the problem still is there. I am really nervous I broke my wifi chip or something. Here is a screenshot of what is happening. I hope someone can help me.
Thank you.
Click to expand...
Click to collapse
Is the WiFi icon greyed out in the bottom right? If so try removing your Google account from settings and the readd it. I think Google have been having some DNS issues recently.
sbdags said:
Is the WiFi icon greyed out in the bottom right? If so try removing your Google account from settings and the readd it. I think Google have been having some DNS issues recently.
Click to expand...
Click to collapse
I removed my Google account and tried to re add it. I get to the part where I need to be connected to wifi and I get this. Something seems to be horribly wrong.
wl123 said:
I removed my Google account and tried to re add it. I get to the part where I need to be connected to wifi and I get this. Something seems to be horribly wrong.
Click to expand...
Click to collapse
Do you have a back up nandroid to go back to? Try a clean wipe as well to eliminate software issues.
sbdags said:
Do you have a back up nandroid to go back to? Try a clean wipe as well to eliminate software issues.
Click to expand...
Click to collapse
Yes I have a backup from like chromi 4.5. I am trying to restore right now. If I clean wipe it, wont it delete the nandroid backups?
wl123 said:
Yes I have a backup from like chromi 4.5. I am trying to restore right now. If I clean wipe it, wont it delete the nandroid backups?
Click to expand...
Click to collapse
Just do a factory wipe. As long as you don't do a full data wipe you will keep your nandroids if they are on internal.
This :http://www.transformerforums.com/fo...h-will-not-turn-asus-say-start-over-help.html
is exactly the same problem I am having.
sbdags said:
Just do a factory wipe. As long as you don't do a full data wipe you will keep your nandroids if they are on internal.
Click to expand...
Click to collapse
How long does it usually take to Restore Data when restoring a nandroid backup? It seems to be taking a long time
wl123 said:
How long does it usually take to Restore Data when restoring a nandroid backup? It seems to be taking a long time
Click to expand...
Click to collapse
15 mins... ish
BTW you don't need to wipe when restoring as it does that for you automatically.
sbdags said:
15 mins... ish
BTW you don't need to wipe when restoring as it does that for you automatically.
Click to expand...
Click to collapse
**** me. Restored back to 4.6.4. Wifi is still broken. Gets to the the "Turning Wi-Fi- on..." screen and never turns on. I am freaking out.
Do you think doing this will work? And if so, how do I start a terminal session?
I've had the Bluetooth not turning on issue four times on my TF101 - the first two times a hard reset (no data loss) fixed it - have you tried this, as opposed to a restart? - and the next two times I just waited and eventually BT turned on. I've never encountered this with WiFI (yet).
In case anyone else encounters this, on a rooted tablet the following might also help:
Open a terminal session and -
su - <enter>
cd /system/bin <enter>
stop bluetoothd <enter>
start bluetoothd -n <enter>
This will force stop and then restart the Bluetooth daemon. I haven't yet worked out (mainly because I haven't need to) what the equivlent process is for WiFi.
wl123 said:
**** me. Restored back to 4.6.4. Wifi is still broken. Gets to the the "Turning Wi-Fi- on..." screen and never turns on. I am freaking out.
Do you think doing this will work? And if so, how do I start a terminal session?
I've had the Bluetooth not turning on issue four times on my TF101 - the first two times a hard reset (no data loss) fixed it - have you tried this, as opposed to a restart? - and the next two times I just waited and eventually BT turned on. I've never encountered this with WiFI (yet).
In case anyone else encounters this, on a rooted tablet the following might also help:
Open a terminal session and -
su - <enter>
cd /system/bin <enter>
stop bluetoothd <enter>
start bluetoothd -n <enter>
This will force stop and then restart the Bluetooth daemon. I haven't yet worked out (mainly because I haven't need to) what the equivlent process is for WiFi.
Click to expand...
Click to collapse
I got that problem before. I believed that this was what I did if you want to try it out:
1. Wipe both Caches and data
2. Restart your system
3. Shut it off again
4. Go to recovery and select the Android for a cold boot
5. Restart it again and it work for me
I don't know why I had to go through that sequences but I seem to work for me, good luck.
LetMeKnow said:
I got that problem before. I believed that this was what I did if you want to try it out:
1. Wipe both Caches and data
2. Restart your system
3. Shut it off again
4. Go to recovery and select the Android for a cold boot
5. Restart it again and it work for me
I don't know why I had to go through that sequences but I seem to work for me, good luck.
Click to expand...
Click to collapse
Thanks im about to try.
Q1: How do you wipe cache and data without reset?
So, Wipe, Restart, Turn back off. Restart into recovery and select android for a cold boot? What do you mean by that?
wl123 said:
Thanks im about to try.
Q1: How do you wipe cache and data without reset?
So, Wipe, Restart, Turn back off. Restart into recovery and select android for a cold boot? What do you mean by that?
Click to expand...
Click to collapse
1. Restart into your recovery, assuming TWRP, and select Wipe option in your recovery
2. When you boot into recovery, there are 3 icons, the middle icon is the android that I am talking about
Hope that helps
LetMeKnow said:
1. Restart into your recovery, assuming TWRP, and select Wipe option in your recovery
2. When you boot into recovery, there are 3 icons, the middle icon is the android that I am talking about
Hope that helps
Click to expand...
Click to collapse
Everytime I restart to recovery, it loads TWRP. I see a little android icon as it is booting, but its not like I can click on him. When I wiped using TWRP, it did a factory reset. I restarted to system, but the damn wifi is still not working. I am so frustrated.
Thank you for your help. I am going to eat and drink a beer and try again later.
wl123 said:
Everytime I restart to recovery, it loads TWRP. I see a little android icon as it is booting, but its not like I can click on him. When I wiped using TWRP, it did a factory reset. I restarted to system, but the damn wifi is still not working. I am so frustrated.
Thank you for your help. I am going to eat and drink a beer and try again later.
Click to expand...
Click to collapse
Hehe, I have been there so many times before. You can use the volume up to select and volume down to confirm. Any way, did you tweak your device before the problem? Did you use D2SD? Maybe you explain a little more details what you did so that people have better understanding of your problem. The worse case is you have to flash the rom again .
LetMeKnow said:
Hehe, I have been there so many times before. You can use the volume up to select and volume down to confirm. Any way, did you tweak your device before the problem? Did you use D2SD? Maybe you explain a little more details what you did so that people have better understanding of your problem. The worse case is you have to flash the rom again .
Click to expand...
Click to collapse
I was not running Data2SD (at least I dont think). I just figured out how to cold boot android. Do you think this could be a hardware issue with my wireless card? It seems to me like it has to be some sort of software bug
wl123 said:
I was not running Data2SD (at least I dont think). I just figured out how to cold boot android. Do you think this could be a hardware issue with my wireless card? It seems to me like it has to be some sort of software bug
Click to expand...
Click to collapse
I had that problem before. Therefore, I am very sure that it is a program bug. Do you use Micro SD in your tablet? When I tweak my tablet, there are all kinds of problems that I have encountered. If you give me some more details, I might be able to help you out.
LetMeKnow said:
I had that problem before. Therefore, I am very sure that it is a program bug. Do you use Micro SD in your tablet? When I tweak my tablet, there are all kinds of problems that I have encountered. If you give me some more details, I might be able to help you out.
Click to expand...
Click to collapse
OK. I was running Chromi-X 4.6.6 ODEX at the time it happened. I used to use a micro sd card but it was acting weird and I took it out. I have been using only the internal SD for the last ~3 months. I use _that/ stock modded kernel variant based from ASUS Stock that comes with the ChromiX mod. I run Apex launcher. Android version 4.2.1.
Using TWRP 2.5 on 10.6.1.14.4 via goomanager.
So far I have tried:
- Flashing ChromiX 4.6.8
- Recovering an old nandroid backup (4.6.4)
- Clearing cache and data via TWRP and restarting with cold boot
wl123 said:
OK. I was running Chromi-X 4.6.6 ODEX at the time it happened. I used to use a micro sd card but it was acting weird and I took it out. I have been using only the internal SD for the last ~3 months. I use _that/ stock modded kernel variant based from ASUS Stock that comes with the ChromiX mod. I run Apex launcher. Android version 4.2.1.
Using TWRP 2.5 on 10.6.1.14.4 via goomanager.
So far I have tried:
- Flashing ChromiX 4.6.8
- Recovering an old nandroid backup (4.6.4)
- Clearing cache and data via TWRP and restarting with cold boot
Click to expand...
Click to collapse
If you don't mind, you can try a clean install.
1. Boot back into twrp and select wipe, use format option instead of wipe
2. Install cromi x, prefer 3.6.5
3. After the installation is completed, restart your tablet and leave it there for a few minutes
4. Make sure that you must SHUT IT OFF COMPLETELY for a few seconds and turn it back on
Hope it will solve your problem, good luck.
LetMeKnow said:
If you don't mind, you can try a clean install.
1. Boot back into twrp and select wipe, use format option instead of wipe
2. Install cromi x, prefer 3.6.5
3. After the installation is completed, restart your tablet and leave it there for a few minutes
4. Make sure that you must SHUT IT OFF COMPLETELY for a few seconds and turn it back on
Hope it will solve your problem, good luck.
Click to expand...
Click to collapse
Regarding #2. Where would I find a download of chromix 3.6.5?
Holy ****.
I just rebooted into TWRP before formating, and then rebooting back to system to save my pictures, and all of a sudden the WiFi is working again. Going to flash the latest Chromi X and see what happens
Hi,
So i decided to install NOVA launcher and kept it as default launcher.
No when i wanted to go back to google launcher the system was getting crashed and some error like : "systemui" is not working was poping up.
Meanwhile i was getting notifications of whatsapp messenger and i could use it but when i was trying to exit the app , again the problem occured.
Thats when i decided to reboot the phone to my bad luck it is not going further after "FOUR CIRCLES(red,green,yellow and blue) which comes after google logo.
I had previously owned S2 and when i used nova launcher and tried to switch back ( aftr uninstalling nova) it automatically use to use google launcher.
Please help.
Thanks & Regards,
V
If it won't boot you may have to fastboot the factory image can you get into recovery and do you have a custom recovery If so try clearing cache in it
Sent from my SAMSUNG-SGH-I727
jd1639 said:
If it won't boot you may have to fastboot the factory image can you get into recovery and do you have a custom recovery If so try clearing cache in it
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
I went into recovery and tried factory reset as well as wiping cache but it takes for ever.
So again , i just have powered off the phone and waiting for suggestions.
I guess i need to flash factory image ?
Thnks
V
vzuwOw said:
I went into recovery and tried factory reset as well as wiping cache but it takes for ever.
So again , i just have powered off the phone and waiting for suggestions.
I guess i need to flash factory image ?
Thnks
V
Click to expand...
Click to collapse
How long is forever? Give it a good 10 minutes, maybe longer
Sent from my SAMSUNG-SGH-I727
vzuwOw said:
Hi,
So i decided to install NOVA launcher and kept it as default launcher.
No when i wanted to go back to google launcher the system was getting crashed and some error like : "systemui" is not working was poping up.
Meanwhile i was getting notifications of whatsapp messenger and i could use it but when i was trying to exit the app , again the problem occured.
Thats when i decided to reboot the phone to my bad luck it is not going further after "FOUR CIRCLES(red,green,yellow and blue) which comes after google logo.
I had previously owned S2 and when i used nova launcher and tried to switch back ( aftr uninstalling nova) it automatically use to use google launcher.
Please help.
Thanks & Regards,
V
Click to expand...
Click to collapse
I need you to answer a few questions before anyone can help...
Do you have a custom recovery installed? (Eg. TWRP or CM?)
- If not, are you rooted?
- If you do, have u made a Backup through your custom recovery?
- If you're not rooted, do you have warranty?
- If you don't have warranty, how long have you had you're phone for, because Google provide warranty for a certain amount of time with your phone.
Basically, if you have a custom recovery installed or are not rooted with warranty, don't panic.
In not an advanced user but I know done stuff... And there's always a way!
Sent from my Nexus 5 using Tapatalk
jd1639 said:
How long is forever? Give it a good 10 minutes, maybe longer
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
Gave good 10 + mins
Will try it one more time.I guess it should hardly take about 30 secs or so.
Oh, and also, see if you can fastboot by pressing the power button and volume down whilst booting up. If you can't, then try pressing power button + volume up + volume down whilst booting up.
Sent from my Nexus 5 using Tapatalk
zz
:good:
ProVickers said:
I need you to answer a few questions before anyone can help...
Do you have a custom recovery installed? (Eg. TWRP or CM?) - NO,2 month old phone , full stock.
- If not, are you rooted? NO
- If you do, have u made a Backup through your custom recovery? NO,I dont mind if my data is lost
- If you're not rooted, do you have warranty? YES,but now i stay in different country.so count it as NO
- If you don't have warranty, how long have you had you're phone for, because Google provide warranty for a certain amount of time with your phone. have been using since 2 months
Basically, if you have a custom recovery installed or are not rooted with warranty, don't panic.
In not an advanced user but I know done stuff... And there's always a way!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Answers in BOLD
ProVickers said:
Oh, and also, see if you can fastboot by pressing the power button and volume down whilst booting up. If you can't, then try pressing power button + volume up + volume down whilst booting up.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I can do that , it is showing me options over there like recovery,poweroff,bootloader recovery,etc.
If factory reset doesn't work then you option is to flash the factory image. Have you unlocked the bootloader?
Edit, you'll want to review this. http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 5
jd1639 said:
If factory reset doesn't work then you option is to flash the factory image. Have you unlocked the bootloader?
Sent from my Nexus 5
Click to expand...
Click to collapse
No,I hav'nt modded my phone.
Just tried using nova launcher and uinstalled so this prob.
PS: I this any how to do with google search.Because i had disabled it from settings.
vzuwOw said:
PS: I this any how to do with google search.Because i had disabled it from settings.
Click to expand...
Click to collapse
This is probably why it crashed. Your phone doesn't have a launcher to boot into. That's the reason it is boot looping. As mentioned earlier, you'll have to flash the factory image.
jd1639 said:
If factory reset doesn't work then you option is to flash the factory image. Have you unlocked the bootloader?
Edit, you'll want to review this. http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 5
Click to expand...
Click to collapse
UPDATE : i can go into fastboot by pressing power + volume down
There earlier when i clicked on recovery it showd me option for cache wipe and data factory reset but instead of that i see a red triangle which has a exclamation mark on a sleeping android logo.
I have nt unlocked the bootloader.
El Daddy said:
This is probably why it crashed. Your phone doesn't have a launcher to boot into. That's the reason it is boot looping. As mentioned earlier, you'll have to flash the factory image.
Click to expand...
Click to collapse
Yea, i feel the same. I forgot it was google launcher and its a nexus phone.
If it would have been some other trebuche launcher(like in samsung) , this problem would'nt have persisted.
vzuwOw said:
UPDATE : i can go into fastboot by pressing power + volume down
There earlier when i clicked on recovery it showd me option for cache wipe and data factory reset but instead of that i see a red triangle which has a exclamation mark on a sleeping android logo.
I have unlocked the bootloader.
Click to expand...
Click to collapse
That is the stock recovery. You can press both volume buttons at the same time, to show the recovery options.
Flashing the factory image is very easy. You put your phone in fastboot mode, plug it into your computer, and simple run the Flashall.bat (or .sh depending on your OS.)
Touchwiz Home in Samsung devices does not rely on google search. Our Nexus has a launcher that requires google search to run. Otherwise you can install AOSP launcher.
Beauenheim said:
That is the stock recovery. You can press both volume buttons at the same time, to show the recovery options.
Flashing the factory image is very easy. You put your phone in fastboot mode, plug it into your computer, and simple run the Flashall.bat (or .sh depending on your OS.)
Touchwiz Home in Samsung devices does not rely on google search. Our Nexus has a launcher that requires google search to run. Otherwise you can install AOSP launcher.
Click to expand...
Click to collapse
Done.
Phew
Thanks a lot everyone.
Sent from my Nexus 5 using Tapatalk
@jd1639
@Beauenheim
@ProVickers
@El Daddy
Thanks a lot all of you Cookies are in transit
Sent from my Nexus 5 using Tapatalk
vzuwOw said:
@jd1639
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Glad you got it working
Sent from my Nexus 5
Repeated Post.
vzuwOw said:
Repeated Post.
Click to expand...
Click to collapse
@vzuwOw if you run into this problem again just fastboot flash the system.img, not the flash-all.bat. it would have kept the rest of your settings and you wouldn't have to redo your while phone.
Sent from my Nexus 5