Related
Hello Everyone,
As of today, my phone received the new OTA Update for my HTC One S. However, obviously I cannot update due to my phone being rooted. As a person who is still relatively new with rooting (about a month rooted with my phone-first time), I have a couple questions.
First and foremost, have you guys enjoyed the OTA Update so far? I have read about the list of improvements, and they look promising.
Secondly, I obviously want to stay rooted, are there any suggestions about how to update and then have my phone rooted? Preferably without losing my root, but I don't think that's possible.
Thirdly, I saw a thread about the viper (I believe that's what it's called) rom and that could be my possible solution. But, I am rooted on stock rom and have never put on another rom before. So what are your thoughts on this rom?
Thanks in advance
Sent from my HTC VLE_U using xda app-developers app
Problem Fixed
DrOfLife said:
Hello Everyone,
As of today, my phone received the new OTA Update for my HTC One S. However, obviously I cannot update due to my phone being rooted. As a person who is still relatively new with rooting (about a month rooted with my phone-first time), I have a couple questions.
First and foremost, have you guys enjoyed the OTA Update so far? I have read about the list of improvements, and they look promising.
Secondly, I obviously want to stay rooted, are there any suggestions about how to update and then have my phone rooted? Preferably without losing my root, but I don't think that's possible.
Thirdly, I saw a thread about the viper (I believe that's what it's called) rom and that could be my possible solution. But, I am rooted on stock rom and have never put on another rom before. So what are your thoughts on this rom?
Thanks in advance
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Hey Dr.
I had the same issue and fixed it. I'm enjoying the OTA update...seems snappier and the option to change the menu button and get rid of that eyesore at the bottom of the screen is great....See this post on how to fix it:
http://forum.xda-developers.com/showthread.php?p=32069130
All you have to do is download the stock recovery (link located in the post above), rename it "Recovery.IMG" and put it in the /Data/Recoveries folder that your All In One Kit uses. Then open up the All In One root kit, flash the stock recovery, and reboot your phone. It should look the same, and give you the same notification that an update is available. Install the update, and then reflash your TWRP or CWM and reroot (the OTA unroots the device, so you need to reinstall SuperSu.
Thanks to all the people that have helped me do the same!!!
fsustrength said:
Hey Dr.
I had the same issue and fixed it. I'm enjoying the OTA update...seems snappier and the option to change the menu button and get rid of that eyesore at the bottom of the screen is great....See this post on how to fix it:
http://forum.xda-developers.com/showthread.php?p=32069130
All you have to do is download the stock recovery (link located in the post above), rename it "Recovery.IMG" and put it in the /Data/Recoveries folder that your All In One Kit uses. Then open up the All In One root kit, flash the stock recovery, and reboot your phone. It should look the same, and give you the same notification that an update is available. Install the update, and then reflash your TWRP or CWM and reroot (the OTA unroots the device, so you need to reinstall SuperSu.
Thanks to all the people that have helped me do the same!!!
Click to expand...
Click to collapse
I keep flashing the stock recovery with all-in-one and then downloading and installing the update. Everytime, about halfway it goes back to the red triangle with the exclamation point and restarts the phone five minutes later.
I check software and its still 4.0.3 and the update redownloads. I've tried several "stock recoveries" and the update afterwards... never works.
TheAdictsPunk said:
I keep flashing the stock recovery with all-in-one and then downloading and installing the update. Everytime, about halfway it goes back to the red triangle with the exclamation point and restarts the phone five minutes later.
I check software and its still 4.0.3 and the update redownloads. I've tried several "stock recoveries" and the update afterwards... never works.
Click to expand...
Click to collapse
I have also tried the steps and have run into the same problem. All is well when I flash into recovery, but when the phone starts updating about quarter or half-way through it also gives me the same red error message and the phone restarts soon after with no update. I have tried several times with the same problem.
However, thanks fsustrength for the instructions, before I was getting no where, but now I almost got it
Sent from my HTC VLE_U using xda app-developers app
ckpv5 said:
As there are many questions on how to do OTA update & to revert to stock after a device is rooted and bootloader unlocked; I made this simple guide which I hope will help the newbies especially.
NOTE : always do a backup and a nandroid backup before trying any of these.
OTA update:
A) ROM is stock, bootloader unlocked, stock recovery and not rooted.
- just run the OTA update, there is no need to relock the bootloader
B) ROM is stock, bootloader unlocked, CWM recovery and not rooted.
- flash the stock recovery that comes with your RUU, extract the RUU for the stock recovery.
* boot to bootloader
* fastboot flash recovery recovery_signed.img
* fastboot reboot-bootloader
* fastboot erase cache
* fastboot reboot
- run the OTA update
C) ROM is stock, bootloader unlocked, stock recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- run the OTA update, there is no need to relock bootloader
- Once done, run OTA Rootkeeper and click restore root
D) ROM is stock, bootloader unlocked, CWM recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- no need to relock bootloader
- boot to bootloader and fastboot flash the stock recovery
- run the OTA update
- Once done, run OTA Rootkeeper and click restore root
E) ROM is custom, bootloader unlocked, CWM recovery and rooted and you have a stock nandroid backup
- flash the stock boot.img if after nandroid restore, you have a bootloop
- flash the stock recovery.img
- relock the bootloader - fastboot oem lock
- boot your device and run the OTA update
F) ROM is custom, bootloader unlocked, CWM recovery and rooted and you don't have a stock nandroid backup
- if you dont have the stock nandroid backup, you need to run RUU
- before you can run the RUU you need to:
* flash the stock recovery.img
* flash the stock boot.img (maybe no need)
* relock the bootloader - fastboot oem lock
* run RUU
- run device setup
- run the OTA update
Flashing RUU to revert to stock or to update your One V after you have a custom ROM installed.
- you must have the correct RUU for your device.
- if you are not sure, download CID Getter from Play Store and run it, it will show your CID.
- with your CID, you may be able to find a correct RUU for your device
then (even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- flash RUU
Note : for people with ERROR 155 UNKNOWN ERROR they need to go into HBOOT and select FASTBOOT and run the RUU to revert to stock (thanks Lloir)
And usually:
Error 155 - usually wrong recovery.img /wrong boot.img
Error 140 - wrong bootloader / bootloader unlocked
Error 131 - wrong RUU for your device
Credit to all XDA members that posted all the guides in various forum thread and some from own experience which I compiled here for easy reference.
Click to expand...
Click to collapse
Some wonderful person wrote a guide for the One V. Every though it's not the same phone the rules are the same. If these instructions help you click the link and thank the guy for writing it.
http://forum.xda-developers.com/showpost.php?p=27288357&postcount=1
Wow, that is a very useful guide right there! However, while reading the guide, Step D is exactly what both TheAdictsPunk and I seem to have done (I'm making an assumption that he did). I did in fact have and used the root keeper app, put it on temporary unroot, and flashed the stock rom and ran the update. Yet, I still run into the problem of the red error sign. I'm sure there is a factor that maybe could cause it to stop, but I cannot put a finger on it.
However, I did notice something while following the procedures of the guide on my phone. When I flash the stock rom on my phone, I have to re-download the system update. While downloading the system update I notice that some of my apps get root permissions from SuperSu in the background, even though in root keeper I temporarily took off root. Rootkeeper also states that my phone is unrooted. Could this problem cause the red error message? If so, any way to fix it?
Sent from my HTC VLE_U using xda app-developers app
DrOfLife said:
Wow, that is a very useful guide right there! However, while reading the guide, Step D is exactly what both TheAdictsPunk and I seem to have done (I'm making an assumption that he did).
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
I did! Last night I even tried flashing the recovery image through fastboot instead of the all-in-one kit. Then, even, the recovery image wouldn't flash all the way through... maybe our phones are having a problem with the recovery being reflashed and not the update at all.
I had the same exact issue. I finally got fed up and just flashed the RUU with my computer and then just used the All-in-one program to re-root. I am now enjoying 2.31 and really glad I updated. Obviously the RUU wipes everything, but I had done a full backup using Titanium Backup, and then restored all the important settings and data (like accounts, wifi list, bookmarks, dictionary, etc.) (but not the system apps themselves! ) and it worked out pretty well. Still had some things to adjust, like sounds and such. If you want to keep your SMS's use the built-in backup in the messaging app, then restore after the update.. more reliable than any other app I've tried.
mmceorange said:
I had the same exact issue. I finally got fed up and just flashed the RUU with my computer and then just used the All-in-one program to re-root. I am now enjoying 2.31 and really glad I updated. Obviously the RUU wipes everything, but I had done a full backup using Titanium Backup, and then restored all the important settings and data (like accounts, wifi list, bookmarks, dictionary, etc.) (but not the system apps themselves! ) and it worked out pretty well. Still had some things to adjust, like sounds and such. If you want to keep your SMS's use the built-in backup in the messaging app, then restore after the update.. more reliable than any other app I've tried.
Click to expand...
Click to collapse
I'm strongly considering doing that, I can back all my contacts and apps and sms messages via Mobile Go. So, wiping my phone isn't too big of an issue for me because I can restore almost everything I need back on my phone. If you don't mind me asking, where did you get the source that you got the RUU? Also, I have never flashed an ruu before so is their a guide for our phone to flash a RUU?
Sent from my HTC VLE_U using xda app-developers app
DrOfLife said:
I'm strongly considering doing that, I can back all my contacts and apps and sms messages via Mobile Go. So, wiping my phone isn't too big of an issue for me because I can restore almost everything I need back on my phone. If you don't mind me asking, where did you get the source that you got the RUU? Also, I have never flashed an ruu before so is their a guide for our phone to flash a RUU?
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
http://www.lastnite.de/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
Links to downloads are on that page.. just copy/paste.
Basically start your phone in fastboot, connect to usb, then run the ruu with admin privileges. Make sure you are on stock recovery, and already have the USB drivers installed on your PC (unless you're on Linux.. already has them.. and maybe Mac too?)
mmceorange said:
http://www.lastnite.de/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
Links to downloads are on that page.. just copy/paste.
Basically start your phone in fastboot, connect to usb, then run the ruu with admin privileges. Make sure you are on stock recovery, and already have the USB drivers installed on your PC (unless you're on Linux.. already has them.. and maybe Mac too?)
Click to expand...
Click to collapse
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Sent from my HTC VLE_U using xda app-developers app
DrOfLife said:
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Click to expand...
Click to collapse
Ok I figured out a couple answers to my questions. One, the Europe version and the T-Mobile Version are different. That explains why the RUU did not work and gave me Error 130. However, the T-Mobile RUU, RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S, is the alternate version that also recieves the OTA update. The RUU is found here http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Then, following the steps, I have successfully updated my phone to the newer softeware!
But of course, I run into another problem.... The CWM recovery does not work for my phone. I flashed the recovery via the HTC One S All-in-One Toolkit. But when getting my phone into recovery mode, it "crashes." (By crashes I mean the phone will go into the htc developmental screen, then turn to black, then reload the normal bootup screen and boot normally up) So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Rerooting
DrOfLife said:
So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Click to expand...
Click to collapse
I'm still running stock 1.84, but I'm rooted and unlocked. I do not have any kind recovery like CWM or TWRP. You may have to flash a stock recovery image in order to re-install the recovery of your choice. If you want to get rooted again try this method: http://forum.xda-developers.com/showthread.php?t=1577831 It's what I used to gain root. It's a rather easy to follow guide. I used this instead of the AIO kit.
I'm going to try and revert to locked and unroot in order to get the update. Wish me luck.
DrOfLife said:
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Oh lol sorry about that.
DrOfLife said:
Ok I figured out a couple answers to my questions. One, the Europe version and the T-Mobile Version are different. That explains why the RUU did not work and gave me Error 130. However, the T-Mobile RUU, RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S, is the alternate version that also recieves the OTA update. The RUU is found here http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Then, following the steps, I have successfully updated my phone to the newer softeware!
Click to expand...
Click to collapse
Awesome!
DrOfLife said:
But of course, I run into another problem.... The CWM recovery does not work for my phone. I flashed the recovery via the HTC One S All-in-One Toolkit. But when getting my phone into recovery mode, it "crashes." (By crashes I mean the phone will go into the htc developmental screen, then turn to black, then reload the normal bootup screen and boot normally up) So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Click to expand...
Click to collapse
I personally have never encountered that before, so I am of little help here. The suggestion above me sounds like the right direction though.
Red triangle error
dc211 said:
Some wonderful person wrote a guide for the One V. Every though it's not the same phone the rules are the same. If these instructions help you click the link and thank the guy for writing it.
http://forum.xda-developers.com/showpost.php?p=27288357&postcount=1
Click to expand...
Click to collapse
I'm using method C, i still get that red triangle error. Also i can't get the ruu for my phone. I'm desperate can you please help me.
lonegunman0 said:
I'm using method C, i still get that red triangle error. Also i can't get the ruu for my phone. I'm desperate can you please help me.
Click to expand...
Click to collapse
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
skidmarc11 said:
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
Click to expand...
Click to collapse
If this many people are running into this problem, maybe we can get a role call of whose using what method, if not stock ROM what custom they are using, and what carrier they us?
I'm stock ROM, Stock Recovery, and Tmobile US. I used Method C.
I'm wondering if they have changed the update in a way that is preventing some people from updating. like it detects a certain file before update or something idk. I'm not any sort of advanced android user so I am probably wrong, but it's the first thing that comes to mind. Otherwise, maybe they sent out a bad update file, but I feel like that probably wouldn't be the case since it's been happening for a couple days now.
Thought's ideas anyone, or am I alone in any of these thoughts?
Stock rom
mylegiscramped said:
If this many people are running into this problem, maybe we can get a role call of whose using what method, if not stock ROM what custom they are using, and what carrier they us?
I'm stock ROM, Stock Recovery, and Tmobile US. I used Method C.
I'm wondering if they have changed the update in a way that is preventing some people from updating. like it detects a certain file before update or something idk. I'm not any sort of advanced android user so I am probably wrong, but it's the first thing that comes to mind. Otherwise, maybe they sent out a bad update file, but I feel like that probably wouldn't be the case since it's been happening for a couple days now.
Thought's ideas anyone, or am I alone in any of these thoughts?
Click to expand...
Click to collapse
skidmarc11 said:
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
Click to expand...
Click to collapse
Yes i agree about the file detection. I'm running stock rom but i think i've just realised my problem. Although i have a stock rom my problem is that the stock rom i'm running is deodexed. I read somewhere that if the stock rom is tweaked in any way or if any bloatware is deleted you can't get OTA updates.
Hope this helped
Wouldn't an RUU fix any of those problems?
Yes it would
Sent from my HTC One S using xda app-developers app
So get this: I've got a friend who owns this One X, right? He got it replaced, and he got back a phone running the "new OTA", which I'm assuming is 2.20. He unlocked his bootloader and got root, and tried to flash a custom recovery (CWM from what he tells me), and then it died. He knows that I'm good at the whole Android thing, so he gave me the phone with the task of bringing it back to life.
Given that my regular phone is a GNex, "bricked" and "softbricked" aren't terms I use often, so I'm not entirely sure it's applicable to this situation. But, I'll tell you everything I know about the situation.
When I power it up, it comes up with the htc splash, then the "This build is for development purposes only..." message. It stays like that for a little bit, then the screen goes off. It comes back within five seconds, and it just continues ad nauseum.
I'm able to get into hboot and fastboot (booting into the bootloader with power+voldown) and execute fastboot commands, but I really don't know what I should do, and even if I do, I don't have the files I need.
The bootloader has this information; I'm fairly sure it can help...
Code:
evita pvt ship s-on rl
HBOOT 1.14.0002
eMMC boot
Radio - 0.19as.32.09.11_2
I executed a fastboot command (I forget which one), and I wrote down the value...
Code:
mainver: 2.20.502.7
I assume this is the installed system version, or something similar, but please correct me if I'm wrong xD
All I'm trying to do is to get this thing to boot into Android. If I can do that much, I'm sure he'd be more than elated. Thing is, I'm not entirely sure what's wrong with this phone, much less what I'd have to do to fix it.
TL;DR
My friend's phone is screwed up, how do I fix it?
wiiareonfire said:
So get this: I've got a friend who owns this One X, right? He got it replaced, and he got back a phone running the "new OTA", which I'm assuming is 2.20. He unlocked his bootloader and got root, and tried to flash a custom recovery (CWM from what he tells me), and then it died. He knows that I'm good at the whole Android thing, so he gave me the phone with the task of bringing it back to life.
Given that my regular phone is a GNex, "bricked" and "softbricked" aren't terms I use often, so I'm not entirely sure it's applicable to this situation. But, I'll tell you everything I know about the situation.
When I power it up, it comes up with the htc splash, then the "This build is for development purposes only..." message. It stays like that for a little bit, then the screen goes off. It comes back within five seconds, and it just continues ad nauseum.
I'm able to get into hboot and fastboot (booting into the bootloader with power+voldown) and execute fastboot commands, but I really don't know what I should do, and even if I do, I don't have the files I need.
The bootloader has this information; I'm fairly sure it can help...
Code:
evita pvt ship s-on rl
HBOOT 1.14.0002
eMMC boot
Radio - 0.19as.32.09.11_2
I executed a fastboot command (I forget which one), and I wrote down the value...
Code:
mainver: 2.20.502.7
I assume this is the installed system version, or something similar, but please correct me if I'm wrong xD
All I'm trying to do is to get this thing to boot into Android. If I can do that much, I'm sure he'd be more than elated. Thing is, I'm not entirely sure what's wrong with this phone, much less what I'd have to do to fix it.
TL;DR
My friend's phone is screwed up, how do I fix it?
Click to expand...
Click to collapse
He probably forgot to flash boot.img in fastboot.
If you are bricked, this phone will not turn on and be listed as QHSUSB_DLOAD in windows.
edit: cwm + evita(htc one xl) = bad.
he needs TWRP
wiiareonfire said:
So get this: I've got a friend who owns this One X, right? He got it replaced, and he got back a phone running the "new OTA", which I'm assuming is 2.20. He unlocked his bootloader and got root, and tried to flash a custom recovery (CWM from what he tells me), and then it died. He knows that I'm good at the whole Android thing, so he gave me the phone with the task of bringing it back to life.
Given that my regular phone is a GNex, "bricked" and "softbricked" aren't terms I use often, so I'm not entirely sure it's applicable to this situation. But, I'll tell you everything I know about the situation.
When I power it up, it comes up with the htc splash, then the "This build is for development purposes only..." message. It stays like that for a little bit, then the screen goes off. It comes back within five seconds, and it just continues ad nauseum.
I'm able to get into hboot and fastboot (booting into the bootloader with power+voldown) and execute fastboot commands, but I really don't know what I should do, and even if I do, I don't have the files I need.
The bootloader has this information; I'm fairly sure it can help...
Code:
evita pvt ship s-on rl
HBOOT 1.14.0002
eMMC boot
Radio - 0.19as.32.09.11_2
I executed a fastboot command (I forget which one), and I wrote down the value...
Code:
mainver: 2.20.502.7
I assume this is the installed system version, or something similar, but please correct me if I'm wrong xD
All I'm trying to do is to get this thing to boot into Android. If I can do that much, I'm sure he'd be more than elated. Thing is, I'm not entirely sure what's wrong with this phone, much less what I'd have to do to fix it.
TL;DR
My friend's phone is screwed up, how do I fix it?
Click to expand...
Click to collapse
sounds like your FRIEND needs to flash in fastboot the boot.img that came with his rom...
Crappyvate said:
sounds like your FRIEND needs to flash in fastboot the boot.img that came with his rom...
Click to expand...
Click to collapse
absolutelygrim said:
He probably forgot to flash boot.img in fastboot.
Click to expand...
Click to collapse
Would I be able to get a stock boot.img and system.img from the 2.20 RUU? Should I even use the RUU for this?
wiiareonfire said:
Would I be able to get a stock boot.img and system.img from the 2.20 RUU? Should I even use the RUU for this?
Click to expand...
Click to collapse
what ROM did he flash. copy the boot.img from that ROM and flash it in fastboot, then flash the ROM
First, extract boot.img onto comp. Move boot.img into adb files. Rezip Rom and transfer to sdcard. Fire up command prompt where you stored boot.img. type --> fastboot flash boot boot.img
Once successful, flash Rom IN RECOVERY. profit
Tell your FRIEND to follow posts before blindly flashing, he'd be more prepared
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
Can you get into boot loader? Hold the volume down whilst the phone boots. Flash TWRP!! Clockworkmod is not supported for our device. Oh and very first. Make sure you have the Evita not the international one x.
Check this thread out. Might help
http://forum.xda-developers.com/showthread.php?p=33303798
Sent from my One X using xda premium
absolutelygrim said:
what ROM did he flash. copy the boot.img from that ROM and flash it in fastboot, then flash the ROM
Click to expand...
Click to collapse
He didn't flash any ROM, only CWM. He wasn't ever able to get into recovery to flash anything.
subarudroid said:
Can you get into boot loader? Hold the volume down whilst the phone boots. Flash TWRP!! Clockworkmod is not supported for our device. Oh and very first. Make sure you have the Evita not the international one x.
Check this thread out. Might help
http://forum.xda-developers.com/showthread.php?p=33303798
Sent from my One X using xda premium
Click to expand...
Click to collapse
Just did that, and it's still not working. Can't even boot into recovery.
I'm gonna need a boot.img, but he started from stock OTA. I don't know how the boot.img could've gone bad from flashing a bad recovery, but I'll try that anyway.
Question is, where would I get a boot.img for the stock sense ROM? Or, how would I be able to flash a ROM without being able to get into recovery?
wiiareonfire said:
He didn't flash any ROM, only CWM. He wasn't ever able to get into recovery to flash anything.
Just did that, and it's still not working. Can't even boot into recovery.
I'm gonna need a boot.img, but he started from stock OTA. I don't know how the boot.img could've gone bad from flashing a bad recovery, but I'll try that anyway.
Question is, where would I get a boot.img for the stock sense ROM? Or, how would I be able to flash a ROM without being able to get into recovery?
Click to expand...
Click to collapse
hold your horses, let's take a deep breath here. Have you tried to reboot in recovery through adb ? If that does not work why don't you try to fastboot flash a proper recovery for the one x, TWRP http://forum.xda-developers.com/showpost.php?p=33179690&postcount=1
Crappyvate said:
hold your horses, let's take a deep breath here. Have you tried to reboot in recovery through adb ? If that does not work why don't you try to fastboot flash a proper recovery for the one x, TWRP http://forum.xda-developers.com/showpost.php?p=33179690&postcount=1
Click to expand...
Click to collapse
Code:
C:\Android>adb reboot recovery
error: device not found
Surprisingly enough, you need to be booted into android for adb commands to work. Even the bootloader option for "recovery" gets me nowhere.
Out of nowhere, he tells me he tried to flash a rom.
Ali: the rom that i flashed hmmm.
if i sent that to you would you be able to do anything?
well, tried flashing?
Me: a download link would be preferable
but yes, i'll need that
Ali Haider: got it.
give me a few minutes.
what if the rom wasn't supported?
because i can't completely remember which of the several roms i tried to flash were the problem
Me: what do ya mean "not supported"
Ali:
like clockwork- it apparently doesn't work
Me:
gimme whichever you flashed most revently
a link
i'll need the boot.img
and if you don't know which rom, gimme a list to narrow it down
and i'll go one by one
Click to expand...
Click to collapse
TL;DR, he flashed with CWM and that's why it's screwed up.
Ladies and gents, we might be getting somewhere with this. Albeit, slowly, thanks to my friend who can't read the posts.
I think Crappyvate has the right idea here. You need to flash a proper recovery.
Sent from my One X using xda premium
subarudroid said:
I think Crappyvate has the right idea here. You need to flash a proper recovery.
Click to expand...
Click to collapse
So I've flashed TWRP at least three different times, and I can't the phone to boot into it.
I've flashed two different boot.img files, no avail.
He claims all he's done is fastboot flash CWM, and then the thing went down the drain. Splash screen over and over again, exactly what I'm seeing here. Is there any reason that flashing TWRP over it wouldn't work? Is there a fastboot command I can use to make sure the partition is clean?
wiiareonfire said:
So I've flashed TWRP at least three different times, and I can't the phone to boot into it.
I've flashed two different boot.img files, no avail.
He claims all he's done is fastboot flash CWM, and then the thing went down the drain. Splash screen over and over again, exactly what I'm seeing here. Is there any reason that flashing TWRP over it wouldn't work? Is there a fastboot command I can use to make sure the partition is clean?
Click to expand...
Click to collapse
What happens after flashing twrp in flashboot ? what msg do you get ?
Okay, scratch that. I flashed TWRP again and again through fastboot, and instead of using "recovery", I used "factory reset", and it opened up TWRP.
Fun fact: it's not able to mount the /sdcard, so using adb to push the zip for the ROM just crashes TWRP. That was my last-ditch plan to get the ROM file onto the phone to flash it. Anyone else got any idea how to get a file on there?
wiiareonfire said:
Okay, scratch that. I flashed TWRP again and again through fastboot, and instead of using "recovery", I used "factory reset", and it opened up TWRP.
Fun fact: it's not able to mount the /sdcard, so using adb to push the zip for the ROM just crashes TWRP. That was my last-ditch plan to get the ROM file onto the phone to flash it. Anyone else got any idea how to get a file on there?
Click to expand...
Click to collapse
thats a cwm classic it corrupted the SD card. you need to reformat the sd card, can you mount usb through twrp ?
Crappyvate said:
thats a cwm classic it corrupted the SD card. you need to reformat the sd card, can you mount usb through twrp ?
Click to expand...
Click to collapse
I formatted it... I think correctly? NTFS, right? If not, what file system, and what program should I use to format it that way?
I believe Fat32, but I may be wrong on that.
And you can use windows built in formatter.
wiiareonfire said:
I formatted it... I think correctly? NTFS, right? If not, what file system, and what program should I use to format it that way?
Click to expand...
Click to collapse
yep fat 32, dunno windows sorry...
Yup fat32. That what I did. My first hox I soft bricked as well with cwm
Sent from my One X using xda premium
I formatted with FAT32... It's still not accepting the file. TWRP crashes when the adb push command is finished. Is there something I'm missing?
Hey Everyone!
I've been trying to fix this problem for hours with no luck, and while I've found solutions that have worked for others I can't find one that is specific enough to my situation.
So I just got an HTC One X that is locked to Rogers today from Kijiji, and I love it - great phone. The thing I didn't like was the hoard of stock apps that took up about four pages on the app drawer, so I thought hey, I'll root it and delete them. I didn't have any intention of using any custom ROMs, just wanted superuser permission to delete stock apps. Unlocking went fine (finding the token and what not using the app I found on here), and the rooting seemed to go alright until it turned off and didn't start again. I pulled out the cable from the computer and now things are weird..
I can sometimes get into the hboot, but when I try to just start the phone normally it goes to the HTC splash screen and has red writing telling me "this build is for development purposes only", etc etc. I really wanted to get rid of those stock apps but at this point I just want my phone working again. Am I screwed?
I CANNOT find the RUU that I need ANYWHERE. I've tried flashing both Clockwork Recovery and TWRP, and both are apparently successfully installed, but neither will open for me. This is seriously pushing me towards an iPhone
Thanks in advance.
oot-n-aboot said:
Hey Everyone!
I've been trying to fix this problem for hours with no luck, and while I've found solutions that have worked for others I can't find one that is specific enough to my situation.
So I just got an HTC One X that is locked to Rogers today from Kijiji, and I love it - great phone. The thing I didn't like was the hoard of stock apps that took up about four pages on the app drawer, so I thought hey, I'll root it and delete them. I didn't have any intention of using any custom ROMs, just wanted superuser permission to delete stock apps. Unlocking went fine (finding the token and what not using the app I found on here), and the rooting seemed to go alright until it turned off and didn't start again. I pulled out the cable from the computer and now things are weird..
I can sometimes get into the hboot, but when I try to just start the phone normally it goes to the HTC splash screen and has red writing telling me "this build is for development purposes only", etc etc. I really wanted to get rid of those stock apps but at this point I just want my phone working again. Am I screwed?
I CANNOT find the RUU that I need ANYWHERE. I've tried flashing both Clockwork Recovery and TWRP, and both are apparently successfully installed, but neither will open for me. This is seriously pushing me towards an iPhone
Thanks in advance.
Click to expand...
Click to collapse
Yes, please get an iphone! Redpoint73 resource compilation thread, linked in my signature, has all the RUUs and OTAs you would ever need. Good luck.
Sweet, I found the right RUU but it's a zip file and I'm not able to get into recovery mode on my phone. I can get into hboot but rebooting to recovery from there just shows the HTC splash screen with the "developer only" message" then shuts off again. I've tried installing both Clockwork and TWRP with no luck. Any ideas?
exad said:
Yes, please get an iphone! Redpoint73 resource compilation thread, linked in my signature, has all the RUUs and OTAs you would ever need. Good luck.
Click to expand...
Click to collapse
oot-n-aboot said:
Sweet, I found the right RUU but it's a zip file and I'm not able to get into recovery mode on my phone. I can get into hboot but rebooting to recovery from there just shows the HTC splash screen with the "developer only" message" then shuts off again. I've tried installing both Clockwork and TWRP with no luck. Any ideas?
Click to expand...
Click to collapse
The zip file is an OTA and not an RUU. You would need to extract the recovery from that zip file (may be burried deep). Will be called recovery.img or recovery_signed.img or something to that effect. Fastboot flash recovery recoveryfilename.img then boot to that recovery then install the zip through the phone's stock recovery.
I really appreciate the help but I still can't seem to find the proper RUU. I've tried a few and they all fail. If it helps, the number I get when I typed getvar version-main is: 3.17.631.2
Would someone be able to link me to a download for this particular RUU? Thanks
Edit: Thought I'd update a bit of what I've done. Ive found the one I should need in the list you've provided, but there is no link for download. There is the OTA file but not the RUU. I've been using ARUWizard to try to install the RUU, but any one I've tried so far just says it's not the right one. No other error messages, it just tells me to find the appropriate ROM. I can't understand why this is so difficult to find the right one! It seems like all the other models are readily available. Thanks again!
(This looks like the one, but no download link:
3.17.631.2
File Timestamp: 04/12/12
Publically Seen: 08/01/13
Android: 4.1.1
Kernel: 3.4.10-g240d4d5
hboot: 2.14.0000
radio: 0.23a.32.09.29_10.128.32.34
adsp: 31.1.0.45.0815
wcnss: 1031145
tp_syn3202: 3.2_PR1293981
tz: 001.138.010
sbl1: 001.138.003
sbl2: 001.138.004
sbl3: 001.138.005
OTA: OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.3 2.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl 6j.zip (full)
RUU: N/A
Source: evitaul-jb-crc-3.4.10-240d4d5.zip
exad said:
The zip file is an OTA and not an RUU. You would need to extract the recovery from that zip file (may be burried deep). Will be called recovery.img or recovery_signed.img or something to that effect. Fastboot flash recovery recoveryfilename.img then boot to that recovery then install the zip through the phone's stock recovery.
Click to expand...
Click to collapse
Rogers did not release an ruu for that software version. Proceed with the ota the way I explained in my last post or s-off if you want to run the ruu for the older software version.
Sent from my One X using xda app-developers app
For some reason flashing stock recovery doesn't work for me. It says it is successful but when I try to boot to recovery it just goes right back to hboot or sits on the HTC splash screen. I can install TWRP though. Do you know of a nandroid backup for my phone? cid is Roger001
exad said:
Rogers did not release an ruu for that software version. Proceed with the ota the way I explained in my last post or s-off if you want to run the ruu for the older software version.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
oot-n-aboot said:
For some reason flashing stock recovery doesn't work for me. It says it is successful but when I try to boot to recovery it just goes right back to hboot or sits on the HTC splash screen. I can install TWRP though. Do you know of a nandroid backup for my phone? cid is Roger001
Click to expand...
Click to collapse
Fastboot erase cache
Sent from my HTC One X using xda premium
31ken31 said:
Fastboot erase cache
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Try that. Nandroid will not restore your recovery. Only the ROM/kernel/radio files and settings.
I have tried that but unfortunately still can't get into stock recovery. It just goes to the HTC splash and shuts off after a couple of seconds. I know I have the right OTA so if I can get into stock recovery I shouldn't have a problem. Any other suggestions? Am I downloading the wrong version of the recovery?
exad said:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Try that. Nandroid will not restore your recovery. Only the ROM/kernel/radio files and settings.
Click to expand...
Click to collapse
oot-n-aboot said:
I have tried that but unfortunately still can't get into stock recovery. It just goes to the HTC splash and shuts off after a couple of seconds. I know I have the right OTA so if I can get into stock recovery I shouldn't have a problem. Any other suggestions? Am I downloading the wrong version of the recovery?
Click to expand...
Click to collapse
Extract the recovery from the OTA Zip file. It will be in there somewhere. I have done this myself so I know it works.
exad said:
Extract the recovery from the OTA Zip file. It will be in there somewhere. I have done this myself so I know it works.
Click to expand...
Click to collapse
I have as well and worked like a charm
Sent from my HTC One X using xda premium
Sorry, I forgot to mention, if you are not S-OFF, you need to relock after flashing stock recovery and doing fastboot erase cache.
Hey guys, sorry for the late reply, it was a busy long weekend. Here's where I'm at now. I've managed to install cyanogenmod, which booted up fine and everything looked great, but the touch screen didn't work. After some searching I found it it is because the firmware is too new or something, and to downgrade the touch firmware I would have to S-OFF, which would require me to superCID... and I don't know what any of that is and I'd really just like to get back to stock anyway, so..
I've done what you said. Taken the "recovery.img" out of the OTA file for my phone. I've flashed the recovery, relocked the bootloader and erased the cache. Upon booting to recovery it will either splash the HTC screen then go to a black screen (I used to think it was powering off but it looks like it is on but just not displaying anything). Sometimes it will show a image of a phone with a red exclamation mark with a triangle around it.
I feel like I've royally screwed up this phone and I'd just like to get it back to stock.
Thanks!
Edit: The internet is telling me hold volume up + power to get to recovery from the red triangle, but it just reboots me into the bootloader.
exad said:
Sorry, I forgot to mention, if you are not S-OFF, you need to relock after flashing stock recovery and doing fastboot erase cache.
Click to expand...
Click to collapse
You just need to get into stock recovery. Then you can install that ota zip file. I remember having a hard time getting into it too. I would reflash stock recovery to try to remember how I got to the flash screen but my motherboard is out on rma.
Sent from my Sony Tablet S using xda app-developers app
Just posting in case other people have my problem:
I didn't fix it myself, but a friend did for me. He said it wasn't rooted properly so he basically started from scratch and redid that part of it. There is no RUU file for my phone, but he used to AT&T version and it seems to have worked perfectly. Nothing I've noticed so far has any problems.
Anyway, thanks for all the help guys!
exad said:
You just need to get into stock recovery. Then you can install that ota zip file. I remember having a hard time getting into it too. I would reflash stock recovery to try to remember how I got to the flash screen but my motherboard is out on rma.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
oot-n-aboot said:
Just posting in case other people have my problem:
I didn't fix it myself, but a friend did for me. He said it wasn't rooted properly so he basically started from scratch and redid that part of it. There is no RUU file for my phone, but he used to AT&T version and it seems to have worked perfectly. Nothing I've noticed so far has any problems.
Anyway, thanks for all the help guys!
Click to expand...
Click to collapse
Since your friend fixed the issue for you what firmware are you now now. Is it still rooted?
Looks like I have Android version 4.1.1, HTC Sense 4+, and using CleanROM 6.5.0. Is that what you were wondering?
Also, SuperUser is enabled in SuperSU, so that means I'm rooted right?
takylo said:
Since your friend fixed the issue for you what firmware are you now now. Is it still rooted?
Click to expand...
Click to collapse
I was running a rom on my phone working fine until the new update came and I tried to install which sent me to my recovery page (TWRP v2.5) I then factory reset hoping this would work and managed to delete my recoveries and now whenever i restart my phone i either get the message of no os installed or when i install a rom and it actually works i get stuck in a boot loop. im not sure if it is the rom or not (KickDroidXL v5) any help would be appreciated, Thankyou
Your problem is your recovery version, TWRP 2.5 is very buggy and has major issues with wiping and with flashing. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can flash the ROM again and you should be fine.
Sent from my Evita
thanks for that, successfully running twrp 2.6 however when i attempt to install my rom it loaded into recovery as if i chose it from the bootloader screen. when i skipped that one and tried another it got to the htc screen then turned off
thanks again, its now working after looking at your q&a thread! was stuck on the boot loop without the boot.img file, too easy
Guested said:
thanks for that, successfully running twrp 2.6 however when i attempt to install my rom it loaded into recovery as if i chose it from the bootloader screen. when i skipped that one and tried another it got to the htc screen then turned off
thanks again, its now working after looking at your q&a thread! was stuck on the boot loop without the boot.img file, too easy
Click to expand...
Click to collapse
Yeah, you should get s-off either here or here. Then you won't have to worry about flashing the boot.img anymore. You're gonna need s-off to upgrade your firmware anyway, otherwise you're gonna suffer signal losses and random reboots.
so trying to use s-off at the moment and i am not able to boot into recovery (just goes to htc startup screen and phone turns on) i then tried usb debugging where i got the response, needs to be formatted, tried that and said it was impossible as i didnt have any permissions! any ideas?
Neither of the s-off processes need to boot into recovery, what do by mean by that?
Sent from my Evita
so i tried the rum runner method which got stuck when on test 2 it tells me it must ferment longer, i wait in this process for awhile and it attempts to start my phone however it doesnt start up only a black screen with no led (i assume the phone is off) the only way to start is by holding down the power and waiting for the 15 flashes from the buttons then putting it into bootloader, from there i chose recovery and it starts normally without entering the twrp screen.
Test 2: Booting device
Waiting for ADB (19/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[TTTT********************************************************]
Press ENTER to exit
Do you have SuperCID? If so you could try the Facepalm method instead.
Sent from my Evita
timmaaa said:
Do you have SuperCID? If so you could try the Facepalm method instead.
Sent from my Evita
Click to expand...
Click to collapse
no CID, i tried using http://androidforums.com/sensation-4g-all-things-root/636482-guide-how-supercid.html
didnt work came up with an error of too many links after getting to this stage -change CID
fastboot oem writecid 11111111 (eight ones)
okay so i assume it has something to do with the rom, i flashed twrp 2.6 back and recovery works fine! any suggestions on a battery low and stable rom?
Asking which ROM is best/most stable/fastest/prettiest question isn't allowed so I can't answer that, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge. Each user has different tastes anyway, the best way to see which ROM suits you is to flash a few and find out for yourself.
Sent from my Evita
timmaaa said:
Asking which ROM is best/most stable/fastest/prettiest question isn't allowed so I can't answer that, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge. Each user has different tastes anyway, the best way to see which ROM suits you is to flash a few and find out for yourself.
Sent from my Evita
Click to expand...
Click to collapse
thanks for that, didnt know! got a new rom running smoother, however rum runner doesnt work and no method to change the CID works? when changing it to 11111111 it gets an error that the device is not connected
Guested said:
thanks for that, didnt know! got a new rom running smoother, however rum runner doesnt work and no method to change the CID works? when changing it to 11111111 it gets an error that the device is not connected
Click to expand...
Click to collapse
You need to get adb/fastboot and your drivers sorted out. Try using an app called pdanet+ from the Play Store, you download it to your phone and then another component on your PC. When you open the PC component it'll install drivers, it's what got everything working for me.
Sent from my Evita
So I bought a HTC One Mini recently (maybe a month back or so). I loved it, and I decided to root it, (I'm S-ON btw) but I didn't know what custom ROMs were. So I decided to try getting one,(the onedroid one) and failed many times because it said failed. I had TWRP, so when I tried to flash the zip, and when it failed, it said clear cache/davlik or whatever, and I clicked it. Ever since, I've been stuck in a boot loop, and whenever I tried to press recovery, or factory reset, it would say Entering Recovery... at the top, and then the teamwin logo part would flash for a split second and keep flashing for like 3 seconds, and the bootloop would start all over again.
I tried to fastboot erase cache, I even fastboot oem lock 'd, but now it's relocked and whenever I try to enter recovery or factory reset, it just puts me back into the bootloop/bootloader. I really need help on this please.
I've also flashed a new recovery when my bootloader was unlocked, and that didn't work either. Please help, thanks!
alright so update: I fixed that problem, my internal s torage was 0 MB so I formatted my data, and I have storage now as well. I don't know what to do from this point on, I tried factory resetting but theres no OS on the SDCard or anywhere, so... yeah. I'm downloading a stock android 4.2.2/sense 5 (which was what was on my HTC one before **** went down) to see if I can flash it on there and just install it on. Will give feedback when I'm done.
Okay, so now I am completely stuck. I can get into recovery, but I don't know what to do at all now. Help me please.
Omarion23145 said:
Okay, so now I am completely stuck. I can get into recovery, but I don't know what to do at all now. Help me please.
Click to expand...
Click to collapse
download a rom and sideload it. next time do a nandroid backup.
Omarion23145 said:
So I bought a HTC One Mini recently (maybe a month back or so). I loved it, and I decided to root it, (I'm S-ON btw) but I didn't know what custom ROMs were. So I decided to try getting one,(the onedroid one) and failed many times because it said failed. I had TWRP, so when I tried to flash the zip, and when it failed, it said clear cache/davlik or whatever, and I clicked it. Ever since, I've been stuck in a boot loop, and whenever I tried to press recovery, or factory reset, it would say Entering Recovery... at the top, and then the teamwin logo part would flash for a split second and keep flashing for like 3 seconds, and the bootloop would start all over again.
I tried to fastboot erase cache, I even fastboot oem lock 'd, but now it's relocked and whenever I try to enter recovery or factory reset, it just puts me back into the bootloop/bootloader. I really need help on this please.
I've also flashed a new recovery when my bootloader was unlocked, and that didn't work either. Please help, thanks!
Click to expand...
Click to collapse
1st. Rule of hacking up your device.
- Never flash any Rom that's not found in its own device forum. So since your in the mini forum flash only the roms that are available or you'll have a paper weight ( brick ) ... So that's your whole issue with device bootlooping ...
Omarion23145 said:
alright so update: I fixed that problem, my internal s torage was 0 MB so I formatted my data, and I have storage now as well. I don't know what to do from this point on, I tried factory resetting but theres no OS on the SDCard or anywhere, so... yeah. I'm downloading a stock android 4.2.2/sense 5 (which was what was on my HTC one before **** went down) to see if I can flash it on there and just install it on. Will give feedback when I'm done.
Click to expand...
Click to collapse
Again only flash HTC One Mini roms. Not HTC One roms. Your going to nuke your device by not knowing the basics of flashing. So grab a HTC One Mini rom. And if all is still boot looping unlock your bootloader and obtain a stock recovery for this device and flash it then factory reset from bootloader, it will fix corrupt partitions.. Then flash philz latest recovery from our One Mini forums..
Also need to know your hboot version. Is it 2.21 or 2.22??
Omarion23145 said:
Okay, so now I am completely stuck. I can get into recovery, but I don't know what to do at all now. Help me please.
Click to expand...
Click to collapse
Like I said download a Rom from our development forums found in the One Mini forums.. but like I said I need your hboot version to decide what rims you may flash.
Sent from my HTC One mini using Tapatalk
xXminiWHOOPERxX said:
1st. Rule of hacking up your device.
- Never flash any Rom that's not found in its own device forum. So since your in the mini forum flash only the roms that are available or you'll have a paper weight ( brick ) ... So that's your whole issue with device bootlooping ...
Again only flash HTC One Mini roms. Not HTC One roms. Your going to nuke your device by not knowing the basics of flashing. So grab a HTC One Mini rom. And if all is still boot looping unlock your bootloader and obtain a stock recovery for this device and flash it then factory reset from bootloader, it will fix corrupt partitions.. Then flash philz latest recovery from our One Mini forums..
Also need to know your hboot version. Is it 2.21 or 2.22??
Like I said download a Rom from our development forums found in the One Mini forums.. but like I said I need your hboot version to decide what rims you may flash.
Sent from my HTC One mini using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2665746
Would sideloading that (the purestock version) work? My HBOOT is 2.21, S-ON.
Omarion23145 said:
http://forum.xda-developers.com/showthread.php?t=2665746
Would sideloading that (the purestock version) work? My HBOOT is 2.21, S-ON.
Click to expand...
Click to collapse
Yes, but since your s-on you'll have to flash boot.img manually
Sent from my HTC One mini using Tapatalk
xXminiWHOOPERxX said:
Yes, but since your s-on you'll have to flash boot.img manually
Sent from my HTC One mini using Tapatalk
Click to expand...
Click to collapse
Wait so do I just adb sideload it or do I just "fastboot flash boot boot.img" ?
Omarion23145 said:
Wait so do I just adb sideload it or do I just "fastboot flash boot boot.img" ?
Click to expand...
Click to collapse
Adb sideload the Rom.. Flash the Rom... Then enter fastboot and flash boot.img with the command line you just wrote dealing with fastboot
Sent from my HTC One mini using Tapatalk
xXminiWHOOPERxX said:
Adb sideload the Rom.. Flash the Rom... Then enter fastboot and flash boot.img with the command line you just wrote dealing with fastboot
Sent from my HTC One mini using Tapatalk
Click to expand...
Click to collapse
Haha, sorry! Recently got the HTC One Mini so I'm not really used to all this (I just made the switch from iOS to Android a month ago). Anyways, thanks! I'll update if it worked or not.
Omarion23145 said:
Haha, sorry! Recently got the HTC One Mini so I'm not really used to all this (I just made the switch from iOS to Android a month ago). Anyways, thanks! I'll update if it worked or not.
Click to expand...
Click to collapse
HTC are the best android smartphones. Just wait and you'll see
Sent from my HTC One mini using Tapatalk
xXminiWHOOPERxX said:
HTC are the best android smartphones. Just wait and you'll see
Sent from my HTC One mini using Tapatalk
Click to expand...
Click to collapse
Haha. That fixed it! Thanks a lot man, I really appreciate it. I thought it would never get fixed .