Samsung Galaxy tab S SM-T800 Help Pleaseeeeee - Galaxy Tab S Q&A, Help & Troubleshooting

Tablet is stuck on samsung boot screen
I got it in this state not sure about history
I used odin to flash multiple firmwares (every firmware flashed successfully after rebooting it says android is updating then give this error error below)
Recovery <3e>
E:failed to verify whole-file signature
E:signature verification failed
Installation Aborted
i tried from kitkat to lollipop minimum 5 to 6 including IRON ROM
THEY ALL FLASHED BELOW ARE SOME OF THEM
CURRENTLY ON (T800XXUIBOCC)BTU
(T800XXU1BOCC)
(T800XXU1ANF8)
(T800XXU1BOE2)
(T800XXU1ANFB)
( Firmwares i used i have tested them on some demo devices they worked flawlessly )
Also tried kies IT DOWNLOADED THEN FLASHED BUT GAVE SAME ERROR
Twrp 2.8.1.0 works on my tab no further version
I cant flash zip via twrp it says no md5 found error
i am able to get into download mode can flash by odin any firmware
problem i get every time is below
recovery <3e>
E:failed to verify whole-file signature
E:signature verification failed
Installation Aborted
I have spent 2 weeks on xda forums tried many things i cant remember all of them now
any help pleaseeeee

OK the first big mistake you are making is attempting to flash firmware in stock recovery.
This is *NOT* DOWNLOAD mode.
To enter DOWNLOAD mode hold POWER +HOME +VOL DOWN(not up)
You will then see a screen asking if you wish to continue. Select continue.
Then load your stock firmware with the md5 extension into the AP tab of ODIN and flash.
It will auto reboot and take about ten minutes on the SAMSUNG loading screen to complete booting.

Flashing 100 % in download mode
ashyx said:
OK the first big mistake you are making is attempting to flash firmware in stock recovery.
This is *NOT* DOWNLOAD mode.
To enter DOWNLOAD mode hold POWER +HOME +VOL DOWN(not up)
You will then see a screen asking if you wish to continue. Select continue.
Then load your stock firmware with the md5 extension into the AP tab of ODIN and flash.
It will auto reboot and take about ten minutes on the SAMSUNG loading screen to complete booting.
Click to expand...
Click to collapse
I am flashing in download mode using power +volume down+home ( then volume up to get in download mode )
Odin add md5 then flashes 100% tablet reboot shows samsung boot screen for 5 secs then green android comes wiggling ears
A green line flashes says updating after 25 % (i assume 25 %by line going green) it goes back to start then goes again to 25 % (i assume 25 %by line going green)
Then that message
Recovery <3e>
Failed to update package
whole file e signature failed
help pleassseeee

You need to post a screen shot, I've never heard of this before.
I'd also advise you try a different cable and pc.

Will post screen shots in morning
ashyx said:
You need to post a screen shot, I've never heard of this before.
I'd also advise you try a different cable and pc.
Click to expand...
Click to collapse
I thing i would also like to mention as it clicked my mind after your 1 reply
when i press only power button to turn it on tablet sometimes goes directly to recovery without using button combo
then says no command and android thingi dies with red triangle popping from chest

wont let me post images
ashyx said:
You need to post a screen shot, I've never heard of this before.
I'd also advise you try a different cable and pc.
Click to expand...
Click to collapse
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!

Booting into recovery everytime
ashyx said:
You need to post a screen shot, I've never heard of this before.
I'd also advise you try a different cable and pc.
Click to expand...
Click to collapse
I am sure my tablet is going directly into recovery when i press power button
i have observed it with twrp also when i flash twrp after twrp successfully installed it shows boot screen then goes directly to twrp without button combo
i have uploaded all images on imageshack but i cant upload them

