Samsung GS4 i377M stuck in reboot after kingo rooting and unroot, wipe, pwr btn rmved - Device Repair

Hey all,
Alright so, just tried to fit every detail of this problem with this phone in the title there. I got this phone from a friend and i sent it away to get the screen replaced. Got it back, screen works great, everything worked great, great. But after i changed all the information over to mine, then rooted it with Kingo (which was really easy and awesome), I later decided to unroot, and after that was done, i put the otterbox case on it, and it just kept rebooting after that.
I seriously thought it was a power button issue. But was it really?. I then wiped the phone by going into recovery mode, to see if that would clear up the kingo problem, but it still reboots. I removed the power switch off the motherboard after that, and after putting everything back together, I booted the phone up and tried to set everything up, but it then crashed and showed the Samsung Galaxy S4 logo on the screen again, and just would not boot after that.
To me, it sounds like it's just constantly crashing. I've already ruled out the possibility of it being the power button, and I have no idea if it is the Kingo root causing it to crash, what should I try next?. Thanks.

Related

Nexus One stuck in bootloader

Pardon for the long post but my Nexus One has been out of comission for a few days now so I'll list everything I've tried to make it work in an attempt someone might be able to help me!
Okay, here goes.
A couple days ago I removed the battery on my phone to install an invisible shield. Prior to that I had owned the Nexus One brand new for about a week, had it rooted first thing with the HTC Desire ROM...it was running perfectly
After the installation of the shield was complete I reinserted the battery and hit the power button. The phone booted straight to the bootloader (aka white Robots on Skateboards screen). Funny thing, I was unable to navigate the bootloader (vol up/down) without fiddling with the trackball first by pressing it a couple times) Anyway if I would reboot the phone via bootloader it would return...power off the phone it wouldn't power off just reboot to bootloader.
In this mode I could still use fastboot perfectly and I could enter the restore screen. At this point I kept attempting a reboot and it actually went through at one point and did a full boot to the OS...when I powered down and booted up again however, it was back to the same issue.
On the modaco forum they suggested I flash an alpha2boot.img as the boot image replacement for r21 desire rom as a fix, I tried this method with no success. Since, I've factory reset the phone several times replacing it with various ROMs (currently running stock) none of it fixed the problem.
I also found a way to brute force the phone into safe mode via the fastboot command in prompt: fastboot-windows reboot Using this command the phone successfully reboots, albeit into SAFE MODE. In safe mode the phone works perfectly in every way. I'm just limited in that I can't install any applications and I can't reboot properly (without a computer and command prompt).
I was doing some research on the forums and read the problem could be with the trackball. It would make sense that the phone could only boot to bootloader if the phone had the key press for the trackball triggered somehow. That said, the trackball functions perfectly when operating the phone in safe mode so I doubt this is the issue.
Another idea is that the phone is stuck in some state in the SPL or bootloader...I was wondering if there was anyway to reflash the SPL or bootloader to see if I could resolve the issue that way. (how I would do this, I have no idea)
Any help, suggestions, or advice is very appreciated. As I already unlocked my phone I have a feeling I am out of luck for warranty though I would pay for HTC to repair it if they could. I would prefer to fix it in the software however and not send it in.
Reflash the stock ROM and see if that helps.
mortzz said:
Reflash the stock ROM and see if that helps.
Click to expand...
Click to collapse
He said he's running stock rom...
@ OP, if everything was absolutely perfect before putting the shield on, and everything to crap immediately after finishing the shield, then obviously something went wrong during the install.
The obvious yet unfortunate conclusion is that some solution got inside or something, most likely inside the trackball. =\
Detail exactly what you did when you installed the invisible shield.
Did you get you phone wet at all?
Got the front of the phone a little wet and I'm guessing some did get in the trackball. That said, I do invisi shields every day for my job and never had an issue with any phone...wouldn't it be ironic that mine was the one that got screwed up.
I think it's interesting to note that the trackball still works perfectly when the phone is running in safe mode, no double clicks or anything like that...possibly a sensor was tripped?
Got the front of the phone a little wet and I'm guessing some did get in the trackball. That said, I do invisi shields every day for my job and never had an issue with any phone...wouldn't it be ironic that mine was the one that got screwed up.
I think it's interesting to note that the trackball still works perfectly when the phone is running in safe mode, no double clicks or anything like that...possibly a sensor was tripped?
So I called it quits on fixing this phone and I'm sending it out to HTC does anyone know how I go about getting restore back to factory settings?
Well you can't relock the bootloader, but if you can use fastboot when your phone's on the booatloader, you can use that to wipe the phone.
Oh wow, sorry to hear it.
If your phone will not boot without the help of fastboot, I wouldn't worry to much about what state Android is in (factory, or custom rom). HTC will attempt to boot the phone, toss it in a bin, and then send you a replacement.
Or that is my assumption anyways. A friend had a similar issue; he unlocked his phone and decided after flashing the Desire rom, that he wanted to stay stock with what came on his Nexus for a while. After flashing the stock images back, his phone looped into bootloader. Off to HTC it went and within a week he had a new phone.
Best of luck!
Sorry to post in such an old thread, but I'm having the exact same issue. Even the part with the invisible shield. Didnt install it myself, the idiot at best buy used too much of the liquid I guess. Did you send yours in or what? I managed to get the phone to work for about a month then it started acting up again today. Wont boot into anything other than safe mode, or fastboot. When it boots into safe mdoe, the phone turns off within a few seconds then goes straight to the boot animation. Would love to get this issue settled, really annoying
i am having same problem. fasboot doesnt even find my phone. i got into safe mode but when i turned it off and back on it went back to fastboot
Same
I am getting the same problem! this really sucks. I think the phone might have gotten a little bit wet, just a few drops of water, and that may have caused this. Should I just call HTC and send it in?
btw, the phone was working fine, even with the very little moisture that was wiped from it. But, I took out the battery when I got home, and this happened.
so is this because on invisibleshield? cuz i just ordered mine today!!
I think its from a little bit of moisture getting into the trackball. I've been doing many "tests" trying to figure out the problem, and my almost final conclusion is the trackball not working good. Most of the time I try to start-up the phone i get into safemode, and once I have gotten into the normal way of things, but the trackball wasn't working well. I think I might have to cal htc, and that sucks because I am going out of the country in 4 days... I won't be able to take my nexus if I can't come up with a way to fix it myself.
I DID IT!
Well, I think I did.
My theory that moisture was the cause of this bootloader stuckness is quite correct. I took a towel, and rubbed the trackball to it for a good 5-10 min, then I did it for another 5-10 min wiping while pressing down on the trackball. I'm very sure that there was some moisture extracted from the device. The trackball is working now. I now do not have to call HTC or send it in.
I kept on booting into fastboot and then recovery, being unable to press buttons, but then I rebooted again into safe mode, where the trackball wasn't working either. I kept moving around the trackball, and then I figured it out, because I felt a slight bit of moisture. Now, it boots up normally, I can access the recovery, and all selection is working.
But, I have a bad feeling that this problem will come back to haunt me. It's good for now though.
Phone is working great as usual.
Can confirm the same issue.
Drop of water on the trackball.
Rebooted into an unresponsive fastboot.
Fastboot reboot command from the computer got me into safemode.
Rolling the trackball while pressed fixed it, the phone boots properly now.

