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
Related
The other thread was just too messy with too much cross information.
So, here's the quick and dirty. If you're on 4.4. and rooted you can upgrade to 4.4.2 after disabling Gravity Box and ANY mods (wifi tether, etc) and you will keep root but you will lose the ability to write to the system. This effectively makes root useless.
It's unlikely 4.4.2 will ever be rooted, but there is some sliver of hope that a solution will be found (likely involving SBF) that allows you to retain root and /system RW but it can't be taken for granted.
There's lots of other info, but this thread is just designed to separate out the discussions.
Just to add..
Inside the OTA is a manifest file which which contains check sums for files which need to exist on your phone. If the expected files are not on your phone, or the checksums of the files don't match the manifest, the OTA will fail. Hence why you need to undo some of the "hacks" and "mods"
Addtioinally to install the OTA, you need to have stock recovery on your phone. If its not on there, the OTA will either fail, or worse, put you in a boot loop! (erasing your phone's cache can help you out of the loop... mfastboot erase cache )
Once you are on 4.4.2, you can not downgrade your rom to 4.4 or older!! Trying to downgrade can/will result in bricking your device.
Can anyone comment on the "This will be permanent" warning from when rooting with SlapMyMoto/MotoWPNoMo?
I'm trying to get all my ducks in a row before I update to 4.4.2 and lose a functional root.
I'm thinking of reflashing /sys or restoring tether hack, and accepting OTA.
evandena said:
Can anyone comment on the "This will be permanent" warning from when rooting with SlapMyMoto/MotoWPNoMo?
I'm trying to get all my ducks in a row before I update to 4.4.2 and lose a functional root.
I'm thinking of reflashing /sys or restoring tether hack, and accepting OTA.
Click to expand...
Click to collapse
When MotoWPNoMo came its disabling write protection was "permanent" (it survived flashing between the roms which were out at that time) however it does NOT survive the 4.4.2 OTA.
The statement in the initial post... "keep root but you will lose the ability to write to the system. This effectively makes root useless. " is 100% accurate for those with locked bootloaders.
I got the notification this morning when I woke up that the OTA was downloaded and ready to install. It was a persistent notification, and I didn't want it there. I long pressed on it and went to app info, which was MotoOTA. I force stopped it, which did remove the notification, but it came back immediately.
I then unchecked the "show notifications" box and it was gone. I'm not really a fan of freezing apps with TiBu or anything like that, so this worked for me. I don't really care to update unless I can keep root and have write protection off.
I didn't see anything in the changelog that really implied that I'm missing much by not upgrading, for now at least. I decided to get the Moto Maker edition because I valued the customization more than then unlocked bootloader. The phone works great and does everything I need it to right now, so I have no desire to upgrade and lose root yet.
One question though, I read somewhere before that booting through recovery disables write protection, and allows you to install Xposed and other root stuff. I assume that write protect being off only lasts until the next reboot? And then you'd need to boot through recovery again, and possibly apply things through Xposed each time? Or is it just for initial setup?
fury683 said:
One question though, I read somewhere before that booting through recovery disables write protection, and allows you to install Xposed and other root stuff. I assume that write protect being off only lasts until the next reboot? And then you'd need to boot through recovery again, and possibly apply things through Xposed each time? Or is it just for initial setup?
Click to expand...
Click to collapse
You don't have to boot into recovery each time. You do need to soft reboot each time after a hard reboot though for it to stick
evandena said:
Can anyone comment on the "This will be permanent" warning from when rooting with SlapMyMoto/MotoWPNoMo?
I'm trying to get all my ducks in a row before I update to 4.4.2 and lose a functional root.
I'm thinking of reflashing /sys or restoring tether hack, and accepting OTA.
Click to expand...
Click to collapse
Well that didn't work. I'm stuck in a boot loop now. Guess I'll try flashing /sys when I get home.
fury683 said:
...One question though, I read somewhere before that booting through recovery disables write protection, and allows you to install Xposed and other root stuff. I assume that write protect being off only lasts until the next reboot? And then you'd need to boot through recovery again, and possibly apply things through Xposed each time? Or is it just for initial setup?
Click to expand...
Click to collapse
The early root processes (RockMyMoto and SlapMyMoto) replaced stock recovery with a trick that booted the phone with write protect disabled. To take the OTA, you need to put stock recovery back, thus removing this trick.
Later, MotoWPNoMo replaced the trick of booting to a tricked recovery, and allowed Write Protection to be disabled for normal boot too, and allowed stock recovery to be put back on, but this doesn't survive the OTA.
---------- Post added at 05:35 PM ---------- Previous post was at 05:34 PM ----------
evandena said:
Well that didn't work. I'm stuck in a boot loop now. Guess I'll try flashing /sys when I get home.
Click to expand...
Click to collapse
No. Put your phone in bootloader mode... then...
mfastboot erase cache
KidJoe said:
No. Put your phone in bootloader mode... then...
mfastboot erase cache
Click to expand...
Click to collapse
Can that be done from the phone with fastboot, or do I need my computer? I haven't messed with this stuff since November, so I'm a little rusty.
evandena said:
Can that be done from the phone with fastboot, or do I need my computer? I haven't messed with this stuff since November, so I'm a little rusty.
Click to expand...
Click to collapse
Have to enter that command from the PC
Wifi Tether require Write Protection?
I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.
Reserved Name said:
I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.
Click to expand...
Click to collapse
You'll probably have to keep the file on your phone to replace each time you do a hard reboot. Without R/W, your changes won't stick after a boot. Otherwise, I think you can still use the entitlement trick without an issue other than it not sticking.
Reserved Name said:
I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.
Click to expand...
Click to collapse
I'd like to know this too. At this point the only thing I really use root for is Greenify, which no longer requires root, tethering with my unlimited data (VZ), and bypassing the exchange pin requirement.
KidJoe said:
Have to enter that command from the PC
Click to expand...
Click to collapse
I'm having problems getting into recovery. Once I select Recovery from the fastboot menu, it boots straight into normal mode.
*edit* maybe I don't need adb to recognize the phone for fastboot erase cache to work. Playing with it now...
*edit 2* ok, it looks like that stopped my boot loops. Now to figure out why the update didn't work the first time...
CartlandSmith said:
you select recovery by hitting vol up button.
Click to expand...
Click to collapse
Yep, was. It was booting to safe mode when Recovery was selected.
I should clarify, I don't use the entitlement hack I just use the Wifi Tether apk. Just wondering if it requires write protection to be disabled or not. Thanks.
If I take the OTA and have root but no system RW, is it still possible to install Xposed, soft reboot, and it works normally until a hard reboot happens? Or is Xposed completely broken?
Reserved Name said:
I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.
Click to expand...
Click to collapse
You're talking "wifi tether for root" like this -> https://code.google.com/p/android-wifi-tether/
I don't think it will work due to the changes it makes when you start and stop tethering. (It appears to update files in the normally write protected area). Then again, if temp changes can be made after 4.4.2 is installed, it might work.
I think you and I are the only ones who use that app.. most everyone else is using Xposed or the hacked entitlement apk.
evandena said:
I'm having problems getting into recovery. Once I select Recovery from the fastboot menu, it boots straight into normal mode.
*edit* maybe I don't need adb to recognize the phone for fastboot erase cache to work. Playing with it now...
*edit 2* ok, it looks like that stopped my boot loops. Now to figure out why the update didn't work the first time...
Click to expand...
Click to collapse
If it's booting normally when you select recovery, it's because your recovery is missing - probably because you used SlapMyMoto.
You need to restore your recovery... you can boot into fastboot, then write the correct recovery to your phone with fastboot flash recovery recovery.img, where recovery.img is a file pulled out of the SBF package for whatever version you're running.
You guys really should just wait! Even if a new root method isn't discovered, you will be able to flash a stock 4.4.2 ROM or Eclipse's stock-based ROM via Safestrap soon enough. Certainly not worth risking losing root! Patience!
Sent from my Moto X
Are the root methods too complicated/risky for you? This is a simple solution.
Start with: original droid maxx software (12.7.7 i believe) on Verizon
1. Install motoroot 1.0 (JCase's first root method from original development section), run it, and click root (that's click #1). Make sure everything's working, reboot a few times, use rootchecker to make sure you've got root. (note you won't have write protection off and there'll be a 10-15 sec delay after booting up before you have root). But hey, it's 1 click.
2. Take 1st Verizon OTA to the 4.2.2 with camera update (12.15.15 i believe). Root should survive. Check that it did with root checker.
3. Install the write protection no more from the moto x original development section on your computer. download android-sdk and make sure adb is working, make sure fastboot is working. connect your phone to your computer and run the "write protectoin no more" app on your computer (that's click #2).
That's it. Now I have write protection permanently off, and I have root. I didn't have to use cydia impactor and mess with a tricky update to 4.4 which if it doesn't work I couldn't go back to a rooted phone. I never had to fxz anything or restore anything to stock, or lose any of my data. I didn't have to pay a dime or give someone on ebay all my phone info.
Sure I'd like to have 4.4, but pretty happy with where I am and how easily I got here. And I've read a lot of people say "the root methods are too complicated" --- well this is pretty easy cause you're just using 2 packaged apps.
I've gotten a lot from this forum, and just thought I'd share. Please don't flame. I feel like this is the best compromise of features:effort for me.
It was really easy to put an unlock code into adb.
Sent from my XT1080 using Tapatalk
Piaband said:
It was really easy to put an unlock code into adb.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
if i could unlock it when i had gotten it in august, sure. but it's too much effort to start over at this point. i have everything set up perfectly. never had to start over. also didn't want to pay for it and send my info to some stranger on the internet. anyway, moot point. good for you, but that option's not available for most people.
So does this work when your already updated to 4.4?
Sent from my XT1080 using XDA Premium 4 mobile app
No nothing roots 4.4 at this point.
vegasdgk said:
So does this work when your already updated to 4.4?
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No he basically just rewrote the instructions of how to root the original firmware.
akellar said:
No he basically just rewrote the instructions of how to root the original firmware.
Click to expand...
Click to collapse
I didn't rewrite it. No where are there instructions for getting root AND write protection off on the 4.2.2 camera update without 1 using command line commands AND 2 that network based program (called Cydia compactor I think). There's none of those complications here. Most people don't even realize 1 click root survives the camera update.
But you are right as to kit kat. I thought my title was clear that this is for jellybean though.
mistermojorizin said:
Are the root methods too complicated/risky for you? This is a simple solution.
Start with: original droid maxx software (12.7.7 i believe) on Verizon
1. Install motoroot 1.0 (JCase's first root method from original development section), run it, and click root (that's click #1). Make sure everything's working, reboot a few times, use rootchecker to make sure you've got root. (note you won't have write protection off and there'll be a 10-15 sec delay after booting up before you have root). But hey, it's 1 click.
2. Take 1st Verizon OTA to the 4.2.2 with camera update (12.15.15 i believe). Root should survive. Check that it did with root checker.
3. Install the write protection no more from the moto x original development section on your computer. download android-sdk and make sure adb is working, make sure fastboot is working. connect your phone to your computer and run the "write protectoin no more" app on your computer (that's click #2).
That's it. Now I have write protection permanently off, and I have root. I didn't have to use cydia impactor and mess with a tricky update to 4.4 which if it doesn't work I couldn't go back to a rooted phone. I never had to fxz anything or restore anything to stock, or lose any of my data. I didn't have to pay a dime or give someone on ebay all my phone info.
Sure I'd like to have 4.4, but pretty happy with where I am and how easily I got here. And I've read a lot of people say "the root methods are too complicated" --- well this is pretty easy cause you're just using 2 packaged apps.
I've gotten a lot from this forum, and just thought I'd share. Please don't flame. I feel like this is the best compromise of features:effort for me.
Click to expand...
Click to collapse
Hello,
I have rooted my phone when i am in 12.7.7, then i took the OTA update 12.15.15, now my device is in a boot loop, it boots normally and after a few seconds it will reboot and it goes over and over again.
any thoughts on this and should I use RSDLite to flash it to either 12.7.7 / 12.15.15???
-Zeta- said:
Hello,
I have rooted my phone when i am in 12.7.7, then i took the OTA update 12.15.15, now my device is in a boot loop, it boots normally and after a few seconds it will reboot and it goes over and over again.
any thoughts on this and should I use RSDLite to flash it to either 12.7.7 / 12.15.15???
Click to expand...
Click to collapse
which method did you use to root it? what system stuff did you change after rooting it?
a lot of people had bootloops after taking an OTA because they did the root method that had replaced their stock recovery with a write protect off mode. so in effect, they were having bootloops because they didn't have the recovery, not because they had root. it their case, there was an easy solution of just flashing a recovery. unfortunately i don't know the details of how to do that off the top of my head.'
in any case, rsd'ing to either of those software versions will likely fix all problems.
i rooted as i described with motoroot 1.0, which didn't affect my recovery and was easy to OTA without problems.
good luck
mistermojorizin said:
which method did you use to root it? what system stuff did you change after rooting it?
a lot of people had bootloops after taking an OTA because they did the root method that had replaced their stock recovery with a write protect off mode. so in effect, they were having bootloops because they didn't have the recovery, not because they had root. it their case, there was an easy solution of just flashing a recovery. unfortunately i don't know the details of how to do that off the top of my head.'
in any case, rsd'ing to either of those software versions will likely fix all problems.
i rooted as i described with motoroot 1.0, which didn't affect my recovery and was easy to OTA without problems.
good luck
Click to expand...
Click to collapse
Thanks for the quick reply,
I used the PwnMyMoto here to root, i forgot that this method will replace / remove the stock recovery.
With a minute of panic and some google search, I'd managed to use RSD lite to flash the 12.15.15 FXZ and now my phone is back in business but kinda lost root.
Right now I am looking into the RockMyMoto method here and see if it can help me to gain root.
-Zeta- said:
Thanks for the quick reply,
I used the PwnMyMoto here to root, i forgot that this method will replace / remove the stock recovery.
With a minute of panic and some google search, I'd managed to use RSD lite to flash the 12.15.15 FXZ and now my phone is back in business but kinda lost root.
Right now I am looking into the RockMyMoto method here and see if it can help me to gain root.
Click to expand...
Click to collapse
glad you got your phone back in order, might want to check out slapmymoto (which is the path to rooted kit kat and involves running rockmymoto on the way) while you're at it
mistermojorizin said:
glad you got your phone back in order, might want to check out slapmymoto (which is the path to rooted kit kat and involves running rockmymoto on the way) while you're at it
Click to expand...
Click to collapse
Not sure about the battery life on kitkat of the MAXX right now, so i will stick with 4.2.2 first and do a little research.
Anyway, thanks for the reply and I've gained root on 4.2.2 (12.15.15) using RockMyMoto:laugh:
I was offered the 5.1 update on my 2013 Nexus 7. In an attempt to be on the safe side, I uninstalled busybox, titanium, and fully unrooted (I always had the stock recovery, so I didn't have to worry about that). Anyway, even after all those precautions, the attempt to install failed after a couple of minutes with an android keeled over and a red warning triangle. The highly informative message "Error!" was displayed under the keeled over android. Just wondering if other folks are seeing this same problem.
About 5 minutes later while I was poking around in this forum, the tablet rebooted itself and it appears to be running 5.0.2 with no obvious problems.
Any clues about what might be going on? Any way to extract more information than "Error!"?
Claghorn said:
I was offered the 5.1 update on my 2013 Nexus 7. In an attempt to be on the safe side, I uninstalled busybox, titanium, and fully unrooted (I always had the stock recovery, so I didn't have to worry about that). Anyway, even after all those precautions, the attempt to install failed after a couple of minutes with an android keeled over and a red warning triangle. The highly informative message "Error!" was displayed under the keeled over android. Just wondering if other folks are seeing this same problem.
About 5 minutes later while I was poking around in this forum, the tablet rebooted itself and it appears to be running 5.0.2 with no obvious problems.
Any clues about what might be going on? Any way to extract more information than "Error!"?
Click to expand...
Click to collapse
To take ota you must have a clean non rooted system. Not one you attempted to remove traces of root from. If you want ota you have to flash 5.0.2 system.img extracted from the factory image. Any trace of root or a missing file or apk will cause it to fail.
madbat99 said:
To take ota you must have a clean non rooted system. Not one you attempted to remove traces of root from. If you want ota you have to flash 5.0.2 system.img extracted from the factory image. Any trace of root or a missing file or apk will cause it to fail.
Click to expand...
Click to collapse
I'm not sure what would leave a trace. I've always been able to get OTA previously via the fully uninstall everything technique.
Claghorn said:
I'm not sure what would leave a trace. I've always been able to get OTA previously via the fully uninstall everything technique.
Click to expand...
Click to collapse
Since lollipop it is very sensitive to anything different or missing in system. Just flash the 5.1 factory image with the ~w removed from the flash-all.bat file so it doesn't wipe data. Or use wugs to flash stock 5.1 image with "no wipe" enabled. Or like I said in previous you can always flash a clean system image of 5.0.2 then take ota. Either way will update you without wiping data.
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root. I don't get it why people bother with OTA all the time. Always issues with them. I just did this and went from 5.0.2 to 5.1 without losing any data, and tablet now really flies. It keeps a lot more apps in RAM, for better multitasking, and I don't experiance any lag what so ever. I strongly recommend everyone to update to 5.1, because it feels like you just got a new tablet. Good job Google !
neo5468 said:
... I don't get it why people bother with OTA all the time ...
Click to expand...
Click to collapse
I'm not really bothering with it - it just showed up and started bothering me .
1.Backup everything.
2.Flash 5.1 with nexus root toolkit.
3.Restore all the data.
4.Change your build in NRT to android 5.1
5.Root it and flash TWRP/CWM if you want.
6.?????
7.Profit! duh
neo5468 said:
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root.
Click to expand...
Click to collapse
... or wait for a week until someone will release a rooted 5.1 update
sensboston said:
... or wait for a week until someone will release a rooted 5.1 update
Click to expand...
Click to collapse
Why would you wait a week, we already waited too long for offical 5.1 to come out for our tablet. It is 5minutes of work, works 100% and also fasboot is the safest way to flash. Also you download the image straight from developers.google.com so there is no bs. I much rather flash that. But to each his own.
There is already a recovery flashable "stock rooted 5.1" thanks to scrosler (cleanrom Dev).
5.1 rooted ROM
neo5468 said:
Why would you wait a week
Click to expand...
Click to collapse
Agree, week is too long. A few days - better words And "one click" solution is much better in case of possible mistakes during flashing separate partitions, rooting etc...
neo5468 said:
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root. I don't get it why people bother with OTA all the time. Always issues with them. I just did this and went from 5.0.2 to 5.1 without losing any data, and tablet now really flies. It keeps a lot more apps in RAM, for better multitasking, and I don't experiance any lag what so ever. I strongly recommend everyone to update to 5.1, because it feels like you just got a new tablet. Good job Google !
Click to expand...
Click to collapse
I haven't done this in forever, is it just adb reboot bootloader, then the fastboot commands for flash system.img/boot.img. I have a custom recovery, does that matter?
beall49 said:
I haven't done this in forever, is it just adb reboot bootloader, then the fastboot commands for flash system.img/boot.img. I have a custom recovery, does that matter?
Click to expand...
Click to collapse
Custom recovery is fine. There is also a new boot loader to flash as well I think. You can also run the flash all batch file in the factory image and just remove the -w from it so it doesn't wipe data. But what you posted is also correct, but flash the boot loader too. If your rusty at it just use wugs toolkit, it will run the commands for you.
Solid, removing the -w was what I was forgetting. I knew there was something else.
Thanks!
Well this popped up for me yesterday and I, in a total blonde moment, clicked OK and it promptly crashed my tablet. Which is what is expected to happen being that it was running rooted and non stock recovery.
So yes it was bricked. But is it a Nexus. It was a soft brick and easily fixed with the Nexus Root Toolkit. Which is what I would have done to update it anyway. I don't normally take OTAs. Yes I sinned before the Gods of RomFlashing and paid for it with wasted time. LOL
nlinecomputers said:
Well this popped up for me yesterday and I, in a total blonde moment, clicked OK and it promptly crashed my tablet. Which is what is expected to happen being that it was running rooted and non stock recovery.
So yes it was bricked. But is it a Nexus. It was a soft brick and easily fixed with the Nexus Root Toolkit. Which is what I would have done to update it anyway. I don't normally take OTAs. Yes I sinned before the Gods of RomFlashing and paid for it with wasted time. LOL
Click to expand...
Click to collapse
That's a little odd, usually (since lollipop) it will just fail. Bummer it actually flashed and soft bricked.
madbat99 said:
That's a little odd, usually (since lollipop) it will just fail. Bummer it actually flashed and soft bricked.
Click to expand...
Click to collapse
No big deal really. I don't keep important data on it. It's mostly used for Kindle and games. Easy to fix.
Hey! So recently I got a Samsung Galaxy J3 and was wondering if it was possible to get Xposed on it? Flashing a Zip is not an option, by the way.
Hey man, I'm right there with you, I want to know as well. I hope this thread gets more attention! I got this phone recently myself and am so far very sad at the lack of ability to do things with it root-wise, such as getting root to frickin stick and getting things like Xposed installed (with-out boot looping your device....).
Hi,
If you're on 5.0.x, flash Xposed by arter97.
If you're on 5.1.x, flash Xposed by wanam.
Find both on Xposed General thread.
Sent from my ASUS_Z00AD
krasCGQ said:
Hi,
If you're on 5.0.x, flash Xposed by arter97.
If you're on 5.1.x, flash Xposed by wanam.
Find both on Xposed General thread.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
The problem is that I don't have custom recovery either, and I'm not yet experienced enough to know how to flash something like xposed without it, without bootlooping. I actually already have the xposed you're talking about, wanam is what I need since im on 5.1, so if someone guides me on how to flash it or at least points me in the right direction, maybe that'd help.
Also as a side question, somewhat related to this, anyone know what I should do about custom recovery? There are models close to mine but not the exact same that are covered by TWRP or CWMR, but I've been very strongly advised against such a course of action.
darknaio said:
The problem is that I don't have custom recovery either, and I'm not yet experienced enough to know how to flash something like xposed without it, without bootlooping. I actually already have the xposed you're talking about, wanam is what I need since im on 5.1, so if someone guides me on how to flash it or at least points me in the right direction, maybe that'd help.
Also as a side question, somewhat related to this, anyone know what I should do about custom recovery? There are models close to mine but not the exact same that are covered by TWRP or CWMR, but I've been very strongly advised against such a course of action.
Click to expand...
Click to collapse
I'd recommend TWRP, actually. If your device doesn't have a custom recovery developed, it could be a pain. Just hoping if someone could develop it one for your device.
Sent from my ASUS_Z00AD
krasCGQ said:
I'd recommend TWRP, actually. If your device doesn't have a custom recovery developed, it could be a pain. Just hoping if someone could develop it one for your device.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
I would agree with you, as I had TWRP on my last phone and liked it quite a bit. I just don't know which phone's TWRP to try and how to try and flash it on there. Do I do it through Odin? Theres (if I recall correctly) a TWRP for the Samsung Galaxy J2 and J5, on either side of my J3 (Which it's so odd that the newer phone came out with a "series" number in the middle like that). Which would you suggest I do, J2 or J5, or neither?
darknaio said:
Hey man, I'm right there with you, I want to know as well. I hope this thread gets more attention! I got this phone recently myself and am so far very sad at the lack of ability to do things with it root-wise, such as getting root to frickin stick and getting things like Xposed installed (with-out boot looping your device....).
Click to expand...
Click to collapse
Me being dumb, I tried manually installing the required files for Xposed a few weeks ago and it bricked immediately. So I had to get a replacement. I'm not sure if it's because I did it wrong but based on that I don't think we'll ever be able to install Xposed which really sucks. Coming from my previous phone which had a lot of tweaks from xposed it just feels weird using a normal phone.
darknaio said:
am so far very sad at the lack of ability to do things with it root-wise, such as getting root to frickin stick
Click to expand...
Click to collapse
I know what you mean. Every time I restart my phone I have to re-root it if I want to do something with it. Luckily I don't really need root on this phone. Mainly because of the lack of things you can do with it. Hoping to see something come out of this though
EqiiKxDude said:
Me being dumb, I tried manually installing the required files for Xposed a few weeks ago and it bricked immediately. So I had to get a replacement. I'm not sure if it's because I did it wrong but based on that I don't think we'll ever be able to install Xposed which really sucks. Coming from my previous phone which had a lot of tweaks from xposed it just feels weird using a normal phone.
Click to expand...
Click to collapse
I know exactly what you both mean. My previous crappy phone had loads of things from xposed on there that I missed. However the good news I guess is since I don't need certain UI tweaks because I'm satisfied with what this phone comes with I'm not missing out on too much. And thus far every time I get bootloop I just use Odin to flash a copy of the original firmware and somehow it doesn't reset everything so I can still keep trying without losing all my apps. Just haven't found anything that sticks. Maybe one of us should try a custom recovery from a different Samsung Galaxy J Series like the 2 or 5.
darknaio said:
I know exactly what you both mean. My previous crappy phone had loads of things from xposed on there that I missed. However the good news I guess is since I don't need certain UI tweaks because I'm satisfied with what this phone comes with I'm not missing out on too much. And thus far every time I get bootloop I just use Odin to flash a copy of the original firmware and somehow it doesn't reset everything so I can still keep trying without losing all my apps. Just haven't found anything that sticks. Maybe one of us should try a custom recovery from a different Samsung Galaxy J Series like the 2 or 5.
Click to expand...
Click to collapse
Yeah I mainly used Xposed on my previous phone to make it look more like Lollipop but since this phone comes with it I don't need it as much. And I didn't know you were able to unbrick this phone? I would have saved about $40 if I knew that ? well then yeah we should probably try one of them. I think we should go with the newest one though
Thats what I was thinking, but I don't know which J series came out before the J3 this year or I'd try that one. And yep, luckily able to unbrick it thanks to Odin. Actually unbricked it from even worse than a boot loop, I accidentally destroyed my recovery somehow so I couldn't even boot into that and do a factory reset, but thankfully Odin's separate from the recovery so it still worked. End of the day if you can at least get your phone recognized by your computer and can flash something onto it, flashing stock = unbrick (usually).
I own the J3 also. Have gained temp root via king root so I could debloat the system. We need a cf auto root option. Our device is 5.1.1 and I think the kernel has to be modified for true root. Then development can start. As for xposed,you need full root for that to work properly. I suggest to you all to get a copy of the device firmware,install odin on pc so you can reinstall firmware if you decide to use temp root and end up boot looped after debloating to much or making other potentially harmful changes.
Curtis1973 said:
I own the J3 also. Have gained temp root via king root so I could debloat the system. We need a cf auto root option. Our device is 5.1.1 and I think the kernel has to be modified for true root. Then development can start. As for xposed,you need full root for that to work properly. I suggest to you all to get a copy of the device firmware,install odin on pc so you can reinstall firmware if you decide to use temp root and end up boot looped after debloating to much or making other potentially harmful changes.
Click to expand...
Click to collapse
I have the same thing, temp root that's lost when I reboot. I've already had to go the Odin route with the original firmware so I've got my backup covered. I'm also working with the dev behind Super Sume and he thinks he has the issue resolved, if not he's going to teamview with me to try and get past this. If we manage to solve the problem I'll post the results and subsequent steps here. Hopefully this will lead to root sticking through reboot. If so then at minimum may be able to solve -some- of the problems. Though I don't know if this will fix Xposed not working, as it always caused me to boot-loop in the past (only solved by going into TWRP and rebooting from there) and even if root sticks the only way to flash Xposed according to current theories is to do so from custom recovery, which I haven't found one for this device yet.
Have you been able to get a custom recovery on your J3? If so that would be the other key part to solving a lot of these problems. If I get the Super Sume to work and someone else can manage to get a custom recovery working, maybe that'll be the start of this device's support here =D.
No but I believe by repacking an edited firnware you can add xposed that way.
Curtis1973 said:
No but I believe by repacking an edited firnware you can add xposed that way.
Click to expand...
Click to collapse
Unfortunately I wouldn't know the first thing about editing a firmware, much less be able to add Xposed lol. Could that be a way to manually add custom recovery? Or are we still dependent on someone making a version compatible with this phone?
will need a custom recovery built for the device. with proper root you could then use flashify to install it to the device. root opens the door for everything. temp root will never get much except ability to debloat the device.
---------- Post added at 08:17 AM ---------- Previous post was at 08:15 AM ----------
i reached out to chainfire in hopes of cf auto root for the j3. but have not heard back. but does not mean i wont. will see. otherwise i will keep on trying what i can.
Quick question. Has anyone updated their J3 yet? I keep getting a notification for a Software update, is it safe?
EqiiKxDude said:
Quick question. Has anyone updated their J3 yet? I keep getting a notification for a Software update, is it safe?
Click to expand...
Click to collapse
Ive been seeing that too and ignoring/swiping it away. Not sure what it is though.
my system is edited so im not getting update pushes. probably nothing significant.
Curtis1973 said:
my system is edited so im not getting update pushes. probably nothing significant.
Click to expand...
Click to collapse
Your J3 is modified? Temp root, or something else?
ok, so there are some things i've found out by doing some research and combining what i found on here with the issues that some people were having with the Cricket version of the LG Stylo, and would like to share with you guys. while i was rooting my phone with kingroot, i noticed a threat that discussed that using supersu me and supersu wasn't an option without soft bricking your phone with a boot loop, after some research and trial i figured out how to get around the problem. The issue was the uninstallation of kinguser app form the phone, this is because using supersu me uninstalls kingroot and replaced it with the superuser binaries, but it leaves some core files of kinguser behind which causes errors, an if you keep your phone on, you'll notice that you'll start getting error messages for an about kingroot permission and all types of errors until your phone starts to freeze and act up. there is an easy fix for it all that worked for me, and would like to share this information and help people having this issue.....
I'm posting this as a hint for those who needed the help with installing xposed on cricket model LG STYLO only running 5.1.1
so to begin, download system repair 2016 and apps2sd from play store, kinguser directly from their site so it will be the latest version,,,root your phone,,,,,don't delete the kinguser apk you downloaded you'll need it for later,,,,now install supersu me from the play store and open and run it, it'll uninstall kinguser and replace the binaries for superuser, this is where its gonna become tricky,,,,,,download supersu and run which will ask for update of binaries also let it finish updating and uninstall the supersu me control,,,,,now open apps2sd and clear the davik cache and other caches without restarting,,,,then run system repair 2016, it'll show that you had a few errors because kinguser hates the fact that supersu me uninstalled it and left messed up configurations on your phone, then clear the davik cache again, now you have to use the same kinguser apk you get at the start of the process and reinstall it to your phone, or else you will be getting a boot loop issue......for some reason even though all the caches are cleared and the system has been checked for errors, the kinguser app installs itself as a system app, a dependency if you will, like a basic LG/Cricket app that if you uninstall will cause errors, so but reinstalling it we stop that problem, you can run it but don't need to activate the root option of kinguser......this will cause the kinguser permission errors to stop also from this point only you can restart your phone,,,,,now you're able to install flashfire and xposed frameworks, and even restart your phone without worry of boot looping since there isn't much support for the LG-H634 stylo model.........:angel::angel:
hope this was helpful for you guys that was in need of replacing kinguser, and installing xposed framework, i've not tried anything further with the twrp install but keep a look out for the names "vegito6" "vegito69" ....and wish me luck on twrp
#humbleprogrammer
seems i've got to post at least 10 times in order to post outside pics
So I rooted my same phone via kingroot and it has the purify apo along with it. Also having problems with errors and stuff. I'm gonna follow your method see what happens. This being #2 stylo after bricked the first one and couldn't find kdz. Anyway I'll get back to ya let me know if you have anymore info thanks for the help man.
orphan tear maker
Help Please
Drumdestroyed said:
So I rooted my same phone via kingroot and it has the purify apo along with it. Also having problems with errors and stuff. I'm gonna follow your method see what happens. This being #2 stylo after bricked the first one and couldn't find kdz. Anyway I'll get back to ya let me know if you have anymore info thanks for the help man.
orphan tear maker
Click to expand...
Click to collapse
got bricked today, anyone any luck with something??
markos638 said:
got bricked today, anyone any luck with something??
Click to expand...
Click to collapse
ok i'm not sure how you guys got bricked, but i just got bricked using flahfire to create backup, so don't use that app as of yet, but anyways working on the replacement now, gonna be trying to create a restore img or flashable zip for the cricket stylo.
vegito69 said:
ok i'm not sure how you guys got bricked, but i just got bricked using flahfire to create backup, so don't use that app as of yet, but anyways working on the replacement now, gonna be trying to create a restore img or flashable zip for the cricket stylo.
Click to expand...
Click to collapse
I got bricked, trying to change from kingroot to SU, I´ll really appreciate when you find solution give us instructions on how you did it!!
Have you guys any luck with a recovery method? And think you for helping I'll do my best with what I have. Also idk if I mentioned it earlier but when I reboot lg symbol appears but (authentication failed #9) appears below it. It was roted via king root and didn't o anything but remove some bloatware. Idk God be with you man cuz this is a bummer
vegito69 said:
ok i'm not sure how you guys got bricked, but i just got bricked using flahfire to create backup, so don't use that app as of yet, but anyways working on the replacement now, gonna be trying to create a restore img or flashable zip for the cricket stylo.
Click to expand...
Click to collapse
I'm pretty sure that you ended up with brick because you didn't unlock your bootloader before backing up. My girlfriend did the same thing. As of right now I'm trying to figure out If there's a way past the bootloader or at least a way to do everything the bootloader can do without unlocking it.
Original Firmware
Can we not flash the original firmware via download mode ? I had this phone (bought from a friend, cricket sim unlocked, phone bricked while i was playing around. )
I'm not super familiar with LG phones, but i keep hearing about a KDZ , is that some kind of official image format ?
If we can flash it for stock via download mode, can someone direct me as to where I might find instructions for our variant of the device, please ?
I was able to replace Kingroot with SuperSu using a guide I found on a website called w0lfdroid, I think. I just Google 'replace Kingroot with SuperSu and it was the second one down (I'm a new user so I can't post the link). I think it worked pretty well, but I'm still not able to flash TWRP or start the process to get xposed. If I can't get it, I might unroot and try the process again with this method.
as anyone with brick try this http://lg-firmware-rom.com/downloads/lg-g-stylo-h634-stock-tot-firmware-v10g/ , they offer files for unbricking, $40 bucks
what do you guys think
markos638 said:
as anyone with brick try this http://lg-firmware-rom.com/downloads/lg-g-stylo-h634-stock-tot-firmware-v10g/ , they offer files for unbricking, $40 bucks
what do you guys think
Click to expand...
Click to collapse
works great, after flashing with LG Flash tools tot method just take out battery and wait 5sec, and put it back in and turn on, android logo will show and then it will boot normally, now i'm back to working on the supersu install methods to help people from bricking, wish me luck . also backing up boot img and then trying to use super sume to switch to still will cause boot looping to my knowledge. got 2 phones working on it, thanks to our annonomous LG guys for the unbricking
https://mega.nz/#!95ZSCARR!dWAG0bd5zi3DQUal3gfB4nMH-zmIR0H0kdCXBdWGLQk
password = wang276634161
vegito6 said:
works great, after flashing with LG Flash tools tot method just take out battery and wait 5sec, and put it back in and turn on, android logo will show and then it will boot normally, now i'm back to working on the supersu install methods to help people from bricking, wish me luck . also backing up boot img and then trying to use super sume to switch to still will cause boot looping to my knowledge. got 2 phones working on it, thanks to our annonomous LG guys for the unbricking
https://mega.nz/#!95ZSCARR!dWAG0bd5zi3DQUal3gfB4nMH-zmIR0H0kdCXBdWGLQk
password = wang276634161
Click to expand...
Click to collapse
works just fine!!!! lg stylo is back!!! thanks vegito ,....
vegito6 said:
works great, after flashing with LG Flash tools tot method just take out battery and wait 5sec, and put it back in and turn on, android logo will show and then it will boot normally, now i'm back to working on the supersu install methods to help people from bricking, wish me luck . also backing up boot img and then trying to use super sume to switch to still will cause boot looping to my knowledge. got 2 phones working on it, thanks to our annonomous LG guys for the unbricking
https://mega.nz/#!95ZSCARR!dWAG0bd5zi3DQUal3gfB4nMH-zmIR0H0kdCXBdWGLQk
password = wang276634161
Click to expand...
Click to collapse
Great job man. It is people like you who keep the community going.
Su binary installation failed!
Mooose-Nuckle said:
I'm pretty sure that you ended up with brick because you didn't unlock your bootloader before backing up. My girlfriend did the same thing. As of right now I'm trying to figure out If there's a way past the bootloader or at least a way to do everything the bootloader can do without unlocking it.
Click to expand...
Click to collapse
well not really, because if you go into the developer options there is the oem bootloader unlock you can select, not sure but i've got a cricket and boost version i've been working on it for a while, for some reason the phone doesn't like the way SU gets injected into the phone, and writes things to the wrong areas, i've been playing with some scripts for superuser installers from zip, hopefully i get a hit.
---------- Post added at 09:48 AM ---------- Previous post was at 09:47 AM ----------
jxs714 said:
Great job man. It is people like you who keep the community going.
Click to expand...
Click to collapse
thats the life of us programmers and developers thats trying to get better lol, we just share the knowledge passed down lol
vegito6 said:
well not really, because if you go into the developer options there is the oem bootloader unlock you can select, not sure but i've got a cricket and boost version i've been working on it for a while, for some reason the phone doesn't like the way SU gets injected into the phone, and writes things to the wrong areas, i've been playing with some scripts for superuser installers from zip, hopefully i get a hit.
---------- Post added at 09:48 AM ---------- Previous post was at 09:47 AM ----------
thats the life of us programmers and developers thats trying to get better lol, we just share the knowledge passed down lol
Click to expand...
Click to collapse
I noticed there is no solution posted. I recently bricked my phone and fixed it, thanks to you. I was simply wondering of there has been progress with getting the framework installed. Your help is much appreciated.
So I'm sort of confused... I cannot install xposed, and can't seem to find a work around. I am rooted but not with kingroot. I used a one click root tool on pc, and works great... Using su that is suggested using in this guide, so no trace of king root. Idk, could someone give me a quick run down on how to install xposed?
So no luck with installing xposed yet
So far I am rooted with Super SU and have exposed installer I'm just having a hard time getting the framework installed. I do not have custom recovery installed. Is there any way to flash the framework zip file with like flashify or another app like that?