Root Asus Memo Pad 176 on lollipop .36 newest firmware plus Xposed - MeMO Pad 7 General

***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

Related

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.

[SOLVED] Vibrant Root Concerns

Hey there. I rooted my Vibrant successfully, but realized I left some important things out. I used this guide to root my Vibrant: http://forum.xda-developers.com/showthread.php?t=723479
The problems:
1) I can't nandroid (not that I need to, I only have 4 apps)
2) I would like to install either Miui v4 or CyanogenMod 9 but cannot as my recovery screen does not show me the options to do so (I only get the 4 options you normally would get unrooted, such as "Reinstall Packages"), so I'm stuck with the lame default homescreen.
3) I'm currently on 2.1-update1; should I upgrade to 2.2? If so, must I unroot to upgrade, and then reroot? And if this were the case, how do you unroot, and can I reroot using the same method in the link above?
Also, I was looking at this guide: http://wiki.cyanogenmod.com/wiki/Sa...te_Guide#Installing_the_ClockworkMod_Recovery
and noticed the line "This guide assumes the Samsung Vibrant already has Android 2.2 build UVKB5 already installed on it."
Does this mean 2.2 is required to install the CWM Recovery?
Thank you.
I'm not sure how you don't have CWM recovery if you followed the guide as it is written. Maybe its because the 2.1 is updated? I would do the following and see if that's all it takes. You definitely don't want to update to stock 2.2 via Kies or anything of that nature.
Worst case scenario, we can have you Odin back to stock JFD. You'll be smooth sailing from there.
Search the forums and find the update.zip for CWM for our Vibrant.
Put that on the lowest level of your INTERNAL storage. Not your microsd card. For example f:\update.zip
Now go to your boring 4 option stock recovery and select reinstall packages. It will reboot to the same boring screen. Select reinstall packages again, and it will reboot into Clockwork Mod Recovery.
Let me know if that does anything for you. Also what version of stock recovery do you have?
Toast6977 said:
Search the forums and find the update.zip for CWM for our Vibrant.
Click to expand...
Click to collapse
Can pull that directly from my signature, if OP wants. (Only works on Eclair [JFD] build btw)
Also OP, You will have to have a ROM that you are going to want to flash saved on your Internal SD card. Jsut download it, put in a folder and follow the ROM OP's instructions. Since you are fresh and new, I would NOT suggest flashing anything of ICS or JB until you get the hang of things first.
Read, read and then read somemore. When it comes time to flash ICS or beyond, there is a guide in my signature. Good luck and make sure to hit Toast's "Thanks" button. He is a good asset to have around here.
Wow! I was hesitant to even check today, let it alone this early! Did not think that I would have two very useful replies waiting for me. Thanks guys, much appreciated!
I'll try the Odin thing out first before I even try to flash (you need root first before flashing, I'm assuming). Just out of curiosity, what is JFD and Odin? I'm still gonna try it out using the guides found here, but just curious.
EDIT: Damn, it worked like a charm! Now I have CWM. The mistake I made was that I only installed the Superuser/ROOT and not both. Gonna play with it for a bit now
I'm glad that your issue was solved
If you have any other questions/issues feel free to hit us up. We tend to lurk around these parts from time to time.
--you could now modify the title of this post to add [Solved] to the title or contact Oka1 and let him know it's case closed.--
Toast6977 said:
I'm glad that your issue was solved
If you have any other questions/issues feel free to hit us up. We tend to lurk around these parts from time to time.
--you could now modify the title of this post to add [Solved] to the title or contact Oka1 and let him know it's case closed.--
Click to expand...
Click to collapse
Thank you for teaching me the etiquette around here as well