everything is Force Closing since yesterday

hey guys, I don't know what's going on with my S7 but yesterday was working fine and out of nowhere everything started to FC! From twitter to "Google Services Framwork", Gmail, browser, tweetdeck, calendar, voice, I can't pretty much use it anymore, I haven't done any new app installations so i don't know what's wrong! is it just me, or anyone else having this problem??
Any help will be much appreciated!
Thanks
That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.
djdanska said:
That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.
Click to expand...
Click to collapse
ha! i remember I already did that. After the Update we had, and I exchanged mine for a new one I decided to stay with no root (i don't know why! lol) so I guess I'll reset everything and go back to root I figured at the end I was gonna do that, but I was trying to see if it was just me or there was a fix
thanks man!
ok, so since yesterday I've been trying to factory reset the DS, and when it boots back on, everything stays the same!
I'm a little confused now, if I take a picture and I turn the tablet off, when I turn it back on, the picture disappears. Same thing happens if I move widgets, delete or create new ones on the screen, they go back to as the configuration was on friday night! GV not working, and the last message that shows there, same thing, shows the last one on friday. I don't know what can I do.... should I call dell??
duck tape and dynomite
stupid thing started crashing yesterday FC this and FC that ....cant restore it as i no longer have write access to the internal sd card
1) tried nv flash
2) tried restoring from clockwork
3) tried pushing files through adb
4) tried fastboot ....
if i didnt just dump money into this thing id blow it up ......
any help would be appreciated.......any tips to fix it or kill it completely so i can get another one
actually deleted all of the files on internal sd card and uninstalled every program on the device looked completly stock ....rebooted it and it went back to how it was yesterday ......theres gotta be a reason why other are having the same problem that started on the same day .....maybe dell pushed an OTA update and screwed us ......just a thought cause mine was fine till i went 4g yesterday so my sis could post facebook pics ....not sure but hope we can figure this out
Samething happened to me
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution
jz83 said:
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution
Click to expand...
Click to collapse
I'm running stock, and I discovered the hard way that you can't let the S7 battery run all the way down. The S7 will not power itself down in time. I had the same issue, and the only way around it was to do a complete factory reset, using the menu button from the main screen. I think the reset is in the "About" section, but I don't have my S7 with me now.
Being used to WM6, which powers the device down at 5%, I was not expecting the device to do this, but there it is.
dell streak 7
im not sure if I am the only one with this issue you but becareful with the streak 7 mine well both of mine wont charge properly and the newest one wont charge at all. i have to send it back to dell for them to fix it. Im not sure what cause this but my only advie is to never use a different charger for it only dell chargers. Im guessing that it messes up the battery callibration and then it gets really hot when charging

