All ROMs stuck in boot screen - Verizon Droid Incredible 2

Hello all - I've been working for a few weeks (off and on) trying to get my old Incredible 2 in a working order to use as a wifi media device. To get he newer apps I needed to upgrade to at least ICS. I went through htcdev to be able to flash roms and then decided to downgrade and try to get to s-off - at which point I discovered revolutionary was down....I've since been able to get back to the htcdev unlocked bootloader process so I'm s-on with hboot .98. I'm using TWRP 2.6.3. I've tried three different roms - two cm10.2 and one cm11 and while they flash I'm not able to get past the boot screen (past the HTC one). I've done wipes before each flash and I've flashed the correct boot.img each time. I've tried each one of them at least twice to no avail. Is there any other settings or things to try??
My ultimate problem is that I was able to get to Android 4.2.2 but the app that I need to play my music from the cloud is Microsoft Groove which due to a recent change is no longer working with 4.2.2 (kind of like the perfect timing I had with revolutionary being down) - so I'm trying to get to something higher than that...Any other ROM ideas might help too???
Thanks. I've learned so much following this forum over the last few weeks - I just can't seem to get past this one by myself.....

Well thankfully I was able to solve my own problem...Figure I'd update here in case anyone else comes across the same issues. I basically did not have the best TWRP version installed - you need to have TWRP 2.7.0.0 installed. Once I installed that recovery I was able to flash each and every rom and the phone is starting up fine (after also flashing the correct boot.img file). We'll now see if I can get past the app issue itself that I was having but I'm definitely past the boot screen issue.

Related

Looking for some help...

