Develop Bugs

[Q] April Fools Prank gone wrong... help please

Okay so let's start off by saying my cousin is an idiot. He tried pulling an April fool's joke on me (ill spare you the details) and ended up wiping my phone THROUGH THE STOCK METHOD (As in going to settings and resetting the phone...). And so, im left with a phone in bootloop... awesome. So I need some help reviving it. I have no freaking clue if I still have clockwork running on it (i think it is because the boot animation for the ROM i was running is still there and the unlock thing at the bottom when it first boots up is there). I was running AOKP beta 25 with lean kernel along with the lucid theme atop of AOKP. Can someone please help guide me on how to get my phone up and running?

azn android said:
Okay so let's start off by saying my cousin is an idiot. He tried pulling an April fool's joke on me (ill spare you the details) and ended up wiping my phone THROUGH THE STOCK METHOD (As in going to settings and resetting the phone...). And so, im left with a phone in bootloop... awesome. So I need some help reviving it. I have no freaking clue if I still have clockwork running on it (i think it is because the boot animation for the ROM i was running is still there and the unlock thing at the bottom when it first boots up is there). I was running AOKP beta 25 with lean kernel along with the lucid theme atop of AOKP. Can someone please help guide me on how to get my phone up and running?
Click to expand...
Click to collapse
You may have to flash the stock google factory image. If you hold down both volume buttons and the power button while the phone is off, you can get into fastboot mode (the screen with the opened up Android). Then you can use the gnex toolkit (you can get it from the development forums) to flash the stock google factory image.

Just boot into recovery. You'll then know if you have CWM. If you have CWM, just try a data/cache/dalvik wipe and reboot. If it still bootloops, do a full wipe and re-flash the ROM.
If you don't have CWM, you can flash it through fastboot and try the above.
Don't freak out. A bootloop is about the farthest from a brick you can be.

what exactly will that do..? Will I lose unlock/root? and sorry if you don't mind, could you point me to the tool?

Alright so even after wiping and reflashing the ROM, im still in a bootloop. I dont mind having to go back to 100% stock no unlock if that's what it takes but can anyone help me out?

OK the easiest way to sort this out for you but perhaps not the best way is go to http://code.google.com/android/nexus/images.html and download a factory rom and use a tool kit like mskips http://forum.xda-developers.com/showthread.php?t=1392310 to flash everything back to stock. This will wipe your entire phone so back up anything you wanted to keep but I promice your phone will work again.
I only say this isn't the best possible way as it would be best to learn about adb and fast boot as to know how to do all this manually but I don't have a good knowledge on adb but its something I'm meaning to do just don't have a great deal of time for. The tool kit will do everything for you simply by pressing keys and a few clicks and will install all the drivers you need. Good luck
Sent from my Galaxy Nexus using Tapatalk

Thank you! I was able to flash to the stock image and keep my unlock! Sadly, since my cousin wiped my phone, i lost everything anyways... but I have my essential things (pictures, contacts, and some apps) already backed up. Thank you for your help!

azn android said:
Thank you! I was able to flash to the stock image and keep my unlock! Sadly, since my cousin wiped my phone, i lost everything anyways... but I have my essential things (pictures, contacts, and some apps) already backed up. Thank you for your help!
Click to expand...
Click to collapse
Glad you figured it out. Flashing the Google Images doesn't relock the bootloader (unless you explicitly do so with the oem lock command). You can now start over and load a custom ROM.

Good I'm glad you fixed it, today your learned a little bit of how to get out of sticky situations. I'm glad to of helped
Edit
Now be sure to return the favour to your cousins phone
Sent from my Galaxy Nexus using Tapatalk

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] Soft Bricked Phone..anyway to extract userdata?

