Related
Hi, I know I F** up so Im sending my G1 to tmo today but I just want to share my problem with yall so that I wont F** up in the future.
I am super dumb so spare the shotouts please..
I have a G1 that does the following:
Power button = stays booting with Tmo image for ever....
Camera+power = Flashscreen but when I try to flash image it shows not allow...with red numbers 0007002 I think..
Home + Power = 3 options --> 1. Reboot (works) 2. Update (won`t work it says cache/recovery/command not found) 5,215,715 etc files not known. 3. Wipe (works as far as I know).
Also combination Home + back button = back to fabric installation works says press send to go further. But when it restarts does nothing my phone stays loading the tmo image till battery is empty.
The story: I tried to update a zip for hero from youtube and after that nothing worked anymore.
(I did not follow all the steps- bcuz I am stupid!)
What kind of mule am I??????? A big one!
What have I done wrong and is there any point in sending the device to tmo or should I trow it in the trashcan?
Peace and thanks for the laughs
dizzydix said:
Hi, I know I F** up so Im sending my G1 to tmo today but I just want to share my problem with yall so that I wont F** up in the future.
I am super dumb so spare the shotouts please..
I have a G1 that does the following:
Power button = stays booting with Tmo image for ever....
Camera+power = Flashscreen but when I try to flash image it shows not allow...with red numbers 0007002 I think..
Home + Power = 3 options --> 1. Reboot (works) 2. Update (won`t work it says cache/recovery/command not found) 5,215,715 etc files not known. 3. Wipe (works as far as I know).
Also combination Home + back button = back to fabric installation does nothing my phone stays loading the tmo image till battery is empty.
The story: I tried to update a zip for hero from youtube and after that nothing worked anymore.
(I did not follow all the steps- bcuz I am stupid!)
What kind of mule am I??????? A big one!
What have I done wrong and is there any point in sending the device to tmo or should I trow it in the trashcan?
Peace and thanks for the laughs
Click to expand...
Click to collapse
What was the update you were trying to flash and what were the steps you took prior to that?
Hi Supremeteam
I took all the files from youtube link
http://www.youtube.com/watch?v=_dxB_qvM2KU&feature=related
VIDEO NAME: Hero Rom on G1---Jachero 2.3.6-----There is a difference between Theme and Rom.
I DID NOT FOLLOW ALL STEPS!
I think it went dead after I updated the radio or spl. I read somewhere on xda that you must radio first before spl. Maybe that is the problem that I have. BUt I am not sure as I was flashing all day long just to get a hero theme. So I dont know all the steps I did (stupid again)
Thanx
Download THIS reformat sd card to FAT32 using your computer and sdcard reader. put the file on the sdcard. boot using camera+power.
Hi there Fingerlickin
Fingerlickin said:
Download THIS reformat sd card to FAT32 using your computer and sdcard reader. put the file on the sdcard. boot using camera+power.
Click to expand...
Click to collapse
I did this a copple of times but it says: not allow ... (and then the red numbers above somthing like 0072008 etc.)
I also tried RC7 but still same error.
I tried to make a goldcard, but I won`t flash, same error.
I dont want to spil anyone`s time so I dont think we can repair the G1 but what I want with this thread is to get the cause of this all.
Is it because I did not follow all the steps?????
Bcuz then I hope every dumbass like me reads this thread before they crush their G1 also.
I knew there was a chance of F**ing up so I took a risk and I`m not crying but I just want tips for the future and to prevent more people of doing such a dumb thing.
Thanx guys
Well if you can get into recovery and bootloader your not bricked. Is your phone rooted? What have you done to it so far? This can prolly be fixed if you can provide us the info we need.
supremeteam256
supremeteam256 said:
Well if you can get into recovery and bootloader your not bricked. Is your phone rooted? What have you done to it so far? This can prolly be fixed if you can provide us the info we need.
Click to expand...
Click to collapse
Ok, 2 days ago was the first time I changed anything from Tmo to custom.
My first modification was: http://www.youtube.com/watch?v=cfskzfjOMgc
How To Root Android in 1 Click
This worked like a charm and was perfect.
After that I installed
http://forum.xda-developers.com/showthread.php?t=538762
[THEME] HE-AERO v1.6 - 4.0.4/4.1.11.1*Now with Stericson Lockscreen*[9/20]
I had a black panel above my screen and was very happy. Because that is all I wanted.
Then I got greedy and wanted the rom from POST 1.
And then I got all the errors from Post 1.
So really, that is all I can think of I did.
dizzydix said:
Ok, 2 days ago was the first time I changed anything from Tmo to custom.
My first modification was: http://www.youtube.com/watch?v=cfskzfjOMgc
How To Root Android in 1 Click
This worked like a charm and was perfect.
After that I installed
http://forum.xda-developers.com/showthread.php?t=538762
[THEME] HE-AERO v1.6 - 4.0.4/4.1.11.1*Now with Stericson Lockscreen*[9/20]
I had a black panel above my screen and was very happy. Because that is all I wanted.
Then I got greedy and wanted the rom from POST 1.
And then I got all the errors from Post 1.
So really, that is all I can think of I did.
Click to expand...
Click to collapse
I'm on my work computer so I can't see whats in the youtube link. What version radio do you have? What version spl do you have? Did you format your sd card in 3 partitions?
supremeteam256
supremeteam256 said:
I'm on my work computer so I can't see whats in the youtube link. What version radio do you have? What version spl do you have? Did you format your sd card in 3 partitions?
Click to expand...
Click to collapse
I will provide you with the right information if I still can.
Im also at work, and my G1 is in the car. But I dont know if it has enough power bcuz Im going to drop it at the store after work.
But I will try to open the flash screen and note down the specs.
*** Did you format your sd card in 3 partitions? --- That doesn`t ring a bell.
I formated FAT32 but I never heared of 3 partitions, that is new to me.
Peace
dizzydix said:
I will provide you with the right information if I still can.
Im also at work, and my G1 is in the car. But I dont know if it has enough power bcuz Im going to drop it at the store after work.
But I will try to open the flash screen and note down the specs.
*** Did you format your sd card in 3 partitions? --- That doesn`t ring a bell.
I formated FAT32 but I never heared of 3 partitions, that is new to me.
Peace
Click to expand...
Click to collapse
You need to have the new radio and spl for hero to fit so if you didn't do that then that could be part of your problem. You card should be in 3 partitions (fat32, ext2/3, and linux-swap). There are several different ways to partition your card. You can do it in Ubuntu (tut in my sig), or you can do it in parted, and couple other ways.
supremeteam256
supremeteam256 said:
You need to have the new radio and spl for hero to fit so if you didn't do that then that could be part of your problem. You card should be in 3 partitions (fat32, ext2/3, and linux-swap). There are several different ways to partition your card. You can do it in Ubuntu (tut in my sig), or you can do it in parted, and couple other ways.
Click to expand...
Click to collapse
Haha, ok
Know what`s Ironic.. I left Ubuntu one week ago for Vista.
But I will put a disk in and try you method.
(that is after I send it to the store, it`s always easier to let them do it for you .
I will keep an update..
Peace
dizzydix said:
Haha, ok
Know what`s Ironic.. I left Ubuntu one week ago for Vista.
But I will put a disk in and try you method.
(that is after I send it to the store, it`s always easier to let them do it for you .
I will keep an update..
Peace
Click to expand...
Click to collapse
What are you going to have them do?
supremeteam256
supremeteam256 said:
What are you going to have them do?
Click to expand...
Click to collapse
I don`t know I just go to the store that I bought it from and I will send it for reparation. They will send it to tmo.
If it can`t be repaired I will get it back and then I will try it myself on sundays when I have nothing to do.
Why?
dizzydix said:
I don`t know I just go to the store that I bought it from and I will send it for reparation. They will send it to tmo.
If it can`t be repaired I will get it back and then I will try it myself on sundays when I have nothing to do.
Why?
Click to expand...
Click to collapse
Just want to make sure you don't say what you were doing to it. And they won't send it to T-Mobile they would send it to HTC for repair. But to be completely honest with you, I wouldn't do that. Your phone does not need to be sent off. As soon as you have the phone in front of you and you have time to mess with it, it can be fixed. As long as you can get into bootloader and recovery your good. Its your phone and you can do what you want with it, but it should be an easy fix. Let us walk you thru it first before going.
supremeteam256
supremeteam256 said:
Just want to make sure you don't say what you were doing to it. And they won't send it to T-Mobile they would send it to HTC for repair. But to be completely honest with you, I wouldn't do that. Your phone does not need to be sent off. As soon as you have the phone in front of you and you have time to mess with it, it can be fixed. As long as you can get into bootloader and recovery your good. Its your phone and you can do what you want with it, but it should be an easy fix. Let us walk you thru it first before going.
Click to expand...
Click to collapse
Woww, that is a major offer man.
Ok you know what I keep it one more day bcuz I appreciate your help.
I just lost hope bcuz I tried everything I could find on forums and google so I did my research but I couldent get it trough and spend yesterday 12 whole hours on trying to flash and got tired. (thats how much I love my phone).
So once at home I will post a foto or specs of the flash page.
I didnt know someone would really be this kind and helpfull.
dizzydix said:
Woww, that is a major offer man.
Ok you know what I keep it one more day bcuz I appreciate your help.
I just lost hope bcuz I tried everything I could find on forums and google so I did my research but I couldent get it trough and spend yesterday 12 whole hours on trying to flash and got tired. (thats how much I love my phone).
So once at home I will post a foto or specs of the flash page.
I didnt know someone would really be this kind and helpfull.
Click to expand...
Click to collapse
There are several of us that are helpfull and don't mind helping. It's just the repeated dumb questions and people that want there hand held for the simplest thing (not saying you). Then thats when we can get ruthless, but yea we will help you out. You will prolly realize after the fact that it was prolly something simple and prolly want to slap yourself for wanting to take it back. lol.
supremeteam256
supremeteam256 said:
There are several of us that are helpfull and don't mind helping. It's just the repeated dumb questions and people that want there hand held for the simplest thing (not saying you). Then thats when we can get ruthless, but yea we will help you out. You will prolly realize after the fact that it was prolly something simple and prolly want to slap yourself for wanting to take it back. lol.
Click to expand...
Click to collapse
Hahaha, Im already laughing. I hope I will smack myself.
I hope if its ok to also post some pictures I will make at home in about an hour.
And I may load a video to youtube of the flash screen, maybe it helps.
Who knows.
dizzydix said:
Hahaha, Im already laughing. I hope I will smack myself.
I hope if its ok to also post some pictures I will make at home in about an hour.
And I may load a video to youtube of the flash screen, maybe it helps.
Who knows.
Click to expand...
Click to collapse
Yea thats cool to post whatever. Just post when you get settled in.
supremeteam256
supremeteam256 said:
Yea thats cool to post whatever. Just post when you get settled in.
Click to expand...
Click to collapse
HI,
Here is the update:
My screen shows (in rainbow screen):
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.261
Sep 2 2008
Serial10
dizzydix said:
HI,
Here is the update:
My screen shows (in rainbow screen):
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.261
Sep 2 2008
Serial10
Click to expand...
Click to collapse
Ok I'm gonna have you start from the begining so we are on the same page. First thing I want you to do is download this http://www.megaupload.com/?d=EMY1HIVU that is RC29. Also is your card already partitioned to fat32?
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?
Okay so - recently my I9000m went into a boot loop (during normal use - though I did have voodoo installed) and I can not access recovery mode. I could however access download mode.
I attempted to install stock firmware from samfirmware - no luck.
I attempted to install stock firmware from the forums - no luck.
I attempted to install EZBase - no luck.
I even attempted to use Virniks 'stock everything' tutorial - no luck.
After all these attempt and various other attempts involving 3 button fixes I was still having boot-loops.
So I got desperate - and I installed the Odin One Click for captivate - I know...bad idea but like I said.. I was desperate.
Now my i9000m (bell canada) starts up with the AT&T Logo and then boot loops!
The worst part is I can't even access download mode anymore! I understand that this is probably due to the fact that the buttons are remapped - keeping that in mind I tried as many key combos as I could but still get nothing but the AT&T Logo looping over and over.
So to the point.. does anyone have a surefire way to get to captivate download mode on a I9000M?
I've read about the JIG solution but I'll use that as a last resort as I would have to order the pieces (I'm not much of a solderer).
So are there any non-JIG solutions to get back to download mode/restore my phone?
All input is appreciated and I'd like to thank everyone that has tried to help me these last couple of days!
Sounds like your internal SD card is dead.
I was having similar issues where the phone would just bootloop. I re-flashed 4-5 different stock roms which all did the same thing. One of the stock roms allowed me into recovery mode, which yielded no success only a no sd card message.
I have gone ahead and sent my phone out to Bell for repair.
Viper717 said:
Sounds like your internal SD card is dead.
I was having similar issues where the phone would just bootloop. I re-flashed 4-5 different stock roms which all did the same thing. One of the stock roms allowed me into recovery mode, which yielded no success only a no sd card message.
I have gone ahead and sent my phone out to Bell for repair.
Click to expand...
Click to collapse
I'm thinking of doing the same (bringing it to bell) though I'm not sure they'll honor the warranty with it booting up with the AT&T logo, hah :<
Yeah i dont think they would service that, i was fortunate enough to get back a stock i9000m rom so it still boot up with that.
You can try contacting samsung directly to see if they will be able to repair for you, or try the jig and re-flash to stock bell rom
Viper717 said:
Yeah i dont think they would service that, i was fortunate enough to get back a stock i9000m rom so it still boot up with that.
You can try contacting samsung directly to see if they will be able to repair for you, or try the jig and re-flash to stock bell rom
Click to expand...
Click to collapse
Called samsung last night - they said I have to bring it to bell first.
Worst case scenario I'll pay sammy to fix it =/
Update: Just got off the phone with Bell, described my problem, said that I messed with the software real hard and they said that as long as I didn't remove any warranty stickers I'll still be able to get it fixed by samsung foh freeee.
Viper717 said:
Sounds like your internal SD card is dead.
I was having similar issues where the phone would just bootloop. I re-flashed 4-5 different stock roms which all did the same thing. One of the stock roms allowed me into recovery mode, which yielded no success only a no sd card message.
I have gone ahead and sent my phone out to Bell for repair.
Click to expand...
Click to collapse
I have urgued him to flash any SGS firmware with recovery image, but he didn't listen.
And yes, I think that his internal storage bus is dead.
If so, he should write down IMEI of his phone, and send email to the Samsung Korea with the info, that his internal SD card is dead. They will send him brand new phone.
But in the case he would rather use warranty service of his provider, he will need to:
a) try reboot with adb, and fastest as he can, try to issue "reboot download" command with it
OR
b) make JIG, and reboot to download mode, and reflash stock ROM
Asking Samsung Korea for new phone with IMEI sent to them do not require any of above...
EDIT: I have missed your last reply. Good to know, that Bell will fix it for you. But I do not think that they will be able to fix it. They will more likely give you new phone.
Virnik0 said:
I have urgued him to flash any SGS firmware with recovery image, but he didn't listen.
And yes, I think that his internal storage bus is dead.
If so, he should write down IMEI of his phone, and send email to the Samsung Korea with the info, that his internal SD card is dead. They will send him brand new phone.
Click to expand...
Click to collapse
I did listen - no matter how many times I tried to flash the sgs firmware w/ recovery image it would just keep booting and wouldn't enable the functionality.
As i detailed above I tried several recommended methods to re-enable the recovery mode and none of them worked.
Thanks for your help - hopefully Bell honors what they said on the phone.
Sozage said:
I did listen - no matter how many times I tried to flash the sgs firmware w/ recovery image it would just keep booting and wouldn't enable the functionality.
As i detailed above I tried several recommended methods to re-enable the recovery mode and none of them worked.
Thanks for your help - hopefully Bell honors what they said on the phone.
Click to expand...
Click to collapse
OK. Just do not panic :-D
You will get your phone back, more likely new one.
And on other hand, this result is not your fault. Some "first-line" SGS phone models has been faulty. You are not the first one with such problem.
Virnik0 said:
OK. Just do not panic :-D
You will get your phone back, more likely new one.
And on other hand, this result is not your fault. Some "first-line" SGS phone models has been faulty. You are not the first one with such problem.
Click to expand...
Click to collapse
They said they would send it to Samsung and give me a loaner until mine is back.
Not sure if they'll still honor it when I show up in person...but I'm hoping for the best.
So to give a final update:
After a couple commutes back and forth to the Bell store and a couple phone calls to Samsung it looks like I voided the warranty and I'm SOL on getting this phone repaired.
The (semi)bright side of the story is that I have an insurance policy with Bell and I'm getting a brand new SGS for $150.
Sozage said:
So to give a final update:
After a couple commutes back and forth to the Bell store and a couple phone calls to Samsung it looks like I voided the warranty and I'm SOL on getting this phone repaired.
The (semi)bright side of the story is that I have an insurance policy with Bell and I'm getting a brand new SGS for $150.
Click to expand...
Click to collapse
Little too much for a few hours of your time. If you'd reflashed stock ROM and ignored vibrant fw, as I've suggested, they would have no chance to find out what happened, and you've been given new phone for free. But you were in a hurry. Besides, your second, but in the circumstances of your haste not important misstake was, that you've told them what you have done.
Sent from my GT-I9000 using XDA Premium App
Virnik0 said:
Little too much for a few hours of your time. If you'd reflashed stock ROM and ignored vibrant fw, as I've suggested, they would have no chance to find out what happened, and you've been given new phone for free. But you were in a hurry. Besides, your second, but in the circumstances of your haste not important misstake was, that you've told them what you have done.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Exactly what I thought...you gave them extremely obvious reasons to put you at fault when you could have easily gotten a free replacement out of this. Don't answer questions that aren't asked
My father's I9000M had a failed SD and I got it replaced for free. Ironically his had a single ROM flashed on it and mine has had over 100 and been 100% fine.
chambo622 said:
Exactly what I thought...you gave them extremely obvious reasons to put you at fault when you could have easily gotten a free replacement out of this. Don't answer questions that aren't asked
My father's I9000M had a failed SD and I got it replaced for free. Ironically his had a single ROM flashed on it and mine has had over 100 and been 100% fine.
Click to expand...
Click to collapse
Btw, it does not matter how many times you'll reflash, this sd bus failure is pretty common in some first series of GT-9000 and GT-9000M
Sent from my GT-I9000 using XDA Premium App
chambo622 said:
Exactly what I thought...you gave them extremely obvious reasons to put you at fault when you could have easily gotten a free replacement out of this. Don't answer questions that aren't asked
My father's I9000M had a failed SD and I got it replaced for free. Ironically his had a single ROM flashed on it and mine has had over 100 and been 100% fine.
Click to expand...
Click to collapse
My BELL phone started up with an AT&T logo... even if I didn't volunteer the information they would have figured it out and sent me the bill.
As soon as they determine it is off warranty Samsung charges $35 dollars just to evaluate the problem and then charges you to fix it.
Yes I should have just brought it back when it first messed up but I figured my warranty was already voided due to the voodoo installation that I could not reverse (due to the boot loops).
Lesson learned.. probably won't tweak my phone too much in the future...especially if (like my last phone) I can't get into recovery mode - though I'm hoping this is fixed in the new phone I get.
Sozage said:
My BELL phone started up with an AT&T logo... even if I didn't volunteer the information they would have figured it out and sent me the bill.
As soon as they determine it is off warranty Samsung charges $35 dollars just to evaluate the problem and then charges you to fix it.
Yes I should have just brought it back when it first messed up but I figured my warranty was already voided due to the voodoo installation that I could not reverse (due to the boot loops).
Lesson learned.. probably won't tweak my phone too much in the future...especially if (like my last phone) I can't get into recovery mode - though I'm hoping this is fixed in the new phone I get.
Click to expand...
Click to collapse
$5 jig could have saved you $150
But at least you're having your phone repaired...
Kops said:
$5 jig could have saved you $150
But at least you're having your phone repaired...
Click to expand...
Click to collapse
Not repaired! New phone! Maybe even one without a faulty SD card!
Sozage said:
My BELL phone started up with an AT&T logo... even if I didn't volunteer the information they would have figured it out and sent me the bill.
As soon as they determine it is off warranty Samsung charges $35 dollars just to evaluate the problem and then charges you to fix it.
Yes I should have just brought it back when it first messed up but I figured my warranty was already voided due to the voodoo installation that I could not reverse (due to the boot loops).
Lesson learned.. probably won't tweak my phone too much in the future...especially if (like my last phone) I can't get into recovery mode - though I'm hoping this is fixed in the new phone I get.
Click to expand...
Click to collapse
The lesson you should've learn is to READ before you attempt anything.
I've flashed about anything to this phone and it's pretty hard to really brick the thing... Flashing the rom from a captivate is realy not in the line of "tweaking" rather than no-sens what so ever...
t1mman said:
The lesson you should've learn is to READ before you attempt anything.
I've flashed about anything to this phone and it's pretty hard to really brick the thing... Flashing the rom from a captivate is realy not in the line of "tweaking" rather than no-sens what so ever...
Click to expand...
Click to collapse
Right, it should be enought to use common sense, and think a little before any further action. I have tried almost anything, starting with dualboot to xubuntu linux, or editing apk's, modding and themming apps (not always successful), erasing all data partitions, created new ones, installed (or at least tried) to install gentoo linux with simple routing capability, and so on. And I'm still here.
Truth is, that some first lines of SGS were affected with faulty sd bus. But there is no need for paying warranty service, and no need to be few days without my phone. If common sense is used, then User would not:
1) install captivate firmware
2) flash anything before cwm is working
if both above fails, he'll reboot to the download mode, flashed canadian or any other fw containing Sbl.bin, alias recovery.
After that, he would flash standard stock firmware which is used by his operator. As a last thing, he would wipe sdcard from recovery.
Phone will look, behave and WILL BE same as he'd bought it.
So they will look on it, and will see standard, untouched phone, which is unknowingly rebooting itself.
Voila! They'll have no other chance then give you brand new phone right on the spot.
So for the next time, keep your mouth shut at least, when you deal with operator ;-)
Sent from my GT-I9000 using XDA Premium App
t1mman said:
The lesson you should've learn is to READ before you attempt anything.
I've flashed about anything to this phone and it's pretty hard to really brick the thing... Flashing the rom from a captivate is realy not in the line of "tweaking" rather than no-sens what so ever...
Click to expand...
Click to collapse
I wish people would read the entire thread before posting more bs like this.
Trying to put the captivate software on my phone via Odin One Click was the 10th or so thing I tried to do to restore my phone. Nothing would work - recovery mode did not work on my phone nor was I able to restore it.
Flashing the captivate software was an attempt to get recovery working (a desperate attempt) and had nothing to do with my comment about tweaking.
diaf.
I know there is nothing you can do but out is bs that you' voided' warranty. they make you pay $150 for THEIR hardware failure.
Hi everybody, I enjoyed my stock N4 for almost a year and today several apps started to crash suddenly, after that the device rebooted itself and never got out of the bootloop. I immediatly booted into recovery and tried to wipe the cache memory and perform a factory reset but I cannot do either of the two, the error I get is something like "can't mount cache partition".
What should I do? How did this happen?!? I really need my phone back asap.
Thanks everybody!
Flash the stock images.
Chromium_ said:
Flash the stock images.
Click to expand...
Click to collapse
Ok I will but...How can this happen? A fully stock phone who never had a problem suddenly corrupts it's partitions?! (This is my understanding of the situation, correct me if I am wrong)
Thanks again for the link
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
chikosneff said:
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
Click to expand...
Click to collapse
sounds like your storage itself fails. thats the same issue that happens when the storage goes bad.
simms22 said:
sounds like your storage itself fails. thats the same issue that happens when the storage goes bad.
Click to expand...
Click to collapse
Thanks for helping, yes it looks like..so I can throw away my phone or there's something more I can try?
It feels so weird because it's one of the few phones I always kept stock, never fell, never had a single problem. Damn.
chikosneff said:
Thanks for helping, yes it looks like..so I can throw away my phone or there's something more I can try?
It feels so weird because it's one of the few phones I always kept stock, never fell, never had a single problem. Damn.
Click to expand...
Click to collapse
You could give this a try, but I really doubt it'll do much. I guess its worth a shot though.
chikosneff said:
Ok I will but...How can this happen? A fully stock phone who never had a problem suddenly corrupts it's partitions?! (This is my understanding of the situation, correct me if I am wrong)
Thanks again for the link
Click to expand...
Click to collapse
chikosneff said:
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
Click to expand...
Click to collapse
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Why did it happen? A phone is basically a mini computer, same as when you have to reload a computer OS sometimes,(failing hardware, bad app???)
Timboe73 said:
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Why did it happen? A phone is basically a mini computer, same as when you have to reload a computer OS sometimes,(failing hardware, bad app???)
Click to expand...
Click to collapse
I'll give it a shot thanks, but I am afraid that the fastboot flash error is pretty clear :crying:
I get the phone being a computer, and I am totally ready to reload an OS...but I am not so ready to see the storage fails so suddenly leaving me with no phone, especially because this phone has received more care than any other phone I ever had..
Timboe73 said:
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
If its failing when he does it manually via fastboot commands, its very unlikely that using a toolkit will change anything. A toolkit simply runs the same fastboot commands behind a GUI.
Switched to windows to give the toolkit a try, then I will follow the unbrick procedure...I still cannot believe that this phone is lost without even having experienced the fun to mess it up with my own hands
chikosneff said:
Switched to windows to give the toolkit a try, then I will follow the unbrick procedure...I still cannot believe that this phone is lost without even having experienced the fun to mess it up with my own hands
Click to expand...
Click to collapse
As expected: toolkit not working. Since the bootloader " relocks" itself after rebooting the toolkit is unable to flash it afterwards.
Will try to contact google support but I am currently living in Europe I don't think it will be easy to get help.
Any other help is greatly appreciated. Thanks everybody.
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
another case reported :/
i think some batches of nexus 4 contains emmc brick bugs
just see this thread, more then 5 or 6 have been reported here.
http://forum.xda-developers.com/showthread.php?t=2259334
so after reading that thread i **** my self, because if this occured to my nexus i will have no warranty no google claims no nothing because i live in Pakistan.
So i ran emmc check app on my phone to check what it shows.
my emmc check shows i have "NO, Sane chip"
this means i am safe? if it give me "Yes, Insane chip" then i,m not safe according the my theory.
EMMC check app also shows the chip type, my chip type is "016g92"
googling this chip type i came across no specific results, one from S3 sudden death thread discussion. one person reports he have the 016g92 type and it is a safe chip according to other folks.
and one person having a galaxy s3 bricked his emmcs chip and claim the warranty. after the phone returns his chip type change to 016g92
http://smartphone.usofttech.com/t85915.html
so they change the emmc chip to 016g92.
can i surely assume that my nexus is safe from this serious hardware defect?
also any one here run the emmc chip and do give there chips type here, as i want to confirm if i,m safe or not. if not i,m going to sale my phone here. because the lose will be unbearable for me if the brick did occured
---------- Post added at 11:48 AM ---------- Previous post was at 11:37 AM ----------
simms22 said:
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
Click to expand...
Click to collapse
Dear Sir do advice me
simms22 said:
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
Click to expand...
Click to collapse
I still have 2 weeks of warranty left but I'll be in Europe till next year..I will try to ask the warranty service if I can send it in at my own expense.
Damn a worldwide warranty service doesn't look so useless now as it looked when I bought it :laugh:
PHONE BACK FROM THE DEAD!!!
So I got in touch with google's customer care to arrange the RMA and just to show them that my phone was impossible to recover I jumped ahead and told 'em: ok let's do a factory reset together so that I can show you what's the problem....
Fastboot>recovery>>data wipe....COMPLETED!
I cannot understand why did it work, I tried to wipe it at least ten times yesterday.
So now I have my N4 back working. What's your opinion on what happened? Do you feel like the problem is going to show up again soon? Is there anything I should do now that it's working? I just did a factory reset, not the cache wipe.
Just FYI: RMA from oversea is a pain in the ass, you have to ship the phone back to somebody in the U.S. and THEN ask for the RMA.
I wish I had your luck, mine did the same thing about 2 weeks ago. Couldn't get it to factory reset either. Mounting issue. My RMA came in yesterday. I'm enjoying the new phone though. It's even got the little nubs on the back. Mine original was a creaky 1st or 2nd batch one, I think. I will miss all the memories, pics, and data on my old one though.
SefEXE said:
I wish I had your luck, mine did the same thing about 2 weeks ago. Couldn't get it to factory reset either. Mounting issue. My RMA came in yesterday. I'm enjoying the new phone though. It's even got the little nubs on the back. Mine original was a creaky 1st or 2nd batch one, I think. I will miss all the memories, pics, and data on my old one though.
Click to expand...
Click to collapse
Since I feel this problem is hardware related I do not feel completely safe and I believe you were the lucky one getting the RMA
I had no choice, I should have sent the phone back to the US and then ask for the RMA...big pain in the ass
:fingers-crossed: let's hope this thing holds