Related
Alright here's what happened. I went to root my new G1, I started to follow the steps from the Unlockr but stopped halfway through cause i thought i was going in circles I had finished at "rooted" my phone when i looked in the "about phone" i thought for sure that i hadn't. So i went and did Androids world but when i did the first step my phone got stuck. I thought it was bricked but doing some reading think its soft bricked. But i don't know what to do, i cant get to the rainbow screen or the Home+Power screen only the G1 logo. What do i do?
did you flash the the spl and radio, and flash the right one first ?
jad011 said:
did you flash the the spl and radio, and flash the right one first ?
Click to expand...
Click to collapse
I actually never got to that I don't think i ever officially rooted my phone.
Place your phone on a stack of papers and get a new one
Mjolnir106 said:
Alright here's what happened. I went to root my new G1, I started to follow the steps from the Unlockr but stopped halfway through cause i thought i was going in circles I had finished at "rooted" my phone when i looked in the "about phone" i thought for sure that i hadn't. So i went and did Androids world but when i did the first step my phone got stuck. I thought it was bricked but doing some reading think its soft bricked. But i don't know what to do, i cant get to the rainbow screen or the Home+Power screen only the G1 logo. What do i do?
Click to expand...
Click to collapse
I'm going to be real lazy and ask you to post links to the guides you used
I would google them myself , but busy and seeing as you have them in your internet history...
when is an url not an url?
when http is hteeteep
I will then have a look and see just what damage you may have done and if it can be undone
ok so i got my hands on my sisters old G1 and it was unrooted and with rc30.
so i was able to downgrade it to rc29, flash it with RA recovery 1.7.0, and i was applying the the spl next. i booted into recovery and flashed the spl, and when i rebooted the g1 i just got suck at the tmobile g1 screen, i left it there for like 10 minutes thinking its gonna do its thing but it was still stuck there.
i pulled the battery out and pressed home and the power button, and it still didnt wanna go into recovery. so i pulled the battery again. so pressed and held the camera button and power button and it booted into the g1 screen instead!
so at this point i think i bricked it since im just stuck at the g1 screen and cant do nothing from there and i wanted a 2nd opinion to confirm it, or for a possible solution.
im thinking i messed up with the spl, but the one i have DL is the same one i used with my old G1 and its still kicking some (this one has a problem with the flex ribbon cable i believe, but completely usable.)
Im pretty sure when a phone is bricked, you cant even boot your phone, so im pretty sure ur phone is not bricked.
sorry, idk how to fix this, but im sure someone does.
You have to flash a rom, of coursebit would get stuck at g1 screen bcuz it had no direction(no rom)
Sent from my HTC HD2
the situation is you can get into hboot but not recovery nor system，right?
you could flash radio/spl via fastboot ,then flash recovery, rom at last.
read this thread:http://forum.xda-developers.com/showthread.php?t=532719,try to fix it
edward0119 said:
the situation is you can get into hboot but not recovery nor system，right?
you could flash radio/spl via fastboot ,then flash recovery, rom at last.
read this thread:http://forum.xda-developers.com/showthread.php?t=532719,try to fix it
Click to expand...
Click to collapse
no i cant access recovery, or hboot.
when i hooked it up to the computer hoping that it might recognize it, nothing happened either when i tried to boot into hboot, or recovery.
so ive been doin some more digging into the internet and yep i did end up bricking it.
looks like im gonna perform some phone operation between the two g1s to have a fully working one.
so pressed and held the camera button and power button and it booted into the g1 screen instead!
you said this last day,it doesn't work now?
edward0119 said:
you said this last day,it doesn't work now?
Click to expand...
Click to collapse
no it doesnt.
i have no access to hboot, or recovery. and it doesnt get recognized by my computer if i try to have it hooked up with the usb, so i cant even use adb or nothing.
so like i said, i could pretty much confirm myself that i bricked it. so right now im like phoneless because my original g1 has an issue with it not showing nothing if the keyboard is CLOSED (yes closed, not open! lol) and it ended up closing on me when i tossed it in my bed (doh!)
damm that sucks man.. sorry for your loss lol
ldrifta said:
damm that sucks man.. sorry for your loss lol
Click to expand...
Click to collapse
haha its alright, only option right now is phone operation with the two g1s i have, but i need to buy a torx screwdriver for it since the one i got is the wrong size.
but its not such a bad thing because ive been hearing that i might end up getting a new HTC phone as a graduation present. so heres to hoping thats true! lol
I guess it is bricked,maybe it can be fixed by a serviceman
Well seeing it's screwed lol try out JTAG used it before to unbrick a phone once ^^ that should be a solution for you
xillius200 said:
Well seeing it's screwed lol try out JTAG used it before to unbrick a phone once ^^ that should be a solution for you
Click to expand...
Click to collapse
yeah i was looking into that, but idk it seemed wierd for me.
but last night i opened up the g1s and replaced the motherboards from eachother. and now i got a working g1!
Ok, so I had an HTC Salsa, and idk how but the screen somehow broke. I didnt drop it or anything but when i took the phone out of my pocket it was completely shattered. I sent it to the service center for repairs, and they sent it back to me saying they've done everything they could. The ****ty part is all the hardware is in place. They put in a new motherboard, new glass, new screen, everything, but the phone wont boot up it just keeps showing the white HTC screen. Its like a bootloop. I was hoping someone could help me, if this bootloop can be fixed or not somehow? Any answers? Please?
ok firstly welcome....
now then...you sya its stuck at htc screen, is this phone completely stock...untouched.
if it is...then you will have to get the ruu for your country and install it.
unless you have all the relevant updated software ie bootloader done then the process gets easier....
explain what u got mate
No it wasnt untouched. I unlocked bootloader, got cwm 5 from this thread's method:
http://forum.xda-developers.com/showthread.php?t=1478678
I didnt install data2sd, and I had the HTC Thing ROM, I re odexed it and was using links2sd with it. When i got my phone back my bootloader went back to the old S-ON version, lost my cwm 5 recovery and the phone doesnt boot up just stays stuck on the white HTC screen
Sccyther said:
No it wasnt untouched. I unlocked bootloader, got cwm 5 from this thread's method:
http://forum.xda-developers.com/showthread.php?t=1478678
I didnt install data2sd, and I had the HTC Thing ROM, I re odexed it and was using links2sd with it. When i got my phone back my bootloader went back to the old S-ON version, lost my cwm 5 recovery and the phone doesnt boot up just stays stuck on the white HTC screen
Click to expand...
Click to collapse
ok....
reflash the recovery from bootloader
using adb cmds plug phone into computer
>adb reboot bootloader
now reflash recvoery using the method you did.
now recovery will be installed.
>adb reboot recovery
now your back into recovery reflash the rom u want.
Now word of warning....
what you tried to do will **** it up..i know i did it too. reodexing inst the wisest of options.
u can still use links2sd on deodexed version but would you want to....you dont get as much space even with a gb partition...it doesn't fully move the apps into that storage area...
Theres a PH11IMG file too should i install that zip too? Coz i have a little problem there. My phones battery is low and it keeps showing up in the bootloader. So it wont detect the zip file and give me an option to install the zip
Sccyther said:
Theres a PH11IMG file too should i install that zip too? Coz i have a little problem there. My phones battery is low and it keeps showing up in the bootloader. So it wont detect the zip file and give me an option to install the zip
Click to expand...
Click to collapse
if your bootloaders unlocked like u say it is you won't need it...anyway the pm11img.zip is hboot not bootloader.
if u typed my cmd in then you wouldn't see that bit.
its easier using dos cmd for this...its quicker and can override what ever the phone wants to do.
charge your battery for half an hr.
min 30% is needed but 50% is recommended
Oh damn did I say unlocked? Its locked now. I had unlocked it before sending it for repairs, when it came back that pink strip that said unlocked it gone. Its locked now i guess. So I do need the PH11IMG thing but it wont prompt to install it in the hboot coz it keeps showing battery voltage too low
Sccyther said:
Oh damn did I say unlocked? Its locked now. I had unlocked it before sending it for repairs, when it came back that pink strip that said unlocked it gone. Its locked now i guess. So I do need the PH11IMG thing but it wont prompt to install it in the hboot coz it keeps showing battery voltage too low
Click to expand...
Click to collapse
ok....dont do anything........................
do u still have your unlock file u got from htcdev? if u do...rerun that program again and it will be unlocked then goto bootloader and do as instructed
and if that don't work then who ever u sent it redid the software....so then i need your software info from hboot mate
The unlock code.bin file? Yea i have it with me but i forgot what to do with that file. How do i run it again?
Sccyther said:
The unlock code.bin file? Yea i have it with me but i forgot what to do with that file. How do i run it again?
Click to expand...
Click to collapse
ok asuming the token file is in c:\android still then use this (copy & paste cmd line)
>fastboot flash unlocktoken Unlock_code.bin
that should unlock it again...
Ok thank you so much. Im gonna go get a battery from my friend as mine is completely drained for this job. Lets hope this works.
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
I like my Sprint M8 and I've avoided messing with it because I'd hate if it got bricked. It got bricked. In my pocket. Somehow. Seriously, I was using it like normal, put it in my pocket for maybe a half hour, then took it back out without having even moved from my seat and it's off. I assumed it somehow died but when I plugged it in it became obvious that wasn't the issue. It doesn't really seem to care what I do with the buttons, but eventually it'll end up in fastboot mode and nothing else. Any of the options just result in a black screen. Sometimes I get a charging screen though. HELP.
Bump
Cwazywazy said:
I like my Sprint M8 and I've avoided messing with it because I'd hate if it got bricked. It got bricked. In my pocket. Somehow. Seriously, I was using it like normal, put it in my pocket for maybe a half hour, then took it back out without having even moved from my seat and it's off. I assumed it somehow died but when I plugged it in it became obvious that wasn't the issue. It doesn't really seem to care what I do with the buttons, but eventually it'll end up in fastboot mode and nothing else. Any of the options just result in a black screen. Sometimes I get a charging screen though. HELP.
Click to expand...
Click to collapse
Destiny oi? maybe you should have really messed with it lol.
But were you able to enter recovery? You could try factory reset from there
jazzdglass said:
Destiny oi? maybe you should have really messed with it lol.
But were you able to enter recovery? You could try factory reset from there
Click to expand...
Click to collapse
Only goes into fastboot. If I try to hit recovery or factory reset, or basically anything that goes outside of fastboot I just get a black screen. I just bought a new phone (Pixel) so it's not a big deal, but I still really like my M8 and if I can fix it I will.
I have run into that a few times with mine and Was ALWAYS able to fix it .
Its just being stubborn. If you have Fastboot you can FIX IT
Is it rooted and bootloader unlocked
Cwazywazy said:
Only goes into fastboot. If I try to hit recovery or factory reset, or basically anything that goes outside of fastboot I just get a black screen. I just bought a new phone (Pixel) so it's not a big deal, but I still really like my M8 and if I can fix it I will.
Click to expand...
Click to collapse
Two case ..
1. SOFTWARE :
First try to RUU . (It will solve nearly all software related issue) . Backup everything as it will wipe all .
If going to flash marshmallow then firstly flash marshmallow firmware and theb RUU.
If problem still there then may b (not sure though) its..(2)
2.HARDWARE :
I have nearly same problem . The device stay at fastboot but can't go to any other option i.e recovery . (After flashing ruu ) , stay ON when only charger connected etc ..
Changed battery and all working fine now.
Your seems to be only software related .. try ruu first
Hit THANKS if somebody help you
sonnu0100 said:
Two case ..
1. SOFTWARE :
First try to RUU . (It will solve nearly all software related issue) . Backup everything as it will wipe all .
If going to flash marshmallow then firstly flash marshmallow firmware and theb RUU.
If problem still there then may b (not sure though) its..(2)
2.HARDWARE :
I have nearly same problem . The device stay at fastboot but can't go to any other option i.e recovery . (After flashing ruu ) , stay ON when only charger connected etc ..
Changed battery and all working fine now.
Your seems to be only software related .. try ruu first
Hit THANKS if somebody help you
Click to expand...
Click to collapse
It's totally stock and unrooted. I tried RUU about a thousand times, every time it gets to the rebooting into fastboot or whatever stage where it times out and fails because the phone takes minutes to turn back on and go into fastboot no matter what I do with the buttons, even if I don't touch them at all. My battery was fine, I think. Still lasted the whole day just fine. Stays on when I disconnect it.