Develop Bugs

Stuck in endless boot-loop (PLEASE HELP)!!!

I have no clue how this started. Last thing I did was flash Amon_RA 2.3 recovery on FEB 9th then the newest CM7 nightly, 32 I believe. Everything was fine with my phone up until an hour ago. I was on the phone with Sprint, they screwed up my sign-up date. But thats a whole other story. My phones battery was getting low during the call. Once I ended the call I set my phone down then noticed it started going into a boot cycle. Now all it will do is boot to the splash screen then reboot again, and again, and again. I tried to pull the battery and boot to recovery. It does the same thing. It will let me get to the bootloader and select recovery. Once I select recovery, it starts its damn boot loop. Any ideas? PLEASE HELP!

Well since you can't get into recovery, try pushing a recovery via adb or fastboot...

teh roxxorz said:
Well since you can't get into recovery, try pushing a recovery via adb or fastboot...
Click to expand...
Click to collapse
Its been soo long since I had to do any adb. Actually since launch using toasts root methods. Can you explain the commands please? On another note I do not have any recovery.img's saved to my pc. I dl'd them directly to my phone and flashed from a terminal app.

http://forum.xda-developers.com/showthread.php?t=705026
this thread can help you out especially the OP

download the amon-ra p36img.zip and place it onto your sdcard somehow, pull the battery, boot into bootloader, flash the pc36img and then reboot. they you'll have recovery and can load any rom you want again

t3project said:
download the amon-ra p36img.zip and place it onto your sdcard somehow, pull the battery, boot into bootloader, flash the pc36img and then reboot. they you'll have recovery and can load any rom you want again
Click to expand...
Click to collapse
^ Do exactly that [basically what I was saying/] But take out the battery and put the SD card in your computer via adapter to put the file on there.

Ok, the PC36IMG.ZIP is on the root of my sd and the bootloader is not seeing it? Now what?

if you're using windows make sure to not have the file as PC36IMG.zip.zip

mich11128 said:
if you're using windows make sure to not have the file as PC36IMG.zip.zip
Click to expand...
Click to collapse
Ok, I got it to see it. I ran the update, once it rebooted I selected recovery. It first asked me if I want to delete data? Or something on those terms. I chose no, and it will not let me boot to recovery still.....Back to the boot loops
Edit: First time I must have selected clear storage by mistake. Anyway I hit no at that point. I just re-dl'd the pc36img.zip file to make sure. It does run in the boot loader but will not reboot to recovery. Still endless loop????

splink7007 said:
Ok, I got it to see it. I ran the update, once it rebooted I selected recovery. It first asked me if I want to delete data? Or something on those terms. I chose no, and it will not let me boot to recovery still.....Back to the boot loops
Click to expand...
Click to collapse
Considering you can't get into recovery still, I would suggest reflashing the recovery and erasing the data when prompted.
Did you do a nandroid backup? I only ask cause once you get back into recovery you can just restore that.

so the bootloader read the file, then you ran the update and then it asked you to delete data? I don't remember that being a part of the process. Try it again and as soon as it's done updating try to get into the recovery again. If not then try to use adb.

sekigah84 said:
Considering you can't get into recovery still, I would suggest reflashing the recovery and erasing the data when prompted.
Did you do a nandroid backup? I only ask cause once you get back into recovery you can just restore that.
Click to expand...
Click to collapse
Ya I hit clear storage at first by mistake. I believe if I hit that it will wipe my entire sd card and will loose my nand backup?

mich11128 said:
so the bootloader read the file, then you ran the update and then it asked you to delete data? I don't remember that being a part of the process. Try it again and as soon as it's done updating try to get into the recovery again. If not then try to use adb.
Click to expand...
Click to collapse
Re-ran the update and still loops. The first time I ran it I hit clear storage instead recovery by mistake. Im sitting at the bootloader screen. I cant remember the adb commands. Can you refresh my memory? Thanks

Copy recovery-RA-supersonic-v2.3.img to the root of your sdcard
start the terminal app or launch adb shell
su(press enter)
flash_image recovery /sdcard/recovery-RA-supersonic-v2.3.img(press enter)
reboot recovery(press enter)
I find it strange that all this happened after getting off the phone with Sprint lol.
Does it still say S-OFF at the top of your bootloader?

