G1 won't boot - G1 General

I bought it yesterday from some guy on craigslist with a dead battery, but after chrarging it with my carger it would not boot, just the G1 screen. i can not enter the recovery menu, but the boot loader menu does work. Is there anything I can do? I tried reloading the rc29 Dreaimg.nbh, but won't boot. It has the pvt 32b and seeing as how that one is easier to root, I am hoping it's a random issue and not a rooting brick.

As a side note, I have searched. through millions of forums, google, and even my attic for answers. there is always people who get no recovery and no Boot loader screen, then there are those who can access both, but I have not heard of one who can access one witout the other.

did the guy tell u if it had been rooted? if so you can flash a custom recovery image
do you know how to use fastboot? if not have a look around and then try this:
try flashing cyanogens recovery image found here:
http://forum.xda-developers.com/showthread.php?t=523558&highlight=recovery
hopefully this will allow you to do a wipe and flash a new image
if you cant do this give me a shout and il think of something else

The guy did not tell me it wouldn't work, he said it worked fine and then this happened. i traded him an old PSP I had laying around for it, so no big loss on my side. I have emailed him, but no response. Well, How would I type in those commands? Through the phone, or the PC? Thos directions are pretty unclear.

what happened when loading the Dreaimg.nbh
Did it successfully do it? It could take a while to boot afterwords so be patient.

find a guide to setting up fastboot.if ur running windows i cant help but if u run ubuntu or some other linux i can....
after setting up fastboot
boot into the spl by holding camera+power with the usb plugged in
and type the commands in on the computer (again just follow instructions on using fastboot)
its the 2nd set you should use, the ones with "fastboot clear...." etc

Oh thanks. I have jaunty installed on my other pc will see how that goes. The dreaimg.nbh file worked. No errors. Do I just restart with green+menu+red, or was I supposed to wait?

restarting should have been fine...
http://forum.xda-developers.com/showthread.php?t=537508
you may find this useful when trying to set up fastboot in jaunty....
remember when you first plug the phone in to type "sudo adb enable-server"
then "adb devices" to make sure it is detected
the first command needs to be sudo whereas the other doesnt otherwise your device wont be detected
adding the line to bashrc didnt work for me so i tend to do it from within
~/androidsdk/tools/
and it works perfect
good luck
if u dont get a reply here i may not be looking at my computer, so u can email me or gtalk me on [email protected] and il always get it (tnx to my g1 )

I was successful in running all the fastboot/adb files in Windows, but while doing some more research, I don't think this phone was rooted. I am not getting the fastboot menu when I hit back button and my PC won't read the phone.

Last night I found out that after leaving it on for like 15-20 minutes it restarts, but after the second restart the phone died. It had been charging all day as I was using it. Seeing as how it was plugged into the PC. I am heading to a t-mobile store and am going to see if I can get a hold of an extra battery, not buy one mind you just ask "politely" to see one. Seems crazy, but I have a hunch it might be that my battery has gone dead. None of the nbh files I tried did anything except the rc30, that one caused my phone to start restarting, before it would stay on the g1 one for more than thirty minutes without a restart.

Sounds like its unrooted and stock but somehow has a corrupted rom.. It should be recoverable. Try the goldcard method to get RC30 on there:
http://forum.xda-developers.com/showthread.php?t=485364

I have been reading through that thread, but I have no idea how to actually use the goldcard that was generated. Anyone can help me through it seeing as I can not enter commands from my phone.

