Help - Rebooting in each 30s After Android loads - Galaxy Grand Duos i9082 Q&A, Help & Troubleshootin

Hello all, good evening.
I own a I9082L and was warning from Samsung about some update in my Android Version.
I agreed and did the update.
But after it, my SGD always reboot 30 seconds after Android load.
I mean, tha Android appears to load right and I can use all apps, but 30 seconds after, my GDD reboots. by it self.
I can use ODIN and TWR.
I already flash others Roms using TWR and ODIN, but no success.... rebooting again after 30 seconds.
I did Full Wipe, formated my SD Card.
I read on other thread that it can be Kernel or Partition problem.
So, I flashed some Stock Kernel that I found in this Forum by K2wl.
For the Partition problem I need a Bin File, and I canĀ“t find one.
Any sugestions???
Beste regards.
Marcos

This is in the wrong section.
Sent from my GT-I9082 using Tapatalk 2

Related

Unbrickable my ***...

ok..
so im stuck.. tried to reflash the stock DL17, using the downloads provided, including PIT (repartition checked).. via ODIN 1.3 to clear back to stock..
after flashing, the phone booted to DL17 - sort of.. no data was gone, all the wife's programs were there, and i got into a FC hell during setup. ACORE, GAPPS, pretty much every program.
then re-odined the DL17 by itself, no repartition, no pit..
now i cant get anything to flash...ODIN tells me it flashes fine, normal on there.. the phone does not hit the samsung logo.. goes straight to the android system recovery and i have NO hotkeys to select anything..
it says at the bottom..
"e:can't mount /dev/block/st111" (twice)
then under that it says
"update.zip gone"
ive tried every combo from the dev tools thread, and all flash fine via ODIN but go straight back to the android recovery, and i cant select anything..
anyone have any creative ideas?
First, "bricked" is used for when your phone does nothing.
Second, this isn't a development post. And read through stickies in general forum. This problem has been solved. Mostly from Irc.
Sent from my SCH-I400 using xda premium
geez im just going to leave this one alone lol
completly correct..my fault..i wasnt paying attention to where i was posting because of my frustration level..
and for the record i tried the heimdall magic fix in general section and it didnt work. phone starts to boot then shuts off. have to pull battery to get power. 3 finger recovery does not work either..just flashes the screen with samsung and dies again.
ciscogee said:
First, "bricked" is used for when your phone does nothing.
Second, this isn't a development post. And read through stickies in general forum. This problem has been solved. Mostly from Irc.
Sent from my SCH-I400 using xda premium
Click to expand...
Click to collapse
MIUI 1.12.9 RickS :: Glitch V13 :: ED05 Radio
Not sure txwolf and tb101 are resident fixers on that. Try to make Irc apmt. Good luck.
Moderator. Can you move post to general?
Sent from my SCH-I400 using xda premium
The fact that no data was gone the first time interests me.... Was it definitely a full system/data/cache/everything else tar?
I would download the EC07 full package, repartition, then try my magic fix....
Sent from my SCH-I400 using xda premium
trailblazer101 said:
The fact that no data was gone the first time interests me.... Was it definitely a full system/data/cache/everything else tar?
I would download the EC07 full package, repartition, then try my magic fix....
Sent from my SCH-I400 using xda premium
Click to expand...
Click to collapse
if i remember correctly, on irc, he said he flashed a rom that wasn't meant for the continuum, rather another galexy device..
well you surely are not bricked. but the cache partition is in deed messed up. (stl11 refers to the cache partition) unfortunatly, it seams as though you have done just about everything.
Try loading up heimdall and load only the pit, the kernel(imnuts hacked kernel is what i recomend using), and the modem/radio(ec07).
This should fix any partition issues. It will format the partitions in place where they should be but it will not write to the partitions. What i recommend next is different from most other things.
Hopefully if all is well, when you install the kernel it should fix the issues with the boot loader. boot into CWM if possible. Now try and flash a version of ec07.
If you are only receiving the stl11 issue all other partitions should be good. once the kernel and everything else is in place and you flash the system it should be good and boot up... hopefully
mrjake1970 said:
completly correct..my fault..i wasnt paying attention to where i was posting because of my frustration level..
and for the record i tried the heimdall magic fix in general section and it didnt work. phone starts to boot then shuts off. have to pull battery to get power. 3 finger recovery does not work either..just flashes the screen with samsung and dies again.
MIUI 1.12.9 RickS :: Glitch V13 :: ED05 Radio
Click to expand...
Click to collapse
Starts to boot? Where does it get to? Do you get into recovery, at all? Also, do you get samsung logo? Before you said it was booting straight into recovery. Has that changed after magic fix? I'd recommend doing a full ec07 stock with repartition in heimdall.
Thank you all..
I havent been to the IRC yet. Been trying everything else.
Here is the full story of the phone...
1. When the first ROM came out for this, I flashed it. Something (no idea what) borked it during the flash, and the phone wouldn't turn on. I could only get to CWM. I would try and wipe data, nothing would happen. I got a walk through from someone here on other stuff to try, which included mounting all the drives, and wiping them. I have never been able to mount (manually) any drive since - but it got me running again.
I was getting errors in CWM constantly.
2. No matter what i flash, or what (or how many times) i wipe data, datadata, system, ect.. whenever i flash anything the data from the old ROM remains on the phone and i end up in force close hell on the new ROM..
3. i probably the most stable ROM was EC03.. it worked but after a while would start random rebooting 4-5 times a day. ..so then wife wanted to try MIUINA.. we had her on V4 for a while. Then with upgrade to V5, things went bad again. I couldn't wipe data, ODIN the stock EC07 worked once, but the old data remained (all her settings/programs were force closing and old wallpaper remained.) then after that, I tried to ODIN MIUINA v5 again, ODIN said it worked, phone bootlooped into "stock" recovery, but gave the errors i posted above. no keypresses avail. t
tried heimdall fix all solution, now it boots to the SAMSUNG screen and hangs then shuts off, and wont turn on until a battery pull.
i cant 3 finger to recovery (wont let me, just hangs at samsung screen and then dies after about 2 minutes)
right now, i can get ODIN to work about half the time with the phone "taking" the flash, will get to the verizon logo and while building the dalvik, it dies, shuts off and then wont boot past samsung logo.
im going to try and see if i can get ODIN to let me flash CWM and get to cyan recovery and try a nandroid restore if it will let me.
can i use the DL17 stock MD5 file in heimdall? this is my first time using heimdall.. dont i need other files?
mrjake1970 said:
Thank you all..
I havent been to the IRC yet. Been trying everything else.
Here is the full story of the phone...
1. When the first ROM came out for this, I flashed it. Something (no idea what) borked it during the flash, and the phone wouldn't turn on. I could only get to CWM. I would try and wipe data, nothing would happen. I got a walk through from someone here on other stuff to try, which included mounting all the drives, and wiping them. I have never been able to mount (manually) any drive since - but it got me running again.
I was getting errors in CWM constantly.
2. No matter what i flash, or what (or how many times) i wipe data, datadata, system, ect.. whenever i flash anything the data from the old ROM remains on the phone and i end up in force close hell on the new ROM..
3. i probably the most stable ROM was EC03.. it worked but after a while would start random rebooting 4-5 times a day. ..so then wife wanted to try MIUINA.. we had her on V4 for a while. Then with upgrade to V5, things went bad again. I couldn't wipe data, ODIN the stock EC07 worked once, but the old data remained (all her settings/programs were force closing and old wallpaper remained.) then after that, I tried to ODIN MIUINA v5 again, ODIN said it worked, phone bootlooped into "stock" recovery, but gave the errors i posted above. no keypresses avail. t
tried heimdall fix all solution, now it boots to the SAMSUNG screen and hangs then shuts off, and wont turn on until a battery pull.
i cant 3 finger to recovery (wont let me, just hangs at samsung screen and then dies after about 2 minutes)
right now, i can get ODIN to work about half the time with the phone "taking" the flash, will get to the verizon logo and while building the dalvik, it dies, shuts off and then wont boot past samsung logo.
im going to try and see if i can get ODIN to let me flash CWM and get to cyan recovery and try a nandroid restore if it will let me.
can i use the DL17 stock MD5 file in heimdall? this is my first time using heimdall.. dont i need other files?
Click to expand...
Click to collapse
You will need the dl17 pit file. And to use heimdall, you need to break the tar down to its component files. I use 7zip for that, but winrar works too. I'll be in irc in 30 minutes, if you want to run through it.
thank you Txwolf1980 for the offer of an IRC chat, seriously..i just got this late this afternoon..i had to leave friday evening, and didnt get back until late.
i finally got the thing to boot..but it was out of total desperation, i started (logically, yet with reckless abandon, since I had nothing to lose at this point) flashing crap..
here is what i did to get this puppy running again..
ODIN, heimdall and CWM were doing nothing for me..no boot, no recovery, no 3 finger..nothing... still couldnt even boot into original system recovery..
since i have a fascinate, i had a few beers and decided to flash cwm4 (for the MTD ROMS) just to see what would happen...tried a 3 finger and it flickered the screen as if it *wanted* to go to recovery but didnt go into recovery, just kicked me back to the samsung screen..however i took the flicker as a good sign, maybe that jogged something somewhere..
i immediately reflashed the CWM adryn that is used for the continuum.. and 3 fingered after ODIN rebooted..
PROFIT! i now had the softkeys back to select the update zip for cyan recovery..
got into cyan recovery and went to mounts and storage, and mounted everything, wiped them (except for sd card) then unmounted them all and wiped them all again..
it took the commands.. i wiped the snot out of everything i could find to wipe.. i went back to install zip from SD card and flashed stock EC03 that i put on there months ago.. and hit reboot..
PROFIT! it booted.. it was all FUBAR, had screen flickering funny, and key presses were delayed by 3-4 seconds.. the phone was functional, calls, text, market all worked.. however, when the phone was powered off, it returned to stock (like a data wipe) upon restart. which was really weird..
f-it, i was booted.. and it was functional.. now to fix this for good...
i then did some research here, and found i was using the wrong PIT and EC07 ODIN files when flashing in ODIN.. found the right ones...and pulled battery, went to download mode, and flashed EC07 leak (production) with the I500 PIT, repartition checked..and ODIN immediately applied the PIT and flashed EC07...
the wifes phone is now running like a champ.. its not rooted, and is binged and bloated, but its looking like its completely fixed.. time will tell, but its been running for the last 6 hours now perfectly. I even rebooted 2x to make sure the changes/data/downloads stuck this time, and they did.
the wife threatened to snip off my giblets if i attempted to root it or mess with it anymore i tried to remind her that she is the one who liked the "cool other rom-thingies" but that didnt fly.. so i handed her the phone and said have fun....
sincere and heartfelt thanks to all who pitched in to the conversation to help... i hope that this post will help others who think their continuum is completely fubar..
im done messing with her phone. ill head back to flopping between ICS and MIUI on my fascinate where i know more abotu what im doing.. i haven't turned my fassy into a door stop in almost a year of HEAVY flashing..

