Hey
I just got a huge bootloop while attempting to flash new Venom Room to my HTC One X. http://forum.xda-developers.com/showthread.php?t=1868236
I cannot access the recovery.. After restart (power button+volume down) i can get to bootloader section, but when i try to get into recovery, the phone just restart and stop on the white htc screen.
I already tried to reinstall recovery. Installation was successful, but the problem persists..
Before i had Incert Coins room.
The phone is unlocked, new recovery is installed
Please, help
If you had Insert Coin working on your phone, you have an international (Tegra3) version of the One X. This forum (and the Venom ROM you linked) are for the Snapdragon S3 version. Completely different hardware.
If I'm correct, you flashed a ROM for the wrong phone. Try running the RUU for your phone, but if that doesn't work you may be screwed. Recovery partitions are not the same for the versions. The ROM overwrote the recovery partition of your phone.
You are right.. It WAS the wrong rom.. I have tegra3 processor and this rom comes from american section..
But - is the RUU reinstall only one thing what i can do? I heard its dangerous
Senbration said:
But - is the RUU reinstall only one thing what i can do? I heard its dangerous
Click to expand...
Click to collapse
RUU just returns your phone to the stock condition. Stock ROM and stock recovery. There should be nothing dangerous about it. Just use the right one for your version, carrier, etc. But the CID check should ensure that you don't run the wrong RUU (if RUU is for a different CID, the RUU will not run).
Only thing with RUU, is that it wipes all user data. That may be why you heard its "dangerous". But in the condition you are in, this is not even a consideration anymore.
RUU is not dangerous, and it may be your only hope at this point.
You will need to lock your bootloader before running the RUU.
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Senbration said:
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Click to expand...
Click to collapse
I'm assuming you meant relocked bootloader and now has security warning relocked if this what you meant then you are fine flash the ruu
Sent from my Nocturnalized One XL using Forum Runner
Senbration said:
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Click to expand...
Click to collapse
You mean relocked and not reloaded? If so, you should be good to run the RUU. Redpoint, sorry for highjacking your help session
Sent from my One X using xda premium
ohh, its Relocked.. Im just a bit nervous right now hoping it will unbrick this phone..
Just 3min to complete RUU download.
Do U guys think this stock RUU will rewrite the partitions back?
I've noticed another problem.
Cannot load RUU because the battery level is lower then 30%.
But when i plug the charger the light doesnt flash. It starts to flash when i switch on the phone.
Also cannot switch the phone with the power button. It restart all the time. Only can do that from bootloader command "power down". But when the phone is off the power light doesnt flash..
Does it mean that the battery is not charging at all? Because the light can flash only because the power is low..
The phone shut down completly now.. Does not charge the battery at all.. Power gone off and i cannot even turn on the phone..
Is there any solution how to make it charge?
Ok, the problem is that the wrong ROM i tried to install changed partition and also it seems it destroyed Recovery..
Without recovery the phone cannot charge while being in bootloader mode...
Is there any way to make phone charging when Recovery doesnt work and cannot be flashed?
Please help
Take the phone apart. I mean all the way spart and hardwire a charger to the phone/ battery. Its a pain but you can do it.
Ohh..
I found a treat http://forum.xda-developers.com/showthread.php?t=1658084
There is a way to charge battery by running the script, which makes phone reinstalling constantly. Each time it is reinstalled, the battery is charged a little bit more.
After mayby 40min i went up from 3686 V to 3720 V.
It seems that my only hope is to reinstall RUU. I tried to flash wrong ROM, from wrong model and as one user wrote above, it has rewritten my partition. Same time it destroyed recovery.. I cannot flash recovery now because the partition is rewritten...
And without working recovery i cannot charge the battery being in bootloader.. If i understand it all correctly.
I already tried to install RUU with 3710 V. It started to install, but stopped after few min with information that battery is too low..
So i think ill leave this script running for a whole night, and hope, in the morning battery will be charged just enough to install RUU eventually..
Uff
Okey, finally its fixed..
After 7 hours of constant reinstalling the phone by the script, the battery was loaded enough to finish RUU instalation process.. (battery went to about 3830mV power)
After oryginal RUU was installed, everything went fine.
Now i already re-unlocked the bootloader, re-rooted the phone and all works correctly.
Thanks all people who helped. Mostly to redpoint73, who diagnosed the problem straight away and put me on the right track.
Amazingly impressive to me.
Thanks for following up with your success.
WR
Sent from a CleanRom-V OneX
THAT is AWESOME
Senbration said:
Thanks all people who helped. Mostly to redpoint73, who diagnosed the problem straight away and put me on the right track.
Click to expand...
Click to collapse
Your welcome, and no problem really. It was an easy problem to recognize, as I've seen it several times before on here.
Nice job getting the phone charged. Haven't seen that solution before.
Thanks people for not calling me a noob and not blaming for installing the wrong ROM. Even though it was a silly mistake..
Sent from my HTC One X using Tapatalk 2
Senbration said:
Thanks people for not calling me a noob and not blaming for installing the wrong ROM. Even though it was a silly mistake..
Click to expand...
Click to collapse
Sh1T! Did I forget to do that???? I must have been in a good mood . . .
Heh it must have been so
Sent from my HTC One X using Tapatalk 2
Related
Hi all, I am sorry if this is already posted or answered but I spent all day yesterday searching and reading and cannot find the answer.
I have 2 Htc sensations that I messed up some how and would be very grateful if you could help me with them.
Phone 1 has been rooted for a long time and in preparation for ICS I flashed T-mobil: Download 3.32 from here
http://forum.xda-developers.com/showthread.php?t=1459767
and now the phone works but it will randomly reboot. I have wiped the cache, delvak cache and battery stats.
I am completely lost please help.
Phone 2 I think I may have messed up real bad here is what I did to it.
I rotted it from here
http://forum.xda-developers.com/showthread.php?t=1192300
I got to step 2 sub step 6 and now it continuously reboots it starts with the white screen with HTC on it then goes to another white screen that says HTC Quietly brilliant for a second and repeats.
Please help me yes I am a noob and grateful for any help.
Wow that was a fun ride (not really) it appears I did not flash the PG58IMG file correctly, after I flashed it correctly I got Insert Coin installed and so far it seems that they both are working. only time will tell.
Thanks anyway guys.
A.J.
If you are trying to install the latest firmware and having the HTC log restart problem. Try to super wipe on the recovery and install first the 3.12 firmware.
HTH
Did you install supercid after root?
Sent from my HTC Sensation 4G using xda premium
Both phones are working fine but I have a new question, I can not get the voice dialer to work ie I long press the button on my plantronics bt and say call tom.
I have tried vlingo from the market and this fix
http://forum.xda-developers.com/showthread.php?t=1133246
but nothing has worked. is it just not working in Insert Coin rom?
Did I just brick my phone?
I tried to flash the 1.17 firmware and the last step failed, now it wont boot at all just a black screen the only thing it will do is the charge lite will come on bit it stays on after I unplug it.
which of the 2 phones you are talking about?
In a previous post you said that problem was solved, now what?
Also, it would be better to know what your bootloader says and what you were attempting to do before black screen.
area1509 said:
Did I just brick my phone?
I tried to flash the 1.17 firmware and the last step failed, now it wont boot at all just a black screen the only thing it will do is the charge lite will come on bit it stays on after I unplug it.
Click to expand...
Click to collapse
Sounds like a brick to me, but since the problem is unclear, it's possible to fix. I wish I could help but I don't understand your issue to be honest!
I had 3.32 on it with Insert Coin ICS and thought I have 2 so might as well restore one to factory setting that's when I tried to flash the 1.17 and it never started again.
T-Mobile HTC Sensation 4G
The other one is working so I am not messing with it.
I had the same thing happen to me and it was over for the phone. Took it in to tomo and told them it died and after I charged it and went to turn it on, bam, went black and never came back. They never got it to work either and replaced it for me
You mean 1.17 is the hboot?
In this case you installed a hboot for GB while on ICS rom. Obviously it won't work.
If you want to downgrade to GB you can try to run a GB RUU while in bootloader - fastboot usb (if you can still reach it)
kualmente said:
You mean 1.17 is the hboot?
In this case you installed a hboot for GB while on ICS rom. Obviously it won't work.
If you want to downgrade to GB you can try to run a GB RUU while in bootloader - fastboot usb (if you can still reach it)
Click to expand...
Click to collapse
He was in the process of going back to gb and that's 1 of the steps. U have to flash a gb firmware to go back to it from ics. I've done it countless times with no issues.
mugetsu666 said:
He was in the process of going back to gb and that's 1 of the steps. U have to flash a gb firmware to go back to it from ics. I've done it countless times with no issues.
Click to expand...
Click to collapse
Oh yes I have made many times too buf, if he changed firmware without changing rom obviously get stuck, and this seems happening to him.
No what's happened to him is what happened to me. It's like it gets fried or something. The screen goes black and u can't turn it on or get into bootloader. Tmobile told me when it happened it was dead and got me a new 1
kualmente said:
Oh yes I have made many times too buf, if he changed firmware without changing rom obviously get stuck, and this seems happening to him.
Click to expand...
Click to collapse
Yes you got it I will try to get it replaced. Wish me luck.
Thank you guys so much.
area1509 said:
Yes you got it I will try to get it replaced. Wish me luck.
Thank you guys so much.
Click to expand...
Click to collapse
Good luck mate. Just let us know if it worked
All of a sudden one day I turned it on and it wouldnt go past the htc logo. It comes on, stays on the logo for a few seconds then reboots. I dont know what could have caused this but my friend had it for the day and when I got it back this started happening. I've tried turning the phone on without a simcard and memory card, fractory reseting and wiping the cache partition.
I am a newb but have gotten a reasonable amount of knowlege on android over the past 24 hours but so far none of the posts or information i've gotten on the internet has proven useful. Does anyone know of a solution or advice which may help me with booting to my os.
By the way I have an HTC sensation 4g on T-mobile
Not to sure of the version of android thou but I have a HBOOT of 1.18.
Bricked ..
phoenix220693 said:
All of a sudden one day I turned it on and it wouldnt go past the htc logo. It comes on, stays on the logo for a few seconds then reboots. I dont know what could have caused this but my friend had it for the day and when I got it back this started happening. I've tried turning the phone on without a simcard and memory card, fractory reseting and wiping the cache partition.
I am a newb but have gotten a reasonable amount of knowlege on android over the past 24 hours but so far none of the posts or information i've gotten on the internet has proven useful. Does anyone know of a solution or advice which may help me with booting to my os.
By the way I have an HTC sensation 4g on T-mobile
Not to sure of the version of android thou but I have a HBOOT of 1.18.
Click to expand...
Click to collapse
this same thing happened to me but i have the Sensation not the 4g .. but i'm sure you probably messed up in the firmware update bit .. as i remember that logo flash and restart all the time ..
follow this one, http://forum.xda-developers.com/showthread.php?t=1472298
you've got to get any files concerning the firmware you had off your sd card before you try anything else ..
and check this too: http://forum.xda-developers.com/showthread.php?t=1668276
these are all guides from zero that show you everything ..
good luck then ..
modyali88 said:
this same thing happened to me but i have the Sensation not the 4g .. but i'm sure you probably messed up in the firmware update bit .. as i remember that logo flash and restart all the time ..
follow this one, http://forum.xda-developers.com/showthread.php?t=1472298
you've got to get any files concerning the firmware you had off your sd card before you try anything else ..
and check this too: http://forum.xda-developers.com/showthread.php?t=1668276
these are all guides from zero that show you everything ..
good luck then ..
Click to expand...
Click to collapse
I tried flashing but i only got a little farther then kept restarted again. I turned it on the next morning and it wouldnt even turn on.
Need more details...
Stock?
Rooted?
S-on or s-off?
Custom recovery installed?
One thing is for sure, your phone isn't bricked and can be restored. The details of the device in the questions above are needed to determine exactly how to fix it though.
It sounds like your ROM got corrupted. (I can't even guess how) Ultimately you will be able to fix this by installing a new ROM. It's just a matter of figuring out what procedures you need to use based on your set up in order to do that.
Skipjacks said:
Need more details...
Stock?
Rooted?
S-on or s-off?
Custom recovery installed?
One thing is for sure, your phone isn't bricked and can be restored. The details of the device in the questions above are needed to determine exactly how to fix it though.
It sounds like your ROM got corrupted. (I can't even guess how) Ultimately you will be able to fix this by installing a new ROM. It's just a matter of figuring out what procedures you need to use based on your set up in order to do that.
Click to expand...
Click to collapse
It is stock, but i flashed it from gb to ics to try to resolve the problem. Rooted with htcdev, s-on. Also I installed CWM after it began to do that. I flashed a new hboot but that solved nothing, the next day it got worse and wouldn't even turn on.
phoenix220693 said:
It is stock, but i flashed it from gb to ics to try to resolve the problem. Rooted with htcdev, s-on. Also I installed CWM after it began to do that. I flashed a new hboot but that solved nothing, the next day it got worse and wouldn't even turn on.
Click to expand...
Click to collapse
you should used revolutionary.io method to S-OFF easily your device with that hboot version
that means that you have GB firmware and an ICS rom can't run in that fw version
while your are S-ON you should have installed 4ext recovery,enable smartflash from it and then flash a GB rom
after that you said you flashed a new hboot
i am not sure if you can do that as your are S-ON
and the result is not even turning on!
it seems to me that your device is bricked
use the unbricking project from dev section
edit:can you still enter to bootloader?
rzr86 said:
you should used revolutionary.io method to S-OFF easily your device with that hboot version
that means that you have GB firmware and an ICS rom can't run in that fw version
while your are S-ON you should have installed 4ext recovery,enable smartflash from it and then flash a GB rom
after that you said you flashed a new hboot
i am not sure if you can do that as your are S-ON
and the result is not even turning on!
it seems to me that your device is bricked
use the unbricking project from dev section
edit:can you still enter to bootloader?
Click to expand...
Click to collapse
I cannot use revolutionary because i get the phone to go past the htc logo. I could only get into the bootloader. I upgraded from 1.18 to 1.27 so s-on didnt matter. I tried to unbrick but it said no device found.
phoenix220693 said:
I cannot use revolutionary because i get the phone to go past the htc logo. I could only get into the bootloader. I upgraded from 1.18 to 1.27 so s-on didnt matter. I tried to unbrick but it said no device found.
Click to expand...
Click to collapse
from fastboot connect your device into the pc
go to the folder where you have adb and fastboot files
open a command window there and do
fastboot getvar version-main
i assume you have 3.32.or3.33 firmware but do it
if yes then from this thread do step 2
http://forum.xda-developers.com/showthread.php?t=1631861
after that enable smartflash from recovery and flash an ics rom
So My phone is constantly freezing and rebooting in apps every 5-15 minutes and I am going to try going back to stock and seeing if this occurs. My question is do i have to wipe my current rom? Or do i only have to fastboot oem lock and run ruu? Help would be appreciated. Think it is getting worse..
WhatTheAndroid? said:
So My phone is constantly freezing and rebooting in apps every 5-15 minutes and I am going to try going back to stock and seeing if this occurs. My question is do i have to wipe my current rom? Or do i only have to fastboot oem lock and run ruu? Help would be appreciated.
Click to expand...
Click to collapse
Yes, just run fastbook oem lock and then run the ruu. Make sure that you have the latest drivers from HTC (use htc sync if you can). Good luck!
For ruu grab the appropriate one .... Relock your bl like you Saud and run the ruu from you bl mode ...no need to wipe anything the ruu will do that for you
Skeeterdrums said:
Yes, just run fastbook oem lock and then run the ruu. Make sure that you have the latest drivers from HTC (use htc sync if you can). Good luck!
Click to expand...
Click to collapse
and i run the command in fastboot on my htc one x? ive did it once before.
WhatTheAndroid? said:
and i run the command in fastboot on my htc one x? ive did it once before.
Click to expand...
Click to collapse
Yessir head over to gunnymans thread in general forum to clear any confusion that remains
phone is going haywire.....Not being detected..rebooting every second..cant even get into an app...got into twrp and going to charge it ill 70 and restore to a better backup then hopefully ruu...thanks for the help
WhatTheAndroid? said:
phone is going haywire.....Not being detected..rebooting every second..cant even get into an app...got into twrp and going to charge it ill 70 and restore to a better backup then hopefully ruu...thanks for the help
Click to expand...
Click to collapse
Usually, the phone doesn't get detected if the drivers aren't up to date. Is it rebooting even from bootloader? You should be able to install everything from there, hopefully meaning restarts aren't an issue.
HTC One X using CleanRom 5.1 with BeastKernel 4.4
Skeeterdrums said:
Usually, the phone doesn't get detected if the drivers aren't up to date. Is it rebooting even from bootloader? You should be able to install everything from there, hopefully meaning restarts aren't an issue.
HTC One X using CleanRom 5.1 with BeastKernel 4.4
Click to expand...
Click to collapse
finally got it recognized and successfully ruu'd.It was very odd, like the phone was progressively getting worse for some reason.i am not not getting rebooted on stock rooted so it had to do something with my settings on the rom..like i said i under clocked and overclocked it, hot rebooted it, wiped cashe and dalvik...nothing was working and it finally just kept rebooting and freezing at home screen..Maybe a bad successful flash lol.. im not really sure.. or flashing over a bad flash had something to do with it..I might wait till jellybean comes out.
Have you tried to simply factory reset?
i personally like ruu'ing. i should do the same soon just to clean house. in the end it's pretty easy to get fluent on this phone.
i would say immediately after unlocking bootloader to ruu. i noticed some differences in the 1.85 to 2.20 ota vs the 2.20 ruu. it will also clean up any mess that might of been left on the phone. im also pretty ocpd =)
also htc sync imo is useless, i just use the standalone htc drivers haven't had any issues with them.
OP... What rom/kernel combo were you running?
Only time I've seen another phone go that nuts is when my cousin flashed rohans kernel in viper lol
Sent from my One X using Tapatalk 2
InflatedTitan said:
OP... What rom/kernel combo were you running?
Only time I've seen another phone go that nuts is when my cousin flashed rohans kernel in viper lol
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Viper and beastmode. My phone was going nuts....froze at the start screen 3 times and reset it self into a bootloop, then went back to freezing when start screen appeared..one of the times all I could see is the notification bar but I couldn't drag it Down. Lots of other crazy stuff happened on it as well...to much to tell. But I heard cleanrom is pretty stable, do I have to wipe stock rooted(no custom Rom yet) trying to find a good one and do I have to flash boot IMG if I'm on 1.14 or is it Included in the cleanrom installer? Might try elemental with cleanrom..see how that works out.
So, just to set the stage, I'm not a developer, but I'm fairly practiced at using ADB, unlocking bootloaders, rooting and unrooting, and installing custom recoveries and ROMs - that is to say, I know what I'm doing. I recently bought an HTC One, and in preparation for wanting to sell my One X on ebay, I wanted to return it to completely stock and make sure OTA updates were working properly.
I started by relocking the bootloading and installing the 2.20.502.7 RUU (I have an AT&T One X). That went fine and booted up properly, but I wasn't seeing the OTA updates, so I thought maybe the stock recovery hadn't been installed properly, and when I tried to boot into the recovery I couldn't get the menu to show (the initial image appeared, but holding Vol Up+Down didn't do anything, just made the error image appear after several seconds). So I downloaded the stock recovery image, reunlocked the bootloader, flashed the stock recovery...and then when I went to reboot the phone turned off and hasn't turned back on since.
Getting stuck in a bootloop or something I know how to deal with, but the phone is completely unresponsive, holding the power button for any length of time seems to have no effect, hoping you guys might have some ideas.
FYI My phone was on bootloader 1.09 before flashing the RUU, 1.14 after.
Requested moving to the AT&T One X forums
TToivanen said:
Requested moving to the AT&T One X forums
Click to expand...
Click to collapse
Ugh....thought that's where I was, evidently didn't look at the forum close enough...
bikeracer4487 said:
So I downloaded the stock recovery image, reunlocked the bootloader, flashed the stock recovery...and then when I went to reboot the phone turned off and hasn't turned back on since.
Click to expand...
Click to collapse
Where did you download from, and can you give link? Any charge light, when you connect the wall charger?
redpoint73 said:
Where did you download from, and can you give link? Any charge light, when you connect the wall charger?
Click to expand...
Click to collapse
Link to site of download link: http://onexroot.com/one-x-unroot/how-to-unroot-rooted-htc-one-x/
Download link: http://downloadandroidrom.com/file/HTCOneX/unroot/OneXUnroot.zip
Connecting charger shows blinking red notification light. As a side note, the phone was at 96% battery when I was working on it and I left it plugged in overnight, just in case.
That website doesn't make mention of the AT&T version. Not certain, but I'm inclined to believe its the recovery for the quad core version. Different hardware, with different partitions, so you might be hosed.
Take great care when you install mods from these kinds of websites (places other than XDA). They often do not clearly delineate between the dual core and quad core versions of the One X.
redpoint73 said:
That website doesn't make mention of the AT&T version. Not certain, but I'm inclined to believe its the recovery for the quad core version. Different hardware, with different partitions, so you might be hosed.
Take great care when you install mods from these kinds of websites (places other than XDA). They often do not clearly delineate between the dual core and quad core versions of the One X.
Click to expand...
Click to collapse
Yeah...that was dumb...I realized what you were getting at as I was getting the link for you... That said, I WAS able to get it turn on just now by holding down the Vol Down button and power for 10 seconds...although, didn't actually do anything, letting go of those buttons and simultaneously unplugging it from the charger made it turn on...not sure which or both of those things were actually the cause though. But once I was booted in I tried booting into recovery with "adb reboot recovery" but that got me to the HTC logo screen with the developer warning but it hung there. Luckily, I was able to boot into the bootloader, but again, trying to get into the recovery made it hand at the "quietly brilliant" screen. Do you know if the stock RUU's are supposed to flash the stock recovery, or do have a link to AT&T's stock recovery? I'm having a hard time finding one labeled properly.
Yes, RUU flashes stock recovery.
If the screen is coming on, that is usually a good sign. Try the RUU again.
BTW, do not not not install the 3.18 RUU if you are SuperCID and S-on. Or you will brick.
redpoint73 said:
Yes, RUU flashes stock recovery.
If the screen is coming on, that is usually a good sign. Try the RUU again.
BTW, do not not not install the 3.18 RUU if you are SuperCID and S-on. Or you will brick.
Click to expand...
Click to collapse
Okay, I'll try that, I still have the 2.20 RUU. Good to know on the 3.18 since I am def SuperCID. Will being SuperCID affect my ability to install OTA updates?
bikeracer4487 said:
Will being SuperCID affect my ability to install OTA updates?
Click to expand...
Click to collapse
Yes, SuperCID and S-on will also brick your phone, if you try to install 3.18 OTA.
You might consider doing s-off, or changing back to the AT&T CID. Even if you don't update using the 3.18 OTA, its very possible the buyer will.
redpoint73 said:
Yes, SuperCID and S-on will also brick your phone, if you try to install 3.18 OTA.
You might consider doing s-off, or changing back to the AT&T CID. Even if you don't update using the 3.18 OTA, its very possible the buyer will.
Click to expand...
Click to collapse
Good idea. Found a thread for S-OFF (http://forum.xda-developers.com/showthread.php?t=2155071) but not sure how to restore AT&T CID.
EDIT: Frick, wish I had though to do this BEFORE installing RUU and unrooting the phone.
Hi All!
Recently i flashed TWRP and Cynogenmod 10.2.1 stable to my HTC Telestra One XL (evita)
I unlocked boot-loader
I successfully rooted
But I shut down once, and when i tried to boot, it got stuck in a boot-loop
Upon many retries, it suddenly wont turn on
when I charge it it only has a flashing red light but it wont even turn on, no screen not buttons; nothing!
And if I plug it in to my PC, the pc keeps sounding the USB Connected sound multiple times over a short period of 30 seconds to 2 minutes and then it gives off multiple shaky beeps
I hope this is enough info to let anyone help out!
Thank You in Advance
EDIT:
when connected to a pc it shows drivers is ready to use but tries to install QHUSB_DLOAD but fails and latest RUU does not detect
Thx again
What is the exact full filename of the ROM zip that you flashed? When a device is showing up as QHSUSB_DLOAD in Windows it usually means it's bricked.
Sent from my Evita
timmaaa said:
What is the exact full filename of the ROM zip that you flashed? When a device is showing up as QHSUSB_DLOAD in Windows it usually means it's bricked.
Sent from my Evita
Click to expand...
Click to collapse
Just found out:
a friend of mine tried to flash a file named "cm-10.0.0-evita" and it gave off a message saying that this phone is not rooted or missing supersu/ something along those lines
before that he wiped sd card (whole thing)...
and then it went off from there
NOTE: its a phone with mess with, but still want to fix even though its just a side phone we barely use....help appreciated
So does it power on at all?
Sent from my Evita
timmaaa said:
So does it power on at all?
Sent from my Evita
Click to expand...
Click to collapse
nope
when plugged in it only has a red LED that flashes once every once in a while and thats it
pc recognises it but wants to install qhusb_dload (as mentioned) and it just sais no driver found
i am researching and i found something called a "RIFF Box" but unsure if its worth it, plus i dont know where to jtag it (if its possible at all)
PS: hi from sydney!
Al-Dazzlez said:
Just found out:
a friend of mine tried to flash a file named "cm-10.0.0-evita" and it gave off a message saying that this phone is not rooted or missing supersu/ something along those lines
before that he wiped sd card (whole thing)...
and then it went off from there
NOTE: its a phone with mess with, but still want to fix even though its just a side phone we barely use....help appreciated
Click to expand...
Click to collapse
How did he try to flash it -_- these vague responses make it very hard to help. Bottom line is you can try pressing and holding power until the light goes off and then power and volume down to get the bootloader up, if that doesn't work you can try the evita jet tool to try to unbrick it. Bricks such as yours are not recoverable 9 times out of 10.
It looks like your only option is to get a jtag repair done. I wouldn't bother trying to do it yourself unless you're a fully experienced electronic engineer or the like. I'm not sure how many jtag repairers there are in Australia but I'm guessing Google should be able to reveal that information. Howdy from Melbourne.
Sent from my Evita
Hi from Canada!... I just wanted to be part of the greetings.. :laugh:
exad said:
How did he try to flash it -_- these vague responses make it very hard to help. Bottom line is you can try pressing and holding power until the light goes off and then power and volume down to get the bootloader up, if that doesn't work you can try the evita jet tool to try to unbrick it. Bricks such as yours are not recoverable 9 times out of 10.
Click to expand...
Click to collapse
he placed the cyanogen mod on the phones sd card, then he wiped sd card, after that he used the install function on twrp it gave him a message that his phone is not rooted and if he would like to root it, he accepted, then it rebooted into twrp, and he tried again to install, same message appeared and then he gave up and shut it down...(sorry for vague terms, please bear with me, still trying to learn the ropes of talking on this forum)
I gotta say, this is all very odd :/ How did he install anything if he wiped the SD card after copying it over? :/ hmmmm In any case, you CAN try he jet tool as per my last post before getting a jtag. You'll need a linux install or Bootable USB stick/CD/DVD though.
My guess is that the only thing he installed was SuperSU. That'd be why it booted straight back into TWRP.
Sent from my Evita
timmaaa said:
It looks like your only option is to get a jtag repair done. I wouldn't bother trying to do it yourself unless you're a fully experienced electronic engineer or the like. I'm not sure how many jtag repairers there are in Australia but I'm guessing Google should be able to reveal that information. Howdy from Melbourne.
Sent from my Evita
Click to expand...
Click to collapse
i researched..nothing..just some videos of people who do it (jtag)in the US and US only......
but still asking 'round the shops wont hurt i guess:laugh:
ill keep ya posted about using that tool you mentioned!
and exad; SUP!
and yeah.. it sounds weird to me too but i mainly play around with stuff like the galaxy series samsung's so the htc stuff is still new...and i have to admit...i am hating it so far.... but still experience cant hurt :laugh:
Hi guys!
im back
I JTAG'd the phone overseas, and it came back, surely enough, working, but now another problem arises,
the guy apparently unlocked the bootloader, S-Off, and installed CM with android 4.3.1. the phone boots, everything is well, but for times from 10 seconds to minutes of usage it just turns off, the Hboot shows
***tampered***
***relocked***
any idea wth is wrong with it now?
it does not reboot from power menu, and does not do anything really since I cant keep it on for more than a few minutes at most. I cannot keep it on long enough to unlock the bootlaoder anymore, and I cannot boot into TWRP (as the guy told me he put it on)
da hell do I Do now? any help appreciated
Try an RUU, any Evita RUU is fine if you have s-off.
Sent from my Evita
timmaaa said:
Try an RUU, any Evita RUU is fine if you have s-off.
Sent from my Evita
Click to expand...
Click to collapse
Thank you, tried but it did not pick up, but:
UPDATE:
I booted into teamwin, and flashed a CM11snapshot (latest one) everything seems fine so far (after 20 million dalvik and cache and factory restores) but now i am waiting for the problem to arise again, if not, ill have one problem left to fix....the back button does not work....
and now how the hell do i use an RUU on a custom frimware, ? (used it once on this phone but using a stock rom)
thanks again for your time timmaaa, seriously appreciated
Al-Dazzlez said:
Thank you, tried but it did not pick up, but:
UPDATE:
I booted into teamwin, and flashed a CM11snapshot (latest one) everything seems fine so far (after 20 million dalvik and cache and factory restores) but now i am waiting for the problem to arise again, if not, ill have one problem left to fix....the back button does not work....
and now how the hell do i use an RUU on a custom frimware, ? (used it once on this phone but using a stock rom)
thanks again for your time timmaaa, seriously appreciated
Click to expand...
Click to collapse
There's only one way to run an RUU, and that's to connect your phone and initiate the program in Windows. You're s-off so all security checks are disabled.
Sent from my Evita
timmaaa said:
There's only one way to run an RUU, and that's to connect your phone and initiate the program in Windows. You're s-off so all security checks are disabled.
Sent from my Evita
Click to expand...
Click to collapse
I Just ran one, Unlocked bootloader, on Cm11 snapshot after re-root and all that crap done, should be alright now