Well, I've had my unit rooted since about a week after I bought it, 2 1/2 years ago. Everything fine - even after using SlimLP 5.02 February Alpha version. Up until yesterday. Something happened, very slow, and wouldn't get into any Google app/site. Kept saying "Google Play" not installed when it was.
Anyway, tried to reflash to Omni 4.4.4 - had MAJOR issues seeing the screen (auto dimming enabled - and simply too dark). Finally worked through the startup/config stuff, and decided since it had an issue - go back to stock a few days and make sure hardware was ok.
So, fired up Odin, flash the old stock firmware I had from Sammobile a while back - now it's stuck at the flashing "SAMSUNG" label. I'm charging fully (was around 50% when I flashed), and will try to reflash again with latest Sammobile firmware (slightly newer that the one I've got).
Now - to the question - anyone know of CWM 6.0.1.1 (I believe) or SlimLP Lollipop would have re-partitioned the device? IF it did, anyone got a PIT file to get the partitions lined back out for the GT-P3113 (Galaxy Tab 2 7)?
No need to repartition. Just enter recovery mode and factory reset it.
Sent from my LGUS990
Ok - it's finally working - I hope. I honestly have no idea what shook it loose.
Process - updated a stock Samsung image for that unit half a dozen times using Odin 3.10. Would always reboot, play the "Samsung Chime", and get to the colored "SAMSUNG" logo and hang. Hooked up to Kies to see if I could do an Emergency Firmware Reload - no dice. Kies would know that something was hooked up, but it wouldn't ever get to saying model, etc. Tried Kies3 - it immediately said it wasn't the correct version - so it knew enough to know Kies3 wouldn't work.
Anyway, loaded a slightly newer version of the stock firmware, using Odin 3.10.0, AND got a stock PIT file for my 8GB unit and applied that - same results. Went into the now Stock Recovery mode (vol+ & power), wiped cache, data, reset - 4 times. Every time, it would reboot and hang. Finally went in, and instead of wiping anything, just rebooted (hit the power button) - this time it took off "updating xx of xx apps". Booted up, went into "I'm a new system - configure me". Afterwards, downloading updates for apps. Seems to be functioning.
So - I don't know what was hanging it up, I don't know if the eMMC is going bad (I haven't loaded it that much, unless the SlimLP Lollipop did something to cause issues). I wouldn't mind the stock firmware so much, except for the 8 tons of crap they load onto it, and you can't get rid of.
There was a "decrappify" that could be applied - but wasn't terribly successful 2 years ago (early 2013). Does anyone know of one that works for the GT-P3113? I'm going to stay stock for a couple of weeks, and watch it to see if it starts acting up again.
Related
Phone: Samsung Galaxy S3 - i747m 16GB
Rom: Cyanogenmod 10.2.1
This is an FYI, and curiosity post. FYI in case somebody else thinks to try what I did, and curiosity as I'm not 100% sure what I did wrong. Apologies if this is the wrong place for this - first post.
So, I flashed a bad modem update, and hardbricked my phone. Used the methods described here to debrick via SDCARD (SGH-I747M-UEMK5, so I guess I was using 4.3 bootloader - figured this out later - used a SANDISK Ultra 32GB UHS-1 card BTW). Got my phone back to the point where I needed the SDCARD inserted for the phone to function. Attempts to flash the bootloader via recovery didn't work (didn't check, but seemed that it "worked", but might have gone to the SDCARD, and not internal memory). Reading further, posts suggested that I revert to stock.
As I now had download mode available again, fired up ODIN, and with "I747MVLUFNE6_I747MOYCFNE6_BMC" (which is 4.4, and I didn't realize I had a 4.3 bootloader at this time) from sammobile, proceeded to flash with no warnings. Succeeded. Phone rebooted, and I received the "stock" samsung boot animation with sound. It did its thing for a bit, and then came to the "decrypt phone" prompt. My phone had been encrypted a while back, but wasn't when I started this "journey". I recalled having this problem once before when reverting to stock, and no code entered worked (needed to wipe data). For fun, I entered the code that was previously used to encrypt the device. It actually appeared to start working (that green Android picture with gears showed up when you put in the right code), and I could see the outline of the statusbar. It sat there for about 30 seconds, and then powered off. I thought it would reboot, but it didn't. No powerup, or lights visible, and I've tried virtually every debrick image on SDCARD (NE6) to no avail.
So, I'm getting the phone JTAG'ed tomorrow, but thought I'd throw this out as I initially thought I had solved the problem, but guess not. The only thing I can think of is flashing 4.4 stock vs. 4.3, however, the phone initially booted. Could it have flashed the bootloader again after ODIN and during the subsequent initial boot, and somehow screwed itself up?
Update after JTAG:
Took the phone to a reputable repair shop. Unfortunately, the JTAG was unsuccessful. Speaking briefly with the tech, he said that they tried writing at different speeds a couple of different times, and each time the write was successful, however, still no dice. They were using a Riffbox.
Unless something drastic happens, I feel that this is the end of this one (also, open to more "exotic" methods now lol)
- A few days ago my phone freezes while I am using it, and its stuck on the google screen. at this point, it's on 5.0.1 unrooted, unlocked bootloader.
- I try going into recovery and wiping cache and doing factory reset. I keep getting errors but eventually the wipes work. Still doesn't boot though. So I do this a few times. I got it to boot twice but both times it froze within 5 mins and back to the same thing.
- I fastboot 5.0.1 factory image, goes through. but still no dice - stuck on google boot screen.
- I research and find out about the infamous power button problem. it doesn't seem like thats the issue with mine because the buttons seem to work fine. whatever, i take it to a local repair shop (phone is out of warranty) and the next day they inform me that there is no physical issue and that their software reset worked. they used the LG factory firmware way of resetting the device.
- Got the device back, used it for a while. It was fine for the time being but it was on 4.4.3 and I got the 4.4.4 update. I go and unlock bootloader, flash 5.0.1 factory image and push TWRP+root.
- Doesn't boot again, stuck on google logo
- I tried a whole bunch of stuff and nothing worked. I ended up with flashing 4.4.3 factory image in fastboot and relocking the bootloader so I could take it back to the shop the next day. At this point the phone wasn't even turning on.
- The next day (today), I tried turning it on, nothing. I put it in the charger for a while, then turned it on.... and it booted! used it for a while, it's fine.
- Did 4.4.4 system update, it's fine.
- Unlocked bootloader, it's fine.
- Tried to flash 5.0.1 factory image and again same issue - stuck on google screen.
- Been dicking around the last few hours trying to fix it ended with flashing 4.4.3 again but same issue, I then put the phone into download mode and connect to the computer but I got a green screen something about DemiGod Watchdog HW reset. I did the reset.
- Phone booted up again! Did the 4.4.4 system update and then it started freezing and rebooting withing few seconds of use. Now it's back to being stuck on google screen.
- I am obvious gonna bring it back to the shop now but any idea as to what is happening here?
nikulogical said:
- A few days ago my phone freezes while I am using it, and its stuck on the google screen. at this point, it's on 5.0.1 unrooted, unlocked bootloader.
- I try going into recovery and wiping cache and doing factory reset. I keep getting errors but eventually the wipes work. Still doesn't boot though. So I do this a few times. I got it to boot twice but both times it froze within 5 mins and back to the same thing.
- I fastboot 5.0.1 factory image, goes through. but still no dice - stuck on google boot screen.
- I research and find out about the infamous power button problem. it doesn't seem like thats the issue with mine because the buttons seem to work fine. whatever, i take it to a local repair shop (phone is out of warranty) and the next day they inform me that there is no physical issue and that their software reset worked. they used the LG factory firmware way of resetting the device.
- Got the device back, used it for a while. It was fine for the time being but it was on 4.4.3 and I got the 4.4.4 update. I go and unlock bootloader, flash 5.0.1 factory image and push TWRP+root.
- Doesn't boot again, stuck on google logo
- I tried a whole bunch of stuff and nothing worked. I ended up with flashing 4.4.3 factory image in fastboot and relocking the bootloader so I could take it back to the shop the next day. At this point the phone wasn't even turning on.
- The next day (today), I tried turning it on, nothing. I put it in the charger for a while, then turned it on.... and it booted! used it for a while, it's fine.
- Did 4.4.4 system update, it's fine.
- Unlocked bootloader, it's fine.
- Tried to flash 5.0.1 factory image and again same issue - stuck on google screen.
- Been dicking around the last few hours trying to fix it ended with flashing 4.4.3 again but same issue, I then put the phone into download mode and connect to the computer but I got a green screen something about DemiGod Watchdog HW reset. I did the reset.
- Phone booted up again! Did the 4.4.4 system update and then it started freezing and rebooting withing few seconds of use. Now it's back to being stuck on google screen.
- I am obvious gonna bring it back to the shop now but any idea as to what is happening here?
Click to expand...
Click to collapse
1.I presume the "DemiGod Watchdog HW reset" green screen came up after you gave the phone for HW servicing? If so then they could have knocked around the parts a bit to cause a hardware issue(not sure what causes it)
2.Check the MD5 of the 5.0.1 factory image.
3.Instead of factory image use the OTA zip file and flash in stock recovery.
So I used the LG tool myself to flash the firmware (4.4.3 is the only one available) and it worked fine. Updated to 4.4.4. Fine.
I then adb sideload the 4.4.4 - 5.0.1, and stuck on google logo again .................im pulling my hair out this is so weird.
gamer.11 said:
1.I presume the "DemiGod Watchdog HW reset" green screen came up after you gave the phone for HW servicing? If so then they could have knocked around the parts a bit to cause a hardware issue(not sure what causes it)
2.Check the MD5 of the 5.0.1 factory image.
3.Instead of factory image use the OTA zip file and flash in stock recovery.
Click to expand...
Click to collapse
So I used the LG tool myself to flash the firmware (4.4.3 is the only one available) and it worked fine. Updated to 4.4.4. Fine.
I then adb sideload the 4.4.4 - 5.0.1, and stuck on google logo again .................im pulling my hair out this is so weird.
1) yes this was after.
2)i tried adb sideload.. ill try that good idea.
can't flash ota.zip in recovery. only adb and that didn't work.
think i'm just gonna hang on to 4.4.4 then for now. tried everything.
Just an update. I was running 4.4.4 just fine but the phone froze and went back to the Google screen again.
bump
Might as well rma
Hi,
i got my s6 about a month or two ago, became it from a friend so it was not new and it already had stock 6.0.1 installed.
It worked fine till a week ago or something, then it suddenly started freezing (till either the battery goes out, or i put it out manually with lower+power button) or directly restarting.
At first it happened about one time a day and i din't really wonder, it was rooted, had xposed, u know the instability...
But from day to day it became more frequent until it was about every 10 minutes.
so what troubleshooting have i done till now:
factory reset. It got better and less frequent, but it still happened. After about one day it was at the 10 Minute frequency back.
completely wiped it (twrp) flashed stock 6.0.1 w/ odin. Same result as factory reset
installed xtrestolite. Same result.
Looked if the Problem was a Hardware fault. tried stress testing the GPU the CPU and the RAM. None of these freezed/resarted the phone.
installed another Kernel. Same result
tried to flash stock 5.1.1 w/ odin. Odin gave me an sboot.bin error, excluded the sbin from rom. Odin gave me an CM.bin error., excluded Cm.bin from ROM. Odin gave me no Error, Phone bootlooped at Samsung Galaxy s6 screen.
Tried various variations of 5.1.1 and 6.01 stock roms mixed up. (CM.bin and sboot.bin from 6.0.1, rest from 5.1.1,...) always leading to either bootloop at Samsung screen or Phone force crashing.
I do believe it's a Software fault, as it does work normally for a day or something when factory reset, but as I tried about 1000 things, i'm not sure anymore.
By now I really don't have any more ideas but some questions:
Why can't i flash stock 5.1.1? I'm 100% sure i tried the right csc and BTU.
Is there any custom ROM i could try? The next thing i'll try is flashing CM13, just to try if it force crashes. If it does not it still sucks cos its unstable af.
Are there other non-touchwiz-based ROMs?
Biiig thanks in advance, any help is appreciated. :angel:
Edit: when I try to flash 5.1.1 it also gives me an error on the phone in Download Mode: SW REV. CHECK FAIL. DEVICE: 4 BINARY: 1
Anyone has an Idea what that means?
Edit2: Sometimes when it freezes, the red led is lighting (also till no battery or i manually put it out), By now i'm not sure if it just freezes too (already lighting when the freeze happens) or if it is additional to the freeze.
jaannnis said:
Hi,
i got my s6 about a month or two ago, became it from a friend so it was not new and it already had stock 6.0.1 installed.
It worked fine till a week ago or something, then it suddenly started freezing (till either the battery goes out, or i put it out manually with lower+power button) or directly restarting.
At first it happened about one time a day and i din't really wonder, it was rooted, had xposed, u know the instability...
But from day to day it became more frequent until it was about every 10 minutes.
so what troubleshooting have i done till now:
factory reset. It got better and less frequent, but it still happened. After about one day it was at the 10 Minute frequency back.
completely wiped it (twrp) flashed stock 6.0.1 w/ odin. Same result as factory reset
installed xtrestolite. Same result.
Looked if the Problem was a Hardware fault. tried stress testing the GPU the CPU and the RAM. None of these freezed/resarted the phone.
installed another Kernel. Same result
tried to flash stock 5.1.1 w/ odin. Odin gave me an sboot.bin error, excluded the sbin from rom. Odin gave me an CM.bin error., excluded Cm.bin from ROM. Odin gave me no Error, Phone bootlooped at Samsung Galaxy s6 screen.
Tried various variations of 5.1.1 and 6.01 stock roms mixed up. (CM.bin and sboot.bin from 6.0.1, rest from 5.1.1,...) always leading to either bootloop at Samsung screen or Phone force crashing.
I do believe it's a Software fault, as it does work normally for a day or something when factory reset, but as I tried about 1000 things, i'm not sure anymore.
By now I really don't have any more ideas but some questions:
Why can't i flash stock 5.1.1? I'm 100% sure i tried the right csc and BTU.
Is there any custom ROM i could try? The next thing i'll try is flashing CM13, just to try if it force crashes. If it does not it still sucks cos its unstable af.
Are there other non-touchwiz-based ROMs?
Biiig thanks in advance, any help is appreciated. :angel:
Edit: when I try to flash 5.1.1 it also gives me an error on the phone in Download Mode: SW REV. CHECK FAIL. DEVICE: 4 BINARY: 1
Anyone has an Idea what that means?
Edit2: Sometimes when it freezes, the red led is lighting (also till no battery or i manually put it out), By now i'm not sure if it just freezes too (already lighting when the freeze happens) or if it is additional to the freeze.
Click to expand...
Click to collapse
did you slove you problem? i have sam, but i cant flash nothing with odin, finish flash supceful, but stuck after samsung s6 edge logo, he have black screen with blue light blinking? solution?
Had the same problem on 2 devices. I just fix them flashing the stock rom several times. Just remember to format data and cache after and before flash with odin.
ccalixtro said:
Had the same problem on 2 devices. I just fix them flashing the stock rom several times. Just remember to format data and cache after and before flash with odin.
Click to expand...
Click to collapse
Yea man I would assume this is the only quick fix for this issue tbh.
I'm on cm13 and it's definitely gotta be an issue in Xposed hooks and power switches, because I've seen it happen with Kernel Auditor the cores just FLY thru the roof at bootup, full on max mode, then it reboots lol, and every single time, I was just done either
1; rebooting thru my xposed power menu,
2; rebooting thru the "reboot to system" option thru TWRP,
But man I got SeLinux Enforcing on an AOSP build right now, + other craziness, and my knox counter still tells me im on official binaries haha!
Hi guys,
I got exactly the same problem on an SM-G920F, i already try what @jaannnis do even re-partition on ODIN, im not rooted, not xposed all stock firmeware, i tried 7.0 and 6.0.1 over odin and over smart switch, that work for 12 hours and back to freeze every 10mn.
Im wondering its a batterie problem, or charging circuit issue...
Someone got a solution
Thx in advance
Hi! So, my father's old Samsung Galaxy Tab 2 10.1 P5110 (bought 5 years ago) has gotten into a bootloop. It's an odd case. Basically, it's like the device is completely read-only.
To describe the symptoms:
It boots into the OS, but after 30 seconds or so it suddenly restarts. The device cannot be turned off (it just reboots and reboots and reboots...), so it empties the battery if left unplugged.
I can enter download mode and recovery mode, where the device is stable.
The device is not rooted.
I tried to flash it with TWRP recovery (it worked on my mother's tablet; exact same model, but no problem like this), but the recovery mode is always unchanged. I've flashed with Odin 1.8*, Odin 3.0*, and latest Heimdall; it always completes, but nothing changes. I've learned about having to boot to recovery after flashing due to a script replacing custom recovery, but even when I go directly to recovery mode, it's the same old stock recovery.
I decided to try another approach, by uninstalling apps during those short 30 second intervals of functioning OS; I got to uninstall one app (AVG anti-virus software), but after the reboot, the app was installed again.
I tried to go into recovery mode to do "wipe data/factory reset" and "wipe cache partition", but even that did nothing! Everything is where it was.
I can use ADB in recovery mode, so I tried to see if I could do some damage there, but the tablet is unrooted, and no rooting works either. (Tried rooting with Odin and "apply update from external storage" in stock recovery.) Couldn't find a writable directory to upload a su executable into either.
Just now I finished a 90 minute flashing of some Chilean stock firmware -- although I'm Swedish -- to see if that made things "rewritable", but guess what? All the old apps and files and settings were still there, in Swedish.
At this point I'm starting to suspect that I could hit it with a sledgehammer and it would just return to normal after a minute.
My father is not poor (just a bit cheap!), so buying a new tablet isn't a big deal, but I'm ostensibly a computer engineer...ing student, so it feels like a surrender to leave it unsolved. What might be the problem? Can memory in these devices become read-only due to some hardware fault?
Risky suggestions are welcome. If it's bricked, that's no problem.
EDIT: Whoops! My father ordered a new tablet; I was still going to experiment on the old one, maybe get it working again, but it seems that he went and tried the sledgehammer mode on it. But what happened is still an open question.
I bricked my GT-P3113 long ago, and flashed the stock rom a couple days ago. I rooted using a CF-AutoRoot package, and flashed TWRP using Odin, thinking that I could go and flash LineageOS and Gapps. Before doing that, I tried making a backup. I left it for about an hour backing up to my SD card, and came back with the progress bar all the way, with no percentage, and not being able to cancel. There's no title box in sight, and all it says is "Simulation Partition" under it. I rebooted, and went back to the recovery. I decided to say screw it, and tried flashing LOS and then Gapps. I rebooted after, and nothing happened. It booted back into normal Android 4.2.2, and i've tried many more times to get this to work. Only strange thing that I've found is that when I enter download mode using the key combo ( PWR + VolDown, ) it shows the warning message about a Custom OS, and a small text in the top left that says "ODIN MODE" and the flash count (which is currently around 8 or 9, after many tries.) When I enter download mode through TWRP, it shows no text. I've tried reflashing TWRP, and reflashing to older versions, but the same thing happens again. Maybe I rooted incorrectly or something, but i'm honestly at a loss right now. Maybe flashing with Odin3 v3.12 caused it, but I really have no idea. Any help or if you could point me to another thread, would be very much appreciated.
Boot your 4.2.2 and download something or take a picture. If it's gone after a reboot your emmc became read only.
Most 16 GB models use a known faulty MAG2GA emmc.
You could try to find someone who can flash an updated emmc firmware, but the issue will be there again in most cases and a new emmc will be needed.