Develop Bugs

[Q] gahhhhhhh! please please help

i rooted my galaxy nexus last night, and today i was trying to put a rom on it, i went to wipe the cache, and now it wont boot past the google screen and im freaking out!

Before you flashed did you wipe system? Huh I bet not even so you only mention wipe cache....what about data , dalvik ?
Did you read directions in the op for the ROM?
Sent from my SPH-D710 using Tapatalk 2

it told me to wipe to factory, i tried doing that and it just froze, and now it wont boot. im trying to figure all this out but im a little over my head unfortunately.

Try booting into recovery and then wiping and flashing your ROM

i was trying to flash the codename android 1.6 rom, i cant post the link it wont let me

when i boot into recovery mode, it shows a droid with its chest open and a red exclamation point

I've never heard of that ROM but in fastboot will it let you use your volume and power keys to navigate to recovery? If not, try using fastboot commands on the computer to get into recovery (if you can? I'm not too acquainted with fastboot commands)

i can get into recovery but then it shows the droid with the red alert

m4gkman said:
i can get into recovery but then it shows the droid with the red alert
Click to expand...
Click to collapse
That's fastboot. Try looking into fastboot commands and see if any command will let you boot into recovery from there.

You buggered the boot image... Just flash it again, via fastboot...
They are normally in .Franco kernels...

you mean through terminal and stuff? my knowledge to this stuff is still pretty basic so im trying to grasp all of this

familyguy59 said:
You buggered the boot image... Just flash it again, via fastboot...
They are normally in .Franco kernels...
Click to expand...
Click to collapse
so fastboot is throught he computer?

m4gkman said:
so fastboot is throught he computer?
Click to expand...
Click to collapse
Yes. Fastboot is used, in CMD (Windows) Gnome terminal (Ubuntu/Linux distributions) and the Mac OS terminal...
You need to install the ADB drivers and download the fastboot/adb files first, though (Check the Windows 8 thread (In my signature), all you need is in there...
Or, download a .Franco kernel (Check the developement section, for your device (GSM/verizon/Sprint) and search the forum...

i did fastboot and all that stuff on my laptop at home(the one i rooted it with), do i basically need to redo all of that?

m4gkman said:
i did fastboot and all that stuff on my laptop at home(the one i rooted it with), do i basically need to redo all of that?
Click to expand...
Click to collapse
Yes, but just flash the boot.img
Code:
fastboot flash boot %Userprofile%\Downloads\<Whatever the file is named>.img

Ngo93 said:
That's fastboot. Try looking into fastboot commands and see if any command will let you boot into recovery from there.
Click to expand...
Click to collapse
No, that is not fastboot. That is recovery. He has the stock recovery flashed, which is the Android lying on its back with a red exclamation point.
m4gkman said:
i can get into recovery but then it shows the droid with the red alert
Click to expand...
Click to collapse
You need to flash CWM before you do anything else. Get it from the link in my signature and flash it in fastboot. Then boot into CWM, do a wipe, and re-flash the ROM you want.

efrant said:
No, that is not fastboot. That is recovery. He has the stock recovery flashed, which is the Android lying on its back with a red exclamation point.
You need to flash CWM before you do anything else. Get it from the link in my signature and flash it in fastboot. Then boot into CWM, do a wipe, and re-flash the ROM you want.
Click to expand...
Click to collapse
We've been there. Done that and got the T-shirt. The phone is working fine. Just installing CND 1.6

familyguy59 said:
We've been there. Done that and got the T-shirt. The phone is working fine. Just installing CND 1.6
Click to expand...
Click to collapse
No, he hasn't been there, and obviously you didn't understand that.
If he sees the Android lying on his back with the red ! then he has the STOCK recovery flashed, not CWM.

efrant said:
No, he hasn't been there, and obviously you didn't understand that.
If he sees the Android lying on his back with the red ! then he has the STOCK recovery flashed, not CWM.
Click to expand...
Click to collapse
CWM is flashed, it's installing CND (Or has installed) but whatever we do, it's a bootloop. lol) I'm doing everything, with him, whilst he's at work, via TV ^^
I'm seing exactly everything, what is happening, on the computer. I flashed everything myself...

familyguy59 said:
CWM is flashed, it's installing CND (Or has installed) but whatever we do, it's a bootloop. lol) I'm doing everything, with him, whilst he's at work, via TV ^^
I'm seing exactly everything, what is happening, on the computer. I flashed everything myself...
Click to expand...
Click to collapse
Ah, ok! None of that was mentioned in the thread. Had no idea that you were helping him -- I thought you were helping him in this thread.

