When I try to start my G1 the display just stays black, not the "stuck on g1 screen" problem, it stays black and it doesn't vibrate like it usually does when starting it.
What I did was rooting, changing recovery to amonra 1.7.0 and installing the spl_1_33_2003.zip spl update, the update was successfully as it restarted normally and started to boot. Then I wanted to get to the bootloader mode so I pulled the battery. Since then the only Reactions are the red LED when charging and the Blue LED when getting in this JTAG-Mode or whatever.
I couldn't find any thread about this problem and I already did this whole procedure on another G1 without any problems.
I really hope, that you can help me
you should have waited for it to boot before pulling the battery
it is a 2 stage install, first is preps , then it reboots and competes the flash
you have a brick now
Dexter245 said:
When I try to start my G1 the display just stays black, not the "stuck on g1 screen" problem, it stays black and it doesn't vibrate like it usually does when starting it.
What I did was rooting, changing recovery to amonra 1.7.0 and installing the spl_1_33_2003.zip spl update, the update was successfully as it restarted normally and started to boot. Then I wanted to get to the bootloader mode so I pulled the battery. Since then the only Reactions are the red LED when charging and the Blue LED when getting in this JTAG-Mode or whatever.
I couldn't find any thread about this problem and I already did this whole procedure on another G1 without any problems.
I really hope, that you can help me
Click to expand...
Click to collapse
You should not have pull the battery, that is a no no especially during the install.
Are you able to even go into any mode? IE: camera+power, etc...
Nope, no Mode works, tried every combination, it just wont start-.-
Dexter245 said:
Nope, no Mode works, tried every combination, it just wont start-.-
Click to expand...
Click to collapse
U definitely have a bricked G1.
Well if u can't get into recovery nor bootloader its a sure sign of a brick...
How charged was ur battery? My battery died one time and it wouldn't load up as well. It went from a full charge to nothing.. just a thought....
But try charging it and try to get back Into bootloader.. but don't rule anything out.
Will think more but keep us posted
Sent from my T-Mobile myTouch 3G Slide using XDA App
twiztidnutzzzzz said:
Well if u can't get into recovery nor bootloader its a sure sign of a brick...
How charged was ur battery? My battery died one time and it wouldn't load up as well. It went from a full charge to nothing.. just a thought....
But try charging it and try to get back Into bootloader.. but don't rule anything out.
Will think more but keep us posted
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Oh! Yea! Happens to mine last weekend. But mine was doing the splash screen loops.
Battery was about at 50%. Tried with another battery and everything's the same. Looks like I really bricked it-.-
Anyway, thanks for the help
Future reference when doing serious mods such as updating spl, radio always make sure you have a full charge as these things can drain ur battery pretty quick. And the last thing u want is for ur battery to die in the middle.....
Have u tried reformatting ur sdcard. ?
Sent from my T-Mobile myTouch 3G Slide using XDA App
Why should I reformat it, it makes no difference at all if an sdcard is inside or not, and the sdcard is working without any problems
Weirld **** happens man, , just a simple question. Never hurts to explore all options.. I'm done good luck
Sent from my T-Mobile myTouch 3G Slide using XDA App
Dexter245 said:
Why should I reformat it, it makes no difference at all if an sdcard is inside or not, and the sdcard is working without any problems
Click to expand...
Click to collapse
It does, sometime SD Card get corrupted. And it will prevent your phone from booting up correctly especially when you SD to install your apps etc...
Related
Hi. Ok, first of all I have done some research on the forum, but I haven't really found any answer for my problem.
I have a Htc touch diamond. And I installed a rom from the forum, i beleive it was the "shine"-rom. However now i gets weird....
The day after, everything was normal, and then all of a sudden my backlight gets really dim. Ok, could be a small bug i thought.
A few hours later it got darker and it was hard to see what was on the display.
And later on the evening it got almost all black. I couldn't quite tell what was what on the display.
The next day, and still, its totally dead. There is no light in the "ring" when i plug in the charger, and i cant get it to show any life.
I have tried everything, left it in the charger for a whole day, swapped battery, reset, hard reset, super hard reset. left it without battery for a day. Nothing.
Help me out. Any ideas?
Ps. There is no warranty on the phone.
Thanks!!
Wow... have not seen this before...
Even now, are you unable to even switch on your diamond? If you can't, don't see any way to revive it. If you can, try to flash another ROM and see if it improves...
How?
How can I flash it again, if I cant even turn it on? hmmm....
Help
Nothing? No idea?
I opened it up, but that didn't shed any major light on the situation....
//
Skeptisk said:
How can I flash it again, if I cant even turn it on? hmmm....
Click to expand...
Click to collapse
Can you get it into bootloader? {Hold Vol. down button while pressing power}
If it will go into bootloader, you can flash from there
Humblehippie said:
Can you get it into bootloader? {Hold Vol. down button while pressing power}
If it will go into bootloader, you can flash from there
Click to expand...
Click to collapse
Nope. He can't even get it to turn on. Don't think it'll be able to boot into bootloader...
otacon said:
Nope. He can't even get it to turn on. Don't think it'll be able to boot into bootloader...
Click to expand...
Click to collapse
It just seems odd that bootloader won't even load. If it was something that damaged the OS then the BL should at least fire up. But, I just re-read everything again & see that there is no mention of Hard-SPL, so maybe it damaged the Boot sector as well.
If he didn't Hard_SPL then: This is a great example as to why you should always Hard-SPL before flashing anything.
If he did Hard_SPL: Then this is one for the medical journals {a disease that no-one's heard of & it's a killer}
Strange
Hi again.
I did actually Hard-Spl. And i have tried different ROM's earlier and I never had any problems.
I dont have a clue what to do, and without any warranty im basicly screwed.
I was thinkin, maybe I could get som spare part? Seeing how the "ring" doesn't even light up when I plug in the charger??
//
When my "ring" didn't light up I had to send the phone back to HTC and they changed the motherboard. Phone wasn't charging or turning on at all.
I was running one of the ENERGY ROMs on my TP2, so it's got a different SPL and all that. I then put it in the box for about 5 weeks. I took it out two days ago to install XDANDROID. I used XDANDROID for about an hour, until the TP2 started randomly shutting itsself off. I've tried flashing NRGZ28's ULTRA LITE ROM and the official T-Mobile USA 6.5 ROM for the TP2. It won't go past the boot loader a majority of the time. When it does, it goes on to act like it's flashing the RHODIMG.nbh on my MicroSD but almost instantly after it starts, it shuts off again. It doesn't always try to flash the .nbh, but when it does, it never finishes. It's the same story with a hard reset. I can't ever get it to turn on, and the only way it does turn on is to do a battery pull. If I'm lucky, it'll stay on for about 60 seconds and then shut off again. I'm really clueless as to what to do here and I'm hoping someone can help me.
The Bootloader reads as folows:
RUUNBH
RHOD210 32M SS-BC
SPL-0.85.OilNex
MicroP(LED) 0x0A
MicroP(KEY) 0x04
TURBO HW/TURBO SW
TP MFG DATA
[unreadable]
812,19...
217.855 Calibrated
The reason 1.5 of the lines is unreadable is because of the message over it: "Upgrade ROM code error. please try again."
http[colonslashslash]farm3[/url][dot]static[dot]flickr[dot]com/2726/4386331314_8036d882a6_o.jpg
try flashing hard spl 1.01 it looks like you got an old version of the spl. read the sticky on flashing for newbies i belive it tells you how to do the hard spl if you are having difficulty by usb connection other than that i wouldnt know what to tell you i nver had that problem only bad flashes but those could be solved by reflashing another ROM
Sorry, i should have explained that better. I can't connect to the PC. It won't stay in bootloader mode so I can't flash it that way either. From what i understand, the only way i can flash anything to it right now is to get the xxxx.nbh file, rename it to RHODIMG.nbh and place it on the root of my SD. When I do that, though, it won't finish the flash. It just keeps going in a loop. about every 5 minutes it randomly turns on and tries to flash the RHODIMG.nbh if present. If it's not present, it just flashes the boot loader for >10 seconds and shuts off again.
Also, I'm not sure if this makes any difference, but I've had TWO computers recognize it as a new device, "Qualcomm CDMA Technologies MSM."
Make sure the battery has a good charge, nothing else springs to mind
PS. the qualcomm thing is what appears when it's flashing via USB
also maybe try formatting your SD card and put the stock ROM back on there, or try diff card
chasejones8 said:
Sorry, i should have explained that better. I can't connect to the PC. It won't stay in bootloader mode so I can't flash it that way either. From what i understand, the only way i can flash anything to it right now is to get the xxxx.nbh file, rename it to RHODIMG.nbh and place it on the root of my SD. When I do that, though, it won't finish the flash. It just keeps going in a loop. about every 5 minutes it randomly turns on and tries to flash the RHODIMG.nbh if present. If it's not present, it just flashes the boot loader for >10 seconds and shuts off again.
Also, I'm not sure if this makes any difference, but I've had TWO computers recognize it as a new device, "Qualcomm CDMA Technologies MSM."
Click to expand...
Click to collapse
it sounds like you dont have your sd card formatted make sure its format to FAT32 go to your computer inserd sd card & reformatted (make sure its a micro sd & that its less than 2g) then transfer the ROM to the card already renamed to RHODIMG then inserd ur card on your phone & flash it. it should work. let us know what happens
MadBeef said:
Make sure the battery has a good charge, nothing else springs to mind
Click to expand...
Click to collapse
I wish I could. I have no means of checking the battery status. I've had it plugged in pretty much constantly for about the last two days.
MadBeef said:
PS. the qualcomm thing is what appears when it's flashing via USB
Click to expand...
Click to collapse
I figured that's what that was, I was just a little shocked that it said CDMA.
And I tried wiping the card and reflashing, but it did exactly the same thing.
See at the top of your bootloader readout, where it says RUUNBH? That means the RUU flag is set, and that needs to be unset before you can do other things. What you need to do is establish a connection with your device via MTTY. Follow the instructions here about how to do that. Once you get an MTTY connection established with the device (it may take awhile since MTTY is quirky sometimes), type
Code:
Set 16 0
You may need to manually soft reset afterward, but otherwise you should be in the clear
The TMO Stock ROMs can install via PC even if your phone has a faulty USB connection. The stock ROM installer will keep restarting the phone's USB connection automatically as needed if your phone can't appropriately flash in one straight attempt. You can get the newest stock ROM here. And definitely install HardSPL again after getting the phone up and running on the stock ROM.
You might also try MTTY.exe. When connected, run the command 'set 16 0' then 'task 8' then 'task 0'. If your phone doesn't automatically soft reset, then manually soft reset with the stylus.
will MTTY.exe work via parallels on a Mac? I haven't tried it yet, but I have limited access to a PC. also, I tried doing the HardSPL and the TMO rom via PC, but the phone just does the same thing. It will connect, but then the RUU tries to check the phone settings and the phone shuts off. this is the problem i am having. i just cant get it to say on long enough to do anything. I'll try the MTTY.exe through parallels and if it won't respond, I'll have to wait to try it on a PC. I'll let you know how that goes.
MTTY is quirky enough that it probably won't work through parallels, though there's no reason you shouldn't at least try and see if it works. You'll probably have to wait until you can get access to that PC. Best of luck
DaveTheTytnIIGuy said:
MTTY is quirky enough that it probably won't work through parallels, though there's no reason you shouldn't at least try and see if it works. You'll probably have to wait until you can get access to that PC. Best of luck
Click to expand...
Click to collapse
Thanks. I'll have to wait till i get back to the phone but i will let you know how it turns out.
also, in reading your sig, i see that i was using the same SPL that you are. have you had any problems with it?
I was also using the ENERGY LEO ROM [i now see that you are using it too.], which apparently was defective because the next day, the chef posted a new one because of "sleep of death." I read through the thread and didn't see anyone with the issues that i was having.
chasejones8 said:
Thanks. I'll have to wait till i get back to the phone but i will let you know how it turns out.
also, in reading your sig, i see that i was using the same SPL that you are. have you had any problems with it?
I was also using the ENERGY LEO ROM [i now see that you are using it too.], which apparently was defective because the next day, the chef posted a new one because of "sleep of death." I read through the thread and didn't see anyone with the issues that i was having.
Click to expand...
Click to collapse
I haven't had any problems with this SPL, but then again, this is the only end-user version of HardSPL for GSM devices that's been made available. The SPL isn't even your problem, the only problem is that a bootloader flag is set which shouldn't be.
As for the EnergyROM sleep of death problem, that's not what you're suffering from. The sleep of death problem is when your device won't resume after being put into standby, meaning one must soft-reset their Rhodium and lose any unsaved data in open programs. It's a somewhat common problem among many HTC devices, from the old ones like the Kaiser to the newer ones like the Rhodium (though I don't think any Android device has this problem).
jdep1 said:
try flashing hard spl 1.01 it looks like you got an old version of the spl.
Click to expand...
Click to collapse
Eh ? Sorry, but I think you're confused. He's running 0.85 HardSPL, which is the one and only version for GSM Rhodiums.
I got to a PC and tried MTTY.exe
I can't seem to get it to connect. It just says "USB port can not open."
Any suggestions?
EDIT: I can get it to connect to a different version of MTTY.exe for a short time, but I can't type anything. All I get is a blinking cursor.
chasejones8 said:
I was running one of the ENERGY ROMs on my TP2, so it's got a different SPL and all that. I then put it in the box for about 5 weeks. I took it out two days ago to install XDANDROID. I used XDANDROID for about an hour, until the TP2 started randomly shutting itsself off. I've tried flashing NRGZ28's ULTRA LITE ROM and the official T-Mobile USA 6.5 ROM for the TP2. It won't go past the boot loader a majority of the time. When it does, it goes on to act like it's flashing the RHODIMG.nbh on my MicroSD but almost instantly after it starts, it shuts off again. It doesn't always try to flash the .nbh, but when it does, it never finishes. It's the same story with a hard reset. I can't ever get it to turn on, and the only way it does turn on is to do a battery pull. If I'm lucky, it'll stay on for about 60 seconds and then shut off again. I'm really clueless as to what to do here and I'm hoping someone can help me.
The Bootloader reads as folows:
RUUNBH
RHOD210 32M SS-BC
SPL-0.85.OilNex
MicroP(LED) 0x0A
MicroP(KEY) 0x04
TURBO HW/TURBO SW
TP MFG DATA
[unreadable]
812,19...
217.855 Calibrated
The reason 1.5 of the lines is unreadable is because of the message over it: "Upgrade ROM code error. please try again."
http[colonslashslash]farm3[/url][dot]static[dot]flickr[dot]com/2726/4386331314_8036d882a6_o.jpg
Click to expand...
Click to collapse
I had this EXACT same problem a week ago. I fell asleep in the middle of flashing, the phone died when it finished. I woke up, turned on the phone, ENERGY leo was trying to run its install but kept dying. Smart me, I tried to reflash (by holding the vol down button and turning it on- not through usb) and it kept dying in the middle of trying to flash.
The problem is the battery. It can't charge when it's flashing and it can't hold a charge long enough to get past the flash.
I swapped batteries with my friend, restarted the flash and it worked fine.
I let my battery charge in my friends Sprint Hero
and voila, everything went on happily ever after.
tl;dr find a way to use a charged battery while flashing.
your phone's not bricked.
bfgarzilla9k said:
I had this EXACT same problem a week ago. I fell asleep in the middle of flashing, the phone died when it finished. I woke up, turned on the phone, ENERGY leo was trying to run its install but kept dying. Smart me, I tried to reflash (by holding the vol down button and turning it on- not through usb) and it kept dying in the middle of trying to flash.
The problem is the battery. It can't charge when it's flashing and it can't hold a charge long enough to get past the flash.
I swapped batteries with my friend, restarted the flash and it worked fine.
I let my battery charge in my friends Sprint Hero
and voila, everything went on happily ever after.
tl;dr find a way to use a charged battery while flashing.
your phone's not bricked.
Click to expand...
Click to collapse
That's the best news i have heard so far. I don't know anyone with a TP2, but i do know someone with a Hero. I'm assuming the GSM hero uses the same battery as the CDMA Hero and the TP2. I'll look into it and let you know how it goes.
chasejones8 said:
That's the best news i have heard so far. I don't know anyone with a TP2, but i do know someone with a Hero. I'm assuming the GSM hero uses the same battery as the CDMA Hero and the TP2. I'll look into it and let you know how it goes.
Click to expand...
Click to collapse
chin up, bud
I actually had a replacement sent to me.
That took a week. I fixed my phone the DAY AFTER i requested a replacement.
ohwell.
Brand new TP2 for ten dollars (shipping) I'm not really complaining.
&yes. The GSM Hero does use the same battery. I was just looking at my friends phone, decided to take a look at the battery and shat bricks when I saw it fit in my phone.
report back after you try your friends battery if it works or not!
bfgarzilla9k said:
chin up, bud
I actually had a replacement sent to me.
That took a week. I fixed my phone the DAY AFTER i requested a replacement.
ohwell.
Brand new TP2 for ten dollars (shipping) I'm not really complaining.
&yes. The GSM Hero does use the same battery. I was just looking at my friends phone, decided to take a look at the battery and shat bricks when I saw it fit in my phone.
report back after you try your friends battery if it works or not!
Click to expand...
Click to collapse
thank you so much! that fixed everything. they weren't quite the same battery, the one from the HERO isn't quite as wide. it did work, though. I'm charging my tp2 now. not sure if the battery is shot or not. everytime i unplug it, it shuts off. i'll have to charge it for a while and see if that changes anything. again, thanks so much!
So a guy I know sold a perfect HD7 on ebay and when the guy got it he said it didnt work and sent it back. When my friend got it back he found that it now starts to boot up and fails and reboots only to just start looping. I was wondering if anyone has any idea of how to get it out of the reboot loop. I am android guy so Im not sure how this works or if reboot is the right term or if you can simply flash back to stock or something, but XDA is full of smart people so I figured I would ask.
Thanks!
You are right!
If the phone doesn't boot completely I think the only choice you have is flash the correct stock rom on it.
can you give as a little bit mor information about the phone? (branding, region,...)
can you get into the bootloader menue (hold vol-down when phone powers on)
I had this on my HD7 dont flash the rom before you have tried replacing the battery. I spent days trying this sor t of aproach and nothing worked it just ment i lost my saves on my games once i did get it working.
what would happen in my case was it would show the htc logo then just as it is about to flash the o2 screen it would reboot. I got a test battery for £3 once i found out it was this I replaced it with a nice one.
Can you access the tri-color screen???
Ok so I ordered a new battery and now it boots up and runs great and was about 75% full when I first turned it on so I plugged it into the computer so it could completely charge and I left it for a few hours now I go back and its now at about 25% so basically its not charging for some reason. Also it gets really hot... So from what i can tell the USB port is broken... Also it wont connect to the computer that I can tell. Also yet I can get to the tricolor screen. And now I turned it off and back on and all it does it show the htc screen and then the little black and gray battery icon.
If you have hspal/rspal you may can flash a dft rom....if you want more support in how to flash roms please pm me
Sent from my HD7 T9292 using XDA Windows Phone 7 App
dj.95 said:
If you have hspal/rspal you may can flash a dft rom....if you want more support in how to flash roms please pm me
Sent from my HD7 T9292 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Yep I was able to get that and a stock rom installed and it didnt help.
hello all, so I've had my vivid for about 6 months now. it's unlocked, I just S-off'd it, the whole shabang. i've been flashing new roms and having some fun with it. last night I put a new rom on it and made sure everything was working, then i took it off the charger cause i was going out for a bit. the phone died (no big deal because i wasnt in the process of flashing or anything) but now it wont come back.
i put it on a wall charger and the orange light wont come on, the thing is legit dead. AT&T sent me a new battery that should get here tomorrow or tuesday. once i get that everything should be working right? or do i have bigger problems on my hands?
thanks a bunch
TCox37 said:
hello all, so I've had my vivid for about 6 months now. it's unlocked, I just S-off'd it, the whole shabang. i've been flashing new roms and having some fun with it. last night I put a new rom on it and made sure everything was working, then i took it off the charger cause i was going out for a bit. the phone died (no big deal because i wasnt in the process of flashing or anything) but now it wont come back.
i put it on a wall charger and the orange light wont come on, the thing is legit dead. AT&T sent me a new battery that should get here tomorrow or tuesday. once i get that everything should be working right? or do i have bigger problems on my hands?
thanks a bunch
Click to expand...
Click to collapse
i have actually had it happen where i had to reflash recovery so it would charge when turned off. IDk how the hell recovery had anything to do with it charging when off but it fixed it....
lolwutwin said:
i have actually had it happen where i had to reflash recovery so it would charge when turned off. IDk how the hell recovery had anything to do with it charging when off but it fixed it....
Click to expand...
Click to collapse
well right now the phone wont even turn on. no recovery, no bootloader. once the battery comes i will make sure i am still unlocked and S-off, then reflash recovery and start from scratch rom and kernel wise
EDIT: it came on briefly then died. i'm convinced the battery is just toast
TCox37 said:
well right now the phone wont even turn on. no recovery, no bootloader. once the battery comes i will make sure i am still unlocked and S-off, then reflash recovery and start from scratch rom and kernel wise
EDIT: well i unplugged it then plugged it back in and the screen came on slightly. it's still black but i can tell it's illuminated. i guess i'll just wait for tomorrow and hope that i'll be up and running again
Click to expand...
Click to collapse
thats exactly what mine did
If you search... You'll find a thread where they talk about this...
The recommendation was to plug it in... Wait for the orange led to stop flashing... Touch all the capacitive buttons... See if the light comes on... If not unplug and plug back it back in repeatedly until there is enough snot to keep it on...
And if you believe in god... Pray
Sent from my HTC PH39100 using Tapatalk 2
Hello developers,
Suddenly my note cant start any more, it shows the Samsung logo and then turn off.
in rare cases it will continue to the splash screen but then quickly turn off. ...
what would this be,,, a soft brick,,, a hard brick,,, or a battery problem,,,,
Alsager said:
Hello developers,
Suddenly my note cant start any more, it shows the Samsung logo and then turn off.
in rare cases it will continue to the splash screen but then quickly turn off. ...
what would this be,,, a soft brick,,, a hard brick,,, or a battery problem,,,,
Click to expand...
Click to collapse
Easiest way to make sure it's not a battery problem is just to buy a new one from ebay and eliminate the possibility.
But it sounds like an internal problem to me, not software related. You could try a wipe.
wrsg said:
Easiest way to make sure it's not a battery problem is just to buy a new one from ebay and eliminate the possibility.
But it sounds like an internal problem to me, not software related. You could try a wipe.
Click to expand...
Click to collapse
If the battery has waranity? how you find out is slow
wrsg said:
Easiest way to make sure it's not a battery problem is just to buy a new one from ebay and eliminate the possibility.
But it sounds like an internal problem to me, not software related. You could try a wipe.
Click to expand...
Click to collapse
drulo222 said:
If the battery has waranity? how you find out is slow
Click to expand...
Click to collapse
I did a factory reset ( I was on JB then) and didn't solve the issue. when the phone is connected to the charger it can go beyond the Samsung logo and the splash screen for a while but will turn off quickly. without a charger it will only show the Samsung logo and then turn OFF.
Can you go into recovery, plug the cable, and then power off the phone? leave it like that for few minutes.
I can go into the download mode but not recovery.... what does that mean???? Tried your other suggestion, but no luck...!!
Is your battery swollen if looking at the side and you say it will go past splash screen if plugged into charger so does that mean it will boot into the Rom if plugged in or does it just stay splash screen and also if not able to get into recovery could mean something happened with the kernel so flashing a fresh jb Rom with Odin maybe what you need. The problem with that is if your battery is bad it could cause more problems trying to flash anything with dead battery as in bricking the device. So you should start with new battery and let charge a few hours then see if your phone boots up if not then you could flash with pc Odin and go from there.
Sent from my GT-N7000 using XDA Premium 4 mobile app
He should try kernel option you gave him, if everything else failed. I read around there were like 3 people with same situation. Maybe they used the same thing?
Search philz kernel, download one or two, and flash those in odin. Its a safe kernel, and powerful cwm.
He probably fixed by now. Hope so, for his own good.
Issue Solved, It was broken battery, Changed the batter and the phone is working again. Thanks everybody for your help....
Alsager said:
Issue Solved, It was broken battery, Changed the batter and the phone is working again. Thanks everybody for your help....
Click to expand...
Click to collapse
by any chance, do you know what were the old battery voltages under measurements?