Develop Bugs

[Q] free beer if you fix my one x!

Hi, if you can help me unbrick my phone I'll buy you a beer (or three!)
I have an htc one x which i managed to unlock the bootloader via htcdev as in various tutorials....
I was too lazy to take a backup
I then tried to install cyanogenmod 10 using cwm recovery.... (by flashing a zip file i had downloaded - one of the nightly builds)
I wiped the cache etc in cwm
it got stuck in a boot loop i think as it got to the spinning cyanogen logo then nothing happened...
I've tried to get it working again using lots of different methods - i downloaded some RUU exes which failed because they said they weren't the correct ROM (even though they should be right) - then i read a tutorial about how to use fastboot to flash system.img onto the phone but it fails giving error code 00000006
I can't push any zip files to the phone using ADB as I get permission denied errors
I've also tried to use fastboot to flash various recoveries but I can't apply any zips because I can't get them onto the phone in the first place
I've also flashed various recovery.img files but when they load, I get a red triangle after a few seconds
If someone could tell me how to use ADB to push a zip file to the phone I'd be really grateful - have tried everything but keep getting permission denied errors
Thanks
(oh and if you manage to help me fix it I WILL buy you a beer... or 3)

oh and ....
ALSO I've googled the problem and tried all of the options I can find which could help - please don't just send me a link to a page because i can guarantee I've probably already tried the solution and failed. When I boot into recovery, I can't use adb push to send files to the phone because it says it's not connected even if i try the option for mount data, or mount storage - the only time windows seems to manage to aknowledge it's existence is on the fastboot screen -
lazclark said:
Hi, if you can help me unbrick my phone I'll buy you a beer (or three!)
I have an htc one x which i managed to unlock the bootloader via htcdev as in various tutorials....
I was too lazy to take a backup
I then tried to install cyanogenmod 10 using cwm recovery.... (by flashing a zip file i had downloaded - one of the nightly builds)
I wiped the cache etc in cwm
it got stuck in a boot loop i think as it got to the spinning cyanogen logo then nothing happened...
I've tried to get it working again using lots of different methods - i downloaded some RUU exes which failed because they said they weren't the correct ROM (even though they should be right) - then i read a tutorial about how to use fastboot to flash system.img onto the phone but it fails giving error code 00000006
I can't push any zip files to the phone using ADB as I get permission denied errors
I've also tried to use fastboot to flash various recoveries but I can't apply any zips because I can't get them onto the phone in the first place
I've also flashed various recovery.img files but when they load, I get a red triangle after a few seconds
If someone could tell me how to use ADB to push a zip file to the phone I'd be really grateful - have tried everything but keep getting permission denied errors
Thanks
(oh and if you manage to help me fix it I WILL buy you a beer... or 3)
Click to expand...
Click to collapse

Have you flashed the cm boot IMG and then erased fastboot cache?
fastboot flash boot pathtoboot.IMG
fastboot erase cache
For the RUU to work you need to have stock recovery and a relocked boot loader.
if you download the latest clockworkmod mounting as USB storage is fixed.
Sent from my HTC One X using xda app-developers app

