[FIRMWARE][GPE] Lollipop 5.11.1700.3 + hboot 1.57 (NO WIPE) - One (M7) Android Development

Here is the latest GPE Firmware extracted from the 5.0.1 OTA. This has the red warning removed on the HBOOT 1.57 zips
Click to expand...
Click to collapse
READ THESE BEFORE FLASHING
Flashing the NO WIPE zips will not touch your SD Card (But always backup just in case)
Flashing the other zips WILL WIPE YOUR SD CARD, so do a backup before flashing
You need to be s-off to flash this
Charge your phone to at least 40%
These firmwares are safe to flash but are always flashed at your own risk
Click to expand...
Click to collapse
100% ORIGINAL 5.11.1700.3 FIRMWARE
Download: firmware_lp_gpe-original.zip
md5 Checksum: 2913b3bcd655a15a58efaf2bd92a8883
ORIGINAL 5.11.1700.3 FIRMWARE - NO WIPE VERSION with TWRP 2.6.3.3
Download: firmware_lp_gpe_orig-NOWIPE.zip
md5 Checksum: 9f8d938c4af3d5968858c8d1f067f543
Click to expand...
Click to collapse
GPE FIRMWARE WITH HBOOT 1.57 AND UNLOCKED ICON GONE!
Download: firmware_lp_gpe-hboot157.zip
md5 Checksum: af34fc7bf5fda0060537775d1d30f330
GPE FIRMWARE WITH HBOOT 1.57 AND UNLOCKED ICON GONE - NO WIPE VERSION with TWRP 2.6.3.3
Download: firmware_lp_gpe_hb157-NOWIPE.zip
md5 Checksum: f6aec17709eeea2437e87af540257049
As I said, the GPe Unlocked Icon is gone from the splashscreen, the bootloader is the white HBOOT 1.57 found in Sense firmware
Click to expand...
Click to collapse
Some technical info about the firmware
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-opendsp: 34.120.274.0429
(bootloader) version-main: 5.11.1700.3
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
To flash type in the commands below
Code:
cd (to location of firmware)
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip filename.zip
(You will get an error - hboot pre! update, just type the following command)
fastboot flash zip filename.zip
fastboot reboot
Click to expand...
Click to collapse
Please press the thanks button if this was useful
Click to expand...
Click to collapse
Click to expand...
Click to collapse
...

thanks mate

EDIT:
Nevermind

dd98 said:
Here is the latest GPE Firmware extracted from the 5.0.1 OTA. This DOES NOT have the red warning removed.
Download: firmware_lp_gpe.zip
md5 Checksum: 2913b3bcd655a15a58efaf2bd92a8883
Some technical info about the new firmware
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-opendsp: 34.120.274.0429
(bootloader) version-main: 5.11.1700.3
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
To flash it (at your own risk) you need to type the following
Code:
cd (to location of firmware)
adb reboot oem-78
fastboot flash zip firmware_lp_gpe.zip
(You will get an error - hboot pre! update, just type the following command)
fastboot flash zip firmware_lp_gpe.zip
fastboot reboot
Please press the thanks button if this was useful [emoji13]
Click to expand...
Click to collapse
Does it wipe the phone?
Sent from my HTC One using Tapatalk

Woohoo! All I need is a CWM flashable zip of Lollipop for my One. Can someone point me to where I can find it? Thanks dd98 and the whole community!

Shadow.Mage said:
Woohoo! All I need is a CWM flashable zip of Lollipop for my One. Can someone point me to where I can find it? Thanks dd98 and the whole community!
Click to expand...
Click to collapse
I flashed a TWRP nandroid back up and it's running great
Sent from my HTC One using Tapatalk

Stupid question but I have to ask... Dirty flash or full wipe? I'm running stock rooted GPe ROM.

Shadow.Mage said:
Stupid question but I have to ask... Dirty flash or full wipe? I'm running stock rooted GPe ROM.
Click to expand...
Click to collapse
Regarding the nandroid backup? Gotta wipe first then flash,then flash su
Sent from my HTC One using Tapatalk

question.com said:
Regarding the nandroid backup? Gotta wipe first then flash,then flash su
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Sorry lol! That one slipped right passed me. It's a nandroid not a zip.

question.com said:
Does it wipe the phone?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
no, but always do backups

