Develop Bugs

[Q] CM10.2 MK3 build support?

I want to flash CM10.2 on my rooted 4.3 MK3 s3. Is it possible to flash that rom on the phone although Cm10.2 is android 4.2.2?
Thanks!

WoodenDiamond71 said:
I want to flash CM10.2 on my rooted 4.3 MK3 s3. Is it possible to flash that rom on the phone although Cm10.2 is android 4.2.2?
Thanks!
Click to expand...
Click to collapse
As long as the file you download does not downgrade the boot loader. ROM zips will not do this unless otherwise noted. Flashing tar files through ODIN can brick your phone if you downgrade Android version number because tar files reflash every part of the phone, including bootloader.
sent from my GS3

joeyhdownsouth said:
As long as the file you download does not downgrade the boot loader. ROM zips will not do this unless otherwise noted. Flashing tar files through ODIN can brick your phone if you downgrade Android version number because tar files reflash every part of the phone, including bootloader.
sent from my GS3
Click to expand...
Click to collapse
You're correct about the downgrading the bootloader part since i have learned my lesson the first time, but as far as flashing the rom is concerned my recovery will not flash it and i get the broken android as the background and my recovery says the installation was aborted. I am using philz touch recovery 6 btw.

WoodenDiamond71 said:
You're correct about the downgrading the bootloader part since i have learned my lesson the first time, but as far as flashing the rom is concerned my recovery will not flash it and i get the broken android as the background and my recovery says the installation was aborted. I am using philz touch recovery 6 btw.
Click to expand...
Click to collapse
You should be also getting a status 7 error, because the bootloader you currently have (MK3) is not listed as one of the "approved" bootloaders in the updater-script for any 4.3.x ROM based on AOSP. You will need to go into the updater-script and modify one of the lines to match your bootloader, or get rid of the assert lines altogether. Any KitKat 4.4.x ROM's will have your bootloader listed, so this is not necessary for the newest ROM's.

How would I do that? Is there a tutorial I can follow
Sent from my SPH-L710 using Tapatalk

WoodenDiamond71 said:
How would I do that? Is there a tutorial I can follow
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
http://androidforums.com/virgin-mobile-galaxy-s3-all-things-root/791952-all-in-one-guide-modifying-custom-sprint-roms-virgin-mobile-use.html
This is a tutorial I have put together on Android Forums for the rooted Virgin Mobile community (SGS3), since we have to always modify or delete the asserts in order to get Sprint ROM's to flash on our phones. Principle is the same for any Sprint user in your situation. I also just made a YouTube video showing how to do the relevant parts of my tutorial.
https://www.youtube.com/watch?v=IZnYSrUIXKM
Hope this helps! Feel free to PM me if need be for any clarification.

Sweet!! Thanks I'll check it out later once I get out of work. Thanks once again I'll pm if it worked
Sent from my SPH-L710 using Tapatalk

BRICKED... help?

Hey all, I need some help. I bricked my phone, and I can only get into download mode and recovery. Flashing through odin fails each time, and so does flashing through recovery. Gives me a status 7 error. Ive made sure I'm downloading all the proper files, but Im stumped here. My phone also isnt recognized in Kies. Ive uninstalled and reinstalled the drivers multiple times now. Im too nervous to go to an AT&T store because theyll see I voided my warranty from the recovery (using philz recovery).
Anyone got any clue on what Im doing wrong? Any help would be much appreciated.

Syst3m Deadlock said:
Hey all, I need some help. I bricked my phone, and I can only get into download mode and recovery. Flashing through odin fails each time, and so does flashing through recovery. Gives me a status 7 error. Ive made sure I'm downloading all the proper files, but Im stumped here. My phone also isnt recognized in Kies. Ive uninstalled and reinstalled the drivers multiple times now. Im too nervous to go to an AT&T store because theyll see I voided my warranty from the recovery (using philz recovery).
Anyone got any clue on what Im doing wrong? Any help would be much appreciated.
Click to expand...
Click to collapse
EDIT: In your sig, it says you have an S2? this is the S3 section.
What happened exactly to soft-brick?
The software you're flashing with Odin might not be good, try another one. Also, since you can get in recovery, you can try clean flashing the ROM you had running previous to the brick.

BWolf56 said:
EDIT: In your sig, it says you have an S2? this is the S3 section.
What happened exactly to soft-brick?
The software you're flashing with Odin might not be good, try another one. Also, since you can get in recovery, you can try clean flashing the ROM you had running previous to the brick.
Click to expand...
Click to collapse
I have an S3 now, just havent updated my sig.
And I was trying to root. I was on the latest stock 4.4.2 and flashed the wrong file by mistake. Forgot what it was. So now I cant flash any files in recovery or odin. It just fails each and every time. I know all these files cant be bad
So root wasnt successful and now I cant even revert back to stock

Kies interferes with odin. Uninstall it from your computer and try odin again.

DocHoliday77 said:
Kies interferes with odin. Uninstall it from your computer and try odin again.
Click to expand...
Click to collapse
Still didnt work. Odin let me install a recovery file, but it just wont let me install files to restore back to stock. Same with recovery, I'm still getting the status 7 error. It doesnt make any sense. Ive downloaded and redownloaded from different places, so I highly doubt that all these files are bad

Are you running the latest Philz? Sometimes, the status 7 error occurs with an outdated recovery. Have you tried flashing a custom ROM with TWRP?

audit13 said:
Are you running the latest Philz? Sometimes, the status 7 error occurs with an outdated recovery. Have you tried flashing a custom ROM with TWRP?
Click to expand...
Click to collapse
I'm running 6.0.5 - no I haven't tried TWRP

What rom were you running before? What do you want to be running now?
And what is your current firmware/bootloader version? Not sure about philz recovery, but status 7 errors usually occur when you dont have the required firmware build.
Also, at least for the T999, cm roms updater-scripts are outdated. So if we have the newest available, it still gives the status 7 errors because the new builds haven't been added. Just thought I'd mention this in case you're updated to the new kk firmware and are trying to flash a cm rom.

DocHoliday77 said:
What rom were you running before? What do you want to be running now?
And what is your current firmware/bootloader version? Not sure about philz recovery, but status 7 errors usually occur when you dont have the required firmware build.
Also, at least for the T999, cm roms updater-scripts are outdated. So if we have the newest available, it still gives the status 7 errors because the new builds haven't been added. Just thought I'd mention this in case you're updated to the new kk firmware and are trying to flash a cm rom.
Click to expand...
Click to collapse
I was running official 4.4 unrooted. I'm trying to install Likewise S5.

Install terminal emulator from the play store and enter this:
getprop ro.bootloader
If it returns I747UCUEMJB you should be ok to flash likewise and something else is preventing it. If its anyway but that, you probably need to update your base firmware/bootloaders first.
If you're still unable to boot anything, the build should be shown on the Download Mode screen. You can probably reflash your previous rom and boot to that for right now though.

I was able to get a custom ROM installed, but now I have no reception. Im guessing the bootloader needs to be updated. So I tried updating it via odin. That failed. I also tried flashing it in recovery and still got a status 7 error. Im at my whits end here

You probably need to flash your modem. Run the Terminal Emulator command I posted before, and if it returns I747UCUEMJB, flash the MJB modem. If it returns anything else, flash the modem that matches, but let us know first just to be on the safe side.

DocHoliday77 said:
You probably need to flash your modem. Run the Terminal Emulator command I posted before, and if it returns I747UCUEMJB, flash the MJB modem. If it returns anything else, flash the modem that matches, but let us know first just to be on the safe side.
Click to expand...
Click to collapse
Terminal Emulator tells me my bootloader is 1747UCUFNE4

Syst3m Deadlock said:
Terminal Emulator tells me my bootloader is 1747UCUFNE4
Click to expand...
Click to collapse
So yeah, you need the 1747UCUFNE4 baseband. Look in Settings/About Phone to know which one you have before going and flashing it.

BWolf56 said:
So yeah, you need the 1747UCUFNE4 baseband. Look in Settings/About Phone to know which one you have before going and flashing it.
Click to expand...
Click to collapse
I cant seem to find the 1747UCUFNE4 baseband,

Syst3m Deadlock said:
I cant seem to find the 1747UCUFNE4 baseband,
Click to expand...
Click to collapse
Did you check which one you have atm?
And here, from Doc http://forum.xda-developers.com/showpost.php?p=53626873&postcount=4

BWolf56 said:
Did you check which one you have atm?
And here, from Doc http://forum.xda-developers.com/showpost.php?p=53626873&postcount=4
Click to expand...
Click to collapse
Thanks a bunch, it worked!!!

[Q] SGH-I747 Update Issues to 4.4.2

I'm trying to help out a friend and update his Galaxy S3 SGH-I747. He originally had cyanogenmod installed but he restored his phone back to stock and flashed a stock recovery back to the phone. When he tries to do an OTA updated it downloads but fails to install? His current android version is 4.1.1 but his baseband is I747UCUFNE4 which if im not mistaken is for android 4.4.2 what would be the easiest way to get his phone updated to the stock 4.4.2 software?

Follow one of enewman17's how to update threads in General.

4.4.2 upgrade stops at 28%
DocHoliday77 said:
Follow one of enewman17's how to update threads in General.
Click to expand...
Click to collapse
Can you be a bit more specific?
Thanks

bmoliver said:
Can you be a bit more specific?
Thanks
Click to expand...
Click to collapse
The beauty of search: http://forum.xda-developers.com/search.php?searchid=292146343
Two threads from enewman17: UCUEMJB to UCUFNE4 firmware update; How to update SGH-I747 to UCUFNE4_4.4.2

DocHoliday77 said:
Follow one of enewman17's how to update threads in General.
Click to expand...
Click to collapse
BWolf56 said:
The beauty of search: http://forum.xda-developers.com/search.php?searchid=292146343
Two threads from enewman17: UCUEMJB to UCUFNE4 firmware update; How to update SGH-I747 to UCUFNE4_4.4.2
Click to expand...
Click to collapse
Thanks, I had found the last link (....2789917) by doing a Google search (i.e., searching within the forum was less successful).

Hey bmoliver and BWolf56,
I am in the same boat as your friend where my baseband (bootloader) version is I747UCUFNE4 but the software version is stuck at 4.1.1. AT&T is identifying a OTA update, downloading but the update is failing.
I tried the method described in http://forum.xda-developers.com/showthread.php?t=2789917. But when I am trying to flash MJB bootloader, it is failing. I read elsewhere in this forum that downgrading from UCU to MJB is not really advisable.
I am stuck in 4.1.1 and my phone is half functional at the moment with the camera, nfc, bluetooth not functional :crying:.
Was your friend able to get this resolved bmoliver?
I tried searching for a I747UCUFNE4 md5 file that I can flash using odin (just a hope that it might work) but could not find.
It would be great if one of you can point me to it.
PS: I am a complete newbie to this entire thing and so far from what I read, my phone is probably soft-bricked and am hoping that someone would guide and help me get out of this.
EDIT: One more thing that I observed is when I am trying flash something in the download mode, I get the error and "sw rev check fail fused 3 binary 0" and it fails
Thanks,
CJ
bmoliver said:
Thanks, I had found the last link (....2789917) by doing a Google search (i.e., searching within the forum was less successful).
Click to expand...
Click to collapse

jchennuri said:
Hey bmoliver and BWolf56,
I am in the same boat as your friend where my baseband (bootloader) version is I747UCUFNE4 but the software version is stuck at 4.1.1. AT&T is identifying a OTA update, downloading but the update is failing.
I tried the method described in http://forum.xda-developers.com/showthread.php?t=2789917. But when I am trying to flash MJB bootloader, it is failing. I read elsewhere in this forum that downgrading from UCU to MJB is not really advisable.
I am stuck in 4.1.1 and my phone is half functional at the moment with the camera, nfc, bluetooth not functional :crying:.
Was your friend able to get this resolved bmoliver?
I tried searching for a I747UCUFNE4 md5 file that I can flash using odin (just a hope that it might work) but could not find.
It would be great if one of you can point me to it.
PS: I am a complete newbie to this entire thing and so far from what I read, my phone is probably soft-bricked and am hoping that someone would guide and help me get out of this.
Thanks,
CJ
Click to expand...
Click to collapse
You don't want to downgrade bootloaders, that will brick your phone.
You'll have to flash NE4 with Odin (or a NE4 custom ROM through custom recovery) to get your baseband and software matching.
The thread you linked should work if you follow it to a T. If something doesn't work, let us know and be specific about what happened.

Thanks for the info BWolf56,
Sorry for asking a trivial question (just getting accustomed to the lingo used here) .
When you say I should follow it to a T, are you just referring to follow all the steps.
I tried two things
1. follow each step, but failed at step 3 since I was trying to downgrade my bootloader.
2. I jumped from step 2 to step 6 and tried to flash 4.4.2OTA.zip in recovery mode but that also failed. I dont remember the exact error I got, I can try it again to give you more details if you think it is safe.
Thanks
BWolf56 said:
You don't want to downgrade bootloaders, that will brick your phone.
You'll have to flash NE4 with Odin (or a NE4 custom ROM through custom recovery) to get your baseband and software matching.
The thread you linked should work if you follow it to a T. If something doesn't work, let us know and be specific about what happened.
Click to expand...
Click to collapse

jchennuri said:
Thanks for the info BWolf56,
Sorry for asking a trivial question (just getting accustomed to the lingo used here) .
When you say I should follow it to a T, are you just referring to follow all the steps.
I tried two things
1. follow each step, but failed at step 3 since I was trying to downgrade my bootloader.
2. I jumped from step 2 to step 6 and tried to flash 4.4.2OTA.zip in recovery mode but that also failed. I dont remember the exact error I got, I can try it again to give you more details if you think it is safe.
Thanks
Click to expand...
Click to collapse
If you jumped to #6, you didn't flash a custom recovery, which you need to flash the OTA.

I did install TWRP 2.6.3.1 which I am guessing is the custom recovery (as part of step 2) and then I tried to flash the OTA. Am I missing something here?
BWolf56 said:
If you jumped to #6, you didn't flash a custom recovery, which you need to flash the OTA.
Click to expand...
Click to collapse

jchennuri said:
I did install TWRP 2.6.3.1 which I am guessing is the custom recovery (as part of step 2) and then I tried to flash the OTA. Am I missing something here?
Click to expand...
Click to collapse
What error did you get when flashing it?

I just tried flashing it again and got the following error.
I loaded the zip into my internal SD and went to recovery mode (twrp gui, Power+Home+Volume Up)
and tried installing the zip
_______________
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of samsung/d2u (the screen does not allowing me to scroll to the right to look at the complete line after 'd2u')
E: Error executing updater binary in zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Error flashing zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Updating partition details...
FAILED
_________________
This is the error I am getting.
Am I missing something? Please let me know if you need any more info
Thanks a ton!!!
BWolf56 said:
What error did you get when flashing it?
Click to expand...
Click to collapse

