Develop Bugs

[Q] Stuck on "touch android to begin" after attempting to flash stock

Hello, I tried to post this in the developer forum but I am new so not allowed. I currently have a Galaxy S2 White t989 from t-mobile. Two days ago I upgraded my phone to official ICS via kies, I was already on Stock GB before and ICS made me phone practically unusable. I read a thread with directions on how to flash to stock from here:
http://forum.xda-developers.com/showthread.php?t=1513359
I followed those procedures to a t and now when my phone boots I can't get it past touch "android" to begin and a million things begin to "force close..g,apps,etc) Is there something I am missing? Just got this phone and I hope I haven't forever messed it up. If anyone has a link to a thread already solving the same issue...please let me know. I am a newbie with flashing so please have patience.

factory reset data

Thanks for your reply, but how would I go about doing this...I can't get pass the set-up screen to access the phone features. Is there another method to performing this.

Happened to me also, what I read was install clockwork recovery via ODIN (look for the thread in the other sections). Then you'll need to wipe cache and dalvic cache. Then you'll be able to continue to set up your phone.

OK great, will try it out, please wish me luck everyone. Love my s2, would be terrible if it is unusable.

Ok, so I installed clockwork recovery and still having the same issues...how I didn't anything with the recovery prompting to clear those caches?

yay!! back on stock and everything is working great..much thanks!!

Hello
I'm having the same issue that was stated above. I used the SGSII toolkit to do the stock rom flash and that is how I got to this point. I just wanted to know if using the process shown here http://forum.xda-developers.com/showthread.php?t=1858435 ? I skipped number 1 since it says it is optional. I now cannot find the "T989UVLH1.tar.md5" and all I can find is a file named "T989UVLH1_T989TMBLH1_T989UVLH1_HOME.tar.md5". Am I supposed to rename this one? Thank you very much.
edit.
I used the file T989UVLH1_T989TMBLH1_T989UVLH1_HOME.tar.md5 in odin>PDA>start. Then had an com.android.phone stopped unexpectedly problem. Used the toolkit to do a factory reset and everything is fine now. I'll have to do a little more research before I try rooting again, gave me too many headaches.

Custom ROM infinite first boot

Firstly: I'm a total n00b for this. I have flashed custom ROMs before, but not for Nexus, so this is my first attempt, so far failing spectacularly.
That said, I'd appreciate advice on both what I did wrong and how to un-brick my phone.
I searched and my problem seems strictly linked to bad flashing, but all solutions are phone specific and I haven't found a thread for Galaxy nexus, so here goes:
I chose this firmware for my flash. I also used the toolkit from stickied post above.
I unlocked the bootloader and then ran (not installed) the CWM tools. Using them I flashed the image directly. The phone was not rooted though I later ran the rooting procedure and it finished without reporting any particular errors. Android naturally never booted during this procedure.
Anyway, my phone now stays in boot animation indefinitely. Recovery mode with fastboot works, but no android joy.
Help greatly appreciated.

More info is needed you didn't mention toro, toro plus, maguro. Ask you need to do is bout into bootloader and fastboot your images back to stick look in your models thread on how to do that so you can get the correct ones.
Sent from my Galaxy Nexus using xda premium

Sorry for panicking too soon. Phone unbricked. Would still appreciate info on what I did wrong to brick it in the first place.

Beamer9408 said:
More info is needed you didn't mention toro, toro plus, maguro. Ask you need to do is bout into bootloader and fastboot your images back to stick look in your models thread on how to do that so you can get the correct ones.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hm, I've been reading on toolkit and roms for a couple of days now and I still can't really say what toro or maguro is. In what way would they be important for my troubles?

