Database Info

[stuck] in joupunt screen after s-off

Hi
GUYS , I've done everything , first the htcdev unlock then the s-off from controlbear
when I rebooted the phone it's either stuck in the fastboot and couldn't flash recovery it says "remote image error! bootmagic check fail"
and when I normally reboot it gets me to joupunutbear blank screen and stuck there
I tried to do this in the cmd
ControlBear.exe -r
but it says error format the sd normally in the pc
and I did that with to deferent sds and nothing happend
any help will be much appreciated :good:

solved it by new firmware and flashing recovery from fastboot

What you should have done before gaining S-OFF with joupunt are': unlocking bootloader through htc dev, flashing clockworkmod, install supersu then you are good to go with no stress. It worked for me like that.
Sent from my HTC Sensation Z710e using xda app-developers app with beat audio

[Q] Help! HTC One S doesnt work.

Help I can not mount storage on phone and I have no os installed. I still have access to recovery.Is their any way to fix this.

RAdical_Future said:
Help I can not mount storage on phone and I have no os installed. I still have access to recovery.Is their any way to fix this.
Click to expand...
Click to collapse
If everything is stock then you need to go into bootloader by hold Vol- when turning it on and do a factory reset.

if the mem card has low free space then sometimes this happens...free some space...and try....
Sent from my One V

Not stock
Darknites said:
If everything is stock then you need to go into bootloader by hold Vol- when turning it on and do a factory reset.
Click to expand...
Click to collapse
No I'm running TWRP recovery and I cant mount storage.

Relock your device and run the appropriate RUU file...this will help
Sent from my HTC VLE_U using xda app-developers app

Hi. You have to flash STOCK recovery back, wipe dáta, then flash TWRP again and sd should mount then. Worked for me. I think there is a sticky in Q&A about this.
Sent from my HTC One S using xda app-developers app

Help.
tominozh said:
Hi. You have to flash STOCK recovery back, wipe dáta, then flash TWRP again and sd should mount then. Worked for me. I think there is a sticky in Q&A about this.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Whenever I connect my phone to the computer it wont recognize it or anything.

Ok, before you relocked your bootloader and flash an RUU, ty this first: go back to the bootloader by holding the down volume and power button. The re flash the stock recovery (not custom recovery).you can find the stock recovery in the threads here. You flash it via fast boot in the bootloader ie fastboot flash recovery ×recovery file×. If you get to your custom recovery you should be able to rype adb reboot bootloader to get you back to the bootloader screen.
Once you have the original recovery flashed try doing a factory reset. The original recovery will run and will reformat your sd card.
This worked for me once when my sd card got corrupted and then I didn't need to relocked my bootloader.
Sent from my HTC One S using xda premium
---------- Post added at 01:30 AM ---------- Previous post was at 01:26 AM ----------
Oh and you should be able to use adb commands when your phone is connected to the computer and you are in custom recovery. So if you have problems getting to your bootloader type the adb reboot bootloader command I described above. And once your in bootloader there should be no reason why your computer won't recognize the fastboot usb. I'd it doesn't you need to un install and re install the drivers on your pc. Then it's not a phone issue.
Sent from my HTC One S using xda premium

Help.
AKToronto said:
Ok, before you relocked your bootloader and flash an RUU, ty this first: go back to the bootloader by holding the down volume and power button. The re flash the stock recovery (not custom recovery).you can find the stock recovery in the threads here. You flash it via fast boot in the bootloader ie fastboot flash recovery ×recovery file×. If you get to your custom recovery you should be able to rype adb reboot bootloader to get you back to the bootloader screen.
Once you have the original recovery flashed try doing a factory reset. The original recovery will run and will reformat your sd card.
This worked for me once when my sd card got corrupted and then I didn't need to relocked my bootloader.
Sent from my HTC One S using xda premium
---------- Post added at 01:30 AM ---------- Previous post was at 01:26 AM ----------
Oh and you should be able to use adb commands when your phone is connected to the computer and you are in custom recovery. So if you have problems getting to your bootloader type the adb reboot bootloader command I described above. And once your in bootloader there should be no reason why your computer won't recognize the fastboot usb. I'd it doesn't you need to un install and re install the drivers on your pc. Then it's not a phone issue.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
What drivers and do you know a guide to install them?

Htc One X with no os

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.

Rom questions

I used the hasoons2000 tool kit. I unlocked bootloader an flashed recovery twrp. What are the steps to flash cyanogen?
Noob question.. -_- don't I need to "root" then flash a rom or will flashing the rom root my phone. I had done this before just for the purpose of controlling my cpu. Soo I didn't really care for roms I just followed a tutorial. I'm inclined enough to get it done so any help would be extremely appreciated.
Sent from my HTC One X using xda app-developers app

Ok so I need to know you're hboot boot into bootloader and that info will be on top...and that's a good question you ask why don't you have root acess yet? Well with newer HTC's we have to unlock bootloader than flash a recovery than flash a Rom or root in your case a Rom which gives you root to .... But what's your hboot? 1.14 or 1.09

1.14 thank you for tryin dude
Sent from my HTC One X using xda app-developers app

Ok so for hboot 1.14 you have to fastboot flash the boot img of the Rom before or after you flash doesn't matter...so do that go wipe in recovery and than go flash the Rom and gapps

So the boot icon from the cm10mod dl I put in my phone so where, boot in recovery an install it. Using twrp
Sent from my HTC One X using xda app-developers app

Nonono! So you see the boot.img from the cm download in the zip take that place it in your adb fastboot folder on your computer wherever you may have...put your phone in fastboot ..open a command prompt from your fastboot folder and type fastboot flash boot boot.I'mg

Does the img an fast boot need to be in there own folder? So do that an then throw the whole zipped rom file on the phone an install through recovery?
Sent from my HTC One X using xda app-developers app

http://forum.xda-developers.com/show....php?t=1671237
Moving on from what isaid download the file in the link which I posted.... Put the boot image 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 I told you to...now go wipe in recovery and install the Rom it doesn't matter if you keep the boot img in the Rom zip or not

AshKohru said:
Does the img an fast boot need to be in there own folder? So do that an then throw the whole zipped rom file on the phone an install through recovery?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
The fastboot is something accessed by going into your bootloader (by holding power+vol down). Then connect your phone to your PC and flash boot.img by typing in: "fastboot flash boot boot.img" in command prompt. The boot.img can be found in every .zip file of a rom

AshKohru said:
Does the img an fast boot need to be in there own folder?
Click to expand...
Click to collapse
As kittens mentioned, boot.img needs to be in the same folder as fastboot.exe. I'd recommend making a folder for these files, somewhere easy to navigate to. You will have to open a command prompt window, then change directory to the folder containing boot.img and fastboot.exe.

tried it, when i turn it on it has the first screen an says devo mode **** an the the screen goes black. plz help i want it normal im done with this

One XL no onger recognizes unlock.bin from HTC DEV

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