One of my friends BRICK his phone and he has no idea how. He has a rooted HTC ONE X on AT&T network with Viper XL (Not even sure what version of the ROM) probably from last december.
It is now stuck on the Booting animation screen and won't get passed that. I am able to access TWRP recovery, but there is not zip files or backups any longer. When I originally flashed this phone for him I had a zip file on the root of the internal SD CARD. It no longer is there and i have not rooted/flashed a phone for almost a year and can't remember.
I tried to fastboot oem lock and it fails (was thinking i could some how get it to boot and install stock jelly bean)
I am able to mount the SD card via TWRP and throw a rom in there via zip, but when i unmount i and go to restore or install i do not see any zip. When I mount again the file i put in the phone no longer exists.
Is there a work around or another way to flash any custom room. I was thinking of CM10 nightly evita... I don't care what rom as long as i can get the phone working again for him.
Is there a way to flash a rom the way we flash boot.img via fastboot where the files can reside on the PC and not the phone? Any assistance/tips would be great. Again i don't care which rom I flash and i have TWRP recovery access. Currently i have CM10 downloaded if hat helps. Thank you in advanced
Is there anything showing up on the sd card at all in TWRP? You could try formatting the sd card in Windows and trying to move a ROM over again.
Sent from my Evita
timmaaa said:
Is there anything showing up on the sd card at all in TWRP? You could try formatting the sd card in Windows and trying to move a ROM over again.
Sent from my Evita
Click to expand...
Click to collapse
Im able to see folders and stuff like the typical android folders. So you are saying i should mount the SD card/try to format the sd card via windows then try to put a zip file in there to see if i can access it? Question.. All i would need to do is flash the boot.img first via fastboot then install the zip via twrp right?
Yeah that's what I mean. Most people flash the boot.img afterwards but I believe you can do it before flashing the ROM.
Sent from my Evita
timmaaa said:
Yeah that's what I mean. Most people flash the boot.img afterwards but I believe you can do it before flashing the ROM.
Sent from my Evita
Click to expand...
Click to collapse
When i format the sd card does it need to be FAT32? What format?
Yep, fat32 is the right format.
Sent from my Evita
timmaaa said:
Yep, fat32 is the right format.
Sent from my Evita
Click to expand...
Click to collapse
Weird i get the same results as before. I formatted the SD card via fat32, through the zip in there, then I unmount the sd card so i can get back to twrp menus to install and android folders are back, but no zip. I am able to successfully copy the cm10 zip there so i don't get it.
Which version of TWRP are you using? And what process are you following when wiping before the flash?
Sent from my Evita
Sounds similar to what happened to me when i did factory reset in bootloader. Others seem to be able to just format in pc and have it work in recovery but it didn't work for me so i just ruu'd to fix it. Since it might have been awhile since you setup his phone you might as well s-off the phone then run latest jb ruu so you have flash latest cm10.1 nightlies which also no longer needs touchscreen downgrade. Afterwards flash latest twrp 2.6.0.0 and copy rom of choice to sdcard and flash.
How will he s-off if he can't boot into the OS?
Sent from my Evita
timmaaa said:
Which version of TWRP are you using? And what process are you following when wiping before the flash?
Sent from my Evita
Click to expand...
Click to collapse
TWRP version 2.3.1.0
Weird I never had issues before and fyi this phone used to be mine so i did all the flashing originally then sold it to a friend of mine and he refused to go back to stock and preferred to stay with viper xl. Now i'm trying to help him out, any thoughts?
DvineLord said:
Sounds similar to what happened to me when i did factory reset in bootloader. Others seem to be able to just format in pc and have it work in recovery but it didn't work for me so i just ruu'd to fix it. Since it might have been awhile since you setup his phone you might as well s-off the phone then run latest jb ruu so you have flash latest cm10.1 nightlies which also no longer needs touchscreen downgrade. Afterwards flash latest twrp 2.6.0.0 and copy rom of choice to sdcard and flash.
Click to expand...
Click to collapse
That's the problem I downloaded the latest RUU from HTC and I don't have a way to flash it or else I would have. Not sure what else I can do here. Anyone have any ideas what I can try next or is this consider a Permanently bricked phone? If it is then i don't want to spend time on it as I have already dedicated over 2 hrs, thanks.
XsMagical posted a fix for corrupted sd cards on this forum a while back, you could give that a try.
Sent from my Evita
timmaaa said:
XsMagical posted a fix for corrupted sd cards on this forum a while back, you could give that a try.
Sent from my Evita
Click to expand...
Click to collapse
So that's what it probably is a corrupted SD CARD? Thanks I will search his posts.
Yeah that's my best guess. It does seem odd that you can still view the Android folders from within recovery though. When you copy something from your pc across does it definitely succeed? I had a wild thought earlier that maybe it had been formatted as read only or something like that.
Sent from my Evita
timmaaa said:
Yeah that's my best guess. It does seem odd that you can still view the Android folders from within recovery though. When you copy something from your pc across does it definitely succeed? I had a wild thought earlier that maybe it had been formatted as read only or something like that.
Sent from my Evita
Click to expand...
Click to collapse
Yeah it successfully completes and I am able to see the file there. Even if i remove the USB cable without unmounting and then plug it back the file is still there. It's when I unmount from TWRP when it then vanishs. I found the article from the guy who wrote a tutorial on how to fix corrupted SD cards, but the link is now broken and no longer exists, doh!
Have you tried upgrading to TWRP 2.6? Not sure if it's gonna help, but anything is worth a try at this stage, right?
Sent from my Evita
timmaaa said:
Have you tried upgrading to TWRP 2.6? Not sure if it's gonna help, but anything is worth a try at this stage, right?
Sent from my Evita
Click to expand...
Click to collapse
Sure it's worth a try. How do i upgrade twrp? It's been a while. Is it just flashing via fastboot? BC if it's a zip remember I can't do that.
Download it from here. Put it in your fastboot folder. Issue these fastboot commands:
fastboot flash recovery "recovery.img"
(whatever the exact filename is, minus the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you can enter recovery from your phone screen.
Sent from my Evita
timmaaa said:
Download it from here. Put it in your fastboot folder. Issue these fastboot commands:
fastboot flash recovery "recovery.img"
(whatever the exact filename is, minus the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you can enter recovery from your phone screen.
Sent from my Evita
Click to expand...
Click to collapse
Great thanks.
Related
I posted in the Q&A of the general One X forum and they told me to post my problem here.
I tried flashing CM10 mod on my One X and because I am a noob I omitted to do a backup of my phone when I wiped everything. I then proceeded as usual, flashed the boot.img then opened the zip to install CM10, then flashed boot.img again but it didnt work.
I don't know how but after that I successfully messed up my phone. I have no ROM, Lost TWRP, have no backup and the only thing I can use is Fastboot and Bootloader.
My phone lo longer appears on my computer so I cannot move files onto it.
I relocked my phone and flashed all the RUU's that I could find. Used the ARUwizard to try the PJ83IMG to no avail.
Every answer I found on the internet did not work so far and I'm getting desperate. Nothing seems to work. Is there a solution?
PS: Is it just me or is the rogers HTC One X harder and more complicated to mod than other versions of the phone? If I were to buy a new phone which one should I buy?
PPS: Buying a new phone is my last option. I do not want to resort to that. I will if I have to.
This is why 1 click unlocks are so bad for the community. People mindlessly unlock their phones and screw it up.
As for your situation, if you run a RUU successfully but your phone still won't boot then you're probably SOL. Go ask Niceppl and see if he can help you.
And no, Rogers is the easiest to mod. HTCDev supports Rogers HOX bootloader unlock. After that, the rest is the same.
thedauntlessone said:
This is why 1 click unlocks are so bad for the community. People mindlessly unlock their phones and screw it up.
As for your situation, if you run a RUU successfully but your phone still won't boot then you're probably SOL. Go ask Niceppl and see if he can help you.
And no, Rogers is the easiest to mod. HTCDev supports Rogers HOX bootloader unlock. After that, the rest is the same.
Click to expand...
Click to collapse
Everytime I try an RUU it says I have the wrong RUU for the device... I tried all of them that I could download. Do I need to do anything else before flashing the RUU maybe?
You didn't SuperCID which is essential for ATT RUU. Right now you basically have a phone with Rogers ID trying to install ATT RUU so it fails.
If you can't get 1.73 rogers RUU working then I have no clue what you can do.
Can you unlock the phone still from fastboot?
If you can have tried to reflash twrp from fastboot?
If it works you may be able to mount the sd card from twrp and move rom to your sd card and flash it.
Just throwing out some ideas since nothing you have tried has worked so far.
Sent from my Nocturnalized Beast
E.Cadro said:
Can you unlock the phone still from fastboot?
If you can have tried to reflash twrp from fastboot?
If it works you may be able to mount the sd card from twrp and move rom to your sd card and flash it.
Just throwing out some ideas since nothing you have tried has worked so far.
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
I cannot mount my virtual sd card to my computer.
I tried to mount my system in TWRP but on my computer it says I cant access it and I need to format it.
Should I format it or will that indefinitely kill my phone.
LimesAreOranges said:
I cannot mount my virtual sd card to my computer.
I tried to mount my system in TWRP but on my computer it says I cant access it and I need to format it.
Should I format it or will that indefinitely kill my phone.
Click to expand...
Click to collapse
Hmm. That sounds like it got corrupted, which may be why your phone cant access anything. Your comp should only be able see the partition that acts like the external sd, so formatting it SHOULD be ok, but get a few more opinions on that before you do it. If so then you can copy a rom on and flash it in twrp.
Could it be -?
I've been trying and trying.
I've been told by someone that maybe I could plug in an SD card reader into my phone. It wasn't recognized.
Could it be my firmware update?
My phone in RUU or ARUwizard or "getvar version-main" says my phone rom version is 1.94.631.3
The rogers RUU out there is 1.73.631.1
Could that be why I cannot install anything on this brick?
LimesAreOranges said:
I've been trying and trying.
I've been told by someone that maybe I could plug in an SD card reader into my phone. It wasn't recognized.
Could it be my firmware update?
My phone in RUU or ARUwizard or "getvar version-main" says my phone rom version is 1.94.631.3
The rogers RUU out there is 1.73.631.1
Could that be why I cannot install anything on this brick?
Click to expand...
Click to collapse
I believe that is the new Rogers OTA. I believe it may have the hboot update which is not rootable. If you have already relocked your boot loader and have the updated hboot, you may have a bookend I am afraid.
All you can do is unlock your bootloader again, push twrp recovery via fastboot, then mount the SD from recovery and copy a rooted custom ROM to your SD and flash it.
Hopefully someone will chime in and tell me I am wrong for your sake....
Beamed from my TN Special Edition powered HOXL on Rogers.
GibMcFragger said:
I believe that is the new Rogers OTA. I believe it may have the hboot update which is not rootable. If you have already relocked your boot loader and have the updated hboot, you may have a bookend I am afraid.
All you can do is unlock your bootloader again, push twrp recovery via fastboot, then mount the SD from recovery and copy a rooted custom ROM to your SD and flash it.
Hopefully someone will chime in and tell me I am wrong for your sake....
Beamed from my TN Special Edition powered HOXL on Rogers.
Click to expand...
Click to collapse
If only my VSD worked... I gave you a thanks anyways. I'll wait for something to come up I guess. I'm kinda fed up with trying and nothing working over and over again.
If you have fastboot why not go through htcdev bootloader unlock? Every in here has suggested it.
Once unlocked flash new recovery and install a rom?
Ps force reboot the phone also by holding the power button for 10seconds.
Thank you for your imput. But my problem lies in the fact I cannot access my phone storage to install a custom rom nor can I flash a working RUU.
LimesAreOranges said:
I cannot access my phone storage to install a custom rom.
Click to expand...
Click to collapse
I found force reboot of phone fixed my sd card when I had a similar problem when I couldnt write to it successfully.
twistedddx said:
I found force reboot of phone fixed my sd card when I had a similar problem when I couldnt write to it successfully.
Click to expand...
Click to collapse
Didnt work. thanks though
Update on the situation
So I just tried TWO different methods and both did not work .
1.) I tried pushing a custom rom (Nocturna) to my SD card.
I cannot access ADB unless I am in TWRP, and pushing a file that big to my SD just crashes my phone. My SD also still cannot mount, I still cannot partition it, I still cannot do anything regarding my sd.
So I tried pushing the zip to other folders on my phone and I got a Process error like before on cmd promt as well as a crash TWRP.
So then I tried a second method.
2.) Downgrading software.
Since my firmware version was 1.94.xxx.x I tried this method http://forum.xda-developers.com/showthread.php?t=1671135
Everything went fine. Bootloader shows 1.11.0000 even though I wrote 1.00.000.0 and in the RUUs it shows 1.00.000.0.
But now that my phone is relocked, suprise! NONE of the RUUs work. I thought this would certainly fix the problem but aparently not.
Any suggestions?
LimesAreOranges said:
So I just tried TWO different methods and both did not work .
1.) I tried pushing a custom rom (Nocturna) to my SD card.
I cannot access ADB unless I am in TWRP, and pushing a file that big to my SD just crashes my phone. My SD also still cannot mount, I still cannot partition it, I still cannot do anything regarding my sd.
So I tried pushing the zip to other folders on my phone and I got a Process error like before on cmd promt as well as a crash TWRP.
So then I tried a second method.
2.) Downgrading software.
Since my firmware version was 1.94.xxx.x I tried this method http://forum.xda-developers.com/showthread.php?t=1671135
Everything went fine. Bootloader shows 1.11.0000 even though I wrote 1.00.000.0 and in the RUUs it shows 1.00.000.0.
But now that my phone is relocked, suprise! NONE of the RUUs work. I thought this would certainly fix the problem but aparently not.
Any suggestions?
Click to expand...
Click to collapse
Edit
If your on 1.94 then you also have the upgraded hboot you can not downgrade and ruu a lower version it will fail you can only ruu 1.94
Sent from my Nocturnalized Beast
E.Cadro said:
Edit
If your on 1.94 then you also have the upgraded hboot you can not downgrade and ruu a lower version it will fail you can only ruu 1.94
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
Thank you!!! So basically I need to wait for it to come out and I'm all set?
LimesAreOranges said:
Thank you!!! So basically I need to wait for it to come out and I'm all set?
Click to expand...
Click to collapse
Yes if there was a 1.94 ruu it might work but I don't think I've seen one but I could be wrong.
On another note am I understanding you correctly you were able to mount your sd via twrp if so I'm surprised it crashed It's how I always move rom zips over to my phone.
Sent from my Nocturnalized Beast
Yeah, my sd is kaput. I hope the RUU will fix it when it comes out. How long do you think it is going to take? I'm paying way too much for a plan if I'm not going to be using a smartphone.
LimesAreOranges said:
Yeah, my sd is kaput. I hope the RUU will fix it when it comes out. How long do you think it is going to take? I'm paying way too much for a plan if I'm not going to be using a smartphone.
Click to expand...
Click to collapse
I recently had this issue cause i was messing around and I hit wipe in TWRP by accented. So it wipped everything on my phone to include the Hboot so no version showed up when i tried to flash the RUU. I grabbed the OTA 2.20 update with the kernal and now everything works minus the battery its drains crazy fast.
Hey guys, I bought a used one x at&t and it came with twrp 2.2.20 and cleanromv5 I wanted to install cyanogenmod 10 and i was downloadingnit through rom toolbox,i also saw that there was twrp version 2.3.3.1 availiable so iinstalled it when i rebooted into recovery it booted into twrp 2.2.2.0 so i rebootedinto into system and then it booted into twrp 2.3.3.1 and everytime i reboot the same thing happens,i even tried wiping the phone and my backup.pls help me out!!!!!
maybe try flash 2.4 TWRP via fastboot?
claytonmas said:
Hey guys, I bought a used one x at&t and it came with twrp 2.2.20 and cleanromv5 I wanted to install cyanogenmod 10 and i was downloadingnit through rom toolbox,i also saw that there was twrp version 2.3.3.1 availiable so iinstalled it when i rebooted into recovery it booted into twrp 2.2.2.0 so i rebootedinto into system and then it booted into twrp 2.3.3.1 and everytime i reboot the same thing happens,i even tried wiping the phone and my backup.pls help me out!!!!!
Click to expand...
Click to collapse
For1n said:
maybe try flash 2.4 TWRP via fastboot?
Click to expand...
Click to collapse
i think that the twrp 2.2.2.0 that came with the phone is from the boot img, but what i dont understand is that when is ekect reboot system option it reboots into twrp 2.3.3.1 even after resetting the phone etc.plsgive me a solution.
Don't use rom toolbox... you could potentially download an incorrect rom
Sent from my evita using Tapatalk 2
InflatedTitan said:
Don't use rom toolbox... you could potentially download an incorrect rom
Sent from my evita using Tapatalk 2
Click to expand...
Click to collapse
what do i do now?
claytonmas said:
what do i do now?
Click to expand...
Click to collapse
i think i flashed the twrp 2.3.3.1 in the boot partition and not recovery.
claytonmas said:
i think i flashed the twrp 2.3.3.1 in the boot partition and not recovery.
Click to expand...
Click to collapse
you'll need to flash at least a new kernel (which is written to the boot partition), and maybe a new ROM. You may also want to flash the newest version of TWRP to your recovery (which is 2.4 now).
So to flash the recovery, you'll want to run this command in fastboot -> fastboot flash recovery openrecovery-twrp-2.4.1.0-evita.img
then boot into your recovery and either use "adb push ROM.zip" or mount the sdcard as removable storage and drag the file from your comp onto your sdcard. Once it is on there, you can flash away (remembering to flash the boot.img if your hboot version is 1.14 or higher).
you'll need to flash at least a new kernel (which is written to the boot partition), and maybe a new ROM. You may also want to flash the newest version of TWRP to your recovery (which is 2.4 now).
So to flash the recovery, you'll want to run this command in fastboot -> fastboot flash recovery openrecovery-twrp-2.4.1.0-evita.img
then boot into your recovery and either use "adb push ROM.zip" or mount the sdcard as removable storage and drag the file from your comp onto your sdcard. Once it is on there, you can flash away (remembering to flash the boot.img if your hboot version is 1.14 or higher).
Click to expand...
Click to collapse
thanks alot.one more question,im going to install cm10 and i think the boot .img of cm 10 has cwm .pls tell me how to flash the boot.img,also i i a factory reset in the bootloaer and now the sd car wont mount in recovery,havn't trie on pc yet.pls reply. thanks a million.
The boot.img of the ROM does not contain a recovery. They are separate.
Sent from my HTC One X using Tapatalk 2
claytonmas said:
thanks alot.one more question,im going to install cm10 and i think the boot .img of cm 10 has cwm .pls tell me how to flash the boot.img,also i i a factory reset in the bootloaer and now the sd car wont mount in recovery,havn't trie on pc yet.pls reply. thanks a million.
Click to expand...
Click to collapse
Skip twrp 4.0 and use 4.1... 4.0 has mounting problems.
.You'll need to install twrp. Youll have to download it from the thread in original dev section. Drop that download in your adb/fastboot folder... right click and choose open cmd prompt here... youll have to google the cmd because i havent used it since may... Enter twrp and mount.
Go to my computer, right click on removable storage and choose format..
You'll need to download a rom on your computer at this point, as formatting takes 20 minutes or so. Personally I recommend the latest viperxl 2.3.1, as this one flashes the boot.img for you so that's one less step you'll have to take.
Once formatted, you should be able to read storage.. so drag the rom into your sdcard. Wipe cache, dalvick, factory reset, system wipe ONLY IN TWRP!!!
you should be good... if not report back but don't do anything crazy.
Sent from my evita using Tapatalk 2
InflatedTitan said:
Skip twrp 4.0 and use 4.1... 4.0 has mounting problems.
.You'll need to install twrp. Youll have to download it from the thread in original dev section. Drop that download in your adb/fastboot folder... right click and choose open cmd prompt here... youll have to google the cmd because i havent used it since may... Enter twrp and mount.
Go to my computer, right click on removable storage and choose format..
You'll need to download a rom on your computer at this point, as formatting takes 20 minutes or so. Personally I recommend the latest viperxl 2.3.1, as this one flashes the boot.img for you so that's one less step you'll have to take.
Once formatted, you should be able to read storage.. so drag the rom into your sdcard. Wipe cache, dalvick, factory reset, system wipe ONLY IN TWRP!!!
you should be good... if not report back but don't do anything crazy.
Sent from my evita using Tapatalk 2
Click to expand...
Click to collapse
Thanks alot guys ,i got my phone running cm 10 but one problem ,my simcard is from Qatar an now im roaming in india ,my sim used to register on airtel n i could send and recieve ,essages aswell as make calls now it registers on tata docomo and i cant make any calls nor receive them.ps :my one x was unlocked.
You will need to add the APN for your carrier. Settings then mobile networks then APN. Menu add son and putthe settings in.
Sent from my HTC One X using Tapatalk 2
First of all I decided to install CM10 without making a backup on TWRP 2 (clever Kyle). Then when it was stuck on the bootanimation for about an hour, I got annoyed and looked through the forums for help. "Factory reset, clear caches before installing etc" So I deleted the ROM, factory reset via TWRP, deleted both cache and then tried to install CM10. Failed.
Then I tried to mount the SD card to my computer to try to find other ROMS to install. Viper and Energy both failed. I then tried CM10, Viper and Energy with CWM 5.8, and the installation of all gets aborted almost instantly, which I am guessing means that it failed on there as well. I then tried ADB, and pushing keeps failing. Does anybody have any ideas at all on how to get just any ROM onto the phone so that I can get the official 4.1 update again (my phone was on 4.1 before trying CM10, so the HBOOT is most likely 4.1 as well). Any advice would be greatly appreciated, because having a £350 paperweight is not what I particularly want, especially considering I have another 9 months contract to run and no spare phone on the same network as my current contract.
kylepont said:
Any advice would be greatly appreciated
Click to expand...
Click to collapse
When you say that installing ROMs fails and adb pushing fails, you should tell us what error messages you get.
If you can still get into bootloader, you're probably going to be fine.
First, check that you can mount your sdcard in recovery. I don't mean mount onto your PC over USB, but just mount the sdcard partition onto the root filesystem.
If you can not get into recovery, re-flash one.
If recovery can not mount the sdcard, then you have to go to the sticky on how to fix unmountable sdcard. It involves flashing a stock recovery and then clearing storage from bootloader.
If your recovery is good and your sdcard is mountable, adb pushing should work. If it doesn't, post error messages. Make sure your sdcard is mounted before you try to push fils to it.
In recovery, format system, data, cache, but not sdcard. Then flash a zip. Then boot back into bootloader/fastboot and fastboot flash the boot image that comes with the rom. (Did you do this last step when flashing other roms?)
If this does not work not for you, describe in detail what you do and what you see. If it does work out, I suggest you make a nandroid backup so you can get back to this state, and S-off the device.
-Jobo
touch of jobo said:
If this does not work not for you, describe in detail what you do and what you see.
Click to expand...
Click to collapse
Sometimes a print screen can speak louder than words. This is the problem, I followed the tutorial posted specifically for my phone and that didn't work. (I used a dropbox link because I could only upload 640 x 640 according to the attachments screen, so you can see the full picture here)
www(dot)dropbox(dot)com/s/ei0y16oar828dh4/Picture1(dot)png
EDIT: I used platform-tools instead of tools because Google decided to move the adb application to that folder in the most recent update
Re: [Q] Soft Brick... Can't install ROMS and pushing does not work.
kylepont said:
Sometimes a print screen can speak louder than words. This is the problem, I followed the tutorial posted specifically for my phone and that didn't work. (I used a dropbox link because I could only upload 640 x 640 according to the attachments screen, so you can see the full picture here)
www(dot)dropbox(dot)com/s/ei0y16oar828dh4/Picture1(dot)png
EDIT: I used platform-tools instead of tools because Google decided to move the adb application to that folder in the most recent update
Click to expand...
Click to collapse
Have you flashed the boot.img?
fastboot flash boot boot.img
Sent from my One S using Tapatalk 2
usaff22 said:
Have you flashed the boot.img?
fastboot flash boot boot.img
Click to expand...
Click to collapse
boot.img? (Noob question incoming, prepare your anuses) What is a boot.img and why do I need it?
kylepont said:
Sometimes a print screen can speak louder than words.
Click to expand...
Click to collapse
You get this:
cannot stat 'ROM.zip': No such file or directory
..because either you have not mounted your /sdcard partition, but more likely because you dont have ROM.zip in your working directory.
Either move ROM.zip to the same directory where adb sits, or use:
adb push C:\full\path\to\rom.zip /sdcard/
Also, is the file youre trying to push actually named 'ROM.zip' or something else, like ViperOneS_2.1.0.zip or so..
Edit:
kylepont said:
boot.img? (Noob question incoming, prepare your anuses) What is a boot.img and why do I need it?
Click to expand...
Click to collapse
The flashing instructions for your ROM will likely state that you have to 'flash the boot image (or boot.img or kernel) in fastboot before booting into the rom.
You can find a file named 'boot.img' inside your rom zip. You have to flash that in fastboot. You can do it before or after flashing the rom, but you must do it before booting into the rom.
kylepont said:
usaff22 said:
Have you flashed the boot.img?
fastboot flash boot boot.img/QUOTE]
boot.img? (Noob question incoming, prepare your anuses) What is a boot.img and why do I need it?
Click to expand...
Click to collapse
Extract the boot.img file from the ROM. Place it in your adb folder. Boot into bootloader, select fastboot and connect to PC. Type command fastboot flash boot boot img
Click to expand...
Click to collapse
touch of jobo said:
You get this:
cannot stat 'ROM.zip': No such file or directory
..because either you have not mounted your /sdcard partition, but more likely because you dont have ROM.zip in your working directory.
Either move ROM.zip to the same directory where adb sits, or use:
adb push C:\full\path\to\rom.zip /sdcard/
Also, is the file youre trying to push actually named 'ROM.zip' or something else, like ViperOneS_2.1.0.zip or so..
Click to expand...
Click to collapse
All the boxes are ticked on the TWRP Mount screen, including System and SD card. And yes, I did make sure that it is:
1) in the same folder as the adb
2) called ROM.zip. I tried re-naming it CM10.zip and tried that in the adb and still no luck, without without the .zip file suffix.
And usaff22, does that involve unzipping the ROM that I am using?
Okay, so the boot.img was flashed successfully. I then went back onto TWRP, tried to flash the zip and it failed...
kylepont said:
I did make sure that it is [...] called ROM.zip. I tried re-naming it CM10.zip and tried that in the adb and still no luck, without without the .zip file suffix.
Click to expand...
Click to collapse
It can not find the local file. Make sure the file is not actually called 'ROM.zip.zip' (with 2x .zip ... you seem to have extensions hidden for most types but it shows .zip).
kylepont said:
Okay, so the boot.img was flashed successfully. I then went back onto TWRP, tried to flash the zip and it failed...
Click to expand...
Click to collapse
Which version of TWRP? I don't use it, but I read that the latest version has issues and you should use the previous version (2.2.0? I dont know).
Also, does it say anything interesting when it fails?
Before flashing the zip, did you format your system, data, cache partitions?
EDIT: After repeatedly trying to adb push, I finally got CM10.zip.zip onto the phone. Flashing took a bit longer than last time, but booting took no time at all. Thank you touch of jobo and usaff22, your advice was a lot of help.
touch of jobo said:
It can not find the local file. Make sure the file is not actually called 'ROM.zip.zip' (with 2x .zip ... you seem to have extensions hidden for most types but it shows .zip).
Click to expand...
Click to collapse
Ah, putting .zip.zip fixed that error, but has now given me a new one: protocol failure
touch of jobo said:
Which version of TWRP? I don't use it, but I read that the latest version has issues and you should use the previous version (2.2.0? I dont know).
Click to expand...
Click to collapse
TWRP v.2.3.3.0. Do you recommend an older build then, or do you think that CWM is a better tool for the job? (I have that on standby)
touch of jobo said:
Before flashing the zip, did you format your system, data, cache partitions?
Click to expand...
Click to collapse
I haven't done that again... Should I do that again? All that is on the system is the boot.img and the CM10.zip folder
kylepont said:
Ah, putting .zip.zip fixed that error, but has now given me a new one: protocol failure
Click to expand...
Click to collapse
I can't help with that adb error. Never seen it. Try searching the forums for it. Sorry. Also, I don't use Windows, so I don't know about driver versions and things.
kylepont said:
TWRP v.2.3.3.0. Do you recommend an older build then, or do you think that CWM is a better tool for the job? (I have that on standby)
Click to expand...
Click to collapse
TWRP and CWM are both fine for flashing ROMs, just not this specific version of TWRP. Since I dont use it myself, I dont know the exact version numbers, but read around a bit and you'll find what worked for others.
Maybe flashing a different recovery will even get rid of your protocol error.
If you've made nandroid backups (I guess you havent or we wouldnt be here.. sorry) you should stay with the same recovery (same 'brand', not same version) or you can't restore them.
kylepont said:
I haven't done that again... Should I do that again? All that is on the system is the boot.img and the CM10.zip folder
Click to expand...
Click to collapse
The CM10.zip should be on your sdcard, not your system partition. You dont need the boot img at all on your device. You need it on your PC in order to fastboot flash it.
Before flashing a ROM you should wipe your 'system', 'data', and 'cache' partitions, but not your 'sdcard' partition. Only if you flash (a newer version of) the same ROM you have operational, then you can sometimes flash without wiping. This is called 'dirty flashing'. But this does not apply in your case.
Successful flash of CyanogenMod, thanks for the help.
I would like to thank touch of jobo and usaff22 for their help, I just hope that somebody else will see this thread and get all of the answers that they need.
Re: [Q] Soft Brick... Can't install ROMS and pushing does not work.
kylepont said:
I would like to thank touch of jobo and usaff22 for their help, I just hope that somebody else will see this thread and get all of the answers that they need.
Click to expand...
Click to collapse
I would rename the zip to something else like sense.zip, place it on the desktop and do adb push C:\Users\username\Desktop\sense.zip /sdcard/
Make sure you use backward slashes for the PC file location, and forward slashes for the phone paste location.
This way we are also providing the full path on the PC.
Also make sure you use the latest adb from the SDK website. You don't need the whole thing, just the platform-tools bit, and replace the files in the new folder with the old one.
Sent from my One S using Tapatalk 2
Oh, while you're here, another problem has come about. Mounting the SD card will not work, and I can't replace it with a new SD card because... Well, there is no removable cover. I know how to fix it, I've read enough on here to find that out, but the only thing that I am missing is a stock recovery image for the S4 version (CID is ORANG001 if that is required) so if anybody knows a link for this then that will be greatly appreciated.
kylepont said:
Oh, while you're here, another problem has come about. Mounting the SD card will not work, and I can't replace it with a new SD card because... Well, there is no removable cover. I know how to fix it, I've read enough on here to find that out, but the only thing that I am missing is a stock recovery image for the S4 version (CID is ORANG001 if that is required) so if anybody knows a link for this then that will be greatly appreciated.
Click to expand...
Click to collapse
You might be able to find an RUU lying around on one of the websites which give RUUs such as androidfiles.org/ruu
I tried looking, but no sign of an orange RUU. An easy way to overcome this would be to change your CID to HTC__001 and use an unbranded RUU.
kylepont said:
the only thing that I am missing is a stock recovery image for the S4 version (CID is ORANG001 if that is required)
Click to expand...
Click to collapse
You can extract the recovery image from any RUU or OTA. Recoveries do not depend on carrier.
But .. if you can see your sdcard from within recovery (when 'choosing' a zip to flash, or from an adb shell or so) and from within Android, then you do not have The Unmountable Sdcard Issue and you should not go through that process. Only if you get an 'Unable to mount /sdcard' error in recovery.
touch of jobo said:
If you can see your sdcard from within recovery (when 'choosing' a zip to flash, or from an adb shell or so) and from within Android, then you do not have The Unmountable Sdcard Issue and you should not go through that process. Only if you get an 'Unable to mount /sdcard' error in recovery.
Click to expand...
Click to collapse
So I just use the stock recovery of any RUU I can find lying around for the HTC One S?
usaff22 said:
I tried looking, but no sign of an orange RUU. An easy way to overcome this would be to change your CID to HTC__001 and use an unbranded RUU.
Click to expand...
Click to collapse
How do I change the CID? Because knowing me, I'll screw it up and brick it if that is possible.
kylepont said:
So I just use the stock recovery of any RUU I can find lying around for the HTC One S?
Click to expand...
Click to collapse
Yes. You can use the recovery image from any RUU or OTA.
But first make sure you need it. The stock recovery thing is only to fix the situation where your sdcard is unmountable and you get that error in recovery.
kylepont said:
How do I change the CID? Because knowing me, I'll screw it up and brick it if that is possible.
Click to expand...
Click to collapse
This is the thread: http://forum.xda-developers.com/showthread.php?t=1671643
It involves extracting, hex-editing, and flashing a critical part of your device. If you make the slightest mistake you have a brick. However, if you read carefully and double check every step, it's not difficult. Many have done it. Read the thread.
Once you have supercid, you may as well get s-off as well. (This is the thread: http://forum.xda-developers.com/showthread.php?t=2155135 ) That way you can always flash anything.
Whatever you decide to do, before you start on anything, read all the instructions to the end, so that you're sure you can complete the process before you start. Also, before you start any process, try to understand what each step does and why it is necessary. That may involve a lot of reading and searching, but that is a Good Thing in the end.
touch of jobo said:
Yes. You can use the recovery image from any RUU or OTA.
But first make sure you need it. The stock recovery thing is only to fix the situation where your sdcard is unmountable and you get that error in recovery.
Click to expand...
Click to collapse
It is unmountable. I tried CWM and TWRP to no avail. Also, I have HBOOT version 2.15 which I heard is a bugger to work with. Also, I got the ZIP file for the stock 4.1, and I read that the stock recovery is in the firmware folder, but I cannot access it. (https://www.dropbox.com/s/kyn9sb5x7gpd7fr/Picture2.png) Then, I tried to get to the CID, following the instructions that you gave me, and I didn't get very far (https://www.dropbox.com/s/g6ik0i3los7unde/Picture3.png)
Hey guys, im trying to flash my htc one xl to viperXL. I've gotten TWRP on it and I made a backup and installed ViperXL but it keeps going to a boot loop.I managed to get it into recovery and it showed that my SDCard was wiped. I couldnt restore it, any help? I will provide more detail if asked. I just want to restore it to stock
Please someone help me ;( I just want to get back to stock.
Did you factory reset in bootloader?
Sent from my Evita
SD has been corrupted. Possibly because you did a factory reset in bootloader (known bug) as mentioned in the previous reply.
Plug the device into a Windows PC, go to device manager and format the SD. Then mount the SD in TWRP and move a ROM to the device, and flash.
timmaaa said:
Did you factory reset in bootloader?
Sent from my Evita
Click to expand...
Click to collapse
redpoint73 said:
SD has been corrupted. Possibly because you did a factory reset in bootloader (known bug) as mentioned in the previous reply.
Plug the device into a Windows PC, go to device manager and format the SD. Then mount the SD in TWRP and move a ROM to the device, and flash.
Click to expand...
Click to collapse
Holy ****! thank you!!!!!! I searched everywhere for a fix. You guys are lifesavers I thought It was bricked for good!!!!!
Zehmistah said:
Holy ****! thank you!!!!!! I searched everywhere for a fix. You guys are lifesavers I thought It was bricked for good!!!!!
Click to expand...
Click to collapse
Also don't forget if you are S-ON that you should flash the boot.img manually after you flash a new ROM. I use TN_WIN_Boot_Installer to ease this task.
drubin333 said:
Also don't forget if you are S-ON that you should flash the boot.img manually after you flash a new ROM. I use TN_WIN_Boot_Installer to ease this task.
Click to expand...
Click to collapse
What's hard about "fastboot flash boot boot.img" to begin with.... Using tools only adds risk
Or flashimagegui
Hi All,
I know this might sound like a redundant topic to you all (since there are many discussions about this on here) but after having gone to MANY threads on forums, MANY different websites and trying MANY different things to correct this, to no avail, i'm still stuck!!! :crying:
I am on Evita...running:
S-ON
HBoot-1.14.0002
Radio-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
AT&T Stock RUU 2.20
I've relocked the device, flashed stock RUU (via fastboot), erased the cache, factory reset, wiping from TWRP recovery.....NOTHING is working!
All the phone does is boot to the "HTC quietly brilliant" screen, hang for a few moments then restart.
Any help someone can provide, would be greatly appreciated! This is my kid's phone and he's bugging about wanting to get it back. Thanks!:good:
Start with rooting step first.....http://forum.xda-developers.com/showthread.php?t=1952038
And for further guide.... http://forum.xda-developers.com/showthread.php?t=1671237
Swyped from T3DRO1CS RedHoXence
Hang on. You'll need to provide more information, saying you've tried many things could mean anything. What exactly have you tried with this phone? I'm assuming it has been unlocked and rooted in the past? Does it have SuperCID?
Also, you said you flashed an RUU via fastboot, but an RUU is an exe file which runs by itself so flashing via fastboot isn't correct. Where did you get this alleged RUU and how did you run it?
@ted77usa
Just wait a minute, we need to properly identify what has been done to this device before going any further.
Sent from my Evita
timmaaa said:
Hang on. You'll need to provide more information, saying you've tried many things could mean anything. What exactly have you tried with this phone? I'm assuming it has been unlocked and rooted in the past? Does it have SuperCID?
Also, you said you flashed an RUU via fastboot, but an RUU is an exe file which runs by itself so flashing via fastboot isn't correct. Where did you get this alleged RUU and how did you run it?
@ted77usa
Just wait a minute, we need to properly identify what has been done to this device before going any further.
Sent from my Evita
Click to expand...
Click to collapse
Thanks so much for taking your time to reply, guys.
Sorry, I didn't give full details. Yes, the phone has been rooted, unlocked and running CM10.1 fine for several months. All of a sudden, it got into this weird bootloop. So, I tried doing some of the tricks that people have posted about relocking the bootloader and flashing the stock rom via fastboot. That didn't work so I tried running the RUU...that didn't work. I went back in and tried a factory reset from the bootloader...nothing. I did a erase cache from fastboot and fastboot flashing the boot.img...still doing it. I went into TWRP recovery and wiping Delvik, Cache and Factory Reset....again, still stuck in bootloop.
Sorry to be lengthy but I'm trying to retrace as many steps as possible for you guys.
Ok, just to be clear, you ran the full RUU exe file?
Sent from my Evita
Stupid question.....
I just had a thought. I have the same exact HOX as my son. It's rooted, unlocked and running same CM10.1 rom as his was and it's running fine. Could I try backing up from my phone's clean nandroid file? So, it ends up just acting as a mirror of my phone?
Yes, you can create a backup on your son's phone using TWRP, copy the backup to a pc, copy it to your phone, and restore the backup. Being that you're s-on though you'll need to manually flash the boot.img from that ROM using fastboot. Do you still have a copy of the ROM zip?
Sent from my Evita
timmaaa said:
Yes, you can create a backup on your son's phone using TWRP, copy the backup to a pc, copy it to your phone, and restore the backup. Being that you're s-on though you'll need to manually flash the boot.img from that ROM using fastboot. Do you still have a copy of the ROM zip?
Sent from my Evita
Click to expand...
Click to collapse
Yes, I do. I always keep a copy of the rom on my phone for emergencies. Now, the other question is, my phone is running 1.85. The messed up phone is running 2.20 (both S-ON). Will it not work or...coming from a nandroid backup, does that not matter? Never tried doing a mirror before...
The firmware version that either phone is on won't make a difference as the backup tool can't touch that partition.
Sent from my Evita
timmaaa said:
The firmware version that either phone is on won't make a difference as the backup tool can't touch that partition.
Sent from my Evita
Click to expand...
Click to collapse
So, I need to just make sure the phone is back to being rooted, unlocked and running TWRP, then mount it and load the nandroid to the SD card. Should I do backup from fastboot or TWRP?
Do you think it will throw it out of that bootloop? I've spent two days on this and I'm ready to be done!
Add long as you have TWRP installed it should work just fine. You have to do the backup using the backup tool in TWRP. When you create the backup on your son's phone you will find it on the sd card at TWRP/backups/serial number, you need to put it in the same file tree on your sd card.
Whether or not it's going to solve your problem I'm not sure, but anything is worth a shot.
Sent from my Evita
timmaaa said:
Add long as you have TWRP installed it should work just fine. You have to do the backup using the backup tool in TWRP. When you create the backup on your son's phone you will find it on the sd card at TWRP/backups/serial number, you need to put it in the same file tree on your sd card.
Whether or not it's going to solve your problem I'm not sure, but anything is worth a shot.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, well..here goes nothing. I will report back the progress! I really appreciate the time for your advice. :good:
It's no problem at all, I'm always happy to help someone get their phone back on track.
Sent from my Evita
timmaaa said:
It's no problem at all, I'm always happy to help someone get their phone back on track.
Sent from my Evita
Click to expand...
Click to collapse
Well, I've got the phone loading into TWRP 2.5.0.0 and when I try to do a wipe Delvik, Cache and Factory Reset...it's telling me it can't find the SD Card.
"E: Unable to mount '/sdcard'
E: Unable to mount storage"
Phone says it's still CID: 11111111
Bootloader: Unlocked.
Any clue how to get the phone to read/write to the SD Card so I can back up to a nandroid?
Did you mention doing a factory reset from bootloader? If so, you'd corrupted the sd card and you'll need to format it using Windows before you can use it. Also, you'll need to flash TWRP 2.6 because 2.5 is full of bugs.
Sent from my Evita
timmaaa said:
Did you mention doing a factory reset from bootloader? If so, you'd corrupted the sd card and you'll need to format it using Windows before you can use it. Also, you'll need to flash TWRP 2.6 because 2.5 is full of bugs.
Sent from my Evita
Click to expand...
Click to collapse
I did! Thanks for remembering. :good:
Any special way I should format the sd card when I do it on Windows? Thanks for the tip on 2.6!
It should come up as fat32 as the default, if not just make sure you format it to fat32 and that's it. It'll probably take twenty minutes or so.
Sent from my Evita
timmaaa said:
It should come up as fat32 as the default, if not just make sure you format it to fat32 and that's it. It'll probably take twenty minutes or so.
Sent from my Evita
Click to expand...
Click to collapse
Got it! Flashed 2.6 in getting ready to back up from my phone's nandroid. Fingers crossed!:fingers-crossed:
After I back up from my nandroid in TWRP, should I flash the boot.img from fastboot?
Yes you'll need to flash the boot.img afterwards, good luck.
Sent from my Evita
timmaaa said:
Yes you'll need to flash the boot.img afterwards, good luck.
Sent from my Evita
Click to expand...
Click to collapse
How can I get it to see my nandroid backup? I have it installed inside the TWRP folder just like it would be on my phone but when I go to Restore, it shows nothing on my sd card. wtf?? I think I'm getting one step closer and another hurdle arrises!! ugh...
Thanks for your help btw, timmaaa!! :good: