Develop Bugs

BRICKED??!!

Guys, I think I may have bricked my phone. I've been rooting for a while and I know this is usually impossible. But I'm having major issues
I tried to flash an updated version of gummynex, so I flashed super_wipe_lite and then the ROM, and it aborted the installation. So I tried to mount USB storage in clockworkmod, which of course failed because there is no sd card. I rebooted, and I got the blank google screen with unlock. If I reboot holding power and volume down, the only option I get is start. I can't get ADB to connect in either this mode, or in the standard google logo screen!
WHAT ARE MY OPTIONS!? Thanks!

Wrong forum. Anyways, you're not out of luck, ypur bootloader is fine so I'm sure there's some Oden related restore for the nexus. Try the stickies.
Sent from my Galaxy Nexus using xda premium

Edited: So you can get to the bootloader, but from there you can't use fastboot? Like its not showing in fastboot devices?
Sent from my Galaxy Nexus using xda premium

davehasninjas said:
So you can get to the bootloader, but from there you can't use the volume keys to go to fastboot?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
wow I'm dumb. I forgot you had to hold volume up + down to get the options to boot to recovery. I'm in CWM-touch and installing another ROM I had ont here so I can boot it up from my pc, copy the new rom again to my sdcard, and flash it. Unless there's a way to get ADB to work without installing a rom? then I could just push the new rom?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Wrong section
edit
10 char

If you're already softbricked I would recommend just getting the factory files, use fastboot to flash back to stock and just start over again, if you had already used super wipe than its not like you need to save any data, and its always better to be safe than sorry.
Edit: if you can get to recovery and have another rom or nand then you'll be fine regardless.
Sent from my Galaxy Nexus using xda premium

In CWM recovery the ADB daemon is started so you can use ADB to push a new ROM to /data/media to flash via CWM.

http://forum.xda-developers.com/showthread.php?t=1426207
There's the ODIN files my friend. It's like 4 threads up. Do what everyones saying and use these to get back to stock.

silow said:
In CWM recovery the ADB daemon is started so you can use ADB to push a new ROM to /data/media to flash via CWM.
Click to expand...
Click to collapse
+1 on this. I had to do it when I first got the phone. Boot into CWM recovery and then adb works to push a new ROM.

You don't have to Odin back to stock. Let me guess, you're using the new touch recovery?
Boot into bootloader and flash the regular recovery through fastboot. PM me if you need any help.
Sent from my Xoom using Tapatalk

Galaxy Nexus briked!!!

Hello
Last night i wanted to update my phone from AOKP M4 to B28 and with that ocasion i wanted to update the kernel too. I tried to flash B28 over the M4 with cache wipe and nothing after this i make a full wipe(factory,partition,dalvick and battery stats). And all was good...when i try to flash the Leankernel the phone entered in bootloop. After this i tried all the options(gnex toolkit,fastboot,odin)and nothing, my phone now only enter in fastboot mode or download mode the cwm disappear and instead of cwm is the green robot with a red triangle on it.
I post two screenshot maybe someone can help me with this problem because i think i will lose the warranty.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/URL][/IMG]
First are from the gnex tollkit ant the last is from fastboot.

Did you try to unroot / reroot via fastboot?

Tryed everything but nothing only errors...

Time to buy a new nexus mate.
Eligible XDA Developer GRAVITY 360

Tried adb? If yes congats you are the 1st who achieved to brick gnex. Except someone else have a crazy idea!

Should i comment your post??

flash the stock images http://code.google.com/android/nexus/images.html
everyone should know how to flash it manually with fastboot..you probably need to flash only kernel and system
the common user error is that when you get a bootloop, people went crazy and start doing eveything...the next time when you got a bootloop, you SIMPLY have to go in recovery and restore the backup.
EDIT: what the error with fasboot? the pic is too small to read

andQlimax said:
flash the stock images http://code.google.com/android/nexus/images.html
everyone should know how to flash it manually with fastboot..you probably need to flash only kernel and system
the common user error is that when you get a bootloop, people went crazy and start doing eveything...the next time when you got a bootloop, you SIMPLY have to go in recovery and restore the backup.
EDIT: what the error with fasboot? the pic is too small to read
Click to expand...
Click to collapse
He lost cwm as well so he could't go to recovery and restore. If he can't root/unroot via fastboot i doubt he can flash stock image. I hope he can.