power on off
ashyx said:
You need to post a screen shot, I've never heard of this before.
I'd also advise you try a different cable and pc.
Click to expand...
Click to collapse
one more thing when i plug it for charging it shows samsung boot screen not battery charging screen
i have back cover off so i disconnected battery to power it off and checked with that also it shows samsung boot screen
even when it is power off (disconnecting battery then connecting ) connected with pc also shows samsung boot screen
by boot screen i mean the first one you see when powering on not the logo
Also your 1st reply that i am flashing firmware in recovery is leading me to conclusion that my tab is going directly into recovery after boot
Also i can email you all the photos of whole process i take photos of odin and tablet at the same time and used other pc and cable

It seems your partitions are messed up somehow. This probably happened flashing cm and why it boots to recovery.
I've seen this behaviour before.
I'd advise you to flash the stock firmware with the pit file for the t800.
You will find the pit file on this forum.

Will do and update
ashyx said:
It seems your partitions are messed up somehow. This probably happened flashing cm and why it boots to recovery.
I've seen this behaviour before.
I'd advise you to flash the stock firmware with the pit file for the t800.
You will find the pit file on this forum.
Click to expand...
Click to collapse
Thank you will do and update

Same result
ashyx said:
It seems your partitions are messed up somehow. This probably happened flashing cm and why it boots to recovery.
I've seen this behaviour before.
I'd advise you to flash the stock firmware with the pit file for the t800.
You will find the pit file on this forum.
Click to expand...
Click to collapse
Used stock with pit same result landed in recovery after flash same error
when i reboot it goes to directly to recovery after boot screen

mastjadoon said:
Used stock with pit same result landed in recovery after flash same error
when i reboot it goes to directly to recovery after boot screen
Click to expand...
Click to collapse
Ok can you try flashing my latest twrp in the dev section.
Make sure you disable auto-reboot then force reboot into recovery.
Are there any errors at all when flashing?

Twrp
ashyx said:
Ok can you try flashing my latest twrp in the dev section.
Make sure you disable auto-reboot then force reboot into recovery.
Are there any errors at all when flashing?
Click to expand...
Click to collapse
Yes will do
There are no errors in odin

Images
ashyx said:
You need to post a screen shot, I've never heard of this before.
I'd also advise you try a different cable and pc.
Click to expand...
Click to collapse
http://imageshack.com/a/img903/8343/lrKUQB.jpg
http://imageshack.com/a/img907/7663/d8EYtX.jpg
http://imageshack.com/a/img911/4048/ewVIZi.jpg
http://imageshack.com/a/img908/2148/bD3I2A.jpg
http://imageshack.com/a/img910/9052/vxv1OG.jpg
http://imageshack.com/a/img908/6008/MDTkbY.jpg
http://imageshack.com/a/img910/3480/P2MxPA.jpg
http://imageshack.com/a/img901/8369/ZYccFK.jpg
http://imageshack.com/a/img901/6032/KWbV5m.jpg
http://imageshack.com/a/img907/4011/jdDw2U.jpg
http://imageshack.com/a/img905/2626/9xMXn7.jpg
http://imageshack.com/a/img911/1065/OVwrzx.jpg
http://imageshack.com/a/img901/838/LSJ3Mw.jpg
http://imageshack.com/a/img910/7158/yNuogo.jpg
http://imageshack.com/a/img907/5787/i2Gnf6.jpg
http://imageshack.com/a/img907/7690/Ojuh6M.jpg

Twrp
ashyx said:
Ok can you try flashing my latest twrp in the dev section.
Make sure you disable auto-reboot then force reboot into recovery.
Are there any errors at all when flashing?
Click to expand...
Click to collapse
tried as advised new twrp 2.8.7.2-f2fs with auto reboot unchecked
when force rebooted into recovery if flashes on teamwin logo wont go further

OK from what I can gather from your images is that you start off with a lollipop firmware then flash an early ANFB firmware.
As far as I can remember it boots into recovery afterwards on that firmware to complete the flashing process.
However it seems it is not compatible with your model.
What region is this tablet from?
I'd forget about flashing KitKat firmware for now. Use lollipop firmware.
The first thing I suggest is to manually boot to recovery and wipe the cache partition then wipe data/factory reset.
Next is stop using ODIN 3.09 and download 3.10.7
Load the lollipop firmware correct for the device region and flash with ODIN.
If it fails after booting to recovery, wipe the cache partition again and see if it boots.
If not report back and I'll post how to get past it.