velis74 said:
Hm, I've been reading on toolkit and roms for a couple of days now and I still can't really say what toro or maguro is. In what way would they be important for my troubles?
Click to expand...
Click to collapse
It's very important to know what type of google nexus you have. Majority of custom ROMs are only compatible to certain type of GNex. Maguro is for GSM GNex while TORO is for CDM/LTE GNex. Check the link below for more info:
https://groups.google.com/forum/#!msg/android-building/qzSxFEqWvNg/qanfxMkzXHMJ
One more thing, aside from Maguro and Toro, you still need to know what build or version of GNex you have (yakju or takju). This can also be considered when flashing new custom ROMs. I know majority (or all) of the ROMs works well with either yakju or takju, there is still a slight possibility that you will encounter an issue with the version. Check out the links below for more info regarding yakju and takju:
http://forum.xda-developers.com/showthread.php?t=1778543
http://forum.xda-developers.com/showthread.php?t=1617685

Oh, in that case, I have a GSM version, Maguro it would seem.
The ROM I downloaded doesn't specifically say, but the same developer posted another ROM for which he confirmed GSM compatibility.
So can I myself find out what ROM this is since I can't ask the question in the development thread (I don't have 10 posts yet)?

did you clear all the caches via custom recovery? Although I haven't hit issues with my nexus while flashing, past devices, a factory reset sorts the bootloop most often (unless it was a bad flash). Just note that factory resetting the nexus gets rid of ALL of your data since there isn't an external SD to house your files and keep them protected from a wipe.
I would recommend you making a nandroid backup now that you're up and running again btw
Just my 2 cents

Kohawk09 said:
did you clear all the caches via custom recovery? Although I haven't hit issues with my nexus while flashing, past devices, a factory reset sorts the bootloop most often (unless it was a bad flash). Just note that factory resetting the nexus gets rid of ALL of your data since there isn't an external SD to house your files and keep them protected from a wipe.
I would recommend you making a nandroid backup now that you're up and running again btw
Just my 2 cents
Click to expand...
Click to collapse
Yes, I cleared everything I found in main menu and advanced menu of CWM.
Do I *NEED TO* root my phone in order to install a custom ROM? I would think not, but one can't be sure. That's why I only unlocked bootloader before flashing.
Edit: Yes, I found about the factory reset the hard way. Executed full wipe, then tried to flash...

velis74 said:
Yes, I cleared everything I found in main menu and advanced menu of CWM.
Do I *NEED TO* root my phone in order to install a custom ROM? I would think not, but one can't be sure. That's why I only unlocked bootloader before flashing.
Click to expand...
Click to collapse
I would think you should have rooted... my logic is that you're flashing a zip, so you're making changes to /system, which requires root. I'm not technical enough to say whether or not installing a zip can work around not having root access, but I would think not. If you were flashing system images, I would think you could get by without rooting, but not for just a zip file.
Have you taken a look at the toolkit? Soon as I got my nexus I did the one click to unlock, root, install CWM. Took less than 10 min. I already knew fastboot commands, so no reason for me to do it manually if I can get it done automatically.

Kohawk09 said:
I would think you should have rooted... my logic is that you're flashing a zip, so you're making changes to /system, which requires root. I'm not technical enough to say whether or not installing a zip can work around not having root access, but I would think not. If you were flashing system images, I would think you could get by without rooting, but not for just a zip file.
Have you taken a look at the toolkit? Soon as I got my nexus I did the one click to unlock, root, install CWM. Took less than 10 min. I already knew fastboot commands, so no reason for me to do it manually if I can get it done automatically.
Click to expand...
Click to collapse
no to toolkits... just no...
you do not need root to flash custom roms, only an unlocked bootloader and CWM or TWRP for your recovery.

Zepius said:
no to toolkits... just no...
you do not need root to flash custom roms, only an unlocked bootloader and CWM or TWRP for your recovery.
Click to expand...
Click to collapse
Why all the hate for the toolkit? Probably the only confusing thing to me since moving to the nexus is why so many seem to be against its use... I think its a great and helpful tool.

Kohawk09 said:
Why all the hate for the toolkit? Probably the only confusing thing to me since moving to the nexus is why so many seem to be against its use... I think its a great and helpful tool.
Click to expand...
Click to collapse
go look at Q&A
everyday there are at least 5-10 threads saying "HELP I BRICKED MY NEXUS... i used this toolkit but i have no idea what happened to my phone"
if someone is too lazy to type in these 2 commands and then flash su.zip to their phone, they dont need to be dinking with custom ROMs
Code:
fastboot oem unlock
fastboot flash recovery nameofclockworkortwrp.img
nexus phones are some of the easiest phones to unlock and root. there is no real need for a toolkit.

