Can someone help me? - Galaxy S6 Q&A, Help & Troubleshooting

I read in the thread guide that i should do this. just ignore it if i'm wrong.
Device: Samsung galaxy s6 edge SMG925f
Rom name: idk i can't even go to the home screen
Rom veersion: idk i can't evn go to the home screen
Build number: idk but i flashed an md5 file with the name G925FXXS5DQJ1_G925FOLB4DQJ1_G925FXXU5DPL6_HOME.tar
Rooted:????
no mods, i remember flashing twrp though
Okay to the problem,(sorry for my bad english) so my mom gave me a broken galaxy s6 edge if i fixed it then it's mine! but the problem is i can't ,it's been seven days since the first day i'm fixing this device.
at first it was stuck in a bootloop and 98% chance it will freeze during booting when it freezez it sometimes create lines of corrupted pixels i just press vol down + power to reboot.
I researched how to fix it and did a factory reset and wipe cache but still not working.
So i figured out i need to download a firmware to fix, so i downloaded one and it took two days because of the slow free download and frequent fails. i tried to flash it and i realised i downloaded the wrong one, so i downloaded one again and it took me a day. after that i tried to flash it using odin 3.12 and it fails during flashing 99% percent of the time because of the constant freezez and i need to press vol down + power for 1 minute for it to reboot now if i'm very lucky the flash will complete BUT during installation it froze at 24% so i flashed it again for the second time, that took 8 hours. and suddenly it to complete the flashing and installation BUT, upon completion it sudddenly says something like "No drk please install drk" i was completely infuriated and upon hours of research i found a tutorial where i need to flash auto chainfire so i did it, and it doesn't work it just cause bootloops
so after that i researcheed again and found this file kernel_G925f sforum i flashed it. and upon reboot it says 'Kernel is not seandroid enforcing' ,and it's not yet fixed it just cause bootloops and sometimes freeze on unfinished samsung logo animation.
I am now trying to flash firmware again to see if it could get fixed. every hour i am losing hope.
If theres any tips i could get that would be good.
If i fixed this s6 it'll be the biggest achievement of my life and own my first working smartphone.

japiestjapi said:
I read in the thread guide that i should do this. just ignore it if i'm wrong.
Device: Samsung galaxy s6 edge SMG925f
Rom name: idk i can't even go to the home screen
Rom veersion: idk i can't evn go to the home screen
Build number: idk but i flashed an md5 file with the name G925FXXS5DQJ1_G925FOLB4DQJ1_G925FXXU5DPL6_HOME.tar
Rooted:????
no mods, i remember flashing twrp though
Okay to the problem,(sorry for my bad english) so my mom gave me a broken galaxy s6 edge if i fixed it then it's mine! but the problem is i can't ,it's been seven days since the first day i'm fixing this device.
at first it was stuck in a bootloop and 98% chance it will freeze during booting when it freezez it sometimes create lines of corrupted pixels i just press vol down + power to reboot.
I researched how to fix it and did a factory reset and wipe cache but still not working.
So i figured out i need to download a firmware to fix, so i downloaded one and it took two days because of the slow free download and frequent fails. i tried to flash it and i realised i downloaded the wrong one, so i downloaded one again and it took me a day. after that i tried to flash it using odin 3.12 and it fails during flashing 99% percent of the time because of the constant freezez and i need to press vol down + power for 1 minute for it to reboot now if i'm very lucky the flash will complete BUT during installation it froze at 24% so i flashed it again for the second time, that took 8 hours. and suddenly it to complete the flashing and installation BUT, upon completion it sudddenly says something like "No drk please install drk" i was completely infuriated and upon hours of research i found a tutorial where i need to flash auto chainfire so i did it, and it doesn't work it just cause bootloops
so after that i researcheed again and found this file kernel_G925f sforum i flashed it. and upon reboot it says 'Kernel is not seandroid enforcing' ,and it's not yet fixed it just cause bootloops and sometimes freeze on unfinished samsung logo animation.
I am now trying to flash firmware again to see if it could get fixed. every hour i am losing hope.
If theres any tips i could get that would be good.
If i fixed this s6 it'll be the biggest achievement of my life and own my first working smartphone.
Click to expand...
Click to collapse
Ahhhhh. forget it i finnaly fixed it the only problem is overheating. funny thing is i got rid of the freezing issue by hitting the phone against my leg.

