Related
Ok, I know I'm not the first to have this screen pop up because of a failed flash and I did indeed search before asking. I've been searching since late last night and so far I'm stumped. I've installed and reinstalled Samsung Kies to get the official drivers quite a few times so far (because the drivers Heimdall installs don't play well with ODIN) and that gets ODIN to recognize the phone but once I click start after putting in the ROM I am trying to install, it just sits saying "SetupConnection" for as long as I choose to let it sit there. If I try Heimdall, it changes drivers to one that is usable and then fails to get a response at handshake with Loke. I've never had this happen before. I was coming from ParanoidAndroid trying to unroot the phone to sell and now I'm here. Any ideas?
That is an alternate download mode that shows after a failed firmware update. Use Heimdall and one click back to stock.
You will probably need to uninstall any drivers installed by Odin in order for heimdall to work.
Sent from my SGH-T959V using xda premium
I'm aware of that. I know what the screen means. I only mentioned it as a point of reference. My point was that after getting that screen, everything I have tried to flash has failed. That's one of the ways I attempted. Any heimdall does the same thing, though. It fails at handshake with Loke. Being that there is no log, I am not entirely sure what is causing ODIN to fail but 2 different roms have had the same effect. Thanks for the response. By the way, I'm sorry if I seem snappish, I didn't mean to be. Just been a long aggravating night.
Heimdall One-Click. Not Heimdall. Use the second link in my signature. Read the notes and you will learn you can install Heimdal One-Click drivers for one usb port and Samsung drivers one a different usb port without confict.
I found the one click unbrick which worked like a charm. Going to attemp to get this thing back to stock again. Thanks for your help.
Oh, and by the way, this is the heimdall I was using. One click and stock KJ6. I've never tried actual heimdall. Didn't honestly know that there was a heimdall standalone version. By the time I started messing with this phone, all the one click stuff was already made. Made it a lot easier than the old days of rooting the G1, so I never looked for anything else til now. No point in making a job harder.
First, I tried searching for hours, and I haven't been able to find this same issue anywhere on the forums yet. If I missed it, sorry, and thanks.
I downloaded the stock 2.3.6 firmware from the Hiemdall One-touch thread here, and ran it on my phone (SGH-T959V Galaxy S 4G, and I made sure the firmware was for that specific model and not the Vibrant). It ran through the first time just fine, and then I went to do the bootloader (which I gather I probably shouldn't have done and didn't need to do maybe). Heimdall One-Click started running, then gave me this message and restarted the phone to a black screen:
Code:
Uploading PIT
PIT upload failed!
Ending session...
Rebooting device...
Now, I can pull the battery and get the phone into Download Mode just fine, and I've tried running the same firmware as well as several others (AntonX-Basic_with_a_twist, Stock KJ6 + root-One-Click, hampsterblade-Basic_MIUI_Kernel_r2_OC_UV, at least), but while they all do the first restore fine, none will load the bootloader and I get the same results every time. The phone is obviously not 100% bricked since I can get into Download Mode, but all I get is a black screen, no lights under the buttons and nothing on screen, not even the rainbow pattern or the Samsung logo. It's as if the phone isn't doing anything at all, and it doesn't change if I just pull the battery and leave it (tried for 15-20 minutes a little while ago). The only thing I can do is put it back into Download Mode, but none of the firmwares I've found have worked to restore the bootloader.
I am using a Mac with 10.8 and Java 1.7, and if it's necessary I can get access to Windows, but that will take me some time and effort, so if there's any way to resolve it using just the Mac that'd be best.
jW
When you flash the Heimdall package, does the phone boot fine?
It should have work with Mac, can you double check things?
If possible can you try re-downloading the .jar package.
And in the terminal run the .jar package (sorry I don't know OS X commands).
Thanks for the responses. It does not work after I run the Heimdall package, before or after I check the Flash bootloader checkbox. I have tried redownloading the packages several times, and I always run them with "java -jar [path to file].jar", which should be the proper command structure (and they do open and run and report success up until the point of that error, which is after the first time through but before any other steps complete in the Flash bootloader process).
Is there another method instead of the Heimdall One-Click .jar's that I can use? I have the full Heimdall installed of course, but I can't seem to find a stock PIT file for this phone that it will recognize.
jW
jondesu said:
Thanks for the responses. It does not work after I run the Heimdall package, before or after I check the Flash bootloader checkbox. I have tried redownloading the packages several times, and I always run them with "java -jar [path to file].jar", which should be the proper command structure (and they do open and run and report success up until the point of that error, which is after the first time through but before any other steps complete in the Flash bootloader process).
Is there another method instead of the Heimdall One-Click .jar's that I can use? I have the full Heimdall installed of course, but I can't seem to find a stock PIT file for this phone that it will recognize.
jW
Click to expand...
Click to collapse
As far as I know don't be desperate, that happened to me and I ended up with a bricked device.
Either boot into a free Linux distro. or use a Windows computer.
th3controller said:
As far as I know don't be desperate, that happened to me and I ended up with a bricked device.
Either boot into a free Linux distro. or use a Windows computer.
Click to expand...
Click to collapse
Thanks, I've got a Linux distro downloading and I'm looking into whether I could get a copy of Windows or borrow a PC easily.
jW
You've verified the md5 of the .jar file? I'm not sure which one you're using, please specify.
If the package file is fine and got downloaded correctly though, the next thing I'd try is a different USB cable. I have two cables, both work fine with my own phone, but I was flashing my friend's phone the other day and only one of them worked. This has happened to others too and it very likely might be the issue.
At this point though stop trying to flash the bootloaders. We're not sure whether your phone will flash successfully. You'll need to try flashing without the bootloaders and if the gingerbread package got flashed correctly you'll wind up getting the rainbow screen (assuming your phone still has the froyo bootloaders) which will be a good sign, and from there it'll be safer to flash the bootloaders.
FBis251 said:
You've verified the md5 of the .jar file? I'm not sure which one you're using, please specify.
If the package file is fine and got downloaded correctly though, the next thing I'd try is a different USB cable. I have two cables, both work fine with my own phone, but I was flashing my friend's phone the other day and only one of them worked. This has happened to others too and it very likely might be the issue.
At this point though stop trying to flash the bootloaders. We're not sure whether your phone will flash successfully. You'll need to try flashing without the bootloaders and if the gingerbread package got flashed correctly you'll wind up getting the rainbow screen (assuming your phone still has the froyo bootloaders) which will be a good sign, and from there it'll be safer to flash the bootloaders.
Click to expand...
Click to collapse
Thanks, I'll give that a try (still trying to get Linux installed here to try that as well). The first one I tried, and the one I think I'd prefer to use is the T959VUVKJ6 Stock UVKJ6 from the Heimdall One-Click thread in the forums here. I tried some of the others when that one failed. It downloaded fine, and I tried downloading it again with no change in the results.
I should clarify, btw, that I have been trying flashing it without the bootloader, but when I do that, it still sits on the black screen. The very first time I did it and one other time later, I did get the rainbow screen (and the first time, but never again, it did boot up to the stock OS and home screen), but now if I flash with or without the bootloader, I get nothing, probably because the bootloader got screwed up by the first bad flash.
My first step today will be using another cable (there's one handy, I just didn't think about it), and then I'll move on to trying Linux/Windows.
jW
**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
So, somehow I managed to download and install CRC4 (950U) onto my galaxy 955U now I am trying to upgrade to CRD4 (955U) with Odin but I kept getting fail sha256 errors so I now have Prince Cosmy ODIN which fixed that but now Setup Connection does not pass and if it does it fails, I have been able to load everything in to odin and only get as far as Setup Connection is there something else I can try that I have not tried already? Please Help
I have downloaded G955U1 software and tried that but it does not load the system.img and I am still on the same version
Zmantech said:
So, somehow I managed to download and install CRC4 (950U) onto my galaxy 955U now I am trying to upgrade to CRD4 (955U) with Odin but I kept getting fail sha256 errors so I now have Prince Cosmy ODIN which fixed that but now Setup Connection does not pass and if it does it fails, I have been able to load everything in to odin and only get as far as Setup Connection is there something else I can try that I have not tried already? Please Help
I have downloaded G955U1 software and tried that but it does not load the system.img and I am still on the same version
Click to expand...
Click to collapse
Try one section at a time.. Don't rush it.. AP.. BL.. and so on.
You'll find that it's a bit easier to handle than loading up the entire rom in one shot.. Make sure you don't have the auto reboot box checked.. But as you do each section reset the Odin software. Once you complete the last section, attempt to boot up recovery and reset cache and then wipe user data.. TWICE. Then boot back into download mode and then load the entire rom into the proper slots.. This especially helps if you're RMP fuse says it's blown.. Once you have accomplished this then attempt to restart. You will find that this phone is very hard to kill, if you treat this problem like a better opportunity to learn more about the phone than panicking. It might actually reboot once to preform a reset on its own. It's normal. After the reboot let it go for a bit.. Get it and you settled.
Good luck.
How did you install CRD4? Was it through a stock recovery zip?
If so, make sure you're using Odin 3.13.1 (see attached) to go back to G995U firmware
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