No service?!?! - Verizon Droid Incredible 2

Downgraded the boot loader to .97 from .98. The phone was downgraded from 2.3.4 to 2.3.3. Tried flashing new ROMs and flashed the latest incredible 2 radio image. The back cover is on the phone but it still says no service. IMSI is unavailable. I'm completely stumped. Help me out!

Euforeik said:
Downgraded the boot loader to .97 from .98. The phone was downgraded from 2.3.4 to 2.3.3. Tried flashing new ROMs and flashed the latest incredible 2 radio image. The back cover is on the phone but it still says no service. IMSI is unavailable. I'm completely stumped. Help me out!
Click to expand...
Click to collapse
Did the MD5 match? Sounds weird.
Hope it works out for you.

tincbtrar said:
Did the MD5 match? Sounds weird.
Hope it works out for you.
Click to expand...
Click to collapse
I ended up fixing it. Had to RUU the original gingerbread on. Turned on roaming. *228 to program then rooted it again. Working fine now.

Same issue
Ive switched to ICS 4.0.4 and everything was fine except the camera wasnt working properly...(Wifes phone) so that was a deal breaker for her and so I went to Cyanogenmod 7.1.0 and now she has no reception. I figured id have to RUU to use *228 but im trying to look around and avoid doing so. If I find a work around then ill come back and post.

Why ruu? Flash a stock based sense Rom like nitsuj stock, andybones, or my sabotage and use *228. No need to ruu for that.
Sent from my ADR6350 using xda premium

Related

Rooting, 3.30, and other problems

