First off, I know I just signed up. I've been creeping for the past month or so.
So here is the situation:
Summary: I have a hardware problem on a rooted/unlocked htc evo design and have to return it to stock settings to return but have lost usb connection and cannot re-establish.
Hboot:
Unlocked
S-On
1.26.0000
Software Info:
version: 2.3.4
htc sense: 3.0
software number: DesignerEvo-0.5
Longer Version:
I bump into a tech-head tweak everything buddy of mine and he says i just have to "flash the new ics" to my phone.
15 hours of banging the head against the wall later i realize im trying to unlock/root/su/flash as though i have the evo 4g not the evo DESIGN 4g which i actually have. (and which i shortly discovered has nothing customized for it) After that I was off and away-ish...
so here is what i have done (don't mock me for saying it wrong):
- Unlocked the phone via htc dev site (it won't let me post links yet)
- Flashed/Installed Custom Recovery Clockwork mod 5.0.2.7
- Flashed su-2.3.6.3
- Flashed Designer Evo 0.5 found at sdx-developers (wont let me link)
- then for kicks flashed a a vaelek rom that said it was compatible-ish for the evo design from http://forum.xda-developers.com/showthread.php?t=1399351 it didnt see usb and other issues, so...
- then came back to Designer Evo
- installed setcpu to try to improve battery life...
Everything was fine for a couple of weeks (other than no ics and crappy battery life!)...
All of a sudden at random the phone powers off with battery reading charged. It will reboot, and within minutes power off again.
It does this in stock rom and custom.
If i keep it on charge it stays on.
If i remove it after charging, it holds power for a little while, but still powers off.
I thought conflict may have been between setcpu and a power savings app i had running and had forgotten to remove. removed, seemed to be okay then same.
I decided to come back on here figure out how to flash back to factory and unroot, and plugged it into computer (windows 7) via usb. "unknown device". reinstalled drivers. same problem. opened as ubuntu 11.x, still nothing. installed drivers nothing.
I dloaded a stock PH44img.zip w/ phone and put it on root and it would load at hboot, but do nothing after. may require s-off?
This is weird, I did a factory reset from recovery and on reboot it defaulted to the vaelek custom rom, so i went back to my oldest backup.
so... as i said, I think I have a hardware problem on a rooted/unlocked htc evo design and have to return it to stock settings to return but have lost usb connection and cannot re-establish.
Hang in there Vince...somebody is bound to point you in the right direction
I guessing people were off partying this weekend and have yet to respond?
ok this is crazy.... My design 4g is nowing doing the same thing.... Google brought me to this thread... anyone know anything?
Have you tried ruu'ing back to stock or flashing a different rom thru recovery
Sent from my PG06100 using xda app-developers app
shrekdaklown said:
Have you tried ruu'ing back to stock or flashing a different rom thru recovery
Sent from my PG06100 using xda app-developers app
Click to expand...
Click to collapse
Tried several roms . No luck..
tried to ruu via boot loader... It won't take. I may need to relock the boot loader.
Related
So I got my s-off but I don't know which Rom to use.....what are some of the top Rom recommended?
Sent from my HTC Sensation 4G using XDA App
I've tried many of the roms, but I still prefer the stock rom. It runs perfectly fine... you just need to remove the bloatware... It's also all personal preferences, so start flashing and see how you like each one.
I am also using the stock ROM, but with bloatware and sense frozen via Titanium Backup. I am also using ADW EX launcher (a must since I froze Sense). My phone is super snappy, and without the risk of it being a brick.
If you are new to all this, I would wait before flashing a ROM. They are still buggy and nothing for a new guy to be trying to troubleshoot when he needs to be on his way to work in the morning. ;-)
First things first, you need to figure out which CWM version your phone needs to avoid a NASTY problem with dead batteries and a phone that wont boot.
There are two versions out, one is a "fixed" version from Alpharev (the .4 version). The other is the newest .5 that is available from ROm Mananger (marketplace app).
Chances are, your phone will not charge right with one of them. While you have a somewhat charged battery, install the .4 version and then turn off your phone (no fastboot, fully off). Try to charge for an hour. Boot up and then see if your phone charged. If so, and you were able to boot up normally, then you are done. If not, install CWM version .5.
Matt
Well I'm rooted already.....and I'm using .4 and don't have any battery charging problems.......I've owned a mytouch 4g before and rooted that also but I didn't like the sense ui on that phone. So basically use stock with no bloatware then......that sounds good to me. This sense ui doesn't bother me at all.....
Sent from my HTC Sensation 4G using XDA App
Just installed new rom on phone.
Keeps rebooting every couple of minutes. Now I am not sure if it happened before I installed rom or not as I just went straight ahead and installed it as I have just received a replacement handset from a broken screen.
Any help?
Sense rom? Aosp rom? Rom name? Root? No root? More info man...
*Swaypovano sa Desire S BRE*
Saga3D v3.0 (Desire S official Sense 3.0) - [2.3.5] OTA 2.10.401.5
That rom. Installed the new hboot and orig stock kernal
Assume you have rebooted into recovery and wiped data, cache and dalvik cache, then tried to reboot?
Yes, I have done that a couple of times. I left it on connected with cable overnight and it doesnt seem to have rebooted. Seems to point to a battery problem??
It does boot properly. But after a minute it just restarts.
Edit. A bit more testing and it doesnt reboot when using a game or app. As soon as it closes to main screen it seems to just reboot as the screen goes into standby.
Edit 2. I have changed setting to stop screen turning off and its not done a reboot for the whole 10 minutes.
Does anyone think its a warranty claim? Or any more things to try?
Warranty claim seems a bit drastic, I'd try installing the rom again, or try a different rom, Endymion is sense 3.5 and stable... I was toying with it today, or pre rooted stock or even cm7 which at least you know is also rock solid
Sent from my HTC Desire S using xda premium
Just tried cm7 and it does the exact same.
Edit.... tried 4 different roms now. Going to go to stock with s-on and test. Then back to the shop again
Edit 2. Just use RUU on it and it is the same. Looks like I need to return it yet again.
Any more tips before I take it back in?
I had the same problem after 2.3.5 update. Went back to old version and it's fine now.
Assuming that you are not OC or UV then continue, else adjust to stock settings and re-try.
I recall a couple of others having a similar problem that was caused by either
a) loose battery connection, resolved by placing a piece of folded paper on top of battery to ensure it sat solidly in the slot.
b) dodgy battery, suggest that you contact HTC support, explain that phone keeps rebooting you suspect battery and request that they post you a new battery - don't post old battery back until you are sure its the battery at fault.
I was running the latest tweaked ROM yesterday when it rebooted itself into a boot loop. Iets stuck at "Samsung"
I attempted to restore using Odin following the instructions in the how to fix your phone thread. Though i've been successful with that in the past, this time it didn't fix the phone. Its still stuck on Samsung, but will randomly display the stock boot ani with sound, or even get to the lock screen, but then immediately go back to displaying Samsung.
Any ideas would be greatly appreciated, and yes, i've followed all instructions correctly with wipes and loading things in Odin, etc.
Thanks!
Hmm... was there anything going on at the time of reboot? Very curious.
Beyond that - assuming all went as it should with ODIN, if you are still having issues then the problem is a bit beyond the rom. It seems a scapegoat but perhaps a hardware error is underlying things...?
Anyhoo - what file (or files) have you tried to ODIN? There are a few to choose from, and they all can be found here (just be sure to only DL and use the charge-specific ones of course). I would try each one and hope at some point something sticks to where the phone is usable again. Sorry for the troubles!
Thanks for your reply! Phone was just sitting on my desk, I was text messaging...it may have been plugged into a non Samsung charger. I doubt its the fault of your ROM tho, as it had been running great since I installed 2.1 a few weeks ago. Its always run hot so that might have just caught up with it.
I'll try all those files this time on fresh downloads, might have been something corrupted.
thanks again!
UPDATE: Successfully loaded ED1 on, and it boots. I can unlock the phone, begin the setup process, but then it reboots. I'm so confused...
Find the most current OTA file and flash it instead of working your way all the way from Froyo to Gingerbread.
Sent from my SCH-I510 using xda premium
I had something similar happen to me just a week ago. I was on stock debloated deodexed and odined to tweeked and it bootlooped, Odin said successful but nothing was happening just Samsung logo. I knew there was no problem with tweeked cause I used the same file b4 and it worked fine. Tried to Odin back to stock ep4 same Samsung logo Odin still said it was successful. So I changed cable and made shure I was not moving phone or cable while it was doing its thing. It worked. Then updated to fp1, cwm superuser then Odin to tweeked. Everything ok. I figured the only problem of my was that the cable was a bit loose when I plugged it in the phone, the connections in the phone I guess were not getting the full contact as they should have. So try making shure you connect/plug in cable all the way and don't touch it while Odin is doing its job. You might also need to flash the stock ep4 file. Sorry could not help more. This worked for me, now on tweeked 2.2 n no problems.
Sent from my SCH-I510 using xda app-developers app
Hey,
I have a telus HTC One S and they just released the Android v 4.1.1 (my current is 4.0.3)
I've rooted my phone and installed CWM. But i would like to undo this to install the new ota update to this version. I assume this means i will have to :
remove super User
lock my boot loader using fast boot
Then using the RUU_Ville_U_TELUS_WWE_1.70.661.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254554_signed.exe
file install the stock recovery and rom?
Is this correct or am i missing something.
hbforce
Thehurst said:
Hey,
I have a telus HTC One S and they just released the Android v 4.1.1 (my current is 4.0.3)
I've rooted my phone and installed CWM. But i would like to undo this to install the new ota update to this version. I assume this means i will have to :
remove super User
lock my boot loader using fast boot
Then using the RUU_Ville_U_TELUS_WWE_1.70.661.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254554_signed.exe
file install the stock recovery and rom?
Is this correct or am i missing something.
Click to expand...
Click to collapse
Right, go for it.
"IF I HELPED YOU HIT THANKS BUTTON"
.
You don't need to re-lock bootloader. Just remove superuser and restore stock recovery, then you are ready for OTA update.
So It worked but I encountered another issue, after the update was done my phone was unable to stay connected to the telus network.
it will connect to 4g with almost full bars for about 2 mins of which i can use data then it will disconnect me entirely, I can't search for the network or automatically configure it.
I took it to telus the sales guy played around with it reset the setting, nothing, then he Gave me a new sim (said it fixed his htc one which he did the same update last week) but it didn't work for me.
Does anyone know why this is happening or how i might fix it. They want me to sent my phone into for repairs but I don't want a loner phone for the 3 weeks it takes them to fix it.
I'm tempted to run the RUU again and sent my phone back to the stock 4.0.3 from 4.1.1 to see if it works and then try upgrading again.
Any advice?
maybe clear cache and possibly check the apn setting.
I tried that, and even factory recoveries with no luck so i returned it to Telus and hopefully it'll be repaired, It says re-locked and the tampered was removed so hopefully i don't get my warranty void'd if it is i'm sure i can down grade to the original os then load a custom rom and it should work
Just got my phone back from HTC
Despite having previously rooted my phone, they repaired it with no questions, and for free. Turns out my phone had a defective mainboard so once i updated the defect affected the phones ability to connect to the wireless network or something. But with the replaced board and with the new software update its working perfectly again.
Hi people,
here is stock kernel extracted from One SV k2_u/k2_ul/k2_plc_cl version but with modded ramdisk.
I put this thread into general section but as soon as sources are out this will be moved into Original Development section and it will be replaced by my new kernel.
Features:
- Unsecured kernel
- init.d support
- Persistent ADB enabled
Instructions:
- Run "fastboot flash boot boot.img" command.
- Reboot & Enjoy!
DOWNLOAD for k2_u
DOWNLOAD for k2_ul
DOWNLOAD for k2_plc_cl
Make a nandroid backup first!
Credits:
- old.splatterhand
- eduardog131 for stock k2_plc_cl kernel
Enjoy!
xpirt
Will this help for a 4.2.2 rom?
GtrCraft said:
Will this help for a 4.2.2 rom?
Click to expand...
Click to collapse
Sorry this should be on One SV general section and I reported but anyone moved yet. @Ghost
It's stock kernel for One SV btw.
xpirt
Hi,
Can you mod k2ul version kernel?
@xpirt
Would you be willing to make a tutorial on here as to how you did this, the requirements needed to accomplish it, and what to check for, as well as the changes which must be made for such a modification? I am asking this so many will learn and as well take the idea and possibly grow from it by coming up with even better ideas in the future. Without the knowledge or know how then this will only keep people in the dark and nobody wins from this. You don't have to make a tutorial, but if you were to do so it would be very much appreciated friend.
Sent from my C525c using XDA Premium 4 mobile app
If someone gives me stock k2_ul kernel I can mod it as well.
@Modding.MyMind I modded it with cygwin kitchen, you can unpack any kernel and edit its ramdisk. The file modded is default.prop.
xpirt
Added k2_ul version! @bataya
xpirt
@xpirt
I know you have the mod, but what about write protection for this kernel for those who are S-On?
Sent from my C525c using Tapatalk
Modding.MyMind said:
@xpirt
I know you have the mod, but what about write protection for this kernel for those who are S-On?
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
I made the module for now.. a stock kernel with write protection disabled will come with my custom kernel too one day, but now I'm busy with something else..
xpirt
xpirt said:
I made the module for now.. a stock kernel with write protection disabled will come with my custom kernel too one day, but now I'm busy with something else..
xpirt
Click to expand...
Click to collapse
No worries man. Handle your priorities .
Sent from my C525c using Tapatalk
Added modded k2_plc_cl kernel, thx to @eduardog131 for stock kernel.
xpirt
Will this let people use rom toolbox to change the notification icons like wifi icon cell signal icon and so forth?
SnakeFist2005 said:
Will this let people use rom toolbox to change the notification icons like wifi icon cell signal icon and so forth?
Click to expand...
Click to collapse
Not this, this is the kernel. To use toolbox a deodexed system + root/busybox should be enough.
xpirt
Experiment went awry!!!! Ended with a nice surprise!!!
So this is a an interesting story. I have tried many ways to finish flashing the OTA's after I have implemented the RUU. None seemed to work. I was missing a key step pull out the firmware.:silly: duh. Im still a very real noob here and learning on my own. And I was on github the other day browsing and searching and there was a put an uncompiled SE supported string for a kernel of our dear phone the PLC. So grabbed and immediatly started browsing reading and learning placing things here and their....I learn hands on, not from stories or guides. Well things quickly went wrong like many of you reading this are thinking and I wound up with a big paper weight hahahaha. No biggie I got 4 different nandroids that I have compiled and the RUU right I am good.
NO SO FAST nandroids wont flash something about error 23 or 24. RUU I ran 4 times deleted re downloaded and ran again nothing. Again I am still not in panic mode I have enough hardware on my computer to makeshift something to get the RUU to download. I dont know how this happened somehow in the midst of my scramble to get my phone back I had put in an old hboot radio and ics boot img. See my phone has never run ics before. So now I was staring at drivers failing cause their is no OS RUU isnt working nandroids wont work. My phone is down and my computer when I take it to work has no internet. I went through my archives and found the data for the binaries and the data for an ics rom but it was bare bones but heck I had no other choice. So I through the old firmware mixed with bits of the newer kernel.
I booted from recovery with adb to oem-78 which I believe is the updater portion of RUU. I ran the the firmware from their I first relocked bootloader before I did this. I did not take the first time/ flush the zip and run it again took like a charm. I then went back to fastboot flashed TWRP 2.6 instead of my normal 2.7 just cause I wanted to booted into recovery no problem. While in recovery I flashed the ICS stock rom like the firmware did not take. No worries ran it again and worked the second time. then wiped cache and dalvic flashed superSU 2.0.2 which was bought from play store and donated for zip thanks btw. and busybox X. booted into bootloader rebooted bootloader like a dozen times and flashed the ICS boot img. twice seems like the theme hear.
K bear with me I know I am long winded. Tried booting into the system after another dozen times rebooting bootloader. finally gave up went back to recovery reflashed ICS rom only once and then did busybox and SU another time for good measure. I did an avance wipe of dalvic and cache this time. booted straight to system and put the phone down came backe 20 min later it was working I played around it was glitch bad but working. I let it be for another 30 min. Came back rebooted a couple times and went to recovery to instantly backup as all mine where now worthless. When I got home I noticed it wouldnt receive wifi signal after playing around I downloaded the latest OTA for the 4.1.2 JB and the 4.5 sense update. Pulled the firmware flashed that after replacing the HBOOT with an old version and then found my other SD card and pulled a bunch of saved stuff off and found a stock JB 4.5 sense rom. flashed like above steps basically to the amount of reboots. lol. I finally got it to boot and within the hour I am running a smooth JB 4.1.2 sense 4+ OS thats what android tuner says my Hboot however says
Unlocked
K2_PLC_CL PVT SHIP S-OFF RL
CID 11111111
HBOOT 1.01.0000< oldest one i've seen lol.
Radio 1.12.00.0208
OpenDSP- v 10.2.0268.0401
eMMC-boot
Feb 8 2013, 16: 29: 40:-1
As u see no line for OS and well no os and no data associated with eMMC just the boot. Everything seems to run way way way smoother now thought even before I started messing around. No lag perfect signal. My call problems gone only thing is my batt percent and my mms but those are pre existing problems I am working on.
My kernel says I am the 3.4 variation. On my phone and in all my apps. Except rom tool box it says I am 3.2
I wrote this hopefully a true dev can take what I did and come up with something amazing that can be used across the board of the ONE SV users.Thanks oh some how my toggle switches all turned orange in bootloader and all my highlited things in the rom turned green dont know how that happened either. :fingers-crossed:
Fant0m3 said:
So this is a an interesting story. I have tried many ways to finish flashing the OTA's after I have implemented the RUU. None seemed to work. I was missing a key step pull out the firmware.:silly: duh. Im still a very real noob here and learning on my own. And I was on github the other day browsing and searching and there was a put an uncompiled SE supported string for a kernel of our dear phone the PLC. So grabbed and immediatly started browsing reading and learning placing things here and their....I learn hands on, not from stories or guides. Well things quickly went wrong like many of you reading this are thinking and I wound up with a big paper weight hahahaha. No biggie I got 4 different nandroids that I have compiled and the RUU right I am good.
NO SO FAST nandroids wont flash something about error 23 or 24. RUU I ran 4 times deleted re downloaded and ran again nothing. Again I am still not in panic mode I have enough hardware on my computer to makeshift something to get the RUU to download. I dont know how this happened somehow in the midst of my scramble to get my phone back I had put in an old hboot radio and ics boot img. See my phone has never run ics before. So now I was staring at drivers failing cause their is no OS RUU isnt working nandroids wont work. My phone is down and my computer when I take it to work has no internet. I went through my archives and found the data for the binaries and the data for an ics rom but it was bare bones but heck I had no other choice. So I through the old firmware mixed with bits of the newer kernel.
I booted from recovery with adb to oem-78 which I believe is the updater portion of RUU. I ran the the firmware from their I first relocked bootloader before I did this. I did not take the first time/ flush the zip and run it again took like a charm. I then went back to fastboot flashed TWRP 2.6 instead of my normal 2.7 just cause I wanted to booted into recovery no problem. While in recovery I flashed the ICS stock rom like the firmware did not take. No worries ran it again and worked the second time. then wiped cache and dalvic flashed superSU 2.0.2 which was bought from play store and donated for zip thanks btw. and busybox X. booted into bootloader rebooted bootloader like a dozen times and flashed the ICS boot img. twice seems like the theme hear.
K bear with me I know I am long winded. Tried booting into the system after another dozen times rebooting bootloader. finally gave up went back to recovery reflashed ICS rom only once and then did busybox and SU another time for good measure. I did an avance wipe of dalvic and cache this time. booted straight to system and put the phone down came backe 20 min later it was working I played around it was glitch bad but working. I let it be for another 30 min. Came back rebooted a couple times and went to recovery to instantly backup as all mine where now worthless. When I got home I noticed it wouldnt receive wifi signal after playing around I downloaded the latest OTA for the 4.1.2 JB and the 4.5 sense update. Pulled the firmware flashed that after replacing the HBOOT with an old version and then found my other SD card and pulled a bunch of saved stuff off and found a stock JB 4.5 sense rom. flashed like above steps basically to the amount of reboots. lol. I finally got it to boot and within the hour I am running a smooth JB 4.1.2 sense 4+ OS thats what android tuner says my Hboot however says
As u see no line for OS and well no os and no data associated with eMMC just the boot. Everything seems to run way way way smoother now thought even before I started messing around. No lag perfect signal. My call problems gone only thing is my batt percent and my mms but those are pre existing problems I am working on.
My kernel says I am the 3.4 variation. On my phone and in all my apps. Except rom tool box it says I am 3.2
I wrote this hopefully a true dev can take what I did and come up with something amazing that can be used across the board of the ONE SV users.Thanks oh some how my toggle switches all turned orange in bootloader and all my highlited things in the rom turned green dont know how that happened either. :fingers-crossed:
Click to expand...
Click to collapse
so are you saying that you flashed this kernel?
what exactly do you want a dev to do? i think, by reading what you said, that what you did was, try to compile a kernel with bits and pieces, and when you flashed it, it didnt work? so you tried to restore a backup that you also 'compiled'(?), which failed as well. you then flashed an older hboot which allowed your update to take.... the downgrade to update has stumped lots, including me. its basically the process of manual updating. these phones are all different because the partitions are in different locations in the device. and certain varients have no sim card slot. the radios are running "different channels" etc...
sorry for continuing off topic..
Thanks for the kernel and all your work