Its UK model
ashyx said:
OK from what I can gather from your images is that you start off with a lollipop firmware then flash an early ANFB firmware.
As far as I can remember it boots into recovery afterwards on that firmware to complete the flashing process.
However it seems it is not compatible with your model.
What region is this tablet from?
I'd forget about flashing KitKat firmware for now. Use lollipop firmware.
The first thing I suggest is to manually boot to recovery and wipe the cache partition then wipe data/factory reset.
Next is stop using ODIN 3.09 and download 3.10.7
Load the lollipop firmware correct for the device region and flash with ODIN.
If it fails after booting to recovery, wipe the cache partition again and see if it boots.
If not report back and I'll post how to get past it.
Click to expand...
Click to collapse
Will get back asap after following instructions

Tried with odin 3.10.7 same result
ashyx said:
OK from what I can gather from your images is that you start off with a lollipop firmware then flash an early ANFB firmware.
As far as I can remember it boots into recovery afterwards on that firmware to complete the flashing process.
However it seems it is not compatible with your model.
What region is this tablet from?
I'd forget about flashing KitKat firmware for now. Use lollipop firmware.
The first thing I suggest is to manually boot to recovery and wipe the cache partition then wipe data/factory reset.
Next is stop using ODIN 3.09 and download 3.10.7
Load the lollipop firmware correct for the device region and flash with ODIN.
If it fails after booting to recovery, wipe the cache partition again and see if it boots.
If not report back and I'll post how to get past it.
Click to expand...
Click to collapse
Flashed 2 lolipop roms 1 for uk same result
second canada same result landed in recovery after flash same error
One thing it is now not going in recovery on power button
when i press power button boot screen shows and then it goes blank
can get through button combo

mastjadoon said:
Flashed 2 lolipop roms 1 for uk same result
second canada same result landed in recovery after flash same error
One thing it is now not going in recovery on power button
when i press power button boot screen shows and then it goes blank
can get through button combo
Click to expand...
Click to collapse
It will always go to recovery after flashing as it uses recovery to complete the flashing process.
Even if it fails in recovery just wipe cache and factory reset and it should boot.
Will take about ten minutes on the SAMSUNG logo with sparks then you will see the updating message and finally boot into android.
To circumvent the device booting into recovery after flashing use 7zip and right click on the md5 file then choose open archive and highlight sboot.bin, boot.img, recovery.img and system.img.
Drag these out of the window into an empty folder.
Next highlight these four files and right click then in 7zip select 'add to archive'
Select 'tar' and make sure compression method is 'store'.
Once the process is finished you can flash the resulting tar file in AP slot of ODIN.

Will do and update asap
ashyx said:
It will always go to recovery after flashing as it uses recovery to complete the flashing process.
Even if it fails in recovery just wipe cache and factory reset and it should boot.
Will take about ten minutes on the SAMSUNG logo with sparks then you will see the updating message and finally boot into android.
To circumvent the device booting into recovery after flashing use 7zip and right click on the md5 file then choose open archive and highlight sboot.bin, boot.img, recovery.img and system.img.
Drag these out of the window into an empty folder.
Next highlight these four files and right click then in 7zip select 'add to archive'
Select 'tar' and make sure compression method is 'store'.
Once the process is finished you can flash the resulting tar file in AP slot of ODIN.
Click to expand...
Click to collapse
Just got home after work will follow your advise and will update

Related

AOKP to STOCK BIG PROBLEMS

