Here is what I did so far to get here.
First I followed the guide to root my phone, and to be honest, all was perfect. I had to restore stock rom cause my first few tries failed. But seems I flashed a rom for a different provider. It worked anyway, but I don't have my sim card in that phone, it's temporarily in another device.
I had a little issue in settings, where battery was coming up two times in the list. That bugged me, I wanted to restore the rom and see if a full restore would take care of this issue, but somehow, after I installed twrp and rooted my phone, I can no longer flash anything stock with odin, it fails.
If I try to flash the AP tar.md5 file, it fails when it gets to system. And then after rebooting, I see this message:
"An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC Software"
I tried installing smart switch and kies, and both software doesn't detect my device in download mode or twrp (obviously)...
So to get rid of the emergency message, I flashed twrp again with odin, and been successful. If I tried to flash the AP image again, or CSC, it fails. And then I get the message back.
After flashing twrp, I'm stuck in a boot loop. Would need to restore system I think, but cannot seem to be able to do it with Odin.
Any possible way to recover my device?
Update: Turns out I must have made a mistake with the firmware I thought I had flashed, versus the one I was trying to flash and was failing. I downloaded the latest october firmware and it's currently flashing in odin!
This not be posted in development !
mchlbenner said:
This not be posted in development !
Click to expand...
Click to collapse
Sorry about that, I thought it was related to the topic. Obviously, you saw that I do not have a thousand posts around here, a wise thing to do would have been to suggest me where should I have posted this, and how can I move my thread around? Do I wait for a mod to move it himself?
pleclair said:
Here is what I did so far to get here.
First I followed the guide to root my phone, and to be honest, all was perfect. I had to restore stock rom cause my first few tries failed. But seems I flashed a rom for a different provider. It worked anyway, but I don't have my sim card in that phone, it's temporarily in another device.
I had a little issue in settings, where battery was coming up two times in the list. That bugged me, I wanted to restore the rom and see if a full restore would take care of this issue, but somehow, after I installed twrp and rooted my phone, I can no longer flash anything stock with odin, it fails.
If I try to flash the AP tar.md5 file, it fails when it gets to system. And then after rebooting, I see this message:
"An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC Software"
I tried installing smart switch and kies, and both software doesn't detect my device in download mode or twrp (obviously)...
So to get rid of the emergency message, I flashed twrp again with odin, and been successful. If I tried to flash the AP image again, or CSC, it fails. And then I get the message back.
After flashing twrp, I'm stuck in a boot loop. Would need to restore system I think, but cannot seem to be able to do it with Odin.
Any possible way to recover my device?
Click to expand...
Click to collapse
You forgot to flash all of them
BL, AP, CP, CSC
pleclair said:
Sorry about that, I thought it was related to the topic. Obviously, you saw that I do not have a thousand posts around here, a wise thing to do would have been to suggest me where should I have posted this, and how can I move my thread around? Do I wait for a mod to move it himself?
Click to expand...
Click to collapse
Just because you have a lot of post you don't post question in development section.
587.saboor said:
You forgot to flash all of them
BL, AP, CP, CSC
Click to expand...
Click to collapse
I did flashed all of them. But it always fails. No matter if I select only BL, AP, CP, CSC... or all of them. Almost seems like twrp is preventing write or something else does.
It fails after a few seconds in the process. Is there any kind of log generated by odin? If so, where can I find it? I don't see much information beside that it fails.
OEM unlock checked in dev options?
USB debuging checked? these were always the go to mischecks...
back when I had the galaxy a5 2017 520W canada unit I flashed a european rom to see if FM radio was going to work. it Worked, but I had the simular issue with battery showing up twice AND I ended up tripping knox while doing it. phone seemed to work fine other then that issue and the radio worked as well.
Flashed it back to 520W stock... later sold the phone... no issues. perhaps it was different with nougat
supertac said:
OEM unlock checked in dev options?
USB debuging checked? these were always the go to mischecks...
back when I had the galaxy a5 2017 520W canada unit I flashed a european rom to see if FM radio was going to work. it Worked, but I had the simular issue with battery showing up twice AND I ended up tripping knox while doing it. phone seemed to work fine other then that issue and the radio worked as well.
Flashed it back to 520W stock... later sold the phone... no issues. perhaps it was different with nougat
Click to expand...
Click to collapse
Yeah, I have those two checked. For some reasons, I was tired that night, and was actually trying to flash 7.1.1 firmware, while having already upgraded to 8.0. So I believe this operation wasn't getting thru because of that. I was tired, and picked the wrong folder, and flashed 7.1.1. Well, I was trying to flash, but it kept failing, but had a tiny bit done, enough to screw this up like this.
When I picked the right folder, 8.0, then it worked.
As for tripping knox, you probably tripped it while flashing twrp. I believe it trips it, haven't heard of a way to do it.
pleclair said:
Yeah, I have those two checked. For some reasons, I was tired that night, and was actually trying to flash 7.1.1 firmware, while having already upgraded to 8.0. So I believe this operation wasn't getting thru because of that. I was tired, and picked the wrong folder, and flashed 7.1.1. Well, I was trying to flash, but it kept failing, but had a tiny bit done, enough to screw this up like this.
When I picked the right folder, 8.0, then it worked.
As for tripping knox, you probably tripped it while flashing twrp. I believe it trips it, haven't heard of a way to do it.
Click to expand...
Click to collapse
nope. NEVER flashed twrp once on the A5- the european firmware tripped it on the 520W
Related
**NOTE** For the SM-P900! However steps should be the same for SM-P905 EXCLUDING THE FILE TYPES (THEY ARE DIFFERENT DO NOT ATTEMPT TO USE THE FILES FOR THE SM-P900 OR BYE BYE TO YOUR NOTE 12.2 Pro because now you have a problem that may or may not be repairable/reversible). You just have to make sure you have the coordinating files for the process!
If anyone else has issues try this and these steps to complete the Root/Custom ROM/TWRP Recovery installations successfully for a "First time go":
1. Remove Kies and Kies3 files, related files, folders, and everything that has anything to do with the primary installation of either the two programs on your PC and your devices. When/if prompted, select the checkable box and elect not save any type of files... if you want to keep them save them OFF your main PC on a flash or removable storage device.
2. REMOVE ALL SAMSUNG DRIVERS AND REPLACE WITH ONLY OFFICIAL SAMSUNG DRIVES!!! THIS IS A BIG MUST!
3. Using your USB 2.0 cable and ports Install the Custom Rom "P900XXUANB3-RecoveryImg.tar" FIRST and flash it via ODIN 3.07 under the PDA checkbox that is "fixed" (so you noobs don’t make any soft bricks if this is your first attempt at rooting), and only use the ODIN 3.07 THAT COMES W/ CHAINFIRES AUTO ROOT .zip file and then unzip the folder to open ODIN 3.07 ONLY! This is only because I have read that there have been issues installing the SU via Chain Fires Auto Root Process... the file is called (currently as of 25 JUNE 2014) "P900XXUANB3-RecoveryImg.tar" PDA select it and then start when in DOWNLOAD MODE on your device. Manually select DOWNLOAD MODE if you have to BEFORE PRESSING START! Otherwise, one is just going to sit there and not accomplish anything.
http://forum.xda-developers.com/attachment.php?attachmentid=2591013&d=1392923580
http://forum.xda-developers.com/attachment.php?attachmentid=2591159&d=1392930654
http://forum.xda-developers.com/attachment.php?attachmentid=2775098&d=1401644348
4 Reboot back into DOWNLOAD MODE. Flash in ODIN 3.07 with the PDA section and select this file next to install: "openrecovery-twrp-2.7.1.0-v1awifi.img.tar"
5. In DOWNLOAD MODE and flash the file under the PDA box TWRP (OR CURRENT RECOVERY OF YOUR CHOICE THAT IS AVAILABLE)
6. AGAIN... Restart your device into DOWNLOAD MODE via ODIN 3.07 and select PDA and then finally root this: "CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5" Then you can backup, restore, flash anything, and be happy! YOU SHOULD FINALLY HAVE A SUCCESSFUL ROOT! Turn off and REBOOT into RECOVERY to see if TWRP stuck and then reboot to see if the SU stuck. IF everything stuck reboot back into TWRP to flash whatever rom is available MAKE SURE TO BACK UP EVERY FILE BEFORE YOU FLASH ANY NON-STOCK ROMS. If not successful rinse wash and repeat until it does!
http://download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
7. That’s it you should have root and a custom rom and recovery if you followed these instructions for flashing via ODIN 3.07 and Chainfires AutoRoot files. If you still have an issue repeat until root/recovery/Rom sticks. If you have to update the Binary for the SU just go to the Google Play Store and install the app and then try it again till it works. GOOD LUCK it worked for me this way!
**IMPORTANT**
BACK UP BACK UP BACK UP BACK UP after every flash that is possible to back up. If you can, back up the NON-SU stock ROM BEFORE installing SU, after installing the recovery and/or back up.
***IF I HELPED YOU OUT THANK ME***
DISCLAIMER - all research was observed via comments on the thread according to issues people have been having during ROOTING the device I simply have compiled the data and made a check list!
Need a link to the files you mentioned.
Thanks. Very helpful.
I have a P900. Is there a way to unroot and bring a unit back to stock? My main concern is if Samsung sends out a software/firmware update, and a device is already rooted, can the update be applied?
sstea said:
Thanks. Very helpful.
I have a P900. Is there a way to unroot and bring a unit back to stock? My main concern is if Samsung sends out a software/firmware update, and a device is already rooted, can the update be applied?
Click to expand...
Click to collapse
Read THIS
But still one quiestion, why the heck you root your device if you are going to update it via Samsung's official ways. Ah and one more question.. why the heck would you want to update your device if it's rooted?
A new update from Samsung can patch all known security holes and make your device unrootable, and since you are rooted now, one would think that you don't want to loose it. Or where do I know if you rooted because it sounded nice and cool, without knowing what you did and most importantly WHY you did.
Spere said:
Read THIS
But still one quiestion, why the heck you root your device if you are going to update it via Samsung's official ways. Ah and one more question.. why the heck would you want to update your device if it's rooted?
A new update from Samsung can patch all known security holes and make your device unrootable, and since you are rooted now, one would think that you don't want to loose it. Or where do I know if you rooted because it sounded nice and cool, without knowing what you did and most importantly WHY you did.
Click to expand...
Click to collapse
Thanks. I appreciate the reply. I have rooted many devices before. I have to admit that it was more of following posted instructions and not fully understanding the details. What gives me pause is how extremely limited the support is for this tablet. I want to root my note if I can make it more responsive, get rid of bloatware, enable more apps for multi-window, titanium backup, etc. I want to make sure that if I root that I don't get stuck with on an old release. So will previously rooted Notes be able to get the necessary files to easily update and maintain root, or does rooting now mean that a tablet may be stuck at the current release? Thanks
sstea said:
Thanks. I appreciate the reply. I have rooted many devices before. I have to admit that it was more of following posted instructions and not fully understanding the details. What gives me pause is how extremely limited the support is for this tablet. I want to root my note if I can make it more responsive, get rid of bloatware, enable more apps for multi-window, titanium backup, etc. I want to make sure that if I root that I don't get stuck with on an old release. So will previously rooted Notes be able to get the necessary files to easily update and maintain root, or does rooting now mean that a tablet may be stuck at the current release? Thanks
Click to expand...
Click to collapse
You can always flash stock firmware via odin
I was just wondering if everyone was having a much easier time with achieving root now? Kies caused me to "Hang" a lot during the Root and custom rom to stick w root... as of right now i can not get the only ONE custom ROM that looks promising, i have found by GWatts (correct me if i am wrong and i apologize if i have typed the wrong screen name handle) i believe his handle is... at this point im not sure what i am doing wrong as of yet but im sure i am missing a step or i just need to start back at unroot back to stock firmware and try and try again lol. not saying anything is wrong with his work at all by any means because people other than me with the same device have gotten it to stick and im just wishing i could as well because its sweet looking ROM! NOT TO MENTION THE ONLY ONE THAT IS OUT (that is which i know about. i haven't been on in a few months idk), SO KUDOS TO WATTS i just haven't been successful at installing his custom rom just yet... Im hoping that its just going to need to be erased again and then reformatted after a factory reset and what not, i pray it sticks because his incorporation of the aroma installer was a nice touch and his ROM really looks good... Now if i can just get it not to stick at samsung boot logo and freeze id be good lol!
sanvara said:
Need a link to the files you mentioned.
Click to expand...
Click to collapse
ok
I followed your instructions but while flashing the cf-auto-root file my screen got all distorted (speckled grains of color), and nothing else happened for about 15 minutes, until I just unplugged it and shut it off.
Now when I power it on it gives me the error "Firmware upgrade uncountered an issue. Please select recovery mode in Kies & try again."
I wonder what I did wrong.
pnuker said:
I followed your instructions but while flashing the cf-auto-root file my screen got all distorted (speckled grains of color), and nothing else happened for about 15 minutes, until I just unplugged it and shut it off.
Now when I power it on it gives me the error "Firmware upgrade uncountered an issue. Please select recovery mode in Kies & try again."
I wonder what I did wrong.
Click to expand...
Click to collapse
**Edit**
I went back and reflashed the twrp file and it got me out of the error screen. I installed supersu, and then re-flashed the cf-auto-root file, and it worked like a charm. I'm not sure if it was the installation of supersu, or just repeating the process that fixed it, but I'm happy either way...
Thank you! I succesfully rooted my SM-P900 after all mentioned problems ( hanging in the cache.img and after a while a disturbed screen etc.) with your guide. I am a very happy rooter now.
Thanks,
Thanks to the poster. I tried rooting with the instructions from a few other sites and thought I bricked it,
Followed your instructions, and presto.. Rooted! :good:
Rooted!
Thanks for your post. This is my first time ever rooting a device. Your method worked perfectly!
your welcome!
frankiecxyz said:
Thanks for your post. This is my first time ever rooting a device. Your method worked perfectly!
Click to expand...
Click to collapse
your very welcome! it took me a bit to get it down but i eventually figured it out and at the time information on rooting the device was hard to find with this specific model. then i discovered what the issues where and felt the need to post it! im glad i could help!:laugh:
Flash SU with TWRP not ODIN
Here's my story...
Received my new UK spec SM-P900 Note Pro 12.2, ran through the initial setup, performed two OTA upgrades to KOT49H.P900XXUANI1, then attempted to flash SU using Odin 3.07 using the various instructions on this forum. Result: failed cache flash and soft brick!
Used Keis 3 to recover the tablet which took two hours! After more reading I discovered the quick boot recovery flash method, so re-attempted on a different PC, with exactly the same result. Re-flashed the boot, tried again, fail, again, fail, etc, etc. Various permutations of PCs, Odin versions and USB ports were tried.
Concluded that the Odin method was NEVER going to work, so had a rethink. Used Odin to flash TWRP v2.8. Downloaded the latest SU-BETA v2.7 flash for TWRP (not Odin), copied it to the root of the tablet SD and then flashed it with TWRP. Worked first time with no messing about!!!
Booted, ran SU and upgraded to Premium, disabled KNOX from within SU. Tablet locked up. Booted, re-ran SU, disabled KNOX again, this time successfully. Ran Titanium, filtered with KNOX and froze all occurrences, then de-installed KNOX completely. :good:
Lesson learnt... DO NOT use Odin to flash SU on a P900 !
soft bricked
Hello!
First of all let me say that I'm a complete newbie, this is my first android device. I tried to root my SM-P900 (P900XXUANI1) using an online guide (image with URL attached, as I am not allowed to paste URLs)
Unfortunately at Step 10 (flashing with Odin) the operation failed and now I ended up with a soft bricked device (I assume this is the correct definition). It will only show the message asking me to connect it to KIES to recover it.
I know i can try to use KIES 3 and restore it, but before that i would like to ask if there is any alternative which will allow me to unbrick the device without losing all my data... (yeah i know...).
If i follow this guide will this help? I'm not sure if I can even put the device in download mode again as it shows the error message about connecting it to KIES...
At this point I don't care about rooting, I just want to unbrick the device.... I understand the guide up to (and including) step 3. But for the rest of the steps I'm lost Could anyone please explain them in a bit more detail? I don't want to install any custom firmware, just to unbrick it...
Any help would be very appreciated!
Thank you
Yemble said:
Here's my story...
Received my new UK spec SM-P900 Note Pro 12.2, ran through the initial setup, performed two OTA upgrades to KOT49H.P900XXUANI1, then attempted to flash SU using Odin 3.07 using the various instructions on this forum. Result: failed cache flash and soft brick!
Used Keis 3 to recover the tablet which took two hours! After more reading I discovered the quick boot recovery flash method, so re-attempted on a different PC, with exactly the same result. Re-flashed the boot, tried again, fail, again, fail, etc, etc. Various permutations of PCs, Odin versions and USB ports were tried.
Concluded that the Odin method was NEVER going to work, so had a rethink. Used Odin to flash TWRP v2.8. Downloaded the latest SU-BETA v2.7 flash for TWRP (not Odin), copied it to the root of the tablet SD and then flashed it with TWRP. Worked first time with no messing about!!!
Booted, ran SU and upgraded to Premium, disabled KNOX from within SU. Tablet locked up. Booted, re-ran SU, disabled KNOX again, this time successfully. Ran Titanium, filtered with KNOX and froze all occurrences, then de-installed KNOX completely. :good:
Lesson learnt... DO NOT use Odin to flash SU on a P900 !
Click to expand...
Click to collapse
Have you got a link to the odin rwrp 2.7 you used and the su 2.7 flash for twrp please?
VenomousViper said:
**NOTE** For the SM-P900! However steps should be the same for SM-P905 EXCLUDING THE FILE TYPES (THEY ARE DIFFERENT DO NOT ATTEMPT TO USE THE FILES FOR THE SM-P900 OR BYE BYE TO YOUR NOTE 12.2 Pro because now you have a problem that may or may not be repairable/reversible). You just have to make sure you have the coordinating files for the process!
If anyone else has issues try this and these steps to complete the Root/Custom ROM/TWRP Recovery installations successfully for a "First time go":
1. Remove Kies and Kies3 files, related files, folders, and everything that has anything to do with the primary installation of either the two programs on your PC and your devices. When/if prompted, select the checkable box and elect not save any type of files... if you want to keep them save them OFF your main PC on a flash or removable storage device.
2. REMOVE ALL SAMSUNG DRIVERS AND REPLACE WITH ONLY OFFICIAL SAMSUNG DRIVES!!! THIS IS A BIG MUST!.......
Click to expand...
Click to collapse
When i trying root, my SGN freeze in "cache". Odin show error and tablet goes to Emergency Firmware Recovery. Аnd it does not matter what program I use and how I do it.
Mine Reboots Constantly
I rooted my SM-900 about two weeks ago.
It worked great for a week until the device started rebooting by itself.
The first time a couple times a day, now it does it whenever as often as twice in 5 minutes.
Is there a way to see which app is causing this or does anyone know why this might be happening?
Though I rooted I haven't been poking around. I figured it'd be like using Linux but now I see it's not quite like that.
Thanks in advance.
sunnykhs said:
I rooted my SM-900 about two weeks ago.
It worked great for a week until the device started rebooting by itself.
The first time a couple times a day, now it does it whenever as often as twice in 5 minutes.
Is there a way to see which app is causing this or does anyone know why this might be happening?
Though I rooted I haven't been poking around. I figured it'd be like using Linux but now I see it's not quite like that.
Thanks in advance.
Click to expand...
Click to collapse
Have you cleared dalvic cache and cache in TWRP recovery? Be forewarned the process takes a while for cache wipe.
Sent from my SM-P900 using Tapatalk
this is the second time i've soft bricked my phone in the past 6 days and if this is fixable i will probably consider researching for weeks at a time before trying anything new..
anyway, the first time i soft bricked my phone last week, my s6 was rooted (via chainfire, G920IDVU1AOC6) but i decided to unroot so i could update software. after unrooting with SuperSU, i attempted to update by using smart switch and then something went wrong with that process (my firmware was at G920IDVU1AOC4) which i then fixed by flashing G920IDVU1BOE3 (latest stock firmware) WITHOUT the hidden.img
backstory out of the way, i wanted to flash TWRP so i could install xposed installer. i used the same chainfire firmware that worked the week prior (above) and so now my phone is soft bricked
things i've tried:
- flashing recovery of AOC4 - i can get back into recovery mode with the older firmware
- flashing AOC4 stock firmware with AND without the hidden.img
- flashing the BOE3 stock firmware with AND without the hidden.img
i'm still able to get into download mode and stock recovery and i've already tried wiping cache and factory reset but nothing works.
i continue to get FAILED on odin
if anyone is able to bring my phone back from purgatory for the second time it would be greatly appreciated.
thanks in advanced, mojo.
Ok, I soft bricked my s6 too :/ its fine now so dont worry, actually, I read somewhere the problem of failing is in Odin, and you need to flash the stock recovery and then recocery.img you extracted from it in a way odin can read, im from my phone now so I will try to search it out, hope I will find. Dont worry dude your s6 is alive.
Ok i found it, http://forum.xda-developers.com/galaxy-s6/help/solved-stuck-download-mode-failed-odin-t3104736 , I burned stock and then the file he supplied,worked like a charm.
JusTeN_ said:
Ok, I soft bricked my s6 too :/ its fine now so dont worry, actually, I read somewhere the problem of failing is in Odin, and you need to flash the stock recovery and then recocery.img you extracted from it in a way odin can read, im from my phone now so I will try to search it out, hope I will find. Dont worry dude your s6 is alive.
Ok i found it, http://forum.xda-developers.com/galaxy-s6/help/solved-stuck-download-mode-failed-odin-t3104736 , I burned stock and then the file he supplied,worked like a charm.
Click to expand...
Click to collapse
thank you so much for your reply and reassurance! i'll try this out right now and update on the results
UPDATE: i tried flashing stock and then the my-recovery.img.tar and i could get into recovery but i was stuck in boot loop.
is there something i'm doing that's incorrect?
Saafir said:
Did you remove the cable, boot download mode, then reconnect and let the driver install screen complete on your PC? Sorry if its a bit redundant but I had made this mistake before.
Click to expand...
Click to collapse
yes i have reconnected each time but thanks anyway!
JusTeN_ said:
Ok, I soft bricked my s6 too :/ its fine now so dont worry, actually, I read somewhere the problem of failing is in Odin, and you need to flash the stock recovery and then recocery.img you extracted from it in a way odin can read, im from my phone now so I will try to search it out, hope I will find. Dont worry dude your s6 is alive.
Ok i found it, http://forum.xda-developers.com/galaxy-s6/help/solved-stuck-download-mode-failed-odin-t3104736 , I burned stock and then the file he supplied,worked like a charm.
Click to expand...
Click to collapse
I FIXED IT.
i'm not exactly sure of the steps i took, as i had to keep waiting for my Unified Android Toolkit to create the tars but essentially what i did was i flashed;
- stock BOE3 WITHOUT hidden.img
- TWRP recovery (was able to boot into twrp and when i looked through some settings (reboot) it said i had no OS installed for some reason
- from this info i tried flashing the AOC4 older firmware WITHOUT hidden.img then it worked.
do you think it is worth attempting the smart switch thing mentioned in that link you posted?
i wouldn't want to run into this problem again..
my lord.. so SOMEHOW i managed to get myself into this for THE THIRD TIME..
once i got it fixed, just a few hours ago, everything was fine and i was then able to flash CF root again.
but once i tried to install TWRP (it worked before i fixed the second time) odin FAILED again and i'm back to square one.
i'm unsure how to properly fix it and the steps i took before aren't working now and i can't even flash any recoveries (whether its AOC4, BOE3 or TWRP)
can anyone suggest anything else please?? i'm in panic mode again lol
this is definitely the last time i try to do any type of configuration with this device.
Do you have recovery now? Maybe burn some custom rom? ..
JusTeN_ said:
Do you have recovery now? Maybe burn some custom rom? ..
Click to expand...
Click to collapse
now i can't flash the twrp .. it won't work. this suck so much!
UPDATE (final update, hopefully ): fixed it AGAIN.
after going through this hellish nightmare for the 3rd time and reading countless threads, i've discovered that the FAILs on odin may be occurring due to the corruption of the firmware file.
so if anyone goes through my problem, CREATE A COPY of the desired firmware before flashing with odin!
thanks justen for your patience and attempts to help me!
Hi everyone, I hope that you can help me. My phone was rooted for quite a long time but since it was rooted it wouldn't allow me to access my banking app or PayPal or other apps that I needed to, so around a week ago I decided to unroot it with a simple unroot button in the SuperSU.
However this did not end well and when my phone was rebooting it got stuck in the boot loop and it would not load again, I tried wiping the cache which didn't help. I then wiped the phone completely and that did not help with anything.
So then I read about it and I decided to try using Odin to flash the phone with the stock firmware, and whichever firmware I used the Odin would fail and give me a "Nand write start fail". I tried for hours and day and could not get this to work.
So then I decided I would try contacting Samsung and see if they could fix it for me, they took the phone but today I got an email saying that the can't repair it because the KNOX was tripped and the warranty is voided.
So right now I don't really know what to do, do I buy a new phone?
You can do JTAG maybe
darkliesbehind said:
Hi everyone, I hope that you can help me. My phone was rooted for quite a long time but since it was rooted it wouldn't allow me to access my banking app or PayPal or other apps that I needed to, so around a week ago I decided to unroot it with a simple unroot button in the SuperSU.
However this did not end well and when my phone was rebooting it got stuck in the boot loop and it would not load again, I tried wiping the cache which didn't help. I then wiped the phone completely and that did not help with anything.
So then I read about it and I decided to try using Odin to flash the phone with the stock firmware, and whichever firmware I used the Odin would fail and give me a "Nand write start fail". I tried for hours and day and could not get this to work.
So then I decided I would try contacting Samsung and see if they could fix it for me, they took the phone but today I got an email saying that the can't repair it because the KNOX was tripped and the warranty is voided.
So right now I don't really know what to do, do I buy a new phone?
Click to expand...
Click to collapse
Tried flashing bootloader and stock recovery? Smart Switch emergency initialization?
And a bit more details would help, like model, CSC, Android version, can you enter recovery, is it stock or custom, is there any DRK error in recovery, which firmware you tried to flash, which kernel you used for rooting, whatever you think it could be useful.
brenner650 said:
Tried flashing bootloader and stock recovery? Smart Switch emergency initialization?
And a bit more details would help, like model, CSC, Android version, can you enter recovery, is it stock or custom, is there any DRK error in recovery, which firmware you tried to flash, which kernel you used for rooting, whatever you think it could be useful.
Click to expand...
Click to collapse
I will provide more details when I receive the phone back from samsung. But from what I can remember. I am able to go into recovery mode, it was running stock ROM, I tried to flash both Vodafone firmware which is what I bought the phone with and I also tried UK base firmware. its the SM - G920F model. It was running the newest android, I don't remember what version it was but the update wasn't too long ago .
with Smart Switch emergency initialization, you can make that your phone works, it's long but it works. i do it.
look at (it's in french but you can do it)
https://www.youtube.com/watch?v=mi7O0OvnS2E
Okay, so I've tried using the Smart Switch initialization and this did not work, it says that my device was not supported for initialization.
darkliesbehind said:
Okay, so I've tried using the Smart Switch initialization and this did not work, it says that my device was not supported for initialization.
Click to expand...
Click to collapse
what model are you using?...download the latest MM rom with the PIT file ....flash the PIT file with odin to repartition the phone and flash the stock rom....it should work
I've looked through the forums to identify a similar problem to mine in hopes I can resolve this issue but I've not found one. So here's my problem.
I have a UK Galaxy S7 running on the 6.0 firmware that came with the phone when it first released (Yes I know it's very old and should have updated along the way but I had plans to root and install customs at some point which obviously didn't happen). The phone is unrooted and the stock rom is the XEU version with Multi-CSC (according to recovery)
The phone was running fine until a few days ago when all of a sudden it shut off and wouldn't power on via the power button. So I pressed and held Home + Volume Down + Power. The green screen appeared and selected Volume Down to restart the device (as you do in odd situations like this).
PHONE IS NOW STUCK IN BOOTLOOP!!!
I have tried various means (not including flashing) to get the phone to boot to the home screen with no success. I have not performed a factory reset from recovery because I have various data, including pictures, music and other software on the internal storage which I wish to keep and not lose. The phone is still under warranty so I can take it to a Samsung repair outlet to get them to fix it for me but due to data privacy or whatever, they have to format it clean to then install the most recent firmware.
I've been scouring the forums for help on flashing OTA updates which retain data on phone whilst possibly allowing my phone to boot into the home screen so I can access my data. Is such a thing possible?
Any help would be greatly appreciated.
You can flash the latest firmware without losing data (as long as the hardware is not faulty) by downloading it from either sammobile, updato.com or using the samfirm tool here on XDA (Fastest option)
Then extract the firmware and add all 4 parts to ODIN 3.12.7 (Do not use ODIN 3.13.1 unless you want to flash BTU Oreo 8.0)
AP << (Takes quite a long time to add, be patient as ODIN will look frozen)
BL
CP
HOME_CSC
If you use CSC instead of HOME_CSC it will wipe the device after the flash, HOME_CSC will not wipe it
Put the phone into download mode (Home & Power & Volume Down)
Connect to PC USB and hit start on ODIN
Wait for the flash to complete (It can take quite a while) and the phone should hopefully boot back into Android
Thank you for the quick response.
It's imperative I get this right and ensure I've understood your reply correctly.
I have downloaded the following:
SM-G930F_1_20180417125627_cz5yqc22v0_fac - from SamFirm as it was much quicker like you said.
Odin3+v3.12.7 - This particular version was quite difficult to get a hold of. Various sites redirecting me to various pages without a direct link to download but I hope that is the correct one.
The firmware zip contains the following files:
AP_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship_meta.tar -------1
BL_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship.tar -------2
CP_G930FXXU2DRB6_CL648265_QB8952207_SIGNED.tar -------3
CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar
HOME_CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar -------4
I have labelled the files 1-4 in the order of flashing/installation (I presume?)
I will also follow your instruction of flashing HOME_CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar as this will NOT wipe any existing data on the phone?
Will following the above steps act as an upgrade to the phone and not wipe apps/pictures etc in the internal storage?
Have I missed out any other steps?
Cassie` said:
Thank you for the quick response.
It's imperative I get this right and ensure I've understood your reply correctly.
I have downloaded the following:
SM-G930F_1_20180417125627_cz5yqc22v0_fac - from SamFirm as it was much quicker like you said.
Odin3+v3.12.7 - This particular version was quite difficult to get a hold of. Various sites redirecting me to various pages without a direct link to download but I hope that is the correct one.
The firmware zip contains the following files:
AP_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship_meta.tar -------1
BL_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship.tar -------2
CP_G930FXXU2DRB6_CL648265_QB8952207_SIGNED.tar -------3
CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar
HOME_CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar -------4
I have labelled the files 1-4 in the order of flashing/installation (I presume?)
I will also follow your instruction of flashing HOME_CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar as this will NOT wipe any existing data on the phone?
Will following the above steps act as an upgrade to the phone and not wipe apps/pictures etc in the internal storage?
Have I missed out any other steps?
Click to expand...
Click to collapse
Almost, you must flash all 4 files at the same time, load them all into ODIN before hitting start, doesn't matter which order you load them in as long as they are all loaded before flashing
And you are correct with the rest, HOME_CSC will not wipe anything, and yes it will act as an upgrade although it is a full ROM you are flashing, to you the user, it will appear exactly the same as an upgrade as long as you use HOME_CSC
No other steps needed
I have loaded all 4 files as seen in the screenshot however, after clicking on Start, about 5 or so minutes later, it says FAIL in the first box above where it initially said RECOVERY. It's stopped and not done anything else.
I'm not sure what to do here.
I've also added a shot of the top left of odin screen
Cassie` said:
I have loaded all 4 files as seen in the screenshot however, after clicking on Start, about 5 or so minutes later, it says FAIL in the first box above where it initially said RECOVERY. It's stopped and not done anything else.
I'm not sure what to do here.
I've also added a shot of the top left of odin screen
Click to expand...
Click to collapse
Yea it's failed, you can close ODIN and disconnect now
You can try doing it again, but that should have worked, you could try downloading the latest 6.0.1 ROM and flashing that the same way first, it looks like your bootloader is version 1 where this ROM is version 2 as shown by the S2 number in the middle of the firmware version
*Detection* said:
Yea it's failed, you can close ODIN and disconnect now
You can try doing it again, but that should have worked, you could try downloading the latest 6.0.1 ROM and flashing that the same way first, it looks like your bootloader is version 1 where this ROM is version 2 as shown by the S2 number in the middle of the firmware version
Click to expand...
Click to collapse
I've gone to https://updato.com/firmware-archive-select-model?record=0DB04AD4C34211E69215FA163EE8F90B
From there I've selected the most recent 6.0.1 ROM which is dated 4th December 2016. Problem is that the download is EXTREMELY slow and I have no idea how to use SamFirm to download that particular ROM.
I guess all I can do now is play the waiting game and repeat the steps with the 6.0.1 ROM once it's downloaded.
Thank you for your responses and I will post back here once the download has finished.
Cassie` said:
I've gone to https://updato.com/firmware-archive-select-model?record=0DB04AD4C34211E69215FA163EE8F90B
From there I've selected the most recent 6.0.1 ROM which is dated 4th December 2016. Problem is that the download is EXTREMELY slow and I have no idea how to use SamFirm to download that particular ROM.
I guess all I can do now is play the waiting game and repeat the steps with the 6.0.1 ROM once it's downloaded.
Thank you for your responses and I will post back here once the download has finished.
Click to expand...
Click to collapse
Yea unfortunately all alternatives other than samfirm tool are slow, and samfirm only downloads the latest ROM
Judging by the bootloader version and the ROM version you have chosen, if this also fails, then I would assume a hardware failure
The only other thing I could suggest if this doesn't work, is to pick an older version of ODIN to flash the older firmware, ODIN 3.11.1 was used for MM 6.0.1 ROMs if I'm remembering correctly
https://forum.xda-developers.com/showthread.php?t=2711451
or
https://odindownloader.com/download/odin3-v3-11-1
I've restarted the device and it said An error has occurred while updating the device software use the emergency recovery function.
I attempted to reboot the phone a couple of times to get into recovery and I was successful. I now see the the Bootloader version is now 2 as opposed to 1. After seeing this I attempted to flash version 7 as initially suggested yet it did not work.
I'm not sure how Bootloader changed from 1 to 2 and is still failing to flash in odin. I am still waiting for the 6.0.1 ROM to download, fluctuating between 16-19 hours as of writing this response. Once it's ready I'll try and load up odin 3.11.1 as a second solution and try 6.0.1, even though Bootloader says 2.
Cassie` said:
I've restarted the device and it said An error has occurred while updating the device software use the emergency recovery function.
I attempted to reboot the phone a couple of times to get into recovery and I was successful. I now see the the Bootloader version is now 2 as opposed to 1. After seeing this I attempted to flash version 7 as initially suggested yet it did not work.
I'm not sure how Bootloader changed from 1 to 2 and is still failing to flash in odin. I am still waiting for the 6.0.1 ROM to download, fluctuating between 16-19 hours as of writing this response. Once it's ready I'll try and load up odin 3.11.1 as a second solution and try 6.0.1, even though Bootloader says 2.
Click to expand...
Click to collapse
Your ODIN screenshot looks like it managed to flash the bootloader before it failed, so it's possible you are going to need to use a version 2 ROM from now on, I have the same phone, XEU G930F and it is running Bootloader version 2 (Running the BTU Oreo 8.0 stock ROM)
But if the 7.0 Nougat ROM failed again it's looking more like a hardware issue, seems to be failing when it should be starting to flash SYSTEM (AP)
You can try flashing the 7.0 ROM section AP on it's own with ODIN 3.12.7, see if that fails immediately, if it does that's likely where the problem lies, it's not unheard of for these S7's to fail like this out of the blue, I see it maybe a couple of times a month on XDA
Only solution is to get the mainboard replaced
But yea, give 6.0.1 a shot anyway, worth a try saying as everything else has failed up to now
(Looking for mirrors for that 6.0.1 ROM, I've got it on my main machine but it is offline right now with no graphics card so I can't access any files, stuck with a laptop, I always download and save every new firmware release for this reason)
There is Samsung SmartSwitch software for Windows for the emergency firmware recovery, but it WILL wipe your phone back to factory and delete all your data (Last resort if nothing else works, although if ODIN doesn't work, I'd say hardware failure)
Right so I've managed to download the most up to date 6.0.1 ROM and attempted to flash it with ODIN V3.11.1 and it idles at the recovery.img part and fails like the previous efforts.
I'm not sure if attempting to get OREO running with the latest ODIN might work? If not then I may have to give up and do a factory reset through Samsung SmartSwitch.
It probably is a hardware failure as I had noticed the lightning bolt appearing when the phone is off whilst plugged in the charge, it take about a minute or so for the percentage bar to appear, usually it was about 2 seconds before this disaster occurred.
Cassie` said:
Right so I've managed to download the most up to date 6.0.1 ROM and attempted to flash it with ODIN V3.11.1 and it idles at the recovery.img part and fails like the previous efforts.
I'm not sure if attempting to get OREO running with the latest ODIN might work? If not then I may have to give up and do a factory reset through Samsung SmartSwitch.
It probably is a hardware failure as I had noticed the lightning bolt appearing when the phone is off whilst plugged in the charge, it take about a minute or so for the percentage bar to appear, usually it was about 2 seconds before this disaster occurred.
Click to expand...
Click to collapse
Worth a try flashing Oreo, BTU on samfirm tool will give you it for the G930F
If you're seeing problems with the charging now, you might get lucky and find the USB port is the only thing needing replacing, but if you send it off for repair it's unlikely even if that is the case that they won't just charge you for a new mainboard, you can likely get USB ports from eBay but opening the S7 isn't as straight forward as the back is glued on for IP68 water resistance and needs a heatgun to remove, not sure if anything else like the screen needs removing for USB, I've not opened mine
You've tried a new USB cable and a different PC too ?
*Detection* said:
Worth a try flashing Oreo, BTU on samfirm tool will give you it for the G930F
If you're seeing problems with the charging now, you might get lucky and find the USB port is the only thing needing replacing, but if you send it off for repair it's unlikely even if that is the case that they won't just charge you for a new mainboard, you can likely get USB ports from eBay but opening the S7 isn't as straight forward as the back is glued on for IP68 water resistance and needs a heatgun to remove, not sure if anything else like the screen needs removing for USB, I've not opened mine
You've tried a new USB cable and a different PC too ?
Click to expand...
Click to collapse
The charging issue occurred immediately when the phone shut off by itself and wouldn't power on conventionally. The phone is still under warranty so if the Samsung SmartSwitch software is unable to recover the phone then I will take it to the repair center and have them fix/replace it. If it's a case of undoing the glue and whatnot then I'd rather they give me a replacement.
I did change the USB cable to a different one, and I've attempted to flash the 2 different ODINS with the 2 different ROMS on a laptop as opposed to the desktop I was using. Still fails at the recovery.img part of ODIN.
I'm going to try Samsung SmartSwitch now and see if this will give it some life. If THAT doesn't work then it's 100% hardware issue and my data was lost to begin with.
Considering both versions of ODIN didn't work with either ROM, I don't think I'll be looking for the BTU version of OREO to attempt to install with. If there's a direct download that's quick I might but I think I'll attempt to Emergency Recover through the Samsung tool.
I want to thank you plenty for your help and knowledge on this. It certainly has been helpful and given me better understanding of the problem I'm facing and potential solutions. I have a feeling that the SmartSwitch recovery won't work either and still be posting back here hahaha.
OK I've got bigger problems on my hands now.
SmartSwitch and Kies both say "SM-G930F" does not support initializing. Please contact our service center.
I've already inputted my serial number and it gives me the same message on both programs. When I called up customer support they said my warranty is till the end of May this year.
Would the service center be able to solve this problem?
Cassie` said:
OK I've got bigger problems on my hands now.
SmartSwitch and Kies both say "SM-G930F" does not support initializing. Please contact our service center.
I've already inputted my serial number and it gives me the same message on both programs. When I called up customer support they said my warranty is till the end of May this year.
Would the service center be able to solve this problem?
Click to expand...
Click to collapse
Yea I'd get it repaired under warranty asap then if it runs out soon, they will most likely replace the mainboard I'd say, which means 100% data loss as the storage is on a chip on that board, or might even send you a new S7
Really does sound like hardware failure if all of these recovery options have failed, just keep quiet about what you've done to try and fix it, just act dumb and say it won't turn on or they could claim you nulled your warranty messing with ODIN
And no probs, that's what XDA is all about Let us know how the repair goes and buy a MicroSD card to save your important files to this time so you don't lose anything if it happens again
*Detection* said:
Yea I'd get it repaired under warranty asap then if it runs out soon, they will most likely replace the mainboard I'd say, which means 100% data loss as the storage is on a chip on that board, or might even send you a new S7
Really does sound like hardware failure if all of these recovery options have failed, just keep quiet about what you've done to try and fix it, just act dumb and say it won't turn on or they could claim you nulled your warranty messing with ODIN
And no probs, that's what XDA is all about Let us know how the repair goes and buy a MicroSD card to save your important files to this time so you don't lose anything if it happens again
Click to expand...
Click to collapse
I had an SD card inside with all my pictures I took whilst in Japan (Thank GOD!). I took it out when this issue arose to avoid potential data loss there.
As far as ODIN is concerned, warranty still appears intact but yes I'll keep hush hush when I'm there. I believe they said they'd give me a refurbished S7 if they couldn't reflash it there.
Cassie` said:
I had an SD card inside with all my pictures I took whilst in Japan (Thank GOD!). I took it out when this issue arose to avoid potential data loss there.
As far as ODIN is concerned, warranty still appears intact but yes I'll keep hush hush when I'm there. I believe they said they'd give me a refurbished S7 if they couldn't reflash it there.
Click to expand...
Click to collapse
Yes, ODIN will not void warranty if you only flash stock, but telling them you used ODIN might, it's not a tool meant for us, it's Samsung's internal flashing tool not meant to be leaked online, sometimes they'll use any reason to blame you and not have to pay out / replace it so yea best not say anything other than official recovery methods suggested by Samsung themselves, if anything at all, I'd just say I didn't do anything, an OTA update came through and it never rebooted or something
Good job with the pics, I don't save any media to the phone itself, I create folders on the SDCard and move it over if I can't have it save there automatically, that way wiping the phone is nothing but a pain to set back up again, nothing actually lost
*Detection* said:
Yes, ODIN will not void warranty if you only flash stock, but telling them you used ODIN might, it's not a tool meant for us, it's Samsung's internal flashing tool not meant to be leaked online, sometimes they'll use any reason to blame you and not have to pay out / replace it so yea best not say anything other than official recovery methods suggested by Samsung themselves, if anything at all, I'd just say I didn't do anything, an OTA update came through and it never rebooted or something
Good job with the pics, I don't save any media to the phone itself, I create folders on the SDCard and move it over if I can't have it save there automatically, that way wiping the phone is nothing but a pain to set back up again, nothing actually lost
Click to expand...
Click to collapse
I'm going to give flashing one last try.
I am currently downloading Android 8.0.0 for United Kingdom (BTU, NOT XEU). I have to head to work in a few minutes. When I get back I'll attempt to flash that without BootLoader as that will change it to version 3 and you can't downgrade from that from what I've read here and there. If that fails then it's off to the repair center. If it's some sort of hardware failure then it won't flash regardless what stock rom/ODIN version I'm using.
Not sure if BTU update with home CSC will retain my data (assuming it works)
Cassie` said:
I'm going to give flashing one last try.
I am currently downloading Android 8.0.0 for United Kingdom (BTU, NOT XEU). I have to head to work in a few minutes. When I get back I'll attempt to flash that without BootLoader as that will change it to version 3 and you can't downgrade from that from what I've read here and there. If that fails then it's off to the repair center. If it's some sort of hardware failure then it won't flash regardless what stock rom/ODIN version I'm using.
Not sure if BTU update with home CSC will retain my data (assuming it works)
Click to expand...
Click to collapse
Your CSC will remain XEU as it is Multi-CSC containing BTU, and BTU contains XEU, I'm running it now with BTU firmware & XEU CSC
Bootloader for this Oreo 8.0 BTU firmware is still 2, with it being a new Android version you'll need to flash the BL too anyway
*Detection* said:
Your CSC will remain XEU as it is Multi-CSC containing BTU, and BTU contains XEU, I'm running it now with BTU firmware & XEU CSC
Bootloader for this Oreo 8.0 BTU firmware is still 2, with it being a new Android version you'll need to flash the BL too anyway
Click to expand...
Click to collapse
I've had no luck flashing it with Oreo. It's definitely going to the repair centre. Such a shame.
I'm very grateful for your time and help with this. I will report back this weekend with the results of what the repair centre will do regarding the device. Don't like to leave a thread without an end result.
Many thanks again!
So the past couple days I've been learning what I can about rooting. Finally decided to give it a shot and well I can't seem to get ODIN to work correctly. It seems to always end with abl.elf and then failing at write. I've tried Comsy and a few versions of ODIN including the latest version.
I'm currently downloading the latest firmware for my phone which is what I was updated to.
I have the Galaxy s8+ SM-G955U originally through VZW. I remember the ending of my firmware was CRE9 so I found this version off of Samsclub: G955USQU4CRE9_G955UOYN4CRE9. I downloaded some stock files for my device because I wanted to reset my bootloader version so I could root and use PARTCYBORG's rom. That's when it seemed to start looping.
I have access to download and recovery if you need that information. I also have downloaded the latest samsung drivers for Odin. I'm pretty sure if I could get it to write I could fix this issue but I've gone through a hundred threads on this forum and I'm pretty much a bit overwhelmed now. Please help
EDIT: I think I've nearly gotten it, but I'm stuck now. Odin 3.12 and Comsy 3.12 seemed to get me close. I've ran into missing Home Binary and Fail! Model Mismatch. Trying a 3.13 version of ODIN and then calling it.
One of the frustrating things about rooting for the first time is 'what are the expectations' in how things 'should' go.
Make sure you are using the most recent USB drivers. Odin, for some, will error out on the first flash attempt. It sure did when I was first learning, and it still does now, however someplace that I don't recall suggested this:
Connect with Odin, and Odin will say your phone is connected.
Setup your flash pieces.
Then flash.
Odon will fail, but this time you will leave the phone connected and re-enter download Odin.
Doing the above got me and others past the Odin errors on first flash attempts. It sure was troublesome.
Hope this works for you.
JeffDC said:
One of the frustrating things about rooting for the first time is 'what are the expectations' in how things 'should' go.
Make sure you are using the most recent USB drivers. Odin, for some, will error out on the first flash attempt. It sure did when I was first learning, and it still does now, however someplace that I don't recall suggested this:
Connect with Odin, and Odin will say your phone is connected.
Setup your flash pieces.
Then flash.
Odon will fail, but this time you will leave the phone connected and re-enter download Odin.
Doing the above got me and others past the Odin errors on first flash attempts. It sure was troublesome.
Hope this works for you.
Click to expand...
Click to collapse
hi I installed the image twrp 3.2.2.0 but by mistake on boot. how can I restore the boot? thank you