dd98 said:
no, but always do backups
Click to expand...
Click to collapse
Nice. Will flash now. Thanks
Sent from my HTC One using Tapatalk
---------- Post added at 03:23 PM ---------- Previous post was at 03:05 PM ----------
dd98 said:
no, but always do backups
Click to expand...
Click to collapse
Installed, doesn't have the red warning. Just the unlocked icon.
Side note, I used to have firmware 609.401.10 this one is 5.11.1700.3 so is this an older firmware? Also, hboot is older.
Sent from my Nexus 7 using Tapatalk

Do I have to flash TWRP after flashing this firmware?

question.com said:
Nice. Will flash now. Thanks
Sent from my HTC One using Tapatalk
---------- Post added at 03:23 PM ---------- Previous post was at 03:05 PM ----------
Installed, doesn't have the red warning. Just the unlocked icon.
Side note, I used to have firmware 609.401.10 this one is 5.11.1700.3 so is this an older firmware? Also, hboot is older.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
the 6.09.401.10 firmware is sense firmware, 5.11.1700.3 is gpe firmware. they are both completely separate but the 5.11.1700.3 is the newer firmware but for some strange reason, htc and google still stick with hboot 1.54

elbos2k said:
Do I have to flash TWRP after flashing this firmware?
Click to expand...
Click to collapse
if you want to flash roms, kernels, root and modifications then yes

dd98 said:
the 6.09.401.10 firmware is sense firmware, 5.11.1700.3 is gpe firmware. they are both completely separate but the 5.11.1700.1 is the newer firmware but for some strange reason, htc and google still stick with hboot 1.54
Click to expand...
Click to collapse
Thanks for the clarification
Sent from my HTC One using Tapatalk

dd98 said:
if you want to flash roms, kernels, root and modifications then yes
Click to expand...
Click to collapse
I meant reflash. I already have GPE 5.0 installed just wondering if updating the firmware is worth it. Currently on a ATT firmware...

elbos2k said:
I meant reflash. I already have GPE 5.0 installed just wondering if updating the firmware is worth it. Currently on a ATT firmware...
Click to expand...
Click to collapse
if your running a gpe rom at the moment, then your firmware is already updated then, but re-flashing twrp is what i did after installing gpe because i needed to root

dd98 said:
if your running a gpe rom at the moment, then your firmware is already updated then, but re-flashing twrp is what i did after installing gpe because i needed to root
Click to expand...
Click to collapse
How do you manage to flash twrp? Coz the stock recovery cant

rhong said:
How do you manage to flash twrp? Coz the stock recovery cant
Click to expand...
Click to collapse
you flash twrp using fastboot, not using the stock recovery.
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootlaoder

alray said:
you flash twrp using fastboot, not using the stock recovery.
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootlaoder
Click to expand...
Click to collapse
Thanks a lot mate

Related

Please help!! Stuck in fastboot after flashing a rom

