Hey all,
I started to update to the latest RUU following Scott's instructions. First half seemed to go ok. However, when the tried to reboot, the screen went black, and the orange LED at the top is stuck on. Phone's nonresponsive. It's been that way for about 45 minutes now. So right now, it looks like it's only done half an update.
I haven't done a battery pull yet, but I'm wondering if I should. Any thoughts, or am I SOL?
Thanks,
Super
Superguy said:
Hey all,
I started to update to the latest RUU following Scott's instructions. First half seemed to go ok. However, when the tried to reboot, the screen went black, and the orange LED at the top is stuck on. Phone's nonresponsive. It's been that way for about 45 minutes now. So right now, it looks like it's only done half an update.
I haven't done a battery pull yet, but I'm wondering if I should. Any thoughts, or am I SOL?
Thanks,
Click to expand...
Click to collapse
Mine rebooted after the first round of updating and was stuck on boot screen. I took the battery off. Rebooted back I to bootloadet and reflashed the leak (you will notice it updates stuffs in order from the top to the bottom this time) and it was back on business.
Good luck
Yeah, after about an hour I figured I didn't have anything to lose. Pulled the battery and rebooted to the bootloader. It finished and seems to be working now.
Superguy said:
Hey all,
I started to update to the latest RUU following Scott's instructions. First half seemed to go ok. However, when the tried to reboot, the screen went black, and the orange LED at the top is stuck on. Phone's nonresponsive. It's been that way for about 45 minutes now. So right now, it looks like it's only done half an update.
I haven't done a battery pull yet, but I'm wondering if I should. Any thoughts, or am I SOL?
Thanks,
Super
Click to expand...
Click to collapse
You basically have to flash the ruu twice. It basically just does the firmware the first round, and the rom the second.
qudwis said:
You basically have to flash the ruu twice. It basically just does the firmware the first round, and the rom the second.
Click to expand...
Click to collapse
I knew that it had to be done twice. My concern was that it bombed the first time and bricked it due to how it was responding.
Related
does anyone know how long it should take for odin to finish flashing my phone back to stock? Also has anyone seen this screen? It's black, with a white cell phone and a white computer with a yellow triangle with an "!" in the middle between them....? that's all i can get my phone to do. Odin is taking a really long time and i'm not sure everything's working right.
it should take 5-15 minutes at max.
I get that sign every time i do odin, but unlike others i just click the power button and reboot and its good... try that?
well how do i know when odin is finished? becuase it's been stuck on step: chache.rfs for about 20 minutes now and i don't know if it's just frozen up or what. I don't want to unplug it if i'ts still doing something.
hate to sound like a **** head but when that happened to me this last go around (getting stuck on the chache part) i unplugged which gave me the computer ... ! thingy i put it back into download mode and opened odin then plugged my phone back in. hit start after putting my pit and tar files in their respective spots and it worked. took less then 6minutes i'd say.
There are ways to dl mode your phone from computer ... ! screen just find them. im leaving for a puppy otherwise i would have linked it. gf getting angry RAWR!! <(*-*t)
thats her giving me the bird and ready to kill. LOL
That happened to me also, and it was my very first flash on the Vibrant. It soft-bricked, but I just kept at it... got back into download mode... and tried again. It worked. As far as I can gather, as long as you can still get to download mode, you are golden, even if it takes a try or two. It seems that Odin is sometimes temperamental. It only takes a couple of minutes to flash via Odin, but when you are sitting there waiting for the PASS notification, it does seem like an eternity the first time you do it.
I got a FAIL the first two times on the very first attempt. It's a bit unnerving when you aren't sure it'll come back.
vballrkc said:
does anyone know how long it should take for odin to finish flashing my phone back to stock? Also has anyone seen this screen? It's black, with a white cell phone and a white computer with a yellow triangle with an "!" in the middle between them....? that's all i can get my phone to do. Odin is taking a really long time and i'm not sure everything's working right.
Click to expand...
Click to collapse
Are you running window's 7?
If you are run as admin , also that happened to me to couple days ago at the 5th time trying it finally worked
theronw68 said:
Are you running window's 7?
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App
I am currently downgrading back to stock on my T959 using Odin 3 and it keeps hanging at the very first part when it says file analysis. I have been at this part for a good 30 mins. any suggestions? just keep retrying until it works?
Just keep at it...ODIN likes to be picky.
mine normally takes like 2-4 min
mine froze on factory reset.rfs or something yest for like 10 min so i unplugged and got the 'phone ! pc screen', took me like 2 hours to get it to connect to odin again
aecabanaboy said:
I am currently downgrading back to stock on my T959 using Odin 3 and it keeps hanging at the very first part when it says file analysis. I have been at this part for a good 30 mins. any suggestions? just keep retrying until it works?
Click to expand...
Click to collapse
could redownload odin and the pit/tar files again and try that
It takes about about 3 minutes to get my Vibrant from any custom to JFD. I just Odin 3 v1.81, s1_odin_20100512.pit, can T959UVJFD.tar files only. Total time is about 2:20-2:35 seconds.
Mine takes about 2-3 minutes
i am now flashing with odin and its stock on catche is this a problem ?
mine hasnt moved from the downloading screen - its been about 39min.
Hey guys,
Hoping someone can help out here, although I'm guessing I will need to do this: http://forum.xda-developers.com/showthread.php?t=991072
My phone has been prompting for the last 36 hours or so to do the OTA update which I had been putting off due to wanting to retain root (done with SuperOneClick) and not having time to follow the instructions for that. I had wireless turned off last night, and this morning when I turned it back on it downloaded the update without asking, but still asked before attempting to install. It's been asking me every hour since and I've said 'Later' every time.
Anyway, I stepped away from my desk for half an hour at work this afternoon and came back to find my device boot-looping. I don't expect anyone at work would have touched it, I just don't know what led up to this behaviour. I get the Motorola animation, then the AT&T "Rethink Possible" animation, and then the screen goes blank and the LED blinks red about 120 times at about 3 times the speed of a normal notification and then it starts over again.
The only reason I'm concerned about doing the SBF flash is that this is a SIM-Unlocked device on Telstra network in Australia and I really don't want to loose wifi functionality. Other than that I'm quite comfortable doing so. The phone had only been rooted, I hadn't done the deodex ROM or any mods.
Does anyone have any suggestions?
WheelieBin said:
Hey guys,
Hoping someone can help out here, although I'm guessing I will need to do this: http://forum.xda-developers.com/showthread.php?t=991072
My phone has been prompting for the last 36 hours or so to do the OTA update which I had been putting off due to wanting to retain root (done with SuperOneClick) and not having time to follow the instructions for that. I had wireless turned off last night, and this morning when I turned it back on it downloaded the update without asking, but still asked before attempting to install. It's been asking me every hour since and I've said 'Later' every time.
Anyway, I stepped away from my desk for half an hour at work this afternoon and came back to find my device boot-looping. I don't expect anyone at work would have touched it, I just don't know what led up to this behaviour. I get the Motorola animation, then the AT&T "Rethink Possible" animation, and then the screen goes blank and the LED blinks red about 120 times at about 3 times the speed of a normal notification and then it starts over again.
The only reason I'm concerned about doing the SBF flash is that this is a SIM-Unlocked device on Telstra network in Australia and I really don't want to loose wifi functionality. Other than that I'm quite comfortable doing so. The phone had only been rooted, I hadn't done the deodex ROM or any mods.
Does anyone have any suggestions?
Click to expand...
Click to collapse
Seems like if it did try to install it failed somewhere not allowing for full boot... have you tried pulling the battery also try and find out if it is running 1.5.7 also try booting in recovery and factory reseting. And also don't you only lose wifi when flashing 1.5.2? I might bw wrong about that though
Sent from my MB860 using XDA Premium App
drock212 said:
Seems like if it did try to install it failed somewhere not allowing for full boot... have you tried pulling the battery also try and find out if it is running 1.5.7 also try booting in recovery and factory reseting. And also don't you only lose wifi when flashing 1.5.2? I might bw wrong about that though
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Sorry, I should have specified... yes, I have pulled battery - issue persists. I hadn't gone as far as a factory reset, but it's definitely less dramatic than a reflashing, so trying that now...
OK, factory reset seems to have done the trick - it was still on 1.2.6, I'll do the update to 1.5.7 with the v2 Root Process now and see how I go.
WheelieBin said:
OK, factory reset seems to have done the trick - it was still on 1.2.6, I'll do the update to 1.5.7 with the v2 Root Process now and see how I go.
Click to expand...
Click to collapse
Congrats friend! Glad to hear you're out of that boot loop.
Sent from my MB860 using XDA Premium App
I have a very unusual problem that i just googled and have not come across. I woke up this morning and found that my display wasn't turning on, as if the phone was off. I had encountered this problem before and a battery pull worked fine. Im on MR2 btw... but this issue is different, my diplay is completely dead, D-E-D, dead... after the battery pull i held the power button to start up again but all i got was the vibration on start up, no lcd screen response.
i know the issue is the lcd screen and i can replace it myself, if it had just been that. i have the total protection plan set up and can replace it, but my only issue is that the TB is rooted. upon fixing it they will realize it once the CM7 animation comes up. i need advice on how to handle this situation.
i cant bootload neither, display is completely off... i can hear sound going on so i know its on. Help please!
i had CM7 rc1.2, mr2 radio, clocked up to 1.6.. i was on bamf for a while but switched to cm7 2 days ago.
You cant boot into recovery mode? Try booting into hboot see if the screen works. If it doesnt just take it to VZW and when they fix it be like "What the heck! You guys rooted my phone?!"
alluzzion2o9 said:
I have a very unusual problem that i just googled and have not come across. I woke up this morning and found that my display wasn't turning on, as if the phone was off. I had encountered this problem before and a battery pull worked fine. Im on MR2 btw... but this issue is different, my diplay is completely dead, D-E-D, dead... after the battery pull i held the power button to start up again but all i got was the vibration on start up, no lcd screen response.
i know the issue is the lcd screen and i can replace it myself, if it had just been that. i have the total protection plan set up and can replace it, but my only issue is that the TB is rooted. upon fixing it they will realize it once the CM7 animation comes up. i need advice on how to handle this situation.
i cant bootload neither, display is completely off... i can hear sound going on so i know its on. Help please!
i had CM7 rc1.2, mr2 radio, clocked up to 1.6.. i was on bamf for a while but switched to cm7 2 days ago.
Click to expand...
Click to collapse
Have you tried running a RUU (ROM update utility) to return your phone to stock? Download one of the .exe RUU's (not the zip) to your computer from this page http://dougpiston.com/ThunderBolt/RUU/ and run it from your computer with your phone plugged in and turned on. With any luck it will return your phone to stock.
i cannot multi quote for $hit, anyways no i cannot get into bootloader because my display wouldn't boot up... but out of sheer luck i finally got it to work!!! and heres what i found! the screen has water damage! then i remembered this morning before getting my phone i tipped over a cup of tea my son left there. im lucky the phone even boots up! i guess facing the phone downwards saved my phone but not the screen... ill hit up VWM and see what they have to say.
nucher said:
Have you tried running a RUU (ROM update utility) to return your phone to stock? Download one of the .exe RUU's (not the zip) to your computer from this page http://dougpiston.com/ThunderBolt/RUU/ and run it from your computer with your phone plugged in and turned on. With any luck it will return your phone to stock.
Click to expand...
Click to collapse
does it matter which one i pick? of the RUU i mean?
[edit]
nevermind i got it, the process seems similar to updating touchpro2, half way through updating.. thanks man! although i got my phone working im going to be bothered with the watered down screen. i can simply open it up and clean it but that'll waste my total protection plan i have with VWM =P
alluzzion2o9 said:
i cannot multi quote for $hit, anyways no i cannot get into bootloader because my display wouldn't boot up... but out of sheer luck i finally got it to work!!! and heres what i found! the screen has water damage! then i remembered this morning before getting my phone i tipped over a cup of tea my son left there. im lucky the phone even boots up! i guess facing the phone downwards saved my phone but not the screen... ill hit up VWM and see what they have to say.
does it matter which one i pick? of the RUU i mean?
[edit]
nevermind i got it, the process seems similar to updating touchpro2, half way through updating.. thanks man! although i got my phone working im going to be bothered with the watered down screen. i can simply open it up and clean it but that'll waste my total protection plan i have with VWM =P
Click to expand...
Click to collapse
Glad you were able to get the RUU to work. I didn't specify one RUU because I figured you would use any one of them just to get your phone to stock, then you can take it to Verizon or mail it to asurion for replacement.
nucher said:
Glad you were able to get the RUU to work. I didn't specify one RUU because I figured you would use any one of them just to get your phone to stock, then you can take it to Verizon or mail it to asurion for replacement.
Click to expand...
Click to collapse
ye i already set up the order... cost $99 in deductables or some $hit... hopefuly it will be here tues/wednes.. thanks a whole lot for the help
alluzzion2o9 said:
ye i already set up the order... cost $99 in deductables or some $hit... hopefuly it will be here tues/wednes.. thanks a whole lot for the help
Click to expand...
Click to collapse
You're welcome. When you get the new phone don't hesitate to put CM 7 back on after you're rooted. I feel its they most flexible and up to date ROM you can put on an Android phone.
nucher said:
You're welcome. When you get the new phone don't hesitate to put CM 7 back on after you're rooted. I feel its they most flexible and up to date ROM you can put on an Android phone.
Click to expand...
Click to collapse
will come in tomorrow, i have 15 days to mail my damaged one or its 300 ;P. CM has always been my fav. its super fast. my favorite part is how fast booting up can be, unlike bamf sense 3.0. only problem i had with cm7 was that when it rings it rings once.. and when i get a voicemail notification it goes ape $hit.
other than that its still my fav.
alluzzion2o9 said:
will come in tomorrow, i have 15 days to mail my damaged one or its 300 ;P. CM has always been my fav. its super fast. my favorite part is how fast booting up can be, unlike bamf sense 3.0. only problem i had with cm7 was that when it rings it rings once.. and when i get a voicemail notification it goes ape $hit.
other than that its still my fav.
Click to expand...
Click to collapse
I had the same problem with the phone only ringing once, I changed the ringtone from Digital Phone to Bell Phone and that solved my problem. I read that certain ringtones don't work properly with CM7 and there is fix in the next update.
Hey, guys, I know there are a lot of these issues with a lot, if not all, of the HTC smartphones, but I've only seen a few of these for the HTC Radar, and they all seem to give the same answers. Hopefully my explanation of the problem will help!
So, I got the phone thanksgiving weekend 2011, so I've had it for about a year. One day around the beginning of April this year, my phone randomly began a restarting loop, where it would gradually restart itself from a blank white screen over and over, then it went to the HTC screen over and over, and then periodically switched between the HTC screen and the black "Windows Phone" load screen over and over again. I tried taking off the battery cover and leaving it for a couple of minutes and then hours, but I put it back and it just kept rebooting. I was left without a phone for about two days.
On the second day, I put it on the charger and left it in my dorm while I was in class all day, and when I came back, it was rebooting still, but I noticed that it always made it to the "Windows Phone" logo loading screen and then restarted. After about 4 reboots, it went back to normal and I was able to use the phone. After the next couple of months, it stopped doing it in such a long period of time, but the battery usage went up almost 30-40% than what it used to be. Once in a while, it would reboot once, but then it would be back to normal.
This time, in late October, it started the reboot thing again, but this time, only going up to the HTC screen and looping that. I tried taking the battery cover off again and leaving it for hours, but same problem now. So I decided to leave it off for a day. By this time, I had my HTC Desire HD as backup, but it was unlocked, and at the time when I bought it, I didn't know anything about HSDPA numbers, so I could use my T-Mobile SIM, but no mobile network, since it's a Telus/AT&T phone.
I tried charging it, but this time, it lasted for a whole week. After rebooting over and over, it would last 3 hours, then stop because the battery would die out. So I just left it, and left it, and weeks went by, and my warranty had long since expired, so I couldn't go to HTC about this. I even called them to see what I could do, and they told me to do a Factory Reset, well... here is a list of the things I tried:
- IMAGE CRC: At first I didn't know what this was, and so I looked it up. After finding out what it was, I tried it, and I got two numbers: BL CRC-0xD19F79E1 and OS CRC-0x4CC706B. I looked those up on the internet and got nothing. I restarted the phone, and nothing happened at all. (If there was something else I was supposed to do here, please tell me!)
- Factory Reset: This was the LAST thing I wanted to do, but I had no choice and I tried it, hoping the error would be fixed. So I scrolled down to it, everything seemed to be normal, it gave me a warning, and I clicked it ... I was very suspicious of this, because as soon as I clicked "Factory Reset", it said "Reset complete. Press Volume Down to restart". I mean IMMEDIATELY after. Now, I KNOW that Factory Resets take much longer than an instant to actually have happened. But I restarted anyway. ... Nothing, still. I tried it several times after that, only to get the same result.
Those are the two options I tried, besides looking on the internet... if I can avoid buying a new Radar, I would like to, at all costs, because the next time I have a decent amount of money, I would like to save it for something else. Is there anything else I could try to resolve this issue, or at least gain more information on the problem?
Thank you all very much for reading my post!
BladedYouth said:
Hey, guys, I know there are a lot of these issues with a lot, if not all, of the HTC smartphones, but I've only seen a few of these for the HTC Radar, and they all seem to give the same answers. Hopefully my explanation of the problem will help!
So, I got the phone thanksgiving weekend 2011, so I've had it for about a year. One day around the beginning of April this year, my phone randomly began a restarting loop, where it would gradually restart itself from a blank white screen over and over, then it went to the HTC screen over and over, and then periodically switched between the HTC screen and the black "Windows Phone" load screen over and over again. I tried taking off the battery cover and leaving it for a couple of minutes and then hours, but I put it back and it just kept rebooting. I was left without a phone for about two days.
On the second day, I put it on the charger and left it in my dorm while I was in class all day, and when I came back, it was rebooting still, but I noticed that it always made it to the "Windows Phone" logo loading screen and then restarted. After about 4 reboots, it went back to normal and I was able to use the phone. After the next couple of months, it stopped doing it in such a long period of time, but the battery usage went up almost 30-40% than what it used to be. Once in a while, it would reboot once, but then it would be back to normal.
This time, in late October, it started the reboot thing again, but this time, only going up to the HTC screen and looping that. I tried taking the battery cover off again and leaving it for hours, but same problem now. So I decided to leave it off for a day. By this time, I had my HTC Desire HD as backup, but it was unlocked, and at the time when I bought it, I didn't know anything about HSDPA numbers, so I could use my T-Mobile SIM, but no mobile network, since it's a Telus/AT&T phone.
I tried charging it, but this time, it lasted for a whole week. After rebooting over and over, it would last 3 hours, then stop because the battery would die out. So I just left it, and left it, and weeks went by, and my warranty had long since expired, so I couldn't go to HTC about this. I even called them to see what I could do, and they told me to do a Factory Reset, well... here is a list of the things I tried:
- IMAGE CRC: At first I didn't know what this was, and so I looked it up. After finding out what it was, I tried it, and I got two numbers: BL CRC-0xD19F79E1 and OS CRC-0x4CC706B. I looked those up on the internet and got nothing. I restarted the phone, and nothing happened at all. (If there was something else I was supposed to do here, please tell me!)
- Factory Reset: This was the LAST thing I wanted to do, but I had no choice and I tried it, hoping the error would be fixed. So I scrolled down to it, everything seemed to be normal, it gave me a warning, and I clicked it ... I was very suspicious of this, because as soon as I clicked "Factory Reset", it said "Reset complete. Press Volume Down to restart". I mean IMMEDIATELY after. Now, I KNOW that Factory Resets take much longer than an instant to actually have happened. But I restarted anyway. ... Nothing, still. I tried it several times after that, only to get the same result.
Those are the two options I tried, besides looking on the internet... if I can avoid buying a new Radar, I would like to, at all costs, because the next time I have a decent amount of money, I would like to save it for something else. Is there anything else I could try to resolve this issue, or at least gain more information on the problem?
Thank you all very much for reading my post!
Click to expand...
Click to collapse
May be it is a Hardware problem. Why you don't try to put HSPL and to cook custom rom ? I do this on mine few days ago and now the phone is more useful than before. I cooked HD2O ROM and till now working fine for me. When you change bootloader with HSPL may be it will work out if it is a Software problem. Also you need to change Radio Firmware other wise the device can not boot. When I am doing HSPL a few times phone just loop restarts and not start but after I do everything like it was in treads here and flash new radio the phone is working fine now. But may be there is a Hardware problem.
Tonyco1 said:
May be it is a Hardware problem. Why you don't try to put HSPL and to cook custom rom ? I do this on mine few days ago and now the phone is more useful than before. I cooked HD2O ROM and till now working fine for me. When you change bootloader with HSPL may be it will work out if it is a Software problem. Also you need to change Radio Firmware other wise the device can not boot. When I am doing HSPL a few times phone just loop restarts and not start but after I do everything like it was in treads here and flash new radio the phone is working fine now. But may be there is a Hardware problem.
Click to expand...
Click to collapse
Thank you very much for responding! So just to be clear, how exactly do I go about flashing a ROM on the Radar, and a new radio? On Android phones, its much easier to root the device or simply place the ROM folder in there and make it work. I have no experience with doing this to a Radar, as I was previously led to believe that this was impossible. Should I just browse this forum?
BladedYouth said:
Thank you very much for responding! So just to be clear, how exactly do I go about flashing a ROM on the Radar, and a new radio? On Android phones, its much easier to root the device or simply place the ROM folder in there and make it work. I have no experience with doing this to a Radar, as I was previously led to believe that this was impossible. Should I just browse this forum?
Click to expand...
Click to collapse
Yes just browse this forum but only section about Windows Phone 7 Development and Hacking. You will find DFT exclamation of how to install HSPL. In mine it was very easy because I not receive Country ID fail my phone was buy in Europe. If you receive Country ID error you need to proceed with goldcard it is explained there but first proceed without goldcard if it work it is very easy. Also when you proceed SPL2.05 it is not clear in the topic but you need to be in bootloader so you should start your phone with VolUp and VolDn keys pushed this is not explained in the topic and I waist a lot of time till figured out. After that just download one of the 7.8 ROMs here in Radar section and write it down. Also download new radio and use some RUU to put it on the phone before the ROM other wise the phone can not boot. Try and after that if you have problems write down here.
MY RADAR TURNED BACK ON! I don't know exactly what happened, but after a couple of reboots, the battery indicator flashed and then it rebooted twice until finally turning on the full amount.
Tonyco1 -- Thank you very much for staying with me and replying to my request! Although what you suggested is not needed for my booting issue, I'm going to try it anyway to see if I can actually boot 7.8! Thank you again.
BladedYouth said:
MY RADAR TURNED BACK ON! I don't know exactly what happened, but after a couple of reboots, the battery indicator flashed and then it rebooted twice until finally turning on the full amount.
Tonyco1 -- Thank you very much for staying with me and replying to my request! Although what you suggested is not needed for my booting issue, I'm going to try it anyway to see if I can actually boot 7.8! Thank you again.
Click to expand...
Click to collapse
OK but you need to but some custom ROM my phone turn back on when I put custom ROM a lot of features and works really good.
I have the Verizon S4 i545, obviously. Rooted right after getting it in June. Still on Android 4.2.2, kernel 3.4.0-562219, build number i545VRUAMDK. I have never updated anything. Tried, tbh, but OTA fails. But whatever. I have never had an issue with anything, until a few days ago. Now, whenever my phone turns on, regardless of whether it was restarted or powered down then on, It hangs at the Verizon animation, then finally goes to my lockscreen with no notification bar. Phone is essentially useless at this point because when I unlock my phone, I get a black screen that does nothing. Only way to fix it, is to pull the battery, then power on. Works every time. I have no idea what happened to cause this. I have not removed anything system related recently. Any ideas?
I would like to fix the problem and leave it. But if I can't, I might be flashing a new rom.
Kasper DG said:
I have the Verizon S4 i545, obviously. Rooted right after getting it in June. Still on Android 4.2.2, kernel 3.4.0-562219, build number i545VRUAMDK. I have never updated anything. Tried, tbh, but OTA fails. But whatever. I have never had an issue with anything, until a few days ago. Now, whenever my phone turns on, regardless of whether it was restarted or powered down then on, It hangs at the Verizon animation, then finally goes to my lockscreen with no notification bar. Phone is essentially useless at this point because when I unlock my phone, I get a black screen that does nothing. Only way to fix it, is to pull the battery, then power on. Works every time. I have no idea what happened to cause this. I have not removed anything system related recently. Any ideas?
I would like to fix the problem and leave it. But if I can't, I might be flashing a new rom.
Click to expand...
Click to collapse
Are you running a custom rom.
No I'm not. Everything is untouched except for the root process. That's it.
Kasper DG said:
No I'm not. Everything is untouched except for the root process. That's it.
Click to expand...
Click to collapse
I would guess to flash VRUAMDK no wipe factory image.
http://forum.xda-developers.com/showthread.php?t=2301259
Any idea why I'm randomly having this problem?
Kasper DG said:
Any idea why I'm randomly having this problem?
Click to expand...
Click to collapse
I don't really know, I've never encountered a problem like that yet.
Ok. Might try flashing the factory image.