Database Develop

HELP: G1 not powering up

Hi,
i just reflashed my mobile this morning(GMT+0800, CST)
first, i flashed current radio
then, danger spl.
now, cannot power up. removed battery and tried several times without any respond.
so, what can i do?

what can you do?
get a new g1. after you flash danger, ur supposed to press home + back, not using the trackball. then your suppose to reflash your rom. if you cant turn it on, your bricked.
tell the rep it shut off while updating to cupcake and wont turn on. good luck
the members of XDA have no sympathy for you.

Lets verify it's a true brick before you give up on it.
1) did you check to see if your G1 is a PVT?
2) when you say "won't turn on" what exactly are you seeing? G1 screen? completely dead?
3) does holding camera and power to turn it on do anything different?
4) does holding home and power to turn it on do anything different?
Also, Don't mention anything about cupcake. Just say "the phone wanted to apply an update and this is what is does afterwards". Play dumb, you don't know anything about cupcake, donut, or any other pastry.

same problem
my phone is a PVT
did camera and power and it is stuck @ the screen
*my phone did this while trying to do a hard reset*
*I was unsatisfied with my cm 4.0.4. compatiable theme made by ENOCH v1.4 i believe*
*i did the reboot and pressed alt+w and it still took me to the enoch screen*
help please

my phone is a PVT -- GOOD
did camera and power and it is stuck @ the screen -- WHAT SCREEN, DETAILS PLEASE
*my phone did this while trying to do a hard reset* -- OK
*I was unsatisfied with my cm 4.0.4. compatiable theme made by ENOCH v1.4 i believe* -- OK
*i did the reboot and pressed alt+w and it still took me to the enoch screen* IS THIS REBOOT USING HOME+POWER?
help please

*I was unsatisfied with my cm 4.0.4. compatiable theme made by ENOCH v1.4 i believe*
Click to expand...
Click to collapse
OH serious business there, i heard that this theme maker added special code that if badmouth his theme it bricks your phone, lol

*it goes to the rainbow screen*
*quickly flashes to "loaiding.....no image file*
*then It gets stuck at the rainbow screen*