Screwed up my One X

I tried installing a custom rom today and I think I messed up really bad, because my phone does not get pass the boot screen and I cannot enter the recovery setting. I think I messed up after entering
fastboot flash boot boot.img
in the command prompt and restarting because I forgot to put the rom zip on my phone. Since then I could not get pass the boot screen and even tried running a backup using CWM, but it didn't help. I then managed to mount my phone and put the rom onto it and installed it, but again it didn't help.
Now my phone can only enter the bootloader, I select hboot and fastboot, but nothing else works. Everytime I select recovery or factory reset I get the htc boot screen and it gets stuck. Does anyone have any solutions?
Thanks

did u backup your phone rom???
if you did u can go to recovery and restore it
and never try to change rom again trust me in that
otherwise i can't help bcuz i did the same mistake

I did make a backup, but like I said I can't enter recovery anymore, so I can't load the backup.
Thanks for trying to help anyway though.

fastboot erase cache
Often fixes recovery problems.

BenPope said:
fastboot erase cache
Often fixes recovery problems.
Click to expand...
Click to collapse
Still not working, thanks anyway.

What HBOOT version do you have and what custom ROM are you trying to install?
edit: you didn't need to restart after changing boot.img cause in Recovery you can just go Advanced and then mount USB and copy the ROM or whatever files you want that way.

BlueSingA said:
What HBOOT version do you have and what custom ROM are you trying to install?
edit: you didn't need to restart after changing boot.img cause in Recovery you can just go Advanced and then mount USB and copy the ROM or whatever files you want that way.
Click to expand...
Click to collapse
I have hboot 1.39.0000 and I was trying to install the latest cyanogenmod cm-10-20130106-NIGHTLY-endeavoru.
Yeah I realized this after I restarted and did it get the zip onto the phone. I think I installed it, but the phone is still stuck on the boot screen
UPDATE: Okay I've managed to install CWM recovery, so I think I'm making progress

You had to flash CWM again? Odd..
Anyway, if you happen to encounter the same problem with CM10 I suggest you try some other custom ROM.. Just make sure you "fastboot flash boot boot.img" and then "fastboot erase cache", and if for some reason you decide to format the sdcard or simply forget to add in the ROM zip, you can do it in Recovery when you mount the device as USB under Advanced options. Best of luck!

BlueSingA said:
You had to flash CWM again? Odd..
Anyway, if you happen to encounter the same problem with CM10 I suggest you try some other custom ROM.. Just make sure you "fastboot flash boot boot.img" and then "fastboot erase cache", and if for some reason you decide to format the sdcard or simply forget to add in the ROM zip, you can do it in Recovery when you mount the device as USB under Advanced options. Best of luck!
Click to expand...
Click to collapse
Yeah CWM didn't load up, but I got it working again. Well it seems I'm back to getting the rom to install and being stuck at the boot screen again, so maybe I just need to use a different rom. Thanks for the help though

Okay, I've tried installing a few roms, but unfortunately I'm still on the boot screen, I can sometimes even reach the cyanogenmod boot screen, but get stuck there. I've read that this might be kernel issue, does anyone have any ideas?

CM10 requires a special boot.img for newer hboots. Check post 9308 in CM10 thread.
Sent from my EndeavorU using xda app-developers app

TToivanen said:
CM10 requires a special boot.img for newer hboots. Check post 9308 in CM10 thread.
Sent from my EndeavorU using xda app-developers app
Click to expand...
Click to collapse
You are a goddamn hero! Thanks, this solved everything.

No problem!
Sent from my EndeavorU using xda app-developers app

[Q] Cannot get out of boot animation nor flash by odin or fastboot - Help please