I tried flashing CM10 onto my AT&T HOX and now I'm stuck in the fastboot menu (picture below)
Let me know what information I could supply that could help
C:\Users\temp\Downloads\OneXUnroot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.16.32.09.01_3
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.73.502.1
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4127mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.080s
Shows "relocked" what did you do there? Can you get into recovery.
Sent from my One X using xda premium
lost45 said:
I tried flashing CM10 onto my AT&T HOX and now I'm stuck in the fastboot menu (picture below)
Click to expand...
Click to collapse
Relocked + custom recovery = no boot
subarudroid said:
Shows "relocked" what did you do there? Can you get into recovery.
Sent from my One X using xda premium
Click to expand...
Click to collapse
I was trying to follow some instructions from another website to flash it back to stock and I did a oem relock
And no I can't get into recovery, just the bootloader menu and the fastboot menu.
lost45 said:
I was trying to follow some instructions from another website to flash it back to stock and I did a oem relock
And no I can't get into recovery, just the bootloader menu and the fastboot menu.
Click to expand...
Click to collapse
You have to unlock again.
iElvis said:
You have to unlock again.
Click to expand...
Click to collapse
Could you point me in the right direction on how to do this from fastboot?
Edit: Just realized it has to be in fastboot to unlock the bootloader.
I'll post results after I do this.
lost45 said:
Could you point me in the right direction on how to do this from fastboot?
Click to expand...
Click to collapse
How did you do it the first time? You just flash the same unlock token you used before.
After I reunlock it should I flash the stock recovery?
Then what would my next step be?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
lost45 said:
After I reunlock it should I flash the stock recovery?
Then what would my next step be?
Click to expand...
Click to collapse
What are you trying to do? Flash CM?
iElvis said:
What are you trying to do? Flash CM?
Click to expand...
Click to collapse
At this point I'd like to flash anything that can work. If I can do CM10 that would be great.
Newest Update:
I have TWRP successfully running. How can I copy the .zip onto the sdcard now?
lost45 said:
At this point I'd like to flash anything that can work. If I can do CM10 that would be great.
Click to expand...
Click to collapse
Once you reunlock, you may or may not still have root. Open superuser or SuperSU (whatever you have installed), go into settings, and turn it off and back on again. Then check a root app to see if you're still rooted. If all you did was relock, you should still be rooted.
If that's the case, reboot to recovery and flash away. You have the old hboot so you don't need to worry about flashing boot.imgs.
ok, if you can get back to square 1 (any rom installed, any recovery installed) and get into bootloader and recovery you will be fine. remember when flashing a rom to the One X, you must do "fastboot flash boot boot.img" from terminal before you proceed and flash from twrp (or whatever recovery you use). otherwise it will flash but not boot.
so i recommend:
1. going into your recovery and clearing EVERYTHING (cache, dalvik, data) and then get back into fastboot mode.
2. running the "fastboot flash boot boot.img" from terminal on your PC
3. exiting bootloader and getting into recovery
4. flash the rom/gapps/root zips
if this doesnt work, then let me know. i'll try my best to help you out
EDIT: sorry, just saw that you had the old hboot.... never mind about all those steps :/ i honestly dont know what you should do next, since you dont need to flash the boot.img...
tyessen said:
ok, if you can get back to square 1 (any rom installed, any recovery installed) and get into bootloader and recovery you will be fine. remember when flashing a rom to the One X, you must do "fastboot flash boot boot.img" from terminal before you proceed and flash from twrp (or whatever recovery you use). otherwise it will flash but not boot.
so i recommend:
1. going into your recovery and clearing EVERYTHING (cache, dalvik, data) and then get back into fastboot mode.
2. running the "fastboot flash boot boot.img" from terminal on your PC
3. exiting bootloader and getting into recovery
4. flash the rom/gapps/root zips
if this doesnt work, then let me know. i'll try my best to help you out
EDIT: sorry, just saw that you had the old hboot.... never mind about all those steps :/ i honestly dont know what you should do next, since you dont need to flash the boot.img...
Click to expand...
Click to collapse
I have TWRP working now so I'm going to try to find a good ROM and flash it through recovery.
I'll let you know how it goes
UPDATE: Flashing CM10 with a nightly failed, it would just sit at the start up screen. I flashed the stable CM10 from here: http://get.cm/?device=evita&type=stable which worked!
Now I just need to flash gapps
lost45 said:
I have TWRP working now so I'm going to try to find a good ROM and flash it through recovery.
I'll let you know how it goes
Click to expand...
Click to collapse
ok, hope it works if you get it to work and it runs fine, make a backup in twrp so you always have a safety-blanket if something goes wrong someday
CM10 should boot fine just make sure you wiped everything and flash boot.img in fastboot
CM10 went on smoothly and its all set. Thanks for the help!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
You might want to edit your first post to take out your imei, serial # etc...
Sent from my HTC One XL using xda premium
iElvis said:
Once you reunlock, you may or may not still have root. Open superuser or SuperSU (whatever you have installed), go into settings, and turn it off and back on again. Then check a root app to see if you're still rooted. If all you did was relock, you should still be rooted.
If that's the case, reboot to recovery and flash away. You have the old hboot so you don't need to worry about flashing boot.imgs.
Click to expand...
Click to collapse
I know this is an old thread, but I have the same issue, but when I flash anything it just bootloops still. And my dalvik cache wipe always fails when I try to do that. I dunno why that is.
Read 4 posts up.. Flash boot.IMG first. And wipe everything
Sent from my One X using xda premium

Updated TWRP 2.7.0.0 for Ville

