Database Users

Telus Hero Nandroid backup

Hey guys, I'd first like to thank everyone posting guides on the forums, has made my job a lot easier. I'm currently in the middle of trying to root my telus hero with the gold card method. I made the gold card, i think anyways, but before i go ahead and run the RUU file to downgrade, I want to make a nandroid backup of my phone. I downloaded the recovery image which is supposed to have nandroid v2.2 in it, but I'm not to sure how exactly to use it... I'm kind of a reallllly big nub.

chaosthebomb said:
Hey guys, I'd first like to thank everyone posting guides on the forums, has made my job a lot easier. I'm currently in the middle of trying to root my telus hero with the gold card method. I made the gold card, i think anyways, but before i go ahead and run the RUU file to downgrade, I want to make a nandroid backup of my phone. I downloaded the recovery image which is supposed to have nandroid v2.2 in it, but I'm not to sure how exactly to use it... I'm kind of a reallllly big nub.
Click to expand...
Click to collapse
From my understanding, as I saw it, I believe that the RUU's are safe, since they're HTC approved images, just that the gold card allows you to revert to a lower version of an HTC rom. Think of it as the RUU's as an official update, but an older official update, and the gold cards make your phone seen as a phone that can accept any update (new or old). So there will not be any harm when you run an official update like this unless your computer crashes midupdate or you pull the battery..or the cable gets unplugged.
Nandroid backups can be produced using the recovery image (i call it a menu since that's all you really see from it), which is covered later in a tutorial if you're reading one. This recovery image is applied after a downgrade (the downgrade gives you the ability to have root access, which is i believe necessary to get the recovery image installed), and thus be able to make these nandroid backups. The nandroid backups then get saved onto the SD card to which you can transfer to your computer for safe keeping. This ensures you can revert to an official rom with previous settings applied in case of an awry custom rom installation. The nandroid backups can also be used for nonofficial roms that you've deemed stable when you tested them, and this can be done as many times as you want.
I'm not sure if I'm entirely right, but I believe I have the gist of it. If anyone can correct me for any errors or can elaborate more, please feel free to share After all, we're all new at one point, hopefully veterans of this will chime in and allow us all to learn!
Also, welcome to the forums! Glad to have you!!

alright, so if I understand correctly, I first need to root my phone to gain root access to perform these nandroid backups?
I'm using this guide" Get started rooting Telus HERO130! (No need for QMAT!)", I'd post a URL but it seems that since I am a new member I'm not allowed to post URL's. I've gotten up to step 6. When I run that RUU file it says its going to erase everything on the phone, so I decided its probably best if I backed up my phone before I try this in the event that I mess everything up horribly.
Is this possible without having root access to use the recovery image with nandroid on it? or am I just having another noob moment?
thanks for the help!

Help: reverting phone to factory settings (or at least make it look like it)

I'm getting my phone replaced because of dust under the screen, they said they would do it free and I would get a refurb (fine by me, I hate this ****ty dust). So I need to figure out how to revert the phone back to factory settings. I have my phone rooted and flashed with the recovery rom, and pancake 0.1 so what can I do to make it either back to factory or look like factory...

Did you do a nandroid backup before you upgraded it?

yup, i did, it's saved on my desktop, what do I do to use it ?

If you still have it copied on your SD card, boot into recovery, and do a nandroid restore.
If not, copy it back into the nandroid folder, then do a recovery boot and a restore.
That should get you back to where you were before the upgrade.

ok thanks, i'll give it ago and let you know

Good luck.

ok that worked, now there probably isn't a way to 'remove' root right ? I have a few root apps left over from before the nandroid backup I guess i'll just uninstall them and they probably won't be able to tell.

I don't think you can unroot without doing an RUU of the original ROM (I could be wrong). The reason I didn't point you in that direction initially is because a small set of people (of which I am one) had problems with their phone more or less bricking when putting that RUU on it. If you factory wipe the phone before you turn it in they'll have to actually look pretty hard to find it's been rooted. I doubt they'll bother, since if they can't fix what's broken they'll just send it back to sprint, and give you a refurb/new unit. If it looks like it used to (stock) they're not going to check any further than that.

thanks for the help . I'm sending it directly back to sprint, no one's going to be checking inbetween. Hopefully they just make sure it works and isn't water damaged and send it on it's way.

I'm sure that's all they'll do. As long as it looks like stock they won't have any reason to investigate further.

[Q] note 3 beginner questions before custom rom install

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

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

What to backup?

Which things should I select to backup in twrp?
Last time when I restored the backup I got stuck in the bootloader.

ZaKh10 said:
Which things should I select to backup in twrp?
Last time when I restored the backup I got stuck in the bootloader.
Click to expand...
Click to collapse
Everything!

This is the question that pisses me off every time I see it. Not because the OP asked it,,,but because no one ever really gives a good answer. Rather they give what they do. There are many devs out there who spend a crap load of time making TWRP and it would just be nice if they spoke up and ended this debate. Is it system_images, vendor_image, boot, and data? Some say no Vendor_image because that causes problems. Others say backup everything,,,well why backup everything and take up all that space if you dont need to? I backed up everything and got stuck in a bootloop when I restored. I have been doing android since day one and never seen so many answers to one question. Can just one TWRP dev speak up and give us a definitive answer, or do they not know as well?

Archangel said:
This is the question that pisses me off every time I see it. Not because the OP asked it,,,but because no one ever really gives a good answer. Rather they give what they do. There are many devs out there who spend a crap load of time making TWRP and it would just be nice if they spoke up and ended this debate. Is it system_images, vendor_image, boot, and data? Some say no Vendor_image because that causes problems. Others say backup everything,,,well why backup everything and take up all that space if you dont need to? I backed up everything and got stuck in a bootloop when I restored. I have been doing android since day one and never seen so many answers to one question. Can just one TWRP dev speak up and give us a definitive answer, or do they not know as well?
Click to expand...
Click to collapse
This X 1,000!
I've made different backups checking off different things to back up and I'm terrified of having to restore something! Let's just say I'm extra careful of any mod I flash in case I fu-- something up! Haven't had to restore a backup yet and will be shaking when I have to. I have read so much about it, but there is no clear answer and much of it is confusing. And maybe it's the blond girl in me but I remain confused about the A and B partitions - something else I need to read up on.
Wish TWRP devs would have an official message on what to back up and restore! :good:

exactly right! Plus I LOVE the people who say well just back up what they do and it was a fluke that it worked for them. I am like you now, I am very careful what mods I use because I know I will have to start over from scratch and redo my phone. For me I just use TWRP for flashing zips now thats all.
darbylonia said:
This X 1,000!
I've made different backups checking off different things to back up and I'm terrified of having to restore something! Let's just say I'm extra careful of any mod I flash in case I fu-- something up! Haven't had to restore a backup yet and will be shaking when I have to. I have read so much about it, but there is no clear answer and much of it is confusing. And maybe it's the blond girl in me but I remain confused about the A and B partitions - something else I need to read up on.
Wish TWRP devs would have an official message on what to back up and restore! :good:
Click to expand...
Click to collapse