Weird problem with GT-8190L when trying to root, install CWR/TWR or custom ROM

Hi hello howdy!
I'm going to skip the foreplay cose the action here is pretty weird and you'll want to get right in, trust me.
I've a Galaxy S3 Mini GT-8190L, that reboots itself, after it has booted up, and I entered the sim pin and lock pattern I've from seconds to 5 min of grace before the phone restarts itself. I have tried two different batteries and the problem persists. I went and decided to rule out hardware problems (power bttn) and after some tinkering, ruled that out too. So now my best guess is firmware.
The phone is not rooted, does not have recovery mode installed, and is running stock 4.1.2 jelly bean with TouchWiz, no mods, no hack-y stuff, your old regular samsung s3 mini.
I tried installing CM11 with odin, and didn't work. But not because odin threw an error, no, that went on perfectly according to the program. But when the phone booted up, the rom was still stock, nothing changed, and it rebooted itself briefly. Weird. So then I thought "well, maybe at least the recovery mode is there now" since it supposedly was a package install. But no, when I tried to boot onto recovery the phone gets stucked on the boot screen with the samsung brand and model of the phone, and then restarts itself, this happens like four times and then the phone boots normally, the OS starts, everything loads and then goes on to restarting. So this was not a solution either.
Next I though, well lets just install the recovery, no, that didn't work, odin said that the install was successful but it was not. Tried with odin 3.04, .07 and .09, tried CW and TWR, neither of them load, as before, when trying to boot to recovery the phone displays the splash and the reboots itself like four times before starting up the OS.
Next I though well, lets try to root this thing, at this point I was just trying anything to see if anything sticked, but nothing, tried SuperOneClick, and no. Wanted to try TowelRoot but that uses an apk. I tried vRoot against my best judgement, but that didn't work, but not because of the reasons you might think, it did install, the phone managed to stay on for enough time for it to get running, but when it restarted, there was no app there, it was as if nothing was installed just a few second ago. I thought "huhh? That's really weird". So I went and did some testing on this matter.
It turns out that no matter what I do, I can install an app, delete 5 apps, change settings, and nothing sticks, when the phone restarts it goes back to the way it was, its like the phone lost the short memory and its like that Adam Sandler and Drew Barrymore's movie, 50 First Dates. The phone rollsback to the state it was when everything began.
I even tried to change something quick, and restart myself the phone to see if that would make the change stick, but no, that didn't work either.
So, I came up with a brilliant idea, look up a similar case on internet, 'cose you know, it has to have happened to someone else before me. But this is so weird that looking it up is a challenge by itself. I tried a few things here and there but nothing does it. So now I'm here writing my sci-fi story looking for some feedback on how can this story be ended without killing any of the characters, I want everyone to survive and work again. You know, happy endings.
Any ideas on what can be the problem? Seen anything like this before?

Freedom did it