i need some help here guys. i was running AOKP for the longest time and loving it. then today i tried to update to the latest version. i downloaded the rom and went to flash the .zip in CWM. i've done this dozens of times. this time things were completely different. i kept getting FCs over and over. so i booted into recovery again to reflash. for whatever reason, it seemed like my file system was corrupted. folders i had never seen were all over the place. it was a big mess. i decided to flash back to stock. i booted into DL mode and did this with odin successfully. then upon reboot, the phone was stuck at the Samsung logo. looking into this i saw that i needed to boot into recovery, wipe data/factory reset, wipe cache, and wipe dalvik cache. i tried doing this but no matter what, my phone will not boot into recovery. i have even used odin to flash CF-SGS3-CWM-v5.5-v1.0.tar. when i press volume up+home+power i get the first samsung logo with the tiny blue text up at the top saying "recovery booting" but then nothing happens and the phone just goes to a normal boot attempt, which stalls at the samsung logo. please help guys. just for a quick overview. was on [ROM] AOKP(Jellybean 4.2.1 )Task & Ktoonsez (12/23) (AT&T/Rogers), potential file system corruption during a routine upgrade, flashed back to stock with odin (meaning i can still boot into DL mode), but CANNOT boot into RECOVERY mode. i'm freaking out
jamesquags said:
i need some help here guys. i was running AOKP for the longest time and loving it. then today i tried to update to the latest version. i downloaded the rom and went to flash the .zip in CWM. i've done this dozens of times. this time things were completely different. i kept getting FCs over and over. so i booted into recovery again to reflash. for whatever reason, it seemed like my file system was corrupted. folders i had never seen were all over the place. it was a big mess.
i decided to flash back to stock. i booted into DL mode and did this with odin successfully. then upon reboot, the phone was stuck at the Samsung logo. looking into this i saw that i needed to boot into recovery, wipe data/factory reset, wipe cache, and wipe dalvik cache. i tried doing this but no matter what, my phone will not boot into recovery.
i have even used odin to flash CF-SGS3-CWM-v5.5-v1.0.tar. when i press volume up+home+power i get the first samsung logo with the tiny blue text up at the top saying "recovery booting" but then nothing happens and the phone just goes to a normal boot attempt, which stalls at the samsung logo. please help guys.
just for a quick overview. was on [ROM] AOKP(Jellybean 4.2.1 )Task & Ktoonsez (12/23) (AT&T/Rogers), potential file system corruption during a routine upgrade, flashed back to stock with odin (meaning i can still boot into DL mode), but CANNOT boot into RECOVERY mode. i'm freaking out
Click to expand...
Click to collapse
First of all, good job on searching before posting! :good:
Second, if you want help, try using capital letters at the start of a sentence and using paragraphs. It makes it sooo much easier to read that way.
Third, just keep trying. But from what you're saying about a file-system issue, that could be bad? It's not familiar to me anyways. Hope it didn't damage the internal SD.
If nothing else works, then try the USB-JIG to access Recovery mode. They're like $5 on eBay.
Okay, try these things.
1) Odin a non-rooted, stock ROM that comes with a 3E recovery and try to access that recovery.
If that doesn't work, move onto this step:
2) Odin a different recovery. I attached one to this post. Just unzip it and then odin it. :CWM-Recovery-LTE-SGS3-v5.tar:
Try to get recovery again after a battery pull.
If that doesn't do it, then try this next:
1) Odin a rooted ROM onto the phone.
2) Download the attached "openrecovery-twrp-2.3.1.0-d2att" and unzip it.
3) Download this ADB & Fastboot tool and extract it to your C:/ drive with subfolders using this path: "C:/Android/platform-tools/".
Here is the file to download:
http://www.androidfilehost.com/?fid=9390135922294523275
4) Rename the openrecovery-twrp-2.3.1.0-d2att to "recovery" and place it into the Platform-tools folder.
5) Open the JPEG and follow the EXACT same commands in the pic. This will install TWRP recovery for you.
Then try once again to get into recovery.
If it still doesn't work, then buy a USB Jig.
REPLY
Thanks so much for the advice.
Regarding the TWRP installation, is the phone connected to the computer in DL mode for this?
I am currently downloading a rooted stock ROM. This might help shed light on what is going on here.... I unzipped the .tar you attached to your first post and stuck it in the PDA slot with the phone connected and in DL mode. ODIN did nothing and the returned a FAIL message saying that it "Failed to Open Serial [COM] Port". Hmmmm. Anyways I am going to try to install the TWRP recovery. If not I will buy the USB jig. Thanks again for you help. -jim
jamesquags said:
"Failed to Open Serial [COM] Port".
Click to expand...
Click to collapse
Have you installed the phone drivers? They're linked from the Odin thread.
smelenchuk said:
Have you installed the phone drivers? They're linked from the Odin thread.
Click to expand...
Click to collapse
Yes i have installed the drivers. I have flashed multiple .tar files today.
jamesquags said:
Thanks so much for the advice.
Regarding the TWRP installation, is the phone connected to the computer in DL mode for this?
I am currently downloading a rooted stock ROM. This might help shed light on what is going on here.... I unzipped the .tar you attached to your first post and stuck it in the PDA slot with the phone connected and in DL mode. ODIN did nothing and the returned a FAIL message saying that it "Failed to Open Serial [COM] Port". Hmmmm. Anyways I am going to try to install the TWRP recovery. If not I will buy the USB jig. Thanks again for you help. -jim
Click to expand...
Click to collapse
The TWRP doesn't use Odin. You have to use ADB/FastBoot like I show in the picture attached with it.
I have yet to find an Odin flashable TWRP.
CZ Eddie said:
The TWRP doesn't use Odin. You have to use ADB/FastBoot like I show in the picture attached with it.
I have yet to find an Odin flashable TWRP.
Click to expand...
Click to collapse
After flashing the ROOTED STOCK ROM, I tried about 7 times to boot into recovery. It finally did!!! I then was able to do a wipe data and cache and I'm all set.
Thanks so much for helping me out. -jim
To get into recovery hold the power+volume up+ home key when you see the blue text at the top of the screen let go if the power button but still press the home + volume up
Sent from my SGH-I747 using Tapatalk 2
jerrycoffman45 said:
To get into recovery hold the power+volume up+ home key when you see the blue text at the top of the screen let go of the power button but still press the home + volume up
Click to expand...
Click to collapse
Why do you continue to hold the home + volume up? I release all three as soon as I see the blue text and it goes into Recovery just fine for me.
CZ Eddie said:
Why do you continue to hold the home + volume up? I release all three as soon as I see the blue text and it goes into Recovery just fine for me.
Click to expand...
Click to collapse
i dont know i have always done it that way well learned something new just tried it your way thanks

