Develop Bugs

[SOLVED] messed up radio, need advice...

I made a real dumb mistake just now and hoping there is a way out of this. I was in titanium back up after updating to 4.0.4 GSM and decided it would be a good idea to use the integration of updates to rom option, one of the apps was phone or contacts or something like that and it was the first app to be processed and it appeared to be stuck not doing anything, so I made the real bad mistake of force closing titanium backup. Now I don't have signal, my baseband is unknown. I tried restoring all system apps and tried to flash the 4.0.4 update which gave me a status 7 error.
I was hoping there might be a way to fix this without opening my boot loader and having transfer all my stuff to PC which is painfully slow on my window xp PC. Then fast booting the full factory 4.0.4 and set up literally everything again.
Please advice...
Sent from my Galaxy Nexus GSM using Tapatalk expect possible typos

you'll have to unlock your bootloader to fix this. its inevitable. after you get it up and running, you can relock it if you wish to do so.
TIP: you NEVER NEVER NEVER NEVER want to restore system app data. it is calling for bad news.

The Gingerbread Man said:
[snip]
I was in titanium back up after updating to 4.0.4 GSM and decided it would be a good idea to use the integration of updates to rom option
Click to expand...
Click to collapse
This is NEVER a good idea.
The Gingerbread Man said:
Now I don't have signal, my baseband is unknown. I tried restoring all system apps and tried to flash the 4.0.4 update which gave me a status 7 error.
I was hoping there might be a way to fix this without opening my boot loader and having transfer all my stuff to PC which is painfully slow on my window xp PC. Then fast booting the full factory 4.0.4 and set up literally everything again.
Click to expand...
Click to collapse
I honestly don't have any ideas for you. There are so many things that may have messed up.
If you want, I can give you a link to the /system dump that I made for adrynalyne, and you can boot into CWM and try to copy all those files overtop of the files currently in your system and see if that will work. But my suggestion would be to unlock your bootloader and flash a fresh image...

efrant said:
This is NEVER a good idea.
I honestly don't have any ideas for you. There are so many things that may have messed up.
If you want, I can give you a link to the /system dump that I made for adrynalyne, and you can boot into CWM and try to copy all those files overtop of the files currently in your system and see if that will work. But my suggestion would be to unlock your bootloader and flash a fresh image...
Click to expand...
Click to collapse
Pretty much would be the best and easiest way of resolving all of this. Unlock bootloader, fastboot flash stock google images. And relock your bootloader (if you desire... I see no purpose of relocking it) and be on your way.

Thanks guys didnt think I could do it without unlocking my boot loader. Here's to spending all tomorrow morning on the PC and getting in the neck from gf who is meant to be phoning me in the am!
Will fresh flash entire 4.0.4 rom in the morning as its 2.45 am UK time now, got alarm set for 7.30, just hope I can fix it before going to work! Thanks again guys
Sent from my Galaxy Nexus GSM using Tapatalk expect possible typos

The Gingerbread Man said:
Thanks guys didnt think I could do it without unlocking my boot loader. Here's to spending all tomorrow morning on the PC and getting in the neck from gf who is meant to be phoning me in the am!
Will fresh flash entire 4.0.4 rom in the morning as its 2.45 am UK time now, got alarm set for 7.30, just hope I can fix it before going to work! Thanks again guys
Sent from my Galaxy Nexus GSM using Tapatalk expect possible typos
Click to expand...
Click to collapse
Easiest way is to do this:
1) Plug your device into your computer and open a command prompt in the same directory as your adb.exe file
2) Get all your data off your device by typing: adb pull /sdcard
3) Follow this guide for a fresh yakju IMM76D install.

phone fixed now finally. In the end i went back to 4.0.2 as i had it on my pc flashed that then rooted it and then moved 4.0.4 back on to my phone and used stock recovery to flash it and then booted into cwm and flashed su.zip. Now to just put all my stuff back onto my phone...

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.

i need to re-flash the stock takju 4.1.1 on my phone.

could someone post the link to where i can download the actual file. i did a manual update from ics to jb through the toolkit, but something got messed up. my phone has not been working properly. i was just going to flash the entire clean JB rom again, but i'm a complete noob and can't find it. i've searched the forum, but i get super confused with the multiple rom/files threads.
can i just downloand the factory image of the jb 4.1.1, boot into cwm and just flash that file. I believe it will wipe everything and lock my bootloader again. i've been trying to sort things out, but it's driving me crazy, especially my contact search. normally, the people you call most frequently show up right away as you type or two letters of the name and at the top of the search. for me, it's always at the bottom of the list. it's super annoying. i have to scroll all the way down to select them. also, the pics that i take with my camera only appear as files on my comp. there's no preview of the actual pictures. for work, i always need to select/pick out a couple, but now without seeing the image, i have to manually click through each picture, open each one until i find the one i need.