Hi everyone, I'm new here and I have a GNex on my hands.
While I received it to fix; I could not get it past a bootloop from the nexus 4.0.4 Boot.
Problem is I cannot seem to get past the boot animation screen nor upgrade it.
Tried flashing another bootloader via fastboot, and the bootloader does not change, stays in same version.
HW Version : 9
Bootloader version : PRIMEKK15
Baseband version : I9250XXKK6
I proceed doing a fastboot erase bootloader and trying another bootloader, rebooting into another bootloader but no luck
Tried also ODIN flash but no luck; stays into the same
Booting into recovery mode goes into stock recovery and tries to flash a file from /cache
By trying to flash CWM via fastboot flash recovery <cwm image> flashes image but no luck on booting into CWM.
Anbody can lend a hand please?
Thanks!

jhonnyx said:
Hi everyone, I'm new here and I have a GNex on my hands.
While I received it to fix; I could not get it past a bootloop from the nexus 4.0.4 Boot.
Problem is I cannot seem to get past the boot animation screen nor upgrade it.
Tried flashing another bootloader via fastboot, and the bootloader does not change, stays in same version.
HW Version : 9
Bootloader version : PRIMEKK15
Baseband version : I9250XXKK6
I proceed doing a fastboot erase bootloader and trying another bootloader, rebooting into another bootloader but no luck
Tried also ODIN flash but no luck; stays into the same
Booting into recovery mode goes into stock recovery and tries to flash a file from /cache
By trying to flash CWM via fastboot flash recovery <cwm image> flashes image but no luck on booting into CWM.
Anbody can lend a hand please?
Thanks!
Click to expand...
Click to collapse
You can flash a custom recovery like cwm or twrp. Then you can acces the custom recovery and adb push your ROM and gapps. Then you do the wipes and flash the ROM and gapps. If you dont understand anything you just have to tell me
Sent from my Galaxy Nexus using XDA Premium HD app

Thanks mrgnex. I've tried flashing TWRP, but the only thing it does is boot into stock recovery and tries to flash a file from /cache/, which file is: 5a81769b6d01.signed-yakju-IMM76I-from-ICL53F.5a81769b.zip; pretty weird. Issue is the same as this thread: http://forum.xda-developers.com/showthread.php?t=1909331&page=4

use: fastboot boot recovery.img

and "recovery.img" which recovery do you suggest? twrp or a CWM in particular?

doesnt matter. whichever.

jhonnyx said:
and "recovery.img" which recovery do you suggest? twrp or a CWM in particular?
Click to expand...
Click to collapse
I suggest the latest TWRP.
http://www.teamw.in/project/twrp2
Edit: Have you read this?

TheMysteriousOne said:
I suggest the latest TWRP.
http://www.teamw.in/project/twrp2
Edit: Have you read this?
Click to expand...
Click to collapse
While now I'm trying to install latest TWRP (already did and no luck) I'm downloading the pack from the "Have you read this?".
The things that I'm seeing right now that seem to be wrong are:
1 - everytime I reboot the phone, the "fastboot oem unlock" seems to be gone and phone re-locks again (weird!)
2 - every change I make to the filesystem, seems to be non-persistent I/E: push something via adb push and on reboot it's gone! :/
Any help would be greatly appreciated.

jhonnyx said:
While now I'm trying to install latest TWRP (already did and no luck) I'm downloading the pack from the "Have you read this?".
The things that I'm seeing right now that seem to be wrong are:
1 - everytime I reboot the phone, the "fastboot oem unlock" seems to be gone and phone re-locks again (weird!)
2 - every change I make to the filesystem, seems to be non-persistent I/E: push something via adb push and on reboot it's gone! :/
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Can you elaborate on why exactly you were not able to install TWRP?

TheMysteriousOne said:
Can you elaborate on why exactly you were not able to install TWRP?
Click to expand...
Click to collapse
Surely:
1 - Unlock via fastboot oem unlock
2 - fastboot erase recovery (exits with ok)
3 - fastboot flash recovery twrp_versiondoesnotmatter.img (exits with ok)
4 - reboot w/power+vlup+voldown and select reboot recovery
5 - stock recovery appears
an alternate method that i've tried:
1 - Unlock via fastboot oem unlock
2 - fastboot boot twrp_versiondoesnotmatter.img (exits with ok)
3 - TWRP boots and flashes a zipfile from /cache/ then reboots automatically
That's what happens. A mistery, huh?
Also I've tried OMAP Flash, and; the same issue happens over and over again

Have you tried doing a factory reset using the stock recovery?