I'm currently making another attempt, but this time I'm rooting the phone and trying an image that is confirmed GSM.

Zepius said:
go look at Q&A
everyday there are at least 5-10 threads saying "HELP I BRICKED MY NEXUS... i used this toolkit but i have no idea what happened to my phone"
if someone is too lazy to type in these 2 commands and then flash su.zip to their phone, they dont need to be dinking with custom ROMs
Code:
fastboot oem unlock
fastboot flash recovery nameofclockworkortwrp.img
nexus phones are some of the easiest phones to unlock and root. there is no real need for a toolkit.
Click to expand...
Click to collapse
makes sense.... agree its probably more of a hinder than a help for those without basic fastboot knowledge. Especially since that knowledge is needed for getting out of a bind many times. Was just curious why I see some much negativity towards it...I still think its a useful tool to save time, at least from my perspective, if you already have that background. The files are all downloaded together and it was more of a convenience thing for me at least. The driver piece is probably the most helpful, since they can be a real PITA if there are leftovers from previous devices...

Just thought I pop my head in and say you were bootlooped. Not bricked. Not even soft bricked as that would constitute you had no recovery, which you did have. Just getting you clear on the lingo we use here.
Sent From My Toro+ via SkyBlue Tapatalk

Seems I chose a bad ROM after all. Flashing to CdTDroid's other ROM worked immediately.
Well, almost: after flash it would continuously report "system UI stopped working" or some such. I had to perform another factory reset before it actually worked as it should.
Now to go test if my issues with this phone are finally over or not.

velis74 said:
Seems I chose a bad ROM after all. Flashing to CdTDroid's other ROM worked immediately.
Well, almost: after flash it would continuously report "system UI stopped working" or some such. I had to perform another factory reset before it actually worked as it should.
Now to go test if my issues with this phone are finally over or not.
Click to expand...
Click to collapse
before you install a rom, always wipe data/cache.

That's the problem: I thought I did. Anyway, it's working now. Will have another go at CM later. Since I'm on custom ROM I might as well go all the way
Sent from my Galaxy Nexus using xda app-developers app

velis74 said:
I'm currently making another attempt, but this time I'm rooting the phone and trying an image that is confirmed GSM.
Click to expand...
Click to collapse
You don't need to root, as flashing the ROM will wipe the root. Most ROMs come with root access already, so people don't notice when they flash.

Yeah, figured as much + stopped doing all the unnecessary crap. Turns out flashing takes few steps but I dare not be as careless to say it's easy.
I have now successfully flashed the CM10 ROM by CdTDroiD straight from stock 4.0.4.
Turns out I misinterpreted "wipe data/factory reset" in CWM. It doesn't clear the filesystem (/sdcard) as I thought. Seems I managed to delete my files some other way during the first flashing attempt. Not clearing data was the cause of bootloop as Über reminds me it's called.
I did all that plus kept the original ICS animation which I like better than JB one. I'm really happy thus far having used it for a couple of hours.

[Q] Rom - wipe issues

Verizon Toro cdma
I I think I know what is wrong, but can't figure out exactly how to get it fixed. I crushed my screen this weekend on my GN. So I found a decent one on Craigs. Guy had it rooted/unlocked/JB. I'm not sure what bootloader he had on it and I know for a face that it did not have the latest JB Radios.
I basically want to wipe this thing and get a stock JB back on it and then put my backed up JB rom that I have in clockwork. I can not get it to recover to this backup, but I can get it to restore back to my ICS backup. I have been trying to use wugtoolkit and have successfully got CWM touch put on, but as far as roms, I'm stuck.
I can't even flash back to stock rom in Wug??
Every time I do a factory wipe, etc in CWR it will not boot.
I went to factory images on google and didn't see a 4.1.1?? I thought they came out with it?
Any help would be appreciated.

