Just received insurance replacement H91810j, root strategy? - LG V20 Questions & Answers

So I had to get a warranty replacement phone about 3 weeks ago and got stuck on 10r with no chance of root (was following the LAF thread but I guess that hit a pretty hard wall; little above my technical knowledge but I think that's the current end result) and for the second time in my life I broke a screen (before I'd even sent back the original phone from the warranty swap). I was all kinda pissed at myself for trashing a brand new to me phone, but the silver lining may be that the insurance replacement phone came with H91810j so root may be back on the table.
I apologize for asking something I could probably find from RTFF but I've been out for a while and it's a little complex to find info on root/upgrade path for such an older build. So the question is, what do I do now? Root immediately? Upgrade to a newer build but pre-10p then root?
Any help is much appreciated (including "hey dumbass, here's the thread that answers this exact question, why didn't you RTFF?!?!").

Hey erikk,
I believe you can still root it using recowvery, but there might be a few extra steps as per this post: https://forum.xda-developers.com/v20/how-to/instruction-to-root-h918-10i-t3536472
As long as your Anti-rollback version still shows 0 you'll be okay to go ahead and root.
If you don't mind - can you share with me the files in your data/ipsec/wo folder? I'm trying to figure out T-Mobile VoLTE/WifiCalling on an H990DS.
Thanks!

