Develop Bugs

Rooting with Visonary 14 killed me phone

I didnt think this was possible but I think I bricked my phone by using Visionary and permroot.
I clicked on the permroot, the icon went on, rebooted and got stuck at the HTC green screen.
After pulling the battery;
I tried doing a factory reset, nothing.
I tried a stock image of tmobile, nothing (at least I think I did this right)
ADB doesnt recognize the device in windows
I have only seen a red triangle and exclamation point after trying several posts suggestions.
I'm stuck on what to do, and have a replacement coming, but not soon enough.
Can I do anything with this? Like get the original Tmobile image back on? If so, how? I'm not the brightest bulb when it comes to this, as the g1 was so much easier. A bit of instructions would be great.
Thank you!

People have been warned about visionary's high chance of bricking over and over again and that they should just use the rage method but they can't seem to get it.
Also: you do realize that the nand lock was to prevent this exact thing: people bricking their phones then returning them hoping to get them replaced. If it doesn't get replaced then you full well deserve it for not reading the countless posts about people bricking their phones using visionary.
First off: are you s-off?
Sent from my T-Mobile G2 running Cyanogenmod.

You didn't read the post which said you should not try to install the stock rom?
fastludeh22 said:
Ok mods, I know this normally isn't the place, but I think this is very important as I'm seeing more and more semi bricks, some of which are not recoverable without HTC signing keys!
So I ask you mods, please don't lock this, if anything it really needs to be a sticky!
That being said, if you are s-off, do NOT flash the signed offical PC10IMG.zip. if you don't have the correct rom on there when you do, as per the unroot thread you will get stuck.
Let me give u an example of what I've been seeing and why its happening so everyone understands. Example: you perm root/s-off your phone. You decide to do some rom playing. You end up boot looping and can't fully boot into android. So u say hey, ill reload pc10 and start over, WRONG.
What happens is s-off does no checks, sigs, version number etc. So when you load it up it starts to flash. Hboot(s-on) is first, then recovery, then radio. Thing is it has to reboot to do radio, so it reboots, at this point your s-on so it does a version check. "Main is older" then it quits before ever touching the system.img or boot.img. at this point you are locked. You have s-on, stock recovery, and can't boot android. Long story short, your screwed.
Now depending on the rom/kernel u had/have installed you may have adb access. At this point you have a small chance of recovering, which is better then some. I just spent the last 5 hours working with someone on a fix and think we got it, but the bat has died and will have to pick back up tomo. If this works or not, I also have one more idea we can try. I will update OP with any fixes we find.
*If your system was bootable when you started this, it may still boot. but you will be s-on, stock recovery, and still on whatever rom you were running. at this point you will have to hex edit to downgrade, or wpthis.ko if there is one for your kernel to get back to s-off.
*ive seen some people saying. i did it, it worked for me, but don't add any supporting info. this is bad for people new to android cause it makes them feel they will be ok. the only way this can work is if you have a version installed as old or older then the official img, or if you take hboot out of the update which then makes it no longer the official update. but my question is why are you flashing this? if you want to fully unroot, then follow the unroot guide. if you just want to go back to stock w/root, grab one of the stock w/root roms.
Long story short, do your rom flashing from recovery. Stay out of hboot unless you are following proven instructions to a T, or being walked though be a "pro". I hope this helps save some people!
* if you just read all this going DAMN, i already did that, then go here:
http://forum.xda-developers.com/showthread.php?t=842495
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App

@ddgarcia05 - that should be ok if he wasn't at S-OFF with the eng hboot though, which I don't believe that Visionary applies.

ibemad1 said:
People have been warned about visionary's high chance of bricking over and over again and that they should just use the rage method but they can't seem to get it.
Also: you do realize that the nand lock was to prevent this exact thing: people bricking their phones then returning them hoping to get them replaced. If it doesn't get replaced then you full well deserve it for not reading the countless posts about people bricking their phones using visionary.
First off: are you s-off?
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
I checked and it said S-On and this was in recovery

ddgarcia05 said:
You didn't read the post which said you should not try to install the stock rom?
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
ADB doesnt recognize the device in windows and this was also in recovery

Anyone? Bueller?

cwis said:
ADB doesnt recognize the device in windows and this was also in recovery
Click to expand...
Click to collapse
Check out the adb guide at http://forum.xda-developers.com/showthread.php?t=865685
If you install the HTC Sync software, as mentioned in that guide, that should give you the drivers that you need.