1) stop using a toolkit.
2) there are no factory images from google for JB for the vzw nexus up yet.
3) follow this guide to the return to stock and then get the OTA to JB: http://forum.xda-developers.com/showthread.php?t=1626895

I will look into it.
Thank you

I tried that way, but commandline fails to find fastboot. I can flash the stock image through toolkit (yeah I know you said not to, but it is the only thing that works) yet it will never boot afterwards. Also the radios fail to install.
I just understand why my backup will not install. I keep getting error while restoreing /system

did you follow the steps exactly?
doesnt sound like you did.

Yep, opened up my command line, cd to the directory where the files were unzipped with 7-zip. Typed in fastboot and it says it doesn't understand that command. Using Win7.
I don't understand the toolkit, and I understand the other way you pointed to helps you learn. Still doesn't explain why it is stuck at boot (google) and why my restore/backup doesn't work.

you dont have the fastboot.exe downloaded in that same folder.
EDIT: fastboot allows you to delete the /system parition and reload it with the stock images.

Hmmm, didn't see that in the steps. Ok, so where do I get the fastboot .exe... NEVERMIND. I found it.
I also noticed in his instructions that after you unzip everything that you should have 6 files, yet I have? I downloaded the yakju.
Going through the steps, got fastboot in there now and up and running.
Click to expand...
Click to collapse

msucoleman said:
Hmmm, didn't see that in the steps. Ok, so where do I get the fastboot .exe... NEVERMIND. I found it.
I also noticed in his instructions that after you unzip everything that you should have 6 files, yet I have? I downloaded the yakju.
Going through the steps, got fastboot in there now and up and running.
Click to expand...
Click to collapse
uh you should not be using yakju. you need to be using mysid (thats the verizon version)
you could seriously screw up your phone if you use the GSM one (yakju)

got it and thanks again for pointing to that way. I see where my mistake was. I didn't download the toolkit with the other files.
Hmm, for some reason the radios did not work. Moving my .zip ones over now and will flash them. Hopefully will be back up and running full after a hour.

You might want to slow down a bit and do some reading first. 30 minutes of reading a few sticky'd posts can save you a lot of trouble. Read, understand, then flash (not the other way around). A good starting point is efrant's 101 & FAQ post.

Whoops. Flashing the correct one now.

You are correct on the slowing down part. I'm now back to where I need to be as far as starting out. I just missed that part on which file. I was thinking I could go straight to Jb, But i understand how to get there from here. That is the first time I have used fastboot and it was pretty easy.

[Q] updated to 4.1.2, now want to root

I looked all around and cant find much since the 4.1.2 update for at&t was only released a few days ago.
Anyway I just updated to 4.1.2 on my unrooted s3. The update added significant bloatware and has made everything lag including my keyboard which now takes 5-10 seconds to show up. I want to root and install AOKP, however I am a complete n00b at this and all guides available seem to be rooting from 4.0.1 through 4.1.1. So I have a few questions:
Will I have a problem rooting from 4.1.2? Do I need to downgrade to an earlier version? (if so how do I do this)
Do I use odin to install AOKP?
If any of this has been answered please point me towards the proper thread, I looked before posting but couldn't find much.

mlager8 said:
I looked all around and cant find much since the 4.1.2 update for at&t was only released a few days ago.
Anyway I just updated to 4.1.2 on my unrooted s3. The update added significant bloatware and has made everything lag including my keyboard which now takes 5-10 seconds to show up. I want to root and install AOKP, however I am a complete n00b at this and all guides available seem to be rooting from 4.0.1 through 4.1.1. So I have a few questions:
Will I have a problem rooting from 4.1.2? Do I need to downgrade to an earlier version? (if so how do I do this)
Do I use odin to install AOKP?
If any of this has been answered please point me towards the proper thread, I looked before posting but couldn't find much.
Click to expand...
Click to collapse
Use this tool to root the phone http://forum.xda-developers.com/showthread.php?t=1963790 the download you want is in post #3. Instructions in that thread are easy to follow. Don't worry about firmware version, it will work whether on 4.1.1 or 4.1.2.
After you have done this you will need to install a recovery, and then flash your AOKP through recovery This next link will direct you to everything you will need to know.
http://forum.xda-developers.com/showthread.php?t=1725839