Ok all, i think i have hit my limit of what i can think to do to fix my phone so i'm throwing this out looking for some help.
So i have run into a major problem. Starting back on the first i flashed from CyanogenMod Nightly 175 to nightly 181, 181 FC's alot on the google processes framework and such, and it was unusable so i went back to my Nightly 175 restore i had created. It was working fine until today and it became unusable, FC's for everything.
So i first started by trying to get into Safe Mode to do a restore, and RomManager FC'ed before i could get it to do anything
Then i tried to get into the restore area, same thing, FC
Tried to use the notification Tray icon to "update" to 181, same thing FC
All these steps were attempted again after a normal reboot
None worked
I then went to reboot into recovery, and it only would reboot into the Bootloader
Once in the Bootloader i tred to do the Recovery option, but all it does is reboot into the bootlaoder
I do know that i had just updated the RomManager recovery option to 5.0.2.0 or whatever the latest was. I'm wondering if there is a problem with that?
My phone was originally reflashed with unrevoked 3.
i went to dougpiston.com and got the RUU program from there after searching through some forums, but that program when run says it is unable to communicate with my phone when attempting to verify software on my phone
I also tried un-sync'ing all of the google accounts on the phone and a factory reset, but even after the reboot the last account is still there and it appears as if the factory reset did not work
I also have this posted over in CM's forums, but i was hoping maybe someone here could help.
anything is appreciated at this point
garaxiel said:
Ok all, i think i have hit my limit of what i can think to do to fix my phone so i'm throwing this out looking for some help.
So i have run into a major problem. Starting back on the first i flashed from CyanogenMod Nightly 175 to nightly 181, 181 FC's alot on the google processes framework and such, and it was unusable so i went back to my Nightly 175 restore i had created. It was working fine until today and it became unusable, FC's for everything.
So i first started by trying to get into Safe Mode to do a restore, and RomManager FC'ed before i could get it to do anything
Then i tried to get into the restore area, same thing, FC
Tried to use the notification Tray icon to "update" to 181, same thing FC
All these steps were attempted again after a normal reboot
None worked
I then went to reboot into recovery, and it only would reboot into the Bootloader
Once in the Bootloader i tred to do the Recovery option, but all it does is reboot into the bootlaoder
I do know that i had just updated the RomManager recovery option to 5.0.2.0 or whatever the latest was. I'm wondering if there is a problem with that?
My phone was originally reflashed with unrevoked 3.
i went to dougpiston.com and got the RUU program from there after searching through some forums, but that program when run says it is unable to communicate with my phone when attempting to verify software on my phone
I also tried un-sync'ing all of the google accounts on the phone and a factory reset, but even after the reboot the last account is still there and it appears as if the factory reset did not work
I also have this posted over in CM's forums, but i was hoping maybe someone here could help.
anything is appreciated at this point
Click to expand...
Click to collapse
You're problem is ClockworkMod. Version 5 is a steaming heap of crap that's caused this sort of problem, not only for dInc users, but Tbolt and other device users. The solution seems to be flashing back to an older recovery. And if it works, don't fix. I'm still running version 3.something on my Tbolt and have no plans to change that. I NEVER use ROM Manager and recommend nobody ever touch it except for a few things. I almost never have it installed on any device.
OK then dumb question but if RomManager FC's on me, how do i flash back to a working version or to an alternate version entirely? i have been unable to find other ways of flashing outside of RomManager
Older Recovery versions are available on "dougpiston.com" just follow the directions.
www.dougpiston.com has what you're looking for under "recoveries". They're flashed in hboot like a radio, RUU, splash screen, etc.
Also if that doesn't work, which it probably will, you can also flash a PB31IMG which essentially is the RUU but you do not need a PC. You put that on the root of the SD (as in, not in any folders. Probably know that already...) and reboot into HBOOT (Power and volume down) and itll load it up.
Note: Make sure the file is PB31IMG.zip and not PB31IMG.zip.zip
Ha!!! got it back (well on the road to back anyways)
Was able to find a PB31IMG on dougpiston.com and hboot flashed it in (3.0.0.8). I had one on my PC but it must have been corrupt because it didn't work before. once that was working i was able to get into recovery get a restore back to my 175 nightly and am in the process now of flashing nightly 181 on there cleanly and rebuild the whole phone from scratch. damn i hope this works thanks all for help and ideas.
Nice, I actually had the same problem when I updated cwm but it was way back when they first updated to the 2.x.x recoveries. I was freakin for a bit lol....glad you got it working. Does anyone know why whenever I flash a different version of cwm I have to flash it twice?
Sent from my ADR6300 using xda premium
pete_kowalski83 said:
Nice, I actually had the same problem when I updated cwm but it was way back when they first updated to the 2.x.x recoveries. I was freakin for a bit lol....glad you got it working. Does anyone know why whenever I flash a different version of cwm I have to flash it twice?
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
No idea...are you using ROM Manager?

[Q] Google apps on Cyanogen 7.1 booted as recovery update as the only possible option