Samsung Logo Keeps Flashing, wont boot HELP

Never thought I'd be the one to create a thread like this..
After I flashed the OKV4 ROM, strange things started to happen (this was after a full wipe). Apps kept force closing, etc. Later that day, when I picked up my phone, I saw the samsung logo flashing over and over. Making me unable to enter recovery.
Download mode still worked though and I proceeded to flash a stock firmware via ODIN. This did not help. Oh, and the Odin flash succeeded, without rebooting my phone though...
So, I'm still stuck with my phone which can't seem to get out of this strange loop.
HELP :C
I remember reading somewhere here that if you have flashed a diff FW now and then a possibility the last recent kernel is still in the system folder etc....this is maybe the cause of the bootloop.
Since you had confirmed going to download mode is possible..this may work logically... Why not do the following :
Get your phone rooted via Recovery (there is a thread here by The-E)..Once done flash arco68's CWM Recovery....Boot to recovery n do this :
Factory Format....Wipe n Clear including Delvik...Then go to Mount n Storage wipe every single folder...System...Data...Etc (this will wipe every single data left behind but I assure you the CWM will not be wiped) once done reboot n put the device into DL mode and use Odin to flash back to the stock FW.
From this moment the recovery will be replaced by stock version and the stock FW will be restored....once it boot up..Walla as I had done this over two times :
Best of Luck !!
Sent from my GT-I8150 using xda premium
I think you misunderstood me :/
This isn't the ordinary bootloop where the boot animation plays. It resets literally 2 seconds after starting. This makes me unable to enter the recovery at all. Thanks for the effort tho.
Tl;dr:I can not enter recovery mode.
treUse said:
I think you misunderstood me :/
This isn't the ordinary bootloop where the boot animation plays. It resets literally 2 seconds after starting. This makes me unable to enter the recovery at all. Thanks for the effort tho.
Tl;dr:I can not enter recovery mode.
Click to expand...
Click to collapse
Hi Bro...
I already discuss it in this Tread couple a days a go
You not alone bro
I ask The-E to mention all Wonder user to get safety flashing
Until this time we didn't get way to fix it yet

