Database Users

[Q] Best first steps with a new tablet

Ultra Noob here
So I had my first android-TF700 for about 10 days. Played around with it, read around this site and realized it was a tablet for someone with experience.
So I now have an N10. Charged, not even turned on yet. What should be my next steps? I see a couple toolkits,an auto root, and ASOP-
What would you suggest a noob start with?
I know, I know, turn it on
Thanks!

Depends on what you want to accomplish with the device. If you want to try or at least gain some understanding as to the different features you might be interested in, read the first post of the different ROMs available and see if anything sounds enticing.
I personally use me for taking media with me on the go, be it news or videos, so I don't have to carry a laptop around. I'm on CM10.1 right now but cycle through every rom to see how everything works. Good luck!
Sent from my Nexus 10 using XDA Premium HD app

First step is unlocking the bootloader and installing root and a custom recovery. Even if you don't need it at the moment there will come the time you want to try it. When you unlock the bootloader you will lose all your data so it's the best if you do it at first when you get your tablet.

rauschkugl said:
First step is unlocking the bootloader and installing root and a custom recovery. Even if you don't need it at the moment there will come the time you want to try it. When you unlock the bootloader you will lose all your data so it's the best if you do it at first when you get your tablet.
Click to expand...
Click to collapse
And how do you unlock the bootloader and install root?
What do you mean a custom recovery?
Are there other ways to root the device with out wiping it? Seems like most android smartphone you can load up an exe or something to shift the su app around or something.
Thanks.. (still waiting for my N10 to arrive.. meanwhile.. still playing with my ICS Bionic)

There are tons of threads here about unlocking the bootloader, rooting and installing a recovery like teamwin or clockworkmod.

rauschkugl said:
There are tons of threads here about unlocking the bootloader, rooting and installing a recovery like teamwin or clockworkmod.
Click to expand...
Click to collapse
Found the threads. Look easy enough to follow. Something I'm not understanding . What does it mean to install a recovery? whats the purpose of that. I've search and (at least not yet) found a good description of what/why that it. I'm sensing that devices are different (duh!) and I didnt need to install a "recovery" on my Droid Bionic when I rooted it, but this N10 must be different.

With the custom recovery you're able to install zip files, make a backup of your Rom,... You can't do that with the recovery that comes with the nexus 10.

Recovery is like a separate system that you can boot to, if you want to mess with the main Android OS. Like rauschkugl said, you can boot to a custom recovery to flash different ROMs that are distributed in flashable ZIP files. You can also make (or if anything goes wrong, revert to) a complete backup of the device's internal memory.

Ok I am rooted and unlocked with mskip's awesome toolkit and DroidModderX video which really helped.
I picked all in one click option and choose TWRP. I fell asleep when I got to TWRP, so I guess I will have to reboot to the recovery page to pull it up.
After that I have no idea what to do I really haven't played with the N10 much. I was planning to leave it stock for awhile (as suggested by rauschkugl).
Do I need to do any backup or anything with TWRP if it's a new tablet? if so what and how ? Please point me to a tutorial for noob types.
Other question is I have a system update and 6 new updates waiting for me to install, can I go ahead and do that rooted and unlocked with stock ROM and no TWRP backup yet?
Thanks!

EraVulgaris said:
Ok I am rooted and unlocked with mskip's awesome toolkit and DroidModderX video which really helped.
I picked all in one click option and choose TWRP. I fell asleep when I got to TWRP, so I guess I will have to reboot to the recovery page to pull it up.
After that I have no idea what to do I really haven't played with the N10 much. I was planning to leave it stock for awhile (as suggested by rauschkugl).
Do I need to do any backup or anything with TWRP if it's a new tablet? if so what and how ? Please point me to a tutorial for noob types.
Other question is I have a system update and 6 new updates waiting for me to install, can I go ahead and do that rooted and unlocked with stock ROM and no TWRP backup yet?
Thanks!
Click to expand...
Click to collapse
Great questions. You are one step ahead of me on my new N10. I've not turned it on yet, really wanting to, but I dont want to do much to it, until after I unlock/root/ and learn how to make backups. Though since i've got a TBpro license, I'll probably use that. I dont want to tweak the OS. so I think I need root just to be able to run TBpro. I just want to be sure I'll still get OFA updates, and I want to learn more about if and how backup work for a multi-user N10.

EraVulgaris said:
Ok I am rooted and unlocked with mskip's awesome toolkit and DroidModderX video which really helped.
I picked all in one click option and choose TWRP. I fell asleep when I got to TWRP, so I guess I will have to reboot to the recovery page to pull it up.
After that I have no idea what to do I really haven't played with the N10 much. I was planning to leave it stock for awhile (as suggested by rauschkugl).
Do I need to do any backup or anything with TWRP if it's a new tablet? if so what and how ? Please point me to a tutorial for noob types.
Other question is I have a system update and 6 new updates waiting for me to install, can I go ahead and do that rooted and unlocked with stock ROM and no TWRP backup yet?
Thanks!
Click to expand...
Click to collapse
I would suggest straight away that you perform a backup with TWRP, so that if you decide to delve deeper into ROMs and playing with your system files, you'll have a completely stock backup to rely on. Simply boot into recovery and select 'Backup', then you can rename the backup file if you want, then swipe the slider across and wait, then you're done!
When it comes to system updates, you'll most likely have to use your root toolkit to unroot the device, else the update will fail. You can however continue to update all your apps as you normally would. Hope this helped

OK
So I kinda started from the beginning of Droid ModderX's video, picked yes to update the toolkit i had donated- (got an update) accessed TWRP (pain to get to- could I download goomanager now after I have TWRP?) and backed up my stock set up just as you said Huggogguh :good:.
Then I went ahead and touched "install system update" that was hanging around in the upper left corner of my tablet (I'm being really specific for other noobs) and it updated my system to 4.2.1 and my apps. Build number changed to JOP4OD
Looked at root checker app. I am now not rooted, so I will go back through toolkit and choose 4 once I am in fastboot mode to reroot I hope:fingers-crossed:.
Thanks!

EraVulgaris said:
OK
So I kinda started from the beginning of Droid ModderX's video, picked yes to update the toolkit i had donated- (got an update) accessed TWRP (pain to get to- could I download goomanager now after I have TWRP?) and backed up my stock set up just as you said Huggogguh :good:.
Then I went ahead and touched "install system update" that was hanging around in the upper left corner of my tablet (I'm being really specific for other noobs) and it updated my system to 4.2.1 and my apps. Build number changed to JOP4OD
Looked at root checker app. I am now not rooted, so I will go back through toolkit and choose 4 once I am in fastboot mode to reroot I hope:fingers-crossed:.
Thanks!
Click to expand...
Click to collapse
Sounds like a great success then so are you saying that you performed the system update while you were rooted and you retained the root access?

Nope. Got the OTA system update and it knocked me off root. But I got it back easily with the toolkit.

MotoWpNoMo works for the Maxx permanent Write Protection Off

Ok guys it looks like Jcase did it again he created an exploit that gets write protecton off for good or until an OTA. He states this will survive even an FXZ or factory data reset.
Here is what I did took about 15 min. go here ---->http://forum.xda-developers.com/showthread.php?t=2551113 down load the exploit follow the instructions it's very easy the exploit does it all. I am not sure if I needed to do this or not but I did to be safe I used fastboot and put stock recovery back. Just take the recovery.img from the FXZ and open a command prompt type in this command------> fastboot flash recovery recovery.img
You must be in fastboot obviously it will flash recovery back and you lose WP off. You then run MotoWpNoMo and it bypasses WP protection for ever or until OTA from what I have read. Open a command prompt and type in this command------> adb shell getprop ro.boot.write_protect to check if write protection is disabled it will return a value of "0". No more having to boot into recovery to make system changes that require writer protection off this is true root. Great job Jcase!!!!!!!!!!!!!!!!!!!!
Oh and we have stock recovery back and I beleive that voodoo ota root keeper works on 4.2.2 so I think we will have a very easy time upgrading to 4.4 and not have to re-root this is just a theory at this point.
I just tweeted Jcase looks like he tested this method it was the rumrunner team (beaups and fuses) that created this exploit.

Why couldn't this come at the beginning of a weekend, instead of a week? Aaaarrrrrggghhhh!
fat-fingered and Maxx-ed out.

Einsteindks said:
Why couldn't this come at the beginning of a weekend, instead of a week? Aaaarrrrrggghhhh!
fat-fingered and Maxx-ed out.
Click to expand...
Click to collapse
It actually did but I worked all weekend and was not able to try it until today but it is SUPER EASY TO DO.
The other plus to this is voodoo still protects root on 4.2.2 so since we have stock recovery back we SHOULD not guaranteed but should be able to download the update to our sdcard an install 4.4 through stock recovery and keep root. The only question is if we would need to run the exploit again to get write protection off. I don't know if it would survive the OTA but I am leaning on it not surviving. Not that it matters this works on 4,4 anyway.

Another quick way to see if WP is off is to uninstall then re-install SS recovery we could not do that before unless we booted in to recovery with WP off. I just tried it and it works great.

Worked perfect on my Mini. Just be patient and keep an eye on it for granting superuser permission and unlocks after reboots.

should i just wait for kitkat to come out? because i dont feel like refreshing everything and starting over lol.. since i went back to stock and not able to save data XD

bigv5150 said:
Ok guys it looks like Jcase did it again he created an exploit that gets write protecton off for good or until an OTA. He states this will survive even an FXZ or factory data reset.
Here is what I did took about 15 min. go here ---->http://forum.xda-developers.com/showthread.php?t=2551113 down load the exploit follow the instructions it's very easy the exploit does it all. I am not sure if I needed to do this or not but I did to be safe I used fastboot and put stock recovery back. Just take the recovery.img from the FXZ and open a command prompt type in this command------> fastboot flash recovery recovery.img
You must be in fastboot obviously it will flash recovery back and you lose WP off. You then run MotoWpNoMo and it bypasses WP protection for ever or until OTA from what I have read. Open a command prompt and type in this command------> adb shell getprop ro.boot.write_protect to check if write protection is disabled it will return a value of "0". No more having to boot into recovery to make system changes that require writer protection off this is true root. Great job Jcase!!!!!!!!!!!!!!!!!!!!
Oh and we have stock recovery back and I beleive that voodoo ota root keeper works on 4.2.2 so I think we will have a very easy time upgrading to 4.4 and not have to re-root this is just a theory at this point.
I just tweeted Jcase looks like he tested this method it was the rumrunner team (beaups and fuses) that created this exploit.
Click to expand...
Click to collapse
you mean i can keep the root by flash back the stock recovery.img ? so i can still receive the ota , and have the root after update ?

I doubt that you can keep your root and take the OTA. It caused a whoping lot of problems last time around, and I don't see it being any different when we take KitKat either. Best to flash a stock version of the ROM, then take the update. You may still keep write protection off.
fat-fingered and Maxx-ed out.

Einsteindks said:
I doubt that you can keep your root and take the OTA. It caused a whoping lot of problems last time around, and I don't see it being any different when we take KitKat either. Best to flash a stock version of the ROM, then take the update. You may still keep write protection off.
fat-fingered and Maxx-ed out.
Click to expand...
Click to collapse
That is not necessarily true. The issue with the last update was taking the ota with root still installed. Voodoo still works on 4.2.2 so if you protect root and then unroot with voodoo you should be able to take the update and then restore root after the update. I used voodoo on the last update and kept root what screwed me was I lost write protection off. When I tried to run pwnmymoto it saw I was already rooted and wouldn't run the exploit so I was stuck till I could fxz and run pwnmymoto again. That won't happen here since we have write protection off script now. So you use voodoo then restore root then run motowpnomo and you will have root and write off protection.

bigv5150 said:
That is not necessarily true. The issue with the last update was taking the ota with root still installed. Voodoo still works on 4.2.2 so if you protect root and then unroot with voodoo you should be able to take the update and then restore root after the update. I used voodoo on the last update and kept root what screwed me was I lost write protection off. When I tried to run pwnmymoto it saw I was already rooted and wouldn't run the exploit so I was stuck till I could fxz and run pwnmymoto again. That won't happen here since we have write protection off script now. So you use voodoo then restore root then run motowpnomo and you will have root and write off protection.
Click to expand...
Click to collapse
root vs running your phone without a recovery. 2 different things , wouldn't you say? root was maintained through the OTA without any steps to hide it. rooting your phone doesn't mess up system updates. running without a recovery does.

Ok, so I am right in that when root is in place, it causes problems during updates (due to recovery used for WP off mode. Prob'ly the reason for most noob problems.). I wasn't aware that voodoo still worked. I certainly would've used it last time! I'll try it next time. So, theoreticaly, having a clean root, run the WP script, flash the OE recovery back on, and, using voodoo, KK should take, as long as the factory ROM isn't altered? Ideally then, we should be able to restore root, and still have a WP off after KK? I'm guessing, to be on the safe side, safestrap should temporarily be uninstalled. Probably not necessary, but it couldn't hurt.
Edit: looks like voodoo wont work into 4.4, due to KK.
fat-fingered and Maxx-ed out.

mistermojorizin said:
root vs running your phone without a recovery. 2 different things , wouldn't you say? root was maintained through the OTA without any steps to hide it. rooting your phone doesn't mess up system updates. running without a recovery does.
Click to expand...
Click to collapse
I don't understand what you are trying to say we have full root now and stock recovery like any other android device. Taking an OTA root wont survive the reason why people boot looped had nothing to do with root as much as not having recovery. Once the OTA tried to install itself there was no recovery to install it hence the bootloop.

Einsteindks said:
Ok, so I am right in that when root is in place, it causes problems during updates (due to recovery used for WP off mode. Prob'ly the reason for most noob problems.). I wasn't aware that voodoo still worked. I certainly would've used it last time! I'll try it next time. So, theoreticaly, having a clean root, run the WP script, flash the OE recovery back on, and, using voodoo, KK should take, as long as the factory ROM isn't altered? Ideally then, we should be able to restore root, and still have a WP off after KK? I'm guessing, to be on the safe side, safestrap should temporarily be uninstalled. Probably not necessary, but it couldn't hurt.
Edit: looks like voodoo wont work into 4.4, due to KK.
fat-fingered and Maxx-ed out.
Click to expand...
Click to collapse
Correct but most of us have probably altered the system in one way or another and will have to fxz for a clean system to take update.
Voodoo wont work on 4.4 it works for 4.2.2 but I see what you are saying it may not restore root once on 4.4. That I am unsure of since I don't believe any one has tried it. Worst case scenario it doesn't restore root and you have to re-root then install stock recovery then run motowpnomo. I can't see the harm in trying.

this is not a root tool correct just RW tool?

StankFiss said:
this is not a root tool correct just RW tool?
Click to expand...
Click to collapse
Yep
fat-fingered and Maxx-ed out.

bigv5150 said:
Ok guys it looks like Jcase did it again he created an exploit that gets write protecton off for good or until an OTA. He states this will survive even an FXZ or factory data reset.
Here is what I did took about 15 min. go here ---->http://forum.xda-developers.com/showthread.php?t=2551113 down load the exploit follow the instructions it's very easy the exploit does it all. I am not sure if I needed to do this or not but I did to be safe I used fastboot and put stock recovery back. Just take the recovery.img from the FXZ and open a command prompt type in this command------> fastboot flash recovery recovery.img
You must be in fastboot obviously it will flash recovery back and you lose WP off. You then run MotoWpNoMo and it bypasses WP protection for ever or until OTA from what I have read. Open a command prompt and type in this command------> adb shell getprop ro.boot.write_protect to check if write protection is disabled it will return a value of "0". No more having to boot into recovery to make system changes that require writer protection off this is true root. Great job Jcase!!!!!!!!!!!!!!!!!!!!
Oh and we have stock recovery back and I beleive that voodoo ota root keeper works on 4.2.2 so I think we will have a very easy time upgrading to 4.4 and not have to re-root this is just a theory at this point.
I just tweeted Jcase looks like he tested this method it was the rumrunner team (beaups and fuses) that created this exploit.
Click to expand...
Click to collapse
Am I the only one who noticed that this is totally missed credited? Jcase had nothing to do with this exploit. He is thanked for his contribution of root access that allows for it but that is all.
Sent from my XT1080 using XDA Premium 4 mobile app

TheWhiteChallenger said:
Am I the only one who noticed that this is totally missed credited? Jcase had nothing to do with this exploit. He is thanked for his contribution of root access that allows for it but that is all.
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah I guess so because everyone else knows how to read maybe you should read the WHOLE POST!!!!! is says at the end that "I just tweeted Jcase looks like he tested this method it was the rumrunner team (beaups and fuses) that created this exploit". I mean it's actually in your post where you quoted me "reading comprehension it's a wonderful thing".

Crud. Just tried this, and it says driver errors and some junk. I KNOW everything IS installed, I put stock recovery back first. Security things/firewall off, to. Any ideas?
Edit: scratch request...was starting in fastboot mode...oops.
fat-fingered and Maxx-ed out.

Einsteindks said:
Crud. Just tried this, and it says driver errors and some junk. I KNOW everything IS installed, I put stock recovery back first. Security things/firewall off, to. Any ideas?
Edit: scratch request...was starting in fastboot mode...oops.
fat-fingered and Maxx-ed out.
Click to expand...
Click to collapse
Lol can't tell you how many times I have made that mistake. Also using the wrong USB port for rsd and it doesn't see my phone.

I'm getting confused reading all of the posts that seem to be more about upgrading and rooting than this actual exploit. But my question is this.... I am rooted through jcase's exploit ("pwnmymoto" i think it's called) and still on the original firmware (pre camera update) with no recovery. Can i run this permanent WP killer from where my phone is now? Or do i have to flash the stock recovery back first? Also, will this wipe data?
To be honest, it's been a while since i flashed anything and i'm not real comfortable with the FXZ process just yet. All of my other phones have been highly supported by the devs and i have always had a utility to do all of the work for me. I'm hoping this will be pretty easy. I just want to know what i'm getting into before i soft brick my phone and have to wait days to figure out how to fix it.

[Q] Bricked by Nexus (and I'm not a techie)

Hi everybody.
Okay I'm not a techie. I managed to root my nexus 4 running android 5.0.1 with kingo root. I wanted the OTA 5.1 UPDATE, so unrooted, tried the OTA and it failed.
I've installed minimal adb and fastboot but after various goes I'm no further on. Is my phone ruined?
Under system recovery I'm now showing LMY470. If I try and reboot I just get the google display.
PLEASE - can anybody help (I go on holiday on Sunday and really need my phone!)
Hope somebody can help
Rob

Just flash the factory image with fastboot.
Download the factory image, extract it. In there is a flash-all batch file
Boot into the bootloader and connect your device to the pc
Double click on the flash-all
Note, this will wipe your device.
Sent from my Nexus 5 using XDA Free mobile app

robigouk said:
Hi everybody.
Okay I'm not a techie. I managed to root my nexus 4 running android 5.0.1 with kingo root. I wanted the OTA 5.1 UPDATE, so unrooted, tried the OTA and it failed.
I've installed minimal adb and fastboot but after various goes I'm no further on. Is my phone ruined?
Under system recovery I'm now showing LMY470. If I try and reboot I just get the google display.
PLEASE - can anybody help (I go on holiday on Sunday and really need my phone!)
Hope somebody can help
Rob
Click to expand...
Click to collapse
Your phone is not ruined.... You may need to have to flash the image again. You might want to try using the "Nexus Root Toolkit"
Just search for it It will walk you through the whole process. You might also search for the SkipSoft Android Tool Kit.
I hope that helps Let us know how you get on

Blacksmith5 said:
Your phone is not ruined.... You may need to have to flash the image again. You might want to try using the "Nexus Root Toolkit"
Just search for it It will walk you through the whole process. You might also search for the SkipSoft Android Tool Kit.
I hope that helps Let us know how you get on
Click to expand...
Click to collapse
All done. manged to put no the original 4.3 and then let it do all the OTA stuff. dont' think I'll be rooting again, put me off!

robigouk said:
All done. manged to put no the original 4.3 and then let it do all the OTA stuff. dont' think I'll be rooting again, put me off!
Click to expand...
Click to collapse
When you say you "unrooted", how did you do so? I have found with 5.+ that in order for the OTA to not fail when you have been rooted, requires that you flash the stock images for the current version, as opposed to Factory Resetting, and then you will be able to install the OTA update without it failing. Has to do with out the updater checks the entire partition and not pieces, which is a new method. If one byte of data is out of place on System partition, it OTA fails.

Xposed installed

Ok guys, bear with me.
I haven't done much "developing" or anything but I was able to get Xposed to install and now have Gravity Box running on my stock and locked Maxx. I used the KingRoot described and provided in the thread http://forum.xda-developers.com/droid-ultra/general/root-kingroot-4-4-4-su-6-7-t3117552 by @aviwdoowks. I had installed SuperSU Pro, KingRoot from the aforementioned thread, and the Xposed framework. After getting root with KingRoot, I went into SuperSU and checked survival mode (don't know if this does anything or not). Then, I went into Xposed and had it set to classical installation.
Now, this is where some persistence and effort went into effect. Through multiple attempts, of rebooting , KingRoot rooting, and trying to install Xposed, it finally took. Where aviwdooks, says to wait after booting to run KingRoot, I ran it immediately. As soon as root was obtained I would go into Xposed and run the Classical install. When it finally took, and asks to reboot, HIT CANCEL. Then from the Xposed menu, hit soft-reboot. So far I have survived multiple soft-reboots with Xposed running.
hope this helps someone.

@teerout
Kudos
Does it all go to data? Or rather once installed is system not utilized?
Btw the synchronization to gdrive is all sorted out now. My entire sd excluding 0/TiBU AND including legacy/TiBU!! Using Drive AutoSync.
Ti does tower above He in both convenience and allowing all user apps. I thought I would say it here as my thread is rather a mess

Avi,
I don't know how to answer that about data or system being utilized. Good work with getting the backups to work. I should do something similar.

teerout said:
Avi,
I don't know how to answer that about data or system being utilized. Good work with getting the backups to work. I should do something similar.
Click to expand...
Click to collapse
Still working?
How long now?

yes, still working. I had it running the other day, but wanted to make sure I could recreate it before posting on here. So from installing it this morning around 830, its past noon now, still working and surviving the soft-reboots. it looses functionality on a hard reboot, but can always be re-activated. hope to hear others can get it too.

@teerout
Hi,
You on su6-7.2?
We are all waiting to hear from you at 9:41am sharp.

Yes this is a known effect of a soft boot. You can change anything you want in /system (with root) as long as you only do soft boot. Only the user apps get initialized from terminating zygote.
You are better flashing in root per CrashXXL's thread. It would be nice to bake xposed in so it survives a KK OTA like root does but I suspect the only way is to image and flash the entire 6-72 /system partition.

aviwdoowks said:
@teerout
Hi,
You on su6-7.2?
We are all waiting to hear from you at 9:41am sharp.
Click to expand...
Click to collapse
No, SU6-7.
Yea, Ive been debating if I want to take the steps to work through the method crash put together. Got essentially the same results. Im tempted to try the "crash" method with an older fxz from Moto, but don't want to destroy my device.

teerout said:
No, SU6-7.
Yea, Ive been debating if I want to take the steps to work through the method crash put together. Got essentially the same results. Im tempted to try the "crash" method with an older fxz from Moto, but don't want to destroy my device.
Click to expand...
Click to collapse
Have many bricked that way? I just thought it was damn arduous.
Soooo how long?

aviwdoowks said:
Have many bricked that way? I just thought it was damn arduous.
Soooo how long?
Click to expand...
Click to collapse
don't think anyone has reported they bricked, im just hesitant to force my phone to brick through the process. im also trying to determine from this other thread by littletoslo in the QA section, if they used an older fxz file and got it to work.
xposed is still running with the gravity box mods, no hiccups.

On 6-7, the crashxxl method survives a hard reboot for both su and xposed. Using an older or newer fxz with the crash method will brick your device. Furthermore, just flashing an older version may result in serious gpt version issues.
Sent from my XT1080 using XDA Free mobile app

larsdennert said:
On 6-7, the crashxxl method survives a hard reboot for both su and xposed. Using an older or newer fxz with the crash method will brick your device. Furthermore, just flashing an older version may result in serious gpt version issues.
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
To verify: I took the OTA this morning after a quick skim of xda, much to my chagrin, as I learned xposed didn't survive. To fix this, I can just reflash the 6-7 back using rsdlite and I'm back in business? Is anyone working on a fix for surviving hard reboot with baked in xposed on the 6-7.2? Thanks!

Yes the keys didn't update. You can do a full rsd flash of 6-7 and go back through the root/xposed process. If I find some time I will tackle making a system image of 6-7.2 with root and xposed. It may come down to root on the G4 though. If it doesn't have a R/O system image, I'm jumping ship from many years of Motorola.

larsdennert said:
Yes the keys didn't update. You can do a full rsd flash of 6-7 and go back through the root/xposed process. If I find some time I will tackle making a system image of 6-7.2 with root and xposed. It may come down to root on the G4 though. If it doesn't have a R/O system image, I'm jumping ship from many years of Motorola.
Click to expand...
Click to collapse
How this pertains to the op?

aviwdoowks said:
How this pertains to the op?
Click to expand...
Click to collapse
Basically just reaffirming that you can temp install xposed if you have some sort of root as long as you only soft reboot. Problem is you can only soft reboot so many times before it locks up and then you have to cold boot (Vol up + Vol Dn + Power). A better way is to bake it in to the r/o system image like CrashXXL and the Moto X. An even better way is to be done with Motorola LOL.

larsdennert said:
Basically just reaffirming that you can temp install xposed if you have some sort of root as long as you only soft reboot. Problem is you can only soft reboot so many times before it locks up and then you have to cold boot (Vol up + Vol Dn + Power). A better way is to bake it in to the r/o system image like CrashXXL and the Moto X. An even better way is to be done with Motorola LOL.
Click to expand...
Click to collapse
.... Reboot is hold power on X, Ultra & newer
Ok. :good:

I think I've just successfully extracted a modified 6-7.2 system image for flashing back. This should be interesting.

larsdennert said:
I think I've just successfully extracted a modified 6-7.2 system image for flashing back. This should be interesting.
Click to expand...
Click to collapse
you had my curiosity, now you have my attention.

See next post

Save for pics
used here

G6 Play: Pie Soak Test

Please mirror.
ui_print("Target: motorola/aljeter/aljeter:9/PPP29.41/b1fe5:user/release-keys");
Download
As far as I know, you must be on the Sept. patch. So, you must downgrade firmware first. It also appears to be for the Aljeter only, so I don't know if it'll work on the Jeter.
I am not responsible for any bricked devices.
1. Downgrade to OPP27.91-143 first.
2. Extract gpt_main0.bin from the ota zip and flash it in fastboot.
fastboot flash partition gpt_main0.bin
3. Reboot to recovery, and apply the OTA update from your sdcard.
4. Let the system restart. It'll take about 10min.

Could anyone verify?

Figures it's for Aljeter. Makes me wonder if Jeter will get it at all.

yes it is for aljeter and is working fine

Spaceminer said:
Please mirror.
ui_print("Target: motorola/aljeter/aljeter:9/PPP29.41/b1fe5:user/release-keys");
Download
As far as I know, you must be on the Sept. patch. So, you must downgrade firmware first. It also appears to be for the Aljeter only, so I don't know if it'll work on the Jeter.
These installation steps need confirmation. I am not responsible for any bricked devices.
1. Downgrade to OPP27.91-143 first.
2. Extract gpt_main0.bin from the ota zip and flash it in fastboot.
fastboot flash partition gpt_main0.bin
3. Reboot to recovery, and apply the OTA update from your sdcard.
4. Let the system restart. It'll take about 10min.
Click to expand...
Click to collapse
Tested and working on G6 Play do Brasil!

Up and running in UK. G6 Play XT1922-2, Carrier: ID Mobile (Carphone Warehouse), retgb.
Can't get root though, Magisk won't install for me in TWRP. Unable to mount storage or OEM. Not that fussed about that though.
Butter smooth, no glitches so far, no random reboots, battery life is great but still under observation.

Eddster3000 said:
Up and running in UK. G6 Play XT1922-2, Carrier: ID Mobile (Carphone Warehouse), retgb.
Can't get root though, Magisk won't install for me in TWRP. Unable to mount storage or OEM. Not that fussed about that though.
Butter smooth, no glitches so far, no random reboots, battery life is great but still under observation.
Click to expand...
Click to collapse
That's a Pie/Magisk problem. Easy fix...
1. Format /data in TWRP using the "yes" option. Then reboot directly back into recovery.
2. Mount /vendor then flash the universal dm-verity disabler by zackptg5.
3. Reboot directly into recovery once more and flash Magisk.
4. Reboot normally, and install the Magisk manager app manually. Done.
(Magisk should disable encryption and verity, but I've never had it work %100 of the time for both. Hence the disabler.)

Spaceminer said:
That's a Pie/Magisk problem. Easy fix...
1. Format /data in TWRP using the "yes" option. Then reboot directly back into recovery.
2. Mount /vendor then flash the universal dm-verity disabler by zackptg5.
3. Reboot directly into recovery once more and flash Magisk.
4. Reboot normally, and install the Magisk manager app manually. Done.
(Magisk should disable encryption and verity, but I've never had it work %100 of the time for both. Hence the disabler.)
Click to expand...
Click to collapse
Thanks @Spaceminer !!!! I'll give it a go. I thought at first that I might need to make some sort of patched boot image and faff about quite a bit but your instructions are clear and straightforward.
I must say I'm impressed with the G6 Play. I had a Nexus 6P and a Pixel both of which died on me from physical and customisation fatigue. I could afford a flagship so got this to see be through and I haven't had one complaint yet.
The handful of Pie features and esthetics have been implemented well by Motorola and battery life is still epic on this device.
Edit: rooted and fully set up how I usually have my daily driver handset. Pie is so tasty!

Eddster3000 said:
Up and running in UK. G6 Play XT1922-2, Carrier: ID Mobile (Carphone Warehouse), retgb.
Can't get root though, Magisk won't install for me in TWRP. Unable to mount storage or OEM. Not that fussed about that though.
Butter smooth, no glitches so far, no random reboots, battery life is great but still under observation.
Click to expand...
Click to collapse
Ta for taking the plunge and testing mate! Was beginning to think we'd never get this thing, glad to know it works on the same model number as I've got
Now to figure out the exact detailed step-by-step to getting this going, considering I'm actually on the November update...

picopi said:
Ta for taking the plunge and testing mate! Was beginning to think we'd never get this thing, glad to know it works on the same model number as I've got
Now to figure out the exact detailed step-by-step to getting this going, considering I'm actually on the November update...
Click to expand...
Click to collapse
Op is a step by step. Literally. Downgrade to Sept = Flash the build specified. Except the bootloader etc.
Flash the gpt.bin from the new build, apply update.

madbat99 said:
Op is a step by step. Literally. Downgrade to Sept = Flash the build specified. Except the bootloader etc.
Flash the gpt.bin from the new build, apply update.
Click to expand...
Click to collapse
Well yeah, I know that much. I meant the extra stuff like unlocking bootloader and downgrading the firmware etc lol. Ta for the extra info, mind.
Extra questions though because despite being having novice experience of doing phone flashing stuff, I've never touched a soak test for official firmware before...but I'm guessing I'll have to move back to Oreo temporarily to get the official Pie update...? Or will it just shift up from this soak test version?

Anyone get this working with the xt1922-7?

Donavonn said:
Anyone get this working with the xt1922-7?
Click to expand...
Click to collapse
No dice! The bootloader won't accept the gpt.bin. I think the recovery partition is the only thing that gets expanded though, so... I think if someone makes a back up of Pie in TWRP, then I can make it work on our phone. My idea is this.
1. Restore a Pie system backup using twrp, including the boot.img.
2. Use fastboot to flash the modem, oem.img, and vendor.img. Basically flash every part that isn't a patch file.
3. Hope that crap works.
I think that, or something similar would make it happen. I'll be the lab rat if someone wants to upload a system backup.

Spaceminer said:
No dice! The bootloader won't accept the gpt.bin. I think the recovery partition is the only thing that gets expanded though, so... I think if someone makes a back up of Pie in TWRP, then I can make it work on our phone. My idea is this.
1. Restore a Pie system backup using twrp, including the boot.img.
2. Use fastboot to flash the modem, oem.img, and vendor.img. Basically flash every part that isn't a patch file.
3. Hope that crap works.
I think that, or something similar would make it happen. I'll be the lab rat if someone wants to upload a system backup.
Click to expand...
Click to collapse
Haha yes! Someone get this guy a backup! Also, if it does work, the UI and everything can be changed to English, right?

Okay quick question, considering it was said "Flash the build specified except bootloader etc."; what is meant by "etc" here? Which parts of the older firmware should I avoid flashing. I know I gotta get in on that sparsechunk action but what about the other stuff like fsg, modem, boot etc? Sorry for asking what's probably a very obvious question but I don't wanna accidentally bugger my phone up trying to get this working

Donavonn said:
Haha yes! Someone get this guy a backup! Also, if it does work, the UI and everything can be changed to English, right?
Click to expand...
Click to collapse
Yes, it should be possible on the first setup. I think if it works, LTE probably won't without an APN edit. That's what happens when I flash xt1922-5 RETUS firmware anyways.

picopi said:
Okay quick question, considering it was said "Flash the build specified except bootloader etc."; what is meant by "etc" here? Which parts of the older firmware should I avoid flashing. I know I gotta get in on that sparsechunk action but what about the other stuff like fsg, modem, boot etc? Sorry for asking what's probably a very obvious question but I don't wanna accidentally bugger my phone up trying to get this working
Click to expand...
Click to collapse
Flash every part of the old firmware that you are able to. The bootloader and gpt.bin usually fail to flash if they are older than your current version. You should still try anyways. If they fail, just continue flashing the next items in line.

Spaceminer said:
Flash every part of the old firmware that you are able to. The bootloader and gpt.bin usually fail to flash if they are older than your current version. You should still try anyways. If they fail, just continue flashing the next items in line.
Click to expand...
Click to collapse
Righto. Just to clarify, I'm gonna need to unlock my bootloader to make this downgrade happen, right?

picopi said:
Righto. Just to clarify, I'm gonna need to unlock my bootloader to make this downgrade happen, right?
Click to expand...
Click to collapse
Official firmware should flash without any issue on a locked bootloader. That's my understanding. I don't know if this is %100 accurate. Every Motorola I've ever had, I unlocked the bootloader immediately. So, I've never had to test this.

Spaceminer said:
Official firmware should flash without any issue on a locked bootloader. That's my understanding. I don't know if this is %100 accurate. Every Motorola I've ever had, I unlocked the bootloader immediately. So, I've never had to test this.
Click to expand...
Click to collapse
Righto. In that case I'll report back with my findings, but yeah I'd imagine it should work fine as well. We'll see, fingers crossed.