Develop Bugs

[FIX] Working on a solution for unfortunate I9000M users with dead internal SDcard.

Hello!
I learned some new simple skills with the Gingerbread port that can allow me I think to produce a complete workaround for unfortunate I9000M users.
I9000M is a phone very similar to the Galaxy S GT-I9000, sold as "Bell Vibrant" in Canada.
This model is affected by a anormal % of defective model, so high I feel really bad for users owning one of them.
During Voodoo development, I was in contact with lots of them, including one with its internal SD dying live. Painful experience for the owner for sure and also for me helpless.
Now, to help me help you, I will need the collaboration of some of you. Not necessarily with a perfect condition working phone.
A phone affected will allow to verify the success of the operation.
UPDATE
It turns out there are several states of "dead" or "dying" phone, something I didn't anticipated based on the previous reports.
1/ Phone booting only if you plug an External SDcard
This is where I can do something not over-complex to make the phone work 99% normal, with access to the sdcard as internal storage and on USB.
There is still something to do in this area.
2/ Phone not booting at all including with an External SDcard inserted
I could fix them in theory, but my previous remove attempts were unsuccessful, using a special baked kernel for this occasion where unsuccessful for some reason.
I could maybe develop a solution if someone sends me its dead phone.
But I guess his best option is to send it to Bell instead!

Okay what do I need:
If possible, remote adb access to:
- a normal working phone
- a phone barely working using the external sdcard as "fallback", without the ability to use it as sdcard/USB.
What do you need:
- A I9000M
- An external SDcard
This will be done real time on IRC, join us at this channel: http://bit.ly/gQMeSC
Ask if you need help to setup that

Very good idea that will help many people who have wasted money on a broken phone hopefully! You are a saint my friend
Sent from my GT-I9000 using XDA App

Sign me up! What do you need?
EDIT: Nevermind, you posted what you needed before I posted. I can help. I have a fully functional i9000M on Froyo and one dead i9000M phone. No matter what I do in Odin using stock Bell firmwares, it will not ... run. Won't and can't mount the internal for the life of it.
Anyways, how does one grant remote ADB access?

PreemoX2 said:
Sign me up! What do you need?
Click to expand...
Click to collapse
A direct access to the phone rooted via remote adb would be perfect.

Mange to do that: SGS nobel prize

DocRambone said:
Mange to do that: SGS nobel prize
Click to expand...
Click to collapse
From someone residing in Stockholm, it's something
But no kidding, I think it can be done in just a few hours with direct access to phones

supercurio said:
From someone residing in Stockholm, it's something
But no kidding, I think it can be done in just a few hours with direct access to phones
Click to expand...
Click to collapse
Would be great, had so many bricked phones when we (with Idan) made a bell rom, really scary.
Ps check here:
http://forum.xda-developers.com/showthread.php?t=880823
Loads of users u can assist

I flashed a couple of Doc's roms and my sd died. I wish all the best to this project, but am too paranoid to do any more flashing until i get my spare back

Always curious if a fix can be found. I'm in the repair loop now but if my repaired unit comes back and fails again I may just skip the process and use information you can learn in this thread.
Great stuff supercurio.

The issue is more complex and challenging that expected.
On some phones the internal SD is still here but dying, and on other phones the internal SD is not detected at all (which make things easier)

My first two phones, after they died, mmcblk0, mmcblk0p1, and mmcblk0p2 were all missing, then when I inserted an external sd, the phone started using that as the mmcblk0/p1/p2.
On my third phone, when it died, mmcblk0 was missing, but mmcblk0p1 and mmcblk0p2 were still there (I have no idea how..) But inserting an external sd did nothing...
On my fourth phone death, mmcblk0 was there, but mmcblk0p1 and mmcblk0p2 were both missing... Again, inserting an external did nothing...
The fourth time I was actually beside a computer when it died so I was able to look at adb logcat to see what it was doing... all it kept saying was a lot of various apps not being able to write to /data/data, then when I rebooted, it never came back
First two deaths: With an eclair kernel, phone would show the Samsung GT-I9000M logo, then turn off. You could then insert an external sd card and have it boot into Android. With a froyo kernel, I could only access recovery, but nothing else would boot up.
Last two deaths: With a froyo kernel, phone would show the Samsung GT-I9000M logo, then turn off, and turn back on, and turn off... till I pulled the battery out. With an eclair kernel, I could boot into recovery, but that was it.
I have a product exchange plan that if my phone dies I can go in to Futureshop and exchange it for a new one, so I don't have the dead phones anymore.
Hope this information is of some use...