This looks bad. Being that you're new. this can be very bad.
You have three choices:
1: study each thread about Bricking G2.
2:find a more experienced person to help you unbrick your phone.
3:find a very strong magnet and place it on your phone leave it there for an hour and bring it back.

[Q] Help with semi (maybe full??) Brick G2 after Visionary+

OK before i get SEARCH.. I did and here is what i have looked at so far (i am 3+ hours into my search)...
http://forum.xda-developers.com/showthread.php?t=838484
http://forum.xda-developers.com/showthread.php?t=842495
http://forum.xda-developers.com/showthread.php?t=905261
ANd a few others that link back to one of those 3.
This is not my phone. I am helping my buddy who attempted to perma-root his phone using Visionary+ 14. I have an evo, and several other android phones and understand the basics of ADB and how to do most this stuff.
After he applied the patch, we are stuck on the white HTC screen. The problem is, it does NOT have the ENG SPL, we are still s-ON and still have stock recovery.
Here is what i have attempted so far:
download and tried to have it reload PC10IMG.zip - Got an error that said the version i was trying to install was older than the one i already had. I downloaded the latest one i could find.
Since i can get into the stock recovery, i downloaded and tried to use update.zip to reinstall things correctly, but that didnt work. It didnt error out and looked like it installed correctly, but still just stuck at the white HTC screen.
I cannot access ADB (at least any way that i know how).
Yes, i have the correct USB drivers installed and ADB is working as i have accessed it for other phones.
Here is the phone stats:
VISION PVT SHIP S-ON
HBOOT-0.82.000
MICROP-0425
RADIO-26.03.02.26_m
eMMC-boot
Sep 2 2010, 17:59:38
I cannot find the right RUU to give that a try either. I have found a few that MIGHT be right, but i dont want to mess it up more by flashing the wrong thing (if this would even help.. i dunno)
ANY HELP WOULD BE REALLY APPRECIATED!!!!

Anyone?? Help????

