I try to adb reboot fastboot but not effect
someone know how can I get fastboot mode?
uprom via fastboot is more convinient than recovery (especial when up some tiny rom like boot.img, recovery.img itself)
Related
Hi
Messed up my desire a while back. It won't boot. When I turn it on I get this screen
When I plug it in to PC then unplug it I get this screen
Can't flash any RUU. Can't access recovery. Just nothing. Anyone any ideas what I can do?
Sent from my GalaxyS2 with CM9
Hm, no fastboot. Does it recognize it if you connect the phone to your pc? Your PC may see a USB serial console that accepts commands.
Google for "HbootAnalysis" to get a list of commands.
The gotofastboot commands looks worth a shot. Once in fastboot you should be able to flash anything you want.
The phone reacts, and the computer knows there is something there. Just not a phone...
Sent from my GalaxyS2 with CM9
So you cannot even access fastboot?
No
Sent from my GalaxyS2 with CM9
This is probably extremely unhelpful so I apologise but what did you do/what happened to the Desire to make it (what seems to be) stuck in a loop?
this is a partition/radio brick
it usually happens when you try and RUU a device when its using the new alpharev hboots that do not have the right sizes (hes using the sense hboot which doesnt use stock sizes)
so basically it kills the partitions. this is because alpharev put that "annoying" hboot protection on to stop RUU's from overwriting it. i love the alpharev team but that really isnt needed
I dont think its possible to fix this without being able to get to fastboot as we need to get the hboot flashed with stock sizes
Stuck on the way RRU
I encountered the same problem today:
My solution:
You need Android-sdk with fastboot command
"fastboot devices" work for me
I got my last backup ClockworkMod on my sdcard
/clockworkdmod/backup/2012-01-16-18.04.51/
width these files:
boot.img
data.yaffs2.img
system.yaffs2.img
recovery.img
...
I flashed these files
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.yaffs2.img
fastboot flash userdata data.yaffs2.img
Then I tried the boot
fastboot oem boot
Iit worked !
After the reboot I stood on this page RUU (hboot)
To erase the RRU Flag on fastboot:
fastboot oem resetRUUflag
And now all is working on my cyanogen 7 NB
Try for Yourself
fxjumper
fxjumper said:
I encountered the same problem today:
My solution:
You need Android-sdk with fastboot command
"fastboot devices" work for me
I got my last backup ClockworkMod on my sdcard
/clockworkdmod/backup/2012-01-16-18.04.51/
width these files:
boot.img
data.yaffs2.img
system.yaffs2.img
recovery.img
...
I flashed these files
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.yaffs2.img
fastboot flash userdata data.yaffs2.img
Then I tried the boot
fastboot oem boot
Iit worked !
After the reboot I stood on this page RUU (hboot)
To erase the RRU Flag on fastboot:
fastboot oem resetRUUflag
And now all is working on my cyanogen 7 NB
Try for Yourself
fxjumper
Click to expand...
Click to collapse
indeed this should work
he said he cant boot to fastboot though, are you saying you can use fastboot in the RUU screen?
yes i can enter fastboot command
but after these stuff, i loosed my name/serial_number in adb but not in fastboot
my new adb username/serial_number is 1234567890ABCDEF
how to flash recovery.img and boot.img throught adb procedure ?
i want to downgrade my p6 from B708 to B5xx
but i dont now how to flash recovery.img and boot.img throught adb procedure
Please help ?:crying:
Flash recovery
Hi.connect phone to pc with USB debugging on.settings>developer options>usb debugging
no use this commands:
adb reboot bootloader> phone restarts in fastboot mode.
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot.
problem !!!
Hooshang said:
Hi.connect phone to pc with USB debugging on.settings>developer options>usb debugging
no use this commands:
adb reboot bootloader> phone restarts in fastboot mode.
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot.
Click to expand...
Click to collapse
I do that and now my P6 is stuck on huawei logo
Please Help !!!
fastboot reboot
Sent from my HUAWEI P6-U06 using XDA app
help me , my phone no connect fastbot
If you are NOT able to boot into 12S, and ONLY fastboot mode is available. This CM12S recovery file will help. Just unzip and run following command in fastboot mode.
fastboot -i 0x1ebf flash recovery recovery.img
Thanks for this, mate.
Hello whenever i try to use the fastboot boot twrp.img command on adb the img wont load it gets stuck on the fastboot logo.
Try
fastboot flash recovery twrp.img
elwholo said:
Hello whenever i try to use the fastboot boot twrp.img command on adb the img wont load it gets stuck on the fastboot logo.
Click to expand...
Click to collapse
Rename ur boot image file to twrp.img
And then in adb type
1. fastboot devices (see if you are connected or not... If connected type 2nd command)
2. fastboot flash recovery twrp.img
After that by using power up button navigate to RECOVERY MOD and press power key
DONE
U will be running twrp recovery
flash magisk via recovery to maintain root
Enjoy
Could someone please help me with the proper commands to flash these 3 files in Fastboot mode with ADB
ADB FASTBOOT commands to flash
boot.img
recovery.img
recovery2.img
https://openkirin.net/user_guide/how-to-flash-extracted-partition-images/
MadGoogler78 said:
Could someone please help me with the proper commands to flash these 3 files in Fastboot mode with ADB
ADB FASTBOOT commands to flash
boot.img
recovery.img
recovery2.img
Click to expand...
Click to collapse
This must be nougat.
Let's say the images are in same folder you are running the cmd window from. If they are not then you need to adjust the command to include the full path to them.
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash recovery2 recovery2.img
Now of you are getting error messages , like , partition length over, or , partition does not exist, then you must not have nougat rom on device.
In that case you will need different commands, and different files. Lol