Related
borked up the fascinate whilst trying to update to the devs 2.2.
i know exactly what i did wrong. i was running voodoo5, and i clicked to disable lag fix, but i forgot to restart to let it *actually* disable before trying to load the new stuff. STUPID!
when that happened, it hung on samsung screen, then after battery pull all the phone will do is boot loop.. samsung screen, then goes to robot and screen says says "wiping cache, data, ect.." and then back to samsung screen to reboot and reboot.
i have literally 30 tabs open with articles from here and other forums, nothing seems to be working. here is what i have tried.
1. tried booting back to red cwm and playing with the lagfix (enable and disable again) to see if it would work, no go. i ended up losing red cwm - had to ODIN red back.. i cant get green to flash.
2. tried flashing DL09 both the full package and each individual part via ODIN
3. tried flashing the stocki500system.md5 (from the board) and kernel via ODIN, and nothing.. same boot loop. everything i have flashed via ODIN still gives me a boot loop..
4. tried to connect via ADB but it wont let me access the phone.. NOTE: i just downloaded ADB as a last resort and know nothing about it..
the only thing i can seem to do is get to red cwm. i have several backups in the restore section, but none of them seem to work - either i get a "no file found" even though i can see the file(s), or i get an error after it does load that says ".android_secure.img not found. skipping restore of /sdcard/.android_secure"
any ideas?
Okay follow these steps. Make sure you follow them step by step. Even though you have the lagfix installed this removed it for me.
http://forum.xda-developers.com/showthread.php?t=782204
Place the PIT file where it belongs. Then ODIN the system, kernel, and recovery in that order. Don't restart the process every time. Just ODIN them one after another.
thank you very much for taking a moment to answer. i did follow that thread, however
i managed to get the stocki500 recovery but the other files (recovery, PIT) are all 404 not found errors.
ive tried that stock md5 and it still boot loops. i actually have that tab open from when i tried that route..
any other ideas and thanks again
Thats why its not working. Try this restore by adrynalyne. The file is there and everything is in one. Just ODIN in the PDA section. This should work.
http://forum.xda-developers.com/showthread.php?t=867648
I got myself into a bit of pickle too. Kept getting errors on the new_cwm file. After numerous attempts. I figured out the file hadn't downloaded correctly and the archive was damaged. Folks who havent installed Froyo yet, do yourself a favor and check the files before you save it to your sd card.
BSayre18 said:
Thats why its not working. Try this restore by adrynalyne. The file is there and everything is in one. Just ODIN in the PDA section. This should work.
http://forum.xda-developers.com/showthread.php?t=867648
Click to expand...
Click to collapse
downloading now.. thanks for the point to this file.. i hadnt found that one yet
no problem. it should work out good.
mailaliasgar said:
I got myself into a bit of pickle too. Kept getting errors on the new_cwm file. After numerous attempts. I figured out the file hadn't downloaded correctly and the archive was damaged. Folks who havent installed Froyo yet, do yourself a favor and check the files before you save it to your sd card.
Click to expand...
Click to collapse
i soft bricked doing that with a corrupt file before.. however that time i was able to restore using my backup.
this time, every time i try a method, it kicks me back to boot loop. if the file that im downloading now doesnt work, i will have to try and figure out ADB as a last resort..
thanks much for the help!
BSayre18 said:
no problem. it should work out good.
Click to expand...
Click to collapse
problem
thank you for all your help
mrjake1970 said:
problem
thank you for all your help
Click to expand...
Click to collapse
So this worked for you? You just re-rooted as normal?
def
Thank you all for your help. i applied all the info i got here, and one of them worked it finally took the ODIN flash to stock and i recovered into FROYO from there.
seriously thank you all.. its great that the community is so supportive
I did the exact same thing a couple of days ago, and recovered a similar way, odin back to D101, flashed DL09 & superclean, then restored a backup, then disabled voodoo and finally flashed DL30. I've got a couple of questions.
1: Is voodoo completely off my phone or is it just disabled (is there a difference)? When I apply update.zip from the blue recovery I get green cwm.
2: Each time I backup, restore, flash a different rom I apply update.zip, then from green recovery I flash "new_cwm.zip". Is this necessary?
Joe T said:
I did the exact same thing a couple of days ago, and recovered a similar way, odin back to D101, flashed DL09 & superclean, then restored a backup, then disabled voodoo and finally flashed DL30. I've got a couple of questions.
1: Is voodoo completely off my phone or is it just disabled (is there a difference)? When I apply update.zip from the blue recovery I get green cwm.
2: Each time I backup, restore, flash a different rom I apply update.zip, then from green recovery I flash "new_cwm.zip". Is this necessary?
Click to expand...
Click to collapse
i followed all the hints i got, and i think that the one i got about formatting helped me get out of the boot loop from hell.. it finally took my flash from ODIN, it wouldn't until i did the format(s)..
mind you i am NOT an expert, however from what i read and talked about offline, voodoo is still resident on your phone but disabled (check to see if you have the voodoo file still on your card).. if DL30 is running fine, you are ok..
from what i have read, yes.. the new cwm is required in order to get it to mesh properly with 2.2 leak.. i havent had any issues and i loaded that as well.. from one of the posts i read, if you are a serial flasher, then you need to make sure that not only you download the new cwm zip, but also should have deleted the entire clockworkmod folder from your card for best results..
I love this threadd.... I did the same damn thingg...
Sent from my SCH-I500 using XDA App
You guys are not alone. I'm just glad the peeps that know what's going on have the patience to put up with us.
Sent from my SCH-I500 using XDA App
adrynalyne's di01 odin package covers a multitude of sins.
upsidedownaaron said:
adrynalyne's di01 odin package covers a multitude of sins.
Click to expand...
Click to collapse
It will literally bring any phone back from the dead as long as its a software issue. I recommend keeping the di01 package, samsung drivers and Odin 1.3 on your computer at all times...
Sent from my SCH-I500 using XDA App
godihatework said:
It will literally bring any phone back from the dead as long as its a software issue. I recommend keeping the di01 package, samsung drivers and Odin 1.3 on your computer at all times...
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
ABSOLUTELY!! I have those on my computer at all times, adrynalynes d101 brought me back a few times.
Sent from my stock 2.1
unrooted, fully bloated (for now) Fascinate
I was wondering how it was possible to brick your phone (which somehow happened to me..) just by trying to get into CWM Recovery by doing the 3 button press.. As it is possible because it happened to me earlier today I was just wondering if it was a step that I did wrong.. Also I had nothing installed except flashing the Froyo EB01 modem which flashed successfully and than reflashed cwm recovery all which worked though I forgot I had to reboot fast or else samsung would replace cwm. So when I flashed a second time and than tried rebooting into cwm that's when it got stuck and bricked..
I got it solved earlier thanks to Adranalyne.
If anybody needs his thread for the all in one odin:
http://forum.xda-developers.com/showthread.php?p=9711053
Ensure it's not simply blank screen...hit search soft key when it ' should' go into cwm
Sent from my SCH-I500 using XDA App
Shadowchasr said:
Ensure it's not simply blank screen...hit search soft key when it ' should' go into cwm
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Naw, it was stuck on the samsung logo screen for an hour-got bricked. But i fixed it .
Can someone explain how exactly you fix it? I am having that problem as we speak...
sengokubattosai said:
Can someone explain how exactly you fix it? I am having that problem as we speak...
Click to expand...
Click to collapse
Odin it back to stock. Either Dl01 or Eb01. Both files include everything for you to recover your phone ans be able to boot back up past the samsung logo.
Taking it back to EB01 every time can be a bit extreme. There are CWM tar files that you can use to just flash CWM with Odin. I've used them when my phone would not boot into recovery. Remember the best way to get to "Download" mode is to pull the battery and while holding the down vol button plug it into your PC. I know thats common knowledge but it's always good to put it out there. Other techniques can prevent Odin from establishing a connection.
I've even seen complete Super Clean tars up to 2.6. I don't remember where but when 2.7.1 bricked my phone I just used Odin to flash a 2.6 tar and my phone was back to normal. Now I use that ROM image instead of EB01 when an update fails.
I would stress that any ROM compiled by someone else is not going to be endorsed by the Dev that created the update. I just took a chance because I was already down and it worked great.
Hey guys,
I flashed back to stock with ODIN. Everything passes. But when the phone reboots it comes up with Samsung custom logo and seems to get stuck there? Any ideas?
EDIT: this is the ATT I337, I have flashed with ODIN before and it worked out fine. I am doing everything I normally did.
evolution2012 said:
Hey guys,
I flashed back to stock with ODIN. Everything passes. But when the phone reboots it comes up with Samsung custom logo and seems to get stuck there? Any ideas?
EDIT: this is the ATT I337, I have flashed with ODIN before and it worked out fine. I am doing everything I normally did.
Click to expand...
Click to collapse
Have you made any changes since you last used ODIN? Did you flash a different version? How long are you waiting?
hamzer11 said:
Have you made any changes since you last used ODIN? Did you flash a different version? How long are you waiting?
Click to expand...
Click to collapse
I waited like 3 minutes or so. But it never passes the custom Samsung screen at boot. Maybe I need to give it more time? I flashed Loki and I installed slimbean. Slimbean was a little buggy as it is still in beta so I went to restore my recovery. My recovery was missing from TWRP so I tried flashing back to stock odin to start over from square one.
I am using ODIN 3.07 on a PC running Windows 8. If I find out that all i have to do is wait longer I am gonna feel like an idiot lol.
evolution2012 said:
I waited like 3 minutes or so. But it never passes the custom Samsung screen at boot. Maybe I need to give it more time? I flashed Loki and I installed slimbean. Slimbean was a little buggy as it is still in beta so I went to restore my recovery. My recovery was missing from TWRP so I tried flashing back to stock odin to start over from square one.
I am using ODIN 3.07 on a PC running Windows 8. If I find out that all i have to do is wait longer I am gonna feel like an idiot lol.
Click to expand...
Click to collapse
Initial boots can be long but I don't know about more than 3 minutes? Not really sure about what happens if you ODiN back after TWRP? I'll let more technical folks take a stab at it. It can't hurt to wait though.
Well I don't know what was ailing the odin flash, but I just used Kies emergency recovery and all is fine now. Weird... Appreciate your help.
evolution2012 said:
Well I don't know what was ailing the odin flash, but I just used Kies emergency recovery and all is fine now. Weird... Appreciate your help.
Click to expand...
Click to collapse
Question for you, does recovering this way wipe everything? Apps, root, settings, all mods? Just want to know for my own reference.
hamzer11 said:
Question for you, does recovering this way wipe everything? Apps, root, settings, all mods? Just want to know for my own reference.
Click to expand...
Click to collapse
This was my first time ever using KIES recovery. As far as I could tell everything is wiped. I did a factory reset afterwards just to be safe so I can't say with 100% certainty. I had the custom logo after reboot for 10 seconds, then after a manual reboot it boots regularly without the custom logo.
Phone stuck on "Samsung - Custom" screen after creating TWRP backup. Help please?
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Simonzi said:
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Click to expand...
Click to collapse
There are no less than a dozen similar threads about similar problems already. Have you looked at those threads for a possible solution yet? You can find them by using the search function or better yet just doing a visual search of the first few pages of the "General" and "Q&A" sections. Good luck.
Sounds like a ROM and kernel issue. Try flashing a ROM with a loki'd kernel.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Tylorw1 said:
Sounds like a ROM and kernel issue. Try flashing a ROM with a loki'd kernel.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
I don't see how that could be the case. I didn't flash anything. I just loaded TWRP, created a backup, and rebooted my phone. No ROM\kernel change. Nothing more than creating a backup in TWRP.
scott14719 said:
There are no less than a dozen similar threads about similar problems already. Have you looked at those threads for a possible solution yet? You can find them by using the search function or better yet just doing a visual search of the first few pages of the "General" and "Q&A" sections. Good luck.
Click to expand...
Click to collapse
I tried searching, the closest one I could find on the first few pages was this one. I just didn't see any specific to my situation because nothing was flashed. Like my response to Tylorw1, all I did was boot into recovery, create a backup, and reboot my phone. Didn't flash a ROM, change a kernel, format anything, etc...
I has this same problem... It happened after every single reboot after flashing various ROMs or anything.. I gave up and went back to CWM and haven't had the problem since :good:
Sent from my SGH-I337 using xda app-developers app
Simonzi said:
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Click to expand...
Click to collapse
what version of twrp? if it is 2.6.?.? then get off of it, also, what I did was pull battery for 3min, it booted fine....go back to early version of twrp...
STVERDI said:
I has this same problem... It happened after every single reboot after flashing various ROMs or anything.. I gave up and went back to CWM and haven't had the problem since :good:
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I've wanted to go back to CWM. That's what I had on my S3. Only thing stopping me, is all my nandroid backups for my S4 are done with TWRP, and I don't want to run into a situation where I need them, and them not being compatible
TheAxman said:
what version of twrp? if it is 2.6.?.? then get off of it, also, what I did was pull battery for 3min, it booted fine....go back to early version of twrp...
Click to expand...
Click to collapse
Nope, still on 2.5.0.2. Finally, after a third complete wipe/format and restore from the back I had created (the one that started the whole issue), it works fine. Such a huge pain in the ass.
a user had to boot back into twrp and wipe data/factory reset yesterday to fix this issue.
Simonzi said:
I've wanted to go back to CWM. That's what I had on my S3. Only thing stopping me, is all my nandroid backups for my S4 are done with TWRP, and I don't want to run into a situation where I need them, and them not being compatible
Nope, still on 2.5.0.2. Finally, after a third complete wipe/format and restore from the back I had created (the one that started the whole issue), it works fine. Such a huge pain in the ass.
Click to expand...
Click to collapse
And you have to be ****ing kidding me. I rebooted into recovery while typing my initial response, just to verify I was still on the 2.5.x.x TWRP. Booted up TWRP, verified that, choose "Reboot System", and same thing. Back to sitting at the Samsung screen. Nandroid backups or not, ditching TWRP as soon as I get it able to boot back up.
Even worse off now than when I started. After my last post, where my phone was doing the same "stuck on Samsung logo" thing, just from booting into TWRP, I decided to swap to a different recovery. Searched for "switch from TWRP to CWM", and found my own post I had made a few months ago, but never went through.
Following those instructions now, I decided on the PhilZ CWM. Head over to that thread, grab the loki'd zip, load up TWRP, and flash the zip. Now I can't even boot into recovery!! It just freezes on the Samsung screen with the blue "recovery booting" text.
Can still get into download mode, so I tried using ODIN to flash PhilZ jflteatt.tar.md5 file, and it fails.
At this point, waiting for the stock 1.6 firmware package to download, so I can just ODIN that.
If anyone has any other suggestions though, they'd be great. Have an hour to try while waiting for that to download
somebody had mentioned this...
http://forum.xda-developers.com/showpost.php?p=44629460&postcount=8
make sure you have the correct firmware and proceed as you are. likely your best bet.
Simonzi said:
Even worse off now than when I started. After my last post, where my phone was doing the same "stuck on Samsung logo" thing, just from booting into TWRP, I decided to swap to a different recovery. Searched for "switch from TWRP to CWM", and found my own post I had made a few months ago, but never went through.
Following those instructions now, I decided on the PhilZ CWM. Head over to that thread, grab the loki'd zip, load up TWRP, and flash the zip. Now I can't even boot into recovery!! It just freezes on the Samsung screen with the blue "recovery booting" text.
Can still get into download mode, so I tried using ODIN to flash PhilZ jflteatt.tar.md5 file, and it fails.
At this point, waiting for the stock 1.6 firmware package to download, so I can just ODIN that.
If anyone has any other suggestions though, they'd be great. Have an hour to try while waiting for that to download
Click to expand...
Click to collapse
Stock 1.6 firmware package?
Make sure you get the correct firmware? Go to SamMobile and get the stock firmware from there or go to Adam Outlers "Stock firmware ODIN" thread in the General section (the AMDL firmware link is in that thread you just have to look for it).
scott14719 said:
Stock 1.6 firmware package?
Make sure you get the correct firmware? Go to SamMobile and get the stock firmware from there or go to Adam Outlers "Stock firmware ODIN" thread in the General section (the AMDL firmware link is in that thread you just have to look for it).
Click to expand...
Click to collapse
Yeah, I meant 1.6gb firmware package. Just forgot the "gb". That's what I'm currently downloading, but trying to recover it with Kies while waiting.
I would like to report I had the same problem.
After changing roms and making a nandroid, and then deciding to switch roms again, I ran into the stuck at Samsung Custom with a lock boot screen. Most roms would boot up once, but a restart or power down would lead to being stuck. I was flashing through TWRP.
I went into TWRP and flashed OUDHS recovery which overrode TWRP and wiped/flashed through OUDHS a new rom.
Problem solved.
S3 at&t stuck in TWRP booting screen.
xBeerdroiDx said:
a user had to boot back into twrp and wipe data/factory reset yesterday to fix this issue.
Click to expand...
Click to collapse
Im new to custom roms, I pressed ok for an update on my phone, after the update was complete my phone shut off and booted into TWRP and now I can't get back to my android screen nor make calls etc. HELPPPPPPPP PLEASSSSSEE I have been trying to fix my phone since july and I have been using this cheap phone that don't even get internet. I have an S3 1747 at&t
Lnjames said:
Im new to custom roms, I pressed ok for an update on my phone, after the update was complete my phone shut off and booted into TWRP and now I can't get back to my android screen nor make calls etc. HELPPPPPPPP PLEASSSSSEE I have been trying to fix my phone since july and I have been using this cheap phone that don't even get internet. I have an S3 1747 at&t
Click to expand...
Click to collapse
Wrong forum. Please go to the s3 section with your question.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Had this problem just now, solved it by fixing permissions.
I am running an MDL based S4, and screwed the pooch. I was going to wipe the internal storage and made the mistake of doing it through TWRP 2.5. Now, I have the same problem of being stuck on the custom boot screen. I have tried to change from TWRP to OUDHS Recovery, but still boot loops to Custom screen. I have tried fresh installs of 4.2 ROMs and 4.4.2 Google Editions. Do I need to flash via ODIN?
Flame away....I know better than this!!!!
Help would be greatly appreciated.
Sent from my GT-N8013 using Tapatalk 4
Hi!
So I followed Djembeys guide to root my s4 back when ME2/MF2(or smthn in that matter)was the newest firmware avable. But now I wanted to go back to stock and update my phone and as stated in the guide that would be no problem, well OTA didn't work so i did it via Kies. It worked as expected for a while before my phone started freezing and rebooting itself forever, like as soon as i get into the launcher.
Things I've tryed to do:
*Checking in download mode that everything is official, it is, and the phone doesn't seem to reboot while in download mode, should I flash a stock rom, I mean, what if the phone shuts off in the middle of the process?
*Doing a factory data reset via stock recovery, the "android" in recovery falls down and a triangle at his stomach. However the data reset worked, but it didn't solve the problem, still reboots but now when the phone is trying to set itself up.
What can i do guys? You think i can send it back to the store seeing everything is official in download mode?
NidexX said:
Hi!
So I followed Djembeys guide to root my s4 back when ME2/MF2(or smthn in that matter)was the newest firmware avable. But now I wanted to go back to stock and update my phone and as stated in the guide that would be no problem, well OTA didn't work so i did it via Kies. It worked as expected for a while before my phone started freezing and rebooting itself forever, like as soon as i get into the launcher.
Things I've tryed to do:
*Checking in download mode that everything is official, it is, and the phone doesn't seem to reboot while in download mode, should I flash a stock rom, I mean, what if the phone shuts off in the middle of the process?
*Doing a factory data reset via stock recovery, the "android" in recovery falls down and a triangle at his stomach. However the data reset worked, but it didn't solve the problem, still reboots but now when the phone is trying to set itself up.
What can i do guys? You think i can send it back to the store seeing everything is official in download mode?
Click to expand...
Click to collapse
Which s4 is this? This is the sprint variant. Post it in the appropiate s4 of your carrier. You can try to odin back to stock.
Sent from my SPH-L720 using xda app-developers app
ROMANTiC KiD said:
Which s4 is this? This is the sprint variant. Post it in the appropiate s4 of your carrier. You can try to odin back to stock.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Aww really, i totally missed that this was for sprint:/. I have the NEE version(unbranded GT-I905). Are you sure i can flash stock, what if it would reboot while flashing? It is already stock, just that I have this damn problem with the reboots;(
Mine did some of that kind of thing when I first went to MF9 a few days ago. I think the reason I had the problem was because I did a nandroid recovery using a custom recovery (TWRP). I think (but have no proof) that it overwrote some of the MF9 stuff with MDL stuff. So to fix it, I redid everything and recovered my apps and data through Titanium Backup instead. All good now.
Follow the directions I posted yesterday in the following thread to get to unrooted, stock MF9:
http://forum.xda-developers.com/showthread.php?t=2427006
jejb said:
Mine did some of that kind of thing when I first went to MF9 a few days ago. I think the reason I had the problem was because I did a nandroid recovery using a custom recovery (TWRP). I think (but have no proof) that it overwrote some of the MF9 stuff with MDL stuff. So to fix it, I redid everything and recovered my apps and data through Titanium Backup instead. All good now.
Follow the directions I posted yesterday in the following thread to get to unrooted, stock MF9:
http://forum.xda-developers.com/showthread.php?t=2427006
Click to expand...
Click to collapse
It worked fine and your phone didn't reboot in download mode? I've tested to be inside download mode for around 10 min, so i guess it's fine if i flash stock rom.
NidexX said:
It worked fine and your phone didn't reboot in download mode? I've tested to be inside download mode for around 10 min, so i guess it's fine if i flash stock rom.
Click to expand...
Click to collapse
I'm not exactly sure what you're asking, but the phone worked fine once I redid it. Before that, it would have random boots, and then multiple boots like a boot loop. But it never did more than 2 boots before actually coming up. But it would reboot after a while. BlueTooth would not turn on, stuff like that. It just was not right. But the redo with the TiBu restore worked great. I'm now very stable on MF9, rooted, stock rom.
jejb said:
I'm not exactly sure what you're asking, but the phone worked fine once I redid it. Before that, it would have random boots, and then multiple boots like a boot loop. But it never did more than 2 boots before actually coming up. But it would reboot after a while. BlueTooth would not turn on, stuff like that. It just was not right. But the redo with the TiBu restore worked great. I'm not very stable on MF9, rooted, stock rom.
Click to expand...
Click to collapse
nvm dude, seems like it's hardware failure. I tried flashing it with stock MGA firmware and the problem remains, as well as the screen ****ing up just before it is about to reboot. Well, thanks anyway!