I have a situation with my girls g flex. I'm a Samsung user so I can't really help her.
OK here's what happened I rooted her phone with towelroot everything has been fine for months except just last night she wanted to take freedom off her phone because it kept messing with the play store so inside freedom's settings I hit turn freecore off it rebooted the phone then when it turned back on the sprint logo just flashed it wouldn't boot normally so I went into recovery and wiped and it still does the same thing even using the hard reset screen thing. So now when it boots after wiping it will quickly flash the sprint screen barely seeing the yellow screen. How can this be fixed
tune in to Kool London FM
I can try to help
Beatjunkee said:
I have a situation with my girls g flex. I'm a Samsung user so I can't really help her.
OK here's what happened I rooted her phone with towelroot everything has been fine for months except just last night she wanted to take freedom off her phone because it kept messing with the play store so inside freedom's settings I hit turn freecore off it rebooted the phone then when it turned back on the sprint logo just flashed it wouldn't boot normally so I went into recovery and wiped and it still does the same thing even using the hard reset screen thing. So now when it boots after wiping it will quickly flash the sprint screen barely seeing the yellow screen. How can this be fixed
tune in to Kool London FM
Click to expand...
Click to collapse
Honestly,
Sounds like your gunna need 2 Download Lgflash Tools & the correct file 2 flash, so you need, to get Variant Model #, hunt down Software. after you reflash, UPDATE your phone.
Go to Check Updates take all updates b4 you reroot device hope this helps
Also power phone down and hold her Vol up & plug the USB Charger in @ same time you're holding Vol up this should put the phone in Download Mode, so you can flash new firmware

Note 4 Reboot Problem with Weird Temporary Solution

I'll try to make this short.....
I am using N910T3. Phone was charging in car while using (stop by roadside). Out of sudden it shutdown and went into reboot loop and the phone is extremely hot. I took the battery out for soft reset and try to turn on again. Phone will freeze at different screen (Lock Screen, Home Page, Samsung Logo, Powered by Android) and give two separate vibration before reboot.
I thought it is battery problem so I bought a new battery to try, but still the same problem. So I went on to backup all file before I perform hard reset. While doing that, I find out the phone can be use for longer before reboot if it was stay off for a long time. So I have this crazy idea: put it in a fridge. Surprisingly it works! The phone will not reboot anymore and I can manage to backup all file before doing anything else. Also, the phone will not charge if you plug in right after a few reboot.
Then, along with the fridge method, I perform factory reset through normal android setting. Now it will just stuck at powered by android screen while in reboot loop. I then try to flash with Odin, multiple times. Flash by Odin is complete, phone restart, then it freeze and reboot, at different screen (Installing system update, Erasing, powered by android).
Out of frustration I try with the fridge method to flash, and IT WORKS AGAIN!!!. The phone can now boot to welcome screen where you first setup your phone. However, it will then freeze again and reboot while doing so.
There was only this one time, where I left the phone off for a day after flash with a previous stock ROM, turn it on and skip as much setup as I can, finally reach the homepage screen, then will stay on without any reboot issue. I thought I finally fix it. I then power off the phone, put in my Sim Card and SD Card, power it on, then again, reboot issue appear.
I tried flash with latest stock ROM, previous stock ROM (one updates away), flash any stock ROM with pit file. I sometimes will get error code on device after flash (can't remember the exact error). I also cannot boot into recovery mode without flashing a twrp. Sometimes if success, I will get straight to Lock Screen without going through the phone welcome setup process. But again, none of these I tried can solve the reboot loop.
I may went too far and mix up all steps to the phone. Does anyone have any idea how to fix this? Or is my phone, as I believe, has a faulty motherboard that cause the reboot loop? Thanks in advance for reading through my problem!
Hello there, I had a Tmo Note 4 which I loved it until the end, it's a hardware problem and there is no fix for it unless you replace the board, by the time you buy the board and what you need to pay for labor you're going to expend a few hundred dollars, I also tried the freezer method but it finally the phone gave up, it does not turn on anymore. That was my experience. Good luck bud.
oscarmaldonado said:
Hello there, I had a Tmo Note 4 which I loved it until the end, it's a hardware problem and there is no fix for it unless you replace the board, by the time you buy the board and what you need to pay for labor you're going to expend a few hundred dollars, I also tried the freezer method but it finally the phone gave up, it does not turn on anymore. That was my experience. Good luck bud.
Click to expand...
Click to collapse
Seems like that's the case I guess.....But if anyone has any suggestion please do tell so I can give it a shot.
jackgan said:
Seems like that's the case I guess.....But if anyone has any suggestion please do tell so I can give it a shot.
Click to expand...
Click to collapse
Try a firmware flash before newsest. Then take the ota
anyone know if a 910t3 mother board will fit in a 910t frame? Asking cuz I wanna switch them out.

Categories

Resources