Database Develop

Boot loop fix

Greetings!
I'm not sure if anyone will need this but I thought I'd write it up just in case.
I'm also not sure what I did but my phone was stuck in a boot loop. I tried reinstalling the 2.2 update but nothing.
I also tried resetting the phone here.
Then I reinstalled the 2.2 update and still got nothing.
This is what finally worked.
There are a few things you will need in order to complete this.
The USB cable.
The Android SDK here.
The 2.2 Update here.
DISCLAIMER: This update should only be used if you have Cricket wireless service.
Using this update otherwise will probably render your phone useless. I will update this thread when new updates become available for different carriers.
1. Put the phone in fast boot. (hold send while pressing power)
2. Open a command prompt on your PC.
3. cd to where fastboot.exe is installed. ex:
C:\Program Files\Android\android-sdk\tools
4. Type the following with a return at the end of each
fastboot erase system
fastboot erase boot
fastboot reboot
5. This should reboot your phone. Before it starts back up,
hold the up and down volume buttons. This will bring you into "modem download mode"
6. Start the 2.2 update and your back to functional after it reboots.
Note: You may lose everything on your phone, so back it up.
More information here from Mattix724:
http://forum.xda-developers.com/showpost.php?p=11655438&postcount=19

Great guide, although I posted this about 3 days ago in another thread... did you copy my guide and start a new thread for it?
4. Put your phone into fastboot. Hold Volume + up and the send and power keys. You can do "fastboot -w" and it will wipe user data and cache. You will need to type "fastboot erase system" and it will erase the system partition. Now type "fastboot reboot" and your phone will restart.
Click to expand...
Click to collapse
Sent from my Zio using XDA Premium App

Wow man no i didn't see your post. I even looked for info on this subject and found very little. I'm sorry.
Sent from my Zio using XDA App

Its good it needed a thread of its own anyway.
Sent from my Zio using XDA Premium App

Hellyeah, thanks for writing this guide fellas. This method will be really handy.

Thanks for linking to my post. Can we make this a sticky so others can find this since the OTA may have "broken" a few phones.
Sent from my Zio using XDA Premium App

I know it broke mine. I'm trying to install ADK on a machine now so I can try this. Mine shows the Kyocera screen, then blank screen with nothing, then the keys light up and it sits like that for several minutes, then finally the Kyocera logo again.
I can get fast boot, by pressing Volume Up, Send, Trackball button, and End.

Down load sdk-manager from Google's Android Development site. Follow the instructions from this thread and you should be back in business. Once your phone boots up again after the update you just have skip Google sign in and dial *228 and you should have 3G service again. If you need more help read below.
Mattix724 said:
Uninstall the drivers for your zio that you have currently installed. Install the drivers that are on the site for the update download. Turn the phone off, unplug your battery for about 10 seconds if you need to. Hold + up and - down on the volume and the power button to put your phone into Modem Download Mode manually. Give the computer a minute to recognize the device. Run the updater again and if it fails or gives you an error message I would reccomend downloading the updater again. I have been able to run the updater several times already with no issues.
If you are still having problems, you may need to download sdk-manager if you do not have it already. You can always just use fastboot to erase the system and then run the update. The update will then set up the system partition and update the phone.
I had to do this just a few hours ago after I semi-bricked my phone while messing around with the cpu. What I did to get it working again after "bricking" it was...
1. you will need to have the android folder for the sdk-manager in the root of your hard drive to make it easier, unless you know where it is located.
2. Open command prompt and change to the tools directory within the sdk-manager folder. Mine was located in C:\Android\SDK-Manager\Tools
3. You may need to find the AdbWinApi.dll file, mine was located in the platform-tools directory so I just copied it to the main Android folder then copied fastboot from the tools directory and also placed that into the main Android folder.
4. Put your phone into fastboot. Hold Volume + up and the send and power keys. You can do "fastboot -w" and it will wipe user data and cache. You will need to type "fastboot erase system" and it will erase the system partition. Now type "fastboot reboot" and your phone will restart.
5. Put your phone in Modem Download Mode and run the updater.
Click to expand...
Click to collapse
Sent from my Zio using XDA Premium App

I'm trying that now. Waiting for the update to download. I already installed the driver. Had to use Bootcamp on my MacBook Pro (ughhh). Didn't have to bother uninstalling drivers since none had ever been installed.
I've got it in modem download mode now. ::crosses fingers::
Thanks for you help I really, really appreciate it.

