Well, tried to install 4.3 ROM with MK2 firmware and the modem.bin. But somehow every 4.3 or 4.4
ROM out there, I've tried is not resulting in sucess. The odin and recovery installation goes fine. Then I go into twrp and
install the ROM even that goes fine - and eventually the S4 boots and just no calls etc can be done.
I have the backup with 4.2.2 stock ROM (Tmobile, S4 US). I want to just goback tu MDL firmware (and whatever modem file)
using ODIN and try to restore the backup. Is this possible? IF yes, can you guys please point me to right files to do ODIN
and see if twrp recognizes my old backup (that was actually taken using the non-twrp, recovery tool).
Please help!
Or can I make sure twrp recognizes my backup in the external microsd card and restore from there?
Can I use MK2 firmware itself to use 4.2.2. backup?
didadi said:
Well, tried to install 4.3 ROM with MK2 firmware and the modem.bin. But somehow every 4.3 or 4.4
ROM out there, I've tried is not resulting in sucess. The odin and recovery installation goes fine. Then I go into twrp and
install the ROM even that goes fine - and eventually the S4 boots and just no calls etc can be done.
I have the backup with 4.2.2 stock ROM (Tmobile, S4 US). I want to just goback tu MDL firmware (and whatever modem file)
using ODIN and try to restore the backup. Is this possible? IF yes, can you guys please point me to right files to do ODIN
and see if twrp recognizes my old backup (that was actually taken using the non-twrp, recovery tool).
Please help!
Click to expand...
Click to collapse
Have you read my guide yet? http://forum.xda-developers.com/showthread.php?t=2544612
And just a note: Don't post threads like these here in the development section.
Ok,thanks _ will try. Please move this thread to the general q/a section. Sorry.
Also - how can I make twrp to recognize the original backup ? - Or do I need to install the stock recovery using odin again?
Just the sound doesn't come from the phone. (Like calls, can't hear etc).
Does anybody has more insights into this how to fix? - Trying to odin the stock firmware (MDL) and ODIN gets error auth! failed.
Not getting clear instructions to restore my original firmware or nandroid backup from cwm. (I've a backup luckily in the external card).
Does anybody have stock 16GB, S4 Tmobile pit file that can be used for ODIN restore process?:angel:
Related
Greetings Folks,
I know this question has been asked before, and I did read a lot of threads on this topic, but ended up getting confused with terms like ADB shell, root shell, emulator etc . So, here I am, asking for help from you guys. I will try to explain what I am trying to achieve, and hope you will point me in the right direction.
I have a ROOTED GT i9082 (firmware details in screenshot). I have backed up my phone using CWM backup mode (.tar format), and I see that the backup folder contains a lot of different kind of files (like .tar, .img and .tar.a extensions). Please see the attached screenshot for the list. Now, I want to create just one single ODIN flashable file (.tar or .tar.md5) from all these files. The reason for this, is if I decide to try and install some stock not-rooted ROM, and lose the CWM, then restoring back to my old rooted ROM could be a hassle. But if I have a backup ODIN flashable file of my current rooted ROM, then I can straight-away flash my backed-up .tar file from ODIN and restore my phone back to my custom ROM.
I have ODIN and the ADB drivers installed on my laptop, just don't know how to create one single ODIN flashable .tar file from all the various files created by the CWM backup. Any help/advice would be appreciated!!! Cheers!!!
acemccloud1 said:
Greetings Folks,
I know this question has been asked before, and I did read a lot of threads on this topic, but ended up getting confused with terms like ADB shell, root shell, emulator etc . So, here I am, asking for help from you guys. I will try to explain what I am trying to achieve, and hope you will point me in the right direction.
I have a ROOTED GT i9082 (firmware details in screenshot). I have backed up my phone using CWM backup mode (.tar format), and I see that the backup folder contains a lot of different kind of files (like .tar, .img and .tar.a extensions). Please see the attached screenshot for the list. Now, I want to create just one single ODIN flashable file (.tar or .tar.md5) from all these files. The reason for this, is if I decide to try and install some stock not-rooted ROM, and lose the CWM, then restoring back to my old rooted ROM could be a hassle. But if I have a backup ODIN flashable file of my current rooted ROM, then I can straight-away flash my backed-up .tar file from ODIN and restore my phone back to my custom ROM.
I have ODIN and the ADB drivers installed on my laptop, just don't know how to create one single ODIN flashable .tar file from all the various files created by the CWM backup. Any help/advice would be appreciated!!! Cheers!!!
Click to expand...
Click to collapse
If those things confuse you then the more you will get confused if we tell you about LINUX COMMAND LINE.
What I know is that there is nobody yet that can do the things you are asking. There is a tutorial on XDA about extracting files from the tar.md5 ODIN flashable file then "cooking" a custom rom from those files.This can also be done with the files from a NANDROID backup. I do not know of a way to do the reverse of that. That is make an ODIN flashable file from those "modded" files. I am sure there is a way but I think it is beyond the means of us non programmers/developers.
Furthermore, it is easier to restore CWM in case you lose, after that restore any NANDROID backup as long as they are on the external sd card.
If you want to learn try THIS
muntinlupa said:
If those things confuse you then the more you will get confused if we tell you about LINUX COMMAND LINE.
What I know is that there is nobody yet that can do the things you are asking. There is a tutorial on XDA about extracting files from the tar.md5 ODIN flashable file then "cooking" a custom rom from those files.This can also be done with the files from a NANDROID backup. I do not know of a way to do the reverse of that. That is make an ODIN flashable file from those "modded" files. I am sure there is a way but I think it is beyond the means of us non programmers/developers.
Furthermore, it is easier to restore CWM in case you lose, after that restore any NANDROID backup as long as they are on the external sd card.
If you want to learn try THIS
Click to expand...
Click to collapse
Thanks for your response @ muntinlupa
Let me explain what I wish to do, and then maybe you can help me understand this better.
I wish to upgrade my i9082 to 4.2.2, but most of the ROMs available on XDA need me to already be on 4.2.2 leaked ROM. I tried a few of the leaked 4.2.2 which were fine with me being on 4.1.2. After flashing the initial 4.2.2 ROM, I was able to boot up successfully, but after that, when I tried to install Balli's GENNXT XUBMGA 4.2.2 ROM, my phone went into boot loop. So I have decided to try the Samsung official 4.2.2 ROM (released in Germany probably), and then try installing Balli's ROM. But the problem is that the official ROM needs to be flashed via ODIN, and will not be rooted. So I fear that after flashing the official 4.2.2 ROM, I might lose my CWM, thereby rendering my restore ability useless, even though I have my CWM backups for my current ROM (Balli's 4.1.2 rooted ROM).
So, my queries are as follows:-
1) If I flash the official 4.2.2 ROM, will I lose my CWM? If yes, is there any way I can flash and install the CWM again with ODIN, with the official 4.2.2 unrooted ROM still installed?
2) Does flashing CWM via ODIN require root or unlocked bootloader?
3) If I can install CWM with the official 4.2.2 unrooted ROM installed on my phone, will I be able to boot into recovery and restore my backed up rooted Balli's 4.1.2 ROM?
So basically, I want to try the 4.2.2 ROM, but want to be able to revert my phone back to 4.1.2 in case I don't like it.
acemccloud1 said:
Thanks for your response @ muntinlupa
Let me explain what I wish to do, and then maybe you can help me understand this better.
I wish to upgrade my i9082 to 4.2.2, but most of the ROMs available on XDA need me to already be on 4.2.2 leaked ROM. I tried a few of the leaked 4.2.2 which were fine with me being on 4.1.2. After flashing the initial 4.2.2 ROM, I was able to boot up successfully, but after that, when I tried to install Balli's GENNXT XUBMGA 4.2.2 ROM, my phone went into boot loop. So I have decided to try the Samsung official 4.2.2 ROM (released in Germany probably), and then try installing Balli's ROM. But the problem is that the official ROM needs to be flashed via ODIN, and will not be rooted. So I fear that after flashing the official 4.2.2 ROM, I might lose my CWM, thereby rendering my restore ability useless, even though I have my CWM backups for my current ROM (Balli's 4.1.2 rooted ROM).
So, my queries are as follows:-
1) If I flash the official 4.2.2 ROM, will I lose my CWM? If yes, is there any way I can flash and install the CWM again with ODIN, with the official 4.2.2 unrooted ROM still installed?
2) Does flashing CWM via ODIN require root or unlocked bootloader?
3) If I can install CWM with the official 4.2.2 unrooted ROM installed on my phone, will I be able to boot into recovery and restore my backed up rooted Balli's 4.1.2 ROM?
So basically, I want to try the 4.2.2 ROM, but want to be able to revert my phone back to 4.1.2 in case I don't like it.
Click to expand...
Click to collapse
Everything you need to know is HERE. Installing balliboxer rom needs a wipe after flashing or else you will get bootloop.
And I have done this 2 X. I am back to 4.1.2 now because I want to utilize the external2internal app.
And if you wan to get back to nandroid backup of your 4.1.2 then flash any stock 4.1.2 then install CWM and do a restore from CWM. Very easy for me.
Absolutely right @muntinlupa
@acemccloud1
Go easy man...nothing to worry...
First flash leaked or official 4.2.2 through odin..yes u will lose cwm...so flash cwm through odin...same way as u flashed on 4.1.2...boot in to cwm...wipe data factory reset...wipe cache n dalvik cache...now flash GENNXT 4.2.2...after flashing wipe cache n dalvik cache...reboot..
now u r on ballis GENNXT 4.2.2
Now if u want to revert back..(4.1.2 restore)
Flash stock 4.1.2 through odin (necessary as u can't restore ur 4.1.2 backup on 4.2.2)...flash cwm through odin...restore ur 4.1.2 backup with cwm....
Remember...before doing factory reset if ur backup file is in internal sd then just move it on external sd>clockworkmod>backup>ur file...n do not rename ur backup file...u may get md5 mismatch error...happy flashing....:thumbup:
Sent from my GT-I9082 using Tapatalk 2
Thanks @jetvis37 and @muntinlupa :highfive:
I have a better understanding of how to do this now.....I will try it out first thing tomorrow morning....keeping my fingers crossed
Before I get to the point let me explain what happened. I attempted to root my S3. It did work up until I got to the point where I was ready to flash a ROM and it didn't work. I received the "status 7" error on CWM and I receive an error on TWRP that means the same thing. So what I did since I couldn't restore from a backup that I would get bootloops from, I attempted to install a ROM that was .tar or md5.tar through ODIN which only worked for original firmware (given in the screenshot). I have managed to install this ROM on my phone through TWRP but unfortunately it is for TMobile and somehow my AT&T service works on it. Here is a screenshot of the phone. I have tried flashing "aokp_task650_d2lte_kitkat_6.3.2014" that is made for the AT&T S3 but no matter what I try to flash it will not flash. I have already tried doing the "ASSERTS" method but it did not work. Can someone please help me fix this issue??? :/
dreammaster252 said:
Before I get to the point let me explain what happened. I attempted to root my S3. It did work up until I got to the point where I was ready to flash a ROM and it didn't work. I received the "status 7" error on CWM and I receive an error on TWRP that means the same thing. So what I did since I couldn't restore from a backup that I would get bootloops from, I attempted to install a ROM that was .tar or md5.tar through ODIN which only worked for original firmware (given in the screenshot). I have managed to install this ROM on my phone through TWRP but unfortunately it is for TMobile and somehow my AT&T service works on it. Here is a screenshot of the phone. I have tried flashing "aokp_task650_d2lte_kitkat_6.3.2014" that is made for the AT&T S3 but no matter what I try to flash it will not flash. I have already tried doing the "ASSERTS" method but it did not work. Can someone please help me fix this issue??? :/
Click to expand...
Click to collapse
The hybrid firmware thing shouldn't really happen but for some reason, cross flashing between T999 (T-Mobile) & i747 (AT&T) sometimes happens without necessarily causing a brick. I would suggest you do a complete stock restore to AT&T 4.3JB firmware (UCUEMJB). Thereafter, you can go back to flashing your preferred custom ROM. Since you appear to be able to get to TWRP, you can first, from custom recovery, remove all existing firmware including OS and then reinstall the stock firmware. It appears the bootloader is still UCUEMJB so flashing AT&T stock firmware shouldn't be a problem. Please see the thread below for 4.3 stock restore...
http://forum.xda-developers.com/showthread.php?t=2658486
Larry2999 said:
The hybrid firmware thing shouldn't really happen but for some reason, cross flashing between T999 (T-Mobile) & i747 (AT&T) sometimes happens without necessarily causing a brick. I would suggest you do a complete stock restore to AT&T 4.3JB firmware (UCUEMJB). Thereafter, you can go back to flashing your preferred custom ROM. Since you appear to be able to get to TWRP, you can first, from custom recovery, remove all existing firmware including OS and then reinstall the stock firmware. It appears the bootloader is still UCUEMJB so flashing AT&T stock firmware shouldn't be a problem. Please see the thread below for 4.3 stock restore...
http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
So in this case, I just flash everything that it gives me correct? Is the stock ROM still rooted? If it is not then what rooting process do you suggest I go through? If it is a rooted ROM. Then do you recommend I unroot it and root it again or take some other alternative method? I really appreciate your help
dreammaster252 said:
So in this case, I just flash everything that it gives me correct? Is the stock ROM still rooted? If it is not then what rooting process do you suggest I go through? If it is a rooted ROM. Then do you recommend I unroot it and root it again or take some other alternative method? I really appreciate your help
Click to expand...
Click to collapse
It's a complete stock image which will take you to as near factory condition as you can get. This means it is unrooted. You would need to re-root after (successful) firmware installation. Prior to flashing the firmware, please remember to use custom recovery to remove all existing firmware including OS. Once you've restored the firmware, there are several ways to root but my preferred method is SafeRoot. You can find the download links and instructions to SafeRoot in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2565758
You can also try Option 2 in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2538991
Larry2999 said:
It's a complete stock image which will take you to as near factory condition as you can get. This means it is unrooted. You would need to re-root after (successful) firmware installation. Prior to flashing the firmware, please remember to use custom recovery to remove all existing firmware including OS. Once you've restored the firmware, there are several ways to root but my preferred method is SafeRoot. You can find the download links and instructions to SafeRoot in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2565758
You can also try Option 2 in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2538991
Click to expand...
Click to collapse
I am running 4.4.2 on my S3 (AOKP Task650) but unfortunately I am receiving some battery drain. Is there a Kernel I could use to prevent this and save more battery? Which Kernel do you recommend most? Also I am having issues with my Data. I get "E" for edge in a 4G LTE area? Is there a radio that I can flash or APN for this to fix that problem?
dreammaster252 said:
I am running 4.4.2 on my S3 (AOKP Task650) but unfortunately I am receiving some battery drain. Is there a Kernel I could use to prevent this and save more battery? Which Kernel do you recommend most? Also I am having issues with my Data. I get "E" for edge in a 4G LTE area? Is there a radio that I can flash or APN for this to fix that problem?
Click to expand...
Click to collapse
just to confirm, you re on ucuemjb bootloader, and installed/running Task650 4.4.4 rom 7.21.2014 (at this writing thats the latest update for the rom)
right?
sorry last time i tried to flash task650 rom, i got errors concerning the bootloader, went back to CM11 which has been my go-to-go rom and everything works fine, after you respond i will flash and get back to you on the network issues
thanks
Hey guys,
I was running Cyanogenmod 11 for a while which I installed using the automatic tool online. During the summer I flashed Dirty Unicorns but I have issues with the camera and random rebooting. I just got a Galaxy Gear for Christmas and I've read that its only compatible with touchwiz roms.
I'm trying to go back to stock and I am ok with losing my root access.
I have an SGH-1747m on Baseband I747MVLUEMK5 and my service provider is Bell. The android version is 4.4.4 currently. Whats the easiest method to do this? I've read some concerning information that going back to an earlier version of android will soft brick your phone, but I believe the most current Bell firmware is still in Jelly Bean.
Is it as easy as downloading the correct firmware and flashing it using Clockworkmod Recovery?
Thanks
You should download the stock ROM from sammobile.com and flash it in Odin to get back to stock.
audit13 said:
You should download the stock ROM from sammobile.com and flash it in Odin to get back to stock.
Click to expand...
Click to collapse
The latest version available for my baseband is 4.3. Will I run into problems going from 4.4.4 to 4.3?
Flashing in Odin will flash everything, including the bootloader and modem.
audit13 said:
Flashing in Odin will flash everything, including the bootloader and modem.
Click to expand...
Click to collapse
Thanks. So if I'm understanding correctly I just flash the latest firmware released by my carrier (4.4.2)? Is there anything else to watch out for when choosing the firmware?
Also, before flashing should I make a backup with Clockwork Recovery or any other program? Will Clockwork Recovery still be present after flashing with ODIN?
ZombieLee said:
Thanks. So if I'm understanding correctly I just flash the latest firmware released by my carrier (4.4.2)? Is there anything else to watch out for when choosing the firmware?
Also, before flashing should I make a backup with Clockwork Recovery or any other program? Will Clockwork Recovery still be present after flashing with ODIN?
Click to expand...
Click to collapse
Yes, flash the latest firmware for your phone. Be sure it's firmware for the i747m and not anything else. Always make a backup if you ever screw up or want to go back to where you are now. You will lose everything by flashing the stock firmware with ODIN, even clockwork mod recovery.
Thanks. When I made a backup before going to Dirty Unicorns I used Clockwork Recovery. If Clockwork will be deleted by flashing with ODIN, how would I utilize that backup if I needed it? Should I use another program to back up?
EDIT: I flashed it and everything went smoothly. Sincere thanks to everyone who gave me help!
I was on CM 12.1 and I want to go back to completely stock Note 4, as if I purchased my device from the Sprint Store!
I went to download Odin and the stock firmware of Android 5.0.1 for my device, I followed instructions online, and when I press start in Odin, after about 3 seconds it Fails.
Can I not go back to stock Touchwiz 5.0.1 firmware after being on CM 12.1? I do not have a nandroid backup, and even when I try and access Recovery, it is no longer custom recovery, it is a very simple looking recovery screen, with no option to restore a backup.
What can I do! ): I'm extremely stressed and worried I'm not quite sure what to do.
My phone does go into Download mode just fine and show up in Odin.
Also, my phone actually boots up fine, and works fine, but there is no custom recovery, and Odin is failing when trying to flash the stock firmwares
Down load the latest tar from samsung its in the dev section that will fix your phone with odin
pbedard said:
Down load the latest tar from samsung its in the dev section that will fix your phone with odin
Click to expand...
Click to collapse
Since you're familiar with CM and recent OE1 writes both on TW and CM, can you tell the OP if reactivation lock exists on CM, please? How to disable, if enabled?
He's trying to flash OF5 in Odin but it quickly fails or he's downloading the correct OF5 tar now. Add any suggestions you think he might need when coming from CM12 to stock tar these days.
I suspect the recovery is now stock due to partial flash (if possible), reactivation lock or attempt to root in Odin again.
Thanks in advance.
Sent from my SM-N910P using Tapatalk
Hey everyone. I'm having some troubles with every custom ROM I install on my S3 T-Mobile (d2tmo) so I want to come back to Stock ROM. I've been watching some tutorials, but lot of them are pretty old, and none is for the Galaxy S3.
So, what do I need to do to go back to Stock ROM?
Should I do a full wipe from recovery (TWRP) and then flash stock ROM via Odin?
The custom ROM I flashed is 6.0.1. The phone had 4.3 when I flashed the custom ROM.
Am I right about what I think I should do?
Thanks in advance. :good:
Yep. The firmware you'll use in Odin should be a .tar.md5 file.
Just flash the latest stock rom from sammobile.com using Odin. No need to do anything before flashing the stock ROM.
After flashing the stock ROM, immediately boot into recovery and perform a factory wipe.
audit13 said:
Just flash the latest stock rom from sammobile.com using Odin. No need to do anything before flashing the stock ROM.
After flashing the stock ROM, immediately boot into recovery and perform a factory wipe.
Click to expand...
Click to collapse
tonytien said:
Yep. The firmware you'll use in Odin should be a .tar.md5 file.
Click to expand...
Click to collapse
Thank you very much for answering my questions guys! Everything turned out ok!
But I have a doubt about a little think that I hope you could help me.
Before flashing the stock rom I was planning on backing up my efs folder from the TWRP,version 2.8.70 for my s3 (d2tmo), but when I try to do a backup, there no "EFS Folder" option, however, on my other phone, a Galaxy Note 3 Exynos Variant (International Version) when I try to perform a backup there is a EFS folder option for backing up. It is also a TWRP recovery, and same version. 2.8.7.0. I know the phones are completely different, but, why if I'm using the same custom recovery and same version I can't do a EFS Folder backup from the backup option?
I hope I made myself clear about my question. Sorry for my English BTW, it is not my first language.
Thanks in advance!
Maybe this will help although it requires root: http://forum.xda-developers.com/s6-edge-plus/development/updating-t3210266