So I got impatient and RTFF and was able to find what I thought was the best way through, so I thought I'd help anyone else who gets into the same situation in the future.
I first rooted on H91810j following this:
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
This thread (https://forum.xda-developers.com/v20/development/lg-h918-t-mobile-one-click-recowvery-t3491969) has a bundled, do it for you version of the above, but the above was updated after the all-in-one thread and personally I felt more comfortable using the non-simplified method. But if you don't understand ADB or the stuff in the manual version, the do it for you version is probably better for you.
I then upgraded to 10r using the following:
https://forum.xda-developers.com/v20/development/rom-h91810q-stock-rom-twrp-flashable-zip-t3681312
I will mention one thing that was a tad bit unclear in the guide that freaked me out at the time. You need to put the latest SuperSU or no-verity-opt-encrypt and the H91810r img on your microsd card and in the phone BEFORE starting. Step 3 has a step:
Flash the latest zip from https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ to turn off forced encryption at boot and allow you to boot a modified system. If you're flashing SuperSU.zip, it will also do this for you so this won't be necessary.
Warning: If you don't flash either no-verity-opt-encrypt or SuperSU, you will probably end up in a horrifying never-ending boot loop of "corruption"!
Click to expand...
Click to collapse
Well I got there and I hadn't put the files on my SD card and I flipped out thinking I was screwed; the sd card wasn't even inserted in the phone. I was able to put the files on and hot insert the sd card but I was terrified I'd just bricked my second brand new replacement.

Boxy52 said:
Hey erikk,
I believe you can still root it using recowvery, but there might be a few extra steps as per this post: https://forum.xda-developers.com/v20/how-to/instruction-to-root-h918-10i-t3536472
As long as your Anti-rollback version still shows 0 you'll be okay to go ahead and root.
If you don't mind - can you share with me the files in your data/ipsec/wo folder? I'm trying to figure out T-Mobile VoLTE/WifiCalling on an H990DS.
Thanks!
Click to expand...
Click to collapse
Hey Boxy, thanks for the reply. I actually had my just previous reply almost completely written and hadn't submitted it but your reply jogged me to finish it.
I'm happy to share the files with you if they'll help now that they're the 10r versions?

erikk said:
Hey Boxy, thanks for the reply. I actually had my just previous reply almost completely written and hadn't submitted it but your reply jogged me to finish it.
I'm happy to share the files with you if they'll help now that they're the 10r versions?
Click to expand...
Click to collapse
Hey, glad it worked out!! Sorry I didn't get to your thread sooner... looks like you found better info than I did anyway I actually bricked an H918 that was on 10q before I got this H990DS as a replacement... so I was certain you'd be okay if you weren't on 10p or 10q, haha.
Yes, please! I'd love if you could dump the files for me. Can you also check what the permissions are in that folder? Thanks! Also, if you could show me your APNs.

Related

Root Status

Well, I've asked a mod to lock the other root status thread. It was getting kind of out of hand. After about page 80, people stopped looking at what we had done so far, and trying to help by putting ideas out that already failed.
This is what we know:
Fastboot is locked down in everything but oem-78 mode. You can get to this mode by typing "reboot oem-78" at an adb shell. Fastboot is essentially unlocked, allowing fastboot boot and fastboot flash, only the .img images we try to boot or flash NEED TO BE SIGNED.
Goldcards no longer allow non signed firmware to be loaded, only signed firmware with a different SID.
All known flashing methods require the .img files to be signed by HTC. We do not have the privatekey, nor do we have any way to decrypt the key as it is RSA. Meaning this is a NO GO.
All previous known exploits (asroot2, g1 telnetd, DROID update.zip method) have been patched. They won't work. And there isn't a way around this.
All the partitions except /data are mounted as read only. Meaning, without root access, there is NO way to modify them. In the init.rc file, they are mounted rw, and directly after that mounted ro. We can read and write to /data as we wish, but NOTHING important is here.
The only folder anything can run as root out of is /system/bin. Every other partition is mounted with the nosuid option, meaning code CANNOT be run as root. Simple enough. We can't run anything as the user root, or the group root.
Lets try to stay a little more on topic this time. Please don't let this become another 40 pages of complete crap. And please keep this thread about root access, any other problems should be posted in the appropriate forum.
Thanks, and lets get this root done!
I'm currently comparing superboot.img in a hex editor to the vanilla boot.img for that phone so I can better understand what he did, and how. I'll see what I can turn up, maybe we can make one for the eris.
EDIT: It seems it's not going to be so easy. There's a lot of things changed. It appears he changed something at the top of the file right after the header, and then there is some sort of (SHA1?) hash right below that, but I don't know what it's calculated from. This is beyond my skills at the moment, I think.
Are any of the fields changed from the original boot.img show up in our boot.img? Chance of searching for each field in our img and replacing with possibly what he did?
is it possible that the guy who made superboot has htc signature, or somehow decrypted it???? 8-O
Yes I guess anything is possable but I think their is a better chance of monkeys flying out of my butt.
well i guess it was time to lock the other thread as some people could not play nice..... so i guess we will use this one now..... next idea anyone, and i am guessing jman will no longer be joing us, so it looks like we are on our own.
im ready to get this done what have we got so far?
About 140 pages of failed attempts.
well i know that much i have been sitting back following from the begining now im ready to get my hands dirty, though i have no clue what im doing
binny1007 said:
well i guess it was time to lock the other thread as some people could not play nice..... so i guess we will use this one now..... next idea anyone, and i am guessing jman will no longer be joing us, so it looks like we are on our own.
Click to expand...
Click to collapse
Ok, I missed something I think. Thats what I get for not refreshing every 10 seconds What happened to jman? Or is it better off that I not ask
punk.kaos said:
Ok, I missed something I think. Thats what I get for not refreshing every 10 seconds What happened to jman? Or is it better off that I not ask
Click to expand...
Click to collapse
I don't think I'll be following these threads anymore. I try to help you guys, but in the end some of you just don't appreciate the help.
I don't claim to be an expert, and I never promised anybody that I could root their phone. I simply have information to share that I think has brought you guys to a greater understanding of your phones and the Android system. Most of you are thankful, but I really don't need to be attacked personally in these threads that don't even have anything to do with my phone.
I'd like to thank the moderator for locking down the other forum, I'd also like to thank whichever moderator deleted the message that was quite insulting to me.... I only happened to see it because it came into my email. Yes, I subscribed to the thread via email to try to keep up with you guys and offer any help I could as quickly as I could.
I'm sorry guys, I wish you luck, but I just don't need to be berated in open forum like that for trying to help the Eris owners out, so I won't be keeping up with your rooting efforts.
There are a couple of you that have been very appreciative, and please feel free to PM me.
Thanks jman and I understand, if I was in your shoes I would do the same and I reported that post almost right after it was posted hoping you would not see it. But I know for me I have a greater understanding of my phone and like I have said before Thank you very much for your help. It's a shame to see you go but we understand.
Binny
doubt this will help, its all that htc tech support would throw up at me.
http://developer.htc.com/
contains hero and adp but nothing about eris.
jmanley69 said:
I don't think I'll be following these threads anymore. I try to help you guys, but in the end some of you just don't appreciate the help.
I don't claim to be an expert, and I never promised anybody that I could root their phone. I simply have information to share that I think has brought you guys to a greater understanding of your phones and the Android system. Most of you are thankful, but I really don't need to be attacked personally in these threads that don't even have anything to do with my phone.
I'd like to thank the moderator for locking down the other forum, I'd also like to thank whichever moderator deleted the message that was quite insulting to me.... I only happened to see it because it came into my email. Yes, I subscribed to the thread via email to try to keep up with you guys and offer any help I could as quickly as I could.
I'm sorry guys, I wish you luck, but I just don't need to be berated in open forum like that for trying to help the Eris owners out, so I won't be keeping up with your rooting efforts.
There are a couple of you that have been very appreciative, and please feel free to PM me.
Click to expand...
Click to collapse
Thanks for sticking through with us. You've been extremely helpful since day one, and I would like to say thanks and basically say what Binny said above.
I haven't had a lot of time to follow the thread, but, I too, am happy that it was locked. Hopefully the Eris owners can regroup in a day or so after we all chill out. Sigh. Fingers are still crossed for root.
Has anyone been able to actually BOOT any of the images extracted from the rom.zip via fastboot in oem-78 mode? If so, and you could post how, I might have access to an image with root access. I've tried repeated times to perform "fastboot boot recovery.img" but it sends it and then sticks on "booting..." I have moved forward with the RUU at this point, but the device never actually boots into the img.
Unfortunately, I cannot not upload the image due to my job.
Also, if anyone can help with goldcard downgrading, I might be able to downgrade to an old version with root access. My downgrade continues to fail due to the bootloader version being too high. I created the goldcard per the appropriate thread and it appeared to work as the Cell South thread indicated, but still no dice on the downgrade.
If your gold card is made right it should work.... are you putting the .zip on you gold card and renameing it PB00IMG.zip?
binny1007 said:
If your gold card is made right it should work.... are you putting the .zip on you gold card and renameing it PB00IMG.zip?
Click to expand...
Click to collapse
Yes, but it still fails with error 43, I believe. "Main version check"
Did you run the simlock option in the bootloader, and it passed
binny1007 said:
Did you run the simlock option in the bootloader, and it passed
Click to expand...
Click to collapse
Yes. Perhaps goldcard doesn't work on this device like it's supposed to.

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.

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

ZTE Axon 7 USA Bootloader/TWRP/Update Help

So here's my story,
I bought this Zte phone off someone on craigslist a couple of weeks ago, and I've loved it every since. In fact, I have yet to turn it off, I've kept it on the entire time. Today the new update 29 came out for the US, and I tried downloading. To my dismay when the phone restarted I was greeted with a bootloader screen, and then a TWRP screen. I freaked out and panicked and emailed the guy I bought the phone from since I heard that unlocking bootloader on your phone voids the warranty. He told me he had done it in such a way OTA framework that it didn't void the warranty and also I can always relock the phone but be careful because I might brick it. I'm not a very tech savvy person and have no idea what to do to relock the phone so I can download this new update. Could someone please help me out and walk it out with me step by step so I know what to do. Thanks so much guys!
Look in the section rooms, recoveries,etc... look for one the says roms update stock DrakenFX
Since you are not tech savvy, you could just keep it unlocked and use those twrp flashable files to update B29.
http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
credit: @DrakenFX
However If you will wish to restore to locked state without twrp, I will be happy to guide you but you'll have many more steps to do.
Nik2424 said:
Since you are not tech savvy, you could just keep it unlocked and use those twrp flashable files to update B29.
http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
credit: @DrakenFX
However If you will wish to restore to locked state without twrp, I will be happy to guide you but you'll have many more steps to do.
Click to expand...
Click to collapse
I would much rather just restore to locked state without twrp so I don't have to worry about this situation again. I don't need bootloader or twrp and just wanna remove both. Would you please guide me through this?
ctran1996 said:
I would much rather just restore to locked state without twrp so I don't have to worry about this situation again. I don't need bootloader or twrp and just wanna remove both. Would you please guide me through this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/axon-7/how-to/b20-factory-image-posted-t3492552 click the link in this post. It will take you to the ZTE site with the official B20 firnware. You flash this in stock recovery and you will have a fully locked Axon 7.
tabletalker7 said:
http://forum.xda-developers.com/axon-7/how-to/b20-factory-image-posted-t3492552 click the link in this post. It will take you to the ZTE site with the official B20 firnware. You flash this in stock recovery and you will have a fully locked Axon 7.
Click to expand...
Click to collapse
How do I flash to stock recovery with teamwin keeps popping up and restarting and not allowing me to flash it?
ctran1996 said:
I would much rather just restore to locked state without twrp so I don't have to worry about this situation again. I don't need bootloader or twrp and just wanna remove both. Would you please guide me through this?
Click to expand...
Click to collapse
If you're not tech savvy, you probably don't want to do this. It's not simple and for whatever reason, some people (who would consider themselves more tech savvy) have had some issues.
Your best bet is to copy all of your data from internal memory (just in case), flash a new copy of TWRP (recovery only, you don't need to do boot) using tenfar's tool (http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204), then follow the steps in DrakenFX's thread to get B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
I'm happy to write you a guide for getting back to bone stock, but I'm not going to do it until next week when I have time at work and as I said earlier, some folks have had issues. For what it's worth, you likely won't hard brick the phone. So far, we've only seen soft bricks AFAIK.
rczrider said:
if you're not tech savvy, you probably don't want to do this. It's not simple and for whatever reason, some people (who would consider themselves more tech savvy) have had some issues.
Your best bet is to copy all of your data from internal memory (just in case), flash a new copy of TWRP (recovery only, you don't need to do boot) using tenfar's tool (http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204), then follow the steps in DrakenFX's thread to get B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
I'm happy to write you a guide for getting back to bone stock, but I'm not going to do it until next week when I have time at work and as I said earlier, some folks have had issues. For what it's worth, you likely won't hard brick the phone. So far, we've only seen soft bricks AFAIK.
Click to expand...
Click to collapse
Are they really hard to follow?? I mean my guides?
If I could I love to redo Tenfar tool guide ,but don't think he will allow me recreate that thread in a more clean way (guide wise)
ctran1996 said:
How do I flash to stock recovery with teamwin keeps popping up and restarting and not allowing me to flash it?
Click to expand...
Click to collapse
http://www.mediafire.com/file/1jw9b24glt5fd7t/recovery.img put this on your SD card
Boot to TWRP
Push Install (top left)
Push Install Image (bottom right)
find the recovery.img and push it - TWRP will install it for you.
Then reboot into recovery.
You will now be in stock recovery and can use it to install update from SD card and install the B20 firmware from ZTE
BE WARNED - THIS WILL FACTORY RESET YOUR PHONE WHEN YOU ARE DONE!!!!!
DrakenFX said:
Are they really hard to follow?? I mean my guides?
If I could I love to redo Tenfar tool guide ,but don't think he will allow me recreate that thread in a more clean way (guide wise)
Click to expand...
Click to collapse
Hah, no, your guides are not hard to follow. They're great
I think the bigger problem is that there are a lot of threads to wade through and there are various posts within in each thread that address specific issues users have run into. If someone who claims not to be "tech savvy" doesn't understand something in your thread (not because it's unclear but because they have zero experience with this and need some hand-holding) and then happens to read something else in the thread and tries that, it can get messy.
rczrider said:
Hah, no, your guides are not hard to follow. They're great
I think the bigger problem is that there are a lot of threads to wade through and there are various posts within in each thread that address specific issues users have run into. If someone who claims not to be "tech savvy" doesn't understand something in your thread (not because it's unclear but because they have zero experience with this and need some hand-holding) and then happens to read something else in the thread and tries that, it can get messy.
Click to expand...
Click to collapse
That is my problem entirely! I AM tech savvy as I have worked as a Microsoft/VMware Systems engineer for over 20 years and when I try to make heads or tails of doing some of the things necessary to flash a ROM, or root, or unlock the bootloader.... after my eyes glaze over I just stick with Nova Prime and hope the original manufacturers get everything worked out. What's really needed is a well written manual detailing step-by-step basics on what all these various things do as well as how to do them. Then more specific guides on a per phone basis. I know, it's asking too much! LOL :silly:
ctran1996 said:
So here's my story,
I bought this Zte phone off someone on craigslist a couple of weeks ago, and I've loved it every since. In fact, I have yet to turn it off, I've kept it on the entire time. Today the new update 29 came out for the US, and I tried downloading. To my dismay when the phone restarted I was greeted with a bootloader screen, and then a TWRP screen. I freaked out and panicked and emailed the guy I bought the phone from since I heard that unlocking bootloader on your phone voids the warranty. He told me he had done it in such a way OTA framework that it didn't void the warranty and also I can always relock the phone but be careful because I might brick it. I'm not a very tech savvy person and have no idea what to do to relock the phone so I can download this new update. Could someone please help me out and walk it out with me step by step so I know what to do. Thanks so much guys!
Click to expand...
Click to collapse
OK. Step by Step to get it back to B20
1) Move anything you want to save off your internal storage to your sd card or computer.
2) Download B20 image button.
3) Save file to SD card
4) Boot into Recovery by shutting it down and then push Volume Up Button+Power Button
5) When screen comes up boot into Recovery
6) in TWRP click Install, choose Select Storage, Choose Micro SDCard, Locate your update.zip file and click it
7) Swipe to confirm flash
WARNING: This will clean out your phone and turn it to B20. @DrakenFX can tell you how to not wipe the internal storage if you want to edit the update.zip file.
Hope this helps.
Thank you this is exactly what I was looking for. However, when I tried this the other day, it reset my phone as planned, but TWRP and bootloader were still on there. Any way of getting them off?
swehes said:
OK. Step by Step to get it back to B20
1) Move anything you want to save off your internal storage to your sd card or computer.
2) Download B20 image button.
3) Save file to SD card
4) Boot into Recovery by shutting it down and then push Volume Up Button+Power Button
5) When screen comes up boot into Recovery
6) in TWRP click Install, choose Select Storage, Choose Micro SDCard, Locate your update.zip file and click it
7) Swipe to confirm flash
WARNING: This will clean out your phone and turn it to B20. @DrakenFX can tell you how to not wipe the internal storage if you want to edit the update.zip file.
Hope this helps.
Click to expand...
Click to collapse