Related

[SOLVED] [Q] GT-P5113 Reboot Loop Plz Help

I ended up sending this to Samsung for repair. Luckily my tab was still under warranty. It took them 3 times to finally get it fixed correctly. First time they replaced the main board and the data link cable plug. When I got it back it lasted about an hour before it started doing the reboot loop again. So I sent it back and that time that did a software upgrade, but they obviously didn't even test it before sending it back cuz it only lasted 30 min. then it started with the reboot loop. Before I sent it back for the 3rd time I got in contact with a manager cuz I was so frustrated at this point. That time I sent the tablet directly to her to make sure it was fixed and tested before sending it back to me. I've had it for about 2 weeks now with no problems. They replaced the main board again. So either they gave me a faulty one the first time they "fixed" it or they didn't do anything to it.
So if your tab is stuck in the reboot loop and there's nothing you can do to make it stop, contact Samsung.
I bought this about 2 weeks ago and got to use it for about 5 days.
Woke up in the middle of the night cuz I kept hearing the start up sound to my tablet. So what it does is starts up then I get a prompt saying "Unfortunately, the process com.google.process.gapps has stopped" I click ok and then another prompt that says "Unfortunately, Goole+ has stopped" with the choice of clicking "Report" of "Ok" then the screen freezes and it all starts again.
So I have about 3 - 5 seconds after it starts up and I've tried going in and doing a system restore but it crashes before I can do that. I have manged to go in and delete my google account but when it restarts my account is back.
So then I tried using the Odin3 program with every different file that I could find that would be compatible with my tab and it shows that it installs fine but nothing ever changes on the tab it self. I have tried using the Pit file and the stock rom, the stock rom alone, the pit file alone, twrp open recovery, clockwork open recovery, CF Auto Root, but no luck. I have tried having the auto reboot on and off and then rebooting it myself, still no change.
When I go into recovery mode it shows the android with a red triangle. and of course if I try to install anything from there it always does the signature fail. Which I'm guessing cuz it's not rooted. So at this point I am wondering is there a way to just completely wipe everything off and start completely over? I have wasted so much time on this POS I'm about to just throw it away. Any advice would be more greatly appreciated.
Thank you.
GT-P5100
Hi Im a new member. Im have the same trouble also.
there is an endless restart cycle, and my tablet can last only for around 10 to 15 seconds power on then it will restart again and repeat the process until the battery die.
I can only power off if i connect to the power supply.
I already tried ODIN with several stock PDA files, root with CWM and philtouch, but nothing happens. Everything is passed but there is no change on the about devices after the reboot. Then it continue the endless restart again.
When i boot in original recovery, there is an error already. if i flash zip file root, there is an error in signature.
Please help me brothers and sisters.
Any luck figuring this problem out?
OSANG said:
Hi Im a new member. Im have the same trouble also.
there is an endless restart cycle, and my tablet can last only for around 10 to 15 seconds power on then it will restart again and repeat the process until the battery die.
I can only power off if i connect to the power supply.
I already tried ODIN with several stock PDA files, root with CWM and philtouch, but nothing happens. Everything is passed but there is no change on the about devices after the reboot. Then it continue the endless restart again.
When i boot in original recovery, there is an error already. if i flash zip file root, there is an error in signature.
Please help me brothers and sisters.
Click to expand...
Click to collapse
Have you had any luck fixing this problem?
OSANG said:
Hi Im a new member. Im have the same trouble also.
there is an endless restart cycle, and my tablet can last only for around 10 to 15 seconds power on then it will restart again and repeat the process until the battery die.
I can only power off if i connect to the power supply.
I already tried ODIN with several stock PDA files, root with CWM and philtouch, but nothing happens. Everything is passed but there is no change on the about devices after the reboot. Then it continue the endless restart again.
When i boot in original recovery, there is an error already. if i flash zip file root, there is an error in signature.
Please help me brothers and sisters.
Click to expand...
Click to collapse
Same Problem with me, for me it says USB device is not recognized and I cannot sent anything from my computer now. Totally Stuck with this stupid thing.