Ok. I just got my EVO Tuesday and while I cannot confirm for sure that i had 3.30 to begin with I am pretty sure I did.
Not knowing that the guide i was following to root the device was for an older version I attempted to root, and bricked the phone. I managed to restore the phone using "RUU_SuperSonic_S_Sprint_WWE_3.29.651.5_Radio_2.15.00.09.01_NV_1.77_CNV_release_150224_signed.exe" and I was back to normal....or so i thought
Now the camera/camcorder does not work. I am assuming that my phone was 3.30 and the 3.29.651 I am on now doesnt speak to the camera the same way. It was rumored the 3.30 builds had camera fixes so this makes sense.
Here are my actual questions, with number 1 being the biggest and most important to me at the moment:
1. How do i get back to the 3.30 version the phone came with? IS there a RUU similar to what i used for 3.29 to restore the phone? Where can i get this?
2. If i cant get back to 3.30, is there any way to fix the camera?
3. How can I successfully root 3.29.651? Ive tried every guide i have found here, unrevoked 3, and the one touch rooter programs, but none seem to work. They all fail applying the radio image with FAIL-PU
I appreciate any support and thanks in advance to everyone who can help
94tbird said:
Ok. I just got my EVO Tuesday and while I cannot confirm for sure that i had 3.30 to begin with I am pretty sure I did.
Not knowing that the guide i was following to root the device was for an older version I attempted to root, and bricked the phone. I managed to restore the phone using "RUU_SuperSonic_S_Sprint_WWE_3.29.651.5_Radio_2.15.00.09.01_NV_1.77_CNV_release_150224_signed.exe" and I was back to normal....or so i thought
Now the camera/camcorder does not work. I am assuming that my phone was 3.30 and the 3.29.651 I am on now doesnt speak to the camera the same way. It was rumored the 3.30 builds had camera fixes so this makes sense.
Here are my actual questions, with number 1 being the biggest and most important to me at the moment:
1. How do i get back to the 3.30 version the phone came with? IS there a RUU similar to what i used for 3.29 to restore the phone? Where can i get this?
2. If i cant get back to 3.30, is there any way to fix the camera?
3. How can I successfully root 3.29.651? Ive tried every guide i have found here, unrevoked 3, and the one touch rooter programs, but none seem to work. They all fail applying the radio image with FAIL-PU
I appreciate any support and thanks in advance to everyone who can help
Click to expand...
Click to collapse
Is it a 0004 hardware?? If it is then it came w 3.30 pre installed. Idk how another rom can break the cam i think its the kernel that plays a roll w the cam.. i could be wrongg tho. Try flashing to a 3.30 build rom theres plenty around. I suggest calk rom or go bare bone stock its over by babiboi thread, two versions deodexed and odexed see what u find bro
Sent from my phone.. I think using EViO???
I got my phone yesterday and also had a hell of a time rooting...try the "Sprint Lovers" dated 11/11, its the one that got me through it...gotta place on sdcard and use hboot...wish I could be more helpful but rooting EVO is nothing like a Hero....
jauger said:
I got my phone yesterday and also had a hell of a time rooting...try the "Sprint Lovers" dated 11/11, its the one that got me through it...gotta place on sdcard and use hboot...wish I could be more helpful but rooting EVO is nothing like a Hero....
Click to expand...
Click to collapse
+1 on the sprint lovers rom, totally forgot that i used that rom when i first rooted my phone. Deff go w that one for starters..
Sent from my phone.. I think using EViO???
luckylui said:
Is it a 0004 hardware?? If it is then it came w 3.30 pre installed. Idk how another rom can break the cam i think its the kernel that plays a roll w the cam.. i could be wrongg tho. Try flashing to a 3.30 build rom theres plenty around. I suggest calk rom or go bare bone stock its over by babiboi thread, two versions deodexed and odexed see what u find bro
Sent from my phone.. I think using EViO???
Click to expand...
Click to collapse
Where can I get the 3.30 rom? I need a stock one as I havent been able to root the device to install a custom rom
jauger said:
I got my phone yesterday and also had a hell of a time rooting...try the "Sprint Lovers" dated 11/11, its the one that got me through it...gotta place on sdcard and use hboot...wish I could be more helpful but rooting EVO is nothing like a Hero....
Click to expand...
Click to collapse
luckylui said:
+1 on the sprint lovers rom, totally forgot that i used that rom when i first rooted my phone. Deff go w that one for starters..
Sent from my phone.. I think using EViO???
Click to expand...
Click to collapse
Do you have a link to this rom? Can I install this if i am not rooted? I have not been able to root to get to any custom rom
my hardware version is 0003
when i run unrevoked 3 it says rooting success, but here are the last few lines before it fails:
this was triumph
rebooting
when bootloader starts choose hboot usb ----- never goes to bootloader after this restart goes right to phone
i reboot it manually and choose hboot usb
running pre reboot sequence
waiting for reboot
internal error, couldnt find misc
or this happens
scanned a lot of files fast
rebooting
bootloader starts, choose hboot usb
waiting for hboot to be ready
running preboot sequence
waiting for reboot
running root
waiting for root
this was a triumph,reboots to andriod desktop while program says when bootloader starts choose hboot usb
reboot phone manually
waiting for hboot
communication with phone unexpectantly inturrupted, try again
I just replaced my busted EVO for a new one. Has the new 3.30 in it, hardware is 003. After rooting I lost camera/video due to the PC36IMG I had used while rooting. I installed Myns Warm 2.2 rev3 and got camera/video back, so far that's the only one I can get it on. Just for SnG's I changed out kernels to Kings, and sure enough lost camera and vid. Reflashed 2point2 rev3 with stock HTC kernel and back to working cam. Hopefully this will help. I haven't tried Sprint Lovers yet, but I would imagine it would work the same as Myn's. Any other rom I have run (MIUI _CM6.1) no camera again.
Phiber0p said:
I just replaced my busted EVO for a new one. Has the new 3.30 in it, hardware is 003. After rooting I lost camera/video due to the PC36IMG I had used while rooting. I installed Myns Warm 2.2 rev3 and got camera/video back, so far that's the only one I can get it on. Just for SnG's I changed out kernels to Kings, and sure enough lost camera and vid. Reflashed 2point2 rev3 with stock HTC kernel and back to working cam. Hopefully this will help. I haven't tried Sprint Lovers yet, but I would imagine it would work the same as Myn's. Any other rom I have run (MIUI _CM6.1) no camera again.
Click to expand...
Click to collapse
what method did you use to root it?
94tbird said:
Ok. I just got my EVO Tuesday and while I cannot confirm for sure that i had 3.30 to begin with I am pretty sure I did.
Not knowing that the guide i was following to root the device was for an older version I attempted to root, and bricked the phone. I managed to restore the phone using "RUU_SuperSonic_S_Sprint_WWE_3.29.651.5_Radio_2.15.00.09.01_NV_1.77_CNV_release_150224_signed.exe" and I was back to normal....or so i thought
Now the camera/camcorder does not work. I am assuming that my phone was 3.30 and the 3.29.651 I am on now doesnt speak to the camera the same way. It was rumored the 3.30 builds had camera fixes so this makes sense.
Here are my actual questions, with number 1 being the biggest and most important to me at the moment:
1. How do i get back to the 3.30 version the phone came with? IS there a RUU similar to what i used for 3.29 to restore the phone? Where can i get this?
2. If i cant get back to 3.30, is there any way to fix the camera?
3. How can I successfully root 3.29.651? Ive tried every guide i have found here, unrevoked 3, and the one touch rooter programs, but none seem to work. They all fail applying the radio image with FAIL-PU
I appreciate any support and thanks in advance to everyone who can help
Click to expand...
Click to collapse
Check out the Q&A in this thread http://forum.xda-developers.com/showthread.php?t=829045
This is a known issue regarding your later 0003 and 0004 versions. Follow these steps to root and set your phone up.
CharlyDigital said:
Check out the Q&A in this thread http://forum.xda-developers.com/showthread.php?t=829045
This is a known issue regarding your later 0003 and 0004 versions. Follow these steps to root and set your phone up.
Click to expand...
Click to collapse
some of the best info so far thank you
wrong forum
Rakeesh_j said:
wrong forum
Click to expand...
Click to collapse
correction your the best help ever thanks
Rakeesh_j said:
wrong forum
Click to expand...
Click to collapse
luckylui said:
Is it a 0004 hardware?? If it is then it came w 3.30 pre installed. Idk how another rom can break the cam i think its the kernel that plays a roll w the cam.. i could be wrongg tho. Try flashing to a 3.30 build rom theres plenty around. I suggest calk rom or go bare bone stock its over by babiboi thread, two versions deodexed and odexed see what u find bro
Sent from my phone.. I think using EViO???
Click to expand...
Click to collapse
just an FYI but i flashed the 3.30 rom back and the camera is functional again WOOHOO. now if i can only root it. At least i know i can get back to 3.30 now
still can not root using this method
http://forum.xda-developers.com/showthread.php?t=829045&highlight=fail-pu
it fails on the radio, FAIL-PU
and on the bootloader it says C1 as the error
any suggestions are welcome
thanks in advance
OK. FINALLY got S-OFF. but i am not root, at least as per titanium backup is concerened. What now?
rooted and uploaded a custom rom, sprint lovers. Thanks to everyone