It worked great for me. I just tested it with a back up and restore from internal as well as an OTG cable.
http://teamw.in/project/twrp2
What rom you have?
I know that for some 4.2.2 rom is better to keep the modified twrp 2.6.1.0
Here you can find a modified version of the latest TWRP that works correctly on hboot 2.16, which have the data/media storage partition in the same system partition.
Yep, thank you! Works just fine for me.
I've installed Liberty ROM 6b and hboot is 2.16. which one is proper for my device?
mosi-comp said:
I've installed Liberty ROM 6b and hboot is 2.16. which one is proper for my device?
Click to expand...
Click to collapse
The version for hboot 2.16:
/data/media storage partition (HBOOT 2.16.0000 only)
twrp-2.7.0.5-ville-dm.img (9 MB)
pandolf84 said:
Here you can find a modified version of the latest TWRP that works correctly on hboot 2.16, which have the data/media storage partition in the same system partition.
Click to expand...
Click to collapse
There are a lot of issue with this recovery because since /sdcard is on /data/media and there is no symlink to /sdcard, than a lot of installer and aroma installer will fail during zip flashing...
also it would be nice if backup is done like 2.6.1.0 (accessible from sdcard/TWRP/backups)
and also it would be nice if the default directory points to /sdcard and not /
I'm having issues with mounting to usb with this version of twrp. It wont connect via ADB or as a storage device =/
Naiks20 said:
I'm having issues with mounting to usb with this version of twrp. It wont connect via ADB or as a storage device =/
Click to expand...
Click to collapse
Did you flash the correct version for your boot? Also note that no recovery for 2.16 will be able to mount as usb due to new partition layout which is not fat32 anymore. You can mount a usb otg or otherwise use adb sideload feature (google it). This is not the fault of the dev.
Sent from my KFAPWI using Tapatalk
---------- Post added at 10:14 PM ---------- Previous post was at 10:11 PM ----------
pandolf84 said:
Here you can find a modified version of the latest TWRP that works correctly on hboot 2.16, which have the data/media storage partition in the same system partition.
Click to expand...
Click to collapse
Your latest unofficial twrp is working great for me on the 2.16 hboot. Stable so far and when I reboot to system there are no multiple reboots or other issues.
Have you thought about posting the link in the htc one s development forum? A lot of folks who may be interested tend to view that subforum more than this one. Also I had a bit of trouble downloading the link. I had to tell my browser to download the target and had to rename to .img as it was originally trying to download and open as a webpage.
Sent from my KFAPWI using Tapatalk
This recovery works great also for me, but i'm not the developer of this mod.
I don't remember who have posted on xda forum the link of MDMower website.
Bye
T-Mobile HTC One S won't enter recovery
I flashed openrecovery-twrp-2.7.1.0-ville.img onto my t-mobile htc one s (i wish i knew the model number i think it may be the pj40100 or the z520e or both, the z520e pj40100 and i'm running hboot 2.15.0 with bootloader unlocked s-on After flashing i rebooted the bootloader and then tried to go into recovery but the phone just goes into a loop of failed system boot attemps and the white htc quietly brilliant screen just goes on and off over and over until i hold down the power button long enough to power down the phone Phone has a brand new battery that I used another phone to fully charge What could be the problem?
Maybe you have to delete twrp-folder from SD card and retry...
I flashed this to my One S T-Mobile but phone can't enter recovery
I flashed this to my One S T-Mobile but phone can't enter recovery and returns to white htc quietly brilliant screen going on and off
What's your flash command and steps....?
Unable to boot or enter recovery
fastboot flash recovery openrecovery-twrp-2.7.0.0-ville
foeti said:
What's your flash command and steps....?
Click to expand...
Click to collapse
---------- Post added at 07:52 PM ---------- Previous post was at 07:45 PM ----------
There's no sd card present and I tried clear storage from bootloader didn't help the phone doesn't boot to system or recovery i'm running mainver 3.14 installed via ruu hboot 2.15 I'm thinking i need to flash boot.img maybe i dunno
foeti said:
Maybe you have to delete twrp-folder from SD card and retry...
Click to expand...
Click to collapse
I've got exactly the same problem with my HTC ONE S ville. Cannot get TWRP 2.7.1.2 or any newer version to work, only bootloop. Just wanted to install cm11 on H-Boot 2.15 unlocked, S-OFF :crying::crying:
rifek4 said:
Use unofficial TWRP v2.8.5.5, -> LOOK HERE <-. From me recommend CyanogenMod 12 or other ROM's on this base (Candy5, Resurrection Remix, PAC-MAN)
Click to expand...
Click to collapse
Unfortunately no luck at all. The only Recovery I got to work is "openrecovery-twrp-2.6.3.0-ville-selinux.img" but this one is to old to flash new roms. I can flash CM10 with it, but it is also not booting. Here are the details of my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.16.31501S.17_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.77.111.5
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 3870mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I send it to a specialist (someone with a Riff Box xD), because I bricked the bootloader (QHUSB_DLOAD). I got the phone back with unlocked super cid hboot 2.15. That are very good prerequisites, but as I said no Recovery works for me. No Philz, no offical or inoffical twrp. This device is the first one in my "carrier" that is really frustrating me...
First: Please delete your serial number and your imei. Just for your own safety.
And second: As your "fastboot getvar all" output states your phone is on hboot 1.09 and not 2.15. So that's the culprit for your problems.
Just flash a RUU that corresponds to your CID and update your phone to the latest firmware version using the OTA function of the stock rom. If you can't find a suitable RUU get S-OFF by flashing a Sense based rom and using either rumrunner or facepalm. After that you will be able to use every RUU you want. If you use facepalm just be careful not to install OTAs before you undo SuperCID or you will brick your phone.
P.S.: Maybe there's a faster method to solve your problems but that's actually what I would do.
Thank you for the advice, normally I delete those data but it was to late for thinking clearly xD
The vars I posted were the ones before I bricked the phone. I got it back with the values I described after that. But I was not able to update TWRP and in general not able to boot any ROM flashed with old TWRP. But after one week of pain I found this awesome Thread http://forum.xda-developers.com/showthread.php?t=2751518 the RUU updated the whole phone to Hboot 2.16 and suddenly I was able to install TWRP 2.8.5.5-ville and flash the special Hboot 2.16 version of cm11. I had to flash boot.img manually, because S-OFF was gone after RUU update, no big deal. I'm happy now =)

[Q] Boot Loop(I can enter into hboot but recovery doesn't work)

Hi everyone. I had maximun HD rom installed and working for several months but, one day my htc one s stars a infinite boot loop. I can enter into Hboot mode but when I try enter into recovery, do clear storage or do a factory reset it just restarts as it does when it try to boot the system.
I tried reflashing the recovery but it had no effect, also tried to reflash the boot.img but the same.
I'm stuck .
firmware info:
version: 0.5
version-bootloader: 2.16.0000
version-baseband: 1.20.50.05.16
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: HT24FW403470
imei: 359902041309034
product: vle
platform: HBOOT-8960
modelid: PJ4011000
cidnum: T-MOB010
battery-status: low
battery-voltage: 3283mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4958290506
hbootpreupdate: 11
gencheckpt: 0
Thanks for your help n_n
realityrd said:
Hi everyone. I had maximun HD rom installed and working for several months but, one day my htc one s stars a infinite boot loop. I can enter into Hboot mode but when I try enter into recovery, do clear storage or do a factory reset it just restarts as it does when it try to boot the system.
I tried reflashing the recovery but it had no effect, also tried to reflash the boot.img but the same.
I'm stuck .
Thanks for your help n_n
Click to expand...
Click to collapse
May you post your firmware infos? HBOOT version, CID, radio...
LS.xD said:
May you post your firmware infos? HBOOT version, CID, radio...
Click to expand...
Click to collapse
Thanks, I updated the post.
realityrd said:
Thanks, I updated the post.
Click to expand...
Click to collapse
You can flash this firmware update to fix your phone. It will set it back to HBOOT 2.15 and stock radio. Then you can run the stock RUU or flash a new custom recovery + rom
firmware.zip for T-MOB010--> LINK
Here is how to flash it --> GUIDE
You will need to charge your battery first as it has to be at least 30% charged. I'd suggest to charge it to 70% just to be safe.
Sounds like you got the same issue I got last year and only running a RUU fixed it.
LS.xD said:
You can flash this firmware update to fix your phone. It will set it back to HBOOT 2.15 and stock radio. Then you can run the stock RUU or flash a new custom recovery + rom
firmware.zip for T-MOB010--> LINK
Here is how to flash it --> GUIDE
You will need to charge your battery first as it has to be at least 30% charged. I'd suggest to charge it to 70% just to be safe.
Click to expand...
Click to collapse
I'll try as soon as I charge the phone, I'm having difficulties doing that. Thanks n_n
LS.xD said:
You can flash this firmware update to fix your phone. It will set it back to HBOOT 2.15 and stock radio. Then you can run the stock RUU or flash a new custom recovery + rom
firmware.zip for T-MOB010--> LINK
Here is how to flash it --> GUIDE
You will need to charge your battery first as it has to be at least 30% charged. I'd suggest to charge it to 70% just to be safe.
Click to expand...
Click to collapse
I have flashed the the firmware but I'm still unable to go into recovery mode :crying:
realityrd said:
I have flashed the the firmware but I'm still unable to go into recovery mode :crying:
Click to expand...
Click to collapse
I assume you can get into the boot loader. Maybe lock the boot loader and run the RUU to get back to stock. Someone else chime in if you have better suggestions please.
realityrd said:
I have flashed the the firmware but I'm still unable to go into recovery mode :crying:
Click to expand...
Click to collapse
Did you perform "factory reset / clear storage" in bootloader mode before you installed the custom recovery again?
808phone said:
I assume you can get into the boot loader. Maybe lock the boot loader and run the RUU to get back to stock. Someone else chime in if you have better suggestions please.
Click to expand...
Click to collapse
Already did, I had the very same thing happen to me.
LS.xD said:
Did you perform "factory reset / clear storage" in bootloader mode before you installed the custom recovery again?
Click to expand...
Click to collapse
It doesn't matter what you do only RUU will fix this.
LS.xD said:
Did you perform "factory reset / clear storage" in bootloader mode before you installed the custom recovery again?
Click to expand...
Click to collapse
nope, I just followed the guide
Darknites said:
Already did, I had the very same thing happen to me.
It doesn't matter what you do only RUU will fix this.
Click to expand...
Click to collapse
How i can know what is my correct RUU file. I have S-off (does It matter?)
realityrd said:
How i can know what is my correct RUU file. I have S-off (does It matter?)
Click to expand...
Click to collapse
OK, now I could be wrong but you being S-OFF means you can install any RUU. But obviously I would install one that matches the country/carrier and processor.
realityrd said:
How i can know what is my correct RUU file. I have S-off (does It matter?)
Click to expand...
Click to collapse
Any will do since you got S-Off.
realityrd said:
How i can know what is my correct RUU file. I have S-off (does It matter?)
Click to expand...
Click to collapse
This is the matching RUU for taking your phone back to full stock --> LINK
You probably will need to flash the included recovery before you run the RUU.
LS.xD said:
This is the matching RUU for taking your phone back to full stock --> LINK
You probably will need to flash the included recovery before you run the RUU.
Click to expand...
Click to collapse
Include recovery? You mean the stock recovery?
Thanks n_n
Don't Flash CWM Latest.
Guys Don't flash CWM Lastest Version from its website. It doesn't work. Try TWRP 2.4 or above.
Jnanadarshan said:
Guys Don't flash CWM Lastest Version from its website. It doesn't work. Try TWRP 2.4 or above.
Click to expand...
Click to collapse
Which recovery version doesn't work?
6.0.4.6
LS.xD said:
Which recovery version doesn't work?
Click to expand...
Click to collapse
Version 6.0.4.6 Doesn't work.
Jnanadarshan said:
Version 6.0.4.6 Doesn't work.
Click to expand...
Click to collapse
At all? Or for specific roms?

[Q] K2_UL breaked during official update, what can I do?

Hi everyone
I decided to update my HTC one sv using wifi, but after reboot, the cell phone stay on htc logo.
I can go to bootloader but not recovery, it seams official recovery is damaged.
S-on
Locked
HBOOT 2.00
Radio 1.15.40a.00. 04
Can anyone help? Should I use RUU file? What if there was not suitable RUU out there?
You can find everything you need to fix your phone here:
http://forum.xda-developers.com/showthread.php?t=2292432
HTC K2_PLC_CL
Thanks alot for your reply but I don't know where to start. For example which ruu is suitable for my device?
Or can I unlock the bootloader at this situation to install custom rom in case of unavailability of suitable ruu rom?
Sent from my HTC One using Tapatalk
If your phone is locked and S-On (and never was unlocked S-off), you should think about returning for warranty.
The warranty period is already expired. Another solution?
Sent from my HTC One using Tapatalk
More information about your phone model, please!
I dont think he can use an RUU. Last I checked, the available RUU's for you guys is based on ICS. Because he is S-On he can't use it since it would require downgrading. Would need to be S-Off to do that.
If there is a JB RUU for you guys then he is good to go, but I haven't seen one yet.
Sent from my C525c using Tapatalk
old.splatterhand said:
More information about your phone model, please!
Click to expand...
Click to collapse
What information exactly?
Sent from my HTC One using Tapatalk
Modding.MyMind said:
I dont think he can use an RUU. Last I checked, the available RUU's for you guys is based on ICS. Because he is S-On he can't use it since it would require downgrading. Would need to be S-Off to do that.
If there is a JB RUU for you guys then he is good to go, but I haven't seen one yet.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Can I S-OFF only through hboot and without working android os?
Sent from my HTC One using Tapatalk
salehi.com said:
Can I S-OFF only through hboot and without working android os?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
No!
Connect your phone with fastboot and type into the cmd:
Code:
fastboot getvar all
Put the output here (except your IMEI & Serial number)
old.splatterhand said:
No!
Connect your phone with fastboot and type into the cmd:
Code:
fastboot getvar all
Put the output here (except your IMEI & Serial number)
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: 1.15.40a.00.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.708.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ************
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8015000
(bootloader) cidnum: HTC__622
(bootloader) battery-status: good
(bootloader) battery-voltage: 3842mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.078s
- unlock your bootloader at htcdev.com
- flash k2ul recovery with fastboot
- wipe everything in recovery (except internal & external sd)
- flash a stock rom from recovery (either 4.1.2 or 4.2.2)
- get S-Off: if 4.1.2 rom, then use moonshin.io or if 4.2.2 rom use rumrunner.us
- after you are S-off you get a firmware.zip from me, wich updates your phone/radio related to your modelid, so you can run the latest 4.2.2 software without bugs
You can find everything you need in my index thread, which is linked in my signature.
Good luck!
old.splatterhand said:
- unlock your bootloader at htcdev.com
- flash k2ul recovery with fastboot
- wipe everything in recovery (except internal & external sd)
- flash a stock rom from recovery (either 4.1.2 or 4.2.2)
- get S-Off: if 4.1.2 rom, then use moonshin.io or if 4.2.2 rom use rumrunner.us
- after you are S-off you get a firmware.zip from me, wich updates your phone/radio related to your modelid, so you can run the latest 4.2.2 software without bugs
You can find everything you need in my index thread, which is linked in my signature.
Good luck!
Click to expand...
Click to collapse
Thanks alot for your step by step guide.
Step one have been done!
In step two, there are a lot of recovery there but none of them are compatible with my device(version-main: 2.14.708.5)
http://forum.xda-developers.com/showthread.php?t=2317379
can you please give a link of recovery for above version?
And after that in step 3, should i use the following link?
http://forum.xda-developers.com/showthread.php?t=2512742
TWRP Recovery 2.7.0.1
- unlock your bootloader at htcdev.com Done.
- flash k2ul recovery with fastboot Done.
- wipe everything in recovery (except internal & external sd) Done.
- flash a stock rom from recovery (either 4.1.2 or 4.2.2) Done. k2ul_4.2.2_3.11.401.1_stock_odexed_v3.zip
- get S-Off: if 4.1.2 rom, then use moonshin.io or if 4.2.2 rom use rumrunner.us Unsuccessful(rumrunner)! Here's the log:
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (37/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: Download updated package at www.rumrunner.us
Press ENTER to exit
salehi.com said:
- unlock your bootloader at htcdev.com Done.
- flash k2ul recovery with fastboot Done.
- wipe everything in recovery (except internal & external sd) Done.
- flash a stock rom from recovery (either 4.1.2 or 4.2.2) Done. k2ul_4.2.2_3.11.401.1_stock_odexed_v3.zip
- get S-Off: if 4.1.2 rom, then use moonshin.io or if 4.2.2 rom use rumrunner.us Unsuccessful(rumrunner)! Here's the log:
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (37/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: Download updated package at www.rumrunner.us
Press ENTER to exit
Click to expand...
Click to collapse
Did you use rumrunner universal?
Sent from my C525c using Tapatalk
Modding.MyMind said:
Did you use rumrunner universal?
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Yes.
salehi.com said:
Yes.
Click to expand...
Click to collapse
Make sure you do not have a lockscreen password of any kind turned on. Must be off.
Sent from my C525c using Tapatalk
Modding.MyMind said:
Make sure you do not have a lockscreen password of any kind turned on. Must be off.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
The screen lock is already None
Settings-Security-Screen lock-none
Do you have root? If not (because rom is stock), flash SuperSu.zip, linked in my index thread and don't forget to allow root permission to adb shell!

I have no ROM. How install one?

Hi there!
I unlock the bootleader and root my device (HTC One S) to install another ROM.
I have done a full clean, so I have nothing. I installed the clockworkmod recovery.
What Can I do to install the factory rom and let my device like factory, but with the bootloader unlocked?
PD: Sorry with my english.
jajasuperman said:
Hi there!
I unlock the bootleader and root my device (HTC One S) to install another ROM.
I have done a full clean, so I have nothing. I installed the clockworkmod recovery.
What Can I do to install the factory rom and let my device like factory, but with the bootloader unlocked?
PD: Sorry with my english.
Click to expand...
Click to collapse
You can relock your bootloader, flash a RUU (stock firmware package), unlock the bootloader again. Or you can just flash a sense based custom rom. BUT if I was you, I would go for a Kitkat (Android 4.4.4) or Lollipop (5.0.2) custom rom, as it really improves your One S
LS.xD said:
You can relock your bootloader, flash a RUU (stock firmware package), unlock the bootloader again. Or you can just flash a sense based custom rom. BUT if I was you, I would go for a Kitkat (Android 4.4.4) or Lollipop (5.0.2) custom rom, as it really improves your One S
Click to expand...
Click to collapse
Thanks for answering.
I prefer the second jejeje
Which rom would you recommend me? It doenst matter if it is kitkat or lollipop. I wanna use the mobile
I dont know if it is a S3 or S4 :S
jajasuperman said:
Thanks for answering.
I prefer the second jejeje
Which rom would you recommend me? It doenst matter if it is kitkat or lollipop. I wanna use the mobile
I dont know if it is a S3 or S4 :S
Click to expand...
Click to collapse
Thats quite bad Are you familiar with using fastboot commands? Its important if its S3 or S4.
LS.xD said:
Thats quite bad Are you familiar with using fastboot commands? Its important if its S3 or S4.
Click to expand...
Click to collapse
Yes, I have installed some recoveryes using it
What should I do?
jajasuperman said:
Yes, I have installed some recoveryes using it
What should I do?
Click to expand...
Click to collapse
Connect phone in "fastboot" mode to your computer.
Open command line and type:
fastboot getvar all
Post the output here but remove your "IMEI"
LS.xD said:
Connect phone in "fastboot" mode to your computer.
Open command line and type:
fastboot getvar all
Post the output here but remove your "IMEI"
Click to expand...
Click to collapse
Here u have:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH24WW408505
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4174mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
HTC One S - S4 - Europe
1. step: flash actual recovery
Fastboot flash recovery openrecovery-twrp-2.8.5.0-ville.img
Once done choose your rom from HERE
LS.xD said:
HTC One S - S4 - Europe
1. step: flash actual recovery
Fastboot flash recovery openrecovery-twrp-2.8.5.0-ville.img
Once done choose your rom from HERE
Click to expand...
Click to collapse
Installed.
I´ll choose this: http://forum.xda-developers.com/htc-one-s/development/rom-resurrection-remix-lollipop-t2986405
What is the second step?
jajasuperman said:
Installed.
I´ll choose this: http://forum.xda-developers.com/htc-one-s/development/rom-resurrection-remix-lollipop-t2986405
What is the second step?
Click to expand...
Click to collapse
Download ROM - GApps - SuperSU
copy all to your sdcard. (you can connect your phone via twrp recovery: "Mount" --> "Enable MTP"
then press "Install" and select the downloaded zips.
Order: 1. Rom 2. GApps 3. SuperSU (4. Kernel)
You can optionally use a "custom kernel" e.g. Frosted Kernel which can be controlled with Trickster Mod
LS.xD said:
Download ROM - GApps - SuperSU
copy all to your sdcard. (you can connect your phone via twrp recovery: "Mount" --> "Enable MTP"
then press "Install" and select the downloaded zips.
Order: 1. Rom 2. GApps 3. SuperSU
Click to expand...
Click to collapse
I tried only flashing the Rom, and when I reboot, I see a black screen and the device do nothing :S
The Roms says something habout 2.15 and 2.16. Do I nothing something else?
jajasuperman said:
I tried only flashing the Rom, and when I reboot, I see a black screen and the device do nothing :S
The Roms says something habout 2.15 and 2.16. Do I nothing something else?
Click to expand...
Click to collapse
Yup i forgot that your phone is S-ON. S-ON means you need to flash the kernel manually via fastboot each time you install a rom. Flash 1. 2. 3. and then connect your phone in fastboot mode to the computer.
Extract "boot.img" from the rom.zip and flash it via fastboot:
Fastboot flash boot boot.img
LS.xD said:
Yup i forgot that your phone is S-ON. S-ON means you need to flash the kernel manually via fastboot each time you install a rom. Flash 1. 2. 3. and then connect your phone in fastboot mode to the computer.
Extract "boot.img" from the rom.zip and flash it via fastboot:
Fastboot flash boot boot.img
Click to expand...
Click to collapse
You are the best!
Thank thank thank you very very much DD
Wow
jajasuperman said:
You are the best!
Thank thank thank you very very much DD
Wow
Click to expand...
Click to collapse
You're happy - me too

Categories

Resources