thanks!
wow that was a quick reply - yes I've flashed the cm boot img and erased the cache - which version of CWM is the latest? - When you say mounting as USB storage is fixed, do you mean that windows will be able to see the device and write files to it?
(I'm really sorry for asking these questions - the problem is that I know a BIT about how android works but not as much as I should do)
treebill said:
Have you flashed the cm boot IMG and then erased fastboot cache?
fastboot flash boot pathtoboot.IMG
fastboot erase cache
For the RUU to work you need to have stock recovery and a relocked boot loader.
if you download the latest clockworkmod mounting as USB storage is fixed.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse

Are you absolutely sure you flashed the boot.img from the rom.zip using fastboot on your computer? Because it really sounds like you didn't

This is a thread I made and it should provide you with a solution if not a starting point if you insist on CM10.
http://forum.xda-developers.com/showthread.php?t=1900127
Good luck!

sorry hope i'm not wasting your time!
I ran the command as follows :-
fastboot flash boot boot_signed.img
(I got the img file from the ruu )
I'm not 100% sure if it worked, but at that stage I didn't see any errors
Michealtbh said:
Are you absolutely sure you flashed the boot.img from the rom.zip using fastboot on your computer? Because it really sounds like you didn't
Click to expand...
Click to collapse

CWM 5.8.4.0 has the USB mounting fixed. You can go to mounts and storage and mount as USB, then the PC will see it.
fastboot flash recovery recovery.img
Wipe cache and dalvik cache.
I'm pretty sure you either didn't flash the boot.img or flashed the wrong one, so get it again to make sure it's the right one and
fastboot flash boot boot.img
And
fastboot erase cache

thanks!
I'll give it a go - to be honest i don't insist on using cm10 at all - i just wanted to see what jellbean was like and it seemed like a reasonable way of achieving that.... i'd be quite happy with any decent rom if it can fix the lag problems i have and some of the other issues.....
great tutorial by the way! - once my phone has charged up again I'll try it
ORStoner said:
This is a thread I made and it should provide you with a solution if not a starting point if you insist on CM10.
http://forum.xda-developers.com/showthread.php?t=1900127
Good luck!
Click to expand...
Click to collapse

ahhhh!
i think i was trying to run CWM 5.8.2.7 which possibly didn't have usb mounting working? Will give that a shot thanks!
BenPope said:
CWM 5.8.4.0 has the USB mounting fixed. You can go to mounts and storage and mount as USB, then the PC will see it.
fastboot flash recovery recovery.img
Wipe cache and dalvik cache.
I'm pretty sure you either didn't flash the boot.img or flashed the wrong one, so get it again to make sure it's the right one and
fastboot flash boot boot.img
And
fastboot erase cache
Click to expand...
Click to collapse

Thanks.
I use CM10 myself at the moment because of the aesthetics, but because of the amount of ram and battery it uses I wish I had stuck with ARHD.
Come October we should see Jellybean ARHD which will have great features like USB OTG without a powered hub.

lazclark said:
i think i was trying to run CWM 5.8.2.7 which possibly didn't have usb mounting working? Will give that a shot thanks!
Click to expand...
Click to collapse
Mount as USB not working on that version, also charging not working either. It was not a great release in terms.of features, but it was updated quickly, that's quite an.old version now.
Do you know which tutorial you followed? It really needs updating, there are a lot of people on this old version struggling more than they need to.

Right, first you're going to flash a recovery which allows you to mount USB storage. Either cwm or TWRP, download the recovery.img and flash through fastboot using fastboot flash recovery rocoveryname.img.
Download a new rom and extract the boot.img from it. Flash that boot.img using the usual fastboot method.
Now boot into the new recovery, connect to your pc and mount USB storage from the option in recovery. Copy over the rom you downloaded. Unmount USB storage. Now do a full wipe through the menu in recovery - format /data, /system and /cache. Now flash the rom and reboot

Some assistance is requested

Hello there,
I'm slightly new to the forums, at least posting to them so if I'm in the wrong section or if I'm just not suppose to ask these questions... well... lend some expert advice and help me out!
I'm by no means an expert on rooting and flashing, pretty much every thing i have learned has been on my Optimus V, Nexus 7, and My latest device, HTC One V and i learned it all on these forums!
So my problem is... My HTC One V i have unlocked it and rooted it with a tool kit i found on here called "Hasoon2000's HTC One V All-In-One Kit" and all was well in the world. But now that i have rooted it I've grown bored with the device... after less than 24 hours of running stock rooted. And i've attempted to flash MIUI.us on my device as found on the developers website Now I've flashed many custom roms on my other devices, currently running Paranoid Android Beta 3 on my Nexus and Harmonia 2 (I believe) on my OV. But this phone has become quite the hassle. I'm running TWRP CDMA recovery and i Factory reset, wipe data, cache, dalvic (spelled correctly?) and it boots up to the MIUI boot logo then it goes to the usual Google start screen where you select language and set up your device... but... at that point it fails to do anything then boot loops back out and restarts the phone, and repeats... sometimes it won't even get out of the boot loop and it will just restart the phone... so i have used the RUU and reset the phone multiple times after this has occurred... If anyone could be of assistance or point me towards the correct forum it would be much appreciated!
I'm not totally sure what else could help anyone out there but it says S-OFF and i am unlocked and i have tried multiple roms and none of them have worked yet at all, the AOSP rom actually got to the home screen then restarted... this is getting quite frustrating and slightly irritating so if anyone could lend a helping hand I'd be much appreciative!

If you have a brand new phone it may have the ota already applied, which means none of the custom kernels will work, which means no JB roms.

robaho said:
If you have a brand new phone it may have the ota already applied, which means none of the custom kernels will work, which means no JB roms.
Click to expand...
Click to collapse
Okay but when i do the RUU or even initially it always gives me the option to do system update OTA once i turn it on the first time... and on all the different ROM threads it says you have to extract the "boot.img" and flash in fastbot... so i extract the rom onto the SD card then once i flash the rom I've tried rebooting to bootloader and on my computer with SDK tools running command "fastboot flash boot boot.img" and that never works, i've tried flashing the jellyboot5 kernel i've tried many many options and bricked my phone about 20 times in the first 24 hours of owning my device... Black Friday purchased!
Sorry i'm still getting used to these devices... this is my first HTC and it's been... very much a learning experience but i really wanna try out some new roms on better phones than the OV

the last OTA broke the Radio (-> v.0928) firmware
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
mkgarrod said:
Okay but when i do the RUU or even initially it always gives me the option to do system update OTA once i turn it on the first time... and on all the different ROM threads it says you have to extract the "boot.img" and flash in fastbot... so i extract the rom onto the SD card then once i flash the rom I've tried rebooting to bootloader and on my computer with SDK tools running command "fastboot flash boot boot.img" and that never works, i've tried flashing the jellyboot5 kernel i've tried many many options and bricked my phone about 20 times in the first 24 hours of owning my device... Black Friday purchased!
Sorry i'm still getting used to these devices... this is my first HTC and it's been... very much a learning experience but i really wanna try out some new roms on better phones than the OV
Click to expand...
Click to collapse

master_c said:
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Click to expand...
Click to collapse
Okay so I just wanna make sure i understand all this... I'm basically doing the same thing that the RUU does? What does the RUU do outside of this? and i tried what you said and it never notices it and now when i boot up my phone it has no service and doesn't connect to the network....

master_c said:
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Click to expand...
Click to collapse
Oh and when i type the fastboot oem lock command it gives me this
Code:
C:\Fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.271s
(Sorry for the awful format, I'm not used to actually taking part in a forum!) but regardless of the FAILED status it still says relocked... I'm not sure if that's a problem or not

You can ignore the error msg, I saw the same thing and the relock worked correctly. The RUU didn't flash the radio correctly when I ran the application, and I couldn't `fastboot flash radio` directly because of S-ON (or install the zip through TWRP), but when I copied the rom zip to PKIMG76 and installed it in hboot, I was able to flash the radio back to 0521_2, at which point I could run sick kernel and AOKP Jellybean without the bootloop (I originally documented it on this thread: tinyurl.com/cf2aq5n)
mkgarrod said:
Oh and when i type the fastboot oem lock command it gives me this
Code:
C:\Fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.271s
(Sorry for the awful format, I'm not used to actually taking part in a forum!) but regardless of the FAILED status it still says relocked... I'm not sure if that's a problem or not
Click to expand...
Click to collapse

master_c said:
You can ignore the error msg, I saw the same thing and the relock worked correctly. The RUU didn't flash the radio correctly when I ran the application, and I couldn't `fastboot flash radio` directly because of S-ON (or install the zip through TWRP), but when I copied the rom zip to PKIMG76 and installed it in hboot, I was able to flash the radio back to 0521_2, at which point I could run sick kernel and AOKP Jellybean without the bootloop (I originally documented it on this thread: tinyurl.com/cf2aq5n)
Click to expand...
Click to collapse
Okay so if i put that pk76img.zip into my fastboot folder on my PC then run "fastboot flash pk76img.zip' will it do the same thing? most of my devices when i rooted them and flashed custom images It's never been this difficult and i've never had to actually use CMD which i'm enjoying learning these commands and stuff but it's starting to get on my nerves that i can't get it to work when i boot by phone up into Boot loader here's what is says
Code:
***UNLOCKED***
PRIMOC PVT SHIP S-ON RL
HBOOT-1.53.0000
RADIO-1.00.00.0521_2
eMMC-boot
May 14 2012,20:27:38
I'm not sure if any of that will help at all.. but my Network is fine now but i really don't know what to do next... it says S-ON which i believe might be the problem but i AM rooted..

You wouldn't need to `fastboot flash...`; just copy the file to the root directory of your SD card, make sure it's named "PK76IMG.zip" (possibly case sensitive), and when you enter HBOOT it should say "searching for PK76IMG... blah blah" until it finds the file, at which point you'll see a blue progress bar, and it'll eventually ask you to confirm installation after it verifies the file(s).
All that said, it looks like you already have the correct version of RADIO, so I'm not sure this will help, but it's probably worth a try, unless you're flashing the wrong kernel for MIUI...
mkgarrod said:
Okay so if i put that pk76img.zip into my fastboot folder on my PC then run "fastboot flash pk76img.zip' will it do the same thing? most of my devices when i rooted them and flashed custom images It's never been this difficult and i've never had to actually use CMD which i'm enjoying learning these commands and stuff but it's starting to get on my nerves that i can't get it to work when i boot by phone up into Boot loader here's what is says
Code:
***UNLOCKED***
PRIMOC PVT SHIP S-ON RL
HBOOT-1.53.0000
RADIO-1.00.00.0521_2
eMMC-boot
May 14 2012,20:27:38
I'm not sure if any of that will help at all.. but my Network is fine now but i really don't know what to do next... it says S-ON which i believe might be the problem but i AM rooted..
Click to expand...
Click to collapse

master_c said:
You wouldn't need to `fastboot flash...`; just copy the file to the root directory of your SD card, make sure it's named "PK76IMG.zip" (possibly case sensitive), and when you enter HBOOT it should say "searching for PK76IMG... blah blah" until it finds the file, at which point you'll see a blue progress bar, and it'll eventually ask you to confirm installation after it verifies the file(s).
All that said, it looks like you already have the correct version of RADIO, so I'm not sure this will help, but it's probably worth a try, unless you're flashing the wrong kernel for MIUI...
Click to expand...
Click to collapse
Well I'm not really sure on the rules of forums... about posting links to other things like that... but i think my problem is a kernel issue... I have the JellyBoot5.zip... that everyone was talking about and even someone on that other forum you posted said something about it... but... maybe i'm just doing that wrong... do i go into TWRP recovery... flash the Jellyboot5.zip then reboot to bootloader, and on CMD run "fastboot flash boot boot.img" (which i extract the boot.img from the jellyboot5.zip...) is that correct? I'm really trying to NOT be illiterate on these things but i'm at a total loss... i may just stick with root and stock if i can't figure this out soon.

I would try the v2.0.0 kernel (tinyurl.com/d8xknzb) ... I actually had a (different) bootloop problem after installing the jellyboot5.zip in TWRP, so maybe this kernel will do the trick.
mkgarrod said:
Well I'm not really sure on the rules of forums... about posting links to other things like that... but i think my problem is a kernel issue... I have the JellyBoot5.zip... that everyone was talking about and even someone on that other forum you posted said something about it... but... maybe i'm just doing that wrong... do i go into TWRP recovery... flash the Jellyboot5.zip then reboot to bootloader, and on CMD run "fastboot flash boot boot.img" (which i extract the boot.img from the jellyboot5.zip...) is that correct? I'm really trying to NOT be illiterate on these things but i'm at a total loss... i may just stick with root and stock if i can't figure this out soon.
Click to expand...
Click to collapse

master_c said:
I would try the v2.0.0 kernel (tinyurl.com/d8xknzb) ... I actually had a (different) bootloop problem after installing the jellyboot5.zip in TWRP, so maybe this kernel will do the trick.
Click to expand...
Click to collapse
Okay so i wanna make sure i'm doing this right... I put that zip i just downloaded into my sd card on the root of the drive... then go into recovery... and flash it? do i wipe anything? anything at all? do i need to flash the boot.img? if i DON'T flash a custom rom right now also... will that mess up my phone since stock is running ICS?

It's a JB kernel so it probably won't work with an ICS rom, but I can't say I've tried it. And yeah, you need to flash the boot.img, and also install the zip in recovery, but you shouldn't need to wipe anything if you're just changing kernels (although there isn't much point unless you're installing a JB rom at the same time...)
mkgarrod said:
Okay so i wanna make sure i'm doing this right... I put that zip i just downloaded into my sd card on the root of the drive... then go into recovery... and flash it? do i wipe anything? anything at all? do i need to flash the boot.img? if i DON'T flash a custom rom right now also... will that mess up my phone since stock is running ICS?
Click to expand...
Click to collapse

master_c said:
It's a JB kernel so it probably won't work with an ICS rom, but I can't say I've tried it. And yeah, you need to flash the boot.img, and also install the zip in recovery, but you shouldn't need to wipe anything if you're just changing kernels (although there isn't much point unless you're installing a JB rom at the same time...)
Click to expand...
Click to collapse
Well as soon as i get back to my house I'm going to try this out and try reflashing the MIUI rom which is JB i believe and hope it works! if not... I'll be using that RUU tool again... I think i've been on that more than i have my new phone!

Why did no one report this thread? Obviously I'll see it eventually, but come on guys/gals!
Moved to Q&A.

[Q] Strange behaviour - internal storage problem?

Hey together,
I hope you can help me. I have a strange problem.
Chronologically:
1) I had been running Xylon JB 4.2 ROM for 2 or 3 months on my GNexus. Everything was fine. Except that I noticed over the time a slight lag all over the OS. The general reaction time was not so fast as it should be (Note: My phone has not that memory unit which causes those extreme lags I read about somewhere in this forum).
2) So I decided to go back to stock. I did a full wipe and flashed a JOP40D 4.2.1 Odex Rooted Busybox FactoryImage which I took from this forum (don't know which thread). The good: Android was very fast again. The bad: Immediately after flashing it I encountered problems. At every boot I got the "Android is upgrading... XX of XX apps..." screen, even after a separate dalvik wipe, and really at every boot (not just the 1st after dalvik wipe). Furthermore, I noticed that some apps behave strange, for example Play Music couldn't play any music from my internal storage which worked fine under Xylon. Plus, system settings like the ring sound were not saved so that after reboot there was set a different ring tone. I thought, well, maybe something went wrong when I restored my apps via TB (apps via update.zip, data via TB app).
3) Due to the strange behaviour I decided to carry out a complete wipe via TWRP. I mean really a full storage wipe, this sort of wipe when TWRP warns you and says this was not needed most of the time. I thought it couldn't be wrong to wipe everything that can be wiped to fight the problem. After that, I flashed 4.1 factory image via the GNex Toolkit because there was no rom zip anymore on the internal storage. (4.1 because the Toolkit couldn't download any newer image correctly). Back in Android, I copied bigxie's JOP40D deodex ROM on the storage and flashed it (full wipe before). And yes I updated the SuperSU binaries as bigxie told. This time I didn't use Titanium Backup for restore, but installed the apps directly from Play Store, the cleanest method. And AGAIN, the phone is showing some strange behaviour! This time no problems with dalvik cache, but with some other part of the storage as it seems. Some apps refuse to start ("app XYZ was closed" - report - OK), even after uninstall and reinstall from Play Store, for example Öffi, DB Navigator, mehr-tanken which worked fine under Xylon. the Facebook app doesn't save data correctly. At nearly every start it asks me if I want to find friends (normally only 1st start). But other Facebook app settings (notification etc.) are saved correctly. Strange, isn't it?? Wipe cache and dalvik cache didn't change anything.
I'm completely desperate. What can be the cause for the strange behaviour? Maybe the storage or something broken?
I've flashed ROMs so often with several Android devices, so I think I'm not such a complete noob. But what could have happened?
I beg you to answer if you have any suggestions what I can try.
I could kick myself for touching my Xylon setup which had worked fine (just slightly slow), even considering that I'm facing my exams in 6 weeks and should learn day and night...
Thanks in advance!!!