Downgrading to FROYO

Yes, it can be done. There is an RUU floating around, and I just successfully downgraded. That said, while recovery was removed, S-OFF was NOT removed.
What I do not know is how this would affect those who did OTA or the .3 release. I did flash down though from Gingersense.
More to come, as I now have to read about how to get Clockwork Recovery back into place.. That's critical now.
EDIT: Blah.. Just FYI, it doesn't look like the RUU I was using was the stock release. But it's Froyo regardless.
EDIT 2: Big Blah.. If you're S-ON, it won't work. Works fine if you're S-OFF though.
What was the name of the file?
Sent from my ADR6350 using XDA App
RUU_Vivo_W_VERIZON_WWE_1.34.605.3_Radio_0.99.01.0225_2_NV_VZW1.92_release_181303_signed.exe
Looks like 1.34.605.4 is the stock release, but I'm not positive.
And I'm back to where I was before I ran the RUU. Everything appears to work. No issues getting CWM recovery back on.
This may be an option for those who went OTA and want to get root...they just might not have it with OTA.
sk0t said:
And I'm back to where I was before I ran the RUU. Everything appears to work. No issues getting CWM recovery back on.
This may be an option for those who went OTA and want to get root...they just might not have it with OTA.
Click to expand...
Click to collapse
Ill give it a shot seeing that I haven't received my xtc clip yet and pounced on gb leak since alpharev wasn't available yet
Sent from my ADR6350 using XDA Premium App
Stam2000 said:
Ill give it a shot seeing that I haven't received my xtc clip yet and pounced on gb leak since alpharev wasn't available yet
Sent from my ADR6350 using XDA Premium App
Click to expand...
Click to collapse
Please, post your results. I'm curious to hear!
I tried it, and I received an error from the ruu program. Error 190 or something like that.
Sent from my ADR6350 using XDA Premium App
Can you mirror the file, FileFactory is horribly slow. 2 hours? Really?
Does this downgrade HBOOT so you can root the device? I just picked up a new Incredible 2 on Craigslist, 2 days old. Came with Gingerbread installed
shoman24v said:
Does this downgrade HBOOT so you can root the device? I just picked up a new Incredible 2 on Craigslist, 2 days old. Came with Gingerbread installed
Click to expand...
Click to collapse
dunno, just called Verizon and getting a replacement, i hope it doesn't have gingerbread on it - that would be sweet.
Ok. I'm wondering if this will work. My incredible 2 has 2.3.3 with HBOOT of .97. Now AlpharevX works with that HBOOT its just that it can't can't get root because of gingerbread. Would downgrading to froyo fix this? Love this phone. Hate the ****ing bloat.
Sent from my ADR6350 using Tapatalk
It looks like it's an issue of security checking. If you could get it downgrade to Froyo, then it should work. But because of S-ON, it won't downgrade. At least, that's the best I can figure.
So the solution would be to just wait until GB gets S-OFF?
Conrthomas said:
So the solution would be to just wait until GB gets S-OFF?
Click to expand...
Click to collapse
Yes. For whatever reason, despite being signed updates, HTC and/or Verizon won't let you downgrade the device. It worked for me because I was S-OFF already though, so it's a "security" issue.
I also have s-off on mine but after I got it I did factory reset and then it downloaded and installed update while it was charging and i never knew untill i looked and was like o crap it updated by itself so i hope this works.
sk0t i think i could hug you for this post i just ran that ruu and was able to get my root back just installed CM7
sk0t said:
Yes, it can be done. There is an RUU floating around, and I just successfully downgraded. That said, while recovery was removed, S-OFF was NOT removed.
What I do not know is how this would affect those who did OTA or the .3 release. I did flash down though from Gingersense.
More to come, as I now have to read about how to get Clockwork Recovery back into place.. That's critical now.
EDIT: Blah.. Just FYI, it doesn't look like the RUU I was using was the stock release. But it's Froyo regardless.
EDIT 2: Big Blah.. If you're S-ON, it won't work. Works fine if you're S-OFF though.
Click to expand...
Click to collapse
Just made an account to post this...hope it helps. My roommate was fed up with 2.3 on her Droid X so she called verizon to complain and they send her an OTA flash back to 2.2. I know its a different phone but it may be an option for you folks that are looking as well...cheers!
blindy107 said:
Just made an account to post this...hope it helps. My roommate was fed up with 2.3 on her Droid X so she called verizon to complain and they send her an OTA flash back to 2.2. I know its a different phone but it may be an option for you folks that are looking as well...cheers!
Click to expand...
Click to collapse
I have to admit, that is very interesting. I wonder if they'd do it for the HTC phones. I know the X had a ****-ton of problems with 2.3.
sk0t said:
I have to admit, that is very interesting. I wonder if they'd do it for the HTC phones. I know the X had a ****-ton of problems with 2.3.
Click to expand...
Click to collapse
I just got off the phone with big red, and they said with these phones there is not a way to back out an upgrade. If anyone else has any luck, please let us know
chardie26 said:
I also have s-off on mine but after I got it I did factory reset and then it downloaded and installed update while it was charging and i never knew untill i looked and was like o crap it updated by itself so i hope this works.
Click to expand...
Click to collapse
micdawg12 said:
I just got off the phone with big red, and they said with these phones there is not a way to back out an upgrade. If anyone else has any luck, please let us know
Click to expand...
Click to collapse
Damn that really sucks. This is exactly what happened to my sister. I wonder, when did pushing updates with no confirmation become okay? I thought the OTA needs your permission to install?