I copied this from the amon ra recovery thread
Copy recovery-RA-supersonic-v2.3.img to the root of your sdcard
start the terminal app or launch adb
su(press enter)
flash_image recovery /sdcard/recovery-RA-supersonic-v2.3.img(press enter)
reboot recovery(press enter
now whenever I am about to start adb I use the command "./adb devices" without quotations of course, to make sure adb recognizes my evo oh and ignore the ./ that's just for mac users. When you enter that command you should see the serial number for your evo. after that I use
./adb shell
that should lead to
#
Then you type
su
and then you enter the rest of the commands. Sorry I didn't really organize it but that's pretty much it.

sekigah84 said:
Copy recovery-RA-supersonic-v2.3.img to the root of your sdcard
start the terminal app or launch adb shell
su(press enter)
flash_image recovery /sdcard/recovery-RA-supersonic-v2.3.img(press enter)
reboot recovery(press enter)
I find it strange that all this happened after getting off the phone with Sprint lol.
Does it still say S-OFF at the top of your bootloader?
Click to expand...
Click to collapse
lol you beat me to it and I was also about to ask if the phone was still rooted. READ MY MIND hahaha

sekigah84 said:
Copy recovery-RA-supersonic-v2.3.img to the root of your sdcard
start the terminal app or launch adb shell
su(press enter)
flash_image recovery /sdcard/recovery-RA-supersonic-v2.3.img(press enter)
reboot recovery(press enter)
I find it strange that all this happened after getting off the phone with Sprint lol.
Does it still say S-OFF at the top of your bootloader?
Click to expand...
Click to collapse
I totally agree!! Crazy....Yes it still says S-OFF. How do I launch adb shell from the bootloader? Im sorry, I havent used adb or fastboot since launch rooting using toasts method.

Wish I could help you there but I haven't ran adb on a windows since my G1 lol I'll see if I find a thread with some help for adb and windows.
EDIT: Maybe this will help. http://forum.xda-developers.com/showthread.php?t=694250

Ok, if I run fastboot devices, it sees my device. But if I run adb devices, it doesnt see my device anymore. Im soo lost now.

sorry I forgot adb runs through recovery, what you have to use I believe is fastboot flash to flash the recovery image
here try this page better...I used this when I had to root my nexus one the hard way (before that crappy 1-click method was devised) this is the best guide I'd ever used as far as adb/fastboot commands.
http://forum.xda-developers.com/showthread.php?t=694250

Terminal Emulator

Is there a way to flash recovery image with terminal emulator i knew there was a way when i first rooted my G1 if so is it safe and how to i do it ?

If you want to flash a recovery image (I guess you mean a Nandroid backup) you need to do it from the recovery. You cannot do it from the phone itself, neither from terminal nor from ADB.

Logseman said:
If you want to flash a recovery image (I guess you mean a Nandroid backup) you need to do it from the recovery. You cannot do it from the phone itself, neither from terminal nor from ADB.
Click to expand...
Click to collapse
No i mean flash cwm recovery i.e (boot.boot.img) from terminal emulator instead of ADB as ADB is nothing more than a remote terminal?

You don't flash boot.img files with ADB, you do it with Fastboot. Fastboot is a completely different thing.

Logseman said:
You don't flash boot.img files with ADB, you do it with Fastboot. Fastboot is a completely different thing.
Click to expand...
Click to collapse
Ooops my bad lol i thought there was a way to to it with terminal emulator like flash_image etc

For most phones, you can flash the recovery through a terminal.. but with newer SE phones, recovery is built into the kernel and you can't flash a new kernel unless you're in fastboot mode

There's three ways to get CWM working on your phone.
1. Boot the CWM (boot.img) through fastboot. Then use it and then reboot phone. CWM is gone and you need to boot it again from fastboot when ever you have to use it.
2. Flash Doomlords kernel as it's embedded in the boot.img (kernel). You can boot into at every time you need to from your phone (native CWM).
3. Flash CM7 onto your phone. Same story as with Doomlords kernel.
For all three choises above you need an unlocked bootloader to do it as you have to have fastboot access to issue the commands.
Regards Dousan...

[Q] installed Sper wipe before copy rom.zip to sdcard

I isntalled Super Wipe to my htc one x before load rom.zip to sd card :S now cant open phone or recovery mod :S so how can i load stock rom again help please

rover_x said:
I isntalled Super Wipe to my htc one x before load rom.zip to sd card :S now cant open phone or recovery mod :S so how can i load stock rom again help please
Click to expand...
Click to collapse
First you will need to reflash your recovery while your phone is in fastboot mode, you can do this by opening a cmd and using the command 'fastboot flash recovery recoveryfilehere.img' and changing recoveryfilehere for your recovery file's name.
I am a bit unsure on these next steps but I believe you will then need to boot into the recovery you just installed and then use the following commands.
'adb devices'
'adb shell'
'mount sdcard'
and then in another cmd you will use the command 'adb push ROMNAME.zip /sdcard
then reboot into recovery and look for your ROM in the root of your sd card and install it as usual. Don't forget to flash the kernal too.

I tried these steps but didnt get result

See http://forum.xda-developers.com/showpost.php?p=26119526&postcount=17 and adapt to yours.

i tired many times , but each time get message " error:device not found" :S

Do you have HTC USB driver installed ?

yes i did

So it means that you're successfully boot into recovery by fastboot boot recovery.img and adb not working for you ?
Please note, adb will not work when you do fastboot flash recovery recovery.img

ckpv5 said:
So it means that you're successfully boot into recovery by fastboot boot recovery.img and adb not working for you ?
Please note, adb will not work when you do fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Ah right, my bad
Sent from my HTC One X using xda premium

How to push files in fastboot or Recovery?

Hello,
One friend of mine have flashed franco kernel, but problably the kernel was corrupted and now he get stuck at the google logo.
How can he push a new kernel to the phone memory to flash it in the recovery?

Adb push in a custom recovery or you can reflash your ROM
Sent from my Galaxy Nexus using Tapatalk 2

JB has been known to get stuck at "google" for 10min or so. Did you wait long enough?
good day.

RevengeFNF said:
Hello,
One friend of mine have flashed franco kernel, but problably the kernel was corrupted and now he get stuck at the google logo.
How can he push a new kernel to the phone memory to flash it in the recovery?
Click to expand...
Click to collapse
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it

Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
Confirmed working, and a BAZILLION times faster than the chrome browser.

Zector said:
Confirmed working, and a BAZILLION times faster than the chrome browser.
Click to expand...
Click to collapse
??? chrome browser can flash roms?
10chars

Does it work with CWM?
Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
I tried this and it said "insufficient permissions for device" in ADB. My phone randomly rebooted and gets stuck on the boot logo, but everything on my sdcard got deleted. I have a Verizon Galaxy Nexus if that helps

If it's only the kernel causing problems, the easiest would be to run "fastboot flash boot <name of boot.img here>" from fastboot?(the original boot.img from the rom he's using would be found inside the zip file)
But if you screwed something else up in the process, you may need to flash the entire rom again from the recovery. If you are using cwm recovery, I believe it allows you to mount storage, so you can just move the rom file from the computer, and if you are using twrp, they have an option to sideload(under advanced), where you can connect you phone to your pc and run "adb sideload <name of rom.zip file here>" and it will install it right away.

