Related
I have PayPal for which I will use to donate an amount to the person(s) who can help me.
I just recently got a new GS4 becuase of an insurance replacement. I looked at the specs before I flashed TWRP. After failing to install 4.2.2 ROMS, I finally found a 4.3 mk2 stock ROM to install. I have the phone working. But TWRP is not installed. My phone tests positive for ROOT with Rootchecker
Currently I'm getting this message everytime I boot "Kernel is not seandroid enforcing"
I have multiple 4.4.2 and 4.3 ROMs I like to use on my SD card, I'd like to continue from a TWRP backup i've made using that recovery.
Here are my current specs:
Model
SGH-M919
Android Version
4.3
Baseband
M919UVUEMK2
Kernel Version
[email protected] #1
Build Number
JSS15J.M919UVUEMK2
SELinux status
Permissive
Secure boot status
Type: Samsung
The replacement phone was probably already on the MK2 bootloader and modem when you received it. Which means you had Knox pre-installed and tripped it when you rooted the phone. The "kernel is not seandroid enforcing" error message does not affect the functioning of your phone in any way. It's just a part of the Knox bootloader. You can continue to re-install TWRP recovery and flash any ROM you want. Your phone will function as normal. Just don't try reverting to the 4.2.2 MDL baseband/modem because it won't work. There's currently no way to revert to 4.2.2 MDL if you're on MK2 or higher. If you want to get rid of the message just flash the stock kernel in a recovery.
Try to be careful with your replacement phone now since you tripped Knox. It might be harder to get a replacement depending on how T-Mobile is.
No donations are needed for these kinds of things.
Ok Im flashing Infamous 4.4.2 Version 3.7 after ODIN flashing TWRP 2.6.3.1
The only reason I'm flashing that ROM is because no backups are not showing theirselvesin the Restore option, what would cause that?
Is TWRP 2.5.0.2 better?
Did I miss a step? All my actions were using odin to flash the twrp recover, and then flash another ROM, or restoring a Previous Back. Should I have flashed a rooted bootloader, or rooted firmware or anything besides those two?
nopotential said:
Ok Im flashing Infamous 4.4.2 Version 3.7 after ODIN flashing TWRP 2.6.3.1
The only reason I'm flashing that ROM is because no backups are not showing theirselvesin the Restore option, what would cause that?
Is TWRP 2.5.0.2 better?
Click to expand...
Click to collapse
The backups could either be stored on the internal or external SD card. Try switching between both and see if they appear. They'll be in the TWRP folder on the root of either the internal/external storage.
I've had no problems with the latest TWRP v2.7.0.1. If you have problems then use v2.5.0.2.
If you have connection problems after installing Infamous 4.4.2, you might need to Odin the newest KitKat NB4 modem found here.
Download the file and flash MODEM.bin via Odin under the phone slot.
Personally, since you already tripped Knox, you should just Odin flash the complete NB4 KitKit stock ROM which will give you the newest modem without having to mess with anything else or do various flashing of things. Everything for flashing NB4 KitKit can be found here. Download the full 4.4 firmware from here.
brian117 said:
The backups could either be stored on the internal or external SD card. Try switching between both and see if they appear. They'll be in the TWRP folder on the root of either the internal/external storage.
I've had no problems with the latest TWRP v2.7.0.1. If you have problems then use v2.5.0.2.
If you have connection problems after installing Infamous 4.4.2, you might need to Odin the newest KitKat NB4 modem found here.
Download the file and flash MODEM.bin via Odin under the phone slot.
Personally, since you already tripped Knox, you should just Odin flash the complete NB4 KitKit stock ROM which will give you the newest modem without having to mess with anything else or do various flashing of things. Everything for flashing NB4 KitKit can be found here. Download the full 4.4 firmware from here.
Click to expand...
Click to collapse
I want to use a custom ROM because of the features. Should I still flash the latest firmware, the KitKat NB4?
nopotential said:
I want to use a custom ROM because of the features. Should I still flash the latest firmware, the KitKat NB4?
Click to expand...
Click to collapse
You will still be able to flash the custom ROM after you Odin flash the KitKat NB4 firmware. The steps are as followed:
1. Open Odin v3.07.
2. UNcheck the boxes that say auto reboot and f. reset time.
3. Power off your phone and enter Download Mode by holding down the Vol DOWN + Home + Power buttons at the same time. Hit Vol UP after the warning message comes up.
4. Connect your phone to your PC and wait for it to appear in the COM: box in Odin.
5. Click the PDA tab and select the "M919UVUFNB4_HOME.tar.md5" file that you extracted from http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip.
6. Wait for it to run an MD5 check. The program will freeze and unfreeze when it's done.
7. Click start and let Odin flash the ROM.
8. When it says PASS, unplug the phone and long press the power button until the phone turns off and reboots on its own. Leave it alone for about 2 minutes and then power it off.
9. Reboot back into Download Mode and then flash the CF-Autoroot found here.
10. Flash that via the PDA slot in Odin, reboot, and you should now be rooted. You can then continue to do everything else such as install TWRP and flash Infamous 4.4.2.
brian117 said:
You will still be able to flash the custom ROM after you Odin flash the KitKat NB4 firmware. The steps are as followed:
1. Open Odin v3.07.
2. UNcheck the boxes that say auto reboot and f. reset time.
3. Power off your phone and enter Download Mode by holding down the Vol DOWN + Home + Power buttons at the same time. Hit Vol UP after the warning message comes up.
4. Connect your phone to your PC and wait for it to appear in the COM: box in Odin.
5. Click the PDA tab and select the "M919UVUFNB4_HOME.tar.md5" file that you extracted from http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip.
6. Wait for it to run an MD5 check. The program will freeze and unfreeze when it's done.
7. Click start and let Odin flash the ROM.
8. When it says PASS, unplug the phone and long press the power button until the phone turns off and reboots on its own. Leave it alone for about 2 minutes and then power it off.
9. Reboot back into Download Mode and then flash the CF-Chain's Autoroot found here.
10. Flash that via the PDA slot in Odin, reboot, and you should now be rooted. You can then continue to do everything else such as install TWRP and flash Infamous 4.4.2.
Click to expand...
Click to collapse
Thanks for the step by step. I'm following it now. The NB4_HOME.tar.md5 is taking a long time to flash with ODIN. But I will follow it closely, if everything looks good I'll send out a donation, I appreciate your help.
nopotential said:
Thanks for the step by step. I'm following it now. The NB4_HOME.tar.md5 is taking a long time to flash with ODIN. But I will follow it closely, if everything looks good I'll send out a donation, I appreciate your help.
Click to expand...
Click to collapse
Like I said donations are not needed. It does take a while for it to flash through Odin so that's normal.
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
nopotential said:
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
Click to expand...
Click to collapse
My Wifi is unable to be turned on in this stock rom. I'm going to flash TWRP and then Infamous
nopotential said:
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
Click to expand...
Click to collapse
Yes that will happen. You just boot into recovery and factory reset and it will boot. Let me know if that works.
nopotential said:
My Wifi is unable to be turned on in this stock rom. I'm going to flash TWRP and then Infamous
Click to expand...
Click to collapse
If you continue to have WiFi problems, flash this via recovery.
brian117 said:
Yes that will happen. You just boot into recovery and factory reset and it will boot. Let me know if that works.
If you continue to have WiFi problems, flash this via recovery.
Click to expand...
Click to collapse
It looks like everything is looking good by following your list. Thank you.
nopotential said:
It looks like everything is looking good by following your list. Thank you.
Click to expand...
Click to collapse
Awesome! Good to hear man. Enjoy KitKat and the newest modem. The new modem has gave a significant reception boost for a lot of people. Hope it's the same for you. And please check your PM.
-Deleted-
Ok the backround. about 5 days ago the software update started. All seemed ok but then I was getting reboots 4-5 times a day. Brought it to AT&T and they tried to reflash. After backing up info I signed the release form holding them not liable for bricking the phone. Asked the tech how many have bricked on him and he said none. Sorry I was his first...maybe. Screen asking for Kies program to repair. AT&T tech not allowed to use Kies. I downloaded Kies but no luck.
Got the bugger to go to the Boot screen of "Warning...a custom OS....". Then the "Downloading, do not turn of target" screen. It is stuck there or I should say I have left it there. Top of screen says Odin Mode (in red), Produce Name: SGH-I747, Current Binary: Samsung Official, Qualcomm SecureBoot: Enabled, Warranty Bit: 0, Bootloader Ap SWREV: 3.
I have downloaded Odin 3.09. I have the USB drivers installed. I want to restore last known version of AT&T android 4.2.2 or the upgrade 4.3 that didn't seem to take. I am not sure which version it was running before the crash. My wife's S3 is running 4.3.
What Next? Where do I get the file to upload to the phone? Thanks.
So your s3 was trying to upgrade from 4.1.2 or 4.3?
thenexusgeneration said:
So your s3 was trying to upgrade from 4.1.2 or 4.3?
Click to expand...
Click to collapse
Not sure. I think I checked the build version after the install and it read 4.2.2. Can't be absolutely certain when i saw that build number. Would make sense to check it after the install assuming the install happened at all. But again the wife and I bought the two S3's at the same time and hers is running 4.3.
If you got the ota a few days ago, and judging from the SWREV (Software Revision), you are currently on 4.4.2 firmware (NE4). This means you cannot flash older firmware on Odin (or any other way, OT it'll really brick). From now on you can only flash NE4 firmware.
You can, however, flash older roms.
If you haven't already, try factory resetting from recovery. (This will wipe all your data including the internal sdcard)
If that doesnt work, my only other suggestion is to flash TWRP via Odin, then boot TWRP recovery and flash the stock NE4 rom from enewman17.
DocHoliday77 said:
If you got the ota a few days ago, and judging from the SWREV (Software Revision), you are currently on 4.4.2 firmware (NE4). This means you cannot flash older firmware on Odin (or any other way, OT it'll really brick). From now on you can only flash NE4 firmware.
You can, however, flash older roms.
If you haven't already, try factory resetting from recovery. (This will wipe all your data including the internal sdcard)
If that doesnt work, my only other suggestion is to flash TWRP via Odin, then boot TWRP recovery and flash the stock NE4 rom from enewman17.
Click to expand...
Click to collapse
I can't get to the factory reset screen, only the warning screen before pressing volume up to load a custom OS. I'm confused....well on may levels but I digress. I thought ROM and firmware were the same thing.
Also the TWRP site has two files, same file I Assume, in different formats, md5 and tar. Are they the same file? Do I use one over the other? To flash TWRP using Odin what screen should I start with on the S3? thanks.
To boot recovery hold volume up, home and power. When it vibrates release power only.
A rom (as we use it here) is just the O/S on the /system partition and is usually flashed in recovery. They also include kernels most of the time. The firmware is this, and more. It includes images for multiple partitions. (aboot, sbl2, sbl3, tz, rpm, modem, recovery, boot, system, cache)
Around here you'll see a lot of folks refer to this as just the bootloaders, but they are talking about the base firmware. Sorry if I confuse anyone with that btw, I try to remember to call it the bootloaders, but am just used to using the term firmware.
As for flashing twrp from odin, it must be a .tar or .tar.md5. Both are used by odin. The .md5 extension just tells odin a hash value is included. It will then run an md5 checksum to verify the file about to be flashed is valid, or not corrupted. Either one will work, but the .tar.md5 is safer. If the download gets corrupted somehow, odin will catch it and refuse to flash.
When flashing anything in odin you need to be in Download mode.
DocHoliday77 said:
To boot recovery hold volume up, home and power. When it vibrates release power only.
A rom (as we use it here) is just the O/S on the /system partition and is usually flashed in recovery. They also include kernels most of the time. The firmware is this, and more. It includes images for multiple partitions. (aboot, sbl2, sbl3, tz, rpm, modem, recovery, boot, system, cache)
Around here you'll see a lot of folks refer to this as just the bootloaders, but they are talking about the base firmware. Sorry if I confuse anyone with that btw, I try to remember to call it the bootloaders, but am just used to using the term firmware.
As for flashing twrp from odin, it must be a .tar or .tar.md5. Both are used by odin. The .md5 extension just tells odin a hash value is included. It will then run an md5 checksum to verify the file about to be flashed is valid, or not corrupted. Either one will work, but the .tar.md5 is safer. If the download gets corrupted somehow, odin will catch it and refuse to flash.
When flashing anything in odin you need to be in Download mode.
Click to expand...
Click to collapse
Thanks Doc, when I try the boot recovery hold volume up, home and power I get the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." message. If I use the hold volume down, home and power combo I get to the "Warning!! A custom Os can cause....." screen. If I press volume up it goes to the "Downloading...Do not turn off target!!" screen. If I press volume down it reboots to the "Kies" screen. Which screen mode should I be in when attempting to flash the TWRP file with Odin? thanks.
OK I tried to flash the TWRP file. Put S3 in download mode, Opened Odin, plugged in S3, Odin showed "added", tried to load the TWRP file into Odin but it freezes Odin. Non responsive Odin. Tried 4 times with and without plugging in phone. any clues?
Try downloading the file again. Could be a corrupted download. Also, what version of Odin are you using?
Oh, and kies interferes with Odin. Uninstall it and try odin again.
DocHoliday77 said:
Try downloading the file again. Could be a corrupted download. Also, what version of Odin are you using?
Oh, and kies interferes with Odin. Uninstall it and try odin again.[/QUOTE
Thanks I tried 3.09 first then 3.07. 3.09 hangs right away. 3.07 doesn't say "not responding" but nothing happens. Looks like it will but no. I wait for about 45 min. I will try everything from scratch. I did uninstall Kies with no help. Kies can't find the device - generic code 43.
Is it the Bootloader ap SWREV: 3 that indicates I need 4.4.2?
If its an older version such as 4.3 can i/should I still install 4.4.2?
Where do I find 4.4.2. Thanks for all your help because this is like finding a specific needle in a stack of needles without even fulling understanding what a needle is! God I miss DOS.
I've been doing all the above without sim or sd card installed. Does that make any difference.
Click to expand...
Click to collapse
IT's BACK ALIVE! Now what?
What happened? None of the .MD5 files would load and would just lock the Odin. Since I had nothing to loose I used a 2.6 version of the .tar file without the .MD5 check. It loaded fine, rebooted and there is my phone screen with all my apps and info. I'm afraid to even unplug it from the cable (silly I know). Checked the version and it reads 4.4.2., baseband version I747UCUFNE4, Kernel version 3.4.0-1514807, build number KOT49H.I171UCUFNE4, SE for Android status Enforcing SEPF_SAMSUNG-SGH-I747_4.4.2_0016.
Am I done? Is it safe to put back in service or should I do something else? thanks
Weird! Sounds like something on your system didn't like the md5sum. Never seen that before!
But if it appeared to flash ok, rebooted and it says PASS in Odin, you should be good to go.
First though, what exactly did you flash? Can you link to it? To my knowledge there is no NE4 firmware package available. Ive been trying to make one but it hasn't worked yet....
DocHoliday77 said:
Weird! Sounds like something on your system didn't like the md5sum. Never seen that before!
But if it appeared to flash ok, rebooted and it says PASS in Odin, you should be good to go.
First though, what exactly did you flash? Can you link to it? To my knowledge there is no NE4 firmware package available. Ive been trying to make one but it hasn't worked yet....
Click to expand...
Click to collapse
Just flashed the TWRP http://true-android.blogspot.com/2014/01/install-twrp-recovery-2631-on-at-galaxy.html. It passed it and phone rebooted to the normal reboot and my old screen. Weird? I do weird all the time. I used Odin 3.09. I have run it through some of its apps. I will wait 24 hours to see if it reboots by itself.
Cool, sounds like it should be ok then. Hopefully it'll make it through your testing period!
DocHoliday77 said:
Cool, sounds like it should be ok then. Hopefully it'll make it through your testing period!
Click to expand...
Click to collapse
Well it's functioning but we are back to the reboots 4-5 x a day. I can get to the recovery screen now. Anyone have a guess of my best next option?
Not sure, could be a faulty power switch though. Lots of these have been going bad in recent months, but it usually happens all the time, not just a few times a day.
Sent from my SGH-T999 using Tapatalk
Just a F/U. The reboot was getting to be a problem. Also had a problem with back up and restore apps. Found one that worked so I did a factory reset. All is good again. Love my S3 again. Still not happy with how AT&T handled the problem though.
Hi everyone,
I've scoured the forums for months on this one, and I've never found anyone with this issue, so I hope someone can give me a little direction.
I have a Telus Galaxy S III (SGH-i747m), currently running TWRP 2.8.4 and CM12.1
On normal boot, the screen flashes the Samsung logo and then goes dark.
The LED flashes, and once booted the buttons (and presumably the touch screen) all work, but with a blank screen.
When booting to recovery, I get the samsung logo and the 'booting recovery' message, and then it goes dark.
Recovery mode works - I can access via adb, but have to work entirely by command line because of the blank screen on the phone.
Booting to download mode works normally.
The only thing that's not working is the screen, except I know it works from the splash screen and download modes.
When it first went dark, I was running CM12 nightlies.
I've since tried the following (after the usual options of wiping the cache, fixing permissions, and 'the battery trick'):
flashing the stock rom - all that did was trip the warranty bit counter (now sitting at 1) - no change in screen function
flashing back to CM12 - successful flash, no change in screen function
changing recovery img - switched from CWM to TWRP to stock and back again - no change in screen function
I'm at a complete loss for how to get this phone back up and running, and frustrated because the issue doesn't appear to be hardware related (the screen DOES work, after all –*just not anywhere useful), and there's no apparent block in the phone's ability to operate, regardless of the rom it's running, which leads me to suspect that it's some sort of permissions issue that's not being resolved by the 'fix permissions' command in recovery.
I also looked at this unbricking guide for Verizon phones, but can't seem to find an equivalent procedure for att&t / canadian versions.
If anyone has any thoughts on getting this old girl up and running again, I'd be most appreciative.
Flashing a stock rom would not trip the warranty counter. Rooting or installing a custom recovery would trip Knox.
Immediately after flashing a stock rom, are you booting into recovery to perform a full wipe before the first boot?
audit13 said:
Flashing a stock rom would not trip the warranty counter. Rooting or installing a custom recovery would trip Knox.
Immediately after flashing a stock rom, are you booting into recovery to perform a full wipe before the first boot?
Click to expand...
Click to collapse
Yes and no - booting to recovery was fine, but I couldn't wipe without reinstalling TWRP, as the screen was still disabled, so I ended up with overlapping steps and mass confusion.
Any particular reason you could not wipe in stock recovery?
Flashing to stock on its own doesn't fix the screen issue, so I can't see to navigate the recovery menu on the phone, and no way to enable usb debugging to do it via adb
You're flashing stock rom from sammobile.com? You're using Odin 3.07? Did you try booting into stock recovery right after flashing store and before the first boot?
audit13 said:
You're flashing stock rom from sammobile.com?
Click to expand...
Click to collapse
Yes
You're using Odin 3.07?
Click to expand...
Click to collapse
Heimdall, actually
Did you try booting into stock recovery right after flashing store and before the first boot?
Click to expand...
Click to collapse
Yes - result was as described in the OP: Samsung logo, 'entering recovery', then blank
Redownload the stock rom and try again. ??
---------- Post added at 04:50 AM ---------- Previous post was at 04:49 AM ----------
If that doesn't work, maybe a wire jiggled Loose somehow....
---------- Post added at 04:52 AM ---------- Previous post was at 04:50 AM ----------
Also. Stock recovery uses the hardware keys to operate, does it not?
Maybe flash with Odin 3.07 instead? Didn't know that stock tar ROMs could be installed via heimdall
audit13 said:
Didn't know that stock tar ROMs could be installed via heimdall
Click to expand...
Click to collapse
I've done it on my Captivate.
Wow, I paid ovet 200 for my captivate many years ago. In fact, it is still being used by a friend of mine!
audit13 said:
Wow, I paid ovet 200 for my captivate many years ago. In fact, it is still being used by a friend of mine!
Click to expand...
Click to collapse
I still use mine as a sports tracker (cycling over 7400 miles last year, 2100 this year) and an mp3 player.
Wow, you must be in great shape! That's incredible athletic prowess. I'm officially jealous.
Working from a Mac, so using Odin is problematic, but I've tried every other option available to me - Heimdall (both via front end and command line), WebOdin, even went as far as trying Kies (pretty sure this was when I finally tripped the Knox counter).
At one point, in desperation, I even went so far as to extract the stock .tar and manually assign every file to its partition - all to no avail.
If I could even get the screen to stay lit into recovery mode so I could see to run a factory reset after flashing (or if someone could be so kind as to count button presses to navigate through the stock recovery menu to do it blind), I think I'd be able to get somewhere (with any luck).
So, an interesting development has taken place…
I got myself to a Windows machine and tried flashing stock via Odin 3.07.
No change in the function of the screen; however, something new has shown itself in download mode:
ODIN MODE
PRODUCT NAME: SGH-I747M
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER AP SWREV: 2
It's possible that my memory is faulty, but I think this is the first time I've seen a system status of custom with the official binary…unless, of course, the system status is reflecting the tripped KNOX counter, in which case I'm entirely out to lunch
neverdar said:
So, an interesting development has taken place…
PRODUCT NAME: SGH-I747M
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER AP SWREV: 2
It's possible that my memory is faulty, but I think this is the first time I've seen a system status of custom with the official binary…unless, of course, the system status is reflecting the tripped KNOX counter, in which case I'm entirely out to lunch
Click to expand...
Click to collapse
Warranty Bit: 1 indicates the tripped Knox counter
SYSTEM STATUS: Custom could be from having rooted, installed a custom recovery, or a custom rom.
Neither of these should be causing the screen to be dark.
---------- Post added at 03:27 PM ---------- Previous post was at 03:17 PM ----------
You mentioned unzipping the stock ,tar and flashing the partitions. Have you tried using adb to flash the recovery, is this what you previously attempted? I don't know if it would be any different than flashing by Odin or Heimdall.
I wonder if there is a problem with the partition table or PIT file. I could see this being the reason the recovery doesn't flash. Any ideas regarding this @audit13 @DocHoliday77 ?
After flashing a stock ROM, Binary and System should have changed back to "Official".
I believe that the PIT file is included with the stock ROM from sammobile.com. The entire ROM is flashed via PDA in Odin 3.07 with no need for a separate PIT file. My belief is based on the fact that every time I flash an s3 or s4 with a full stock ROM, one of the messages in the Odin progress window is "Getting PIT file".
audit13 said:
After flashing a stock ROM, Binary and System should have changed back to "Official".
I believe that the PIT file is included with the stock ROM from sammobile.com. The entire ROM is flashed via PDA in Odin 3.07 with no need for a separate PIT file. My belief is based on the fact that every time I flash an s3 or s4 with a full stock ROM, one of the messages in the Odin progress window is "Getting PIT file".
Click to expand...
Click to collapse
It was my understanding that Odin pulls the partition table from the phone before flashing (hence why nearly every guide warns about NOT ticking the 're-partition' box), so it's possible that I have a damaged partition table, and that's why it's not flashing correctly.
So the big question becomes, does anyone know where to find a stock PIT file for it?
In all my searches over the last months, I've never come across a PIT file my phone would accept…
neverdar said:
It was my understanding that Odin pulls the partition table from the phone before flashing (hence why nearly every guide warns about NOT ticking the 're-partition' box), so it's possible that I have a damaged partition table, and that's why it's not flashing correctly.
So the big question becomes, does anyone know where to find a stock PIT file for it?
In all my searches over the last months, I've never come across a PIT file my phone would accept…
Click to expand...
Click to collapse
Heimdall pulls the PIT file from the phone in that manner.
I have attached the PIT file I have used with my phone and Heimdall. I don't recall if it came from my phone or is one I found in the forums. I added the .txt ending so that I could upload it. Simply remove .txt to use. The file worked with my phone in the past two months, that's the best guarantee I can provide.
BTW that PIT is from an i747, not an i747M. @audit13 will it work for the i747M? My thought is that it will since they share the same ROMs.
neverdar said:
It was my understanding that Odin pulls the partition table from the phone before flashing (hence why nearly every guide warns about NOT ticking the 're-partition' box), so it's possible that I have a damaged partition table, and that's why it's not flashing correctly.
Click to expand...
Click to collapse
dawgdoc said:
Heimdall pulls the PIT file from the phone in that manner.
I have attached the PIT file I have used with my phone and Heimdall. I don't recall if it came from my phone or is one I found in the forums. I added the .txt ending so that I could upload it. Simply remove .txt to use. The file worked with my phone in the past two months, that's the best guarantee I can provide.
BTW that PIT is from an i747, not an i747M. @audit13 will it work for the i747M? My thought is that it will since they share the same ROMs.
Click to expand...
Click to collapse
Thanks for the info about the partition tables. Didn't know it was pulled from the phone.
hello guys, im having a problem with a s4 mini, i dont have a recovery, a friend gave it to me with this problem.
I can get download mode but when i try to flash TWRP or CWM i get the OK signs in odin but it doesnt get into recovery, well it gets to recovery but it says "no command" (sin comando, in spanish).
It used to have jellybean and updated itself to kitkat, it never had a custom rom.
This is what the screen in download mode shows:
ODIN MODE
PRODUCT NAME : GT-I9195
CURRENT BINARY: samsung official
SYSTEM STATUS: Official
KNOX KERNEL LOCK : 0x0
KNOX WARRANTY VOID : 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER RP SWREV: 2
WRITE PROTECTION ENABLE
I tried lot of things, but my last resort is to ask, if you have anything to help i appreciate!
maybe should try stock rom next with odin.
S3miniFin said:
maybe should try stock rom next with odin.
Click to expand...
Click to collapse
Already tried many stock firmwares for i9195 , when odins flashes it, it reboots to recovery and it says "NO COMMAND" ( Sin comandos ) then reboots and starts again with that.
Did you get this fixed mate. I'm pulling my hair out with the same problem. My son messed up a perfectly good phone that I had used for 3 years, and the toerag won't tell me what he did. (apparently he was texting when it when down) Tried various version of stock ROM and I get get diddly squat. ODIN fails to write the firmware and I get aboot on the phone screen. Current problem is stuck on Bootloop. Might just throw the thing away and buy a new one. Would like to fix it though....I'd be eternally grateful for any advice....Thnx
Capokhatpin,
Your son didn't do anything to your phone ! It's just faulty hardware and common problem to Samsung S4 Mini ...
And until now there are dozens of phones that are broken and there is still no solution for that problem.
So, leave the kid alone ...
Cheers !
I have the similar problem at my i9195 - at booting directly to recovery after "successful" flash of cwm over odin or heimdall, the stock recovery appears again without any change...
So did I understand it correctly that there is no chance to fix it?
lupus92 said:
I have the similar problem at my i9195 - at booting directly to recovery after "successful" flash of cwm over odin or heimdall, the stock recovery appears again without any change...
So did I understand it correctly that there is no chance to fix it?
Click to expand...
Click to collapse
No I think you have different problem, are you flashing cwm recovery 2x? You need to flash it once then boot immediately back into download & flash it a 2nd time. If you only do it once or you do a normal boot between flashes it will not work, start again.
2x? Hmh, i tried it (both odin and heimdall), but it doesn't work either (also 3x or 4x)... again just stock recovery.
The story behind it: An update from stock rom failed, and after it it stuck at boot logo. When starting recovery, error messages that mounting /system failed appear. So I decided to try to flash CM on it -> first custom recovery. I tried the CM recovery, CWM recovery, Twrp.... No success. In Odin mode it says "Current Binary: Samsung Official" and "System Status: Official".
Any ideas how to fix it?
lupus92 said:
2x? Hmh, i tried it (both odin and heimdall), but it doesn't work either (also 3x or 4x)... again just stock recovery.
The story behind it: An update from stock rom failed, and after it it stuck at boot logo. When starting recovery, error messages that mounting /system failed appear. So I decided to try to flash CM on it -> first custom recovery. I tried the CM recovery, CWM recovery, Twrp.... No success. In Odin mode it says "Current Binary: Samsung Official" and "System Status: Official".
Any ideas how to fix it?
Click to expand...
Click to collapse
I couldn't do it, i threw it away, just give the kid a slap, don't keep trying, you deserve better.
God**** phone.
IronRoo said:
No I think you have different problem, are you flashing cwm recovery 2x? You need to flash it once then boot immediately back into download & flash it a 2nd time. If you only do it once or you do a normal boot between flashes it will not work, start again.
Click to expand...
Click to collapse
So, I tried also to flash the stock ROM by booting it with „debrick“ image from SD card and flashing from „download mode“ went good, but after reboot it was same and I couldn't boot into „recovery“ with message „No command....“ or something like that. And You write that I have to flash only CWM or other TWRP recovery and then twice in the row. Is that correct ?
Sent from my GT-N7000 using XDA-Developers mobile app
Boombastical said:
So, I tried also to flash the stock ROM by booting it with â??debrickâ?? image from SD card and flashing from â??download modeâ?? went good, but after reboot it was same and I couldn't boot into â??recoveryâ?? with message â??No command....â?? or something like that. And You write that I have to flash only CWM or other TWRP recovery and then twice in the row. Is that correct ?
Click to expand...
Click to collapse
No, sorry I misunderstood @lupus92 original situation.
Boombastical said:
So, I tried also to flash the stock ROM by booting it with �¢??debrick�¢?? image from SD card and flashing from �¢??download mode�¢?? went good, but after reboot it was same and I couldn't boot into �¢??recovery�¢?? with message �¢??No command....�¢?? or something like that. And You write that I have to flash only CWM or other TWRP recovery and then twice in the row. Is that correct ?
Click to expand...
Click to collapse
jobs done so back to xda.
I have wondered if in situations like the above where nothing seems to work if a nand erase in Odin would help, but I've never seen it mentioned here on the S4 Mini forum. Is there a reason?
I've not researched it or tried it, but have seen it done on other forums (maybe the S4????). You have to use the full original stock firmware that originally came with your phone at the SAME TIME (else it will brick) I think and have a back up of your imei (though it should rebuild?). I'm not even sure if it deletes ALL partitions or leaves some ..... might be worth looking into it. @lupus92
IronRoo said:
jobs done so back to xda.
I have wondered if in situations like the above where nothing seems to work if a nand erase in Odin would help, but I've never seen it mentioned here on the S4 Mini forum. Is there a reason?
I've not researched it or tried it, but have seen it done on other forums (maybe the S4????). You have to use the full original stock firmware that originally came with your phone at the SAME TIME (else it will brick) I think and have a back up of your imei (though it should rebuild?). I'm not even sure if it deletes ALL partitions or leaves some ..... might be worth looking into it. @lupus92
Click to expand...
Click to collapse
I have here an S4 Mini and when I boot it with SD Card and 'debrick' image on it, it always fail to write to nand but it allow me to go to 'download mode' and to flash original stock ROM but after succesful flashing and reboot it still have no acces to recovery...
Does flashing only any custom recovery would help ?
Any idea ?
Sent from my GT-N7000 using XDA-Developers mobile app
Boombastical said:
I have here an S4 Mini and when I boot it with SD Card and 'debrick' image on it, it always fail to write to nand but it allow me to go to 'download mode' and to flash original stock ROM but after succesful flashing and reboot it still have no acces to recovery...
Does flashing only any custom recovery would help ?
Any idea ?
Click to expand...
Click to collapse
I don't think another recovery will help, but I'm no expert about this sort of thing. I would say it's worth a try through.
If that doesn't work and you are at the point of throwing your phone away, I wonder if it's worth giving the "nand erase all" command a try as it has been shown to fix write permissions (though I'm not sure if this is your problem) and other major issues software issues. But as it deletes the entire nand memory so you need to be very careful & know exactly what will hapen. You need a backup of your efs/imei (I'd use 2 methods just to be sure as have just read someone couldn't restore it from some app),( can you boot into system?) Also you must use a FULL stock ROM with pit file etc to rebuild partitions.
For example the guy below with a regular S4 seems to be in similar situation, though for different reason, he was able to recover using nand erase all. But our phone is different of course!
Also have read one case where guy had to flash stock with nand erase all ticked then had to immediately reflash stock again without erase ticked.
http://forum.xda-developers.com/galaxy-s4/help/help-nand-erase-t2863345
--–-------------------------------------
edit; Also another S4 thread they have flashed bootloaders to fix write access to partitions,
http://forum.xda-developers.com/showthread.php?t=1840030
&
http://www.androidauthority.com/galaxy-s3-i535-unbrick-soft-brick-125413/
IronRoo said:
I don't think another recovery will help, but I'm no expert about this sort of thing. I would say it's worth a try through.
If that doesn't work and you are at the point of throwing your phone away, I wonder if it's worth giving the "nand erase all" command a try as it has been shown to fix write permissions (though I'm not sure if this is your problem) and other major issues software issues. But as it deletes the entire nand memory so you need to be very careful & know exactly what will hapen. You need a backup of your efs/imei (I'd use 2 methods just to be sure as have just read someone couldn't restore it from some app),( can you boot into system?) Also you must use a FULL stock ROM with pit file etc to rebuild partitions.
For example the guy below with a regular S4 seems to be in similar situation, though for different reason, he was able to recover using nand erase all. But our phone is different of course!
Also have read one case where guy had to flash stock with nand erase all ticked then had to immediately reflash stock again without erase ticked.
http://forum.xda-developers.com/galaxy-s4/help/help-nand-erase-t2863345
--–-------------------------------------
edit; Also another S4 thread they have flashed bootloaders to fix write access to partitions,
http://forum.xda-developers.com/showthread.php?t=1840030
&
http://www.androidauthority.com/galaxy-s3-i535-unbrick-soft-brick-125413/
Click to expand...
Click to collapse
Thanks for sharing your thoutghs, but unfortunately I can't boot anymore to 'Download mode'. [emoji45] It can be still booted by 'Debrick' image from SD card but nothing more then that. From there I can't go anywhere further. Without SD Card it doesn't give signs of life except if it is attached via USB it shows as QHSUSB_DLOAD...
I have no time now to play with the phone, but I will try in the weekend again to come to 'Download mode' and to flash again recovery or to erase flash nand cause I have already EFS back up somewhere on my external HD and then we will see what will happened. Thanks again and cheers !
Edit: I can't flash anything thru 'Debrick image' via Odin 3.09. It always give error: Faild to write mmc nand... It can't erase nand nor boot to 'Download mode' ... So I'm clueless at the moment... It looks as the nand is damaged and it can't be accessed anymore... Sadly, I think this S4 Mini will be ended as spare phone for parts only for my girlfriend phone... That's it... If someone have more ideas about it I can still try it... Cheers !
Sent from my GT-N7000 using XDA-Developers mobile app
Hi, I've digged through much of xda and not found a satisfying answer. My phone boots into download, is detected by odin (7,8,9,12 all ok), and whatever I do, odin says it was successfull. I tried flashing the stock ROM, the official ROM with 4.4.2, pit file, all in vain. Before crashing my s4 was running cm13 with twrp3.0.2-1. When turning phone on, it just displays "Samsung GalaxyS4 mini / GT-I9195 label on black screen, with "set warranty bit: kernel" in upper left corner. Download mode boots ok, but recovery - twrp 3.0.2-1 logo is displayed for about 8 seconds, and then phone reboots to "normal" mode - displaying the logo.
It would be great if some of you had an idea of what to do as I've been trying on my own for 3 weeks now and nothing changed for better.
As there are people looking at this thread, it would be great to hear from you! I still did not succeed in flashing anything, twrp screen shows for 8sec and then phone reboots to normal, which is samsung splash screen. I'm using samsung drivers, have tried different usb ports, used different computers, still nothing.
Did you try 4 files firmware?
http://firmware.smartphonewp.com/download-samsung-galaxy-s4-mini-gt-i9195-full-firmware-4-files/
Hi,
Unfortunately I can't help you here, but I have a similar problem and it might be related to yours. I have also have a Samsung S4 mini GT-i9195 LTE. Originally with Android 4.4.2 but lately with no OS at all. And I can't figure out how to get one back. What happened, chronologically and (very) detailed:
I rooted my phone with KingoRoot, which worked fine as far as I can tell. When I didn't like the KingoSuperUser-App I installed SuperSU. But it failed to work, apparently because of Knox or something like that. I later wanted to flash my phone with a LineageOS ROM (lineage-14.1-20170505-nightly-serranoltexx-signed.zip) and therefore I wanted to install TWRP as custom recovery. As the usual way with Odin seemed a bit complicated to me at the time, I decided to install the "TWRP Manager" App, which went well. But as soon as I tried to install my ROM with it, it asked if my bootloader was unlocked. So, after searching the internet about that and it said that Samsung phones usually have an unlocked bootloader and only have to be rooted, I went on with installing the LineageOS ROM using the TWRP Manager. Mind you, I am not talking about the custom recovery that you have to boot in to by pressing Vol-Up+Home+On/Off-Button, I am talking about the app that you can download and just needs root permissions to do the same stuff. I had downloaded the ROM-zip onto my SDcard before and wanted to flash it from there.. Now, when I let the app go on, the screen just went blank. And this might be the moment I overreacted. I panicked and tried to start my phone again. But it only went as far as the Samsung logo and didn't go further and I had to pull the battery to turn it off. I then tried to boot into recovery mode by pressing Vol-up+home+On with no result, I then tried with Vol-down+home+On and found Download mode with:
Code:
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1 -> this one might have been 0x0 the first time
CSB-CONFIG-LSB: 0x30
BOOTLOADER RP SWREV: 2
WRITE PROTECTION: Enable
After some research I downloaded Odin3 (v3.12.5) and managed to flash TWRP (2.6.3.0) onto my phone. And I found the ROM-zip file, but it would not let me unpack and flash it and it didn't help to uncheck the "Zip file signature verification." When I tried to flash I always got the same error massage:
Code:
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/external_sd/lineage-14.
Checking for MD5 file...
Skipping MD5 check: no MD5 file foun
Warning: No file_contexts
Target: 1493971678
detected filesystem ext4 for /dev/bl
Can't install this package on top of
E: Error executing updater binary in
Error flashing zip '/external_sd/lin
Updating partition details...
And it gives a "failed" response. Now, I tried moving the zip to internal_sd and flashing with no better result. I also tried to flash a stock ROM which I downloaded from Sammobile.com. This didn't work either. The adb push method and the sideload didn't work out either.
Interestingly, when I go to "Reboot" -> "Power Off" to turn the phone off I get a dialog:
No OS installed! Are you sure you wish to power off?
-> "Swipe to power off"
-> then comes the next dialog:
Install SuperSU?
Your device does not appear to be rooted.
Install SuperSU now?
This will root your device.
-> "Swipe to install."
Which had no effect at all but to inform me that my phone apparently isn't rooted after all. I therefore downloaded the S4Mini_RootKit_v2.zip and tried flashing it, which was successful. But I still got the same dialog when powering off and I couldn't install the zip files either.
That's where I am now and I really don't know what to try or do next. As I could flash TWRP onto my phone, shouldn't it also be possible to flash an OS?
I hope this was a precise enough description. If someone has any further question, please ask.
@albaCross @desolate_sorrow
Try an factory reset with the recovery.
Download a multiple Firmware from Sammy with PIT.file
Boot into Download mode.
Download Odin 3.07 or 3.09 not newer
Flash all Files with Pit.file
Reboot.
bierma32 said:
@albaCross @desolate_sorrow
Try an factory reset with the recovery.
Download a multiple Firmware from Sammy with PIT.file
Boot into Download mode.
Download Odin 3.07 or 3.09 not newer
Flash all Files with Pit.file
Reboot.
Click to expand...
Click to collapse
I posted this thread precisely because my recovery DOES NOT work. No option for factory reset. It just reboots after ~8 secs of twrp 3.0.2-1 screen. Flashed with ODIN 3.09, official intern. ROM from sammobile into AP and drive. google. com /file/d /0Bx2R0nz6jh17bllKenctWnVsWkE/edit <-- this PIT file. Also tried this pit with different versions of twrp - 2.6, 3.0, 3.1 - still no change at all, no recovery booting
@desolate_sorrow
But you are not tried a multiple ROM with PIT.file.
You flashed only a Single File ROM under AP.
On the multiple ROM you can extract the CSC File and than you have the PIT.
Pit you can only flash with Odin and a ROM.
bierma32 said:
@albaCross @desolate_sorrow
Try an factory reset with the recovery.
Download a multiple Firmware from Sammy with PIT.file
Boot into Download mode.
Download Odin 3.07 or 3.09 not newer
Flash all Files with Pit.file
Reboot.
Click to expand...
Click to collapse
Perfect! Worked like a charm for me! While factory reset itself did nothing to improve the phone, the other stuff worked. I flashed my phone with the .tar.md5 file I extracted from the .zip file (from sammobile.com) using Odin 3.09 and my phone works again, thank you soo much!
I then rooted it again and flashed LineageOS (lineage-14.1-20170505-nightly-serranoltexx-signed.zip) onto it. It worked but during the first startup I got the error massage "Setup wizard keeps stopping". I then tried the newest (20170519) version and got the same error again. Any Idea how I might repair this?
About the pit. file: what exactly is the difference between this multiple pit file, a "usual" pit file and the .tar.md5 file I used?
On a multiple ROM file is all separately, Bootloader, Phone , Modem and CSC file.
The PIT file is the partion File of the RAM. You can extract this seperat from the CSC file.
To the issue the the gapps. Try an older Version or flash first the LOS and setup WiFi.
Than flash Opengapps with wipe cache and dalvik than normally works the wizard.
bierma32 said:
@desolate_sorrow
But you are not tried a multiple ROM with PIT.file.
You flashed only a Single File ROM under AP.
On the multiple ROM you can extract the CSC File and than you have the PIT.
Pit you can only flash with Odin and a ROM.
Click to expand...
Click to collapse
i got the same problem, that the recovery is not working, flashing a multiple rom with pit doesn't help (neither recovery nor rom is working).
but i guess the main problem is, that i got a REV02 phone and I only can find REV01 firmware (e.g. this one here: http://firmware.smartphonewp.com/download-samsung-galaxy-s4-mini-gt-i9195-full-firmware-4-files/)
are there any REV02 firmwares out there, which maybe can help? or does anyone (@bierma32, @albaCross or @desolate_sorrow) got any other ideas?
bierma32 said:
To the issue the the gapps. Try an older Version or flash first the LOS and setup WiFi.
Than flash Opengapps with wipe cache and dalvik than normally works the wizard.
Click to expand...
Click to collapse
Thanks for replying. I tried flashing the LOS ROM and booting without gapps. According to TWRP it was successful. But when I booted for the first time I got similar error messages as before "[any app name] stopped running". Just with several names and all of them one after the other. Most of them appear to be named something like .android.com with different pre- and suffixes.
I then tried a more actual version of LOS with a similar result (same error message, similar names). After several times I decided to go back to my previously created TWRP backup (of the stock ROM with root access and several of the more annoying apps removed, also I had checked all partitions when backing up): I did a custom recovery and recovered my backup file and it seemed to work, TWRP said "success". On booting I again had the now so familiar error messages on the screen. Same happened when I flashed the stock ROM and recovered my backup after that, or at least tried. While TWRP still said it was a success it would not get past the screen where you choose your language.
After this I gave up and went back to the stock ROM and "rebuilt" my old phone. Maybe my phone just doesn't like anything but the stock ROM, so I should probably just stick to it.
But, just out of curiosity, what exactly is the problem with the phone if neither custom ROMs nor system backups work on it properly?
1of16 said:
i got a REV02 phone and I only can find REV01 firmware
Click to expand...
Click to collapse
this was me just 2 days ago!
i was on lineage os 7.1.1 with TWRP and was stuck wanting to go back to stock.
i flashed many many roms and they all failed in ODIN.
Eventually i found a Netherlands ROM that did not fail on the REV02 check - might be worth a go!
my thread
good luck!
Hello,
I own s4 mini gt i 9192
i have rooted it with kingroot when it was in a stock firmware, then i have decided to install lolipop rom with twrp with superuser in it, everything gone smooth i have used my phone over 3 months, one morning i woke up, the battery level was 43 %, i have set it in the charger returned back after 30 minutes and have seen that it only got 3% energy, pulled out the battery and inserted back, charged the phone for a while in a turned off mode, and powered it one, strangely it started but showed some kind of upgrading panel on the main screen than immediately it turned off and started to restart again and again, i have booted it in recovery mode, wiped the cache restarted the phone, main screen turned on to enter my password but in a seconds it went black again, opened it up in twrp recovery mode, went into advanced settings and wiped something in there(i can not exactly remember the name of the thing i have wiped but there was an option to wipe it in twrp advanced settings, it warned me "that my phone would not start correctly but anyway i have done it") after it's wipe phone started with s4 mini logo, and restarted like this over and over again, in recovery mode it only shows twrp logo no options panel to access to internal or external sd card, neither wipe or factory just nothing but twrp logo. I have flashed the 4 files recovery pack, (pit, ap,csc and etc,) but same it is never helped, i have used multiple recoveries, and the original stock rom from sammobile, but it has nor cure, i am a newbie on tech and xda please if you could help me, i have tried to post it to xda forms but i did not find a button to post a thread, thanks.