so I've been playing with the options long enough that I'm not satisfied with what's available, so I figured I'd try customizing a kernel myself. I think I have a pretty good idea about how to make that happen, but I've run into a problem on testing. I can't seem to boot using fastboot boot ______. Whether I'm using the twrp recovery boot, dd of mmcblk0p35, or the freshly split boot.img(ramdisk and kernel), fastboot responds with ok, but my phone sticks on the bootloader fastboot usb screen, requiring a hard reboot. Is the only option to use the any kernel zip? or am I just screwing something up?
Related
A quirk of the Advent Vega (also Tegra) that allows you to enter fastboot mode also applies on the 2X (Thanks Bumble-Bee for the tip!)
Basically, if you wipe the boot partition (e.g. 'dd if=/dev/zero of=/dev/block/mmcblk0p5') then reboot, the device drops to fastboot.
Handy testing feature for devs.
P
That sounds great!
Does fastboot boot work? Does fastboot flash work? Any other lockdowns there?
maxisma said:
That sounds great!
Does fastboot boot work? Does fastboot flash work? Any other lockdowns there?
Click to expand...
Click to collapse
Fastboot boot did, didn't try anything else yet!
P
Fastboot flash works, ish.
I could flash recovery, but not boot. What would be nice is a radio in .img format so I don't have to backup and restore the bastard thing when a new one is out.
Ahh this would be so awsome.. since i Smartflash can't detect my P990
(so i can't flash the latest basebands or revert them)
Gief Radio in .img format !
Would anyone Know how to get the radio as .img ?
Would this work on the T-Mobile LG G2X?
Good question.
I expect the boot partition is different, so don't blindly follow the command here.
Rusty! said:
Good question.
I expect the boot partition is different, so don't blindly follow the command here.
Click to expand...
Click to collapse
I did follow the command blindly with my P990, but no boot for me. Luckily there's an escape with the NVflash stock ROM.
It's fine on the P990, it's meant to 'not' boot, it's not broken at that stage, it's in fastboot. You can fastboot boot your way out of it.
Is this a safe option to try on my v10D? Fastboot decreases boot time by how much really?
That's not what fastboot means, to be honest, this isn't going to be for you
Hey All,
I was trying to install GingerStreak 2.4.4 from GingerStreak 2.4.3.
http://forum.xda-developers.com/show....php?t=1333010
According to the instructions, I flashed
amss.mbn - http://mirror2.streakdroid.com/amss.mbn
and
dsp1.mbn - http://mirror2.streakdroid.com/dsp1.mbn
(got both the files from the first link above)
Then when I tried to reboot into Bootloader (Power+Vol Up+Vol Down) but nothing happens apart from the Dell logo being displayed.
I try to boot normally, still stuck at the Dell logo. The phone never even reaches the boot animation.
I try to go boot into fastboot (power+camera key)mode, but the phone never even boots. The screen stays off, so do the LED lights.
I figured out that the files downloaded above were incomplete(due to slow speed Chrome showed incomplete files as download complete).
amss downloaded: 111KB. Actual Size: 15.41MB
DSP1 Downloaded: 250KB. Actual Size: 8.94MB
So, I flashed the wrong files.
Now, I guess, the phone is bricked big time.
I need big time to get into fastboot mode (to flash the correct files) or anyhow get my phone working.
Guys, need help. Please help me out and get this issue sorted out.
You should maybe consider the Streak forum...
Sorry, my bad. I just searched for my problem an found this thread. Poured out all my worried without bothering to check on the device name.
Thanks anyhow!
RESOLVED!
so I just got my moto x dev edition, unlocked the bootloader, and then screwed it up...
i tried flashing the recovery as described here, http://forum.xda-developers.com/showthread.php?t=2458451 but didn't realize/understand that fastboot and mfastboot were not interchangeable. it looked like it went ok, but I wasn't able to reboot into recovery. so, now on boot to recovery i get the little android on his back with a red triangle. i'm pretty sure that the stock recovery is gone, but cwm is not installed either. which brings me to my next little problem...
so i did some reading and got mfastboot installed and thought ok I just need to reflash cwm on phone again. problem is, now the phone won't stay in usb debug mode so that i can see it when fastbooted. that is, when i reboot the phone into fastboot by holding the power/vol down I can't see the phone when doing 'adb devices', and whem I let it boot up i see usb debug is switched off. when i switch it on, then i can see the phone from adb again, but when i try to 'reboot bootloader' it gives me a not allowed error.
at this point i'm just sick and afraid i bricked it. i am coming from a galaxy nexus and never had anything like this happen before. i truly appreciate any help here, at this point i feel like puking and dreading telling the wife i just blew 450.... :-/
ps i'm on mac 10.7 so if i need rsd it will be via a virtual machine....
herrdrchili said:
so I just got my moto x dev edition, unlocked the bootloader, and then screwed it up...
i tried flashing the recovery as described here, http://forum.xda-developers.com/showthread.php?t=2458451 but didn't realize/understand that fastboot and mfastboot were not interchangeable. it looked like it went ok, but I wasn't able to reboot into recovery. so, now on boot to recovery i get the little android on his back with a red triangle. i'm pretty sure that the stock recovery is gone, but cwm is not installed either. which brings me to my next little problem...
so i did some reading and got mfastboot installed and thought ok I just need to reflash cwm on phone again. problem is, now the phone won't stay in usb debug mode so that i can see it when fastbooted. that is, when i reboot the phone into fastboot by holding the power/vol down I can't see the phone when doing 'adb devices', and whem I let it boot up i see usb debug is switched off. when i switch it on, then i can see the phone from adb again, but when i try to 'reboot bootloader' it gives me a not allowed error.
at this point i'm just sick and afraid i bricked it. i am coming from a galaxy nexus and never had anything like this happen before. i truly appreciate any help here, at this point i feel like puking and dreading telling the wife i just blew 450.... :-/
ps i'm on mac 10.7 so if i need rsd it will be via a virtual machine....
Click to expand...
Click to collapse
so, if i understand you correctly, u've held down the volume down button and power button? becasue that's your fastboot. That's where you need to be to use RSD, and that's what i'd do.
ADB commands aren't used in fastboot mode. You should be able to see the device in fastboot mode with the command fastboot devices. Also, remember that the stock rom will try to restore the stock recovery when it is booted so if you flash recovery in fastboot mode then let the stock rom boot it will reflash the stock recovery which shows you the little droid and the red triangle.
You should still be okay though. Shut the phone off and boot into fastboot manually with power and volume down. Reflash the recovery. I know there are warnings about using mfastboot but I used standard fastboot before I saw those and didn't have an issue. From the fastboot screen after flashing the recovery, use volume down to get to highlight recovery and then press volume up to select, not power. Power will just do a standard reboot.
If you flashed twrp recovery then rebooting system will prompt you to install su. I think clockwork does the same thing. Letting the recovery install su will also prevent the stock recovery from getting restored and from there you should be good.
herrdrchili said:
so I just got my moto x dev edition, unlocked the bootloader, and then screwed it up...
i tried flashing the recovery as described here, http://forum.xda-developers.com/showthread.php?t=2458451 but didn't realize/understand that fastboot and mfastboot were not interchangeable. it looked like it went ok, but I wasn't able to reboot into recovery. so, now on boot to recovery i get the little android on his back with a red triangle. i'm pretty sure that the stock recovery is gone, but cwm is not installed either. which brings me to my next little problem...
so i did some reading and got mfastboot installed and thought ok I just need to reflash cwm on phone again. problem is, now the phone won't stay in usb debug mode so that i can see it when fastbooted. that is, when i reboot the phone into fastboot by holding the power/vol down I can't see the phone when doing 'adb devices', and whem I let it boot up i see usb debug is switched off. when i switch it on, then i can see the phone from adb again, but when i try to 'reboot bootloader' it gives me a not allowed error.
at this point i'm just sick and afraid i bricked it. i am coming from a galaxy nexus and never had anything like this happen before. i truly appreciate any help here, at this point i feel like puking and dreading telling the wife i just blew 450.... :-/
ps i'm on mac 10.7 so if i need rsd it will be via a virtual machine....
Click to expand...
Click to collapse
ok then - i guess rsd has potential?
xpsychox said:
so, if i understand you correctly, u've held down the volume down button and power button? becasue that's your fastboot. That's where you need to be to use RSD, and that's what i'd do.
Click to expand...
Click to collapse
i can reboot into fastboot, but adb can't see the phone. I'll start trying to setup rsd and and see if it can do any better. any good links you know to get up to speed on that would be appreciated. if you know how to simply reflash the recovery via rsd that would be helpful too - thanks in advance!
herrdrchili said:
i can reboot into fastboot, but adb can't see the phone. I'll start trying to setup rsd and and see if it can do any better. any good links you know to get up to speed on that would be appreciated. if you know how to simply reflash the recovery via rsd that would be helpful too - thanks in advance!
Click to expand...
Click to collapse
the sites that I know of are for the device I have, a non devliper edition... I don't know if it makes a difference, I don't wanna make anything worse.
thanks for the sanity check,,,
btdonovan said:
ADB commands aren't used in fastboot mode. You should be able to see the device in fastboot mode with the command fastboot devices. Also, remember that the stock rom will try to restore the stock recovery when it is booted so if you flash recovery in fastboot mode then let the stock rom boot it will reflash the stock recovery which shows you the little droid and the red triangle.
You should still be okay though. Shut the phone off and boot into fastboot manually with power and volume down. Reflash the recovery. I know there are warnings about using mfastboot but I used standard fastboot before I saw those and didn't have an issue. From the fastboot screen after flashing the recovery, use volume down to get to highlight recovery and then press volume up to select, not power. Power will just do a standard reboot.
If you flashed twrp recovery then rebooting system will prompt you to install su. I think clockwork does the same thing. Letting the recovery install su will also prevent the stock recovery from getting restored and from there you should be good.
Click to expand...
Click to collapse
THANKS! just needed another set of eyes - man i need to not try doing this after a long day again i really appreciate your help. i got it now!
herrdrchili said:
THANKS! just needed another set of eyes - man i need to not try doing this after a long day again i really appreciate your help. i got it now!
Click to expand...
Click to collapse
Glad I could help!
I've been playing with custom boot images for the P7 (I run Ubuntu in a VM on my machine). Unpacking, repacking is not a problem. But I've discovered that "fastboot boot myboot.img" doesn't work! The error message is "remote: command not allowed". I know I can flash my custom boot image that is "fastboot flash boot myboot.img" certainly works. I've only done this once as my phone fell over and I had to rebuild it. Time consuming as you know. Is this a special feature of Huawei phones designed to make life interesting? Is there a work around/solution?
Edit:
I've found much to my dismay that Huaweis implementation of the bootloader is highly constrained. Most of the normally available fastboot commands have been turned off. Very disapointing. No easy way to test if a custom boot image works without flashing. And then if it doesn't, one has to rebuild from scratch or re-install from a nand backup.
Hi,
I was on 5.0, running stock recovery and rooted. Today, installed TWRP for 5.0 on my device. I tried to flash the droid command center widget on my phone usng twrp, and it failed. I also hit the fix permissions option. After that the phone does not boot up, simply flashes the unlocked bootloader sign and shows the moto boot animation for a second or two before shutting down.
I can boot into recovery, and the computer detects the phone. But adb doesn't detect the device. I have the 1092 5.0 OTA on my computer and saved it on the phone in an attempt to flash it thru TWRP, but that failed with the message shown in the img attached. I also tried flashing stock 4.4.4, but that gave an error "Updating partition details" failed.
Can someone help me get back into my phone? :crying: ADB doesn't seem to be detecting my phone, else I'd have tried to install a rom via fastboot.
I have multi-tool v4.1 installed, would I be able to flash a rom (stock unrooted and full wipe is perfectly fine too) via that considering adb does not detect my phone, but the computer does?
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
oldcynic said:
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Click to expand...
Click to collapse
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
HAXTREME said:
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
Click to expand...
Click to collapse
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
oldcynic said:
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
Click to expand...
Click to collapse
Ah yes. For some reason, my fastboot file had gotten deleted from the folder and so the command didn't run. Everything went smooth once I noticed that. Had to downgrade to 4.4.4., but w/e. Thanks @oldcynic
I updated my oneplus and i got the TWRP decryption message, so i formatted it back to the stock format.
now all the phone does is boot into the bootloader but gets stuck on the boot screen of Blu Spark 3.1.1
my computer wont recognize it while its in the bootloader or while its stuck trying to boot in twrp
is there anything i can do or is my phone screwed at this point? i see a lot of threads that would answer parts of my issue but nothing that covers this as a whole. id rather ask for help now while there may be some hope.
nickhawkjones said:
my computer wont recognize it while its in the bootloader or while its stuck trying to boot in twrp
Click to expand...
Click to collapse
So no response to fastboot commands, while in bootloader-fastboot mode?
Are you sure you installed the right drivers for your pc? If all else fails, you can do this.
This is how I fixed my phone when i was stuck at a black screen. You can also try a different usb cord or port. Check device manager and see if it recognizes it when its plugged in. hope this helps!
https://www.youtube.com/watch?v=BvfA5WrVDQM
can you boot into fastboot? if your phone can boot to fastboot mode..just flash stock recovery image..then flash rom via adb shell (better flash the stock rom). if it works you can reinstall the custom recovery image or something. dont forget to erase everything via stock recovery..