Okay. Here's the deal.
My friend gave me a used HTC One S. My idea was to flash a new custom ROM on it (preferably something like CM12). He told me it was rooted, so it seemed like it was no problem. Although, it was S-On.
When I turned out on the phone, I first noticed some things. It stayed on the "HTC: Quietly Brilliant" logo, however, it had that red "This build is for development purposes only" text underneath it. After waiting almost an hour, I realized something was up. After a few attempts, I was able to get into bootloader and loaded up TWRP recovery. I poked around in the files to see what the issue could be, when I realized something. The phone was Romless! The /sdcard folder was completely empty, besides a TWRP folder. If I moved up one level, the only folders were:
and-sec
boot
cache
data
dev
devlog
etc
sdcard
license
proc
recovery
res
root
sbin
supersu
sys
system
tmp
usb-otg
and they were all empty.
Okay, so it didn't have a ROM. No big deal, right?
My first idea was to use the CM12 installer. It didn't work; for some reason it thought the device was a Samsung galaxy S2?!
So my next idea was to connect it to my pc and transfer files. Unfortunately, since it was in TWRP, it wouldn't show up on my PC so I could edit the files. So, first I tried mounting storage, but it failed, saying "E: Can't mount /sdcard". So, my next idea was to use USB OTG. After putting the CM12 file on my flash drive and connecting it to the phone, it showed up and I was able to browse the files to install CM12. On my first try, I flashed it straight from the flash drive and rebooted. When this happened, it was on the HTC logo for a good minute, then it rebooted again straight into TWRP. After that, I decided that maybe I'd have to create folders inside /sdcard. So, after a few minutes, I created the empty folders Android, Download, DCIM, Pictures, etc. in /sdcard. I copied CM12 into download and flashed it. Instant failure, giving the same "Can't mount scard" errors.
I tried rebooting. But when I did, all the folders I made as well as CM12.zip were gone!
I also tried using adb push and sideload commands. It still did not work. Still got sd card mounting errors.
Interesting. With that, I turned to XDA for help. After reading a few forums, I downloaded Hasson's All-In-One-Toolkit and tried reinstalling TWRP recovery. No luck. After that, I switched the recovery to PhilZ Touch 5. Still, once again, got internal sd errors for mounting.
Not knowing what else to do, I settled on one other option. RUU. After doing some searching online and finding the right RUU, which was RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2 .exe.
I followed instructions online about RUU and looked for a temp file. While I expecting only one ROM.zip, there were two files called rom_01.zip and rom_02.zip. They both had the same files with the same file names in them, the only difference was rom_01. zip was 35 Mb, while rom_02 was 681 mb. I tried both. They'd give me the same "please flush again immediately" the first time, but after flashing again, every time it would give me "signature verify fail."
With that, I am unsure what else to do. The only thing on the phone at the moment is PhilZ touch 5. Mounting storage does not work, and installing via sideload doesn't either. Any help with this situation is very, very appreciated.
I apologize for how long this post was.
http://forum.xda-developers.com/showthread.php?t=1630459
In order to see anything on system in TWRP, you should have mounted it before (go to Mount and check system). But that's not the point.
You didn't say anything about which One S do you have (S4/Ville or S3/Ville C2),which version of TWRP you have and most important which hboot you're on.
For most ROMs you'll need 2.15 hboot, also because you're S-On you must flash kernel in fastboot after you flash the ROM. You flashed CM12 so I presume you have 2.15 hboot but you never said you flashed also the kernel in fastboot mode. That's why phone don't boot
Sent from nowhere over the air...
Rapier said:
In order to see anything on system in TWRP, you should have mounted it before (go to Mount and check system). But that's not the point.
You didn't say anything about which One S do you have (S4/Ville or S3/Ville C2),which version of TWRP you have and most important which hboot you're on.
For most ROMs you'll need 2.15 hboot, also because you're S-On you must flash kernel in fastboot after you flash the ROM. You flashed CM12 so I presume you have 2.15 hboot but you never said you flashed also the kernel in fastboot mode. That's why phone don't boot
Sent from nowhere over the air...
Click to expand...
Click to collapse
The phone is S4/Ville.
It's on 2.15 hboot as well.
The TWRP version it had was 2.5.0.0.
Related
Here is the history
NS4G
Rooted in early January and flashed an ICS rom (Vgomez)
Then flashed CM9 alpha 20 and made a couple of Nandroid backups over the course of the month.
Briefly flashed the Stock 4.0.4 rom. Didn't like it.
Restored via Nandroid to the CM9 alpha 20
everything was great.
Yesterday I went to make a call and the phone locked. I tried to power down...no luck. So I pulled the battery.
It never came back. (got some type of 'android lost encryption' error)
I power up the phone and it brings me to a brand new user page where I would have to login with my gmail creds.
Then it starts throwing errors like calander stopped working, google settings app stopped working, android.process.acore stopped working. etc...
I can boot to CWM and but it will not allow me to recover to anything other than what I described above.
I can mount the USB partition and it appears to allow me to copy files into that partition. However, if I try to flash a ROM, Kernel, etc. It terminates the operation and says the file is bad.
When I reboot CWM and go to view the USB partition again, those files that I had just moved into the partition are now missing.
It is as though I have not copied the file at all.
Without access to the allow USB debug setting, I cannot adb anything.
I have tried the Samsung yellow boot/restore (odin?) when I click the 'Download files' button it throws a generic error and halts the process.
At this point, I don't care if the phone is put back to stock because I won't lose anything important. I just want to get my phone working again.
edit: I do have access to fastboot. I have wiped everything and tried to boot and it sticks in the bootloader (good?) I assume that when I try to flash one of the ROMs that I do have in the USB partition...it will go back to the way it was. (errors and all)
I suspect that the Kernel is corrupt. How would I fix this without being able to write to the USB partition?
deralaand said:
Here is the history
NS4G
Rooted in early January and flashed an ICS rom (Vgomez)
Then flashed CM9 alpha 20 and made a couple of Nandroid backups over the course of the month.
Briefly flashed the Stock 4.0.4 rom. Didn't like it.
Restored via Nandroid to the CM9 alpha 20
everything was great.
Yesterday I went to make a call and the phone locked. I tried to power down...no luck. So I pulled the battery.
It never came back. (got some type of 'android lost encryption' error)
I power up the phone and it brings me to a brand new user page where I would have to login with my gmail creds.
Then it starts throwing errors like calander stopped working, google settings app stopped working, android.process.acore stopped working. etc...
I can boot to CWM and but it will not allow me to recover to anything other than what I described above.
I can mount the USB partition and it appears to allow me to copy files into that partition. However, if I try to flash a ROM, Kernel, etc. It terminates the operation and says the file is bad.
When I reboot CWM and go to view the USB partition again, those files that I had just moved into the partition are now missing.
It is as though I have not copied the file at all.
Without access to the allow USB debug setting, I cannot adb anything.
I have tried the Samsung yellow boot/restore (odin?) when I click the 'Download files' button it throws a generic error and halts the process.
At this point, I don't care if the phone is put back to stock because I won't lose anything important. I just want to get my phone working again.
edit: I do have access to fastboot. I have wiped everything and tried to boot and it sticks in the bootloader (good?) I assume that when I try to flash one of the ROMs that I do have in the USB partition...it will go back to the way it was. (errors and all)
I suspect that the Kernel is corrupt. How would I fix this without being able to write to the USB partition?
Click to expand...
Click to collapse
If you have access to fastboot and assuming your flash storage isn't damaged, you should be able to flash over /boot with a boot.img and over /system with a system.img... But you might have to search around for them. Sorry i can't be more help.
kernels ; battery ; ROM ; gov/sched
http://www.mediafire.com/?wg9krukqp43nq1i theres a link to the boot.img for the apex bigxie rom (ics 4.0.3), try flashing that through fastboot i think the command is "fastboot flash boot %imglocation%.img" so just put the img in the folder you usually flash stuff with the fastboot bat in it, then try and flash this boot and tell me what happens.
ps, the %imglocation% should be the name of the img wherever you put it, so it will probably be boot.img.
Long time listener, first time caller.
I have the latest hboot 1.45.0013, S-On, Unlocked with HTC Dev Tool.
I used the Hasoon2000 tool to install SU, CWM, and a recovery image. I then used the instructions in the thread (http://forum.xda-developers.com/showthread.php?t=1508556) to install ICS and obtain root installing pyr-o-ice sense 1.1.1 (http://forum.xda-developers.com/showthread.php?t=1469615) Everything worked, created nandroid backup and installed titanium.
Some buttons didn't work, so I looked for updates and found Virtuous ROMs. So, I used CWM to clear dalvic, flashed boot image of the Virtuous Inquisition then used CWM to install zip. Bootloop. ROM just hangs on black screen with white V for 15 to 20 minutes.
MT4GS thread stated that Primadonna and Inquisition were comparable, so I followed the same proceedure, flashed Primadonna boot image then installed ROM through CWM. This time there was tmobile splash screen, but the same system hang.
At this point I tried to restore a recovery, but CWM could not find one. Used Astro to delete all boot images from SD root, assuming this may be the problem, and flashed a Virtuous ROM again. Same problem.
Based on this thread, I thought it might be the kernal, and tried flashing the pyr-o-ice boot image that worked initially. (http://forum.xda-developers.com/archive/index.php/t-1628171.html). No dice. CWM could not install the ROM (error 1)
So, at this point, I used CWM factory reset and wipe all data. And of course that made things worse, because the SD card with recoveries was wiped. I used adb to push the recoveries from Hansoon's toolkit, but stock recovery was not available (red triangle screen hang) and cwm could not mount the SD card.
So, at this point I used CWM to format SD card (blank anyway), and at this point adb failed to recognize the decive and I could no longer fastboot into recovery or hboot through adb. (volume down + power stopped working with pyr-o-ice install)
if i remove the battery and hold power + volume while using an adb reboot hboot command i can get into hboot about every 10th attempt. adb doesn't recognize the device ("waiting on device", or adb devices yields a blank list); however the phone in hboot will transfer to usb fastboot when connected with a cable.
i looked at pushing a zip file through adb to the sd root, but that was ineffective (adb does have write access to the sd root, maybe because i am s-on?). i purchased a second sd card, and copied the recovery images from hansoons toolkit and rebooted into recovery. still went to tmobile splash, followed by V-screen bootloop.
i looked at placing a stock ruu on the sd and naming the file PG59IMG.zip, but because i'm S-on i can't flash radios, so that's out.
So, here we are. Iffy access to fastboot, 2 sd cards, a lot of determination, and a persistent bootloop.
Can someone, PLEASE help me?
Thanks!
AFAIK, you cannot flash the boot.img with CWM if you are S-ON, you *MUST* use Fastboot to flash that. So, before you messed it all up, if you had just extracted the boot.img from the ROM and flashed it using Fastboot, it likely would have worked just beautifully.
Try booting into recovery and doing a regular flash of the ROM, THEN a fastboot flash of the boot.img.
SOLVED!!
Thanks to the folks heading up the HTC Unbricking Project (http://forum.xda-developers.com/showthread.php?t=1627881) ESPECIALLY Dexter93!! who patiently unraveled this for me, and Blue6IX for the Restore to Stock instructions in the Developers Reference Guide (http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24) I'm back to stock, and ready to try it all again!
Can someone send me an apk that automatically clicks the thanks button for selected developers at regular intervals?
Thanks again!
Solved???
Fuzi0719, thanks for your reply. I may have written this inappropriately, but what coded in the command prompt was "fastboot flash boot boot.img".
The ROM zip file was placed on the SD card, and I rebooted into recovery, and used CWM to install zip from SD. I'm new to this so I may have used the wrong term for installing the zip through CWM, the boot image file was always handled through the above command.
I'm back to "stock" at this point, but when I boot into the bootloader, the phone looks for PG59DIAG.zip and PG59DIAG.nbh before PG59IMG.zip.
It then asks if I want to install the update. (This is after I have already installed the "update", and the phone reset itself even with my old wallpaper.) When I got to the home screen there was a white circle in upper left corner of the status bar, with "check content" message. Each time the screen locked (default 30 seconds) unlocking it took me to the mytouch splash screen with the green circle and white background for about 10 seconds before resuming.
Each time I check to see if the phone registers requiring any updates. It doesn't. Two installs of the PG59IMG.zip. "recovery" eliminates the unlock splashscreen, and wiped any customizations. However, the phone will not manually boot into the bootloader; I have to use adb. Hboot reinstalls the PG59IMG.zip as an update every time.
If I accept it reboots within seconds like a fresh doubleshot. If I decline the "update" it reboots to the Tmobile MyTouch 4G Slide text splash screen, then moved to the green circle screen for a few minutes before I get to the homescreen.
Blue6IX was looking for help with these last month (http://forum.xda-developers.com/showthread.php?t=1580077), so maybe they are just extraction files that HTC sends with the OTA update that would prevent my phone from trying to install the "update" every time?
In any case, my question at this point is after coming from such an unstable point with my phone, is this what every relocked bootloader does? Or, is this a problem that means something else is still wrong with the system? Because taking it back to stock has not solved this.
Thanks.
Thanks for clarifying, you wouldn't believe the number of people who fail to follow that one simple step of fastboot flashing the boot.img, so that's why I stated that. So, now you have the phone relocked, and running a stock ROM (the 1.55?), but with CWM 5.0.2.7? Were you wanting to update to the 1.63 ROM? I'm unclear on what it is you want to do. For one thing, if you've already flashed the PG59IMG then I would delete it off the sd card so it doesn't keep trying to load it.
Yup.
It was just that simple.
Mainly I wanted to make sure that my phone was stable before I went back to unlock the bootloader, etc.
Went back to HTC, got a new token (just in case), and I'm creating a nandroid backup right now. Thanks.
I really appreciate it.
Hopefully the next time I get stuck, it's just as simple to fix, but far less embarrassing.
I have a 2.2.0 hboot 1.14 unlocked, tampered CID1111111 One XL from AT&T. I was trying to try my first cooked ROM Friday night and I think I may have totally screwed up. I did a "factory reset" from the bootloader instead of from TWRP 2.3.1. My phone gets to "initiating Swagger" and gets stuck. I tried to re-ROM but TWRP can't find the directory. Everything appears to have been over-written. I tried to use the 2.2.0 RUU to start over, but now my computer doesn't recognize the device in HTCsync. I tried to re-image the hboot with a stock 2.2.0 image to see if that would at least start up so that I could use the RUU. It doesn't appear to have helped. HTCsync still doesn't recognize my phone although it now alerts me that the device "MyHTC" is now on the computer. I tried to mount the USB with TWRP and the computer tells me that the drive is "unformatted" and asks to "format?" So far I've cancelled out of that.
Is this device borked beyond repair?
Update: The solution was very sinple. Reformatted SD in FAT32. Re-downloaded AOKP and Gapps. Extracted the boot.img file from AOKP. Copied zipped AOKP and Gaaps to newly formatted SD. Flashed the boot.img file in fastboot using the Team Nocturnal tool. Everything booted normally and runs great!
Many thanks to area51avenger and crappyvate!! You guys are what makes this community rock! Keep up the good work.
I believe I had this problem yesterday when trying to install AOKP, I didn't flash the boot.img before I ran the .zip in TWRP. I was stuck in the boot screen and then wiped all my data. Couldn't mount SD from TWRP, had to install HTCSync on my computer, relock the bootloader, and run the RUU of what I was previously on. I tried to go to 1.85, but it didn't allow me because I was previously on 2.20, getting the RUU for 2.20 and running it gave me back stock Sense, and I re-unlocked my bootloader and was able to successfully install AOKP after flashing the boot.img.
Don't factory reset from bootloader.
Format card to fat32, mount usb storage in twrp, copy aokp over.
Install as per the 1000 threads here
sdimock said:
I have a 2.2.0 hboot 1.14 unlocked, tampered CID1111111 One XL from AT&T. I was trying to try my first cooked ROM Friday night and I think I may have totally screwed up. I did a "factory reset" from the bootloader instead of from TWRP 2.3.1. My phone gets to "initiating Swagger" and gets stuck. I tried to re-ROM but TWRP can't find the directory. Everything appears to have been over-written. I tried to use the 2.2.0 RUU to start over, but now my computer doesn't recognize the device in HTCsync. I tried to re-image the hboot with a stock 2.2.0 image to see if that would at least start up so that I could use the RUU. It doesn't appear to have helped. HTCsync still doesn't recognize my phone although it now alerts me that the device "MyHTC" is now on the computer. I tried to mount the USB with TWRP and the computer tells me that the drive is "unformatted" and asks to "format?" So far I've cancelled out of that.
Is this device borked beyond repair?
Click to expand...
Click to collapse
So you can actually reboot in recovery ? reformat your sd card (fat32). Try to flash the boot.img of the rom you're on, reflash the romzip and see where that takes you. Note: there seems to be some issue with htc sync while you flash so make sure to disable htc sync.
Hey guys,
Finally decided to flash a new rom (NOS M7) and kernel (KillX) onto my phone, I loaded up the zips onto my sd card and just flashed it using recovery only. I didn't flash boot.img in bootloader/fastboot. I know its stupid, its my fault that I was tired and that I haven't really flash roms since mid 2011 on my sensation after settling on a virtuous rom.
Now my wifi doesn't work (haven't been playing with it much - could be many more things that don't work), but the main problem is that I found out adb doesn't work for my phone anymore when i tried to flash boot.img again. Sure, I can still use my phone as a external drive, but that's about it. Can't find my phone though 'adb devices' when the phone is switched on normally, in fastboot usb, and in recovery. However, I can still sideload a .zip file in recovery. that works.
In fastboot, I get 'This device cannot start. (Code 10) - A request for the USB BOS descriptor failed.' I've tried downloading the newest drivers from htc, updated my sdks, installed/uninstalled htc sync manager - which always came up with 'unable to sync with device that is locked, please unlock device' or something like that even though my device's screen was unlocked.
You probably figured out that I'm not that advanced with technology as some of you peeps out there. :angel:
What do you think I should be doing now?
I feel like I have half a phone working. :crying:
Cheers,
Reece
Which variant do u have ... X920d or e ??
Also it might be best to return to stock first and ten start over again ... Also provide the hboot version from the boot loader screen
I have the x920d,
here's the info.
Hboot - 1.39.0000
Radio 3A.21.306.10
s-on.
What do you mean by return to stock, as in relocking my phone etc... but how? I can't even use adb. I can't really flash roms properly either.
Anyone...??
Try the ADB on another computer, it should work.
I'm still getting no luck with adb on another computer.
What else can i do?
I can even use adb .
Hope that help.
http://forum.xda-developers.com/showpost.php?p=39653035&postcount=12
Note: That guy did with x920e ROM but I think the process should be same, good luck.
Sorry that i took a while to reply.
I just tried going into recovery and wiping everything as per the link,
i can't seem to wipe cache and system. weird. that's what i get for trying to format system or cache
'Formatting /system(or cache)...
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p32
Error formatting /system(or cache)!'
I can now flash boot.img, but somehow that won't mean anything until I can wipe my phone.
Can I try wiping it in bootloader?
Okay, so I have a slight problem. I was trying to install Cyanogen mod. I followed the directions, first installing the zip from TWRP, then i flashed the boot.img. After that, i tried booting it up. For some strange reason, it wouldn't boot up. it would get to a certain point, then it simply rebooted all over again. After trying a few more things, I finally decided i should reset it to the stock rom. The only problem is, i do not have S-Off, and to get S-Off, i need to boot into the normal mode. I then remembered i could probably do that from the SD card, but when i tried, ADB complained with a permissions error. Upon further investigation, I then found that I couldn't even mount the SD card. I tried using a different version of TWRP, and every other version couldn't even start up. When i tried, it rebooted before actually getting to the recovery. I decided to try CWM. That at least opened fine, but it also was unable to mount the SD card. I also tried flashing the stock rom zip files using the rebootRUU command, but that came up with an "Unknown error". At this point, i think this could all be resolved if i had S-Off, but i cannot do so. I was wondering if anyone knew how to do it with only fastboot, or if anyone had any other ideas on how to get it working.
Thanks in advance.