There are how-tos from 2012 about using Voodoo to store root access (like squirrels storing their nuts for the winter) but is there a better way now? ... Am I wrong in anticipating a problem here?
9.18.94.XT926.Verizon.en.US with saferoot
Thanks
I wouldn't take the OTA until someone figures out a way to root the OTA, and that doesn't look very promising. Honestly, I don't think Voodoo will help out here, either.
RikRong said:
I wouldn't take the OTA until someone figures out a way to root the OTA, and that doesn't look very promising. Honestly, I don't think Voodoo will help out here, either.
Click to expand...
Click to collapse
Guess I could educate myself about how Saferoot works, but ... I'm still learning Java! Will be a while before I know how things _really_ work.
Thanks
From the play store:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For the unlocked fellows and fellowettes out there, it's as simple as 1) unrooting, 2) taking OTA, and 3) flashing SuperSU in TWRP / CWM to regain root access, correct?
LifeAsADroid said:
For the unlocked fellows and fellowettes out there, it's as simple as 1) unrooting, 2) taking OTA, and 3) flashing SuperSU in TWRP / CWM to regain root access, correct?
Click to expand...
Click to collapse
As long as you haven't frozen or removed any other system apps, then yes. I usually just do a clean wipe and install with RSD Lite since I remove all kinds of crap when I use stock.
And yeah, you can always flash SuperSU in recovery if your bootloader is unlocked.
/e: On second thought, take that first sentence with a grain of salt. I realized I've never actually taken an OTA the traditional way with a custom recovery installed. It seems like that wouldn't work properly.
killrhythm09 said:
As long as you haven't frozen or removed any other system apps, then yes. I usually just do a clean wipe and install with RSD Lite since I remove all kinds of crap when I use stock.
And yeah, you can always flash SuperSU in recovery if your bootloader is unlocked.
/e: On second thought, take that first sentence with a grain of salt. I realized I've never actually taken an OTA the traditional way with a custom recovery installed. It seems like that wouldn't work properly.
Click to expand...
Click to collapse
Holy cow, I am thanking you all over the place tonight! Such great useful information you have! I was wondering if you wouldn't mind explaining in a little more detail what you mean by "clean wipe and install with RSD Lite". I have a feeling I may or may not have deleted something important along the way. I know I have frozen things in TiBu (which I can defrost, update, and re-freeze or finally delete since this will be our last update from Motorola), and I don't think I have deleted any of the system files as of yet, but I am pretty certain I have modified system files (changing things in SystemUI, etc) for certain mods.
In case the modded files forbid me from taking the OTA, could you explain a little about how you clean wipe and install with RSD Lite?
After final install of KitKat (by whichever method), if I have clean wiped, I'll lose my photos, messages, etc, yes? Is there a way to save that stuff? TiBu backup of the "text messaging" app or the "gallery" app perhaps?
I promise you I am not thread-stalking you around XDA, but thanks again for all your time tonight!
RSD Lite is a software tool you install on your PC to flash Motorola phones in fastboot. If you ever see an fxz package (which I think stands for fastboot xml zip) they can be used by RSD Lite to basically restore your phone to stock. They usually come with a file with different sections that you can comment or uncomment if you only want to flash specific partitions (i.e. only the modem, or just the kernel).
There's probably a better solution for backing up, but I just use TiBu and then copy everything off my internal storage & SD onto my PC temporarily, then copy it back after. I do it so infrequently that I haven't bothered to figure out a better way, sorry.
/e: Meant to include this site, since it has lots of different firmware releases that you can use with RSD Lite:
http://sbf.droid-developers.org/phone.php?device=5
If you have any other questions, let me know.
LifeAsADroid said:
For the unlocked fellows and fellowettes out there, it's as simple as 1) unrooting, 2) taking OTA, and 3) flashing SuperSU in TWRP / CWM to regain root access, correct?
Click to expand...
Click to collapse
1.5) flash stock from custom recovery.
Note m recovery is in my button goodies. I think hd & m share the same img. Check the md5.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
Voodoo root keeper will work for easy unroot but not for keeping root beyond 4.2.
I personally won't take the update until sometime figures out a way to have root in kit kat.
LifeAsADroid said:
In case the modded files forbid me from taking the OTA, could you explain a little about how you clean wipe and install with RSD Lite?
Click to expand...
Click to collapse
The best solution is to use SamuriHL's House of Moto tools. You must read, read again, and read one more time before installing and using the tool. Once it's set up correctly, it is very easy to use. You can get it here -> http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20-for-now/
Read the OP in the thread first. Again, read it and then once more, as he states. The instructions are all there, but you have to read through them entirely before you attempt to use the tools.
I use this all the time when I'm ready to flash back to stock after being on a custom ROM when a new OTA comes out.
I use Titanium Backup to backup all my apps and data to my external SD card.
I use Backup to Gmail app to backup my call log, sms and mms messages so I can restore them later.
I backup my contacts and such to Google as well.
I use Listables to generate a list of the apps I had installed. I have so many that I sometimes forget which ones I used.
After that, I use HoM to flash back to stock and then reinistall TiBu to restore my apps.
Then, I use HoM to flash back the custom recovery (TWRP in my case) and flash root back onto my device (I'm unlocked so I don't have to use an exploit).
However, it would be best to hold off on root if you are wanting to obtain the OTA, unless of course you are using a locked device. Then, you might want to hold off until it's determined if there is a root exploit that will work.
Even though I'm unlocked, I'm going to wait and make sure they don't find a way to relock it. I don't believe they can since it was a physical change in the device (blown fuse - can't unblow it - is that a real word?)
That's it.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ShiftRRv1.0
Shift Root and Recovery will be able to root you're phone in a pretty safe manner. The program is designed to only flash the eng boot if the MD5 checksums are correct.
This does it by simply pushing / pulling the hboot from the phone and checking the MD5 as if you were to manually do it. Only this just does it automatically.
Check Root:
This will just run a quick and simple SU test to make sure you are or are not rooted.
Root:
You will click on this to install the ENG Hboot and load the correct files after the Hboot has been flashed.
Install Recovery:
You simply select the recovery image you want to use with your HTC Evo Shift. Leave the phone at the home screen and click install. It will auto reboot you to bootloader, flash the zip then auto reboot you to recovery to make sure it flashed successfully.
Backup / Restore WIMAX:
This option lets you quickly and easily backup your wimax keys to your home pc. It will also let you restore your wimax keys to your phones partitions.
[WHAT THIS PROGRAM DOES]
When you click on root, and click "NO" for this phone does not have a ENG Hboot. The program push's the ENGHboot from the Hboot folder to the phone and push's busybox. From there it gets a temp root shell. It then cross checks the MD5sum on the phone itself using busybox md5sum /data/local/eng_hboot if the MD5Sum math's it then proceed's with the dd if cmd. Once the dd if cmd is done. The program then sends the dd if cmd to /data/local/eng_hboot_check, it runs the cmd busybox md5sum again and verifies that the MD5Sum matches if so everything went well, the program cleans up its mess off the phone and alerts you its safe to reboot. IF IT FAIILS it will try 1 more time. The program is designed to check the HBOOT md5sum and verify if its the ORIG hboot if it is not and the MD5Sum doesn't check between the ENG and ORIGINAl it will attempt to flash the original and notify you if it succeeds. IF IT FAILS AGAIN. IT WILL NOTIFY YOU NOT TO TURN OFF YOUR PHONE AND COME HERE FOR FURTHER INSTRUCTIONS. I ADVISE YOU TO LISTEN.
After this YOU MUST REBOOT THE PHONE.
When phone is powered up again Click Root again this time select "YES" that the phone has a ENGHboot, this will get temp root again and push all the needed files, "SQLITE3", "BusyBOX", "SU", "Superuser.apk" to there proper location.
If YOU CLICK "YES" and didnt have the ENG Hboot thats fine it simply will temp root you and push files to your phone, but when you reboot they will be gone. Just start from the begining again and do it again.
Download V1 Here
DOWNLOAD NOW HERE
User's having trouble opening the application please download the latest dotNET framework from:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0a391abd-25c1-4fc0-919f-b21f31ab88b7
THIS IS FOR XDA MEMBERS ONLY. PLEASE DO NOT POST IN OTHER FORUMS AND PLEASE DO NOT MIRROR THE PROGRAM.
download link added
Image of program added.
Reserved...
Thanks for sharing. No need for me to try it now but if I ever replace or need to re-root. Really like the option to backup wimax keys too.
Looks great but too bad I don't need it! Like the option to back up wimax, but what about restoring them!?
Im giving this a try now
It "did its thing" after rebooting the program is still "waiting" and the phone is booted. Hmmm help?
xstingstreetx,
Can you give me more information?
Were you trying to root, or where you trying to do recovery?
Version of windows as well?
ahhhh!! I'm back 2 download it and.. well I'll wait again lol Thanks a lot for this..
I RUUed my phone and Wanted an easy way to re-root..
working?
other than the OP has anybody got this to work properly?
amoamare said:
xstingstreetx,
Can you give me more information?
Were you trying to root, or where you trying to do recovery?
Version of windows as well?
Click to expand...
Click to collapse
I was trying to root, and I have windows 7 64 bit
Where is the link ! someone please give me the file , pretty please please please been waiting for this !!!
I don't know if this is what it's trying to achieve or not. I don't know how to do it either. Judging by all my previous phones, an all in one script could be written to do everything the s-off, root, and recovery post is telling how to do. Just a "simple" batch file and some support files and presto, it's all done!
Zip everything needed together and just unzip and run. I could probably teach myself by ripping apart other all in one packages and adjusting my port to follow loosely what they are doing but I just don't have the free time to spend on that project. By the time I would get around to doing it, someone else would have finished it. I just don't know things like telling the phone to reboot into different modes so it could continue it's job. I can visualize it in my head but making it a reality is completely different. Doh!
Anyone know where the download link went? I've been having trouble with rooting my phone and wanted to try this, but theres no download link in the first post (unless my computer decided to stop showing links).
Link was removed temporarily. Learn to read guys, sheesh
On a side note, I'm pretty psyched about this OP, since I haven't had the ambition to sit down and root my phone yet. Just curious, are there any files that would need to be downloaded prior to using this (such as the ****-root.zip used in the other root method)?
Oops, saw everything except "removed temp..." in the first post.
It looks like there isn't anything extra that needs to be downloaded. Looks like the OP figured out a way around it.
SirRipo said:
Link was removed temporarily. Learn to read guys, sheesh
On a side note, I'm pretty psyched about this OP, since I haven't had the ambition to sit down and root my phone yet. Just curious, are there any files that would need to be downloaded prior to using this (such as the ****-root.zip used in the other root method)?
Click to expand...
Click to collapse
Possibly the recovery files ( clockworkmod 2.x or 3.x ) and have HTC sync set up to even connect the phone I would guess.
Sent from my PG06100 using XDA App
Sorry guys will work on this again in a few days girl is supposed to be going in to labor today...
On the side note the issue that I ran into is that running rageagainstthecage from the windows side does not give you root. It actually disables usb connection between the phone and the computer. I was trying to make this so you didnt need anything other then the program. But now with that being a problem z4root would be needed to obtain at least temp root but if i doesnt drop you to # then it still will not work from doing it automatically using arguments. That is what i'm trying to resolve first..
Ill get back to you guys on it, and ill even add the option to restore wimax keys.
That's what I was thinking You have to Temp root with Z4root first.
Since The manual root requires super user to work.
Dude!!!! thank you so much for this. Been wanting t root badly but was afraid to try the other method. Good luck with baby!!
Perhaps someone brave could test it out by temp rooting with visionary/z4root and then running the program? If you posted the download link back up.
What I have tried:
SuperOneClick (all versions) <-- Siege Tanks Were Doomed
Gingerbreak <-- Just sits there
Z4Root <-- doesn't do anything
Rageagainstthecage <-- doesn't work
tried flashing Clockwork mod via tcard like works for the ZTE Blade, phone pretends like it is working then reboots and no change, trying to start using the power button and vol - yields nothing.
tried cooking my own rom with the kitchen make the update.zip file
Do adb reboot recovery
the phone comes back to the android system recovery <3e>
I select the option to do update.zip from sdcard
I get:
verifying update package...
installation aborted...
I need root access to remove the AT&T preloaded apps that won't uninstall won't stay killed and are hogging all my space on the phone (limited storage). I would also like to be able to upgrade to 2.3.7 from my current 2.3.4 and possibly make my own roms.
I have emailed ZTE Chinese support to see if I can get an non pork filled rom the Indian who answered their tech support line didn't have an answer and told me not to flash the ZTE roamer rom (if I could even find it) because it will brick my phone. They have been no help!
What am I doing wrong in the android recovery (I have tried both installer scripts)? Is there a way to rebuild the system.img from the system folder that was created in the kitchen because I might be able to rebuild it into the .bin file that the phone will accept from a sdcard with the built in update feature?
Ok so I figured out how to repack the system.img I then dropped it back into the folder and used zte-pack.exe to build my .bin file. I go to the tcard update and it fails verification...is there a signature that needs to be made? I didn't see an option in zte-pack
i got the same phone with at&t....was unable to root it either, but i only tried super one click...
good luck and share, if you find a way.
Not sure if there is away as of yet. Just did a fast search and it seems no root has been done for it yet
try another time z4root
I am unable to root my XT928 either...Good Luck!
Apo11on said:
i got the same phone with at&t....was unable to root it either, but i only tried super one click...
good luck and share, if you find a way.
Click to expand...
Click to collapse
I am soooo close just need that extra little bit of help, I will get it and when I do I will definitely share. I've only had a droid for 2 weeks and I have come this far, I am not going to stop. I have a BS in Computer Science and used to be a MCSE, I don't know this tech well enough yet but I will. Just hoping someone on here has the skillset I need to help complete this,
primanka said:
try another time z4root
Click to expand...
Click to collapse
tried it multiple times as I have with all of the one click exploits and custom rom trials
We got root, just need a forum to post, and maybe anotehr tester if someone is interested.
Shoot me a pm
jcase said:
We got root, just need a forum to post, and maybe anotehr tester if someone is interested.
Shoot me a pm
Click to expand...
Click to collapse
Thank you kind Sir! jcase to the rescue again - spent a couple of hours with me and busted this thing open. I can confirm my AT&T Aveil ZTE Z990 is fully rooted now. Mad props to jcase
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Will post instructions after I Get another tester and write it up, however I am submitting a CVE And reporting it to google/zte. It is particularly dangerous (as far as malware abusing it).
jcase said:
Will post instructions after I Get another tester and write it up, however I am submitting a CVE And reporting it to google/zte. It is particularly dangerous (as far as malware abusing it).
Click to expand...
Click to collapse
Just woke up and saw this...can't wait to test thanks. PM Sent
I can confirm it works..I am now rooted!
jcase said he will post later... was able to remove the annoying at&t apps and gain back 30mb using titanium back...now to learn how to flash a custom rom...
http://www.androidpolice.com/2012/0...e-avail-att-offer-quick-and-easy-root-access/
enjoy
There are detailed instructions for rooting, unlocking, other ROMs and more on a Russian site but I don't understand much of it. If anyone can help out it would be great!
I'm prevented from posting links here but search for zte Roamer unlock.
schoolage said:
There are detailed instructions for rooting, unlocking, other ROMs and more on a Russian site but I don't understand much of it. If anyone can help out it would be great!
I'm prevented from posting links here but search for zte Roamer unlock.
Click to expand...
Click to collapse
we know about this - i'm fluent in russian. none of their file links work - it's an old thread on 4pda forums. you can use translate.google.com or several other engines, to translate web pages in real time.
according to ZTE although they share the same model numbers they have different radios (IE GSM / CDMA) and flashing the roamer to the avail will brick it. Apparently ZTE has not gotten the concept of using distinct model numbers yet...
I was able to get root by simply entering *983*7668#. watch the screen and you will see a message that says wait a few minutes for root. I then installed superuser and Titanium Backup proceeded to remove the apps I didn't want/need, I was also able to backup everything else that I wanted to!
theloon said:
I was able to get root by simply entering *983*7668#. watch the screen and you will see a message that says wait a few minutes for root. I then installed superuser and Titanium Backup proceeded to remove the apps I didn't want/need, I was also able to backup everything else that I wanted to!
Click to expand...
Click to collapse
How did you run Titanium Backup without installing a su binary?
shimapan said:
How did you run Titanium Backup without installing a su binary?
Click to expand...
Click to collapse
It just worked, even after a fresh flashing of the T card image.bin from ZTE.
Oh and heres a little batch file with needed files to automate jcase's procedure.
Today I had a message from OTA that 45.0.2310.en.EU is available but I have 2.3.5 CEE Nandroid on 2.3.5 RTEN sbf and there is no way to upgrade it so I would be thankful if someone have any suggestion how can I push it to update it to 45.0.2310.en.EU. Maybe should I try to update it from 45.0.2310.en.DE and then somehow write this en.EU or something?? I will be very thankful for full .sbf en.EU.
To avoid questions I don't need to downgrade option to CM, Froyo, or MS2Ginger, I just need stock rom with Polish language.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Indeed, I'm in the same situation like you. FOTA update doesn't works even if I unroot and uninstall CWM. Somehow, the patch update recognize that my ROM was rooted even if all original applications are there.
Strange indeed. I can obtain that zip update but I don't know how to get it works.
Hi!
I managed to install it using clockworkmod "install update.zip from sdcard".
Just edit the "\META-INF\com\google\android\update-script" and delete the "assert(getprop("ro.product.device") == "umts_jordan" || getprop("ro.build.product") == "umts_jordan");" line. Replace the file with winrar.
Be sure that you have not installed any zip that modifies /system files, because they will fail on sha1 check.
If the MTD:boot line fails, you should use the attached boot.img, which is the original CEE boot.img, and try again.
And last the line
assert(package_extract_file("cdt.bin_signed", "/tmp/cdt.bin_signed"),
write_raw_image("/tmp/cdt.bin_signed","cdt.bin"),
delete("/tmp/cdt.bin_signed"));
fails but I don't think it's necessary, probably it fails because modifying the script damages the signature.
Prepare yourself for the new lockscreen!!
Can you make an update zip with all included? I have that MTD:boot: error. Where should I insert that "boot" file? On the root of update.zip?
I don't understand the last line indication. What is about it?
And the last question: the root, I suppose that it will make the phone unrooted and non-rootable.
No need to unroot.
Firstly replace the updater-script with the one attached. Rename the archive to update.zip and place it into \sdcard.
Then put CEEBoot folder into \sdcard\clockworkmod\backup
Start clockworkmod Backup and Restore->Advanced Restore->CEEBoot->Restore boot
Then "install update.zip from sdcard".
I'm very newbie in Android, but I think the result is not rootable yet.
All the applications into the SuperUser list keep showing that permission is granted. SndInitDefy even pops up the superuser prompt.
But it's not true, as there is not root access.
Maybe a more advanced user than me can find a solution.
So be sure that you change your font before installing the update, it will keep working fine!
Doesn work. Boot loop before Motorola animated logo.
Here is my nandroid backup
Motorola Defy+ 2.3.6 CEE Nandroid Backup
Beware that the system font is changed!
And not sure about downgradeability if you flash boot.img! Use it at your own risk!
I'll try it but when DFP-231 will be rootable cause now custom rom is not usable without root. I need to say I'm not and expert in android too so I can try this method with updating but I'd prefer nandroid or full sbf of this rom to be sure everything works fine to mod it like my old DFP-125 but thanks for replies and advice.
Edit:
Thanks for nandroid. Is it clean or updated nand from DFP-125??
No, its not clean! It's the updated 125.
Sorry, but my favorite font is installed in the nandroid.
You don't have to try it, I just uploaded it for anyone how have trouble with it, I guess there will be a full sbf soon.
Thanks anyway. I hope full sbf will be soon and it wont be like with DFP-125 witch is still not available and only rt and de can be found.
As I said, I tried to install again with update.zip method above but I've got an bootloop again (with whipe data and cache).
So I managed to restore the system as it was to be accepted by OTA update. First of all, I flashed the 2.3.5 sbf for Great Britain (provided here on XDA, there is no sbf for CEE, only nandroid ), than I rooted it and installed CWM (last official one) . Made a backup for Zinio, Cardio Trainer and 7player. Than I restored the original nandroid for CEE region provided and than restored the 3 apps above (the nandroid doesn't have them) and restored boot.img for CEE provided here on this tread. The nandroid for CEE is an untouched one except those 3 apps that have been deleted. I get that nandroid from a german forum.
After all these procedures, I unrooted via CWM, checked if everything is okay. Than uninstalled CWM via its own menu. Than made an hard reset via bootmenu of the phone, reboot, set the Motoblur account, check and download the update package and installed it normally (as the phone indicates). Everything went fine. Now I have the last CEE with 2.3.6 unrooted and not yet rootable.
I'm glad you made it.
I think that the bootloop problem you had, has something to do with the way you root your phone and the Busybox installed.
There is no need either to uninstall clockworkmod or unroot.
LeopardSurd said:
As I said, I tried to install again with update.zip method above but I've got an bootloop again (with whipe data and cache).
So I managed to restore the system as it was to be accepted by OTA update. First of all, I flashed the 2.3.5 sbf for Great Britain (provided here on XDA, there is no sbf for CEE, only nandroid ), than I rooted it and installed CWM (last official one) . Made a backup for Zinio, Cardio Trainer and 7player. Than I restored the original nandroid for CEE region provided and than restored the 3 apps above (the nandroid doesn't have them) and restored boot.img for CEE provided here on this tread. The nandroid for CEE is an untouched one except those 3 apps that have been deleted. I get that nandroid from a german forum.
After all these procedures, I unrooted via CWM, checked if everything is okay. Than uninstalled CWM via its own menu. Than made an hard reset via bootmenu of the phone, reboot, set the Motoblur account, check and download the update package and installed it normally (as the phone indicates). Everything went fine. Now I have the last CEE with 2.3.6 unrooted and not yet rootable.
Click to expand...
Click to collapse
Thanks for guide to make it work but I'll better wait until someone root DFP-231 cause I wont stay with clean stock rom for next few week/months but I hope it will be days. Thank anyway. Good work.
p4tgb said:
I'm glad you made it.
I think that the bootloop problem you had, has something to do with the way you root your phone and the Busybox installed.
There is no need either to uninstall clockworkmod or unroot.
Click to expand...
Click to collapse
Well I did that because I smell that Motorola will never release an update through MSU. Until now, there are a couple of updates for Roms in some regions that where never available as sbf. I just wanted to come back to original. The official ROM is not bad and is better builded in terms of stability than CM7. For original ROM, I only need root to delete those 3 apps and to use Root Call Blocker (it needs root acces). I can live without root.
Indeed I have had busybox and tried to uninstall it but without success. Busybox installer said that cannot do it (more instances).
I was trying a few other mods that took me to installing apps to toggle root but needed special SU and all that jazz...I was not very comfortable with installing another app just to toggle it.
So I tried a terminal command way and it worked well, but remembering the commands and typing it in all the time sucked so I found an updater script that will work just the same.
Only bug is reverting back might take two flashes because of the mounting another folder. I might try and solve it when I have time but works flashing it twice.
The code I used makes it easy to know if it's working....look at theses screenshots of the recovery log
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PokeFix.zip recovery messages:
renaming files bin = Root off
renaming files xbin = Root off
nothing to rename = already done
PokeFix-revert.zip recovery messages:
reverting files bin = Root on
reverting files xbin = Root on
nothing to revert = already done
Click to expand...
Click to collapse
How this works:
The script will look at the folders bin and xbin where the su files are located so simply remaning them suBU will kill root and apps that look for root...the other script renames it back to su from suBU so rooted again on boot! Simple and clean!
To confirm you can flash them and get the nothing to message just to make sure!
If you have root in other folders and this does not work let me know and I will try and make special zips.
Hope this helps you CATCH 'EM ALL and use android Pay of course.
DJDARKKNIGHT96
TeamBlackOut
Link to files:
Gimmie Pokemon and Android pay on CM
Gimmie Pokemon and Android pay on DU/SuperSU comming soon hopefully but this thread seems to work with systemless root http://forum.xda-developers.com/apps/supersu/suhide-t3450396/post68424603
@djdarkknight96 Nice job David!!! Awesome thinking
Sent from my Nexus 6P using XDA Labs
Seems this is the place I need to be for PoGo fix.
LG G2 d800. Custom LolPop ROM. Apparently I am no longer rooted, but the LP cust ROM must be causing the PoGo "not compatible". Have tried a few suggestions to no avail. Cant access TWRP anymore either. Any ideas?
davizzyus said:
Seems this is the place I need to be for PoGo fix.
LG G2 d800. Custom LolPop ROM. Apparently I am no longer rooted, but the LP cust ROM must be causing the PoGo "not compatible". Have tried a few suggestions to no avail. Cant access TWRP anymore either. Any ideas?
Click to expand...
Click to collapse
Oh man no TWRP access, you need recovery or you could root then use a terminal app and do these commands to find and hide the files they check for.
I got that from G+ so no credit to me for that, and it inspired my script.
Reboot after done
djdarkknight96 said:
Oh man no TWRP access, you need recovery or you could root then use a terminal app and do these commands to find and hide the files they check for.
I got that from G+ so no credit to me for that, and it inspired my script.
Reboot after done
Click to expand...
Click to collapse
Okay, used Kingroot, but It's acting kind of funny. I think it's rooted. At least it passed root checker app twice. Then tried to use Flashify to flash TWRP img. 2.8.6 which was on there as my recent recovery image. Tapped boot into recovery and the LG logo with the boot certificate error came up. I thought I was screwed, but hit power button, and it did a regular boot into Lolli.
I'm nervous about messing with it. Last thing I want is another brick. Is there a way to check for sure that TWRP is on there successfully?
And if it is, and if I am rooted, You're saying that entering all of that code into terminal command will work and allow Pogo? Sounds too good to be true. I'm sure I'll find another new and unusual way to brick that I haven't done yet...
---------- Post added at 07:05 PM ---------- Previous post was at 07:00 PM ----------
djdarkknight96 said:
Oh man no TWRP access, you need recovery or you could root then use a terminal app and do these commands to find and hide the files they check for.
I got that from G+ so no credit to me for that, and it inspired my script.
Reboot after done
Click to expand...
Click to collapse
Does this do the same as if I went into the file through ES File Explorer and delete the su out of xbin? That trick worked for me over the weekend after I flashed CM13 and MM. I think I read somewhere it only works on CM13.
davizzyus said:
Okay, used Kingroot, but It's acting kind of funny. I think it's rooted. At least it passed root checker app twice. Then tried to use Flashify to flash TWRP img. 2.8.6 which was on there as my recent recovery image. Tapped boot into recovery and the LG logo with the boot certificate error came up. I thought I was screwed, but hit power button, and it did a regular boot into Lolli.
I'm nervous about messing with it. Last thing I want is another brick. Is there a way to check for sure that TWRP is on there successfully?
And if it is, and if I am rooted, You're saying that entering all of that code into terminal command will work and allow Pogo? Sounds too good to be true. I'm sure I'll find another new and unusual way to brick that I haven't done yet...
---------- Post added at 07:05 PM ---------- Previous post was at 07:00 PM ----------
Does this do the same as if I went into the file through ES File Explorer and delete the su out of xbin? That trick worked for me over the weekend after I flashed CM13 and MM. I think I read somewhere it only works on CM13.
Click to expand...
Click to collapse
If you boot recovery then it's safe now. Yes that script worked on non systemless root but I got lazy and made zips to do the same thing in recovery. While Android is running I wouldn't delete Root files..Just a bad feeling. I go to recovery for all system files just for piece of mind lol
djdarkknight96 said:
If you boot recovery then it's safe now. Yes that script worked on non systemless root but I got lazy and made zips to do the same thing in recovery. While Android is running I wouldn't delete Root files..Just a bad feeling. I go to recovery for all system files just for piece of mind lol
Click to expand...
Click to collapse
Someone suggested renaming the files, instead of deleting them. Also, I don't want MM. I prefer LP. Do you know if I can flash CM 13 and run Lollipop on it?
I'm still really new to all this.
davizzyus said:
Someone suggested renaming the files, instead of deleting them. Also, I don't want MM. I prefer LP. Do you know if I can flash CM 13 and run Lollipop on it?
I'm still really new to all this.
Click to expand...
Click to collapse
My script does rename them inside the zip, I just got the idea from that pic on G+. CM13 is Marshmallow though lollipop would be CM12....I recommend whatever runs good on your device. I use CM13 but I'm a Nexus user.
Yeah, that's what I thought. I just wasn't a fan of MM when I used it for a day last weekend, plus PoGo would freeze for a second or two every time I caught one. Anyway, thanks for your feedback. Maybe someone will come up with a workaround, or maybe those Niantic F"ers Will come to their senses and stop their idiocy of blocking innocent root users.
Hi @djdarkknight96, could please help me on my HTC Desire 620? I successfully flashed the PokerFix.zip file, however after rebooting, Android Pay still identifying the device as rooted, unlocked bootloader or running a custom ROM...any ideas? Many thanks in advance.
ptreber said:
Hi @djdarkknight96, could please help me on my HTC Desire 620? I successfully flashed the PokerFix.zip file, however after rebooting, Android Pay still identifying the device as rooted, unlocked bootloader or running a custom ROM...any ideas? Many thanks in advance.
Click to expand...
Click to collapse
I'm using Magisk now, this mod only worked on Cyanogen mod 13 but Magisk is great and gives root and safety net passes.
Okay, I am sure a lot of you already know how to do this to your Pixel. Some of us do not, and I was one of them. I am the standard noob that just followed Youtube videos to unlock previous carrier locked phones. I am now enjoying this Google Pixel that is unlocked!
So if you are reading this thread, hopefully there isn't another one just like this (yes I looked).
To start off, if you are in here reading this, you have unlocked your bootloader and installed a custom recovery such as TWRP and rooted. Now you are seeing that you need to update your phone with the latest security patch. You try and you try and you can't do it. Even when you unroot it will still fail to update, or at least it did for me. Here I will explain what I went through and did to obtain the latest update. (Warning, you will loose root and custom recovery). THIS IS INTENDED FOR THE GOOGLE STORE PURCHASED PHONES
Lets get this started finally.....
Go into your developer options and enable usb debugging.
Download the newly released package file from google that has fastboot and ADB without needing android SDK.
DOWNLOAD or read about it HERE
Now you will need to download the Factory Image for you device
Find your correct device HERE
Make sure you choose the correct device and correct update, for me I downloaded the "7.1.1 (NMF26U, Jan 2017)" for my Pixel. Also a USA phone.
So now you have the adb fastboot binary package and your factory image. You will need to extract the platform-tools-latest-windows.zip and open the folder and you will see another folder, open it and now you will see a bunch of files. Now open another window and extract your factory image. Once it is done, open the folder until you see the files. Now copy these into the Platform tools folder in the directory with the fastboot.
Once this is done your folder should look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now you will want to right click "flash-all" and click edit. It will open notepad and show the contents of the batch file. You can hit Ctrl+F and type in -w in the search and hit okay, or you can look for it without search (it is near the bottom). Once you find it, just delete the "-w" and save the file. Make sure to keep it as the batch file or this won't work.
Once this is done, in the folder that is shown above, click a blank area in the folder so no file is highlighted. Now hold shift and right click, it will come up with a dialog saying open command window here, click that.
Now we are going to reboot the phone into bootloader mode. In the command window, type everything that is underlined below
adb reboot bootloader
Now your phone should have booted into the bootloader screen or it should be asking for USB rights to use adb. If it asks for permission, hit okay and re run the code above and your phone should reboot.
Once you are in the bootloader screen you will need to do is run the flash-all.bat. It will load and go though some text on the CMD window it brings up. It will say some files are missing, which is fine. But if it fails it will tell you that it did. You can also tell by rebooting the phone or click "start" in the bootloader mode and then checking for OTA updates. It should say January 5th patch installed.
Now you can go through and install your custom recovery again and re root. Which takes no time at all and I am sure someone on here has posted before. If not, let me know and I can make a tutorial over it.
Note: I am very sorry for the bad layout and extended write up. First time ever doing this and I am hoping to help people. If there are any errors, let me know!
All of this is already well known and documented. It is device molding 101
No one with 2 licks of common sense uses YouTube videos for something like this.
zelendel said:
All of this is already well known and documented. It is device molding 101
No one with 2 licks of common sense uses YouTube videos for something like this.
Click to expand...
Click to collapse
Haha well my apologies, I did state that I was a complete noob about all of this. I'm sure there are other noobs like myself
exbtlegends said:
Haha well my apologies, I did state that I was a complete noob about all of this. I'm sure there are other noobs like myself
Click to expand...
Click to collapse
I'm not a noob, but i'm a old fart, and we forget things, even simple things like this, I'm glad to have a simple reminder of how to do things. Thanks for the refresher.
jrat69 said:
I'm not a noob, but i'm a old fart, and we forget things, even simple things like this, I'm glad to have a simple reminder of how to do things. Thanks for the refresher.
Click to expand...
Click to collapse
Not a problem ?
I know you say this is for the GPS version, but has anyone tried it on Verizon? I'm not sure if the firmware is the same on both phones, so I don't want to soft-brick by downloading the Google version if they're different. Same boat as you were, OTA fails even after unrooting.
32BitWhore said:
I know you say this is for the GPS version, but has anyone tried it on Verizon? I'm not sure if the firmware is the same on both phones, so I don't want to soft-brick by downloading the Google version if they're different. Same boat as you were, OTA fails even after unrooting.
Click to expand...
Click to collapse
As long as you never re-lock your bootloader, the process is the same. There's no more separate Verizon images, just USA and international.
This is really complicated. ADB side load the OTA file, reinstall TWRP and root, done.
Good work. This is a very minute stuff of removing -w from the batch file. Very handy work.
Sent from my Pixel using Tapatalk
Do you need to reflash stock kernel before removing root/TWRP before flashing?
32BitWhore said:
Do you need to reflash stock kernel before removing root/TWRP before flashing?
Click to expand...
Click to collapse
Flashing the image overwrites anything you customized besides the regular user data and internal storage (with the -w removed). You don't have to remove or reflash anything else before following these instructions.
TCPDump said:
This is really complicated. ADB side load the OTA file, reinstall TWRP and root, done.
Click to expand...
Click to collapse
I couldn't side load the update.. TWRP would not load the side load feature.
I'm having an issue also: https://forum.xda-developers.com/pixel/help/sideload-ota-t3534926... Can we just unroot, take the OTA and then reroot?
km8j said:
I'm having an issue also: https://forum.xda-developers.com/pixel/help/sideload-ota-t3534926... Can we just unroot, take the OTA and then reroot?
Click to expand...
Click to collapse
Even when I un rooted mine. I was still failing to get the update.
If you made any changes the the system partition then it will fail and simply unrooting doesn't make the all the changes needed. So if OTA mean anything to you then I would suggest not messing with your device as there is Jo promise that after an OTA you will be able to root again tonight away
jesssiii said:
As long as you never re-lock your bootloader, the process is the same. There's no more separate Verizon images, just USA and international.
Click to expand...
Click to collapse
I know the past 2 were the same for google pixel and Verizon pixel but I wouldn't assume they are always going to be. I'm sure some of them will be specific at times whenever Verizon decides they wanna mess with them
FYI, I was able to sideload after updating TWRP to RC1, but now SuperSU 2.79 will install from within TWRP but when the phone restarts SuperSU is not installed... not sure if we have to wait until a new version of SuperSU is released.
SpoiledHeeb said:
FYI, I was able to sideload after updating TWRP to RC1, but now SuperSU 2.79 will install from within TWRP but when the phone restarts SuperSU is not installed... not sure if we have to wait until a new version of SuperSU is released.
Click to expand...
Click to collapse
You need SuperSU 2.79 RC3