Related
I'm trying to restore my Acer Iconia A500 back to the stock/ original ROM so that I can grab the official update in July. Is there any way to do that? I really like the custom ROMS, I just want to revert to see what it was like.
Mestiza5683 said:
I'm trying to restore my Acer Iconia A500 back to the stock/ original ROM so that I can grab the official update in July. Is there any way to do that? I really like the custom ROMS, I just want to revert to see what it was like.
Click to expand...
Click to collapse
And, of course you made a backup via clockworkmod???? eh?
Why are so many not making backups of their tabs before installing unknown software?
There's lots of threads about this in the forums with instructions already. And this belongs in the General forum, not development.
Yes I'd also be interested in this. I have the droid x so when ever I want to revert to factory settings theirs a program on the computer (rsd lite) I use to revert it. So I almost never backup my roms. Now on my iconia they don't have such program. At least that I know of. So I flashed a rom on my iconia and didn't make a backup of my current one. I tried fixing it by flashing stock_acer a500.zip I thing by dexter don't quote me on that one. But it was the emea version so now its stock european and I live in america. Help is apreciated.
I'm a flashing person that has flashed many times on my phones. I forgot to make a nandroid backup of my original rom myself...so I'm not judging. I would say, flash honeyvillian, as its the closest thing to stock I've seen.
But, if your already flashing, I wouldn't want to grab the official anything...someone will post it once it comes out.
Sent from my A500 using XDA Premium App
I want to flash it to the latest stock. So when ota 3.1 is released, I could rest assure knowing that my device would get updates ota.
Euclid's Brother said:
And, of course you made a backup via clockworkmod???? eh?
Why are so many not making backups of their tabs before installing unknown software?
There's lots of threads about this in the forums with instructions already. And this belongs in the General forum, not development.
Click to expand...
Click to collapse
because we are impatient and stupid
I am running to get someone with a tablet of my country to get back the STOCK ROM in case of... I am going to see if I can deal with the shop to root and recovery on SD Card the stock rom so I will be able to have the stock rom...
For USA version 1.104.02, Check out this post.. You'll probably want to skip flashing the stock recovery until you know the system will boot normally.. So from this post, run itsmagic, flash boot, flexrom and system, in that order. Preferable from an adb connection. The tablet will freeze while flashing system. Give at least 5 mintues to make sure it's complete.
You may need to do a data wipe if it bootloops (that's why you should skip flashing recovery). Once it's booting normally, you can flash the stock recovery if you want.
Alternatively, you should be able to replace the files in dexter's stock update zip with these files. But I haven't looked at that zip, so I don't know if system is an image file or a archive file.
Thanks for the replies quick question though. How do in run its magic is their a command for ADB or do I acess it via clockwork recovery?
Respawntime said:
Thanks for the replies quick question though. How do in run its magic is their a command for ADB or do I acess it via clockwork recovery?
Click to expand...
Click to collapse
You download it from the itsmagic thread in the development form and follow the directions in that thread.
Euclid's Brother said:
And, of course you made a backup via clockworkmod???? eh?
Why are so many not making backups of their tabs before installing unknown software?
There's lots of threads about this in the forums with instructions already. And this belongs in the General forum, not development.
Click to expand...
Click to collapse
I too would like to restore to the 3.0.1 stock rom, however my backup of the stock rom got corrupted somehow. I know it had to be something I done, but know not what it was I did. Any help would be much appreciated. Or would it be a better idea to flash the 3.1 leak?
I've been trying to update from 4.1.2 to 4.2.2, but I deleted some stock apps and now the update is failing. I've tried flashing it manually and OTA, and various other things, but nothing has helped so far. Has anyone else had this problem?
The OTAs are for use with [size=+2]unmodified[/size] factory ROMs.
bftb0 said:
The OTAs are for use with [size=+2]unmodified[/size] factory ROMs.
Click to expand...
Click to collapse
I figured that out when I tried to update. I can't flash it either, so your post doesn't really help.
wipeout4wh said:
I figured that out when I tried to update. I can't flash it either, so your post doesn't really help.
Click to expand...
Click to collapse
My post tells you that you have the wrong expectation about what OTAs are capable of... and that you are probably the 200'th dude to come in here and say
"Wahhh! The OTA doesn't work on my heavily modified stock ROM!".
If you want it to work without exerting any mental effort, return the /system, boot, and recovery partitions back to 100% pure stock corresponding to whatever release your original ROM was based upon, and run the update. Then re-flash your recovery and re-perform all your /system mods, starting with a flash of the same root kit you started with.
Note that the the update you are contemplating also includes a bootloader update - performed the safest way possible (signature checking performed by the existing boot loader). Doing it the manual way (via fastboot) is quite dangerous, even for experts. If you have a 3g version there is also a radio update which also should not be attempted in any other way than via a pure stock OTA install including use of a stock recovery.
Make a full Nandroid backup before you begin anything - and get a copy of that backup off of the tablet as well as a failsafe measure. If you screw things up moving forward, at least you will be able to start over from where you are right now.
If you have been operating using best practices, you should already have a nandroid backup of the pure-stock /system & boot images. TWRP allows you selectively restore individual partitions. Few users seem to know how to actually make a backup of stock recovery partitions, but you can get that out of oldblue910's archive site - find the link in the OTA thread.
good luck
wipeout4wh said:
I figured that out when I tried to update. I can't flash it either, so your post doesn't really help.
Click to expand...
Click to collapse
He's telling you the plain and simple truth. Want the OTA- as it stands, you're out of luck. Either return to stock and then flash the OTA, or flash the 4.2.2 factory image. That's it. Nothing more. That anyone even bothered to answer this uselessly redundant thread is a miracle in and of itself.
Sent from my Nexus 7 using Tapatalk HD
Hello!
So, I've read through the beginner guides (and that is a hilarious video btw!) and just want to double check a few things. I'm on Fido (Canada) with a stock S4 (i337M) that I got a couple days ago.
1. I assume I use the instructions here: http://forum.xda-developers.com/showthread.php?t=2314494 [HOW-TO] and here http://forum.xda-developers.com/showthread.php?t=2298299 [Canadian Root and Recovery].
1a. That tool will allow me to un-root in case I need the warranty, yes?
2. I also want to flash to vanilla Android (aka Pure Google / Google Edition)... which ROM do I use? There are so many I can't tell.
2a. I know the Samsung camera app doesn't work on the Pure Google ROM, but is basic functionality still working, i.e. can I still take a picture / video / etc.? Is there any other basic functionality missing? (I heard something about the volume button?)
3. Which ROM do I use if I want to restore to factory?
4. I also need to backup my SMS, contacts, call log, app data, settings etc. so I can restore them easily after flashing to new ROM, or after restoring to factory ROM. Will Titanium handle all of this?
Thanks
kabutar said:
Hello!
So, I've read through the beginner guides (and that is a hilarious video btw!) and just want to double check a few things. I'm on Fido (Canada) with a stock S4 (i337M) that I got a couple days ago.
1. I assume I use the instructions here: http://forum.xda-developers.com/showthread.php?t=2314494 [HOW-TO] and here http://forum.xda-developers.com/showthread.php?t=2298299 [Canadian Root and Recovery].
1a. That tool will allow me to un-root in case I need the warranty, yes?
2. I also want to flash to vanilla Android (aka Pure Google / Google Edition)... which ROM do I use? There are so many I can't tell.
2a. I know the Samsung camera app doesn't work on the Pure Google ROM, but is basic functionality still working, i.e. can I still take a picture / video / etc.? Is there any other basic functionality missing? (I heard something about the volume button?)
3. Which ROM do I use if I want to restore to factory?
4. I also need to backup my SMS, contacts, call log, app data, settings etc. so I can restore them easily after flashing to new ROM, or after restoring to factory ROM. Will Titanium handle all of this?
Thanks
Click to expand...
Click to collapse
That guide should be fine. If you want "vanilla Android", right now the closest thing would be CM, you can get it from http://get.cm and select "jfltecan" (the canadian S4 model). Ye,s, Titanium can backup all of those things you mentioned, although I am not certain about system settings - there will be a lot of different settings between TouchWiz and AOSP.
CommentProvider said:
That guide should be fine. If you want "vanilla Android", right now the closest thing would be CM, you can get it from http://get.cm and select "jfltecan" (the canadian S4 model). Ye,s, Titanium can backup all of those things you mentioned, although I am not certain about system settings - there will be a lot of different settings between TouchWiz and AOSP.
Click to expand...
Click to collapse
awesome thanks. I'm not worried about system settings just apps and their settings.
for the factory ROM would this work?: http://forum.xda-developers.com/showthread.php?t=2261573 (again, I'm on Fido in Canada)
and lastly, I'm still not clear on the difference between Odin/Loki/whatever you use to root and/or flash - would someone be able to clarify?
Also, just to be clear, what is meant by 'recovery'?
Thanks again
http://forum.xda-developers.com/showthread.php?p=41989987
Loki
refers to the exploit that allows us to run custom recoveries as well as custom roms. You only need to have a loki'd rom if you have a model with a locked bootloader (AT&T).
recovery is a partition that you can access at boot by holding down a combination of keys. (volume up and home button in the case of our sgs4) every phone has recovery stock but it doesn't do much. you can replace stock with clockwork mod recovery which is extremely useful for flashing all kinds of things and making backups before you do. There are other alternative recoveries besides clockwork but that seems to be the most common. TWRP is also gaining popularity these days. You can easily switch between recoveries and or upgrade your current recovery. All that needs to happen is for a new image to be flashed onto the recovery partition. See the rooting guide for more info on how to flash a custom recovery.
Sent from my SGH-I747
mymusicathome said:
http://forum.xda-developers.com/showthread.php?p=41989987
Loki
refers to the exploit that allows us to run custom recoveries as well as custom roms. You only need to have a loki'd rom if you have a model with a locked bootloader (AT&T).
recovery is a partition that you can access at boot by holding down a combination of keys. (volume up and home button in the case of our sgs4) every phone has recovery stock but it doesn't do much. you can replace stock with clockwork mod recovery which is extremely useful for flashing all kinds of things and making backups before you do. There are other alternative recoveries besides clockwork but that seems to be the most common. TWRP is also gaining popularity these days. You can easily switch between recoveries and or upgrade your current recovery. All that needs to happen is for a new image to be flashed onto the recovery partition. See the rooting guide for more info on how to flash a custom recovery.
Sent from my SGH-I747
Click to expand...
Click to collapse
ok, great, thanks. just to clarify one last time: am I correct in understanding that I don't need to have a custom recovery in order to flash a ROM? or is that what installing clockwork mod/TWRP means? (or is that what rooting means?)
Lastly... is there somewhere with a list of what each custom ROM is, and/or what things don't work in the ROM? I do want vanilla, but I'd also be interested in checking out the other ROMs to see if there's one that will keep some TouchWiz functionality while removing the ridiculous skin.
Also, for vanilla Android, would you recommend waiting till devs release a MOD based off of the S4 GE?
kabutar said:
ok, great, thanks. just to clarify one last time: am I correct in understanding that I don't need to have a custom recovery in order to flash a ROM? or is that what installing clockwork mod/TWRP means? (or is that what rooting means?)
Lastly... is there somewhere with a list of what each custom ROM is, and/or what things don't work in the ROM? I do want vanilla, but I'd also be interested in checking out the other ROMs to see if there's one that will keep some TouchWiz functionality while removing the ridiculous skin.
Also, for vanilla Android, would you recommend waiting till devs release a MOD based off of the S4 GE?
Click to expand...
Click to collapse
Check out the link in my first post. A plethora of knowledge that will help you in your Rom journey.
Play around and test the options of roms you have. Each user has different likes/dislikes. MAKE SURE YOU READ THE ORIGINAL POST OF THE ROM YOU ARE PLANNING ON FLASHING. They will contain the basic inductions to flash the Rom and usually any bugs that exist.
Check out this thread for a list of compatible roms -
http://forum.xda-developers.com/showthread.php?p=41834056
[GUIDE][NOOB'S]These non-AT&T ROMs work on AT&T/TMO/Canadian S4 devices. Here's how!
A quick search can be a beautiful thing
Sent from my Nexus 10 using xda premium
mymusicathome said:
Check out the link in my first post. A plethora of knowledge that will help you in your Rom journey.
Play around and test the options of roms you have. Each user has different likes/dislikes. MAKE SURE YOU READ THE ORIGINAL POST OF THE ROM YOU ARE PLANNING ON FLASHING. They will contain the basic inductions to flash the Rom and usually any bugs that exist.
Check out this thread for a list of compatible roms -
http://forum.xda-developers.com/showthread.php?p=41834056
[GUIDE][NOOB'S]These non-AT&T ROMs work on AT&T/TMO/Canadian S4 devices. Here's how!
A quick search can be a beautiful thing
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
Thanks again for the link! I have actually seen several of those... but am just still very confused. mainly on these points:
- FIDO's rom isn't in those lists, and the variety of options for flashing (e.g. some ROMs say they need to be flashed with ODIN not TWRP) is a bit overwhelming!
- there's a post saying the Canadian ROMs are for odin not recovery flashing?
- I'm still not clear on whether I need to install a custom kernel just to flash a different ROM
- Also not clear on how to restore to factory stock (to take it to store for example)
- In the link you sent, the OP said non-ATT people should use the versions in their own forums... but does this apply to Canadian users too or is this ok for them?
Feel free to tell me if I'm being really dumb, but I really am a little lost lol.
As for buggy ROMs... would it be better to wait for one based off the S4 Google Edition?
Thanks again
Canadian dont need loki dont use loki never use loki
Take time to understand everithing before flashing
rodger is the same as fido exept for the rodger bloatware (my accout,visual voicemail etc)
what i did root with cf auto root
installed goomanager on google play ,this app can installed twrp and it really easy
in recovery i flash mint jelly rom ,after its done i flash faux kernel for canadian
To factory restore you have to installe stock rom thru odin ,(from what i understand) it change the rom and the kernel at the same time
zild8 said:
Canadian dont need loki dont use loki never use loki
Take time to understand everithing before flashing
rodger is the same as fido exept for the rodger bloatware (my accout,visual voicemail etc)
what i did root with cf auto root
installed goomanager on google play ,this app can installed twrp and it really easy
in recovery i flash mint jelly rom ,after its done i flash faux kernel for canadian
To factory restore you have to installe stock rom thru odin ,(from what i understand) it change the rom and the kernel at the same time
Click to expand...
Click to collapse
ok, so I'm just sorting through all of this. Successfully rooted and flashed CM nightly. However, now I see 'rogers' instead of 'fido' and 4G in the status bar, which I understand means that I'm on LTE according to stock JB icons.
So to sort this out:
a) what do I do about this incorrect network name?
b) if I restore to stock rom through odin, and it installs the 'rogers' rom, how do I get back to the fido apps? will I still have the network access / wrong name problem?
c) if I want to go BACK to stock eventually, I seem to have two options:
http://forum.xda-developers.com/showthread.php?t=2261573 [FACTORY STOCK]
http://forum.xda-developers.com/showthread.php?t=2269304 [12 May Official STOCK firmware collections for Canadian S4]
which do I use?
d) I took a nandroid image, BUT: can I restore from this (after wiping all data) to get back to factory ROM, or MUST I use ODIN? Or, do I need to use ODIN and then nandroid to restore everything about the stock ROM?
Thanks!!
A = I think cm have an option to rename carrier label if not you can install xposed framework and notach xposed and the go in frameword,module then activate nottach .open nottach then chose any option that you want ,over 100...
or i think you can try change your apn to show fido ( not sure)
B= check playstore for fido app
C= ? i dont know i think both of then are good, iwould use the one that say canadian stock firmware
D = if you restore from nandroid i think you flash counter gonna still show that you running cutom rom ,best way should be thru odin
Read a lot before you do anithing,you have to understand ..seem to be easy to brick .did not happen to me since one years ,but i read a lot..
And hit the thanks button when somebody helps you
zild8 said:
A = I think cm have an option to rename carrier label if not you can install xposed framework and notach xposed and the go in frameword,module then activate nottach .open nottach then chose any option that you want ,over 100...
or i think you can try change your apn to show fido ( not sure)
B= check playstore for fido app
C= ? i dont know i think both of then are good, iwould use the one that say canadian stock firmware
D = if you restore from nandroid i think you flash counter gonna still show that you running cutom rom ,best way should be thru odin
Read a lot before you do anithing,you have to understand ..seem to be easy to brick .did not happen to me since one years ,but i read a lot..
And hit the thanks button when somebody helps you
Click to expand...
Click to collapse
AWESOME, thanks for all that. Successfully flashed, so hopefully that's the end of it all. And thanks for pointing out the thanks button!!
Two LAST quick things:
- if I use the Canadian stock firmware, do I still end up with a wrong carrier name sign? I imagine I may need to ask the dev that, but just in case you happen to know. I actually can't seem to fix it using the methods you suggested, so I'd prefer not to have this happen.
- ok so I can flash with ODIN and then use nandroid to restore a snapshot of the filesystem I assume?
kabutar said:
AWESOME, thanks for all that. Successfully flashed, so hopefully that's the end of it all. And thanks for pointing out the thanks button!!
Two LAST quick things:
- if I use the Canadian stock firmware, do I still end up with a wrong carrier name sign? I imagine I may need to ask the dev that, but just in case you happen to know. I actually can't seem to fix it using the methods you suggested, so I'd prefer not to have this happen.
- ok so I can flash with ODIN and then use nandroid to restore a snapshot of the filesystem I assume?
Click to expand...
Click to collapse
-If you flash back to your stock carrier specific firmware with ODIN the carrier will be correct. You will be back to just as when you first got it from the dealer (provided they didn't set it up for you first).
-You shouldn't be able to restore the nandroid if you ODIN back to stock because you will no longer have a custom recovery.
blyndfyre said:
-If you flash back to your stock carrier specific firmware with ODIN the carrier will be correct. You will be back to just as when you first got it from the dealer (provided they didn't set it up for you first).
-You shouldn't be able to restore the nandroid if you ODIN back to stock because you will no longer have a custom recovery.
Click to expand...
Click to collapse
- Well the problem is that my carrier is Fido, a subsidiary of Rogers, and so CM only has a 'Rogers' release. Similarly there is only a 'Rogers' stock firmware, so I don't want to flash back to that and have the carrier still wrong...
- OK, well I assume I could root, flash nandroid, and then unroot - yes?
Thanks!
kabutar said:
- Well the problem is that my carrier is Fido, a subsidiary of Rogers, and so CM only has a 'Rogers' release. Similarly there is only a 'Rogers' stock firmware, so I don't want to flash back to that and have the carrier still wrong...
- OK, well I assume I could root, flash nandroid, and then unroot - yes?
Thanks!
Click to expand...
Click to collapse
-I see the dilema.
-Well as opposed to even flashing to stock with ODIN in the first place. I would suggest booting to recovery (TWRP or CWM), and restore your Nandroid backup. This should bring you to the point before you flashed any ROM. Keep in mind this won't however remove status showing 'custom'.
If you happened to already ODIN back to stock you would have to root again, install custom recovery and perform the step above.
blyndfyre said:
-I see the dilema.
-Well as opposed to even flashing to stock with ODIN in the first place. I would suggest booting to recovery (TWRP or CWM), and restore your Nandroid backup. This should bring you to the point before you flashed any ROM. Keep in mind this won't however remove status showing 'custom'.
If you happened to already ODIN back to stock you would have to root again, install custom recovery and perform the step above.
Click to expand...
Click to collapse
that is what I was thinking... there are ways to unroot as far as I know so hopefully that should be ok!
thankfully I did take a nandroid backup. speaking of which - I have 3 files, does this sound ok?:
- boot/sys/data (these were originally selected so just went with it)
- efs
- other (everything else)
last clarification: I thought nandroid was not recommended if switching between ROMs? like if I had a computer backup (i.e. nandroid) but took the backup in Windows XP (i.e. stock rom) and then tried to restore it over Windows 8 (i.e. CM rom), bad things would happen? or is the nandroid more like an acronis boot image thing where it completely wipes everything?
lastly, if I do that... do I need to wipe factory data, dalvik cache, etc or will nandroid take care of that for me?
many thanks again!
kabutar said:
that is what I was thinking... there are ways to unroot as far as I know so hopefully that should be ok!
thankfully I did take a nandroid backup. speaking of which - I have 3 files, does this sound ok?:
- boot/sys/data (these were originally selected so just went with it)
- efs
- other (everything else)
last clarification: I thought nandroid was not recommended if switching between ROMs? like if I had a computer backup (i.e. nandroid) but took the backup in Windows XP (i.e. stock rom) and then tried to restore it over Windows 8 (i.e. CM rom), bad things would happen? or is the nandroid more like an acronis boot image thing where it completely wipes everything?
lastly, if I do that... do I need to wipe factory data, dalvik cache, etc or will nandroid take care of that for me?
many thanks again!
Click to expand...
Click to collapse
I think when you go into recovery and restore nandroid everything will restore.
I would just restore the nandroid from your current state via recovery. If you are worried about it or it causes a problem, it isn't to many more steps to flash to stock via ODIN, root and install recovery and proceed with restore.
I think it is always safe practice to wipe first, and not to dirty flash.
blyndfyre said:
I think when you go into recovery and restore nandroid everything will restore.
I would just restore the nandroid from your current state via recovery. If you are worried about it or it causes a problem, it isn't to many more steps to flash to stock via ODIN, root and install recovery and proceed with restore.
I think it is always safe practice to wipe first, and not to dirty flash.
Click to expand...
Click to collapse
ok thanks.
However: I may be SAVED! I just realized that Fido is often tagged as FMC, and there's a stock firmware for that one in this thread. Thank the heavens!
kabutar said:
ok thanks.
However: I may be SAVED! I just realized that Fido is often tagged as FMC, and there's a stock firmware for that one in this thread. Thank the heavens!
Click to expand...
Click to collapse
Didn't know that! Never been with Fido. Great news for you, all you have to do is ODIN that firmware
blyndfyre said:
Didn't know that! Never been with Fido. Great news for you, all you have to do is ODIN that firmware
Click to expand...
Click to collapse
Yeah, very relieved, and now just gotta figure out why my phone is showing up as a Rogers phone when the nightly is tagged Rogers + Fido and I'll be good to go. I must say I miss multi-window a little and the handwaving over screen a lot, but by god TouchWiz was ugly.
hey kabutar
Yesterday i flash the 12 may stock firmware thru odin ,to revert backt to stock
Here what i did
-latest odin 3.07
-put your phone in download mode with usb not pluged to computer ...
-closed all kies software
-plug your phone in computer
add firmware on pda button ,dont touch any other option.
reboot i add a lot of crashing app so i went to recovery and errase data
reflash thru odin the stock firmware ,and boom everthing was stock ,no more custom in os or in download mode
Hi All,
I just got an SPH-i337 yesterday and attempted to Root + Install Mod.
I ended up rooting and installing Safestrap (TWRP 2.6.x.x). Upon first use I backed up my current OS to a removable SD card using the utility in TWRP. I then, because I was not clear on how to download install CM which was what I was going to, installed ROM Manager and selected CM without setting up a ROM slot. I think this is where I went wrong.
Upon reboot, I was unable to access the Stock ROM and had no options to go to CM. When I attempted to perform a restore from my backup on SD it failed as well and keeps going to the Android recovery screen (not TWRP).
I'm now just trying to go back to stock and have tried using both Heimdall and Odin to no avail. Odin at least provides an error message:
SW REV. CHECK FAIL: Fused:4, Binary:1. What does this mean? That I'm attempting to use an image (.tar.md5 file) which is not current? Is there a way that I can still recover my phone?
..also, please let me know if there are pieces of information that I'm missing. I don't have much to go off of since the firmware and other information (I believe) is not able to be accessed.
Again I just got the phone yesterday. I also have about 40 tabs open that are full of searches that I've been doing regarding this. As yet, no luck.
revolut10n said:
..also, please let me know if there are pieces of information that I'm missing. I don't have much to go off of since the firmware and other information (I believe) is not able to be accessed.
Again I just got the phone yesterday. I also have about 40 tabs open that are full of searches that I've been doing regarding this. As yet, no luck.
Click to expand...
Click to collapse
Look for the mk2 tar files. And do a lot of reading. You went wrong in a number of different areas
revolut10n said:
Hi All,
I just got an SPH-i337 yesterday and attempted to Root + Install Mod.
I ended up rooting and installing Safestrap (TWRP 2.6.x.x). Upon first use I backed up my current OS to a removable SD card using the utility in TWRP. I then, because I was not clear on how to download install CM which was what I was going to, installed ROM Manager and selected CM without setting up a ROM slot. I think this is where I went wrong.
Upon reboot, I was unable to access the Stock ROM and had no options to go to CM. When I attempted to perform a restore from my backup on SD it failed as well and keeps going to the Android recovery screen (not TWRP).
I'm now just trying to go back to stock and have tried using both Heimdall and Odin to no avail. Odin at least provides an error message:
SW REV. CHECK FAIL: Fused:4, Binary:1. What does this mean? That I'm attempting to use an image (.tar.md5 file) which is not current? Is there a way that I can still recover my phone?
Click to expand...
Click to collapse
revolut10n said:
..also, please let me know if there are pieces of information that I'm missing. I don't have much to go off of since the firmware and other information (I believe) is not able to be accessed.
Again I just got the phone yesterday. I also have about 40 tabs open that are full of searches that I've been doing regarding this. As yet, no luck.
Click to expand...
Click to collapse
Safestrap only works with other TW ROMS, so your first issue was trying to use CM. Second, it's not official TWRP and is not even installed to the recovery partition so using ROM Manager was your second issue. Trying to boot into recovery normally will take you to stock recovery since it isn't installed in the recovery partition, there should be a splash screen that comes up after the Samsung Galaxy S4 screen asking to either press for recovery or continue. If that works, you can use the backup from there. If it's gone, you have to use ODIN. The reason you get that SW REV. CHECK FAIL is because you're trying to flash an older firmware than you have. Depending on if you were on 4.2.2 or 4.3 you will either need the MF3 or MK2 .tar.md5 respectively.
jd1639 said:
Look for the mk2 tar files. And do a lot of reading. You went wrong in a number of different areas
Click to expand...
Click to collapse
Thanks for pointing me to those files. I'm sure I did go wrong in a few places as I felt that I was largely just winging it.. There's a TON of information out there. Is there anything specific that I was more wrong than the rest?
revolut10n said:
Thanks for pointing me to those files. I'm sure I did go wrong in a few places as I felt that I was largely just winging it.. There's a TON of information out there. Is there anything specific that I was more wrong than the rest?
Click to expand...
Click to collapse
Deadly sin said it all. Cm and rom manager. Here are the files you need http://forum.xda-developers.com/showthread.php?p=49687770
Thanks everyone. Hell of an introduction to Android, I have to say considering I just got off the WinPhone bandwagon yesterday (been using it for ~7 years).
revolut10n said:
Thanks everyone. Hell of an introduction to Android, I have to say considering I just got off the WinPhone bandwagon yesterday (been using it for ~7 years).
Click to expand...
Click to collapse
The s4 is a very difficult phone to use custom roms on. Once you're back up and running start here and read a lot before doing anything with it http://forum.xda-developers.com/showthread.php?p=42320391
jd1639 said:
The s4 is a very difficult phone to use custom roms on. Once you're back up and running start here and read a lot before doing anything with it http://forum.xda-developers.com/showthread.php?p=42320391
Click to expand...
Click to collapse
Now you tell me - after I've been trying to do this for 12+ hours. Many thanks though - it looks like the MK2 AiO files are working.
jd1639 said:
The s4 is a very difficult phone to use custom roms on. Once you're back up and running start here and read a lot before doing anything with it http://forum.xda-developers.com/showthread.php?p=42320391
Click to expand...
Click to collapse
Unfortunately, it seems that I can't use the method listed directly on that page on account of running the MK2 baseband. If I'm going to go forward it looks like I'll have to use SafeStrap and unofficial TWRM + TW mods for the time being.
Of course, if something about what I'm saying is wrong, I'd be glad to hear it.
revolut10n said:
Unfortunately, it seems that I can't use the method listed directly on that page on account of running the MK2 baseband. If I'm going to go forward it looks like I'll have to use SafeStrap and unofficial TWRM + TW mods for the time being.
Of course, if something about what I'm saying is wrong, I'd be glad to hear it.
Click to expand...
Click to collapse
Check my last Post #50 it should get u an idea and where to find related link. Also check that MK2 INDEX & ROM LIST ....:good:
Hi,
I am looking at flashing some custom roms to see which one I like, I have got root by using the cf-auto root by cahinfire but, before I begin I just want to make sure that I back every thing up correctly to avoid any trouble further down the line.
As I understand it ( I use the term 'understand' loosely ) I need to back up the EFS folder and imei
Is that all that is needed? or is there something else that i should do? essentially I would just like to ensure that I can revert back to a stock rom, im not that concerned about knox or warranty. Im sorry if this has been brought up before but as a novice I would appreciate some assistance in gaining a proper understanding of the requirements before starting off
thanks
Backing up EFS has it's pros and cons - I done it, but then I got a mess up, and restoring my EFS did not work. I had to run the fire script posted in the dev section (this script rebuilds your EFS partition so it can be read properly again) - I have seen countless users brick their devices by backing up EFS with bad/rogue apps, so if you go this method, choose very very wisely.
My advice, install CWM, and make a back up via that. - it'll see you right. - If by chance you do get a mess up, you can run the fire script by firausman in the dev section and it'll fix unknown baseband and bootlooping errors.
Ultimately, I cannot stress that you read as much as you can and are aware of the potential what can and does happen, what cannot happen and ultimately can you fix it if something does go wrong.
EDIT:: here is the SCRIPT if you do indeed need it, keep it on your extSD Card for just in case reasons.
radicalisto said:
Backing up EFS has it's pros and cons - I done it, but then I got a mess up, and restoring my EFS did not work. I had to run the fire script posted in the dev section (this script rebuilds your EFS partition so it can be read properly again) - I have seen countless users brick their devices by backing up EFS with bad/rogue apps, so if you go this method, choose very very wisely.
My advice, install CWM, and make a back up via that. - it'll see you right. - If by chance you do get a mess up, you can run the fire script by firausman in the dev section and it'll fix unknown baseband and bootlooping errors.
Ultimately, I cannot stress that you read as much as you can and are aware of the potential what can and does happen, what cannot happen and ultimately can you fix it if something does go wrong.
EDIT:: here is the SCRIPT if you do indeed need it, keep it on your extSD Card for just in case reasons.
Click to expand...
Click to collapse
Thanks for the reply and advice Radicalisto.
I will check out CWM and how and what that backs up. If I take a guess now it will make an image of my current system that can be restored? If so does that ensure a back up of efs folder?
mjneil.81 said:
Thanks for the reply and advice Radicalisto.
I will check out CWM and how and what that backs up. If I take a guess now it will make an image of my current system that can be restored? If so does that ensure a back up of efs folder?
Click to expand...
Click to collapse
CWM offers an EFS backup yes, it has to be done seperate to the IMAGE back up though. Also note if you back up a 4.3 ROM on MJ7 firmware you cannot downgrade to a lower version ie: MJ1-2-3-4-5-6 etc - you can go to MK2 and back to MJ7 though.
Similar if you back up a 4.3 and upgrade to 4.4.2 then that backup becomes useless as it cannot be restored.
CWM - Install custom ROM, keep that script I posted close by, and you'll be 100% :good:
radicalisto said:
CWM offers an EFS backup yes, it has to be done seperate to the IMAGE back up though. Also note if you back up a 4.3 ROM on MJ7 firmware you cannot downgrade to a lower version ie: MJ1-2-3-4-5-6 etc - you can go to MK2 and back to MJ7 though.
Similar if you back up a 4.3 and upgrade to 4.4.2 then that backup becomes useless as it cannot be restored.
CWM - Install custom ROM, keep that script I posted close by, and you'll be 100% :good:
Click to expand...
Click to collapse
Thanks alot for your assistance im going to get the back up sorted and read up some more there is fair bit that i need to understand before flashing
Wise words my friend. Read up and understand are the two most important words of advice anyone can give and words that anyone should take heed of.
Good luck, if you run into problems, just holler :good:
radicalisto said:
Wise words my friend. Read up and understand are the two most important words of advice anyone can give and words that anyone should take heed of.
Good luck, if you run into problems, just holler :good:
Click to expand...
Click to collapse
so far the best thing I have come up with is to flash the latest 4.4.2 stock rom, I think this is the best option until some of the custom ROMs develop along a bit further.
but this leeds to a few more questions (I hope its not too much of a bother) Im going ( i think) to download the rom from Firmwares|SamMobile but it will be from another country(im in Australia) could this affect the perfomance of the phone in anyway or can I just flash other modems/radios in order to fix any problems that may occur?
mjneil.81 said:
so far the best thing I have come up with is to flash the latest 4.4.2 stock rom, I think this is the best option until some of the custom ROMs develop along a bit further.
but this leeds to a few more questions (I hope its not too much of a bother) Im going ( i think) to download the rom from Firmwares|SamMobile but it will be from another country(im in Australia) could this affect the perfomance of the phone in anyway or can I just flash other modems/radios in order to fix any problems that may occur?
Click to expand...
Click to collapse
So long as your note isn't a Hong Kong model you're alright, Here is a faster download link for XEO (Stock Polish ROM) - So long as it's an Intl N9005 (not HK) should be fine
all done upgraded to 4.4.2 no problems at all thanks radicalisto
mjneil.81 said:
all done upgraded to 4.4.2 no problems at all thanks radicalisto
Click to expand...
Click to collapse
:highfive:
ok now I have a problem I just tried to root the phone again with cf autoroot and its stuck in a boot loop. I cant get it back in download mode or recovery any suggestions
all good i got back into download mode hahaha *stops having a heart attack