I tried running it. It hung at 98% for quit a while and then said Download fail. Error code: [0x500900000]
I'm gonna try to wipe with fastboot now. I'm update my results.

I wiped with fastboot and now I'm trying to update again. I thought I would post the commands I used and it might help those that aren't as good with the command line.
Code:
cd "C:\Program Files\Android\android-sdk\tools"
copy ..\platform-tools\AdbWinApi.dll .
fastboot -w
fastboot erase system
fastboot reboot
Then I booted in modem download mode and it told me it was updating. I pulled the battery after it was done and put it back in modem download mode again and I'm waiting for the update. I'll update again when finished.

I got "Download fail." again. Any other suggestions?

Erase boot aswell. Also do not remove the battery. Just turn the phone back on after it turns off
Sent from my Zio using XDA Premium App

Trying it now. Couldn't figure out how to get Modem Download Mode without pulling the battery till I realized I could hold the volume keys while I typed fastboot reboot.

I was also thinking of trying to do fastboot update, but I'd need the update.zip. I tried extracting the MSI to see if it contained the update.zip but it doesn't. I'm assuming I could make one from the files in the MSI update installer, but I'm not sure how.

You would need to tear down the installer package for that. I've need to try that. If I find the images I will make a zip for the update.
Sent from my Zio using XDA Premium App

I noticed it uses it's own adb included in the MSI. I tried killing adb before running the update and it's running and has been sitting at 98% a lot longer this time. 98% is where it always fails. If it helps the Status at the top of the app says TX LOADER.
I've got to figure something out here. I can't afford another phone right now. I really don't want a brick. ;(

If you can find files such as boot.img and system.img recovery.img and a couple others that are listed when your phone is in fastboot.
Sent from my Zio using XDA Premium App

You might need to delete the recovery partition aswell as boot and system. Worst case scenario you end up erasing everything you see in fastboot then trying to update again.
Sent from my Zio using XDA Premium App

How do I do that. Fastboot says at the begining now CANNOT READ BOOT IMAGE HEADER. That happened after I did fastboot erase boot.
In fastboot on the screen I see it has 9 memory areas.
fota_amss
boot
system
flex
recovery
userdata
fota_boot
cache
misc
I was thinking of clear others that I hadn't yet, but I'm not sure if I'll kill fastboot doing that and then really be bricked.

Nexus One recovery won't start, stuck on bootloader

Hello,
ok so the problem is I tired to update to Jelly beam, i read about it here and i follow the steps. I make it to recovery and when i wanted to install files from zip it gave me error - Installation Aborted. I read somewhere that i have to update my Clockwork recovery so i tried and since then i can't do anything. When i press the power button i go to bootloader, from there if i chose Recovery the phone reboots and stucks on the colored X. When i type "adb devices" in cmd so i can try to apply some method list of devices is empty. I think it can be fixed if i make it to recovery but i can't. I looked a lot and maybe its because im mad or something but i can't find a solution, so if anyone can help me i will be very happy. I don't bother if im back to stock.

Use fastboot in bootloader, adb is only available in os and recovery
fastboot flash recovery recovery.img
Sent from my Nexus One using xda app-developers app

demkantor said:
Use fastboot in bootloader, adb is only available in os and recovery
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Tried that, stuck on : <waiting for device>
EDIT: I tried on my brother laptop and it worked but when i exucute the command, it says FAILED(remote: image update error)
EDIT2: Thanks i fixed it its working now. WOOHO!

when in bootloader have phone in fastboot mode, connect to pc via usb, make sure you have the proper drivers
HERE, THIS SHOULD HELP this is for a different phone so dont use the files but the concept is the same

[Q] Htc One BRICKED.

After only four day of having this phone i managed to brick it. I would really like to know if its fixable or if i have a really nice paper weight. Im stuck on a boot loop, I was half way through flashing a rom when it suddenly shut off. Now it will not boot up. I can load into the bootlader but when i try to go into recovery it just sends me to fastboot. When i restart the phone i can see the old recovery (TWRP)for just an instant but then the screen goes completely black. If i plug in to my pc, nothing happens my computer detects it but it says y device is damaged nd it cant identify it. PLEASE HELP Am i out of luck?
Ive looked around but i couldnt seem to find anyone with the same problem as me (Sprint Variant)