it seems like everytime i read about someone having some kind of strange anomoly, its someone whos using a toolkit (not trashing you, but i keep seeing the correlation); which is why i havent touched them, plus fastboot is more fun. anyways this is how i would go about it, and get your stock image ready.
fastboot format system
fastboot format userdata
fastboot format cache
fastboot erase boot
fastboot erase recovery
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot rebooot-bootloader
fastboot flash userdata userdata.img
fastboot reboot
try that, just make sure you have adb and fastboot set up right. its the most basic failsafe for sure method to get to 100% stock without any trash left behind on your phone

Hey, thanks for your detailed suggestion!
I'm not sure if the problem can be toolkit related as I didn't use the toolkit for the first flash (step 2 in my first posting). But nevertheless, I'll follow your suggestion as soon as I can manage it.
I have not much experience with fastboot as the only thing I did with fastboot was flashing custom recoveries.
So just to be safe I'd like to know what you mean exactly by
1) fastboot flash boot boot.img
2) fastboot flash system system.img
3) fastboot flash userdata userdata.img
I downloaded the JOP40D factory image and unzipped the RAR file. It contains:
bootloader-maguro-primelc03.img, flash-all.bat, flash-all.sh, flash-base.sh, image-yakju-jop40d.zip, radio-maguro-i9250xxlh1.img
Shall I take the boot.img, system.img and userdata.img from the zip file?
What shall I do then with all the other files except the zip file?