[Q] samsung infuse 4g crashing just as it starts

Hi there everyone, recently signed up on here as xda seems to be the holy grail when it comes to all thing smartphone.
I'm fairly new to these type of phones and recently was given an infuse 4g that was suffering a power button problem.
The power button problem has been resolved with a new one and the phone was working fine for 3 / 4 weeks.
One day the phone shut down by itself and entered the boot loop syndrome. Factory clearing it hasnt seemed to do anything to resolve the problem as it continued to reboot continuosly.
I came across the thread about gtg ultimate unbrick guide in the developers forum and this seemed like a good way to go, get the phone all the way back to stock and then work from there.
Kies installed and all drivers installed fine. downloaded the gtg unbrick pack and followed the instructions line for line. Odin reports everything passed, took about 2:59 to complete.
phone rebooted and continued to do boot loop so went into recovery as stated and wiped data and cache and rebooted again.
phone is still stuck in some sort of boot loop, but it gets to display the 1st of the setup android phone screens, then just as you get a chance to select next to go onto the next screen, the phone reboots.
Any one have any idea what could be going wrong or as im fairly new to this, is there anything im doing or not doing right that is causing this.
The phone is an at&t infuse.
regards
Trevor
sound like an issue with stuck power button. it's a know issue with this model. google "infuse 4g boot loop" there's few youtube videos you can try.
tt33333 said:
sound like an issue with stuck power button. it's a know issue with this model. google "infuse 4g boot loop" there's few youtube videos you can try.
Click to expand...
Click to collapse
I've already replaced the power button with a new one, but the technician i use did say he will remove the power button completely to see if it does the same, just to rule that out
Trev
just redone the gtg flash and it boots into the os (ver2.2.1) and then within about 5 seconds turns off and reboots
can the new on off switch be faulty......im not so sure as in recovery mode, i can leave it on that screen forever and it doesnt attempt to reboot
Tried the one click repair with hemdial or what its called, updating thisnpost via a moto defy mini so excuse any typos.. The hemdiaOl just seemed to meas it up further. So got baxk into downliad mode with odin and reflashed to gtg brick recovery. Not fixed, still booting but at least the screen is now viewable.
To recover one of these phones, is there like a definitive guide as to what to do to first prepare one of these phones for recovery, ie, first, flash to this with cwm and then clear data, cache, dalcik etc. like an idiots fuide, i feel i may need one
Regards
Trev

Can't downgrade from OF6...