Good news it's not bricked i would put this question on the rom thread someonethere sshould be able to help

There's a Sprint One forum as well, so hopefully you found a ROM on there!
http://forum.xda-developers.com/forumdisplay.php?f=2215

jaythenut said:
Good news it's not bricked i would put this question on the rom thread someonethere sshould be able to help
Click to expand...
Click to collapse
I really hope so because on a college budget i cant afford another phone D:

Seen this in a couple of other places. Seems certain recoveries are possibly becoming currupted during flashing a new ROM.
What you need to do it get back into fastbboot, and....
fastboot erase recovery
fastboot erase cache
the re-flash your recovery, boot into recovery, full wipe and reflash your ROM.

wnp_79 said:
Seen this in a couple of other places. Seems certain recoveries are possibly becoming currupted during flashing a new ROM.
What you need to do it get back into fastbboot, and....
fastboot erase recovery
fastboot erase cache
the re-flash your recovery, boot into recovery, full wipe and reflash your ROM.
Click to expand...
Click to collapse
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!

i suggest you contact with HTC customservices to repair this problem.

Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
Can you flash recovery in fastboot ?
the safest thing to do is relock and use a matching RUU to get back to stock

Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
Your phone isn't bricked. There are two tools in this forum that can help you. One is made by hasoon2000(I think that's his user name), and the other is jwtool(I think). Use them to help to flash a recovery if you don't know how to use fastboot.

DynamicRam said:
Can you flash recovery in fastboot ?
the safest thing to do is relock and use a matching RUU to get back to stock
Click to expand...
Click to collapse
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.

Muquita said:
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Click to expand...
Click to collapse
dont give up
Sent from my HTC One

Muquita said:
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Click to expand...
Click to collapse
Edit: Just got done typing the stuff below and saw you can't connect to your device in fastboot? What do you mean by re-installed driver?
Don’t worry, as long as you can still get into hboot your phone is not completely bricked!
The fastboot commands I referred to need to be carried out on your laptop/pc when you phone is connected in fastboot.
Can I assume that as you have already unlocked bootloader and flashed a custom recovery you are already familiar with this and have your computer set up for fastboot commands?
(Apologies if you already know some of this, best not to skip parts out though!)
I’d start with downloading a fresh version of your chosen recovery, and place it in your fastboot directory ready. I’d also do the same with your ROM.
Like you have already done, boot into fastboot. Connect your phone to your pc, and the red text should change to ‘Fastboot USB’.
Then open up command prompt and get to your fastboot directory. (On Windows 7 you just find that folder in Explorer, hold shift and right-click, then choose ‘Open command window here’.)
To check your pc is talking to your phone, type ‘fastboot devices’. You should get a device serial number back if all is well.
Then type ‘fastboot erase cache’ and hit enter.
Then type ‘fastboot erase recovery’ and hit enter.
Then type ‘fastboot flash recovery [name of recovery].img’ and hit enter.
Then type ‘fastboot reboot recovery’ and hit enter.
Hope fully you should successfully boot into recovery now. Once in recovery, mount USB storage and copy over your fresh ROM. Choose to do a full wipe including cache and dalvik, then reflash your ROM.
Reboot.
Let me know how this goes.

cronus101 said:
Your phone isn't bricked. There are two tools in this forum that can help you. One is made by hasoon2000(I think that's his user name), and the other is jwtool(I think). Use them to help to flash a recovery if you don't know how to use fastboot.
Click to expand...
Click to collapse
I used the hasoon2000 to flash TWRP earlier, but my problems is that my pc wont recognize my phone. When i plug it in it and try to re-flash it it cant find it. When i check my devices it shows up as an android device but it says the drivers are damaged. if i could get it to read it i think i should be eable to reflash somethint.
I APPRICIATE ALL THIS HELP. i really am trying to be as specific as possible :fingers-crossed:

Hey so just a thought and experience I have had with all my HTC phones is when you see that quick glimpse of the TWRP recovery screen then it disappears to an empty black screen......you are sometimes still in a form of recovery but during your Rom flash something (i don't know for sure) changed and it doesn't show the screen only black. So with that long explanation out of the way....have you tried once the screen goes black the
"adb devices "
Mine whenever in this situation would return the output of serial number and recovery so then you can push or sideload the Rom and boot into the system at which point your fastboot drivers will finally be recogniZed.....
Hope this helps a little
Sent from my HTC EVARE_UL using xda app-developers app

Muquita said:
I used the hasoon2000 to flash TWRP earlier, but my problems is that my pc wont recognize my phone. When i plug it in it and try to re-flash it it cant find it. When i check my devices it shows up as an android device but it says the drivers are damaged. if i could get it to read it i think i should be eable to reflash somethint.
I APPRICIATE ALL THIS HELP. i really am trying to be as specific as possible :fingers-crossed:
Click to expand...
Click to collapse
I'd say the next step is to re-install your drivers in the SDK. Open up your Android SDK and reinstall them. In Windows Device Manager, find your connected device (probably now with an exclamation mark on it) and right click on it and select 'Update Driver'.
(Assuming you are using Windows 7 here?)
http://developer.android.com/tools/extras/oem-usb.html

Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
when you are in fastboot, connect your phone using the usb cable, and when you see "fastboot" written in red turned into "fastboot usb" or something like this, do the commands below using cmd window of course :
1) fastboot erase recovery
2) fastboot erase cache
3) fastboot flash recovery recoveryname.img
4) fastboot erase cache
Let us know when you fix it
Good Luck

wnp_79 said:
I'd say the next step is to re-install your drivers in the SDK. Open up your Android SDK and reinstall them. In Windows Device Manager, find your connected device (probably now with an exclamation mark on it) and right click on it and select 'Update Driver'.
(Assuming you are using Windows 7 here?)
http://developer.android.com/tools/extras/oem-usb.html
Click to expand...
Click to collapse
(Win8 but the procces is identical.) All my drivers are up to date. Still no love.

On the dev forum is a thread that includes all the latest drivers (including an app to remove older drivers.)
Find that thread, download the drivers and bmp and driver removal tool. Remove drivers with tool, install the new drivers, reboot, connect phone and see if 'adb devices' finds anything.
Also make sure you're using the latest adb.
Sent from my HTC One using xda app-developers app

thneed said:
Hey so just a thought and experience I have had with all my HTC phones is when you see that quick glimpse of the TWRP recovery screen then it disappears to an empty black screen......you are sometimes still in a form of recovery but during your Rom flash something (i don't know for sure) changed and it doesn't show the screen only black. So with that long explanation out of the way....have you tried once the screen goes black the
"adb devices "
Mine whenever in this situation would return the output of serial number and recovery so then you can push or sideload the Rom and boot into the system at which point your fastboot drivers will finally be recogniZed.....
Hope this helps a little
Sent from my HTC EVARE_UL using xda app-developers app
Click to expand...
Click to collapse
This actually sounds really similar to my situation.. Would you care to be a little more specific on the procedure? noob here.

Tabtoub said:
when you are in fastboot, connect your phone using the usb cable, and when you see "fastboot" written in red turned into "fastboot usb" or something like this, do the commands below using cmd window of course :
1) fastboot erase recovery
2) fastboot erase cache
3) fastboot flash recovery recoveryname.img
4) fastboot erase cache
Let us know when you fix it
Good Luck
Click to expand...
Click to collapse
My pc will not recognize my phone. The drivers are up to date but when i plug it in it says something malfunctioned ?

[Q] Flash back to Stock

Hi guys, I'll just start things off with saying that I am far from being anywhere near as technologically advanced as the majority of you so I would like your help if possible.
I had wanted to flash back to Stock and unroot my Moto X but for some reason I had gone into TWRP and decided to delete everything. Now every time I try to reboot from TWRP, it'll just say that the phone does not have an OS Installed and therefore if I reboot it, it will just stay on the 'Warning Bootloader Unlocked" screen.
I've read quite a few threads on various forums but I am unable to get my laptop to recognise the device in fastboot. That's my only problem so far as I've downloaded the Motorola Device Manager and all those other things but still cannot get my laptop to show the device for me to put the files into. When I plug it in, I am able to hear the sound and the device recognizes that it's been plugged in but I can't see it on my laptop.
Any and all help is GREATLY appreciated. Thanks guys and forgive my ignorance.
Sent from my SM-N9005 using XDA Free mobile app

