Database Users

[FULL-UNROOT][HOW-TO] S4 MINI GT-i9195

Hello,
many people out there say it's impossible to do a full unroot on the S4 Mini, but I'll prove them wrong:
If you have a custom recovery like clockworkmod installed, that's obvious for a rooted phone,
before flashing you'll have to flash an original Samsung stock recovery first.
Otherwise the after-reboot process doesn't work correctly and you'll still have status "custom".
So here is what I did step-by-step:
- I startet with a rooted Samsung stock rom (XXUAMG8)
- I let SuperSU unroot the device (one of it's options), then
- I went into system/accounts/backup&restore and did the full restore - reboot
- I installed an original Samsung stock recovery with Odin - reboot
- I flashed the original Samsung stock rom (XXUAMG8) with Odin.
Afterwards you can check in DL mode the status, it's all "Official".
Additional Notes:
On my phone, when I didn't flash the samsung recovery first, the system boot time increased to up to 5(!) minutes every time (not only the first one...)

And why would I want to unroot my phone?
The warranty is void anyway. The Knox flag remains 0x1.

Original Samsung Stock Recovery Request
Hello, friend!
Can you get me that "original Samsung stock recovery" you mentioned, please?
Recently, I flashed a CWM file on my GT-I9192 and it doesn't work properly.
I'm searching everywhere and I couldn't find anything that helped me out...
So you're my savior...:laugh
Please attach the file or show me the link... So you will help not just me, but too many people that just messed up their phones..:angel::good:
Best regards from Brazil.

If you do not want to flash a custom rom, you don't need cwm.
Instead, use saferoot
http://forum.xda-developers.com/showthread.php?t=2565758
...
work perfectly on my seranoltexx.

gogoland2002 said:
If you do not want to flash a custom rom, you don't need cwm.
Instead, use saferoot
...
Click to expand...
Click to collapse
This thread is about UNROOTING and not how to root...

cemimo said:
And why would I want to unroot my phone?
The warranty is void anyway. The Knox flag remains 0x1.
Click to expand...
Click to collapse
This how-to is about a phone with an older bootloader without knox.
So if you have a knox free bootloader, this description leads you back to full warranty conditions

help
Peter Semper said:
Hello,
many people out there say it's impossible to do a full unroot on the S4 Mini, but I'll prove them wrong:
If you have a custom recovery like clockworkmod installed, that's obvious for a rooted phone,
before flashing you'll have to flash an original Samsung stock recovery first.
Otherwise the after-reboot process doesn't work correctly and you'll still have status "custom".
So here is what I did step-by-step:
- I startet with a rooted Samsung stock rom (XXUAMG8)
- I let SuperSU unroot the device (one of it's options), then
- I went into system/accounts/backup&restore and did the full restore - reboot
- I installed an original Samsung stock recovery with Odin - reboot
- I flashed the original Samsung stock rom (XXUAMG8) with Odin.
Afterwards you can check in DL mode the status, it's all "Official".
Additional Notes:
On my phone, when I didn't flash the samsung recovery first, the system boot time increased to up to 5(!) minutes every time (not only the first one...)
Click to expand...
Click to collapse
I know this is an old thread and this is my first post.
I have tried doing these steps and my device still says custom I think I am using the wrong stock firmware I was on Vodafone UK firmware then rooted to Cwm 6.0.4.6 I am currently trying to unroot to receive ota update as kies doesn't work to update I did unroot with original firmware that was btu black edition I am guessing this shouldn't make a difference but if I am wrong then go ahead and laugh at me but I do need help with my phone
thanks
steve

mason01983 said:
I know this is an old thread and this is my first post.
I have tried doing these steps and my device still says custom I think I am using the wrong stock firmware I was on Vodafone UK firmware then rooted to Cwm 6.0.4.6 I am currently trying to unroot to receive ota update as kies doesn't work to update I did unroot with original firmware that was btu black edition I am guessing this shouldn't make a difference but if I am wrong then go ahead and laugh at me but I do need help with my phone
thanks
steve
Click to expand...
Click to collapse
flash twice the firmware in odin, sometimes baseband isn't flashed

Didn't work for me either.
Starting from CM11, wanted to flash latest stock ROM with KNOX boot loader removed - downloaded my local carrier-specific firmware from Samsung updates, then proceeded to use the tar and md5 -rt tools on a Mac, failed signature. So did it in Windows using 7zip and it managed to flash. Did it twice to ensure baseband was flashed.
Flashing the stock recovery then doing the same still gives me a custom version
Anyone has any ideas on how to return to stock? I'm on non-KNOX boot loader.
Sent from my SM-N9005 using XDA Premium 4 mobile app

I had cm 4.4.2 on my I9195 I have to re flash with odin to go back to clockwork mod then flash original firmware twice and it worked just waiting for the ota update now

problem
It did work flashing original firmware twice however I go into recovery mode and I have a dead android with a red triangle and the words no command

It works. I got "official" status and I can download software updates, but now I get dead android with red triangle when I go recovery mode with this message:
Code:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : NEE
Succesfully applied multi-CSC.
No command.
And when I select reboot it says "error," then reboots normally and everything works fine... But is there something wrong?

Tyhjäntoimittaja said:
It works. I got "official" status and I can download software updates, but now I get dead android with red triangle when I go recovery mode with this message:
Code:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : NEE
Succesfully applied multi-CSC.
No command.
And when I select reboot it says "error," then reboots normally and everything works fine... But is there something wrong?
Click to expand...
Click to collapse
Which recovery?

splitterzelle said:
Which recovery?
Click to expand...
Click to collapse
Samsung stock recovery which is attached in the first post.

Same prob.
Tyhjäntoimittaja said:
Samsung stock recovery which is attached in the first post.
Click to expand...
Click to collapse
Same here. I've got problems with that Android Stock recovery file. After flashing it, when I tried to go into recovery mode, the dead android logo appeared. However if I reflash CWM everything goes ok. Where can I find another stock android recovery file?, it seems that this one only works for some specific sort of models. Mine is: GT-i9195L. (the "L" doesn't really matter).
Thanks.

[Q] Failed Root?

Hello everyone, before I continue I will give my phone details below:
Model Number: GT-I9505
Andriod version: 4.4.2
Baseband version: I9505XXUFNC5
So my problem is that I followed a guide to rooting my Galaxy S4, after which Odin confirmed to me that my phone had passed the rooting setup, all very good. The problem occurs when checking to see if my phone had successfully being rooted, I downloaded Root Checker Basic which informed me that my phone actually isn't rooted.
So as anyone would do they start the rooting process again, to which the same outcome repeated.
I can not post the link to the guide I used, the website I followed was ibtimes. The guide I followed is named 'Root galaxy s4 (LTE) I9505 on Official Andriod 4.2.2 Kitkat Firmware.
The link above is the guide I used.
So my question is, has anyone else come across this in the past? I did a brief search in the forums prier to posting this but came to no avail.
Thank you for any and all help with regards to my problem!

1. Try to root ur phone 2 times with same method u used.
2. Always KNOX app will block SuperSU app. You will have to freeze or delete KNOX app.

As requested I deleted the KNOX app and tried a Root, it has again come up with the same results, quoting from the SuperSU app 'There is no SU binary installed, and SuperSU cannot install it. This is a problem!'
I can not think as to what I am doing wrong.

Update:
I have factory reset my phone, and tried the root again to which the results are the same, Odin doesn't go yellow, it goes blue but some people say this can be due to different versions.
I have got usb debugging enabled, the battery is charged. This is really frustrating as I was wanting to get put a ROM on my phone today haha.
If anyone has any further advice that will be much appreciated!

Have you tried flashing CWM Recovery to your phone? When exiting CWM if you're not rooted, it'll tell you and ask if you want to root. Select Yes then go back into Android and check your SuperSU.
Otherwise, you could always try use Odin to flash one of Djembys pre-rooted stock roms?
If you're just wanting to flash a custom rom, then you could just download a custom rom, put it on your phone internal storage (or external SD), flash a custom recovery and then flash the rom? That's worked for me in the past.

Try to root again with odin and if your recovery say anything like ''fix root'' always say no

[Guide] Downgrading from 4.3 to 4.1.2 on N7100 (KNOX 0x1 Users Only!)

N7100 4.3 to 4.1.2 Downgrading Guide (Comprehensive)​
Read First!:
Hi there! Welcome to my first guide to downgrading your Jelly Bean OS back to the Stock 4.1.2. By reading this guide I will assume that you have ALREADY TRIPPED YOUR KNOX FLAG (0x1), IF YOU DON'T KNOW WHAT KNOX IS, DON'T USE THIS GUIDE and you have decided to downgrade to stick with 4.1.2 for a better user experience as I did. A couple of notes before we begin, as I feel I need to inform you of the risks you are about to take, however, I WILL NOT BE RESPONSIBLE FOR YOUR DECISIONS / BROKEN DEVICES, ETC by following this guide. This doesn't mean that the guide is faulty by any means (as I did much testing) but that you are willing to take the risks and be accountable for them. Just to be crystal clear.
By upgrading to 4.3 you have already locked your bootloader, which means the device won't let you downgrade to any lower versions or custom ROMS by directly flashing them though ODIN. Till now there has been no fix for unlocking it across all devices and this guide is not able to fix it. However, it can remove the KNOX application, which prevents all root access to the device. This will allow better methods for rooting if you ever require it.
I must also inform you that your IMEI number will temporarily fall when downgrading to 4.1.2. This is common. IMEI registers your device to the mobile network, similar to your PC's MAC Address to connect you to the internet so there can be communication. IMEI and other important information is stored your efs partition which is then read by your modem. 4.3 uses a NEW efs V2 which can't be read by older modems. When you downgrade to 4.1.2, you also downgrade the modem and IMEI can't be read. TO FIX you need to simply revert to your new modem. So it is benificial to create an efs/modem backup in this guide (Just in case).
Once you downgrade to 4.1.2, the bootloader will disable system updates from Samsung. You won't need them anyway, because you will be staying with 4.1.2, if not, then why are you reading this??? But you can directly flash back to official 4.3 via PC Odin as the bootloader allows this. You can get your updates back when on 4.3.
- You must have Wifi active on you phone at all times / Access to Google Playstore
- You need at least 1.5 - 2 GB free in INTERNAL memory free
- Read carefully / take your time
Now that all is clear, lets begin!
Tools Needed:
- Samsung USB Drivers For Windows Download Here
- Register to Sammobile.com for firmwares (Your original stock 4.3 AND desired 4.1.2) Here
- PC Odin (v3.09) Download Here
- Custom Recovery philz-touch V5 (V6 is too buggy) Download Here
- Dr. Ketan's Multitool Advance V6 (Courtesy of Dr. Ketan) Download Here
- Mobile ODIN PRO @ Playstore Purchase Here
- SuperSU (Extract "superuser.apk" from "common" folder) Download Here
- EFS Tool Samsung N7100/900 Here
- (IMPORTANT! 4.3 Modem File) Modem.bin (Extract from the .zip file, I find XXEMJ5 modem works well) Here
Instructions:
Notes: When I say enter DOWNLOAD MODE, power off your device, hold VOLUME DOWN + HOME KEY + POWER KEY until your device displays a warning message. Then press VOLUME UP.
When I say enter RECOVERY MODE, power off your device, hold VOLUME UP + HOME KEY + POWER KEY until your device displays NOTE II N7100 screen then let go.
1.) Download and install Samsung USB drivers for Windows if you haven't already, for PC mobile communication.
2.) Go to sammobile.com (listed above) and get a copy of your official 4.3 firmware AND your desired 4.1.2 version that you want to downgrade to. Pay Attention to get your correct country and carrier ROM! (Smartphone > Android > Galaxy NOTE II N7100 > Your Country/Carrier).
3.) Download and extract Odin 3.09 to your PC's desktop, Right click and choose "Run as Administrator".
4.) On your phone, enter Developer Mode by going to Settings > More > About Device and tapping "Build Number" a few times, until the message "You are now a developer" appears. Back in settings, go to Deveoper Options and enable "USB Debuging".
5.) Connect your phone to PC via USB cable and enter DOWNLOAD mode.
6.) PC Odin should detect your device, by showing a blue bar (COM PORT #) and "Added!" message should pop up. Extract philz-recovery V5.md5 and flash it by checking the checkbox next to AP, then click AP to add the file, and click Start. (Make sure ONLY Auto-reboot and F. Reset time is selected in Odin). --> This is the step that trips KNOX counter.
7.) Wait for green "PASS" to show in Odin and your phone to finish reboot. Now on your PC, go to your GT-N7100 directory and move (DO NOT EXTRACT) [1] Dr. Ketan's Multitool V6.zip AND [2] superuser.apk AND [3] modem.bin (your N7100 4.3 modem) to the "Download" folder on your phone.
8.) Extract your .md5 4.1.2 firmware, and move it to this folder on your phone as well. (4 files in Download folder now)
9.) On your phone, enter RECOVERY mode (you will see a purple skinned custom recovery), touch "Install zip" and "Choose zip from sdcard"
10.) Find your Download folder, and touch Dr. Ketan's Multitool V6.zip. Touch "Yes" to confirm install.
11.) Here, agree to the Terms of Use and touch Next a couple screens. Touch Proceed with Multitool and do the following:
- Root Device/Inject Busybox (Next)
- DeKNOX Device (Next)
- Skip all the rest (Next a couple screens)
- Do NOT change the rest (Next a couple screens)
- When prompted to run, touch RUN. Next and reboot.
12.) Now that your device is KNOX free, go to My Files > All Files, and find the Download folder. Touch superuser.apk. You will get a warning message, just hit "Settings" and find "Unknown Sources" and make sure it is checked. Touch "All" and "Install".
13.) In Supersu, touch "Continue" for Su Binary Update. Select "Normal". A message may indicate it failed, but it still funtions after a little wait.
14.) Install Dr. Ketan's EFS Tool Samsung N7100/900, Just for safety, backup your efs. Grant permissions from Supersu when asked.
15.) On your PC, go to your N-7100 root folder, you will see a new folder called "MyEFS#####" with a file inside (efs.img), copy this folder to a safe place on your computer and keep it.
16.) Install Mobile Odin Pro from Playstore. Run app, grant permissions, download updates.
17.) In Mobile Odin, touch "Open file..." > "Internal SD-card" and navigate to your Download folder. Select your 4.1.2 firmware. Hit OK.
18.) Make sure "Wipe data and cache" AND "Wipe Dalvik cache" is checked (If not, you will see a lovely bootloop, a big NO-NO). Finaly, hit "Flash Firmware" > "Continue"> "Check" for safety sakes.
19.) Wait a little while (About 2 reboots), you are now reverting to 4.1.2. You will be greeted with a welcome screen (Welcome back! ) Sign-in to your device.
20.) Back on 4.1.2, all is well... Except IMEI!!! To fix, go back into Mobile Odin app. Select "Open File..." > "Internal SD-card" > "0" > "Download" > Select "modem.bin".
21.) Touch "Flash Firmware" > "Continue". And wait for reboot. (DO NOT wipe cache this time) ~ DONE! ~ (Optionally, you can now use Triangle Away to clear flash counter, and remove Supersu and Mobile Odin for a cleaner look)
======================================================================================================
If you have any questions, comments or concerns, post here first before you attempt. Say thanks, if it worked for you. Finally, thank YOU for reading my guide.