staud said:
Hey, thanks for your detailed suggestion!
I'm not sure if the problem can be toolkit related as I didn't use the toolkit for the first flash (step 2 in my first posting). But nevertheless, I'll follow your suggestion as soon as I can manage it.
I have not much experience with fastboot as the only thing I did with fastboot was flashing custom recoveries.
So just to be safe I'd like to know what you mean exactly by
1) fastboot flash boot boot.img
2) fastboot flash system system.img
3) fastboot flash userdata userdata.img
I downloaded the JOP40D factory image and unzipped the RAR file. It contains:
bootloader-maguro-primelc03.img, flash-all.bat, flash-all.sh, flash-base.sh, image-yakju-jop40d.zip, radio-maguro-i9250xxlh1.img
Shall I take the boot.img, system.img and userdata.img from the zip file?
What shall I do then with all the other files except the zip file?
Click to expand...
Click to collapse
what all is in the file image-yakju-jop40d.zip? you should have boot.img, recovery.img, system.img, userdata.img. if those are all in there, you can extract them to the folder you use to flash from in fastboot. for example, the command fastboot flash boot, is the command to flash the boot image. the second part is the file name you want it to flash, so fastboot flash boot boot.img. you shouldnt need to flash the bootloader or radios if they are working correctly. if you want to anyways, check efrant's nexus guide on here, i forget the commands to differentiate between the two different radios when you flash them.
if you do the bootloader and decided to erase and flash instead of just flashing over it, DO NOT use the command fastboot reboot-bootloader until after you flash the bootloader. otherwise it will try to reboot into a bootloader that doesnt exist, if that makes sense. someone correct me if im wrong about this part.