boss. said:
Hi guys, I'll just start things off with saying that I am far from being anywhere near as technologically advanced as the majority of you so I would like your help if possible.
I had wanted to flash back to Stock and unroot my Moto X but for some reason I had gone into TWRP and decided to delete everything. Now every time I try to reboot from TWRP, it'll just say that the phone does not have an OS Installed and therefore if I reboot it, it will just stay on the 'Warning Bootloader Unlocked" screen.
I've read quite a few threads on various forums but I am unable to get my laptop to recognise the device in fastboot. That's my only problem so far as I've downloaded the Motorola Device Manager and all those other things but still cannot get my laptop to show the device for me to put the files into. When I plug it in, I am able to hear the sound and the device recognizes that it's been plugged in but I can't see it on my laptop.
Any and all help is GREATLY appreciated. Thanks guys and forgive my ignorance.
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
You don't put files on the phone and you don't use twrp. Follow the instructions in the return to 100% stock thread.

samwathegreat said:
You don't put files on the phone and you don't use twrp. Follow the instructions in the return to 100% stock thread.
Click to expand...
Click to collapse
I've tried following the steps but I was unsure of step 3 where it says to download and install the proper firmware for the device but still unsure on how to install it. RSD Lite won't pick up the device nor will it show up when I type 'adb devices' in CMD. And finally, how do I go about turning on USB debugging when it won't boot up past the bootloader unlock screen?
Appreciate the help
Sent from my SM-N9005 using XDA Free mobile app

boss. said:
I've tried following the steps but I was unsure of step 3 where it says to download and install the proper firmware for the device but still unsure on how to install it. RSD Lite won't pick up the device nor will it show up when I type 'adb devices' in CMD. And finally, how do I go about turning on USB debugging when it won't boot up past the bootloader unlock screen?
Appreciate the help
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Turn the phone off. Unplug it. Hold down VOL DOWN, and press power. The phone will boot into the bootloader. This is how you flash with rsd lite.
Adb does not work in bootloader, and isn't used for this. Once in bootloader (ap fastboot mode), rsd lite should recognize the device.
Make absolutely sure you do not downgrade to a previous version (you will brick), and make sure you flash the correct firmware for YOUR device/carrier.
You can only flash the same version or higher than what you were on before you erased everything.

samwathegreat said:
Turn the phone off. Unplug it. Hold down VOL DOWN, and press power. The phone will boot into the bootloader. This is how you flash with rsd lite.
Adb does not work in bootloader, and isn't used for this. Once in bootloader (ap fastboot mode), rsd lite should recognize the device.
Make absolutely sure you do not downgrade to a previous version (you will brick), and make sure you flash the correct firmware for YOUR device/carrier.
You can only flash the same version or higher than what you were on before you erased everything.
Click to expand...
Click to collapse
Thanks for the help! Unfortunately RSD Lite doesn't recognise the device in bootloader. Am I supposed to put the files into a certain place for things to start working properly and is it also because I'm using windows 8.1? I've already installed the Motorola Device Manager as well.
Really sorry for all the questions - complete newbie right here
Sent from my SM-N9005 using XDA Free mobile app

boss. said:
Thanks for the help! Unfortunately RSD Lite doesn't recognise the device in bootloader. Am I supposed to put the files into a certain place for things to start working properly and is it also because I'm using windows 8.1? I've already installed the Motorola Device Manager as well.
Really sorry for all the questions - complete newbie right here
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
You said you downloaded moto device manager... Did you install it? If so you are one of the unlucky ones and will have to use the manual method with fastboot and mfastboot. Take it slow and follow the instructions. Leave out the config carrier line.
To make sure fastboot is working, type fastboot devices while in bootloader mode.

samwathegreat said:
You said you downloaded moto device manager... Did you install it? If so you are one of the unlucky ones and will have to use the manual method with fastboot and mfastboot. Take it slow and follow the instructions. Leave out the config carrier line.
To make sure fastboot is working, type fastboot devices while in bootloader mode.
Click to expand...
Click to collapse
Oh okay that makes sense. Yeah I had installed but still nothing. Okay, I'll try the manual method, thanks heaps!
I've typed it fastboot devices in CMD and it came up with T017500PDP fastboot. I assume that's good? Haha
Sent from my SM-N9005 using XDA Free mobile app