TheMysteriousOne said:
Have you tried doing a factory reset using the stock recovery?
Click to expand...
Click to collapse
AFAIK, Yes
What happens once I start the stock recovery; as I've already stated; starts flashing a zip file located into /cache/ (5a81769b6d01.signed-yakju-IMM76I-from-ICL53F.5a81769b.zip); then bleh, starts the bootloop again.
I've tried the power+volup then selected wipe cache and wipe system and it's the same.

Did you try flash google's stock images (all of them) ?
Also try flashing TWRP in the boot (kennel) partition by :-
Code:
fastboot flash boot <path to twrp>.img
This will force the phone into Recovery (But you will have recovery bootloop , can be solved by flashing a kernel) .
when you boot into recovery install a Kernel and ROM . also you will lose the recovery after that .
You can flash the TWRP from the TWRP itself (to put it in the right partition) by (in the build in terminal) :-
Code:
dd if=/<path to twrp in SD>.img of=/dev/block/mmcblk0p8
Good Luck .
Sent from my Galaxy Nexus using xda app-developers app

$Parker said:
Did you try flash google's stock images (all of them) ?
Also try flashing TWRP in the boot (kennel) partition by :-
Code:
fastboot flash boot <path to twrp>.img
This will force the phone into Recovery (But you will have recovery bootloop , can be solved by flashing a kernel) .
when you boot into recovery install a Kernel and ROM . also you will lose the recovery after that .
You can flash the TWRP from the TWRP itself (to put it in the right partition) by (in the build in terminal) :-
Code:
dd if=/<path to twrp in SD>.img of=/dev/block/mmcblk0p8
Good Luck .
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
fastboot flash boot <path to twrp>.img does not boot the recovery . I mean; still boots the normal Kernel.
Actually I'm trying what TheMysteriousOne told me by downloading the stock Gnex zip (250Mb) to flash via Odin.

Ohh, bad luck strikes again:
<ID:0/011> system.img
<ID:0/011> Complete(Write) operation failed.
cannot write system.img :/
Any ideas?

Unlock your bootloader with omapflash. Although even if it does unlock, Your emmc/board probably has died.
a manta wrote this.

beekay201 said:
Unlock your bootloader with omapflash. Although even if it does unlock, Your emmc/board probably has died.
a manta wrote this.
Click to expand...
Click to collapse
can you please me guide how to do the omapflash?
I've downloaded a file called OMAPFlash_tuna.zip.
- Set battery of the device aside
- Plug device into USB, let it detect the device and flash the SBF I think.
That'd be all?

beekay201 said:
Unlock your bootloader with omapflash. Although even if it does unlock, Your emmc/board probably has died.
a manta wrote this.
Click to expand...
Click to collapse
Pardon me, if EMMC/Board is dead; why does it boot or get into bootloop? There is something that reflashes itself; it even overrides odin or heimdall...

Have you tried going back to completely stock using the method outlined here? http://forum.xda-developers.com/showthread.php?t=1626895

jhonnyx said:
can you please me guide how to do the omapflash?
I've downloaded a file called OMAPFlash_tuna.zip.
- Set battery of the device aside
- Plug device into USB, let it detect the device and flash the SBF I think.
That'd be all?
Click to expand...
Click to collapse
Read this thread
http://forum.xda-developers.com/showthread.php?t=2016628
a manta wrote this.

[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] HTC One M8 (bricked?)

Hi guys I am trying to get my phone in some sort of working order. I have CWM Recovery 6.0.5.1 for some reason no matter what I do to change the recovery it stays the same. I've tried installing lower CWM and also tried installing TWRP which again it says it was installed but when i go to recovery it still shows the CWM recovery. I installed CM11 and it worked fine, when I installed gapps is when the problems started. I've tried install multiple roms now, and it just doesn't want to take anything

thetinyjesus said:
Hi guys I am trying to get my phone in some sort of working order. I have CWM Recovery 6.0.5.1 for some reason no matter what I do to change the recovery it stays the same. I've tried installing lower CWM and also tried installing TWRP which again it says it was installed but when i go to recovery it still shows the CWM recovery. I installed CM11 and it worked fine, when I installed gapps is when the problems started. I've tried install multiple roms now, and it just doesn't want to take anything
Click to expand...
Click to collapse
try restoring a stock nandroid backup. if you dont have one then download one from general thread. and also make a nandroid backup of your current rom. not so sure what your problem is but maybe returning to pure stock will help.

