Okay, so I decided to do something stupid and forget to backup my HTC One S while rooting. I installed CM10, and it got stuck in a bootloop, so stupid me decided to also do a factory reset and basically delete everything I needed to get out of it. I've tried numerous things, including ADB sideloading a ROM, but whenever I do that, it also gets stuck in a boot loop. I have no idea how to use RUU's, and if anybody could help me to fix my phone, that'd be really really helpful. I'm also kindof a n00b towards this stuff, so step-by-step instructions would be much appriciated Thanks.
~MuZiiX
Is your device S-off and do you have supercid?
Then I believe you can just use any RUU file for your phone to get it back to stock.
A Ruu is basically a file that installs the stock ROM onto your device.
Find the Ruu you need here: http://forum.xda-developers.com/showthread.php?t=2094414
Just download it, connect your phone with a USB and run the Ruu file ( it's an .exe ) on your PC.
I hope this helps. Don't just listen to my advice. I'd wait till someone confirms my advice to be safe/correct. I'm still a bit of a noob after all who's trying to help and learn.
CuzCrostyPwns said:
Is your device S-off and do you have supercid?
Then I believe you can just use any RUU file for your phone to get it back to stock.
A Ruu is basically a file that installs the stock ROM onto your device.
Find the Ruu you need here: http://forum.xda-developers.com/showthread.php?t=2094414
Just download it, connect your phone with a USB and run the Ruu file ( it's an .exe ) on your PC.
I hope this helps. Don't just listen to my advice. I'd wait till someone confirms my advice to be safe/correct. I'm still a bit of a noob after all who's trying to help and learn.
Click to expand...
Click to collapse
I think my device is s-off...i used the HTC One S all in one toolkit, and I have no idea what supercid is :s I've tried a couple RUU's before (don't know if i used them correctly, but i did relock the bootloader when i did it) but none of them helped. It just stayed at a black screen with "htc" in the middle. No error triangles or anything.
Did you run the RUU files like you would run an .exe file on your pc with your phone connected by USB?
I'm not sure how your PC will recognize your phone when you're not in fastboot (bootloader).. Or am I misunderstanding something.
Wait. Can you get into your recovery? Do you still have that installed?
CuzCrostyPwns said:
Did you run the RUU files like you would run an .exe file on your pc with your phone connected by USB?
I'm not sure how your PC will recognize your phone when you're not in fastboot (bootloader).. Or am I misunderstanding something.
Wait. Can you get into your recovery? Do you still have that installed?
Click to expand...
Click to collapse
Yeah, the RUU's were .exe's with my phone connected through USB. I can get into recovery, I have CWM installed.
I'm not sure if CWM has this option, but maybe you can mount your phone through recovery.
Then just place a new ROM on your SD card and flash it.
CuzCrostyPwns said:
I'm not sure if CWM has this option, but maybe you can mount your phone through recovery.
Then just place a new ROM on your SD card and flash it.
Click to expand...
Click to collapse
Well thats what I've been trying to do with the ADB sideloading, because it wont let me mount my sd card. It just says 'ERROR MOUNTING SD CARD" and when I've tryed flashing a new ROM from ADB sideloading, it just gets stuck in a bootloop again.
My best bet is to run the RUU file.
To know which one is the correct one is to see which RUU title fits your phone's Stock 'settings' the best (ie: provider, country, android version)
---------- Post added at 08:42 PM ---------- Previous post was at 08:20 PM ----------
Oh and this thread should be moved to the Q&A forum I just realized
CuzCrostyPwns said:
My best bet is to run the RUU file.
To know which one is the correct one is to see which RUU title fits your phone's Stock 'settings' the best (ie: provider, country, android version)
---------- Post added at 08:42 PM ---------- Previous post was at 08:20 PM ----------
Oh and this thread should be moved to the Q&A forum I just realized
Click to expand...
Click to collapse
I've tried running multiple RUU files, and I have no idea what one to use. The phone when I got it was unlocked, and the android version was ICS I'm pretty sure.
I dunno how to find my stock settings because I cant get past the loading screen.
Did you try flashing the boot.IMG from adb. It sounds to me, that since every ROM you try results in a bootloop that you did not flash the boot.IMG
Sent from my HTC One S using xda app-developers app
did you flash boot.img? most of roms will bootloop without it
Roundtableprez said:
Did you try flashing the boot.IMG from adb. It sounds to me, that since every ROM you try results in a bootloop that you did not flash the boot.IMG
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Pardon my stupidity, but what boot.IMG would I flash? As I stated before, I'm not that good at this kind of stuff :s
MuZiiX said:
Pardon my stupidity, but what boot.IMG would I flash? As I stated before, I'm not that good at this kind of stuff :s
Click to expand...
Click to collapse
the boot.img is located in the zip you downloaded from get.cm
NQNH said:
the boot.img is located in the zip you downloaded from get.cm
Click to expand...
Click to collapse
So what command would I use while flashing the boot.IMG file? (again sorry for not getting this, I just wanna get my phone working again)
MuZiiX said:
Pardon my stupidity, but what boot.IMG would I flash? As I stated before, I'm not that good at this kind of stuff :s
Click to expand...
Click to collapse
You failed to follow the instructions to install the rom. That is why you phone wouldn't boot.
Download or build from source
Download gapps
wipe unless you're upgrading from an earlier CM10 ROM
flash rom in recovery
flash gapps in recovery
unless you have s-off fastboot flash boot boot.img
Click to expand...
Click to collapse
Take your CM10 Rom and open it up. Inside you'll find a file called boot.img. Copy that file to the location where you installed the toolkit. Place it in the data folder there. Then open the toolkit and press the "flash a kernel" button. Just follow the instructions to flash the file.
You phone should now be fixed just reboot it.
Next time, make sure you read the instructions and if you aren't sure what's going don't move forward. Or use the search button. Finally, questions like this one go in the Q&A forum. :good:
dc211 said:
You failed to follow the instructions to install the rom. That is why you phone wouldn't boot.
Take your CM10 Rom and open it up. Inside you'll find a file called boot.img. Copy that file to the location where you installed the toolkit. Place it in the data folder there. Then open the toolkit and press the "flash a kernel" button. Just follow the instructions to flash the file.
You phone should now be fixed just reboot it.
Next time, make sure you read the instructions and if you aren't sure what's going don't move forward. Or use the search button. Finally, questions like this one go in the Q&A forum. :good:
Click to expand...
Click to collapse
Thanks, I'll try that and see how it goes. I totally forgot to do a backup, and I now know that I should do one...and sorry, I'm kinda new to the forum and went here as a last resort.
MuZiiX said:
Thanks, I'll try that and see how it goes. I totally forgot to do a backup, and I now know that I should do one...and sorry, I'm kinda new to the forum and went here as a last resort.
Click to expand...
Click to collapse
It not really a big deal. Your problem is the most common one we see in Q&A. Also, once you finish flashing the boot.img keep in mind that CM10 can take a few minutes to boot the first time.
Also, just a heads up while the toolkits are helpful learning the command yourself actually lets do you a lot more things a lot faster.
heres how to do it using fastboot:
Http://forum.xda-developers.com/showthread.php?t=1752270
Sent from my One S using xda app-developers app
CuzCrostyPwns said:
heres how to do it using fastboot:
Http://forum.xda-developers.com/showthread.php?t=1752270
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Thanks for the quick responses guys, I'm going to try that once I get home. Do I absolutely need USB debugging enabled? Because mine Isn't :s
MuZiiX said:
Thanks for the quick responses guys, I'm going to try that once I get home. Do I absolutely need USB debugging enabled? Because mine Isn't :s
Click to expand...
Click to collapse
Nope, just gotta do it one of the three ways mentioned. If debugging isn't enabled use option 1.
This can either be done via
1 powering off and keeping volume up & the power-button pressed
2 the extended power-menu (If your ROM has it, just select "reboot" & then "bootloader")
3 via adb, connect your phone with the pc, make sure it says "USB debugging connected", go to Android/platform-tools/ & then press shift while you perform a right click with the mouse, then choose "open prompt here", type
Click to expand...
Click to collapse
Related
Apologies in advance if this is the wrong forum.
Today I successfully perm rooted my Doubleshot...
Then I tried to flash CM9 Alpha 5 using CW recovery.. downloaded the .zip...
Flashed it.. hit reboot... and it wont get past the mytouch splash screen.
I've tried flashing other roms, and other alphas.. but they all don't reboot into the rom.
I can still boot into recovery and get into ClockWork..
Any ideas on what I can flash or do to at least get any rom running on here... I'm not even picky at this point... I just wanted something like CM7 or some AOSP.
Thanks in advance.
sinistersai4d4d said:
Apologies in advance if this is the wrong forum.
Today I successfully perm rooted my Doubleshot...
Then I tried to flash CM9 Alpha 5 using CW recovery.. downloaded the .zip...
Flashed it.. hit reboot... and it wont get past the mytouch splash screen.
I've tried flashing other roms, and other alphas.. but they all don't reboot into the rom.
I can still boot into recovery and get into ClockWork..
Any ideas on what I can flash or do to at least get any rom running on here... I'm not even picky at this point... I just wanted something like CM7 or some AOSP.
Thanks in advance.
Click to expand...
Click to collapse
when you say perm root you mean s-off right?
im assuming he's s on....remember to take the boot.img out of the cm9 zip and flash it using fastboot. You can find out more info on how to do it here. Also apology accepted (this should be in general)
Over 500 posts and people still don't know what threads to post questions in...
Thread reported
Yes, perm root using the root tool. I believe that's S-off... but I'm not certain.
sinistersai4d4d said:
Yes, perm root using the root tool. I believe that's S-off... but I'm not certain.
Click to expand...
Click to collapse
its not s-off, go here to get s-off
http://forum.xda-developers.com/showthread.php?t=1576672
my HTC MyTouch 4G Slide using Tapatalk 2
gtmaster303 said:
Over 500 posts and people still don't know what threads to post questions in...
Thread reported
Click to expand...
Click to collapse
Badass
Sent from my myTouch_4G_Slide using xda premium
Let me take advantage of this newb. I got my new device, S-On Unlocked. I restored my modded version of stock and using blues UV 5% kernel. Wifi wont work, and my camera has weird lines on it. But the pics are still good. I just needa fastboot the boot.img righ'?
sinistersai4d4d said:
Apologies in advance if this is the wrong forum.
Today I successfully perm rooted my Doubleshot...
Then I tried to flash CM9 Alpha 5 using CW recovery.. downloaded the .zip...
Flashed it.. hit reboot... and it wont get past the mytouch splash screen.
I've tried flashing other roms, and other alphas.. but they all don't reboot into the rom.
I can still boot into recovery and get into ClockWork..
Any ideas on what I can flash or do to at least get any rom running on here... I'm not even picky at this point... I just wanted something like CM7 or some AOSP.
Thanks in advance.
Click to expand...
Click to collapse
1) This goes in General. I don't know why the mods can't just add a Q&A board to remove the n00b confusion.
2) Fastboot the ROM's boot.img before booting up.
blackknightavalon said:
1) This goes in General. I don't know why the mods just don't add a Q&A board to remove the n00b confusion.
2) Fastboot the ROM's boot.img before booting up.
Click to expand...
Click to collapse
Ok, I'm def S-ON but unlocked and nperm rooted.
Can someone walk me through what to do? How can I fastboot the rom's boot.img?
I'm sorry I'm new to this, that's why I'm using my secondary device to learn. I've been googling anything I can find and it got me to through the root process but now I'm stuck.
xmc wildchild22 said:
im assuming he's s on....remember to take the boot.img out of the cm9 zip and flash it using fastboot. You can find out more info on how to do it here. Also apology accepted (this should be in general)
Click to expand...
Click to collapse
This something I have to do with a PC (as opposed to Mac)? No way to unbrick this thing without methods like this? Just asking, before I try and commandeer a pc.
sinistersai4d4d said:
This something I have to do with a PC (as opposed to Mac)? No way to unbrick this thing without methods like this? Just asking, before I try and commandeer a pc.
Click to expand...
Click to collapse
Did you not read the stickies?
You have to take the bootimage from the rom that you are using and put in a folder and name it so you can reconize it. You follow the command prompt instructions they give in this thread. You have to have some knowlege of a PC in order to be successful. I had the same problems as you did. You can get it to work... Do you know how to use the command prompt for your PC?
Sent from my SGH-T959V using Tapatalk 2
wesomatic said:
You have to take the bootimage from the rom that you are using and put in a folder and name it so you can reconize it. You follow the command prompt instructions they give in this thread. You have to have some knowlege of a PC in order to be successful. I had the same problems as you did. You can get it to work... Do you know how to use the command prompt for your PC?
Click to expand...
Click to collapse
Not really. But I guess I'll start there...
And thanks for everyone's help. Here goes nothing.
sinistersai4d4d said:
Not really. But I guess I'll start there...
And thanks for everyone's help. Here goes nothing.
Click to expand...
Click to collapse
You can just flash back to stock to fix it. Learn to fastboot, then run CM9.
Sent from my Galaxy Nexus using Tapatalk 2
AgentCherryColla said:
You can just flash back to stock to fix it. Learn to fastboot, then run CM9.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks again for all your help...
Last question before I fastboot, is it necessary to have the SDK or ADB to fastboot? Can I fastboot/flash the kernel using Hasoon's all-in-one-kit (the app I used to attain root)? Or is it too late since now the device wont boot and Hasoon "can't find the device"?
I have the boot.img I want in a place where I can locate it. Can I use the command prompt without the SDK/ADB?
Interestingly enough I was able to mount using recovery, and boot a new kernal... phone won't boot but at least it's stuck at a different splash screen lol "mikroms"..
I'm calling this progress.
*UPDATE*
Ok, got it!
I mounted the phone to my computer using recovery and used the Hasoon kit to flash the CM boot image.. then I rebooted and got the mikroms splash screen. That was because the last zip i flashed wasn't CM.. it was the MikRom..
so I went back into recovery, flashed CM.. now I'm good!
sinistersai4d4d said:
Thanks again for all your help...
Last question before I fastboot, is it necessary to have the SDK or ADB to fastboot? Can I fastboot/flash the kernel using Hasoon's all-in-one-kit (the app I used to attain root)? Or is it too late since now the device wont boot and Hasoon "can't find the device"?
I have the boot.img I want in a place where I can locate it. Can I use the command prompt without the SDK/ADB?
Click to expand...
Click to collapse
Of course not. 'Fastboot' is an 'ADB' command. BUT if Hasoon's tool 'can't find device'....that's an ADB error message and you probably don't have all the drivers installed that you need but he has the necessary files included for what you need for 'Unlocked" & recovering from a mess-up. You may as well go ahead & install ADB tho....you'll eventually need it.
---------- Post added at 10:12 AM ---------- Previous post was at 09:59 AM ----------
sinistersai4d4d said:
Interestingly enough I was able to mount using recovery, and boot a new kernal... phone won't boot but at least it's stuck at a different splash screen lol "mikroms"..
I'm calling this progress.
Ok, got it!
I mounted the phone to my computer using recovery and used the Hasoon kit to flash the CM boot image.. then I rebooted and got the mikroms splash screen. That was because the last zip i flashed wasn't CM.. it was the MikRom..
so I went back into recovery, flashed CM.. now I'm good!
Click to expand...
Click to collapse
I believe what you did is 'Flash' a ROM from MikROMs but the kernel didn't go because you have S-On. Take that same '.zip' you just flashed, look inside it and put the file named 'boot.img' where you can find it in the windows 'path' and THEN
'fastboot flash boot boot.img' http://forum.xda-developers.com/showthread.php?t=1508556
You should boot up fine then.
I just recently rooted my HTC One X and and now attempting to unlock the bootloader using HTC Dev. I've gotten my folder set up with all of the correct files (ADB and such) as well as gotten Android SDK installed. So far I've gotten into my command prompt and navigated to my file called "fastboot" that contains all of my adb files. I'm stuck at the fastboot unlock token stage. Whenever I enter that I get this error-
C:\fastboot>fastboot oem get_identifier_token
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
I've played around with it and tried different things, but still get this error. I am in bootloader/fastboot mode so that isn't the problem.
One thing I find interesting is that if I do "adb devices" I get
C:\fastboot>adb devices
List of devices attached
Click to expand...
Click to collapse
So as you can see, it doesn't say there are any devices connected. Is this normal?
Please, if you see what I'm doing wrong it'd be great if you could help me out!
tanner4137 said:
I just recently rooted my HTC One X and and now attempting to unlock the bootloader using HTC Dev. I've gotten my folder set up with all of the correct files (ADB and such) as well as gotten Android SDK installed. So far I've gotten into my command prompt and navigated to my file called "fastboot" that contains all of my adb files. I'm stuck at the fastboot unlock token stage. Whenever I enter that I get this error-
I've played around with it and tried different things, but still get this error. I am in bootloader/fastboot mode so that isn't the problem.
One thing I find interesting is that if I do "adb devices" I get
So as you can see, it doesn't say there are any devices connected. Is this normal?
Please, if you see what I'm doing wrong it'd be great if you could help me out!
Click to expand...
Click to collapse
If I'm not mistaken you need to super Cid before doing that I'd suggest just using and following this thread http://forum.xda-developers.com/showthread.php?t=1672284
Thank you so much! I got that done, unlocked the bootloader, and installed TWRP recovery. Now before I install CleanROM do I have to flash the boot.img using "fastboot flash boot boot.img" or am I good to just flash the whole .zip file through recovery?
tanner4137 said:
Thank you so much! I got that done, unlocked the bootloader, and installed TWRP recovery. Now before I install CleanROM do I have to flash the boot.img using "fastboot flash boot boot.img" or am I good to just flash the whole .zip file through recovery?
Click to expand...
Click to collapse
Depends ...what firmware r u on 1.73 or 1.85
---------- Post added at 02:18 AM ---------- Previous post was at 02:17 AM ----------
If you're on 1.73 you don't have to do anything but on not sure about 1.85 ill get back to you :angel:
1.85
tanner4137 said:
1.85
Click to expand...
Click to collapse
Unless you took the 2.20 update you dodon't have to do that so go ahead and flash clean rom and enjoy 99.7% ssure
Could I see where you found this?
tanner4137 said:
Could I see where you found this?
Click to expand...
Click to collapse
A couple different threads now I'm 99.9 percent sure you isn't have to flash the boot img. U can post in the q and a section if you really must you'll get a straight answer there
First you do have adb files installed? If you do make sure you install the drivers. Just install HTC Sync and make sure that it's not running in the task bar. Then try again. I'm almost sure that the drivers are missing in this case.
Sent from my HTC One XL using xda premium
TheNightHawk223 said:
First you do have adb files installed? If you do make sure you install the drivers. Just install HTC Sync and make sure that it's not running in the task bar. Then try again. I'm almost sure that the drivers are missing in this case.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Lol, thanks. If you read above you can see that I solved that. What I'm needing to know now is if I have to flash a boot.img before I flash a ROM, or if I can just download the .zip and flash it from recovery.
tanner4137 said:
Lol, thanks. If you read above you can see that I solved that. What I'm needing to know now is if I have to flash a boot.img before I flash a ROM, or if I can just download the .zip and flash it from recovery.
Click to expand...
Click to collapse
Sorry I'm just incredibly lazy and forget to read sometimes , well since you never took the 2.20 RUU/OTA you just have to run the zip unless the instructions for the rom specificly says to flash the boot.img.
Sent from my HTC One XL using xda premium
Alright guys here's the deal. I went through the htcdev root process. everything was running fine for awhile. installed cm10. now all i can access is recovery and bootloader. i have no access to the sdcard at all. there are no backups or anything in place on the sd card to access through recovery. i am at a complete loss as to what to do. i have gone through and attempted to install ruu's with no success. i have pulled the boot and recovery images off said ruu's to no success. i am at a complete loss. HELP!!!
bardoom said:
Alright guys here's the deal. I went through the htcdev root process. everything was running fine for awhile. installed cm10. now all i can access is recovery and bootloader. i have no access to the sdcard at all. there are no backups or anything in place on the sd card to access through recovery. i am at a complete loss as to what to do. i have gone through and attempted to install ruu's with no success. i have pulled the boot and recovery images off said ruu's to no success. i am at a complete loss. HELP!!!
Click to expand...
Click to collapse
What HBoot are you on? Have you been using the All In One Tool? If so, you're better off doing the commands manually. Don't get me wrong its a handy tool but when you do it yourself you understand more about the whole process and what not.
hboot
HBOOT-1.14.004
RADIO-1.08ts.50.05.16
i was using the toolkit initially. i used it to unlock the bootloader to being with. Once I started having issues I starting typing everything out manually. I have gone through the steps of the stickied thread at the top of the forum with no luck.
bardoom said:
HBOOT-1.14.004
RADIO-1.08ts.50.05.16
i was using the toolkit initially. i used it to unlock the bootloader to being with. Once I started having issues I starting typing everything out manually. I have gone through the steps of the stickied thread at the top of the forum with no luck.
Click to expand...
Click to collapse
It sounds like you're having the same problem as I was having. Don't worry just be upset that there's no S-Off for the One S yet, I know I am. Anyway! If you want to go back to stock you have to use the European stock RUU (2.31 or 2.21). Because we have that dreaded 1.14 HBoot we can't use the T-Mo RUU anymore because they don't match up.
Flash the boot.img and the recovery.img from the European RUU. If you can't find them just start up the RUU and open an explorer window and type "%temp%" into the address bar. Find the folder with the .zip named "rom" in it (it'll be less confusing if you delete what you can from the temp folder before hand), open it up and find "boot_signed.img" and "recovery_signed.img" copy them to your platform tools folder and flash.
After that Relock your bootloader and flash the RUU. Below is a link to posts by Football and Sneaky Ghost for the RUU (it's easier to get it from Sneaky's dropbox link in his signature). Let me know if it works and show some love to the thanks button if it does. Good luck!
Hit that thanks button for Sneaky
http://forum.xda-developers.com/showpost.php?p=32262143&postcount=153
And again for Football since he gets all these RUU's out
http://forum.xda-developers.com/showpost.php?p=23542379&postcount=1
alrighty then
do you have any idea if there are any mirrors for this file?
bardoom said:
do you have any idea if there are any mirrors for this file?
Click to expand...
Click to collapse
Bro... the links at the bottom of my post have what you need... did you read what I said?
these links require you to be a premium member of the site to download. which i am not.
bardoom said:
these links require you to be a premium member of the site to download. which i am not.
Click to expand...
Click to collapse
"(it's easier to get it from Sneaky's dropbox link in his signature)" SneakyGhost has a dropbox link in his signature https://www.dropbox.com/sh/nnpoodr69b7ibmk/qdQyL3RBwE you don't even need an account to download it. Even if you do need an account, dropbox is a very useful service and it wouldn't hurt to sign up. But I am sure you don't need an account because I've had people download from a public folder before without an account and I was not logged in when I downloaded from his public folder.
It's so true that the all in one tool takes the learning out. However I would use the post in the stickies on how to unbrick and solve mounting issues. As long as you can still get in and out of recovery. You can manually install the boot.IMG then flash the utb Rom to be refreshed. But if you want to go back to stock. Dude here is giving great guidance and advise.
Sent from my HTC One S using xda app-developers app
---------- Post added at 09:28 PM ---------- Previous post was at 09:24 PM ----------
cannondale0815 said:
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Code:
adb push utb.zip /sdcard
6) While still in CWM, flash the zip.
The trick here is that only the stock recovery is capable of restoring access to the sdcard by it's proprietary "clear storage" option.
Good luck!
-J
Click to expand...
Click to collapse
Sent from my HTC One S using xda app-developers app
alright. i see it now. i was going to the filefactory folder and not the dropbox acct. I'm in the process of downloading the extracted RUU for 2.31 and I will post when I have an update. Thanks again for all of your help so far.
I've followed every guide I can find. I've flashed nandroid backup. I've attempted flashing ruu's with no success. I've done everything I can think of and nothing is getting me out of this bootloop. What am I missing?!?!!1
finally got it back up a running. thanks again for all your help on this.
Good job dude. Tell us how you did it. It may help others.
Sent from my HTC One S using xda app-developers app
Hey guys,
i flashed Paranoid Android and gApps last night, and it froze during the loading screen. I went back to recovery, and i could not install anything from TWRP. It showed no files, and my phone said there was no OS installed. My computer would not read my phone after this. I am on a Windows XP machine right now because i normally use a Mac but i cant flash images through that.
How do i fix this? and this is my first rom flash, so i would appreciate all the help!
Thanks!
Ill try to post pictures later, but they will be images taken from an iphone. I just want to get back to ParanoidAndroid!
Not enough information. When you plug your phone in does it ask you to format it? Can you still get to twrp? Where did you get the paranoid android from?
Sent from my VENOMized HoxL
area51avenger said:
Not enough information. When you plug your phone in does it ask you to format it? Can you still get to twrp? Where did you get the paranoid android from?
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
I got it from an xda link. I don't have it cuz I'm on my fiancés iPhone four. It can get into twrp but It shows no files when I try to install. And I I plug in to the computer it just makes noise and goes to htc screen with red lettering.
You probably just did this:
http://forum.xda-developers.com/showpost.php?p=38471340&postcount=11
Try the above fix, and come back here, and tell is if it worked or not.
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
experimentation said:
I got it from an xda link.
Click to expand...
Click to collapse
That's amazingly vague. What area51avenger is trying to figure out, is if you tried flashing a ROM meant for the quad core version of the One X (code named Endeavoru), which can be real bad news. If you can figure out what you flashed, and tell us, it would be helpful.
But the fact your screen still comes on is good news. Try to format the SD, and you might have to install TWRP again, but I don't think it will be that hard to get you fixed.
redpoint73 said:
You probably just did this:
http://forum.xda-developers.com/showpost.php?p=38471340&postcount=11
Try the above fix, and come back here, and tell is if it worked or not.
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
That's amazingly vague. What area51avenger is trying to figure out, is if you tried flashing a ROM meant for the quad core version of the One X (code named Endeavoru), which can be real bad news. If you can figure out what you flashed, and tell us, it would be helpful.
But the fact your screen still comes on is good news. Try to format the SD, and you might have to install TWRP again, but I don't think it will be that hard to get you fixed.
Click to expand...
Click to collapse
It was a file named pa-evita.zip from xda somewhere. I am jut trying to figure out how to get twrp to reinstall it. Since nothing shows up now.
experimentation said:
It was a file named pa-evita.zip from xda somewhere.
Click to expand...
Click to collapse
That's good news. Its the proper version of PA for our phone (EVITA) rather than the quad core varian (EVDEAVORU).
experimentation said:
I am jut trying to figure out how to get twrp to reinstall it. Since nothing shows up now.
Click to expand...
Click to collapse
I'd try to reformat SD first, as already mentioned.
If that doesn't work, you can re-install TWRP a couple ways:
1) Flash using fastboot. You will find a fastboot flashable version if you search the TWRP thread (posted by another user). http://forum.xda-developers.com/showthread.php?t=1677447
2) Use the All-In-One Toolkit: http://forum.xda-developers.com/showthread.php?t=1952426
---------- Post added at 10:26 AM ---------- Previous post was at 10:24 AM ----------
And the original cause of all this may be very simple: you may have forgotten to flash boot.img using fastboot, after flashing Paranoid Android. This is mandatory if you are hboot 1.14 or higher, and S-On.
When the phone failed to boot, did you go into hboot and do a factory reset?
redpoint73 said:
That's good news. Its the proper version of PA for our phone (EVITA) rather than the quad core varian (EVDEAVORU).
I'd try to reformat SD first, as already mentioned.
If that doesn't work, you can re-install TWRP a couple ways:
1) Flash using fastboot. You will find a fastboot flashable version if you search the TWRP thread (posted by another user). http://forum.xda-developers.com/showthread.php?t=1677447
2) Use the All-In-One Toolkit: http://forum.xda-developers.com/showthread.php?t=1952426
---------- Post added at 10:26 AM ---------- Previous post was at 10:24 AM ----------
And the original cause of all this may be very simple: you may have forgotten to flash boot.img using fastboot, after flashing Paranoid Android. This is mandatory if you are hboot 1.14 or higher, and S-On.
When the phone failed to boot, did you go into hboot and do a factory reset?
Click to expand...
Click to collapse
Honestly I don't remember. I was rebooting after flashing gapps and I just rebooted nornally, not using flash boot. So after work today ill try all this and report back. Thanks guys. I do love my phone running paranoid!!
experimentation said:
Honestly I don't remember. I was rebooting after flashing gapps and I just rebooted nornally, not using flash boot. So after work today ill try all this and report back. Thanks guys. I do love my phone running paranoid!!
Click to expand...
Click to collapse
Well, update. I am trying to mount my phone to my windows xp machine, and i cannot get it to read. I can get to device manager, but I cannot figure out how to format sd. I know I am probably being a noob about this, I just want this to get solved. Help!
Ok good news. I have it formatted. What is my next step?
experimentation said:
Ok good news. I have it formatted. What is my next step?
Click to expand...
Click to collapse
1. Install TWRP - You can find the lastest version here
Once you've downloaded it put it in your adb/fastboot folder. In your adb/fastboot folder shift + right click > open command window here.
Type, adb reboot bootloader, enter. Now that your phone is in the bootloader and says FASTBOOT USB.
Type in the cmd that is open, fastboot flash recovery openrecovery-twrp-2.4.2.0-evita.img, enter. This should install the newest TWRP recovery.
2. Now make sure that pa-evita.zip and a copy of the boot.img from the zip as well as the gapps.zip for the rom is in your adb/fastboot flolder.
type in cmd, fastboot flash boot boot.img, enter. Now on your phone goto BOOTLOADER and hit the power button, scroll down to RECOVERY and hit the power button again rebooting your phone into TWRP recovery.
type in cmd, adb push pa-evita.zip /sdcard/TRWP, enter
type in cmd, adb push gapps.zip /sdcard/TRWP, enter
3. From TWRP.
Install > navigate to the sdcard/TWRP > pa-evita.zip > Swipe to confirm Flash > Wipe Cache & Dalvik > Back > Home
Install > navigate to the sdcard/TWRP > gapps.zip > Swipe to confirm Flash > Wipe Cache & Dalvik > Back > Reboot System.
All the bold adb and fastboot commands are copy paste-able but make sure the file names are correct
Hi all,
Apology if this questions may already been ask millions of time but I am really stucked at the moment and hoping that someone may guide me to the correct direction.
I have got HTC One X-LTE (Evita)
I managed to get S-OFF and also CID - 111111
It has TWRP 2.6
The last time I got it working was on the STOCK 4.2.2 I downloaded from the XDA - then I got into the issues of rebooting and loosing signal from time to time. so I went into my TWRP backup I had and reflashed it using my old backup made from my TWRP.
the reflashed failed and now I can only boot up to the HTC logo and then black screen.
I can get to the TWRP recovery and I have got fastboot and ADB on my PC.
When I run the fastboot devices command --> it shows device connected BUT when i try ADB command ---> no device is found.
It will be much appreciated if someone can guide me to the right direction as I am really stucked at the moment not sure where to start.
I tried searching in the forum but I don't think I went to the correct area/tutorial.
Please help
Thank you
When you made your twrp backup did you select system,data, and boot? If it's hanging at the HTC screen it seems there is not boot.img installed or one that is incompatible with your backup. Open whatever Rom your backup is made from and copy the boot.img to your fastboot directory. Then reboot the phone into fastboot mode and flash the boot.img using this command.
Fastboot flash boot boot.img
Then reboot the phone and see what happens
Sent from my HTC One XL using Xparent Red Tapatalk 2
ImagioX1 said:
When you made your twrp backup did you select system,data, and boot? If it's hanging at the HTC screen it seems there is not boot.img installed or one that is incompatible with your backup. Open whatever Rom your backup is made from and copy the boot.img to your fastboot directory. Then reboot the phone into fastboot mode and flash the boot.img using this command.
Fastboot flash boot boot.img
Then reboot the phone and see what happens
Sent from my HTC One XL using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
Thanks for the reply.
When looking at the TWRP backup I copied into my PC - does not have the .img - the one I can find is MD5
Can I use the existing ROM I donwload from XDA like : EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge.zip
when I extracted EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge.zip - I can see the "boot.img" can I use this one?
Thanks
ardabelati said:
Thanks for the reply.
When looking at the TWRP backup I copied into my PC - does not have the .img - the one I can find is MD5
Can I use the existing ROM I donwload from XDA like : EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge.zip
when I extracted EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge.zip - I can see the "boot.img" can I use this one?
Thanks
Click to expand...
Click to collapse
I had a somewhat similar experience with Viper 4.0 ROM - I managed to get Cyanogenmod installed correctly (particularly this one). Take a shot and see if it works - atleast your phone will be up and working.
sandys1 said:
I had a somewhat similar experience with Viper 4.0 ROM - I managed to get Cyanogenmod installed correctly (particularly this one). Take a shot and see if it works - atleast your phone will be up and working.
Click to expand...
Click to collapse
Hi Sandy,
I tried the link but I think it is broken link.
Can you please let me know which one is the link .
Cheers
ardabelati said:
Hi Sandy,
I tried the link but I think it is broken link.
Can you please let me know which one is the link .
Cheers
Click to expand...
Click to collapse
hmm - Im on ROM dated 09/13, which is not present now. Your best bet would be http://get.cm/get/aOM
Also remember to flash Google Apps (play store, etc.) which is packaged separately here - http://goo.im/gapps/gapps-jb-20130813-signed.zip
ardabelati said:
Hi Sandy,
I tried the link but I think it is broken link.
Can you please let me know which one is the link .
Cheers
Click to expand...
Click to collapse
Did it work finally ?
sandys1 said:
Did it work finally ?
Click to expand...
Click to collapse
Hi Sandy
Thank you again for your help
I finally got my phone at least booting again.
What i did was I went to the fastboot and then correct to the PC and when it was asking for format the drive, I did format it (fingers crossed) and luckily it let me see the ROm I downloaded from the Stock 4.2.2 Turge version.
Now my problem is that the phone keeps rebooting.
I don;t know how to flash the kernel as suggested on the front page of the thread.
What is the most stable ROM at the moment?
I want to learn how to flash and fix this - I have kept reading post after post but I still can not get myself to where I want it to be which is fixing the reboot issue from the STOCK 4.2.2 Turge version.
I am a real newbie so I am not too familar with some of the fancy terms people use.
Any help is greatly appreciated.
Thanks again
ardabelati said:
Hi Sandy
Thank you again for your help
I finally got my phone at least booting again.
What i did was I went to the fastboot and then correct to the PC and when it was asking for format the drive, I did format it (fingers crossed) and luckily it let me see the ROm I downloaded from the Stock 4.2.2 Turge version.
Now my problem is that the phone keeps rebooting.
I don;t know how to flash the kernel as suggested on the front page of the thread.
What is the most stable ROM at the moment?
I want to learn how to flash and fix this - I have kept reading post after post but I still can not get myself to where I want it to be which is fixing the reboot issue from the STOCK 4.2.2 Turge version.
I am a real newbie so I am not too familar with some of the fancy terms people use.
Any help is greatly appreciated.
Thanks again
Click to expand...
Click to collapse
It sounds like it might be a bad download or something. I noticed u never mentioned wiping the phone before flashing, Are u clean wiping? And also what hboot are you on?
Sent from my HTC One X using xda app-developers app
ardabelati said:
Hi Sandy
Thank you again for your help
I finally got my phone at least booting again.
What i did was I went to the fastboot and then correct to the PC and when it was asking for format the drive, I did format it (fingers crossed) and luckily it let me see the ROm I downloaded from the Stock 4.2.2 Turge version.
Now my problem is that the phone keeps rebooting.
I don;t know how to flash the kernel as suggested on the front page of the thread.
What is the most stable ROM at the moment?
I want to learn how to flash and fix this - I have kept reading post after post but I still can not get myself to where I want it to be which is fixing the reboot issue from the STOCK 4.2.2 Turge version.
I am a real newbie so I am not too familar with some of the fancy terms people use.
Any help is greatly appreciated.
Thanks again
Click to expand...
Click to collapse
You can either flash the kernel, which can be found in the Android Development section, flashing the kernel is just like flashing a ROM, just install in Beastmode. Or you can upgrade your firmware to 2.15, the instructions are I'm the first post of the ROM thread.
Asking which ROM is best/favorite/most stable is against the rules so we can't answer that question.
When you say the phone keeps rebooting, does it ever make it into the OS or is it boot looping (showing the boot animation then starting over)?
Sent from my Evita
timmaaa said:
You can either flash the kernel, which can be found in the Android Development section, flashing the kernel is just like flashing a ROM, just install in Beastmode. Or you can upgrade your firmware to 2.15, the instructions are I'm the first post of the ROM thread.
Asking which ROM is best/favorite/most stable is against the rules so we can't answer that question.
When you say the phone keeps rebooting, does it ever make it into the OS or is it boot looping (showing the boot animation then starting over)?
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply
When you said that flashing kernel is the same as flashing ROM, I did it By going to TWRP and the press install and locate the zip file. Is this what should be done?
What is beast mode?
Sorry for the basic questions
Thanks
Yeah that's how you install the kernel. It must be done after you install the ROM. I kinda worded my reply a bit weird, sorry about that. Beastmode is the name of the kernel, you can find it here:
http://forum.xda-developers.com/showthread.php?t=2165880
Sent from my Evita
I did try to flash it through recovery but it always failed. Not sure why. I copied the kernel zip file into my phone sd and then I went to recovery and press the install and located the kernel zip file but still failed.
Sent from my HTC One XL using Tapatalk 2
Which recovery version are you using?
Sent from my Evita
Recovery is 2.6.3.
The process failed on not able to fine the MD5 file or something like that. We don't need to extract the Zip file do we?
Cheers
Disable md5 checking in settings. You never need to extract a kernel or ROM zip.
Sent from my Evita
timmaaa said:
Disable md5 checking in settings. You never need to extract a kernel or ROM zip.
Sent from my Evita
Click to expand...
Click to collapse
I have checked the setting in TWRP and nothing is ticked.
When I flash the zip, it is still saying "failed due to md5 does not exists".
I am not sure which should be address first but I now noticed that there is an error : "unable to locate storage device"
also came out.
When I plug my phone to PC I can see the storage but why it is saying "storage device not found" in TWRP?
Thanks