Develop Bugs

I Need Help Quick!

I made a goof and flashed a kernel for 4.03 and I'm still on Fabolous' ICL53F Deodexed Rom. What a goof! I did a backup before this, but it doesn't show up in recovery. Also, when I plug the phone in via USB, the computer isn't recognizing it (I guess because it isn't completely booting up?). Anyway, I need the original stock kernel for 4.02, and instructions on how to get it on my phone so I can flash it in recovery! Thanks in advance! It's definitely time to move up to 4.03.....

You can make a dropbox account and download the app on your phone to transfer the rom
Sent from my Galaxy Nexus using XDA App

Err I mean kernel
Sent from my Galaxy Nexus using XDA App

I have a Dropbox account but I can't get the phone to do anything, except sit in recovery. Then I have the issue of actually loading the kernel so I can flash it.

Flash the kernel in fastboot

joshnichols189 said:
Flash the kernel in fastboot
Click to expand...
Click to collapse
I need to get into fastboot and I need the actual kernel

Ok. So here's what I have. I can get to recovery, but can't mount usb. All I think I need is a copy of the original 4.0.2 kernel placed in the downloads section, etc. so I can flash it. Or maybe even a 4.0.3 rom to flash since the kernel I flashed was for 4.0.3. Right now I go to recovery then I can hit start and I just get the Google logo with the unlocked icon. This can't be too difficult for someone who understands this. I'd sure appreciate someone's help.

If you can get to recovery you can get to fastboot.. you have to go through fastboot to get to recovery..
Go find a 4.0.2 compatible kernel, and in fastboot flash it using
fastboot flash boot (name of kernel.img)

My GNex maguro not accepting Jelly bean

I have Galaxy Nexus Maguro and I tried all ways to install jelly bean and it fails and stuck on Nexus logo ... I tried stock ROMs and kernels and Cocked one's but no success. The device work perfectly with all ICE Cream version. Any help or hint or tips will be appreciated.
Thanks in advance ...

alfkhr said:
I have Galaxy Nexus Maguro and I tried all ways to install jelly bean and it fails and stuck on Nexus logo ... I tried stock ROMs and kernels and Cocked one's but no success. The device work perfectly with all ICE Cream version. Any help or hint or tips will be appreciated.
Thanks in advance ...
Click to expand...
Click to collapse
Look at the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2

no luck
efrant said:
Look at the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
First thank you for your response. I followed your procedure but the problem still exist. Stuck on Nexus logo.

More Info Required...
alfkhr said:
First thank you for your response. I followed your procedure but the problem still exist. Stuck on Nexus logo.
Click to expand...
Click to collapse
Are you unlocked and rooted?
Have you installed CWM?
If so, can you boot sucessfully to it?
Are you using the GN Toolkit?
Bit more info as to what you have done so far would be helpful...

unsuccessfully
I am very sad http://forum.xda-developers.com/images/icons/icon9.gif

alfkhr said:
First thank you for your response. I followed your procedure but the problem still exist. Stuck on Nexus logo.
Click to expand...
Click to collapse
You need to provide a bit more detail for us to help. Did you flash all the images (including the lc03 bootloader)? Did they flash successfully?
Sent from my Galaxy Nexus using Tapatalk 2

I did all scenarios ...
efrant said:
You need to provide a bit more detail for us to help. Did you flash all the images (including the lc03 bootloader)? Did they flash successfully?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
All six img files were flashed successfully. Device rebooted and stuck on New Jellybean logo. To be sure what I did is right I did the same steps for ICS img files and it boots to ICS without any problem ,,,
before that I try to use recovery CWM but without luck.

alfkhr said:
All six img files were flashed successfully. Device rebooted and stuck on New Jellybean logo. To be sure what I did is right I did the same steps for ICS img files and it boots to ICS without any problem ,,,
before that I try to use recovery CWM but without luck.
Click to expand...
Click to collapse
When you are booted in fastboot mode, does it indicate that you are on the lc03 bootloader and xxlf1 radio?
Sent from my Galaxy Nexus using Tapatalk 2

Hanging When Booting JB
alfkhr said:
All six img files were flashed successfully. Device rebooted and stuck on New Jellybean logo. To be sure what I did is right I did the same steps for ICS img files and it boots to ICS without any problem ,,,
before that I try to use recovery CWM but without luck.
Click to expand...
Click to collapse
What happens when you boot into CWM?
If you have a JB ROM image on your flash then you should be able to completely wipe the phone (system, data and dalvik (under advanced options)), install the new ROM then boot it up.
Having a phone that hangs during boot is usually symptomatic of not having wiped the phone properly when flashing a new ROM.

yes
efrant said:
When you are booted in fastboot mode, does it indicate that you are on the lc03 bootloader and xxlf1 radio?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes boot loader version is lc03 and Radio is xxlf1

mlindema said:
What happens when you boot into CWM?
If you have a JB ROM image on your flash then you should be able to completely wipe the phone (system, data and dalvik (under advanced options)), install the new ROM then boot it up.
Having a phone that hangs during boot is usually symptomatic of not having wiped the phone properly when flashing a new ROM.
Click to expand...
Click to collapse
Yeah it sounds like maybe you didn't wipe man.
Sent from my Galaxy Nexus using Tapatalk 2

Yes I do
mlindema said:
What happens when you boot into CWM?
If you have a JB ROM image on your flash then you should be able to completely wipe the phone (system, data and dalvik (under advanced options)), install the new ROM then boot it up.
Having a phone that hangs during boot is usually symptomatic of not having wiped the phone properly when flashing a new ROM.
Click to expand...
Click to collapse
I did all kind of wipe !!!

Try this: Make sure you have the JRO03C boot and system images handy (i.e., in the same directory as your fastboot.exe file), reboot into fastboot mode and type the following command in a terminal:
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot reboot-bootloader
fastboot flash system.img
fastboot flash boot.img
fastboot reboot-bootloader
fastboot reboot
EDIT: Note that it should take 5-10 mins to boot up.

Still
efrant said:
Try this: Make sure you have the JRO03C boot and system images handy (i.e., in the same directory as your fastboot.exe file), reboot into fastboot mode and type the following command in a terminal:
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot reboot-bootloader
fastboot flash system.img
fastboot flash boot.img
fastboot reboot-bootloader
fastboot reboot
EDIT: Note that it should take 5-10 mins to boot up.
Click to expand...
Click to collapse
Still nothing ...but there is something I should mention ... I was in JB before one month .. then I got back to ICS cos JB still in the first stages as custom Rom. Then I flags ics miui rom and work great then I flashed miui update and it was corrupted and get many problems till I fix it by going back to stock ICS. Now do you think this is the issue ???

alfkhr said:
Still nothing ...but there is something I should mention ... I was in JB before one month .. then I got back to ICS cos JB still in the first stages as custom Rom. Then I flags ics miui rom and work great then I flashed miui update and it was corrupted and get many problems till I fix it by going back to stock ICS. Now do you think this is the issue ???
Click to expand...
Click to collapse
Going back and forth should have nothing to do with it. But it really does sound like you're not wiping one of the needed things first which mixes your ICS and JB files.
I'd suggest that you download something like CM10 and AOKP build1, go to CWM and do ROM Wipe/Factory Reset, Wipe Cache, and Wipe Dalvik. These are the 3 you need to do. Then install zip from SD - your new ROM. Then install gapps for JB. Boot up. If you use Titanium Backup, don't restore any system data.

Yes I do
netbuzz said:
Going back and forth should have nothing to do with it. But it really does sound like you're not wiping one of the needed things first which mixes your ICS and JB files.
I'd suggest that you download something like CM10 and AOKP build1, go to CWM and do ROM Wipe/Factory Reset, Wipe Cache, and Wipe Dalvik. These are the 3 you need to do. Then install zip from SD - your new ROM. Then install gapps for JB. Boot up. If you use Titanium Backup, don't restore any system data.
Click to expand...
Click to collapse
still the same

Up

Have to reflash kernel everytime aosp

I have been having many issues flashing roms on this phone, the number one issue is that my phone often gets stuck in boot loop after flashing aosp/cm/aokp etc roms. What I figured out is that everytime I reboot the device it will get stuck in boot loop, the only solution is to flash kernel via fastboot quite inconvenient as I do not always have my netbook with me. Perhaps it could have something to do with the update, however I have used the ruu to stock many times and this last time I did not update. Unless the hboot got permanently up dated and using the ruu back to stock doesn't revert back to the old one...
In any case am I the only one having these issues? I really don't mind sense and I love all the cool widgets but I want Jellybean so I would rather not go back to ics.

dude, both the kernels sense and aosp are seperate, only solution is take a backup via cwm or TWRP AND restore it whjen u want

I understand sense kernels are different than aosp, my problem is that after I flash rom+gapps+kernel reboot into fastboot fastboot boot boot.img that phone boots up and all is well except when I reboot as in turn power off then on my phone will bootloop. I was under the impression that once you fastboot boot boot.img you only had to reflash the kernel when you want to flash a new rom. I have to fastboot everytime my phone is shut down.
Also I just did a nandroid back up of stock rom with out flashing kernel in fastboot after using slickkernel(I forget the actual name) from aosp. So it appears that the kernel is only lasting at the intitial boot everything else gets defaulted to stock kernel.

md1008 said:
I understand sense kernels are different than aosp, my problem is that after I flash rom+gapps+kernel reboot into fastboot fastboot boot boot.img that phone boots up and all is well except when I reboot as in turn power off then on my phone will bootloop. I was under the impression that once you fastboot boot boot.img you only had to reflash the kernel when you want to flash a new rom. I have to fastboot everytime my phone is shut down.
Also I just did a nandroid back up of stock rom with out flashing kernel in fastboot after using slickkernel(I forget the actual name) from aosp. So it appears that the kernel is only lasting at the intitial boot everything else gets defaulted to stock kernel.
Click to expand...
Click to collapse
ok try this, download sick kernel fastboot it, the flash the image via cwm

I figured out my own mistake, I was using fastboot boot boot.img which does not flash the kernel but is more of a test drive. So I now did this and all is right with the world fastboot flash boot boot.img. I do not have a lot of experience with fastboot or bootloaders. Sorry to clutter the Q&A

Ohhhh lol good
Sent from my One V using xda premium

Out of curiosity, could you provide detailed instructions on what you did? I am having the same issue as you were, I believe.

mastertr said:
Out of curiosity, could you provide detailed instructions on what you did? I am having the same issue as you were, I believe.
Click to expand...
Click to collapse
Here are the steps
*Download rom, gapps, kernel
*in recovery factory reset, wipe system ( optional)
*install ROM, gapps, kernel
*reboot into boot loader(hboot)
*Mount USB and extract boot.IMG from ROM and put it in c:/Android
*make sure phone days fastboot, if not press power button
*open up adb
*CD c:/Android
*fastboot flash boot boot.img
*restart phone and out sticks
Important part is to add flash to the fastboot commands
Sent from my SGH-T999 using xda premium

Here
http://forum.xda-developers.com/showthread.php?t=1996665
Sent from my One V using xda premium

[Very serious]Non-booting/non-changing/not working problem

I woke up today to a bootloop. After pulling out the battery, I cant turn it on, it was stuck at the google logo. I thought it was some rom issue or something. When I had the time, in the afternoon, I just boot to recovery, and wiped data+sd card. Turns out sd card was not wiped.
Just now, I found a way to boot it. (AFTER WIPING DATA) I used the gnex toolkit and boot with insecure image, and guess wat? My old rom boots. Everything was the way it was, and then it crashed and stuck on the google logo again.(I made sure i wiped things two to three times, data and sd) I did a few experiments:
1) Flash using ODIN
2) Flash CWM using toolkit--it changed back to twrp after reboot
3) Changing the icon on my homescreen after boot--- everything was the same again after booting
4) Flash stock image using toolkit
5) Wipe data using manual adb
6) Try to lock my bootloader
Everything I tried changing, change back to the original state after reboot. What is the problem?
Device: Galaxy Nexus
ROM: Purity 7 sept release
Kernel: Fancy r42
Logs in twrp are showing updating partition, not FAIL. So I really don't think there is a need to show the recovery log.
HELP ME!