I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom

thetinyjesus said:
I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom
Click to expand...
Click to collapse
Install/flash via fastboot the official cwm 6.0.51 that you had. then try again. if your lucky then it might work.

thetinyjesus said:
I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom
Click to expand...
Click to collapse
Get TWRP Manager from the play store. Hit the three line menu thingy on the top left of the app, and pick install TWRP. Super easy.

Ok guys ive tried reinstalling the same CWM version and reinstalling CM11 with no luck. I cannot change the bootloader to TWRP because it appears to be stuck on the CWM. The problem started for me when I installed the gapps through CWM, as soon as I did that when the phone went to boot it now says please enter the password for android, then says it was the right password but data is corrupt and cant use phone.
Is there a way to attempt to just format the entire phone including partition size and start from scratch again?

thetinyjesus said:
Ok guys ive tried reinstalling the same CWM version and reinstalling CM11 with no luck. I cannot change the bootloader to TWRP because it appears to be stuck on the CWM. The problem started for me when I installed the gapps through CWM, as soon as I did that when the phone went to boot it now says please enter the password for android, then says it was the right password but data is corrupt and cant use phone.
Is there a way to attempt to just format the entire phone including partition size and start from scratch again?
Click to expand...
Click to collapse
How are you trying to flash these recoveries (they're not called bootloaders, that is something totally separate)?
Have you tried using TWRP Manager as I suggested earlier, or are you using ADB? And If you are using ADB and trying to flash it that way, what fastboot commands are you giving?
There is no way that your should be "stuck" with CWM.

Okay what i have to do is fastboot its the only thing i can get to work. Not at my computer but yeah i fastboot the recovery img via cmd in windows. Fastboot flash recovey i use ane it successfully does. Doesnt matter what img or recovery i use when i boot into recovery it still uses cwm. Also only way i can put a rom on is adb sideload but now thats even failing with status 7 error

Also when i try the command fastboot oemRUU or whatever the command is it reboots the phone shows CM logo and boots till asking for android pw

thetinyjesus said:
Okay what i have to do is fastboot its the only thing i can get to work. Not at my computer but yeah i fastboot the recovery img via cmd in windows. Fastboot flash recovey i use ane it successfully does. Doesnt matter what img or recovery i use when i boot into recovery it still uses cwm. Also only way i can put a rom on is adb sideload but now thats even failing with status 7 error
Click to expand...
Click to collapse
The status 7 error is because of an outdated recovery. Not much help, I know.
It's strange that the TWRP Manager doesn't work. I've helped others with problems flashing recovery, and it has worked for them.
You could also try ROM Toolbox to update your CWM, or ROM Manager, but ROM Toolbox is better/more complete. It has everything ROM Manager has plus some.
The other option that you may not want to take is to do a COMPLETE wipe of your phone. That always sucks.

Going to try those programs. Thank you btw and how do i perform the full wipe i was about to throw the phone out lol.

@thetinyjesus You could also try this app. No PC necessary.

Thanks but cannot use the app i cannot get the phone to boot. Do you have directions for a full wipe

thetinyjesus said:
Going to try those programs. Thank you btw and how do i perform the full wipe i was about to throw the phone out lol.
Click to expand...
Click to collapse
Actually, you full wipe in recovery. lol
If you haven't tried TWRP Manager yet, that would be my first choice.

Damn that didnt work than i tried all those format options in the bunked recovery with no luck it sucks

If you're using the command prompt to flash the recovery, provide a screenshot of your desktop so that we can see what you're doing and what "it's" doing.
Starting to think that it's more of an "operator" fault and not anything to do with the device that doesn't want to play along.

Okay once im back home ill show the output

Here is the output from flashing the recovery. Once again when I went to recovery it loaded with CWM.

Also here is the output from sideloading the cm file again (same error no matter what rom I try)
Windows CMD: C:\Users\Jimmy\Desktop\platform-tool>adb sideload cm.zip
sending: 'cm.zip' 100%
Phone: Installing update...
set_perm_recursive: "/system" not a valid uid
E: Error in /tmp/update.zip
(Status 7)
Installation aborted

Anyone?