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.
Related
hey everyone. I am a bit confused, and i would greatly appreciate your help. So I have a Desire Z from bell. Currently this is what I see when i hold vol down, and power:
Vision PVT SHIP S-ON
H-Boot- 0.81.0000
Microp- 0425
eMMc- boot
Sep 2 2010.17:59:38
So I want to get it back to stock. simply just like out of the box. I do have a back up, BUT it still keeps clock work mod recovery. Which I want to get rid of too. like I said JUST LIKE OUT OF THE BOX. So i was doing some research, and I found that a way to do that is to flash to spf file. I dont really know what that is, but I am assuming it a complete stock rom? (correct me, thank you.) So If any of you could provide me with that file, or tell me how to go about doing this, I would be very very thankful. Again, Thank you for all your help.
HeatRyder said:
hey everyone. I am a bit confused, and i would greatly appreciate your help. So I have a Desire Z from bell. Currently this is what I see when i hold vol down, and power:
Vision PVT SHIP S-ON
H-Boot- 0.81.0000
Microp- 0425
eMMc- boot
Sep 2 2010.17:59:38
So I want to get it back to stock. simply just like out of the box. I do have a back up, BUT it still keeps clock work mod recovery. Which I want to get rid of too. like I said JUST LIKE OUT OF THE BOX. So i was doing some research, and I found that a way to do that is to flash to spf file. I dont really know what that is, but I am assuming it a complete stock rom? (correct me, thank you.) So If any of you could provide me with that file, or tell me how to go about doing this, I would be very very thankful. Again, Thank you for all your help.
Click to expand...
Click to collapse
Hmm not sure what that spf method is. Simply find the thread with all pc10img.zips in it, and find your stock rom. Flash in the bootloader and your good to go!
Sent from my HTC Vision using XDA Premium App
xsteven77x said:
Hmm not sure what that spf method is. Simply find the thread with all pc10img.zips in it, and find your stock rom. Flash in the bootloader and your good to go!
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
omg thank you. that makes sense. the only thing is how do I find the right one?
This is what I see in my software information:
Android Version: 2.2
Baseband Version: 12.22.60.09bU_26.02.01.15_M2
Kernel Version: 2.6.32.21
Build number: 1.34.666.5
Software number:1.34.666.5
Btw doing this will get rid of clockwork mod too right? THANK YOU!!!!
Do you have a g2 buddy? Or is it a desire? If it's g2 i can definitely help ya Edit: LOL nevermind i see that its a desire z. Go to this page....
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#ROMs
Hopefully that at least gets ya in the right direction cause i dont know much about desire z
If your phone has been updated with an ota, it might not be so easy to install a pc10img unless the pc10img IS the ota update. The phone not being rooted and s-on will not let you "downgrade" versions. There may be an easier way, but if you can't simply flash a pc10img, you may have to actually go through all the steps to root/s-off it, THEN you can install the original pc10img.
Hopefully someone with more knowledge with me will just know how to flash the stock recovery if nothing else for you. Here's hoping!
xsteven77x said:
If your phone has been updated with an ota, it might not be so easy to install a pc10img unless the pc10img IS the ota update. The phone not being rooted and s-on will not let you "downgrade" versions. There may be an easier way, but if you can't simply flash a pc10img, you may have to actually go through all the steps to root/s-off it, THEN you can install the original pc10img.
Hopefully someone with more knowledge with me will just know how to flash the stock recovery if nothing else for you. Here's hoping!
Click to expand...
Click to collapse
k so right now i am just gonna s-off. then i will try the pc10img again. hopefully it will work, and i will be back to how it was out of the box. without clockwork and root and etc.Thank you so far.
Your welcome. Even after you flash the pc10img it will still be s-off. Just follow the directions that wiki page i gave you to put s back on. It will involve getting temp root on your new stock rom, and having gfree put s back on. Dont worry, it cleans up and does not leave ANY trace that you did the temp root (if you have to send it back or something). Let me know how it goes! I'm watching this in case you need help.
xsteven77x said:
Your welcome. Even after you flash the pc10img it will still be s-off. Just follow the directions that wiki page i gave you to put s back on. It will involve getting temp root on your new stock rom, and having gfree put s back on. Dont worry, it cleans up and does not leave ANY trace that you did the temp root (if you have to send it back or something). Let me know how it goes! I'm watching this in case you need help.
Click to expand...
Click to collapse
okay so far i have turned s-off. it was a bit of a process but i did it. now i need the pc10img. i am having trouble finding the right one. i looked at the forum u gave me, but i still dont understand which one i should use. btw i have my desire z with bell. i also gave some information above. so what do u suggest?
you would want your hboot to say s on instead of s-off if you are returning to stock
Sent from my PC36100 using Tapatalk
im0rtalz said:
you would want your hboot to say s on instead of s-off if you are returning to stock
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
You even confused me with that one. If he was s-on and that start of all of this, the hboot s-stuff has nothing to do with it. Even if it did, installing the pc10img will replace the hboot with the correct one. He used gfree (i think) to get s-off.
I'm sorry OP if i had a desire i would be able to give u the right version to install If you look in the main dev forum i'm sure there is a topic called return desire to stock, and find the pc10img that they recommend. That would be my next suggestion since i really dont know about that phone
xsteven77x said:
You even confused me with that one. If he was s-on and that start of all of this, the hboot s-stuff has nothing to do with it. Even if it did, installing the pc10img will replace the hboot with the correct one. He used gfree (i think) to get s-off.
I'm sorry OP if i had a desire i would be able to give u the right version to install If you look in the main dev forum i'm sure there is a topic called return desire to stock, and find the pc10img that they recommend. That would be my next suggestion since i really dont know about that phone
Click to expand...
Click to collapse
I searched a lot. i think my brain is going to explode. I just cant find the right RUU. i tried a couple and they all turn in to error [158] image error. I am so confused at this moment.
I tried RUU_Vision_BellMobility_WWE_1.34.666.1_Radio_12.28b.60.140e_26.03.02.18_M2_release_154437_signed.exe which should work. but it still says error 158. i dont know how to get through this.
okay so i am unrooting now. BUT another roadblock. hboot wont install pc10img it says parsing then returns to the main menu of hboot. i have double checked everything, the image is legit, and the name is fine. when i try to install it through clockwork it says error (bad). i am confused. i will appreciate any help. if u need the firmware info and all, please look at the first few posts.
I have hw 003 hboot 2.10. I can enter hboot but not recovery. during normal boot phone just shows evo boot screen and boot loops. same thing when I try to enter recovery. I was s-off but after trying some methods in other brick threads I ended up with s-on.
I was using miui 2.2.3 when I turned it rebooted into recovery to make a nand and that is when the loops started. I have tried several ruu's with no luck on getting it to boot. was going to try the lastest ruu but not sure if I should.
I am flashed for cricket so there is not the option of bricking and returning to sprint for a replacement.
Edit: was not using twrp. Ar 2.3 was my recovery. As stated earlier I tried several ruu's in pc36img.zip.
If you can get to hboot you are not bricked. Have you tried using a pc36img of a stock rom in the hboot? This should boot you to a stock rom, thus allowing you to re-root and get your recovery back.
sitlet said:
If you can get to hboot you are not bricked. Have you tried using a pc36img of a stock rom in the hboot? This should boot you to a stock rom, thus allowing you to re-root and get your recovery back.
Click to expand...
Click to collapse
You can be bricked and still get in hboot Twrp2.0 did it to a few phones, the partitions end up screwed up and you can boot to hboot but no recovery or system not sure which partition gets borked but I think its the misc partition
We are legion, for we are many
Where is Captain_Throwback to save the day and another evo once again
Oh I am sure Captain will save the day soon as he always does.
That does not sound like fun man, sometimes the evos get crazy and there is nothing you can do about it. Did you do anything different before you had this issue? flash any files, adjust any system settings or mess with the hardware in anyway?
stevovanburen said:
Oh I am sure Captain will save the day soon as he always does.
That does not sound like fun man, sometimes the evos get crazy and there is nothing you can do about it. Did you do anything different before you had this issue? flash any files, adjust any system settings or mess with the hardware in anyway?
Click to expand...
Click to collapse
No i had been running miui for a few days and was getting prepared for the next update by doing a nand. I rebooted to recovery with the reboot option in the rom. Then bang boot loop city here i am. Just tried the newest ruu pc36img.zip and still nothing. Going to get it unlocked later and see if I can reflash .img files through fastboot.
Sent from my M865 using XDA App
You weren't using twrp2.0 were u? If you were more than likely SOL that's one of the main reasons twrp for the evo is no longer supported even tho it works great on other devices like the kindle fire and 3vo I use it on the KF which I have running cm9 which I just got running on the evo as well now I gotta get my kernel fixed for this thing, have you tried reflashing your recovery? Or using adb to push a boot.img
Sent from my PC36100 using xda premium
evo4gnoob said:
Where is Captain_Throwback to save the day and another evo once again
Click to expand...
Click to collapse
I know. Captain has become the shaman of the Evo. He needs a special title, like Honorary Genius, or something.
sent from AOKP heaven
You guys flatter me .
I don't have any experience with MIUI, though. It's the one ROM I've never tried, but if it's an AOSP ROM, then the bootloop of death is always a possibility.
We haven't had any success rescuing anyone in that scenario, unfortunately. Flashing the ENG HBOOT will allow you to run fastboot commands, though, so that's probably the first step if you want to flash stuff through fastboot.
If you can't get adb working, then there probably isn't much hope. Since you ended up S-ON, and now without a custom recovery, I don't think there's much you can do. Perhaps others with a similar issue can chime in, but as far as I know, there's no current solution. The only way I'd know for sure is having the phone in my hands personally, but I doubt that's a possibility. I haven't personally experienced this bootloop thing, but it sounds scary .
jlmancuso said:
No i had been running miui for a few days and was getting prepared for the next update by doing a nand. I rebooted to recovery with the reboot option in the rom. Then bang boot loop city here i am. Just tried the newest ruu pc36img.zip and still nothing. Going to get it unlocked later and see if I can reflash .img files through fastboot.
Sent from my M865 using XDA App
Click to expand...
Click to collapse
Ok so I have unlocked the bootloader from the htcdevelopers site and i can now use fastboot commands and have tried flashing the recovery. I see it load and write to the phone only thing is that it makes no difference. I still just get the boot loop.
Hate to say it, my friend, but I think it's the end of the road for that phone
HipKat said:
Hate to say it, my friend, but I think it's the end of the road for that phone
Click to expand...
Click to collapse
maybe but i will keep trying till the phone catches fire in my hands. I dont know the meaning of "quit". I read last night in a xda thread about a possible fix by this guy and some people said it would just brick the phone and others say it works. only thing is i have been unable to find that thread again. it had a link to some evo.docx file.
jlmancuso said:
maybe but i will keep trying till the phone catches fire in my hands. I dont know the meaning of "quit". I read last night in a xda thread about a possible fix by this guy and some people said it would just brick the phone and others say it works. only thing is i have been unable to find that thread again. it had a link to some evo.docx file.
Click to expand...
Click to collapse
I assume you're referring to this thread: http://forum.xda-developers.com/showthread.php?t=1480630
Have fun trying! Many have tried, and I think only 1 ever succeeded.
thanks captain.
capn, thanks for the link! I've had that README_EVO.docx file on my SD for god-knows-how-long and have always wondered where in the hell I got it lol (and 'why').
@jlmancuso
Good luck, but condolences as well. My $ says, if Cap'n can't fix it, it likely can't be fixed (on Evo). Seems that guy has explored every RUU, Hboot, recovery, NV, Radio, kernel etc. He could probably BUILD an Evo, HW and SW lol.
sent from AOKP heaven
Captain throwback just the person i want to see lol i have a evo with 2.18 hboot
with s-on the phone keeps boot looping wrote the wrong nv to the phone now its boot looping also used the latest ruu top no avail still boot loops now is there a way i can repair the nv please help me with your guiding light and also this phone is not rooted or no roms its all stock also says in purple at the top ***LOCKED (00w) *** what ever that means ??
fatalfury said:
Captain throwback just the person i want to see lol i have a evo with 2.18 hboot
with s-on the phone keeps boot looping wrote the wrong nv to the phone now its boot looping also used the latest ruu top no avail still boot loops now is there a way i can repair the nv please help me with your guiding light and also this phone is not rooted or no roms its all stock also says in purple at the top ***LOCKED (00w) *** what ever that means ??
Click to expand...
Click to collapse
I think someone else was able to fix this problem . . . there's a thread around here somewhere. I'll try and find it.
EDIT: This is the thread - you'll probably want to read the whole thing, and if you have issues, maybe you can PM the guy that got it working.
The potential problem I see for you is that you're S-ON and bootloader is locked. You're probably going to have to unlock your device with HTCDev.com before you can make any headway. How were you able to write NV items to the phone? Don't you have to be S-OFF to do that?
Captain_Throwback said:
I think someone else was able to fix this problem . . . there's a thread around here somewhere. I'll try and find it.
Click to expand...
Click to collapse
i remember you had them downgrade to the ENG hboot and they were able to use fastboot to change the NV ?
evo4gnoob said:
i remember you had them downgrade to the ENG hboot and they were able to use fastboot to change the NV ?
Click to expand...
Click to collapse
Yup. I updated my post above with the thread, but that guy was S-OFF, so it was actually possible. Not much you can do with S-ON and locked bootloader.
Captain_Throwback said:
Yup. I updated my post above with the thread, but that guy was S-OFF, so it was actually possible. Not much you can do with S-ON and locked bootloader.
Click to expand...
Click to collapse
use HTC dev to unlock then use your guide to downgrade then root with revolutionary then downgrade hboot ?
i thought I saw it somewhere that "Captain" was going to upload a PC36IMG for this specific version of ROM, but I now can't find it.
The reason I want to use it is because my phone currently has the 4.67 software and 2.18 HBoot. Every time I try to flash an older version, it gives me the "main version older" error. Plus, my phone's USB port is not working with diag mode on (although still charges). So PC36IMG seem to be my only chance. Please advise where to get it or if I am wrong with my understanding. Thanks!
are you trying to root you evo with hboot 2.18 ?
i am some what lost...forgive me if i am wrong about anything. do you need the pc36img for 4.67 and 3.18 hboot ?
Sorry. Not really. I bought this evo 4g from cl and it turned out to be flashed to cricket. I want to flash it back to sprint so I can use it. I've read a lot and tried a lot but nothing helps. It looks like my problem is that:
1) it is now unrooted, so I don't have access to terminal so fastboot is not an option
2) it has a bad USB. I don't know if it is the hardware, or because of the previous flash
So my only chance is to load the PC36IMG to SD card and flash it from there. For some reason, whenever I do it, it loads it, checks it and goes back to bootload. This happens to all PC36IMGs I tried (maybe 6-7 of them) EXCEPT the following one:
PC36IMG_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2 .15.00.11.19_NV_1.90_release_161482_signed.zip
However, this one does not work either. After it checks it, it gives the error that "MAIN VERSION IS OLDER"
I thought if I can find a newer version than what I have (4.67) I may have a chance. I found that the one in my title is newer. But it looks like it is not a PC36IMG.zip file (how do I tell BTW? It just failed on me).
I searched and found other solutions like downgrading, but all required USB port which I don't have. So is there anyway I can still revive this?
This is my info on top of phone.
SUPERSONIC EVT3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
Radio-2.15.00.12.19
Dec 21 2011, 12:50:32
XenonV said:
are you trying to root you evo with hboot 2.18 ?
i am some what lost...forgive me if i am wrong about anything. do you need the pc36img for 4.67 and 3.18 hboot ?
Click to expand...
Click to collapse
well you need USB to be able to flash the phone, + you wont be able to do anything unless its rooted :/
But question:
1) I was wondering if the USB problem I am having is due to the earlier flash (I read about some ROMs leads to bad USB). If I install a stock ROM (newest) with my microUSB, I may have my USB back. Is that correct? Do you think it might work? It still charges, just not recognized data-wise.
2)Am I correct that I can copy the newer version of software (like the one in the title) as a PC36IMG.zip to my microSD card, and have the phone load into bootloader and recover that way?
Thanks!
XenonV said:
well you need USB to be able to flash the phone, + you wont be able to do anything unless its rooted :/
Click to expand...
Click to collapse
Yes, roms can cause hardware issues, well not only roms, but kernels, and more. And for your second question I can't say no or yes, but give it a try
Sent from my PC36100 using xda app-developers app
I see! Thanks! So are you aware of any PC36IMG for 5.07 software? And you mentioned 4.67 Hboot 2.18. Do you have a link? I don't think I tried it since I was looking for a "newer" version. But may be it will work? Thanks!
And, do you suggest install a different kernel, radio, etc? If so, which one should I try? I don't think I can make it worse.
XenonV said:
Yes, roms can cause hardware issues, well not only roms, but kernels, and more. And for your second question I can't say no or yes, but give it a try
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
i may have solved your problem....http://d-h.st/jrt
Sorry for being ignorant. I think I tried this one. It went back to bootloader after it "checking PC36IMG" without any real changes.
I thought it was due to it is a file I need to install from computer, rather than directly rename and put onto SD. That is why I was asking for a PC36IMG.zip file. I guess I am wrong?
Again, sorry for the ignorance. Never done these before. Just trying to save this brick I just bought. Thanks!
XenonV said:
i may have solved your problem....http://d-h.st/jrt
Click to expand...
Click to collapse
you mean flashing...try this http://www.youtube.com/watch?v=CA0Xfjstk_U&feature=my_liked_videos&list=LLjr29qtQIqEr0PzGlm9JIqw the audio on that vid sucks so turn your volume all the way up
I kinda realize the way, but my phone USB port not working right now. So that does not help.
XenonV said:
you mean flashing...try this http://www.youtube.com/watch?v=CA0Xfjstk_U&feature=my_liked_videos&list=LLjr29qtQIqEr0PzGlm9JIqw the audio on that vid sucks so turn your volume all the way up
Click to expand...
Click to collapse
PHONE INFO-
Virgin Mobile
primo c S-ON
HBOOT- 1.57.0000
Radio- 1.00.00.0928
Clockwork Recovery
I successfully managed to root my phone using the all in one tool thing, which I'm sure you have seen somewhere before. before researching any further, i decided to install the Paranoid (I think it was called) Rom, to get Jellybean. I found a tutorial, and it seemed simple enough. I went ahead with the step listed, and got to a part where it said to do a factory reset. I came across a problem there, because every time i tried to do it, a message said something along the lines of "unable to mount to /sd-ext". I was left with a nonfuctioning device, and googled a fix. I found stuff about RUU's, but i couldn't find one that worked for me because of my radio version. On other threads, people said that they successfully flashed a different radio, but they were probably on GSM phones. I attempted to do the same with a 1.00.00.0512_2 radio, but i got a signature error. I did more research, and learned that I can't do it because CDMA's are S-on. from what i've read, there isn't a way to make the Primoc version S-Off, so im pretty much stuck. I'm just wondering if there is any way that i have not found yet to save my phone, or if im screwed until they make a RUU for my phone, or a way to S-off the phone, to flash the different radio. Perhaps the answer is really simple and i've missed this whole time. I know that other people have asked this, but i really need to know
That blows man, at this moment there is no way of getting the S-off on the one v, people are still trying to find a way to get the s-off. Since you have the latest radio and boot version is technically impossible to go back to stock using the RUU. many people have had this problem, there isn't really a way of fixing it. You can try flashing codefirex rom or rythmicrom
, which work with the new radio.
Sent from my One V using xda app-developers app
do you have a custom recovery flashed to the device?
somekid15 said:
do you have a custom recovery flashed to the device?
Click to expand...
Click to collapse
Yes I believe so. I cant link it, but i looked up "clockwork recovery htc one v " in google and clicked the first link.
killadude123 said:
Yes I believe so. I cant link it, but i looked up "clockwork recovery htc one v " in google and clicked the first link.
Click to expand...
Click to collapse
when it reboots hold down on the volume and click recovery
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?