are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.

player911 said:
are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.
Click to expand...
Click to collapse
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.

jacktay94 said:
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.
Click to expand...
Click to collapse
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Yup,I tried it already thru toolkit. Not working either.

Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.

SoHaunted said:
Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.
Click to expand...
Click to collapse
i did adb bro, its the last thing i tried, i learnt and try.
Sent to Samsung centre, they told me its my flash IC thats blown. sobs

[Q]How to root and unlock the latest build

So I just picked up this device couple days ago. It's running 4.4.2
This has surely been asked before but how do I root this build? I only found TUTs for 4.3 here on xda
Thanks
PS. This is my first nexus device
//Sent from somewhere in your house

Wug's Nexus Root Toolkit v1.8.2
http://forum.xda-developers.com/showthread.php?t=2389107

lzzar said:
So I just picked up this device couple days ago. It's running 4.4.2
This has surely been asked before but how do I root this build? I only found TUTs for 4.3 here on xda
Thanks
PS. This is my first nexus device
//Sent from somewhere in your house
Click to expand...
Click to collapse
Fastboot commands to unlock bootloader and install TWRP. Then flash a root zip.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

LinearEquation said:
Fastboot commands to unlock bootloader and install TWRP. Then flash a root zip.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Which command is to unlock the bootloader?
//Sent from somewhere in your house

