Hello one and all, I seem to be having some trouble getting a custom rom.
Using "Hasoon2000's HTC One X All-In-One Kit",
I have completed the root process of my phone, and flashed a new boot.img file from my computer with the CMD that flashed a new rom.
Upon trying to reboot, I get stuck in a loop of the phone turning off, and the HTC logo again and again and I can't access my recovery from the toolkit, as it keeps telling me the device is not found.
I'm stuck on the fastboot/bootloader menu, but what I need right now is to open the recovery (or TWRP recovery menu which IS flashed and worked prior to this incident).
I have tried this on a windows 8 OS, then on a windows 7 OS re installing my drivers several times, but to no avail.
So my main questions are:
How can I get the device to be recognized?
How would I boot the stupid ROM?
Should I just revert back to custom?
and finally:
Why do chemists enjoy working with ammonia?
(Because it's pretty basic stuff.)
Thanks in advance for the help.
Hold the power button and the volume - together as long as needed to see the bootloader. Do not let go before, not even when the phone reboots.
From there you can navigate to the recovery.
Download the android sdk bundle, unpack it and navigate to the platform tools folder. Open a command window in there
Then uninstall HTC sync manager if you still have it but leave the drivers
Put the phone in the bootloader and then type in the command window on the pc
Fastboot devices
If a serial pops up you are good to go !
Related
Hi, My DHD volume buttons no longer work and I've been reticent to send it off to get fixed as I can do with out the volume controls as opposed to being without a phone for 2-3 weeks.
However I used Rom manager to boot into CWR and was in the process of upgrading to revolution 5.2.4 from 5.1.8.
I ran the full wipe script then my fat fingers rebooted the phone rather than flashing the rom.
I now cant get back into CWR to flash the new rom. It just sits at the boot logo, obviously as all other partitions have been wiped.
Is there any other way I can force the phone to boot into CWR, perhaps using the sdk tools or similar?
I've tried adb devices, but it doesnt show up. Is there an external way to force the phone into flashing a new ROM or booting into CWRM ?
Thanks
Ron
I would like to help, first lets try using adb, command would be adb reboot recovery
Hi, thanks for the help.
As mentioned in OP. I have powered the phone on and have have already attempted this, but the device is not recognised by adb.
tools>adb reboot recovery
error: device not found
My question is how to get the device to be recognised if its simply sitting at the boot image?
R
Sorry I over looked that, it seems to me if adb (which is an sdk tool) won't recognize the device as being attached, i don't see any other sdk tool doing any different, also as far as I know there is no alternate method to scrolling through the boot loader that would allow you to choose recovery and flash a zip other then the volume keys , so it seems the solution is, to send the phone off, get the volume keys fixed, and then you will be able to get back into the boot loader, and select recovery, and reflash a rom. Other than that, I don't see any other method, if adb doesn't recognize the device as being plugged in, I am assuming you attempted to boot into boot loader as well, and see if adb recognized the device?
EDIT: stupid question you can't boot into boot loader without volume key
I just want to confirm that I need do nothing else other than configure the sdk and ENV path etc, such that if i can run adb and get the deafult output, eg switches fr command line options etc...
then all I should need to do is turn phone on and connect via usb to computer. I dont need to edit any config files for specific phone versions or whatnot?
If not then Ill try and bring it to a vodaphone shop and see if they can fix the volume button...
R
if you get the volume buttons fixed, we don't even need adb, I was simply thinking adb since your volume buttons are broken. Once the volume buttons are fixed, you simply need to boot into boot loader, then to recovery, mount USB mass storage, put a new rom on there, wipe the phone, flash the rom and your good
Good luck mate, do some mediation meanwhile and learn to keep patience, so when your phone is back, you can treat it gently while in the recovery.
You will be alright once your vol keys are fixed.
All right, guys, if you come through for me I'm going to buy you all lunch and give you pony rides.
I've got a Virgin Mobile (USA) Wildfire S CDMA in my hands. I've been trying to get it back to factory settings, so of course I tried to run an RUU (RUU_Marvel_Virgin_Mobile_1.37.351.1_Radio_47.10.35.3029H_7.46.35.08_release_188032_signed.exe located at AndroidFiles, if anyone's interested). I put the device into Fastboot USB mode, launched the RUU EXE, and sat back and watched as it updated the radio. Then the phone vibrated thrice and stayed black, while the RUU timed out and told me there was an error.
I've since discovered that the device is now in Qualcomm Recovery Mode, and the accepted way of fixing this is to put a PG76IMG.zip file on the SD card and press up a couple of times after your device powers on with five vibrations. The issue I'm having is that I can only get the device to vibrate three times when I hold VolDown and Power, regardless of how many different PG76IMG.zip files I try.
Where do I go from here? Any help at all would be appreciated. Think of the pony rides!
What file you downloaded? Try with this.
I don't know what Qualcomm Recovery Mode is, but you can try to install with fastboot.
Method:
First need to download the .zip Fastboot (win or ubuntu) but if you use ubuntu, need to dowload first SDK platform tools and then download the .zip, introducing it in the folder "Platform-tools". In windows only need to download.
Then, open terminal and browse to the folder. When you are in, write "fastboot flash system SYSTEMFILE.IMG". It flashes, final only need to reboot (fastboot reboot).
If you need to install a custom recovery the command is: fastboot flash recovery recoveryfile.img
You can download the file here.
Tell me what happened with the issue
LaMüSe said:
What file you downloaded? Try with this.
I don't know what Qualcomm Recovery Mode is, but you can try to install with fastboot.
Method:
First need to download the .zip Fastboot (win or ubuntu) but if you use ubuntu, need to dowload first SDK platform tools and then download the .zip, introducing it in the folder "Platform-tools". In windows only need to download.
Then, open terminal and browse to the folder. When you are in, write "fastboot flash system SYSTEMFILE.IMG". It flashes, final only need to reboot (fastboot reboot).
If you need to install a custom recovery the command is: fastboot flash recovery recoveryfile.img
You can download the file here.
Tell me what happened with the issue
Click to expand...
Click to collapse
That looks very promising, but I can't get the phone into Fastboot. Literally the only thing it's capable of doing right now is vibrating three times after I hold the power button, and then it won't do anything else until I pull the battery. This is apparently the Qualcomm Diagnostic Mode.
Panic bump? I kinda hoped this wouldn't just disappear into the depths of the forums...
Was running MMuzzy, tried Omni, decided to go back (no statement on Omni, just didn't want to deal with new, setting up and such) and the only backup I have is in TWRP... but I switched to CM to install Omni... and like an over eager cleaner, I deleted the install files for everything last time I was in Omni... then I went into recovery, wiped and realized I need TWRP to restore my backup (no files found in CW)
All I can do is boot into recovery and I cannot figure out how to set up windows so I can put an install file on there to run so I can get back to TWRP and clean this mess up. I tried installing the Samsung drivers on an XP workstation but the computer doesn't find drivers when plugging in the phone... I pointed to the samsung/drivers folder in programs but no luck.
Bail a ding bat out?
Bump
Can anybody explain how to get this thing viewable in windows? (With no phone control)
Please.... and thank you in advance!!!
I am ready to pay someone for help on this
Help me get this back to life... name a reasonable price
Use efrant's guide in the stickys to flash the factory image and use his link for Windows drivers. It always works and his fastboot tutorial has saved my device more than once.
Link:
http://forum.xda-developers.com/showthread.php?t=1626895
For my instructions, download these, you will end up using them:
1. Android drivers for windows, I would prefer Universal Naked Driver (UND):
http://forum.xda-developers.com/showthread.php?t=1766220
2. Android debugging tools (ADB), I would prefer minimal ADB:
http://forum.xda-developers.com/showthread.php?p=42407269
3. TWRP recovery image: http://www.teamw.in/project/twrp2/90 download the last version you remembered using or just use the latest openrecovery-twrp-2.6.3.2-maguro.img
Install 1 & 2 in order. You may need to have the phone boot to recovery to install #1. Installing the drivers in Windows XP/7 will be easier, Windows 8/8.1 requires an advanced step to disable unknown driver enforcement.
For #2, if you have ADB/Fastboot already, skip this step. If you don't, then you may need to install it while in recovery too. Install it to a folder you are familiar with, I would choose C:\ and make an Android folder.
After you have both installed, boot your phone to bootloader mode. When it is shut off, hold VOL + and - at the same time then press the power button for all 3 simultaneously. It will boot into bootloader mode, where you see the android and your Galaxy Nexus revision/software details.
Move the TWRP recovery img file to the location of your ADB folder. For my example, I will assume #2 (adb tools) are installed in Local Disk (C and the android folder, so C:\Android
From here you would use the command prompt/terminal start > run > cmd or start, find program Command Prompt.
In the terminal type cd\foldertoTWRPimgfile\ or in my example, cd\android\
Next, type fastboot flash recovery openrecovery-twrp-2.6.3.2-maguro.img
my example would look like:
C:\android\ fastboot flash recovery openrecovery-twrp-2.6.3.2-maguro.img
it will show a progress indicator, then OK'd when it is finished.
You can then manually boot to recovery in fastboot, hit a volume button on your phone a few times until you see RECOVERY, then hit the power button to load it. You should now be in TWRP and be able to restore your backup, hope it is still there. Since it is likely that you were last using an older version of TWRP for MMuzzy, you might notice differences if you flash a newer version of TWRP.
kaijura said:
For my instructions, download these, you will end up using them:
1. Android drivers for windows, I would prefer Universal Naked Driver (UND):
http://forum.xda-developers.com/showthread.php?t=1766220
2. Android debugging tools (ADB), I would prefer minimal ADB:
http://forum.xda-developers.com/showthread.php?p=42407269
3. TWRP recovery image: http://www.teamw.in/project/twrp2/90 download the last version you remembered using or just use the latest openrecovery-twrp-2.6.3.2-maguro.img
Install 1 & 2 in order. You may need to have the phone boot to recovery to install #1. Installing the drivers in Windows XP/7 will be easier, Windows 8/8.1 requires an advanced step to disable unknown driver enforcement.
For #2, if you have ADB/Fastboot already, skip this step. If you don't, then you may need to install it while in recovery too. Install it to a folder you are familiar with, I would choose C:\ and make an Android folder.
After you have both installed, boot your phone to bootloader mode. When it is shut off, hold VOL + and - at the same time then press the power button for all 3 simultaneously. It will boot into bootloader mode, where you see the android and your Galaxy Nexus revision/software details.
Move the TWRP recovery img file to the location of your ADB folder. For my example, I will assume #2 (adb tools) are installed in Local Disk (C and the android folder, so C:\Android
From here you would use the command prompt/terminal start > run > cmd or start, find program Command Prompt.
In the terminal type cd\foldertoTWRPimgfile\ or in my example, cd\android\
Next, type fastboot flash recovery openrecovery-twrp-2.6.3.2-maguro.img
my example would look like:
C:\android\ fastboot flash recovery openrecovery-twrp-2.6.3.2-maguro.img
it will show a progress indicator, then OK'd when it is finished.
You can then manually boot to recovery in fastboot, hit a volume button on your phone a few times until you see RECOVERY, then hit the power button to load it. You should now be in TWRP and be able to restore your backup, hope it is still there. Since it is likely that you were last using an older version of TWRP for MMuzzy, you might notice differences if you flash a newer version of TWRP.
Click to expand...
Click to collapse
Wow... I really do not know where to begin to thank you... that REALLY saved my bacon as it is my work phone as well as personal cell too. Please send me a PM with a donation addy and an amount if you have one or I would be happy to send you a Christmas present...
Merry CHRISTmas everyone!!!!
Hi there,
I've been a bit of a [email protected] and fudged my Huawei P6. I Was on South African Vodacom Stock Jelly Bean Rom, read this forum and got so excited about the world out there that i thought, why don't i try flashing a rom, i've only bricked a sgs2 and lg-g2 before... I should know what to do by now (never done a day's computer course in my life!)!
So flashed kitkat beta and then tried to flash Kit Kat... I have left the phone for about a week in the hopes I'd come back to it & it would miraculously work as I've read a lot of the forum posts on here and have a gut feeling I'm screwed so hoping one of you Huawei P6 XDA Guru's can Help. From what I remember I did this...
1) Rooted the phone with SRS Root or Root Genius
2) After a few attemps managed to install official kitkat beta from dload/update.app from external SD Card so I could then install official Chinese KiTKAT rom or HYDRO Rom.
3) Played with the kitkat beta for a while all working (bar the beta crashes etc) ( I think at that point I intalled CWMOD or TWRP)
4) It was very late, I should have gone to bed, I'd had a few beers, but no I carried on & was planning to install Hydrorom & (Mis)understood got mixed up with official chinese kit kat rom installation
5) Booted into recovery & flashed official chinense kitkat rom with GAAPS ticked to flash as well (maybe that will tell you guys if I was using CWM or TWRP!)
5.0117...c) If my memory serves me right I didn't (4am idiot/tired/few beers/rushing etc) wipe dalvic or any of that... just flashed from external sd card ZIP streight over kitkat beta (aaaarrgh!)
6) Phone is now stuck in bootloop with Huawei Ascend words first, then loading a Huawei flower logo. Goes no further, just stays on until battery flat...
7) Left phone plugged into power with screen on for a day hoping it was just taking a while to flash rom... & nothing happened
8) Tried the following but hope I'm doing them all wrong and you GURU's will have a giggle at my comlete lack of skills:
a) reboot phone - no luckb) hold down power & +vol & -vol -... no luck just flower logo againc) every combination of power and two volume buttons - no luck just flower logod) putting folder dload/update.app on external sd card and using b)method to flash update - no luck just flower logoe) putting stock recovery.img on root of external sd card and doing b) - no luck just flower logof) putting all of extracted TWRP download " TWRP_Installer_20140414 on root folder of external sd card - no luckg) spending 4 hours finding a "how to remove the battery from huawei P6" link and watched a russian guy remove battery on you tube. Did that as read that can reset boot loader/recovery.... no luckh) downloaded various versions of Android SDK Tools. Phone shows up as a "please insert sd card" in windows file manager and appears "offline" when trying to access it from command prompt ADB etc
checked that HiSuite was stopped in Task Manager etc, reinstalled drivers etc. One problem I'm hoping you'll all say is 100% to blame for SDK Tools not working is I'm on latest update of Windows 8.1 64bit...
Edit: Read other forum... I see the red led when turning phone on as well...
Edit: Just installed propper android sdk tools not small made up file and now phone changed from showing "offline" to "unauthorised" in adb...
So, please help.
Fixed it
Ok managed to fix this and hope it will help others. Was up till 2am last night after deciding to give it another go after getting no replies! The main problem here must have been that as device was seen as unrecognized on PC and I couldn't get past boot screen so there was no way to allow debugging/authorize I.e. No pop up on phone as stuck in Hauwei flower screen.
Previously I Couldn't get fastboot or adb on PC to do anything, just kept saying phone was offline or unauthorized.
Rebooted phone from boot loop screen of huawei flower on screen holding power and - vol button for a long time until only boots to huawei ascend words logo (phone still plugged into PC), let go of both. PC makes sound to show there is USB device, now it doesn't boot the huawei flower screen just stays on the Hauwei ascend screen (I think normally this would open recovery etc), so maybe it is in recovery just not showing on screen... I don't know?!
Adb devices says no device however... And obviously no adb commands work at all...
However, fastboot commands for some reason work even though devices still shows nothing... so I tried various commands but what worked for me was typing the following in command promt on PC:
Fastboot flash boot boot.img (Stock)
Where all the img,zip,app files I was flashing were were in the platform-tools folder where adb and fastboot are.
Then
Fastboot flash recovery recovery.img. (Stock)
Then I think what did it, I was obviously on a broken twrp recovery... Was I flashed
Fastboot flash recovery twrp_2_6_3_3_recovery.img
To my amazement twrp touch recovery loaded and I could then go about wiping dalvik etc and reflashing all the correct files.
So I'm now finally running HYDROROM_V7
All the files I used are on the hydro rom page here so thanks to them for that! :
http://forum.xda-developers.com/showthread.php?t=2630208
Hope this works for all of you stuck in bootloop etc as I really thought my phone was stuffed!
Ciao
pommiesa said:
Ok managed to fix this and hope it will help others. Was up till 2am last night after deciding to give it another go after getting no replies! The main problem here must have been that as device was seen as unrecognized on PC and I couldn't get past boot screen so there was no way to allow debugging/authorize I.e. No pop up on phone as stuck in Hauwei flower screen.
Previously I Couldn't get fastboot or adb on PC to do anything, just kept saying phone was offline or unauthorized.
Rebooted phone from boot loop screen of huawei flower on screen holding power and - vol button for a long time until only boots to huawei ascend words logo (phone still plugged into PC), let go of both. PC makes sound to show there is USB device, now it doesn't boot the huawei flower screen just stays on the Hauwei ascend screen (I think normally this would open recovery etc), so maybe it is in recovery just not showing on screen... I don't know?!
Adb devices says no device however... And obviously no adb commands work at all...
However, fastboot commands for some reason work even though devices still shows nothing... so I tried various commands but what worked for me was typing the following in command promt on PC:
Fastboot flash boot boot.img (Stock)
Where all the img,zip,app files I was flashing were were in the platform-tools folder where adb and fastboot are.
Then
Fastboot flash recovery recovery.img. (Stock)
Then I think what did it, I was obviously on a broken twrp recovery... Was I flashed
Fastboot flash recovery twrp_2_6_3_3_recovery.img
To my amazement twrp touch recovery loaded and I could then go about wiping dalvik etc and reflashing all the correct files.
So I'm now finally running HYDROROM_V7
All the files I used are on the hydro rom page here so thanks to them for that! :
http://forum.xda-developers.com/showthread.php?t=2630208
Hope this works for all of you stuck in bootloop etc as I really thought my phone was stuffed!
Ciao
Click to expand...
Click to collapse
Hey very good that you managed to fix your problem, when I first read your question I didn't had any ideas on how to fix it. But you had a bootloop I think and when you press power and vol- until it reboots you come in the bootloader, on our device it only shows the bootlogo so its seems that it is stuck but actually you are in the boot loader and can use fastboot commands. So glad you fixed your problem.
Gesendet von meinem P6-U06
So I have hit a wall.
I have an old HTC One M8 - I want to root it and play with it.
I have Mint 19 installed on my old Thinkpad, I want to start learning Python and GO and doing things with Android.
So I successfully unlocked the bootloader last night I can't even remember how but I followed instructions and did it.
Now I am trying to root using TWRP and running into issues.
I have platform-tools on my desktop (I found it somewhere via these XDA Forums)
I have (I believe) a good TWRP HTC One M8 recovery image in that folder, named recovery.img
i got that through a link on here somewhere too.
I can successfully boot to the white text menu by restarting and holding power and volume down, and it says Fastboot USB
From there on my PC I open a command prompt in the platform-tools folder and put in the recommended command line:
fastboot flash recovery recovery.img (I have renamed it recovery.img)
It says it successfully flashed, but after this I cannot figure it out, it keeps booting to regular HTC start up screen.
I have SuperSU on the phone ready go to - I understand this would be the next step.
I also have the TWRP program on the phone but it doesn't do anything, the only thing I can do with it is download the iso for One M8 again.
Any ideas?
I am missing something here, I cannot boot into TWRP after its flashed.
Thanks