mortenmhp said:
using cwm recovery, I believe it allows you to mount storage, so you can just move the rom file from the computer
Click to expand...
Click to collapse
this will not work, not with cwm nor with twrp, at this point; likely, it will never work as we don't have removable storage.

Then just use the sideload, it works quite well for me.

mortenmhp said:
Then just use the sideload, it works quite well for me.
Click to expand...
Click to collapse
Or just 'adb push rom.zip /sdcard/', or if that doesn't work, 'adb push rom.zip /data/media'.
Sent from my i9250

in my case TWRP didn't do so good with adb,
I think the recovery devs should have ADB in mind first of all. without ADB ur one foot in the grave

GruiaNovac said:
in my case TWRP didn't do so good with adb,
I think the recovery devs should have ADB in mind first of all. without ADB ur one foot in the grave
Click to expand...
Click to collapse
adb works fine with TWRP if you have updated adb drivers/adb daemon.
guess fastboot flashing images also eludes you.
so no, you're not in the grave.
*note* thanks for necroing a thread from December.

No, in bootloader its fine.
And apparently (if It wasn't a fluke) I think i booted normally , and having no rom it just stood there, and adb worked.
that saved me
TWRP dissapoints . have to look for replacement

stuck in recovery
so Im stuck in a similar situation
before installing a ROM which instructed to wipe the device, i did so, in fact i over did it.. wiped data/cache/davlik/system and internal storage
the same storage which had the ROM that i was supposed to install after wiping it.
I felt very dumb, but now stuck with the bootloader / fastboot / and TWRP recovery .. the TWRP recovery version i have HAS the adb sideload feature
which i've tried to install the Cyanogen ROM using ./adb sideload filename.zip , which hasnt work for Cyanogen but worked for the GApps after that ( I thought that was kinda weird).
the sideload command goes thru the sending of the entire ROM to the phone, but it never installs correctly..
NOW im stuck
any suggestions or help on how i can do it with what appears to me to be as fastboot / adb side load / and recovery options"??
thank you very much in advance
=====
update
=====
solved my problem... mounting the partition turns on full ADB to push the files onto the drive and install them using the recovery software

Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
you just saved my life... and my phone

Need urgent help, lost and confused.

Hello XDA, I got my Galaxy Nexus stock and OTA upgraded it to 4.1.1 Jellybean. I unlocked and rooted the phone and while installing roms I accidentally formatted and factory reseted my phone. I can get into boot loader, and I have CWM installed. If I could just move a rom onto the phone I could boot it. Problem is I cant figure out how to. Keep in mind I am also using a mac. Can anyone help me figure out how to push a rom zip onto the sdcard? Any help would be appreciated, thanks!

Mac infos
http://forum.xda-developers.com/showpost.php?p=23229578&postcount=3

Help
My ADB debugging wasnt on at the time, and now I cant push files to it, anyone have any ideas?

colinrball said:
My ADB debugging wasnt on at the time, and now I cant push files to it, anyone have any ideas?
Click to expand...
Click to collapse
You can abd push from a custom recovery

Alright so USB debugging isnt on but I can still use adb commands? How?

You have to boot into a custom recovery (CWM or TWRP) and use adb commands.
for ex. adb push NameOfRom.zip /sdcard/

I just tried that and my terminal returned
device not found

Don't mount anything don't do anything special in recovery at all.
You're booted into recovery?
Also...I found when I wasn't using naked drivers that it took ~30 seconds for ADB to actually be recognized.
Maybe wait a minute and try again.
If not unplug and plug in.

I can use fastboot commands and it it recognized in fastboot, can I flash a stock rom from this mode?

colinrball said:
I can use fastboot commands and it it recognized in fastboot, can I flash a stock rom from this mode?
Click to expand...
Click to collapse
If you're using fastboot...that means you're not in custom recovery.
Navigate to recovery in that menu.
Or use fastboot boot ______________.img to boot into a custom recovery if you have one downloaded and in your platform tools directory.
But yes, you COULD do that.
But I wouldn't yet.
You'll lose all of your data/apps/etc.

There are Google factory images for the GSM & Verizon versions
[HOW-TO] [GSM & CDMA] Convert to latest yakju/takju/mysid (incl JB) / Return to stock

Jubakuba said:
If you're using fastboot...that means you're not in custom recovery.
Navigate to recovery in that menu.
Or use fastboot boot ______________.img to boot into a custom recovery if you have one downloaded and in your platform tools directory.
But yes, you COULD do that.
But I wouldn't yet.
You'll lose all of your data/apps/etc.
Click to expand...
Click to collapse
There is nothing on my phone, I have CWM installed, however there are no ROMs on the sdcard to flash through CWM. How would I move a file onto my sdcard that I could flash with CWM via fast boot?

colinrball said:
There is nothing on my phone, I have CWM installed, however there are no ROMs on the sdcard to flash through CWM. How would I move a file onto my sdcard that I could flash with CWM via fast boot?
Click to expand...
Click to collapse
I've explained this process already.
Post three of my guide.
Good luck.
|
|
|
v​

You don't flash fastboot images via CWM. If you have CWM installed & you're booted in to bootloader (fastboot) mode use the volume keys to reboot into recovery

Jubakuba said:
If you're using fastboot...that means you're not in custom recovery.
Navigate to recovery in that menu.
Or use fastboot boot ______________.img to boot into a custom recovery if you have one downloaded and in your platform tools directory.
But yes, you COULD do that.
But I wouldn't yet.
You'll lose all of your data/apps/etc.
Click to expand...
Click to collapse
I tried pushing a zip to the phone while using adb and a custom recovery. My terminal says it pushed the files to my SD card, however when I go to install the zip, no files appear. Even when I restart recovery there are still no zips found. Any ideas?
Thanks,

Maybe try...
adb push NameOfRom.zip /sdcard/NameOfRom.zip
or
adb push NameOfRom.zip /data/media/NameOfRom.zip

3rdstring said:
Maybe try...
adb push NameOfRom.zip /sdcard/NameOfRom.zip
or
adb push NameOfRom.zip /data/media/NameOfRom.zip
Click to expand...
Click to collapse
Its still giving me a failed message, error flashing zip