greetings,
i have a problem hope that you can help me fix it, yesterday i tried to install custom rom cm10 in the process of doing so i didn't backup my previous kernal and now am stuck with fastboot window with no os installed and i can go to recovery, my cid 11111111 i tried kindle utility app but it didn't work..
please help if you can.
thanks in advanced
If you can get to recovery just flags the ROM you want. Make sure to factory reset and wipe cache and dalvik. If your hboot is 1.14 you'll also need to get the boot.IMG file from the root of the ROM zip and do fast boot flash boot boot.img.
Sent from my One X using xda app-developers app
Disregard.
Sent from my HTC One XL
the problem is that i can't enter the recovery mode to flash any rom so is there any way that i can do it manually using cmd window ??? and btw my hboot is 1.09
jantish said:
the problem is that i can't enter the recovery mode to flash any rom so is there any way that i can do it manually using cmd window ??? and btw my hboot is 1.09
Click to expand...
Click to collapse
Can you put the phone in fastboot mode? Download http://techerrata.com/file/twrp2/evita/openrecovery-twrp-2.3.3.0-evita.img, put it in your fastboot directory, and do fastboot flash recovery openrecovery-twrp-2.3.3.0-evita.img. Then, you can reboot and go into recovery to flash a custom ROM.
Need help i fromatted my SD now i only have twrp 2.2.0 and jelly bam Rom on SD. wont boot past boot screen. need major help it is urgent.
OKAY I SOLVED THE PROBLEM TECHNICALLY. I BASICALLY JUST RELOCKED THE BOOTLOADER AND THEN RAN THE RUU. SO THANKS FOR THE HELP YOU GUYS
BUMP
OK you need to download newest twrp boot img ...put phone in fastboot mode fastboot flash recovery (recovery name) fastboot erase cache
Fastboot reboot
Go into twrp recovery mount SD put new ROM on SD ... flash ROM
Erase both caches
On your CPU go to the zip open it right click on boot IMG choose extract to where you have your fastboot.
Phone in fastboot
Fastboot flash boot ( your boot IMG)
Fastboot erase cache
Fastboot reboot
Wait a few min if no boot put back in recovery erase both caches manually then reboot system.... will work
Sent from my HTC One S using xda premium
---------- Post added at 10:33 PM ---------- Previous post was at 10:27 PM ----------
Sorry forgot while in twrp before you flash ROM wipe factory reset system and both caches all x3 then proceed to install
Sent from my HTC One S using xda premium
Sent from my One S using xda premium
it's just syaing waiting for device
When does it say that...
Sent from my One S using xda premium
$droyd$ said:
When does it say that...
Sent from my One S using xda premium
Click to expand...
Click to collapse
Actually hen i go to fast boot it says device not found. also when im in the bootloader it doee not say "fastboot USB" so idk how to get my computer to find my device
Download and install HTC sync on your PC... Sounds like your missing drivers... Installing HTC sync should give you your drivers...
Sent from my One S using xda premium
Just remember to close HTC Sync before attempting to use adb/fastboot, as HTC Sync likes to mess with the adb connection.
$droyd$ said:
Download and install HTC sync on your PC... Sounds like your missing drivers... Installing HTC sync should give you your drivers...
Sent from my One S using xda premium
Click to expand...
Click to collapse
okay so i downloaded and installed the drivers and htc sync so now do you recommend which recovery to flash ; also it say in the cmd "adb server is out of date... killing" "error device not found"
Hello,
I have got a ville s4 with the newest jb installed. I wanted to get root and installed this kernel: Elemental
After that my device keeps bootlooping, I cant boot into recovery but bootloader.
How can I restore my device to original htc firmware?
please help me,
kind regards
Did you try flashing it from fastboot as instructed in the thread?
"extract boot.img from the zip, reboot to bootloader and do: fastboot flash boot boot.img"
Fails because I relocked the bootloader.
If i want to unlock it, htcdev sais unlockstring is wrong
My fault. I copied wrong. will try now
In recovery now sais "cant mount sd card"
If you relocked it run that appropriate RUU from fastboot and start over
Sent from my HTC VLE_U using xda app-developers app
What hboot is your phone on.?
Sent from my HTC One S using xda premium
I flashed Jellybam by going through their instructions, just going through twrp clearing my data and then flashing the rom.
I am now stuck on the boot logo and can't connect it to the computer as it won't recognize it what can I do at this stage. I followed all the directions, it was rooted. Should i let the battery drain out or what?
Any help would be appreciated.
Did you flash boot.img after flashing rom?
Sent from my HTC One S using xda app-developers app
Did not, I guess that was the problem...from the rom download page did not state I had to do that. How would I flash the boot.img?
NaviJ95 said:
Did not, I guess that was the problem...from the rom download page did not state I had to do that. How would I flash the boot.img?
Click to expand...
Click to collapse
Open ROM on your PC.. Extract it to where you have fastboot installed.. Reboot your phone to bootloader and select fastboot then connect to pc your phone should now say.... fastboot usb.....Open terminal either in that directory or navigate to it and type
Fastboot flash boot boot.img
After its done
Fastboot wipe cache..... Then go back to recovery and wipe both caches it should boot after that..
Sent from my HTC One S using xda premium
Good day everyone.
I relocked and installed stock RUU (4.0.3) on my Evita since I had that failing zip install though TWRP. It worked fine but when I tried to manually install the latest RUU (Android 4.1) it failed. Now I decided to unlock it again and start to flash custom ROMs, problem started.
1.) After flashing boot, recovery and custom rom (tried it with CM 10.1 and JellyBam), it would go only up to the boot image (HTC) and stay on there forever. Cleared everything that I could clear on the recovery and cleared fastboot cache.
What I did, relocked it again and tried running the stock RUU (through the computer) and shows error and won't complete.
2.) Now, phone no longer recognizes the Unlock_code.bin from HTC dev. I tried manually flashing it in fastboot and as well as using the All-in-one-tool for Evita, it would somehow show that it went through on both but looking at my phone, it stays: Relocked. Tried it with at least three unlock bin files to no avail.
3.) Other than that, turning the phone off and back on would go straight to bootloader. When I select Recovery, it would go back straight to fastboot mode. Tried to flash recoveries again, and would get this:
E:\Mobile Devices\sd-fix\Nocturnal_SD_FIX_EVITA\Nocturnal_SD_FIX_EVITA>fastboot
flash recovery openrecovery-twrp-2.5.0.0-evita.img
sending 'recovery' (7992 KB)... OKAY [ 2.140s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.871s
E:\Mobile Devices\sd-fix\Nocturnal_SD_FIX_EVITA\Nocturnal_SD_FIX_EVITA>fastboot
flash recovery openrecovery-twrp-2.2.0-evita.img
sending 'recovery' (7460 KB)... OKAY [ 1.692s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.370s
Now I'm stuck with a phone with no OS. Please help. I appreciate your time.
Here's my phone info.
AT&T HTC One X
S-ON
HBOOT - 2.14.0000
Getting a new code only requires fast boot. So just get a new unlock code.....
*edit*
Sorry I misread. This happened to me. Just simulate a battery pull by pressing and holding power and try again. Keep doing that over and over. Eventually, it will work.
Took me about 10-15 tries once.
Sent from my One X using xda app-developers app
Also try to lock the phone even if it tells you it is already locked.
fastboot oem lock
Do that prior to attempting the unlock after full power cycle. Sometimes that gets the device back on track, dont worry too much this issue is not exactly new and after a bit of dicking around the phone will unlock again.
Thanks for your responses!
Yeah, it did. After a number times requesting for unlock bins and re locking, finally it was unlocked.
Now I now have problem #1 from OP. It actually goes to HTC boot screen, stays there for a couple of seconds then reboot. It's been doing that in a loop. Flashed three different ROMs and three different versions of TWRP and phone still does the same thing.
Found my mainver to be 3.18 which I suspect have been changed when I attempted to run the 4.1 RUU (this was before I tried to unlock the bootloader). Downloaded the said RUU from two different sites just to be sure. None of those have worked.
So I found a thread here in XDA saying that this could be the reason why I couldn't boot any of these ROMs.
Any thoughts/help would be greatly appreciated.
Must not have read very much before trying to root if you don't know fastboot flash boot boot.Img
Sent from my One X using xda app-developers app
You're s-on so you need to flash the boot.img manually on hboot 2.14.
Retrieve the boot.img from the ROM zip and place it in your working directory on your pc.
Copy ROM to phone (if you haven't already done that).
Do a full wipe in recovery, then flash the ROM.
Reboot to the bootloader, connect phone to pc, make sure it says fastboot usb on your phone screen.
Open a command prompt in your working directory and issue the following command:
fastboot flash boot boot.img
Reboot the phone.
Enjoy.
Sent from my Evita
Typically bootloops are solved by
flashing recovery cwm or twrp.
wipe cache, data and system.
Manual install the boot.ing from rom you are installing.
Fastboot flash boot boot.img
Install your rom in recovery.
Hopefully all will work then
Sent from my HTC One XL using xda app-developers app
exad said:
Must not have read very much before trying to root if you don't know fastboot flash boot boot.Img
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
timmaaa said:
You're s-on so you need to flash the boot.img manually on hboot 2.14.
Retrieve the boot.img from the ROM zip and place it in your working directory on your pc.
Copy ROM to phone (if you haven't already done that).
Do a full wipe in recovery, then flash the ROM.
Reboot to the bootloader, connect phone to pc, make sure it says fastboot usb on your phone screen.
Open a command prompt in your working directory and issue the following command:
fastboot flash boot boot.img
Reboot the phone.
Enjoy.
Sent from my Evita
Click to expand...
Click to collapse
twistedddx said:
Typically bootloops are solved by
flashing recovery cwm or twrp.
wipe cache, data and system.
Manual install the boot.ing from rom you are installing.
Fastboot flash boot boot.img
Install your rom in recovery.
Hopefully all will work then
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
It's actually my fourth device. Did flash boot.img all the time. That's why it's kind of frustrating.
Any thoughts about damaged eMMC? Just hypothetical.
I don't know if it was a brick but I had an issue before where this HOXL didn't boot up after flashing a wrong kernel. Didn't even light up when plugged to power and had to re-flash the eMMC block using that WIP method. It went back to life.
Might need to try that again. Would that be possible? Still have to download live ubuntu, though. The one I used before got corrupted.
What I did so far:
-relock
-unlock
-erased fastboot cache
-flashed boot.img ( from the custom ROMs that I've tried )
-flashed twrp ( 3 versions )
-wiped every wipe option i could see
I already have tested at least 6 ROMs on this device with no issue with TWRP.
I had ViperXL installed before this happened. I wiped everything out and tried to flash the ATT Android 4.1 RUU and everything got screwed.
edit: i typed the capcha on the title box. lol
You're still s-on right?
Sent from my One X using xda app-developers app
exad said:
You're still s-on right?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yup!
Is there a way to s-off while you're on fastboot? Facepalm method requires it on booted android. So far can't see other procedures done through fastboot.
EjWilkes0121 said:
Yup!
Is there a way to s-off while you're on fastboot? Facepalm method requires it on booted android. So far can't see other procedures done through fastboot.
Click to expand...
Click to collapse
Get twrp running 2.3.3.1 and flash any sense Rom then s-off
Sent from my HTC One XL using xda premium
I'm going to try again once I get home from work.
Thanks for all your responses guys.
Done it all.
Relocked, intalled RUU - fail.
Unlocked, wiped everything, installed ROM, erased fastboot cache, flashed boot.img, erased fastboot cache - bootloop.
Tried using CWM and same thig happes - bootloops after flashing rom and boot.img
However, I just noticed something.
Whenever I get to flash a zip through recovery, process seems to just complete in no time. I have flashed multiple ROMs and one could really see progress shown on progress bar on both recovery flashing( CM10.1, JellyBam ) and through Aroma installer( CleanROM, ViperXL ).
When this problem started, entire process would initiate, pauses for few seconds then it completes. Can't see the progress bar move across.
I might be going out of topic here but I'm desperate in having this fixed.
Your thoughts and ideas means a lot.
Are there any roms you can boot?? How are you downloading the files? On a pc? Did the md5 match. Maybe the usb wire has a defect and screws the file upon transfer. Your have a really strange issue. I'll flash out of boredom and never had that happen, Even with roms that do nothing more than boot.
And your running twrp 2.3.3.1???
Sent from my HTC One XL using xda premium
I think the recovery is most likely at fault here.
Make sure it's twrp 2.3.3.1: http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img
Use a USB 2.0 port just to be safe.
check md5 omg so important!
Code:
fastboot erase recovery
fastboot flash recovery openrecovery-twrp-2.3.3.1-evita.img
fastboot erase cache
fastboot reboot bootloader
Select recovery
Check the md5 of the sense rom you downloaded
Extract boot.img from rom.
Transfer the rom zip to the phone.
wipe cache, dalvik, system and factory reset in recovery
install sense rom
reboot to bootloader
Code:
fastboot flash boot boot.img
fastboot reboot
Do all that and then tell me what happens.
Back to life!
A huge thanks to you guys! Big time! :victory:
It could be the recovery that screwed it up. Been trying TWRP 2.5 and TWRP 2.2 most of the time. I gave TWRP 2.6 a shot and that made a successful install. I flash ViperXL 3.2.7 + ElementalX 6.7 and phone's back to life!
One thing i noticed. After I S-Off'ed, phone's kind of jerky using normal use. One noticeable thing is the lock screen that doesn't respond after waking, takes 1-2 sec to respond when swiping the lock ring. Big prob for me, battery stuck at 77% even when charged or used heavily. Random reboots also happen. Maybe have to read the entire FacePalm S-Off thread this week. LoL. For now, back to S-On, phone works perfect.
Again, thanks so much for your help guys! Won't be missing any Thank button that you got. :laugh:
I found current sense roms work better with latest firmware so s-off ruu to 3.18 and then see how things run.
Sent from my HTC One X using xda app-developers app