Related
Hi guys,
Was trying to install a ROM last night in CWM Recovery, then I was having some difficulty, after each ROM swipe I was doing the Factory Wipe/Dalvik Cache Wipe/Cache Wipe.
Anyways, I ended up having to try and flash the pre-rooted Stock ROM, I used Odin 3.07 to flash it and in Odin it appeared to work fine, the phone was rebooting and Odin was in "Pass" mode, but the phone never gets beyond the Samsung boot screen.
I then tried to see if I could flash CWM Recovery in Odin and try and get into Recovery mode, it flashed fine in Odin and the device rebooted but still stuck in Samsung boot screen.... but I cannot get into Recovery mode manually, I even tried getting in via the Q3 Toolbox kit, and it says it cannot locate the device :/
So today, last desperate option, I tried flashing the un-rooted stock image for my carrier (Rogers), it seemed to work fine in Odin but it STILL just will not boot back up, still stuck in the Samsung boot screen.
Is this what a brick is? Beyond continually trying to re-flash the stock carrier MD5 via Odin, what can I do? Oddly enough the phone does recognize in the Q3 Toolbox for the Root options, just not for the Reboot into Recovery option. Is there something I can try in the Q3 Toolbox?
/Scared / really concerned
Please help, any help is appreciated.
Once again, I CANNOT get into CWM Recovery.
Sianspheric said:
Hi guys,
Was trying to install a ROM last night in CWM Recovery, then I was having some difficulty, after each ROM swipe I was doing the Factory Wipe/Dalvik Cache Wipe/Cache Wipe.
Anyways, I ended up having to try and flash the pre-rooted Stock ROM, I used Odin 3.07 to flash it and in Odin it appeared to work fine, the phone was rebooting and Odin was in "Pass" mode, but the phone never gets beyond the Samsung boot screen.
I then tried to see if I could flash CWM Recovery in Odin and try and get into Recovery mode, it flashed fine in Odin and the device rebooted but still stuck in Samsung boot screen.... but I cannot get into Recovery mode manually, I even tried getting in via the Q3 Toolbox kit, and it says it cannot locate the device :/
So today, last desperate option, I tried flashing the un-rooted stock image for my carrier (Rogers), it seemed to work fine in Odin but it STILL just will not boot back up, still stuck in the Samsung boot screen.
Is this what a brick is? Beyond continually trying to re-flash the stock carrier MD5 via Odin, what can I do? Oddly enough the phone does recognize in the Q3 Toolbox for the Root options, just not for the Reboot into Recovery option. Is there something I can try in the Q3 Toolbox?
/Scared / really concerned
Please help, any help is appreciated.
Once again, I CANNOT get into CWM Recovery.
Click to expand...
Click to collapse
You're soft bricked, don't panic just yet. A hard brick is when the device is completely unresponsive. So far this sounds fixable.
To get into recovery, are you holding down the volume up + home key for long enough after the Samsung logo appears?
I'd try that again, but if not: Try to Odin CWM again but uncheck "Auto-Reboot" in Odin. After it's done flashing, pull the battery out, put it back in, and use the key combos to get into recovery. Hopefully you have a nandroid backup saved or another rom saved on your sd that you can restore at this point. (Please note that using this method may increase your flash counter, but that can easily be fixed with Triangle Away).
Hope this helps.
If its just hanging at the samsung logo..pull the battery, put it back in, boot into stock recovery ( vol up+home+power) wipe data/factory reset then reboot.
After that just download one f the one click rooted stock rogers roms. Odin it, Then use the S3 toolkit to flash a recovery only.
Should be goo to go from there
I am flashing the pre-rooted stock ROM's via Odin again, and then will try and flash CMW Recovery again but without the Auto-Reboot selected.
I was pretty certain I was holding the keys long enough previously to try and get back into Recovery but it never would actually go into CWM Recovery.
Will let you guys know how it goes, thanks for replying.
skrambled said:
You're soft bricked, don't panic just yet. A hard brick is when the device is completely unresponsive. So far this sounds fixable.
To get into recovery, are you holding down the volume up + home key for long enough after the Samsung logo appears?
I'd try that again, but if not: Try to Odin CWM again but uncheck "Auto-Reboot" in Odin. After it's done flashing, pull the battery out, put it back in, and use the key combos to get into recovery. Hopefully you have a nandroid backup saved or another rom saved on your sd that you can restore at this point. (Please note that using this method may increase your flash counter, but that can easily be fixed with Triangle Away).
Hope this helps.
Click to expand...
Click to collapse
Just tried this.
Flashed the pre-rooted stock ROM, it went to Pass in in Odin, device never booted past the boot screen. Pulled out battery, re-inserted and then flashed CWM Recovery in Odin with Auto-Reboot turned off, that went fine to Pass, pulled battery and did the key combo to enter Recovery. I got the "Booting Recovery" in top left corner in blue for a second, held onto the key combo and nothing, just went back into the same Samsung boot screen and it's stuck there.
Sianspheric said:
Just tried this.
Flashed the pre-rooted stock ROM, it went to Pass in in Odin, device never booted past the boot screen. Pulled out battery, re-inserted and then flashed CWM Recovery in Odin with Auto-Reboot turned off, that went fine to Pass, pulled battery and did the key combo to enter Recovery. I got the "Booting Recovery" in top left corner in blue for a second, held onto the key combo and nothing, just went back into the same Samsung boot screen and it's stuck there.
Click to expand...
Click to collapse
Hmmmm...one more thing to try. Re-download the stock firmware image in the unlikely event that you got a bad/corrupted download (also may want to try the version that doesn't have root injected). Then try again.
I'd say to try a different USB port on your pc, but since Odin is saying Pass that doesn't seem likely. Worth a shot though if the above fails (and also worth trying to Odin from a different computer).
Hang in there, you aren't hard-bricked yet! :fingers-crossed:
It has to rebuild cache everytime you flash, if you are clearing things correctly. This can take up to 10 minutes. Also, when the first samsung logo appears take finger off power button and hold the home and appropriate volume button.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
The Q3 Toolbox kit saved me.
I couldn't flash into Recovery (not CWM Recovery, stock Recovery) no matter how long I held the key combo
But I eventually managed to get into Stock Recovery using the Q3 Toolbox.
Thanks for the advice people.
Holy shiiit that was nerve wracking for a while.
Hi everyone
I've tried every thing : tool kit 3 => several version of recovery : CWM, TWRP, installed with Odin (Pass/ RESET : ok). But i'm still boot my recovery to "android system recovery 3e" (cf pic), I can't reach CWM or TWRP : //
I pull off bettery, but till the same way.
Anyone can help me ? Thank's
-----------------------------------
I'm using Galaxy Note 2 GT N7100
4.1.2
Revert back to recovery problem
hazzel said:
Hi everyone
I've tried every thing : tool kit 3 => several version of recovery : CWM, TWRP, installed with Odin (Pass/ RESET : ok). But i'm still boot my recovery to "android system recovery 3e" (cf pic), I can't reach CWM or TWRP : //
I pull off bettery, but till the same way.
Anyone can help me ? Thank's
-----------------------------------
I'm using Galaxy Note 2 GT N7100
4.1.2
Click to expand...
Click to collapse
Having same issue with SGH-T889. Any help? Heard of similar issue with Nexus 4. They have revert recovery disabler. Not tried on my Note 2. Is similar solution available for T889?
After flashing recovery in Odin are you booting up the phone (or is odin - i.e. auto reboot is checked)? There is a file (/system/etc/install-recovery.sh) that you need to disable to have recovery "stick". There are a few ways to do this, but my preference has been to do it within cwm/twrp recovery via adb after flashing in odin but prior to first bootup of phone.
Hope that helps!
Ive had luck un-checking auto-reboot in odin, flashing recovery, wait for it to say pass, unplug USB, pull battery, and boot straight into recovery by holding home + vol up when powering on.
This can be dangerous so make sure odin is completely done before unplugging.
Sent from my GT-N7105 using Tapatalk 2
^^ this
same prob
hazzel said:
Hi everyone
I've tried every thing : tool kit 3 => several version of recovery : CWM, TWRP, installed with Odin (Pass/ RESET : ok). But i'm still boot my recovery to "android system recovery 3e" (cf pic), I can't reach CWM or TWRP : //
I pull off bettery, but till the same way.
-----------------------------------
I'm using Galaxy Note 2 GT N7100
4.1.2
Click to expand...
Click to collapse
I have the same problem :/ i tried going back to odin and unchecking auto root as suggested, but whenever i clicked start it just stayed stuck at "Setup Connection" or whatever... i'm trying to install a custom rom and i just cant access CMW! I have the AT&T model by the way.
Nintendoassasin64 said:
I have the same problem :/ i tried going back to odin and unchecking auto root as suggested, but whenever i clicked start it just stayed stuck at "Setup Connection" or whatever... i'm trying to install a custom rom and i just cant access CMW! I have the AT&T model by the way.
Click to expand...
Click to collapse
I know you can't access CWM Recovery..
Allot of us use TWRP Recovery and it works great. I think it is safe to say it is a Superior Recovery now. I suggest you use that Recovery.
You can get it installed easily by downloading GooManager from the play store, opening the app, hit your menu button and tap Install Open Recovery Script. That's it. Quick and easy!
For the people having a hard time, are you rooted? If you are just download goomanager and use it to install twrp
Sent from my SGH-T889 using xda app-developers app
Finally got fixed
I tried by un ticking the "Reboot" in Odni and manually pulled out battery and cable and tried Recovery mode... it went smoothly as expected... thanks dude
This works when everything else fails!
dj_spore said:
Ive had luck un-checking auto-reboot in odin, flashing recovery, wait for it to say pass, unplug USB, pull battery, and boot straight into recovery by holding home + vol up when powering on.
This can be dangerous so make sure odin is completely done before unplugging.
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
Been looking for a solution for hours and the android system recovery was feeling like a thorn in the foot that will never go away. But surprise, surprise, your simple suggestion did the trick!
Thanks a ton!! :good:
Hi, I've managed to use Odin to install the bell with root image, phone now working with I747MVLUEMK5..downloaded clockworkmod recovery manager and used the att recovery image. Downloaded custom Roms, factory reset the phone, wiped cache and dalvik then installed the custom ROM. It installed properly but when I reboot, it won't turn on, I have to do the download mode to recover it back using the Odin. Tried different custom ROM and I made sure they are for this image MVLUEMK5... But same result, it won't boot up... Help...did I miss a step?
Copy a ROM to your SD card, install a custom recovery (I prefer CWM), boot into recovery, wipe cache, Dalvik, data, and system, install the custom ROM, reboot the phone.
Every 4.4.2 ROM I have tried (Valudus, Cyanfox, CM11) will boot with a stock 4.1.2 bootloader or newer so you should be fine.
Do you have any warranty left on your phone? Does your phone have Knox installed?
audit13 said:
Copy a ROM to your SD card, install a custom recovery (I prefer CWM), boot into recovery, wipe cache, Dalvik, data, and system, install the custom ROM, reboot the phone.
Every 4.4.2 ROM I have tried (Valudus, Cyanfox, CM11) will boot with a stock 4.1.2 bootloader or newer so you should be fine.
Do you have any warranty left on your phone? Does your phone have Knox installed?
Click to expand...
Click to collapse
Here’s the Steps I went through:
*
I have a Bell S3 with 4.3 JB from OTA
*
1.******Downloaded Odin to my PC
2.******Downloaded the image from* 66 CF Root….
3.******Loaded it to my phone (Using Odin)
4.******Made sure the phone is rooted after and it is
5.******Downloaded CWM Manager from Playstore
6.******Changed the Recovery image using the Manager to Samsung Galaxy S3 for AT&T (d2att)
7.******Downloaded Omni Rom then moved it to the SD card using My File app
8.******Rebooted to Recovery
9.******Backed up my phone
10.***Did a Factory reset
11.***Did a Wipe Cache
12.***Did a Wipe Davlik
13.***Flashed the Rom with no error
14.***Rebooted to System
15.***Samsung Logo showed up for a sec then the phone is dead
16.***Tried to turn it on by pressing the power button but not working, I thought the battery was drained when I rebooted, I plugged it in for half an hour but still not turning on. Was able to press the power_
17.***Vol down and home and it booted to Download mode
18.***Used Odin to load the image frok step 2 above and tried the same steps using different rom (Beanstalk-4.4) and the result is the same
Too much work for me. There is no need to have root before installing a custom ROM.
Do this:
Use Odin to install Philz Touch Recovery from here (use the tar version in PDA, do not check auto reboot): http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
Once it flashes and you see Reset in the windows, pull the battery, disconnect the phone from computer, boot into recovery, wipe cache, dalvik, system, data, flash rom, reboot.
Thanks for the help...I'll try this tonight...when you say pull the battery, you mean literally take the battery out of the phone? Would it boot to recovery when I put the battery back? or will it normally boot then I would reboot to recovery.
Thanks!
snyph3r said:
Thanks for the help...I'll try this tonight...when you say pull the battery, you mean literally take the battery out of the phone? Would it boot to recovery when I put the battery back? or will it normally boot then I would reboot to recovery.
Thanks!
Click to expand...
Click to collapse
Yes, remove the battery. Disconnect the USB cable, replace the battery, press volume +, home, and power to get into recovery. Wipe cache, Dalvik, system, data, and flash your custom ROM.
audit13 said:
Yes, remove the battery. Disconnect the USB cable, replace the battery, press volume +, home, and power to get into recovery. Wipe cache, Dalvik, system, data, and flash your custom ROM.
Click to expand...
Click to collapse
Okay, installed Philz recovery using Odin, pulled bttery, unplug usb then boot to recovery...Philz recovery booted, was able to set to factory, wipe cache,dalvik and flash beanstalk rom,...rebooted the system and still shows samsung logo for a sec and phone turned off....I was still able to go back to phils recovery and tried a different rom and it did the same...just not booting up after flashing...
One thing I noticed is when flashing the rom it doesnt take long (less than 2 minutes) then it completed withoiut error....could it be the zip file or the SD card where i copied them?
snyph3r said:
Okay, installed Philz recovery using Odin, pulled bttery, unplug usb then boot to recovery...Philz recovery booted, was able to set to factory, wipe cache,dalvik and flash beanstalk rom,...rebooted the system and still shows samsung logo for a sec and phone turned off....I was still able to go back to phils recovery and tried a different rom and it did the same...just not booting up after flashing...
One thing I noticed is when flashing the rom it doesnt take long (less than 2 minutes) then it completed withoiut error....could it be the zip file or the SD card where i copied them?
Click to expand...
Click to collapse
Most of the 4.3 roms take a long time at the first boot once you flash it (when I flashed S3Rx it took 3 minutes 32 seconds, I timed it because most people say I waited a long time but have no recollection of how much time) it will stay at one of the boot image screens for several minutes then it should vibrate once the blue led should illuminate and then it will finish booting.
If the wait is too much for you turn it on, set it down, walk away, find something to do, 10 minutes later come back, if it hasn't booted now make sure you followed all the instructions correctly and flashed the right stuff for the phone model you have.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
---------- Post added at 06:09 AM ---------- Previous post was at 06:06 AM ----------
To make sure we are on the same page, is it just stuck at a boot screen or is it getting to a screen turning off and going back to the same screen repeatedly?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
snyph3r said:
Okay, installed Philz recovery using Odin, pulled bttery, unplug usb then boot to recovery...Philz recovery booted, was able to set to factory, wipe cache,dalvik and flash beanstalk rom,...rebooted the system and still shows samsung logo for a sec and phone turned off....I was still able to go back to phils recovery and tried a different rom and it did the same...just not booting up after flashing...
One thing I noticed is when flashing the rom it doesnt take long (less than 2 minutes) then it completed withoiut error....could it be the zip file or the SD card where i copied them?
Click to expand...
Click to collapse
Try a different ROM. I use validus and it installed without a problem.
audit13 said:
Try a different ROM. I use validus and it installed without a problem.
Click to expand...
Click to collapse
I was able to flash Validus and And Candykat but could not flash Omni and Beanstalk....flashes with no error but just wont boot up...
I quickly checked the difference between validus/candy Kat vs omni/beanstalk...I looked at the updater-script and found that both validus and candykat doesn't have "assert((getprop...." lines in the beginning of the script, they start at mount ("ext4","EMMC.... line...I wonder if I take the assert lines on the Omni and Beanstalk updater-script if it is going to work..
snyph3r said:
I quickly checked the difference between validus/candy Kat vs omni/beanstalk...I looked at the updater-script and found that both validus and candykat doesn't have "assert((getprop...." lines in the beginning of the script, they start at mount ("ext4","EMMC.... line...I wonder if I take the assert lines on the Omni and Beanstalk updater-script if it is going to work..
Click to expand...
Click to collapse
You can remove the asserts and try, but the phone still may not boot. Any particular reason you want Omni or Beanstalk? I personally prefer Validus.
audit13 said:
You can remove the asserts and try, but the phone still may not boot. Any particular reason you want Omni or Beanstalk? I personally prefer Validus.
Click to expand...
Click to collapse
didn't work without the assert either....just wanted to try different Roms...I'm on Validuz now but having a couple of issues...WiFi is not turning on, have to reboot to turn it on and reboot doesn't work either. It won't turn on unless I pulled the battery which is a pain....
snyph3r said:
didn't work without the assert either....just wanted to try different Roms...I'm on Validuz now but having a couple of issues...WiFi is not turning on, have to reboot to turn it on and reboot doesn't work either. It won't turn on unless I pulled the battery which is a pain....
Click to expand...
Click to collapse
That is strange. I run validus on mine and WiFi is fine. Calls and data ate fine as well.
snyph3r said:
Here’s the Steps I went through:
*
I have a Bell S3 with 4.3 JB from OTA
*
1.******Downloaded Odin to my PC
2.******Downloaded the image from* 66 CF Root….
3.******Loaded it to my phone (Using Odin)
4.******Made sure the phone is rooted after and it is
5.******Downloaded CWM Manager from Playstore
6.******Changed the Recovery image using the Manager to Samsung Galaxy S3 for AT&T (d2att)
7.******Downloaded Omni Rom then moved it to the SD card using My File app
8.******Rebooted to Recovery
9.******Backed up my phone
10.***Did a Factory reset
11.***Did a Wipe Cache
12.***Did a Wipe Davlik
13.***Flashed the Rom with no error
14.***Rebooted to System
15.***Samsung Logo showed up for a sec then the phone is dead
16.***Tried to turn it on by pressing the power button but not working, I thought the battery was drained when I rebooted, I plugged it in for half an hour but still not turning on. Was able to press the power_
17.***Vol down and home and it booted to Download mode
18.***Used Odin to load the image frok step 2 above and tried the same steps using different rom (Beanstalk-4.4) and the result is the same
Click to expand...
Click to collapse
Just curious... are you going into mounts and storage to format system along with the factory reset and dalvik / cache wipes ??
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.
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.