This work for 4.4.2 or only is for 4.3?

killerkiller said:
This work for 4.4.2 or only is for 4.3?
Click to expand...
Click to collapse
I haven't tested 4.4.2 steps are similar, but I highly don't recommend.
Things to keep in mind:
- Instead of 4.3 firmware, download a backup of your current stock 4.4.2 that to can recover to.
- 4.3 modems reported not to work on 4.4.2 and I read the new bootloader is preventing EFS writing.
- Knox in 4.4.2 has been upgraded to V2.0 and Dr. Ketan's tool may not be able to temporarily stop it

Sorry if this is a stupid quesiton. Does any of this apply to the Sprint Note 2, or would that be a different process for going from 4.4.2 with 0x1 Knox back to 4.1.2?

No, it *should* work fine with Mobile Odin.

kristoff123 said:
Sorry if this is a stupid quesiton. Does any of this apply to the Sprint Note 2, or would that be a different process for going from 4.4.2 with 0x1 Knox back to 4.1.2?
Click to expand...
Click to collapse
Not at all, I'm glad you asked. I specifically designed this guide for N7100 International version only. But, since you've mentioned it I would imagine steps would be similar with Mobile Odin (standard) with different conditions. I suggest extreme caution if you even think to try.
Again, here are your conditions:
- Find your stock 4.4.2 you can flash to recover to if things go wrong. (Sprint's version of 4.1.2 to downgrade to as well).
- Dr. Ketan's tool is designed to work on 4.3, and may not work on 4.4.x therefore you need to find a manual way to root, and stop Knox security components before Mobile Odin can be used.
- MOST importantly, your Sprint modem contains LTE capabilities which is different from International HSPA only modems. Therefore, you must find a copy or backup your current 4.4.2 modem for flashing later. Failure to do this will result in unreadable IMEI and loss of calling/texting functions.
So only do it if you like risks or have the resources. I hope you find this information useful.

OOps
I wish I had seen this a good few weeks ago

4.4.2 - 4.1 N7100 Downgrade
Thanks, the guide worked ok for me to downgrade from 4.4.2 to 4.1.2, though i rooted with an Autoroot.zip file for 4.4.2 which also deknoxed and used philzstouch cwm recovery to install it.
Dr Ketans multitool advance v6 was a bit buggy with 4.4.2 and froze if i went too fast, though it did backup my efs eventually.
My problem is that even after I restore my efs and my imei is back, i still get, 'service state : out of service' and cannot make phone calls.
Though this is likely because I accidentally bought a used note 2 off ebay which has a cloned IMEI (the one in the phone is different from the one on the back) as the phones real IMEI is reported as lost or stolen and so blocked by the network. (I did try to return the phone to its rightful owner, but they don't let you do that, they just block the IMEI and make it useless! , prob because they sell more phones that way)
I was hoping 4.1.2 would work with this dodgy 'cloned' IMEI but it does not seem to!

Please tell me after downgrade in download mode the knox thingy still shows?
Edit. Answer myself. Since the bootloader is not downgraded the knox thingy will be there.
Sent from my GT-N7100

Downgrade 4.4.2 - mobile odin not working
i followed the steps on 4.4.2 (official ROM) to downgrade, however, mobile odin did not worked properly.
After initiating the Flash Rom on mobile Odin, it shows all the pop-ups until rebooting device.....however...the device does not reboot....
Followed below process:
1- Flash 4.4.2 Stock ROM via Odin
2- Install CWM Recovery
3- Using Dr Ketan tool DeKnox the phone
4- Root the device using autoroot via Odin
5- Install SuperSU (checked for working)
6- Install Mobile Odin
7- Followed the steps on Mobile Odin to flash 4.1.2 & 4.3 (both not working)
any help here is appreciated!!!

successfully downgraded to 4.1.2 from 4.4.2
manual reboot to recovery mode did the trick!!!
wipe data is a must...i did go into a boot loop...then reflashed....post which I was also able to downgrade to 4.3 and then followed the steps to 4.1!!!
boot loader remains the same!!! now showing Knox & flash count!!
however, my problem of no sound in-call is not resolved!!! this issue was developed after i upgraded to 4.4.3

dude_charming said:
manual reboot to recovery mode did the trick!!!
wipe data is a must...i did go into a boot loop...then reflashed....post which I was also able to downgrade to 4.3 and then followed the steps to 4.1!!!
boot loader remains the same!!! now showing Knox & flash count!!
however, my problem of no sound in-call is not resolved!!! this issue was developed after i upgraded to 4.4.3
Click to expand...
Click to collapse
Forgive me for not supporting you and this thread for a while, I was mostly active on Knox threads researching. I am glad it worked up until the point of returning to official 4.1.2 software, even using 4.4.x Kitkat.
You cannot downgrade a locked bootloader. If you updated to the latest 4.4.3 you will be stuck on it. My phone came with the 4.3 bootloader and still is. You can use Triangle Away to reset flash count all the way back to 1, but it will not return to 0 due to Knox security. (Once Knox is 0x1 it can't be reset as of now)
Can you explain your no-sound in-call problem? Is this on 4.1.2 firmware or 4.4.3? Is relating to only your dialer or other apps as well?

stevelav said:
Thanks, the guide worked ok for me to downgrade from 4.4.2 to 4.1.2, though i rooted with an Autoroot.zip file for 4.4.2 which also deknoxed and used philzstouch cwm recovery to install it.
Dr Ketans multitool advance v6 was a bit buggy with 4.4.2 and froze if i went too fast, though it did backup my efs eventually.
My problem is that even after I restore my efs and my imei is back, i still get, 'service state : out of service' and cannot make phone calls.
Though this is likely because I accidentally bought a used note 2 off ebay which has a cloned IMEI (the one in the phone is different from the one on the back) as the phones real IMEI is reported as lost or stolen and so blocked by the network. (I did try to return the phone to its rightful owner, but they don't let you do that, they just block the IMEI and make it useless! , prob because they sell more phones that way)
I was hoping 4.1.2 would work with this dodgy 'cloned' IMEI but it does not seem to!
Click to expand...
Click to collapse
Actually this guide doesn't touch your IMEI data, I just suggest people to back it up for safety reasons. If you came from 4.4.2, you need to restore your 4.4.2 .bin modem file (your country) for your IMEI to work. (I do not know if this is the case for cloned IMEI as I do not know the status of your phone.)
PS. (Yes philz-touch v6 is very buggy, and it will hang if you do not have fast fingers. Use V5)

[Q] [HELP] i9505 Recovery Booting Stuck

Hello guys,
I need your help again!
I recently changed my i9100g with this other device, GT-I9505 Italian version, no brand.
The history of this device was quite this: stock FW until 4.3 (just my suppose) --> CM11 --> try to flash 4.2.2 stock --> brick @[email protected]
Now I tried to put the original 4.4.2 firmware by flashing with Odin v3.09, because I don't want custom rom for the moment, just make it work.
The problem is that the phone stucks at Samsung logo, and when I tried to go in recovery mode, it stays on the same logo but there's a blue write in the top left corner "Recovery Booting".
Do you have any suggestion?
TY in advance

Drake9090 said:
Hello guys,
I need your help again!
I recently changed my i9100g with this other device, GT-I9505 Italian version, no brand.
The history of this device was quite this: stock FW until 4.3 (just my suppose) --> CM11 --> try to flash 4.2.2 stock --> brick @[email protected]
Now I tried to put the original 4.4.2 firmware by flashing with Odin v3.09, because I don't want custom rom for the moment, just make it work.
The problem is that the phone stucks at Samsung logo, and when I tried to go in recovery mode, it stays on the same logo but there's a blue write in the top left corner "Recovery Booting".
Do you have any suggestion?
TY in advance
Click to expand...
Click to collapse
Flash the stock rom again..and do NOT check autoreboot in odin.
The straight away boot into recovery, factory reset it..and you'll boot
"If someone helps, never forget to hit thanks ? "

DeepankarS said:
Flash the stock rom again..and do NOT check autoreboot in odin.
The straight away boot into recovery, factory reset it..and you'll boot
"If someone helps, never forget to hit thanks ? "
Click to expand...
Click to collapse
Thank you very much for your reply!
It doesn't work, maybe I'm just doing something wrong, what should I have to do after flash?

Drake9090 said:
Thank you very much for your reply!
It doesn't work, maybe I'm just doing something wrong, what should I have to do after flash?
Click to expand...
Click to collapse
-Open odin
-Uncheck autoreboot
-Add your firmware file to the AP/PDA section
-Start the process
When this will end, your ohone wont boot automatically (obviously)
After 2-3 minutes start it, if it turns on properly congo..
If it doesnt..just boot into recovery (volume up+home button+power button) and perform a data wipe.
If this does not helo at all, download the LATEST KITKAT 4.4.2 UNBRANDED again for your phone as it can be a bad download issue too.
"If someone helps, never forget to hit thanks ? "

DeepankarS said:
-Open odin
-Uncheck autoreboot
-Add your firmware file to the AP/PDA section
-Start the process
When this will end, your ohone wont boot automatically (obviously)
After 2-3 minutes start it, if it turns on properly congo..
If it doesnt..just boot into recovery (volume up+home button+power button) and perform a data wipe.
If this does not helo at all, download the LATEST KITKAT 4.4.2 UNBRANDED again for your phone as it can be a bad download issue too.
"If someone helps, never forget to hit thanks ? "
Click to expand...
Click to collapse
I would try another firmware less recent, just to see what happens...
But I have great news: Philz touch works, so now I have a working custom recovery!
the problem is that I can't just flash a custom ROM to repair
I think I need the pit file, but I can't find one on the internet @[email protected]

Drake9090 said:
I would try another firmware less recent, just to see what happens...
But I have great news: Philz touch works, so now I have a working custom recovery!
the problem is that I can't just flash a custom ROM to repair
I think I need the pit file, but I can't find one on the internet @[email protected]
Click to expand...
Click to collapse
Y do you need a pit? Pit files are not to be played with and can possibly brick if not flashed with utmost care.
Try a stock firmware first. Dont try any stock firmware till you have a working phone..
"If someone helps, never forget to hit thanks ? "

DeepankarS said:
Y do you need a pit? Pit files are not to be played with and can possibly brick if not flashed with utmost care.
Try a stock firmware first. Dont try any stock firmware till you have a working phone..
"If someone helps, never forget to hit thanks ? "
Click to expand...
Click to collapse
I'm flashing this firmware: I9505XXUGNG8_I9505ITVGNG1_ITV
I was thinking about pit because the philz says strange errors:
failed to mount /data to setup /data/media, or something like this... and also other problems related to /sdcard
Have you an idea on what to do?
I'm just following this guide: http://forum.xda-developers.com/showthread.php?t=2265477

Drake9090 said:
I'm flashing this firmware: I9505XXUGNG8_I9505ITVGNG1_ITV
I was thinking about pit because the philz says strange errors:
failed to mount /data to setup /data/media, or something like this... and also other problems related to /sdcard
Have you an idea on what to do?
I'm just following this guide: http://forum.xda-developers.com/showthread.php?t=2265477
Click to expand...
Click to collapse
The pit file is right there in @samersh72s thread
In the attachments.
Flash properly after reading the OP very carefully and DO NOT SKIP ANY STEP OR MODIFY any
Still IMHO a data wipe after reflashing can fix your bootloop.
"If someone helps, never forget to hit thanks ? "

DeepankarS said:
The pit file is right there in @samersh72s thread
In the attachments.
Flash properly after reading the OP very carefully and DO NOT SKIP ANY STEP OR MODIFY any
Still IMHO a data wipe after reflashing can fix your bootloop.
"If someone helps, never forget to hit thanks ? "
Click to expand...
Click to collapse
I thought the same way too, but didn't work...
The attachment doesn't work, but some posts later there is one working
I'll try and let you know the results!

Stll locked here...
Used yhe pit file, but nothing changed
in Philz Touch 6 with CWM 6.0.4.7 I have this error:
E: could not mount /data to setup /data/media path!
Have you ever faced it?

Drake9090 said:
Used yhe pit file, but nothing changed
in Philz Touch 6 with CWM 6.0.4.7 I have this error:
E: could not mount /data to setup /data/media path!
Have you ever faced it?
Click to expand...
Click to collapse
Ermm no...
@Lennyz1988 @MAX 404
Help?
Sent from my GT-I9500 using XDA Free mobile app

I was thinking about a possible cause: could it be that I'm using a wrong firmware?
this device is used, so I supposed that it was ITV the correct firmware, but not 100% sure...
I'm just sure that it is no-brand.

Drake9090 said:
I was thinking about a possible cause: could it be that I'm using a wrong firmware?
this device is used, so I supposed that it was ITV the correct firmware, but not 100% sure...
I'm just sure that it is no-brand.
Click to expand...
Click to collapse
Screenshots of "phone info samsung" app please.
"If someone helps, never forget to hit thanks ?"

When you flash the Odin firmware it's succesfull?

DeepankarS said:
Screenshots of "phone info samsung" app please.
"If someone helps, never forget to hit thanks ?"
Click to expand...
Click to collapse
The only info that I'm able to see are the ones in download mode...
If the phone don't boot any firmware, how can I use that app?

Lennyz1988 said:
When you flash the Odin firmware it's succesfull?
Click to expand...
Click to collapse
Yes, or better to say, Odin says PASS, but when I reboot (even with or without Auto-Reboot flag) the phone stucks on Samsung Logo saying Recovery Booting.

DeepankarS said:
The pit file is right there in @samersh72s thread
In the attachments.
Flash properly after reading the OP very carefully and DO NOT SKIP ANY STEP OR MODIFY any
Still IMHO a data wipe after reflashing can fix your bootloop.
"If someone helps, never forget to hit thanks ? "
Click to expand...
Click to collapse
Drake9090 said:
Yes, or better to say, Odin says PASS, but when I reboot (even with or without Auto-Reboot flag) the phone stucks on Samsung Logo saying Recovery Booting.
Click to expand...
Click to collapse
On top of all advice given here...
Can you boot at all? what is the status at the moment , rom recovery?
I would try to flash a recovery first ( twrp , philz) see if it works , do a factory reset ( backup first) and try flashing a stock rom,,see if it helps

MAX 404 said:
On top of all advice given here...
Can you boot at all? what is the status at the moment , rom recovery?
I would try to flash a recovery first ( twrp , philz) see if it works , do a factory reset ( backup first) and try flashing a stock rom,,see if it helps
Click to expand...
Click to collapse
The situation is still the same, so in order:
I cannot boot a complete system, I just stuck on samsung i9505 logo with blue "Recovery Booting" written in top-left on the screen;
At the moment I'm reflashing ossessively the stock rom, and philz touch; I can go in DL mode and not in the stock recovery, but when I flash philz touch I can enter by double clicking vol up when I see the blue, red and yellow writes.
I cannot do a factory reset, that is the real problem I suppose, 'cause when I enter in philz recovery, it says: "error mount /data etc etc..." as you can see in previous posts.
In DL mode this is the situation:
PN: GT-I9505
Current binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
csb-config-lsb: 0x30
write prot: enabled
eMMC Burst mode enabled

Drake9090 said:
The situation is still the same, so in order:
I cannot boot a complete system, I just stuck on samsung i9505 logo with blue "Recovery Booting" written in top-left on the screen;
At the moment I'm reflashing ossessively the stock rom, and philz touch; I can go in DL mode and not in the stock recovery, but when I flash philz touch I can enter by double clicking vol up when I see the blue, red and yellow writes.
I cannot do a factory reset, that is the real problem I suppose, 'cause when I enter in philz recovery, it says: "error mount /data etc etc..." as you can see in previous posts.
In DL mode this is the situation:
PN: GT-I9505
Current binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
csb-config-lsb: 0x30
write prot: enabled
eMMC Burst mode enabled
Click to expand...
Click to collapse
Lets go one step at the time.........forget about recovery for now
Flashing with Odin a stock rom ( use same rom you had before or newer) , what happen? did you followed the guide
http://forum.xda-developers.com/show....php?t=2265477 that @DeepankarS suggested ? did you flash the PIT file?

MAX 404 said:
Lets go one step at the time.........forget about recovery for now
Flashing with Odin a stock rom ( use same rom you had before or newer) , what happen? did you followed the guide
http://forum.xda-developers.com/show....php?t=2265477 that @DeepankarS suggested ? did you flash the PIT file?
Click to expand...
Click to collapse
Followed that guide many times, but the result is stuck in Samsung Logo.
Even tried flashing PIT file, but nothing changed.
maybe flash just a stock recovery after the firmware could solve the problem?

Help recovering data

So I have a friend who decided to mess with his phone, of course without doing a backup, and now he's stuck in a situation that it can't boot even into recovery.
Currently all I see when booting to recovery:
Recovery Booting. . . . .
Set Warranty Bit : recovery
The phone is G900F
He has no idea what version was installed on it before.
I don't need the phone to boot, I need to recover the files on it.
Being a oneplus person myself, I'm not that familiar with samsung phones (my latest samsung was s2).
I've tried to install with odin (3.0.7 - if that matters) the following recoveries:
official twrp 2.8.7
twrp
cwm
All these recoveries showed "Recovery is not seandroid enforcing" message as well as the above when trying to boot into recoveries.
I've tried the official recovery as well:
https://forum.xda-developers.com/galaxy-s5/general/sm-g900f-stock-recovery-5-0-lollipop-t3228871
which removed the "seandroid" message, but that's all.
Not sure what I'm missing.
Any help would be appreciated!

Tahvok said:
So I have a friend who decided to mess with his phone, of course without doing a backup, and now he's stuck in a situation that it can't boot even into recovery.
Currently all I see when booting to recovery:
Recovery Booting. . . . .
Set Warranty Bit : recovery
The phone is G900F
He has no idea what version was installed on it before.
I don't need the phone to boot, I need to recover the files on it.
Being a oneplus person myself, I'm not that familiar with samsung phones (my latest samsung was s2).
I've tried to install with odin (3.0.7 - if that matters) the following recoveries:
official twrp 2.8.7
twrp
cwm
All these recoveries showed "Recovery is not seandroid enforcing" message as well as the above when trying to boot into recoveries.
I've tried the official recovery as well:
https://forum.xda-developers.com/galaxy-s5/general/sm-g900f-stock-recovery-5-0-lollipop-t3228871
which removed the "seandroid" message, but that's all.
Not sure what I'm missing.
Any help would be appreciated!
Click to expand...
Click to collapse
Hmm...
I see that your friend messed up his phone very well .....
Hopefully the eMMC memory is not corrupted becuase then only motherboard replacement would be necessary.
Summarising what you wrote:
1. you flashed "official recovery 2.8.7" -> where did you get it from? 2.8.7 is the very old version!
2. you flashed unofficial TWRP very old (2014) recovery (I checked your link)
3. you flashed unofficial CWM very old (2014) recovery (I checked your link)
4. finally you flashed stock, from old OS 5.0 Lollipop recovery provided from entrusted source - nobody reported that it works in the thread.
I listed this for you in order to underline one thing - READ, READ, READ, ASK, ASK, ASK .... before flashing anything to the phone and tell it to your friend.
Le's start with flashing from ODIN ver 3.12.7 (I am using it) this version of TWRP:
twrp-3.1.1-0-klte.img.tar for G900F which is the latest official recovery:
https://twrp.me/samsung/samsunggalaxys5qualcomm.html
Read how to flash it with odin method (when you open the link).
Edit: Are you sure the phone is SM-G900F? Please check model number on the label under battery (inside the phone).
Edit2: When you enter odin mode check phone model version as well - it is provided by installed bootloader.

Many40 said:
Hmm...
I see that your friend messed up his phone very well .....
Hopefully the eMMC memory is not corrupted becuase then only motherboard replacement would be necessary.
Summarising what you wrote:
1. you flashed "official recovery 2.8.7" -> where did you get it from? 2.8.7 is the very old version!
2. you flashed unofficial TWRP very old (2014) recovery (I checked your link)
3. you flashed unofficial CWM very old (2014) recovery (I checked your link)
4. finally you flashed stock, from old OS 5.0 Lollipop recovery provided from entrusted source - nobody reported that it works in the thread.
I listed this for you in order to underline one thing - READ, READ, READ, ASK, ASK, ASK .... before flashing anything to the phone and tell it to your friend.
Le's start with flashing from ODIN ver 3.12.7 (I am using it) this version of TWRP:
twrp-3.1.1-0-klte.img.tar for G900F which is the latest official recovery:
https://twrp.me/samsung/samsunggalaxys5qualcomm.html
Read how to flash it with odin method (when you open the link).
Edit: Are you sure the phone is SM-G900F? Please check model number on the label under battery (inside the phone).
Edit2: When you enter odin mode check phone model version as well - it is provided by installed bootloader.
Click to expand...
Click to collapse
First, thank you for trying to help me!
Please see attachments:
https://drive.google.com/folderview?id=1euC7-CoBeeUQxTGXQnPPgRE2-5VxFXLh
You can see that it is indeed g900f. I've also checked under the battery.
I've flashed the recovery you asked, however I could not find odin 3.12.7 only 3.12.10, so I've flashed with that (the odin thread on xda does not provide a link for 3.12.7 download).
You can see that it's still not booting with that recovery, it's just stuck at "booting recovery" screen.
I'm thinking perhaps it has a bad bootloader? How would you suggest to proceed?

Tahvok said:
First, thank you for trying to help me!
Please see attachments:
https://drive.google.com/folderview?id=1euC7-CoBeeUQxTGXQnPPgRE2-5VxFXLh
You can see that it is indeed g900f. I've also checked under the battery.
I've flashed the recovery you asked, however I could not find odin 3.12.7 only 3.12.10, so I've flashed with that (the odin thread on xda does not provide a link for 3.12.7 download).
You can see that it's still not booting with that recovery, it's just stuck at "booting recovery" screen.
I'm thinking perhaps it has a bad bootloader? How would you suggest to proceed?
Click to expand...
Click to collapse
Ok. Let's continue ... I hope (as I had very similar situation) that the phone is not hardbricked and eMMC memory is not corrupted -> I faced this on my phone and finally had to replace motherboard.
But let's be optimistic:
1. For data recovery - I don't have a silver bullet for this but I found this software: http://www.recover-android-iphone.com/recover-android/how-to-recover-data-bricked-samsung.html
It needs working odin mode so under condition that it supports s5 G900F it should be able to restore some data.
2. For unbricking - I recommend to flash via odin the latest official Samsung stock firmware dedicated to your friend's country/region:
https://www.sammobile.com/firmwares/galaxy-s5/SM-G900F/
You must be registered to download the software. Link for odin 3.12.7 is available on the bottom of the download page.
Just to underline - odin flash most probably (anybody please confirm that) will wipe your data so be aware of that.
Good luck.

Many40 said:
Ok. Let's continue ... I hope (as I had very similar situation) that the phone is not hardbricked and eMMC memory is not corrupted -> I faced this on my phone and finally had to replace motherboard.
But let's be optimistic:
1. For data recovery - I don't have a silver bullet for this but I found this software: http://www.recover-android-iphone.com/recover-android/how-to-recover-data-bricked-samsung.html
It needs working odin mode so under condition that it supports s5 G900F it should be able to restore some data.
2. For unbricking - I recommend to flash via odin the latest official Samsung stock firmware dedicated to your friend's country/region:
https://www.sammobile.com/firmwares/galaxy-s5/SM-G900F/
You must be registered to download the software. Link for odin 3.12.7 is available on the bottom of the download page.
Just to underline - odin flash most probably (anybody please confirm that) will wipe your data so be aware of that.
Good luck.
Click to expand...
Click to collapse
Why a full firmware is needed? Perhaps I can flash only the parts required to get into recovery? I count mount the phone from recovery, that's why it's my priority.
I would like to know also if odin will wipe everything if flashing a full firmware?

Tahvok said:
Why a full firmware is needed?
Click to expand...
Click to collapse
Because it is commonly recommended way to unbrick a phone.
Perhaps I can flash only the parts required to get into recovery?
Click to expand...
Click to collapse
Perhaps, yes. But:
1. I don't exactly know what restricts your recovery to run properly. Flashing separate recovery failed.
2. You, for example, could try flashing separately one of the latest bootloaders dedicated to G900F from BL section with odin but I doubt it would help.
I count mount the phone from recovery, that's why it's my priority.
I would like to know also if odin will wipe everything if flashing a full firmware?
Click to expand...
Click to collapse
As far as I know yes but I am not 100% sure because I didn't try that myself on s5.
I would appreciate if somebody else confirms that.

Many40 said:
2. You, for example, could try flashing separately one of the latest bootloaders dedicated to G900F from BL section with odin but I doubt it would help.
Click to expand...
Click to collapse
Can you suggest a bootloader for me? I would like to try that first.

Tahvok said:
Can you suggest a bootloader for me? I would like to try that first.
Click to expand...
Click to collapse
In my opinion, if odin mode works then bootloader should be OK. But as you wish -
tell me first what stock firmware will you later on trying to flash on your friends phone or in which country the phone will be operated.

Many40 said:
In my opinion, if odin mode works then bootloader should be OK. But as you wish -
tell me first what stock firmware will you later on trying to flash on your friends phone or in which country the phone will be operated.
Click to expand...
Click to collapse
Hong Kong

Tahvok said:
Hong Kong
Click to expand...
Click to collapse
Latest available Firmware version for Hong Kong is G900FZHS1CQD1 however I can't find a separate flashable bootloader for you.
Generaly, in my opinion you might try any of the latest bootloaders compatible with SM-G900F phone (here you can find a collection: https://forum.xda-developers.com/showpost.php?p=54094068&postcount=3, I am on G900FXXS1CQI4) but again:
1. I doubt it will help for entering recovery;
2. I still recommend to flash complete stock firmware to unbrick the phone.
However if you anyway decide to try with a bootloader, flash it with odin from BL section (untick auto reboot). Also turn off the phone before and after flashing and pull out battery for about 30 sec. It happens that bootloader doesn't flash properly at once even the odin says "PASS" so some people reported that they needed to repeat flashing a few times. I managed to flash bootloader at first time.

Unfortunateely the phone is not with me anymore, so I won't be able to continue testing. Thank you anyway for trying to help me! I really appreciate your help!