Database Users

How to do a complete system restore?

Let me apologize for being a newbie as I come from 5 years of using Windows Mobile and just got my first Tab/Android 2 weeks ago. This is all new to me.
After messing up with some system files and factory applications (like I removed stk.apk and other things) I decided to do a full hardware reset. This is something I did many times in Windows Mobile... whats bad get overwriten in ROM and whats missing gets back where it was. But is seems on this Tab this is not the case.
After the full resetthings only got dramatically worse. All the missing system apps are still missing (I thought they be "restored") and nothing works, just crashes one after the next, cant use anything. I also tried with the system off the method of pressing and holding the “Volume Up” and “Power” buttons at the same time, then after recovery screen appears navigate and select “wipe data / Factory reset” and pressing the “Home” button, but after that and the system re-starts, same thing! All bad.
Can someone please explain to me how to do a full rstore where all system files, all and everythign gets back as it was in the Tab as it was shipped? What a flippin' nightmare... Windows Mobile, I love you!
Thanks in advance.

settings/privacy/factory reset.

natious said:
settings/privacy/factory reset.
Click to expand...
Click to collapse
No no, that doesnt restore anything! All missing files dont get restored. I need a full stock ROM image and restore EVERYTHING. Thats what I dont know where to get and how to do...

VeEuzUKY said:
No no, that doesnt restore anything! All missing files dont get restored. I need a full stock ROM image and restore EVERYTHING. Thats what I dont know where to get and how to do...
Click to expand...
Click to collapse
Yeh i realized that after reading your post properly sorry man, i guess you can just flash one of roms found here, like rotos or modaco's JMI, that would atlest give you a work tab till you can find a stock samsung rom
If you dont have cwm installed you can flash with odin or heidmill (sp)

natious said:
Yeh i realized that after reading your post properly sorry man, i guess you can just flash one of roms found here, like rotos or modaco's JMI, that would atlest give you a work tab till you can find a stock samsung rom
If you dont have cwm installed you can flash with odin or heidmill (sp)
Click to expand...
Click to collapse
Yeah, I enever flashed the Tab. Can U advise me on a stable "OK" ROM? Where can i find odin or heidmill and some sort of a guide to help me step-by-step? I have positively no clue what I am doing... sorry for my ignorance... I feel thoroughly stupid...

I got lucky and found this site. Hope yours is a Verizon Tab
I'm not allowed to post links. But go to google type in "galaxy tab system restore" and click on the "[How TO] Restore VZW Galaxy Tab to stock DJ11" link
It's in the droidforums. net

VeEuzUKY said:
Yeah, I enever flashed the Tab. Can U advise me on a stable "OK" ROM? Where can i find odin or heidmill and some sort of a guide to help me step-by-step? I have positively no clue what I am doing... sorry for my ignorance... I feel thoroughly stupid...
Click to expand...
Click to collapse
First of all, you need to post what "type" of Tab you have, which is generally going to be determined by your country and/or carrier.
Flashing a new Android ROM isn't a particularly complicated process, but it can seem daunting if you've not done it before - this is especially true when using Odin or Heimdall over a "recovery" based flash.
FWIW, the reason your "factory reset" didn't work is because all is essentially does it reformat the /data partition (a generalisation, but close enough for these purposes). On a stock Tab, you cannot mount /system as read/write, so you are unable to change the contents of that partition. This means that on a stock Tab, /system should never change.
However, when you root the device you give yourself the ability to remount /system as read/write and thus make changes which are not going to affected by a factory reset.
Take a look at this thread - lots of useful information there!
Regards,
Dave

foxmeister said:
First of all, you need to post what "type" of Tab you have, which is generally going to be determined by your country and/or carrier.
Flashing a new Android ROM isn't a particularly complicated process, but it can seem daunting if you've not done it before - this is especially true when using Odin or Heimdall over a "recovery" based flash.
FWIW, the reason your "factory reset" didn't work is because all is essentially does it reformat the /data partition (a generalisation, but close enough for these purposes). On a stock Tab, you cannot mount /system as read/write, so you are unable to change the contents of that partition. This means that on a stock Tab, /system should never change.
However, when you root the device you give yourself the ability to remount /system as read/write and thus make changes which are not going to affected by a factory reset.
Take a look at this thread - lots of useful information there!
Regards,
Dave
Click to expand...
Click to collapse
Thanks for the link... yes Ive seen that master thread... I just keep reading from link to link and thread to thread and all gets more complicated, I keep downloading more files and installing more stuff but in the end Im more confused and positively going no where. There is not one simple, from start to finish guideline on how to do the process of wiping all data and installing a new ROM. Ive done this endless times on many phones under WinMo, and with more or less difficulty never had any problems getting this done. But here, the more I read the more utterly chaotically confused I am.
I am yet to have anyone explain what type of Tab I have. Its GSM, I think its Euro, bought in Hong Kong. I have found out all bootloaders and stuff seem to be cleaer and I should be able to flash anything. Its a GT-P1000 and Baseband P1000ZHJJ1. This is all I know.

