i cant enter recovery mode with my HTC branded G2. generally,when you press power+home ,you should enter recovery mode,but it wont work on my phone,no matter how long you holding these keys. you must power the phone and enter the fastboot mode and then flash recovery.img once more,at the end G2 reboots to recovery mode automatically.i‘v searched for a long time ,got nothing can help.anyone here got the same problem?
here is some information:
recovery-RA-sapphire-v1.7.0H.img
HBOOT- 1.33.0009(SAPP10000)
RADIO-3.22.20.17
THX in advance
Do you have ADB on your computer? If so try using adb to get into recovery as such.
adb remount
adb reboot recovery
This method has worked for me when my phone seemed bricked and was hanging on a bad rom flash.
Nanan00 said:
Do you have ADB on your computer? If so try using adb to get into recovery as such.
adb remount
adb reboot recovery
This method has worked for me when my phone seemed bricked and was hanging on a bad rom flash.
Click to expand...
Click to collapse
quick question, im guessing you have to have already flashed the recovery.img to get into recovery mode? because when i tried to flash the recovery.img and cmd kept saying "remote: image update failed" or something like that.
now i believe my device is bricked, wont turn on , or show LED light,.
Related
i was updating my U8150 with a custom ROM (Ideos HD) and somehow i did something wrong, i did the wipe and install the custom ROM and the Kernel update at the same time. The phone was taking long time to install and when splash logo stops for a few seconds it restart and the phone continues on that more, restarting one and one more time.. then i try to see if i can enter to the Recovery mode and looks like i missed the clockworkmod mode, i cannot enter to that, then y try to see if I can enter to fastboot to reinstall the recovery image (clockworkmod) mode and i see an error message saying " Firmware Update Step 1/2 Unpacking" then after the progress bar it says "Update Failed"
i check the cmd and fastboot mode is not allowed, even the device manager is not on that mode, then doing the recovery i can enter for a few seconds to adb but because the phone is restarting i need to do a few commands on this mode....
My question is: if somehow i can flash the recovery mode with adb?? i have see that some guys do with a terminal emulator but with the phone working and the normal way I hace seeing is on fastboot mode but i cannot enter to that mode...
i just wanted to see if somehow i can install with adb the recovery or maybe entering to the adb with shell and install it from there…
any crazy idea I will try it…
Regards
i just download the original firmware and when entering fastbootmode it automatically detects the .APP File, lets see what happens...
i take the file from this >>> http://forum.xda-developers.com/show....php?t=1011527
i hope at least i can get from stock, i will see if need to do root again...
All im getting is the TWRP menu, even after holding the vol down & power. Wont get to the rck screen. Any ideas?
spooky71 said:
All im getting is the TWRP menu, even after holding the vol down & power. Wont get to the rck screen. Any ideas?
Click to expand...
Click to collapse
What happened?
This is a common result if you flash a non-4.2 twrp on a 4.2 bootloader, which will cause a fastboot flash brick.
You will need adb drivers installed on pc, then while in recovery connect your tab to pc, open a command prompt and cd to you android-sdk/platform-tools folder and type
Code:
adb devices
if adb is setup correctly you will get a response with your devices s/n. If this is ok then type
Code:
adb reboot-bootloader
which will reboot your tab to the bootloader screen.
The problem is that whenever I boot up, all i get is the TWRP menu, not letting the pc see the pad. On device manager I get Transformer under other devices. Ive downloaded the drivers, but its not installing them. When I run adb reboot-bootloader, I get device not found.
Have a look here, scroll down and follow on from the where you see the device manager image - this worked for me to get adb working from recovery.
So did this happen after you flashed twrp 2.4.4.0-4.2? or did you flash another twrp or cwm?
Heading out now for a few hours but will be back later
pjc21 said:
Have a look here, scroll down and follow on from the where you see the device manager image - this worked for me to get adb working from recovery.
So did this happen after you flashed twrp 2.4.4.0-4.2? or did you flash another twrp or cwm?
Heading out now for a few hours but will be back later
Click to expand...
Click to collapse
Still nothing. Whats killing me is that it cant detect different sd cards.
Trying some stuff and need to get to stock recovery. Can normally get there from the extended reboot menu or ADB, but hosed something so adb doesn't work. I know it's there, used it for factory reset a dozen times.
Tipe in console:
Su
Reboot recovery
getochkn said:
Trying some stuff and need to get to stock recovery. Can normally get there from the extended reboot menu or ADB, but hosed something so adb doesn't work. I know it's there, used it for factory reset a dozen times.
Click to expand...
Click to collapse
Gabboxxx said:
Tipe in console:
Su
Reboot recovery
Click to expand...
Click to collapse
Doesn't matter, I just reflashed, but I can't run SU, reboot recovery when ADB doesn't work as I clearly stated.
And if u reflash the ftf?
getochkn said:
Trying some stuff and need to get to stock recovery. Can normally get there from the extended reboot menu or ADB, but hosed something so adb doesn't work. I know it's there, used it for factory reset a dozen times.
Click to expand...
Click to collapse
Not via ADB commands ? Try a different cable ? Maybe you forgot to enable USB debugging? Enable unknown sources might help too
I had no problems booting via ADB
adb reboot recovery
I suppose try using a different PC and reflash a different ftf file. That might help as it will complete rewrite the recovery again in case you have screwed it
Check this post where I have successfully booted into recovery via ADB :
http://forum.xda-developers.com/showthread.php?t=2480590
the whole of this was my phone was softbricked. I wanted to get into recovery so I could use ADB to try to fix it. When it's softbricked, ADB won't start up, therefore I could use ADB.
Trust me, I know how to use ADB, I just wanted to know if there was a key combination to get our phones into recovery mode with ADB because ADB wouldn't work because my phone was softbricked. It had nothing to do with me not knowing how to use ADB or how to set it up, it had to do with my phone would brick it self before ADB started, so therefore I couldn't send any ADB commands.
getochkn said:
the whole of this was my phone was softbricked. I wanted to get into recovery so I could use ADB to try to fix it. When it's softbricked, ADB won't start up, therefore I could use ADB.
Trust me, I know how to use ADB, I just wanted to know if there was a key combination to get our phones into recovery mode with ADB because ADB wouldn't work because my phone was softbricked. It had nothing to do with me not knowing how to use ADB or how to set it up, it had to do with my phone would brick it self before ADB started, so therefore I couldn't send any ADB commands.
Click to expand...
Click to collapse
I am uploading drivers on a post. Will quote you to it. Install them. I hope that helps!
here you go
http://forum.xda-developers.com/showthread.php?p=46681107#post46681107
Ok, let me try to explain this.
It's not drivers.
It's not ADB.
It's not my PC.
I softbricked my phone trying something. I didn't want to wipe it, so I wanted to try to get into recovery, where a limited ADB works.
I couldn't boot into recovery from ADB because it was softbricked.
I just wanted to know if there was key to hold down on boot or something to get into the default recovery mode.
I don't need drivers, I don't help getting ADB going, it works fine on my PC. The point was the phone was softbricked, in a boot loop, ADB wouldn't respond, wanted a key command to get into recovery.
I apprecaite the help but people aren't getting what I was asking.
Is there a key command to press at the bootup to get into the stock recovery on this phone? All my other phones, I know the command, but this one I've tried all the combos and no recovery.
Please, no more help on ADB, I know how to use ADB just fine.
Just is there a keypress to do this?
Hi guys,
So after flashing sultans new 3.4 kernel rom, i got myself into a random boot loop. The only problem is that i cannot get into the recovery to fix it, since my VOLUME DOWN button isnt working, and i cant go to adb because it says unauthorized. Is there any way to solve this problem ? Please, i Really need this phone to work
Thanks
fierah said:
Hi guys,
So after flashing sultans new 3.4 kernel rom, i got myself into a random boot loop. The only problem is that i cannot get into the recovery to fix it, since my VOLUME DOWN button isnt working, and i cant go to adb because it says unauthorized. Is there any way to solve this problem ? Please, i Really need this phone to work
Thanks
Click to expand...
Click to collapse
can you boot to the bootloader?
are you on S-ON or on S-OFF?
rzr86 said:
can you boot to the bootloader?
are you on S-ON or on S-OFF?
Click to expand...
Click to collapse
Hi, No I cant boot into the boot loader using VOLUME DOWN + POWER BUTTON, and I am S-OFF. I was trying to use adb since my volume down button doesnt work, so I can boot into recovery. And Im stuck in a bootloop.
fierah said:
Hi, No I cant boot into the boot loader using VOLUME DOWN + POWER BUTTON, and I am S-OFF. I was trying to use adb since my volume down button doesnt work, so I can boot into recovery. And Im stuck in a bootloop.
Click to expand...
Click to collapse
try this command and see if it works adb reboot bootloader and try to open command window as administrator after this go to recovery
Mile_zdr said:
try this command and see if it works adb reboot bootloader and try to open command window as administrator after this go to recovery
Click to expand...
Click to collapse
it doesnt work, it says the devise is unauthorized. Andriod 4.4.2 has a safety feature where you have to first confirm whether you want to use adb to use adb, and i cannot do that because im stuck in a bootloop.
so when i type any adb command it says devise unauthorized
im also waiting this solution.
stuck in logo, and can't confirm popup cornfirmation
Recently I installed a custom ROM that is meant to be installed on a Huawei P8, for my Huawei P8 lite as my new OS because I accidentally deleted my whole OS. When I plug my mobile phone to a power source it shows the Huawei logo, I cannot get it into fastboot/rescue mode. If I try the dload folder to sd-card method it will not do anything. Does anyone know what to do.
Flash the stock firmware. I'm 100% sure your problem would be solved.
munimjaffer said:
Flash the stock firmware. I'm 100% sure your problem would be solved.
Click to expand...
Click to collapse
How do I flash it without fastboot?
pim8181 said:
How do I flash it without fastboot?
Click to expand...
Click to collapse
What do u see when u try to enter fastboot?
munimjaffer said:
What do u see when u try to enter fastboot?
Click to expand...
Click to collapse
When I try to enter fastboot I just see the Huawei logo
pim8181 said:
When I try to enter fastboot I just see the Huawei logo
Click to expand...
Click to collapse
Ok can u enter into recovery mode?
munimjaffer said:
Ok can u enter into recovery mode?
Click to expand...
Click to collapse
Nope....
Your phone got hardbricked with flashing a wrong rom,hardbrick is really hard to unbrick,
i already have one phone that got hardbricked due to flashing a wrong rom,since now i can't find the solution to unbrick it,
hope you find the solution soon..
pim8181 said:
Nope....
Click to expand...
Click to collapse
Is the device recognized by PC? If not, what is device manager labeling the device as?
If it connects to PC and is recognized you can.........
Use adb to clear cache and dalvik/ART cache, then see if the device will boot to recovery or fastboot, if not then power the device off and remove the battery then reinsert the battery(if it has a removable battery). Then leave the device off and connect it to PC then open a adb terminal and type:
adb reboot bootloader (press enter, sometimes the deamon has to start, if nothing happens then type adb reboot bootloader a second time, some devices can be booted from a powered off state with adb)
If that doesn't work try typing:
adb reboot fastboot (press enter).
If none of that works to boot fastboot then try turning the device on, when it gets to the logo, connect the device to PC, open a adb terminal and type:
adb devices (press enter, if it returns a serial number the device is recognized)
Then type:
adb reboot bootloader (press enter and it may boot to fastboot)
Or type:
adb reboot fastboot (press enter)
Or type:
reboot fastboot (press enter)
If none of that gets you to fastboot and you can't boot it manually with the buttons then you're bricked, its not hardbricked though because it boots to logo so that means bootloader is at least there even if it is corrupted and whether anything else is there or works or not.
Whatever you flashed must have had some differences in partitions that flashed over your partitions in places that weren't correct for your device, its more than just the software not being for your device, it is structured completely different than your device.
You've got to get to fastboot someway to flash the stock firmware, that's the only thing I see being able to correct your partitions and put the .imgs in the places they are meant to go.
There is also the possibility that you can download your stock firmware, then extract the kernel(Zimage, its sometimes bundled with/called boot.img or recovery.img, depending on device and android version), the boot.img, the recovery.img and the system.img and then do some research on your device model number and find out which partition(mmcblk0) each of those imgs go in(I could tell you how to use adb to find the partitions but that wouldn't help if flashing the wrong things has screwed up their placements). Then, if adb is working with the device you can use the dd command to manually push the boot.img to its mmcblk0, the recovery.img to its mmcblk0 and the system.img to its mmcblk0.
I would start with dd-ing the recovery, then seeing if it will boot to recovery, if the recovery is a custom recovery and you have a nandroid backup or a correct ROM zip, try restoring or flashing. If it doesn't then dd the boot.img to its mmcblk0 and see if it boots to recovery, if not, dd the system.img to its mmcblk0, you can repeat this process with each of the .imgs in your stock firmware. Maybe if you can push enough to the device it will restore some functionality that will allow you to get booted to a state will allow you to completely reflash the device.
If the confused you then I might have confused myself typing it, lol.