got my phone dec 4th and unlocked, flashed 3 buttons fix and flashed jk3 via odin + cleared everything the very same day.
the next morning got a bunch of FC, flashed jk3 via odin again. This time cleared all data before / after flashing. The very same day my dog ate part of the bezel ( yes, it sucks.... )
JK3 was working fine, but battery was dying on me every 6 - 8 hours. Then I upgraded to jk4 via odin again using a image dump from the forum.
battery was a bit better, but after 4 days it died. It was right after *draining the battery* in my pocket and it got into the same boot loop, vibrating, flashing buttons state.
Gave the battery a good 4 hours charge, and still no luck. Tried pulling out the battery, SIM card and still nothing.
Was able to flash jk3 again, followed by a jk4 upgrade via KIES. at this stage phone got very usable, battery was good, all apps working. But I decided to get away from it as I think we might have more than 1 problem here ( hardware and software might actually be different problems ).
So I flashed jh2, got CWM going and updated to Doc's Bell rom 1.3 with jk3 modem.
It's going strong for the past 5 days, gps is still ****, battery is good though, and no FCs.

So last week I received my shiny new SGS, it replaced the dead one I returned earlier. My corp store replaced it without asking too many questions. The previous one I played with, Flashed Roms, Rooted etc. Then one day it would boot normally until after the Blue Swirl, then nothing, only LED's would light. I even lost the ability to use Download and Recovery mode. While trying to fix it I encountered many errors most were related to the Internal Storage (not surprisingly). Anyway fast forward to today. My replacement SGS was updated via Kies to 2.2 JK4 almost right after I got it. The phone has worked flawlessly, until today. No root, no custom roms, no lagfix... STOCK Froyo. For some reason the battery drained incredibly fast today. I plugged it in after the battery died and let it charge for about an hour, tried to boot it up and I got as far as the first Galaxy S logo, then it would reboot, Galaxy S logo, reboot... etc.
Recovery and download still worked. And recovery mode showed the same Internal SD errors as my last phone. I have tried to flash a few Stock Roms using Odin, none have been successful. Always flashing Galaxy S. Ive somehow managed to lose Recovery mode, but still have Download.
Does any of this help? Ill probably have my phone for the next few days before I have to send it out. Anything I can try?
If you somehow find a way to fix this plague... wow... you will make ALOT of Bell users happy.. lol..

If this works make sure Samsung can't steal your method for themselves. It's exactly the type of thing they'd do.

Hi supercurio, I have a dead sgs and a working one. The dead one was bought to be use for the time I received my screen replacement from ebay but it died. I have mmcblk0p1 missing so the phone get a black sceen after S logo when flashed with 2.1 and it loop on the i9000m screen when flashed with 2.2 and I talk french as my first language (mais celui du Québec pas de France).
The only pronleme is that I cant acces recivery for now as I lost the 3 buttons combo when it died. I made a little 301k ohm jig to acces download mode. I would have to make another one to acces recovery cause for now I can only acces it after an odin flash and repartition wich make it reboot into recovery once the flashing is done.
Can I be of any help?
Sent from my GT-I9000M using XDA App

Im on my fifth one!
Save us!
Sent from my GT-I9000M using XDA App

supercurio:
I am one of the unfortunate ones who have had 3 i9000m's die. The first one was on 2.1 and the other two times were on 2.2. All three phones (when flashed with a 2.1 ROM to boot into recovery, said mmcblk0p1 was either corrupt, or did not exist. When mmcblk0p1 disappeared, so did mmcblk0p2.)
The phone that had 2.1 would boot into the OS with an external SD card inserted. But, can't install apps, and the phone said there is no storage to store anything, anywhere. Basically it was useless.
The phones with 2.2, when the internal SD crashed, both times, it would show the initial Galaxy S (i9000[m]) screen, but then reboot after 2 seconds and loop there. It doesn't even get to the boot animation part! Recovery doesn't work. All you can access is the download mode. Only after you flash a 2.1 ROM, it will go into recovery mode, but it will puke all over the place saying mmcblk0p1 cannot be formatted, or mmcblk0p1 I/O error.
The fact that it goes into the worst possible boot loop, (displaying the Galaxy S, i9000[m] screen for 2 seconds then rebooting without showing the boot animation) scares me, since not much can be done with a phone that does that.
I really hope you can come up with some sort of solution. I've owned the phone since August of this year, and if you add up all the days that I had it in my hands and working... I only had it in my possession for less than 30 days. The rest of the time (3 months+, its been in repair). The last time I sent it back to be repaired AGAIN, was mid november, and I still don't have the phone back...