arvylas said:
He lost cwm as well so he could't go to recovery and restore. If he can't root/unroot via fastboot i doubt he can flash stock image. I hope he can.
Click to expand...
Click to collapse
he lost cwm after tring everything, before that he probably can

I make the cwm work but i don't know how to flash the stock image... If i restore my backup i get a bootloop.

Go to fastboot on the phone. Plug it in. Extract the stock factory image somewhere. Open command prompt, navigate to wherever you have GNex toolkit's fastboot binary.
fastboot flash radio radio.img
fastboot flash boot boot.img
fastboot flash system.img
There you go. Start the phone.

So it's not really bricked after all..
Try to restore the google image with the gnex toolkit by putting the zip file in the correct folder (read instruction).

Steelskinz said:
So it's not really bricked after all..
Try to restore the google image with the gnex toolkit by putting the zip file in the correct folder (read instruction).
Click to expand...
Click to collapse
learn to use fastboot

Use this.
http://forum.xda-developers.com/showthread.php?t=1400871
Restore GNex
Enjoy phone
????
Profit

when my phone bootloopt when i wanted to root it using the toolkit i got the same thing android with red triangle in it...i simply rerooted with a boot image and my problem was solved....... isbit a little glitch that sometimes happens when flashing a prerooted rom or something....cuase this is not the first topic on here with this problem
Sent from my Galaxy Nexus using XDA

I tryed with Gnex ToolKIt read what i post the problem is that in fastboot and Gnex ToolKit i receive this error FAILED<status read failed<too many link>> maybe now you understand me. The only way to flash something is in fastboot in cwm i can cwm work to navigate to wipe but when i want to flash something it restarts.I have cwm 5.0.0.2 something like this.

Try installing via fastboot or cwm a stock or aokp again after wiping everything of course... if you have cwm there is no prob.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-2

arvylas said:
Try installing via fastboot or cwm a stock or aokp again after wiping everything of course... if you have cwm there is no prob.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
Man when i try to flash something in cwm it starts and after reboot it self.

OK, start from the start, when you plug your phone in to the computer in bootloader and type "fastboot devices" does it show up?
If it does then you have no problems.
If not then you may have driver problems.
If it does show up just flash the images one by one and everything will be fine.
The google stock factory images that is.

Toolkits and 1 click methods are the exact reason we have these "OMG I bricked my nexus" threads...... Learn how to use adb and fastboot!!!!!!
Sent from my Galaxy Nexus using xda premium

need some help flashing help. not normal.[SOLVED]

Ive had my phone rooted and.been.flashing since.I got months ago. Imm running ics right now. My issue is I need to flash back to stock and.unroot. Prrrroblem is that my power button is broke. I cantt get into download mode to ODIN it and.cantt get into recovery to flash it. Any thoughts?

Do you have a cwm
Sent from my SPH-D710 using XDA

5FOOTER said:
Do you have a cwm
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I do.

Download the app called Quickboot from the app store. Had recovery and download mode reboot options.
Sent from my SPH-D710 using XDA

Grab Quick Boot from the Play Store. You can boot straight to recovery or bootloader from that app without the power button. Then flash stock ROM and remove root

Wartouched said:
Download the app called Quickboot from the app store. Had recovery and download mode reboot options.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Thanks. I always think about things like this after the fact. I understand newbie frustration haha.

If you are around a PC, you can also use "extra options" in Auto Root. You'll be presented with options to reboot to recovery (Option N) or odin dl mode (Option O). Alternatively you can use "adb reboot recovery" or "adb reboot download"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

sfhub said:
If you are around a PC, you can also use "extra options" in Auto Root. You'll be presented with options to reboot to recovery (Option N) or odin dl mode (Option O). Alternatively you can use "adb reboot recovery" or "adb reboot download"
Click to expand...
Click to collapse
Does the cmd run if I flashed back in november and havnt done anything but flash since then?? I had to root a kindle fire so i understand the adb commands.

And can anyone point me to a way to unroot so sprint will honor a warranty?? I tried to search I didnt find anything clearly defined at unrooting.

coreyalfredson said:
And can anyone point me to a way to unroot so sprint will honor a warranty?? I tried to search I didnt find anything clearly defined at unrooting.
Click to expand...
Click to collapse
That's in sfhub's autoroot as well I believe