[Q] Stuck in limbo, need help!

I have posted several stuff about a situation I am having with my phone.... and I still cannot get it solved fully. I hope I can do it here.
I will try and summarize the situation with some key points.
First here is my current info....
Android Version 2.2.1
Baseband Version 2.15.00.03.04
Kernel Version [email protected]#2
Build Number 1.05.970.1 CL339957 release keys
Software number 1.05.970.1
PRI version 2.11_01c
PRL version 01001
Model Number PC36100
Supersonic DVT1 Ship S-ON
HBOOT-6.17.0001
MICROP-041f
TOUCH PANEL-ATMEL224_20aa
RADIO-2.15.00.03.04
Now I first rooted using revolutionary and got s-off properly.... I played with some roms and found it fun but not enough time to keep at it..... so I decided to s-on and go back to stock using un-revoked. That semi worked.... I got s-on.... but never lost the root. I still have recovery and everything still shows I have root except s-on.
Additionally, I tried to run the stock kddi ruu and i have gotten every error from 140, 170, 171 and even at one time 130...lol still no luck there. In doing all of that I figured out that the image version on my phone is 4.24.651.1 and I need to get to 1.05.970.1 (the stock kddi evo 4g) but cannot get it done.
Also I am HBOOT-6.17.0001 which is confusing in itself. xhausx helped me by giving me a nanadroid version of my kddi rom but that doesn't allow me to update anything and finding updates here is impossible unless I am running stock without root.
I am not sure if I need to flash a new misc partition, wipe my nand or something else and so not know how to do all of that..... can someone please please please help? I am willing to toss a small reward your way if we get me back to when I bought it.
I think you need to run the RUU for your phone; get it back to out of the box, stock, and just start over.
HipKat said:
I think you need to run the RUU for your phone; get it back to out of the box, stock, and just start over.
Click to expand...
Click to collapse
didnt you see this in my message????
Additionally, I tried to run the stock kddi ruu and i have gotten every error from 140, 170, 171 and even at one time 130...lol still no luck there.
if you have another RUU that I do not know about please let me know... because the one that I have from kddi is not working.
my current one is.... RUU_SuperSonic_K_KDDI_JP_1.05.970.1_Radio_2.15.00.03.04_NV_2.11_release_176711_signed.exe
You have a Japanese Evo, right?
Since it's a different phone, most of the people here will not be able to help you. I could tell you what to do if you had a American Evo, but it would probably either error out or further your problem.
Is there a forum for your specific version? Do things generally work the same as our Evos... like can you use the same RUU that I would use?
Sent from my Evo + MIUI using Tapatalk!
I was thinking if this will work somthing I might do if everything fails? Maybe you could try rooting it again and unroot?
Sent from my PC36100 using XDA App
plainjane said:
You have a Japanese Evo, right?
Since it's a different phone, most of the people here will not be able to help you. I could tell you what to do if you had a American Evo, but it would probably either error out or further your problem.
Is there a forum for your specific version? Do things generally work the same as our Evos... like can you use the same RUU that I would use?
Sent from my Evo + MIUI using Tapatalk!
Click to expand...
Click to collapse
The fact that I have a Japanese evo doesn't mean that anyone will not be able to help me. This is actually the place where the developers made the first RUU for the Japanese evo to begin with. There are plenty of pro's here.... we just need to find the right solution for me. Additionally, most everything works the same.... I cannot use the same RUU as you because the cid will come up different and cause me more probs.
culua said:
I was thinking if this will work somthing I might do if everything fails? Maybe you could try rooting it again and unroot?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I have tried to run the root process again and it says in revolutionary that you already have s-off..... which in fact I do not.... and when I do the opposite process it just acts like its running the s-on and does nothing.
AgentTabasco said:
I have tried to run the root process again and it says in revolutionary that you already have s-off..... which in fact I do not.... and when I do the opposite process it just acts like its running the s-on and does nothing.
Click to expand...
Click to collapse
Sorry can't help you. I guess just flash stock Rom for now untill you found an answer for problem. Sometime it fix it self? Lol.
Sent from my PC36100 using XDA App
Fixed
I have fixed my phone since I last posted this thread... thanks to all those that helped me solve my issues.