lzzar said:
Which command is to unlock the bootloader?
//Sent from somewhere in your house
Click to expand...
Click to collapse
fastboot oem unlock

okay so I unlocked the bootloader and flashed recovery. I can boot normally but not into recovery. it gives me the android with the red triangle.
I know the BL is unlocked cause I see the lock symbol at the Google screen
I tried both cwm and twrp
Help?

lzzar said:
okay so I unlocked the bootloader and flashed recovery. I can boot normally but not into recovery. it gives me the android with the red triangle.
I know the BL is unlocked cause I see the lock symbol at the Google screen
I tried both cwm and twrp
Help?
Click to expand...
Click to collapse
It sounds like you still have the stock recovery installed instead of the custom one you're trying to flash. What command are you using to flash the custom recovery? It should be:
fastboot flash recovery [insert recovery filename here].img
Then, use the volume buttons to boot into recovery from the bootloader. Your custom recovery should boot up.

Yeah I used that command. I have used it before on my Optimus 3D
//Sent from somewhere in your house

lzzar said:
Yeah I used that command. I have used it before on my Optimus 3D
//Sent from somewhere in your house
Click to expand...
Click to collapse
Are you using the proper TWRP? You may try the command again.
Edit: In order to flash you have to CD from a folder containing adb.exe and fastboot.exe. Otherwise nothing will flash. Download this folder https://docs.google.com/file/d/0B_nizg6yUZ0NbWNvZHFMR1h6LVE/preview?pli=1 and Stick TWRP in the folder. That folder was put together by Rootjunky.com http://m.youtube.com/watch?v=6k4rCaMPSQ8
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