coreyalfredson said:
Does the cmd run if I flashed back in november and havnt done anything but flash since then?? I had to root a kindle fire so i understand the adb commands.
Click to expand...
Click to collapse
Auto Root uses ADB commands, so basically if you can connect your phone to your PC and you have USB debugging enabled, it will work.
If your power button doesn't work, I would use ODIN as a 2nd option. It is probably the quickest to get you back to stock without fuss, but in the remote chance something goes wrong, you'd need your power button to get back into ODIN DL mode.
You might want to have a USB jig available if you use ODIN since it can get you back into ODIN DL mode even if your power button doesn't work.

coreyalfredson said:
And can anyone point me to a way to unroot so sprint will honor a warranty?? I tried to search I didnt find anything clearly defined at unrooting.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1433101
Follow this forum and read down. This will help you get to stock, unrooted, EL29. EL29 is the current stock firmware. Also sprint isn't really to bad about rooted phones. If your problem is mechanical, it shouldn't matter if your rooted or not.

Motorola Defy+ Bricked

Hi,
Today iÍ totaly bricked my Defy+ after unsuccessful installing CaynogenMod CMX 10 (it stuck on boot animation). After that I tried with CaynogenMod bootmenu to install again 2nd-boot and 2nd-init to boot to stock ROM. But after that I can just boot to stock recovery menu and Android bootmenu (by CM team). In this bootmenu from CM I can just to choose default bootloader. No other functionality works, everytime I choose for example: Recovery -> Custom recovery it appears this error message: No such file or directory...... So I moved to RDSlite, but my phone is not recognized by Windows or RDSLite. And battery is not charging, only blink white LED when is on computer USB. And battery is under 30%. Don't know what to do now...

I take it uv installed all the drivers needed?
Sent from my GT-I9300 using xda app-developers app

snowwhite007 said:
I take it uv installed all the drivers needed?
Click to expand...
Click to collapse
Yes I have installed official drivers from Motorola. I used them for SuperOneClick root.

Are you on bootloader mode while connecting the Defy+ to your PC? This is how it looks when on bootloader mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I have a similar question I'm afraid.
To update my Defy+ from CM7 to CM10 I wiped all there had to be wiped. When I got to "install zip from SDcard" I found out I had placed the wrong SDcard into the phone. Perhaps I shouldn't have done this but I did, I turned off the phone, changed the SDcard and tried to continue the process.
Unfortunately I can't get to the boot menu anymore, there's just the "M" logo. When I try to reacht the "old" bootmenu (reboot with volume down) the phone hangs at the Android robot with an exclamation mark next to it.
Is there a way solution?

andr0idfreak said:
Are you on bootloader mode while connecting the Defy+ to your PC? This is how it looks when on bootloader mode.
Click to expand...
Click to collapse
I never seen this screen. How can I get to this? I just know how to get to bootloader with pressed volume down and power button. And in this it's not worked for me.

@fido1828
I guess that's the stock recovery. Try pressing the options soft key or the vol- or vol+ while in that screenIf that happens, you can wipe data and cache and check again.
---------- Post added at 11:14 PM ---------- Previous post was at 11:13 PM ----------
usrbowe said:
I never seen this screen. How can I get to this? I just know how to get to bootloader with pressed volume down and power button. And in this it's not worked for me.
Click to expand...
Click to collapse
You are doing it wrong buddy. You need to press Vol+ and then the power button.

andr0idfreak said:
I guess that's the stock recovery. Try pressing the options soft key or the vol- or vol+ while in that screenIf that happens, you can wipe data and cache and check again.
---------- Post added at 11:14 PM ---------- Previous post was at 11:13 PM ----------
You are doing it wrong buddy. You need to press Vol+ and then the power button.
Click to expand...
Click to collapse
YES! It work now, and I also upload .sbf. So many thanks to you Iam feelling so stupid now.

andr0idfreak said:
@fido1828
I guess that's the stock recovery. Try pressing the options soft key or the vol- or vol+ while in that screenIf that happens, you can wipe data and cache and check again.
Click to expand...
Click to collapse
Thank you, that helped, a bit. Got to the stock recovery and was able to wipe all except Dalvik. Perhaps there's no need to wipe dalvik again, it was already wiped before and no app has run since.
However, when I try to install CM10 the installation gets aborted because the signature verification fails. The zip files have been put on the SDcard while the card was in the PC. Will that be it? Is there a way to get them on the SDcard using the Defy+ now?

You can flash only ZIPs signed by Motorola via Stock Recovery. To flash a CM ROM, you need to get CWM on board. For that you need to install 2ndinit. If stock ROM boots successfully, root it and install 2ndinit and then download latest recovery to get CWM.