[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

Successful Root and Unlock HTC One M8 with VZW Lollipop

Hey guys,
I have never posted a thread like this so please tell me if I have done anything wrong. I don't have enough time to write a proper guide but if someone wants to they are more then welcome. I take no credit for any of this information, I just took the risk and attempted an M7 root and unlock method on my M8. And it worked! But just a little differently. I followed the steps in this thread but with a few minor changes: http://forum.xda-developers.com/ver...root-root-method-bl-unlock-5-0-x-ota-t3122099
Okay so basically instead of using the mobile app of Kingroot I used the desktop version and had a much higher success rate. Once I gained temporary root for the first time I ran sunshine and finished all of the compatibility tests. The phone will reboot and you will need to re-root. Once you've gained root again run sunshine. It'll only take a couple of minutes. It may crash. That's fine you should now be unlocked. This is as far as I have gotten do to time constraints and not knowing exactly what recovery to flash. If someone knows please let me know! As stated in the original thread this is super finicky but will work. Just have some patience.
Also, I didn't get official software status. In case that's a problem for anyone.
My Phone:
VZW HTC One M8 running lollipop 5.0.1
Ill try to clean this up when I get home from work but I just wanted it to be out there so everyone knows. I will remove this thread if someone posts a better one. Thanks!
UPDATES?
i need this working bro, my m8 is pissing me off, king root wont work i followed all your instructions
also what version of kingroot did you have?
radiowavedev said:
Hey guys,
I have never posted a thread like this so please tell me if I have done anything wrong. I don't have enough time to write a proper guide but if someone wants to they are more then welcome. I take no credit for any of this information, I just took the risk and attempted an M7 root and unlock method on my M8. And it worked! But just a little differently. I followed the steps in this thread but with a few minor changes: http://forum.xda-developers.com/ver...root-root-method-bl-unlock-5-0-x-ota-t3122099
Okay so basically instead of using the mobile app of Kingroot I used the desktop version and had a much higher success rate. Once I gained temporary root for the first time I ran sunshine and finished all of the compatibility tests. The phone will reboot and you will need to re-root. Once you've gained root again run sunshine. It'll only take a couple of minutes. It may crash. That's fine you should now be unlocked. This is as far as I have gotten do to time constraints and not knowing exactly what recovery to flash. If someone knows please let me know! As stated in the original thread this is super finicky but will work. Just have some patience.
Also, I didn't get official software status. In case that's a problem for anyone.
My Phone:
VZW HTC One M8 running lollipop 5.0.1
Ill try to clean this up when I get home from work but I just wanted it to be out there so everyone knows. I will remove this thread if someone posts a better one. Thanks!
Click to expand...
Click to collapse
I'll work on creating a step by step when I get home. I've just been really busy. It's just a lot of trial and error but it should work at some point. Keep a look out for my reply tonight.
xercurial said:
i need this working bro
Click to expand...
Click to collapse
Such a polite way of asking someone to go out of their way to help you or write a guide for you.
lol sorry about that man i did however end up rooting it , now im having trouble
redpoint73 said:
Such a polite way of asking someone to go out of their way to help you or write a guide for you.
Click to expand...
Click to collapse
i am having trouble iwth twrp
xercurial said:
i am having trouble iwth twrp
Click to expand...
Click to collapse
Is there a question you are intending to ask?
And you need to describe the "trouble" exactly and precisely.
What version TWRP?
twrp issues
redpoint73 said:
Is there a question you are intending to ask?
And you need to describe the "trouble" exactly and precisely.
What version TWRP?
Click to expand...
Click to collapse
i have the one the ends with 7.0.1 i believe i cannot check right now, i am servicing it because i have to replace the jack and get a new housing which will take a coupe days to ship, i did however get root s off after trying for the longest time. my issue now is whenever i try to boot into the recovery, most of the time it will take me to stock or show the error triaangle which indicates there is none installed which there is (very frustrating) once in a blue moon however i will finally get into twrp and whenever i try to do a backup, it says failed or some kind of error. and EVERYTIME i try to reboot my system it would bootloop into recovery! and when that happens i would be forced to re install a rom and the whole proccess starts again. So i just stuck with the gpe rom basically and i tried to do a backup and the whole recovery issue just pissed me off so i just decided to to my hardware fix by replacing the frame and the headphone-charging port which ended up not being compatable with the verizon model so i had to re order (very frustrating) will probably by the at&t model at some point instead
anyways sorry for being rude earlier and thanks for your patience!
Alright, sorry that I lied about going home and typing up a step by step things are just hectic ya know? Anyways i'm here now so let me gather myself and get you some help. lol
xercurial said:
i have the one the ends with 7.0.1 i believe i cannot check right now, i am servicing it because i have to replace the jack and get a new housing which will take a coupe days to ship, i did however get root s off after trying for the longest time. my issue now is whenever i try to boot into the recovery, most of the time it will take me to stock or show the error triaangle which indicates there is none installed which there is (very frustrating) once in a blue moon however i will finally get into twrp and whenever i try to do a backup, it says failed or some kind of error. and EVERYTIME i try to reboot my system it would bootloop into recovery! and when that happens i would be forced to re install a rom and the whole proccess starts again. So i just stuck with the gpe rom basically and i tried to do a backup and the whole recovery issue just pissed me off so i just decided to to my hardware fix by replacing the frame and the headphone-charging port which ended up not being compatable with the verizon model so i had to re order (very frustrating) will probably by the at&t model at some point instead
anyways sorry for being rude earlier and thanks for your patience!
Click to expand...
Click to collapse
If I remember correctly all I did was go to twrp's website and download the most recent version for the VZW M8 (I think it might have just been one for all versions not sure) then installed it through adb and it has been working flawlessly. I since installed ViperOne without any problems. The version of twrp I got was 2.8.7.0. Once you get your phone going again i'd suggest reinstalling twrp through adb.
xercurial said:
i have the one the ends with 7.0.1
Click to expand...
Click to collapse
As noted by the previous response, you should get the latest version of TWRP (2.8.7.0) if you are on Lollipop firmware. TWRP versions 2.7 are known to be problematic on LP.
---------- Post added at 11:32 AM ---------- Previous post was at 11:07 AM ----------
radiowavedev said:
If I remember correctly all I did was go to twrp's website and download the most recent version for the VZW M8 (I think it might have just been one for all versions not sure)
Click to expand...
Click to collapse
You're correct, TWRP for CDMA (Verizon, Sprint) and GSM versions (most other M8 versions) was merged some time ago.

What LS997-compatible ROM contains *all* working LG Stock Apps?

So the whole reason I rooted this damn phone was to be able to install working stock apps. Not just the Music and Gallery apps either--ALL THE LG APPS. Which LS997-compatible 100%-working ROM can I flash and get them all, if any? I keep hearing one exists, but no one bothers sharing that info and when I search I find nothing.
Really? No one?
bgibson72 said:
Really? No one?
Click to expand...
Click to collapse
Look in the development section it's like the 5th one down has ls997 in the title
@bgibson72
Im the only person developing a STOCK LS997 rom currently.. It contains the LG base apps and all the removed ones that we didnt get shipped with out model . Includes a ton of extras as well, alternatively we have 3 or 4 aosp roms you can use, but make sure you use twrp and backup your efs before flashing as it tends to jumble your programming up and cause issues. Otherwise you can flash the stock rom the Dev who provided the dirty santa unlock method.
Theres a good bit of info here to locate everything you need to have a awesome experience with the LG V20!
My link
https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923
READ THE ENTIRE FIRST 3 POSTS!!! A LOT OF TIME WENT INTO THIS TO CLEAR UP ANY CONFUSION!
I also itemized a list of 15 or so mods and add-ons that we can use to increase our enjoyment with perspective links to their home locations and the devs that built and maintain them.
jerrycoffman45 said:
Look in the development section it's like the 5th one down has ls997 in the title
Click to expand...
Click to collapse
This one?
{ROMS}[LS997] Stock-ish Magisk+3minit+ModControl 3/10/17
Other than DirtySanta, this is the only other one with LS997 in the title on that page. I'll give it a shot, and thanks for answering.
Team DevDigitel said:
@bgibson72
Im the only person developing a STOCK LS997 rom currently.. It contains the LG base apps and all the removed ones that we didnt get shipped with out model . Includes a ton of extras as well, alternatively we have 3 or 4 aosp roms you can use, but make sure you use twrp and backup your efs before flashing as it tends to jumble your programming up and cause issues. Otherwise you can flash the stock rom the Dev who provided the dirty santa unlock method.
Theres a good bit of info here to locate everything you need to have a awesome experience with the LG V20!
My link
https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923
READ THE ENTIRE FIRST 3 POSTS!!! A LOT OF TIME WENT INTO THIS TO CLEAR UP ANY CONFUSION!
I also itemized a list of 15 or so mods and add-ons that we can use to increase our enjoyment with perspective links to their home locations and the devs that built and maintain them.
Click to expand...
Click to collapse
Hey thanks--I was fairly sure this was the ROM in question. Thank you for providing this! I was hesitant to flash because I'm always a little skeptical about the amount of help I'll get should I get stuck. I'm not exactly a noob at this, but I have plenty to learn. It looks like you've done a lot of work to provide a positive experience, so I'll give it a shot and see how it goes. I promise to read and re-read the instructions on the first 3 posts, and to NOT bother you with questions that have already been addressed in the thread. . Thanks!!
bgibson72 said:
Hey thanks--I was fairly sure this was the ROM in question. Thank you for providing this! I was hesitant to flash because I'm always a little skeptical about the amount of help I'll get should I get stuck. I'm not exactly a noob at this, but I have plenty to learn. It looks like you've done a lot of work to provide a positive experience, so I'll give it a shot and see how it goes. I promise to read and re-read the instructions on the first 3 posts, and to NOT bother you with questions that have already been addressed in the thread. . Thanks!!
Click to expand...
Click to collapse
if you made it through dirty santa the rest should be cake. 99% of the issues i covered for people were
after going to AOSP and not having a backup of their programing info in their efs and having to find a way to
manually go in and fix each fd up piece.
The other is being on older software and downloading a OTA and rebooting with it in your internal storage.
This one causes a endless boot loop into twrp, so be advised to delete the update if your on older software or be prepared to
hit my post # 3 for fixes and be near a pc as you need to fastboot erase the fota and misc directories to resolve the boot loop. A twrp wipe will not fix it and restores etc wont either lol.
Otherwise theres now a lil over 100 pages of chatting and troubleshooting, fixes and things that have gone on, and mostly its all outdated as ive provided the fixes for 99% of everything in the latest version 7.5
Just be prepared to take 15-20 minutes for the phone to boot up the 1st time. My rom is deodexed, and the 1st boot is doing 298 things before you get to the optimization part. There is not boot animations as the phone will always have the static screen issue on reboots so i went ahead a placed a disabled command there to just save time/batt life. The setup wizard is stripped and only there to give you the notice its done booting and time to get to playing around.
Magisk is kinda finicy being its systemless design. It takes some time to get used to it, and be aware that some older apps that dont support exotic root or systemless root may not request root and not fully work. Titanium backup is one i know is getting attacked by googles app scanning and needs to have that turned off before it will work, most of my apps have a option to set "force root" so it asks for a root request regardless if it understands MagiskSu's root methods.
just some food for thought. Hope everything goes well, and there is a ton of people on the forum here that have great knowlege and can help with troubleshooting issues you may have
Team DevDigitel said:
if you made it through dirty santa the rest should be cake. 99% of the issues i covered for people were
after going to AOSP and not having a backup of their programing info in their efs and having to find a way to
manually go in and fix each fd up piece.
Click to expand...
Click to collapse
Yeah, I didn't have many problems there, although I did get stuck in the TWRP loop once.
The other is being on older software and downloading a OTA and rebooting with it in your internal storage.
This one causes a endless boot loop into twrp, so be advised to delete the update if your on older software or be prepared to
hit my post # 3 for fixes and be near a pc as you need to fastboot erase the fota and misc directories to resolve the boot loop. A twrp wipe will not fix it and restores etc wont either lol.
Click to expand...
Click to collapse
I am on the ZV3 version of the software. I do have the ZV5 update in my cache folder--are you saying it's a good idea to delete the update.zip file?
Otherwise theres now a lil over 100 pages of chatting and troubleshooting, fixes and things that have gone on, and mostly its all outdated as ive provided the fixes for 99% of everything in the latest version 7.5
Click to expand...
Click to collapse
That's what I like to hear! :good:
Just be prepared to take 15-20 minutes for the phone to boot up the 1st time. My rom is deodexed, and the 1st boot is doing 298 things before you get to the optimization part. There is not boot animations as the phone will always have the static screen issue on reboots so i went ahead a placed a disabled command there to just save time/batt life. The setup wizard is stripped and only there to give you the notice its done booting and time to get to playing around.
Click to expand...
Click to collapse
Appreciate the heads up. Familiar with the long boot process from DS, lol.
Magisk is kinda finicy being its systemless design. It takes some time to get used to it, and be aware that some older apps that dont support exotic root or systemless root may not request root and not fully work. Titanium backup is one i know is getting attacked by googles app scanning and needs to have that turned off before it will work, most of my apps have a option to set "force root" so it asks for a root request regardless if it understands MagiskSu's root methods.
Click to expand...
Click to collapse
Magisk is a new animal for me, as I've had zero experience with it. I do have Titanium Backup installed, so I'll make a mental note on that.
just some food for thought. Hope everything goes well, and there is a ton of people on the forum here that have great knowlege and can help with troubleshooting issues you may have
Click to expand...
Click to collapse
Thanks again--I appreciate your hard work and dedication to this!
bgibson72 said:
Yeah, I didn't have many problems there, although I did get stuck in the TWRP loop once.
I am on the ZV3 version of the software. I do have the ZV5 update in my cache folder--are you saying it's a good idea to delete the update.zip file?
YES, dont boot into twrp until you remove it, or its back into the twrp loop you go hehe
Click to expand...
Click to collapse
Team DevDigitel said:
bgibson72 said:
Yeah, I didn't have many problems there, although I did get stuck in the TWRP loop once.
I am on the ZV3 version of the software. I do have the ZV5 update in my cache folder--are you saying it's a good idea to delete the update.zip file?
YES, dont boot into twrp until you remove it, or its back into the twrp loop you go hehe
Click to expand...
Click to collapse
Weeeeeeeeeeeeee!!!
Will do!
Click to expand...
Click to collapse

Categories

Resources