[Q] Stuck at T-Mobile's Stick Together Screen - HTC Sensation

Today I rooted my sensation using clockwork mod recovery and then installed supersu. It was working fine until I restarted my phone. Now whenever I try to turn it on I get stuck the the t-mobile stick together screen. I tryed factory resetting from the bootloader and nothing happened. Please keep any answers noob friendly. Not good with the technical terms. Thanks
Got this info from this command fastboot getvar all
not sure what it means but figured it would help
version: 0.5
version-bootloader: 1.27.0000
version-baseband: N/A
version-cpld: None
version-microp: None
version-main: 3.32.531.14
product: pyramid
platform: HBOOT-8260
modelid: PG5810000
cidnum: T-MOB010
battery-status: good
battery-voltage: 3801mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 617f0a98
hbootpreupdate: 11
gencheckpt: 0

Hi,
Firstly ,you should hide your IMEI and serial number.
Can you please explain again exactly what you were doing?
You do not appear to have any radio...

malybru said:
Hi,
Firstly ,you should hide your IMEI and serial number.
Can you please explain again exactly what you were doing?
You do not appear to have any radio...
Click to expand...
Click to collapse
Okay so first thing I did was install the clockwork mod thing (it opens when I click recovery in bootloader)
Then I installed SuperSu through the sd card and clockwork
My phone worked fine for a little, but then no apps would open and I clicked reboot and it got stuck at the stick together screen... I tried installing mEMBERS rom to fix it just a few minutes ago, but nothing changed... thanks