Hi all, I recently soft bricked my VZW Gnex by trying to flash CNA 3.8.
A little background:
I was on CNA 3.6.6 for awhile but the phone started to reboot during certain actions. So I decided to flash CNA 3.8. I was having trouble wiping the phone. I would do a full wipe in CWM touch (format data/cache/system/dalvik cache) and I when I rebooted it was as if nothing happened. Everything was still there. I tried a couple of times, and the same thing would happen, the phone wouldn't wipe.
After posting a thread about not being able to wipe the phone, I was advised to switch to TWRP and try again, which I did. Tried flashing CNA 3.8 and got hung up on the boot animation. I couldn't find my nands with TWRP so I switched back to CWM to try to restore a nand. When I tried to restore, I got md5 mismatch so I couldn't restore. I tried to do a clean reflash of CNA 3.6 but phone always got hung up at the boot animation.
I've been doing battery pulls and numerous wipes/flashes trying to get the phone to boot, but to no avail. Only thing I can do is boot into CWM recovery and fastboot. No matter what I do, the phone will not get past boot animation.
I have the Gnex toolkit but haven't been able to do much with it.
I've been advised to go back to stock (which I tried to do with the toolkit) but still stuck.
Also installed Android SDK for ADB, but admittedly I'm a noob when it comes to trying to get ADB to work.
At this point, is there anyway I can pull userdata from the phone before I try a return to stock approach which erases userdata?
Any help would be GREATLY appreciated! Please help me!

Tool kits are not the best way to mod your phone as when you have an issue your a bit lost.
Jubakuba has a panic section in her guide stickied to the Q&A page, Efrant also has a guide on the same Q&A page. Have a good read, the steps and fastboot/adb commands are all given.

you are not bricked
What happens if you hold down both volume buttons and power with your phone connected via USB?
EDIT: Just reread and saw you can get into fastboot
Connect your phone to your PC while in fastboot. Run GNEX toolkit as Admin.
Choose option 16
choose option 9
download, extract and wipe intnernal
you should be good to go

Thanks for the advice guys.
@Rudeguy: If I do this, I will lose all my personal data on the sdcard correct? Is it possible to pull stuff like pictures, music, etc. before I proceed with going back to stock and starting from scratch?

supasizefries said:
Thanks for the advice guys.
@Rudeguy: If I do this, I will lose all my personal data on the sdcard correct? Is it possible to pull stuff like pictures, music, etc. before I proceed with going back to stock and starting from scratch?
Click to expand...
Click to collapse
There is an option to keep your data. However sometimes you will have to sacrifice your data as it is causing the issue

danstah said:
However sometimes you will have to sacrifice your data as it is causing the issue
Click to expand...
Click to collapse
This is what people don't understand.
Sent from my i9250

bk201doesntexist said:
This is what people don't understand.
Sent from my i9250
Click to expand...
Click to collapse
Thisvis why at minimum, once a week, i pull all pics off phone and put on pc and external. Got kids and grandkids, probably take 1000 pics a month, dont want to lose pics.
Sent from my Galaxy Nexus using xda app-developers app

I was able to pull user data using adb. Learned how to do it from another thread. No worries now.
Sent from my Galaxy Nexus using Tapatalk 2

[Q] GNEX stuck on boot animation twice in 3 months

My Gnex which is 3 months old stuck at boot animation twice in 3 months. first time it was on 4.0.1 ICS and now on 4.1.1 Jelly bean both stock. on the both occasions i did factory reset and lost all my important data. Is this an hardware issue? because i got the problem after turning the bluetooth on for sending the photos on both the occasions.
What is the best thing to do so that my data is safe when next time this situation comes.
I came to know that with usb debugging on we can backup the data even in the boot loop. is it true? and can i keep the usb debugging option always ON on my Gnex.
If this is an software issue then it is very sad since it is coming from the stock android and on the nexus line.
Today 22/5/2013
Again Gnex stuck on bootloop, this time i got the problem, whenever i switch on bluetooth on the phone to connect it with my laptop, it is going into the bootloop, on the previous two occasions, it got stuck when i was trying to transfer through bluetooth though only with laptop, it works fine with other phones.
Is this a hardware problem or software problem, Please help

Nowhere near enough info for anyone to help. Was this after you flashed a rom? What gnex variant do you have?
Sent from my Mahjong Nexus

muneer khan said:
What is the best thing to do so that my data is safe when next time this situation comes.
I came to know that with usb debugging on we can backup the data even in the boot loop. is it true? and can i keep the usb debugging option always ON on my Gnex.
If this is an software issue then it is very sad since it is coming from the stock android and on the nexus line.
Click to expand...
Click to collapse
Best thing to do is root your nexus. Get on the latest update. Another thing you could do is backup your sdcard to your PC using adb or any other means. Or use a cloud service to backup your data.
If you can get into recovery then you should be able to adb pull your data. I usually leave debugging on but not sure how safe it is.
Scent from my bud

