HTC problem - G1 General

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?

Related

OTA update

Hey Im new to android.
I updated my N1 ove the air but it showed a screen of a triangle with a ! inside it and the android , I had to pull the battery out yo restart the phone.
Did I do something wrong? Did it update?
I have not long *rooted* the N1.
confrontation said:
Hey Im new to android.
I updated my N1 ove the air but it showed a screen of a triangle with a ! inside it and the android , I had to pull the battery out yo restart the phone.
Did I do something wrong? Did it update?
I have not long *rooted* the N1.
Click to expand...
Click to collapse
Why did you pull the battery?! The triangle screen is the phone updating... Was it stuck on that screen for more than 10 minutes?
hey
uansari1 said:
Why did you pull the battery?! The triangle screen is the phone updating... Was it stuck on that screen for more than 10 minutes?
Click to expand...
Click to collapse
It wasnt stuck , but it had the status bar down below and then that went away b4 it finished loading , I figured it failed so I tried turning it off but it wouldnt turn off after holding the power button for 10 sec's.
Put the battery back in and the phone booted
confrontation said:
It wasnt stuck , but it had the status bar down below and then that went away b4 it finished loading , I figured it failed so I tried turning it off but it wouldnt turn off after holding the power button for 10 sec's.
Put the battery back in and the phone booted
Click to expand...
Click to collapse
No idea whether it truly finished updating or not.... you are lucky you didn't brick your phone, especially if you pulled the battery during the radio update portion of it. There is a reason the instructions for updating from google say "don't remove the battery during the update process, let it finish on its own"(or something to that effect).
You might want to try re-applying it to make sure everything was flashed correctly.
in the system updates it is saying the fone is up to date.
another thing is...
How did it download the update when I didnt have wifi or 3G connected?
I have it set to only get 2G (have no data plan on 3G and no credit) and while at work this morning it prompted me to install update.
confrontation said:
in the system updates it is saying the fone is up to date.
another thing is...
How did it download the update when I didnt have wifi or 3G connected?
I have it set to only get 2G (have no data plan on 3G and no credit) and while at work this morning it prompted me to install update.
Click to expand...
Click to collapse
The update would still download over Edge. When you go to Settings>About Phone, is the firmware version 2.1 or 2.1-update1?
Also, don't assume anything fails. If you're unfamiliar with the update procedure, feel free to ask up before doing anything. There was another guy whose phone was stuck on that screen for over an hour. He was right to pull the battery... but in your case, it was risky. Anyway, glad to hear you're not bricked man.
uansari1 said:
The update would still download over Edge. When you go to Settings>About Phone, is the firmware version 2.1 or 2.1-update1?
Also, don't assume anything fails. If you're unfamiliar with the update procedure, feel free to ask up before doing anything. There was another guy whose phone was stuck on that screen for over an hour. He was right to pull the battery... but in your case, it was risky. Anyway, glad to hear you're not bricked man.
Click to expand...
Click to collapse
Im sure we dont have "EDGE" is new zealand , im not even sure wot that is.
Its saying firmware version 2.1.
How can I reinstall the update?
and another thing is apps will not download from the market since I have rooted the phone.
it just shows a status bar and says starting download and does nothing (downloading an app now and been doing it for 5mins)
sorry im a NOOB to the N1 , but Im good at the iPhone lol
confrontation said:
Im sure we dont have "EDGE" is new zealand , im not even sure wot that is.
Its saying firmware version 2.1.
How can I reinstall the update?
and another thing is apps will not download from the market since I have rooted the phone.
it just shows a status bar and says starting download and does nothing (downloading an app now and been doing it for 5mins)
Click to expand...
Click to collapse
Well, you can download the update file from the Development forum... follow the procedure directly...just make sure to rename the file to update.zip when you copy it to your sd card.
confrontation said:
sorry im a NOOB to the N1 , but Im good at the iPhone lol
Click to expand...
Click to collapse
We were all noobs at one point. Always search for answers to your questions first. Believe me when I say that 90% of questions, especially noob questions, have been answered numerous times before...and if you can't find an answer, then ask us.
uansari1 said:
Well, you can download the update file from the Development forum... follow the procedure directly...just make sure to rename the file to update.zip when you copy it to your sd card.
We were all noobs at one point. Always search for answers to your questions first. Believe me when I say that 90% of questions, especially noob questions, have been answered numerous times before...and if you can't find an answer, then ask us.
Click to expand...
Click to collapse
Thanks for your help man
cant find update file
confrontation said:
cant find update file
Click to expand...
Click to collapse
http://android.modaco.com/content/g...d-and-unrooted-optional-radio-optional-himem/
Follow the steps in #1
pjcforpres said:
http://android.modaco.com/content/g...d-and-unrooted-optional-radio-optional-himem/
Follow the steps in #1
Click to expand...
Click to collapse
Thanks man
uansari1 said:
Well, you can download the update file from the Development forum... follow the procedure directly...just make sure to rename the file to update.zip when you copy it to your sd card.
We were all noobs at one point. Always search for answers to your questions first. Believe me when I say that 90% of questions, especially noob questions, have been answered numerous times before...and if you can't find an answer, then ask us.
Click to expand...
Click to collapse
Can you tell me how to install stock firmware?