username8611 said:
what all is in the file image-yakju-jop40d.zip? you should have boot.img, recovery.img, system.img, userdata.img. if those are all in there, you can extract them to the folder you use to flash from in fastboot.
Click to expand...
Click to collapse
Yeah, those were in the zip. I followed your fastboot how-to within the last 10 minutes and it worked so far as the new stock Android has just booted. By now I can't tell if the strange things have really disappeared. I'll see how things go within in the next hours and days and repost if I encounter again any problems. By now - thanks dude! :good:
EDIT: You wrote reboot with 3 o once. I noticed it but maybe you might wish to correct that if some other desperate and help-searching guy follows your how-to
EDIT2: After 3 days I haven't encountered any strange behaviour. But I didn't root it again or any other modding stuff. Just stock Android. For the moment I'm happy that it runs without problems and I won't touch it again until my exams are done. It seems to me that your method was successful. Thanks again!

[Q] Stuck in CWM recovery screen

Dear XDA-members,
This afternoon, I tried to root mij HTC One X and flash it to Cyanogenmod 10.2. During the flashing, I made the mistake to forget to put the boot.img and Google Apps files on my SD card. During the rom installation, I got stuck in the splash screen. For this reason, I formatted my SD kaart in the CWM recoveryscreen but now my phone doesn't have any rom at all. When I turn on my phone, I only get to see the white HTC screen. When I try to connect my phone to my pc, it doesn't get recognized. I just want to get my stock ROM back again to get my phone working. I do have acces to the CWM recoveryscreen.
I downloaded the fastboot and RUU files, but fastboot won't recognize my device through the commandscreen. This is why I can't put the RUU files on my phone.
Can someone please help me? I don't have a clue what to try next to save my phone.
Thanks in advance!