Nevermind guys, I got it working! !
Changed a little stuff (usb port and cable, wiped data before flashing)
//Sent from somewhere in your house

@lzzar Glad you got it figured out.
Short story for anyone who might find this thread after seeing the Red Triangle.
I saw an article on Android Police that there was 32gb refurbs for sale for $170. So, clearly we (XDA members) are not the same as normal users when it comes to troubleshooting and fixing problems. So, I bought my 2 sons 1 each and my wife 1 as well. While my sons are very young (single digit ages), I've taught them how to run code. The N7's arrived yesterday and after they went to bed, I fired up the computer and had all 3 tabs going at once updating from 4.3 to 4.4.2, charging, downloading,....
Unlocked all 3 Bl's and proceeded to install TWRP and ROM/Kernels. Point to remember is that I had too many things going on at once. On the very first recovery.img flash, I got the laying down android with red triangle. Flashed the recovery.img again and again the red triangle, all the while I was downloading ROMs and Kernels on my PC.
Then I realized what I was doing wrong. After flashing the recovery.img, I booted into the OS, then powered off and used the key combo to boot into recovery. Wrong!! What step did I miss? After flashing fastboot flash recovery recovery.img, I had forgotten to Volume up and boot into recovery from straight from there.
Once I realized my blunder, I was much happier. After that, it took me under an hour to install recoveries on all 3, flash ROMs and Franco r13, boot and reflashed SuperSU. Too many things going on at once and maybe a few too many drinks as well.

Yes, the exact same mistake with booting into OS after flashing was what I did too
//Sent from somewhere in your house