boss. said:
Oh okay that makes sense. Yeah I had installed but still nothing. Okay, I'll try the manual method, thanks heaps!
I've typed it fastboot devices in CMD and it came up with T017500PDP fastboot. I assume that's good? Haha
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Yes perfect.
Run one command at a time - copy/paste them.
Remember to use mfastboot for system.img - regular fastboot will NOT work. Also remember to skip the config carrier command.

samwathegreat said:
Yes perfect.
Run one command at a time - copy/paste them.
Remember to use mfastboot for system.img - regular fastboot will NOT work. Also remember to skip the config carrier command.
Click to expand...
Click to collapse
You my friend are a legend. Last round (hopefully) of questions though: where the code says to type in fastboot flash .... .gpt.bin and all those other things, am I supposed to put the files somewhere in particular? Because just regularly typing them into CMD comes up with (bootloader) Variable not supported! Then error: cannot open 'gtp.bin' or cannot open 'recovery.img' and so on but on the phone it says getvar partition-type:recovery or boot and so on.
Also the when the instructions say to use mfastboot, CMD says that it is not recognized as an internal or external command. Thanks!
Sent from my SM-N9005 using XDA Free mobile app

boss. said:
You my friend are a legend. Last round (hopefully) of questions though: where the code says to type in fastboot flash .... .gpt.bin and all those other things, am I supposed to put the files somewhere in particular? Because just regularly typing them into CMD comes up with (bootloader) Variable not supported! Then error: cannot open 'gtp.bin' or cannot open 'recovery.img' and so on but on the phone it says getvar partition-type:recovery or boot and so on.
Also the when the instructions say to use mfastboot, CMD says that it is not recognized as an internal or external command. Thanks!
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
First: yes, you have to put those files in the same folder as you are running the commands from. If your command prompt shows C:\users\jimmy\
Then that is where the files should be! You should have extracted the zip file you downloaded to the same folder you are running the commands from.
Second, you obviously have not download mfastboot.exe (it is linked in the return to stock thread) OR you didn't put it in the same folder as the rest of the files.
The "variable not supported" messages are normal. The error cannot open.... errors are NOT.
I'm attaching mfastboot.exe (it's zipped - extract it to the same folder as everything else) to this post so you don't have to go looking for it.
DON'T move on if the first command doesn't work. Make sure each one gives success before you move on.

Awesome!

samwathegreat said:
First: yes, you have to put those files in the same folder as you are running the commands from. If your command prompt shows C:\users\jimmy\
Then that is where the files should be! You should have extracted the zip file you downloaded to the same folder you are running the commands from.
Second, you obviously have not download mfastboot.exe (it is linked in the return to stock thread) OR you didn't put it in the same folder as the rest of the files.
The "variable not supported" messages are normal. The error cannot open.... errors are NOT.
I'm attaching mfastboot.exe (it's zipped - extract it to the same folder as everything else) to this post so you don't have to go looking for it.
DON'T move on if the first command doesn't work. Make sure each one gives success before you move on.
Click to expand...
Click to collapse
Thanks so much, it worked great! The colours are a bit out of wack though (the blues are now orange and so on) and the bot animation is messed but still better than nothing. Thanks so much for your help!

boss. said:
Thanks so much, it worked great! The colours are a bit out of wack though (the blues are now orange and so on) and the bot animation is messed but still better than nothing. Thanks so much for your help!
Click to expand...
Click to collapse
You're welcome....but that isn't normal. I suggest doing it again from the beginning. A full SBF to stock re-writes all the partitions and there shouldn't be anything "out of wack". Sounds like something went wrong....OR your device has physical damage?
Anyways, please consider hitting the "THANKS" button under any and all posts that help you. :good:

samwathegreat said:
You're welcome....but that isn't normal. I suggest doing it again from the beginning. A full SBF to stock re-writes all the partitions and there shouldn't be anything "out of wack". Sounds like something went wrong....OR your device has physical damage?
Anyways, please consider hitting the "THANKS" button under any and all posts that help you. :good:
Click to expand...
Click to collapse
Re-did the whole thing from scratch again and now all problems are solved. Really appreciate the help my friend!
Sent from my SM-N9005 using XDA Free mobile app

HTC One M7 stuck entering recovery after installing Android revolution HD one 92.04a9