You might want to look into hak5.org's tutorial by the koz on how a phone with debugging always enabled is open to some exploits. Though, that comes with the territory. I'd reflash the system.img. To keep the data safe, backup often. You may be able to pull it if needed, and adb backup, but you'd need a custom recovery first. Which means root or unlocked bootloader, which comes with a data wipe. Could it be the bluetooth device with which the phone is interacting? Or do you have the issue as soon as you make the phone visible?

tritonesub said:
Nowhere near enough info for anyone to help. Was this after you flashed a rom? What gnex variant do you have?
Sent from my Mahjong Nexus
Click to expand...
Click to collapse
I have a mangru stock Gnex yakjujp build. i had this problem when the phone was in 4.0.1 ics and 4.1.1 jelly bean both stock. never flashed or rooted.

namtombout said:
Best thing to do is root your nexus. Get on the latest update. Another thing you could do is backup your sdcard to your PC using adb or any other means. Or use a cloud service to backup your data.
If you can get into recovery then you should be able to adb pull your data. I usually leave debugging on but not sure how safe it is.
Scent from my bud
Click to expand...
Click to collapse
Thankyou for your response.
second time when my phone stuck was on latest installed jelly bean OTA 4.1.1. I lost everyting important photos, temple run statistics and other games statistics.
please post the link or steps to install adb and adb pull data.

bodh said:
You might want to look into hak5.org's tutorial by the koz on how a phone with debugging always enabled is open to some exploits. Though, that comes with the territory. I'd reflash the system.img. To keep the data safe, backup often. You may be able to pull it if needed, and adb backup, but you'd need a custom recovery first. Which means root or unlocked bootloader, which comes with a data wipe. Could it be the bluetooth device with which the phone is interacting? Or do you have the issue as soon as you make the phone visible?
Click to expand...
Click to collapse
Thankyou for your response.
on both the occasions as soon as i selected the photos and send via bluetooth the phone got stock, dont know wheather this is a hardware problem or software problem. i transfered the many photos like this but on the two occasions i got the problem.

System UI crash evry time it tries to restart after root66 flash

never had this problem first here is all the background information from my last thread (yes i must be challenged)
really I don't know what to do
I believe i need to completely erase everything from my device as i cannot think of what else it could be but some conflicting something somewhere I am not educated enough to know
it flashes fine with odin but always system ui error I will be trying to go back to 4.1X as i believe that was my last bootloader and hope it works out. In all i want to update to NC2 and take advantage of the last roms beuing developed for this device.
In all i want to get my phone working again i need to get and send calls and texts so i plead for help Any question i will answer to the best of my ability
I have flashed with odin 3.1 and 3.07 NC2 then MJC basically both root 66 4.3 roms I don't know what my problem is maybe if while im waiting for help and using a root 66 for 4.1.2 (last working state) i will use recovery to wipe the sd card? idk but in all i think i need to start FRESH as long as i can get my contacts from Google i'm fine (and the phone rings and such lol)
IM eagerly waiting for help!!! someone else who is having a crappy holiday season maybe you can relate when you get in a funk where it seams everything breaks or needs to be replaced at one time
TUIA

You can't flash back to 4.1 with Odin. Root66 performs a full update including bootloader so no downgrade. You probably just need to factory reset with recovery. Just make sure you backup your internal sd

serio22 said:
You can't flash back to 4.1 with Odin. Root66 performs a full update including bootloader so no downgrade. You probably just need to factory reset with recovery. Just make sure you backup your internal sd
Click to expand...
Click to collapse
Thanks for sticking in there with me i did a factory reset using the recovery (i guess the android recovery) deleted data and cache which deleted all the apps which were messing things up so now it booted up like a brand new phone my contacts are back via Google and that's all i care ill be installing a rom and such soon but idk im starting over it works and upgrade
thank you a lot for sticking with me serio22 all i can do is thank you for all your posts but if i had the means id buy you a beer or something man

No problem man, glad it's fixed!

BeatnikBandit said:
Thanks for sticking in there with me i did a factory reset using the recovery (i guess the android recovery) deleted data and cache which deleted all the apps which were messing things up so now it booted up like a brand new phone my contacts are back via Google and that's all i care ill be installing a rom and such soon but idk im starting over it works and upgrade
thank you a lot for sticking with me serio22 all i can do is thank you for all your posts but if i had the means id buy you a beer or something man
Click to expand...
Click to collapse
http://forum.xda-developers.com/and...-rendering-t3003534/post58190052#post58190052
Try this