Hi everybody,
After unlucky rooting process I've got problem with installing new rom with traditional way. Then I found thread about booting from sdcard having recovery access at my disposal only. This is great idea to have phone working again, but unfortunately it is pain to live without all google apps installed. I tried to install this packages from WIKI (gapps...) but this didn't work.
Desire Z is visible as rooted but unlocked (by HTCDEV tool) and with S-ON. Any ROM update I do goes fine up to the final phone restart. The only white screen with original HTC is lighting without any further change.
I do appreciate if any volunteer could give me a bit of support to get my phone working back.
[I've got my phone back with all functionality by booting ROM - _WWE-2.42.405.2-signed.zip. This fixed my problem and now I can work to make phone as S-OFF]
you need to be S-OFF at first. then you can flash roms.
There are many many tutorials how to get S-OFF.
Best and good luck,
Blubberor

Not bricked but won't get past initial start up screen

Hi.
My son's Galaxy Nexus (Verizon) is having some serious issues. HE has been crack flashing everything under the son (Just like his data) and recently he tried a 4.3 rom (Not sure which one). He started to get random crashes so he flashed back to one of the 4.2.2 rom. Then the phone started crashing all the time so I hooked it up the the Nexus toolkit (I assume it is the one everyone uses) and decided to do a full wipe. The phone was basically two folders and would not boot past the Google logo.
When I hooked it up to the tool kit software it was recognized and I flashed the stock (VZ) rom, no root. When I booted the phone it would go to the start screen looking for WiFi and when I tried to go through the start up process the phone would lock up and reboot. I cannot get past this point to do any troubleshooting.
So is this a hardware issue (The phone is toast) or am I missing something as far as doing a complete wipe to get back to bone stock?
Thank you for your help. (I have as well as my son have been trolling this site and others looking for answers but since I can boot up most did not apply, I think)
mlfca said:
Hi.
My son's Galaxy Nexus (Verizon) is having some serious issues. HE has been crack flashing everything under the son (Just like his data) and recently he tried a 4.3 rom (Not sure which one). He started to get random crashes so he flashed back to one of the 4.2.2 rom. Then the phone started crashing all the time so I hooked it up the the Nexus toolkit (I assume it is the one everyone uses) and decided to do a full wipe. The phone was basically two folders and would not boot past the Google logo.
When I hooked it up to the tool kit software it was recognized and I flashed the stock (VZ) rom, no root. When I booted the phone it would go to the start screen looking for WiFi and when I tried to go through the start up process the phone would lock up and reboot. I cannot get past this point to do any troubleshooting.
So is this a hardware issue (The phone is toast) or am I missing something as far as doing a complete wipe to get back to bone stock?
Thank you for your help. (I have as well as my son have been trolling this site and others looking for answers but since I can boot up most did not apply, I think)
Click to expand...
Click to collapse
Right off the bat, do NOT use toolkits anymore. Please. You need to learn how to use Fastboot.
The best thing to do is start completely fresh. Download latest Galaxy Nexus factory images and fastboot them.
If you have no idea how to use fastboot, I suggest going to this thread and reading up my man: [GUIDE]New To Adb And Fastboot Guide
Any other questions or help I can gladly answer.

HTC M8 weird booting issue

Hello team, I have a weird issue when booting my phone.
HTC M8 8Unlocked International version
This started after I installed Venom Rom 2.0.
It continuously made crash the systemui process so I thought something went wrong with the rom installation.
I reinstalled it, same thing.
I went back to Venom 1.8.0
Problem started:
When it boots I get the HTC white screen and then stays there forever. I thought it was stuck on the boot screen but if I press about 4 or 5 times the power button the screen refreshes and I can use the phone.
I have tested several things and noticed that after 2 minutes, when the HTC logo is there I can press the volume buttons and they actually work. Just the screen is not refreshing until I press several times the power button.
Here is what I have tried to fix this weird issue:
Did full clean with TWRP
I reinstalled Venom 1.7.1 same issue
Upgraded to 1.8.0 same issue
Installed insertcoin rom, same issue
Reinstalled TWRP (Advanced > Reflash Recovery) and went back to Venom rom, same issue
In TWRP I used the option Advanced > Restore Original Boot. Same issue
I did fix permissions. Same issue
At this moment I have no idea what else to try.
ADB and FastBoot are fully functional in my pc.
I noticed I cannot gain SU from ADB when the phone is on this state. As soon as I do adb reboot the phone returns in that state and once is connected back and I can see it using adb devices, the su command does nothing.
I want after fixing this thing to remove the red banner from the screen.
I would really appreciate any suggestions.
Have tried updating the firmware?
I had the long booting issue with custom Roms until I updated my firmware to 2.22.401.4
I think it's cause the latest updates of most the custom Roms run off that firmware and you might be running the older one.
You need to be S-off I think to flash firmware. And it might say you are on 2.22.401.4 in the phone settings but that might not be correct.
LinS123 said:
Have tried updating the firmware?
I had the long booting issue with custom Roms until I updated me firmware to 2.22.401.4
Though I had to get S-off to flash it.
Click to expand...
Click to collapse
Yeah I can't update it because I cannot get s-off since su is not working for me.
One last thing I just tried was installing an Odexed rom and the problem did not happen. This whole story started when using the stock rom, for no reason my phone started rebooting itself every 2 minutes. Then I installed venom and the problem went away.
I did find this odexed rom before to avoid the red banner which did the trick but the reboot problem came back. :crying:
So now I am just stuck trying to fix this with the custom rom
Well, you can try reverting to full stock and retry the entire root process from scratch.
The other way is to revert back to stock and wait for the new OTA to finally be pushed for the firmware update.
Try following this guide. It's written really well and should get you root access properly.
http://forum.xda-developers.com/showthread.php?p=53807690
Credits go to Vomer, the original writer of the guide; it's extremely well written and easy to follow.
EDIT: Posting from a phone is hard... Autocorrect is not always your friend.
LinS123 said:
Well, you can try reverting to full stock and retry the entire root process from scratch.
The other way is to revert back to stock and wait for the new OTA to finally be pushed for the firmware update.
Try following this guide. It's written really well and should get you root access properly.
http://forum.xda-developers.com/showthread.php?p=53807690
Credits go to the original writer of the guide, it's extremely well written and easy to follow.
Click to expand...
Click to collapse
I appreciate the response, I will try that and see what happens.
Just a heads up. Firewater is not guaranteed to work for S-off. It comes down to luck of the draw.
My M8 was an unlucky one so I had to find another way. I hope yours works with Firewater.
There is another tool called sunshine but it is $25, and it guarantees to S-Off any HTC One m8 variant, but I think I might just wait for the official firmware rather than spending $25.
Billchen0014 said:
There is another tool called sunshine but it is $25, and it guarantees to S-Off any HTC One m8 variant, but I think I might just wait for the official firmware rather than spending $25.
Click to expand...
Click to collapse
Thank you for this option as well. I did firewater and gave me the "you are unlucky" not-very-friendly banner LOL
I did it with Sunshine. (Yeah I paid the $25) Sometimes I do think paying the devs for good work is fine.
I can now remove the red banner
BTW. To close this thread. After flashing an Odexed rom the slowness went away, I went back to Venom 1.8.0 and it continued booting normally . Looks like there is kernel problem in my phone with certain roms.

[q] frequent frustrating data drops on htc one m7

Hello All,
Due to my endless frustrations, this might be a long one so please bear with me!
So I purchased a Verizon Global HTC ONE M7 from the States, I am currently in Nigeria and the only thing that makes me sadder and more frustrated than the state of my phone right now is the incessant terror attacks in the country! Initially, almost everything worked fine when i popped in my new Etisalat sim card into the phone, except for the mobile hotspot (which just conveniently turns out to be the one of the top 3 most important features in a phone for me - probably the feature I use the most) this message kept popping up about how hotspot couldn't be used without a VZW sim, etc (also with the non-verizon sim warning when the phone boots up). I tried all I could, eventually deciding to flash a new ROM to clear out everything Verizon and start fresh.
Enter Viperone 6.2.0 - everything worked initially, but after a few weeks i noticed if I did anything like watch a youtube video or download something over a few MBs 90% of the time the data drops (no visible signs like changes from E to H or 3g or the likes, everything looks the same, just that the data stops), toggle mobile data on/off and data connection is back. It worsened and became more frequent over time. Upgraded to Viperone 6.2.1, no difference, so i figured its probably the viperone rom.
Enter Cyanogenmod - http://forum.xda-developers.com/ver...-oneplus-one-stock-rom-cm11s-verizon-t2857425 - and its the same exact issue from the beginning, so im guessing its not to do with the ROM at all (though there are one or two niggling issues with the ROM - cant change BBM display pic, etc)?! I've really tried to comb through the forum and see what makes sense that i could try without bugging y'all - I did a factory reset, wiped everything completely and its the same thing.
I've seen suggestions to similar issues like: flash stock recovery, update radio/firmware/kernel, flash back to custom recovery and some other things which are beginning to sound quite dangerous in my ignorance!! I did believe updating the firmware made sense but after digging deeper, i must honestly say i'm quite confused on what to do. what radio/firmware/kernel works with what software version, etc- most firmware that i've seen are 4.4.3 compatible, while this ROM is 4.4.4., some of them seem to be for stock ROMs only and a lot of other confusions.
So, I'm not gonna be a hero and brick my phone from trying to do what i do not understand, instead here i am, hat in hand, crying out for help after suffering for 3 months! Its really frustrating as, downloads break causing me to lose data, skype or MSLync calls always break and im beginning to look unprofessional to people! This is why I have decided to put up a post of my own specific to my case so i don't medicate for someone else's ailments. So please........ WHAT EXACTLY DO I DO??
PHONE DETAILS (typing it out as i've just realized on this ROM i can't take screenshots with Power+Home button combo anymore and can't be bothered at this point!!!)
ANDROID VERSION: 4.4.4
BASEBAND VERSION: 1.12.41.1112_2
KERNEL VERSION: 3.4.82-gfe09065; [email protected] #1; Wed oct 8 01:36:03 PDT 2014
BUILD DATE: SUN AUG 3 23:00:51 PDT 2014
BUILD NUMBER: CYANOGENMOD 11S v5 (Verizon)
SELinux status: Enforcing
Thanks
Have you tried a stock version of sense? Essentially what our phone was meant to run. Viper uses a lot of custom tweaks for the masses, and sometimes carrier specifics get finicky. I would suggest santods stock Rom, bonestock, or ecliptic. I think nusense uses an international base and not strictly vzw, but you could also try that one...and santod can clarify about the details.
Hope you get it going.
Sent from my One.
Can you flash stock recovery from Santod's firmware thread and do a factory reset? It could be a corrupt nv partition which would only be fixed by doing a factory reset via stock recovery. (If you must, make a nandroid of system and data in your recovery of choice so you can restore your data if you wish).
Uzephi said:
Can you flash stock recovery from Santod's firmware thread and do a factory reset? It could be a corrupt nv partition which would only be fixed by doing a factory reset via stock recovery. (If you must, make a nandroid of system and data in your recovery of choice so you can restore your data if you wish).
Click to expand...
Click to collapse
Thanks for the responses folks, i'll try out your suggestions and revert..
8100
brymaster5000 said:
Have you tried a stock version of sense? Essentially what our phone was meant to run. Viper uses a lot of custom tweaks for the masses, and sometimes carrier specifics get finicky. I would suggest santods stock Rom, bonestock, or ecliptic. I think nusense uses an international base and not strictly vzw, but you could also try that one...and santod can clarify about the details.
Hope you get it going.
Sent from my One.
Click to expand...
Click to collapse
So.. i found time to get to this and decided to go with your suggestion of Santod's stock rom... and now, i think i've done the unthinkable!! After WIPING EVERYTHING "All partitions except SD!" as the instructions stated... i attempted to reboot into bootloader and got a message saying "no OS installed, are you sure you want to reboot"... that scared me a bit, but i thought surely, it must be part of the process! I proceed to reboot to bootloader to flash the firmware and i cant seem to do anything!!
Fastboot is stuck on " waiting for device" for everything i try.
Also, i rebooted back into recovery and attempted to install the stock rom: i get the error message "unable to open zip file"..
Have i destroyed my phone with my own hands, people? :crying:
Mr HaRR said:
So.. i found time to get to this and decided to go with your suggestion of Santod's stock rom... and now, i think i've done the unthinkable!! After WIPING EVERYTHING "All partitions except SD!" as the instructions stated... i attempted to reboot into bootloader and got a message saying "no OS installed, are you sure you want to reboot"... that scared me a bit, but i thought surely, it must be part of the process! I proceed to reboot to bootloader to flash the firmware and i cant seem to do anything!!
Fastboot is stuck on " waiting for device" for everything i try.
Also, i rebooted back into recovery and attempted to install the stock rom: i get the error message "unable to open zip file"..
Have i destroyed my phone with my own hands, people? :crying:
Click to expand...
Click to collapse
FALSE ALARM FOLKS!!! I decided to attempt flashing the CM11 rom i just uninstalled and it worked. Turns out its a known issue with the .zip file for that rom - i am now re-downloading from another mirror. Meanwhile the Fastboot thing was just a driver issue - though i'm surprised because i had all the drivers installed on the system and have used fastboot successfully - anyway i reinstalled the drivers and all was well with fastboot again.
NB: Don't get tired of me just yet please!
brymaster5000 said:
Have you tried a stock version of sense? Essentially what our phone was meant to run. Viper uses a lot of custom tweaks for the masses, and sometimes carrier specifics get finicky. I would suggest santods stock Rom, bonestock, or ecliptic. I think nusense uses an international base and not strictly vzw, but you could also try that one...and santod can clarify about the details.
Hope you get it going.
Sent from my One.
Click to expand...
Click to collapse
hello!
Thanks for your ideas guys. I'm currently running Santod's stock rom (which is brilliant, i must say, i actually wanna stay on this rom) since friday - thought i'd give it the whole weekend and see how it goes.. BUT! i still get thoseconnection drops.. and frequently too.
Any other ideas on what the issue could be?
Mr HaRR said:
hello!
Thanks for your ideas guys. I'm currently running Santod's stock rom (which is brilliant, i must say, i actually wanna stay on this rom) since friday - thought i'd give it the whole weekend and see how it goes.. BUT! i still get thoseconnection drops.. and frequently too.
Any other ideas on what the issue could be?
Click to expand...
Click to collapse
If doing factory reset from stock recovery doesn't fix it, it is most likely a burned SIM. It has happened to me. (Average 150+ GB a month in data, so I burn em easily)
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uz has it right, you need to flash a stock recovery and THEN do a factory reset, then reload your custom recovery and rom. I had the exact same issue before. Or you could flash an ruu file which would reset the partitions also.
ccarr313 said:
Uz has it right, you need to flash a stock recovery and THEN do a factory reset, then reload your custom recovery and rom. I had the exact same issue before. Or you could flash an ruu file which would reset the partitions also.
Click to expand...
Click to collapse
Hey folks, apologies for the touch and go nature of this thread - i just don't have a lot of free time on my hands and other reasons..
Anyhow, i think I want to try out ur suggestion of flashing an RUU - I noticed that im unable to actually enter recovery after flashing stock recovery from Santod's thread (i flashed the latest three recoveries). I can get to bootloader, but when i select recovery, the phone goes black for a few seconds and then i get the RED TRIANGLE WITH THE EXCLAMATION MARK INSIDE, obviously something's wrong, few seconds later the phone reboots itself into normal mode. I did do a factory reset from bootloader, but issue persists.
So now to the RUU flashing issue - could you suggest one for me to flash?
By the way though, isn't flashing an ruu gonna take me back to stock completely (as in back to S-ON, ETC..)?
Thanks a whole bunch - IM DETERMINED TO GET THIS TO WORK!!!
Mr HaRR said:
Hey folks, apologies for the touch and go nature of this thread - i just don't have a lot of free time on my hands and other reasons..
Anyhow, i think I want to try out ur suggestion of flashing an RUU - I noticed that im unable to actually enter recovery after flashing stock recovery from Santod's thread (i flashed the latest three recoveries). I can get to bootloader, but when i select recovery, the phone goes black for a few seconds and then i get the RED TRIANGLE WITH THE EXCLAMATION MARK INSIDE, obviously something's wrong, few seconds later the phone reboots itself into normal mode. I did do a factory reset from bootloader, but issue persists.
So now to the RUU flashing issue - could you suggest one for me to flash?
By the way though, isn't flashing an ruu gonna take me back to stock completely (as in back to S-ON, ETC..)?
Thanks a whole bunch - IM DETERMINED TO GET THIS TO WORK!!!
Click to expand...
Click to collapse
That is in fact stock recovery man. When you get the triangle press volume up and power at the same time. You will enter stock recovery.
Any of my ruu will run fine. You won't lose s-off or unlocked status. You flash them in boot loader fastboot mode.
dottat said:
That is in fact stock recovery man. When you get the triangle press volume up and power at the same time. You will enter stock recovery.
Any of my ruu will run fine. You won't lose s-off or unlocked status. You flash them in boot loader fastboot mode.
Click to expand...
Click to collapse
HA! and now i feel :silly: !!
Bless your soul! i'll give it a go shortly...

Categories

Resources