Related
Hello all,
I think I may have bricked my nexus one. It is completely my fault for attempting things that I knew little about, so flame away But after the flaming, if anyone is willing to help I would be sooooo thankfull...
I successfully rooted my phone following the instructions on this page: (all links edited with a double asterisk as I don't believe I can post links)
h**p://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
Then successfully installed cyanogenmod (which is awesome!) following this page:
h**p://theunlockr.com/2010/01/08/how-to-load-a-custom-rom-on-the-nexus-one/
All was well, I even got the modaco desire rom up and running, and was happily switching back and forth using the recovery screen. I had nand backups for specific setups, etc.
Then I decided it would be good to know how to go back to stock, and found this page:
h**p://**w.androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/
I followed the instructions to the letter (I think) except for erasing userdata (it said "failed: remote not allowed"). I thought that things would be ok, since I'd recently wiped, so I followed the page till the end.
The phone rebooted, and I got the original nexus boot animation - but it's in an endless loop! What's worse, it that now when I try to go to the bootloader or recovery mode, I get the exclamation triangle with the little android.
Is there any way through a command prompt (or other method) that I can fix this? I tried to re-flash the RA recovery image through the command prompt, but the response was, "waiting for device."
ANYTHING that anyone can suggest to help, I would be so thankful! I've been loving the nexus, and hate to think that I crippled it
Thanks in advance,
Randy
I doubt its bricked.
Noticed you didnt mention that fast boot doesnt work? (power button+trackball) try it.
Once you get to fastboot you can flash any ROM back. (fastboot flash **** commands from a command shell)
Did you ever perform a Nand Backup from Recovery?
It's not bricked, the only way to brick is to interrupt power when flashing a Radio image
Connect phone to PC. Open command prompt.
adb reboot recovery
Wipe, reflash.
So far, nobody has managed to brick a Nexus. There is no way as the fastboot mode can restore the whole phone and can't be messed with. Make sure you have the latest version of the SDK with correct USB drivers and fastboot. Then try and reflash the recovery image.
-------------------------------------
Sent from my Nexus One
nexus5894 said:
So far, nobody has managed to brick a Nexus. There is no way as the fastboot mode can restore the whole phone and can't be messed with. Make sure you have the latest version of the SDK with correct USB drivers and fastboot. Then try and reflash the recovery image.
-------------------------------------
Sent from my Nexus One
Click to expand...
Click to collapse
Actually...
http://forum.xda-developers.com/showpost.php?p=6320068&postcount=404
Paul22000 said:
Actually...
http://forum.xda-developers.com/showpost.php?p=6320068&postcount=404
Click to expand...
Click to collapse
............................
It worked!!!!!
It worked!!
britoso, thank you soooooo much! The only way that I knew to get into bootloader/recovery was via power button/volume down, but power/trackball brought up the bootloader screen, and I clicked on fastboot. I was able to flash the RA recover image through the command terminal via fastboot, then able to get into recovery. I had cyan and modaco sense on the sd, and was able to flash one of them on.
I never thought I'd be so happy to see "quietly brilliant"!!! I WILL buy you a beer, a case in fact as soon as money clears my paypal account.
I have learned my lesson, research research research. (I did do some, but not enough to feel comfortable with what I was doing - hence my cry for help!)
Other than the phone and OS itself, the thing I like most about the nexus is the fact that one CAN root, and then customize (sold a Telus moto droid because I could not do that very thing).
I digress... thanks again so much!
And Paul, thanks for your sense ROM; I've had HTC phones from the Touch to the the diamond to the Hero, and missed the UI!
Randy Malkoski said:
It worked!!
britoso, thank you soooooo much! The only way that I knew to get into bootloader/recovery was via power button/volume down, but power/trackball brought up the bootloader screen, and I clicked on fastboot. I was able to flash the RA recover image through the command terminal via fastboot, then able to get into recovery. I had cyan and modaco sense on the sd, and was able to flash one of them on.
I never thought I'd be so happy to see "quietly brilliant"!!! I WILL buy you a beer, a case in fact as soon as money clears my paypal account.
I have learned my lesson, research research research. (I did do some, but not enough to feel comfortable with what I was doing - hence my cry for help!)
Other than the phone and OS itself, the thing I like most about the nexus is the fact that one CAN root, and then customize (sold a Telus moto droid because I could not do that very thing).
I digress... thanks again so much!
And Paul, thanks for your sense ROM; I've had HTC phones from the Touch to the the diamond to the Hero, and missed the UI!
Click to expand...
Click to collapse
Glad to hear it. You learn the most by trial and error.
I think i got the same problem. i tried to Unlock Bootloader and Root Google Nexus One which was successful but then i tried to superboot it and when it came to the part where you "double click the ‘install-superboot-windows.bat’ file" i clicked it but it did not go to the nnext screen where the superboot completes it just stayed at the "bootloader screen". i must hve not done something or done something wrong i dont know.
So then i unplugged the phone from the pc and rebooted it. when it reeboted i wasnt getting any network, the phone was slow and the notification bar would not slide down...also i noticed the phone restarting on itself...
/i tried all kinds of "restore to factory settings" but not solved. Can anyone tell me what to do tht will work. I coud not understand what was said in the above thread as i am new to this android n my first time rooting n stuff n i believe that solution would work for me too..if some one could please explain in simple tirms the steps i need to take would be good...
Really appreciate it....
revonomics said:
I think i got the same problem. i tried to Unlock Bootloader and Root Google Nexus One which was successful but then i tried to superboot it and when it came to the part where you "double click the ‘install-superboot-windows.bat’ file" i clicked it but it did not go to the nnext screen where the superboot completes it just stayed at the "bootloader screen". i must hve not done something or done something wrong i dont know.
So then i unplugged the phone from the pc and rebooted it. when it reeboted i wasnt getting any network, the phone was slow and the notification bar would not slide down...also i noticed the phone restarting on itself...
/i tried all kinds of "restore to factory settings" but not solved. Can anyone tell me what to do tht will work. I coud not understand what was said in the above thread as i am new to this android n my first time rooting n stuff n i believe that solution would work for me too..if some one could please explain in simple tirms the steps i need to take would be good...
Really appreciate it....
Click to expand...
Click to collapse
Tell me what i need to download again and how to go about it...i really need my phone working again ((((
So I went ahead and just did it ran the ruu. So i been trying ways to unroot this as much as my not so experienced self is. Well first i tried to replace the rom.zip with an older one as if that was done it would be the easiest way. well replaced it but it didn't successfully flash once it got to the flash bootloader part. Then I booted to recovery and first thing it said was E:can't archive /cache/recovery/command. So I tried to apply update.zip it started to go through but got a signature failure. Anyways any help with this would be great
new pri 2.20_003
thatguythatdid said:
So I went ahead and just did it ran the ruu. So i been trying ways to unroot this as much as my not so experienced self is. Well first i tried to replace the rom.zip with an older one as if that was done it would be the easiest way. well replaced it but it didn't successfully flash once it got to the flash bootloader part. Then I booted to recovery and first thing it said was E:can't archive /cache/recovery/command. So I tried to apply update.zip it started to go through but got a signature failure. Anyways any help with this would be great
new pri 2.20_003
Click to expand...
Click to collapse
Throw it into the toilet and get a warranty replacement quick, before all the phones have 2.1.
Other then that, the only way to find root would be to have a good knowledge of linux, kernels, c, etc, and find known linux exploits and go down the list and try them.
robchaos said:
Throw it into the toilet and get a warranty replacement quick, before all the phones have 2.1.
Other then that, the only way to find root would be to have a good knowledge of linux, kernels, c, etc, and find known linux exploits and go down the list and try them.
Click to expand...
Click to collapse
I'm getting a new one today from craigslist so if I never post again then I'll be one of those when craigslist goes wrong stories on the news.
Also I never got the warranty from sprint I got the warranty from radioshack because they said that they cover everything but water damage. So right before I threw it off my roof I called radioshack to make sure they would cover it they said they only cover wear and tear and software.
I still would like to know how to make an sign an update zip though so I can flash it through recovery.
thatguythatdid said:
I'm getting a new one today from craigslist so if I never post again then I'll be one of those when craigslist goes wrong stories on the news.
Also I never got the warranty from sprint I got the warranty from radioshack because they said that they cover everything but water damage. So right before I threw it off my roof I called radioshack to make sure they would cover it they said they only cover wear and tear and software.
I still would like to know how to make an sign an update zip though so I can flash it through recovery.
Click to expand...
Click to collapse
First of all, do you have mac or windows?
Doesn't matter, The RUU removes root and the ability to flash a custom recovery, doesn't it?
HeroMeng said:
First of all, do you have mac or windows?
Click to expand...
Click to collapse
Sorry messing with the phone. I got a pc windows 7 64 blah blah. I did try to manual update but it wont let me because it says that main version is older.
robchaos said:
Doesn't matter, The RUU removes root and the ability to flash a custom recovery, doesn't it?
Click to expand...
Click to collapse
Yes and no. While in the new recovery it gives you the ability to flash an update zip from your sd but I get signature fails if I could fake the signature then I could flash a rooted rom and carry out from there putting a new recovery image and so fourth
thatguythatdid said:
Yes and no. While in the new recovery it gives you the ability to flash an update zip from your sd but I get signature fails if I could fake the signature then I could flash a rooted rom and carry out from there putting a new recovery image and so fourth
Click to expand...
Click to collapse
What happens if you try flashing any of the released roms out there, like fresh rom? It is signed using test keys. That would be crazy if the new recovery lets you flash any signed rom, but I predict it's locked down to HTC's keys which are privately encrypted keys. You can't fake them.
flipzmode said:
What happens if you try flashing any of the released roms out there, like fresh rom? It is signed using test keys. That would be crazy if the new recovery lets you flash any signed rom, but I predict it's locked down to HTC's keys which are privately encrypted keys. You can't fake them.
Click to expand...
Click to collapse
I've tried only tried a couple so far it takes a sec though cuz I gotta reboot to put anything on and I'll try the fresh 2.0d
Justg tried the original fresh 2.od and got signature verification failed
Going to pick up my new phone so if any body has anyideas on how to root this when I get back let me know. When we gonna get a leak that lets you sign with htcs keys
thatguythatdid said:
Going to pick up my new phone so if any body has anyideas on how to root this when I get back let me know. When we gonna get a leak that lets you sign with htcs keys
Click to expand...
Click to collapse
It should be 1.5, so just root it w/ http://forum.xda-developers.com/showthread.php?t=583291 and you'll be good to go.
thatguythatdid said:
Going to pick up my new phone so if any body has anyideas on how to root this when I get back let me know. When we gonna get a leak that lets you sign with htcs keys
Click to expand...
Click to collapse
i may be crazy.... but if we find a way to root this 2.1 before they release it couldn't they then patch that exploit? maybe this is why they "leaked" it so we could have a chance to find any holes or exploits in the software/bootloader/recovery?
regaw_leinad said:
It should be 1.5, so just root it w/ http://forum.xda-developers.com/showthread.php?t=583291 and you'll be good to go.
Click to expand...
Click to collapse
I meant the one with the 2.1 on it
thedudejdog said:
i may be crazy.... but if we find a way to root this 2.1 before they release it couldn't they then patch that exploit? maybe this is why they "leaked" it so we could have a chance to find any holes or exploits in the software/bootloader/recovery?
Click to expand...
Click to collapse
you may be right I thought of it but I don't know how clever they are considering how long it's taken them to put out the same rom we had back in march
thatguythatdid said:
I meant the one with the 2.1 on it
Click to expand...
Click to collapse
Oh, sorry my bad
regaw_leinad said:
Oh, sorry my bad
Click to expand...
Click to collapse
No problem . I'm glad that devs are looking at this maybe we can have a solution before the problem
sandboxlove said:
so the new recovery lets you flash updates? their just asking for us to better their software, jesus...
Click to expand...
Click to collapse
What like their gonna do it? I heard the ssamsung 2.1 update didn't even have live wallpapers
go to cyanogens wiki page. and find where he manually replaces the /radio partition.
if you have fastboot you can manually replace every partition this way. including /recovery.
just an idea.
Avalaunchmods said:
go to cyanogens wiki page. and find where he manually replaces the /radio partition.
if you have fastboot you can manually replace every partition this way. including /recovery.
just an idea.
Click to expand...
Click to collapse
Thanks for the idea just got my new phone still got the old one so I'm definitley gonna try some things now. Before I root the new one is there any info or anything someone might want from it. I don't know if it can help someone but it might. I'll wait till tonight to do it
Avalaunchmods said:
go to cyanogens wiki page. and find where he manually replaces the /radio partition.
if you have fastboot you can manually replace every partition this way. including /recovery.
just an idea.
Click to expand...
Click to collapse
Sweet link bro!
So I've apparently, effectively bricked my phone. Under bootloader it is listed as S-OFF. Is there any way I can return my evo in and stay under warranty?
Note: I can not reach recovery.
What happens when you rename a recovery to PC36IMG.zip and try to update via bootloader?
I go into a boot loop no matter what i do, no matter what I flash. I have flashed 10+ PC36IMGs with everything from bootloaders to recoveries, to every img that can be on the phone... there is a thread still on the first page if you want to look at that.
Anyways, it doesn't look like I'm going to be able to fix it, so this is more about what options are available to me in getting a new phone, if you having any suggestions though on what I can do to fix mine, please be my guest and comment on my thread below, I'm still trying to fix it!
Just report the phone lost or stolen and pay $100 deductible.
Sent from my PC36100 using XDA App
I would try one last time to flash Amon's recovery.
Download this: http://forum.xda-developers.com/attachment.php?attachmentid=483320&d=1294435056
Rename it to "PC36IMG.zip"
put it on the root of your sd card via a card reader if you have one or someone elses phone.
then update via bootloader.
Other than that I'm out of ideas. The good news is I'm not as savvy as 95% people on here, which means someone much smarter than me might know the answer. Good luck.
Hmm, yeah I may just have to pay the 100 then... but is that an insurance thing or a warranty thing? I don't have insurance
Do you think Sprint will even check for the S-ON?
thanamesjames said:
Hmm, yeah I may just have to pay the 100 then... but is that an insurance thing or a warranty thing? I don't have insurance
Do you think Sprint will even check for the S-ON?
Click to expand...
Click to collapse
i dont think its a warranty thing its insurance and i think your screwed
What happens when you put a pc36img.zip file on the root of your SD card and start up in bootloader?
I appreciate the people trying to help me... but honestly i've flashed a ridiculous amount of PC36IMGs. Both boot.img and recovery.img and then much more. This is more about, is there anyway I can return it to sprint and get another under warranty. Sounds like i'm out of luck.
So you cleared all the caches?
thanamesjames said:
I appreciate the people trying to help me... but honestly i've flashed a ridiculous amount of PC36IMGs. Both boot.img and recovery.img and then much more. This is more about, is there anyway I can return it to sprint and get another under warranty. Sounds like i'm out of luck.
Click to expand...
Click to collapse
What did you do that caused this issue? Or what were you trying to do? Also what hboot version do you have?
I've done "clear storage" I don't see a place to clear anything other than that in hboot.
thanamesjames said:
I appreciate the people trying to help me... but honestly i've flashed a ridiculous amount of PC36IMGs. Both boot.img and recovery.img and then much more. This is more about, is there anyway I can return it to sprint and get another under warranty. Sounds like i'm out of luck.
Click to expand...
Click to collapse
Pretty much. If you haven't tried yet, try re-rooting via toast's method.
http://forum.xda-developers.com/showthread.php?t=690762
Try going through the whole process. If successful make sure you have a nice stock ROM like the current Sprint Lovers ROM to flash.
Unfortunately my phone isn't getting listed as a device under adb, and thats part of the toast tutorial I have tried his eng-PC36IMG.zip, and it didn't work
woah woah woah....
take your phone to wal-mart and slide it over the demagnetizer at the register a couple times.
THAN take it in.
_MetalHead_ said:
What did you do that caused this issue? Or what were you trying to do? Also what hboot version do you have?
Click to expand...
Click to collapse
I had nightlies of CM7 they would reboot fairly often, but I just figured they were unstable. Out of nowhere it rebooted, and lost all my texts, and desynced my google account. I decided to switch to CM6. When i switched to CM6, soon after it rebooted out of nowhere, and then staid in an endless loop and never came out. I currently have hboot .76, for more fastboot commands.
Try this PC36IMG.zip. If it doesn't work the first time then try it again. If it doesn't work the second time, then I would say you're SOL. I know you said you've tried a bunch but they aren't all the same. It's the sprintlover's full update ROM.
_MetalHead_ said:
Try this PC36IMG.zip. If it doesn't work the first time then try it again. If it doesn't work the second time, then I would say you're SOL. I know you said you've tried a bunch but they aren't all the same. It's the sprintlover's full update ROM.
Click to expand...
Click to collapse
Is it from here? http://forum.xda-developers.com/showthread.php?t=830153
If so I've tried it
thanamesjames said:
Is it from here? http://forum.xda-developers.com/showthread.php?t=830153
If so I've tried it
Click to expand...
Click to collapse
Yep :/ I don't know what to tell you then man, sorry.
I guess I'm going to Sprint and playing stupid!
Has anyone done this successfully?
It sucks because as soon as I started having these problems, all the experts would be frustrated and say "*sigh* you're not bricked, you can get into bootloader" and so I was so sure it was fixable... but apparently not. Every time I mention it I have a thousand people yell at me "FLASH PC36IMG!!" Anyways thanks for the help!
I understand that there are similar threads out there but I still can't seem to figure it out. I apologize ahead of time for any wrong terminology, I'm pretty new to all of this. To give a background on what happend, I started my day off by rooting my phone with the following link (I had tried a different method with visionary plus and terminal but it wouldn't work)
http://forum.xda-developers.com/showthread.php?t=858996
this method worked just fine and gave me s=off, currently what I have is as followed:
Glacier PVT ENG S-OFF
HBOOT-0.85.2007 (pd1510000)
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
After gaining my root I was excited to try and flash a new rom. I installed the clockwork rom manager from the market, flashed the recovery then backed up my current in case of future problems.
Next step for me was to flash a new rom. for this I followed
http://forum.xda-developers.com/showthread.php?t=1070444
everything seemed to be going fine, phone restarted and I sat waiting (since I read the first boot could take 10min or so) after at least an hour I began to worry. Nothing happened, just stayed on the mytouch 4g startup screen and never changed.
I rebooted into recovery to try again, I can get into my hboot and into clockwork Mod Recovery v3.0.2.4 just fine. but there are a whole bunch of errors I cant fix. When clockwork starts I get the errors
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
If I try to format anything (cache, system...) it will say
Formatting /cache... (or system depending on what I am trying)
Error formatting /cache! (or system)
If I try to restore to a previous time it will start to do the restore, it will first do the boot which goes fine, but when it tries to format the system during the restore it fails just like if trying to format it individually.
At this point I would just like to get my phone working, any help would be much appreciated. (please try and use details so I can follow... still trying to learn alot)
I hate to be the bring of bad news, and remember don't kill the messenger, but it sounds as if your phone is truly bricked. There have been several threads on this already. As i know you are aware of. And very few, if any, have recovered.
There is a thread Posted here that boils down to the fact if the VISIONary.apk & root.sh method do not work then you have a bad eMMC.
Since it appears your phone does have a bad eMMC, hope you have insurance on it.
neidlinger said:
hope you have insurance on it.
Click to expand...
Click to collapse
neidlinger- i happen to have bought the insurance for 6 bucks a month or whatever it was - they said it extends the mfr warranty another year and then it gives you drop-in-toilet etc insurance with around a 120$ deduc.
I'm with t-mobile and got the phone thru the mail. If I take this back to a local TMO store for warranty claim, there's no difference is there? (i.e. you dont have to follow the mail route just because that's how you got it originally)
also- would these cache mount or failed -pu errors, essentially beyond repair - are we getting these to be recognized as hardware failure (i.e. no deductabel and counted as a mfr defect) or are these coming up as TMO insisting on counting them as some user fault, requiring the deductable to be paid??
acsi007 said:
neidlinger- i happen to have bought the insurance for 6 bucks a month or whatever it was - they said it extends the mfr warranty another year and then it gives you drop-in-toilet etc insurance with around a 120$ deduc.
I'm with t-mobile and got the phone thru the mail. If I take this back to a local TMO store for warranty claim, there's no difference is there? (i.e. you dont have to follow the mail route just because that's how you got it originally)
Click to expand...
Click to collapse
9/10 times if you buy a phone through the mail you will have to exchange it through the mail they will not allow you to walk into a store and do the exchange. I ran into that with my blackberry 9700.
acsi007 said:
also- would these cache mount or failed -pu errors, essentially beyond repair - are we getting these to be recognized as hardware failure (i.e. no deductabel and counted as a mfr defect) or are these coming up as TMO insisting on counting them as some user fault, requiring the deductable to be paid??
Click to expand...
Click to collapse
nope there is not way around it. once the eMMC fails it's down for the count.
neidlinger said:
I hate to be the bring of bad news, and remember don't kill the messenger, but it sounds as if your phone is truly bricked. There have been several threads on this already. As i know you are aware of. And very few, if any, have recovered.
There is a thread Posted here that boils down to the fact if the VISIONary.apk & root.sh method do not work then you have a bad eMMC.
Since it appears your phone does have a bad eMMC, hope you have insurance on it.
Click to expand...
Click to collapse
Is there any way to tell if the eMMC is bad. the visionary install went fine, just using the terminal to do the sh root.sh command wouldnt work, it would just keep saying failed (function not implemented) which is why I switched to visionary and adb gfree method... which worked like a charm, not a single hickup with it. the problems didnt start coming until after the rom instillation didnt work
hiddentalnt said:
Is there any way to tell if the eMMC is bad. the visionary install went fine, just using the terminal to do the sh root.sh command wouldnt work, it would just keep saying failed (function not implemented) which is why I switched to visionary and adb gfree method... which worked like a charm, not a single hickup with it. the problems didnt start coming until after the rom instillation didnt work
Click to expand...
Click to collapse
i see you didn't read the thread i posted.
The link i posted is to a thread here @ XDA, called "Post your eMMC serial number". It has alot of information regarding this very subject, including how to tell if your eMMC is indeed a faulty one [ by serial number ].
it really doesn't matter when the problem happens. it just matters that it happened.
./gfree is basically forcing the rooting process to happen while the root.sh is asking for it to happen. If the root.sh process doesn't allow you to proceed, then you may have a faulty eMMC. you forced the phone to root and opened up a bee hive in the process.
yeah sorry, I posted and then was just reading that forum as you replied... sorry about that.
hiddentalnt said:
yeah sorry, I posted and then was just reading that forum as you replied... sorry about that.
Click to expand...
Click to collapse
no need to tell me your sorry, . If you want to make me mad tell me Popeye's Chicken is out of business. we all start out somewhere. Just be willing to read prior to doing anything or asking anything. Chances are there is an answer somewhere. Sometimes we like what we read and sometimes we don't either way it's out there.
Hiddentalnt, please post your eMMC serial. We need people who have recovery errors to post what serial they have so we can actually pinpoint the problem being the chip. Thanks. The instructions are posted in the thread neidlinger posted above. Thanks
xdviper said:
Hiddentalnt, please post your eMMC serial. We need people who have recovery errors to post what serial they have so we can actually pinpoint the problem being the chip. Thanks. The instructions are posted in the thread neidlinger posted above. Thanks
Click to expand...
Click to collapse
I just tried to run that command but nothing comes up after it. I dont know if im inputing it in wrong but im currently trying to figure it out... Ill post once I find it. if any advice on why after running the command it just repeats the line, then nothing let me know
hiddentalnt said:
I just tried to run that command but nothing comes up after it. I dont know if im inputing it in wrong but im currently trying to figure it out... Ill post once I find it. if any advice on why after running the command it just repeats the line, then nothing let me know
Click to expand...
Click to collapse
after you got ADB installed and you punch in adb devices does it give you a serial number?
hiddentalnt said:
I just tried to run that command but nothing comes up after it. I dont know if im inputing it in wrong but im currently trying to figure it out... Ill post once I find it. if any advice on why after running the command it just repeats the line, then nothing let me know
Click to expand...
Click to collapse
nevermind... just got it M4G2DE
so from what Im reading...theres no coming back from this, the chip is dead?
hiddentalnt said:
nevermind... just got it M4G2DE
so from what Im reading...theres no coming back from this, the chip is dead?
Click to expand...
Click to collapse
pretty much.
I do know one guy was able to via flashing an older recovery image via the hBoot, but you have to have the .85 engineering screen. Which you do not have.
neidlinger said:
pretty much.
I do know one guy was able to via flashing an older recovery image via the hBoot, but you have to have the .85 engineering screen. Which you do not have.
Click to expand...
Click to collapse
what is the .85 engineering screen, i do have hboot - 0.85.2007 but im assuing thats different.
So its time to call up TMO and have them send me out a new phone? do I need to unroot first so they dont find it?
hiddentalnt said:
what is the .85 engineering screen, i do have hboot - 0.85.2007 but im assuing thats different.
So its time to call up TMO and have them send me out a new phone? do I need to unroot first so they dont find it?
Click to expand...
Click to collapse
Well you need to flash the 2.5.x.x recovery image for the mytouch4g from the hBoot, then reboot then navigate to the recovery and pray that it works. If it loads you might be able to load a new ROM but i only know of one case where that worked.
neidlinger said:
Well you need to flash the 2.5.x.x recovery image for the mytouch4g from the hBoot, then reboot then navigate to the recovery and pray that it works. If it loads you might be able to load a new ROM but i only know of one case where that worked.
Click to expand...
Click to collapse
sorry for asking so many questions. but you really have been a great help. do you have any idea where i can find the 2.5.x.x recovery image, I've been trying to look but I cant find it, just didn't know if you already knew of a forum that had it.
hiddentalnt said:
sorry for asking so many questions. but you really have been a great help. do you have any idea where i can find the 2.5.x.x recovery image, I've been trying to look but I cant find it, just didn't know if you already knew of a forum that had it.
Click to expand...
Click to collapse
I've got it store on my Lunix computer at home. I do not have it on my phone or on my work computer.
sorry. I can post it later on tonight.
neidlinger said:
I've got it store on my Lunix computer at home. I do not have it on my phone or on my work computer.
sorry. I can post it later on tonight.
Click to expand...
Click to collapse
Thanks, I appreciate it. I'm off to class anyways so I have to put a pause on trying to fix it till then.
neidlinger said:
Well you need to flash the 2.5.x.x recovery image for the mytouch4g from the hBoot, then reboot then navigate to the recovery and pray that it works. If it loads you might be able to load a new ROM but i only know of one case where that worked.
Click to expand...
Click to collapse
I would be that ONE case where this option did work. And the difference I have seen between the first time when flashing CWM worked and the second time (when it DIDN'T work) is the COMMAND error. If your CWM says anything about COMMAND error then flashing the old CWM isn't gonna work.
Here is a link to a post I made with a download for the old CWM
http://forum.xda-developers.com/showthread.php?p=14069400#post14069400
have any questions PM me if needed. Hit the Thanks button to if any of us have helped you at all.
Good luck man, I have a 450 dollar batter charger right now, so you'll need it :/
dcwiker05 said:
I would be that ONE case where this option did work. And the difference I have seen between the first time when flashing CWM worked and the second time (when it DIDN'T work) is the COMMAND error. If your CWM says anything about COMMAND error then flashing the old CWM isn't gonna work.
Here is a link to a post I made with a download for the old CWM
http://forum.xda-developers.com/showthread.php?p=14069400#post14069400
have any questions PM me if needed. Hit the Thanks button to if any of us have helped you at all.
Good luck man, I have a 450 dollar batter charger right now, so you'll need it :/
Click to expand...
Click to collapse
I'm not sure I fully understand your directions in the other thread. So when i download the zip, i get inside it and go all the way to recoveries to get out one of the disc image files. which one do I want, there is a 2.5.1.3 and 2.5.1.4 and a 3.0.0.5 but I'm assuming thats not it... but once I get one of those I rename it recovery.img then i use abd to push it... what is the command to push it? and i have to be in hboot then fastboot to push it?
I know this is possible depending on the phone, but on the Vibrant I have not found a way to install clockwork mod without using USB. I saw that mobile odin was an option for some samsung phones but not the Vibrant.
My usb port is dead, no warranty etc. I bought it for 70 in like new condition with knowledge that the port was bad. I figured that the port needed to be soldered back down. But after taking the phone apart, I don't see anything wrong with it. Its not loose on the board, but the socket itself is loose inside.
The baseband is KA2 Eclair. I got it rooted with the oneclickroot tool.
On a side note, the phone also came with pictures of the seller and all his girlfriends naked . Not pretty
So let me review what you want to do, you want to install CWR without having a USB port. Seems easy enough.
Firstly, find a app that will let you connect to your phone to your computer, apps like Dropbox, Box, and this app i put up on these forums a bit ago will do more than just the job HERE
install one of those, which ever you like. I'll use the MIUI File Manager as a example throughout this post because its the easiest.
Open the app, go to the FTP and start service, go to your computer open MY COMPUTER and type in ftp://all your #'s
Put this file in your ROOT meaning just in sdcard/ no folders just drag and drop it in there. DO NOT RENAME,EXTRACT OR ANYTHING TO THE .ZIP just put it in the sdcard/
*Thanks for the CWR file from Woodrube and S15*
Now go into Recovery mode on your phone
Power + Volume up and down ( i think )
Press REINSTALL PACKAGES
It SHOULD say something like booting into clockwork recovery.
it will reboot, if it goes to clock work recovery, GREAT. If not, press Reinstall Packages AGAIN and it should directly go there.
Just reply if i'm explaining something wrong or if you need more help.
Or you could just download and install rom manager and flash clockworkmod through there. No offense xriderx, just seems like a lot of work to just install cwr that a single app can do as well.
djquick said:
Or you could just download and install rom manager and flash clockworkmod through there. No offense xriderx, just seems like a lot of work to just install cwr that a single app can do as well.
Click to expand...
Click to collapse
To each his own, Rom Manager never has worked great on my phone. Even bricked it completely once and I don't believe it was user error.
Relevant guide, +1 cookie. One suggestion though, organize the steps a bit further so there is a clear distinction between steps.
ie:
• Now go into Recovery mode on your phone, Power + Volume up and down ( i think )
• Press REINSTALL PACKAGES. It SHOULD say something like booting into clockwork recovery. it will reboot, if it goes to clock work recovery, GREAT. If not, press Reinstall Packages AGAIN and it should directly go there."
Anywho, to the OP: Since it's rooted, why aren't you simply downloading ROM Manager from the market and installing CWR from there?
edit/ beaten
Don't get me wrong, your tutorial is spot on, I just never had any problems with ROM manager before so I threw it out as a suggestion.
Sent from my Nexus S using xda premium
working on it now, big thanks!
TheEnternal said:
working on it now, big thanks!
Click to expand...
Click to collapse
As far as the port goes, Eugene, Krylon360 and myself all fried ours when we were porting the V4G - so you may not visibly see anything wrong with it at all.
Thanks guys, I ended up semi bricking the phone . Even though it was my 6th droid device. Not sure what I did, I was in recovery and everything was working, then went to reboot and it was stuck on the Galaxy screen, could no longer get into recovery. Too bad that USB port was out . I ended up just reselling it to a guy for parts and still made some profit off it. Shame though, that AMOLED display was beautiful. Ended up getting a G2X yesterday for 195, just missed one at 150 on craigslist. Already got it up with CM 7.2 with a minor OC. Hopefully towards then end of this year I might be able to get a Galaxy 2 for cheap.
hi.
pls need help.
have the same phone. my usb is not working too.
t-mobile vibrant t959.
its CM7.2 skang-kang flashed.
have issue with mute-unmute.
and need to get it back to froyo.
how to do it without usb?
card slot is working fine.
zukko said:
hi.
pls need help.
have the same phone. my usb is not working too.
t-mobile vibrant t959.
its CM7.2 skang-kang flashed.
have issue with mute-unmute.
and need to get it back to froyo.
how to do it without usb?
card slot is working fine.
Click to expand...
Click to collapse
Download the files you need to your phone and flash them
Sent from my HTC Sensation 4G using XDA
johnson8cyl said:
Download the files you need to your phone and flash them
Sent from my HTC Sensation 4G using XDA
Click to expand...
Click to collapse
i have tried this.
but gingerbread loader and froyo loader are different.
it gave an error at flashing and stopped flashing.
Hmmm. That would require fastboot huh. Don't know of a wireless way to use that. Is there an unroot procedure you could do from your sdcard without a cord and then re-root to gb perhaps?
Sent from my HTC Sensation 4G using XDA
and i'm asking for something like this.
but i ask for froyo not unroot.
to flash from sd card.
it gives an error
Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in Android 1.5
it was necessary to remove it when upgrading to the clockworkMod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and updare-binary) to create working update zip packages.
installation aborted.
I don't think it is possible to downgrade to froyo from CM7 without ODIN. I might be wrong but that is how i remember it.
Though i did find this thread..
http://forum.xda-developers.com/showthread.php?t=1149158
But i don't know how that worked for people. You might wanna research a little bit more. IMO you are better off going to ICS.
Br1cK'd said:
Just use Odin, don't shortcut it. The OP here has a very very basic idea of the reason and necessity to change these files, and has not provided a complete set of steps in two different "guides" he has posted here, and nobody has been successful as per the reports.
Bottom line, save both yourself and dev in the future a headache, and just use Odin.
Click to expand...
Click to collapse
its very sad ((((
Just a reminder to some who have USB port problems. I'm not trying to insult anyone's intelligence here but remember Samsung phones are picky about USB cables.
I know because my phone was Semi bricked while doing Odin. Turned out my original Samsung cable went bad halfway through Odin'ing a new bootloader. After two months of playing with it I tried literally 5 different data cables that all fully worked for other phones and a few cheap off the street cables. Some would not even charge my vibrant but would work fine for data and charge on my wife's LG Quantum. Hard to find good micro-USB cables here in Peru. Finally I ended up modifying my original cable with another cable's micro-usb connector and wrapping a separate ground wire around the shield to get it to work. Samsung phones must require really good shielding to communicate and possibly not all cables have the shield connected on both sides or are properly shielded.
zukko said:
hi.
pls need help.
have the same phone. my usb is not working too.
t-mobile vibrant t959.
its CM7.2 skang-kang flashed.
have issue with mute-unmute.
and need to get it back to froyo.
how to do it without usb?
card slot is working fine.
Click to expand...
Click to collapse
Check out 'mobileODIN' on the market.