From Root to Pure Nexus (7.1.2)

Requesting guidance before I brick my phone.
I currently have bootloader unlocked, twrp installed, and my nexus 6p rooted. I'm running 7.1.2. I've also changed a line in the (build.prop) provisions in order to tether free (since I am on at&t)
Basically, I'm wanting to install pure nexus. I have the custom rom file and the vendor image file.
Before I install from, I'm wondering if I need to unroot first? Also curious if how "shamu" will affect things since I'm on Angler.
Thanks!
Okay you need to stop everything you're doing and read this topic until you know what is what.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page577
First of all, you obviously wouldn't flash a Shamu package on Angler. That's a great way to brick your phone, permanently.
Read every single step in that guide above, even if you don't think it's pertinent to what you're trying to do. Read it a second, third, fourth, fifth time until you know the steps by heart. Until you know what's next.
Also, download the correct Angler zip file and DO NOT FLASH A SHAMU ZIP ON YOUR PHONE.
help
RoyJ said:
Okay you need to stop everything you're doing and read this topic until you know what is what.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page577
First of all, you obviously wouldn't flash a Shamu package on Angler. That's a great way to brick your phone, permanently.
Read every single step in that guide above, even if you don't think it's pertinent to what you're trying to do. Read it a second, third, fourth, fifth time until you know the steps by heart. Until you know what's next.
Also, download the correct Angler zip file and DO NOT FLASH A SHAMU ZIP ON YOUR PHONE.
Click to expand...
Click to collapse
Any help on flashing back to stock using TWRP? I unlocked the bootloader and rooted my device (never made a backup till after but still proved to be of no help as it wont work when trying to restore) lesson learned for sure. but i cant boot the device up however i still have access to twrp recovery how can i go back to stock so i can start from scratch?? :crying:
Filly2 said:
Any help on flashing back to stock using TWRP? I unlocked the bootloader and rooted my device (never made a backup till after but still proved to be of no help as it wont work when trying to restore) lesson learned for sure. but i cant boot the device up however i still have access to twrp recovery how can i go back to stock so i can start from scratch?? :crying:
Click to expand...
Click to collapse
You can follow the original advice I posted above. Read that thread I linked. It's ALL covered there. No sense in me writing everything up here when all you need to do is click the link I posted and follow the return to stock sections. There's even one for maintaining your data. Read the thread. It covers literally everything.
..
RoyJ said:
You can follow the original advice I posted above. Read that thread I linked. It's ALL covered there. No sense in me writing everything up here when all you need to do is click the link I posted and follow the return to stock sections. There's even one for maintaining your data. Read the thread. It covers literally everything.
Click to expand...
Click to collapse
Sorry I don't mean to bug man but I'm so lost. I'm trying to find what you are referring me to but I'm not finding the info I need I haven't been on here too often so this is like a pain in my rear so far. Plus I'm a very hands on kinda learner so I need some like handicapped help lol If you don't mind I don't want to pester anyone...
I was able to load pure Nexus. I didn't realize there was a pure nexus rom with Angler on it.
My main question was if I had to reverse the root. But I'm good to good now.
Rom loaded, vendor image loaded, and Google Apps loaded.

Categories

Resources