Ok I went to my Mac because dd command does not work under cygwin that well for me( I'm more familiar with terminals from ubuntu and OS X) Well I can't get the goldcard.img onto my micro sd card. I have been reading and no one seems to have any troubles other than actually generatiiong the gold card. I will report back after I finish the whole thread. Also they suggest an allocation size of 4096, but my sd card only gooes to 100* something.

ok, bad news, I just finished the gold card instaallation and put my sd card into my phone. Now it won't go to the bootloader. Too bad.

Good news. Yesterday I tried to boot it while placing the phone in a drawer and it booted to the recovery menu! I did not have an as card at all so there was nothing I could do so I tried to wipe everything and it finished, but it went back to where it was. I had left it in blue light mode all night. So last night I left it to try and redo what I had done, but it did not work. Atleast it goes back to the bootloader. Gold card did not work but I blame it on the CID number. I can't seem to get the right one. I'm looking though.

I realized what I did. I did not mess with it. I took the battery out last night an did not touch it till just now and it booted to the android screen then froze and restarted and went back to the G3 screen I'm going to leave it like this and see if it gets fixed by tomorrow. Than while booting try to get to the recovery menu. Hopefully it will fix the problems. I seriously think it might be the battery. Tmobile store did not have a spare one though.

Just a suggestion, may or may not work.. I got a new G1 the other day, and have rooted it, etc.. Mine did the same thing, on the G1 screen for hours, never left it.. Take the SD card out of it, and try to start it.. Mine would not load due to the partitioning, I had a 47mb ext2, a fat32, and another ext2 partition, which caused it to hang on the G1 screen.. If no luck there, this site is what helped me root mine, gives the files, and the steps.. http://www.getyourdroidon.com/wiki/index.php5?title=How_to_Root_your_G1
Just take the sd card and put it on your computer via an adapter or something to copy the files (Make sure it's formatted fat32)
If by some reason, my explanation above did work, use partition manager 9 to fix the card.

I booted it withoutth sd card, but same deal. Left it without the battery last night and got it to the recovery menu but would not find the update file. Ended up freezing on me so I went ahead and rebooted. Same deal. I guess I will try again tomorrow.

Phone booted up, was entering my log in info and it froze.... I'm still trying to fix this.

At this point, I would try to go completely back to a fresh OEM install, which I'm not sure you've done since you started to get access to Recovery.
Download the original T-mobile bootloader. Rename it to update.zip and copy it along with dreaimg.nbh to the SD card. Enter Recovery and alt-s to install the bootloader... reboot using Home+Back. It will probably lock up at some point as it's been doing. Turn off the phone and get into bootloader to flash dreaimg.nbh.
Report back after you do this.

Related

Help needed to fix rooting gone wrong

First off im sorry im adding another rooting post to these boards.
So i decided to root my 32B magic today copyed the recovery.img over and update file from the rooting wiki, loaded recovery mode then updated, but now my phone when turned on loads to the vodafone screen and freezes id left it for afew hrs but still no luck.
Here is what i know so far:
I am able to get to fastboot and fastboot usb
I cant however get to recovery mode by pressing menu+power
I can get to the recovery mode using the sdk\tools
my problem is that im sure the fix is relativly simple i.e. load some files onto sd and start again, but the problem is that i have no other way to load the files onto the sd card than through the phone and my knowledge of adb isnt that great although has improved greatly today lol.
Im not sure how correct i am on this, but would it be a possible fix to load say a rom update.zip onto the sd card and load that through recovery mode to bring it up? If that would fix it could i possible get help on the adb code needed to pass the file from computer to the phone through fastboot usb or recovery.
Thank you very much for your help
Ok i think i have figured how to push files to my sd card however whenever i try it come up saying Failed ( remote:signature verify fail)
ok well i managed to move Cyanogen's newest rom over and update to that but its still hanging up at the vodafone screen upon booting, im lost for ideas.
Please any help how ever small would be amazing right now.
please help is desperatly needed.
i am having the same issue.... and it seems NO ONE has a bloody answer to why it is failing
I successfully update to 32A and root. Then i tried to update to MT3G OTA rom and now i'm stuck at Vodafone screen. Need help or ideas and how to recover..
i had the same problem, what i did was that i found a sd card adapter and hooked it up to my computer, its pretty quick and less hassle
waacow said:
I successfully update to 32A and root. Then i tried to update to MT3G OTA rom and now i'm stuck at Vodafone screen. Need help or ideas and how to recover..
Click to expand...
Click to collapse
take out your battery and after a few seconds put it back in, before it powers up go into fastboot(back+power) and that should do it
I still have a pretty red splash screen and stucked.
neoxtian said:
take out your battery and after a few seconds put it back in, before it powers up go into fastboot(back+power) and that should do it
Click to expand...
Click to collapse
I have same problem, but your solution didn't work for me.
I did as follows.
#1. typed following command in terminal.(well, I'm using Mac)
Code:
fastboot-mac flash recovery recovery-RAv1.2.0G.img
#2. pulled battery off from phone.
#3. pluged USB cable to phone and also Mac.
#4. pressed (ENTER) in the terminal, then fastboot-mac said '< waiting for device >'.
#5. put the battery in while pressing (back)+(power)
#6. then, pretty red vodafone splash screen come up.
#7. In the terminal, it still said '< waiting for device >'. Nothing was changed.
#8. On the phone, pretty red splash screen was still there. Nothing was changed.
Those are all I have done many times for last 2 days.
But, it didn't work.
Please let me know if there is something I missed.
I tried and stuck in the exactly same problem as [robotician]. I have MT3G.
robotician said:
#5. put the battery in while pressing (back)+(power)
#6. then, pretty red vodafone splash screen come up.
#7. In the terminal, it still said '< waiting for device >'. Nothing was changed.
Click to expand...
Click to collapse
THe red vodafone should not come up. You have to hold the back key longer perhaps, because it's supposed to go into the fastboot screen with all sorts of text and three androids on skateboards at the bottom.
@Niaski
was your rom made for the 32B or the 32A?
They are very diferent phones and mixing the roms causes the issue you are seeing.

DREA100 and the infamous Triangle of death?

Ok.. So a friend of mine suddenly got a triangle with the exclamation mark picture on his phone. That's all it boots up to. So, he took it to T-mobile, they told him it's FUBAR, and sold him a new phone.
The fact that the thing boots to a recovery mode tells me that there's SOME way to un-FUBAR this phone. My friend is too technologically inadiquate to attempt to do any modifying, so I'm going to assume he was at whatever firmware level would hve been blasted out to T-mobile as of last Friday 01/15/2010.
If I boot the phone normally, it gives me the TriAngle. I pop open the keyboard and hit alt-L and the I get the Android System Recovery menu. at the bottom I get "E:CAn't open /cache/recovery/command"
I've spent all day bouncing around this forum, and many like it, downloaded all sorts of G1 fimwares trying to go back to RC29, RC28, 30, 33.. gah! The latest one I'm trying to update to is "signed-kila-ota-116143-prereq.TC4-RC19+RC28+RC29.zip" Which i rename to update.zip . I hit alt-L, select 'update from SD card' It goes through:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update package....
Installation aborted.
That's it... no more log than that.
I've done the Alt-W, and Alt-S.. wiped cache partition. I think playing around with the recent firmwares might be fun, but I'd like to get this bad boy reset back to factory defaults. I've read the forums here on how to do that.. but all of the procedures fail.
I can get Windows 7 to recognize the phone, but I cannot access the sd card while it is in the phone. I've been transfering data to it by taking the sdcard out, and putting it into a known good SD card reader. I've formatted the sdcard to FAT16, and FAT32 quick and not quick.
Seriously.. why is this so complicated? Now I need some serious digging assistance. Is there an interface that will allow me to directly talk to this phone via the USB cable? How can I force an firmware onto it? Clearly something is functional, or I would get no I/O. How can I get this silly thing back to where it was? I know this thread seems like a redundant one, but as far as I can tell, its not. The typical procedures posted here don't seem to work, but I'll be happy to run through any steps y'all suggest. I'll resign that it's been bricked if that's really whats happened.. but I'm not ready to throw this unit away yet.
Ask questions.. let me answer them. I know this team can get this phone working again.
Thanks y'all.
--Rob aka The Austin Slacker.
Have you tried the RC29 DREAIMG.nbh file?
http://forum.xda-developers.com/showpost.php?p=4593084&postcount=1
Roadmasta01 said:
Have you tried the RC29 DREAIMG.nbh file?
http://forum.xda-developers.com/showpost.php?p=4593084&postcount=1
Click to expand...
Click to collapse
bingo !
sounds like your friend tried to flash something he shouldn't have. or messed around with stuff he shouldn't.
as far as taking it to the store, and accepting their suggestion to "GIVE US YOUR MONEY!" that was a mistake.
the phone is likely fine, and maybe you'll buy it from him for cheap, then fix, resell/use.
good luck, should be easy.
The "press camera and power to get to bootloader" procedure. I've tried holding the Camera while pressing power over and over and all I get is the triangle. However if I press power and the "back" button (swooping arrow to the left), I'll get the bars screen, and a Gray screen telling me to press send to restore.... Which is all good, but there's no progress or any thing to indicate that i've done something by pressing the send button.(based on cell phone standards, I'm assuming "send" is the green "call" button.
Is this normal?
No yeah.. he gave me the G1.. its mine. I just need to fix the little bugger.. .. well.. then laugh at him
Ok.. one more day (well ok.. couple hours) of fiddling with this thing, and i'm begining to wonder if Microsoft was involved. I'm not able to get this poor G1 to do anything new. I tried using a different SD card, hoping perhaps the one I got with it was bad... no dice. camera + power doesn't do anything useful.
I can connect it to the PC.. but i can't see the data card that way. adb devices reads no output, so its not correctly attaching to the PC (tried Windows 7 32bit, and Windows XP 64bit).. There's gotta be a good way to force a known good image onto this silly thing.
Is it probable that the internal memory has gotten corrupt somehow? I know someone out there's got the golden suggestion, please do tell if you do. I'd really like to use this phone.
--Rob
If you can get into fast boot (the tri color screen) there are ways to flash it... try getting into your tri color, then plugging in the USB cable and see if it switches from Serial 0 to USB at the bottom, if so you are golden to flash using the fast boot method.
There are guides around on how exactly to do that, as well a couple places that you can download the official RUU that will do all the hard work for you!
gah.. nothing doing. I can hit Back and Home, and end up with the tri-color screen for about 1/5th of a second, then a gray screen saying:
This operation will delete all your personal data, and reset all settings to manufacturer default. Press Send to restore manufacturer default, or press other keys to cancel.
At this point, the unit is dead. I can remove the battery, and continue on my little quest.. but hitting *any* key at all (including the Send key) will not produce any sort of output. I've tried pressing Send one time, then setting the phone down for a full hour (watched a netflix show) nothing. I can't power it off either w/o removing the battery.
I would throw in the towel.. but from all the research i've been doing, it seems as if this one is behaving in a manner in which other forum users havne't posted. Maybe by continuing to try options and post results, a positive outcome will come out, and someone else who has a G1 behaving this way will have an easier time.
... or y'all can tell me that its toast and to bugger off.. ha ha.. either way.. I continue to google. If you can think of anything, please toss it out.
OH!.. tried an RUU.. found one called. RhodiumSPLRelocker Looks promising.. but can't see the device when attached to the PC... yeah.. guess the phone has to have a functioning OS before that will happen...
You would want a Dream RUU... I looked around a bit and couldn't find one. Maybe someone has a quick link?
Double check that your SD card is formatted FAT32 and see if you can get ADB to see it when on that greay screen.
I've formatted the SD card in FAT32 multiple times.. I even questioned if my Windows 7 32bit would do it, and formatted it on a laptop running XP 64bit. adb doesn't seem to see it ever.
I don't get why I can't get it into fast boot. I've been looking on ebay for dream G1s with broken screens.. heh.. I guess i'm preparing for the worst. really sad, becasue this G1 was actually pretty well taken care of. My friend didn't do anything he shouldn't. HE woke up one morning and it was like this. He lives out in the country.. so he gets pretty spotty signal. I'm wondering if T-Mobile didn't push out an update, and it got interrupted by signal loss.
By the by... I've been doing all this work w/o a SIM card. Does that matter?
austinslacker said:
(based on cell phone standards, I'm assuming "send" is the green "call" button.
Click to expand...
Click to collapse
its not the green send button -- its the red end button
see below extracted from http://theunlockr.com/2009/07/05/how-to-unroot-your-t-mobile-g1/
Load the DreaIMG.nbh File
1. Download the Original DreaIMG.nbh file:
http://www.megaupload.com/?d=XXSQ0T7W
2. If the file downloaded above downloads as a .Zip file, please unzip it first then put the DreamIMG.nbh file that is inside on the SD card, NOT in any folder. (If you did Section I the phone is off still, take out the memory card, put it in the MicroSD adapter and plug it into your computer to transfer the file over, since your G1 won’t turn on right now if you did Section I above. Otherwise if you did not need to do Section I above, then you can just put it on the SD card normally using the usb cable and the phone).
3. Turn the phone off if it is on.
4. Turn on the phone by holding the Camera button and the End key until the bootloader screen turns on.
5. Hit the End key to start the update. DO NOT INTERUPT THIS PROCESS.
6. Once it is done, hit the trackball to restart the phone. You now are on the stock firmware RC29
austinslacker said:
The "press camera and power to get to bootloader" procedure. I've tried holding the Camera while pressing power over and over and all I get is the triangle. However if I press power and the "back" button (swooping arrow to the left), I'll get the bars screen, and a Gray screen telling me to press send to restore.... Which is all good, but there's no progress or any thing to indicate that i've done something by pressing the send button.(based on cell phone standards, I'm assuming "send" is the green "call" button.
Is this normal?
No yeah.. he gave me the G1.. its mine. I just need to fix the little bugger.. .. well.. then laugh at him
Click to expand...
Click to collapse
You mention that you can access fastboot by pressing the back button while turning it on, isn't that how the hero gets into fastboot? maybe your friend tried flashing a rom that was meant for the hero. if you have access to fastboot you should be able to flash a new image from there, just place the image file in the root of your card and follow the fastboot instructions
Also if fastboot isn't doing it for you have you tried adb? if you don't know what that is look it up I've seen a couple guides on how to do it and they are really detailed.
Im having the same problem, Im stuck in the recover triangle of death. Ive done the alt+w and reboot, the RC29 DREAIMG.nbh , the update.zip, camera+power, I cant get the gray screen to pop. Nothing, its brickkkkeeeddddd, FUBAR. There has got to be someway I can reload this G1. I wasnt trying to root it or anything. I was bowling and then it triangled on me. Anyone have any ideas at all on how to fix it?
Triangle of Death
I'm from Brazil, I can't take it to t-mobile to fix...
when i tried to root my G1 did the downgrade perfectly, the screen was just as it was suposed to be.
But in the recovery mode boot, appeared this triangle with an exclamation...
what do i do now???? help plz!
deftoneage12 said:
Im having the same problem, Im stuck in the recover triangle of death. Ive done the alt+w and reboot, the RC29 DREAIMG.nbh , the update.zip, camera+power, I cant get the gray screen to pop. Nothing, its brickkkkeeeddddd, FUBAR. There has got to be someway I can reload this G1. I wasnt trying to root it or anything. I was bowling and then it triangled on me. Anyone have any ideas at all on how to fix it?
Click to expand...
Click to collapse
Any one have any ideas? hell ill pay someone to fix it for me
The only idea I have is make'ing an goldcard so your sure your phone accepts the update (dreaimg)... other than that...
Sent from my HTC Dream G1 using the XDA mobile application powered by Tapatalk
Any chance the home button is stuck? I'm not 100%, but I think if you were to hold home, camera and power, the recovery would come out on top.
Home button is not stuck, and cant seem to figure out the CID of my SD card since my phone is unaccessable.

Is my HERO REALLY BRICKED!!!???

my phones rooted and I have the Regaw mod ROM load on there, and its been good for a couple days now. Last night I went to sleep and forgot to charge my phone so figured the battery died. I plugged in it for about 10-15mins or so to turn it on and all it does is hang on the HTC bootscreen!!!! then I try to boot into recovery and all I get is at the bottom of the screen it says "Build : RA-HEROC-v1.5.2"!!!! Does this mean my phone is bricked!!!???
Remove the battery. Put it back in. Try to boot.
There are other solutions. As long as it turns on there should be a way to unbrick. Try RUU as well.
i tried the battery pull a couple times im trying the RUU now but what the hell could have bricked my phone over night?
I think what the guy in the 2nd post is trying to say, is that if it is booting, it isn't bricked.
It would be bricked if you couldn't do anything with it, then its like a brick.
I know it is probably a bit scary but ify ou can boot it at all, you most likely can fix it.
Did you make any changes (remove any files?) yesterday at some point, and this would have been the first restart?
I don't know, it could be a number of things.
It is probably not bricked. I bricked my G1 so I have some experience in that area. If you can boot into recovery it is not bricked. When I bricked my G1 I couldn't even get to recovery. let it charge a bit. Th battery is probably just dead. OR. take the battery out and plug it in and try to boot. Let it boot for about 15 mins or so.
no i didnt change anything at all, except my sd card said it was corrupted after unplugging it from my PC improperly. and I didnt reformat it right away. I just tried to RUU and i got an Error 170 a USB connection error
BAttitude7689 said:
no i didnt change anything at all, except my sd card said it was corrupted after unplugging it from my PC improperly. and I didnt reformat it right away. I just tried to RUU and i got an Error 170 a USB connection error
Click to expand...
Click to collapse
Where does the recovery image read from? I know we put it in the root folder of the SD, but does it actually boot from there? Could be your issue...
are you runnings apps2sd or whatever it is called?
yes that possibly could be my issue!! how can i fix my sd card or what should I do?
no I am not running apps to SD
BAttitude7689 said:
yes that possibly could be my issue!! how can i fix my sd card or what should I do?
Click to expand...
Click to collapse
BAttitude7689 said:
no I am not running apps to SD
Click to expand...
Click to collapse
I'm not so sure. I am pretty green when it comes to all this rooting stuff. I'm just trying to help figure it out.
Maybe try booting without the SD card in the phone? Could help to narrow down the issue.
I'm sure someone with more knowledge could help.
yea im booting it now with NO SD and its still hangs at the HTC screen
BAttitude7689 said:
yea im booting it now with NO SD and its still hangs at the HTC screen
Click to expand...
Click to collapse
Can you try plugging it into your USB connection and getting into the ADB shell (in CMD) to see if you can access the phone even though it seems stuck.
I know I did this and was able to monitor the logcat when I thought it was stuck, but it was really just doing a whole bunch of stuff.
Just an idea....again, I'm just fishing here trying to help you out.
it tells me error: device not found
i went to (CMD) then cd C:\android-sdk-windows\tools and then adb devices
you might have to manually rewipe your recovery partition in cmd. I had to do that after the official ruu messed up my phone- it wouldn't boot at all, I had to use the fastboot command: fastboot oem boot, then using my nandroid backup restored my recovery.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
im kinda of a noob at some of this so kinda need to explain it out lol ...I just booted to recovery and pressed *vol up* and got me to Fastboot Mode then it says press <Menu> to reset device, should I do that option?
okay i pressed menu and all that got me was it hanging again at the HTC screen.. should i do all of this with my SD card in or out of the phone?
When you boot it and it gets into the "partial" recovery mode, does the PC see the phone? Can you put RA-Heroc-1.6.2 onthe SD card from there? If so, I'd try flashing the new recovery from ADB...very easy...and see if that gets you a bit further along.
You might also try cheating a bit. See if you can pull a nandroid from the SD card (might have to do this with a card reader), then get Flipz's Kitchen and restore the Nandroid after you boot into recovery.
Just a couple of things I'd try....from experience...
S
okay this is what happens i press vol down and power then is load where the androids are on skateboards and it says press <HOME> for recovery along with a Fastboot mode and Simlock option. I press home and then I see the HTC screen for about 30 secs and then where I normally would see the recovery menu with all the green writing i see all black except at the bottom is says
Build : RA-heroc-v1.5.2
sfox said:
When you boot it and it gets into the "partial" recovery mode, does the PC see the phone? Can you put RA-Heroc-1.6.2 onthe SD card from there? If so, I'd try flashing the new recovery from ADB...very easy...and see if that gets you a bit further along.
You might also try cheating a bit. See if you can pull a nandroid from the SD card (might have to do this with a card reader), then get Flipz's Kitchen and restore the Nandroid after you boot into recovery.
Just a couple of things I'd try....from experience...
S
Click to expand...
Click to collapse
To follow this and break it down a bit more for you:
1. Plug in USB with phone off
2. Turn on phone and get it to the "blank" recovery screen.
3. Run through the flashing of the recovery rom image again (see HERE) but start at step 13 or so.
Try doing the above post..

Well chaps, I'm beat. Please help me get my phone working again.

Some backstory first:
There I was, happily running Villain 5.3, complete with apps2sd, and the latest radio. So happy in fact, I decided to ring my friend to tell him about it. So I opened up the dialler, typed "col" and the phone hung on me. So I rebooted it, got stuck in a boot loop.
No problem I thought, I have just installed the vanilla lockscreen, I bet that has something to do with it, so I booted into recovery, and tried a nandroid + ext restore.
It said it was restoring, but the screen simply filled with the progress dots, and continued to do so until the battery died.
Then to my horror, after a recharge, the recovery image is unable to detect the SD card. “E:Can’t mount /dev/block/mmcblk0 [...] Can’t mount sdcard”
It may be worht mentioning, I tried a full wipe, but the progress bar that usually progresses didn't. The on screen status did change from wiping system to wiping cache, but once wiping was finished, the phone hung again, requiring me to pull the battery.
I did some research on potential remedies, but adb devices can't see any devices. Fastboot devices does, but as soon as I try to boot a recovery image, I get error: remote access not allowed, or something similar.
I even tried renaming a rom.zip from an RUU to HEROIMG.zip and loading hboot, but nothign happens.
After much jiggery-pokery I have finally figured out how to get an RUU to actually connect to my phone, but once that is running I get Fail-PU on every part of the update except the radio.
I really can't see any other solution to my problem, either thinking myself or trying advice I find sprawled across the internet, and I can't get t-mobile to fix it because I have invalidated my t-mobile warranty by putting a stock rom on, and the manager of the shop refused to acknowledge I have a right to repair under the sale of goods act.
Any help would be appreciated, and any information desired will be forthcoming.
EDIT: Oh yeah, whenever I start an RUU, it says "Current Image: Error_main (too many links))"
If you are getting remote not allow in fastboot, its a problem witj a perfect spl I think? Failing that try the command fastboot erase userdata -w this should basically do a factory reset on the device
FAILED (remote: not allow) on that too I'm afraid.
I tried the key combo for the factory reset, nothing much happened there unfortunately.
you will have to look into making a goldcard i am afraid :'(
Check here and be patient i had to make it 3 times to get mine to work.
Also i had to use a different RUU to what jesterz suggested,let me google that for you....
www.lmgtfy.com
Good luck!
Ha, I tried every RUU but that one, annoyingly.
I was thinking I'd be knackered as my phone can't connect to adb, but fortunately I still have the generated goldcard image sat in my gmail account, so I'll get right on making a goldcard.
Thanks!
just a guess here..
sounds like...
the SD card might be bad / flaky....
An update!
I don't know if my phone would ever boot after I did this, but I tried it anyway:
fastboot oem rebootRUU
fastboot flash zip rom.zip <----- T-Mobile ROM (all others seem to throw up customer ID error.)
So now, as far as I can tell, I have an (almost) complete system loaded onto my phone under the partition "zip" (I say almost, because userdata won't flash).
However, due to userdata not flashing, I'm stuck in the RUU bootloader bit with the picture of a ROM chip and a big, red cross through it.
Anyone have any ideas how to get out of this screen, without ADB or an SD card (I tried 3, none would mount), or a recovery image because even if I could boot into it, it is now no longer a custom one. All I need is userdata to flash, and I'm good to go.
Also, would my phone actually boot as I flashed everything into "zip," a partition that I just made up.
Had a similar nightmare once. Solved it completely and documented it on the MoDaCo forum, so you may want to give it a try. Google for "No ADB & No SD" and see my post #81 from April 4. Good luck!

[Q] First blue screen, now boot loop.

Hello XDA-devs forums,
I'm having an issue since yesterday.
I have rooted my Huawei Ideos X5, and it ran fine for a day or so.
However, when my battery ran out it shut down into a completely blue screen.
When I tried booting it again, this just showed me a blue screen as well.
Now, I fixed this issue by connecting the phone to my PC after booting it with the Vol+ and Vol- pressed.
(So you get the pink/purple screen)
However, when I opened the phone on my PC, all I saw was a "239 MB" "empty" space, and it should have ~2GB..
I placed a backup copy I saved of my "image" folder in that 239 MB storage, and it booted.
However, today I hooked it up to my PC again to see if it magically changed..
And I couldn't access the 239 MB space anymore.
When I tried fixing the issue with a reboot of the phone, that just caused it to get stuck in a booting loop.
So now I'm stuck with a phone that keeps trying to boot itself,
and I can't access it on my windows PC.
I can, however, access 4 different folders of the phone on my linux notebook.
Now, my question is: can someone with a good understanding of problems like these please help me out?
I'm getting kind of fed up with it, as I've only got the phone for 2 days now.
Thank you in advance, and thank you for taking the time to read this.
Have you tried removing the battery for 5 minutes and then putting it back in?
After this, what happens when you press VOL+ and Power?
How about if you press VOL+, VOL- and Power, without the USB cable?
Hello Katu, thank you for posting.
Regarding your questions:
Yes, I have tried to take out the battery for 5+ minutes- it didn't change anything to the situation unfortunately..
If I press VOL+ and Power at the same time, the device boots into recovery mode.
In this I have tried to format the device in order to reset it to factory defaults, but this did not help either.
When I press VOL+, VOL- and Power, the phone boots into the pink/purple screen.
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
PlanDreaM said:
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
Click to expand...
Click to collapse
Well, I used an original ROM:
U8800 V100R001C00B136(Overseas General version)
And that resulted in the boot.img being corrupted, so I can't even overwrite that anymore.
Also, this is what I see when I hit VOL+, VOL- and Power at the same time to boot into safe mode, and connect it to my PC.
img69 [dot] imageshack [dot] us/img69/244/10101191548pm.png
julle131 said:
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
Click to expand...
Click to collapse
I installed the official B136 rom, and after it rebooted, it would just hang on a black screen.
(it used to show the IDEOS or Android logo when it booted)
Hmm mine came with this Rom
U8800 V100R001C00B135SP01 ( general )
Looking at your name you're from the Netherlands ( so am I )
where did you get this 136 version from ?
I would try to put this one on it
You have to put the 'dload' folder into the root of your SD Card,
then boot into boot-loader, after that it'll automatically flash back to the stock Rom.
1 Format SD card
2 On the SD card, create "dload" folder
3 Put the unzipped Rom into "dload" folder
4 Then boot to bootloader (pink screen)
Yes, mine came with that version as well.
However, I couldn't find it anymore and thus downloaded the version I said earlier.
Also, I did everything as you described, except step 4.
You have to boot to recovery instead of bootloader. (VOL+ and Power)
Anyways, I managed to get ClockworkMod's recovery.img on my phone,
and from there on install a custom ROM on the phone, which magically got it working again - even though it didn't work earlier.
Thank you for reading my thread and taking the time to reply to it.
My issue has been resolved.
just for the record, flashing a stock rom is different from flashing a custom rom..
the 4 steps described by Gman2oo6 is the correct way to flash a stock rom (and it is written clearly in the document that is in the stock rom zip file)
[edit]
step (1) is not a necessary step though..
Yeah, I noticed that.
What I did was format my SDcard with FAT32,
and put a custom rom (update.zip) on the SDcard.
I then booted ClockworksMod Recovery and installed the custom rom from the SDcard.
When I tried installing the stock rom, I just followed the PDF file's instructions that came with the stock rom.
hey i udated to GB 2.3.4 (official)and i didnt like the it cuz the wifif ddnt work and the bluetooth also the DATA so itryed to downgrade to 2.2.2 original official and it did the 2/2 steps intalled and when it restarted it did not want to turn on all that happened was it vibrated and thats all so i left it on like that and when the battery died i plugged it in to the AC and the LED turned on red and the touch kkeys also but not the screen so i really NEED help!
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
i tryed it
nope nothin good happened all that happens is a blank screen with nothin on ,LED is off and the touch keys are off. it justz vibrates and when i put the battery it turn the LED on to red and the touch keys turn on but then like 5 min later the LED and keys turn off
astewart said:
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
Click to expand...
Click to collapse
ok heres what i did i wanted to upgrade my phone to the newest version GB 2.3.4.So what i did was download the update and i followed the installation steps i successfully updated to Gb 2.3.4. so like i was checking how it look and the new feature but when i wanted to go on the android market i went to setting and turn on the wifi and it said Error and then i tried the Bluetooth and it said Error also so then i put my SIMs card in and i was like imma use DATA then and when i restarted my phone it had service but no HSPA+ or Edge or GPRS so like i just hatted my phone from their so then i was trying to root it but iddnt know how to do that so like i read this website and i got the UPDATE.APP or 2.2.2 AT&T did the same steps of the installation of BG 2.3.4 and it went to the process and 1/2 stepp good it passed and then 2/2 also passed it installed it and when it said Successively Installed it said Restarting and the scrren turn of and it vibrated and thats all that happened and i left it like that for the whole days and nothing happened
Do u got any idea?
When i connect it to my laptop it says installing drivers .then its says sucesfully installed drivers ready to use. so then i got to Device Manger and i check what has been installed and their it said USB Human interface device and HID-compliant device WHAT DOES THAT MEAN??
Not sure about the HID (human interface device) probably just the way windows sees the device for interfacing with it. With regards to the not booting I have read a lot of people saying that you need to factory reset and clear cache after the upgrade/downgrade. With the phone off, turn it on by long pressing volume+ and power on button till you get the blue recovery screen and from there you can reset factory/ data and also clear the cache. from what I see this should clear up the problem and start up. Please read this thread, it may help you somehow..... http://forum.xda-developers.com/showthread.php?t=1420728
Hope this helps a little
U mean Boot recovery and imma try it and thanks ill check it out
Sent from my MB300 using XDA App
all that i know is that if u customized your partition, it'll bootloop,
so go back to stock-partition ^^
How do I do that got like the steps or video?
Sent from my MB300 using XDA App
when i downgraded to 2.2.2 i installed this V100R001C00B138SP04CUSTC185D002
http://forum.xda-developers.com/showthread.php?t=1251250 got it from that link
Looks like you are not having much luck. Did you try to factory reset?
astewart said:
Looks like you are not having much luck. Did you try to factory reset?
Click to expand...
Click to collapse
well how do i do that do i need to got to the purple/pink screen or bot recovery cuz i cannot access that my phone doesn't do anything pretty much

Categories

Resources