andr0idfreak said:
If stock ROM boots successfully, root it and install 2ndinit and then download latest recovery to get CWM.
Click to expand...
Click to collapse
Unfortunately the phone won't boot. After the full wipe there's nothing left to boot I'm afraid. Is there any other way?

The only way out now is flashing SBF via RSDLite.

andr0idfreak said:
The only way out now is flashing SBF via RSDLite.
Click to expand...
Click to collapse
ok. RSDlite I used to install CM7, it's still on the pc. But excuse my ignorance, what's SBF?

You used RSDLite to install CM7!!!
You should have read the beginners guide before trying this.
http://forum.xda-developers.com/showthread.php?t=1216982

andr0idfreak said:
You used RSDLite to install CM7!!!
You should have read the beginners guide before trying this.
http://forum.xda-developers.com/showthread.php?t=1216982
Click to expand...
Click to collapse
Sorry, I did read that, understood part of it and managed to install CM7 without any problem.
Now that I re-read parts of it I understand what an SBF is, but still I can't get my PC to see the Defy+. As soon as the battery is placed the phone starts to boot, holding the volume button and subsequently both volume buttons puts it in recovery mode. But than, what can I do to make the computer/RSDlite see the phone?

In that case, try keeping the vol+ pressed, then insert the battery, it should enter to bootloader mode.

HELP bootlooping sony logo!

hi, tried to install aosp lollipop, the installtion went fine. but not touchscreen as usual, this is not the problem my problem is i cant turn my phone on or go to fastboot or flash mode, if i plug it to charger it bootloops on sony logo. i have no idea what happend to it. anyone can help?

bigsmoke9250 said:
hi, tried to install aosp lollipop, the installtion went fine. but not touchscreen as usual, this is not the problem my problem is i cant turn my phone on or go to fastboot or flash mode, if i plug it to charger it bootloops on sony logo. i have no idea what happend to it. anyone can help?
Click to expand...
Click to collapse
i think that i have the weirdest things ever in here :\

it boots now, i can see the lockscreen, if i try to use the off button near simcard it functions as a vol down key! seriously what the hell is going on?
i cant turn it off until it runs out of battery

Can anyone help me, I flashed stock rom from remix rom by flashtool but I can not start, just boot into Sony logo then blue screen then restart again and again ? B4 that it functioned well on remix rom
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

bigsmoke9250 said:
hi, tried to install aosp lollipop, the installtion went fine. but not touchscreen as usual, this is not the problem my problem is i cant turn my phone on or go to fastboot or flash mode, if i plug it to charger it bootloops on sony logo. i have no idea what happend to it. anyone can help?
Click to expand...
Click to collapse
Did you try PC Companion repair? Start there. Are you sure no fastboot or flash mode? I'm surprised that flashing a rom would break that. Is that all you did? Did you use fastboot to flash AOSP?

seaxxz said:
Can anyone help me, I flashed stock rom from remix rom by flashtool but I can not start, just boot into Sony logo then blue screen then restart again and again ? B4 that it functioned well on remix rom
Click to expand...
Click to collapse
If you can get fastboot mode, flash a CM bootand recovery img, boot into recovery, do a full wipe, and flash a rom zip. It sounds like you're having trouble with either a dirty flash or wrong boot img, or both.

levone1 said:
Did you try PC Companion repair? Start there. Are you sure no fastboot or flash mode? I'm surprised that flashing a rom would break that. Is that all you did? Did you use fastboot to flash AOSP?
Click to expand...
Click to collapse
Thank you. I've tried pc companion and it works
---------- Post added at 08:26 AM ---------- Previous post was at 07:58 AM ----------
levone1 said:
If you can get fastboot mode, flash a CM bootand recovery img, boot into recovery, do a full wipe, and flash a rom zip. It sounds like you're having trouble with either a dirty flash or wrong boot img, or both.
Click to expand...
Click to collapse
Thanks for your help. Problem was solved )

levone1 said:
Did you try PC Companion repair? Start there. Are you sure no fastboot or flash mode? I'm surprised that flashing a rom would break that. Is that all you did? Did you use fastboot to flash AOSP?
Click to expand...
Click to collapse
yes i flashed it using fastboot, and again yes i had no fastboot and flash mode but thank god flash mode worked this morning and i am back to stock again. i dont know why that happend or the broken touchscreen on other custom roms? maybe bad luck or doing something wrong