failed updated hosed radio...?

so, i been running cm7.1 for a while. but something, somewhere (i think it was the market) was giving me fc's multiple times a day. fixing permissions would last a second. so, i went back to my stock rom, looking to get that sweet, sweet 2.3.4 ota update.
as many of you know, that ota update, rooted or not, fails for...i don't know...everybody? most people? just us lucky few?
well, i went for it anyways. my phone rebooted, the update starts to install (progress bar goes to about 10%), then it craps out, and i get the yellow bang. a battery pull later, i'm back to my stock 2.2 rom. checking for updates says i'm up to date. NOW, THOUGH...
i cannot connect to bluetooth with any of my roms, and when i walk away from wifi, i don't get emails (maybe tests, too) until i'm back on wifi. so, i figure i need to reflash my radio, which is 2.15.00.07.28.
so, can i flash the latest radio here (2.15.10.07.07)? or, should i stick with a reflashed version of what i've currently got. or, do you think there might be something else wrong, besides the radio?
stupid, horking update...
thx!
shmengie said:
so, i been running cm7.1 for a while. but something, somewhere (i think it was the market) was giving me fc's multiple times a day. fixing permissions would last a second. so, i went back to my stock rom, looking to get that sweet, sweet 2.3.4 ota update.
as many of you know, that ota update, rooted or not, fails for...i don't know...everybody? most people? just us lucky few?
well, i went for it anyways. my phone rebooted, the update starts to install (progress bar goes to about 10%), then it craps out, and i get the yellow bang. a battery pull later, i'm back to my stock 2.2 rom. checking for updates says i'm up to date. NOW, THOUGH...
i cannot connect to bluetooth with any of my roms, and when i walk away from wifi, i don't get emails (maybe tests, too) until i'm back on wifi. so, i figure i need to reflash my radio, which is 2.15.00.07.28.
so, can i flash the latest radio here (2.15.10.07.07)? or, should i stick with a reflashed version of what i've currently got. or, do you think there might be something else wrong, besides the radio?
stupid, horking update...
thx!
Click to expand...
Click to collapse
if you are on the OTA you will need the newer radio. if you did the RUU.exe for the OTA it will install the radio for you but only do this if you do not want root.
if you have root i would hboot the 07.07 radio and flash one of the many OTA based roms in the dev area. or you can go back to CM7 if you like.
thx for the quick reply. i want to make sure i'm clear...
so, no. i am NOT on the ota, as it failed. i did not use the ruu. it really was, actually, over the air. i do have root and would like to keep it. given that, you are saying that it's safe to upgrade my 2.2 stock rom to the 07.07 radio. is that correct?
thx again!
shmengie said:
thx for the quick reply. i want to make sure i'm clear...
so, no. i am NOT on the ota, as it failed. i did not use the ruu. it really was, actually, over the air. i do have root and would like to keep it. given that, you are saying that it's safe to upgrade my 2.2 stock rom to the 07.07 radio. is that correct?
thx again!
Click to expand...
Click to collapse
yes the 07.07 radio will work on froyo but gingerbread doesnot work well on the lower radios to my knowledge.
before updated the radio please make sure the md5 sums match. if the zip is corrupt in any way it WILL brick the phone.
please follow this thread on how to do it. LINK
to make sure the md5 match you can use an app called Astro file manager. its free in market.
(i know the thread says there is an 08.08 radio, this is leaked radio and should only be used if you feel comfortable on what you are doing)
thx guys. i reflashed my 07.28 radio and everything is hunky dory!
07.07...i got my eye on you...
shmengie said:
thx guys. i reflashed my 07.28 radio and everything is hunky dory!
07.07...i got my eye on you...
Click to expand...
Click to collapse
Sweet. Glad you got it working.
Sent from my sexy assistant. (AMOLED HTC Incredible)