[Q] Loads of Problems (rooted, unrooted, firemwares, flash, stuck on logo screen)

I'm having one hell of a time with this tablet. This is pushing a month and I'm still not satisfied with my tablet.
Tonight I finally tracked down what I had hoped was a stock firmware for my tablet. Halfway through the download it timed out and when I went to download it again, the same thing happened.
So I tried to take my tablet that isn't "properly rooted" anymore and use Odin 9, instead of Odin 10, and place kitkat on my device rather than be stuck with Lollipop 5.0.2. All of this because The Sims Freeplay app isn't working and I can't find another soul on the face of the earth who can give me an answer to why this is happening.
Now I'm stuck on the samsung logo. I managed to get it back in download mode and that's where I flashed Lollipop 5.0.2 through Odin 10. I figured that would solve my problem. It didn't, but at least I got TWRP back on my device.
I never recovered anything that came with my tablet. I did not think I'd ever go back to unroot nor did I know how to back it up in the first place. So there's nothing in my recovery I can boot from. So what I did was I came back here and I downloaded the recovery for TWRP. I flashed it from my SD card, it told me it was successful... now what? I've rebooted and my device still loads to the samsung logo...and just stays there. The little confetti animation happens behind the logo, but that's it. It doesn't turn off. It doesn't reset itself.
CAN SOMEONE PLEASE TELL ME WHAT I'M DOING WRONG?!
I've already voided the warranty on this device and I regret almost daily that I decided to root in the first place. I say this only because I think rooted devices are top-notch, but I haven't been having very much luck with them. It took me a week to root. When I finally rooted then my favorite app game stopped working. Then I figured I could flash the stock firmware easily (but it seems like every place I go to find kitkat or even stock lollipop I can't find or I do, but files are corrupt or sites are full of ads).
I can't use my device at all now except click around in TWRP which isn't doing me any good.
I just want my tablet back. I spent 500 dollars on this thing and I haven't had time to even enjoy it. It's only two months old.
Please. Again. Someone HELP me. I want to figure this out and I don't want to accept that I bricked my device because I've watched plenty of videos on youtube and people are stuck with a phone that's resetting and all they do is fix it right there in front of my eyes.
Why can't I fix this? What is it that I'm not doing properly?
geekery15 said:
I'm having one hell of a time with this tablet. This is pushing a month and I'm still not satisfied with my tablet.
Tonight I finally tracked down what I had hoped was a stock firmware for my tablet. Halfway through the download it timed out and when I went to download it again, the same thing happened.
So I tried to take my tablet that isn't "properly rooted" anymore and use Odin 9, instead of Odin 10, and place kitkat on my device rather than be stuck with Lollipop 5.0.2. All of this because The Sims Freeplay app isn't working and I can't find another soul on the face of the earth who can give me an answer to why this is happening.
Now I'm stuck on the samsung logo. I managed to get it back in download mode and that's where I flashed Lollipop 5.0.2 through Odin 10. I figured that would solve my problem. It didn't, but at least I got TWRP back on my device.
I never recovered anything that came with my tablet. I did not think I'd ever go back to unroot nor did I know how to back it up in the first place. So there's nothing in my recovery I can boot from. So what I did was I came back here and I downloaded the recovery for TWRP. I flashed it from my SD card, it told me it was successful... now what? I've rebooted and my device still loads to the samsung logo...and just stays there. The little confetti animation happens behind the logo, but that's it. It doesn't turn off. It doesn't reset itself.
CAN SOMEONE PLEASE TELL ME WHAT I'M DOING WRONG?!
I've already voided the warranty on this device and I regret almost daily that I decided to root in the first place. I say this only because I think rooted devices are top-notch, but I haven't been having very much luck with them. It took me a week to root. When I finally rooted then my favorite app game stopped working. Then I figured I could flash the stock firmware easily (but it seems like every place I go to find kitkat or even stock lollipop I can't find or I do, but files are corrupt or sites are full of ads).
I can't use my device at all now except click around in TWRP which isn't doing me any good.
I just want my tablet back. I spent 500 dollars on this thing and I haven't had time to even enjoy it. It's only two months old.
Please. Again. Someone HELP me. I want to figure this out and I don't want to accept that I bricked my device because I've watched plenty of videos on youtube and people are stuck with a phone that's resetting and all they do is fix it right there in front of my eyes.
Why can't I fix this? What is it that I'm not doing properly?
Click to expand...
Click to collapse
I just skimmed through all this reading, so I may have missed a few things. The thing I didn't see if factory resetting. You need to factory reset in twrp. Just go to wipe and factory reset. Now reboot and wait at least 20 minutes as it does take quite a while to boot.
If doesnt do, transfer a custom stock based ROM for your device (any KK ROM should do) to your SD card. Factory reset in twrp and flash ROM. Now reboot and wait.
Typically, flashing with Odin takes 20 minutes to boot up for the first time. Just be sure you factory reset.
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
I just skimmed through all this reading, so I may have missed a few things. The thing I didn't see if factory resetting. You need to factory reset in twrp. Just go to wipe and factory reset. Now reboot and wait at least 20 minutes as it does take quite a while to boot.
If doesnt do, transfer a custom stock based ROM for your device (any KK ROM should do) to your SD card. Factory reset in twrp and flash ROM. Now reboot and wait.
Typically, flashing with Odin takes 20 minutes to boot up for the first time. Just be sure you factory reset.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
Ok. I just factory resetted. Then I went to reboot and clicked "system". Now it restarted and brought me back to the same samsung logo... do I wait 20 minutes on that screen?
geekery15 said:
Ok. I just factory resetted. Then I went to reboot and clicked "system". Now it restarted and brought me back to the same samsung logo... do I wait 20 minutes on that screen?
Click to expand...
Click to collapse
Yep.
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
Yep.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
By any chance does it take longer than 20 minutes?
It's been 28 minutes and I'm still on the Samsung logo.
geekery15 said:
By any chance does it take longer than 20 minutes?
It's been 28 minutes and I'm still on the Samsung logo.
Click to expand...
Click to collapse
Sometimes. Try and wait 10 more minutes.
If it doesn't boot, I think you may have to flash a custom stock based ROM and flash it from your SD card in twrp.
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
Sometimes. Try and wait 10 more minutes.
If it doesn't boot, I think you may have to flash a custom stock based ROM and flash it from your SD card in twrp.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
Custom Stock Based Rom? Does that mean I'll push myself further away from a stock firmware? Also... where do I find one and are there instructions for it? I thought roms were firmwares up until like 4 hours ago and I've been reading of roots for a little over a month now.
I see you've got the same tablet. By any chance are you running 5.0.2 lollipop and do you happen to know having a rooted device is the reason why The Sims Freeplay won't get past it's splash screen or if it's the app itself and it's newest update that made it wiggy?
I'll flash whatever at this point, but my main reasons for continuing to mess with my tablet was because of not being able to play the sims on there. Every other game I play works.
geekery15 said:
Custom Stock Based Rom? Does that mean I'll push myself further away from a stock firmware? Also... where do I find one and are there instructions for it? I thought roms were firmwares up until like 4 hours ago and I've been reading of roots for a little over a month now.
I see you've got the same tablet. By any chance are you running 5.0.2 lollipop and do you happen to know having a rooted device is the reason why The Sims Freeplay won't get past it's splash screen or if it's the app itself and it's newest update that made it wiggy?
I'll flash whatever at this point, but my main reasons for continuing to mess with my tablet was because of not being able to play the sims on there. Every other game I play works.
Click to expand...
Click to collapse
The only thing I can suggest is download this to your SD card and flash it in twrp. http://forum.xda-developers.com/showthread.php?p=56345482
The Sims may not work because its uncomptiple with lollipop.
Simply, hit wipe in twrp, hit advanced wipe, and tick system, dalivk and cache. Then go back and install the Cm11 zip and reboot. Hopefully it gets you booting
Sent from my SM-T800 using Tapatalk
I'd actually flash this as its more like stock just debloated.
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
You need to wipe system, dalvik, cache and data then Install via twrp.
Wait at least 10 to 15 mins after install for initial boot up.
For future reference whenever you go back to kitkat from lollipop you need to wipe the data and cache partition first.
By the way some apps and games do not work on rooted devices for security reasons.
DUHAsianSKILLZ said:
Yep.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
DUHAsianSKILLZ said:
Sometimes. Try and wait 10 more minutes.
If it doesn't boot, I think you may have to flash a custom stock based ROM and flash it from your SD card in twrp.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
ashyx said:
I'd actually flash this as its more like stock just debloated.
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
You need to wipe system, dalvik, cache and data then Install via twrp.
Wait at least 10 to 15 mins after install for initial boot up.
For future reference whenever you go back to kitkat from lollipop you need to wipe the data and cache partition first.
By the way some apps and games do not work on rooted devices for security reasons.
Click to expand...
Click to collapse
I understand that. That is why I clicked unroot in supersu and tried the game app, but it still wouldn't work. On my galaxy note 3 I run 5.0 lollipop and my game works fine. My phone isn't rooted and I never decided to root it and then unroot it.
Is an app smart enough to know when a device has been rooted and if are those that hack their actual game on rooted devices uses cloak or xposed or both to by pass their root?
I rather be unrooted for the sake of the game, but how does one find the stock firmware? Or is it not possible at this point?
Sorry for any confusion.
ashyx said:
I'd actually flash this as its more like stock just debloated.
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
You need to wipe system, dalvik, cache and data then Install via twrp.
Wait at least 10 to 15 mins after install for initial boot up.
For future reference whenever you go back to kitkat from lollipop you need to wipe the data and cache partition first.
By the way some apps and games do not work on rooted devices for security reasons.
Click to expand...
Click to collapse
Okay. I installed or flashed ironrom to my tablet from twrp. i followed the directions it told me and I decided to pick the regular rom above the custom one that was close to stock. Then it told me that it was going to reboot; which it did. When it came back it got stuck on the same samsung loading screen so I powered it off, went back into TWRP (because powering off now isn't possible, more like restart) and I went to "Reboot " and then I clicked "power off".
I guess I'll be waiting for 10 to 15 minutes.
I Pray I did this correctly.
geekery15 said:
Okay. I installed or flashed ironrom to my tablet from twrp. i followed the directions it told me and I decided to pick the regular rom above the custom one that was close to stock. Then it told me that it was going to reboot; which it did. When it came back it got stuck on the same samsung loading screen so I powered it off, went back into TWRP (because powering off now isn't possible, more like restart) and I went to "Reboot " and then I clicked "power off".
I guess I'll be waiting for 10 to 15 minutes.
I Pray I did this correctly.
Click to expand...
Click to collapse
Thanks for all the help! I'm finally back to where I want to be and the ss freeplay seems to be working. I can't thank you both enough.
geekery15 said:
Thanks for all the help! I'm finally back to where I want to be and the ss freeplay seems to be working. I can't thank you both enough.
Click to expand...
Click to collapse
Why did you reboot back into twrp? You should have just let it do its thing after it rebooted.
So for any others that may happen upon this thread.
What was your solution?
ashyx said:
Why did you reboot back into twrp? You should have just let it do its thing after it rebooted.
So for any others that may happen upon this thread.
What was your solution?
Click to expand...
Click to collapse
I did because I thought it had to be shut down before I powered it on and waited. I realized afterwards that you probably meant to just let it sit for 10 to 15 minutes.
Are you asking me my solution or other peoples solution?
geekery15 said:
Are you asking me my solution or other peoples solution?
Click to expand...
Click to collapse
Your solution.
cant reboot after failed encryption
I was trying to encrypt my galaxy tab s, which is rooted and has lollipop 5.0. Afrer reading encryption failed. I tried to reboot in recovery via twrp. My device doesn't reboot, it just acts like its going thru the motions. Only to return to twrp recovery menu. How do I reboot the system clearing the failed encryptions. I am a noob and any suggestions would be much appreciated.
You will have to go into recovery and wipe the data and cache partition then reboot.
It may take a while to boot up after that.
Well I thought my solution was using IronRom... but i'm not too sure now.
I just got back from work and I went to turn on my tablet and it took me to the same loading screen and then after about 5 minutes it tells me that the system can't respond. It asks me to click "ok" or "wait" ... clicking either just turns my tablet off.
Now the screen has dimmed. It's turning on when it wants and sometimes it'll show me the time in the upper right hand corner, but it won't let me do anything because it's a black screen.
What does all of this mean?
I just noticed if I click the "power button" it just flashes my tablet desktop then goes back to black, but it shows me the battery percentage and the time in the upper right hand corner...
smt 800 stuck in logo
SAMSUNG GALAXY TAB S 10.5 WIFI WHAT IT CAN AND CANT DO
i HAD ROOTED AND INSTALLED LOLLIPOP 5.0 WITH SUPER SU AND TWRP RECOVERY.
I THEN TRIED TO ENCRYPT WHICH FAILED.
MY DEVICE SAID TO REBOOT SYSTEM AND THEN TRY TO ENCRYPT AGAIN. AFTER REBOOTING, MY DEVICE IS STUCK WITH (logo screen)THE SAMSUNG TAB S NAME AT THE TOP OF THE SCREEN AND ANDROID ON THE BOTTOM. I then rerooted with cf auto root thru odin. Odin and my tablet went thru the motions. When everything was complete and device should have initialize, but didn't. This part of the process didn't happen.
I am able to go into DOWNLOAD MODE and can get to manual mode, but I seem to have lost recovery. Here is the info.
android system recovery <3e>
kot49h_t800xxu1af8..
the binary reads: samsung official
system status: custom
Do you have any suggestions.

Help Me With My i9082 Keep Restart Every 5-10 Sec With Every Stock/Custom Rom

Hi everyone my phone keep restart every 10 sec or less more on different custom roms. I tried to flash stock rom it dosnt fix issue, tried many many custom roms still dosnt fix,clear cache/data/ still nothing. it start and then after 10 15 sec it hang/unresponsive and then restart. It dosnt matter you do something or not... it will restart and couple sec before like 2-3 Sec it get freeze/hang/unresponsive and restart. help me out plzzzz.
chappie92k said:
Hi everyone my phone keep restart every 10 sec or less more on different custom roms. I tried to flash stock rom it dosnt fix issue, tried many many custom roms still dosnt fix,clear cache/data/ still nothing. it start and then after 10 15 sec it hang/unresponsive and then restart. It dosnt matter you do something or not... it will restart and couple sec before like 2-3 Sec it get freeze/hang/unresponsive and restart. help me out plzzzz.
Click to expand...
Click to collapse
Did you try to repartition your phone?
No i didnt... I was on some custom rom.. Running fine with no issues and i thought to go back to stock. So i flash stock rom in BL option in odin,instead of PDA. I guess since then everything start going wrong. Also i flash CWM in BL instead of PDA in odin. Then i tried many roms i doesn't fix issue. I tried to flash full stock rom with BL,PDA,CSC,PHONE in odin it doesn't fix. Now if partition is issue how can o check or fix or reset it. Its ext4 this time as shown while i flash rom in CWM.
Same thing happening with me also...I was on LOS 7.1.2 and it all started there.

Note 4 N910P rooted- crash followed by phone being stuck on logo

So i got my note 4 sprint variant a few weeks ago. Rooted it using CF auto root, installed twrp 3.1.0 and installed cm13 on it. It ran fine for a few days then out of nowhere it would shut off and when i tried rebooting it, it would get stuck on logo screen, the blue led would just stay on and then nothing. I thought it maybe the rom so i tried a deoxed rom and the same thing happened. 3 more roms later i kept getting the random crash and then not being able to go past the boot screen.
I don't have xposed installed, or magisk. Just plain root. i am forced to make daily backups using twrp just in case my phone blacks out again. Has this problem happened to any of you guys before? Is there a fix or do i have to break the receipt out?
Personally, I've read about issues on CM and lack of SPen features on CM so I didn't try CM.
But when I ran CM on another Samsung S model phone, I did run CM but always wiped internal memory when switching because app data isn't compatible between the two OS platforms.
Did you wipe internal memory? Have you tried modified stock ROMs? UN7 with modset is a well featured ROM based on Note7. And stable too. Currently using Beastmode kernel but there's a kernel being developed for it.
Sent from my SM-N920P using Tapatalk
mrblack92 said:
So i got my note 4 sprint variant a few weeks ago. Rooted it using CF auto root, installed twrp 3.1.0 and installed cm13 on it. It ran fine for a few days then out of nowhere it would shut off and when i tried rebooting it, it would get stuck on logo screen, the blue led would just stay on and then nothing. I thought it maybe the rom so i tried a deoxed rom and the same thing happened. 3 more roms later i kept getting the random crash and then not being able to go past the boot screen.
I don't have xposed installed, or magisk. Just plain root. i am forced to make daily backups using twrp just in case my phone blacks out again. Has this problem happened to any of you guys before? Is there a fix or do i have to break the receipt out?
Click to expand...
Click to collapse
Try Lineage 14.
https://forum.xda-developers.com/showthread.php?p=70508450
Sent from my trltespr using XDA-Developers Legacy app
samep said:
Personally, I've read about issues on CM and lack of SPen features on CM so I didn't try CM.
But when I ran CM on another Samsung S model phone, I did run CM but always wiped internal memory when switching because app data isn't compatible between the two OS platforms.
Did you wipe internal memory? Have you tried modified stock ROMs? UN7 with modset is a well featured ROM based on Note7. And stable too. Currently using Beastmode kernel but there's a kernel being developed for it.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Thanks I will give it a try when i get the chance this weekend. It's so strange out of all the devices i've rooted this is the only one to give me this crazyness. Yes always wipe internal, system, cache, and dalvik cache.
Even on stock it gave me the random crash and no boot past the samsung logo. I think it's safe to say that this thing is ****ed lol
mrblack92 said:
Even on stock it gave me the random crash and no boot past the samsung logo. I think it's safe to say that this thing is ****ed lol
Click to expand...
Click to collapse
Though not normal, these non boots on Samsung logo should be corrected by wiping dalvik-cache or factory reset. If not, something may be wrong.
That said, the initial boot after flash to optimize applications can easily take more than 12 minutes. Much longer if many apps are to be optimized. Shorter if factory reset is applied (less user apps to optimize but still has some optimization to do).
Are you familiar with reactivation lock or eMMC failure? When you flash stock tar in Odin, check your phone's display and Odin log for errors. A failed boot may boot to download mode and indicate an eMMC error.
Outside of those issues, I'd say wipe everything but ext sdcard, pull the battery, wait at least 30 seconds while discharging the power circuit with power button press and hold (not too firmly). Reinstall battery and boot directly to download mode and flash the stock tar in Odin using Odin defaults. Let it auto reboot. Note any failures.
Alternately, you can remove the ext sdcard or delete the Android folder on it. A functional phone should boot rather quickly with the wipes and no errors; shouldn't stay at the Samsung logo very long but still needs to initialize and find network and start the auto start apps. But prior to initial boot, you should also see it make a brief stop in stock recovery to initialize csc before booting system.
Sent from my SM-N920P using Tapatalk
samep said:
Though not normal, these non boots on Samsung logo should be corrected by wiping dalvik-cache or factory reset. If not, something may be wrong.
That said, the initial boot after flash to optimize applications can easily take more than 12 minutes. Much longer if many apps are to be optimized. Shorter if factory reset is applied (less user apps to optimize but still has some optimization to do).
Are you familiar with reactivation lock or eMMC failure? When you flash stock tar in Odin, check your phone's display and Odin log for errors. A failed boot may boot to download mode and indicate an eMMC error.
Outside of those issues, I'd say wipe everything but ext sdcard, pull the battery, wait at least 30 seconds while discharging the power circuit with power button press and hold (not too firmly). Reinstall battery and boot directly to download mode and flash the stock tar in Odin using Odin defaults. Let it auto reboot. Note any failures.
Alternately, you can remove the ext sdcard or delete the Android folder on it. A functional phone should boot rather quickly with the wipes and no errors; shouldn't stay at the Samsung logo very long but still needs to initialize and find network and start the auto start apps. But prior to initial boot, you should also see it make a brief stop in stock recovery to initialize csc before booting system.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I recieved no errors on my phone screen during the flash. It always passed right through, although one time it did fail due to a faulty usb cable. Other than that once incident I've had no issues with flashing tars through odin. Thanks for your help! really appreciate. I will give the the battery discharge a shot when i get the chance.

Categories

Resources