VeEuzUKY said:
Thanks for the link... yes Ive seen that master thread... I just keep reading from link to link and thread to thread and all gets more complicated, I keep downloading more files and installing more stuff but in the end Im more confused and positively going no where. There is not one simple, from start to finish guideline on how to do the process of wiping all data and installing a new ROM. Ive done this endless times on many phones under WinMo, and with more or less difficulty never had any problems getting this done. But here, the more I read the more utterly chaotically confused I am.
I am yet to have anyone explain what type of Tab I have. Its GSM, I think its Euro, bought in Hong Kong. I have found out all bootloaders and stuff seem to be cleaer and I should be able to flash anything. Its a GT-P1000 and Baseband P1000ZHJJ1. This is all I know.
Click to expand...
Click to collapse
Its pretty much the same as mine then, so i recommend you use modacos kernel and rom and installing cwm
cwm - http://forum.xda-developers.com/showthread.php?t=870690
Kernel - http://forum.xda-developers.com/showthread.php?t=925760
Rom - http://forum.xda-developers.com/showthread.php?t=941423
If you have and external sd card (one that you put into the side of the tab)
You can flash the ext4 kernel via odin, its pretty simple, there will be instructions in the threads.
Are you still able to go on the market? If so download the cwm app and use that so you get the awesome recovery menu and features, you can then use it to flash a new rom and make backups that are really really easy to restore. Seeing it looks like you like to mess around with stuff i suggest it the best way to go.
Hope this helps

Ok thanks for the tips. I have finally managed to get the Tab working again and flashed it with Roto JMI Pre-Rooted Firmware v2. All seems OK at this point. Ill check the links you sent me and follow-up. Flashing Roto JMI Pre-Rooted Firmware v2 with Odin3 1.7 is easy so I hope modacos kernel and rom and installing cwm are easy as well.

A little off topic:
I just got my SGT on Friday and want to root&/flash custom ROM. Gonna definitely root soon...But thinking of holding off on the custom ROM until CM7 is stable or a nice clean Honeycomb ROM is cooked
Does ClockWorkMod require root? I know Titanium Backup does. Can't really do any "fun" things with the tab until it's rooted it seems.

Fido Canada S4 rooting/flashing questions

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

[Q] clarification on multiple topics for a beginner.

Hey guys. I want to start off by saying that I've researched answers to my following questions but the answers have raised more questions.
I will first explain my current setup and the process in which I took to get here.
When I first got my phone it was mj7
From fully stock (no root) I installed the OTA mje update.
I then rooted using Kongo
Installed SS
Installed the JellyBeans rom
Now wwhee I need clarification. ..
If I'm upgrading a new version in the future of this same rom it states to do a factory reset. To me this means use ss and perform a wipe on the rom slot the current rom is installed on. Is this correct? I ask because I've seen posts saying you should reroot before doing so. This leads me to my next question....
If I'm going to unroot and put back to stock as if I was going to do a warranty swap can I use the kingo unroot option and be all set? I've read that this works perfectly fine but then I see others saying you should flash the tar file. And that brings me to my last question. ..
If needing to fflash the tar file should I flash the current mj version my phone is on (I believe this is called the kernel version? ) or whatever is the latest one released ?
I totally understand these are basic questions that I should already know and have been talked about a million times but for a beginner like me and the HUGE amount of info out there I feel I'm getting some contradicting information. Please forgive my lack of knowledge, I'm just now stepping into this world. Thank you in advance... any and all input would be hugely appreciated.