kajvb said:
Dear XDA-members,
This afternoon, I tried to root mij HTC One X and flash it to Cyanogenmod 10.2. During the flashing, I made the mistake to forget to put the boot.img and Google Apps files on my SD card. During the rom installation, I got stuck in the splash screen. For this reason, I formatted my SD kaart in the CWM recoveryscreen but now my phone doesn't have any rom at all. When I turn on my phone, I only get to see the white HTC screen. When I try to connect my phone to my pc, it doesn't get recognized. I just want to get my stock ROM back again to get my phone working. I do have acces to the CWM recoveryscreen.
I downloaded the fastboot and RUU files, but fastboot won't recognize my device through the commandscreen. This is why I can't put the RUU files on my phone.
Can someone please help me? I don't have a clue what to try next to save my phone.
Thanks in advance!
Click to expand...
Click to collapse
Can you mount storage in recovery ? If you can....
Mount storage in recovery and copy/paste rom and kernel on SD, flash rom and kernel, than flash boot.img via fastboot.

Can u do any fastboot commands while phone is on bootloader?
Sent from my HTC One X

Thanks for the quick responses!
Unfortunately, I can't mount storage in recovery so I can't acces my SD card.
I can, however, access the fastboot menu so it's possible to do fastboot commands and get into the CWM menu.

