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.
Related
So I flashed cm 10.2 on my Galaxy S3 AT&T, and forgot to flash the right gapps, so I did that, except I forgot to do a factory reset when I flashed them. When I went to reboot, my phone would not turn on, nor get into recovery mode. It keeps showing the Samsung logo with the little CyanogenMod figure underneath it, and keeps vibrating repeatedly while trying to turn on. This is not a boot loop (I think) because my phone doesnt even get as far as the arrow animation that keeps going in circles. All I can do is access download mode. Can anyone help me? I have tried taking the battery out multple times and waiting for the battery to charge and then trying to turn it on, to no success.
rohanr014 said:
So I flashed cm 10.2 on my Galaxy S3 AT&T, and forgot to flash the right gapps, so I did that, except I forgot to do a factory reset when I flashed them. When I went to reboot, my phone would not turn on, nor get into recovery mode. It keeps showing the Samsung logo with the little CyanogenMod figure underneath it, and keeps vibrating repeatedly while trying to turn on. This is not a boot loop (I think) because my phone doesnt even get as far as the arrow animation that keeps going in circles. All I can do is access download mode. Can anyone help me? I have tried taking the battery out multple times and waiting for the battery to charge and then trying to turn it on, to no success.
Click to expand...
Click to collapse
If you can get to download mode, try flashing a stock file via Odin to reset your phone to working conditions. Thereafter, you can go back to a custom ROM. Would you recall what firmware version you were on prior to flashing CM? If it was anything older than 4.3 (e.g. 4.1.2, 4.1.1), you can Odin back to 4.1.1. If you already had 4.3, you would need to Odin back to 4.3 following the instructions posted in the thread below ..
http://forum.xda-developers.com/showthread.php?t=2722660&page=3. Scroll through carefully for the file you need for 4.3. Otherwise, you can find the Odin flash-able 4.1.1 stock file on sammobile.com
Larry2999 said:
If you can get to download mode, try flashing a stock file via Odin to reset your phone to working conditions. Thereafter, you can go back to a custom ROM. Would you recall what firmware version you were on prior to flashing CM? If it was anything older than 4.3 (e.g. 4.1.2, 4.1.1), you can Odin back to 4.1.1. If you already had 4.3, you would need to Odin back to 4.3 following the instructions posted in the thread below ..
http://forum.xda-developers.com/showthread.php?t=2722660&page=3. Scroll through carefully for the file you need for 4.3. Otherwise, you can find the Odin flash-able 4.1.1 stock file on sammobile.com
Click to expand...
Click to collapse
I have looked at the thread but I am new to all this stuff, how do I flash using Odin?
rohanr014 said:
I have looked at the thread but I am new to all this stuff, how do I flash using Odin?
Click to expand...
Click to collapse
First you will need to download and extract the Odin tool. Odin is Samsung's tool for flashing (installing) firmware. You can download Odin v3.07 via the link below ...
http://www.mediafire.com/download/772dlmuaxfgm0x2/Odin307.zip
Once you have downloaded it, extract the files and look for the executable file (*.exe). That's the one you will need to run to open Odin.
We also need to identify the appropriate firmware to flash. You did not answer the earlier question on what Android version your device was on prior to flashing the custom firmware. This is important to let us know which official version you can safely revert to (4.1.1 or 4.3). If you were an older version than 4.3, you should flash 4.1.1 but if you were already on 4.3, then you should stick to this. Either way, you can download the 4.1.1 file via this link .. http://rapidgator.net/file/681a28a5...ATT_I747UCDLK3_I747ATTDLK3_Original.zip.html?
Download the files to your PC and extract.
To flash via Odin, open Odin.exe on your PC
Click on the PDA tab and navigate to the file you just extracted. Select the file ending in *.tar.md5 (For 4.1.1, this would be I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5). Make sure this file is showing in the PDA tab.
Boot your phone into download mode and connect to your computer with a good quality micro-USB cable. Make sure your phone is recognized by Odin. You should see the message Added in the left pane.
Do not check or uncheck any boxes other than the defaults.
Click on start and waiting for firmware flashing to end and you see Pass. Your phone will reboot at this stage. You can disconnect from your PC
However, for 4.3, it looks like the Odin flash-able file has been taken offline so you would need to this via custom recovery. That's a different process so please revert on your Android version first so we'll know whether this is required or not
I was running JB 4.3, and I am planning to flash 4.1.1 as you've said. I am downloading that rom from the SamMobile site, however it is taking quite a while...
I understand that it shouldnt be a two minute download, however its been 2 hours and only 210 MB has been downloaded.
Also, I have Odin v3.09, which in the place of a PDA tab, there is an AP tab... should I place the file in the AP tab?
rohanr014 said:
I was running JB 4.3, and I am planning to flash 4.1.1 as you've said. I am downloading that rom from the SamMobile site, however it is taking quite a while...
I understand that it shouldnt be a two minute download, however its been 2 hours and only 210 MB has been downloaded.
Also, I have Odin v3.09, which in the place of a PDA tab, there is an AP tab... should I place the file in the AP tab?
Click to expand...
Click to collapse
Please do not try to flash 4.1.1 if you were on JB 4.3 otherwise you could hard brick your phone due to the secure bootloader in 4.3. You need to revert to stock 4.3 via custom recovery. You may go to the thread below for instructions...
http://forum.xda-developers.com/showthread.php?t=2658486
1) Flash custom recovery (I would suggest TWRP because of the GUI). In Odin v3.09 use the AP tab in place of PDA. You can download TWRP for your device via the link below ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
2) Download the stock restore zip file in the thread above and copy to your (micro) SD card. The (TWRP) stock restore zip is also available via the following link .... http://www.mediafire.com/download/30idxwhg2hidxx2/ATT_I747_UCUEMJB_StockRestore_2282014.zip
3) Flash the custom recovery file via Odin. Remove battery immediately the flashing is complete to stop reboot.
4) Place the SD card with the recovery file in your phone
5) Reboot into recovery mode by simultaneously holding down the Volume Up, Home and Power buttons. Hold all buttons until you see the blue flash across your screen, then release power button but keep holding the volume up and home buttons until the Android image appears.
6) Select install and navigate to the stock restore file. Swipe across screen to flash and wait for installation to be complete.
7) Clear cache/dalvik and reboot to system
If you are unable to boot to recovery, then you may still try flashing using Odin v3.09. You may follow the instructions in the thread below and load all the respective partitions. You would need to use the version that has separate flashable files as the single *.tar file has been taken down.
Larry2999 said:
Please do not try to flash 4.1.1 if you were on JB 4.3 otherwise you could hard brick your phone due to the secure bootloader in 4.3. You need to revert to stock 4.3 via custom recovery. You may go to the thread below for instructions...
http://forum.xda-developers.com/showthread.php?t=2658486
1) Flash custom recovery (I would suggest TWRP because of the GUI). In Odin v3.09 use the AP tab in place of PDA. You can download TWRP for your device via the link below ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
2) Download the stock restore zip file in the thread above and copy to your (micro) SD card. The (TWRP) stock restore zip is also available via the following link .... http://www.mediafire.com/download/30idxwhg2hidxx2/ATT_I747_UCUEMJB_StockRestore_2282014.zip
3) Flash the custom recovery file via Odin. Remove battery immediately the flashing is complete to stop reboot.
4) Place the SD card with the recovery file in your phone
5) Reboot into recovery mode by simultaneously holding down the Volume Up, Home and Power buttons. Hold all buttons until you see the blue flash across your screen, then release power button but keep holding the volume up and home buttons until the Android image appears.
6) Select install and navigate to the stock restore file. Swipe across screen to flash and wait for installation to be complete.
7) Clear cache/dalvik and reboot to system
If you are unable to boot to recovery, then you may still try flashing using Odin v3.09. You may follow the instructions in the thread below and load all the respective partitions. You would need to use the version that has separate flashable files as the single *.tar file has been taken down.
Click to expand...
Click to collapse
Just to reaffirm since I am not very experienced and do not wish to break my phone:
1) Download the twrp 2.6.3.1 d2att.tar file and flash it to my phone in download mode via Odin.
2)Download zip file on my computer, and take out the microSD from my phone, and copy the file to my microSD.
3) I am confused here because you stated to flash the custom recovery in step 1... anyways when flash is complete I immediately take my battery out to stop the reboot.
4) I insert the microSD with the zip file containing the stock rom
5) Now I should be able to reboot into recovery mode on my phone, though I could not beforehand.
6) Once in Recovery, go to Install and flash the custom stock.
7)Wipe dalvik cache and cache, and reboot to system.
Please clear up any confusion, I am very cautious and inexperienced. Sorry.
rohanr014 said:
Just to reaffirm since I am not very experienced and do not wish to break my phone:
1) Download the twrp 2.6.3.1 d2att.tar file and flash it to my phone in download mode via Odin.
2)Download zip file on my computer, and take out the microSD from my phone, and copy the file to my microSD.
3) I am confused here because you stated to flash the custom recovery in step 1... anyways when flash is complete I immediately take my battery out to stop the reboot.
4) I insert the microSD with the zip file containing the stock rom
5) Now I should be able to reboot into recovery mode on my phone, though I could not beforehand.
6) Once in Recovery, go to Install and flash the custom stock.
7)Wipe dalvik cache and cache, and reboot to system.
Please clear up any confusion, I am very cautious and inexperienced. Sorry.
Click to expand...
Click to collapse
Yes, you are correct. What you are doing in step 1) is flashing custom recovery to your phone. Custom recovery allows you install zip files to your phone and is more functional and versatile than stock recovery.
The zip file referred to in 2) is the stock restore zip. This is the file you will be flashing from (custom) recovery and is the one from the following link (http://www.mediafire.com/download/30...re_2282014.zip). Once you have downloaded it to your computer, save to an SD card so you can insert it into your phone to flash.
The battery pull is after flashing the TWRP file. You then have to boot into (custom) recovery mode to flash the stock restore zip from the SD card.
You are OK on the other steps. Trust this clarifies. Let me know if you encounter any issues.
I have done everything you said, I flashed the TWRP file via Odin, and then i copied the stock zip file to my microSD and put it back into my phone.
I am able to boot into recovery, and everytime I go to flash the stock rom, midway through the flash my phone starts rebooting. Even if I try to clear dalvik cache and cache first, once they are cleared my phone automatically starts rebooting. What do I do now? The zip file is there and I can reach TWRP recovery, but the flash wont complete because my phone starts rebooting. I am at a 100% battery right now so I do not know what the cause of this could be. Please help, I cannot tell what I did wrong if I did do anything wrong.
Try installing the latest version of Philz Touch for the d2lte. Some people have good results with TWRP. I found Philz Touch, which is based on CWM, better for my purposes. Philz can be installed via Odin as long as you down the tar version.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
Larry2999 said:
Yes, you are correct. What you are doing in step 1) is flashing custom recovery to your phone. Custom recovery allows you install zip files to your phone and is more functional and versatile than stock recovery.
The zip file referred to in 2) is the stock restore zip. This is the file you will be flashing from (custom) recovery and is the one from the following link (http://www.mediafire.com/download/30...re_2282014.zip). Once you have downloaded it to your computer, save to an SD card so you can insert it into your phone to flash.
The battery pull is after flashing the TWRP file. You then have to boot into (custom) recovery mode to flash the stock restore zip from the SD card.
You are OK on the other steps. Trust this clarifies. Let me know if you encounter any issues.
Click to expand...
Click to collapse
Ok, something very strange has occured.
Since my phone would not flash the original stock rom, I decided to go ahead and flash CM10.2 and its gapps to see if it the problem was with my phone or with the file. Everything worked fine and my phone booted and ran CM10.2, but then I had absolutely no signal anywhere. I could confirm something was wrong because there were multiple AT&T users near me that had good signal. So then I went to flash the stock rom, and it worked. I cleared dalvik and cache like normal after all these flashes and performed factory resets, however when I flashed this stock rom, it worked but 1) I could not connect to Wifi 2) I could not use apps with root requirements, and Root Checker said I did not have root access, even though I had definitely rooted my phone earlier when I first ran CM11 and CM10.2
Should I root again? Please help, my phone is working and I can go into download, stock recovery, and normal mode.
audit13 said:
Try installing the latest version of Philz Touch for the d2lte. Some people have good results with TWRP. I found Philz Touch, which is based on CWM, better for my purposes. Philz can be installed via Odin as long as you down the tar version.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
Click to expand...
Click to collapse
The whole idea was to get your phone back to working state. Thereafter, you can build up on the food chain. The stock file you flashed restores the phone to near factory settings including a complete stock (official) firmware, stock recovery, resetting the flash counter. Unfortunately, it also removes root as well. You can, however, re-root in a number of ways. You may also do as Audit advised and reflash Philz Touch custom recovery which would allow you flash any custom ROM of your choice. You do not necessarily need to root to flash custom ROMs if you have custom recovery. However, if you need to use apps which require root, I would recommend you try SafeRoot (http://forum.xda-developers.com/showthread.php?t=2565758). Very easy to use and worked quite well for me.
Finally, you should be able to restore your Wi-Fi from settings. Wi-Fi setup should have happened during the set-up process upon reboot after the firmware installation but sometimes this step is skipped. If you go to Settings, you should be able to enable and set up Wi-Fi.
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.
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
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
Trying to fix a friend's GT-N7105. At the moment it just bootloops the Samsung bootloader screen (which shows the model number GT-N7105).
I can boot it into download mode just fine. On download mode it just says that both the "Current Binary" and "System Status" are "Custom".
I've tried flashing the stock ROM for the phone (the latest for the Optus version) with Odin. I've also tried doing a firmware restore through Kies 2. Both of these complete fine, but the phone continues bootlooping the Samsung logo.
I've tried directly flashing the newest bootloader with Odin, and I've tried flashing a custom recovery with Odin. I've tried flashing the stock firmware with the device's PIT file and re-partition selected. Nothing seems to change how the phone behaves. I can't boot into recovery mode (it just continues the Samsung logo bootlooping).
The emmc doesn't seem busted, since it happily downloads the full system.img when flashing. Odin/Kies finish flashing without errors, so I'm stumped. Any ideas?
Passa91 said:
Trying to fix a friend's GT-N7105. At the moment it just bootloops the Samsung bootloader screen (which shows the model number GT-N7105).
I can boot it into download mode just fine. On download mode it just says that both the "Current Binary" and "System Status" are "Custom".
I've tried flashing the stock ROM for the phone (the latest for the Optus version) with Odin. I've also tried doing a firmware restore through Kies 2. Both of these complete fine, but the phone continues bootlooping the Samsung logo.
I've tried directly flashing the newest bootloader with Odin, and I've tried flashing a custom recovery with Odin. I've tried flashing the stock firmware with the device's PIT file and re-partition selected. Nothing seems to change how the phone behaves. I can't boot into recovery mode (it just continues the Samsung logo bootlooping).
The emmc doesn't seem busted, since it happily downloads the full system.img when flashing. Odin/Kies finish flashing without errors, so I'm stumped. Any ideas?
Click to expand...
Click to collapse
Make sure that you have pressed power + volume up + home button to boot into recovery (maybe you have known already)
And try to format everything: data, system, cache,...Wipe everything. There should be some adb commands to do it without recovery. After that reflash stock ROM again to see if it work.
@Passa91
@ginga133
I can access to recovery mod from odin !
I confirm when I flash this file (BTW it is recovery & cash fix file made by chainfire ) , via odin my phone reboot into stock recovery !!
you can try it At your own risk
here ( in recovery) you can do what you need (delete cash / data..... reboot)
my PC win10 pro 64bit, odin v3.11.1
my phone N7100 twrp 3.0.2.0 , stock kernel , custom rom......
kindly check attached pictures
at last I hope it will help
Regards
xcorona said:
@Passa91
@ginga133
I can access to recovery mod from odin !
I confirm when I flash this file (BTW it is recovery & cash fix file made by chainfire ) , via odin my phone reboot into stock recovery !!
you can try it At your own risk
here ( in recovery) you can do what you need (delete cash / data..... reboot)
my PC win10 pro 64bit, odin v3.11.1
my phone N7100 twrp 3.0.2.0 , stock kernel , custom rom......
kindly check attached pictures
at last I hope it will help
Regards
Click to expand...
Click to collapse
Thanks for that. This seems to be for the N7100. I tried flashing that file both as is and when replacing the included recovery with one appropriate for the N7105. Still just boots back to the bootloader (looping, same as before). Certainly didn't make anything worse.
If I leave it alone, sometimes it randomly makes it to the animated Samsung logo, where it plays the boot sound (dun dun dun duuun dun), but then this animation loops forever (I have tried leaving it overnight).
Passa91 said:
Thanks for that. This seems to be for the N7100. I tried flashing that file both as is and when replacing the included recovery with one appropriate for the N7105. Still just boots back to the bootloader (looping, same as before). Certainly didn't make anything worse.
If I leave it alone, sometimes it randomly makes it to the animated Samsung logo, where it plays the boot sound (dun dun dun duuun dun), but then this animation loops forever (I have tried leaving it overnight).
Click to expand...
Click to collapse
sorry to hear that
i think N7105 differs from N7100 {modem & kernel (boot*img ) }afaik, I cannot confirm
anyhow I did not find an alert from the developer regarding this matter (N7105/N7100) in his post
https://forum.xda-developers.com/showthread.php?t=1932327
at last thanks for reporting your results
Regards
xcorona said:
@Passa91
@ginga133
I can access to recovery mod from odin !
I confirm when I flash this file (BTW it is recovery & cash fix file made by chainfire ) , via odin my phone reboot into stock recovery !!
you can try it At your own risk
here ( in recovery) you can do what you need (delete cash / data..... reboot)
my PC win10 pro 64bit, odin v3.11.1
my phone N7100 twrp 3.0.2.0 , stock kernel , custom rom......
kindly check attached pictures
at last I hope it will help
Regards
Click to expand...
Click to collapse
I've flashed the file, but still having the same bootloop problem. It is ok, I have ordered a new motherboard now. Thanks for the input.