[Q] CWM Recovery Errors

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?

[Q] xoom bricked ?

hi guys ...i hav some big problem n i really need ur help pls.
i hav tried to root my xoom but it failed n now im afraid i hav bricked my xoom
- unlock ok
- fastboot flash boot boot.img ok
- fastboot reboot fail ( dual core technology frozen)
the only thing that it shows is the dual core technology screen nothing more and when i reset it it starts alone by itself again and stock
i hav a motorola xoom 3g titan i guess before i try to root it was 3.0.1 or may be 3.1
but i never try to use a sd card so i dont know if it works
while trying to fix it i wipe the factory, cache but still bricked
best regards
daddymaths said:
hi guys ...i hav some big problem n i really need ur help pls.
i hav tried to root my xoom but it failed n now im afraid i hav bricked my xoom
- unlock ok
- fastboot flash boot boot.img ok
- fastboot reboot fail ( dual core technology frozen)
the only thing that it shows is the dual core technology screen nothing more and when i reset it it starts alone by itself again and stock
i hav a motorola xoom 3g titan i guess before i try to root it was 3.0.1 or may be 3.1
but i never try to use a sd card so i dont know if it works
while trying to fix it i wipe the factory, cache but still bricked
best regards
Click to expand...
Click to collapse
The sd card should not be an issue since you use your computer connected to the Xoom with adb/fastboot when rooting.
Which rooting guide are you using? It does matter, especially for 3G non-US models.
I'm sure you are not bricked. You will need to start again but make sure you have all of the correct files in you platform tools folder (or whatever folder you are using for adb).
If you have successfully unlocked you can skip that step.
You are frozen at the dual core screen because you have flashed an incorrect boot.img for your specific model of xoom, and the android version you have on your xoom a.k.a 3.0-3.2. Since you are on the 3g version make sure you get a 3g boot.img and might as well get both the 3.1 and 3.0.1 boot.Hold the power button and the volume up button at the same time to reboot, wait 3 seconds,and then press only the the volume up button. you should now have a message at the top that says starting fastboot protocol support. begin flashing the images.
rootfan said:
You are frozen at the dual core screen because you have flashed an incorrect boot.img for your specific model of xoom, and the android version you have on your xoom a.k.a 3.0-3.2. Since you are on the 3g version make sure you get a 3g boot.img and might as well get both the 3.1 and 3.0.1 boot.Hold the power button and the volume up button at the same time to reboot, wait 3 seconds,and then press only the the volume up button. you should now have a message at the top that says starting fastboot protocol support. begin flashing the images.
Click to expand...
Click to collapse
Ditto, you will know for sure whenu brick when your screen is black only. You have a little work to do as notedbut stay calm.. You will get things fixed.
rockhumper said:
Ditto, you will know for sure whenu brick when your screen is black only. You have a little work to do as notedbut stay calm.. You will get things fixed.
Click to expand...
Click to collapse
+1 dont jump the gun and read everything over 5x before moving forward... Its a lil work like said but you will probably be more knowledgeable after its all said and done and be able to help others that may be stuck like you one day..
Good luck
Hey guys... I have bricked my xoom too. It's a wifi only xoom. I missed the last step in the guide I was using "fastboot oen lock" and rebooted... so now it stays on the dual core screen. I tried vol up and power buttons to get fastboot and it stays on the starting fastboot protocol... the computer doesn't recognize it. Just don't know what to do next...
Please help...!
Sent from my T959 using XDA App
rickyx said:
Hey guys... I have bricked my xoom too. It's a wifi only xoom. I missed the last step in the guide I was using "fastboot oen lock" and rebooted... so now it stays on the dual core screen. I tried vol up and power buttons to get fastboot and it stays on the starting fastboot protocol... the computer doesn't recognize it. Just don't know what to do next...
Please help...!
Sent from my T959 using XDA App
Click to expand...
Click to collapse
Read the sticky on page one... That says a guide to all your rooting needs... Proceed
This is what scares people
Don't freak out if your xoom won't boot. Your xooms are certainly not nowhere near bricked. >.>
Kippui said:
This is what scares people
Don't freak out if your xoom won't boot. Your xooms are certainly not nowhere near bricked. >.>
Click to expand...
Click to collapse
The word "bricked" gets way too much use... 95% of folks saying they bricked are no where near it...
rockhumper said:
The word "bricked" gets way too much use... 95% of folks saying they bricked are no where near it...
Click to expand...
Click to collapse
I have only seen one bricked xoom so far.
Sent from my PG86100 using Tapatalk
bwcorvus said:
I have only seen one bricked xoom so far.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Dont you know that 50 percent of all statistics are made up? And thats 99 percent of the time
thx guys
i was unfortunately little bit busy with work and exams ....i m relieve ..i will try to follow ur advices and keep u in touch.
thx a lot.
best regards
daddymaths
Is your Xoom still "bricked?" If so, shoot me a PM and I'll help you out. I HIGHLY doubt it is truly bricked.
rooting guide?
okantomi said:
The sd card should not be an issue since you use your computer connected to the Xoom with adb/fastboot when rooting.
Which rooting guide are you using? It does matter, especially for 3G non-US models.
I'm sure you are not bricked. You will need to start again but make sure you have all of the correct files in you platform tools folder (or whatever folder you are using for adb).
If you have successfully unlocked you can skip that step.
Click to expand...
Click to collapse
i have as i say a 3G motorola titan ....could anyone provides me the right routing files ? thx
I have a completely and 100% bricked Xoom. Was in the rooting process, and did something wrong, but the device is totally dead.
No response when plugging in via USB, although white LED illuminates when the power is plugged in.
cdinoz said:
I have a completely and 100% bricked Xoom. Was in the rooting process, and did something wrong, but the device is totally dead.
No response when plugging in via USB, although white LED illuminates when the power is plugged in.
Click to expand...
Click to collapse
Hit power and volume up to reboot...there is nothing the root process can do to brick it. Stop by the irc channel.
Sent from my PG86100 using Tapatalk
Have tried that.... Is still dead, and get no response from the device. Apparently I may have totally wiped the NAND storage....?
cdinoz said:
Have tried that.... Is still dead, and get no response from the device. Apparently I may have totally wiped the NAND storage....?
Click to expand...
Click to collapse
What exactly did you do (or try to do)?
okantomi said:
What exactly did you do (or try to do)?
Click to expand...
Click to collapse
I tried to root the device and install the Tiamat kernel. I was enabling the micro SD slot (or so I thought) and when I dropped in my SD card, there was a warning that the device needed to be re-partitioned. So I did. Didnt format the microSD, seems to have formatted the entire device.
Related to this issue:
http://forum.xda-developers.com/showthread.php?p=14462676#post14462676
cdinoz said:
I tried to root the device and install the Tiamat kernel. I was enabling the micro SD slot (or so I thought) and when I dropped in my SD card, there was a warning that the device needed to be re-partitioned. So I did. Didnt format the microSD, seems to have formatted the entire device.
Related to this issue:
http://forum.xda-developers.com/showthread.php?p=14462676#post14462676
Click to expand...
Click to collapse
That's one of the only two ways to brick it. I would stop by the irc channel, but I think you may have actually bricked it.
Sent from my PG86100 using Tapatalk

