I used the GN Toolkit V2.2 to unlock the bootloader, after installing the adb drivers via PDANet. I flashed Clockwork Mod on as well, and was going to install the Android Revolution ROM. I thought I had already copied the zip file to the internal storage, but when I tried to flash it from inside CWM, it said no files were found. (May have copied it before wiping device, I can't remember). So I restarted so I could copy the zip file again and then flash it. However when starting, it seemed to be stuck on the startup screen, with all the flashing blocks of color fading in and out. After a while stuck on there I couldn't do anything so I did a battery pull to restart. At this point, I can start normally or into recovery mode. If I try to start normally, (or go into recovery mode and choose restart from the submenu), it shows the black screen with the white Google logo, and the unlocked icon, stalls for a few seconds, then does a short vibrate and reloads the logo again. It will keep doing this and not go any further. I tried doing an additional data wipe from recovery mode but that didn't help, and I tried to do USB mount from recovery mode, hoping to copy the Revolution zip file and flash it over, but it couldn't mount. I'm starting to panic a little bit, did I brick or otherwise mess my phone up? What can I do? Any help is REALLY appreciated.
Thanks so much and I hope this is the right forum.
I dont have the answer but I wanted to post to calm you. This happens a lot.....multiple times to me on my android devices. You live and learn next time, do a backup in cwm before wiping data and flashing new stuff
Im sure someone will post shortly to solve your problem
Well ok that is reassuring thanks. I downloaded the Google factory ROM from the code.google.com and was able to flash that on my phone with GN Toolkit. It is trying to boot right now, still on the colorful screen. I think maybe I didn't give it enough time last time around? At least I'm past the black and white logo screen. So I'll let it sit for a few minutes and see what happens.
Edit: I let it run for a couple minutes, and it blacked the screen for a sec, showed the white Google logo again, and then went into the colorful startup screen again. I think it's working now so that's a relief.
If someone finds this thread in the future with a similar issue: Don't battery pull during start up and be patient if you don't want to freak yourself out haha. But as spitefulcheerio said, it will be okay so just don't panic. Thanks again.
Make sure you do a Factory Reset in STOCK recovery after unlocking the bootloader. THEN install CWM. learned that one the hard way. skipped a step after doing the oem unlock.
Yes, first time will take awhile on the boot animation.
And, as long as you see the google logo, you are ok, even if it freezes on that. They designed this phone to be easy
Sent from my Galaxy Nexus Bugless Beast 4.0.3 lte +franco#6
Guess all I needed was a psychological confidence boost, thanks for everyone for being supportive I thought I just threw a few hundred bucks away. But I got Revolution installed, phone and rooted and runs like a dream. Thanks all around!
mynameismolotov said:
I used the GN Toolkit V2.2 to unlock the bootloader, after installing the adb drivers via PDANet. I flashed Clockwork Mod on as well, and was going to install the Android Revolution ROM. I thought I had already copied the zip file to the internal storage, but when I tried to flash it from inside CWM, it said no files were found. (May have copied it before wiping device, I can't remember). So I restarted so I could copy the zip file again and then flash it. However when starting, it seemed to be stuck on the startup screen, with all the flashing blocks of color fading in and out. After a while stuck on there I couldn't do anything so I did a battery pull to restart. At this point, I can start normally or into recovery mode. If I try to start normally, (or go into recovery mode and choose restart from the submenu), it shows the black screen with the white Google logo, and the unlocked icon, stalls for a few seconds, then does a short vibrate and reloads the logo again. It will keep doing this and not go any further. I tried doing an additional data wipe from recovery mode but that didn't help, and I tried to do USB mount from recovery mode, hoping to copy the Revolution zip file and flash it over, but it couldn't mount. I'm starting to panic a little bit, did I brick or otherwise mess my phone up? What can I do? Any help is REALLY appreciated.
Thanks so much and I hope this is the right forum.
Click to expand...
Click to collapse
cancerouspete said:
Yes, first time will take awhile on the boot animation.
And, as long as you see the google logo, you are ok, even if it freezes on that. They designed this phone to be easy
Sent from my Galaxy Nexus Bugless Beast 4.0.3 lte +franco#6
Click to expand...
Click to collapse
mynameismolotov said:
Guess all I needed was a psychological confidence boost, thanks for everyone for being supportive I thought I just threw a few hundred bucks away. But I got Revolution installed, phone and rooted and runs like a dream. Thanks all around!
Click to expand...
Click to collapse
To provide some technical details on why it takes longer the first boot and appears to "hang" at boot animation ...
During the boot animation, the /data/dalvik-cache directory is built up for each application loaded on the device. This occurs during the very first boot. If the /data partition is wiped, the dalvik-cache directory is also wiped and will have to be rebuilt on the first boot. All subsequent boots will be quicker as this directory has already been populated.
Whenever loading a new ROM or performing the fastboot oem unlock command, the /data partition is generally wiped which takes with it dalvik-cache and results in the delayed initial boot time while the dalvik-cache directory is re-populated.
Hope that makes sense and fills in a few blanks on the why Android appears to "hang" at the boot animation during first boot after the /data partition is erased or the /data/dalvik-cache directory is erased.
Related
I flashed the incredibly re-engineered v2.2 rom a week or so ago and it worked great till today it was giving me a force close on a bunch of apps, so i restared it and it still didn't help. Did a *228 and when it restated it just goes to the black screen that says htc incredible Loading then after several seconds it flashes blank for half a second then says same thing. I used rom manager to flash it. I've also used virtuous and skyraider 3.5. I'm good at computers but android is new to me as i've only had this fon 2 months. I have to do a battery pull to restart it. Any Ideas on how to fix this? I can boot into recovery but havn't been able to do anything... Never used it so not sure what to look for but like when i click recovery or factory reset, nothing happens. Oh, and i did a search but didn't come up with similiar problem.
htc incredible s-off
radio 2.15.00.07.28
Flash a different rom.
sent from my Dinc
How do I do that? When I boot in recovery mode I have option of fastboot, recovery, clear storage, simlock, and factory reset. When I select recovery it goes to bootloader, reboot, reboot bootloader, and power down, with reboot highlighted. Wen I select that it boots like normal than gets stuck on boot up screen.
Try fixing permissions through Rom Manager first, if not I would reinstall the rom. Be sure to do a full wipe, don't just flash over your previous rom.
If neither of those work, I would follow this thread
http://forum.xda-developers.com/showthread.php?t=786436
Flash back to stock 2.2 and see if your phone starts acting the same way. If so I would take it back to verizon. If everything seems ok, re-root and flash JUST the rom and apps that you want, no kernel, themes, anything extra yet. See if that fixes the problem.
I made sure I did full wipe when I installed it so that shouldn't b problem. The issue Is i can eve get to rom manager because he Fon wont load past the boot image. And its out of warany so vzw prolly wuldnt be much help.
mennotech said:
I made sure I did full wipe when I installed it so that shouldn't b problem. The issue Is i can eve get to rom manager because he Fon wont load past the boot image. And its out of warany so vzw prolly wuldnt be much help.
Click to expand...
Click to collapse
I would re-download a different ROM (making sure you don't have a corrupt download), check the MD5 SUM's to verify integrity of your download, mount USB Storage in Recovery to transfer the file to your USB card (when phone is off, hold down the Power and Volume Down buttons at the same time), wipe all user data/factory reset and Dalvik, and then reflash the ROM of your choice.
mennotech said:
I made sure I did full wipe when I installed it so that shouldn't b problem. The issue Is i can eve get to rom manager because he Fon wont load past the boot image. And its out of warany so vzw prolly wuldnt be much help.
Click to expand...
Click to collapse
Go to that link in my post, download the PB31IMG from the 2.2 Stock OTA, put it on the root of your SD card, boot into the bootloader and let it update. You will go back to being completely stock and unrooted. Root it and then try installing the rom again.
So I flashed the "Synergy" rom and noticed that I didnt have the 3d carousel effect after letting the rom run for 2 days. I then noticed another download for the rom with the 3d effect. After flashing that rom I am now stuck on the splash screen. I can also no longer boot into recovery. I am able to access the bootloader but that's it. I cant access nothing on my phone.
Find it odd that you cannot get into Recovery. Are you pulling battery, then holding power and down key?
Yep... Ive pulled the battery several times, and tried accessing the recovery by holding power and the down button.. All it does is restart at the splash screen and stays..
Did you wipe prior to flashing ? Never had that issue so what happens when you click on recovery in the boot loader.
You said in the first post that you can access the boatloader, but in your next post, you say starting your phone with vol down and power takes you to your splash screen... this is an important piece of info for me/us to know in order to help, give advice.
If it goes to the boatloader, try reflashing a custom recovery. If it's going straight to your splash screen, that is a result of " fastboot" being enabled in the settings menu, and you're holding your phone wrong and have to wait longer ( up to 10 minutes) as it can take a while to build the dalvik cache and set up the symlinks.
Tower, this is SkyRaider requesting a fly-by...
Flash a custom recovery pc36img.zip in bootloader. When done boot into recovery and factory wipe. Then partition your sd with 1024mb ext2, move ext2 to ext3. Flash synergy and u should be good. Backup ur sdcard before partitioning it.
Sent from my......ummm...let me get back at'chya!
Have no idea how he messed it up .
reaper24 said:
Have no idea how he messed it up .
Click to expand...
Click to collapse
It's one of two things... bad wipe or user is just impatient and isn't used to the longer initial boot time of the sense 3.0 roms, so panic sets in after 2 minutes of boot
Tower, this is SkyRaider requesting a fly-by...
Ok here's my process fellas and this is whats happening (or not happening). Phone is stuck on the SPLASH screen. I can hold the volume down button and power and get into the bootloader. Here's what Ive tried so far thats not working for me. Trying to go into recovery through the bootloader takes me back to a stuck SPLASH screen. Ive installed a PC36IMG.zip (Custom recovery) and when the HBoot looks for the file it doesnt see it. The file doesnt have zip.zip as the extension and the MD5checksum was good on the file. When I installed the rom I did do a full wipe and when i hit restore it took me to my SPLASH screen and stayed there longer than 10 minutes. I flashed plenty of roms and this is the 1st time ive been at this point where im unable to boot my phone. I suspect the recovery is broken
and as of now, there is no other way (that i know of now) for me to load a custom one into my phone.
I also tried to push the file via adb and when entering the command adb shell, i get a device cannot be found message.
Hope this helps you guys help me.
I'm now having the same problem with my Thunderbolt. I need some major help. I can boot into bootloader, but not recovery because I have a p50IMG.zip on my sd card...so it just scans it and asks to install...how do I get it off of the card?
Hello every one,
I am new to the forums and have been looking around for some time. I have a major issue that I need some assistance with if possible.
I am running, well was running, gingerbread 2.3.3 on my HTC Evo 4g phone until yesterday night. Here is some info about what happened. I rooted my phone with revolutionary and everything was going good til I tried to install a new ROM on the phone. The ROM I was downloading was CyanogenMod7, When it finished downloading, the phone booted itself into recovery to install the ROM. Well this is when the problem started, it just sat at the install screen and when it got down with the install it just continued to boot itself into a loop.
I turned the phone off and tried to boot it into recovery, which it did by the way. I did a complete restore of the stock ROM and rebooted the phone, when the phone turned back on is when the phone just continued to restart itself over and over again. So, I did a complete wipe: Recovery, Clear storage etc and nothing seemed to work but instead of it restarting itself, it just sits at the recovery screen and wont go any further. Just like it doesn't have any OS installed to boot from.
I would like some help and see what I can do to fix this problem.
When I go to recovery and boot from the fastboot-bootloader it says:
SD checking "No Image" Loading...
No Image,
loading.....
No image,
Loading....
No image or wrong image....
Click to expand...
Click to collapse
on top of that the sd card well not mount to the phone. I am so lost right now.
Some one pelase help or point me in the right direction.
Which recovery are you using for this? Maybe you can actually get it together by doing a complete wipe and cleaning cache/dalvik and then do the recovery.
I am using the clockwork recovery v3.0.0.5.
Every time I try to wipe the Dalvik Cache it tells me
E:unknown volume for path [/sd-ext] Dalvik Cache wiped
Click to expand...
Click to collapse
I still get the same thing. The one issue that I have encountered was that the sd card is not mounted to the phone. I have android sdk tools installed but the program can't seem to find my phone when I run the command prompt. The other things is now my phone just randomly shuts down and the the battery light just blinks, like its in stand by mode or something. The only thing I can do is take the battery out and what, then replace the battery and see if it works.
Try to charge the battery without using the phone that way you can work with it. My suggestion is to use Amon-RA recovery. Works a whole lot better that Clockwork. And try from there if you can install the ROM right.
It might be problems with your SD card. If is not reading it then that would be the message.
I tried that and nothing, I gave up on trying to save the phone that I went and got a replacement for it.
Hi guys
I've searched the forum for something like this but I'm coming up empty handed. But then again, I'm freaking out a bit.
I just tried flashing ARHD 9.7.0 and I've hit a big snag... For a bit of background, I was previously running ARHD 9.4.2 with the Endeavoru-Faux123-010b3 kernal. The battery was at 35% when I started the process...
I downloaded the zip, put it onto my SD card and rebooted into CWM. No worries there.
Did a wipe/factory reset and wiped the cache aswell. No worries there.
I did NOT flash the boot.img in the zip as I believed it would work okay with the current kernel (possibly the issue)
Went to install zip from SD card and chose the zip to install. AROMA starts up and I go through the familiar install process. No problem there.
I checked the reboot now option in AROMA and let it reboot. This is where the fun begins...
I get the beepy boopy start up sound and let it sit there because, as we all know, first boot can take a while. 10 minutes later, it's stuck at the HTC One splash screen. So I thought I'd reboot into CWM and start over like I've done with other ROM/kernal incompatibilities.
So I hold down the power button, let the three lights blink and the screen go blank and hold down the volume down button. And it goes back to attempting to boot up. I've tried different combinations of holding the buttons down and letting them go and hell, I've even sat there hammering the volume down button while it starts up! Still, I can't get into the bootloader.
Obviously, no bootloader, no ADB connection so I can't go through CMD and can't re-flash the kernel.
I'm currently sitting here looking at it. The USB cable is plugged in and the orange light is lit up so I hope it's charging. I'm at a loss here guys. Please, if anyone can give me some help, I will be most appreciative.
I'm really sorry to have wasted your time. It worked eventually after about 50 tries! :laugh:
Looks like it ws a kernel incompatibility.
But out of curiosity and for anybody else who gets this problem and really can't boot into the bootloader, what would be the steps involved in recovering a device in that state? I'd rather look like a knob in public as long as something constructive comes from it. :silly:
It's a bit tricky to get into hboot after a forced reboot, I think we've all been there
Just avoid the problem altogether by flashing the boot.img inside the zip first to make sure that it boots. Once up and running, flash your custom kernel and modules.
Try this http://forum.xda-developers.com/showthread.php?t=1734365
And don't let go when reboots keep hold of buttons and it should go to bootloader
Sent from my HTC One X using xda premium
I cannot use the hardware buttons any longer to even get into fastboot mode. I tried to insert a new TWRP theme, named it ui.zip, place it in the theme folder, then rebooted the phone and now it will not even go into recovery, fastboot mode, nor turn on. Anybody have any suggestions on how to get through to the recovery. I guess I locked up the recovery, and can no longer boot my phone to even be able to delete that ui.zip file from the theme folder under TWRP.
OK, now I managed to get it into fastboot mode. But that is it.
Can I extract a file from the phone in fastboot mode?
Thanks,
chevy383surfing
Well, I finally figured it out. I'll add an explanation on this whole deal after I get off work. Just in case anybody else runs into the same problem, maybe my little routine will help someone else.
chevy383surfing said:
I cannot use the hardware buttons any longer to even get into fastboot mode. I tried to insert a new TWRP theme, named it ui.zip, place it in the theme folder, then rebooted the phone and now it will not even go into recovery, fastboot mode, nor turn on. Anybody have any suggestions on how to get through to the recovery. I guess I locked up the recovery, and can no longer boot my phone to even be able to delete that ui.zip file from the theme folder under TWRP.
OK, now I managed to get it into fastboot mode. But that is it.
Can I extract a file from the phone in fastboot mode?
Thanks,
chevy383surfing
Well, I finally figured it out. I'll add an explanation on this whole deal after I get off work. Just in case anybody else runs into the same problem, maybe my little routine will help someone else.
Click to expand...
Click to collapse
Next time you loop, vol up and power for 10 seconds with phone Unplugged, then vol down and power to go to boot loader
If for some reason it doesn't restart put the phone close to a bright light
Similar problem
Hi. I am on a Kindle Fire HD 7 and just got cynogeanmod 12. I was going through settings when device got laggy. And somehow the device thought I wanted factory reset so thats what it did. My Kindle Rebooted and now I get a screen that says "teamwin" and every 2 secs. the screen flashes. None of the tips using buttons worked. It can only turn on and off. I need assistance in finding a way to get this back to stock(from there I can re-root and do the process again to get back cynogeanmod).
Thanks,
aputtapa000
aputtapa000 said:
Hi. I am on a Kindle Fire HD 7 and just got cynogeanmod 12. I was going through settings when device got laggy. And somehow the device thought I wanted factory reset so thats what it did. My Kindle Rebooted and now I get a screen that says "teamwin" and every 2 secs. the screen flashes. None of the tips using buttons worked. It can only turn on and off. I need assistance in finding a way to get this back to stock(from there I can re-root and do the process again to get back cynogeanmod).
Thanks,
aputtapa000
Click to expand...
Click to collapse
First, this is the M8 forum, not the Kindle forum. However, I actually can help you with that.
Most stock recoveries seem to have a problem with doing factory resets. Flash the stock recovery for your device, let it perform the factory reset, boot back into the OS (to make sure it worked), then reflash your custom recovery.
jshamlet said:
First, this is the M8 forum, not the Kindle forum. However, I actually can help you with that.
Most stock recoveries seem to have a problem with doing factory resets. Flash the stock recovery for your device, let it perform the factory reset, boot back into the OS (to make sure it worked), then reflash your custom recovery.
Click to expand...
Click to collapse
Tank you for this quick reply :good: . I will try to get back into my stock recovery but if it is on my device, how will I access this on my computer and force flash it on my tablet. I only need help making the tablet responsive/workable. Once this is done I should be able to figure out the rest.
Thanks