I am on Sprint. So I upgraded to OF6 through Odin. I dislike it plus Wifi Tether doesn't work (both Wifi Tether Router and the unlocker). Wifi tether works for about 10 minutes and then it will stop (shows it's still on but no more wifi)
So I downloaded Kitkat (ND2 and NK4). Factory reset the phone, wipe cache, go into download, set up Odin, connect the phone and hit start... aaaand it immediately fails. Phone shows SW REV CHECK FAIL. The phone still functions.
Any help?
You are locked. Since OD3 you can't downgrade to KitKat. Try installing a custom rom lollipop based, like MOAR.
I was in the process of giving up anyways xD Installed Pacman. Thank you for the information. I couldn't really find anything that verified that Sprint did this as well. It looked like only AT&T and Verizon -_-
Hi. Can I downgrade from OD3 if I installed a custom rom?
damntuco said:
Hi. Can I downgrade from OD3 if I installed a custom rom?
Click to expand...
Click to collapse
No you can't downgrade from OD3, a custom rom won't make any difference. Sprint chose to lock the bootloader for OD3 and any version after
What if you're unlocked on kitkat (MOAR) - and you choose to try out a custom rom that's using OD3 or higher? Can you still go back?
Bigjohn_S said:
What if you're unlocked on kitkat (MOAR) - and you choose to try out a custom rom that's using OD3 or higher? Can you still go back?
Click to expand...
Click to collapse
As long as it isn't the official rom via odin you will be good. It's the newer bootloader that prevent you from flashing back so as long as the rom you choose is a recovery flashable rom you're OK. The MOAR 6.2 thread has a link to the latest version of lollipop with the ability to have the unlocked bootloader. Oa6 I believe, I'd suggest you flash that and get on to MOAR 6.2, it's bad ass!
what does MOAR 6.2 bring? I like kitkat... keeping 'material design' to a minimum is my goal. (if I wanted a windows8 phone, I'd have bought one... pretty pastels and all!)
Bigjohn_S said:
what does MOAR 6.2 bring? I like kitkat... keeping 'material design' to a minimum is my goal. (if I wanted a windows8 phone, I'd have bought one... pretty pastels and all!)
Click to expand...
Click to collapse
Newer, faster, all around better imo but ymmv
banccalif said:
Newer, faster, all around better imo but ymmv
Click to expand...
Click to collapse
My problem is if "newer, faster" brings along "more material design crap", then I'm not interested. Yech. Flat, 2d, pastel color garbage needs to die ASAP.
Make a nandroid of your kk setup. Then Odin to OA6, no OD3 or OF6. If you don't like it, then go back to kk.
Thanks.
But I was on lolipop (stock) which is one of the reasons i personally went for moar 2.2
And I've looked for older versions of apks for some of my apps too - ones that tipped over the cliff with material design pastel blue and pink and yellow... OW my EYES!
Downgrade to 4.4
I can't get any 4.4 Rom to work with OF6. Is there anyway to make it work?
az1995 said:
I can't get any 4.4 Rom to work with OF6. Is there anyway to make it work?
Click to expand...
Click to collapse
No.
OF6 stuck?
So I was on OA6 G900P stock twrp and CF Odin rooted, and thought all was good (just updated from KK) and thought, hey, since I updated because of signal/modem issues, I might as well get the newest one. Odin flashed OF6, reboot, waited 45 minutes, still on boot logo. force reboot, waited 16 more minutes, still on Samsung logo... Figured crap, I got a bad flash...
pulled the battery, got to the stock boot menu, it said I was on baseband OA6, binary custom, system custom. I thought crap, it didn't do anything, no wonder it won't boot. So I went back in to Odin and did it again (while downloading another copy of the tar.md5 from a different source), flash went good, tried to flash CF root in Odin, failed. figured, oh well, I'll just add twrp and flash CF from there... twrp failed. Rebooted to see what I'd get, 30 minutes later, still on Samsung logo...
So I pulled the battery again, got back to the boot menu and over to the Odin screen, now it says binary official, system custom, then a big old message "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
Well, I don't have Kies installed, and the download page at Samsung won't load. from this thread, I take it I cannot downgrade at all, OA6 fails in Odin with fail(Auth). And on My S5 it says:
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 1
Any ideas? I'm hunting an OD3 download from somewhere now. Kinda perturbed, as I researched for 5 hours yesterday to prep for this update from 4.4 (yes I just moved to OA6 this morning), and didn't even find this version until AFTER I had OA6 on my phone today, but nothing about any issues with OD3 or OF6 came up in searches. Now all I care about is getting the f'ing thing to boot.
Sort of a retarded policy to prevent ANY downgrade, what to they expect to do if they roll out a brick update, like has happened to various phones in the past? (fyi, I have been watching the loading bar for 15 minutes trying to "open" the download page for Kies on both samsung.com and samsung-kies.en.softonic.com and both still have a blank page)
***UPDATE - opening the download page in IE worked fine...
***UPDATE 2 - post Kies...
Kies comes back and tells me that my device is not supported by Kies 3. Multiple restarts later (every restart comes immediately to the same screen), I was able to get the Custom OS installation screen to come up, and pressing the volume up key got me back to Odin mode, withOUT the stupid firmware upgrade failed use Kies screen. At this time I have no idea what to try... I am hunting a download of OD3 to try, if not, then I will try OF6 again, plug the phone into the wall and let it sit on the boot logo until tomorrow and see if that works.
***UPDATE 3 - waiting on boot logo
New Download (again), new computer, new cable. Flash failed the first try (OF6), disconnected cable and plugged it back in same port to try again. Second flash attempt passed, now waiting on boot. I did not try to flash anything but the stock firmware this time. As I said, I just want the phone to work. If nothing works this time, I'll take it to a non-reseller Sprint store and see if they'll either update it for me or pass me a refurb.. Battery was full when I flashed it, so I'll wait till the battery dies tonight before giving up. (adb does not find the device while it is loading the boot logo, from previous devices, that tells me it is failing to load the boot loader, but I haven't done this but once in the last 16 months, so maybe I'm wrong). I did notice with flashing OA6 I had a boot sound on first boot after Odin and it took 12 minutes to get to the welcome screen, every flash of OF6 I have not had any sound on boot up.
***UPDATE 4 - amazingly fast battery drain from 90% black boot animation...
Well the battery tanked in about 1hr 15 minutes. I pulled the batter, SIM, and SD, then let it charge 7-12 minutes, reconnected to Odin, flashed the brand new 2.8.7.0 TWRP (in ODIN) and it worked... rebooted to TWRP and let it install root on exit, no idea if it succeeded, I can verify it moved the recovery image so TWRP would not get overwritten during boot though, but the last line (immediately after the "Installing SU..." line was on screen about 250ms before the phone rebooted... I've been watching the boot logo ever since, still no Android OS and still unable to detect the phone in ADB (in TWRP, it showed up without permissions, so I know if it ever boots I'll need to change those settings). Next test is to try a factory reset, if not that, then I'll try to restore the OA6 nandroid I took this morning.
***UPDATE 5 - restored OA6 nandroid
twrp let me in, I restored my OA6 nandroid, boot (took 0 seconds), system, and data only. Immediately on reboot (no prompt to root, good sign as I rooted before the nandroid), I had a startup sound! (noticed later that this only happened once) about 60 seconds later I had a big freaking white box with "System is not responding. Do you want to close it" and wait/ok buttons. I waited about 30-45 seconds as I started editing this post, then hit wait. it disappeared, and I saw cell signal 3/5 bars, and the battery % and charge icon at the top, then the screen went black. about 20 seconds after that I had a Samsung boot animation going at a reduced screen brightness (dark enough that I almost cannot see the animation). I'll pause typing now to wait and see what it does... repeat of the same, except I did not see the notification bar icons this time, and it rebooted after maybe 12 seconds of delay. This time I tapped ok... No difference. During all of this, none of the buttons on the phone appear to have any impact on what is going on. and ADB is not picking up the device during any part of this.
Back to TWRP and full restore of the backup (I took all 7 partitions in the backup), boot took 1 second this time... I've noticed that the CPU temp seems to sky rocket during the boot animation. this last time it went up to 68C, after I let the phone sit charging and finally got back into TWRP it was at 40C. 1 second for EFS restore and 2 seconds for modem. again, 60 seconds and the force close box came up, another 40 seconds and I saw the signal strength and battery% plus charge icon.
Back to TWRP again gave me my old TWRP vKT-2.8.4.2, ADB works again as well, so the restore is definitely overwriting the partitions. I pushed the OD3 de-odexed rom to my SD card and flashed it...
***UPDATE 6 - OD3 de-odexed
Ok, so I already typed this and then lost it... long story short, it upgraded android, then did the same crap, but I got a water droplet sound when clicking wait on the System is not responding, saw LTE data for a bit, then it rebooted any way, same crap. Going to reflash OF6 in ODIN and see if I can get anywhere with that, then try some roms... need to let the battery charge up a bit first though. Laterz, if there is another update, it will be a resolution, if not...
I guess this would be double posting, but I have a working phone and prefer to put what I did in a separate post, than to add it at the end of a bunch of troubles; The only thing not mentioned here but is above, I updated from 4.4 Alliance Rom to 5.0 OA6 stock via Odin, plus CF auto root via Odin, and ktTWRP (2.8.4.2) also via ODIN, as soon as the system came up to the welcome screen I rebooted to TWRP without doing anything and took a nandroid of all 7 partitions. And then updated to OF6 not knowing the new bootloader restrictions. The end problem was that OF6 did not boot. Below is a logging of what I did over the last 2 hours and the end result is that my OA6 nandroid is running with the OF6 bootloader? (not sure about this one), kernel? ( I think so), and modem. I am sure some of the more experienced guys around here would know. Personally I like to crack flash till I find something that works, then I might not flash again for 12-24 months, depending on if there were any bugs or not.
So here it is, I hope in the future someone somewhere is helped by this. If mods think this should be it's own post and chop out some of the useless parts to make it guide like, I approve of anyone else using this info and doing it.
wait times on boot up range from 10 minutes to 6 hours with no change. Any time something happens during boot it is always between 30 seconds and 12 minutes. Only while in recovery mode does ADB detect the device, with TWRP 70 it shows without permissions, with ktTWRP (42) it shows the device ID and allows access from adb.
flashed OF6 - Odin - AP
reboot - no audio - no boot
reboot - boot menu - factory reset
reboot - no audio - no boot
reboot - boot menu - wiped cache
reboot - no audio - no boot
flashed OD3 kernel - Odin - AP
reboot - audio - no boot
flashed cf auto root - Odin - AP
reboot for root install - straight back to Odin mode intentionally
flashed twrp 70 - Odin - AP
reboot - audio - no boot
reboot with vol+up - audio - no boot
reboot - twrp 70
flashed fusion 6.0 nightly 8/7/2015 - wiped cache and dalvik - reboot - got Fusion boot animation - no audio - yellow LED - after 8-9 minutes I got a blank screen - I pressed home and got "Unfortunately WFC Settings has been stopped" ok - "Unfortunately Phone has stopped" ok - blank screen - tap screen and capcitive buttons backlight comes on touch either bbutton, get vibration feedback, but nothing else, touch hardware buttons, screen goes off and on, but no other response. 30 seconds later Unfortunately phone has stopped, before I tap ok, I get a background image. Ambient light sensor appears to be able to dim screen brightness, no buttons give any visual effect, other than power button. No notification bar as of yet. 13-14 minutes after initial boot start up, the phone restarted itself.
reboot - loop? - Fusion boot animation - no audio - 4 minutes alter I got "fusion is starting" - lasted 25 seconds - then black screen with "Unfortunately, WFC Settings has stopped" ok - then phone - ok - then both again - ok, ok - blank black screen - 6 minutes later and several "unfortunately ... has stopped" I realized the screen had turned off. Turned it on, and there was a welcome screen with a crash screen on it, I went to type this and the screen went black, welcome screen did not come back, 10 seconds later - adb detected the device by name/ID an says unauthorized - system crashed - adb now shows all ??????? - unauthorized - long press power button brings up the reboot menu (has "settings" but when I press it, it just goes back to the blank black screen) - the only thing that worked from teh power menu was reboot (I would guess power off does too) even gives me the reboot screen with the spinning thing. during the reboot notification and before it actually restarts, ADB recognized the device again.
reboot - during boot up ADB goes to ???? unauthorized for 30-50 seconds, then shows correct system ID/name and unauthorized again - LED is off for the first time since flashing rom (did not even turn off when disconnecting from PC, connecting to laptop, disconnecting from laptop, plugging in to wall, disconnecting, plugging in to laptop...) - boot took 9 minutes 20 seconds - came up to android logo, then Fusion is Upgrading, shot through the apps r
eal quick, then everything stopped again...blank black screen, Amber LED back.
reboot - TWRP 70 - restore nandroid - system/data only OA6 stock - factory reset
reboot - waited 60 seconds before getting boot animation - waiting patiently to boot, ADB shows correct device name and unauthorized the entire time, no LED - waited 30 minutes, still on boot animation
reboot - TWRP 70 - factory reset - restore nandroid - boot/system/data OA6 stock
reboot - no audio - 40 seconds later - welcome preparing your device this may take 3-4 minutes came up - finalizing android upgrade after 30 seconds - update successful - LTE, setup wifi, EULA, software update screen, none found... tap and go.. skipped - add google and samsung. The Sprint filled my System up with crap... looks like it is working.
***UPDATE - 8/15/2015
I had some issues with system crashing again after the first reboot, but I waited on a blank black screen for about 16 minutes and everything loaded up. seemed to run fine, same issue next reboot... Instead of working on it, I flashed fusion ROM, never booted, I let it sit on the boot loader for 4.5 hours (fell asleep), then I flashed MOAR, I have not had any issues since. Checking a few other threads led me to believe I had lost IMEI, possibly the entire partition as I had all of the symptoms after a firmware update; however it is all there, or the restore of my OA6 nandroid put it back, not sure as I did not figure that out until much later on. Good thing I followed at least one smart rule... NANDROID before FLASH! good luck everyone.

Galaxy s6 G920v stuck in bootloop, have tried everything

Hi guys, so recently I bought a Galaxy S6 Verizon off of eBay. I got it for fairly cheap because it was stuck in a boot loop. I usually have no problem fixing stuff like this, but this time is different. So the first thing I tried when I got the phone was to do a reset and cache wipe from recovery. I rebooted the phone and it showed a screen that said "Android is starting, optimizing app 9 out of 31." when it got to 21 the phone rebooted and went back to 9. It did this several times before I attempted to wipe/reset again. I then downloaded the tar file G920VVRU4CPH1 and flashed it in Odin. I did a manual reset before the phone booted, and it is doing the same thing again. reboots to a green screen where it tries to optimize apps, stays there for about 20 seconds, and reboots over and over again in the same cycle. I have tried all other stock marshmallow roms that i can find, Odin won't flash older ones, (assuming its not letting me downgrade). Also another weird thing, every time I flash, the blue update screen goes to 32%, stops, erases, and reboots. Phone is on 6.0.1 version MMB29K.G920VVRU4CPH1 as seen in recovery. Any help would be gladly appreciated. Thank you!
I am having a similar problem with loading new rom. The farthest it gets is 32%. Sometimes it doesn't get even that far.
I ended up just buying a trashed s6 and swapping the motherboards. Only way I could fix it

Help, after flash TWRP and do factory reset instructions in Chinese

Ok I will admit it, I screwed up royally this time. My SM-N9150 (Hong Kong version) was slowing down and draining the battery fast. I could not get the downloader of a new stock ROM to work in Sammobile (tried multiple times, with adblock off but no go) and so I bit the bullet and used Kies to upgrade to Marshmallow. Of course this lost root but I figured I could just re-root (I had rooted using Odin with my old phone, but this one I had rooted using KingoRoot). However, none of the 1-click systems like KingoRoot worked, and neither did Chainfire via Odin (which caused problems on its own). So I flashed the latest CWM via ODIN. It said pass, so I went into recovery, did a backup, then did factory reset, installed SuperSu, wiped the caches and rebooted.
I kept getting weird errors where it would not let me boot into recovery or boot at all. so I thought that maybe CWM was not a good choice. I tried the newest version of TWRP but that gave me the "recovery is not seandroid enforcing" error. So I went back the CWM and tried wiping again.
After a very long Samsung logo bootloop, it eventually showed gearings turning but with instructions in Chinese. It then showed the logo again for long time and then showed something that had only 1 English word "system" and the rest in Chinese. There seemed to be 2 choices at the bottom of the dialog box. When I chose the one of the right, the phone showed a grey progress bar with Chinese letters above, but then went back into a bootloop; when I chose the one on the left, the phone turned off for a long time then restarted but again seems to be stuck at the Samsung logo screen before returning to the message with the word "system".
After it going into a bootloop that lasted over 1 hour, I pulled the battery and then went into recovery and tried restoring the backup I had made at the start. That just left me in the endless Samsung logo bootloop. I left it plugged in overnight hoping it would do something but nada. At one pint I did get a message "unfortunately, the system UI has stopped working" but screen was unresponsive to press OK, and it just went back into the bootloop.
I realize I did not do anything to unlock the bootloader. Would using KIES have locked the bootloader again? Could this be my problem, and if so, how do I fix it?

Categories

Resources