Related
First off im sorry im adding another rooting post to these boards.
So i decided to root my 32B magic today copyed the recovery.img over and update file from the rooting wiki, loaded recovery mode then updated, but now my phone when turned on loads to the vodafone screen and freezes id left it for afew hrs but still no luck.
Here is what i know so far:
I am able to get to fastboot and fastboot usb
I cant however get to recovery mode by pressing menu+power
I can get to the recovery mode using the sdk\tools
my problem is that im sure the fix is relativly simple i.e. load some files onto sd and start again, but the problem is that i have no other way to load the files onto the sd card than through the phone and my knowledge of adb isnt that great although has improved greatly today lol.
Im not sure how correct i am on this, but would it be a possible fix to load say a rom update.zip onto the sd card and load that through recovery mode to bring it up? If that would fix it could i possible get help on the adb code needed to pass the file from computer to the phone through fastboot usb or recovery.
Thank you very much for your help
Ok i think i have figured how to push files to my sd card however whenever i try it come up saying Failed ( remote:signature verify fail)
ok well i managed to move Cyanogen's newest rom over and update to that but its still hanging up at the vodafone screen upon booting, im lost for ideas.
Please any help how ever small would be amazing right now.
please help is desperatly needed.
i am having the same issue.... and it seems NO ONE has a bloody answer to why it is failing
I successfully update to 32A and root. Then i tried to update to MT3G OTA rom and now i'm stuck at Vodafone screen. Need help or ideas and how to recover..
i had the same problem, what i did was that i found a sd card adapter and hooked it up to my computer, its pretty quick and less hassle
waacow said:
I successfully update to 32A and root. Then i tried to update to MT3G OTA rom and now i'm stuck at Vodafone screen. Need help or ideas and how to recover..
Click to expand...
Click to collapse
take out your battery and after a few seconds put it back in, before it powers up go into fastboot(back+power) and that should do it
I still have a pretty red splash screen and stucked.
neoxtian said:
take out your battery and after a few seconds put it back in, before it powers up go into fastboot(back+power) and that should do it
Click to expand...
Click to collapse
I have same problem, but your solution didn't work for me.
I did as follows.
#1. typed following command in terminal.(well, I'm using Mac)
Code:
fastboot-mac flash recovery recovery-RAv1.2.0G.img
#2. pulled battery off from phone.
#3. pluged USB cable to phone and also Mac.
#4. pressed (ENTER) in the terminal, then fastboot-mac said '< waiting for device >'.
#5. put the battery in while pressing (back)+(power)
#6. then, pretty red vodafone splash screen come up.
#7. In the terminal, it still said '< waiting for device >'. Nothing was changed.
#8. On the phone, pretty red splash screen was still there. Nothing was changed.
Those are all I have done many times for last 2 days.
But, it didn't work.
Please let me know if there is something I missed.
I tried and stuck in the exactly same problem as [robotician]. I have MT3G.
robotician said:
#5. put the battery in while pressing (back)+(power)
#6. then, pretty red vodafone splash screen come up.
#7. In the terminal, it still said '< waiting for device >'. Nothing was changed.
Click to expand...
Click to collapse
THe red vodafone should not come up. You have to hold the back key longer perhaps, because it's supposed to go into the fastboot screen with all sorts of text and three androids on skateboards at the bottom.
@Niaski
was your rom made for the 32B or the 32A?
They are very diferent phones and mixing the roms causes the issue you are seeing.
A few days ago I bricked my phone. I performed a SPL flash which seemed to go ok, the phone rebooted and then just stuck at the first splash screen. I waited for 30 minutes and it was still there.
I then removed the battery, reinserted it, and tried booting into recovery mode. Nothing happened, it just stuck at the first splash screen.
So I removed the battery again, reinserted it, and tried booting into fastboot mode. Nothing happened, it just stuck at the first splash screen.
I repeated these steps a few times with the same result.
I tried booting it with the USB cable attached, the result was the same, and Windows showed the phone as an 'unrecognized device'.
At this point, I was nearly crying, my phone was a brick.
Then, for some reason I tried the following:
-On the PC, i ran the command 'fastboot boot recoveryimage.img'.
-At this point the command says 'waiting for device' (or something like that).
-I removed the battery.
-I Connected USB.
-I inserted the battery.
-I booted the phone while holding the HOME key.
-The phone still froze at the first splash screen, but then suddenly, the waiting fastboot command detected the phone and booted the recovery image! Yay!
That's it. I didn't test it any more thoroughly for obvious reasons, I just reflashed the SPL and everything was back to normal.
I hope this helps someone in the future....
Very nice..
wow seriously, didnt expected that..
good job mate!
btw wat did u do to cause the brick?
Just read the very first line of his post...
marcdbl said:
A few days ago I bricked my phone. I performed a SPL flash which seemed to go ok, the phone rebooted and then just stuck at the first splash screen. I waited for 30 minutes and it was still there.
[...]
Click to expand...
Click to collapse
mgear356 said:
btw wat did u do to cause the brick
Click to expand...
Click to collapse
As I said above, I had been flashing the SPL, and when I rebooted following the flash it was bricked (stuck at first splash screen).
It's weird, because once I managed to get back into fastboot, I simply flashed the same SPL again and it worked fine.
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
Never seen someone say the splash screen isn't coming up without blaming the hardware. I didn't think that flashing the wrong SPL would case the splash to not come up. I bricked my first phone by stupidly flashing the wrong SPL first before loading an OS. I thought the whole point of using the word 'brick' was when referring to the phone failing to enter 'fastboot' and 'recovery mode'. At that point, the phone would technically be a 'brick'. This has to be the first post I've seen with a possible fix but I could be wrong since I gave up on fixing that phone awhile ago.
goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
bricking means you can't get to fastboot or recovery no matter what you do.
so he counts as bricking.
this might be a fix for the haykuro spl bricked users..
Well done if we have HTC G1 user with brick phone who want to try this methode and give feedback
goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
No, You can still get to your splashscreen when the phone is bricked, If you cant turn on the phone then thats called the phone is dead not bricked. As stated already if you can't fastboot, or get to recovery then thats a brick.
Just tried it does not work and I was flash the death spl from haykuro,I am getting a new one but wanted to see if this works and I did not think it would which it didnt.
imfloflo said:
Well done if we have HTC G1 user with brick phone who want to try this methode and give feedback
Click to expand...
Click to collapse
Posted the fix on the android community forums. I have none person in mind, bricked it applying a spl, but he hasn't relied yet. Keep you informed if he does.
Did you reflash ROM after applying spl..? If you did and it still didn't boot then that should most likely be a brick. Can you boot into recovery right now and tell us your SPL version and radio?
goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
Yes bricking your phone is when it wont even turn on! In the case of the sapphire when you hold power the led will flsh red quickly once then nothing.
On the blackstone you dont even get the pleasure of the led flash if your phone will turn on there is a way to get it fixed.
When ive been stuck on the bootscreen i have managed to revert using sappimg.nbh (which is 32b in my case) dunno where i got it from but i have it!
sappimg.zip (which is 32A) i got from Amon_RA's post and also have that, ive managed to revert back with both images after being stuck on "red screen of death"
A bit of a personal opinion here:
"Dead" is when the phone doesn't respond to anything, at all.
The charging light does not come on, the power button does nothing, and there is not so much as a flicker in the screen. Also, it is completely inaccessible for hardware debugging (JTAG, serial, USB or otherwise). This usually happens from a hardware problem, or doing something stupid like zero'ing the IPL.
Examples:
- My brother dropped his Nokia N75 in water. It's dead.
- I dropped my Cingular 8125 (HTC Wizard) on the ground. It doesn't power on any more, and plugging it into the charger does nothing. Voltmeter shows a charge running through some areas of the device's motherboard once disassembled. It's dead.
Solutions: Replace, recycle or sell for parts.
"Bricked" is when a purely software problem causes the device to no longer respond.
This may happen on many levels, but usually results in the OS not booting, or booting and being completely unusable (e.g. stopped with kernel panic at OS splash). It may light up and/or show a splash screen, but it fails to enter the bootloader or recovery menus. Its recoverability may vary, but will usually involve a debugging tool and a computer, and likely a copmlete wipe of everything on the device. Even if it's heavily bricked, if it can be recovered via JTAG or similar, it's not "dead".
Examples:
- HTC Dream only goes as far as splash screen, and freezes there. Does not respond to ADB. Does not enter recovery, or bootloader, however fastboot responds.
- HTC Dream shows blank screen, but lights up as if it were powering on. Fastboot does not respond. I connect my HTC ExtUSB Serial dongle to it though, and I'm able to get a response to some commands.
- Western Digital MyBook World Edition NAS powers on, and spins up hard drive, but does not go any farther than that. Front lights do not light up, and no hard disk activity is heard. Networking is not yet enabled. Hard drive can, however, manually be connected to a PC with SATA, and the firmware image re-written to its partitions.
- XBOX (the original) was softmodded, but the dashboard.xbe (the OS shell) was overwritten. It now just stays at the Microsoft logo.
- iPhone was recently jailbroken and SIM unlocked, then Apple pushed an update on me, and my iPhone is in a state where it doesn't enter DFU/Recovery, and when it boots, it says "Emergency calls only."
Solutions: Be very careful not to further brick the device, but use any methods available. Be sure to check documentations, search forums, and then ask questions if unsure. Make sure you finish every process you start.
After this, might just be hardware "damage" (like a power button not working right) or software "errors", like the home screen failing to load because of "Process com.google.android.gapps quit unexpectedly." These are usually relatively easy to fix, or have fixed.
Again, this is just an opinion.
Back on topic though, I seriously wouldn't have probably thought of using fastboot while it's stuck at the G1 screen, unless mine were bricked. Kudos to you, and I hope this works on some other bricked G1's out there (At least ones with the Engineering/Hard/DangerSPL, the stock SPL doesn't support fastboot as far as I know.)
bonesy said:
Yes bricking your phone is when it wont even turn on! In the case of the sapphire when you hold power the led will flsh red quickly once then nothing.
On the blackstone you dont even get the pleasure of the led flash if your phone will turn on there is a way to get it fixed.
When ive been stuck on the bootscreen i have managed to revert using sappimg.nbh (which is 32b in my case) dunno where i got it from but i have it!
sappimg.zip (which is 32A) i got from Amon_RA's post and also have that, ive managed to revert back with both images after being stuck on "red screen of death"
Click to expand...
Click to collapse
Won't agree with that, what you describe as a brick is a DEAD mobile. A brick is a useless piece which wont get into any state of recovery. The only thing i will agree with is that if it'll turn on there is a way to get it fixed that's why we even got the word unbricking which is done with many other pieces than Android mobiles.
Hope this will get us closer to a unbricking method which works on all the BRICKED pieces out there.
Good job dude!
Yes, my phone is back!
I bricked my G1 about 2 months ago pretty much the same way marcdbl did.
I gave up on it and sit it aside getting a new MT3G.
Sweet, now I got 2 phones to play with.
Thank You marcdbl
wow sweet news
fishman0919 said:
Yes, my phone is back!
I bricked my G1 about 2 months ago pretty much the same way marcdbl did.
I gave up on it and sit it aside getting a new MT3G.
Sweet, now I got 2 phones to play with.
Thank You marcdbl
Click to expand...
Click to collapse
Very glad to hear that your dead or bricked or whatever-you-may-call phone is back to LIVE!!!
So I think this solution works for some certain people. So i think rather than arguing on terminology, better spread this good trick to people who had dead/bricked/whatevery-you-may-call phone. IMHO
Thanks for the solution.
Best,
Thihaz
marcdbl said:
A few days ago I bricked my phone. I performed a SPL flash which seemed to go ok, the phone rebooted and then just stuck at the first splash screen. I waited for 30 minutes and it was still there.
I then removed the battery, reinserted it, and tried booting into recovery mode. Nothing happened, it just stuck at the first splash screen.
So I removed the battery again, reinserted it, and tried booting into fastboot mode. Nothing happened, it just stuck at the first splash screen.
I repeated these steps a few times with the same result.
I tried booting it with the USB cable attached, the result was the same, and Windows showed the phone as an 'unrecognized device'.
At this point, I was nearly crying, my phone was a brick.
Then, for some reason I tried the following:
-On the PC, i ran the command 'fastboot boot recoveryimage.img'.
-At this point the command says 'waiting for device' (or something like that).
-I removed the battery.
-I Connected USB.
-I inserted the battery.
-I booted the phone while holding the HOME key.
-The phone still froze at the first splash screen, but then suddenly, the waiting fastboot command detected the phone and booted the recovery image! Yay!
That's it. I didn't test it any more thoroughly for obvious reasons, I just reflashed the SPL and everything was back to normal.
I hope this helps someone in the future....
Click to expand...
Click to collapse
where were you 2 months ago dude? I paid 270€ to change the board on my magic
Good Job! Thanks for the info
I did all the steps to root the phone, 1 and 2, but got stuck in a bootloop. The sprint log stuff would come up, the the 4g, then back to sprint etc. I flashed the PC36IMG.zip of the shipped version, but now I can't get the RUU to take the phone into a fully factory state. It starts, then gets stuck waiting for bootloader with a black screen and htc on it. I really just want to make it factory again and start over with the root process. Any ideas?
Hold power and volume when turning on phone, then select fastboot and have the selection for bootloader highlighted, then start the RUU it should work then.
OK, so I tried the volume down + power btn deal, but still no dice. I really don't undestand wtf happened, cause before doing the 2nd part of root, I was able to load Damage ROM, now anything I load besides the PC36IMG.zip from part 1 just bootloops. Crazy
control_logic said:
I did all the steps to root the phone, 1 and 2, but got stuck in a bootloop. The sprint log stuff would come up, the the 4g, then back to sprint etc. I flashed the PC36IMG.zip of the shipped version, but now I can't get the RUU to take the phone into a fully factory state. It starts, then gets stuck waiting for bootloader with a black screen and htc on it. I really just want to make it factory again and start over with the root process. Any ideas?
Click to expand...
Click to collapse
ive seen this answered in the RUU threads. they mentioned the RUU doesn't automatically reboot the phone into the correct mode, i think it was bootloader? manually booting it into the correct mode, then connecting the USB, resolved the issue.
you might want to search/reference the RUU threads for more details as i never had the issue and am only recalling off the top of my head what ive read, which cant be 100% accurate!
When RUU stops/freezes and your phone has the black screen with "HTC" on it.... do not restart your phone or anything leave it the way it is. What you do is exit out of the RUU program by clicking "exit" when it freezes up. Then without doing anything to the phone, just restart the RUU program and it should pick up where it left off and complete the process. I found this fix in "Q and A" part of the Evo forum and it worked for me.
Sent from my PC36100 using Tapatalk
You need to format the phone rest and format cashe then install the rooted image and it will boot. I had the same problem.
Thanks for the responses, it is working again, YEAH!
I bought a Rogers HTC Magic for a pretty cheap price. It had The Rogers 1.5 Sense UI update on it. I decided I wanted to root it and load other ROMs, etc. So I read that the easiest method was to use Universal Androot to root it, and ROM Manager (from the Market) to flash the appropriate recovery image.
So, I installed both apps. I first ran Universal Androot and rooted. I confirmed root through ADB and also Super User permissions. I then restarted the phone just for peace of mind. After the restart, I ran ROM Manager. It automatically popped up and asked me if I was running an Ion/My Touch or an HTC Magic. I selected HTC Magic, because that's what this is. So then it flashed the recovery image and restarted the phone. When it restarted it went to the Rogers boot screen for a few seconds, and then started a loop of restarts. That's all it does now. It shows the Rogers screen for a few seconds, goes black and reboots over and over. I have tried booting into HBOOT, Fastboot, and into recovery. I cannot boot into any of them. One thing I did notice is that when I'm pressing any of the combinations (volume down + power, home + power, menu + power) for a very brief half a second right before the phone restarts, the bottom of the screen says "ClockwordMod ..." where ... is the version of the image (I'm at work without the phone, so I don't recall the exact number there).
So, is this thing officially a paperweight now, or is there some sort of hope?
Thanks.
Paul
Well, I don't know if you are full-bricked but here is what went wrong. The HTC Magic recovery is incorrect for the mytouch3g (at least the 32b). There was a top option for "saphire/mytouch 3g" which is what you should have chosen. So, you can't load the incompatible recovery. Can't you boot back into the rom you were using? The recovery flash shouldn't have messed with it. If you can, boot back in and flash the correct mytouch3g recovery in rom manager.
adrift02 said:
Well, I don't know if you are full-bricked but here is what went wrong. The HTC Magic recovery is incorrect for the mytouch3g (at least the 32b). There was a top option for "saphire/mytouch 3g" which is what you should have chosen. So, you can't load the incompatible recovery. Can't you boot back into the rom you were using? The recovery flash shouldn't have messed with it. If you can, boot back in and flash the correct mytouch3g recovery in rom manager.
Click to expand...
Click to collapse
Okay. That's weird. I mean, my phone is a Magic so choosing the option for the Magic instead of the Ion/MyTouch seemed to make sense.
Anyway, I cannot get anywhere. Holding vol+ and power does nothing, neither does home and power or back and power. Are there any other tricks to getting anywhere beyond this endless restart loop?
Thanks.
Starting to think I'm screwed.
PaulieORF said:
Starting to think I'm screwed.
Click to expand...
Click to collapse
You may be, I'm not sure exactly what state you are in but the recovery you installed was for a magic 32a (that you have) with a 3.x radio (that you don't have)
The rogers sense rom uses the 6.x hero radio and needs a hero recovery.
The mt3g uses a 2.x radio thus yet another recovery.
Try booting with volume down to see if you can get into the hboot/fastboot screen, but I think you tried this already.. you may also try letting it loop unplugged until the battery drains it may error out giving you access again..
Besides that there is the option of jtag and fixing the software stack that way.
ezterry said:
You may be, I'm not sure exactly what state you are in but the recovery you installed was for a magic 32a (that you have) with a 3.x radio (that you don't have)
The rogers sense rom uses the 6.x hero radio and needs a hero recovery.
The mt3g uses a 2.x radio thus yet another recovery.
Try booting with volume down to see if you can get into the hboot/fastboot screen, but I think you tried this already.. you may also try letting it loop unplugged until the battery drains it may error out giving you access again..
Besides that there is the option of jtag and fixing the software stack that way.
Click to expand...
Click to collapse
Thanks for the reply!
Right, I cannot get into fastboot or hboot. I'll try running the battery down when I get home today. Interesting idea.
Unfortunately running the battery dead with restarts didn't do the trick.
Any idea if there's any place I can send it to who has the smarts to jtag recover this thing?
Thanks.
me too
I did the same thing on a 32B. Rooted. loaded ROM Manager. Ran the recovery, I choose the Ion/MT3G option. tried to load CM6-FroyoRedux-v1.7-32b-blk.zip. Now it's stuck in the boot screen.
tmokeith said:
I did the same thing on a 32B. Rooted. loaded ROM Manager. Ran the recovery, I choose the Ion/MT3G option. tried to load CM6-FroyoRedux-v1.7-32b-blk.zip. Now it's stuck in the boot screen.
Click to expand...
Click to collapse
I don't think it's the same thing.
I rooted, loaded ROM Manager and installed the recovery. I was never even able to get into recovery in order to try to load any ROMs.
I have a Rogers magic, and its a 32a. One way to fix it is to go to the HTC website and punch in your serial number and download the rogers update. Only problem is that will make it a pain to root again. But should fix that reboot loop. But do that as a last resort to get the phone running again.
Sent from my HTC Magic using XDA App
nate_benji said:
I have a Rogers magic, and its a 32a. One way to fix it is to go to the HTC website and punch in your serial number and download the rogers update. Only problem is that will make it a pain to root again. But should fix that reboot loop. But do that as a last resort to get the phone running again.
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
The phone does not identify itself to the computer, so this doesn't work.
The program should try to put the phone into fastboot mode, and install the upgrade. Have you tried pulling the battery and pressing the power button + back, once the battery is installed again?
Sent from my HTC Magic using XDA App
nate_benji said:
The program should try to put the phone into fastboot mode, and install the upgrade. Have you tried pulling the battery and pressing the power button + back, once the battery is installed again?
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
Oh yes. I've gone crazy trying every key combination with every combination of taking battery out, plugging it in, USB cable attached, detached, etc.
The phone never identifies itself as a piece of hardware to the computer in the 5 seconds between reboots.
I had the same problem yesterday, and i was doing the same rooting with Universal Androot and flashing recovery witch Rom Manager (choose the same options). I tried to go into recovery and then it started to bootlooping the whole time.
I was pretty scared when that happens, can't open fastboot menu and the only thing that my phone was showing was HTC logo and a quick blink of clockwork sign over and over.
I don't know exactly how i managed to fix it, but it started to work when i quickly plug off baterry and i immiediatly plug it in (I was doing it at the exactly time when the phone reboots) while holding the power button.
Now my magic turns on, but recovery won't work (just flash for a moment, and reboots) and it always say at the beginning of booting system that SD card was removed which means i can't use any SD card.
I hope it somehow helped you.
naparstekk said:
I had the same problem yesterday, and i was doing the same rooting with Universal Androot and flashing recovery witch Rom Manager (choose the same options). I tried to go into recovery and then it started to bootlooping the whole time.
I was pretty scared when that happens, can't open fastboot menu and the only thing that my phone was showing was HTC logo and a quick blink of clockwork sign over and over.
I don't know exactly how i managed to fix it, but it started to work when i quickly plug off baterry and i immiediatly plug it in (I was doing it at the exactly time when the phone reboots) while holding the power button.
Now my magic turns on, but recovery won't work (just flash for a moment, and reboots) and it always say at the beginning of booting system that SD card was removed which means i can't use any SD card.
I hope it somehow helped you.
Click to expand...
Click to collapse
I tried doing this quickly for about 5 minutes this morning but didn't get it to go anyway. I can try some more after work today.
When you say it booted after this battery pull thing, do you mean the phone booted right into Android, or you were able to get to hboot or fastboot?
Thanks.
PaulieORF said:
I tried doing this quickly for about 5 minutes this morning but didn't get it to go anyway. I can try some more after work today.
When you say it booted after this battery pull thing, do you mean the phone booted right into Android, or you were able to get to hboot or fastboot?
Thanks.
Click to expand...
Click to collapse
I wasn't able to get hboot or fastboot. I pluged off and on the battery in the exact moment when the Logo came out after restarting. The logo was on the screen for the whole time, even while battery plugged off. I guess, i've done it so quickly that phone didn't switched off.
I think i was holding the power+home or power+back buttons all the time.
Can't really rember the exact way, sorry.
PaulieORF said:
I tried doing this quickly for about 5 minutes this morning but didn't get it to go anyway. I can try some more after work today.
When you say it booted after this battery pull thing, do you mean the phone booted right into Android, or you were able to get to hboot or fastboot?
Thanks.
Click to expand...
Click to collapse
Try removing the SD card and booting if its not restarting due to the wrong radio too soon that may help.. if you get into android restore the SD card and run the exploid process I posted a bit back for rogers magics, or the older goldcard method.
I've played around with taking the battery out and putting it right back in at all different times during the booting and can't get the phone to behave any differently. Iv'e tried it with SD card in and SD card out, USB cable in and USB cable out. I can't get anywhere.
I did notice that the phone does show up as an Android device for a second when it's booting. Tried to catch it in adb but no luck.
Starting to think this thing is shot. Any other ideas?
Just so everyone can see what's happening, I recorded a video and uploaded it. Linked below:
http://www.youtube.com/watch?v=hPoxMzm0MVU&hd=1
try to hold and KEEP holding the back + power... Not volume down!
Don't push and release like you did in the video.
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?