http://forum.xda-developers.com/showthread.php?t=1626895

i used the nexus toolkit to flash the google factory image. is that the same thing as flashing the stock rom?

wasya152 said:
i used the nexus toolkit to flash the google factory image. is that the same thing as flashing the stock rom?
Click to expand...
Click to collapse
You know adb and fastboot controls? If so, you can easily reflash... assuming that you got stock recovery, do fastboot boot cwm.img (you need to download clockwork recovery and put it into the fastboot directory)
Then just flash the zip file of stock Jelly Bean.
You can find stock ROM in Google developer site I believe.
Sent from my Galaxy Nexus using xda app-developers app

well, i now believe my issue was not a update problem, but instead a jb issue. i got a new galaxy nexus for my wife last week and when it came in i set it up for me first. tried using it and same issues as i'm having. i guesss it's a coding issue, than an update. the phone has same issue with contacts. when you use search bar to look for contacts, the most frequent ones come up all the way at the bottom of list, instead of up top. it's like it's reversed for some reason. also, when i took a picture with the phone, i could not see a preview on the computer either. tried same thing on my nexus 7. i really hope google fixes this, it's really annoying.

[Q] GNex Unable to Boot

Hello there, I've tried searching before starting this thread, but as of now, I'm panicked already, that I might have killed my GNex.
My GNex is unrooted, and is of the yakjuxw variant. I just received the OTA update to 4.2.1 today, but immediately regretted my decision - as it was noticeably laggier and buggier compared to my previous version - 4.1.1. I searched on how to downgrade it to 4.1.1 / 4.1.2, and I found several threads mentioning doing it manually (the SDK method), but being a total noob on these, I decided to go for the Wug's Nexus Root Toolkit.
I backed up my files, unlocked the bootloader, and rooted my phone using the toolkit (my phone could still enter the homescreen in this step), and proceeded to flash the IMGs with the factory image from Google, but after that, my phone gets stuck at the Nexus's flashing "x" screen, never entering the homescreen. And, I did not make a Nandroid backup prior to flashing it (sigh). Is there still hope for my GNex?
What I plan to do now is to install Odin, download this Stock-Unroot Jellybean thing, then restore it to stock following this thread, then maybe go for the SDK method this time. Are there any other methods for the situation I'm in? E.g. use Odin to flash it to 4.1.2 (the version I want) straight?
I also found this Galaxy Nexus Toolkit, should I use it instead?
Please help, I'm really confused and panicked . I'm downloading the required stuff currently, with a very slow internet speed, so I'll check this thread tomorrow morning.

download the "wugfresh toolkit", and choose the option "soft bricked" , and flash another rom, the program is very easy to use. your phone is probably ok.

Thank you, thank you so much! I tried that just now, but it said that the Fastboot couldn't work or something, that's why I freaked out. Tried again and yeah, it works. Thank you so much!
Thread can be closed, sorry for spamming, moderators.

Stop trying to use a crutch like the toolkit. Take 5 minutes and follow the stickies on setting up ADB and fastboot so you can do if correctly yourself.

The lowest risk is to follow this post: Link
It will restore factory image. No matter if it's rooted or not!
It's easy and you don't need to setup Android SDK or something.
Greetings

How Do I Flash Factory Image?

It's been some time since I've done this so I'm hoping someone can point me in the right direction. I've had my Pixel 2 XL for like a month now...but since day one I've gotten occasional force closes of various apps. Well next week I'm going with a new carrier (Koodo here in Canada) and I thought it would be a great time to flash a factory image to make sure everything is correct. Also when does Google release monthly updates? Is it the first week of April, maybe I'll just wait and flash that factory image when it comes out. Thanks for the help.

acheney1990 said:
It's been some time since I've done this so I'm hoping someone can point me in the right direction. I've had my Pixel 2 XL for like a month now...but since day one I've gotten occasional force closes of various apps. Well next week I'm going with a new carrier (Koodo here in Canada) and I thought it would be a great time to flash a factory image to make sure everything is correct. Also when does Google release monthly updates? Is it the first week of April, maybe I'll just wait and flash that factory image when it comes out. Thanks for the help.
Click to expand...
Click to collapse
If your wanting to flash a factory image, you'll need a few things first.
I would highly recommend that you look over the linked thread carefully. It has many links and tips to help you on your way :good:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418