More detailed steps
First I unlocked the bootloader with htcdev.
Then I flashed clockwork mod using onex installer tool kit (I think it's something like that)
I put the supersu zip on the ad card
I went into bootloader and went to recovery
I installed the supersu zip using that

Relocked the bootloader

reflash the RUU of tmobile one ..this way you can get the phone in working condition but will lose all the data fine ?
connect the phone from bootloader to pc and then double click on RUU thats all (btw you should relock your bootloader ..which i think you did it )
TMOUS ICS RUU ..here

Related

[Q] Trying to get HTC one S on stock rom? Please help ?

I have this HTC one S, I am not sure which network phone is it. I bought is from someone else and he had no idea about network.
Right now when i press factory reset from volume down + power button. it brought me at this screen which say clockwork Mod recovery v 5.8.1.5
I am able to select only first 2 options which are reboot system now and install zip from sdcard . When i pressed install zip from sdcard its not doing anything and bringing me back on same screen
Could you please help me installing stock rom on this phone. ?
Thanks in advance guys
AW: [Q] Trying to get HTC one S on stock rom? Please help ?
If you turn ur phone on with holding power and volume down you should be in your bootloader.
Can you tell us what stands on the top?
Locked/unlocked/relocked and which hboot version?
Sent from my HTC One S using xda premium
this is the info
Tampered
Unlocked
VLE PVT ship s-on RL
HBOOT-1.08.0000
Radi-0.16.31501S.06_3
open DSP-v23.1.0.32.0323
eMMC boot
Mar 21, 2012, 16:01:09
Just curious to know what this information means , please let me know each line if possible. Appreciate your help
AW: [Q] Trying to get HTC one S on stock rom? Please help ?
Tampered: no stock recovery
Unlocked: your bootloader is looked
VLE: Ville: HTC One S
S-ON: security on
Radio: your radio Version
You have to lock your bootloader.
Download the all in one toolkit which you can find in the development section. There are all necessary files.
Be sure you have installed the HTC sync driver.
1. Connect your mobile To your pc when your are in the screen where you can see hboot version etc.
2. There should be "hboot USB" in blue.
3. Navigate to hboot and press power.
4. It should change to "fastboot USB" in red.
5. Then open the all in one toolkit on your PC.
6. Open the folder where ADB and fastboot exe are located.
7. Press shift and right click somewhere in the folder and open the command line.
8. Then type in "fastboot oem lock"
9. If you take a look to your phone you should see that the "unlock" changed To "relocked"
That was the first step.
10. Go To the development section in this forum and look for the wwe europe ville ics ruu 2.31 or sth like that.
11. Download the file
12. Doubleklick the file
13. Follow the instructions
14. Let the ruu install everything
15. If everything works fine you should be on official ICS 4.0.4 with Sense 4.1 now
Good luck!
I hope I wrote an easy understandable instruction.
If u experience any problems feel free to post it here.
I'm sure I or someone else can help you.
Sent from my HTC One S using xda premium
NQNH , thanks a lot for this easy and nice explanation, its really helpful for a noob like me. I have few more questions but lets resolve this issue first. Okay I tried all steps you mentioned and it worked like a charm. just got stuck at final step. Please help.
In CMD i got this
'C:\Users\Owner\Desktop\HTC' is not recognized as an internal or external comman
d,
operable program or batch file.
C:\Users\Owner\Desktop\HTC custom rom procedure\One_S_All-In-One_Kit\data>fastbo
ot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642032 (0x1FDDFD70)
FAILED (status read failed (Too many links))
finished. total time: 0.941s
C:\Users\Owner\Desktop\HTC custom rom procedure\One_S_All-In-One_Kit\data>
This is the error message when i tried step 8, but when i checked the screen it shows relocked now , seems like it worked okay.
i tried this file
http://forum.xda-developers.com/showthread.php?t=1941402
Everytime i runs this RUU application file , after passing thru all steps it says ROM utility stopped working, Seems like i am almost done but just stuck at last point.
Hello NQNH, i tried it one more time and finally passed thru that screen. it started ROM update utility but got back with this error msg
Error (131) customer ID error
The ROM update utility cannot update your android phone
please get the correct ROM update utility and try again
I am using RUU : 1.0.6.2012
please let me know if i can use any other utility
AW: [Q] Trying to get HTC one S on stock rom? Please help ?
What do you get when you type in
fastboot getvar cid
?
Try this RUU
http://www.androidfiles.org/ruu/sec...02.31_10.09a.50.04L_release_275655_signed.exe
Sent from my HTC One S using xda premium
I tried RUU which you suggested , Thanks NQNH but sorry this time it came back with error (130) , model ID error.
fastboot getvar cid : BM___001
AW: [Q] Trying to get HTC one S on stock rom? Please help ?
Seems that you have a branded phone. (Bell Mobile Canada?)
This ruu should run fine:
http://www.androidfiles.org/ruu/sec...02.04_10.08g.50.04L_release_280275_signed.exe
Sent from my HTC One S using xda premium
Thanks Thanks Thanks Thanks a lotttttttttt, I don't know if pressing thanks button is good enough to appreciate your help. I learnt a lot from this session. If you don't mind , just for curiosity can i ask you few more questions,
Tampered (Does it mean somebody tried to install custom rom on it or something else ? )
Unlocked
VLE PVT ship s-on RL ( does S-on means this phone is unlocked or some thing else ? )
HBOOT-1.08.0000 ( is it same like version number in iphone , is it baseband version number, where i can find this number in phone settings ? )
Radi-0.16.31501S.06_3
open DSP-v23.1.0.32.0323 ( don't know what it means , please explain )
eMMC boot ( don't know what it means , please explain )
Mar 21, 2012, 16:01:09 ( is it manufacturing date or date when it was tempered )
Thanks again for your help ..
bindudhindsa said:
Thanks Thanks Thanks Thanks a lotttttttttt, I don't know if pressing thanks button is good enough to appreciate your help. I learnt a lot from this session. If you don't mind , just for curiosity can i ask you few more questions,
Tampered (Does it mean somebody tried to install custom rom on it or something else ? )
Unlocked
VLE PVT ship s-on RL ( does S-on means this phone is unlocked or some thing else ? )
HBOOT-1.08.0000 ( is it same like version number in iphone , is it baseband version number, where i can find this number in phone settings ? )
Radi-0.16.31501S.06_3
open DSP-v23.1.0.32.0323 ( don't know what it means , please explain )
eMMC boot ( don't know what it means , please explain )
Mar 21, 2012, 16:01:09 ( is it manufacturing date or date when it was tempered )
Thanks again for your help ..
Click to expand...
Click to collapse
glad to hear that I helped you.
Tampered means that someone already changed something on the phone (unlocked/relocked/custom recovery)
A comparison should be.. if you bought a new pc and if you open the case you have to break the seal. The "Tampered" say that you had break this seal on the phone (e.g. by unlocking the bootloader)
S-ON means that the security flags are on. Its a system protection so nobody can manipulate system data.
S-ON + locked bootloader -> you can do nothing, no root, no custom things
S-ON + unlocked bootloader -> you can flash custom recovery, root, custom rom (you can see an unlocked bootloader as a compromise between S-ON and S-OFF
S-OFF -> you can do everything what you want, change bootloaderGUI, bootanimations, splashscreens.
Unlocked means that you bootloader is unlocked. If its locked you cant install custom recovery, root and custom firmware. It has to be locked when you install a RUU.
You cant find your HBOOT version in your phone settings because its the version of the bootloader.
the bootloader is independed from the rom you are on. Its like the BIOS from your PC and your ROM is Win7 where you either cant find the bios version.
Radio is the module which is responsible for mobile data etc.
no/wrong/corrupt radio = no network/no signal
openDSP .. i don't know
eMMC boot, I guess that this is the partition where the bootloader is located.. but I'm not sure.
Mar 21, 2012, 16:01:09 is the date when .. difficult to explain .. when the development of the RUU was finished?
if I wrote something wrong please correct me.
Thanks a lot for this very helpful information. Appreciate your help. Kind of person like you are the reason these forums are running successfully and helping novice people like me. Thanks again.
AW: [Q] Trying to get HTC one S on stock rom? Please help ?
Thanks for your words
Sent from my HTC One S using xda premium
Hello.
I'm having same problem with getting back on stock firmware...
After trying to flash into CM10, i got stock in CM boot logo.
So trying to get back to original using RUU.
But it just looks like I can not get right one...
I did everything like in posts above, and when I enter "fastboot getvar cid" I got "HTC_Y13"
Any idea which RUU is correct for that?
I'm still trying, so maybe it will be fools luck... Or maybe someone can put me on point?
auronn said:
Hello.
I'm having same problem with getting back on stock firmware...
After trying to flash into CM10, i got stock in CM boot logo.
So trying to get back to original using RUU.
But it just looks like I can not get right one...
I did everything like in posts above, and when I enter "fastboot getvar cid" I got "HTC_Y13"
Any idea which RUU is correct for that?
I'm still trying, so maybe it will be fools luck... Or maybe someone can put me on point?
Click to expand...
Click to collapse
your cid is a unbranded eu cid.
try any unbranded eu ruu (3.16 or earlier)
Hello everyone,
So, 2 days in front of PC, reading forums and trying. No luck... So try to post it here.
I want to flash to CM10.
Bootloader is unlocked.
Recovery is installed (TWRP S4)
Root is done.
Security S-ON.
When I try to install CM10, everything went fine, but when It have to reboot it just stuck in CM booting logo loop...
And since you can't remove memory card on HTC One S, I think I have no other option how to reinstall stock firmware. And my problems starts...
I relocked bootloader.
Download already like five different RUU's...
The problem is, I can not locate my version, it's blank...
(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: HT23NW410019
(bootloader) imei: 359901040772549
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4124mV
(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
all: Done!
So everytime I start RUU, in the screen Current information about your Android phone" "Image version" is blank and the one with "Verify that you want to update the ROM version" "From Image Version" is blank...
When I push "Next" it goes "Checking", then "Rebooting Bootloader", "Erasing User Data" and "Sending".
When it comes to "Updating Signature" I'm getting error code...
Phone is bought in Norway, and by checking cid: HTC_Y13, I can see that it's HTC-Nor. So which one of RUU's I have to use?
I also tried to flash zip RUU, using One_S_All-In-One_Kit_v3.5 with same no luck...
Really don't know what to do... Any help would be appreciated...
Thank you in advance!
real187 said:
your cid is a unbranded eu cid.
try any unbranded eu ruu (3.16 or earlier)
Click to expand...
Click to collapse
Thank you, I'm downloading and will try this now:
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
Already tried those:
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe
RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.110_Radio_16.12.20.02U_16.05.20.16_M2_release_263510_signed.exe
RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.109_Radio_16.12.20.02U_16.05.20.16_M2_release_263131_signed.exe
RUU_VILLEPLUS_U_JB_45_HTC_Generic_1.14.999.50_Radio_1.10r.50.05.19_10.22a.50.08L_release_294323_signed.exe
And also:
OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.zip
using One_S_All-In-One_Kit_v3.5 with no luck...
Does any body can tell me the difference between Ville, VilleC2 and VillePlus?
real187 said:
your cid is a unbranded eu cid.
try any unbranded eu ruu (3.16 or earlier)
Click to expand...
Click to collapse
Thank you a lot!!!
This one worked:
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1. 11.50.05.28_10.27.50.08L_release_301814_signed_2_4 .exe
auronn said:
Hello everyone,
So, 2 days in front of PC, reading forums and trying. No luck... So try to post it here.
I want to flash to CM10.
Bootloader is unlocked.
Recovery is installed (TWRP S4)
Root is done.
Security S-ON.
When I try to install CM10, everything went fine, but when It have to reboot it just stuck in CM booting logo loop...
And since you can't remove memory card on HTC One S, I think I have no other option how to reinstall stock firmware. And my problems starts...
I relocked bootloader.
Download already like five different RUU's...
The problem is, I can not locate my version, it's blank...
(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: HT23.......
(bootloader) imei: 3599...............
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4124mV
(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
all: Done!
So everytime I start RUU, in the screen Current information about your Android phone" "Image version" is blank and the one with "Verify that you want to update the ROM version" "From Image Version" is blank...
When I push "Next" it goes "Checking", then "Rebooting Bootloader", "Erasing User Data" and "Sending".
When it comes to "Updating Signature" I'm getting error code...
Phone is bought in Norway, and by checking cid: HTC_Y13, I can see that it's HTC-Nor. So which one of RUU's I have to use?
I also tried to flash zip RUU, using One_S_All-In-One_Kit_v3.5 with same no luck...
Really don't know what to do... Any help would be appreciated...
Thank you in advance!
Thank you, I'm downloading and will try this now:
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
Already tried those:
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe
RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.110_Radio_16.12.20.02U_16.05.20.16_M2_release_263510_signed.exe
RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.109_Radio_16.12.20.02U_16.05.20.16_M2_release_263131_signed.exe
RUU_VILLEPLUS_U_JB_45_HTC_Generic_1.14.999.50_Radio_1.10r.50.05.19_10.22a.50.08L_release_294323_signed.exe
And also:
OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.zip
using One_S_All-In-One_Kit_v3.5 with no luck...
Does any body can tell me the difference between Ville, VilleC2 and VillePlus?
Click to expand...
Click to collapse
Firstly, I would recommend removing part of your IMEI and Serial Numbers from your post, it could be used in bad ways by other people.
Ville is the HTC One S with a Snapdragon S4 chipset, clocked at 1.5GHz (dual core) otherwise known as z520e. (You have this phone)
VilleC2 is what became of the HTC One S when HTC ran out of Snapdragon S4 chipsets in many parts of the world due to a shortage. It has a Snapdragon S3, clocked at 1.7GHz (dual core) otherwise known as z560e.
VillePlus is a Special Edition version of the HTC One S, only available in Taiwan. It has the same processor as the Ville, except comes in a white body instead of the normal grey or black options and has 64GBs of internal storage. The other two have 16GBs internal storage. This phone is quite rare.
You should try RUUs only that say ville, and not VillePlus or VilleC2. These won't work and may even irreversibly damage your phone.
OTAs only work when you already have a previous firmware version. Let's say you were on ICS, a Jelly Bean FOTA is released (firmware over the air) and installs ("flashes") on top of your existing ICS installation, keeping your apps and data.
RUUs wipe all data and wipe everything on the phone when installing through a USB connection.
Could you specify what error code you get on the RUUs?
----
The reason why CM10 didn't boot is because you didn't flash the boot.img.
You need to extract the boot.img from the CM10 zip and put that into your "working folder" (the folder with adb and fastboot files in it)
Open up a command prompt / terminal in that folder and type
fastboot flash boot boot.img
when you are in FASTBOOT USB mode in the bootloader.
Go to Fastboot. Plug in your USB with the phone. Now, ctrl and r --> type cmd --> cd to C:/where your adb is --> fastboot read cid
Then type the 8 digit string that you get. It would help us determine your network provider.

[Q] HTC One S having issue with CM10.1

Hi all!
Im in a big pickle here and I cant get myself out at the moment.
First hand.. The info
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.13.0000
(bootloader) version-baseband: 0.17.31501S.10_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3917mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d92cc658
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.093s
Now i've been running cyanogenmod 10 stable since I started rooting etc...
And it's been amazing, but now since there has been a release candidate for 10.1, I was looking into updating it.
I ran into an issue where my boot-loader was not accepted , therefor i would run into an error on Clockwork mod stopping me from flashing 10.1
The bad thing was that I erased my previous installation without backing up the stock and CM10.
So now i'm left with no system. Though I can get into Fastboot and ADB via recovery.I
For some reason if I try to flash CM10 (The rom and the boot file) the cyanogenmod logo will continue spinning.
I tried to fiddle around with my RUU afterwards because I currently have S-On. But i later learned that i need superCID.
^(Which i learned that you need your phone on to alter it to the 8 "1"s) Which i cant do because i have no system.
I might have already altered some files guessing that my boot-loader is named "dirty-d92cc658" and im afraid that I messed up something internally.
So anyways. Im here with my Ville S4 plugged in on fastboot not knowing what to do.
Any Help would be amazing , thank you
Did you try a RUU for Rogers? Not sure if there is one but try to find a RUU that matches your cid
c19932 said:
Did you try a RUU for Rogers? Not sure if there is one but try to find a RUU that matches your cid
Click to expand...
Click to collapse
Do I need to have superCID to flash RUU's ?
Mozziliac said:
Do I need to have superCID to flash RUU's ?
Click to expand...
Click to collapse
If you have a RUU for your specific phone, no, you just need to lock the bootloader.
Have USB debugging turned on (unless running ruu when your phone is in fastboot usb mode)
If you can't find one for Rogers, then yes you have to be super cid to run another RUU.exe (after that change your cid back so an OTA update doesn't brick your phone)
If your phone is on Jellybean, you need to run a JB ruu, if it's Ice Cream Sandwich it won't run. Unless you are supercid I guess.
Khan.orak has a guide for OTA zips to return to stock that you might want.
http://forum.xda-developers.com/showthread.php?p=44365370
Ville / VilleC2 RUU, OTA and Stock Nandroid Collection
http://forum.xda-developers.com/showthread.php?t=2200930
tivofool said:
If you have a RUU for your specific phone, no, you just need to lock the bootloader.
Have USB debugging turned on (unless running ruu when your phone is in fastboot usb mode)
If you can't find one for Rogers, then yes you have to be super cid to run another RUU.exe (after that change your cid back so an OTA update doesn't brick your phone)
If your phone is on Jellybean, you need to run a JB ruu, if it's Ice Cream Sandwich it won't run. Unless you are supercid I guess.
Khan.orak has a guide for OTA zips to return to stock that you might want.
http://forum.xda-developers.com/showthread.php?p=44365370
Ville / VilleC2 RUU, OTA and Stock Nandroid Collection
http://forum.xda-developers.com/showthread.php?t=2200930
Click to expand...
Click to collapse
How can I superCID my phone if I cant boot into the rom?
I've never superCid, can't help you there.
Good news is you can get into bootloader still.
You could fastboot flash a boot.img and flash a rom in recovery.
Just need to mount usb storage in recovery to put the rom.zip on your phone.
Edit: reread that you tried that but rom didn't boot. Hopefully you waited 5-10 min for first load.
try wipedata/factory reset from CWM like 3 times then flashing?
Good luck to ya.
Edit 2: kind of wondering if you can run the Rogers RUU with that low of a bootloader (version-bootloader: 1.13.0000)
Maybe someone can chime in, because that would be nice not having to SuperCid.
Alright so I seemed to get it running on CM 10 by switching recoveries and flashing it's boot.
Then I was able to superCID the phone, which then lead my into S-off'ing it.
Then I was able to update the hboot firmware to 2.15
Cleared the cache and installed the new kernel and flashed cyanogenmod 10.1 rc
Everything went well after that. I did run into a laggy issue, which I then fixed by switching the CPU governor to ondemand instead of interactive.
Thanks for the post guys

SOLVED Boot Loop and bricked

Hey guys already tried everything and everything is still same so what's my problem here we go. 5 Hours ago or less downloaded stock rom and installed with recovery mods everything was great until the phone restarting after android boot logo appears after 1 min device starting to boot loopping . Also i cant handle recovery or factory reset. While installing the rom something comes around " want to install supersu?" and i said no , and why answered no , because thought already this rom has superuser mod . so why i have this problem i know about rooting and i cant open anything to install superuser also with adb i cant handle the device some commands working but others not. Please help me searched almost all the words but still i cant fix that .
Thanks.
Edit: Also when trying to push ROM to sdcard getting " error: device is not found" downloaded all the sdk things and drivers still cannot connect to cmd prompt.
Edit2 : So still trying to do something i think the problem is as i said rooting. The main question is how i can root my device without recovery mode because i cant handle it also i cant push anything with adb , and its so annoying i cant handle anything please help me :/
Korvacs said:
Hey guys already tried everything and everything is still same so what's my problem here we go. 5 Hours ago or less downloaded stock rom and installed with recovery mods everything was great until the phone restarting after android boot logo appears after 1 min device starting to boot loopping . Also i cant handle recovery or factory reset. While installing the rom something comes around " want to install supersu?" and i said no , and why answered no , because thought already this rom has superuser mod . so why i have this problem i know about rooting and i cant open anything to install superuser also with adb i cant handle the device some commands working but others not. Please help me searched almost all the words but still i cant fix that .
Thanks.
Edit: Also when trying to push ROM to sdcard getting " error: device is not found" downloaded all the sdk things and drivers still cannot connect to cmd prompt.
Click to expand...
Click to collapse
Is your one mini international or at&t?also, can you go to your boot loader? just hold down the power button until ur phone is turn off and hold volume down and power. if ur model is the at&t one, you can take the at&t ruu. if not idk what u can do.
abzboi said:
Is your one mini international or at&t?also, can you go to your boot loader? just hold down the power button until ur phone is turn off and hold volume down and power. if ur model is the at&t one, you can take the at&t ruu. if not idk what u can do.
Click to expand...
Click to collapse
Nope its international i bought it from Turkey i think its international also tried HBOOT recovery thins as i said recovery mode is doesnt working anymore . Entering recovery text appear then black screen coming and then device continue loopping forever.
Still waiting for any help guys please.
Also device information here maybe it helps to make something.
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.22.40e.00.07
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3ADWA03301
(bootloader) imei: 35586605630****
(bootloader) meid:
(bootloader) product: m4_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PO5820000
(bootloader) cidnum: HTC__M27
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-871d213f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Korvacs said:
Still waiting for any help guys please.
Also device information here maybe it helps to make something.
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.22.40e.00.07
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3ADWA03301
(bootloader) imei: 35586605630****
(bootloader) meid:
(bootloader) product: m4_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PO5820000
(bootloader) cidnum: HTC__M27
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-871d213f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
If your boot loader is unlocked, then flash a recovery. Flash the twrp 2.6 one not that newest one. And I hope it'll work. Good luck
abzboi said:
If your boot loader is unlocked, then flash a recovery. Flash the twrp 2.6 one not that newest one. And I hope it'll work. Good luck
Click to expand...
Click to collapse
Wont work flashed recovery again and still same thing happened boot loopping
Korvacs said:
Wont work flashed recovery again and still same thing happened boot loopping
Click to expand...
Click to collapse
Can you go to recovery after flash the twrp 2.6.0.0?
Edit: Hey I think I know what you did wrong. Did you flash the boot.img from the zip in the boot loader after flashing the rom? If not go ahead and try. You won't be able to boot through htc logo until you flash the boot.img.
abzboi said:
Can you go to recovery after flash the twrp 2.6.0.0?
Edit: Hey I think I know what you did wrong. Did you flash the boot.img from the zip in the boot loader after flashing the rom? If not go ahead and try. You won't be able to boot through htc logo until you flash the boot.img.
Click to expand...
Click to collapse
Yup first flashed recovery then flashed boot.img but still same thing stuck at htc boot screen and recovery wont working.
Here we go Flashed this http://forum.xda-developers.com/showthread.php?t=2594253 recovery mode and worked now what to i dont know but still trying to fix it.
Korvacs said:
Here we go Flashed this http://forum.xda-developers.com/showthread.php?t=2594253 recovery mode and worked now what to i dont know but still trying to fix it.
Click to expand...
Click to collapse
reflash the rom?
abzboi said:
reflash the rom?
Click to expand...
Click to collapse
Yeah trying to move rom file to sdcard but its more harder for me , i think . Also in ADB Cmd promt while in sideload recovery mode my device was there so its good growth for me So after installing rom.zip getting weird error .
Korvacs said:
Yeah trying to move rom file to sdcard but its more harder for me , i think . Also in ADB Cmd promt while in sideload recovery mode my device was there so its good growth for me So after installing rom.zip getting weird error .
Click to expand...
Click to collapse
Try to install a different rom. The newest 4.3 rom that trigger made
abzboi said:
Try to install a different rom. The newest 4.3 rom that trigger made
Click to expand...
Click to collapse
You mean magio rom ? i am trying to install stocked rom i think its better than modded rom . Also i cant move rom file to sdcard the problem is here i think . I can give teamviewer id pw if u want to help me please.
Korvacs said:
You mean magio rom ? i am trying to install stocked rom i think its better than modded rom . Also i cant move rom file to sdcard the problem is here i think . I can give teamviewer id pw if u want to help me please.
Click to expand...
Click to collapse
Is adb not working for you?
Solved
Anyway fixed everything and flashed stocked rom from trigger. This device make a so much headcache nevermind thanks for helping " abzoi"
Korvacs said:
Anyway fixed everything and flashed stocked rom from trigger. This device make a so much headcache nevermind thanks for helping " abzoi"
Click to expand...
Click to collapse
No problem, glad to hear that your device is working again I hope you'll enjoy you one mini
abzboi said:
No problem, glad to hear that your device is working again I hope you'll enjoy you one mini
Click to expand...
Click to collapse
Yup finally i fixed it but it took almost 24 hours to work it Flashed 4.3 rooted stock rom and working well :good:
Korvacs said:
Yup finally i fixed it but it took almost 24 hours to work it Flashed 4.3 rooted stock rom and working well :good:
Click to expand...
Click to collapse
I had a problem too yesterday. I finally know how to use adb now.

[Q] Rooting mistake

Hey guys.
I wanted to root my HTC One S, and I read that the program SuperOneClick was the fastest way of doing it, so I went ahead and connected the HTC to my PC with the USB cable and clicked "root". After like 15 minutes however the program didn't do anything, it just froze and I had to close it. Root Checker Basic said something similiar to no valid root or something. Tried to click "unroot" now so I could start again with a different method, froze again, closed SuperOneClick again. What am I supposed to do now? Is rooting it again safe as I now probably have some half / corrupted root? And can someone link me to the best method? Thanks in advance.
CrackedHippo said:
Hey guys.
I wanted to root my HTC One S, and I read that the program SuperOneClick was the fastest way of doing it, so I went ahead and connected the HTC to my PC with the USB cable and clicked "root". After like 15 minutes however the program didn't do anything, it just froze and I had to close it. Root Checker Basic said something similiar to no valid root or something. Tried to click "unroot" now so I could start again with a different method, froze again, closed SuperOneClick again. What am I supposed to do now? Is rooting it again safe as I now probably have some half / corrupted root? And can someone link me to the best method? Thanks in advance.
Click to expand...
Click to collapse
One-click-roots are not suggested...
Did you unlock the bootloader?
Just unlocked the bootloader and flashed cwm, my own fault for using superoneclick. Thanks anyway ;p
Sorry for the double post. I may need some help as I probably bricked(?) my One S.
Didn't do anything root-related for a long time so I think I made a beginner's mistake.
What I did was unlock (htcDEV), and flash CWM recovery.
I tried installing liquid kitkat custom rom, but now it won't boot, not even in recovery.
Help?
EDIT: It's stuck in a boot loop :/
CrackedHippo said:
Sorry for the double post. I may need some help as I probably bricked(?) my One S.
Didn't do anything root-related for a long time so I think I made a beginner's mistake.
What I did was unlock (htcDEV), and flash CWM recovery.
I tried installing liquid kitkat custom rom, but now it won't boot, not even in recovery.
Help?
EDIT: It's stuck in a boot loop :/
Click to expand...
Click to collapse
Press Power button for 10secs+ to power off
Can you enter fastboot? Is your phone S4 ville or s3 villeC2?
LS.xD said:
Press Power button for 10secs+ to power off
Can you enter fastboot? Is your phone S4 ville or s3 villeC2?
Click to expand...
Click to collapse
I finally managed to enter recovery / fastboot.
Sorry for the foolish comment but I actually have no idea if it's S4 or S3, how do I find out?
Also what should I do right now? Flash stock rom on it or..?
CrackedHippo said:
I finally managed to enter recovery / fastboot.
Sorry for the foolish comment but I actually have no idea if it's S4 or S3, how do I find out?
Also what should I do right now? Flash stock rom on it or..?
Click to expand...
Click to collapse
FIRST you need to know which phone / firmware you got.
Enter fastboot, connect to pc, open CMD and type "fastboot getvar all"
Copy the log and post it here please. Delete IMEI/serial before you post the log. Then i can exactly tell you what you need to install
LS.xD said:
FIRST you need to know which phone / firmware you got.
Enter fastboot, connect to pc, open CMD and type "fastboot getvar all"
Copy the log and post it here please. Delete IMEI/serial before you post the log. Then i can exactly tell you what you need to install
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.15.50.05.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***
(bootloader) imei: ***
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 3810mV
(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
Here you go, thanks in advance!
CrackedHippo said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.15.50.05.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***
(bootloader) imei: ***
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 3810mV
(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
Here you go, thanks in advance!
Click to expand...
Click to collapse
HTC One S - S4 ville - generic dutch version
You will just need to flash the kernel contained in the rom (boot.img) via fastboot (S-ON means u need to flash kernel manually) to fix your installation
Generally I'd suggest
Flash this recovery via fastboot --> TWRP 2.7.0.8
(its compatible to the lastest CM11 versions 05/01/2014 and newer
And may be try PAC rom (I just love it)
LS.xD said:
HTC One S - S4 ville - generic dutch version
You will just need to flash the kernel contained in the rom (boot.img) via fastboot (S-ON means u need to flash kernel manually) to fix your installation
Generally I'd suggest
Flash this recovery via fastboot --> TWRP 2.7.0.8
(its compatible to the lastest CM11 versions 05/01/2014 and newer
And may be try PAC rom (I just love it)
Click to expand...
Click to collapse
I indeed just flashed the boot.img seperately which was in the rom, and now it works. It's a huge relief to see my phone work again, thanks a lot!!
One more thing so I avoid messing up in the future; When I decide to install another rom, do I always do a factory reset / clear cache, then flash the rom and flash the kernel via fasboot?
CrackedHippo said:
I indeed just flashed the boot.img seperately which was in the rom, and now it works. It's a huge relief to see my phone work again, thanks a lot!!
One more thing so I avoid messing up in the future; When I decide to install another rom, do I always do a factory reset / clear cache, then flash the rom and flash the kernel via fasboot?
Click to expand...
Click to collapse
FULL wipe --> format system, data, cache, dalvik --> flash rom --> immediately go to fastboot and flash the kernel --> reboot and done
Just try to get S-OFF, then the kernel get installed with the rom via recovery
LS.xD said:
FULL wipe --> format system, data, cache, dalvik --> flash rom --> immediately go to fastboot and flash the kernel --> reboot and done
Just try to get S-OFF, then the kernel get installed with the rom via recovery
Click to expand...
Click to collapse
Looks like I was cheering too early. Roughly 1 minute after launching my phone, .comSystemGUI or something along those lines stopped working, and whenever I pressed "ok" the message would instantly return. I can't connect my phone to my PC to put another ROM on it since the message won't disappear. Also I tried re-flashing the same ROM, but now it says can't mount storage/sdcard0.
Really frustrating!
http://forum.xda-developers.com/showthread.php?t=2206434
This topic guided me into getting the sdcard mountable again, but in the process I lost the rom .zip file.
And my phone won't boot anymore, it doesn't get past the HTC logo, so I can't put a new rom on it and flash it.
What is there left for me to do? Stock rom? How do I find the stock rom?
Thanks in advance.
I figured it out, thanks for your guidance LS.xD!
Basically what I did was mount the SD storage in CWM and transfer Pac-man rom onto the storage, then flash the .zip, flash Gapps and finally in bootloader fastboot the boot.img (because I'm S-ON). Maybe this will help anyone.
EDIT: Someone may wanna be careful with using TWRP, it corrupted my SD storage for a while.
CrackedHippo said:
I figured it out, thanks for your guidance LS.xD!
Basically what I did was mount the SD storage in CWM and transfer Pac-man rom onto the storage, then flash the .zip, flash Gapps and finally in bootloader fastboot the boot.img (because I'm S-ON). Maybe this will help anyone.
EDIT: Someone may wanna be careful with using TWRP, it corrupted my SD storage for a while.
Click to expand...
Click to collapse
SD card bug can also be caused by CWM or flashing a rom (Viper really loves to brick SD). I never had any issues with TWRP. The only SD card bug I had in over a year flashing roms to my One S was caused by flashing CWM
Sent from my beloved HTC One S using (most time buggy) Tapatalk

Any Rom Not Working On My Phone :(

i tried to install many roms on my phone but no one worked on it
roms installed but phone goes off after boot logo any solution
version-bootloader: 3.01.0000
version-baseband: 16.11.20.24_M
version-cpld: None
version-microp: None
version-main: 3.19.980.101
version-misc: PVT SHIP S-ON
serialno: HT26MW407496
imei: 352762051624608
meid:
product: villec2
platform: HBOOT-8260
modelid: PJ4020000
cidnum: OPTUS001
battery-status: good
battery-voltage: 3770mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
You have VilleC2, that means roms for your phone are here.
And you're S-ON, so each time you flash a new rom you have to flash the boot.img from the zip manually to make your phone bootable. Did you do that ?
benJX said:
You have VilleC2, that means roms for your phone are here.
And you're S-ON, so each time you flash a new rom you have to flash the boot.img from the zip manually to make your phone bootable. Did you do that ?
Click to expand...
Click to collapse
yes bro i did it bt not worked m very upset man coz my phone is off from last one month
Can you boot to bootloader ? Did you try a ruu ?
benJX said:
Can you boot to bootloader ? Did you try a ruu ?
Click to expand...
Click to collapse
yes i boot to bootloader and can i know where can i get ruu that is compatible for my phone
gurjivan said:
yes i boot to bootloader and can i know where can i get ruu that is compatible for my phone
Click to expand...
Click to collapse
Not sure it will work with your CID but run this one. Plug your phone in fastboot mode before running the RUU.
If it works that's great but if the RUU is not compatible with your CID it will not flash anything to your device so that's not risquy at all to give it a try.
In all cases it will not be worse than now.
benJX said:
Not sure it will work with your CID but run this one. Plug your phone in fastboot mode before running the RUU.
If it works that's great but if the RUU is not compatible with your CID it will not flash anything to your device so that's not risquy at all to give it a try.
In all cases it will not be worse than now.
Click to expand...
Click to collapse
not worked at all i installed viperS/c2 it installed succesfully and i booted boot file also in fastboot mode from zip but my phone stucks on htc this build only for any solution?

Categories

Resources