https://www.dropbox.com/s/yqzlpqo8illa53j/Philz recovery 5.15.9.img
Flash this recovery and you can mount the sd

Thanks, but can you explain how to do that?
I don't think I can use fastboot because my phone doesn't get recognized, but maybe I'm doing something wrong.

OK, I found a way to do that via fastboot, but I couldn't mount it just like in CWM. I did download a RUU.exe because I figured that fastboot is working for me! So I tried to install the stock ROM using the RUU.exe and fastboot, but the flashing progress was aborted because apparantly that RUU version was older than the one on my phone. I googled for a newer one, but there are no newer .exe files and according to others I should use a nandroid backup zip file.
How should I do that? Or is there any way that I can make the RUU.exe I downloaded work, because it seemed to me that the program worked fine except for the older version part. Or is it the easiest to flash Cyanogenmod, I've got those files on my pc as well. I wouldn't know how to do that, just by flashing boot.img from the zip file? I really hope you can help me out!
Further notes: during the RUU installation progress, CWM and Philz were wiped from the SD card and I had to relock my phone. I don't know if any of that should cause a problem though.

Flash that philz, enter recovery. Put in the usb cable and mount. Wait until the sdcard pops up on windows. Can take minutes......but works for sure !

Thank you, I'll try that tonight! Then, what kind of files should I copy on the SD card? And can I use the Cyanogenmod files as well as the stock ones? Lastly, do I need to unlock my phone again?

Unlock, flash recovery, flash boot.img, make a full wipe, install CM, install GAPPS ..... reboot

OK, so just to get it straight:
First I unlock it, then flash philz via fastboot. Then enter recovery mode and mount USB. After that, I copy the Cyanogenmod boot.img and the GApps file on the SD card. Lastly, I install the boot.img file via the Philz recovery program and then the GApps, and I reboot.
Is this right or should I do something different?
Thank you so much!

Cm.zip to sdcard, boot.img flash via fastboot. Install CM.zip and gapps via recovery.

Two last questions:
Which boot.img file do I need to use? The one from the CM.zip?
And how should I do the full wipe?

Also, I can not flash my phone because it won't charge properly... When I connect it to the charger, it will charge and I see the red light. After a while, the battery drains and gets empty, while still seeing the red light. I put it on the charger all night and it was totally empty when I checked this morning. Do you have an idea how I can deal with this?

If you can get into philz recovery. Leave it there. The battery charges inside of it.
And yes always boot.img of the rom.zip you want to install.
Sent from my HTC One X using XDA Premium 4 mobile app

I can not flash Philz yet because the bootloader is still locked. It has charged enough now, but when I try to unlock it by typing 'fastboot flash unlock unlock_code.bin' it says:
Sending 'unlock' (0 KB)... OKAY [0.009]
Writing 'unlock' ... FAILED (remote: not allowed)
finished. Total time: 0.219s
Could it be that I need to get a new unlock_code.bin? Now I use the same one as when I first tried to lock it. Or do I need to type another command for reunlocking? The status on my phone still says relocked...

