Hey Guys,
Ok here is my problem. I have a droid incredible 2 flashed to straight talk That is not the issue also it is rooted and rommed with
skyraider 1.3 that works fine it is no problems there the problem i am having is trying to get s off I have read and read and tried
going through the comprehensive s-off downgrade tutorial. I do have some skills in linux i got adb to work no problems
howeveri got the phone to go to 205.618.03 but when i go to flash the ru it gives me an error parsing zip and whamo quits.
the phone is unlocked s on i have tried for 2 days now stayed with it till 3 in the morning.. the phone works but i want to be able
to flash radios as i am on 312 and would like to upgrade the radio. has anyone had this problem or is it just my phone I have no problems following instructions and i know this is a dated phone but i like it and i want to be able to upgrade the radio any kind of assistance would be greatly appreciated.. I thank you for listening to me whine, and i do appreciate any assistance given
thank you
Mondo
Related
UPDATE (10/19 @ 12:10AM EST): After some searching and messing around I found that having WiFi enabled in CM 7.1.0 causes signal issues and causes the inability to place calls or texts. http://forum.cyanogenmod.com/topic/33935-signal-never-comes-back/page__pid__253023#entry253023
I believe that has solved my problem and I am no longer in need of help. Thank you for any of those that read this.
Today I finally decided to root my Android HTC Droid Incredible 2 for the first time. This is my first time rooting a phone. I did much research before doing so and research any possible ROMs I would be interested in.
I first had to begin by downgrading my HBOOT from 0.98.0000 to 0.97.0000 so that I could use Revolutionary and I followed this guide here: http://forum.xda-developers.com/showthread.php?t=1298990
Next, I began the rooting process by using this guide at the CM7 Wiki: http://wiki.cyanogenmod.com/wiki/HTC_Incredible_2:_Full_Update_Guide and also this guide: http://forum.xda-developers.com/showthread.php?t=1219246
I then returned to the CM7 guide and flashed CyanogenMod 7 onto my phone as well as, the provide GApps.
The phone reinstalled all of the apps that I had previously had before I rooted and change my ROM. I was able to receive one text message and make one phone call before I noticed that I was unable to make anymore phone calls. I tried activating/programming the phone through Verizon's service, but it says that it is unable to each time.
I went to the #cyanogenmod IRC chat room on Freenode and spoke with several users who asked if I flashed Radio. I did not and found this guide here: http://forum.xda-developers.com/showthread.php?t=1134451 and downloaded 1.09.01.0722 Radio and flashed it following the instructions provided. Which updated my radio from .0622 to .0722.
I am still unable to make any phone calls out or take any phone calls in, as the same for text messages. Any assistance, advice, or help would be greatly appreciated.
- Joseph W
my Incredible 2 had been running the Magnolia Beta for the past few months with no issues, until this weekend. It suddenly started to download an update from verizon, but since my phone was obviously rooted this ended badly. In short i was forced to roll back to froyo (2.2.1) but could not manage to change s-off back, so i cannot upgrade back to gingerbread. anybody that can help me out here would be greatly appreciated. at this point i would just be happy to be able to run the most current firmware.
Thanks
lukester78 said:
my Incredible 2 had been running the Magnolia Beta for the past few months with no issues, until this weekend. It suddenly started to download an update from verizon, but since my phone was obviously rooted this ended badly. In short i was forced to roll back to froyo (2.2.1) but could not manage to change s-off back, so i cannot upgrade back to gingerbread. anybody that can help me out here would be greatly appreciated. at this point i would just be happy to be able to run the most current firmware.
Thanks
Click to expand...
Click to collapse
What all have you tried?
Have you tried to flash the 2.3.3 RUU through HBOOT?
Can you root your 2.2.1 if so then you can just flash custom rom again and update kernel.
I've tried the RUU, but that hasnt been working, adb wont recognize my phone, no matter the settings. Could I load the RUU through the phone without adb?
I havent been able to find any tool to root 2.2.1, because Revolutionary was updated to only Gingerbread.
EDIT: Just loaded the 2.3.3 RUU, which actually worked. Can i just root with revolutionary now? Or should i take other steps before that?
Just root with revolutionary and get to flashing.
Sent from my Incredible 2 using xda premium
Hi all, I received a Droid Incredible 2 from a friend who said he ruined it trying to downgrade from 2.3.4. It continuously reboots upon startup. I don't know any other details for what he did to screw up the phone.
So first thing I try to do is return to stock using this link:
http://forum.xda-developers.com/showthread.php?t=1599767
This works fine, I am able to run PG32IMG.zip from bootloader and the phone is able to boot up. However, once I restart the phone, it reboots immediately after it starts up again.
I read around a bit, apparently this can happen when the radio is outdated.
Phone is 2.3.4, Hboot 0.98.0000, radio is 1.09.01.1111, S-ON
So I try to flash the newest radio from this thread:
http://forum.xda-developers.com/showthread.php?t=1134451
The radio I'm trying to flash is 1.09.01.0312.
So I rename the radio PG32IMG.zip and restart to bootloader. The phone checks PG32IMG.zip, but it won't run the update!
So I read around some more, apparently you can try to flash the radio manually using a command prompt. I open the prompt and type in
Code:
fastboot erase cache
fastboot flash zip PG32IMG.zip
Here is where I get an error,
Code:
Failed (remote signarure verify failed)
Not sure what to do next, can anyone point me in the right direction? I am currently using a Droid 2, and an Incredible 2 would be a nice upgrade if I can get it working!
To flash the radio needs to b s off.
Sent from my forgotten by HTC Droid Incredible 2. Kept alivw by great minds at XDA that haven't forget this phone.
Thanks!
So based on this guide:
http://forum.xda-developers.com/showthread.php?t=1751796
I use the downgrade tool to get to GB 2.3.3 and Hboot 0.97, and then run revolutionary to S-OFF. I'm on firmware below 6.01.605.05 (5.something i don't remember off the top of my head)
So I guess what I will have to do is reflash back to stock so the phone can be on without continuously rebooting. Then run the downgrade tool.
Does that sound about right?
Sounds about right. I've been S off for the longest time so people facing these new problems that arise I really can't say. I know once you gain S off is the only way to update the radio.
Sent from my forgotten by HTC Droid Incredible 2. Kept alive by great minds at XDA that haven't forget this phone.
FordNate said:
Sounds about right. I've been S off for the longest time so people facing these new problems that arise I really can't say. I know once you gain S off is the only way to update the radio.
Sent from my forgotten by HTC Droid Incredible 2. Kept alive by great minds at XDA that haven't forget this phone.
Click to expand...
Click to collapse
Thanks! I followed the steps I said above, worked great! Phone is now S-OFF and boots normally in 2.3.3, and has clockwork mod installed.
Incrediblec XD ship S-On
Hboot-0.92.0000
microp-0417
touch panel-atmelc03_16ac
Radio-2.15.10.07.07
Jul 23 2010, 18:06:51
Hello, first thank you for an amazing and current forum, I'd been researching my issue for a while, but most things are dated around 2010. I've experience rooting and ROMing a Droid X with multiple ROMS, but I use the original Incredible as my main phone because I still love it. Well, I originally rooted my Inc with Unrevoked3 I believe. I left the ROM as stock up until a couple months ago when I put CM7.2.0 on it.
About a week ago, the phone would always have working mobile data. Yet, if I received or tried to make a call, I couldn't and then I would lose texting ability. Then, a couple days ago, I was using the Inc for wifi tethering when suddenly it went into an Incredible bootloop. I tried booting to the cyanogen recovery, but it will quickly loop out of it as well.
I went to pvillecomp.com/ and downloaded all the stock Inc software. I individually renamed files to PB31IMG.zip and tried to have HBoot pick up on them. Hboot will see the files, but then do nothing. Except, the originally ROM will get checked and come back and say that the current version is older and can't be flashed.
I've always tried the RUU software for hboot and the original ROM. I either get a usb error or a low battery error even if the battery is charged. Granted, I'm trying the RUU from the phone's bootloader screen.
Does anyone have some support they could throw this way? I use my phone for internet and everything. Thank you all.
-Nevin
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
NevinInc said:
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
Click to expand...
Click to collapse
did you flash any radios? Flashing radios always ends up bad.
NevinInc said:
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
Click to expand...
Click to collapse
S-off, flash TWRP (because CWM sucks) and flash a new rom. This should fix everything. Flashing a radio DOES not screw everything unless you do not know what to flash, in that case you should not be flashing radios.
I'm looking into the TWRP stuff right now since I've only experience with CWM. My only concern is that I still have S-on. How can I get S-off on my phone when I've only access to the bootloader? Sorry if this is a bit off a noob post, I've simply not the experience with the incredible to know. Thank you so much.
-Nevin
123421342 said:
S-off, flash TWRP (because CWM sucks) and flash a new rom. This should fix everything. Flashing a radio DOES not screw everything unless you do not know what to flash, in that case you should not be flashing radios.
Click to expand...
Click to collapse
Btw, no I didn't flash the radio. That was the only thing I didn't attempt to flash. Yet, when attempting to flash anything else, nothing worked. Still wondering about getting S-off before using TWRP, but hopeful to still get it working. Thank you again.
NevinInc said:
I'm looking into the TWRP stuff right now since I've only experience with CWM. My only concern is that I still have S-on. How can I get S-off on my phone when I've only access to the bootloader? Sorry if this is a bit off a noob post, I've simply not the experience with the incredible to know. Thank you so much.
-Nevin
Click to expand...
Click to collapse
BUMP/UPDATE:
Yes, I'm still at it trying to get my Dinc out of it's bootloop and up/running. It's difficult at this point to say what all I've tried. At one point I wanted to use htcdev.com to ensure the bootloader was unlocked/etc. I've had much trouble trying to get fastboot to work correctly on my pc. I've seem to get stuck on "waiting for device" which appears to be a driver error.
I gave up on that and started focusing on the RUU process. I've tried to install the entire Gingerbread 605.3 file. I fixed the error usb 170 by updated or changing htc sync software. Now I'm left with error 140 bootloader error.
I've also updated hboot using the ruu process for version 605.2. This worked on my pc and got me partially excited. Now my hboot shows up as "Locked" now at the top. I also downloaded a different Stock.img file. Hboot detected this and begun the install process. Everything came up as complete and upon reboot went right back into the white screen/incredible bootloop.
So since posting before I've updated htc sync on my pc and have officially relocked my bootloader. I don't mind RUU'ing things to stock, but now gotta get past the Error 140. Any ideas?
So I'm not sure how many are looking at this or have had ideas, but I was able to use htcdev to unlock the bootloader.
Before unlocking the bootloader I was able to RUU to image .15. After this is when I unlocked the booloader. The RUU said it was complete, but I still only bootloop on the incredible white screen. Now, some of the pb31img.zip files I've come across don't even try to install. This includes signed and unsigned .15 img files. Currently these are the new settings to the phone:
Bootloader: unlocked, s-on
hboot 1.07.0000
radio - 2.15.10.12.20
Image version: 4.08.605.15
The last option I can think of is to try using fastboot, but won't that essentially do the same thing? If you think fastboot is the way to go, can u link me or give me some basics on using it. Obviously I used it for unlocking the bootloader so it can't be that complicated.
Are there any other ideas or should I give up on my Dinc? Looking forward to hear what you think. Thanx.
-Nevin
somebody recommended you install TWRP and install a stable Jellybean ROM. Did you try that?
I have always used Viper ROM and I upgraded to 2.01 once it came it. Fooshily, I did not upgrade the firmware (noob, not a newb) because I couldn't figure it out. I finally got it downgraded to stock, then did the OTA to upgrade the firmware. The phone started flawlessly until I flashed Viper 2.01. I (luckily) backed it up before this time and tried flashing Android Revolution. I still had long boot times. I understand most of this stuff, but I always seem to run into problems. Any ideas on how to fix this?
Tampered
Unlocked
S-ON (couldn't get this)
AT&T
Early model, possibly release
I'm at work now but I could post more info later. Thank you, everyone.
Also, I would prefer to use Viper, if that matters.