so I followed everything exactly. I went to install AOKP from ROM manager, the phone restarted, I saw the AOKP splash and it went to load but never got past the multicolored flashing X. Its just loads indefinitely. I restarted a few times and still the same thing. I tried to boot into recovery with power vol down home but it dosent go anywhere, just restarts the phone into the same loading loop. Is there any other way to recover?

To flash back to aosp based ROMS, I've heard you need to go back to the 4.1.1 bootloaders.

Can't install any ROM's. Stuck on Samsung Galaxy Note II Screen

Hey all,
I have read all over the place on how to get this working but I honestly get more confused the more I read. I wanted to switch to another OS since my phone was starting to become bogged down (too many pictures, videos, old files, etc etc etc; My phone is my work tool since I'm a field sales engineer)
So I went ahead and rooted it with ODIN 3 v1.85 and I317-UCUBMK6.tar.md5. I also installed TWRP although I have no clue which version it is. I suppose it's the latest one. My bootloader is LJ2.
I always do the full swipe and a NANDROID back up. However, when I flash a custom ROM, I always end up stuck on the Samsung Galaxy Note II screen. It won't go.
I have tried to install the following ROM's:
DN3 - Always says "Failed" when I try to flash, even when following instructions of reboot recovery and flash again.
JEDI X 20 - Go through the entire aroma installer - it installs - asks for reboot - when rebooting, stuck as Samsung Galaxy Note 2 screen
and it pretty much happens with all of them. I have decided to back to stock (because I was a retard and accidentally deleted my NANDROID backup) and now I find my WIFI is broken.
I pretty sure this has all been discussed in various threads but I rather bring it all into one so that all that are having the same issue as me (I read a lot of people complaining about this issue with very scattered replies) can have a single thread that addresses how to fix this.
Any help will be greatly appreciated.

alkaroth said:
Hey all,
I have read all over the place on how to get this working but I honestly get more confused the more I read. I wanted to switch to another OS since my phone was starting to become bogged down (too many pictures, videos, old files, etc etc etc; My phone is my work tool since I'm a field sales engineer)
So I went ahead and rooted it with ODIN 3 v1.85 and I317-UCUBMK6.tar.md5. I also installed TWRP although I have no clue which version it is. I suppose it's the latest one. My bootloader is 4.3 (I think; I go to About Device and I see the android version 4.3)
I always do the full swipe and a NANDROID back up. However, when I flash a custom ROM, I always end up stuck on the Samsung Galaxy Note II screen. It won't go.
I have tried to install the following ROM's:
DN3 - Always says "Failed" when I try to flash, even when following instructions of reboot recovery and flash again.
JEDI X 20 - Go through the entire aroma installer - it installs - asks for reboot - when rebooting, stuck as Samsung Galaxy Note 2 screen
and it pretty much happens with all of them. I have decided to back to stock (because I was a retard and accidentally deleted my NANDROID backup) and now I find my WIFI is broken.
I pretty sure this has all been discussed in various threads but I rather bring it all into one so that all that are having the same issue as me (I read a lot of people complaining about this issue with very scattered replies) can have a single thread that addresses how to fix this.
Any help will be greatly appreciated.
Click to expand...
Click to collapse
Try this method flash the odin version and update the bootloader ne5 and you should be fine
http://forum.xda-developers.com/showthread.php?t=2802189

210
Thanks man. That post brought a lot to light. So I have the MK6 firmware but the LJ2 bootloader. I'll try doing what Zen Arcade says there but unfortunately I cant download his files. The website he's hosting the files from has severe lag and the files stop downloading.
I'll get back to you on how this goes once I'm able to download them.

terpin32 said:
Try this method flash the odin version and update the bootloader ne5 and you should be fine
http://forum.xda-developers.com/showthread.php?t=2802189
Click to expand...
Click to collapse
Finally downloaded it. Installed it and got that particular operating system working. I will try to get some customs roms installed. Thanks for the help man!