First of all I experimented with some custom ROMs. But after a while I wanted to go back to stock and tried to install a RUU I already used succesfull. But during the installation it hung up and I had to cancel it. And now it is impossible to use everything. The phone just show me the black background with the HTC log and four triangles in the corners. I can't use the bootloader, go into recovery or use adb, first of all because my PC doesn't recognize my phone anymore. Already tried to use adb and some tools like the AIO bye anders and the XL Multi tool. I also tried the Forum search for bricked stuff, but nothing worked so far. Any idea how to fix it?
And please excuse my bad english. It was a long day. ^^
In pretty sure that's completely bring, idk how yous brick the sxl, ivebdonebso much stuff to mine and I wonder how mines still perfect, you might wanna look into some articles about jtag!
Don't know how, as I said. I did also do a lot of stuff to my phone, custom ROMs, Themes, Kernel etc. Now I just tried to go back to stock, relocked, went into fastboot, everything as prescribed.
And during the installation I've got said that the installation was aborted. The progress bar on the phone didn't react and the software stucked too. Additionaly, my PC is really potent, without any other software problems so far. So, Software forced to close and I had no other joice than to put the battery out of my phone to restart it. And so it happened.
Thanks for the info about jtag. As an Electrician, it is really inviting to buy such a machine. But I think, this time I'll bring it to repair and wait for the results. Let to the experts their job. But thanks for the reply.
Mr. Despair said:
Don't know how, as I said. I did also do a lot of stuff to my phone, custom ROMs, Themes, Kernel etc. Now I just tried to go back to stock, relocked, went into fastboot, everything as prescribed.
And during the installation I've got said that the installation was aborted. The progress bar on the phone didn't react and the software stucked too. Additionaly, my PC is really potent, without any other software problems so far. So, Software forced to close and I had no other joice than to put the battery out of my phone to restart it. And so it happened.
Thanks for the info about jtag. As an Electrician, it is really inviting to buy such a machine. But I think, this time I'll bring it to repair and wait for the results. Let to the experts their job. But thanks for the reply.
Click to expand...
Click to collapse
So if you turn on phone all you have is a black screen? What if you pull out battery and insert it and hold down volume down and power button? Does it go to bootloader or also just black screen? If black screen try adb devices and fastboot devices. And when connected look in control panel what it calls the phone. Perhaps it says qsusb or something?
Sent from my HTC Sensation Z710e using XDA Premium HD app
I'm not being rude I'm.just stating sxl is very hard to brick if you even try to, I'm not saying its your fault either, a fault USB cable could brick your phone if your half way through an installation if you can't get into bootloader, recovery or pick up your device in adb, I think the only solution is jtag! All the best!
ricky310711 said:
I'm not being rude I'm.just stating sxl is very hard to brick if you even try to, I'm not saying its your fault either, a fault USB cable could brick your phone if your half way through an installation if you can't get into bootloader, recovery or pick up your device in adb, I think the only solution is jtag! All the best!
Click to expand...
Click to collapse
before jtag , if the phone is under 2 years , always try to send it in for repair they cant boot up the device , then they cant see if it is unlocked
Very true Anders! Just hope he has warrenty!
anders3408 said:
So if you turn on phone all you have is a black screen? What if you pull out battery and insert it and hold down volume down and power button? Does it go to bootloader or also just black screen? If black screen try adb devices and fastboot devices. And when connected look in control panel what it calls the phone. Perhaps it says qsusb or something?
Sent from my HTC Sensation Z710e using XDA Premium HD app
Click to expand...
Click to collapse
When yo flash RUU the phone goes into kind an own bootloader. The black screen with a silver HTC logo. This is the only thing i get into, but with four triangles, in each corner of the display. It doesn't matter what I do, tried to pull the battery, use the key combo, adb/fastboot etc. When the phone starts, it shows directly the screen described above.
Sent in for repair today and just can wait now. But thanks guys for your replies.
How did it go? Did they fix your problem? Also this happened to me, I discovered that the cause was because installing the ruu relocks the bootloader before it wipes the Rom, and mine failed just before wiping the Rom,I had a custom Rom installed so it would not boot into it because the bootloader was locked so I re-unlocked the bootloader then the phone booted up normally!
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Related
I recently bought this Nexus off eBay and it worked fine.
Owner said it had problems with the SD card, but it seemed to be working, for they said it wouldnt read, when it does.
Anyway, it had cyanogen mod 6.1.1 on it, and I hate the setup...so i changed roms. That was a success, but when i flashed a sense rom thru clockwork(most updated) it said:
E:Error in /sdcard/N1Sensation_v0.4.zip
(Status 0)
Installation aborted.
Now, when i flash any roms, whether it says it installed correctly, it doesnt change anything. Now it's stuck at the 4 color x with the unlock icon. Any advice is good advice!
In my hboot, it says:
*** UNLOCKED ***
NEXUSONE PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0b15
TOUCH PANAL-SYNT0103
RADIO-5.00.00.04
Oct 12 2010, 14:33:16
HBOOT
Etc. Etc. Etc.
Thanks for any help!
Edit: I fixed the issue with why it failed, was my fault, didnt partition the card...but i was flashing a stock rom and it said complete and when i rebooted it stayed at the X and then powered off. Since then has never turned on. I don't know what to do. Nothing will turn it back on. I have a universal charger that charges the battery and it said the battery is full. I need help!
Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??
Dude Random21 said:
Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??
Click to expand...
Click to collapse
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.
matistight said:
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.
Click to expand...
Click to collapse
Try flashing CM7. Also...before you do...you may want to search for a format.zip from a member named temasek. It'll wipe your phone...clean. Real clean. Then flash CM7. try that.
also....those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.
SiNJiN76 said:
Try flashing CM7.
those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.
Click to expand...
Click to collapse
I can't flash anything. Phone wont react to anything anymore. Hoping one of my family members can fix it. But if I get it on I will try that.
I am pretty sure i waited long enough, but who knows. I didn't partition my card, which may have been the problem. And also it was S-On....which i thought was odd when it had a custom firmware.
Unlock bootloader. Flash recovery. Boot into recovery. Wipe everything. Flash rom.
Why do you guys keep suggesting software stuff when it's probably a hardware problem he can't get the phone to boot up so he can't do any of that.
Although there is one thing I want you to try before your family take a crack at it to take it apart and what not, it's a long shot but it's your last chance if it's software. Hold down trackball and press power keep holding trackball for another 5-10 seconds (better to long then to short) then connect it to the computer via USB you could see a popup notification saying that it's looking for driver software if you do then it's software and we need to reflash everything and might need to unlock the bootloader. Now if you don't see a popup notification I would still go check in the device manager and check for an unidentified device probably in other (it should be extracted so that you can see it).
If this doesn't work then sorry but I think it's a brick
Because in order to find out if its truly a hardware problem you need to try every software fix first.
Op mentioned nothing of trying fastboot as well. Software fix is free hw is not. That is why we suggest software fixes.
Sent from my Nexus S using XDA App
Let me remind you guys, THE PHONE WONT TURN ON AT ALL REGARDLESS OF WHAT I DO. I can post a YouTube video to show everything. It'd be very random for it to be hardware because it just turned off and will not turn back on. If there is any software like an RUU out there, that would help, if not, ill have to buy a bottom piece and warranty it out. But I'd feel bad because that isn't the right thing to do.
I don't expect you guys to fix it and I and very thankful of your help! But the phone won't turn on at all. So telling me to flash roms doesn't work. Imagine it as flashing a rom with the battery out of your phone. I am wondering if there's an adb way or something to get it to turn on and restore to stock?
With all that said, any help is amazing help and I am very grateful that this isn't a post I have to bump! Thank you so much, when I go on the PC, ill thank the helpful posts
Sent from my (finally) permanent root Sensation 4G
Then it is a brick if it won't turn on at all. The entire getting stuck at the x thing confused me to think it was powering on.
You have me confused sir, I'm not quite sure what good it is your looking for a RUU for. If the phone truly won't turn on/go past the X screen and you have it on a charger with no LED notification, then the phone is bricked. When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom. If you can still get to the bootloader screen then you are not bricked and should retry everything from scratch.
Thread Closed
xsnipuhx said:
When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom.
Click to expand...
Click to collapse
Sensation based, but it was a Sense rom
Confirmed it is bricked.
Sold on eBay for $100
Bought for $77
Semi-Winning.
Thread Closed
A friend of mine tried to root his white tmobile g1 and im not sure what he did to it. heres what im working with.
press power button goes to g1 screen and then to the factory android recovery (e2)
can wipe, factory reset and can select install update.zip
the phone wont take any update i throw at it and ive tried like 7-8 i have found here on xda. I have no idea what phone was on previously.
I CANNOT access the bootloader no matter what i do. i even went as far as to dissasemble the phone and replace the buttons (thought home might be sticking), anyone have any ideas on how i can possibly ressurect this?
without bootloader access i cant flash to downgrade. Im at a loss here and really hate getting outsmarted by a phone. I dont think its a brick... yet being i can hit stock recovery and that blue led test works.
If bootloader is truly gone, not just hidden from you, the phone can not boot. I know of no flash able update.zip for a bootloader in the stock recovery which unfortunately means this is a brick. The blue light mode is only helpful for JTAG, sorry
Sent from my Nexus 7 using xda premium
I finally managed to get the phone to boot by swapping the cables out of another phone. Weird issue but nice having a half dozen phones laying around for parts
Sent from my HTC One XL
I apologize in advance if this has been discussed in the past, but my searching here hasn't helped so I gotta ask for help.
Having a problem with me wife's HTC Vivid. It's bone stock. Nothing has been messed with other than whatever updates may have been installed automatically over the air. She wouldn't let me touch it to root it, mod it, nothing.....
Anyway. Problem happened Saturday night. Phone shut down due to dead battery. Put it on charger overnight. Tried to boot it up Sunday morning and it stops at the white HTC screen. Period. Just sits there. Forever.
I did some reading, learned how to hold power and vol down buttons to get to HBOOT. Tried navigating to recovery. It goes to white HTC screen, then to a black screen with a green circle arrow icon, then to a red triangle with an exclamation point.
I downloaded drivers and the HTC RUU and was going to try fastboot usb, but when it said all data will be lost I stopped.
My wife has tons of pics and stuff on her phone (that she has failed to back up ) and really doesn't want to loose them.
Before I wipe the phone and try to reinstall the stock rom do any of you have any suggestions on a way to get it back up and running and recover her pics and stuff?
Or are we screwed? :crying:
Ginther said:
I apologize in advance if this has been discussed in the past, but my searching here hasn't helped so I gotta ask for help.
Having a problem with me wife's HTC Vivid. It's bone stock. Nothing has been messed with other than whatever updates may have been installed automatically over the air. She wouldn't let me touch it to root it, mod it, nothing.....
Anyway. Problem happened Saturday night. Phone shut down due to dead battery. Put it on charger overnight. Tried to boot it up Sunday morning and it stops at the white HTC screen. Period. Just sits there. Forever.
I did some reading, learned how to hold power and vol down buttons to get to HBOOT. Tried navigating to recovery. It goes to white HTC screen, then to a black screen with a green circle arrow icon, then to a red triangle with an exclamation point.
I downloaded drivers and the HTC RUU and was going to try fastboot usb, but when it said all data will be lost I stopped.
My wife has tons of pics and stuff on her phone (that she has failed to back up ) and really doesn't want to loose them.
Before I wipe the phone and try to reinstall the stock rom do any of you have any suggestions on a way to get it back up and running and recover her pics and stuff?
Or are we screwed? :crying:
Click to expand...
Click to collapse
You get the red triangle/exclamation point because you dont have a custom recovery installed if Im correct. Using the all in one here is the most user friendly way of installing -
http://forum.xda-developers.com/showthread.php?t=1498003
Install twrp and you should be able to recover your pics/vids by selecting "mount/mount sdcard" in the twrp ui with your phone plugged in to your pc. Then opening the storage located under computer. Navigating to the appropriate folder & cut/pastting to a folder on your pc.
I dont know how technology savvy you are but it sounds like flashing the stock kernel will repair your phone hanging on the htc logo. This is the stock ICS kernel - http://d-h.st/rHX
You can flash it through the all in one. Or follow up here -
http://forum.xda-developers.com/showthread.php?t=1416836
Hope this helps. Good luck!
Sent from my HTC Raider X710e using xda premium
yosoywilson78 said:
You get the red triangle/exclamation point because you dont have a custom recovery installed if Im correct. Using the all in one here is the most user friendly way of installing -
http://forum.xda-developers.com/showthread.php?t=1498003
Install twrp and you should be able to recover your pics/vids by selecting "mount/mount sdcard" in the twrp ui with your phone plugged in to your pc. Then opening the storage located under computer. Navigating to the appropriate folder & cut/pastting to a folder on your pc.
I dont know how technology savvy you are but it sounds like flashing the stock kernel will repair your phone hanging on the htc logo. This is the stock ICS kernel - http://d-h.st/rHX
You can flash it through the all in one. Or follow up here -
http://forum.xda-developers.com/showthread.php?t=1416836
Hope this helps. Good luck!
Sent from my HTC Raider X710e using xda premium
Click to expand...
Click to collapse
Thanks for the help. I was able to get the bootloder unlocked with the all-in-one but when I tried to install the kernel it kept failing. I tried several different things over and over again but no luck.
I finally got frustrated and tried the HTC RUU from their website to see what would happen. I had to relock the bootloader before it would work though. It finally ran successfully and the phone is back up and running now.
Only bad news is that I wasn't able to recover any of her files.
Now she understands the importance of backing up files and getting stuff OFF the phone to another form of long term storage. :good:
Thanks again for the help.
Ginther said:
Thanks for the help. I was able to get the bootloder unlocked with the all-in-one but when I tried to install the kernel it kept failing. I tried several different things over and over again but no luck.
I finally got frustrated and tried the HTC RUU from their website to see what would happen. I had to relock the bootloader before it would work though. It finally ran successfully and the phone is back up and running now.
Only bad news is that I wasn't able to recover any of her files.
Now she understands the importance of backing up files and getting stuff OFF the phone to another form of long term storage. :good:
Thanks again for the help.
Click to expand...
Click to collapse
You probably could have recovered your media. Just by mounting the internal memory like I said in my original post. You really should invest in an SD card that way no matter what happens your stuff is accessible. You can use up to 32GB. People also say 64GB SDXC cards work too. But glad its up and running again.
HTC VIVID ICS 4.0.4 SENSE 4.1
yosoywilson78 said:
You probably could have recovered your media. Just by mounting the internal memory like I said in my original post. You really should invest in an SD card that way no matter what happens your stuff is accessible. You can use up to 32GB. People also say 64GB SDXC cards work too. But glad its up and running again.
HTC VIVID ICS 4.0.4 SENSE 4.1
Click to expand...
Click to collapse
I got into CWM recovery and tried mounting the sdcard but kept getting "error mounting sdcard"
No mater what I did I could not get it to mount and become visible on my pc. I could see the disk drive(s) for the phone, but they were shaded and when I'd try to access them it would say insert disk into drive. When using the all-in-one it would try to push the kernel to the phone, but it got errors too. I tried putting the kernel on a micro sdcard and installing it from cwm with no luck. Couldn't get that to show/mount/work either.
I've done modding to my Samsung phones and build my own pc's so I'm not too technologically challenged.... but, Something was just wrong with this phone and it didn't want to cooperate.
And/or I didn't have the time and patience to keep jacking with it.
Switch to twrp
Sent from my Vivid 4G using Tapatalk 2
Hello Forum..
First, I'd like to acknowledge the great All-In-One tool posted for this new phone. I have been rooting Android since the HTC hero and have always trusted this site for development info. That being said...
I am having problems with my brand new HTC one... After using the All In One tool, my booloader is unlocked, but above the "Unlocked" info is says "Tampered". Also.... I cannot flash the TWRP so I can boot to recovery. After the CMD screens, is says flash is successful, but when I try and boot to recovery, I get the HTC screen with the pink font saying "Entering Recovery" but then my HTC One just shuts off. I then have to hold down the power button for at least 45 second b4 the phone turns back on.
1. What did I do wrong, and can this be fixed??
2. I see I can re-lock bootloader with tool, but there is currently no Factory RUU for Sprint yet????
3. Any assistance would be greatly appreciated
cpthook26 said:
Hello Forum..
First, I'd like to acknowledge the great All-In-One tool posted for this new phone. I have been rooting Android since the HTC hero and have always trusted this site for development info. That being said...
I am having problems with my brand new HTC one... After using the All In One tool, my booloader is unlocked, but above the "Unlocked" info is says "Tampered". Also.... I cannot flash the TWRP so I can boot to recovery. After the CMD screens, is says flash is successful, but when I try and boot to recovery, I get the HTC screen with the pink font saying "Entering Recovery" but then my HTC One just shuts off. I then have to hold down the power button for at least 45 second b4 the phone turns back on.
1. What did I do wrong, and can this be fixed??
2. I see I can re-lock bootloader with tool, but there is currently no Factory RUU for Sprint yet????
3. Any assistance would be greatly appreciated
Click to expand...
Click to collapse
1. I actually had to flash recovery twice to get it to work. You may have to do it more. I dunno. Just keep flashing and trying.
2. Nope no ruu yet. Itll be soon I suppose. 3. No problem.
Sent from my HTCONE using xda app-developers app
youkosnake said:
1. I actually had to flash recovery twice to get it to work. You may have to do it more. I dunno. Just keep flashing and trying.
2. Nope no ruu yet. Itll be soon I suppose. 3. No problem.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Wow....thanks for the fast response... I have been trying to flash the TWRP several times... but it just wont boot to recovery. My phone just hangs and then shuts off. Then I get the "Sprint" splash screen and start-up
Did you have any insite on why I get the "Tampered" indication along with the "Unlocked"??
Im assuming its because youve flashed twrp. Mine says the same.
Sent from my HTCONE using xda app-developers app
Make sure you are using the right gui for the all in one tool kit. There are two for the One. If you aren't using the spring version then it won't work.
Sent from my HTCONE using xda premium
WHoooPeeee!!:laugh:
I got boot to TWRP....FINALLY!! I guess it would have worked out better for me If I had used the HTC One "All-In-One" tool that was specific to Sprint...DUH!! I used the Generic HTC One M7......
....Im Unlocked, Rooted & ROM'd.
This site/forum is just Awesome!!!
Have you seen the clockwork mod recovery on the ONE. I spent 5 minutes staring at the screen. couldnt believe the quality of detail.
001358 said:
Have you seen the clockwork mod recovery on the ONE. I spent 5 minutes staring at the screen. couldnt believe the quality of detail.
Click to expand...
Click to collapse
True
Need help....Similar kind of problem
Hi CPTHook,
I got similar kind of problem in my HTC one. I'm not that technically sound. I simply updated my HTC One's softwares over wifi and after working well for four five days my HTC One (M7) sudden;y stopped working. It gets struck either on start screen or bootloader when I start. There are two flags:
**Tampered**
**Unlocked**
'
My phone is kind of dead since 4 months. Please help me out. I'm very sad. I'll be very grateful to you for this.:crying:
Hi guys, I have the non-lte One running on 2.24.707.3. Today, I restored my stock nandroid (4.2.2) and then tried the rumrunner s-off (rumrunner_m7_2.24.401.1). It worked, and I was successfully s-off, superCID on hboot 1.54. I then flashed a modified hboot(descenpet_HBOOT_1.54_2.24_MOD) to remove the red warning. All went well. Later, while I was recieving a call, the phone got hung up, so I did a reset (holding the power + vol down buttons). The phone got switched off, but never booted back up.. I tried holding the power + vol down buttons but even the buttons aren't flashing.. Connecting it to my pc makes no connection sounds, and again holding the combo makes no difference. The charging light also doesn't light up. Please tell me what I should do, and whether it is a hard brick or soft brick. Thanks in advance.
Just press and hold the power button on it's own and see if anything happens
EddyOS said:
Just press and hold the power button on it's own and see if anything happens
Click to expand...
Click to collapse
Tried it, no avail. I think it's a hard brick, it's detected in my pc as in the screenshot. Any idea what to do?
Its not clear in the screenshot, it says Qualcomm HS-USB QDLoader 9008
n1234d said:
Tried it, no avail. I think it's a hard brick, it's detected in my pc as in the screenshot. Any idea what to do?
Its not clear in the screenshot, it says Qualcomm HS-USB QDLoader 9008
Click to expand...
Click to collapse
why did you use modified hboot now you are in serious trouble. As you are supercid download any ruu and try flashing and if your pc can connect via fastboot you can fix your phone. To check you must type in adb fastboot devices. if results are positive tell me i can help you then
hapticc said:
why did you use modified hboot now you are in serious trouble. As you are supercid download any ruu and try flashing and if your pc can connect via fastboot you can fix your phone. To check you must type in adb fastboot devices. if results are positive tell me i can help you then
Click to expand...
Click to collapse
I used a modded hboot to remove the red warning, have a look at this page (http://forum.xda-developers.com/showthread.php?t=2316726)
To do an RUU, I need to reboot in fastboot, but I can't even get the phone to charge.. Of course adb doesn't detect it..
Another point to note is that I rebooted several times after flashing the modded hboot, and it worked all those times, so this is just random... :'(
Why do people care about the red writing? Unless you're sending it to HTC for repair it makes no difference! It just leads to complications such as this
EddyOS said:
Why do people care about the red writing? Unless you're sending it to HTC for repair it makes no difference! It just leads to complications such as this
Click to expand...
Click to collapse
Well, 2 things
1: The process worked, ok? It's a perfect process to remove the red text, and the modded hboot also worked, I rebooted several times after flashing it.
2: The matter of the fact is that I am actually sending it in for camera replacement.. I guess I'll just tel them to replace the mobo along with it..
So, lets stop fighting like losers and find a way to get out of this situation! It'll help many people in the future
Sent from my iPod touch using Tapatalk
C'mon anybody? I can give more info if required, I'd prefer to know how to solve this myself, rather than relying on htc...
Sent from my iPod touch using Tapatalk
If it's not booting up , and you're stuck in that QDLOAD thing, it's usually the mainboard that's fried and HTC replaced the mainboard in my Sensation under the warranty when it happened to me. I was S-OFF at the time as well, and it came back 100% stock and working
n1234d said:
Well, 2 things
1: The process worked, ok? It's a perfect process to remove the red text, and the modded hboot also worked, I rebooted several times after flashing it.
2: The matter of the fact is that I am actually sending it in for camera replacement.. I guess I'll just tel them to replace the mobo along with it..
So, lets stop fighting like losers and find a way to get out of this situation! It'll help many people in the future
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
good luck buddy btw to remove tampered i just ran indian ruu
n1234d said:
C'mon anybody? I can give more info if required, I'd prefer to know how to solve this myself, rather than relying on htc...
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
I think most of the time, that's not something fixable unless by a service center. You may wanna check this thread: http://forum.xda-developers.com/showthread.php?t=2331454
For one guy the phone "magically" just started again, but I wouldn't hold my breath.
Sorry mate.
Ok, thanks for the info.. Maybe I'll make a strong case. My phone was originally replaced with a new one within a week because of battery problems, and scratch marks that I didn't make.. Then the second one had its mobo replaced for that same battery problem, and now I was going to send this in for replacement because my lower speaker is louder than the upper, and my camera has the dreaded pink tint and my phone has a big gap on its side where the service center guys hadn't closed the phone properly..and now this.. Oh boy, am I gonna make a strong case!!
Sent from my iPod touch using Tapatalk
nkk71 said:
I think most of the time, that's not something fixable unless by a service center. You may wanna check this thread: http://forum.xda-developers.com/showthread.php?t=2331454
For one guy the phone "magically" just started again, but I wouldn't hold my breath.
Sorry mate.
Click to expand...
Click to collapse
Yeah, I haven't got any alarms to save me now ;'/
But mine did get bricked randomly..
Sent from my iPod touch using Tapatalk
How about I try this?
http://unlimited.io/qhsusbdload.htm
As it doesn't mention the One I'd say no
EddyOS said:
As it doesn't mention the One I'd say no
Click to expand...
Click to collapse
Oh well, I went ahead and tried it anyways, but nothing happened.. So back to my good ol Nokia for now.. Btw, does rumrunner work with hboot 1.55??
Sent from my iPod touch using Tapatalk
Not yet, no
I bet we'll be seeing a lot more of these threads now...
Okay, although I've read a lot and I've learnt quite some bit, I want to know that if it wasn't the phone that unexpectedly died, was it my mistake somewhere? So I'll start with what I did, step by step, please have a look and tell me if I did anything wrong
1. Originally on ViperOne, tampered and unlocked on hboot 1.54
2. Restored stock nandroid 4.2.2 (2.24.707.3)(India) unrooted
3. Downloaded rumrunner (the version that I previously mentioned)
4. Started the exe
5. Phone reboots 2-3 times, process completes at pouring(3)
6. Reboot to verify s-off
7. Restore ViperOne nandroid
8. Run Revone to reset tampered flag
9. Flash modified hboot to remove warning.. Succeeds, reboot to verify warning gone
10. Reboot like 5-6 times to admire at the bootloader
11. I got a call and my phone hung
12. Reset the phone by holding power+vol down
Aaand the phone never booted again..
Sent from my iPod touch using Tapatalk
crixley said:
I bet we'll be seeing a lot more of these threads now...
Click to expand...
Click to collapse
Lol yeah.. I wouldn't think of myself as a total douche though, maybe I missed something..
Sent from my iPod touch using Tapatalk