hey sorry I'm sure this has been covered but I've been trying to root my new phone for the past 15+ hours and after installing Android revolution HD one 92.04a9 through Team Win Recovery project v2.6.3.0 it now keeps restarting in recovery and then takes me to Recovery project after a htc logo screen.
This is the first time I have attempted to root a phone and I'm a noob evidently so please go easy on me. (all I wanted was to hook up my bluetooth controller so I can play FF7 with more ease) any help would be greatly appreciated as I've just moved from London to the middle of nowhere and I'm bored out of my mind without my beloved HTC
Thanks a lot Mr. Tickles

I am so frustrated with general support of HTC. I am trying to get in touch with service for two months and no luck. My next phone won't be HTC for sure, I know.

ticklemelee said:
hey sorry I'm sure this has been covered but I've been trying to root my new phone for the past 15+ hours and after installing Android revolution HD one 92.04a9 through Team Win Recovery project v2.6.3.0 it now keeps restarting in recovery and then takes me to Recovery project after a htc logo screen.
This is the first time I have attempted to root a phone and I'm a noob evidently so please go easy on me. (all I wanted was to hook up my bluetooth controller so I can play FF7 with more ease) any help would be greatly appreciated as I've just moved from London to the middle of nowhere and I'm bored out of my mind without my beloved HTC
Thanks a lot Mr. Tickles
Click to expand...
Click to collapse
Try factory reset from twrp recovery and the flash again. Also you can try to download the zip of the ROM again to be sure it is downloaded correctly and try change the twrp version.

You are using an older version of twrp. Try updating it first to the latest version and try flashing your rom again
Get the latest one here
https://dl.twrp.me/m7/

But how do I do that if my phone wont appear in my computer any more?
Its 100% connected to my computer though because its appearing in devices printers but under the name android 1.0

You cannot enter in fastboot mode? If you can, then you flash recovery via fastboot

ticklemelee said:
But how do I do that if my phone wont appear in my computer any more?
Its 100% connected to my computer though because its appearing in devices printers but under the name android 1.0
Click to expand...
Click to collapse
@istribo is right, to flash arhd you need at least twrp 2.6.3.3 or newer (latest version is 2.8.7.0) To update your recovery, make sure you have HTC drivers installed on your computer and also uninstall htc sync if its installed (but do not uninstall the drivers). Download your new twrp .img file from the link istribo posted above, save it in the same folder where you have adb and fastboot installed on your computer. Reboot your phone in bootloader / fastboot usb mode. Open a terminal window from your adb/fastboot folder and use these commands to flash the recovery:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
Then reboot in recovery and flash arhd.
Note that you should also have a 7.xx.xxx.x firmware installed on your phone if flashing Android 5.0.2 Sense roms. You can know your firmware version with the command "fastboot getvar version-main"

My phone wont appear in my computer so how am I supposed to copy over the files...

sorry guys I'm going to need a step by step guide made for an idiot lol

ticklemelee said:
sorry guys I'm going to need a step by step guide made for an idiot lol
Click to expand...
Click to collapse
If you press power button and volume down button it gets you into recovery. Then u choose fastboot and the you do what alray said.

right so the fact my phone wont appear in my computer doesn't matter then?

Okay sorry for being silly I've just read that properly. Problem is when I got to install adb/fast boot it says something like incorrect parameter 'sheppard'

ticklemelee said:
Okay sorry for being silly I've just read that properly. Problem is when I got to install adb/fast boot it says something like incorrect parameter 'sheppard'
Click to expand...
Click to collapse
Download the sdk tools here (fastboot and adb): https://developer.android.com/sdk/index.html#Other
Download and install HTC drivers: http://www.mediafire.com/download/k7trah995whrw0d/HTC-Mobile-Driver_v4.16.0.001.exe
Connect your phone to a USB 2 port directly from your computer (no external usb hub, better to use back ports, not front ports)
Reboot your phone in bootloader mode by holding power and volume down. When in bootloader, make sure you see the red "fastboot usb" caption, if not select the "fastboot" option using the vol up/down and power key to enter. Once "fastboot" option is selected, make sure you now see the red "fastboot usb" caption.
Open a terminal window from your sdk tools folder
Type "fastboot getvar all" without the quotes en hit enter
copy paste the output here so we can see it (but do not post your IMEI/Serialno)
Then update your twrp:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader

Sorry I forgot to say I got my phone all working and rooted! Thank you all so much for your help! wouldn't of done it without you guys.