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.
Related
Not sure how to start this...
first off, i'm pretty sure my phone now has a fried eMMC chip, but in reality, i don't really know...
the reason i say i think it's fried is because no matter what method i try to flash anything to my phone with...it simply won't do it...most fastboot commands will not work anymore, my computer won't load the devise anymore so no adb commands, bootloader fails everything when trying to flash a stock rom and gets hung up updating the radio_v2....i've tried running official RUU's but it keeps telling me my phone has less then 30% battery life, wich is simply false. and i can't get into my recovery without it crashing the phone and not letting me turn it back on (till battery pull).
i went onto the #g2root and #xda-devs channels on the freenode server in mIRC, and had talked to a couple people there who also think i probably fried the eMMC chip (making it impossible to write or read anything from the phone), but again...i'm really going on word of mouth rather then first hand knowledge here.
but again today, i ran into yet another possible solution and i just want to know if i should bother trying or if i have a chance.
http://forum.xda-developers.com/showthread.php?t=1314629 is the thread, but i think this is for a desire s, so i suppose my question would be...would this method still work if i just used the right files or, again, am i screwed?
i have an HTC Desire Z that i got from Bell in Canada. it has gotten an OTA firmware update, and does not have root or s-off
if i remember right, everything is still stock, completely. minus the now possibly fried eMMC chip lol
thank you in advance and i will try to edit this post as neccessary so as to update any needed info.
please ask me questions as to what i have done and i will try my best to let you know. i know i had followed probably too many guides for rooting with too many methods lol next time, xda-dev's wiki guide, and that's it!
[edit:] i just found this too...lemme know if this helps..... http://forum.xda-developers.com/showthread.php?t=1284196
[edit:] i do know that when i go into my recovery, it does say those things (e: can't mount cache, blah blah) but it crash's out and doesn't actually get me into the recovery console. if so i would be able to envoke some adb commands and just finish this, but that's adding to the issue really...not being able to get into my recovery.
i feel with you.
it happend for me just today morning.
got my desire z on thursday, installed usual apps.
it started to freeze in random app installations. the last softreset threw it into a boot loop with the same problems you stated above.
you can get pre formated desire z emmc's for around 30 - 40 euro i think. but soldering them on your own requires some skill and tools since their contacs are below and not on the side.
this accident threw me back to my old htc touch diamond (with windows mobile 6.1 D: )
After flashing the latest CM9 nightly, I turned on my phone and found that it is running incredibly slow. Like, it takes over 15 seconds to launch any app. I have reflashed different nightlys and HO!NO!'s rom but the problem persists. I have also checked to make sure that I don't have any CPU settings that are keeping the processor slow. I even restored a nandroid backup, it didn't help.
I have now done the following:
-Wiped Data/factory reset
-Wiped Cache
-Wiped Dalvik Cache
-Install from zip
It is still slow.
Is there something I am overlooking? Any idea what is going on?
EDIT:
This is a logcat(whittled down to ~400 lines) of the issue happening in kernalpanics rom. I had the dialer open, put phone to sleep, woke up phone, and immediately started dialing a number. The phone hangs for about 5-15 seconds, and "catches up" later. The log starts right after I woke the phone, so it should pop up at the beginning.
http://dl.dropbox.com/u/16882142/logcat-copy.txt
Here are two videos of the problem(sorry for the wmv):
CM9
GB Rom
Recap:
-I have formatted SD card and tried without SD
-I have tried with and without the SIM card
-I have flashed many different nandroid backups
-I have formatted everything and installed new Roms (I couldn't get HO!NO!s Rom working though)
-I am trying to follow the "unbrick methods" to flash stock firmware. I cannot get the flash to start though(Post)
-I am running out of ideas!
Sounds to me like you got a lemon. Look into this http://forum.xda-developers.com/showpost.php?p=24179363&postcount=4
Out of curiosity is it a phone from bell?
No, its from AT&T. It is actually a refurbished replacement to a new phone I got in December. I want to return it to factory settings but ADB will not recognize the LGP930. This is incredibly frustrating, when I try to install the drivers through LG software I manually put in my IMEI and it says "File not found"
Thank you for the reply, I really need to try to restore this thing.
EDIT: To reiterate, something is seriously messed up with this phone. It takes ~30 second to launch any app. IT will say the program is not responsding and I have to "wait" instead of close to get it to load.
Try formatting system partition then install CM9 again.
Thank you for taking the time Drumist. I have actually already reformatted /system then reinstalled a nightly. I just did it again and still, it is messed up. My main issue right now is that I can't even connect this damn phone to ADB, I can't try to replace this with CM9, rooted, and CWM.
Can anyone help with the driver issue. HO!NO! won't even install anymore, it just sticks on the LG logo. So I am stuck with CM9, but the drivers don't work. Everytime I hook it up to either of my computers, it will detect it as LGP930 for a split second, then try to find drivers, then it recognizes the device as 4 different devices! LGE Modem, LG USB Composite device, LG GPS, and unidentified device. Please, does anyone know how to get into ADB, I am desperate here.
I essentially have an unusable phone. Just to make a call I have to click on phone, then it hangs for about 30 seconds until it says the app is not responding and asks if I want to force close it. I have to select wait, then eventually the app will load. All list-views work fine so I can scroll the contact list. But when i select a contact I have to wait another 30 seconds.
I have searched and read this forum for hours on what to do about the drivers, but no luck.
Is it possible that this is the fesult of a corrupted file system?
My very limited troubleshooting skills with Android says you've either got a/some app(s) running that's soaking up all the CPU/System resources, or there's some major I/O issues going on with your phone (whether because of messing with the ROM or with Hardware is unknown).
Unfortunately you've also stated that you can't get ADB to work, which throws a big wrench in the works to get some debug logs.
If you haven't already tried, there's a very helpful thread on getting ADB working on the Nitro (via stock Google USB driver, not LG). I highly recommend doing those steps and get ADB working for further troubleshooting: http://forum.xda-developers.com/showthread.php?t=1601159
Another thing to try, for giggles, pull the SDCard out and see if there's any performance gain...Maybe you've got a hosed SDCard, or bent/bad pins in the SDCard slot (worth a shot anyway).
Good luck!
Namuna! Thanks for your reply.
I figured out it is somehow related to the SD card, THANK YOU! I actually tried removing the SD card yesterday when the problem first started, but the trick is I have to boot my phone up with no card in it. Once I put a card in, even if I take it out, the problem starts up again.
Since my phone ran out of battery hours ago, I am at work, and I left my cable at home; I cannot try the google drivers. I won't be geting home until late so I'm going to have to do some more experimenting tomorrow.
You don't need the Google drivers now. LG drivers are working again.
I remember that that is the case Malnilion, but I need to try something.
Bad news, apparently I jumped the gun because my phone is super slow again, with or without an SD card.
I just really need ADB access, a log would be a godsend.
I have found I can get to ADB when in CWM, but I can't get the drivers to work when in CM9 so I can't get a logcat.
Try to adb in recovery. Did you format that SD card?
Sent from my LG-P930 using XDA
I now have a version of kernalpan1cs rom running on my nitro. Almost everything runs fine, but the slowness happens when I try to make any phone call and with other random apps.
I have ADB now, and I am going to post a logcat of what happens when I try to dial a number using the phone app, then when I try to make a phone call.
I just need some help, I can look at the logcat when I do ADB logcat, but I have a hard time keeping track of when the problems happen. There are so many things that happen immediately after it that I cannot keep track of where the previous information was in the console window.
BTW, I notice that when the slowness happens when I dial a number in the phone app that the log reports a bunch of stuff about going into wakelocks and coming out of wakelocks. I thought this was kind of weird.
2 things.
1. I salute you for sticking with this phone through all the issues you've had (and still continue to have). I would've got the thing back as close to stock as possible and then exchanged it for another Nitro a long time ago. You've already done it once, it seems the refurb you got is also suffering some hardware issues...Might be time to do it again!
2. If you are dead set on chasing this rabbit down its' rabbit hole though, then I suggest getting acquainted with another debug tool called ddms (http://developer.android.com/guide/developing/debugging/ddms.html). It's a GUI based debugger that utilizes logcat, but is much more robust with tools for filtering and viewing associated processes.
Good luck!
Have you tried replacing the sim? Sounds like a shot sim to me.
beaups said:
Have you tried replacing the sim? Sounds like a shot sim to me.
Click to expand...
Click to collapse
This is a good point, especially if it's the same SIM that you used on your previous Nitro...Thereby bringing the issues with it!
Thanks guys! First off, I have exams going on so this has definitely taken the backburner, otherwise I would be on top of this.
@beaups: I'm pretty sure it isn't the SIM, when the SIM is out the slowness continues in either ROM.
@Namuna: I think I will give ddms a try once I have some time(hopefully this weekend). Thanks for the tip, I usually like getting my hands dirty
This is a logcat(whittled down to ~400 lines) of the issue happening in kernalpanics rom. I had the dialer open, put phone to sleep, woke up phone, and immediately started dialing a number. The phone hangs for about 5-15 seconds, and "catches up" later. The log starts right after I woke the phone, so it should pop up at the beginning.
http://dl.dropbox.com/u/16882142/logcat-copy.txt
Lastly, if I try to exchange this phone for another, what should I do in order to make it more factory-like? Install a stock ROM? Uninstall CWM?
EDIT:
Here are two videos of the problem(sorry for the wmv):
CM9
GB Rom
I also got the same thing here after updating the cm9 followed by a wipe data.. Tried all the things listed.. format system, gb roms.. Have you had any luck with the unbricking method?
I have same situation about the super slow after cm9. However, i fixed the problem after using the unbricking method. everything back to normal now. You can take a try. It seems like cm9 mess up some I/O address, cause it only slow down whenever you need to input or output from system.(Example: phone call, music ..etc)
did it
had the same problem, [Guide] Unbricking Solution for LG Nitro HD (P930) did it for me, back to usual speed
Yes, the unbricking solution worked for me, I just had to use the method in the original post once I worked out some driver issues.
I still am wondering what caused this though.
A while back I had a random lockup, did a battery pull as this usually fixes it, but this time it just stopped at the HTC loading screen and stayed, 4+ hours, after that is when the problem started. I've exhausted my knowledge and am in dire need of more seasoned users (long time lurker first time poster.)
My phone is Dev-Unlocked, not S-off (I was young and reckless, and apparently an unknowing glutton for punishment)
Here is the problem I am having. I'm unable to flash new ROMs or recoveries. Flashing a ROM from the recovery (always remembering to flash the Boot.img after [Thanks Dev-Lock]), it says it can't mount System, Data, etc. and then says Faild. Flashing using the PG32IMG.zip method, it take about 2 minutes for the progress bar to fill up and it says it's done, but nothing happens, I restart and it's exactly where I was before. Flashing ROMs and recoveries through fastboot is similar, but it says it transferred, though is always locks up at the end -waited hours just in case- ADB doesn't recognize my phone, it used to, but it no longer does and I don't know when it stopped.
I can still get into the bootloader, Fastboot still works, Recovery still works (though extremely slowly.) So there is hope!
I've scoured the help pages, and this is what I've tried in no particular order:
SD Card 2Gb Sandisk & 16Gb Sandisk.
Scanned for viruses
Scanned for errors
Defragmented -why not?
Reformatted (through recovery and computer)
Blessed with burning sage -You think I'm joking?
ROMs flashed from recovery and fastboot.
SkyRaider Zeus 1300
tsm Gingerbang 5.0.1 (what I was running)
Liquid Smooth v3
Cyanogen Mod 7.1.0.1
Cyanogen Mod 7.2.0
6.01.605.05_VZW_OTA-full-odex
Andy Bones stock (forget which version)
Using the PG32IMG method
6.01.605.05_VZW_OTA-full-odex
RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487 (I forget which one this is)
Andybones Stock
Another simple called "Dinc2Stock" (I forget which it is)
Recoveries
Clockwork 5.0.2.0
Clockwork 6.0.1.1 Touch
Clockwork 6.0.2.7 Touch
Team Win Recovery Project 2.5.0.0 (What I was using, and currently what is stuck on there)
"Recovery" (I think it's either 4ext or a Clockwork variant, I forget)
Chilly Bean's anti venom -Awesome little program
Used before flashes
After
In between
Not at all
Phone
Factory reset
Chilled -last Inc2 had an odd overheating issue
Changed cables (3)
Blessed with burning sage -I'm a day or two shy of ritualistic sacrifices
Slept with it under my pillow -Why not?
Tried other batteries (2)
Tried some of the above processes in a RF shielded box -not kidding
Operating systems used
Windows XP
Windows Vista
Windows 7
Linux (not successfully, were odd issues)
Other little tidbits:
A friend has the same model as I, but unrooted, so I've been able to test a few things out, mostly just reaffirming what I already knew. A friend works for Verizon in customer support (he's been telling be rooting is a bad idea, I think he's just scared to Really own his phone) but his best advice was claim it got stolen or dropped and get a new one (I'm not there yet, I'm still mostly honest.) He did get me in touch with a co-worker who is a technician who's response to what I had had already done was along the lines of "Damn... you have tried it all" Inspiring to try and do more, but albeit not helpful.
So, great XDA Devs, what do you recommend?
-Edit- Information I thought might be helpful
Hboot-0 98.000
Radio-1 09.01.0312
The short version: I need to know how to do a carrier wipe on my Evo running CM 7.2, because ##72786# doesn't work.
The longer version: I've been trying to get my Evo activated on Ting since last Friday. It's been sitting around for about 2 years, and it was on an older version of CyanogenMod. Ting said I was all set, and to dial ##72786#, and then enter my MSL. When I do that, I get a message saying that my account could not be validated.
Over the weekend, I kept trying, but eventually decided to switch to a different ROM. That's been very frustrating, because I can't find working download links for the versions I want, and of the several others that I have tried, I can't get the phone to boot, after, at least not beyond the white screen. So, I put my PC36IMG on, and even that wouldn't do the trick. I thought maybe I'd bricked it, because it took 2 tries to get CM 7.2 going again, after all of that.
So, does anyone have any idea how to do a carrier wipe on CM7? From what I read, I have to do it differently, but using the stars in that code doesn't change anything. I tried a calculator hack, but that won't work for me, because the calculator it comes with doesn't have scientific mode. (Although I will now go try downloading one, to see if it works).
I'm at my wits end! I never had any problems during the 6 months or so using CM with Sprint, before I moved on to another phone. I've looked at hundreds of pages, mostly forum threads, and it seems so odd to me that I'm the only one with this problem.
One weird thing, on Sunday, Ting shows me as having downloaded a couple MBs of data, but to my knowledge, this has never successfully connected to their network. Perhaps I managed to get data to connect, when I wasn't aware? I never have even tried the steps to get data switched, since I can't get the carrier wipe done.
New number
If it matters, I didn't port my number, I'm getting a new number with this account.
Stars in Code Got Closer
So, I can use the dialer codes with stars in them. Or rather, some of them work. For example, *#*#33284#*#* will get me to a debug menu. When I try *#*#72786#*#* it reacts, but not like it should. The code I've been typing in disappears from the screen, as though it's been recognized as a valid code, but then nothing else happens, I don't get a menu, or anything.
I finally got another ROM flashed, and I was able to boot, but then the screen doesn't respond to my swipes, so I can't even unlock it. I'll be trying yet another ROM, but this is SO frustrating.
You need a sense ROM. Use captain throwbacks rooted stock. A sense ROM is the only tried and true way.
http://forum.xda-developers.com/showthread.php?p=26516892
Thanks for the reply! I believe I've tried that ROM, but I will give it another go.
The few roms I made from ctb base all have no problems using any codes, feel free to try one to program your phone, and if you do let me know if it worked.
I like to keep tabs on my work.
Sent from my PC36100 using Tapatalk 2
That ROM (captain throwback's 5.07.651.6 Stock Rooted - Deodexed) was already on my phone, so it was one I had tried. I went ahead and flashed it again, though. Pretty much anytime I flash a ROM, when my phone reboots, it stays on the white boot screen forever. I once let it go for 24 hours. I know it did it the very first time I rooted this phone, when I flashed the ROM. I eventually pull the battery, and most of the time, when I turn it on again after that, it boots normally. Some of the ROMs I've tried flashing in the last week won't boot at all, and I have to flash something else to get the phone going. I'm not sure now what the result of the first time I flashed this ROM was, but it's been sitting for about 30 minutes, now. I'm not sure how long I should let it go, before it's safe to pull the battery, so I'll probably wait until I run some errands, and come back to it in a few hours.
I'd be interested to know why the phone doesn't boot on the first try, after flashing, though. I wonder if that's why I've had no success with any of the ROMs I've tried, except for CM.
vinman, I will check yours out, if this isn't successful. I'm guessing the links in your signature will lead me to info?
Ok just to be clear, your rooted, s off, have a custom recovery like Amon 2.34 or smelks.
Do a back up of your sd card on your PC.
Now in recovery wipe everything,
Now format the sd card to 1024
Swap size 0
Upgrade Ext 2 to ext 3 or 4 if using a ROM with support for it, which mine has.
Now put your sd backup from your PC back on your phone sdcard
Now while still in recovery flash the ROM.
If your using mine it will reboot 3 times and take about 5 to 10 min to boot up do to the a2sd. Once it boots let it sit for 5 min to settle in.
Set up your google account
Now from dialer enter your codes you want it should work as I have a older version on my build just so you can use the codes.
Hope this works.
Sent from my PC36100 using Tapatalk 2
---------- Post added at 02:33 PM ---------- Previous post was at 02:32 PM ----------
vinman12 said:
Ok just to be clear, your rooted, s off, have a custom recovery like Amon 2.34 or smelks.
Do a back up of your sd card on your PC.
Now in recovery wipe everything,
Now format the sd card to 1024
Swap size 0
Upgrade Ext 2 to ext 3 or 4 if using a ROM with support for it, which mine has.
Now put your sd backup from your PC back on your phone sdcard
Now while still in recovery flash the ROM.
If your using mine it will reboot 3 times and take about 5 to 10 min to boot up do to the a2sd. Once it boots let it sit for 5 min to settle in.
Set up your google account
Now from dialer enter your codes you want it should work as I have a older version on my build just so you can use the codes.
Hope this works.
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
Just make sure you have all your Ting info in case you wipe it all.
Sent from my PC36100 using Tapatalk 2
So, this has been a pain, I'll put some detail here, in case someone else could use the info.
I backed the SD card up (again, again), and then from Recovery, I did a wipe (Wipe ALL userdata/factory reset). Then a Partition, where it asked the swap size first, which I set to 0. Then for Ext2-size, I set to 1024 MB. It then said FAT32-size would be remainder.
Back under partition, I did "SD:ext2 to ext3". There was an option to do "SD:ext3 to ext4", but I didn't do that. (Info on partitioning here, if anyone needs it)
Those took maybe a few minutes each. I then rebooted the phone normally, and turned on USB Storage, and copied just the clockworkmod folder over, so I'd have the the ROMs, that were saved there.
Nothing worked, so I started over. By nothing worked, I couldn't get it to boot to any of the ROMs I had, even the CM7 that had previously been working. It would just site at the white boot screen, and never would get to the CM7 screen, or whatever one was with the ROM I was trying, even when I'd let it sit for hours. Since I first rooted this phone a couple of years ago, it would often not boot after flashing a ROM, and just sit there at the white boot screen, but when the flash was successful, I'd have to pull the battery, and the 2nd time it would boot properly. I might not be cautious enough now, but I tend to not wait more than 30 minutes before pulling the battery. Also, in the past, I've flashed a ROM, and it wouldn't boot, so I'd repeat flashing that same ROM, and it would work the 2nd time. So, this whole thing has required a lot of patience and even more time. I typically walk through flashing a ROM, wait for it to not boot past the boot screen, reboot, and if it doesn't work I still wait a while, then lather, rinse, and repeat. Just trying to get this phone going in the last month, I've probably actively spent a good 15 hours, and that doesn't count when I just walk away and leave it plugged in, hoping time will help.
Anyway, I realized that that I had made a silly mistake, and that hadn't saved the PC36IMG_Supersonic_Radio_2.15.00.01.15.zip file as just PC36IMG.zip. So I did a wipe, and then partition.
When I partitioned the SD card again, I set swap to 0, and 2048 for the Ext 2, and the remainder for FAT32.
I tried pulling the SD card, using a reader, and copying the files over, but something was wrong, and my laptop wouldn't recognize the card. I'm fairly certain that the reader is broken, and doesn't work with micro SDs anymore, so I just put it back in the phone and tried to reboot.
First time booting, it stuck on the white boot screen again, so I gave it 10+ minutes then pulled the battery, and tried booting once more. Still no go, so wiped and tried again. Still no, 2nd reboot, still no. Tried ext 3, no go.
So, I finally got to the store, since I couldn't find my other Micro SD adapter that works, to get another, and put the PC36IMG file on. I booted to recovery, it found the file, installed it, and rebooted. It stuck on the white boot screen, as expected, so I gave it some time, pulled the battery, and rebooted again.
I've been at this for the last week, and although I was able to get the CM7 ROM going a couple of times, I can't get it going now. And the PC36IMG isn't going, after the 2nd reboot. I have hope, but it's waning. I'll be doing some additional research, in between other stuff, this afternoon. But, I thought I'd go ahead and post this, since I've been writing down what I've done as I go this time, just in case someone stumbles along and knows what I'm doing wrong.
So, I followed some of the advice from the Rooting for Dummies guide and I wiped the Dalvik Cache a couple of times, and then decided to go ahead and Wipe All a couple of times. Then I partitioned the SD card (0, 2048), followed by upgrading ext2 to ext3. I copied PC36IMG back over, and tried that again. I then decided to figure out what the ext2 thing was, and found this question about ext2, ext3, and ext4, which says that it doesn't hurt to go to ext4, that the older ROMs will convert it back, if needed. So, I did that.
Of note, when I rebooted, to try for the PC36IMG again, I noticed that it can't find what I think says PC36IMG.diag, although otherwise it always seems successful, other than not booting past the white boot screen.
I'm waiting to see if it gets past the boot screen, now. Assuming this doesn't work, I'll repeat with the ROMs that I have, and hope that will work. Probably won't post again today, unless I get somewhere new.
Wow, I finally got it going! Notes are below for reference. I tried the deoxed ROM mentioned at the end of my notes. (can't paste right on mobile) but only the 3rd try, it worked. The only thing different was that I didn't have it plugged into the wall when I ran through the flash and reboot, this time. Does anyone know if that would make a difference, or if it's coincidence? Anyway, next I'll want to go back to CM7, but I'll wait till tomorrow, after I backup, and have time.
Here are my unedited notes, in case it might help someone else...
Wiped, partitioned, enabled USB-MS, created a "clockworkmod" folder on the empty SD card, then copied the oldest folder I have handy, "2013-07-13-16.11.44" over. Then exited USB, and selected "backup/restore" and then "restore nandroid", intending to select that backup.
Of course, when I tried to mount the USB, my laptop refused to recognize it, so I had to reboot my laptop, before continuing with that step. This is kind of how every step along the way has gone. Rebooting didn't help, and I though tht worked!
at this might be why my laptop stopped seeing the card through the phone before, and I tried upgrading ext3 to ext 4, which I had skipped this time. That didn't work, so I went ahead and powered the phone off, and used the micro SD card reader to transfer those files over.
Of course, restoring the nandroid didn't work. Apparently, even though I put it back in the folder it came from, Nandroid expects it to be in a different folder. So, I created a "nandroid" folder, to put the files in. It needed them in appropriate subdirectories, so that didn't work.
Next, I pulled out my backup drive, and looked for my original Evo backups, from a couple of years ago.*
I found a nandroid folder that had the device name and then a backup folder with the expected type of name. I got that on the card, put it in, did the recovery, and this time, it was recognized, and the restore started. It took I'd say 20 minutes to complete. When I had it reboot, I walked away, and when I came back it had rebooted to recovery, which was unexpected. I had it power off, and then turned it back on. That repeated when I turned it off and on, so I guess that I've finally hit my first boot loop.
I did a wipe, moved PC36IMG to the root, and tried that. Rebooting gave me the white boot screen, then it went dark, rebooted and went to Recovery. I tried rebooting again, same thing. I did a wipe, then rebooted. It did the dark screen, then rebooted to Recovery. I tried again with the*5.07.651.6_stock_rooted_deodexed_CPTB ROM
I'm having the same exact issue.
Hi all,
I'm having the same exact problems described here, and for the same exact reason. I'm switching from Sprint to Ting, though I ported my number, too.
I've spent all afternoon trying to restore stock roms so I can input the ##72584# number or whatever it is and activate my service, but I can't get any roms to work right now. I'm going to try the recommended DEOX version mentioned in this thread now. Just putting in my note so others can see they're not alone.
If I get it working, I'll mention how.
Good luck. I'd be happy to help, however I can.
Given that sometimes I've had to install a ROM twice to get it to take, I'm really wondering if the phone being plugged into power (not even a PC) might have affected something. It would seem like a really weird thing, but that's the only thing that was different the last time I tried to install that ROM, and it was at least the 2nd time in a row, if not the 3rd. So, try multiple times, until you get it going.
Should not be this hard to flash a sense Rom and enter service programing codes. Simple thing is just back up your SD card to pc,
Then partition your SD card ext 2 is fine for stock gb Rom. So after partition put your backed up SD card back on your SD.
Wipe the phone 3 times except for SD. Flash Rom. Should work fine
What I had to do
In brief what worked for me is that I needed to install a stock rom without the custom recovery to allow the ## commands to work from the dial pad. You do not need to go all the way to S-ON.
Step 1 - Upgrade your custom recovery and have an image of your custom recovery for you to re-install. I use Clockwork Mod. You can get it here:
http://forum.xda-developers.com/showthread.php?t=1473525 Save PC36IMG.zip of your custom recovery on your PC for later.
Step 2 - Boot into your custom recovery and make a backup.
Step 3 - Download and save PC36IMG.zip of the STOCK ROM from here: http://forum.xda-developers.com/showthread.php?t=780141 You do not need the S-ON.
Step 4 - Reboot your EVO 4G into HBOOT with power and vol-down and let it install the stock ROM. THIS WILL OVERWRITE YOUR CUSTOM RECOVERY. You have your custom recovery saved from step 1, right?
Step 5 - Reboot and then use the keypad to do your carrier wipe from this page: https://help.ting.com/entries/22935397-Activation-for-your-HTC-Device Let it reboot several times.
Step 6 - Copy the PC36IMG.zip from step 1 onto your SD card.
Step 7 - Reboot using power vol-down into hboot again and let it install your custom recovery.
Step 8 - Reboot into your custom recovery and restore your backup image onto your phone.
Edited to add, I did not have to wipe my SD card, but your mileage may vary.
use sprint base sense Rom
use s sense base sprint Rom.
you can try digitalkarmav9
it worked for me.
best thing about Ting, you don't have to mess with flashing. and they are resonable if you don't use data.also unlike boost or virgin they toss over to verozon when you roam
Hi guys,
I've got a bit of a problem. My phone is stuck in a boot loop, which is a problem I've dealt with before, with help from these threads.
But this time I'm really stuck. I can't access the HBoot screen like I normally can, by holding down the volume up and power off buttons simultaneously.
I am using (racks memory) I think it's the War something mod of Cyanogen 7 I believe. I installed it 5 months ago and it's been working fine. This is not a new or recent install!
The phone does suffer from low memory issues a lot, as do all Wildfire S's. I have managed to get around that previously by moving apps to the SD card or linking to it or making user apps into system apps. I was in the middle of chatting on whatsapp when suddenly the phoned just blipped and died on me.. then it went into the boot loop. It's never happened before and my suspicion is that it ran out of memory or something.
I've tried removing the battery and leaving it out for some time, no luck. I've tried restarting without the SD card and Sim card. No luck. I've tried connecting it to my laptop... no luck. All the usual tricks just aren't working.
I have TiBu installed and my most recent back up was less than 4 weeks ago. I also did a Nandroid system backup a few months ago, so I should be able to restore ok, I just can't access the HBoot screen.
The other weird thing is, when I left the loading screen going round long enough, like in the time it would normally have booted.. suddenly the sound of my new emails popping up plays... and today, even tho it was on the load screen, it made clicking sounds like when I activate apps when my finger touched the screen. It's almost like the phone has started up as normal, but the load screen just won't go away and underneath it all is normal.
I've never had anything quite like this happen before and I've been without my phone for 3 days now, so came here in desperation for some inspiration! hehe.
I am probably going to buy a new HTC phone with a large system memory cos altho I dearly love my Wildfire S, the low memory has caused me nothing but problems since I first bought it, and I have wasted hours and hours on it, trying to get around the problems caused by it. But until then, I need to get my contacts and messages back and continue to use it for now. I would also ideally like to keep it going and give it to my sister perhaps who doesn't have a smart phone. She won't need as many apps as I do, so it would likely suit her, or maybe my Mum.
Any help anyone can give would be massively appreciated. Thanks guys!
Can't access HBoot!
Hey is anyone out there? I know lots of people get stuck in boot loops and there's a million threads of support for that, but this is different. I can't access the recovery system either. I have clockwork mod on it and normally you can get into that fine. Trying to find help on this problem is really tough cos I have to wade through all the noob threads for standard easy fix boot loops. If anyone could help me on this I'd be extremely grateful.
This might be all I can offer but two things come to mind. The first is you said volume up its volume down to get into the bootloader. The other is to search in the wildfire forum regarding whatsapp. Recently I read a post about a guy who's phone crashed from whatsapp. I don't remember how he recovered you have to search on it; unfortunately the second time he couldn't recover.
Good luck
Sent from my HTC_Amaze_4G using xda app-developers app
Thank you!
MiCeltic said:
This might be all I can offer but two things come to mind. The first is you said volume up its volume down to get into the bootloader. The other is to search in the wildfire forum regarding whatsapp. Recently I read a post about a guy who's phone crashed from whatsapp. I don't remember how he recovered you have to search on it; unfortunately the second time he couldn't recover.
Good luck
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Thank you for this... I'm willing to grasp at any thread at the moment. I did try the volume down option too but no dice there... but the whatsapp thread sounds promising, so I'm going to follow that up right now. It's after 4am and I've been sitting here working on this for hours and hours and at my wits end, so thank you! Fingers crossed!
Accessed HBoot!
Update:
Ok, I couldn't find the thread about whatsapp that was referred to above, but I have just tried accessing the recovery menu, using the volume down and power key, after first removing the sim card, but leaving the sd card in place. Suddenly that seemed to work! The menu came up!
I tried accessing it again with the sim card back in, and it refuses to come up again as before. So that at least is one issue resolved.
Now I'm having trouble mounting my SD card, which it says can't be mounted. I know the backups and recovery files are on the the SD card, but it just doesn't seem to see them there.
I wiped the dalvik cache in case that was causing any problems and it doesn't seem to have resolved this current issue so far. I'm going to keep trying other options as see how I get on, but I least wanted to share the solution to one of the problems my thread raised.
Further Update
I couldn't remember the name of my mod in the first post.. it was the WildChild mod.
After getting my phone into HBoot by removing the sim but keeping the SD card in, I found I was unable to mount the SD card. I researched this problem and some suggest the card may be corrupted.
I have checked the card on an external reader plugged into my PC and it read perfectly fine, and I managed to copy every bit of data on it across to the computer with ease. Others however found that after a reformat it eliminated any problems with mounting.. so that is what I am going to do and then try and restore the copy of the data I saved to the PC back onto the SD card.
Attempting now to reboot normally with the sim back in and the SD card removed this time produced a very desirable result. My phone started back up, albeit without the normal operating system. I was able to connect to wi-fi and my network and see a missed call voice mail message symbol. There are however no apps at all as yet and no background screen. I should mention that the phone did ask me to allow SuperUser permissions again.. I should also mention that I foolishly tried to Fix Permissions in CWM which then sat for a long time, eventually I removed the battery cos I thought it wasn't gonna do anything.. this is a big no no I now find out from the threads and I may have buggered it up a bit. I don't know.
My saga continues anyhow, and although I've not had much support on this, it might still be helpful for others to read and follow should whatsapp crashed their phone too and mess with their SD card somehow.
Another Update - Making Progress!
Next update on this...
I removed the SD card and put it in an external reader again on my PC.
Then I installed the free program Mini Tool Partition Wizard Home Edition and selected MiniTool Partion Wizard rather than the Power Data Recovery.
The Wizard allowed me to see the hidden partition on my drive. I understand now why it has always had trouble reading and writing to the SD card in the Ext section that was hidden. This should have been an EXT-2 or EXT-4 format partition I think, and mine is an EXT-3.
Maybe I'm wrong, I don't know much about these things and just learn as I go and by experiementing.
I had hoped to back up the hidden data in the partition but I was unsuccessful. Instead I found the Rebuild MBR (Master Boot Record) option and applied that to the entire SD card.
I then put it back in my phone, again without the Sim, and went into HBoot and recovery. I then went to my advanced back up and restore section and now the SD card is mountable and readable! I didn't have to wipe it or reformat!
I found my most recent up date which was the end of August... I wish I'd done them monthly, but oh well not too bad... and selected it and chose to Restore Boot.
Once it had completed I tried to reboot, but no dice. I put the sim card back in.. still didn't work... BUT I was now able to get into recovery again, this time without removing the Sim!
So inching along slowly here with this but making progress.
Next I plan to restore boot again, this time with the Sim card in.. and try and restart.. if that fails, I will go back into advanced recovery and try to also Restore System, and lastly restore SD-ext and see if each of those options repairs whatever damage that stupid Whatsapp did to my phone! I hope the little solution to various problems I've had are of some use to someone else here. Now wish me luck!
Wow, you were busy last night while most of the western world slept . I'm guessing if I posted at 11:10 PM and you said it was 4:00 AM, that your in the London timeline. I thought a little bit more, later, and I think that person's post I read fixed his phone by eventually getting into recovery and restoring, which as I remember worked that one time, until he reinstalled and used Whatsapp again some time later (it was at the insistence of a girl that used it). Whatsapp has, like 300 million users, but it does seem to give some people serious problems, and that's why I think most people are hesitant to try and help. They don't want to make things worse, since there are those instances of totally bricking a phone...but as long as a person can get into recovery, it's not bricked!
Interesting...I have done the, "fix mbr" in PCs many times, but I think you've taken it to new levels using it in phones! At least I don't remember reading anything much about someone doing it (in phones) before and it's brilliant, IMHO. You really did a great job sharing what you've done and I hope you get it fixed. I clicked a, "Thanks" for a good post follow up.
Insert standard disclaimer here: I'm not telling you to do anything, or what will or won't work, but sooner or later you're gonna have to restore that backup, but it's your choice on what to do; and, it sure seems like you know what you're doing, especially having made a backup to work from. I can appreciate the way you've gone piece by piece in your restore efforts to try and find where the problem occurred. The nice thing about the Wild Child ROM is it all works, and incidentally I think the developer uses ext2 for his extended SD card partition! It sounds like you reformatted to ext2 or ext4 from ext3, so the only thing there now is what came from restoring that backup piece in Clockwork; therefore, there's nothing that would be lost that isn't already; and, you backed up everything else on the SD card. So I don't want you to brick your phone either, but I'm wondering about wiping the cache and then the dalvik-cache, and then restoring your whole Nandroid backup?! I think your Whatsapp contacts are saved and so if the phone boots to a working condition you could just uninstall Whatsapp right away, boot into recovery and wipe cache and dalvik-cache again just to be safe, and then decide what to do about using Whatsapp again. As long as you can get into recovery, ultimately you could wipe, wipe, wipe and reinstall Wild Child to start all over if nothing else works.
On the other hand maybe you've already got this whole mess straightened out, if not, I'll again wish you - Good luck!
Solved!
So I next wiped the cache partition 3 times, as someone on another thread said sometimes it takes more than one go to clear it all properly for some reason.
I also wiped the dalvik cache again a couple more times. Then I went back to my back up and restored system. Then I tried to boot my baby back up.
I was falling asleep at this time but I remember the phone partially recovered. But most of the apps were broken. I had low memory issues too, so I uninstalled a few apps, managed to restore some individual apps or update them, and log in long enough to send messages to contacts with my email so I wouldn't lose them.
Then I fell asleep with the phone in my hand haha.. when I woke up I immediately continued with it and finally worked my way back to whatsapp being the last app I wanted to deal with. I managed to get into it and send some messages.
Then I did a full nandroid restore on everything.
The phone returned to it's state as of 2 months ago when I last did a nandroid back up. But some of my TiBu apps were backed up more recently. So I manually restored those and things were mostly back to how they were before and I am fairly happy with the low loss of data.
Whatsapp was working fine for a while.. but then it started having problems. It first had all my contacts there... then it lost their names but kept their numbers, then it lost all the old messages and right now I'm in the middle of trying to restore everything again and it's stuck on a restoration. I did a full uninstall of the app, restored the back-up, then it tried to update, but it always fails and now it's just hanging. So it definitely appears that whatsapp is one of the major causes of problems on my phone.
It was also one of the largest apps I had on there. Wildchild is an awesome rom, it only lacked video really and I installed a codec and player for that and got it working again, despite the guys on the Wildchild thread saying they didn't think it was possible. Yes I had trouble with it sometimes, but most of my trouble stems back to the low memory issues and the fact I broke all my apps up by spreading parts of them over the SD card, internal storage as user apps and system memory. That's a Wildfire S problem, not the fault of the Rom.
Anyway, I've made note of all the important numbers and will be buying a larger capacity HTC phone this week. Not sure which yet, but possibly a Sensation or Sensation XE, depending on my budget.
Thanks for your support MiCeltic. Yes I'm in London hehe. And I hadn't read anything about using MBR on a phone, but it was the SD card which had the problem and that certainly fixed it without having to wipe all my data.
I think what I have here is multiple layers of problems.. and I'm really pleased that after 3 days effort I managed to get past most of them. Once I get my new phone and transfer the contacts, I will have to think twice about using whatsapp.. it's my favourite app of all tho, so it will be hard to part with. This phone has many bugs.. I will completely erase it and reflash it when I get time and either keep it as a back up and maybe gift it to my sister or mum as I said before.
:good:
Last update
OK this is my past update on this... Whatsapp had one last surprise in store for me.
After it started messing up my phone again. I gave it one last chance. I completely removed it from the phone and installed it as new from the GooglePlay store. Then when I loaded it, it found the backed up Titanium BackUp messages and restored those.. then when I opened the app, it also had restored all my most recent messages, up to the day before it crashed the whole phone. I was amazed. They must have been stored on the server or something.. I think they sit there for 3 weeks. So I'm likely only missing one weeks worth of messages at most, about 4 weeks ago! Ha! Brilliant. I'm not doing a Nandroid backup cos everything is stable again and I hope to have no more troubles until it comes time to transfer all the date to the new handset... that's gonna take a while cos I will have to learn how to gain the boot mod rights all over again and maybe even flash a custom rom as the stock is sure to be loaded with bloatware. Still.. if it has a 1GB internal memory it shouldn't slow the phone down too much.. not compared to the tiny 150MB this little baby has!
If someone wants to close this thread now, feel free.
Cheers. :good:
You inspired me to read a little more last night and I did see where some people found a fix by uninstalling and then installing new (not from backup), then restoring their contacts. Seems like you've proved that point! Interestingly I read that ALL of your contacts are stored on the Whatsapp server, not just your contacts that have Whatsapp (Remember those permissions you accept when you install an app!). As I said, there are 300 million users, obviously not everyone has the problems, so hopefully it will work for you now and on your new phone, which after reading your posts I know you will make a back up of immediately and again after rooting...AND definitely before installing Whatsapp ! ! ! You might even find your next phone easier to root as a lot of them don't need an update of the bootloader on htcdev for the first step when unlocking and/or many can gain Soff!
Glad you got it working and now all's right with the world...well for now