jchennuri said:
I just tried flashing it again and got the following error.
I loaded the zip into my internal SD and went to recovery mode (twrp gui, Power+Home+Volume Up)
and tried installing the zip
_______________
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of samsung/d2u (the screen does not allowing me to scroll to the right to look at the complete line after 'd2u')
E: Error executing updater binary in zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Error flashing zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Updating partition details...
FAILED
_________________
This is the error I am getting.
Am I missing something? Please let me know if you need any more info
Thanks a ton!!!
Click to expand...
Click to collapse
Sounds like you'll have to use Odin to flash Stock.
Your build.prop is most likely borked (or has been changed to something it's not). d2u is not a variant of the S3, nor does it exist.

Thanks a ton for helping me identify the problem.
I just have to look if a stock file to flash using odin is out there somewhere.
I will post in http://forum.xda-developers.com/showthread.php?t=2789917 to see if enewman17 or someone from the community have a tar or md5 file that I can use.
I will try that and update on how it goes.
BWolf56 said:
Sounds like you'll have to use Odin to flash Stock.
Your build.prop is most likely borked (or has been changed to something it's not). d2u is not a variant of the S3, nor does it exist.
Click to expand...
Click to collapse

jchennuri said:
Thanks a ton for helping me identify the problem.
I just have to look if a stock file to flash using odin is out there somewhere.
I will post in http://forum.xda-developers.com/showthread.php?t=2789917 to see if enewman17 or someone from the community have a tar or md5 file that I can use.
I will try that and update on how it goes.
Click to expand...
Click to collapse
You can grab the stock ROM here: http://forum.xda-developers.com/showthread.php?p=33570269#post33570269
Just make sure you grab the right version.

Thanks for the pointing me there.
I could not find the stock firmware for NE4 though.
They only have MJ2, LK3, LG1, LEM versions, no MJB either.
BWolf56 said:
You can grab the stock ROM here: http://forum.xda-developers.com/showthread.php?p=33570269#post33570269
Just make sure you grab the right version.
Click to expand...
Click to collapse

jchennuri said:
Thanks for the pointing me there.
I could not find the stock firmware for NE4 though.
They only have MJ2, LK3, LG1, LEM versions, no MJB either.
Click to expand...
Click to collapse
There isn't a NE4 stock for Odin. I just noticed the post hasn't been updated in a while.
I though I could find it on Sammobile.com but they have LK3 as their latest too.

Since you somehow have the 4.4.2 modem, you can not flash anything older than the 4.4.2 firmware. Currently there is nothing that you can flash to fix this. Normally, I would say to flash an older modem, but if Odin is seeing it as already updated to 4.4.2 (SWREV 3), and the only thing you have that is 4.4.2 is the modem, flashing anything older will likely hard brick.
You need either the full stock firmware, which there is not one, Thanks AT&T!, or a recovery flashable firmware for 4.4.2. Enewman17 has this, but it will not work for you because of how the modem is flashed. For some reason, he has it patching the 4.3 modem rather than including the full updated one like with the other partitions. If someone makes the same thing, but with the already updated modem, you could probably flash that. No guarantees though. Running 4.1.1 firmware/bootloaders with a 4.4.2 modem is a scenario which is highly unpredictable, so anything you try to flash might cause more problems, we just don't know.
I've PM'd enewman17 to ask if there was a specific reason he updated the modem the way he did. If there is not an issue doing it like i mentioned someone can try to make a new package like that for you to try.

Thanks Doc!
Hopefully enewman17 can come up with a solution for this.
Just an information which I was not able to completely comprehend but maybe pros like you or Bwolf56 will be able to.
I opened Kies and this is what it says.
Firmware information
This is the latest firmware.
Current firmware version: PDA:LK3 / PHONE:NE4 / CSC:LK3 (ATT)
Any thoughts on how do I get the PDA and CSC updated (not even sure what exactly they are)
Thanks
DocHoliday77 said:
Since you somehow have the 4.4.2 modem, you can not flash anything older than the 4.4.2 firmware. Currently there is nothing that you can flash to fix this. Normally, I would say to flash an older modem, but if Odin is seeing it as already updated to 4.4.2 (SWREV 3), and the only thing you have that is 4.4.2 is the modem, flashing anything older will likely hard brick.
You need either the full stock firmware, which there is not one, Thanks AT&T!, or a recovery flashable firmware for 4.4.2. Enewman17 has this, but it will not work for you because of how the modem is flashed. For some reason, he has it patching the 4.3 modem rather than including the full updated one like with the other partitions. If someone makes the same thing, but with the already updated modem, you could probably flash that. No guarantees though. Running 4.1.1 firmware/bootloaders with a 4.4.2 modem is a scenario which is highly unpredictable, so anything you try to flash might cause more problems, we just don't know.
I've PM'd enewman17 to ask if there was a specific reason he updated the modem the way he did. If there is not an issue doing it like i mentioned someone can try to make a new package like that for you to try.
Click to expand...
Click to collapse

Ok, enewman17 just put this together if you want to try it. This includes the full NE4 stock firmware minus system, kernel, cache and recovery.
So flashing it will preserve your current Rom, kernel and recovery, but will otherwise fully update your base firmware/bootloaders to NE4.
This should be perfectly safe to use, but seeing as it is untested, I cannot make any guarantees that it won't make things worse. (I wouldn't post it if I thought it would, but there is always the possibility)
Flash from custom recovery such as TWRP.
http://www.androidfilehost.com/?fid=23578570567716667
Sent from my SGH-T999 using Tapatalk
---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------
If you want to fully update your system (rom) to stock NE4, enewman17 has a thread in the development section with stock rooms you can flash via recovery after you update your firmware posted above.
Sent from my SGH-T999 using Tapatalk

[Q] Updating Bootloader for CM12?

Trying to flash CM12 Rom and it fails cause it needs 3.19.0.00 Bootloader? I am currently on bootloader 3.16.0.00. Any way to update for this ROM
Sent from my HTC6525LVW using XDA Free mobile app

Update your FW

I'm on 4.4.2 after restoring from being hard bricked. Would 4.4.4 Ota update from Verizon have the new bootloader?

kenferrari13 said:
I'm on 4.4.2 after restoring from being hard bricked. Would 4.4.4 Ota update from Verizon have the new bootloader?
Click to expand...
Click to collapse
Short answer, yes
Long answer, do the research. Learn what you're doing. Open an OTA and have a look inside
And read my signature regarding DMs...

I tried installing a 4.4.4 ota from Verizon and it fails. Does it need stock recovery? I have clockwork on there currently

kenferrari13 said:
I tried installing a 4.4.4 ota from Verizon and it fails. Does it need stock recovery? I have clockwork on there currently
Click to expand...
Click to collapse
Yes. Also, if there is a 4.4.3 OTA for Verizon, you need to install that first before going to 4.4.4.

yes you need the stock recovery. I am having the same issue, although I have CM11 and TWRP and I can not seem to find the telus nandoid or recovery for 3.16

Sorry I meant to say 4.4.3 update and it failed on me.

kenferrari13 said:
I'm on 4.4.2 after restoring from being hard bricked.
Click to expand...
Click to collapse
"Hard brick" or "brick" means you had to open the phone to recovery (JTAG, replace motherboard, etc.). Is this what happened to you?
---------- Post added at 01:26 PM ---------- Previous post was at 01:25 PM ----------
kenferrari13 said:
Sorry I meant to say 4.4.3 update and it failed on me.
Click to expand...
Click to collapse
Failed how? Did it give you an error message about the phone being modified?
You need to be on the stock ROM (no system files altered by root) in order to OTA.

I didn't have to replace any hardware. I guess it was more of a soft brick cause it would show splash screen and then freeze.

Well if I install a 4.4.4 Rom from the forums instead of ota Verizon will it have hboot files included?

kenferrari13 said:
Well if I install a 4.4.4 Rom from the forums instead of ota Verizon will it have hboot files included?
Click to expand...
Click to collapse
Nope. Hboot is not included in a ROM.
But it would be included in a firmware package (s-off required to flash).

I do have s off but when I go to flash an hboot update 3.19.0.00 it starts then says installation aborted in CWM! What gives?

Have a thread for HTC One M8 Verizon HBoot downloads that will flash in Clockwork? Maybe my file is corrupt.

You don't flash FW via CWM, you flash it through fastboot. Have you actually read anything?

Well I have read a ton on this I just don't know my terminology that well. I have been trying to flash hboot.zip which i read can be flashed in cw and it fails. I have also tried fastboot install with platform tools/RUU as well and can't get it. I'll try again tonight and report back. Just trying to learn a little here sorry if I'm not up to your standards EddyOS haha.

Well if you can't even spell my name right there's no hope...If you don't get the terminology then don't even start until you do! I didn't do anything until I learnt what I was doing and how to revert the changes I was making before I first rooted my Desire back in 2010 (and it was a lot more technical back then too!)

Okay bud thanks for that! I was only kidding, learn by doing.

Stock rom for S4 mini GT-I9190

Hi there can anybody give me a link to a flashable zip of the stock frimware. I tried to flash the md5 file through odin and it keeps failing. I tried diffrent versions of odin and on Windows 7 and Windows 10 and still no luck
Will appreciate it thanks.

Billabomb75 said:
Hi there can anybody give me a link to a flashable zip of the stock frimware. I tried to flash the md5 file through odin and it keeps failing. I tried diffrent versions of odin and on Windows 7 and Windows 10 and still no luck
Will appreciate it thanks.
Click to expand...
Click to collapse
I don't know where there is a flasheable zip off hand, but you can make your own, there are several tutorials online, search for something like "Convert stock rom to flashable zip"

IronRoo said:
I don't know where there is a flasheable zip off hand, but you can make your own, there are several tutorials online, search for something like "Convert stock rom to flashable zip"
Click to expand...
Click to collapse
I dont have astock rom anymore

Billabomb75 said:
I dont have astock rom anymore
Click to expand...
Click to collapse
You can get stock rom from sammobile.com
https://www.sammobile.com/firmwares/galaxy-s4-mini/GT-I9190/

Billabomb75 said:
.....through odin and it keeps failing.
Click to expand...
Click to collapse
When you say failing, what do you mean? what is the error that you are getting on the phone?
i ask because i am having similar issues. am currently on lineage 7.1.1 and i found a single post out there that mentioned that when i flashed up to 7.1.1 that it triggered a fuse in the flash memory, that cannot be reversed. The error message i get seems to indicate that this is correct. fused2 > binary 1 - meaning that my handset is fused to 2 but the one i am flashing is only a 1.
i have a fully working phone on 7.1.1 but i want to revert to stock and am unable to do so

mrtim123 said:
When you say failing, what do you mean? what is the error that you are getting on the phone?
i ask because i am having similar issues. am currently on lineage 7.1.1 and i found a single post out there that mentioned that when i flashed up to 7.1.1 that it triggered a fuse in the flash memory, that cannot be reversed. The error message i get seems to indicate that this is correct. fused2 > binary 1 - meaning that my handset is fused to 2 but the one i am flashing is only a 1.
i have a fully working phone on 7.1.1 but i want to revert to stock and am unable to do so
Click to expand...
Click to collapse
I get a system write fail on system.ext4... So now i use the carbon 4.4.4 rom
Want to go back to stock

Billabomb75 said:
I get a system write fail on system.ext4... So now i use the carbon 4.4.4 rom
Want to go back to stock
Click to expand...
Click to collapse
ah right. same wants but different issue by the sound of it.
sorry i cant help!