Related
Ok.. So a friend of mine suddenly got a triangle with the exclamation mark picture on his phone. That's all it boots up to. So, he took it to T-mobile, they told him it's FUBAR, and sold him a new phone.
The fact that the thing boots to a recovery mode tells me that there's SOME way to un-FUBAR this phone. My friend is too technologically inadiquate to attempt to do any modifying, so I'm going to assume he was at whatever firmware level would hve been blasted out to T-mobile as of last Friday 01/15/2010.
If I boot the phone normally, it gives me the TriAngle. I pop open the keyboard and hit alt-L and the I get the Android System Recovery menu. at the bottom I get "E:CAn't open /cache/recovery/command"
I've spent all day bouncing around this forum, and many like it, downloaded all sorts of G1 fimwares trying to go back to RC29, RC28, 30, 33.. gah! The latest one I'm trying to update to is "signed-kila-ota-116143-prereq.TC4-RC19+RC28+RC29.zip" Which i rename to update.zip . I hit alt-L, select 'update from SD card' It goes through:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update package....
Installation aborted.
That's it... no more log than that.
I've done the Alt-W, and Alt-S.. wiped cache partition. I think playing around with the recent firmwares might be fun, but I'd like to get this bad boy reset back to factory defaults. I've read the forums here on how to do that.. but all of the procedures fail.
I can get Windows 7 to recognize the phone, but I cannot access the sd card while it is in the phone. I've been transfering data to it by taking the sdcard out, and putting it into a known good SD card reader. I've formatted the sdcard to FAT16, and FAT32 quick and not quick.
Seriously.. why is this so complicated? Now I need some serious digging assistance. Is there an interface that will allow me to directly talk to this phone via the USB cable? How can I force an firmware onto it? Clearly something is functional, or I would get no I/O. How can I get this silly thing back to where it was? I know this thread seems like a redundant one, but as far as I can tell, its not. The typical procedures posted here don't seem to work, but I'll be happy to run through any steps y'all suggest. I'll resign that it's been bricked if that's really whats happened.. but I'm not ready to throw this unit away yet.
Ask questions.. let me answer them. I know this team can get this phone working again.
Thanks y'all.
--Rob aka The Austin Slacker.
Have you tried the RC29 DREAIMG.nbh file?
http://forum.xda-developers.com/showpost.php?p=4593084&postcount=1
Roadmasta01 said:
Have you tried the RC29 DREAIMG.nbh file?
http://forum.xda-developers.com/showpost.php?p=4593084&postcount=1
Click to expand...
Click to collapse
bingo !
sounds like your friend tried to flash something he shouldn't have. or messed around with stuff he shouldn't.
as far as taking it to the store, and accepting their suggestion to "GIVE US YOUR MONEY!" that was a mistake.
the phone is likely fine, and maybe you'll buy it from him for cheap, then fix, resell/use.
good luck, should be easy.
The "press camera and power to get to bootloader" procedure. I've tried holding the Camera while pressing power over and over and all I get is the triangle. However if I press power and the "back" button (swooping arrow to the left), I'll get the bars screen, and a Gray screen telling me to press send to restore.... Which is all good, but there's no progress or any thing to indicate that i've done something by pressing the send button.(based on cell phone standards, I'm assuming "send" is the green "call" button.
Is this normal?
No yeah.. he gave me the G1.. its mine. I just need to fix the little bugger.. .. well.. then laugh at him
Ok.. one more day (well ok.. couple hours) of fiddling with this thing, and i'm begining to wonder if Microsoft was involved. I'm not able to get this poor G1 to do anything new. I tried using a different SD card, hoping perhaps the one I got with it was bad... no dice. camera + power doesn't do anything useful.
I can connect it to the PC.. but i can't see the data card that way. adb devices reads no output, so its not correctly attaching to the PC (tried Windows 7 32bit, and Windows XP 64bit).. There's gotta be a good way to force a known good image onto this silly thing.
Is it probable that the internal memory has gotten corrupt somehow? I know someone out there's got the golden suggestion, please do tell if you do. I'd really like to use this phone.
--Rob
If you can get into fast boot (the tri color screen) there are ways to flash it... try getting into your tri color, then plugging in the USB cable and see if it switches from Serial 0 to USB at the bottom, if so you are golden to flash using the fast boot method.
There are guides around on how exactly to do that, as well a couple places that you can download the official RUU that will do all the hard work for you!
gah.. nothing doing. I can hit Back and Home, and end up with the tri-color screen for about 1/5th of a second, then a gray screen saying:
This operation will delete all your personal data, and reset all settings to manufacturer default. Press Send to restore manufacturer default, or press other keys to cancel.
At this point, the unit is dead. I can remove the battery, and continue on my little quest.. but hitting *any* key at all (including the Send key) will not produce any sort of output. I've tried pressing Send one time, then setting the phone down for a full hour (watched a netflix show) nothing. I can't power it off either w/o removing the battery.
I would throw in the towel.. but from all the research i've been doing, it seems as if this one is behaving in a manner in which other forum users havne't posted. Maybe by continuing to try options and post results, a positive outcome will come out, and someone else who has a G1 behaving this way will have an easier time.
... or y'all can tell me that its toast and to bugger off.. ha ha.. either way.. I continue to google. If you can think of anything, please toss it out.
OH!.. tried an RUU.. found one called. RhodiumSPLRelocker Looks promising.. but can't see the device when attached to the PC... yeah.. guess the phone has to have a functioning OS before that will happen...
You would want a Dream RUU... I looked around a bit and couldn't find one. Maybe someone has a quick link?
Double check that your SD card is formatted FAT32 and see if you can get ADB to see it when on that greay screen.
I've formatted the SD card in FAT32 multiple times.. I even questioned if my Windows 7 32bit would do it, and formatted it on a laptop running XP 64bit. adb doesn't seem to see it ever.
I don't get why I can't get it into fast boot. I've been looking on ebay for dream G1s with broken screens.. heh.. I guess i'm preparing for the worst. really sad, becasue this G1 was actually pretty well taken care of. My friend didn't do anything he shouldn't. HE woke up one morning and it was like this. He lives out in the country.. so he gets pretty spotty signal. I'm wondering if T-Mobile didn't push out an update, and it got interrupted by signal loss.
By the by... I've been doing all this work w/o a SIM card. Does that matter?
austinslacker said:
(based on cell phone standards, I'm assuming "send" is the green "call" button.
Click to expand...
Click to collapse
its not the green send button -- its the red end button
see below extracted from http://theunlockr.com/2009/07/05/how-to-unroot-your-t-mobile-g1/
Load the DreaIMG.nbh File
1. Download the Original DreaIMG.nbh file:
http://www.megaupload.com/?d=XXSQ0T7W
2. If the file downloaded above downloads as a .Zip file, please unzip it first then put the DreamIMG.nbh file that is inside on the SD card, NOT in any folder. (If you did Section I the phone is off still, take out the memory card, put it in the MicroSD adapter and plug it into your computer to transfer the file over, since your G1 won’t turn on right now if you did Section I above. Otherwise if you did not need to do Section I above, then you can just put it on the SD card normally using the usb cable and the phone).
3. Turn the phone off if it is on.
4. Turn on the phone by holding the Camera button and the End key until the bootloader screen turns on.
5. Hit the End key to start the update. DO NOT INTERUPT THIS PROCESS.
6. Once it is done, hit the trackball to restart the phone. You now are on the stock firmware RC29
austinslacker said:
The "press camera and power to get to bootloader" procedure. I've tried holding the Camera while pressing power over and over and all I get is the triangle. However if I press power and the "back" button (swooping arrow to the left), I'll get the bars screen, and a Gray screen telling me to press send to restore.... Which is all good, but there's no progress or any thing to indicate that i've done something by pressing the send button.(based on cell phone standards, I'm assuming "send" is the green "call" button.
Is this normal?
No yeah.. he gave me the G1.. its mine. I just need to fix the little bugger.. .. well.. then laugh at him
Click to expand...
Click to collapse
You mention that you can access fastboot by pressing the back button while turning it on, isn't that how the hero gets into fastboot? maybe your friend tried flashing a rom that was meant for the hero. if you have access to fastboot you should be able to flash a new image from there, just place the image file in the root of your card and follow the fastboot instructions
Also if fastboot isn't doing it for you have you tried adb? if you don't know what that is look it up I've seen a couple guides on how to do it and they are really detailed.
Im having the same problem, Im stuck in the recover triangle of death. Ive done the alt+w and reboot, the RC29 DREAIMG.nbh , the update.zip, camera+power, I cant get the gray screen to pop. Nothing, its brickkkkeeeddddd, FUBAR. There has got to be someway I can reload this G1. I wasnt trying to root it or anything. I was bowling and then it triangled on me. Anyone have any ideas at all on how to fix it?
Triangle of Death
I'm from Brazil, I can't take it to t-mobile to fix...
when i tried to root my G1 did the downgrade perfectly, the screen was just as it was suposed to be.
But in the recovery mode boot, appeared this triangle with an exclamation...
what do i do now???? help plz!
deftoneage12 said:
Im having the same problem, Im stuck in the recover triangle of death. Ive done the alt+w and reboot, the RC29 DREAIMG.nbh , the update.zip, camera+power, I cant get the gray screen to pop. Nothing, its brickkkkeeeddddd, FUBAR. There has got to be someway I can reload this G1. I wasnt trying to root it or anything. I was bowling and then it triangled on me. Anyone have any ideas at all on how to fix it?
Click to expand...
Click to collapse
Any one have any ideas? hell ill pay someone to fix it for me
The only idea I have is make'ing an goldcard so your sure your phone accepts the update (dreaimg)... other than that...
Sent from my HTC Dream G1 using the XDA mobile application powered by Tapatalk
Any chance the home button is stuck? I'm not 100%, but I think if you were to hold home, camera and power, the recovery would come out on top.
Home button is not stuck, and cant seem to figure out the CID of my SD card since my phone is unaccessable.
I have a N1 and its worked fine for a while then i noticed when i turned it on it just stays at the "X" boot up screen.. I have already tried to reset the phone, clear storage, reboot,, and nothing fixes it. What can i do.. i know there has to be a way to load software back onto it or fix whatever is wrong with this thing. please help and thanks for our time.
can you get into the bootloader menu? by holding trackball and power button?
if yes then follow
http://forum.xda-developers.com/showthread.php?t=623496
wow,, ive done some programming and flashing to phones before but trying to follow those instructions and make sense of it all, isnt working with me. Thanks for the advice but that thread doesnt help me to much. i tried downloading everything it says i need and i cant figure it out.
rustynuttz said:
I have a N1 and its worked fine for a while then i noticed when i turned it on it just stays at the "X" boot up screen.. I have already tried to reset the phone, clear storage, reboot,, and nothing fixes it. What can i do.. i know there has to be a way to load software back onto it or fix whatever is wrong with this thing. please help and thanks for our time.
Click to expand...
Click to collapse
another app2SD thing after flashing a new rom?
well then you know more then me. If you can get into bootloader you should be able to get into recovery mode. You can also toggle USB mode, so you can be connected to your comp. In that case you can push a recovery image.
http://forum.xda-developers.com/showthread.php?t=611829
you can also wipe
etc
its all in that thread or somewhere else on this forum
rustynuttz said:
I have a N1 and its worked fine for a while then i noticed when i turned it on it just stays at the "X" boot up screen.. I have already tried to reset the phone, clear storage, reboot,, and nothing fixes it. What can i do.. i know there has to be a way to load software back onto it or fix whatever is wrong with this thing. please help and thanks for our time.
Click to expand...
Click to collapse
Any updates? same thing happened to me.
If in doubt then reflash everything again;
boot
system
and recovery
and start afresh.
see thats the thing,, i can click recovery from the bootloader screen and nothing happens. It will restart and just sit on the same "X" screen. Its very simple to put a phone into a DFU mode or recovery mode for Iphones,Motorolas,blackberry,nokia,samsung,Lg, and a few more i cant think of at the moment. When these phones become corrupt ive learned how to whatever firmware or software i want on dumb thing.. But this HTC is giving me a hard time and i know its something simple.. Most phones have a desktop software that will allow you to mess with phones programming, Itune-iphone/Blackberry-BB desktop Manager/motorola-RSD lite....ect. BUt i cannot find anything really for the HTC or just this N1. A lot of these programs for other brands, once you plug your phone in, will notice that the phone is in a recovery state and offer to do an update or a restore. Now why doesnt the N1 or do they, does google offer something like evryone else does?
rustynuttz said:
see thats the thing,, i can click recovery from the bootloader screen and nothing happens. It will restart and just sit on the same "X" screen. Its very simple to put a phone into a DFU mode or recovery mode for Iphones,Motorolas,blackberry,nokia,samsung,Lg, and a few more i cant think of at the moment. When these phones become corrupt ive learned how to whatever firmware or software i want on dumb thing.. But this HTC is giving me a hard time and i know its something simple.. Most phones have a desktop software that will allow you to mess with phones programming, Itune-iphone/Blackberry-BB desktop Manager/motorola-RSD lite....ect. BUt i cannot find anything really for the HTC or just this N1. A lot of these programs for other brands, once you plug your phone in, will notice that the phone is in a recovery state and offer to do an update or a restore. Now why doesnt the N1 or do they, does google offer something like evryone else does?
Click to expand...
Click to collapse
hmmm I understand your frustration. What did you do before it got to the 'X' splash screen?
I'm assumimg you've tried to reflash a different ROM in recovery mode?
rustynuttz said:
Most phones have a desktop software that will allow you to mess with phones programming, Itune-iphone/Blackberry-BB desktop Manager/motorola-RSD lite....ect. BUt i cannot find anything really for the HTC or just this N1. A lot of these programs for other brands, once you plug your phone in, will notice that the phone is in a recovery state and offer to do an update or a restore. Now why doesnt the N1 or do they, does google offer something like evryone else does?
Click to expand...
Click to collapse
The SDK can do that
like the others said, try get into recovery and reflash everything
SDK? i just turned the phone on and its stuck on the "Splash" screen just a big ol "X". I press volume down and power and pull up the bootloader menus.. i scroll down to recovery and press enter. and it reboots and stays at the damn "x" screen again. I've chosen everyone of the options it offers in that menu and nothing changes.. You know how when u first open that menu it will scan the SD card? Well it shows up for a second then goes away, and in the split second the green lettering is on the screen i swear it says "no splash image" or something like that. UHHHHhhhg!
Hmm I forgot how to get to get to recovery using physical buttons, sth like: power + trackball, or volume down + trackball i guess, so try that
So it looks like your phone is not rooted and you don't have Amon_Ra recovery maybe you have not even turned on USB debugger? tough luck friend
All is not lost if you can get into fastboot mode trackball and power together then using adb reflash boot,system and recovery images.
Or call Customer Service and trade in for a new Nexus One
if not you have to download the SDK http://developer.android.com/sdk/index.html
find stock images and reflash like the above post said
duylong186 said:
Or call Customer Service and trade in for a new Nexus One
if not you have to download the SDK http://developer.android.com/sdk/index.html
find stock images and reflash like the above post said
Click to expand...
Click to collapse
agreed....if you haven't "unlocked" the bootloader then i wouldn't bother with any of the suggestions....Call customer care and get a new one before you un-lock it and this mysteriously happens again...THEN, you'll be S-O-L!!
EDIT: Then with the new one, follow all the threads for un-locking, flashing recovery, nand,flash cyan, flash gapps LALALA
DOUBLE EDIT: Althought it sounds all you've done is messed up the recovery image, which you could re-flash. Then you could get into recovery and flash Cyan, having a functioning phone again
What can we do? I dont want to mess with anything again because i know if anything goes wrong i cant get in to download mode.. But i too want to flash the new roms and gps fixes. Is there anyway to make the hardware buttons unlocked?
Why not use adb? I used it and Odin for the first time two days ago flashing this new patch and it was quite simple. I, like you, have a hardware locked handset. Let's hope it didn't take you nearly the same two hours that it took me.
You can root using clockworks and run some of the patch through clockworks too. Try not to use odin unless you really know what you're doing. A lot have odin hang on them. Other than that, you can flash rom using clockworks.
Sent from my SGH-T959 using XDA App
jonathan3579 said:
Why not use adb? I used it and Odin for the first time two days ago flashing this new patch and it was quite simple. I, like you, have a hardware locked handset. Let's hope it didn't take you nearly the same two hours that it took me.
Click to expand...
Click to collapse
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*
TWO HOURS! Lucky SOB, took me over 4 hours, but I was at work with nothing better to do then to play with it on and off, google some more, crawl xda, play some more....rinse repeat...
But I don't think there will be an official "fix" as in their eyes nothing is broken. It is as they intended. I'm not really sure if this move was by tmo or samsung, but regardless it's a PITA. I used ADB. The hardest part is getting the drivers in, after that it's easy cake walk thanks to the wealth of knowledge here at xda.
glensta said:
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*
Click to expand...
Click to collapse
exactly my point. this is what happened to me. but think about this lets say i flash a rom right and you know how sometimes it hangs on the vibrant screen and just stays there. and in order to get it back i am going have to use odin. which i cant.......... so i think i wont mess with anything anymore. Rather just wait for official 2.2 ota update.
Chief Geek said:
TWO HOURS! Lucky SOB, took me over 4 hours, but I was at work with nothing better to do then to play with it on and off, google some more, crawl xda, play some more....rinse repeat...
But I don't think there will be an official "fix" as in their eyes nothing is broken. It is as they intended. I'm not really sure if this move was by tmo or samsung, but regardless it's a PITA. I used ADB. The hardest part is getting the drivers in, after that it's easy cake walk thanks to the wealth of knowledge here at xda.
Click to expand...
Click to collapse
Take it back and do a warranty exchange cause the buttons arent working correctly.
I've never tried it because I could never get Kies to connect to my phone, but isn't there a way to update firmware through Kies? I know the i9000 guys use Kies to upgrade, but I think that's only to get drivers and the updates though. I wish Samsung had a better interface than Odin to flash firmware. It's absolute garbage.
Hello, I am new to this android stuff but think I may have a problem and no hardware keys may come into play.
I rooted my phone for no other reason than to remove bloatware
I removed what I new was safe and left alot on the phone just because I was not sure what to remove
Phone was working great and had no problems
I decided I wanted to do a factory reset to remove all my apps and user data etc.....
I did do a titanium back up of my apps so I could easily resinstall if I wanted
I did the reset and now as soon as the phone boots I get TWLauncher force close and just about any other app that tries to load just continuose force close loop
I did not remove the original launcher so I am not sure why this is happening but I cant flash since I cant get into download mode and I cant use ADB since my phone wont let me put into debug what to do?????????????
glensta said:
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*
Click to expand...
Click to collapse
This is how I got out of "phone to pc"
get into download mode (i went through it manually, as in plug in the phone, and pressing the volume buttons together at the same time)
Connected to ODIN, and by perfect accident, I clicked on "start" without placing ANY files in ANY spots.
This is what I thought "OMG $h!t" Well my phone was already bricked enough, so i just let it run its course through ODIN. My phone magically rebooted, and it booted into the ROM i had installed before I got the "phone to pc" problem.
Whats the disadvantage of having a hardware locked phone?
From what I'm reading i cant load custom roms? or can use Oden?
Also I just got mine and im sure its hardware locked but how can I tell
TIA
demo23019 said:
Whats the disadvantage of having a hardware locked phone?
From what I'm reading i cant load custom roms? or can use Oden?
Also I just got mine and im sure its hardware locked but how can I tell
TIA
Click to expand...
Click to collapse
The disadvantage is that it is harder (maybe impossible in some situations?) to get into the Download mode if something goes wrong during a ROM update. You can still load custom ROMS but if something goes wrong, you might not be able to get to Download mode to be able to fix it.
I had the phone ! PC screen on mine when I first tried to unsuccessfully flash Vibrant8. Luckily, my Vibrant doesn't seem to be hardware locked and I was able to get back into Download mode and re-flash it with Odin.
I'm able to access download mode with volume keys and i can access recovery mode so i guess im ok
also date on box is 8/27/10
How do you know whether you have a hardware locked Vibrant or not?
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
I trust what you're saying.. but is there any way to test that out without having an already bricked phone? I want to make sure I can recover my phone before flashing your Vibrant hybrid ROM. So after Step 6 do you get the download mode screen? Or does ODIN now show a COM port and it works, even without the little digger guy?
eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
First off, absolutely no disrespect Eugene, you are an amazing developer and a HUGE contribution to this forum, I personally love your work and have tried many of your ROM's (actually looking at switching up to your newest hybrid rom next), but there are most certainly some of these phones that are hardware locked to the point that you can not get in to download mode, regardless of what you do. The steps you posted definitely work for some, and for non-hardware locked phones, they work beautifully, however, there are some phones that no matter what you do, no matter what order you do it in, you will never get in to download mode short of using ADB. The good news is, the lockout was not intentional, and exchanging your hardware locked Vibrant will generally result in a non-hardware locked phone (from mine, and many other's personal experience).
johnny12times said:
First off, absolutely no disrespect Eugene, you are an amazing developer and a HUGE contribution to this forum, I personally love your work and have tried many of your ROM's (actually looking at switching up to your newest hybrid rom next), but there are most certainly some of these phones that are hardware locked to the point that you can not get in to download mode, regardless of what you do. The steps you posted definitely work for some, and for non-hardware locked phones, they work beautifully, however, there are some phones that no matter what you do, no matter what order you do it in, you will never get in to download mode short of using ADB. The good news is, the lockout was not intentional, and exchanging your hardware locked Vibrant will generally result in a non-hardware locked phone (from mine, and many other's personal experience).
Click to expand...
Click to collapse
Download Mode is controlled by SBL, so if they truly changed anything that would be the cause.
I would think you could target redbend to update the SBL or even boot.bin bml /stl location.. I've not tried this, nor do I need too.. Just tossing options out there for people to try & don't mind risking a brick..
If you can get the SBL / Boot.bin for the Stock to flash via redbend, then this will solve the HW locks.. Now, Regarding my Phone, I can still get into Download Mode however, only by doing the USB trick &/or ADB reboot download.
I can not get into recovery unless I use clockwork Manager or ADB into
By the way, this is not a Hardware Lock issue as the thread states.. Not being able to get into download Mode like described, is a zImage issue & not the SBL / BOOT.bin
just as a FYI.
~Eugene
Hello, I am new to this android stuff but think I may have a problem and no hardware keys may come into play.
I rooted my phone for no other reason than to remove bloatware
I removed what I new was safe and left alot on the phone just because I was not sure what to remove
Phone was working great and had no problems
I decided I wanted to do a factory reset to remove all my apps and user data etc.....
I did do a titanium back up of my apps so I could easily resinstall if I wanted
I did the reset and now as soon as the phone boots I get TWLauncher force close and just about any other app that tries to load just continuose force close loop
I did not remove the original launcher so I am not sure why this is happening but I cant flash since I cant get into download mode and I cant use ADB since my phone wont let me put into debug what to do?????????????
Click to expand...
Click to collapse
Its happening because you ran a full titanium backup including system data. Yeah, dont do that. Reflash, then reinstall user apps with data, and pick and choose the system ones that are obvious (mms, bluetooth settings, wireless settings, etc.) Then reboot for changes to take effect. When in doubt, dont restore.
Good luck. Although you won't need it if you do what I just told you.
Sent from my SGH-T959 using Tapatalk
Just to share...
eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
I had the phone!computer bricked Vibrant, and just got my replacement from Asurion (in fact, of the phones in front of me are from Asurion since my original got stolen 2days after it came out ).
On phone1: The original TMO date is 8/12/2010, while the Asurion date is 8/19/2010. Also the ID is GJ/HLP. This one was HW Locked.
On phone2: The original TMO date is 9/2/2010, while the Asurion date is 9/10/2010. Also the ID is SM/HLP. This one doesn't seem to be HW Loocked, I can get into recovery easily, DL Mode ... not so much . Booting with vol+&- gets me into recovery, but booting with just vol- does nothing ...
Any thoughts?
I hope someone can help me. I've been scouring the blogs but couldn't find anything that could help me and I'm stuck. I have a mytouch 3g slide and all of a sudden it keeps rebooting and won't turn completely on...it just keeps rebooting non-stop. I tried taking out the battery overnight and putting it back in, held the volume down button + power button which brought me to the HBOOT screen and only showed FASTBOOT, RECOVERY, CLEAR STORAGE & SIMLOCK. When I tried clicking on RECOVERY it just reboots my phone and does it over and over again, same thing when I do CLEAR STORAGE. I've tried this both with the SD card in and out and it would still not take me to where there's the red triangle...just keeps rebooting. Everything else I've seen on forums tells me to unroot/reroot, reformat, flash etc but since whatever I do it just reboots I can't do it. Other details of my phone are the following:
EXPRESSO PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-0620
TOUCH PANEL-SYNT0102
RADIO-7.07.35.02S
Nov 26 2010, 20:43:01
CM7
I'm sorry but I'm pretty new to this and I get lost with the terms so I'm trying to be as detailed as I can. I really do hope someone can help me
ka-dork said:
I hope someone can help me. I've been scouring the blogs but couldn't find anything that could help me and I'm stuck. I have a mytouch 3g slide and all of a sudden it keeps rebooting and won't turn completely on...it just keeps rebooting non-stop. I tried taking out the battery overnight and putting it back in, held the volume down button + power button which brought me to the HBOOT screen and only showed FASTBOOT, RECOVERY, CLEAR STORAGE & SIMLOCK. When I tried clicking on RECOVERY it just reboots my phone and does it over and over again, same thing when I do CLEAR STORAGE. I've tried this both with the SD card in and out and it would still not take me to where there's the red triangle...just keeps rebooting. Everything else I've seen on forums tells me to unroot/reroot, reformat, flash etc but since whatever I do it just reboots I can't do it. Other details of my phone are the following:
EXPRESSO PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-0620
TOUCH PANEL-SYNT0102
RADIO-7.07.35.02S
Nov 26 2010, 20:43:01
CM7
I'm sorry but I'm pretty new to this and I get lost with the terms so I'm trying to be as detailed as I can. I really do hope someone can help me
Click to expand...
Click to collapse
It sounds as if your phone is toast... however, you could try going to the HTCdev.com site and doing the unlock procedure (which is going to require you to enter fastboot, so if that's not working, you're truly toast).
Once you've got that done, you can then flash a new recovery, like clockworkmod, and see if you can then use that to clear storage, or flash a new ROM.
Alternatively, you could try to just reinstall the froyo update from T-Mobile/HTC.
Thanks
jonnycat26 said:
It sounds as if your phone is toast... however, you could try going to the HTCdev.com site and doing the unlock procedure (which is going to require you to enter fastboot, so if that's not working, you're truly toast).
Once you've got that done, you can then flash a new recovery, like clockworkmod, and see if you can then use that to clear storage, or flash a new ROM.
Alternatively, you could try to just reinstall the froyo update from T-Mobile/HTC.
Click to expand...
Click to collapse
Thanks for the help, jonnycat26. I really appreciate it. It does seem my phone is pretty much toast I tried unlocking it as you said but you're right, it won't let me enter fastboot and my PC couldn't detect the phone since it won't turn on.
I was wondering though, would you happen to have any idea what caused this? It would be good to know so I don't make the same mistake next time around. Thanks again!
Wait! Your phone isn't toast! Download the RUU from the htc website, run it on windows, take the rom.zip from %TEMP%, rename it to ESPRIMG.zip and put it on your sdcard, then boot into Hboot, and it'll reflash the system.
Hitorijanae said:
Wait! Your phone isn't toast! Download the RUU from the htc website, run it on windows, take the rom.zip from %TEMP%, rename it to ESPRIMG.zip and put it on your sdcard, then boot into Hboot, and it'll reflash the system.
Click to expand...
Click to collapse
Thanks, Hitorijanae! I'll try that and let you know how it goes.
Hi Hitorijanae,
Okay I'm not sure if I did it right. I saved it to my sdcard as ESPRIMG.zip as you said and then did the volume down + power thing and it brought me to the screen with the 3 androids (sorry not quite sure if that's the HBOOT page that you were talking about). Anyway it did the SD checking. Does it make a difference if it says [ESPRDIAG.zip] no image or wrong image? Anyway it loaded up the ESPRIMG.zip and then asked me if I wanted to update it and I said yes. After that it asked if I wanted to reboot and when I said yes it just rebooted over and over again like my previous problem. I tried also choosing no and it brought me back to HBOOT and my only options were FASTBOOT, RECOVERY, CLEAR STORAGE & SIMLOCK. Choosing FASTBOOT just brings me to reload bootloader, etc.; choosing RECOVERY my phone just reboot loops again and same if I choose CLEAR STORAGE.
I'm not sure if I'm doing it wrong or just screwing it up even more. Sorry for all the questions but I keep getting stuck. I would appreciate all the help I can get.
ka-dork said:
Hi Hitorijanae,
Okay I'm not sure if I did it right. I saved it to my sdcard as ESPRIMG.zip as you said and then did the volume down + power thing and it brought me to the screen with the 3 androids (sorry not quite sure if that's the HBOOT page that you were talking about). Anyway it did the SD checking. Does it make a difference if it says [ESPRDIAG.zip] no image or wrong image? Anyway it loaded up the ESPRIMG.zip and then asked me if I wanted to update it and I said yes. After that it asked if I wanted to reboot and when I said yes it just rebooted over and over again like my previous problem. I tried also choosing no and it brought me back to HBOOT and my only options were FASTBOOT, RECOVERY, CLEAR STORAGE & SIMLOCK. Choosing FASTBOOT just brings me to reload bootloader, etc.; choosing RECOVERY my phone just reboot loops again and same if I choose CLEAR STORAGE.
I'm not sure if I'm doing it wrong or just screwing it up even more. Sorry for all the questions but I keep getting stuck. I would appreciate all the help I can get.
Click to expand...
Click to collapse
When it's booting up, go into the command prompt, cd to the directory with adb and then do adb logcat.
Hitorijanae said:
When it's booting up, go into the command prompt, cd to the directory with adb and then do adb logcat.
Click to expand...
Click to collapse
When I do that it only says -waiting on device- and nothing else. I tried doing the unlock bootloader thing but when it comes to the part after I type in fastboot oem get_identifier_token it just says waiting on device as well. Any other suggestions? I'm not really a dev so I'm not very confident if what I'm doing is right and I get lost sometimes with what you ask me to do but I try to look it up online to get a better understanding of it and then try it before I ask too many questions. I appreciate your patience with me though and for all your help, Hitorijanae and jonnycat26. I'd like to go on if there's still hope for my phone :crying:
ka-dork said:
When I do that it only says -waiting on device- and nothing else. I tried doing the unlock bootloader thing but when it comes to the part after I type in fastboot oem get_identifier_token it just says waiting on device as well. Any other suggestions? I'm not really a dev so I'm not very confident if what I'm doing is right and I get lost sometimes with what you ask me to do but I try to look it up online to get a better understanding of it and then try it before I ask too many questions. I appreciate your patience with me though and for all your help, Hitorijanae and jonnycat26. I'd like to go on if there's still hope for my phone :crying:
Click to expand...
Click to collapse
Alright, go into HBOOT, then hit power button to go into fastboot. Plug it up, and type fastboot devices in the command prompt.
Thanks!
Hitorijanae said:
Alright, go into HBOOT, then hit power button to go into fastboot. Plug it up, and type fastboot devices in the command prompt.
Click to expand...
Click to collapse
Hi, Hitorijanae!
Sorry for the late reply and things got a bit crazy over here. I had my phone checked and it was a hardware problem so they had to open it up and stuff and now it's all good but I have to be extra careful not to drop or accidentally hit my phone or else it's screwed again. I just wanted to thank you for all your help though
Do you know what was the issue? (Loose cable, failed component, etc)
GoPadge said:
Do you know what was the issue? (Loose cable, failed component, etc)
Click to expand...
Click to collapse
The guy said it was a hardware issue. Something broke off inside and damaged the memory (I accidentally dropped my phone a few days before my phone went bonkers on me). I wish I could explain it better but for the life of me I can't remember the things the guy said right now but he had to open it up and weld the broken bit back together.
ka-dork said:
The guy said it was a hardware issue. Something broke off inside and damaged the memory (I accidentally dropped my phone a few days before my phone went bonkers on me). I wish I could explain it better but for the life of me I can't remember the things the guy said right now but he had to open it up and weld the broken bit back together.
Click to expand...
Click to collapse
Solder, not weld, but I understand completely. I had to replace the power button and digitizer on mine.
GoPadge said:
Solder, not weld, but I understand completely. I had to replace the power button and digitizer on mine.
Click to expand...
Click to collapse
LOL! Yeah, goes to show you how much I know about this stuff I just have to be extra careful with my phone...I hope it holds up for a bit longer.
So i was trying the new beta for PA android and when i was on recovery wiping as usual, the wipe process just froze there for a while, i decided to leave it till it worked again but to no avail it didnt budge at all, so i commited the ultimate sin, and powered it off by holding the power button...
when i tried again tu turn it on the tablet would go thru the google with the padlock screen and then show me a black screen with a little logo of clockworkmod and a version number below, the screen itself has no use since no matter what button i press it does nothing, other than that the tablet keeps rebooting after that.
when i try any combination of buttons to access either the real recovery or the bootloader the tablet just plain ignores that im trying to turn it on, just doesnt work, it just turns on if im not pressing anything besides the power button.
to sum up to all my problems i would love to keep trying and see if at anypoint it will turn to bootloader, i havent seen the notification of the tablet being charged... meaning that i dont know if it has enough battery to last me the remaning ideas i had.
So in a nutshell
-no bootloader
-no fastboot
-no recovery
-cant tell if battery or not
Please if anyone knows how to fix or at least get me to a bootloader i would fix everything else, but i really need the guidance here
Have you tried another charger and cable? A simple idea, but not one to over look.
Without bootloader menu or recovery, not much you can do. I'd work on getting into one of those first. Not much you can do until then.
Osivanlou said:
So i was trying the new beta for PA android and when i was on recovery wiping as usual, the wipe process just froze there for a while, i decided to leave it till it worked again but to no avail it didnt budge at all, so i commited the ultimate sin, and powered it off by holding the power button...
when i tried again tu turn it on the tablet would go thru the google with the padlock screen and then show me a black screen with a little logo of clockworkmod and a version number below, the screen itself has no use since no matter what button i press it does nothing, other than that the tablet keeps rebooting after that.
Click to expand...
Click to collapse
Are you able to get adb to recognize the device with "adb devices"?
KJ said:
Have you tried another charger and cable? A simple idea, but not one to over look.
Without bootloader menu or recovery, not much you can do. I'd work on getting into one of those first. Not much you can do until then.
Click to expand...
Click to collapse
Yeah ive tried 4 other chargers, and nothing new, i know that the os itself takes care of the charging as does the recovery in some cases, but since i have non i dont know if its gonna charge at all or not and trying doesnt sound really appealing since i should save battery in case theres a solution and needs battery power
but thanks for the answer
[email protected] said:
Are you able to get adb to recognize the device with "adb devices"?
Click to expand...
Click to collapse
Dont really know how to check, i mean i could get into the tools and try the command Adb Devices but how should i even begin to test? i mean shouldnt i be in a adb static platform on the device? if i try to get into bootloader it just doesnt turn on, and when it does it goes straight to the black screen with the clockworkmod symbol and numbers
Thanks for the answer
Osivanlou said:
Dont really know how to check, i mean i could get into the tools and try the command Adb Devices but how should i even begin to test? i mean shouldnt i be in a adb static platform on the device? if i try to get into bootloader it just doesnt turn on, and when it does it goes straight to the black screen with the clockworkmod symbol and numbers
Thanks for the answer
Click to expand...
Click to collapse
if you have enough battery and can get pc to see is thru adb. you may be able to fastboot a new rom onto the device. You can from pc Request device to go into bootloader or fast boot from the PC..
This is your only shot.. I Would suggest borrow a friends Nexus 7 Full Battery . If you do not know how to do any of this . Use skips root kit and use the unbrick or factory reset. it will force your device into fast boot and flash a new rom.
Good Luck
erica_renee said:
if you have enough battery and can get pc to see is thru adb. you may be able to fastboot a new rom onto the device. You can from pc Request device to go into bootloader or fast boot from the PC..
This is your only shot.. I Would suggest borrow a friends Nexus 7 Full Battery . If you do not know how to do any of this . Use skips root kit and use the unbrick or factory reset. it will force your device into fast boot and flash a new rom.
Good Luck
Click to expand...
Click to collapse
yeh i know how to use the skip toolkit, yet i hope i have enough battery for the test, because the only friend that i know owns a nexus 7 left the country a few months back, so the battery sounds like its gonna be hard to get. Anyways, as u were saying theres a posibility that while the tablet is rebooting and rebooting it might be able to be found on the adb devices? and use the fastboot, cuz if thats true u would be the hero ive been waiting for...
imma check and tell u later,
thanks for the answer