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
Related
I haven't touched my Rogers G1 rom, it is as stock as they come. One day the battery died, so I plugged the phone to charge and also tried to start it up.
My problem started after that.
I will try to restart the phone and it'll get stuck on boot screen - where it says HTC or sometimes even just the Rogers screen.
Only solution is to take battery out, do hard reset.
I've searched the forums but everybody else asks regarding modded roms and not stock.
Any idea how I could resolve this issue without flashing new roms? Or is that my only way out?
Thanks.
Did you apply Rogers mandatory 911 update that was released about a year ago? You can check by booting into fastboot mode (hold the camera button while powering it on). If your radio version is 3.22.26.17 you have the update. Rogers locked down fastboot in this latest update and the only way to root it is through the ROM. If you don't have this update I can walk you though the steps to root your phone though fastboot.
Just checked and it does have the update.
Should I just go ahead and flash new roms?
I keep having the same issue as before.
With the latest update Rogers locked down fastboot so it is useless. So, I don't believe that there is any way to flash a new ROM without first booting into your existing ROM.
Sorry but I'm inexperienced with flashing roms...
If I can't flash by the fastboot method, I can still flash by rooting the phone, correct?
JiggyNS said:
Sorry but I'm inexperienced with flashing roms...
If I can't flash by the fastboot method, I can still flash by rooting the phone, correct?
Click to expand...
Click to collapse
I'm not completely sure, but usually you need to be able to get into the rom to root. Maybe there is another way.
6 hours later and i got nowhere...
I rooted phone, flashed new cyanogen rom, setup amon ra's recovery but I didn't do new radio since my current is one of the newer ones.
The booting goes nowhere as soon as the rogers logo shows at the beginning of boot up.
Would a new radio help? Could that be the issue?
edit:
The phone rebooted properly and now I have a working fone!
Wait, how did you root the phone without getting into the ROM?
beav_35 said:
Wait, how did you root the phone without getting into the ROM?
Click to expand...
Click to collapse
I used the Androot method, copied onto sd card, launched file via file manager app on phone and it rooted the phone. This is how I remember anyways - I fiddled with the phone for good part of the afternoon so my memory is all over the place with the specifics.
I used this site for rooting.
I thought you said in the op that you couldn't boot into the ROM (got stuck on boot screen). So, what was the problem in the first place? (or how did you fix the ROM?)
Sorry I guess I wasn't clear enough in op.
The only way I could get to use the phone was to do a hard reset and let the phone boot up from there, however if I ever wanted to turn the phone off or restart the phone it would get stuck on the next boot up.
I was able to flash the rom by constantly hard reseting the phone every time I needed to put files onto the memory card.
I've been having trouble with my Vibrant and with T-Mobile in limbo I picked up a N1 off ebay to hold me over. This thing is driving me insane!
The phone came with CM7 installed on it, but the person that shipped it to me didn't erase any of there stuff so I figured I would flash a fresh image on the phone to take care of things. I've flashed my Vibrant a dozen or so times and never had an issue. Flashed the N1 and it comes up with an X made of 4 different colored lines and a little lock at the bottom. I know some roms take a while to load so I let it sit for an hour. Nothing.
Since I've been trying everything I can find out how to recover the phone including all of the guides on the wiki. I'm at my wits end at this point. I can't get into clockwork at all on the phone. It gets stuck in the bootloader and if I select recovery it just takes me back.
I've got droid explorer running, and the phone shows up, but it doesn't show anything on the phone, no folders or files and won't let me load anything on to it. (it says it is, but then stays blank) I have no clue what to do at this point short of taking a sledge hammer to it. (obviously I'm posting this as I consider that to be plan B)
I don't need anything special, I just want a working phone. Is that really so much to ask for?
If ur Phone is running( means u can boot) try flashing cwr from rom manager and flash the rom again or try to hard reset the phone and then see ?
Firstly, I would start of by being more specific about what you have tried.
If you really have tried "everything", then there's nothing anyone can do for you.
I suspect you haven't tried "everything"...?
danger-rat said:
Firstly, I would start of by being more specific about what you have tried.
If you really have tried "everything", then there's nothing anyone can do for you.
I suspect you haven't tried "everything"...?
Click to expand...
Click to collapse
I'm sure I haven't, just what I found in the wiki
I tried the PASSIMG.ZIP and it failed
I tried Amon_Ra's Recovery and the only way I can get it to do anything is to tell it to flash in droid explorer and it just reboots and gets stuck. Now nothing is showing up file wise in droid explorer and I can't transfer the image onto the root.
When I could get into clockwork I tried flashing different roms but it would just go to a screen with the clockwork logo and get stuck.
amolji said:
If ur Phone is running( means u can boot) try flashing cwr from rom manager and flash the rom again or try to hard reset the phone and then see ?
Click to expand...
Click to collapse
I can turn it on to the screen with the multicolored X or the bootloader, that's it. How do I do a hard reset?
n25philly said:
I can turn it on to the screen with the multicolored X or the bootloader, that's it. How do I do a hard reset?
Click to expand...
Click to collapse
in the bootloader I think (dont take my rookie rooting words too serious) theres a hard reset menu under recovery. it will take you to another x and press volume up and power for the menu to pop up.
try fastboot a recovery image (either Amon Ra or CWM) and see if you can get back to recovery after that.
Well I'm assuming you already have a custom recovery since it came with CM and you've, as you said, flashed it (what exactly do you mean by that by the way? flashed another rom?). So all I can recommend is that you wipe a few times and try flashing a few different roms and hopefully one will boot. Not the best advice in the world but its always worked for me before and my N1 and my DEXT before hand when I've messed them up!
You still did not say what you flashed to your phone.
Anyways follow the restore to stock guide.
I don't know what this Droid manager thing is but don't use it. Install the sdk.....
Ok, so, a few weeks ago I tried rooting my new Incredible S from Bell running 2.3.3
I was able to S-Off and then installed CM7. Problem was the phone app would make and receive calls, I just couldn't hear anything nor could the person on the other end. After trying to update my radio I gave up and I thought I went back to stock by installing RUU_Vivo_BellMobility_WWE_1.37.666.3_Radio_Radio_20.23.30.0802U_38.02.01.17_M_release_174461_signed.exe
Once I installed this everything seemed to work properly again although my signal seems crappy but being used to the iPhone I have no basis for comparison.
So last night I thought I'd try and root again and put CM7 back on. I turned off fastboot and rebooted. When the menu came up I was surprised to see I was still S-Off as I thought it would have reverted back to stock. Clearly I have no idea what I'm doing when it comes to Android.
Anyway, after I noticed I was s-off I copied su-3.0-efgh-signed.zip to the root of my SD and attempted to enter recovery mode but all I get is a small pic of my phone with an exclamation point through it.
What I'd like is to root this puppy and run CM7 (or if you have a better suggestion for a rom) and have my phone app work properly. Is there anyone that can point me in the right direction.
Thanks guys!!
christanya99 said:
Ok, so, a few weeks ago I tried rooting my new Incredible S from Bell running 2.3.3
I was able to S-Off and then installed CM7. Problem was the phone app would make and receive calls, I just couldn't hear anything nor could the person on the other end. After trying to update my radio I gave up and I thought I went back to stock by installing RUU_Vivo_BellMobility_WWE_1.37.666.3_Radio_Radio_20.23.30.0802U_38.02.01.17_M_release_174461_signed.exe
Once I installed this everything seemed to work properly again although my signal seems crappy but being used to the iPhone I have no basis for comparison.
So last night I thought I'd try and root again and put CM7 back on. I turned off fastboot and rebooted. When the menu came up I was surprised to see I was still S-Off as I thought it would have reverted back to stock. Clearly I have no idea what I'm doing when it comes to Android.
Anyway, after I noticed I was s-off I copied su-3.0-efgh-signed.zip to the root of my SD and attempted to enter recovery mode but all I get is a small pic of my phone with an exclamation point through it.
What I'd like is to root this puppy and run CM7 (or if you have a better suggestion for a rom) and have my phone app work properly. Is there anyone that can point me in the right direction.
Thanks guys!!
Click to expand...
Click to collapse
You need to reinstall ClockworkMod recovery. When you went back to stock, it overwrote ClockworkMod recovery with the stock HTC recovery.
Ok, will give it a shot. Thanks!
Once I do that, should I be able to flash CM7? The radio is what's really gonna confuse me though.
Just tried reinstalling clockwork recovery and I get the same thing, pic of phone with red exclamation. I have to remove the battery to reboot.
Could the problem be that I need to go back to stock completely and then start from scratch??
christanya99 said:
Just tried reinstalling clockwork recovery and I get the same thing, pic of phone with red exclamation. I have to remove the battery to reboot.
Could the problem be that I need to go back to stock completely and then start from scratch??
Click to expand...
Click to collapse
What method are you using to try and install CWM?
I stuck it on the root of my sd, I boot into the menu and select recovery. That's when I get the exclamation point.
christanya99 said:
I stuck it on the root of my sd, I boot into the menu and select recovery. That's when I get the exclamation point.
Click to expand...
Click to collapse
You will need to either install CWM using a PG32IMG.zip file method or flash the image in FASTBOOT USB mode. You cannot flash CWM using the standard HTC recovery.
Try following STEPS 4 through 9 from the following post:
http://forum.xda-developers.com/showthread.php?t=1337105
I rebooted my phone to install a font and now it continues to turn on (HTC logo) and then restart. Tried to get into recovery and it just exits...
I had my phone off at night and turned it on - read a few text messages - and went to replace the ****ty font I installed yesterday.
Just looping.
Any help?
Can't even turn it off lol - I would need to go into bootloader and click power down. It is odd - I didn't do anything and it started up perfectly before 5 minutes I did the fonts.
flash the boot and/or recovery?
pwr2wh8 said:
flash the boot and/or recovery?
Click to expand...
Click to collapse
I flashed the recovery with CWM and installed Android Revolution HD 6.1
I was just wondering if it was safe to re-flash the recovery again to see if it would work. I don't want to screw up this phone lol.
EDIT: Got it. Reflashed the recovery and had to reflash the ROM.
I don't know why a simple font change would screw ALL of that up. I don't want to keep flashing this ROM lol it has been about 4 times now.
rowebil said:
I flashed the recovery with CWM and installed Android Revolution HD 6.1
I was just wondering if it was safe to re-flash the recovery again to see if it would work. I don't want to screw up this phone lol.
EDIT: Got it. Reflashed the recovery and had to reflash the ROM.
I don't know why a simple font change would screw ALL of that up. I don't want to keep flashing this ROM lol it has been about 4 times now.
Click to expand...
Click to collapse
The ROMS this phone and everything is new. Give it a little time unless you want to guinea pig for use :cyclops:
I had the same thing when I flashed a power menu mod made for this phone but not for my OTA. Really weird thing is when I cleared the cache android booted did its upgrading thing and then restarted and went back to stuck at HTC logo.
nullkill said:
The ROMS this phone and everything is new. Give it a little time unless you want to guinea pig for use :cyclops:
I had the same thing when I flashed a power menu mod made for this phone but not for my OTA. Really weird thing is when I cleared the cache android booted did its upgrading thing and then restarted and went back to stuck at HTC logo.
Click to expand...
Click to collapse
I have the same...
What ca I do?
Reflash recovery doesn't help.
It keeps restarting...
:crying:
DannySchaukens said:
I have the same...
What ca I do?
Reflash recovery doesn't help.
It keeps restarting...
:crying:
Click to expand...
Click to collapse
You need to reflash what ever was on it. Hopefully you made a backup if not and were on stock find the correct nandroid back or RUU for your phone and flash that. You can also try doing a factory reset that may bring it back.
agreed...try to re-flash everything to stock than go from there to find what is causing the problem.
Hey guys, Im fairly new to this stuff, but I got a question or two, it may take me a day to reply so i'll try to put as much info as posible.
Now recently I received the OTA 4.20 (Lolipop) on my phone, so I flashed my stock recovery to download the OTA, making me reroot my phone.
So my phone is re-rooted (after 2 tries) but now it seems like I cant write to my SD card, so I got fed up and went into TWRP recovery and selected wipe data and restore. (Restore point was before I got lolipop) I try to reboot but it takes me as far as HTC One screen. Next I go to recovery and try a factory reset, says its successful, but it lied to me! Still stuck at HTC One screen. So I flash back to stock recovery to try the factory reset with that, it went for a moment, then tried to boot, getting stuck at HTC one screen again, so once more, I flash TWRP to my phone in attempt to get the recovery back, but now I can't load recovery, or boot. So Im stuck there. Is there any advice to what to do from here? I tried command 'fastboot erase cache' thinking that would do something and reflashing the recovery.img but it's still not working. I hope someone can help me.
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
The reason you can't write to your SD card isn't because of lollipop, that was actually added but on kit Kat, but the devs went and added a line of code to a file to allow it again. I am currently running my stock rooted, built from decrypted ruu, originally I wasn't able to but I added that one line of code. I believe all you have to do is flash a stock rooted and SD card write should be enabled. As for not being able to get into recovery or boot at all, boot to bootloader and ruu then flash twrp.
Ok so correct me if im doing something wrong, but I flashed the stock recovery in attempt to factory reset it, it wont work, so I flash TWRP with command line (Fastboot flash recovery twrp.img) And it's 'successful' but it wont load, it will attempt to load but one second in and it goes back to fastboot, how to I move forward from here?
Edit: so idiot me did it again, I was trying to install M7 version into a m8. Resolved, Now I can enter recovery again.
Alright, so now my only problem is now that it wont boot normally, it freezes at HTC one screen. I have access to TWRP recovery, just not sure what to do next from here.
ArthAngel said:
Alright, so now my only problem is now that it wont boot normally, it freezes at HTC one screen. I have access to TWRP recovery, just not sure what to do next from here.
Click to expand...
Click to collapse
I actually just unlocked my bootloader yesterday, installed TWRP today, and had what I thought was the same. The thing is, let it sit. Mine sat at the HTC ONE screen for what seemed to be between 5 and 10 minutes. I read that it happens in one of these threads.
But I let it sit and it eventually went to "Android is Upgrading" and was loading the apps.
dopy25 said:
I actually just unlocked my bootloader yesterday, installed TWRP today, and had what I thought was the same. The thing is, let it sit. Mine sat at the HTC ONE screen for what seemed to be between 5 and 10 minutes. I read that it happens in one of these threads.
But I let it sit and it eventually went to "Android is Upgrading" and was loading the apps.
Click to expand...
Click to collapse
Ok thanks, I'll post back in 20 minutes with an update.
So i've waited about 20 minutes on the HTC one screen, (Still on it as I post this) It is still stuck on it. I dont know if this helps but im able to view my internal and external card via computer cable, but I only see folders, no files of any kind in any of them..
Edit* I WAS able to read it, now I can't.
I GOT IT! I was able to revert to a backup I made. Even though I gotta flash stock again for OTA but F it! I got it working again. Thanks for all your help!