S4 Mini issues - Galaxy S 4 Mini Q&A, Help & Troubleshooting

I once tried to "Unroot" my phone by factory restoring it then flashing a stock rom and original firmware through Odin. Flashing the stock rom worked however when I tried to flash the firmware through Odin I got an "ext4 image fail" error. I am now stuck with a phone that does not boot. It is just stuck on a "Connect to Kies for emergency recovery" screen - but my phone is never detected in Kies. I cannot boot into recovery mode: I tried and I get the Samsung logo with the blue "RECOVERY BOOTING" text at the top for a split second, but then the screen goes black and I get this message at the top of the screen:
"image size too large!! W:1000, H:1920
display image fail
SECURE FAIL: KERNEL"
Basically, I had 4.2.2 Jellybean installed but wanted Kitkat (this was much earlier this year) and so I found a method of installing KitKat which also gave root access. Can't remember what I did to install it.
I have now successfully flashed CWM recovery through Odin but I have absolutely no idea what to do next. All the guides I have read talk about installing something through an SD card via the recovery menu, which I obviously cannot do because I can't reach the recovery menu.
Anyone know the steps to take?

SoulWithin said:
I once tried to "Unroot" my phone by factory restoring it then flashing a stock rom and original firmware through Odin. Flashing the stock rom worked however when I tried to flash the firmware through Odin I got an "ext4 image fail" error. I am now stuck with a phone that does not boot. It is just stuck on a "Connect to Kies for emergency recovery" screen - but my phone is never detected in Kies. I cannot boot into recovery mode: I tried and I get the Samsung logo with the blue "RECOVERY BOOTING" text at the top for a split second, but then the screen goes black and I get this message at the top of the screen:
"image size too large!! W:1000, H:1920
display image fail
SECURE FAIL: KERNEL"
Basically, I had 4.2.2 Jellybean installed but wanted Kitkat (this was much earlier this year) and so I found a method of installing KitKat which also gave root access. Can't remember what I did to install it.
I have now successfully flashed CWM recovery through Odin but I have absolutely no idea what to do next. All the guides I have read talk about installing something through an SD card via the recovery menu, which I obviously cannot do because I can't reach the recovery menu.
Anyone know the steps to take?
Click to expand...
Click to collapse
Not quite sure what you mean by flashing rom & firmware as it's the same thing, I guess you mean you flashed multipart rom files as separate items. Or did you flash "extra" files, by which I mean flash a full stock rom plus some duplicates eg csc, bootloader etc at the same time? Not sure if this would just overwrite or cause issues. Is there a procedure you followed? Eactly what files did you flash?
Anyhow, I think your first problem is that your cwm recovery has not installed properly. CWM is not maintained anymore The first thing I would do is try to flash a stable TWRP for our phone (see ne0zone75's TWRP thread) as this is maintained. If after flashing TWRP you still can only access download mode then you should flash a full stock rom (1 file with 4 files inside) as others have done to solve "image size too large" problem (try different Odin version if fails). If you can boot into recovery thin you can flash a zip file (though I think it would be a good idea to flash a full stock rom so you at least starting with a known configuration , then flash a custom rom or root it)

Related

[Q] Can't flash any ROM via Odin or TWRP

My non-rooted GT-N7100 didn't want to boot after a longer period without battery charge. After fully charging, i got this screen: dropbox dot com/s/jy8sirmpgp6zm7h/20140823_214100.jpg
Later, i got the "firmware upgrade encountered an issue"-message. I tried to flash the latest stock ROM (via ODIN, from sammobile, checked MD5) but I get a fail when writing system.img.
So I decided to flash a custom recovery (twrp v2.8.0.1) (and trip knox..) to flash via an OTG-cable, but this also doesn't work.
TWRP tells me there is "no OS installed" when trying to reboot.
What am I doing wrong?
Wensjong said:
My non-rooted GT-N7100 didn't want to boot after a longer period without battery charge. After fully charging, i got this screen: dropbox dot com/s/jy8sirmpgp6zm7h/20140823_214100.jpg
Later, i got the "firmware upgrade encountered an issue"-message. I tried to flash the latest stock ROM (via ODIN, from sammobile, checked MD5) but I get a fail when writing system.img.
So I decided to flash a custom recovery (twrp v2.8.0.1) (and trip knox..) to flash via an OTG-cable, but this also doesn't work.
TWRP tells me there is "no OS installed" when trying to reboot.
What am I doing wrong?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1922461
try the steps under "3. Odin Instructions for the Samsung Galaxy S III "based" devices".
TWRP recovery should not be an issue if you rooted your phone before installing it. But, if you somehow have messed it up, try getting the firmware from Sammobile and flash it using odin. That should also replace your recovery to stock.
Hope this helps.
Cheers
I can flash a bootloader, recovery, pit-file, .. I'm using the right cable/drivers/.. It's just impossible to flash system.img to that partition. Twrp/philz/cwmrecovery give me an error when trying to wipe. Is it possible that that partition is corrupt?
I've tried a few stock roms and different custom/pre-rooted roms. None are flashable via odin (1.85, 3.07, 3.09), via adb sideload or USB-stick. I can't mount micro SD cards.
The phone was 4.3 when problems started; does anyone know where i can find the latest universal 4.3 stock rom? Sammobile only shows 4.4 and up..
Bricked?
Try twrp 2.7.2.1. and see if it works.

note 3 cannot start odin success

Odin success on each version NB4,NE6 and OB6
Everything goes through smoothly, but it gets stuck on "rebooting to recovery" and never actually gets to recovery
I've flashed twrp,stock recovery img,chainfire, phils, none will actually boot
got this device from a person who said they tried to flash a custom rom and got it into this boot
all I can think of is to repartition the device, but cannot find a pit file that works
odin mode says write protection: enabled
if that is of importance
also tried the unbrick images on sd card, no luck
is there a way to make a bootable recovery.img sdcard? like how nooks can
made a pit from a working note 3 tmo, repartitioned, no go
What you are saying is that you odin successful, and it will not go into recovery, even if you force it to? After the rom image flash, are you in download mode and trying to flash a working recovery?
AxAtAx said:
What you are saying is that you odin successful, and it will not go into recovery, even if you force it to? After the rom image flash, are you in download mode and trying to flash a working recovery?
Click to expand...
Click to collapse
yes odin completely finishes, I tried forcing into recovery mode
loaded twrp,philz recovery, cwm, older versions of recovery, the current version etc.
no longer have the phone but still wonder why it was a no go

Boot Loop - Please help!

Tmobile Galaxy S4 (SGH-M919) Non-rooted
Problem:
The phone was working and then suddenly went into boot loop. The Samsung screen displays and right before it would goto the animation screen, it loops. I can get to download mode and the recovery OS.
What I've tried:
- First thought it was power button, sent it away to replace button but tech says it's not power button. The phone doesn't turn itself on when the battery is inserted. I can use the power button to turn on/off the phone fine.
- Cache wipe
- Factory reset
- Kies update/recovery
- Burn different firmware version (NB4, NH7, NK2, OH3)
- Tried just to burn NB4 twice consecutively without reboot (first time OK. when burn second time w/o reboot, the phone would display error saying the percentage completed is incorrect since it just finished 100%. Odin continues to burn to finish fine.)
Nothing seems to work. It still loops.
I am desperate. Please help! Thanks in advance.
Beocop
An update:
I tried CF Root and was able to get past he first Samsung screen, past the white TMobile screen, but it went back to boot loop again. Don't know what else to do. Any suggestions?
By burn do you mean you odin'd official stock rom? You cannot downgrade after 4.2.2 MDL so if you flashed OH3 then NB4 will not work anymore...just flash oh3 and root it. For root you can either flash recovery through odin then fash supersuBETA via recovery. Or (if you dont have a computer near you) use kingroot then push recovery through terminal emulator, then run remove kingroot app (google it) then flash supersu through recovery. Link to supersubeta: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
lordodin912 said:
By burn do you mean you odin'd official stock rom? You cannot downgrade after 4.2.2 MDL so if you flashed OH3 then NB4 will not work anymore...just flash oh3 and root it. For root you can either flash recovery through odin then fash supersuBETA via recovery. Or (if you dont have a computer near you) use kingroot then push recovery through terminal emulator, then run remove kingroot app (google it) then flash supersu through recovery. Link to supersubeta: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
I've tried flashing OH3 (twice) also. It still boot loops. Then I tried CF Root to see if it does anything. It flashes fine with no problem. It still boot loops.
I can get into download mode and recovery without problem. It just won't let me past the boot loop.
Try different versions of odin/usb cables and reflash. Or and this voids WARRANTY. Put TRWP on your phone and try a different kernel or OS.
lordodin912 said:
Try different versions of odin/usb cables and reflash. Or and this voids WARRANTY. Put TRWP on your phone and try a different kernel or OS.
Click to expand...
Click to collapse
update:
- I've tried different odin versions (3.07,3.09,3.10). I've tried different USB cables. There was no indication on any error during the flashing process.
- I can flash any stock ROM after NB4 (anything before NB4 => Odin fail). After flashing stock ROMS, it can never get past the Galaxy S4 screen. It just boot loop.
**** I tried to download the OH3 stock rom from Sammobile but I always get a corrupt file error in Winrar. Can someone verify if the OH3 ROM on Sammobile is error free?
- I've tried TWRP (2.6.0.0, 2.6.3.1, 2.8.4.0). I've used it to flash CM-12.1 and Darthstalker_S4_V3 ROMs.
- After flashing all the custom CM ROM, it got stuck with the pink screen.
- I get nothing from Darthstalker ROM, just blank.
I am so frustrated with this process. It seems that I am doing something wrong in my process to flash the ROMs. I am missing something.
Can you please list ALL the steps necessary to properly flash a ROM? Please list every single step that you would personally take, no matter how insignificant (remove battery, clear cache, settings, etc.). Just treat me like a 1st grader.
Thanks so much.
Another update...
- So far, I've tried to flash stock ROMS (NB4-OH3) with odin. None of the stock ROMs will boot fully. All stuck at Samsung logo and bootloops from there.
- The best, but not fully functional, solution I've found so far is from:
1- Flash stock rom NH7 (tried NB4,NH7 so far) with odin
2- Flash CF auto root (CF-Auto-Root-jfltetmo-jfltetmo-sghm919.tar.md5) with odin
3- Flash CWM for recovery
4- boot into recovery, from CWM, install cm-11-20140110-SNAPSHOT-InstallerXNPQ02R-jfltetmo-signed.zip from sdcard1
5- From CWM, install gapps kk for 4.4.3 from sdcard1
6- Clear dalvik, format data + cache
It'll boot up fine. However, I get no sound (not from speaker or headphone). Google keyboard keeping turn on and off. The camera doesn't work. Video's cannot be played.
info "about phone":
Model: SGH-M919
Android version: 4.4.2
Baseband version: M9191UVUFNH7 (prob from CF auto root ?)
Kernel version: 3.4.0 cyanogenmod
Cyanogenmod version: 11.0-installer-XNPQ02R
Build date: 1/9/14
Build number: cm_jftetmo-userdebug4.4.2 KOT49H-installerXNPQ02R release-keys
Don't know what to do now. I've no idea why it won't take stock ROMs. I don't know why I am having problems in cyanogenmod. I freakin hate working on these phones.
Any ideas? suggestions? PLEASE!
Flash philz cwm touch recovery with your current recovery. Then use philz recovery to flash this rom: http://forum.xda-developers.com/galaxy-s4-tmobile/development/moving-please-post-t3009561.
Vicious89 said:
Flash philz cwm touch recovery with your current recovery. Then use philz recovery to flash this rom: http://forum.xda-developers.com/galaxy-s4-tmobile/development/moving-please-post-t3009561.
Click to expand...
Click to collapse
Update:
-OK. I tried using philz cwm and burned this ROM but went through the installation process and picking choices. However, it wouldn't even boot.
-I decided to open up the phone to verify I had a SGH-M919. The sticker underneath the battery indicated SGH-M919. The phone has been using and updating OTA with T-Mobile firmware, the latest being OH3 with stagefright fix.
-After I removed the motherboard, what I saw underneath was disturbing. There was one big stamping showing "I337", which is AT&T. Many other stampings on the chips also show I337.
-In download mode, the product name indicated "SGH-M919".
So the question is, do I have a I337 or M919 phone? Currently, I cannot flash or install any firmware that is not for M919. I tried flashing ATT stock rom (I337ATTFNB1) with odin but it failed, indicating many errors such as PIT. I tried installing CM 11 for ATT but it also failed indicating that I need jfltetmo (M919) version. Ever since the bootloop problem, I cannot get the phone to boot with stock M919 roms.

Cannot install CWM/TWRP

I have a Samsung Galaxy Note 3 with Android 5.0 (Lollipop) and Rooted.
I've been trying to flash CWM and also TWRP without success.
I've used all sorts of methods, Odin, ROM Manager, Nandroid Mgr, Flashify, ADB, ... with the same results:
The flashing always seems to be successful but when rebooting into the custom recovery mode, the custom interface doesn't appear but instead, the system tries to boot into what it appears to be the stock recovery's three first colored text lines for a few seconds and it reboots into a loop until I remove the battery.
Then the only way to get back to the system is boot in download mode, flash either CWM or TWRP with Odin (although I know they won't actually work) and it then reboots into system.
Then I restore a backup of the stock recovery that I luckily made with Flashify and at least the stock recovery works.
(BTW, when the stock recovery has been restored, if I go to ROM Manager both CWM and TWRP are listed as "Already Installed" ... I thought that when you flash the stock recovery, any previous custom recovery is removed )
Any help would be appreciated

{GUIDE} - fix for being stuck at samsung boot screen due to rollback protection

Hi all I have been tinkering away and destrying my setup left right and centre to sort this process out but if you're unable to run the latest TWRP for your note from Ian and get stuck at SAMSUNG screen on boot then this process will fix that if followed correctly. This is due to the device's roll back protection.
This process will reset everything back to current date and get everything working on the new Oneui 2.1 base
Process for getting round SAMSUNG screen issue - please read through first and get the files you need before starting. I did this on my N976B but in theory it should work for other 10-range devices, notes indeed!
UNLESS YOUR RUNNING CRUEL KERNEL OR A SPIN OFF, YOU'LL NEED VOL UP AND POWER TO ACTIVATE MAGISK ON EACH BOOT
Needed:
Stock firnware
Magisk app
Twrp image
Pc and odin also patience and a brain lol
-Return to stock by flashing AP/BL/CP&CSC in odin
-Reboot and confirm oem unlocking greyed out, install magisk app and patch twrp image from Ian, also patch your ap file.
-reboot to download, meanwhile get the magisk_patched.tar and insert TWRP renamed as recovery.img in place of the stock patched recovery (keep this one for later)
-In download mode and with auto reboot off in odin, flash BL, Magisk_patched.tar(with the TWRP from Ian in), CP & HOMECSC.
-When flashing is complete exit download mode and immediately hold power and vol up and hold until on TWRP slider screen. swipe to allow modifications, format internal storage and flash multidisabler.
-Reboot TWRP and backup your current patched stock rom. FLASH THE STOCK PATCHED RECOVERY YOU SAVED EARLIER AND THEN FLASH MULTIDISABLER (THIS IS IMPORTANT AS YOU WILL THEN BE ABLE TO INSTALL TWRP VIA THE APP WITHOUT HAVING TO REFORMAT INTERNAL)
-Reboot straight to stock recovery (reboot from TWRP and hold Vol up and power until in stock recovery) and factory reset then reboot.
-You should now boot up as normal, setup your device, in particular have TWRP app and Magisk set up and running.
-Flash the Unpatched TWRP for your device in the TWRP app - reboot TWRP and check the box to kill that annoying swipe to allow modifications and then you are good to flash whatever rom or kernel you want for your device!
Flash the stock patch recovery as boot??
orbital_71 said:
Flash the stock patch recovery as boot??
Click to expand...
Click to collapse
yes then immediately flash multidisabler before you reboot to set up
i have just helped someone through this on TG so it defo works :good::good::good:
It can also confirm this is working. Just followed this guide on my Note 10+ (N975F with CTD1) and happy flashing now.
drexxie1962 said:
It can also confirm this is working. Just followed this guide on my Note 10+ and happy flashing now.
Click to expand...
Click to collapse
Excellent, thanks for testing!!!!!!!
@askmydas
you may find this useful - follow this to get your sec date reset then follow the process spelt out in the thread of the rom you want to use as you may need a different TWRP depending on what sec date the chef of your chosen rom uses.
Hey, when I get to " FLASH THE STOCK PATCHED RECOVERY YOU SAVED EARLIER" I try to do this and it tells me I don't have enough space. Any ideas?
KiwiNote+ said:
Hey, when I get to " FLASH THE STOCK PATCHED RECOVERY YOU SAVED EARLIER" I try to do this and it tells me I don't have enough space. Any ideas?
Click to expand...
Click to collapse
I worked it out, I was trying to install "recovery.img" to boot partition, "recovery.img" needs to be installed to RECOVERY partition. Silly me. Fixed it now, but have a new issue:
After I flash unpatched twrp image through the app, now my phone will only boot into TWRP. I don't even boot with recovery button presses, but it will still boot into TWRP only. Any ideas?
I know this is an old thread, but it may be that my solution could help someone who is locked on the outside of the device (softbrick)
TD,DR: If you have softbrick and you can't boot the device at all, try flashing via Odin the BL, CP, CSC from a stock rom and the AP of another completely different stock rom.
I had an IMEI 0000 issue on my Galaxy Note 8 (SM-N950F), using Hades Rom (custom), and I needed to install the stock rom. As I was on the F(15) binary, there were only two roms (SamMobile and Stockrom.net) available for my country (Brazil) with this binary:
N950FXXUFDUD6_N950FOXMFDUD6_ZTO
stockrom.net_N950FXXUFDUG5_N950FOXMFDUG4_ZTO
And a via Frija:
SM-N950F_1_20210717024140_0wmgsx8iwf_fac
And no Combination Rom for that binary
After flashing these roms several times, I was always stuck on the “Powered by Google” screen, even doing cache wipe and factory reset through stock recovery several times. So I flashed the N950FOXMFDUD6, flashed the CF-Auto-Root and was able to boot the device. Once inside I noticed that it didn't solve the problem of IMEI 0000. I tried a few more procedures, ended up restarting to install TWRP, and the OEM is closed!!! (OEM OFF, Prenormal). I start getting the message “only official binaries are allowed to be flashed(recovery)”. I flash the stock rom, but it gets stuck on “Powered by Google” again. I tryed to install CF-Auto-Root and I get the message “only official binaries…” I can't log into the device anymore. So after four days of desperation, trying every technique possible, trying to create the Combination Rom by unzipping the AP file from the stock Rom and modifying the files inside, without success, I finally try a procedure I haven't seen anywhere else: I go to the modified Odin: Odin3_v3.14.1_3B_PatcheD, I selected the BL, CP, CSC files from the N950FOXMFDUD6 rom and the AP file from the rom SM-N950F_1_20210717024140_0wmgsx8iwf_fac
And it worked! I can boot the device

Categories

Resources