Related
Hello, all. I've spent the last four hours trying update my AT&T HTC One X running Android 4.1.1 to 4.2.2 and I failed hard!
First, I used the all-in-one toolkit to unlock my bootloader, flash clockwork recovery, and root the phone. The first guide I was following gave me error status 7 when I tried to flash the ROM so I wen to this guide:
update-htc-one-x-cm101-android-422-jelly-bean-custom-firmware/2/ (from team android website)
I got to the step below using the SDK I downloaded from dev.android.com and now my phone is dead! The HTC logo appears and then it goes to a black screen. Luckily, I can still reach my fastboot and clockwork recovery menu but nothing I try makes the phone boot.
Step 8 - Type the following command and press Enter.
fastboot flash boot boot.img
Step 9 - Then, type the following command and press Enter.
fastboot reboot
I just want my phone back to normal please! I don't care about rooting anymore. Thank you.
zenkix said:
Hello, all. I've spent the last four hours trying update my AT&T HTC One X running Android 4.1.1 to 4.2.2 and I failed hard!
First, I used the all-in-one toolkit to unlock my bootloader, flash clockwork recovery, and root the phone. The first guide I was following gave me error status 7 when I tried to flash the ROM so I wen to this guide:
update-htc-one-x-cm101-android-422-jelly-bean-custom-firmware/2/ (from team android website)
I got to the step below using the SDK I downloaded from dev.android.com and now my phone is dead! The HTC logo appears and then it goes to a black screen. Luckily, I can still reach my fastboot and clockwork recovery menu but nothing I try makes the phone boot.
Step 8 - Type the following command and press Enter.
fastboot flash boot boot.img
Step 9 - Then, type the following command and press Enter.
fastboot reboot
I just want my phone back to normal please! I don't care about rooting anymore. Thank you.
Click to expand...
Click to collapse
Alright, the ROMs you've been trying to flash are for the quad core One X... please stay in this forum and you should be good to go!
Any ROMs and kernels from here http://forum.xda-developers.com/forumdisplay.php?f=1541 and here http://forum.xda-developers.com/forumdisplay.php?f=1726. Try to flash something from there and report back (you'll still need to flash boot.img
RollTribe said:
Alright, the ROMs you've been trying to flash are for the quad core One X... please stay in this forum and you should be good to go!
Any ROMs and kernels from here http://forum.xda-developers.com/forumdisplay.php?f=1541 and here http://forum.xda-developers.com/forumdisplay.php?f=1726. Try to flash something from there and report back (you'll still need to flash boot.img
Click to expand...
Click to collapse
Thank you very much for your help? Could you please point me to a ROM to flash? I looked through those links and have no idea which to pick/what to do. It doesn't even have to be 4.2...I just want a working phone again. Thanks again!
zenkix said:
Thank you very much for your help? Could you please point me to a ROM to flash? I looked through those links and have no idea which to pick/what to do. It doesn't even have to be 4.2...I just want a working phone again. Thanks again!
Click to expand...
Click to collapse
Well... What would you like? Completely stock? Sense with tweaks? 4.2 with minor tweaks? 4.2 with a ton of tweaks?
RollTribe said:
Well... What would you like? Completely stock? Sense with tweaks? 4.2 with minor tweaks? 4.2 with a ton of tweaks?
Click to expand...
Click to collapse
4.2 with minor tweaks sounds great! Although right now I kinda just want to the stock "boot.img" to verify that my phone is still usable and not totally bricked.
zenkix said:
4.2 with minor tweaks sounds great! Although right now I kinda just want to the stock "boot.img" to verify that my phone is still usable and not totally bricked.
Click to expand...
Click to collapse
Alright then CM10.1 http://forum.xda-developers.com/showthread.php?t=2064621 and AOKP http://forum.xda-developers.com/showthread.php?t=2064724 will both suit you. These have the different boot.img than stock, but just extract and fastboot flash boot boot.img and you should be good to go!
RollTribe said:
Alright then CM10.1 http://forum.xda-developers.com/showthread.php?t=2064621 and AOKP http://forum.xda-developers.com/showthread.php?t=2064724 will both suit you. These have the different boot.img than stock, but just extract and fastboot flash boot boot.img and you should be good to go!
Click to expand...
Click to collapse
Quick update...I flashed boot.img of the first link (CynogenMod) and my phone got passed the "HTC Quietly Brilliant" screen! But now it seems stuck on HTC One (Beats Audio at the bottom) screen. I'll give it a few minutes...
I'm really worried that I did major damage to my phone in the bootloader and clockwork recovery menus. I literally tried every single option there trying to get my phone to boot earlier.
Oh man...it seems stuck. Maybe I should just flash the completely stock boot.img file. If that works, I will factory reset my phone just to make sure everything is back to how it was before.
Dude it sounds like you're trying to flash a cm boot.img with a Sense ROM, that ain't gonna work. You can't just extract a boot.img and flash it with a different ROM.
You need to extract the boot.img from the ROM you're about to flash, then flash that ROM, then flash the boot.img you just extracted.
Sent from my Evita
timmaaa said:
Dude it sounds like you're trying to flash a cm boot.img with a Sense ROM, that ain't gonna work. You can't just extract a boot.img and flash it with a different ROM.
You need to extract the boot.img from the ROM you're about to flash, then flash that ROM, then flash the boot.img you just extracted.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for your help man. If what you're saying is correct, does that mean my phone is hopeless? I deleted/wiped everything using the ClocworkMod Recovery menu. When I choose "install zip from sdcard" I get "E: Can't mount /sdcard/" and when I try to mount an sdcard I get "Error mounting /sdcard". I don't think I can flash any ROMs right now unless install zip from sideload is an option (I don't know how sideloading works).
Try using TWRP recovery instead, you'll find it here:
http://goo.im/devs/OpenRecovery/evita
Download it, check md5 is correct, then:
fastboot flash recovery filename.img
(Filename = exact TWRP recovery filename)
Then issue this command:
fastboot erase cache
Then:
fastboot reboot-bootloader
Now you should be able to select recovery on your phone screen and it should boot into TWRP. Next go to mount and mount usb storage. See if it comes up in Windows, it might need to be formatted from the sounds of it. If it doesn't show up as a usable drive, format it to fat32.
Once that's done you should be able to copy a ROM to your phone to flash. So copy it over, then extract the boot.img from the copy on your pc, then put the boot.img in your fastboot folder.
Do a full wipe in recovery (cache/dalvik/factory reset/system), then install the ROM, then reboot to bootloader, make sure phone is connected by usb, make sure fastboot usb comes up on your phone screen then issue the following command:
fastboot flash boot boot.img
Make sure it's the boot.img from the ROM you just flashed. Now once that's done you should be able to reboot into the ROM.
Sent from my Evita
timmaaa said:
Try using TWRP recovery instead, you'll find it here:
http://goo.im/devs/OpenRecovery/evita
Download it, check md5 is correct, then:
fastboot flash recovery filename.img
(Filename = exact TWRP recovery filename)
Then issue this command:
fastboot erase cache
Then:
fastboot reboot-bootloader
Now you should be able to select recovery on your phone screen and it should boot into TWRP. Next go to mount and mount usb storage. See if it comes up in Windows, it might need to be formatted from the sounds of it. If it doesn't show up as a usable drive, format it to fat32.
Once that's done you should be able to copy a ROM to your phone to flash. So copy it over, then extract the boot.img from the copy on your pc, then put the boot.img in your fastboot folder.
Do a full wipe in recovery (cache/dalvik/factory reset/system), then install the ROM, then reboot to bootloader, make sure phone is connected by usb, make sure fastboot usb comes up on your phone screen then issue the following command:
fastboot flash boot boot.img
Make sure it's the boot.img from the ROM you just flashed. Now once that's done you should be able to reboot into the ROM.
Sent from my Evita
Click to expand...
Click to collapse
This sounds like a good plan. I will give it a try tomorrow after work. Thank you guys for your help!
I couldn't sleep...so I followed your steps and my phone is now alive! Thank you!
I think now I need to flash GApps, right? I have this ---> gapps-jb-20130301-signed.zip
Any chance that's the wrong zip file? Do I need a special one for CM10.1?
That's the right gapps zip, it's the most recent one so yeah you're good to flash it.
And no problems, you're welcome
Sent from my Evita
I am hoping that I can find help out there. My phone will not load past the splash screen.
Over the last few days I have been trying to install a custom rom on my phone. I thought I was on the right track and now I have flashed it but it will not go past the splash screen. I would be grateful for any advice on how to get my phone back functioning. I would even be happy to have it back stock.
So my movements over the last few days have been as follows:
1) HTC DEV unlocked the bootloader
2) Used Hasoon2000's HTC Sensation 4G all-in-one to flash CWM.
3) Then the same tool to copy Prem Root onto the SD card and installed it via CWM.
4) Then used this post here to install JB Miui - http://miuiandroid.com/community/threads/how-to-update-upgrade-miui.15424/
Then when I rebooted it is stuck on the Miui splash screen.
At every stage I felt like things worked well and now I have that sad feeling in my stomach because I have just realized how vital my phone is.
Any help would be greatly appreciated.
Did u flash boot.img after u flashed the rom? Did u full wipe before flashing the rom? Also with s-on users its recommended to use 4ext recovery and in recovery, enable smartflash.
Where can I find information about boot.img - so that is a no. I am installing 4ext now.
jmcclue said:
Did u flash boot.img after u flashed the rom? Did u full wipe before flashing the rom? Also with s-on users its recommended to use 4ext recovery and in recovery, enable smartflash.
Click to expand...
Click to collapse
ok, so I have been looking at the boot.img part and I found this video: http://www.youtube.com/watch?v=5xVl2dBTnmI
I have followed it but still am not having any luck.
Still very lost.
LiamRutherford said:
ok, so I have been looking at the boot.img part and I found this video: http://www.youtube.com/watch?v=5xVl2dBTnmI
I have followed it but still am not having any luck.
Still very lost.
Click to expand...
Click to collapse
open rom.zip and search for the boot.img
probably it is located in the kernel folder
place it in the folder where you have adb and fastboot files
now boot your device to the bootloader and connect it to pc via usb(in the hboot screen it should say fastboot usb)
in the folder where you have adb and fastboot files open a cmd window and do this command
fastboot flash boot boot.img
then
fastboot reboot
done
rzr86 said:
open rom.zip and search for the boot.img
probably it is located in the kernel folder
place it in the folder where you have adb and fastboot files
now boot your device to the bootloader and connect it to pc via usb(in the hboot screen it should say fastboot usb)
in the folder where you have adb and fastboot files open a cmd window and do this command
fastboot flash boot boot.img
then
fastboot reboot
done
Click to expand...
Click to collapse
Thanks - this did the trick. Now to hunt out roms.
LiamRutherford said:
Thanks - this did the trick. Now to hunt out roms.
Click to expand...
Click to collapse
as suggested before it is better to have 4ext recovery
and before flashing any rom enable smartflash from it(for S-ON devices)
smartflash it does exactly what i said above
Okay I was flashing a ROM for the S4 version and the phone began rebooting in the middle of the flash. I realize my error so lets not focus on that Im just trying to fix the boot loop issue. Im trying to use fastboot to fix it but when the phone is connected to my windows 7 PC it makes the connected sound but the device cannot be found by fastboot and it is not shown in the sidebar tree. I cannot get into recovery the TRWP splash screen is displayed for 10 seconds then it goes to the HTC developers use only screen. Please help. Are there any options to repair the damage?
sideshow03 said:
Okay I was flashing a ROM for the S4 version and the phone began rebooting in the middle of the flash. I realize my error so lets not focus on that Im just trying to fix the boot loop issue. Im trying to use fastboot to fix it but when the phone is connected to my windows 7 PC it makes the connected sound but the device cannot be found by fastboot and it is not shown in the sidebar tree. I cannot get into recovery the TRWP splash screen is displayed for 10 seconds then it goes to the HTC developers use only screen. Please help. Are there any options to repair the damage?
Click to expand...
Click to collapse
Okay so can someone confirm then that I am out of luck on this one:?
sideshow03 said:
Okay so can someone confirm then that I am out of luck on this one:?
Click to expand...
Click to collapse
What is device manager showing when your phone is connected to pc while in bootloader (fastboot USB)
for example here is mine:
tivofool said:
What is device manager showing when your phone is connected to pc while in bootloader (fastboot USB)
for example here is mine:
Click to expand...
Click to collapse
It looks the same as yours. But Im not able to connect to the pc to transfer the ROM over. What do I need to do please and thank you?
sideshow03 said:
It looks the same as yours. But Im not able to connect to the pc to transfer the ROM over. What do I need to do please and thank you?
Click to expand...
Click to collapse
well don't give up then, it isn't bricked.
I'm guessing the way you worded it, you have a villeC2 (S3) version and you flashed (S4) ROM? So just make sure you have the S3 version of TWRP flashed and flash a boot.img and rom. wipe caches and you should be fine.
Never mind that if your phone is S4 and I misinterpreted that.
With phone in Bootloader, (fastboot USB) try and check fastboot devices again. Opening your folder with fastboot in it and shift right click, pick open command window.
fastboot devices
(should show a serial #)
flash recovery again, since it was bootlooping. That will probably allow it to be stable again so you can mount USB storage.
If you are in bootloader (fastboot USB) and command window on pc is ran from the correct folder but it still shows device cannot be found then reinstall fastboot drivers. That should fix it for you.
tivofool said:
well don't give up then, it isn't bricked.
I'm guessing the way you worded it, you have a villeC2 (S3) version and you flashed (S4) ROM? So just make sure you have the S3 version of TWRP flashed and flash a boot.img and rom. wipe caches and you should be fine.
Never mind that if your phone is S4 and I misinterpreted that.
With phone in Bootloader, (fastboot USB) try and check fastboot devices again. Opening your folder with fastboot in it and shift right click, pick open command window.
fastboot devices
(should show a serial #)
flash recovery again, since it was bootlooping. That will probably allow it to be stable again so you can mount USB storage.
If you are in bootloader (fastboot USB) and command window on pc is ran from the correct folder but it still shows device cannot be found then reinstall fastboot drivers. That should fix it for you.
Click to expand...
Click to collapse
Im on the S4 variant my error was not flashing the boot.img separately
Im needing to run the cmd as admin so Im opening it up from the start button and changing the directory to the folder fastboot is in. I did get a serial # HT251W408295 fastboot. as shown
Just to confirm my next step is to flash recovery so my command line should be C:\Android fastboot flash recovery twrp2.1.6-ville.img
Correct?
Im using an older twrp cause I read that the newest one is not the best for HTC one S devices.
Thanks
sideshow03 said:
Im on the S4 variant my error was not flashing the boot.img separately
Im needing to run the cmd as admin so Im opening it up from the start button and changing the directory to the folder fastboot is in. I did get a serial # HT251W408295 fastboot. as shown
Just to confirm my next step is to flash recovery so my command line should be C:\Android fastboot flash recovery twrp2.1.6-ville.img
Correct?
Im using an older twrp cause I read that the newest one is not the best for HTC one S devices.
Thanks
Click to expand...
Click to collapse
That would work, BUT:
I see Maximus HD in that pic. For Maximus and any other ROM that uses 2.16 HBoot you can only use the recovery provided in the Maximus original post. It has been modified to work with the new partitions.
If you have moved back to or are still on HBoot 2.15 older firmware, then yes go ahead and flash like you are.
---------- Post added at 07:07 PM ---------- Previous post was at 07:04 PM ----------
oh, and usb storage (mount sd card) will not be available on this new recovery.
Easy way to move a ROM onto the phone while in this recovery is adb push
put ROM.zip in the adb folder and type in command window:
adb push filename.zip /sdcard
tivofool said:
That would work, BUT:
I see Maximus HD in that pic. For Maximus and any other ROM that uses 2.16 HBoot you can only use the recovery provided in the Maximus original post. It has been modified to work with the new partitions.
If you have moved back to or are still on HBoot 2.15 older firmware, then yes go ahead and flash like you are.
---------- Post added at 07:07 PM ---------- Previous post was at 07:04 PM ----------
oh, and usb storage (mount sd card) will not be available on this new recovery.
Easy way to move a ROM onto the phone while in this recovery is adb push
put ROM.zip in the adb folder and type in command window:
adb push filename.zip /sdcard
Click to expand...
Click to collapse
Ok I have both packages now but when I try to flash twrp is shows FAILED (remote: image error! (BootMagic check fail)).
I have verified the md5 with HASHCALC.
Im lost but feel like Im getting somewhere
sideshow03 said:
Ok I have both packages now but when I try to flash twrp is shows FAILED (remote: image error! (BootMagic check fail)).
I have verified the md5 with HASHCALC.
Im lost but feel like Im getting somewhere
Click to expand...
Click to collapse
Is your bootloader locked? Can't install recoveries with locked bootloader.
tivofool said:
Is your bootloader locked? Can't install recoveries with locked bootloader.
Click to expand...
Click to collapse
No I am Unlocked S-off CID 11111111
sideshow03 said:
No I am Unlocked S-off CID 11111111
Click to expand...
Click to collapse
Sorry, you need to extract that zip on your pc and put the recovery.img in your folder. Or I guess just extract it in that same folder you are using.
then depending on the name of the recovery.img flash that. But I think that extracts to recovery.img
so
fastboot flash recovery recovery.img
tivofool said:
Sorry, you need to extract that zip on your pc and put the recovery.img in your folder. Or I guess just extract it in that same folder you are using.
then depending on the name of the recovery.img flash that. But I think that extracts to recovery.img
so
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Ok Ive completed that and the phone went into recovery, i can see the ROM when I click on the install tab. But when I trying to install the ROM i get E: Unable to open zip file Error flashing zip
sideshow03 said:
Ok Ive completed that and the phone went into recovery, i can see the ROM when I click on the install tab. But when I trying to install the ROM i get E: Unable to open zip file Error flashing zip
Click to expand...
Click to collapse
One of the possibilities with that error is a bad download. You may have to redownload the ROM.
Another is if you change the name of the rom, just in case you did that.
Solved
tivofool said:
One of the possibilities with that error is a bad download. You may have to redownload the ROM.
Another is if you change the name of the rom, just in case you did that.
Click to expand...
Click to collapse
Yes it was a bad download. Thanks for all of your help I really appreciate your time to help me get back up and running. :victory:
After update to cm-11-20140413 and instal newest kernel (Sultan-kernel-Pure-v1.4.0) my htc stuck at cyanogen loading screen. I don't know where's the problem. Maybe someone know the solution.
chmiela1991 said:
After update to cm-11-20140413 and instal newest kernel (Sultan-kernel-Pure-v1.4.0) my htc stuck at cyanogen loading screen. I don't know where's the problem. Maybe someone know the solution.
Click to expand...
Click to collapse
probably your kernel is the problem
try to flash the boot.img of the rom via fastboot command
fastboot flash boot boot.img
by the way are you on S-ON or S-OFF?
rzr86 said:
probably your kernel is the problem
try to flash the boot.img of the rom via fastboot command
fastboot flash boot boot.img
by the way are you on S-ON or S-OFF?
Click to expand...
Click to collapse
Thanks flashing new boot helped
rzr86 said:
probably your kernel is the problem
try to flash the boot.img of the rom via fastboot command
fastboot flash boot boot.img
by the way are you on S-ON or S-OFF?
Click to expand...
Click to collapse
I have the same problem, but i cant find the command in the bootloader
Noam_Nissel said:
I have the same problem, but i cant find the command in the bootloader
Click to expand...
Click to collapse
actually you type the command from pc
connect your device to pc in fastboot mode(in the hboot screen should say fastboot usb)
extract the boot.img from the rom and place it in your adb/fastboot folder
then open a cmd window in that folder and type the command
press enter
rzr86 said:
actually you type the command from pc
connect your device to pc in fastboot mode(in the hboot screen should say fastboot usb)
extract the boot.img from the rom and place it in your adb/fastboot folder
then open a cmd window in that folder and type the command
press enter
Click to expand...
Click to collapse
i don't fully understand what to do, can you be more detailed?
Noam_Nissel said:
i don't fully understand what to do, can you be more detailed?
Click to expand...
Click to collapse
ok
boot your device to the bootloader and select fastboot
then connect it to pc
now in your pc navigate to the folder where you have adb and fastboot(i assume you have installed sdk tools)
in that folder press shift + right click
you will see an option open a command window here
then a black window will appear
in that window type the command and press enter
but don't forget first to place the boot.img to the adb/fastboot folder
rzr86 said:
ok
boot your device to the bootloader and select fastboot
then connect it to pc
now in your pc navigate to the folder where you have adb and fastboot(i assume you have installed sdk tools)
in that folder press shift + right click
you will see an option open a command window here
then a black window will appear
in that window type the command and press enter
but don't forget first to place the boot.img to the adb/fastboot folder
Click to expand...
Click to collapse
i have this problem agian, and it doesnt help this time
Noam_Nissel said:
i have this problem agian, and it doesnt help this time
Click to expand...
Click to collapse
what kind of problem and what did you do now?
rzr86 said:
what kind of problem and what did you do now?
Click to expand...
Click to collapse
every rom im installing is getting me into bootloop, i've tried to install from revcovery and from fastboot, and it always the same problem
Noam_Nissel said:
every rom im installing is getting me into bootloop, i've tried to install from revcovery and from fastboot, and it always the same problem
Click to expand...
Click to collapse
i replied in the other thread
Does S-on and S-off matter for this issue?
Hi,
I am facing the same issue, my Sensation z710e is stuck in Cyanogenmod boot logo. following are the details.
bootloader unlocked
s-on
rooted
cwm recovery installed
tried latest CM10 for pyramid devices
I didnt try 'fastboot flash boot boot.img' command yet but i would like to know if s-on matters, my device is already rooted with cwm recovery.
I am having a similar issue as well. I have followed the instructions in this thread [ROM][STABLE][Android 4.4.4] CyanogenMod 11 with 3.0.16 kernel [July 18, 2014]. I have followed all the steps including doing a full wipe, flashed the ROM zip, gapps zip, and the aroma installer for the flash kernel several times with the same result. My screen keeps getting stuck on the white HTC loading screen.
Currently I have restored my phone to my previous ROM using a backup through 4ext recovery (v1.0.0.6 RC2). My HTC Sensation 4G T-mobile is unlocked and rooted with s-on. I have smartflash enabled on 4ext and my ROM is currently stock android 4.0.3. I did search the above mentioned thread for similar issues and a potential solution but none of the things I tried worked.
I would appreciate any help on how to fix this problem. If you need additional information I would be glad to provide it.
Tried another re-install today and everything worked fine, I guess the 5th time is the charm? I still don't know why it didn't work the other times, I did the exact same thing each time.
Hello guys!
I have a problem with my HTC Sensation.
I wanted to install rom from : http://forum.xda-developers.com/showthread.php?t=2530073 so i downloaded ROM ang minimum pack of GAPPS and after full wipe i install this two zips. In bootloader all operations end sucesfull but now when i try to run htc stuck on HTC splash screen..
What i do wrong? Where is a problem?
Big thank you for all your answers
blackchart said:
Hello guys!
I have a problem with my HTC Sensation.
I wanted to install rom from : http://forum.xda-developers.com/showthread.php?t=2530073 so i downloaded ROM ang minimum pack of GAPPS and after full wipe i install this two zips. In bootloader all operations end sucesfull but now when i try to run htc stuck on HTC splash screen..
What i do wrong? Where is a problem?
Big thank you for all your answers
Click to expand...
Click to collapse
R u s-on? If so u will need to flash boot.img from fastboot everytime u flash rom or flash 4ext recovery and enable smart flash.
jmcclue said:
R u s-on? If so u will need to flash boot.img from fastboot everytime u flash rom or flash 4ext recovery and enable smart flash.
Click to expand...
Click to collapse
Tank you for your answer...
But how shoud i properly flash boot.img from fastboot?
blackchart said:
Tank you for your answer...
But how shoud i properly flash boot.img from fastboot?
Click to expand...
Click to collapse
boot your device to the bootloader
select fastboot and connect it to the pc
place the boot.img of the rom in your adb/fastboot folder
open a cmd window in that folder and type the command
fastboot flash boot boot.img
then type fastboot reboot
done
328
rzr86 said:
boot your device to the bootloader
select fastboot and connect it to the pc
place the boot.img of the rom in your adb/fastboot folder
open a cmd window in that folder and type the command
fastboot flash boot boot.img
then type fastboot reboot
done
Click to expand...
Click to collapse
Big thank you for your answer!
I have only a few more question...
I have problem with see my phone in windows... in fastboot i have information fasboot usb but windows says that he could connect usb devices.. it could be a problem conntected with windows 8.1?
my second question - adb/fastboot is a path on my sd card or phone? on my sd card i dont have this path...
my third and last question - from http://forum.xda-developers.com/showthread.php?t=2699401 i can only download rom and kernel zip package... i dont have *.img file in this package. From where can i get this boot.img - should i convert my *.zip file to get boot.img?
Please help me!
blackchart said:
Big thank you for your answer!
I have only a few more question...
I have problem with see my phone in windows... in fastboot i have information fasboot usb but windows says that he could connect usb devices.. it could be a problem conntected with windows 8.1?
my second question - adb/fastboot is a path on my sd card or phone? on my sd card i dont have this path...
my third and last question - from http://forum.xda-developers.com/showthread.php?t=2699401 i can only download rom and kernel zip package... i dont have *.img file in this package. From where can i get this boot.img - should i convert my *.zip file to get boot.img?
Please help me!
Click to expand...
Click to collapse
first thing windows 8.1->big problem you will face connectivity issues
adb/fastboot folder in your pc not sdcard or phone
the boot.img is located in the rom.zip
extract it from there
about w8 search how to set up adb/fastboot(or htc drivers) in w8 if you face connectivity issues