Prevention Information ERROR

Hi i have the following error :
When i try to click on WI-FI button comes up the following
prevention information
the device has detected an application attempting unppermitted actions and has stopped loading.To protect your device it is recomended you reboot.
I have rooted my phone using the topic here
http://forum.xda-developers.com/showthread.php?t=2258633
i had to load the
http://k0nane.info/rom/SGH-M919-UVUAMDB-k0nane.7z
file first cos i was getting an failure when installing the superuser using odin 3.0.7
my recovery is TWRP 2.5.0.0 and i am on wicked v1
Anyone else have this issue?
I had the same issue if you check the build number and the baseband version they are not the same. If you re-odin the MDL build http://k0nane.info/rom/M919UVUAMDL_M919TMBAMDL_TMB.zip again then WIFI should work again. I got it rooted after that by doing the following:
1. Load the OUDHS CWM-Based Recovery 1.0.3.3 for T-Mo GS4, via odin uncheck auto reboot and goto to recovery http://k0nane.info/rom/OUDHS-Recovery-jfltetmo-1.0.3.3.tar
2. Install Chainfire's SuperSU http://www.shabbypenguin.com/Android/Scripts/Nexus-Files/Root/SuperSU-v1.25+.zip then
3 Install [KERNEL] Stock Touchwiz MDB - SetUID Restriction Removed http://d-h.st/GcM
Between installs make sure you wipe the cache and davik cache
then you reboot you should be rooted with the newest update MDL minus the kernel lock
yes its not same the build and the baseband
Is it possible to be done using the twrp?
other recovery was little difficult?
can u send me the links i need please i just don't want to mess around and brick my phone
Thanks a lot
kaniebas said:
yes its not same the build and the baseband
Is it possible to be done using the twrp?
other recovery was little difficult?
can u send me the links i need please i just don't want to mess around and brick my phone
Thanks a lot
Click to expand...
Click to collapse
Check my post again, I couldn't get TWRP to work at first but it maybe i did not uncheck the the auto reboot box when I did that. Once the the recovery is loaded via odin you need to pull the battery then do the home-up volume-power to get into the recovery. I notice TWRP was a bit too sensitive and could not scroll down the list of folders to get to the zip files
dhonzik said:
Check my post again, I couldn't get TWRP to work at first but it maybe i did not uncheck the the auto reboot box when I did that. Once the the recovery is loaded via odin you need to pull the battery then do the home-up volume-power to get into the recovery. I notice TWRP was a bit too sensitive and could not scroll down the list of folders to get to the zip files
Click to expand...
Click to collapse
i manage to install CWM using odin and when i rooted it i install goo manager ant now i am on TWRP
I've tried installing all three recoveries using Odin, but for some reason none are working and now when I try and boot into recovery it just restarts the phone. Anyone know what I should do?
oasad92 said:
I've tried installing all three recoveries using Odin, but for some reason none are working and now when I try and boot into recovery it just restarts the phone. Anyone know what I should do?
Click to expand...
Click to collapse
You need to uncheck the auto reboot box in odin, after the recovery transfer is complete pull the battery and unplug from your computer then do a boot into recover by holding the volume up-home-power button. If not rooted follow the instructions in my post above at the very least you need to load the kernel file
dhonzik said:
You need to uncheck the auto reboot box in odin, after the recovery transfer is complete pull the battery and unplug from your computer then do a boot into recover by holding the volume up-home-power button. If not rooted follow the instructions in my post above at the very least you need to load the kernel file
Click to expand...
Click to collapse
So I did that with all 3 recoveries like 2 or 3 times each, nothing was working I unchecked reboot then would just pull battery after reboot and hold vol up and power to try and get into recovery. Sometimes the litlte blue would appear in the top left corner saying "recovery booting" and would just stay there forever other times that would appear and then the phone would just reboot itself.
Anyway finally found instructions that allowed said to try checking auto reboot and f time reset so did that with a TWRP recovery tar and then it finished and rebooted. I then shut the phone off and held power and vol up to get into recovery and it loaded fine. I was then able to flash the chainfire superuser and kernel you posted. So Thanks a bunch man!