JiMiHenDriX420 said:
If I'm upgrading a new version in the future of this same rom it states to do a factory reset. To me this means use ss and perform a wipe on the rom slot the current rom is installed on. Is this correct? I ask because I've seen posts saying you should reroot before doing so. This leads me to my next question....
If I'm going to unroot and put back to stock as if I was going to do a warranty swap can I use the kingo unroot option and be all set? I've read that this works perfectly fine but then I see others saying you should flash the tar file. And that brings me to my last question. ..
If needing to fflash the tar file should I flash the current mj version my phone is on (I believe this is called the kernel version? ) or whatever is the latest one released ?
I totally understand these are basic questions that I should already know and have been talked about a million times but for a beginner like me and the HUGE amount of info out there I feel I'm getting some contradicting information. Please forgive my lack of knowledge, I'm just now stepping into this world. Thank you in advance... any and all input would be hugely appreciated.
Click to expand...
Click to collapse
One you have updated to MJE and achieved root and installed SS, you're good, until the next OTA rolls out from verizon. Currently I have my stock slot with root and nothing else. My first custom Rom slot has Beans' Rom on it. when people say to do a factory reset, they are talking about a factory reset on the specific rom slot you wish you flash. When you wipe a Rom slot, only that slot is affected, nothing else. So the phone will not lose root, or MJE, or SS.
So, in your case, back up your apps with TB or whatever you use, save your media on your MicroSD if you have one, and wipe the slot that youre going to flash. Dont wipe the stock slot, unless that's the one youre re-flashing. after you wipe, flash the new Beans 5, then either have google sync up your apps, or install titanium backup and go restore everything. Personally i had problems doing a full batch restore, so I only restored a few things, (i left out a bunch of system app data restores such as settings and dictionaries), but that should do the trick.

[Q] Have MDL, have root, have zero idea how to get 4.3

Hello all,
I have had my S4 for awhile now and need some help. When I first received it, I did some reading, rooted, did something that removed a triangle or a padlock, can't remember which one and made sure the AT&T software update was unable to run. At the time, custom recovery wasn't possible so I stopped there. So here I am now, rooted with MDL and I have no idea where to go from here to get the latest 4.3, although apparently I have the holy grail of firmware.
I've read as much as I possibly can, subscribed to the forums, GOOGLED, SEARCHED, RTFM and waited for someone else to come along and ask the very same question. Some did but those threads never really gave me the info I need to SAFELY flash my phone up to 4.3. So what do I do? All I need is some guidance, I follow directions well. Teach me! Please and Thank You
Doug

DO NOT UPDATE YOUR FIRMWARE IF YOU STILL HAVE MDL. ....U JUST NEED INSTALL CWM RECOVERY OR TWRP RECOVERY. .... AND THEN INSTALL CUSTOM 4.3 ROM. .... EVEN 4.4 KITKAT ROM. ..... BUT IF U DO UPDATE TO NEWEST MK2 FIRMWARE THEN U WOULD LOSE THE PRIVILEGE OF MDL..... WHICH IS RARE. ..... GOODLUCK
Swyped from MK2 Deadly Venom SS

Right! One of the things I have learned is that I want to keep the MDL baseband. What I really want are all the improvements that 4.3 or 4.4 offer. Also, I'm hoping my Pebble and my S4 play better together than they do now.
Do I just pick a recovery? Are they the same? Guess I need to read some more.
Sent from somewhere...

DRRies said:
Right! One of the things I have learned is that I want to keep the MDL baseband. What I really want are all the improvements that 4.3 or 4.4 offer. Also, I'm hoping my Pebble and my S4 play better together than they do now.
Do I just pick a recovery? Are they the same? Guess I need to read some more.
Sent from somewhere...
Click to expand...
Click to collapse
This one click tool is pretty awesome. http://forum.xda-developers.com/showthread.php?t=2297033... .. Super easy as 1.2.3.... and have everything u need. ......root....CWM or TWRP recovery and even flash to stock via Odin. ... Hope this work for u and hit THANK button If someone helped you. ...
Swyped from MK2 Deadly Venom SS

