Related
Hey peeps, hope somebody out there can help. I have quite a strange problem and have tried everything I know to sort it with no luck.
Ok before I start I just want to say I'm not playing the blame game, it was probably an unhappy coincidence it happened at the time it did.
I was on kingk's 2.0 hero rom, but decided i'd try maxisma's, so I wiped, formatted ext, flashed maxisma 2.0, then 2.0.1 which had just been released as a fix. Rebooted the phone. Everything was going smooth, I got a little flash of the notification bar same as what happens with every hero rom I've tried, then I got FC on messaging, then the phone froze. Thinking nothing of it, reboot, reflash after a wipe, but I repaired ext after wiping it. Flashed 2 and 2.0.1, then rebooted. Phone got to htc logo, then froze for a few seconds before going back to the animated android. Ok, this rom needs more time in the oven I thought.
I then wiped, formatted and repaired and flashed kingk's rom back to my phone, boot loop
I tried mlign, boot loop
I tried xrom, boot loop
I flashed htc image and then cyanogen's rom, finally got booted.
I've spoken with MikeTaylor (he has the patience of a saint, buy him a beer, I did) and he suggested clearing the dev folder, I tried and was prompted with "device or service in use" so that didn't work. I even thought going back to stock would help, but it didn't. I then thought it had something to do with the SPL, cyanogen's being the only rom not needing haykuros, so I flashed "the official donut" which also gave me a boot loop.
So here I am, asking for any suggestions, and I'm willing to try anything.
Many thanks in advance for any help, and I hope when I get fixed, this thread isn't used anymore, we don't want more people with my problem
The only suggestion I can make is recreating the partitions on your card using parted or something like that. I had the same problem as you going from Cyan to xROM, recreated the partitions and it was fine
well, not near computer to back things up, but i'l give it a go, it's either that or fastboot erase me thinks
if it works, thanks in advance, if it doesn't then thanks for trying
senaia said:
well, not near computer to back things up, but i'l give it a go, it's either that or fastboot erase me thinks
if it works, thanks in advance, if it doesn't then thanks for trying
Click to expand...
Click to collapse
Oh, I assumed that card wouldn't mount so it wouldn't matter if you couldn't back up
So what does fastboot erase do? Wipe out /system?
i was hoping somebody here could tell me that, i've never used fastboot other than changing the splash screen and that was done using a tool, so i didn't actualy use it lol. card mounts, the flash goes through ok, but it just never boots, unless it's cyanogen mod, which i've not used for about 2 months, xrom awesomeness got to me, but i decided to try out a few hero / sense roms while JAC was out of the office, and now i can't go back to it lol
Sorted, being lazy doesn't work. I used amonra recovery to make the partitions initially which worked, then had this problem. Tried using it again and it said it worked but I still couldn't flash. When I checked manually using parted, it showed 3 partitions. Fat32, blank, and swap. Recreated the partitions and I'm now back to full flashing fun. Unfortunate coincidence it happened right after flashing maxisma's 2.0.1
Hi guys,
Tried to upgrade from Darchdroid 2.6.5 to 2.7 today and am now stuck with an unusable phone.
I get a boot loop OR I get stuck on the HTC boot screen for 20+ min. I'm not sure why I get stuck on either one.
This advice was given to me today in the 2.7 thread:
hold down menu+back+power and do a hard reset.
then wipe everything. [EVERYTHING ext4, ect.]
then flash DD2.7
then flash GoogleBits.
good luck.
edit: this has the newest kernel.
__________________
Click to expand...
Click to collapse
The problem is, in order to complete a hard reset, you have to reboot the phone!(right?) But when I reboot, I just get stuck on the HTC boot screen. Is there wiping instructions (i.e. do I need to do certain things from adb instead of the phone?) that I'm missing out on?
Thanks so much. Really loved 2.6.5. Don't know why I keep getting suckered into updating
A hard reset is the same thing as doing a factory reset. So, go into recovery, go tinto the wipe list, and wipe everything on that list. Then, flash it and reboot.
HeroMeng said:
A hard reset is the same thing as doing a factory reset. So, go into recovery, go tinto the wipe list, and wipe everything on that list. Then, flash it and reboot.
Click to expand...
Click to collapse
Thx, Heromeng. Did exactly what you said - wiped everything possible in AmonRa 1.7 and now I'm back to a boot loop.
Some further info: When I was upgrading from 2.6.4 to 2.6.5, Darch said I should push the boot.img from 2.6.4 to make things work. That did the trick for the last update (although I don't know why!).
Is pushing the boot.img from 2.6.4 the way to get 2.7 to work on my phone?
Alright, I went ahead and pushed the boot.img from 2.6.4 and now it's working. I guess it's just like 2.6.5.
My question:
What am I sacrificing by using this boot.img instead of the one from 2.7? I'm not clear what the trade-off is.
Thanks again.
Back up your sd card, then repartition it.
Sometimes ramswapz corrupts the sd card, so you have to format it and repartition before being able to flash a new ROM.
---------------------------------------
There isn't enough of a difference between the kernel where your phone shouldn't boot.
Decad3nce said:
Back up your sd card, then repartition it.
Sometimes ramswapz corrupts the sd card, so you have to format it and repartition before being able to flash a new ROM.
---------------------------------------
There isn't enough of a difference between the kernel where your phone shouldn't boot.
Click to expand...
Click to collapse
Decad3nce: I've re-partitioned it 3 separate times and every time it's a boot loop! Would you tell me if I'm doing this all in the correct order?
-Wipe everything.
-Re-partition sd card
-Enable USB toggle
-Move 2.7 and Googleshits from computer to Phone
-Flash ROM
-Flash googleshits.
-Reboot.
note: I was able to boot into 2.7 with the (pushed) 2.6.4 boot.img but I wasn't able to start wi-fi. So I'm assuming the 2.6.4 boot.img had something to do with that and that's why I'm trying a "virgin" 2.7 flash again.
All I can say is I'm in the same boat. It seemed to me, in my earlier tinkerings, that my phone needed a boot.img that was slightly less overclocked. The few DarchDroid successes I've had were from lower-clocked boot.img's. Without it, I just look at the HTC logo forever.
bohiti said:
All I can say is I'm in the same boat. It seemed to me, in my earlier tinkerings, that my phone needed a boot.img that was slightly less overclocked. The few DarchDroid successes I've had were from lower-clocked boot.img's. Without it, I just look at the HTC logo forever.
Click to expand...
Click to collapse
That's really helpful info, Bohiti. I thought I was alone here!
I am in 2.7 now with the 2.6.4 boot.img but I'm unable to start wi-fi.
This is a dealbreaker for me.
Why would the boot.img affect wi-fi??
Well sorry, kind of. While what I said was true, I just now tried the hard reset suggested to you. (Menu+Back+Power). And then I wiped everything and flashed 2.7 and GoogleShits. And it booted fine, quickly. Only on HTC screen for 10 seconds maybe.
So I'm not in the same boat, though in the past I've had the same symptom with my phone. I haven't rebooted again, maybe I just got lucky.
Darch made changes to his kernel(so it boots at a higher frequency); your phone probably can't handle it then.
Bug him, jus10o, or me(tomorrow) about making a 710mhz bootable.
Decad3nce said:
Darch made changes to his kernel(so it boots at a higher frequency); your phone probably can't handle it then.
Bug him, jus10o, or me(tomorrow) about making a 710mhz bootable.
Click to expand...
Click to collapse
Thanks decad3nce. I will do just that! And thanks for the info, bohiti.
Finally some positive news!
sariamanascar said:
Thanks decad3nce. I will do just that! And thanks for the info, bohiti.
Finally some positive news!
Click to expand...
Click to collapse
I lied. it defaults at 710 on boot. But, try booting 2.6.7 with no sd card in your phone. (do a full wipe, I mean everything)
Decad3nce said:
I lied. it defaults at 710 on boot. But, try booting 2.6.7 with no sd card in your phone. (do a full wipe, I mean everything)
Click to expand...
Click to collapse
OK, just tried this two different times.
No boot loop(!) but now it just hangs on the HTC logo.
Any other ideas?
Bout to go ask Darch and jus10o for ideas....Btw, should I PM them or create a thread?
Thanks again for your help.
sariamanascar said:
OK, just tried this two different times.
No boot loop(!) but now it just hangs on the HTC logo.
Any other ideas?
Bout to go ask Darch and jus10o for ideas....Btw, should I PM them or create a thread?
Thanks again for your help.
Click to expand...
Click to collapse
already told jus10o, but feel free to pm him or Darcj anyways. one of us just needs to compile a kernel that defaults and limits itself under 710.
Decad3nce said:
already told jus10o, but feel free to pm him or Darcj anyways. one of us just needs to compile a kernel that defaults and limits itself under 710.
Click to expand...
Click to collapse
Just PM'd them myself. Thanks for the help, Dec.
Has this issue been addressed? I am having the exact same issue. I have flashed just about every rom on XDA and never had any issues, but I am having the same problem with 2.7 and Buffed2.0...both overclocked kernels. On 2.7 if I do a few battery pulls the phone somehow gets past the HTC logo but everytime I reboot i get the boot loop again.
I have never had any issues like this so I have never had to pull a log. If this would be helpful i would be glad to do it but would need directions on how to.
For all future visitors: Dec was kind enough to modify a kernel that got GPS and Wifi working for me - so thanks Dec. Problem was, GPS eventually started crapping out and I had a whole bunch of force closes over the past week. Including my phone app even crashing on me.
Today, I finally gave up on 2.7 and am on to PureHero which is largely AOSP and (for the non-OC'd version) a lot more stable. While I don't like the look as much, for those of us on weak phones, I think it's the best option.
I had the same issue, but flashed the uv kernel and it booted fine ever since. Couldn't run 2.7 till then.
stand corrected
I recently flashed the UV kernel and I have to say, everything works great. I stand corrected - no one told me the uv kernel was the same thing as "under clocking" a a kernel but I guess that's what it does. Thx.
Worked for me too
Hi just wanted to add that the UV kernel also solved my bootloop problems with DD 2.7.
A few times before the UV I was lucky, and after the 2nd or 3rd iteration of the bootloop it would get past the htc screen and boot. Happened enough times to get hooked on 2.7 haha But the last time I rebooted the phone it was very stubborn and stayed stuck no matter what I tried. That sent me searching back here. Glad I found your post, I assumed the UV kernel was only for those having battery issues, based on the main 2.7 thread.
Hi guys,
I think I finally managed to brick my phone. Everything was working perfectly fine, until today when decided to try GB's Steam kernel.
So a little background first, to make things quicker:
- I was able to open download and recovery mode before, even after doing a odin3 one click restore twice.
- I've tried a Cognition and moved to DarkyYtt3r. Went from 7.0.1 to 7.5 to 7.8 to 8.0.1, no issues.
- Changed the kernel and modem several times. The last one I tried was glitterball's uc/ov stable (no charging death).
- Current set up before this mess:
-- ROM: DarkyYtter v8.0.1 > http://forum.xda-developers.com/showthread.php?t=890429
-- Kernel: gb-reorient-fixed-ocuv-f-cwm.zip > http://forum.xda-developers.com/showthread.php?t=887315
-- Modem: TLJL3 I think.
Everything working beautifully.
Today I saw this thread: http://forum.xda-developers.com/showthread.php?t=903238 ... gb's steam kernel. since no one was having major issues, I made a backup of my current rom using CWNand decided to install the kernel using SGS Kernel flasher, according to instructions.
Cool. I've flashed kernels before a few times. No big deal. And I figured, I'm able to get into Recovery or worst case scenario into download mode. I flashed the kernel, reboot, got into Steam's recovery. Looked around. Activated a couple of tweaks although I don't remember which ones.
Rebooted and this is where the issues began. I got the "intro" window you get with i9000 roms (keyboard intro, syncing, etc). A lot of apps were force closing, including facebook, twitter, rom manager, ADW Launcher, etc.
Ok, so I rebooted to Steam recovery and deleted the cache. Went back and the same problem. At least I was able to boot the system.
I said, oh well, let's go back to our backup. Booted Steam's recovery, and tried to recover from the last backup.
It worked for one boot. Not sure what I did, I don't remember, but after trying to boot again, the phone displays the AT&T screen, the GT-I900 screen and then the Galaxy S screen. I then feel the force close vibration, and the screen goes black. I can touch the softkeys and they blink, but I feel the FC vibration every 10 or 15 seconds.
Somewhere along the line something bad happened.... but here is what's bothering me. I cannot get back into download or recovery mode anymore. Been there all day trying to make it work with no luck at all.
So, more importantly, somewhere along the line, between rom flashes, or something, I lost the ability to get into recovery or download mode. I've heard that I900 roms have different button combos, but nothing works
I'll buy a few resistor packs tomorrow, and some cables just in case. I'm afraid that I won't be able to boot into download mode this way either.
also, adb is not detecting the phone. tried both windows and linux. if I could only get it even for one second so I can send a adb reboot download... but no
Do you guys have any ideas?
Thanks!
cumanzor said:
Hi guys,
I think I finally managed to brick my phone. Everything was working perfectly fine, until today when decided to try GB's Steam kernel.
So a little background first, to make things quicker:
- I was able to open download and recovery mode before, even after doing a odin3 one click restore twice.
- I've tried a Cognition and moved to DarkyYtt3r. Went from 7.0.1 to 7.5 to 7.8 to 8.0.1, no issues.
- Changed the kernel and modem several times. The last one I tried was glitterball's uc/ov stable (no charging death).
- Current set up before this mess:
-- ROM: DarkyYtter v8.0.1 > http://forum.xda-developers.com/showthread.php?t=890429
-- Kernel: gb-reorient-fixed-ocuv-f-cwm.zip > http://forum.xda-developers.com/showthread.php?t=887315
-- Modem: TLJL3 I think.
Everything working beautifully.
Today I saw this thread: http://forum.xda-developers.com/showthread.php?t=903238 ... gb's steam kernel. since no one was having major issues, I made a backup of my current rom using CWNand decided to install the kernel using SGS Kernel flasher, according to instructions.
Cool. I've flashed kernels before a few times. No big deal. And I figured, I'm able to get into Recovery or worst case scenario into download mode. I flashed the kernel, reboot, got into Steam's recovery. Looked around. Activated a couple of tweaks although I don't remember which ones.
Rebooted and this is where the issues began. I got the "intro" window you get with i9000 roms (keyboard intro, syncing, etc). A lot of apps were force closing, including facebook, twitter, rom manager, ADW Launcher, etc.
Ok, so I rebooted to Steam recovery and deleted the cache. Went back and the same problem. At least I was able to boot the system.
I said, oh well, let's go back to our backup. Booted Steam's recovery, and tried to recover from the last backup.
It worked for one boot. Not sure what I did, I don't remember, but after trying to boot again, the phone displays the AT&T screen, the GT-I900 screen and then the Galaxy S screen. I then feel the force close vibration, and the screen goes black. I can touch the softkeys and they blink, but I feel the FC vibration every 10 or 15 seconds.
Somewhere along the line something bad happened.... but here is what's bothering me. I cannot get back into download or recovery mode anymore. Been there all day trying to make it work with no luck at all.
So, more importantly, somewhere along the line, between rom flashes, or something, I lost the ability to get into recovery or download mode. I've heard that I900 roms have different button combos, but nothing works
I'll buy a few resistor packs tomorrow, and some cables just in case. I'm afraid that I won't be able to boot into download mode this way either.
also, adb is not detecting the phone. tried both windows and linux. if I could only get it even for one second so I can send a adb reboot download... but no
Do you guys have any ideas?
Thanks!
Click to expand...
Click to collapse
Did you ever get this problem fixed? The reason I ask is because I'm in this same situation.
We seem to be having the same problem also... Nothing has worked for me so far
http://forum.xda-developers.com/showthread.php?t=960419
Pull your battery, pull your sd card, hold the volume button and plug in the usb cord, this will get you into download
Sent from my GT-I9000 using XDA App
Keep hope alive glaze!
Sent using XDA App
Im going to get a jig hopefully all goes well.
I've tried repeatedly to install CM7.2 and keep getting stuck on a blank screen. I'll see a "CyanogenMod" then "loading..." right below that. Then it goes blank and nothing ever happens after that.
Some background info. I've had CM7 installed on this in the past without problems. Months ago I went back to a rooted stock. Then yesterday I decided to try CM9 alpha. That installed perfectly. But it was too slow, so I decided to try CM7.2.
I used the same CWM 1GB boot SD, copied "encore_CM72-MiRaGe-02012012.zip" along with the Gingerbread Gapps and CWM. Installed in the same order and wipe data/factory reset.
So I got stuck on that blank screen after the CyanogenMod loading... message. I then decided restore to stock. Installed the 1.01 stock image. It also wouldn't boot up, but I powered it on and off 8 times and it did a factory reinstall and then it booted up normally.
Once back at a factory fresh system. I powered it off and tried installing CM7.2 again. Unfortunately I'm having the same problem again. Ugh, why won't it load now.
Hang on... I might be in the process of making a newb mistake. MD5 didn't match on my SD card, probably the ROM.ZIP is corrupted. Trying again with a good copy.
That was it. It's working now. Please disregard my idiot on the Internet moment. Thank you.
You always figure it out five minutes after you finally give up and post for help/venting.
Been there.
I tried to flash the boot image for my first custom rom using easy kernel flasher, and my Vivid is now stuck at the white HTC screen. I then realized that I had used rom manager to flash CWM, even though I had already flashed the custom CWM from the superguide. Is this what caused my phone to hang at the HTC screen?
Is it safe to pull my battery? What is the next step, repeat step 2 from the superguide and then reflash the new kernel and rom?
I apologize if this has already been answered, I just haven't seen this exact question elsewhere and I don't want to pull my battery without being sure that I won't brick my phone or make my problem worse.
Rom manager does not work for our phones. That is why your phone is stuck. I remember another post like this. The guy pulled the battery and flashed the new cwm image without rom manager and it worked. I believe you would start at step two to correct your issue. Let us know how it goes for you.
Ok I pulled the battery and put it back in and now it won't boot at all. The power light flashes orange and then nothing happens. I'm getting a bit more worried about this now.
androuglas said:
Ok I pulled the battery and put it back in and now it won't boot at all. The power light flashes orange and then nothing happens. I'm getting a bit more worried about this now.
Click to expand...
Click to collapse
Alright, so I just did the same exact thing you did... updated CWM from ROM manager and tried to backup the ROM, hung at HTC screen. I haven't gone through the steps to reverting my CWM yet but I did get it to boot. Pull the battery, put it back, boot into HBOOT and let it do its thing, go to fastboot and then reboot. Give it a minute. Mine came back, set for a while at the boot image but it came back.
I just did the whole thing again but with out the HBOOT process and it worked too. Didn't take nearly as long as before at the boot image. Try both or see if you can't get to recovery from HBOOT. I'm pretty new to the Vivid since this is my wifes phone and its a lot different from my Inspire, the process of everything that is
Now reading your 1st post again, I didn't do the exact thing you did but close...
I tried again and it went in to h-boot, and i was able to reinstall the custom vivid CWM. But now I'm not sure if the kernel flash which started all this worked. Is there a way to find out while in recovery?
Should I reboot the phone now, or just flash the rom I was planning on flashing originally? Or should i try to return everything to stock and start all over?
cbronson41 said:
Alright, so I just did the same exact thing you did... updated CWM from ROM manager and tried to backup the ROM, hung at HTC screen. I haven't gone through the steps to reverting my CWM yet but I did get it to boot. Pull the battery, put it back, boot into HBOOT and let it do its thing, go to fastboot and then reboot. Give it a minute. Mine came back, set for a while at the boot image but it came back.
I just did the whole thing again but with out the HBOOT process and it worked too. Didn't take nearly as long as before at the boot image. Try both or see if you can't get to recovery from HBOOT. I'm pretty new to the Vivid since this is my wifes phone and its a lot different from my Inspire, the process of everything that is
Now reading your 1st post again, I didn't do the exact thing you did but close...
Click to expand...
Click to collapse
Thanks man. I got into recovery and fixed the CWM problem, but now I'm not sure what kernel I have running so I don't know if its safe to reboot.
Though I know how to use CWM I couldn't tell you how to check your kernel and whatnot from there. Best thing I can think of, or what I'd do, would be to wipe everything out and restore a nandroid, granted if you have one I've never really messed with kernels untill now so I don't even know if that would work
I realized I could just reflash the kernel while I was in recovery. It hung at the htc screen on the reboot like before, but i just pulled the battery, went back into recovery, flashed the rom, and now everything is working perfectly with the new rom. What a relief.
I think the original kernel flash may have actually worked, and I just freaked out when it hung at the htc screen and assumed it was because of the rom manager/cwm thing. It may have been fine all along.
Here is something that will help with flashing kernels.
http://forum.xda-developers.com/showthread.php?t=1423151
Flash Image GUI
ok i did the same thing awhile ago, i flashed new CWM then insatlled rom ...the Kernal did load thats the reason you got the white screen ..so just go ahead and load your rom you should be fine