Related
Can anyone pls tell me how to root xt1063 on android 5.0.1? The 5.0 method doesn't work here. My system version is 22.21.25 and build number LXB22.46-25
amjamil2010 said:
Can anyone pls tell me how to root xt1063 on android 5.0.1? The 5.0 method doesn't work here. My system version is 22.21.25 and build number LXB22.46-25
Click to expand...
Click to collapse
Supersu will cause bootloops, no matter what.
Download CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu.
Flash it, reboot.
Your device will bootloop a couple of times. If the bootloop continues for more than 4 times, press the power button 5sec till device reboots.
If bootloop continues for more then 4 times, return to recovery, mount system and go to advanced>Terminal Command
Doesn't matter which folder you choose.
Enter the following
Code:
/system/xbin/su --install
If everthing is right, you won't get any response. Choose reboot.
Now your device should bootloop max 3 times and then start normally.
http://forum.xda-developers.com/moto-g-2014/development/xt1064-lollipop-root-t2938051
This method worked but now wifi is not working. Any idea how to fix this?
Is there aby chance to root our phone (1068) without unlocking bootloader? I know that in some of the phones dev crews where able to do it becouse they found some weakpoints in OS (Sony for ex.) is there aby devs working on something like this for our phone?
g_oral said:
Is there aby chance to root our phone (1068) without unlocking bootloader? I know that in some of the phones dev crews where able to do it becouse they found some weakpoints in OS (Sony for ex.) is there aby devs working on something like this for our phone?
Click to expand...
Click to collapse
Unfortunately not yet. Btw, u can relock bootloader if u have any problem with unlocked one
But when i want to unlock bootloader a need to 'say' about that to Motorola and they will have my request in their database. Then they can refuse me guaranty for my phone.
g_oral said:
But when i want to unlock bootloader a need to 'say' about that to Motorola and they will have my request in their database. Then they can refuse me guaranty for my phone.
Click to expand...
Click to collapse
That's the whole point of this strategie. And seeing what's going on in this forum, I can relate somewhat.
Thanks doppelhelix! Worked like a charm. It restarted just as I was about to give up, having let it cycle 5 times, 5 again, and being on the 3rd.
It seems that every time you reboot the phone afterwards, it goes through three bootloops.
It also seems that you can fix that issue by disabling "mount namespace separation" in SuperSU.
When I disabled that, the bootlooping stopped.
When I re-enabled it, the bootlooping started again.
When I disabled it again, the bootlooping stopped.
It seems to be the only variable in my case.
I'm running Android 5.0.1 (with the 5.0.1 modem), the stable version of TWRP 2.8.3.0, and SuperSU v2.40 on an XT1063.
Hello to all. Sorry for my BAD english, try to understand me.
I would like to have root on my Nexus 6, but on Android 6.0 Marshmallow. The problem is that, if I installed the 6.0 rom and try to unlock the bootloader and TWRP recovery appears a message that says that my phone is corrupt and is not safe to use, and does not start anymore.
If I install Android 7 Nougat and lock the bootloader the message disappears, and the phone starts again, as if nothing had happened.
help will be greatly appeciated. thank you.
You're not bricked. You need to install a modified boot image to remedy this issue. If you have TWRP installed, installing a custom ROM such as Pure Nexus or a modified stock ROM will also fix this, since they all have a modified boot image.
Strephon Alkhalikoi said:
...... or a modified stock ROM will also fix this, since they all have a modified boot image.
Click to expand...
Click to collapse
He knows that already;
http://forum.xda-developers.com/showthread.php?t=2946534
NLBeev said:
He knows that already;
http://forum.xda-developers.com/showthread.php?t=2946534
Click to expand...
Click to collapse
Except he apparently didn't at the time I replied, two days prior to your response in the other thread.
Strephon Alkhalikoi said:
Except he apparently didn't at the time I replied, two days prior to your response in the other thread.
Click to expand...
Click to collapse
That's indeed a possibility; reading different threads seems too difficult for me [emoji1]
If I have formatted and installed with encryption disabled, what is the right way to get encryption back?
Can I just go into Settings>Security & Fingerprint>Encrypt Phone and enable it there?
Yup, that should do the trick. Didn't try on T3, but used same method on one of my prev phones.
Did that work?
I did it on OOS 4.1.1 with twrp and franco kernel installed. It worked for me :good:
AndreiVolk said:
I did it on OOS 4.1.1 with twrp and franco kernel installed. It worked for me :good:
Click to expand...
Click to collapse
I wonder if it works with a non oos rom though
stonew5082 said:
I wonder if it works with a non oos rom though
Click to expand...
Click to collapse
Well all custom roms work fine with encrypted devices so i don't see why it shouldn't be possible to encrypt your device on a custom rom. If you want to be 100% sure ask in the thread of your rom
AndreiVolk said:
Well all custom roms work fine with encrypted devices so i don't see why it shouldn't be possible to encrypt your device on a custom rom. If you want to be 100% sure ask in the thread of your rom
Click to expand...
Click to collapse
It worked. I disabled root to be on the safe side and encrypted. I get errors in twrp now, but they don't seem to effect anything.
stonew5082 said:
It worked. I disabled root to be on the safe side and encrypted. I get errors in twrp now, but they don't seem to effect anything.
Click to expand...
Click to collapse
May i know what error TWRP gives after you encrypt your phone ?
I plan to do so as well...
stonew5082 said:
It worked. I disabled root to be on the safe side and encrypted. I get errors in twrp now, but they don't seem to effect anything.
Click to expand...
Click to collapse
nicknacknuke said:
May i know what error TWRP gives after you encrypt your phone ?
I plan to do so as well...
Click to expand...
Click to collapse
Root is not a problem neither. i did it with root enabled.
That twrp error is normal. When you boot in twrp it shows the error that it can't mount data because you're encrypted and you need to type in your password first.
I also suggest you to use blu_spark's twrp because it's always updated. The official twrp for the op3t hasn't a maintainer anymore and it seems abbandoned..
AndreiVolk said:
The official twrp for the op3t hasn't a maintainer anymore and it seems abbandoned..
Click to expand...
Click to collapse
How do you figure that?
https://eu.dl.twrp.me/oneplus3t/
Didgeridoohan said:
How do you figure that?
https://eu.dl.twrp.me/oneplus3t/
Click to expand...
Click to collapse
I mean here on xda. The last build on xda is the 3.0.4.1 which it never came out. There was the 3.1.0.0 which had the wipe bug for the 3t. I don't know who is making those builds and i don't neither know if they test it.
AndreiVolk said:
I mean here on xda. The last build on xda is the 3.0.4.1 which it never came out. There was the 3.1.0.0 which had the wipe bug for the 3t. I don't know who is making those builds and i don't neither know if they test it.
Click to expand...
Click to collapse
You were talking about the official builds... That's the official downloads from the official TWRP website (https://twrp.me). There's a world outside XDA as well...
This is an unrooted 100% Stock J320AUCU3BQI5 firmware.
Working on all exynos j3 models!! (You first need root and to flash with flashfire)
AG models will probably need to enable oem unlock in dev options.
Download
As I said no root, but you can always downgrade back to mm if you need root.
Btw the eng_ root kernel won't boot the system, but it will let you mount as RW and you can edit things thru adb... someone figure out root on this thing!
Thanks to @Iurop for testing AG
@DamienMc thanks for assist me and help me. My J320AG now works with Nougat 7.1.1 without any problem.
Here a couple of screenshots.
galaxy express prime(J320A)
Um I have a question the firmaware above if I want to install it do I need to root? if yes how do I root?
부캐입니다 said:
Um I have a question the firmaware above if I want to install it do I need to root? if yes how do I root?
Click to expand...
Click to collapse
To root just follow this method:
https://forum.xda-developers.com/galaxy-j3-2016/how-to/root-j320a-j320az-alternate-method-t3627225
Hi lurop thanks for your reply! but i have another question to flash nougat file do i have to root or i dont have to
Hi, yes you have to root the phone following the method posted above. Then install flashfire and use it to flash the rom.
Have you do something similar already?
If you do not wish to root and your device is the A or AZ model you can update with Odin.
I fixed and uploaded the full firmware @Iurop provided. You can find that here
Finally got time to mess around with root...and unfortunately we do need a new eng_boot.
But fortunately, like I mentioned, we can still use our old eng_root boot to acquire a root shell.
Btw noticed this Rom does not update stock recovery. I'll package up a fix for it tomorrow, if anyone actually cares
DamienMc said:
Finally got time to mess around with root...and unfortunately we do need a new eng_boot.
But fortunately, like I mentioned, we can still use our old eng_root boot to acquire a root shell.
Btw noticed this Rom does not update stock recovery. I'll package up a fix for it tomorrow, if anyone actually cares
Click to expand...
Click to collapse
I care. Thanks for your time and effort; I can imagine that it (developing) seems rather thankless at times, but your contributions are definitely appreciated.
DamienMc said:
Finally got time to mess around with root...and unfortunately we do need a new eng_boot.
But fortunately, like I mentioned, we can still use our old eng_root boot to acquire a root shell.
Btw noticed this Rom does not update stock recovery. I'll package up a fix for it tomorrow, if anyone actually cares
Click to expand...
Click to collapse
Until now my J320ag works perfectly, no problem at all, phone, sms, internet, app everything run absoluttely fine.
Thanks @DamienMc
I wonder if I could port this to the J320FN?
stock recovery patch
I'll update the rom one day, but this patch is the easiest way to update things...
To apply you must use your pc, use Odin to flash the included eng_root kernel. When it boots the logo will remain onscreen, after two minutes or so you can click the recovery.bat and let it do its thing.
is this rom have arbic ?
tested and working like charm, is there any tool etc for add arbic etc ?
Cant be ported to J320F because of different Chipset,right?
Mr Hassan said:
tested and working like charm, is there any tool etc for add arbic etc ?
Click to expand...
Click to collapse
I never had time to look into adding extra languages, and afaik more locale doesn't support Arabic (plus it doesn't translate everything)
jnk3344 said:
Cant be ported to J320F because of different Chipset,right?
Click to expand...
Click to collapse
Correct, will not work. Most importantly tho they don't have a nougat kernel. And if they did, they'd have their own stock rom... Sorry @Diamond26
DamienMc said:
I never had time to look into adding extra languages, and afaik more locale doesn't support Arabic (plus it doesn't translate everything)
Correct, will not work. Most importantly tho they don't have a nougat kernel. And if they did, they'd have their own stock rom... Sorry @Diamond26
Click to expand...
Click to collapse
Yeah I know sadly...
will this remove region lock?
will this remove region lock?
DamienMc said:
Finally got time to mess around with root...and unfortunately we do need a new eng_boot.
But fortunately, like I mentioned, we can still use our old eng_root boot to acquire a root shell.
Click to expand...
Click to collapse
Isn't eng_boot.tar just a boot.img? Could we extract build.prop from the Nougat ROM and the boot.img from the firmware to update the Root_J320A.zip in your root thread?
@DJJosephJumper
That method will work, we just can't boot while rooted with the stock boot. We need a permissive boot. if you edit that root like you mentioned, it'll only boot to the logo with a working shell. Su commands work there, so it will with with permissive.
Eng_root will do the same, boot to logo only with a rooted shell
sorry if these are noob questions, however GSI's and custom roms confuse me, and I really don't want to brick my phone on accident
Preface:
I have a rooted moto g6 with an unlocked bootloader that supports project treble. as per getprop ro.treble.enabled running pie 29.55-24 Software channel Retail US
1. Can I flash a GSI on my phone
2. Where is there a good guide on how to flash a gsi
3. Will it factory reset my phone
4, Is there anything I should do beforehand
5. Are there any GSI's I can't flash
(What I think is 1:yes 2:If i knew i wouldn't be here 3:yes 4:backup system images 5: Yes
Thanks
Android Adam said:
sorry if these are noob questions, however GSI's and custom roms confuse me, and I really don't want to brick my phone on accident
Preface:
I have a rooted moto g6 with an unlocked bootloader that supports project treble. as per getprop ro.treble.enabled running pie 29.55-24 Software channel Retail US
1. Can I flash a GSI on my phone
2. Where is there a good guide on how to flash a gsi
3. Will it factory reset my phone
4, Is there anything I should do beforehand
5. Are there any GSI's I can't flash
(What I think is 1:yes 2:If i knew i wouldn't be here 3:yes 4:backup system images 5: Yes
Thanks
Click to expand...
Click to collapse
There are different types of treble devices you know. Only a couple GSI work on the g6.
GSI is a system image, so usually flash with fastboot.
Fastboot flash system system.img
Or in TWRP with the "install image" option.
The G6 does not have a b partition. So only try ones that say "arm A only". Meaning arm, not arm 64, and a - only, not a/b.
There is an entire section of this site devoted to it. Search "Project Treble". Without the quotes obviously
Here you go
https://forum.xda-developers.com/project-treble
Better yet here ya go
Built for the g6.
All GSIs are generic system images, so technically they can Flash on any device that has treble (with the correct CPU architecture and partitioning scheme) but when one gets built for your device most of the bugs have been worked out
madbat99 said:
There are different types of treble devices you know. Only a couple GSI work on the g6.
GSI is a system image, so usually flash with fastboot.
Fastboot flash system system.img
Or in TWRP with the "install image" option.
The G6 does not have a b partition. So only try ones that say "arm A only". Meaning arm, not arm 64, and a - only, not a/b.
There is an entire section of this site devoted to it. Search "Project Treble". Without the quotes obviously
Here you go
https://forum.xda-developers.com/project-treble
Better yet here ya go
Built for the g6.
All GSIs are generic system images, so technically they can Flash on any device that has treble (with the correct CPU architecture and partitioning scheme) but when one gets built for your device most of the bugs have been worked out
Click to expand...
Click to collapse
Thank you so much. I installed Lineage OS from https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029 and my phone is working HOWEVER I can't read battery usage from setting but /data/system/batterystats.bin exists
Android Adam said:
Thank you so much. I installed Lineage OS from https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029 and my phone is working HOWEVER I can't read battery usage from setting but /data/system/batterystats.bin exists
Click to expand...
Click to collapse
I would try the one I linked to. It is the most likely to have everything working. Descendant two dot two
The one you're trying to use says it's extremely specific to his device. Majorly buggy for others. Including A only devices.
Android Adam said:
Thank you so much. I installed Lineage OS from https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029 and my phone is working HOWEVER I can't read battery usage from setting but /data/system/batterystats.bin exists
Click to expand...
Click to collapse
Did you ever manage to get battery to work? Mine doesn't either nor does the USB-C port
Sorry I need help installing the ROM GSi RR I get an error in the text of insufficient space and I get error 70 to someone else happens? And I tried to fix the problem and when I managed to install the gapps the phone did not start someone can help me?
ACM1PT said:
Sorry I need help installing the ROM GSi RR I get an error in the text of insufficient space and I get error 70 to someone else happens? And I tried to fix the problem and when I managed to install the gapps the phone did not start someone can help me?
Click to expand...
Click to collapse
Please link to the rom so I can try to help. describe what you're trying to do
Android Adam said:
Please link to the rom so I can try to help. describe what you're trying to do
Click to expand...
Click to collapse
Could you give me a guide on how to install with gapps? Sorry I have to write in English everything I did my language is Spanish sorry
ACM1PT said:
Could you give me a guide on how to install with gapps? Sorry I have to write in English everything I did my language is Spanish sorry
Click to expand...
Click to collapse
I need to know which rom you are using. Please post a link to it. Is this it https://www.google.com/amp/s/forum....urrection-remix-v7-0-arm64-32-b-t3891636/amp/
Android Adam said:
I need to know which rom you are using. Please post a link to it. Is this it https://www.google.com/amp/s/forum....urrection-remix-v7-0-arm64-32-b-t3891636/amp/
Click to expand...
Click to collapse
Are you using Oreo or pie
Android Adam said:
Are you using Oreo or pie
Click to expand...
Click to collapse
pie bro,
I will try to install again have it happen
ACM1PT said:
pie bro,
I will try to install again have it happen
Click to expand...
Click to collapse
I found the problem. The system partition is too small so GApps always fails. To solve it go to twrp adb push your rom, and flash it. Then go to format then system hit repair then resize and confirm. Of you are flashing a big GApps (Super) do it again. Flash GApps then Magisk (for root) then you're done