Fingerlickin said:
my phone is a PVT -- GOOD
did camera and power and it is stuck @ the screen -- WHAT SCREEN, DETAILS PLEASE---answered above
*i did the reboot and pressed alt+w and it still took me to the enoch screen* IS THIS REBOOT USING HOME+POWER?--------yes
help please[/QUOTE
Ive been on this site for hours trying to find answers to no avail
list of things ive done
*tried to update to new cm but download was unsuccessful, one remedy was to do a factory reset and i am @ where I am now*
*reformatted sd card*
*2 reflash to stock methods*
*i get to g1 screen and then it shows the ENOCH screen and stays there*
Click to expand...
Click to collapse

stefan.buddle said:
OH serious business there, i heard that this theme maker added special code that if badmouth his theme it bricks your phone, lol
Click to expand...
Click to collapse
lol well sheesh it shouldnt be so laggy!

If you see the bootloader screen then you still good, you ain't bricked.

supremeteam256 said:
If you see the bootloader screen then you still good, you ain't bricked.
Click to expand...
Click to collapse
what does it mean when I'm stuck @ the enoch screen/black screen/ can get my phone to fully function?

Can you boot into recovery by holding home and press power?

Fixed
I figured it out and just reflashed the rc29 update. I had to go through 3 sd cards but it worked out. Internet was also out for a majority of the day so it stopped me from beable to respond. Thanks for the assistance thought folks!

hiphopsg1holder said:
I figured it out and just reflashed the rc29 update. I had to go through 3 sd cards but it worked out. Internet was also out for a majority of the day so it stopped me from beable to respond. Thanks for the assistance thought folks!
Click to expand...
Click to collapse
Well you didn't have to go back to RC29. All you had to do is load another rom. When you flash the "danger" spl it erases your current rom, that's why everywhere it says you must flash another rom right after it. I guess people don't read anymore.

supremeteam256 said:
Well you didn't have to go back to RC29. All you had to do is load another rom. When you flash the "danger" spl it erases your current rom, that's why everywhere it says you must flash another rom right after it. I guess people don't read anymore.
Click to expand...
Click to collapse
The goal was to get it back to factory so I can return it....Sorry to upset you sir with my lack of reading skills =/

Is my G1 bricked?

Hi all,
I was trying to update to CM 4.2.3, so first I wiped, then installed the regular ole android 1.6 image from Google, it goes to reboot and all seems fine. However, in the boot process it gets past the "T-Mobile G1" screen and then it just stayed at the flashing Android screen for several hours, I finally gave up on it and pulled the battery. Now if I boot normally it will go to G1 screen then to flashing android then NOTHING, the screen is still on but its all black. If I try booting with power+home I get a picture of an exclamation point in a triangle and a phone laying next to it. If I boot with power+camera it says
"DREA100 PVT 32B
HBOOT-0.95.3000
CPLD-4
RADIO-2.22.19.26I
Oct 20 2008
Serial0"
and there's 3 androids at the bottom on skateboard.
I don't what to do, except call Tmo and hope theyll send me a new one. I'm without phone so feeling particularly helpless
EDIT: I did alt-w at the screen with the exclamation point and the phone, it did something, now I'm running 1.6. PHEW, that was a close one

Note, you are never bricked if you can get to the fastboot or recovery screen.

evilkorn said:
Note, you are never bricked if you can get to the fastboot or recovery screen.
Click to expand...
Click to collapse
good to know, thx
i kept searching around for what exactly a bricked phone looks like, but now i know

Take a picture of your initial G1 screen and you're all set

u may have lost root , jus re downgrade then updgrade back

maek_it_happen said:
u may have lost root , jus re downgrade then updgrade back
Click to expand...
Click to collapse
i did, but i got it back. now running cm 4.2.3 and loving it!

[Q] HTC White Screen - Bricked?

I have searched here and Google but can't seem to find the exact problem that I am having. Most similar issues are with different phones and I haven't found any solutions for the HTC Hero. I have been rooted for a couple of months and using CM6 (stable and nightlys) without any problems whatsoever. I have (had?) Clockwork recovery. My phone was running perfectly this morning and the battery was pretty low (down to 10%) so I pulled it and put in a fully charged battery. Now my phone won't boot past the HTC white screen. I can boot into HBoot ONLY (three skateboarding androids) and the screen shows:
HERC XC SHIP S-ON
HBOOT-1.47.0000 (HERO20000)
TOUCH PANEL-SYN0104
RADIO-2.42.01.04.27
Mar 1 2010, 16:02:39
I have tried all the options on HBOOT and can get into FASTBOOT but am unable to reset device, go into recovery, etc. It just goes back to the white HTC Screen after choosing one of these options and never boots up. I've tried with the SD card in and with it out. I even tried to RUU with the .5 Sprint official release but when I run it, the program said my phone was not found and told me to make sure it was plugged into the computer which of course it was. I also tried to run the RUU in FASTBOOT USB mode but still receive the same error.
When I run adb shell on my PC it says the device was not found. When I'm stuck on the white HTC screen if the phone is plugged in to the computer and I unplug the usb from the phone it vibrates 5 times quickly and the screen goes off, but the green notification light is blinking. From this state I am unable to power up the phone at all without a battery pull.
I just don't understand how my phone can go from being PERFECT to FUBAR when the only thing I did was replace the battery. I'm hoping someone can help me. I am eligible for an upgrade but really don't want to spend the $$ right now for an EVO or Epic when my area will never see 4g and the extra $10 is ridiculous.
My setup prior to this morning when I pulled the battery:
Clockworkmod Recovery
CM 6 nightly (Full-73)
BFS #11 kernel
FireRat custom data partitions
And I was rooted with Universal Androot

Have you tried booting into recovery by holding Home and pressing Power? From there you could try wiping everything then reflashing the ROM of your choice.
Have you tried putting the original battery back in and just recharging it fully, then trying to boot?

chromiumleaf said:
Have you tried booting into recovery by holding Home and pressing Power? From there you could try wiping everything then reflashing the ROM of your choice.
Have you tried putting the original battery back in and just recharging it fully, then trying to boot?
Click to expand...
Click to collapse
When I hold home and press power, I just get the white HTC screen of death. When I hold volume down and press power, I get the HBOOT screen and when I try to boot into recovery from that screen it again gives me the HTC screen of death. There is no way past the HTC Screen other than HBOOT and Fastboot. I also charged the phone with the original battery as you suggested and it still did not boot up beyond the HTC screen.
This afternoon I was in the FastBoot screen and plugged my phone into the USB that was connected to my computer. It changed to FastBootUSB and I was able to run the RUU. The program said that the ROM was successfully updated but I sat there for an hour with another white HTC screen before I unplugged the USB and then the phone shut off and I got the 5 quick vibrates. I really think it's toast. RIP, it was such a good phone!

debh945 said:
When I hold home and press power, I just get the white HTC screen of death. When I hold volume down and press power, I get the HBOOT screen and when I try to boot into recovery from that screen it again gives me the HTC screen of death. There is no way past the HTC Screen other than HBOOT and Fastboot. I also charged the phone with the original battery as you suggested and it still did not boot up beyond the HTC screen.
This afternoon I was in the FastBoot screen and plugged my phone into the USB that was connected to my computer. It changed to FastBootUSB and I was able to run the RUU. The program said that the ROM was successfully updated but I sat there for an hour with another white HTC screen before I unplugged the USB and then the phone shut off and I got the 5 quick vibrates. I really think it's toast. RIP, it was such a good phone!
Click to expand...
Click to collapse
Well you'll be the first to kill it this way but I'm sorry to here that and my touch screen is almost toast so ima start a first to
Sent from my HERO200 using XDA App

rulyskull said:
Well you'll be the first to kill it this way but I'm sorry to here that and my touch screen is almost toast so ima start a first to
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Dang, that sucks. I was torn between getting an upgrade or buying a used Hero on Ebay until I find a phone I want. Turns out my phone was only 11 months and 10 days old so I'm still under warranty. My new Hero will be here Tuesday. I'm hoping it doesn't come with the .7 update but if so, I'm hoping I can RUU back to the .5 and re-root. Anyone know if this is possible? Thanks.

debh945 said:
Dang, that sucks. I was torn between getting an upgrade or buying a used Hero on Ebay until I find a phone I want. Turns out my phone was only 11 months and 10 days old so I'm still under warranty. My new Hero will be here Tuesday. I'm hoping it doesn't come with the .7 update but if so, I'm hoping I can RUU back to the .5 and re-root. Anyone know if this is possible? Thanks.
Click to expand...
Click to collapse
Try the one click root(forget What section in here) but ima wait to get the epic or something better
Sent from my HERO200 using XDA App

Have you tried ruu'ing it?
Sent from my HERO200 using XDA App

Vandelay007 said:
Have you tried ruu'ing it?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Yep, I was finally able to RUU while the phone was in FASTBOOTUSB mode and the program on the PC said the ROM was updated successfully but it still never got past the HTC white screen. When I boot into HBoot by holding the volume down/power button the screen flashes a bunch of things so fast I can't read them but it seems like it says something about HCERMG Image Not Found.
The Sprint tech(?) hooked it up and tried to diagnose, install the software but couldn't either. Anyway, since it is under warranty I get a new Hero on Tuesday. I am just baffled at how this happened when all I did was change the battery. You don't realize how much you love something until it's gone. I'm currently using my old Instinct and I find myself constantly turning the screen sideways and wondering why the display won't turn.

Same issue here, (2nd time actually). Last time I was able to put the HERCIMG.zip on the root of my SD Card and then load it with HBOOT, and then I was back to stock and all was good. However since then my HBOOT was updated to 1.47 and now the HERCIMG.zip doesn't work, it says "Main Version is older!" Update Fail!
I haven't figured anything else out yet. Is there an updated HERCIMG.zip for 1.47?

SportsPT said:
Same issue here, (2nd time actually). Last time I was able to put the HERCIMG.zip on the root of my SD Card and then load it with HBOOT, and then I was back to stock and all was good. However since then my HBOOT was updated to 1.47 and now the HERCIMG.zip doesn't work, it says "Main Version is older!" Update Fail!
I haven't figured anything else out yet. Is there an updated HERCIMG.zip for 1.47?
Click to expand...
Click to collapse
Do you mind telling me what you did (twice lol) that put your phone in this unusable state? Like I said I'm not sure how this happened and don't want to repeat it with a replacement phone!

Ok, I put the HERCIMG.zip on the root of my SD Card (found it through Google and had updated 1.47 HBOOT). I booted up holding the volume down and power and the blue progress bar filled up on the right side and when it was finished it went back to the HBOOT screen. I rebooted the system and still have the white screen of death. I'm convinced there's really nothing else I can do to get it running again and must painfully wait until my new phone comes in on Tuesday.

Couldn't tell you how it happened, may have to do with the battery completely dying, but not sure. I tried what you did but got the same results. I think what we need as an updated HERCIMG.zip that works with HBOOT 1.47

While in fastboot, did you try
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash data data.img

unCoRrUpTeD said:
While in fastboot, did you try
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash data data.img
Click to expand...
Click to collapse
I tried all kinds of fastboot commands in FASTBOOTUSB mode through adb but always received the error "remote not allowed" or something to that effect.

debh945 said:
I tried all kinds of fastboot commands in FASTBOOTUSB mode through adb but always received the error "remote not allowed" or something to that effect.
Click to expand...
Click to collapse
What about when you power on the phone normally. You should be able to get into adb shell when it is booting up.
I am going to try fastboot flash boot.img right now on mine and see if I can't get something.
Edit:Haven't tried. Working on a multiboot and now I only have one more obstacle.

unCoRrUpTeD said:
What about when you power on the phone normally. You should be able to get into adb shell when it is booting up.
I am going to try fastboot flash boot.img right now on mine and see if I can't get something.
Edit:Haven't tried. Working on a multiboot and now I only have one more obstacle.
Click to expand...
Click to collapse
If I was not in the FastbootUSB mode, there was only the white HTC screen and adb showed "no devices". I appreciate your help but I can't troubleshoot any longer as I had to turn my phone in to get the new one via warranty replacement. Your efforts might help someone else though with the same problem.
ps, I've been following the multiboot thread very closely and can't wait until this becomes a reality!! That will be so awesome!

debh945 said:
If I was not in the FastbootUSB mode, there was only the white HTC screen and adb showed "no devices". I appreciate your help but I can't troubleshoot any longer as I had to turn my phone in to get the new one via warranty replacement. Your efforts might help someone else though with the same problem.
ps, I've been following the multiboot thread very closely and can't wait until this becomes a reality!! That will be so awesome!
Click to expand...
Click to collapse
Did you pay the extra for warranty or are all heros on warranty for 12 months? Who did you sent the phone to or did you just go to the sprint store?

obsanity said:
Did you pay the extra for warranty or are all heros on warranty for 12 months? Who did you sent the phone to or did you just go to the sprint store?
Click to expand...
Click to collapse
All Heros have a 12 month warranty, I didn't pay extra. I first called Sprint Customer service and since it wouldn't boot for them to troubleshoot on the phone she gave me an Eticket number and the location of the nearest Sprint store with a repair center. I took it in and the tech (?) hooked it up to his computer and could not fix it either so he said he would order me another and it would be here on Tuesday. This was Saturday evening. I received a call today (Monday) from the Sprint Store that my replacement phone was in. Picked it up and rooted it in 5 minutes with Universal Androot, installed Clockwork Mod Recovery, Nandroid restored a backup from the old phone's SD card and I was back in business in 1/2 an hour! Probably TMI, I realize you only asked how I got a new phone but I'm thrilled to have my Froyo back!

Awesome! Makes me feel better trying different ROMs

Funny thing I found this thread, this exact same thing happened to me today.. Hero is completely done.. Getting a replacement tomorrow... I was running firerats also which I can't blame but I'm not running firerats on my new device... Since I installed firerats I've lost 2 8gb sd cards and a phone...
Weird thing is, I had applied the unrevoked-forever and eng spl mod/hack, now when I boot into bootloader it says s-on like what the hell happened? How did I lose s-off and root all together after restarting my phone.

[Q][Solved] Screen not turning on. Is it bricked?

I installed Evervolv-Perdo-2.2.0a2 ROM on my nexus one (before that I had earlier versions), but I had a red-glowing trackball issue which was worrying me so I decided to go back to stock android to see if it fixes my problem. The first thing I did was to uninstall blackrose, so the original bootloader could be restored. After I did that, I copied PASSIMG.zip file onto sdcard, rebooted and seconds after it stated to mess with my phone, the screen went off. I have no idea what happened, but I expect the worst
Now the screen won't turn on. Orange LED lights up when phone is connected to the charger, it vibrates when I hold down the power button, but the screen is always black, no sign of life. Can I bring my awesome phone back to life? Or is it dead? Please help me.

s_t_a_n said:
I installed Evervolv-Perdo-2.2.0a2 ROM on my nexus one (before that I had earlier versions), but I had a red-glowing trackball issue which was worrying me so I decided to go back to stock android to see if it fixes my problem. The first thing I did was to uninstall blackrose, so the original bootloader could be restored. After I did that, I copied PASSIMG.zip file onto sdcard, rebooted and seconds after it stated to mess with my phone, the screen went off. I have no idea what happened, but I expect the worst
Now the screen won't turn on. Orange LED lights up when phone is connected to the charger, it vibrates when I hold down the power button, but the screen is always black, no sign of life. Can I bring my awesome phone back to life? Or is it dead? Please help me.
Click to expand...
Click to collapse
You just flashed an AMOLED version of the microp on you SLCD... Well Done... Try a 2.3.X passimg and see if it works...

race55 said:
You just flashed an AMOLED version of the microp on you SLCD... Well Done... Try a 2.3.X passimg and see if it works...
Click to expand...
Click to collapse
Thank you for your answer.
No, it does not work. It seems like the android does boot up however because trackball is glowing red, but it stops when I hit the power button (lock) and glows again when I push the power button one more time (unlock).

s_t_a_n said:
Thank you for your answer.
No, it does not work. It seems like the android does boot up however because trackball is glowing red, but it stops when I hit the power button (lock) and glows again when I push the power button one more time (unlock).
Click to expand...
Click to collapse
I just googled, and the only solution is to send it back to google/htc. Or just buy a new one! You permanently bricked it. This is from the wiki:
There are several thread, especially one that contains an instruction on howto downgrade the HBOOT version.
Many users are not aware of the difference between an AMOLED and a SLCD Nexus device. The EPF30 ROM, is a special ROM, containing an image that WILL BRICK Nexus One devices that are of the SLCD generation!
The MICROP will be downgraded from 0c15 to 0b15, resulting in an irrecoverable flash, that will let the trackball light up in red, the only solution is to send it back to factory and let them fix it.
A lot of problems people are running into, is when they follow a downgrade instruction made by Nexus One owners, that have an AMOLED device and upgraded to boot version 0.35 by accident.

I have access to fastboot. Won't it help?

s_t_a_n said:
I have access to fastboot. Won't it help?
Click to expand...
Click to collapse
Did you not read my post? It is unrepairable. You downgraded the display driver. There is no update anywhere. You cannot recover it. IT IS BROKEN FOREVER! I'm sorry but there is no recovery from this.

I was able to flash PASSIMG_Passion_Vodafone_Generic_2.15.151.5_R_FRF91_release_signed via fastboot so no, it is not broken forever. The only problem I have now is screen not working in the bootloader/recovery and while loading the system, but after android is loaded it works just like it used to. Anyone knows how to fix this?

If you check the PASSIMG that got you screwed (I guess you didn't read the red letters of warning in Wiki), and find what image is the microp that got downgraded, you might be able to ask a fellow SLCD N1 owner to dump the image for you (assuming that microp is either a partition or contained on partition).
If microp is contained in HBOOT - just flash a newer HBOOT. Look for Gingerbread PASSIMG.

Flashing newer HBOOT worked indeed. Thank you.

[Q] Bricked m7u

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