[Q] Dinc2 reboots on lockscreen after s-off

I have a fairly strange problem. My wife got tired of the Verizon bloatware on her Dinc2 so I offered to root and flash it to a nice rom. Her only requirements were that it work both as a phone and as a camera. After an uneventful downgrade, s-off, root and CWM, we tried aeroevan's unofficial CM9. We found that the camcorder was broken. Next we tried the MikRoms Incredible 2 HD Rls1. This worked beautifully in every respect except one: when I rebooted the phone, it went into a loop. The phone would boot to the opening lock screen.. in some cases I could even unlock it.. and then either turn off or reboot (which one seemed random). After getting back into the bootloader, I tried all the obvious things:
Wiping all partitions
Reloading the ROM
Trying a different ROM
Flashing back to a Stock ROM + root
Flashing back to stock 2.3.3.
In every case, the phone works perfectly with the new ROM up until it is rebooted, after which it goes into a loop at the lockscreen. The only ROM that DOES work is aeroevan's unofficial CM9. It reboots without any issues, but of course the camcorder and camera flash are busted there. At least it's usable as a phone again.
I've looked and looked, and either my google-fu is failing me utterly or this is a fairly unusual problem. Does anyone have the faintest idea what's going on here and how I can work at fixing it?
This is a well known issue with 605.05 software phones (and several other threads already about this). There is a PSA in Development warning this issue exists. Only guaranteed ROMs without issue are AOSP ROMs. If you want working camera, flash CM7.
I have also heard that flashing the radio packaged with the latest software may fix the issue, you can give that a try. You could also try flashing Condemned Soul's 6.xx ROM in development section.
Sent from my ADR6425LVW using Tapatalk 2
Yah, right after I posted this I saw this:
http://forum.xda-developers.com/showthread.php?t=1746490
Sorry about that. Thanks for the info!
I can confirm that flashing the radio to version 1.09.01.0312 as detailed here resolved the reboot-at-locksceen issue. Using the Incredible 2 HD Rls 1.1 ROM, we now have a working phone, a working camera, and a happy wife!
Thanks!
Verteiron said:
I can confirm that flashing the radio to version 1.09.01.0312 as detailed here resolved the reboot-at-locksceen issue. Using the Incredible 2 HD Rls 1.1 ROM, we now have a working phone, a working camera, and a happy wife!
Thanks!
Click to expand...
Click to collapse
I bet the biggest plus is the happy wife part huh?
Sent from my Incredible 2 using xda app-developers app
Verteiron said:
I can confirm that flashing the radio to version 1.09.01.0312 as detailed here resolved the reboot-at-locksceen issue. Using the Incredible 2 HD Rls 1.1 ROM, we now have a working phone, a working camera, and a happy wife!
Thanks!
Click to expand...
Click to collapse
Glad flashing the new radio got it sorted out!
fsiddique said:
Glad flashing the new radio got it sorted out!
Click to expand...
Click to collapse
Perhaps you can help me sort out an issue. I tried rooting and getting S-Off by using the tacoroot, and flashing a new radio method. I got to the radio part, and got the radio onto the root of the sdcard as per the instructions. The phone boots into fastboot, and it checks the radio file, but it says incorrect file a few times, and then returns to the fast boot menu. I didn't know if it worked, or not so i tried to reboot the phone normally but at the lock screen it reboots.
I tried pushing the radio file using adb but it doesnt seem to want to connect to the phone anymore.
I followed these instructions http://forum.xda-developers.com/showthread.php?t=1751796
After going through some fastboot options I flashed the recovery from fastboot and it booted up and stayed booted, i'm assuming i have to start over, which I don't care about, I just need some advice about what is up with the radio not wanting to flash.
wexx2504 said:
Perhaps you can help me sort out an issue. I tried rooting and getting S-Off by using the tacoroot, and flashing a new radio method. I got to the radio part, and got the radio onto the root of the sdcard as per the instructions. The phone boots into fastboot, and it checks the radio file, but it says incorrect file a few times, and then returns to the fast boot menu. I didn't know if it worked, or not so i tried to reboot the phone normally but at the lock screen it reboots.
I tried pushing the radio file using adb but it doesnt seem to want to connect to the phone anymore.
I followed these instructions http://forum.xda-developers.com/showthread.php?t=1751796
After going through some fastboot options I flashed the recovery from fastboot and it booted up and stayed booted, i'm assuming i have to start over, which I don't care about, I just need some advice about what is up with the radio not wanting to flash.
Click to expand...
Click to collapse
Check the md5sum, might be a bad download. You won't need to start over if you're S-OFF already, you can always flash an AOSP ROM to get it working and go from there.
prototype7 said:
Check the md5sum, might be a bad download. You won't need to start over if you're S-OFF already, you can always flash an AOSP ROM to get it working and go from there.
Click to expand...
Click to collapse
Thanks for the quick reply!
I don't know how to check the md5 without adb. Can I do that without communication to the phone.
How can I determine if I'm S-OFF, or flash a rom? For that matter, how do i start over if i need to.
wexx2504 said:
Thanks for the quick reply!
I don't know how to check the md5 without adb. Can I do that without communication to the phone.
How can I determine if I'm S-OFF, or flash a rom? For that matter, how do i start over if i need to.
Click to expand...
Click to collapse
You can check the md5sum from the phone, just use terminal emulator (might need busybox installed). To check if you are S-OFF, boot into the bootloader and it should say S-OFF.
Sent from my Incredible 2 using Tapatalk 2
I've noticed that I can use fastboot commands, (sorry, never had this complex of a root job before. Normally they are one-clicks) Anyway, I look at the top of the screen when its sitting in the fastboot screen and it says VIVO_W XB Ship S-ON RL I assume that means I'm not S-OFF, and its back to square one. Right?
wexx2504 said:
I've noticed that I can use fastboot commands, (sorry, never had this complex of a root job before. Normally they are one-clicks) Anyway, I look at the top of the screen when its sitting in the fastboot screen and it says VIVO_W XB Ship S-ON RL I assume that means I'm not S-OFF, and its back to square one. Right?
Click to expand...
Click to collapse
Yep. What's the hboot version?
Sent from my Incredible 2 using Tapatalk 2
prototype7 said:
Yep. What's the hboot version?
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
HBOOT 0.98.0000
in case you want this info too.
Radio - 1.09.01.1111
I tried going back to stock using the following guide http://forum.xda-developers.com/showthread.php?t=1599767
now i have ***LOCKED*** when i boot into fastboot,and i still have the crazy reboot issue when the phone displays the lock screen.
wexx2504 said:
HBOOT 0.98.0000
in case you want this info too.
Radio - 1.09.01.1111
I tried going back to stock using the following guide http://forum.xda-developers.com/showthread.php?t=1599767
now i have ***LOCKED*** when i boot into fastboot,and i still have the crazy reboot issue when the phone displays the lock screen.
Click to expand...
Click to collapse
\
I am at this exact same radio, firmware version, hboot version and situation too any help would be greatly appreciated. Trying to help a co-worker fix his wife's device.

Categories

Resources