DRRies said:
Hello all,
I have had my S4 for awhile now and need some help. When I first received it, I did some reading, rooted, did something that removed a triangle or a padlock, can't remember which one and made sure the AT&T software update was unable to run. At the time, custom recovery wasn't possible so I stopped there. So here I am now, rooted with MDL and I have no idea where to go from here to get the latest 4.3, although apparently I have the holy grail of firmware.
I've read as much as I possibly can, subscribed to the forums, GOOGLED, SEARCHED, RTFM and waited for someone else to come along and ask the very same question. Some did but those threads never really gave me the info I need to SAFELY flash my phone up to 4.3. So what do I do? All I need is some guidance, I follow directions well. Teach me! Please and Thank You
Doug
Click to expand...
Click to collapse
As ted said, upgrading is bad. You can change modems and such to the MK2 baseband, it's the bootloader that's the issue. As long as you don't try to take any OTA's and don't ODIN any newer version you'll be fine. If you want to run the official AT&T 4.3, your closest bet is StockUp MK2 and the rebloat addon. Otherwise, you can choose either CWM or TWRP and flash away as long as you remember to use the loki patch for things that aren't patched already.

I've read the info at the link you provided before and wondered if I'm already rooted, what would happen? Is that safe to use if currently rooted?
Also, since I'm currently on MDL, would a factory reset return me to a fresh MDL or would it force me to update to current software?

Start here. http://forum.xda-developers.com/showthread.php?p=42320391

Ok so I strated with the thread posted. I now have TWRP installed, nandroid backed up and all sorts of zips on my ext card. Also made Kies backups. My first ROM flash, Stockup_MK2 went fine until reboot and I had no mobile data or cell signal. What did i do wrong? I immediately did a restore from the nandroid backup to return to where was before.

DRRies said:
Ok so I strated with the thread posted. I now have TWRP installed, nandroid backed up and all sorts of zips on my ext card. Also made Kies backups. My first ROM flash, Stockup_MK2 went fine until reboot and I had no mobile data or cell signal. What did i do wrong? I immediately did a restore from the nandroid backup to return to where was before.
Click to expand...
Click to collapse
Did you wipe before installing the rom? Just use the slider toggle in wipe. If so, check that the apn is setup correctly.

DRRies said:
Ok so I strated with the thread posted. I now have TWRP installed, nandroid backed up and all sorts of zips on my ext card. Also made Kies backups. My first ROM flash, Stockup_MK2 went fine until reboot and I had no mobile data or cell signal. What did i do wrong? I immediately did a restore from the nandroid backup to return to where was before.
Click to expand...
Click to collapse
In stead of a stcok MK2 rom might I suggest a fairly stock but cleaned up rom like MDOB or any other close to stock rom's
http://forum.xda-developers.com/showthread.php?t=2280556
Not advocating any one person but he does good stuff and it based on the actual AT&T update to 4.3.. Make sure you do as the guy above me stated and do the simple swipe to wipe in TWRP

Root Asus Memo Pad 176 on lollipop .36 newest firmware plus Xposed

***DISCLAIMER***
If done incorrectly, this can soft brick your device. I take no responsibility for this, and if you're unfamiliar with rooting android I suggest reading up before attempting. There are threads to fix your tablet if this goes sideways, but if this doesn't work I personally can't promise I can help you.
I used this method two days ago, and would like to thank jerbear294 for providing me with the information. I didn't come up with this, I just want to help others looking for root.
Hello guys
First, apologies if this is a redundant thread. All the root methods I've seen in individual topics seem outdated, and I just wanted to make this quick guide to help people from having to scan through pages of information to learn how to root these things. This method works on firmware WW_V12.10.1.33_20150917, which is the current release as of this post.
Lets get to it!
Download
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
(Navigate to page 1, for some reason it links to the last page)
Place it on your computer and unzip.
And the latest supersu .zip 2.46
https://download.chainfire.eu/696/supersu/
Which will be on your tablet.
Install the temp recovery to your computer, connect the tablet, make sure you enable adb (USB Debugging) on it in developer mode (Settings → about → software version → tap build number 7 times for developer mode). Once connected, run the exe in the .zip from the temp recovery.
Choose: TWRP HDPI portrait, T4.
Your device will boot into twrp recovery. Now navigate to the supersu.zip on your tablet, and install, and you should be good to go . Good luck, and happy rooting!
Thanks to everyone who developed these tools (especially Social_Design_Concepts), and XDA for providing a medium to relate them.
To run Xposed, go to http://forum.xda-developers.com/showthread.php?t=3034811
Choose 'xposed-v80-sdk21-x86', this is currently the only version I've had success with. Happy hunting folks!

404 page not found on the first link?

ThunderThighs said:
404 page not found on the first link?
Click to expand...
Click to collapse
Link fixed, thanks and my apologies

thank you a lot! you saved me a lot of browsing! :good:

I updated my me176cx directly from v17 to v33. No matter what I do, the rooting method you outline here doesn't work for me anymore. On v17 it worked first time, now it's a fail every time. No superuser app, no su binary. Any suggestions? I've reinstalled the v33 firmware (it was actually a nandroid backup posted by jerbear on androidfilehost).
Anyway, when I installed temp TWRP this time it asked me did I want to keep system read only - I answered no. Was that a mistake? Also, I went straight from v17 to v33, bypassing the v24 update completely. Was that the wrong thing to do?
Your help would be hugely appreciated, a life with an unrooted device is not one I care to contemplate.

seamo123 said:
I updated my me176cx directly from v17 to v33. No matter what I do, the rooting method you outline here doesn't work for me anymore. On v17 it worked first time, now it's a fail every time. No superuser app, no su binary. Any suggestions? I've reinstalled the v33 firmware (it was actually a nandroid backup posted by jerbear on androidfilehost).
Anyway, when I installed temp TWRP this time it asked me did I want to keep system read only - I answered no. Was that a mistake? Also, I went straight from v17 to v33, bypassing the v24 update completely. Was that the wrong thing to do?
Your help would be hugely appreciated, a life with an unrooted device is not one I care to contemplate.
Click to expand...
Click to collapse
I hear you. I'll be honest - I didn't so much Pioneer this method so much as succeed with it and then repost it to save people some time going through the threads on here :/
That said, I would ask jerbear if he has had this problem reported via his nandroid backup. Answering "no" in twrp was fine, if you said yes it would have been gimped and probably useless, so I doubt that's the problem. I would say it's the nandroid, but I've read people using it and nobody I remember mentioned a problem. In the meantime, try re downloading the backup and flashing it again, and then trying temp twrp and see if it works. I personally haven't tried jerbear's nandroid, so I can't speak on it's behalf
Sorry I don't have something more concrete, let me know what jerbear says and how things play out, and good luck

Opensystem said:
I hear you. I'll be honest - I didn't so much Pioneer this method so much as succeed with it and then repost it to save people some time going through the threads on here :/
That said, I would ask jerbear if he has had this problem reported via his nandroid backup. Answering "no" in twrp was fine, if you said yes it would have been gimped and probably useless, so I doubt that's the problem. I would say it's the nandroid, but I've read people using it and nobody I remember mentioned a problem. In the meantime, try re downloading the backup and flashing it again, and then trying temp twrp and see if it works. I personally haven't tried jerbear's nandroid, so I can't speak on it's behalf
Sorry I don't have something more concrete, let me know what jerbear says and how things play out, and good luck
Click to expand...
Click to collapse
Hey, thanks for the reply. Just to clarify, is this the file you downloaded and restored? https://www.androidfilehost.com/?fid=24052804347832070
Here's what I had to do: I had to create a folder (this folder I named with my device's serial no) as well as creating a folder inside that folder that I named after a nandroid backup that I'd done earlier. Then I placed all the files from the nandroid zip inside that (second) folder. Only then did the TWRP 'see' the backup. I did the usual system/cache/dalvik cache wipe and restored the nandroid without any hitch. You did that or something similar to get TWRP to restore the nandroid, right?
I wonder should I have taken the recovery log from my own nandroid and replaced jerbear's recovery log with it? I'm starting to confuse myself at this point I think..

seamo123 said:
Hey, thanks for the reply. Just to clarify, is this the file you downloaded and restored? https://www.androidfilehost.com/?fid=24052804347832070
Here's what I had to do: I had to unzip the file into a folder (this folder I named with my device's serial no) as well as creating a folder inside that folder that I named after a nandroid backup that I'd done earlier. Only then did the TWRP 'see' the backup. I did the usual system/cache/dalvik cache wipe and restored the nandroid without any hitch. You did that or something similar to get TWRP to restore the nandroid, right?
Click to expand...
Click to collapse
No sorry you misread: I never had to use that nandroid (or any on this tablet yet, all my updates .33 were in order and via ota) - I'm aware of it though and I've only heard good things so I'm not sure where the process might have broken down, outside maybe a corrupted download. That's why I recommended asking jerbear if he's heard of that problem from anyone, because it's a stock backup and I know tons of people have used it and supposedly rooted successfully using temp twrp. From what I can tell, you shouldn't have any problems...it sounds like you know what you're doing and did everything properly.
Can you revert to a previous version, and manually download .33 from https://www.asus.com/support/Download/28/6/0/23/3HzHuNmdcAgeMhJ1/32/ ? I assume there are no backups readily available, but the major xda thread on the 176 might have a couple older ones you can try.
I haven't done as much as a lot of pioneers with my tab, just update, root and install xposed. As such I can't really answer myself what the problem you're having is, just offer general advice I would try. Jerbear hopefully knows about what might be causing the root to fail