I9192 bricked, set warranty bit: recovery

This is my relative phone (S4 Mini Duos) so I am helping him, he flashed CM ROM then flashed the stock ROM again. After flashing is complete and successful the phone only shows
Recovery booting
Set warranty bit: recovery
If force reboot it will show the splash screen then vibrate and turn off, then vibrate and turn on and show the splash screen and so on in a continuous loop
No matter what stock ROM I flashed the result is the same I found a pit file but couldn't find a stock ROM in 4 parts (Bootloader, PDA, Phone, CSC) to debrick it, all I found is the one with one tar file.
I tried to flash TWRP or CWM recovery and it is the same result. All flash processes stock ROM or any recovery is successful but nothing help.
Can I have some suggestions, useful links to help get this phone working again because he can't afford buying a new one.
let me share some of my experience, although it may not help.
My first android device is samsung i9190. and my first time flashing stuff. I flashed twrp through odin and flashed cm12.1 through twrp.
i really liked the rom except i needed best camera which stock rom offer. so here what i did is just open odin and selected my firmware.tar.md5 and click started.
I had one problem arised that my phone would vibrate from time to time on samsung logo but would not start.
So i had to go in stock recover and formatted cache and system(sorry i do not remember it might be restore system option). and after i rebooted the phone worked. And i have done it many times that way it work.
You can also try and flash through kies.
As I said When I flash stock ROM, everything is successful but I have the same result, I can't go into recovery and can't boot normally
Hey there,
Try downloading Unified Android Tool by Skipsoft. It will download all the necessary files relating to your phone and there should be stock recovery files under your model. Then try and boot the necessary files through Odin and see from there. I have a similar problem but I found booting a custom rom helped. But first try and get into recovery. Hold power, home button and volume up to switch the phone on, let go of power when it comes to the logo and see if it reboots into recovery.
Good luck
GeezyTab88 said:
Hey there,
Try downloading Unified Android Tool by Skipsoft. It will download all the necessary files relating to your phone and there should be stock recovery files under your model. Then try and boot the necessary files through Odin and see from there. I have a similar problem but I found booting a custom rom helped. But first try and get into recovery. Hold power, home button and volume up to switch the phone on, let go of power when it comes to the logo and see if it reboots into recovery.
Good luck
Click to expand...
Click to collapse
Thanks for this tip, I will try Skipsoft tool. Right now I can't go into recovery as you see in the attached photo, if I could get a working recovery then maybe I could revive the phone.
OK I tried Skipsoft Unified Android Tool and downloaded all the files, flashing any recovery is successful but I get the same result...
Recovery booting
Set warranty bit: recovery
Still have no clue how to solve this.
If someone have a link for a repair 4 files (Bootloader, PDA, Phone, CSC) to use it with a Pit file, please provide a link
Thanks
salahmed said:
OK I tried Skipsoft Unified Android Tool and downloaded all the files, flashing any recovery is successful but I get the same result...
Recovery booting
Set warranty bit: recovery
Still have no clue how to solve this.
If someone have a link for a repair 4 files (Bootloader, PDA, Phone, CSC) to use it with a Pit file, please provide a link
Thanks
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24459283995303957

