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.
Related
My front facing camera is broken. These are the steps leading to it.
1) Stock Tmo phone my wife used for a month. Both cameras worked. We switched phones.
2) I rooted it. While trying to flash CWM, I accidentally chose to fix root before rebooting. I sort of lost root. I flashed SU again and everything was fine.
3) I was running rooted stock and realized my camera app was broken. It wouldn't launch. After clearing cache and data, it worked. I never checked FFC.
4) Flashed VirginROM after doing a factory reset and clearing caches. FFC does not work. I get a Unfortunately, Camera stopped working error if I try to use it. After that even the regular camera wont work until I clear cache and data.
Is there anything I can do to get my FFC working again? I flashed two different versions of the ROM after doing a factory reset and it won't work.
I'd Odin back to stock. And, start over.
Sent from my SGH-M919 using XDA Premium 4 mobile app
re: camera issues - kernels
ashwinmudigonda said:
My front facing camera is broken. These are the steps leading to it.
1) Stock Tmo phone my wife used for a month. Both cameras worked. We switched phones.
2) I rooted it. While trying to flash CWM, I accidentally chose to fix root before rebooting. I sort of lost root. I flashed SU again and everything was fine.
3) I was running rooted stock and realized my camera app was broken. It wouldn't launch. After clearing cache and data, it worked. I never checked FFC.
4) Flashed VirginROM after doing a factory reset and clearing caches. FFC does not work. I get a Unfortunately, Camera stopped working error if I try to use it. After that even the regular camera wont work until I clear cache and data.
Is there anything I can do to get my FFC working again? I flashed two different versions of the ROM after doing a factory reset and it won't work.
Click to expand...
Click to collapse
Usually camera issues are always related to the kernel so what I would do
is flash a different/newer kernel which will not have any the camera issues.
Here is the direct download link for the stock modified kernel: http://ktoonsez.jonathanjsimon.com/sgs4/TWGE/KT-SGS4-JB4.3-TWGE-TMO-11.14.2013.zip
Flash this using cwm/twrp recovery.
Good luck!
Misterjunky said:
Usually camera issues are always related to the kernel so what I would do
is flash a different/newer kernel which will not have any the camera issues.
Here is the direct download link for the stock modified kernel: http://m3.androidfilehost.com/downl..._Modified_4.3_M919_Kernel.zip&action=download
Flash this using cwm/twrp recovery.
Good luck!
Click to expand...
Click to collapse
Thank you for your reply. I don't want to go back to stock and restart, so this is a better option. I do have a couple of questions:
* Is the kernel independent of the ROM? My current kernel version says
3.4.0-2270815
[email protected] #1
Mon Dec 9 15:47:40 KST 2013
* Do I just download, flash, and reboot in CWM?
Also, clicking the link does nothing. I can't find the zip file to download.
Thanks.
Android_Monsters said:
I'd Odin back to stock. And, start over.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is my last ditch option if all else fails. Thanks.
re: camera issues - kernels
ashwinmudigonda said:
Thank you for your reply. I don't want to go back to stock and restart, so this is a better option. I do have a couple of questions:
* Is the kernel independent of the ROM? My current kernel version says
3.4.0-2270815
[email protected] #1
Mon Dec 9 15:47:40 KST 2013
* Do I just download, flash, and reboot in CWM?
Also, clicking the link does nothing. I can't find the zip file to download.
Thanks.
Click to expand...
Click to collapse
All you do is download and flash in cwm recovery then reboot in cwm recovery.
And yes, all kernels are independent of the rom, that's
why there are so many different kernels which can be
used on the same or other roms.
Good luck!
---------- Post added at 04:03 PM ---------- Previous post was at 03:57 PM ----------
ashwinmudigonda said:
Thank you for your reply. I don't want to go back to stock and restart, so this is a better option. I do have a couple of questions:
* Is the kernel independent of the ROM? My current kernel version says
3.4.0-2270815
[email protected] #1
Mon Dec 9 15:47:40 KST 2013
* Do I just download, flash, and reboot in CWM?
Also, clicking the link does nothing. I can't find the zip file to download.
Thanks.
Click to expand...
Click to collapse
Sorry about the link, I just fixed/updated it and it works fine now.
http://ktoonsez.jonathanjsimon.com/sgs4/TWGE/KT-SGS4-JB4.3-TWGE-TMO-11.14.2013.zip
Good luck!
Misterjunky said:
All you do is download and flash in cwm recovery then reboot in cwm recovery.
And yes, all kernels are independent of the rom, that's
why there are so many different kernels which can be
used on the same or other roms.
Good luck!
---------- Post added at 04:03 PM ---------- Previous post was at 03:57 PM ----------
Sorry about the link, I just fixed/updated it and it works fine now.
http://ktoonsez.jonathanjsimon.com/sgs4/TWGE/KT-SGS4-JB4.3-TWGE-TMO-11.14.2013.zip
Good luck!
Click to expand...
Click to collapse
I flashed the zip in CWM and the phone is stuck at the splash screen that says Samsung Galaxy S4. It doesn't boot. After a while, the entire screen is corrupted. On the top left, I see
Kernel is not SEAndroid enforcing
Set warranty bit: kernel
Do I just restore my most recent Nandroid?
EDIT: Ok, I am a bit concerned now. I can't enter recovery mode either.
re: restore
ashwinmudigonda said:
I flashed the zip in CWM and the phone is stuck at the splash screen that says Samsung Galaxy S4. It doesn't boot. After a while, the entire screen is corrupted. On the top left, I see
Kernel is not SEAndroid enforcing
Set warranty bit: kernel
Do I just restore my most recent Nandroid?
EDIT: Ok, I am a bit concerned now. I can't enter recovery mode either.
Click to expand...
Click to collapse
Yes simply do a restore in recovery..........
Glad you had a nandroid backup... many people don't and need to
ODIN flash the stock unrooted rom and start from scratch.
Good luck!
Misterjunky said:
Yes simply do a restore in recovery..........
Glad you had a nandroid backup... many people don't and need to flash the stock unrooted rom.
Good luck!
Click to expand...
Click to collapse
I am unable to enter recovery.
Pressing and holding down the Power and Volume up button does not take me anywhere.
re: recovery
ashwinmudigonda said:
I am unable to enter recovery.
Pressing and holding down the Power and Volume up button does not take me anywhere.
Click to expand...
Click to collapse
That means the phone is not completely powered down.
So remove the battery for 10 seconds and replace it then press vol-up and power
and it will go into recovery.
Be sure the usb cable is not connected to the phone and computer until
the phone is in recovery mode.
Good luck!
Misterjunky said:
That means the phone is not completely powered down.
So remove the battery for 10 seconds and replace it then press vol-up and power
and it will go into recovery.
Be sure the usb cable is not connected to the phone and computer until
the phone is in recovery mode.
Good luck!
Click to expand...
Click to collapse
No luck. When I do that I see
Set bit warranty: recovery
And it goes blank.
I was able to enter ODIN mode, but I pulled the battery out because I didn't know how to quit it. What is the best way to flash stock ROM with the MK2 bootloader? I really hope I don't brick this phone. Thanks for your patience.
re: recovery - stock roms
ashwinmudigonda said:
No luck. When I do that I see
Set bit warranty: recovery
And it goes blank.
I was able to enter ODIN mode, but I pulled the battery out because I didn't know how to quit it. What is the best way to flash stock ROM with the MK2 bootloader? I really hope I don't brick this phone. Thanks for your patience.
Click to expand...
Click to collapse
As a last resort you will need to ODIN flash the official stock rom.
If you have downloaded the official MK2 stock 4.3 M919 Odin flash rom and flashed it that means
that you cannot go back to 4.2.2 MDL roms so you need to Odin flash the official 4.3 stock firmware.
You can find and download the official 4.3 stock MK2 M919 ODIN flash firmware from http://SamMobile.com.
But if you simply flashed one of the cwm/twrp zip file custom roms here from XDA then you have a choice
to either odin flash the original MDL 4.2.2 M919 stock Jellybean Touchwiz firmware or if you don't care about
KNOX then you can flash the new MK2 Odin flash M919 stock official Jellybean Touchwiz 4.3 firmware.
There is also one other thing you can do, re-flash the cwm recovery using ODIN.
You will need to download the TAR file version of CWM custom recovery which needs to be flashed using ODIN.
Here is the direct download link for the odin flash cwm custom recovery TAR.
https://copy.com/txTLr/Galaxy-S4-tmo-cwr-6.0.3.6.zip?download=1
This will flash the cwm custom recovery to your phone so possibly you can go back into recovery
instead of flashing stock roms. If this does not work you will need to odin the stock rom.
After you odin flash a stock rom you need to root it and then Flash the CWM recovery tar file above
so you can go into cwm recovery.
Once thats done you can restore your nandroid backup.
Good luck!
Misterjunky said:
As a last resort you will need to ODIN flash the official stock rom.
If you have downloaded the official MK2 stock 4.3 M919 Odin flash rom and flashed it that means
that you cannot go back to 4.2.2 MDL roms so you need to Odin flash the official 4.3 stock firmware.
You can find and download the official stock MK2 M919 firmware from http://SamMobile.com.
But if you simply flashed one of the cwm/twrp zip file custom roms here from XDA then you have a choice
to either odin flash the original MDL 4.2.2 M919 stock Jellybean Touchwiz firmware or if you don't care about
KNOX then you can flash the new MK2 Odin flash M919 stock official Jellybean Touchwiz firmware.
There is also one other thing you can do, re-flash the cwm recovery using ODIN.
You will need to download the TAR file version of CWM custom recovery which needs to be flashed using ODIN.
Here is the direct download link for the odin flash cwm custom recovery TAR.
https://copy.com/txTLr/Galaxy-S4-tmo-cwr-6.0.3.6.zip?download=1
This will flash the cwm custom recovery to your phone so possibly you can go back into recovery
instead of flashing stock roms. If this does not work you will need to odin the stock rom.
After you odin flash a stock rom you need to root it and then Flash the CWM recovery tar file above
so you can go into cwm recovery.
Once thats done you can restore your nandroid backup.
Good luck!
Click to expand...
Click to collapse
I am a bit confused. My phone got the OTA 4.3 MK2 update before I rooted it and flashed CWM+custom ROM.
Flashing the recovery did not work.
I am currently downloading the M919UVUEMK2_M919TMBEMK2_TMB.zip from Sammobile to ODIN flash it. Is that right? Also in my Odin(v3.09) I see BL, AP, CP, CSC options. I assume that the recovery and the ROM tar files should be loaded in the AP section, right?
ashwinmudigonda said:
I am a bit confused. My phone got the OTA 4.3 MK2 update before I rooted it and flashed CWM+custom ROM.
Flashing the recovery did not work.
I am currently downloading the M919UVUEMK2_M919TMBEMK2_TMB.zip from Sammobile to ODIN flash it. Is that right? Also in my Odin(v3.09) I see BL, AP, CP, CSC options. I assume that the recovery and the ROM tar files should be loaded in the AP section, right?
Click to expand...
Click to collapse
That even makes it easier.. then simply do this:
Download the official 4.3 stock MK2 M919 ODIN flash firmware from http://SamMobile.com. (or from a faster host link)
Unzip the file and inside you will find a TAR MD5 file and ODIN and ODIN.INI file.
Make an empty folder on your desktop and unzip the contents of the downloaded zip file into the new folder.
Then simply open odin and click the PDA slot, navigate to the TAR MD5 file and select it.
Put the phone into download mode
Connect the usb cable from phone to computer and make sure that the [COM:xx] in Odin lights
up then click the START button in Odin.
Once Odin is done successfully the phone will auto-reboot.
Have a lot of patience because to get the phone to a useable state it may take up to 4-5 minutes.
After its done you need to root the phone with cf-autoroot in Odin's PDA slot.
After it's rooted you need to flash a custom recovery, either TWRP which I would suggest or CWM custom recovery.
Once it's all done you can either start fresh, or simply restore the nandroid backup.
PLEASE NOTE: if your nandroid backup was made from any 4.2.2 stock or custom rom it will error out,
it cannot be done since having the 4.3 MK2 official firmware does not allow downgrading to older versions.
That's one of the drawbacks of the KNOX in the 4.3 firmware.
Good luck!
---------- Post added at 10:32 PM ---------- Previous post was at 10:11 PM ----------
ashwinmudigonda said:
I am a bit confused. My phone got the OTA 4.3 MK2 update before I rooted it and flashed CWM+custom ROM.
Flashing the recovery did not work.
I am currently downloading the M919UVUEMK2_M919TMBEMK2_TMB.zip from Sammobile to ODIN flash it. Is that right? Also in my Odin(v3.09) I see BL, AP, CP, CSC options. I assume that the recovery and the ROM tar files should be loaded in the AP section, right?
Click to expand...
Click to collapse
Don't worry about those "BL, AP, CP, CSC" files, you opened the TAR file which is in the zip file.
Odin will take care of all of that stuff, Odin ONLY wants the TAR MD5 file in the PDA slot.
If you check the properties of the largest file inside the zip file you are downloading you will
see it is a file with a TAR and or MD5 extender. Thats what Odin needs in it's pda slot.
There is NO reason at all to EXTRACT any of the files which are inside the TAR MD5 file.
Think of the TAR MD5 file as if it was one very large image file which is required by Odin.
Hope that explains it.
Good luck!
Misterjunky said:
That even makes it easier.. then simply do this:
Download the official 4.3 stock MK2 M919 ODIN flash firmware from http://SamMobile.com. (or from a faster host link)
Unzip the file and inside you will find a TAR MD5 file and ODIN and ODIN.INI file.
Make an empty folder on your desktop and unzip the contents of the downloaded zip file into the new folder.
Then simply open odin and click the PDA slot, navigate to the TAR MD5 file and select it.
Put the phone into download mode
Connect the usb cable from phone to computer and make sure that the [COM:xx] in Odin lights
up then click the START button in Odin.
Once Odin is done successfully the phone will auto-reboot.
Have a lot of patience because to get the phone to a useable state it may take up to 4-5 minutes.
After its done you need to root the phone with cf-autoroot in Odin's PDA slot.
After it's rooted you need to flash a custom recovery, either TWRP which I would suggest or CWM custom recovery.
Once it's all done you can either start fresh, or simply restore the nandroid backup.
PLEASE NOTE: if your nandroid backup was made from any 4.2.2 stock or custom rom it will error out,
it cannot be done since having the 4.3 MK2 official firmware does not allow downgrading to older versions.
That's one of the drawbacks of the KNOX in the 4.3 firmware.
Good luck!
---------- Post added at 10:32 PM ---------- Previous post was at 10:11 PM ----------
Don't worry about those "BL, AP, CP, CSC" files, you opened the TAR file which is in the zip file.
Odin will take care of all of that stuff, Odin ONLY wants the TAR MD5 file in the PDA slot.
If you check the properties of the largest file inside the zip file you are downloading you will
see it is a file with a TAR and or MD5 extender. Thats what Odin needs in it's pda slot.
There is NO reason at all to EXTRACT any of the files which are inside the TAR MD5 file.
Think of the TAR MD5 file as if it was one very large image file which is required by Odin.
Hope that explains it.
Good luck!
Click to expand...
Click to collapse
My doubt was that I don't see a PDA slot in v3.09 (see attached)
ashwinmudigonda said:
My doubt was that I don't see a PDA slot in v3.09 (see attached)
Click to expand...
Click to collapse
I did not know you are using the latest version 3.09 of Odin,
they changed the names... AP = PDA PDA = AP both are the same thing.
So in all the posts I made wherever you see PDA it's AP from now on.......
Good luck!
Misterjunky said:
I did not know you are using the latest version 3.09 of Odin,
they changed the names... AP = PDA PDA = AP both are the same thing.
So in all the posts I made wherever you see PDA it's AP from now on.......
Good luck!
Click to expand...
Click to collapse
I downloaded and flashed the MK2 stock firmware. ODIN showed a Pass, I disconnected the cable, and the phone rebooted into the T-mobile 4G LTE with a sound and it's been stuck on this for a while now. It hasn't crossed this screen. I don't know what to do.
Probably need to clear data.
Sent from my SGH-M919 using XDA Premium 4 mobile app
---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------
(i.e. boot into recovery and wipe data)
Sent from my SGH-M919 using XDA Premium 4 mobile app
re:
ashwinmudigonda said:
I downloaded and flashed the MK2 stock firmware. ODIN showed a Pass, I disconnected the cable, and the phone rebooted into the T-mobile 4G LTE with a sound and it's been stuck on this for a while now. It hasn't crossed this screen. I don't know what to do.
Click to expand...
Click to collapse
First try this, pull the battery out wait 20 seconds replace it and restart the phone
with the power button.
If that don't work then download the odin flash cf-auto-root in odin's AP slot.
Here is the direct download link: http://download.chainfire.eu/328/CF...jfltetmo-jfltetmo-sghm919.zip?retrieve_file=1
Then here is the TWRP odin flash recovery: http://techerrata.com/get/twrp2/jfltetmo/openrecovery-twrp-2.6.3.1-jfltetmo.tar
Be sure to UN-CHECK "Auto-Reboot" in ODIN when flashing these two TAR files.
After the first one is flashed power off the phone and put it back into download mode.
Be sure the auto reboot is not checked then flash the TWRP recovery TAR file in odin's AP slot.
Then power off the phone and pull battery wait 20 seconds and replace battery then restart the
phone and hopefully it will fully restart completely without getting stuck.
If not continue below.
THIS NEXT PART PRESUMES THAT YOUR PHONE HAS STILL NOT FULLY BOOTED.
After you have flashed both cf-autoroot and twrp power down the phone and restart phone into recovery.
In TWRP recovery click the WIPE button and swipe the bottom slider to do a factory reset.
This step wipes any rogue files and apps which the ODIN flash of the firmware did add to the
phone, it also wipes all apps which came from the playstore or other sources (side loading)
Some rogue apps and the data they create can prevent the phone from a normal startup.
Factory reset also wipes all user data like contacts, passwords mms and other user created data
like your email accounts. It does not wipe the actual email messages on your isp's server.
.
It will NOT format the internal or external sdcards so you will not loose stuff like pictures,
videos, music or any personal documents you have created or anything you have backed up
with any apps which you may have gotten from the playstore or other sources.
When the factory reset is done, click the WIPE button again and select "advanced wipe".
Select Dalvik Cache and Cache then swipe the bottom button.
After doing all this click the back button twice to get to the screen where
it says "Reboot" click the reboot button then on the next screen click on
the "system" button then the phone reboots normally I hope!!!
Cross your fingers.
Good luck!
Misterjunky said:
First try this, pull the battery out wait 20 seconds replace it and restart the phone
with the power button.
If that don't work then download the odin flash cf-auto-root in odin's AP slot.
Here is the direct download link: http://download.chainfire.eu/328/CF...jfltetmo-jfltetmo-sghm919.zip?retrieve_file=1
Then here is the TWRP odin flash recovery: http://techerrata.com/get/twrp2/jfltetmo/openrecovery-twrp-2.6.3.1-jfltetmo.tar
Be sure to UN-CHECK "Auto-Reboot" in ODIN when flashing these two TAR files.
After the first one is flashed power off the phone and put it back into download mode.
Be sure the auto reboot is not checked then flash the TWRP recovery TAR file in odin's AP slot.
Then power off the phone and pull battery wait 20 seconds and replace battery then restart the
phone and hopefully it will fully restart completely without getting stuck.
If not continue below.
THIS NEXT PART PRESUMES THAT YOUR PHONE HAS STILL NOT FULLY BOOTED.
After you have flashed both cf-autoroot and twrp power down the phone and restart phone into recovery.
In TWRP recovery click the WIPE button and swipe the bottom slider to do a factory reset.
This step wipes any rogue files and apps which the ODIN flash of the firmware did add to the
phone, it also wipes all apps which came from the playstore or other sources (side loading)
Some rogue apps and the data they create can prevent the phone from a normal startup.
Factory reset also wipes all user data like contacts, passwords mms and other user created data
like your email accounts. It does not wipe the actual email messages on your isp's server.
.
It will NOT format the internal or external sdcards so you will not loose stuff like pictures,
videos, music or any personal documents you have created or anything you have backed up
with any apps which you may have gotten from the playstore or other sources.
When the factory reset is done, click the WIPE button again and select "advanced wipe".
Select Dalvik Cache and Cache then swipe the bottom button.
After doing all this click the back button twice to get to the screen where
it says "Reboot" click the reboot button then on the next screen click on
the "system" button then the phone reboots normally I hope!!!
Cross your fingers.
Good luck!
Click to expand...
Click to collapse
No luck.
I rooted and flashed the recovery and followed the first step. It was stuck at the Tmobile screen.
Pressing volume up and power button does not take me into any recovery, just a blank screen. Last night I tried this with CWM and now with TWRP, but it won't enter into recovery.
The phone is rooted and cwm v6.0.x is installed. I was trying to flash C-rom last night for my first time but got stuck and said your root maybe lost blash blah. Now every time i turn on my phone, it starts and gets stuck on the black screen with samsung lego.
Before flashing my phone was 4.4.2 i recently received update my phone carrier. Then i rooted it after..
---what i did to solve the problem------
1. I wiped everything (all the catches) and did factory rest. Then tried to restore from backup i made. Didnt work.
2. Connected my phone with Kies and tried frameware upgread.They asked for phone model and s/n, download the framware directly and at the end
it gave me an error. I dont exactly remember what it was but i think it was saying phone can not be recovered.
............................This are what i have done so far.
..................................................................................
Now I'm going to try to flash to the factory rom via Odin. After so many researches, someone was able to fix their phone with they flashed their factory rom and kernel. I thought downloading the factory rom was good enough, what did they mean by flashing the karnel to? you can flash your karnel and rom? where do you get your kenels? This is the link to the process....http://forum.xda-developers.com/showthread.php?t=1833177
................................................................
My phone is on Downloading Mode thing.......This is what i see
ODIN MODE
Product Name: SGH-I747M
Current Binary: Custom
System Status: Custom
Qualcom Secureboot: Enable
Warrenty Bit: 1
BootLoader AP SWREV:2
Any one contributing for the help, must appreciated.
Thanks.
Factory reset, but do not restore your backup. Touchwiz and cm/aosp data are not compatible. So when going between the two, you have to factory reset or it'll hang at boot.
You can restore individual apos from something like Titanium backup, but you cannot restore system data or a nandroid backup.
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
If you flash the stock rom, itll probably boot up again because the data you restored is compatible with that.
Odin Says Fail!
so flashing stock rom via Odin failed
How did it fail? What was in the messages in Odin? What firmware did you try to flash?
fixed!
DocHoliday77 said:
How did it fail? What was in the messages in Odin? What firmware did you try to flash?
Click to expand...
Click to collapse
ok well after so many trials i have successfully installed stock rom. I download my stock rom from this site. http://www.mrcrab.net/androidfirmware/SGH-I747M/Samsung-Galaxy-S3-North-America-SGH--I747M.html
i extracted the md5 file the run it via odin again. first it failed, second time it froze third time it took forever and final at 4th trail it passed.
now im running stock rom.
Just one more thing though. under downloading.. mode thing my Warranty Bit: 1 and is written in red. does it mean anything beside warranty void?
It does void warranty yes. But it also breaks your ability to use knox, which no one ive ever seen on xda really cares about!
Glad to hear you finally got it working!
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.
Hey guys, having some issues with my new GT-I9195I LTE and was hoping someone might be able to help. The phone was running Android 4.4.4 Touch Wiz and had way too much bloat ware so I wanted to get a different rom on there. I followed a guide on rooting using CWM and Odin3 so I did that but as the phone rebooted I missed pressing vol up, home and power and it rebooted into the stock OS. After that I powered off and tried to boot back into recovery but it now just says "Could not do normal boot" in red at the top, and shows the "Downloading..." screen. After that I tried a bunch of different things such as TWRP which made no difference, and even flashing a stock rom I got from SamMobile but Odin fails to flash the stock rom with a FAIL (Auth) message. After all that, it's basically stuck in a boot loop. I can however get it to download mode (vol down, home and power) and use Odin to flash it but they don't seem to make a difference.
Can anyone help guide me through this and back to a working device?
For info, the download screen says the following at the top:
ODIN MODE
PRODUCT NAME: GT-I9195I
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, H1, R1, A1, P1
SECURE DOWNLOAD: ENABLE
Thanks guys.
Wow... you flashed cwm and twrp and you have knox 0x0???Is it possible?
Davidich said:
Wow... you flashed cwm and twrp and you have knox 0x0???Is it possible?
Click to expand...
Click to collapse
I guess so! Though perhaps it has something to do with the fact that I don't seem to have a working recovery mode? The weird thing is I didn't get an error from Odin when flashing either of those, yet it didn't seem to make any difference.
Any ideas on what else I could try?
nero120 said:
I guess so! Though perhaps it has something to do with the fact that I don't seem to have a working recovery mode? The weird thing is I didn't get an error from Odin when flashing either of those, yet it didn't seem to make any difference.
Any ideas on what else I could try?
Click to expand...
Click to collapse
Download a stock rom for your s4 mini from sammobile and flash it with odin...it must restore like factory new your phone
Davidich said:
Download a stock rom for your s4 mini from sammobile and flash it with odin...it must restore like factory new your phone
Click to expand...
Click to collapse
Got a UK rom from sammobile but when I try to flash it complains that "repartition failed" which is strange as I haven't added a PIT file and the Repartition box in Odin is unchecked. That made me think I must have screwed up the partition table.
So I got a PIT file from here and tried flashing that, but this also fails with Odin saying "Re-Partition operation failed" and on the phone it says "SECURE CHECK FAIL : PIT". :s
Any ideas?
http://forums.androidcentral.com/an...018-solved-softbricked-samsung-galaxy-s3.html watch here....do the same things but for s4 mini
Same problem... :crying:
Davidich said:
watch here....do the same things but for s4 mini
Click to expand...
Click to collapse
BOOM! It worked! Actually the problem in the end was down to my own carelessness. I had initially downloaded a rom from sammobile that was a GT-I9195 *NOT* GT-I9195I - big difference! I guess all those errors in Odin weretrying to tell me the rom I'm trying to flash is not for my device! Anyways, when I downloaded the GT-I9195I stock UK O2 network rom and flashed it with Odin it worked perfectly, I didn't even need to get into restore mode to clear cache. It booted straight into Android and then I did a factory reset. Now, I have a much slicker faster phone, thank you so much for your help Davidich!
If anyone else has similar problems then I implore them to double and triple check that the ROM they are trying to flash is indeed for their specific device. It's not exactly clear when you're downloading random roms from forums, but sammobile is clear at least when downloading stock roms.
nero120 said:
BOOM! It worked! Actually the problem in the end was down to my own carelessness. I had initially downloaded a rom from sammobile that was a GT-I9195 *NOT* GT-I9195I - big difference! I guess all those errors in Odin weretrying to tell me the rom I'm trying to flash is not for my device! Anyways, when I downloaded the GT-I9195I stock UK O2 network rom and flashed it with Odin it worked perfectly, I didn't even need to get into restore mode to clear cache. It booted straight into Android and then I did a factory reset. Now, I have a much slicker faster phone, thank you so much for your help Davidich!
If anyone else has similar problems then I implore them to double and triple check that the ROM they are trying to flash is indeed for their specific device. It's not exactly clear when you're downloading random roms from forums, but sammobile is clear at least when downloading stock roms.
Click to expand...
Click to collapse
Nothing
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.