Lost all hope...

It seems that I was fiddling with my OTA and I lost my original build Kind of bummed out, and also the fact that I don't even know how to do a full backup. I did a nandroid backup which doesn't even work. I update to the new ICS firmware and messed up everything...Now I'm left in a gutter feeling utterly upset and don't know what to do. If there's anybody who pity's me, please help. It would be sincerely appreciated. I just want to start off fresh.
Mkami said:
It seems that I was fiddling with my OTA and I lost my original build Kind of bummed out, and also the fact that I don't even know how to do a full backup. I did a nandroid backup which doesn't even work. I update to the new ICS firmware and messed up everything...Now I'm left in a gutter feeling utterly upset and don't know what to do. If there's anybody who pity's me, please help. It would be sincerely appreciated. I just want to start off fresh.
Click to expand...
Click to collapse
So where are you at right now. What rom and what exactly have you done to your tab.
Mkami said:
It seems that I was fiddling with my OTA and I lost my original build Kind of bummed out, and also the fact that I don't even know how to do a full backup. I did a nandroid backup which doesn't even work. I update to the new ICS firmware and messed up everything...Now I'm left in a gutter feeling utterly upset and don't know what to do. If there's anybody who pity's me, please help. It would be sincerely appreciated. I just want to start off fresh.
Click to expand...
Click to collapse
Yeah, I share the pity with you Mate. You shouldn't have to look at that busted tab. Just put that shameful thing in a box and mail it to me, to help ease your pain. Heck, I'll toss in shipping so you won't suffer further insult and pain...
Seriously, though, there are plenty of tools and procedures here to bring it back to life.
First off, before you muck things up further, I would look in your nandroid backup, and get the UID number. Hopefully you wrote this down somewhere before you originally messed with things?
For starters, I would goto this link, and see if it works for you...
http://forum.xda-developers.com/showthread.php?t=1699277
The english steps are not the best in the world, but you will get the general idea.
MD
shaun298 said:
So where are you at right now. What rom and what exactly have you done to your tab.
Click to expand...
Click to collapse
At this moment right now, my a500 tab has that orange light on the bottom and it stays there, and when I turn on the tab it starts up normally like it would, and when it does it turns off. The strange thing is that orange charging light where the power button is, stays on even though I'm not even charging it.
I've tried changing the OTA, but after when it starts in the corner it says something like. " Not official blob" I'm not even sure I know what that even means....I have everything including nandroid backed up all the files into the SD card I had in my tab, I notice is there somewhere due to the amount of space it consumed on my SD.
So please! IF you know of any way to fix this I would be in great appreciation, also it's been a month since I've had this tab, as well I have a 2 year warranty.
Moscow Desire said:
Yeah, I share the pity with you Mate. You shouldn't have to look at that busted tab. Just put that shameful thing in a box and mail it to me, to help ease your pain. Heck, I'll toss in shipping so you won't suffer further insult and pain...
Seriously, though, there are plenty of tools and procedures here to bring it back to life.
First off, before you muck things up further, I would look in your nandroid backup, and get the UID number. Hopefully you wrote this down somewhere before you originally messed with things?
For starters, I would goto this link, and see if it works for you...
http://forum.xda-developers.com/showthread.php?t=1699277
The english steps are not the best in the world, but you will get the general idea.
MD
Click to expand...
Click to collapse
Hahaha funny guy! If you haven't seen my post its here and the reasons. Also I do have the UID saved on a text format on my pc...will that work??
So here is the issue are the current moment friend.
my a500 tab has that orange light on the bottom and it stays there, and when I turn on the tab it starts up normally like it would, and when it does it turns off. The strange thing is that orange charging light where the power button is, stays on even though I'm not even charging it.
I've tried changing the OTA, but after when it starts in the corner it says something like. " Not official blob" I'm not even sure I know what that even means....I have everything including nandroid backed up all the files into the SD card I had in my tab, I notice is there somewhere due to the amount of space it consumed on my SD.
So please! IF you know of any way to fix this I would be in great appreciation, also it's been a month since I've had this tab, as well I have a 2 year warranty.
Have you tried putting a stock update.zip on the root of your external sdcard and booting the tablet by holding the volume down button (left volume rocker) down while pressing the power button until the tablet finds the file and installs it. This should bring you back to unrooted stock ICS with locked bootloader and you can start over. Remember, this must be an update.zip file that is extracted from a stock RUU. You can't just rename a RUU file to update.zip.
Mkami said:
Hahaha funny guy! If you haven't seen my post its here and the reasons. Also I do have the UID saved on a text format on my pc...will that work??
So here is the issue are the current moment friend.
my a500 tab has that orange light on the bottom and it stays there, and when I turn on the tab it starts up normally like it would, and when it does it turns off. The strange thing is that orange charging light where the power button is, stays on even though I'm not even charging it.
I've tried changing the OTA, but after when it starts in the corner it says something like. " Not official blob" I'm not even sure I know what that even means....I have everything including nandroid backed up all the files into the SD card I had in my tab, I notice is there somewhere due to the amount of space it consumed on my SD.
So please! IF you know of any way to fix this I would be in great appreciation, also it's been a month since I've had this tab, as well I have a 2 year warranty.
Click to expand...
Click to collapse
Well, you get the orange light because your EC Pwr management is probably fubarred. That should be fixed when you install a stock rom as suggested in both mine and the other poster.
Considering you have your UID, you should be ok.
Of course I don't know if this is a 3.2 or an ICS UID. Best to have both. The sbk is the same, but the uid numbers differ.
If it's a 3.2., check the Q&A thread for a post I did for a guy earlier today.
But you should be able to follow the steps for the update I posted earlier.
Blob means Bootloader. And looks like you had an unlocked bootloader?
Try to roll back to 3.2. That's where I would start.
MD
cruise350 said:
Have you tried putting a stock update.zip on the root of your external sdcard and booting the tablet by holding the volume down button (left volume rocker) down while pressing the power button until the tablet finds the file and installs it. This should bring you back to unrooted stock ICS with locked bootloader and you can start over. Remember, this must be an update.zip file that is extracted from a stock RUU. You can't just rename a RUU file to update.zip.
Click to expand...
Click to collapse
What do you mean by RUU? Also I've tried a couple of the OTA updates, when I first got the tab it was on 3.1 HC didn't even update it or anything, just had a custom ICS ROM on it. Do you think you can post the steps or anything on how to do this properly and go fresh? It would be sincerely appreciate buddy.
Moscow Desire said:
Well, you get the orange light because your EC Pwr management is probably fubarred. That should be fixed when you install a stock rom as suggested in both mine and the other poster.
Considering you have your UID, you should be ok.
Of course I don't know if this is a 3.2 or an ICS UID. Best to have both. The sbk is the same, but the uid numbers differ.
If it's a 3.2., check the Q&A thread for a post I did for a guy earlier today.
But you should be able to follow the steps for the update I posted earlier.
Blob means Bootloader. And looks like you had an unlocked bootloader?
Try to roll back to 3.2. That's where I would start.
MD
Click to expand...
Click to collapse
Hmmm....I'm not even sure what I am doing wrong but whatever it is, it seems to be not working. I looked for you post for the earlier person that you did, but don't know what it is under. By the way when I first bought the tab it was under 3.1 HC and after getting flexreaper it became to ICS 4.0.3...
So like everytime I turn on the tab it shuts down instantly, as well every time I try to boot an update.zip file onto the SD card it shows this animation of the android with this circular sphere in it's stomach after that it falls over with a red caution sign.
Mkami said:
So like everytime I turn on the tab it shuts down instantly, as well every time I try to boot an update.zip file onto the SD card it shows this animation of the android with this circular sphere in it's stomach after that it falls over with a red caution sign.
Click to expand...
Click to collapse
In my experience the common cause for ending up with a caution sign is a corrupted update.zip (incomplete download, bad SD card, etc.). As for the tablet shutting down, my guess is that's related to the power management functions being broken.
im not THEE most savvy here but i do know a few methods and find it easy to discover lesser known ones, i feel bad for you . if you want you can skype video me and ill try talking it over and maybe a few methods? :highfive:
edit: ok from what i can tell your update was bad and your bootloader is causing problems, the power problems are probably arising from the bad power management as moscow desire told.
the tabs obviously rooted n all right? ok so how about flashing the v7 ics bootloader then trying a custom rom?......<-also recommended by moscow desire
lcd047 said:
In my experience the common cause for ending up with a caution sign is a corrupted update.zip (incomplete download, bad SD card, etc.). As for the tablet shutting down, my guess is that's related to the power management functions being broken.
Click to expand...
Click to collapse
You're right! I was able to fix it and boot up to the usual! Thanks mate!
chismay said:
im not THEE most savvy here but i do know a few methods and find it easy to discover lesser known ones, i feel bad for you . if you want you can skype video me and ill try talking it over and maybe a few methods? :highfive:
edit: ok from what i can tell your update was bad and your bootloader is causing problems, the power problems are probably arising from the bad power management as moscow desire told.
the tabs obviously rooted n all right? ok so how about flashing the v7 ics bootloader then trying a custom rom?......<-also recommended by moscow desire
Click to expand...
Click to collapse
Hi Chismay, well I thought I fixed the issue and the problem. Guess again I did not This I can't believed I used a leaked ICS OTA, kinda ruined most of the things in my tab. Lol just had it for a month and already messed it up by fooling around with it. But your help is greatly appreciated buddy! Would like to get a one on one instructions on what I should do.
Cheers!
Correct me if I'm wrong on this...
1. You originally had Honeycomb on your tablet.
2. You flashed FlexReaper on your tablet
3. You probably got a recent version of FlexReaper.
4. You never upgraded your bootloader.
5. You can still get access to recovery.
If all of these are correct, then I think I know what the problem is. It appears you flashed a rom that requires the ICS bootloader and not the Honeycomb bootloader.
This, I think, is an easy fix...
1. Download the following file: http://www.darktremor.info/files/FLEXREAPER-R12.5-ICS-1.031.00.zip (this is an older version I have on my Acer A500).
2. Put the file on your SD card.
3. Boot up into recovery (if you can't get there, stop here).
4. Once you are in recovery, flash the FlexReaper file you just put on your SD card.
5. Now try to boot and see if it works.
Let me know how it works either here, in a PM, or e-mail me at [email protected]. If you need further assistance, don't hesitate to contact me.
Mkami said:
Hi Chismay, well I thought I fixed the issue and the problem. Guess again I did not This I can't believed I used a leaked ICS OTA, kinda ruined most of the things in my tab. Lol just had it for a month and already messed it up by fooling around with it. But your help is greatly appreciated buddy! Would like to get a one on one instructions on what I should do.
Cheers!
Click to expand...
Click to collapse
tkirton said:
Correct me if I'm wrong on this...
1. You originally had Honeycomb on your tablet.
2. You flashed FlexReaper on your tablet
3. You probably got a recent version of FlexReaper.
4. You never upgraded your bootloader.
5. You can still get access to recovery.
If all of these are correct, then I think I know what the problem is. It appears you flashed a rom that requires the ICS bootloader and not the Honeycomb bootloader.
This, I think, is an easy fix...
1. Download the following file: http://www.darktremor.info/files/FLEXREAPER-R12.5-ICS-1.031.00.zip (this is an older version I have on my Acer A500).
2. Put the file on your SD card.
3. Boot up into recovery (if you can't get there, stop here).
4. Once you are in recovery, flash the FlexReaper file you just put on your SD card.
5. Now try to boot and see if it works.
Let me know how it works either here, in a PM, or e-mail me at [email protected]. If you need further assistance, don't hesitate to contact me.
Click to expand...
Click to collapse
Hahaha! Good job on guessing all that! I just followed your order from step to step and I was about to boot up normally! Everything might be erased and stuff, but hey at least I have my tablet working again :good: Case solved!

Semi-bricked DHD

Evening all,
I have a DHD that is stuck in HBOOT/FASTBOOT, or at least that and the stock recovery program is all I can get to.
I tried an AAHK, and it basically tried to do a downgrade and has left the phone with no data, still at s-on, and I can't find an operator RUU(three uk) to flash it back to a useable state.
Is there a three RUU available?
I'm running around in circles as I can't make a gold card, due to not having another DHD available to retrieve the MMC2. All I need is a goldcard and then I can flash a WWE, but I cant find anywhere to make one without the phone or a similar one.
I dont think it turned the microsd properly into a gc, before it tried to downgrade. Is their anyway I can test to see if the memory card has been successfully goldcarded?
Any help would be greatly appreciated.
Thanks
James
This might help
http://forum.xda-developers.com/showthread.php?p=29203392
Sent from a dream.
Teichopsia said:
This might help
http://forum.xda-developers.com/showthread.php?p=29203392
Sent from a dream.
Click to expand...
Click to collapse
Mine has a lot of those symptoms to be honest. If I vol down/power to get to Hboot, it sits there with no keys being able to be pressed, just highlighted blue FASTBOOT and not even checking for files on memory card
If I just turn it on, it sits at the three splash screen, which i assume is the equivalent of the HTC one for branded phones.
I have now turned it on and left it on as per those linked threads, in the hopes the sd is a proper gold card and it is just slow. Fingers crossed.
Thanks for the pointer
James
There are many threads for your problem, do a search, check what it might be. I believe in the second page of that link has another link, check it out. Find out what is wrong before trying anything. If you have any questions, let us know what are the symptoms, what you have done and so on.
Sent from a dream.
Teichopsia said:
There are many threads for your problem, do a search, check what it might be. I believe in the second page of that link has another link, check it out. Find out what is wrong before trying anything. If you have any questions, let us know what are the symptoms, what you have done and so on.
Sent from a dream.
Click to expand...
Click to collapse
Well what I did, was follow the AAHK instructions, cleaned up my environment etc, went through the install. When it asked to do the downgrade, I said yes, then it asked about wiping and was I sure, so I said yes. It then rebooted the phone and it is now as it is. I pulled the battery and tried vol-down/power, which brings up HBOOT, but it doesnt let me do anything, vol keys and power do not work and it doesnt start looking for image files.
From that thread, it was mentioned it just could be going very slow, and people have just left it overnight. This is what I have done now, and will see if it has accessed the files on the memory card and downgraded properly in the morning.
Thanks
James
Have you tried looking for the RUU here?
Last I remember when aahk downgrades, you will be asked to reboot to basic recovery twice
Panic over, thankfully! Not my phone, you see!
It was so easy to root my S2 and the X10 before that, and the iP3G before that(and custom winmo, and nokia etc etc), I said give it to me, i'll sort you out with some ICS rom action.
Then it all went wrong as explained in my previous posts.
2 days later, i finally found the H3G RUU I needed to get an system on it. Silly branded phones. Took 4 hours to download as it was on a throttled download service(my 100MB leased line usually eats 300MB in seconds, but not this time)
So long story short, into FASTBOOT USB, ran the RUU and it completed and put froyo on the phone, and as a happy coincidence it was at a level that didn't need a downgrade, so AAHK ran through like a trooper, busybox installed and hey presto, ENG S-OFF. IceColdSandwich installed through cwm and one happy mate, who then proceeded to ring his wife and tell her to rent a film, as he would be tinkering with the phone all night lol
It was getting to the point I was going to have to give him my S2, and as I've just taken possession of a Sony SmartWatch, I didn't want to do that!!
Thank for everyone's help and pointers, not sure what went wrong the first time(probably a memory card/incompatibility/goldcard problem), but all sorted now.
James

Categories

Resources