GT-I9195 multiiple unsuccessfull recovery flashing even though ODIN success

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.

S10+ (rooted) flashing update failed, now phone seems bricked

I wanted to update software of my rooted S10plus and flashing failed and my phone is stuck with this blue screen. I can reset it and it returns to this screen in a few secs. I cant enter recovery or anything. I tried flashing stock, separate parts of stock, previous rooted AP, all with and without PIT, with and without NAND erase ticked, I really tried everything I could think of any nothing works. Everything just fails. I hope there is someone smart enough here who can help me. This is correct stock that I was able to flash before. Tried different cables.
Example pic where I flashed stock with PIT and NAND ERASE ticked
The last screen you have is like download mode. Just leave it there and flash stock with odin.
butchieboy said:
The last screen you have is like download mode. Just leave it there and flash stock with odin.
Click to expand...
Click to collapse
I listed all of the things I tried in the post, among there is trying to flash stock with odin. It failed.
Are you International or United States? What was your bootloader version? Did you use boot.img to root or flash in recovery?
S10+ is SM-G975F...and you perhaps try to flashed firmware for wrong device.
Try to Flash only PIT file few times because you rendered partition unreadable.
.
Try open Recovery Mode and in Recovery Mode select factory/reset and restart phone. You will lose everything you installed.
ZmisiS said:
Try open Recovery Mode and in Recovery Mode select factory/reset and restart phone. You will lose everything you installed.
Click to expand...
Click to collapse
i see he already say that he cant go in to recovery.
Vuska said:
i see he already say that he cant go in to recovery.
Click to expand...
Click to collapse
Yes, but what else is left for him but to try to open Recovery mode.
I was in similar situations, but after many attempts, I still opened Recovery mode with various key combinations. For example, one of the solutions is to turn off the phone with various key combinations. After that, I would connect the phone to the computer and open Recovery mode the way you normally open Recovery mode.

Categories

Resources