frettfreak said:
this is why people post in the dev forum when they arent supposed to.... cause NOTHING happens if you post in q&a...
Anyone?? Help????
Click to expand...
Click to collapse
You only posted a few hours ago. On a weekend. Might want to be a little more patient than that...
And you stated you have S-OFF? But not the engineering HBOOT? So were you using Visionary to temproot and then used gfree to get S-OFF? If so, you should be able to flash a custom PC10IMG with the radio removed (so it doesn't check for the version number). I know there is a thread containing one made by Hot_Hands that some people have used.
Or did you actually mean you had S-ON and that was just a typo? If that's the case, you're at the same point as a lot of others who have semi-bricked their device with Visionary (there are lots of threads out there with people describing this exact situation---phone had the OTA already, still S-ON, no ADB access, stuck at the HTC screen). Don't think anyone's come up with a solution yet. Most are just waiting and hoping that an RUU of 1.22 comes out at some point.
And just to make sure, you tried leaving the phone on for a while before connecting with ADB? And ADB didn't work in recovery either?

ianmcquinn said:
You only posted a few hours ago. On a weekend. Might want to be a little more patient than that...
And you stated you have S-OFF? But not the engineering HBOOT? So were you using Visionary to temproot and then used gfree to get S-OFF? If so, you should be able to flash a custom PC10IMG with the radio removed (so it doesn't check for the version number). I know there is a thread containing one made by Hot_Hands that some people have used.
Or did you actually mean you had S-ON and that was just a typo? If that's the case, you're at the same point as a lot of others who have semi-bricked their device with Visionary (there are lots of threads out there with people describing this exact situation---phone had the OTA already, still S-ON, no ADB access, stuck at the HTC screen). Don't think anyone's come up with a solution yet. Most are just waiting and hoping that an RUU of 1.22 comes out at some point.
And just to make sure, you tried leaving the phone on for a while before connecting with ADB? And ADB didn't work in recovery either?
Click to expand...
Click to collapse
Good point!! Sorry.. just a little anxious. Dont want to tell him his phone is bricked....
Also... maybe no one responded cause i am a tard.... its s-ON still, not S-OFF
And just to make sure, you tried leaving the phone on for a while before connecting with ADB? And ADB didn't work in recovery either?
Click to expand...
Click to collapse
you mean leave it on the white HTC screen for a while? What is a while? I left it for a minute or 2 then tried and no dice... you think longer? Also, no ADB when in recovery (i think this is because its stock recovery maybe??)
i DO have access to fastboot (i think) but not sure if this gives us any where to go with it??
Sorry for the confusion and pushy-ness and thanks for your help!

frettfreak said:
you mean leave it on the white HTC screen for a while? What is a while? I left it for a minute or 2 then tried and no dice... you think longer? Also, no ADB when in recovery (i think this is because its stock recovery maybe??)
i DO have access to fastboot (i think) but not sure if this gives us any where to go with it??
Click to expand...
Click to collapse
Well, like I said before, this is the type of semi-brick that people seem to be stuck in when Visionary fails and I haven't seen a working solution. When I said to leave it at the HTC screen, it was just something mentioned in the how to recover semi-brick thread you linked to in the original post. Unfortunately, if that didn't work, you might by out of options.
EDIT: And oh, I forgot to mention about fastboot. Although it might seem like fastboot detects the phone properly, you cannot actually use it to flash anything unless you have the engineering HBOOT, so that doesn't help any.

Maybe geting the orginal stock rom and flash it through bootloader
Sent from my HTC Vision using XDA Premium App

lainvalenajr said:
Maybe geting the orginal stock rom and flash it through bootloader
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Hmmm how do I do that? Is there a different way other than adb? I will check again but pretty sure I don't have adb access (I think this is what the eng spl does but I am just guessing here) does fastboot allow Me to do anything like that?

[Q] Boot loop with no recovery

I know theres probably a thousand topics on this but none of them seem to have the same exact problem or they do and dont have a solution. I can boot my ROM and i cant boot recovery. the only thing i can get to is HBOOT. I have tried many of the PB31IMG.zip files but none of them work. i have also tried the RUU exe program but that did not work either. im kinda graspin at straws here cuz i dont have a phone right now. im also wondering if i should just take it to verizon, but with that im worried about them finding out its rooted, because it still says "S-off" on the HBOOT menu. Any suggestions on what to do?

To my knowledge if you are in a bootloop with no secondary recovery such as Amon-Ra or CWR, the only other option is the RUU downgrade your Inc through the Android HBOOT Recovery. Use these guides here:
http://www.droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html

I have tried that exact process, both options, to no avail...thanks though. Is there any way to revert S-Off back to S-on through HBOOT?

gdaysoccer said:
I have tried that exact process, both options, to no avail...thanks though. Is there any way to revert S-Off back to S-on through HBOOT?
Click to expand...
Click to collapse
For whatever it's worth, my phone was s-off when I took it in to Verizon. (I was having the vibrations-of-death)
They saw the phone wasn't booting up, and even saw my unrevoked splash screen, and that was good enough for them to send me a new phone.
Honestly, I don't think a majority of those sales reps would even know how to get into hboot, and really don't know a whole lot about Android. I'm not saying it'd be impossible to get someone that lurks XDA in their spare time, but... it's unlikely.

And if they did lurk xda they probably wouldn't make an issue of you being rooted
Sent from my ADR6300 using XDA App

I actually just had the same issue as you and spent around 21 hours trying to get things fixed with a few devs and we had no luck. basically the phone would act as if it would take the ruu flash and claim it did and update the hboot like it did but made no change in order to complete a boot cycle. I had no recovery no rom just hboot and fastboot worked. every other option failed. we chalked this up to a hardware failure of some sort. I flashed the lastest Ruu and called *611 explained the problem and they overnighted me a new inc. I still have S-off on the phone but every other item radio/hboot/kernal is all stock. I doubht they wil lreally notice the S-off. all in all the phone is back to stock full wipe. Good luck.

I ended up taking it to the Verizon store today and the rep thought it might have been the battery so he tried a new one of those, but that wasnt the issue. I'm pretty sure he booted into HBOOT because he was playing around with the power and volume buttons, but he didnt ask me anything about it being s-off or rooted or anything and so theyre sending me a new phone, because unluckily they didnt have any in stock at the store i went to, and i have to send this one back. So, so far, it looks like no one really cares or even knows where to check for it being rooted.

simi brick?

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 ?

[Q] Stuck in a loop please help

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?