Command is not correct
Fastboot flash unlocktoken unlock_code.bin
Sent from my HTC One X using XDA Premium 4 mobile app

Thank you so much, it worked!
CM10.2 is installed, I've got only one more problem...
When I boot it, and pass the setup wizard, the phone keeps popping up the same message:
Unfortunately, Setup Wizard has stopped. Every second it pops up.
I can acces various programs, so that works, except for that message.
Do you happen to know a solution for that as well?
Anyway, thank you again for your help!

Installed gapps ? The correct one ? Made a proper full wipe full before installing the rom !
Sent from my HTC One X using XDA Premium 4 mobile app

Yes, I got it to work. Now I've got a new problem... For one afternoon, my phone worked perfectly, but since that evening, now two days ago, I can't connect with my mobile services. I can't call, go on internet (only via WiFi), and when I try to create a new APN, it doesn't show. I tried it with two different SIM cards, neither work. Also my battery drains very fast and when I take a look at my battery app it doesn't show Google play services from which I heard is a common cause
Sent from my EndeavorU using xda app-developers app

[Q] MIUI Rom gone wrong

okay so heres what happened.
I have an international htc one x that is indeed rooted with no roms installed.
I did create a back up and then tried to install the MIUI rom (but I dont really know where that is on my phone. I know I made one with rom manager. I dont have any backups on my computer though)
It worked, however, it didnt have wifi or data signals so i went back to try again.
I opened my bootloader screen. For the record, it is unlocked and hboot is version 1.73 if that helps.
I wiped cashe/data/delvic everything and even factory reset and installed the MIUI RD rom now hoping it would have a difference.
The darn thing got stuck on the MIUI bootloader for hours.
I did the same thing again a few times, sometimes in different orders and then it passed on and another screen came saying 'starting apps'. That got stuck for hours too.
Now I don't have any other roms on my phone, just the MIUI RD. The original miui just vanished too, i dont see it anymore. Also, when I put my USB wire to the phone and connect it to the pc, I cant transfer newer files into it. So this is all I have access to on my phone apparently.
I tried flashing a boot.img and a couple kernels but no luck. I've been trying to do this for all day and this is my first time so I don't know much about it.
I've been googling and somethings say to open cmd and type but i keep getting 'fastboot is not recognized as an internal or external command'
Currently, its not stuck at either the MIUI screen or the Starting Apps. but just the HTC logo screen and not going past.
I don't really want to install any new roms considering i've worked really hard to get this to work and I really want it now more so.
How do i fix this? I want to use this rom.

flash philz recovery (http://forum.xda-developers.com/showthread.php?t=2240646), usb mounting should work on that, then:
steps to install ROM
1. bootloader version should be 1.3x
2. copy ROM to SD Card
3. copy boot.img INCLUDED in the ROM zip to fastboot folder
4. flash the boot.img in fastboot
5. in recovery, wipe system/data/cache/everything
6. flash rom
7. restart

but how exactly do i put it on my phone? my computer isnt detecting my phone when i connect it? im sorry im not exactly an expert on this.

Go to recovery - mounts and storage - hook up the usb cable - tap the last option in the mounts and storage list and wait a few minutes. It won't be mounted instantly

ok i flashed the philtz recovery but when i flash the boot.img it says:
Finding update package
Opening update package
Installing update
installation aborted
for reference: http://forum.xda-developers.com/showthread.php?t=1957490
thats the rom i used and i flashed the boot.img flasher thats right above the download link
edit: also i tried just flashing the rom again and im still stuck on the HTC screen.
its not even going to the miui screen or starting apps anymore. :[

Boot.img must be flashed via fastboot. Not via recovery !

ok, i looked up how to fastboot, downloaded sdk files and i moved the boot.img into the fastboot folder and i opened command prompt there and wrote fastboot flash boot boot.img but i keep getting:
'fastboot is not recognized as an internal or external command'
what did i miss?
EDIT: ok, so the fastboot folder i got from the page didnt work so i used a different fastboot folder, dragged the .boot there and now it worked! finally passed the screen and wifi is connecting!
thank you!

Good, thanks to @tomascus. He summed it up real nice
Cheers