acheney1990 said:
It's been some time since I've done this so I'm hoping someone can point me in the right direction. I've had my Pixel 2 XL for like a month now...but since day one I've gotten occasional force closes of various apps. Well next week I'm going with a new carrier (Koodo here in Canada) and I thought it would be a great time to flash a factory image to make sure everything is correct. Also when does Google release monthly updates? Is it the first week of April, maybe I'll just wait and flash that factory image when it comes out. Thanks for the help.
Click to expand...
Click to collapse
https://developers.google.com/android/images

Make sure you have the latest adb and fastboot. Get them from Google...
Go get the latest image and Unzip it. Do not Unzip the folder inside. Move everything you just unzipped into the folder with adb and fastboot.
Now, if you've unlocked and unlocked critical, great. If you haven't unlocked critical, you'll have to. The system image won't install if the bootloader is out of date. Sadly, this will wipe your data.
If both are already unlocked, then open the flash-all file with a text editor and remove the,"-w" and the space preceding, then save the file. Removing the -w will keep your data. Run the flash-all.bat file and in about 10 minutes everything will be flashed.

back to stock
how to back on stock ....i sell the phone and want all stock...no root no boot loader unlocked ...what is the fastest way pls

lomski said:
how to back on stock ....i sell the phone and want all stock...no root no boot loader unlocked ...what is the fastest way pls
Click to expand...
Click to collapse
First thing!! Forget fast!! You need to fastboot flash a full factory image with the -w still in the script. Maybe even do it twice. Then go in and do a factory reset from the OS for good measure. Once that is done and you know it reboots you can go through the locking command. I would NOT toggle the OEM switch in dev though.
Sent from my Pixel 2 XL using XDA Labs

So this has been a a very frustrating experiance but I think I've got everything working again. I don't know how many times I've flashed different factory images and then tried to install TWRP and then install a new custom rom. So I want to explain all of the steps I took (if I remember them all).
0. I couldn't boot into my system but had TWRP installed. At this point I should have tried to get all my data from the sd card via "adb pull /sdcard" .
1. I didn't find any option to fix my system. So I followed this guide to install a factory image (link).
3. I skipped through all of the setup processes and gave my phone wifi. Then I went into the system and did a factory reset.
4. After skipping thourgh the setup again I enabled adb and bootet into the bootloader "adb reboot bootlader"
5. From the bootloader I booted into TWRP by "fastboot boot twrp-3.3.0.0-taimen.img. In the recovery I set the display time out to 300s because for some reason once the phone timed out I could get into twrp any more and the screen stayed black.
6. I transferred the twrp installer and my rom by " adb push TWRP_installer.zip /sdcard/Download" and " adb push ROM.zip /sdcard/Download"
7. I first added the TWRP installer to the flash queue and then I added the rom and then falshed them both. This allowed me to install the rom.
8. For some reason TWRP was not installed. So repeat step 5 and only flash the TWRP_installter.zip
Problems I had:
- In twrp I often got errors that said unable to mount system or vendor. I decided to ignore the error but this thread might help
- Installing TWRP while the stock rom is installed led to the problem that touch didn't work in TWRP
- Entering a pin for the stock rom and then installing TWRP led to TWRP asking for a pin to decrypt my data. Apparently this is not the case if you use a stock image which is older

After flashing stock ROM ota and twrp installer zip the only way to get TWRP to respond to touch is if you disable screen lock and connect to your PC before booting TWRP.
I've found the most reliable way to flash factory images is do it manually with fastboot, latest platform tools installed and a Linux OS like Ubuntu or pop os.
But first do some research and get comfortable with fastboot commands. And dear god don't relock your bootloader unless you're ?% sure it's totally stock.

@schpongo,
Also, a good point to keep when flashing via TWRP is to flash/install ONE AT A TIME. As per the great @Az Biker, you should even reboot to the bootloader after each subsequent flash/install. So, in your case, it seems that you might/should be rebooting to the bootloader three times; one for TWRP installation, one for flashing the custom ROM, and one more for any other subsequent installation (i.e. custom kernel or custom font)...
Also, as it's been said before, but stock kernel doesn't play nice with touch commands on TWRP, and (usually) the only way around it is to reboot into bootloader using the adb command -- as opposed to holding the volume-down button or from an app.
I know you figured this all out already, but it might bear repeating just in case you didn't know and/or to help any other users here...