i was rooting my htc one x that when well when i tried to flash a rom to it i somehow deleted everything stock os everything i can still get to the bootloader and root screen please some one help me get my phone back and working again??????
What hboot do u have 1.14?
---------- Post added at 12:30 AM ---------- Previous post was at 12:30 AM ----------
And don't worry your phone isn't close to being bricked :victory:
If you want to return to stock unrooted just lock the bootloader via fastboot and install the ruu for your device.
boot into bootloader, run "fastboot oem lock", then run the ruu afterwards
I'm sure someone can provide you your devices ruu download, just be patient.. or if you want a rom installed I'm pretty sure you have to install the boot.IMG first then rom after that after clearing caches.
what is a ruu and can someone give me a step by step process im using the bootloader from onexroot.com i have hboot 1.14 yes
im using team win recovery project v2.3.1.0
The reason your phone didn't boot up all the way was because 1 you flashed wrong Rom or 2 you dint flash the boot IMG separately because your on hboot 1.14
---------- Post added at 02:22 AM ---------- Previous post was at 02:21 AM ----------
Do. you know how to flash the boot IMG through fastboot?
omario8484 said:
The reason your phone didn't boot up all the way was because 1 you flashed wrong Rom or 2 you dint flash the boot IMG separately because your on hboot 1.14
---------- Post added at 02:22 AM ---------- Previous post was at 02:21 AM ----------
Do. you know how to flash the boot IMG through fastboot?
Click to expand...
Click to collapse
no i do not i just downloaded the ruu file
C:\Users\NJHCphotography2012>fastboot erase cache
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
this is a message i am currently getting so i think this is hindering me from recovery any solutions?
If u want to run the ruu go into fastboot from there in command prompt type fastboot OEM lock
Locks your bootloader than go into bl mode and run the ruu... But al you have to do is flash the boot IMG from the Rom and your device will be functional and running that Rom you should read a bit.more
omario8484 said:
If u want to run the ruu go into fastboot from there in command prompt type fastboot OEM lock
Locks your bootloader than go into bl mode and run the ruu... But al you have to do is flash the boot IMG from the Rom and your device will be functional and running that Rom you should read a bit.more
Click to expand...
Click to collapse
C:\Users\NJHCphotography2012>fastboot OEM lock
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
im still getting this message in the command prompt when i try to do it
randyarenz said:
im still getting this message in the command prompt when i try to do it
Click to expand...
Click to collapse
Whoa, there, slow down, hoss.
It's obvious from this thread that you're in way over your head. You should not even be rooting before you even know what a RUU or bootloader is, or how to run fastboot correctly.
First, make sure you have the HTC drivers installed on your computer.
Second, you have to run the command in command prompt from the same directory that you put fastboot.exe.
When you relock and run the RUU, you will be stock, locked, and unrooted. Stay there until you've done a lot more reading and understand what it is you're doing to your phone.
Also, stay away from onexroot.com, which is mainly for the international version. Stuff from there may brick your phone.
iElvis said:
Whoa, there, slow down, hoss.
First, make sure you have the HTC drivers installed on your computer.
Second, you have to run the command in command prompt from the same directory that you put fastboot.exe.
Click to expand...
Click to collapse
Should've said that too thanks for putting that out there
I have a feeling he doesn't even have the sdk installed..... If you do OP open the folder where your android sdk platform-tools folder and hold shift on your keyboard right click on your mouse and chose open command prompt here it will open the cmd window where you need to type your commands like the others told you.... GL and please make sure you read and understand everything before doing ANYTHING
Sent from my Nexus 7 using xda app-developers app
Try this tread may be easier for you to lock bootloader.
Just make sure you read carefully
http://forum.xda-developers.com/showthread.php?t=1952426
Make your way to Onex general and find gunnymans quick and dirty adb and fastboot thread. Download adb. extract. RIGHT CLICK ON THE ADB FOLDER and choose "open command prompt here"
Nowwww you can type fastboot oem lock
That will lock bootloader. Now run the ruu, but you have to have HTC sync or it won't work :/
Good luck and have patience
Sent from my One X using Tapatalk 2
Thanks for all the advice my manager helped me out I had everything right except for a working rom
InflatedTitan said:
Make your way to Onex general and find gunnymans quick and dirty adb and fastboot thread. Download adb. extract. RIGHT CLICK ON THE ADB FOLDER and choose "open command prompt here"
Click to expand...
Click to collapse
As an addendum, you will have to hold down the shift key and then right click for the "open command prompt here" option to appear in the context menu.
Ok new help
I've been trying to install new roms I have backups I'm not worried about losing the stuff but when ever I flash the rom it says mdk5 file not found then proceeds and confuses me to boot up but it just stays on the rom screen and doesn't do anything I know that's because the mdk5 file is needed to run it I'm using viperxl and I also have a clean Rom that works and thoughts? Or aybe missing a step or not getting the right download for the rom? Thanks in advance.
randyarenz said:
I've been trying to install new roms I have backups I'm not worried about losing the stuff but when ever I flash the rom it says mdk5 file not found then proceeds and confuses me to boot up but it just stays on the rom screen and doesn't do anything I know that's because the mdk5 file is needed to run it I'm using viperxl and I also have a clean Rom that works and thoughts? Or aybe missing a step or not getting the right download for the rom? Thanks in advance.
Click to expand...
Click to collapse
I'm also using twrp recovery if that helps
i do this in winxp might work on any windows os.
make a file named "install adb fastboot.bat"
add these lines to it then save and run, if you are in vista/7/8 run as admin.
@echo off
cls
copy adb.exe %systemroot%\system32\
copy AdbWinApi.dll %systemroot%\system32\
copy AdbWinUsbApi.dll %systemroot%\system32\
copy fastboot.exe %systemroot%\system32\
pause
exit
make sure those 4 files are in the same folder when you run the .bat file
this will allow you to use adb/fastboot from anywhere you open the command prompt
Related
So i bought a htc one xl on craigslist a few months ago. I downloaded an app to check if its rooted and it said it was. Long story short i think i downloaded the wrong rom and i cleared everything from TWRP. I really have no business doing anything like this.. Now im stuck. I can get to the bootloader mode screen but when i got to recovery it takes me to twrp. I hope i didn't screw it up too bad. TWRP says "no os" also.
Any help would be appreciated! Im done with messing with rooting and such i don't want to mess up my phone anymore.
ps: I didn't do a backup.
Download the right Rom to your computer lets make it viper xl to make things easy once done downloaded mount usb storage in twrp drag the Rom over... Factory reset and flash the Rom and you're good
It installed fine and everything but its been at the viper xl loading screen for 10 minutes. Any reason why its doing this?
Do you have hboot 1.14? And did you factory reset
Yes and Yes
You still have the zip on your computer right? So I guess we're going to have to fastboot the boot.img which is very simple I'll give you a quick tutorial in a sec
---------- Post added at 01:20 AM ---------- Previous post was at 01:19 AM ----------
http://forum.xda-developers.com/attachment.php?attachmentid=1179735&d=1344782533
---------- Post added at 01:22 AM ---------- Previous post was at 01:20 AM ----------
Flashing boot img through fastboot...
download the file in the link which above which will include adb and fastboot....put that on your computer somewhere you can find it.. now take the boot image out of the Rom zip and place it in that folder... Boot your phone into bootloader scroll down and select fastboot and now open a command prompt with in the fastbootbadb folder on your comp and type to command without the quotes "fastboot flash boot boot.img"
I extract the fastboot folder right? I did that and its "saying waiting for device".
Install the drivers
Sorry but where do i find those?
Alright i think i did it right it said finish in the command prop. Now what do i do?
1991birdofprey said:
Alright i think i did it right it said finish in the command prop. Now what do i do?
Click to expand...
Click to collapse
If you have adb/fastboot installed, have a copy if the rom on your phone and also the computer for less confusion. On your computer, extract to rom and copy the boot.img INSIDE your adb/fastboot folder.
Enter boot loader on your phone, (white screen 3 skating droids). Make sure it says fast boot usb. Run a simple command like "fastboot devices" and see if something shows up. If so, proceed. If not, restart computer or make sure drivers are installed.
On your computer, right click on the adb folder and choose "open command prompt here" in the cmd window type->
Fastboot flash boot boot.img
Upon success, immediately boot into recovery (twrp) and flash (install) the entire rom.
Profit
Sent from my HTC One XL using Tapatalk 2
Thanks a bunch guys! I thought i lost my phone! Everything worked!
So I got this help in the CM Q&A but while I've rooted man devices (mostly with oDin and one-click utilities) I've never used ADB and now I'm wanting to go from a sense to AOSP ROM and can't find active links to ADB or tutorials other than (type something here), youtube hasn't been help either, can someone help e out? I had a hboot 1.85 XL so I had it easy when I rooted.
LINKS
3.18 RUU Downloaded
S-Off Thread: http://forum.xda-developers.com/show....php?t=2155071 open in tab but the instructions aren't user friendly
Downgrade Touchscreen: http://forum.xda-developers.com/show....php?t=2159863
TWRP Recovery: http://goo.im/devs/OpenRecovery/evita downloaded
***openrecovery-twrp-2.3.3.1-evita.img or 2.3.3.0 are recommended at the time of this post***
OPTIONAL- Remove red text from splash screen: http://forum.xda-developers.com/show....php?t=2156368
INSTRUCTIONS
Thanks to @InflatedTitan for this breakdown.
While waiting for the RUU to download...
1. Download the 2 files for s-off and place in adb folder.
2. Download the recovery of choice and put in adb folder.
3 (optional) download the remove red text file and put in adb folder.
4. You'll have to downgrade touchscreen if you want to use aosp *SEE NOTE BELOW*. Head to original dev sticky to download files from h8rift. Put those in adb folder
_________________________________________
1. S-off! Make sure you confirm in bootloader (it usually works easier from a sense rom btw.) 4.2.2 roms need updated adb but it may work.
2. When you ruu, it doesn't touch sdcard. But I would quickly mount and backup your pics and whatnot just in case.
3. Enter fast boot. Run the ruu on the computer. It'll bring you back to 100% stock.
4. Once you up and running, enter fast boot again and send twrp. (Instructions below, insert whatever recovery image you're pushing)
Quote:
fastboot flash recovery openrecovery-twrp-2.3.3.1-recovery-evita.img
5. I recommend to get rid of the ugly ass red text on splash. Follow Liam's thread to rid it.
6. While in fastboot go ahead and downgrade touchscreen following h8rifts instructions.
7. Now you're golden to flash anything you want :thumbup:
*Note as of the 06/26 Nightly, you do NOT need to downgrade your touchscreen. However if you encounter any touch-related problems using TWRP 2.3.3.x, you should flash the downgrade in fastboot to move on. I'd recommend 2.5.0.0 on the latest touchpanel firmware. It works for me but if you run into trouble, downgrade the touchscreen and flash the recommended TWRP recovery.
ADB is a command line shell for accessing your phone remotely using linux commands. So many linux command line commands will work within adb. To become an ADB master, use linux command line.
As for downloading ADB and fastboot...
https://dl.dropboxusercontent.com/u/19685555/fb-adb.zip
I guess I'll stick to sense based ROM's because that wasn't helpful but thanks.
Edit after hours searching came across helpful info, but after changing the directory and putting int adb reboot bootloader i get "error device not found" when my phone is connected, any clue?
USFguy said:
I guess I'll stick to sense based ROM's because that wasn't helpful but thanks.
Click to expand...
Click to collapse
eh? What is it you want to know?
Here's a link to adb breakdown and commands? I googled "adb commands" and it was the first link...............
http://forum.xda-developers.com/showthread.php?t=2141817
Is this what you were looking for?
exad said:
eh? What is it you want to know?
Here's a link to adb breakdown and commands? I googled "adb commands" and it was the first link...............
http://forum.xda-developers.com/showthread.php?t=2141817
Is this what you were looking for?
Click to expand...
Click to collapse
"error: device not found"
USFguy said:
"error: device not found"
Click to expand...
Click to collapse
this is what i got....
USFguy said:
this is what i got....
Click to expand...
Click to collapse
is your phone plugged in with the rom booted and USB debugging turned on?
exad said:
is your phone plugged in with the rom booted and USB debugging turned on?
Click to expand...
Click to collapse
yeah, i uninstaleld HTC sync then went into device manager and updated the driver and it worked, I'm s-off and now waiting for RUU to finish
USFguy said:
yeah, i uninstaleld HTC sync then went into device manager and updated the driver and it worked, I'm s-off and now waiting for RUU to finish
Click to expand...
Click to collapse
current issue is in regards to "Quote:
fastboot flash recovery openrecovery-twrp-2.3.3.1-recovery-evita.img
"
I have openrecovery-twrp-2.3.3.1-recovery-evita.img in my c:\fb-adb folder and running the command from there but it's saying "error: cannot load 'openrecovery-twrp-2.3.3.1-recovery-evita.img'
USFguy said:
current issue is in regards to "Quote:
fastboot flash recovery openrecovery-twrp-2.3.3.1-recovery-evita.img
"
I have openrecovery-twrp-2.3.3.1-recovery-evita.img in my c:\fb-adb folder and running the command from there but it's saying "error: cannot load 'openrecovery-twrp-2.3.3.1-recovery-evita.img'
Click to expand...
Click to collapse
That means you're typing the filename wrong. Type the first few letters and then press tab. It will auto complete the file name for you.
exad said:
That means you're typing the filename wrong. Type the first few letters and then press tab. It will auto complete the file name for you.
Click to expand...
Click to collapse
i'm actually getting the no devices connected again since the ruu finished running.
Press and hold power until the phone shuts off then press and hold volume down until the bootloader comes on then try again
Sent from my HTC One X using xda app-developers app
USFguy said:
current issue is in regards to "Quote:
fastboot flash recovery openrecovery-twrp-2.3.3.1-recovery-evita.img
"
I have openrecovery-twrp-2.3.3.1-recovery-evita.img in my c:\fb-adb folder and running the command from there but it's saying "error: cannot load 'openrecovery-twrp-2.3.3.1-recovery-evita.img'
Click to expand...
Click to collapse
Twrp 2.6 works great. No real reason for 2.3.3.1 anymore but nostalgia.
Sent from my HTC One XL using xda premium
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.
I am new to htc
i am flashing a custom rom for first time on htc
what do i have to know?
and what is needed?
and i am stuck on soft brick and cant mount internal storage
i am using
hboot 2.15
it shows tampered
and twrp 2.8
Tampered is shown because you probably unlocked your bootloader on the HTC dev site (which is the first thing you should do anyway)
Now, taking in consideration what you said in the Candy thread, can you enter in fastboot mode? You can do this by entering in bootloader (with phone off, keep pressed the vol down and press power). On the bootloader screen navigate with vol up/down and select with power button. Enter fasboot from there and while you connect the phone to pc via USB you should notice on uour screen a line saying "fastboot USB"
After this you shoul be able to flash the kernel in that mode. You should have ADB installed for this on your pc (it is done by installing the Android SDK) and the ADB/fastboot drivers working.
Let us know how it goes so far then we can go further
Sent from nowhere over the air...
Rapier said:
Tampered is shown because you probably unlocked your bootloader on the HTC dev site (which is the first thing you should do anyway)
Now, taking in consideration what you said in the Candy thread, can you enter in fastboot mode? You can do this by entering in bootloader (with phone off, keep pressed the vol down and press power). On the bootloader screen navigate with vol up/down and select with power button. Enter fasboot from there and while you connect the phone to pc via USB you should notice on uour screen a line saying "fastboot USB"
After this you shoul be able to flash the kernel in that mode. You should have ADB installed for this on your pc (it is done by installing the Android SDK) and the ADB/fastboot drivers working.
Let us know how it goes so far then we can go further
Sent from nowhere over the air...
Click to expand...
Click to collapse
Do i need to s off
and ive noticed that even after flashing rom system folder is empty except for bin and by the way my device is t mobile
S-off is not mandatory but is good to have as the whole flashing process will be much easier. Is it somewhere in the bootloader screen written UNLOCKED? Above or below the "tampered"...
Sent from nowhere over the air...
Rapier said:
S-off is not mandatory but is good to have as the whole flashing process will be much easier. Is it somewhere in the bootloader screen written UNLOCKED? Above or below the "tampered"...
Sent from nowhere over the air...
Click to expand...
Click to collapse
unlocked yes i did it but i cant flash the rom it wont be pushed into system at all
please my mind is not clear can you give me a link for kernal pleaseee
Kernel that you must flash in fastboot is the file boot.img located in the system folder in the ROM"s zip....that is, you'll have to open the zip you're flashing, go to system and extract that boot.img file. Save it on your pc in the same location where fastboot and adb are installed then open a command prompt there. You can flash it using the "fastboot flash boot boot.img" command
Edit: Here's an XDA tutorial how to do it in detail
http://forum.xda-developers.com/showthread.php?t=1752270
Sent from nowhere over the air...
Rapier said:
Kernel that you must flash in fastboot is the file boot.img located in the system folder in the ROM"s zip....that is, you'll have to open the zip you're flashing, go to system and extract that boot.img file. Save it on your pc in the same location where fastboot and adb are installed then open a command prompt there. You can flash it using the "fastboot flash boot boot.img" command
Edit: Here's an XDA tutorial how to do it in detail
http://forum.xda-developers.com/showthread.php?t=1752270
Sent from nowhere over the air...
Click to expand...
Click to collapse
ive restored from ruu
Rapier said:
Kernel that you must flash in fastboot is the file boot.img located in the system folder in the ROM"s zip....that is, you'll have to open the zip you're flashing, go to system and extract that boot.img file. Save it on your pc in the same location where fastboot and adb are installed then open a command prompt there. You can flash it using the "fastboot flash boot boot.img" command
Edit: Here's an XDA tutorial how to do it in detail
http://forum.xda-developers.com/showthread.php?t=1752270
Sent from nowhere over the air...
Click to expand...
Click to collapse
Why my device wont s-off its always telling me to f***off
eswarvf said:
Why my device wont s-off its always telling me to f***off
Click to expand...
Click to collapse
What RUU Worked?
eswarvf said:
Why my device wont s-off its always telling me to f***off
Click to expand...
Click to collapse
În order to properly s-off, you might need a certain ROM to be installed. Have you tried to get s-off having that stock ROM you got after RUU?
Sent from nowhere over the air...
Can s-off be achieved without an installed ROM?
bobby2x420 said:
Can s-off be achieved without an installed ROM?
Click to expand...
Click to collapse
Only by a j-tag device but I don't know how that works. The software methods presented here needs a ROM as far as I know
Sent from nowhere over the air...
bobby2x420 said:
What RUU Worked?
Click to expand...
Click to collapse
Ya it worked (not androidruu though) i had to search a lot i got tired of it