Opensystem said:
No sorry you misread: I never had to use that nandroid (or any on this tablet yet, all my updates .33 were in order and via ota) - I'm aware of it though and I've only heard good things so I'm not sure where the process might have broken down, outside maybe a corrupted download. That's why I recommended asking jerbear if he's heard of that problem from anyone, because it's a stock backup and I know tons of people have used it and supposedly rooted successfully using temp twrp. From what I can tell, you shouldn't have any problems...it sounds like you know what you're doing and did everything properly.
Can you revert to a previous version, and manually download .33 from https://www.asus.com/support/Download/28/6/0/23/3HzHuNmdcAgeMhJ1/32/ ? I assume there are no backups readily available, but the major xda thread on the 176 might have a couple older ones you can try.
I haven't done as much as a lot of pioneers with my tab, just update, root and install xposed. As such I can't really answer myself what the problem you're having is, just offer general advice I would try. Jerbear hopefully knows about what might be causing the root to fail
Click to expand...
Click to collapse
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?

Just chiming in to say this method worked for me and thanks a lot!
I was on firmware WW_V12.10.1.33_20150917, followed the instructions, and used root checker to confirm. Yep, rooted!
I did tap the keep read only button, more so on accident. Not sure what that does/did but I did find the restore defaults button. I don't know if that "fixed" anything or what but I didn't want to accidentally break something. Anyway, after that, I flashed SuperSU and was rooted.
Thanks again! :good:

seamo123 said:
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Click to expand...
Click to collapse
Yes the general for the memo 176 has a special working xposed, make sure you use that one. I'm a bit busy, but I'll link when I can glad you got it rooted

Joe_Bangles said:
Just chiming in to say this method worked for me and thanks a lot!
I was on firmware WW_V12.10.1.33_20150917, followed the instructions, and used root checker to confirm. Yep, rooted!
I did tap the keep read only button, more so on accident. Not sure what that does/did but I did find the restore defaults button. I don't know if that "fixed" anything or what but I didn't want to accidentally break something. Anyway, after that, I flashed SuperSU and was rooted.
Thanks again! :good:
Click to expand...
Click to collapse
Glad to help, xda is where it's at for community

OMG!!!!!!!! Finally!!! I'm so glad to read this post.... thank you!!! I've been searching a good method for months!
And yes, it works!!! xD

Delichi said:
OMG!!!!!!!! Finally!!! I'm so glad to read this post.... thank you!!! I've been searching a good method for months!
And yes, it works!!! xD
Click to expand...
Click to collapse
Hurray! Glad it worked out for you

seamo123 said:
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Click to expand...
Click to collapse
Hey sorry for the late response, work got crazy on me. I edited the original post to now include how to set up Xposed, for you or anyone else interested. Confirmed working on both .33 and .36

Hey guys!
Sorry for the off-topic but how is the new .36 firmware compared to .33? For me .33 sucked,all memory leaks , crashing apps, slow as hell,fortunately I got motherboard replacement and now I'm on KK again. Should I update to .36? What do you think?

dareas said:
Hey guys!
Sorry for the off-topic but how is the new .36 firmware compared to .33? For me .33 sucked,all memory leaks , crashing apps, slow as hell,fortunately I got motherboard replacement and now I'm on KK again. Should I update to .36? What do you think?
Click to expand...
Click to collapse
It's got less battery drain here, performance seems better too but that could just be a placebo

Opensystem said:
It's got less battery drain here, performance seems better too but that could just be a placebo
Click to expand...
Click to collapse
Thank you. Does upgrading to LP unlock 64 bit capability of the processor (Z3745)? I'd really appreciate it if you could answer me.

dareas said:
Thank you. Does upgrading to LP unlock 64 bit capability of the processor (Z3745)? I'd really appreciate it if you could answer me.
Click to expand...
Click to collapse
I'm not sure, we should be because of art runtime but I feel like our version is bootlegged to a degree

unable to mount /data, internal storage 0MB. How can I load the zip file?
It's probably because FDE. I used a external SD card instead