I would say the best way you guys can help out would be setting up SSH access to your computer (if it's OSX or Linux based) - that way Supercurio can remote access the shell + access the phone.
It won't be a good idea to post SSH details on the IRC ofc, so flicking him a DM with the details would be best.
All you really need to do is install OpenSSH on your computer, and set up a limited user account (Just a regular user will be fine) - Forward port 22 through your router to your computer, and give Supercurio the details. Make sure the Android SDK is available in his home directory so he can use that.
Sort out a time for Supercurio to SSH into your computer, and make sure your phone is connected. Join up on the IRC at that time and he will speak directions to you as needed.
But indeed a good idea, I actually was thinking of a way to fix this too.

Thanks for your reply. We spent several hours fighting with a dead phone yesterday on IRC.
I update the first post accordingly.

[Q] Random shutdowns & bootloop on all roms!

Hi Everyone
I was hoping someone would be able to help me out as I’m a total Noob!
I have an HTC Desire on the Orange network in the UK. I started to get a few problems with my phone shutting down and restarting, my GF’s brother had been recommending that I root and flash a different rom for a while, and seeing as he has a Desire on the T-Mobile network and had never had any trouble with rooting his phone or any of the roms he used I decided to give it a shot.
I followed everything in Linkslovesandroid’s noob thread found here:
http://forum.xda-developers.com/showthread.php?t=1016084
I first tried CyanogenMod7 on GF’s brother’s recommendation, worked ok for a bit but I had problems with constant shutting down and restarting over and over again, is this called bootlooping? The only way to stop it was to remove the battery, even then it was no guarantee. Other things were going wrong like the screen freezing, certain buttons were unpressable etc.
I gave my phone to him and he couldn’t explain why such weird things were happening as his Desire experienced no problems at all. He suggested I try something different like GingerVillain. GV never loaded or booted up for me, I wiped data / factory reset, wiped cache, wiped dalvik, installed zip from SD, the rom would then install okay but when I rebooted the phone never ever got past the Alpha Rev S-off screen. This happened when I tried to install GV 2.5 and 2.6, I see that 2.7 has just been released but don’t see the point in trying seeing as the other 2 versions wouldn’t work.
I then tried Oxygen, again, worked ok for a while but started giving me random shut downs and restarts. Once I was driving down the motor way using sat nav software and the phone just shut down! I had to find somewhere to pull over to restart the sat nav software and again it restarted itself! Lol!
One day my phone went into an endless bootloop, no matter how many times I took the battery out the phone just wouldn’t stay on, I had to flash a new rom just to get the phone to fully boot up! I went back to CM7 but have the same old problems, so now I’m using MIUI and I’m still getting shutdowns!
What is wrong with my phone? If anyone has any ideas what I might’ve done wrong, or whats causing problems please offer your suggestions! I don’t really like the sense Roms, I’d like to try GingerVillain but I could never get it to install! I just need my phone to be stable enough to know I can send an SMS to someone without it restarting! If you need to know about Kernels or radios or anything please just ask me (and tell me where I can find out!) Like I said, I’m a noob when it comes to phones!

Same kind of problems here. Random restarts (no shutdowns) on various roms, including the original stock froyo. Happens mostly while installing stuff from the market.
Any ideas?

Sounds like the motherboard is faulty/hardware error. Send back to repair. Usually the kernel can cause problems and OCing (restarting), but you said, that it happens randomly on every ROM, so that means it is more likely a hardware problem.

I had this too, same symptoms sent it back to HTC, duff motherboard, back in 14 days and all working fine.
Only thing is it got reset to original contract so had to pay to unlock it and then root etc.
But well worth it!

Hi Guys
Thanks for your replies so far!
So is it likely that my motherboard was faulty all along? I used to get random restarts sometimes when I was on the sense that came pre-installed on the phone, but nowhere near as often as I get now I've rooted and flashed new roms.
Is it possible that I've damaged it in some way? That could get me in some trouble because when I rooted I'd have voided my warranty, if I send it back to Orange as faulty now they'll know and could pretty much tell me tough luck!
I've heard you can unroot and put your phone back to how it was, but they'd still be able to tell wouldn't they?
Has anyone ever sent a phone back for repair through Orange UK?
Thanks again for your responses so far guys!

For me it turned out that the SD card was corrupt in some way. Repartitioned and reformatted it, and this does help for now. Might try that first, before sending into repair.
Good luck!

reynard80 said:
For me it turned out that the SD card was corrupt in some way. Repartitioned and reformatted it, and this does help for now. Might try that first, before sending into repair.
Good luck!
Click to expand...
Click to collapse
I agree. If you have system files on your SD and if the SD gets corrupted you might get the result you've described.

That's interesting, the other night when I had such a severe bootloop that I had to flash a new rom just to get the phone to fully boot up, it only booted after I'd removed the SD card.
To begin with I was very happy because I thought I'd solved the problem and all I'd need was to buy a new SD card, however a short while later it happened again with no SD card inside at all!
I decided to give Ginger Villain another go hoping that removing the SD card after "install zip from SD card > reboot" would allow it to boot up, it didn't. Never got past the alpha rev screen.
How will I know if I have system files on the SD card? Should I maybe try the G-Parted stage of the noob guide again to reformat the card and create the ext-4 partition?
Thanks again for your time and help by the way!

dellaclearing said:
That's interesting, the other night when I had such a severe bootloop that I had to flash a new rom just to get the phone to fully boot up, it only booted after I'd removed the SD card.
To begin with I was very happy because I thought I'd solved the problem and all I'd need was to buy a new SD card, however a short while later it happened again with no SD card inside at all!
I decided to give Ginger Villain another go hoping that removing the SD card after "install zip from SD card > reboot" would allow it to boot up, it didn't. Never got past the alpha rev screen.
How will I know if I have system files on the SD card? Should I maybe try the G-Parted stage of the noob guide again to reformat the card and create the ext-4 partition?
Thanks again for your time and help by the way!
Click to expand...
Click to collapse
If your rom requires an sd-ext partition than it stores system files on the SD. Try a rom that doesn't require that. I would go as far as bringing the phone to stock just to verify if it's the phone or the SD. Bringing it back to stock is a requirement for you to return it for servicing if you realize that it's a problem with the phone not the SD.

paul.c said:
If your rom requires an sd-ext partition than it stores system files on the SD. Try a rom that doesn't require that. I would go as far as bringing the phone to stock just to verify if it's the phone or the SD. Bringing it back to stock is a requirement for you to return it for servicing if you realize that it's a problem with the phone not the SD.
Click to expand...
Click to collapse
Hi Paul, is it only stock roms that don't store system files on the SD or can you recommend a rom that doesn't require an ext partition as I'm not too sure what I'm looking for? I realise that I'll have to unroot before I can return the handset but if there's another custom rom out there I can test before unrooting that'd be good!
However, if you fully recommend returning the phone to stock to test then that's what I'll do!

dellaclearing said:
Hi Paul, is it only stock roms that don't store system files on the SD or can you recommend a rom that doesn't require an ext partition as I'm not too sure what I'm looking for? I realise that I'll have to unroot before I can return the handset but if there's another custom rom out there I can test before unrooting that'd be good!
However, if you fully recommend returning the phone to stock to test then that's what I'll do!
Click to expand...
Click to collapse
This ROM http://forum.xda-developers.com/showthread.php?t=896213 doesn't require SD for system files.

I'd first try the complete stock rom with a completely formatted SD card. You can be completely sure that there isn't a software problem with a custom rom.
If this doesn't work, try replacing the SD card. This did help for me.
If still no succes, send it for repairs.

paul.c said:
This ROM http://forum.xda-developers.com/showthread.php?t=896213 doesn't require SD for system files.
Click to expand...
Click to collapse
Thanks for linking me to that rom.
I did a bit of reading about roms that use ext sd partitions and have so far concluded that its for A2SD so an entire app can be run from the sd card instead of internal memory.
So anyway, I've just installed the Redux rom you linked me to that doesn't store sytem files on the sd, first 2 boots had a sudden shutdown and restart! I'm on the 3rd boot now, it's holding okay but I need to put it through its paces to see how long it can go and what sort of performance it will allow before it starts shutting down on me!

reynard80 said:
I'd first try the complete stock rom with a completely formatted SD card. You can be completely sure that there isn't a software problem with a custom rom.
If this doesn't work, try replacing the SD card. This did help for me.
If still no succes, send it for repairs.
Click to expand...
Click to collapse
Hi Reynard. If the Redux rom I've just flashed (less than 10 minutes ago) doesn't use the sd for system files, then if it keeps rebooting on me would that diagnose a faulty motherboard as reliably as using a stock rom?
I'm gonna unroot and flash a stock rom soon anyway, that way I can be sure before I send it back to Orange for repair, although apparently there isn't an official Orange UK stock rom available so I'm just gonna have to get as close as I can and hope they don't notice!

dellaclearing said:
Hi Reynard. If the Redux rom I've just flashed (less than 10 minutes ago) doesn't use the sd for system files, then if it keeps rebooting on me would that diagnose a faulty motherboard as reliably as using a stock rom?
I'm gonna unroot and flash a stock rom soon anyway, that way I can be sure before I send it back to Orange for repair, although apparently there isn't an official Orange UK stock rom available so I'm just gonna have to get as close as I can and hope they don't notice!
Click to expand...
Click to collapse
Probably there is a ROM just that it hasn't been leaked so I hope you won't get in trouble.

paul.c said:
Probably there is a ROM just that it hasn't been leaked so I hope you won't get in trouble.
Click to expand...
Click to collapse
Haha! Me too!

Dayamn! I didn't have a reboot all day on Redux, got home from work and installed Sygic sat nav software and the phone rebooted 3 times just while downloading the map! I had to remove the battery once as well.
Decided I'd just test Google maps navigation while driving to pick up the Mrs from work and it shut down on me
If I can get hold of another sd card to test I'll see if it makes a difference, but there's not really a lot more I can do now other than unroot and send it back to Orange. The strange thing is that it never used to reboot half as much on the stock rom the phone came with, and it never did it while I was sat nav'ing ever. It just used to happen randomly when I was texting or web browsing. Odd.
Where might be the best place to find the closest to stock rom for Desire Orange UK?

Just wanted to update you all.
I found my original SD card that came with the phone, I fully formatted it and then did a completely fresh install of Redux and performed the same tests and got the same results. Still crashed and rebooted! So that tells me it's the phone and not the card!
I'll be restoring to stock and calling Orange tomorrow to get a replacement / repair.
Thanks to everyone who helped me out along the way, your time and effort is very much appreciated!

Hi guys,
I made a goldcard and tried installing the stock ruu, it seemed to work but when I hold vol down and power on it still says:
AlphaRev
BRAVO PVT1 SHIP S-OFF
HBOOT 6.93.1002
I read on the Alpharev website that recent versions of Alpharev aren't overwritten by stock ruu's hboot so it must first be downgraded. I used android flasher to flash the Alpharev downgrader, then it just froze at the "why so serious" screen. I was advised to flash the stock bravo hboot found on the alpharev website, which I did and then I was finally able to install the ruu. Obviously I've done something wrong and I'm guessing its flashing the stock bravo hboot...
Would it be okay to use android flasher again to run just the downgrader image, and then using fastboot flash the ruu again?
Any ideas? I don't want to risk sending my phone back for repair still saying S-Off!

Okay, I kept reading through XDA and found a post by Dzumagos advising someone to do exactly what I just asked, use Android Flasher to run the Alpharev downgrader image and then reflash stock ruu, so I grew a set and tried it myself!
Bravo PVT1 SHIP S-ON
HBOOT-0.93.001
Voila! I'm now back to S-ON, so now I feel I'm ready to call Orange and tell them about the constant shutdowns and restarts, which have still been happening on stock btw, the phone also feels really hot too!
I just hope the replacement they send me is issue free!
Thanks again to everyone who helped out in this thread and in the orange uk ruu thread!
Cheers everyone!

[Q] Five Vibrates & Flashing Green LED - Am I Screwed? [FIXED]

I've had my DInc for over a year now, S-OFF and been through tons of different ROMs without issue.
I've been on MIUI for the past month and went to flash the newest weekly update tonight which worked fine. Cleared Cache and Davlik, flashed and then booted without issue. Everything working fine.
Went to reboot the phone, got the HTC splash and then the five vibrates with the flashing LED. Have to battery pull to get the phone to boot down. Phone will only boot if the phone is plugged into USB. Cannot mount the SD Card while in MIUI or in CWR and cannot view the EMMC either. HBoot shows S-ON now as well.
I've searched Google and here and it seems there have been no fixes in the past for this issue. Have there been any updates on this or is contacting Verizon/HTC for a replacement still the only resolution?
My dilemma is I use my phone for both work and personal and there is sensitive client information on the internal storage that I cannot access to delete. I also have no way to remove my custom splash screen or flash back to a stock ROM. If I can safely wipe the the internal memory then I would attempt a replacement if I can't resolve the issue myself.
Is there any way to fix this or at least wipe everything on the internal memory before I apply for a replacement phone?
Thanks guys!

If you can't format your internal memory, you may want to try running the ruu. That should definitely get you back to a usable point. At least I think it will. Not sure if it will help with your particular situation. You may want to research this.
Sent with my awesome sauce Incredible with some sweet CM7 action

FIXED!!
Ending up finding this thread:
http://forum.xda-developers.com/showthread.php?t=1110865
Which directed me here:
http://forum.xda-developers.com/showthread.php?t=695243
Followed the above directions and everything looks like it's working again! Only tricky part was getting the files in the SDCard as I don't have a reader for the PC. Had to throw them on an FTP, download them on the phone and then unzip on the phone.

hEaTLoE said:
FIXED!!
Ending up finding this thread:
http://forum.xda-developers.com/showthread.php?t=1110865
Which directed me here:
http://forum.xda-developers.com/showthread.php?t=695243
Followed the above directions and everything looks like it's working again! Only tricky part was getting the files in the SDCard as I don't have a reader for the PC. Had to throw them on an FTP, download them on the phone and then unzip on the phone.
Click to expand...
Click to collapse
I have an inc at home with this problem. Ill give it a shot... my daughter uses it now.

im having a hard time with the fastboot. I went into it and it installed some kinda driver but when i do the adb command it tells me that fastboot cammands arent recognized. I do have sdk installed. Im on Xp

[Q] Evo vibrates 5 times on boot, only hboot accessible

A few days ago while flashing a new rom, my Evo quit booting. I wouldn't consider myself a n00b, but I'm out of ideas. Here is what I have done:
* used unrevoked3 and unrevoked-forever to obtain root and s-off at least a year ago
* used CM7.1 stable as my daily driver
* used stock to update radios around the time CM7.1 went to stable
* flashed deck's ICS preview4 to test an app on 4.0, after doing a nandroid and wiping in cwm 5.0.22 (I think that was the version)
* the phone refused to boot, vibrating 5 times and flashing the green notification light
* going into hboot, s-on is back somehow
* recovery could only be reached if the usb was plugged in
* recovery could not mount the sdcard, so no nandroid restore
* tried several stock PC36IMG.zip until 4.24.651.1 finally flashed in hboot
* the phone still won't boot, either vibrating 5 times or showing the red ! triangle
* the 4.24.651.1 RUU tells me my battery is < 30% even though I let my phone charge all night
Any ideas would be greatly appreciated. I don't really want to pay $450 for a new Evo. Thanks in advance.

Custom rom name it the same as img and see if that works if all else fails ruu and revolutionary
Sent from my PC36100 using Tapatalk

VaughnOnix said:
A few days ago while flashing a new rom, my Evo quit booting. I wouldn't consider myself a n00b, but I'm out of ideas. Here is what I have done:
* used unrevoked3 and unrevoked-forever to obtain root and s-off at least a year ago
* used CM7.1 stable as my daily driver
* used stock to update radios around the time CM7.1 went to stable
* flashed deck's ICS preview4 to test an app on 4.0, after doing a nandroid and wiping in cwm 5.0.22 (I think that was the version)
* the phone refused to boot, vibrating 5 times and flashing the green notification light
* going into hboot, s-on is back somehow
* recovery could only be reached if the usb was plugged in
* recovery could not mount the sdcard, so no nandroid restore
* tried several stock PC36IMG.zip until 4.24.651.1 finally flashed in hboot
* the phone still won't boot, either vibrating 5 times or showing the red ! triangle
* the 4.24.651.1 RUU tells me my battery is < 30% even though I let my phone charge all night
Any ideas would be greatly appreciated. I don't really want to pay $450 for a new Evo. Thanks in advance.
Click to expand...
Click to collapse
I had this happen to me a little less than a month ago and it ruined my weekend. I fortunately have a repair plan with Sprint as a "just incase" practice, so I just flashed stock and removed root, then brought in my phone claiming it just "restarted" and the software crashed, breaking my USB and SD card controller. The people at Sprint thought it was just "lint in my MicroUSB port," I laugh and told them to turn it on and they looked at my with a puzzled "wtf did you do to it!?" look.
What caused my problem was my SD card was full when I attempted to backup my ROM. This caused CWM fail at a backup and bricked my phone. Is this what happened to you by any chance?
I never did "fix" my phone's usb/SD management issue, but was able to temporarily boot it, but was plagued with random restarts. I'd like to throw in some links but I'm pinched for time seeing as I need to leave for work. (Search XDA) There was a Android 2.2 image that was I able to flash in the bootloader that let boot fully. But it will erase all traces of root. - Before you try and do anything else, research into if there is ANYTHING you can do with adb over WiFi, because that was the one thing that I didn't try. What I'm saying is to do a lot of reading before you start flashing anything, plan out your attack before you execute it. Because I ended up digging myself a deep hole by just randomly flashing images.
Wish you luck man, sorry I wasn't of much help.

nrm5110 said:
Custom rom name it the same as img and see if that works if all else fails ruu and revolutionary
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Hboot finds the renamed CM7.1 zip and checks it, but does not offer to flash it. I assume this is because s-on is back. Also, I mentioned that RUU is claiming my battery is too low to flash.

OMGWTF_BBQ said:
I had this happen to me a little less than a month ago and it ruined my weekend. I fortunately have a repair plan with Sprint as a "just incase" practice, so I just flashed stock and removed root, then brought in my phone claiming it just "restarted" and the software crashed, breaking my USB and SD card controller. The people at Sprint thought it was just "lint in my MicroUSB port," I laugh and told them to turn it on and they looked at my with a puzzled "wtf did you do to it!?" look.
What caused my problem was my SD card was full when I attempted to backup my ROM. This caused CWM fail at a backup and bricked my phone. Is this what happened to you by any chance?
I never did "fix" my phone's usb/SD management issue, but was able to temporarily boot it, but was plagued with random restarts. I'd like to throw in some links but I'm pinched for time seeing as I need to leave for work. (Search XDA) There was a Android 2.2 image that was I able to flash in the bootloader that let boot fully. But it will erase all traces of root. - Before you try and do anything else, research into if there is ANYTHING you can do with adb over WiFi, because that was the one thing that I didn't try. What I'm saying is to do a lot of reading before you start flashing anything, plan out your attack before you execute it. Because I ended up digging myself a deep hole by just randomly flashing images.
Wish you luck man, sorry I wasn't of much help.
Click to expand...
Click to collapse
My sdcard has over 4gb available space. I flashed stock 2.3 in the bootloader but it still refuses to boot (as mentioned in the original post). As far as I know, you need to be able to boot to use adb. The only images I have tried to flash are stock images and CM7.1.
This is starting to look bleak...

I appologize I didn't see it man
Sent from my PC36100 using Tapatalk

VaughnOnix said:
My sdcard has over 4gb available space. I flashed stock 2.3 in the bootloader but it still refuses to boot (as mentioned in the original post). As far as I know, you need to be able to boot to use adb. The only images I have tried to flash are stock images and CM7.1.
This is starting to look bleak...
Click to expand...
Click to collapse
Sorry, my previous post was in a rush. (As is this one, lol)
Really? So your phone just screwed up out of no where while flashing the ICS alpha4 rom? Were you using CWM? Because if so, I'm switching to Amon RA asap.
Moving on, I know how you're feeling right now. But, I still have hope.
As previously stated, after ruining my EVO I was able to flash a PC36IMG.zip that allowed me to boot my EVO. I had to do some serious digging, but I found the thread I used with the ROM that worked http://forum.xda-developers.com/showthread.php?t=884060.
None of the old Megaupload links work, but this filesonic one does. Download it and flash it in your bootloader. Its signed, it should work. Try to flash it twice if anything. If it still doesn't work, try one of the newer ROMs. I'm only guessing that's the one that worked for me.
The only problem is that I don't think that's a 2.3 ROM, and we need a 2.2 ROM. Because the only root method that doesn't use a USB/SD Card is this: http://forum.xda-developers.com/showthread.php?t=701004 If you can get
If you can get your EVO rooted again with S-Off, follow this guide here: http://forum.xda-developers.com/showthread.php?t=695243 (Original) and you might be home free. But as of now, your goal is to find a stock 2.2 PC36IMG. Hopefully someone else can help here.
I sadly have to get to bed. Just got off work and I need to get some rest, another long day tomorrow. Good luck! I'll be back here next chance I get.

Same thing here
I'm having the exact same issue - flashed ICS alpha 4, now I can't mount my SD card. I don't have the red triangle of death, but I am getting the 5 vibrations on trying to boot - can get to hboot, and was able to *almost* get the SD card to mount using this:
http://forum.xda-developers.com/showthread.php?t=695243
but that only yielded ICS "preparing SD card" and "checking SD card for errors" indefinitely. I backed up and formatted my SD card, and this at least let me browse the empty sd card in Clockwork Recovery - I am in the process of copying my cwm backups back to the sd card in the hopes of being able to restore them from cwm. I'll keep you posted on what happens, and will most likely try to RUU when I get home from work. Puzzling that my s turned back on again as well, it's been off for well over a year...

Update on previous post
spoonydx said:
I'm having the exact same issue - flashed ICS alpha 4, now I can't mount my SD card. I don't have the red triangle of death, but I am getting the 5 vibrations on trying to boot - can get to hboot, and was able to *almost* get the SD card to mount using this:
http://forum.xda-developers.com/showthread.php?t=695243
but that only yielded ICS "preparing SD card" and "checking SD card for errors" indefinitely. I backed up and formatted my SD card, and this at least let me browse the empty sd card in Clockwork Recovery - I am in the process of copying my cwm backups back to the sd card in the hopes of being able to restore them from cwm. I'll keep you posted on what happens, and will most likely try to RUU when I get home from work. Puzzling that my s turned back on again as well, it's been off for well over a year...
Click to expand...
Click to collapse
*** Update ***
Ok, so after all that, I was able to restore my backup from within recovery, copy all of my data back to the sd card, and now I'm back in business...mostly. I still get the 5 vibrations on boot *unless* i'm plugged into the computer, and even then it's not a sure thing (usually takes 3 or 4 tries to get it to boot). At least I have a functioning phone again. Next step - RUU and factory reset, and see what happens. Again, I'll post back with my results. Hope this helps someone

[Q] Ahhh! CM9 Problems. Incompatible files? Really need guidance...phone not working!

Hi,
I trawled threads and guides before starting my upgrade from CM7 to CM9. Thought I had everything in order so set-off. Ended up in a bootloop when I was done. Managed to get the phone sort-of working by installing my previous CM7 zip. I installed just the CM9 file over that and it started working....to a point. It wouldn't take the ICS gapps but did take an older version which at least has my mail and contacts working but I can't get into Play and get regular errors for basic stuff, like clock etc.
I've tried what I can but am now plain stuck and could really do assistance. I'm comfortable with the install procedure (I think!) although realise now that I cocked up my back-up first time round. Have to live with that now. Just want to get to a functioning ICS install.
These are files running right now.
CM9-NIGHTLY-120329-Defy
gapps-20111128
Honestly can't remember which kernel is running now, and confused which should be running. 95% confident that mine is a red lense but never seen another to compare.
CM9_Kernel-signed
CM7_Kernel-signed
These gapps didn't seem to work.
gapps-ics-20120317-signed
gapps-ics-4.0.3-20111217
I'm UK based with a regular Defy. I followed the guide and links (also pulled files from elswhere when the probs kicked in) in here.....http://forum.xda-developers.com/showthread.php?t=1386680
I have posted the problem in there but not sure it's the best place. I'll put a note in there to say I've started a thread. Don't want to upset anyone by double-posting!
Did I mention that I really could do with some guidance?!!!

Gobsheen said:
Hi,
I trawled threads and guides before starting my upgrade from CM7 to CM9. Thought I had everything in order so set-off. Ended up in a bootloop when I was done. Managed to get the phone sort-of working by installing my previous CM7 zip. I installed just the CM9 file over that and it started working....to a point. It wouldn't take the ICS gapps but did take an older version which at least has my mail and contacts working but I can't get into Play and get regular errors for basic stuff, like clock etc.
I've tried what I can but am now plain stuck and could really do assistance. I'm comfortable with the install procedure (I think!) although realise now that I cocked up my back-up first time round. Have to live with that now. Just want to get to a functioning ICS install.
These are files running right now.
CM9-NIGHTLY-120329-Defy
gapps-20111128
Honestly can't remember which kernel is running now, and confused which should be running. 95% confident that mine is a red lense but never seen another to compare.
CM9_Kernel-signed
CM7_Kernel-signed
These gapps didn't seem to work.
gapps-ics-20120317-signed
gapps-ics-4.0.3-20111217
I'm UK based with a regular Defy. I followed the guide and links (also pulled files from elswhere when the probs kicked in) in here.....http://forum.xda-developers.com/showthread.php?t=1386680
I have posted the problem in there but not sure it's the best place. I'll put a note in there to say I've started a thread. Don't want to upset anyone by double-posting!
Did I mention that I really could do with some guidance?!!!
Click to expand...
Click to collapse
To install ICS from scratch first make a backup of evrything you would like to hae later and then refer to the below mentioned link and install ICS:
How To Flash ICS(Defy Builds)
1:Head Over To Stable recovery
2:Wipe Data
3:Install ZIp from SD Card
4:Select ICS(Defy) .zip
5:Flash
6:Flash CM7 Kernel
7:Clear Cache and Dalvik Cache
FIrst Boot will take some time...
Click to expand...
Click to collapse
Ref: http://forum.xda-developers.com/showthread.php?t=1432100
Hope this helps!!

Thanks,
I'll have a good look through that thread tonight. I thought the CM9 kernels were the right one for my red lense defy......?
Should I just leave installing the Gapps zip until after everything else is done? I assume using one of the ICS gapp files is fine?

I installed they Defy+ nightly by Quarx:
http://quarx2k.ru/cm9-nightly-defy+/CM9-NIGHTLY-120330-Defy+.zip
This should already contain the GB kernel right? I flashed it anyway, just to be sure.
I have the Red Lense Defy, it's detected as a Defy+ now and the camera works.
HOWEVER, i had to flash the 'Batter fix for Red Lense', see first post here http://forum.xda-developers.com/showthread.php?t=1432100
This actually caused me a few hours sweat, since i did not flash it at first and then thought my battery was dead. It went empty after an hour or so, and then there was this battery you see when it's charging when then phone is powered 'off', with a big question mark within the battery -- and it would not boot!
I could get into recovery, but once i unplugged it from the power cable it went off shorty after and i did not have the battery fix on the SD card. For some reason i was only able to enter recovery when the usb was only charging, once it was a 'data' connection it would not turn on or turn off quickly. If i turned off my laptop and used the offline charge feature it would power on, however i could not copy over any files I had no microSD -> SD adapter to use my SD card reader.
Finally, having it on power only, I started into the bootloader (power on + Vol+), which also said low power (more fear of a broken battery). After a minute or so, it terminated itself and began to boot CM9 flawlessly. I was able to copy the battery fix from my webserver onto the sdcard. Flashed it. Battery detected again and charging like it should *phew*
This should be stressed A LOT more in the HOWTOs, i was not able to post to the CM9 dev thread yet (<10 posts). Maybe someone can.
Besides all that, it runs really nice now. Overclocked it to 1.3GHz and lots of things run quite smoothly, can't wait for full HW-Acceleration

It worked!!!
Thanks for your help guys. Flashed it as a Defy+ and all seems fine. Pity my main sd card seems to have crapped out during the mess so hoping I'll be able to get my files off it. But, the phone works again!

Gobsheen said:
It worked!!!
Thanks for your help guys. Flashed it as a Defy+ and all seems fine. Pity my main sd card seems to have crapped out during the mess so hoping I'll be able to get my files off it. But, the phone works again!
Click to expand...
Click to collapse
Congrats!!
You may use any data recovery software to retrieve the files ....

Thanks,
One thing I've noticed is that I've never had a 'H' signal since upgrading. It stays on 3G even in areas where I would have had a solid 'H' before. I double checked my APN & it's fine.
Any ideas?