Related
This is it guys... HUGE props to bigrushdog (his kernel made this possible!), MADindustries and modplan!
Download the Motorola WiFi Xoom Root Zip file and unzip it. (MediaFire) - Contains Tiamat 1.3.1
You need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
You'll need fastboot - get it here http://developer.htc.com/adp.html
Make sure you have the latest SDK - adb and fastboot should be in /platform-tools - http://developer.android.com/sdk/index.html
Place the files in the SDK Tools folder.
If rebooting works... - This will wipe your phone by the way!!
adb reboot bootloader
fastboot oem unlock
adb reboot bootloader
If stuck at "Dual Core Technology"
Hold VolUp and power to restart Xoom
Hold VolDown will booting unit for fastboot mode
fastboot flash boot boot.img
fastboot reboot
adb shell
mkdir /data/media/sdcard2
exit
(physically put in microSD card if you are planning to use)
adb reboot
adb remount
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
adb push cifs.ko /system/lib/modules/cifs.ko
adb push tun.ko /system/lib/modules/tun.ko
adb push scsi_wait_scan.ko /system/lib/modules/scsi_wait_scan.ko
adb push su /system/bin
adb shell ln -s /system/bin/su /system/xbin/su
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app
adb push vold.fstab /system/etc/vold.fstab
adb reboot
adb shell
WE HAZ ROOT!!
Check out this video for basic Windows walkthrough from Buddhahb - http://www.youtube.com/watch?v=ZsVpY0PDwtQ
Check out this video for basic Mac walkthrough from sleeplessninjas - http://www.youtube.com/watch?v=zC6J-hV6SM4
Update: 3/27/2011 12:04pm CST Added cifs.ko, tun.ko, and scsi_wait_scan.ko
Update: 3/27/2011 12:22pm CST Added vold.fstab file for USB mounting & MegaUpload
Update: 4/13/2011 10:07am CST Updated to Tiamat's 1.3.1 kernel for SD card support & Gallery support.
awesome work guys!
Woooooooooooooooooooooooooot
fantastic work!!
\o/
can you try the cifs.ko module as well? i have a 3g version and am curious
Thanks Xaositek and HUGE props to MADindustries and modplan for coming up with a quick solution.
Is there a rip of the stock "boot.img" in case it doesn't work so that people who soft brick their xoom can return it back to stock? If so can that be posted in the OP's post? I know I am not the only paranoid one that would like to have the stock boot.img before attempting any rooting.
Also just for curiousity, can someone explain the differences between the wifi and wifi+3g boot.img versions and what they had to do to workaround this. Thanks.
We end up replacing the stock boot - We'll probably need to wait for Motorola to toss us a bone there
I just downloaded the "xoomwifiroot.zip" file and realized the files in the "xoomwifiroot.zip" are just tiamat's 1.1.6 files (boot.img and kernel modules) that can be found in tiamat's thread.
I was expecting the files to be something different that was close to the original root method by Koush where there is a "rootboot.img".
Maybe a better question for my understanding is this. Sorry if I am a noob.
Is Koush's file rootboot.img for the original xoom root only good for rooting the system while tiamat's boot.img file not only roots the system but also has code to overclock the xoom?
ericdabbs said:
I just downloaded the "xoomwifiroot.zip" file and realized the files in the "xoomwifiroot.zip" are just tiamat's 1.1.6 files (boot.img and kernel modules) that can be found in tiamat's thread.
Click to expand...
Click to collapse
It also has the su and Superuser.apk but essentially yes...
ericdabbs said:
Is Koush's file rootboot.img for the original xoom root only good for rooting the system while tiamat's boot.img file not only roots the system but also has code to overclock the xoom?
Click to expand...
Click to collapse
Koush's rootboot got us into this mess, Tiamat's boot.img got us out of it. It also allows the critical adb remount to allow the next steps.
Xaositek said:
It also has the su and Superuser.apk but essentially yes...
Koush's rootboot got us into this mess, Tiamat's boot.img got us out of it. It also allows the critical adb remount to allow the next steps.
Click to expand...
Click to collapse
Gotcha. Thanks for all your help.
ericdabbs said:
Gotcha. Thanks for all your help.
Click to expand...
Click to collapse
Grab the latest file from MegaUpload and add the additional modules
glad I could help get this working and glad that it fixed my bricked xoom! One thing that I would suggest is someone pull the stock ko files and save them, after moto releases the stock boot.img files I am sure that there will be some people that want to go back to the stock kernel which will then be as easy as flashing the stock boot.Img and then pushing the stock ko files back on.
Guess I'll run out and grab one now at Best Buy then. Thanks!
modplan said:
glad I could help get this working and glad that it fixed my bricked xoom! One thing that I would suggest is someone pull the stock ko files and save them, after moto releases the stock boot.img files I am sure that there will be some people that want to go back to the stock kernel which will then be as easy as flashing the stock boot.Img and then pushing the stock ko files back on.
Click to expand...
Click to collapse
Is there a way to extract the stock boot.img and wifi ko files before flashing it with tiamat's files? If so, what are the instructions so that people who haven't rooted it yet can give it a try. That way we can give back to the community.
ericdabbs said:
Is there a way to extract the stock boot.img and wifi ko files before flashing it with tiamat's files? If so, what are the instructions so that people who haven't rooted it yet can give it a try. That way we can give back to the community.
Click to expand...
Click to collapse
Pulling the boot image looks like it is rather difficult but pulling the ko files should be as simple as using the adb pull command instead of adb push. For example
Adb pull /system/lib/modules/something.ko c:/something.ko (put the right paths obviously the second path is just where you want to save it on your computer)
As an FYI. coolbho's ocboot.img does not work on the wi-fi version of the xoom yet. To prevent your headaches I have already flashed and it stays at boot screen. Tiamat's seems the only kernel that is working for wi-fi only
modplan said:
Pulling the boot image looks like it is rather difficult but pulling the ko files should be as simple as using the adb pull command instead of adb push. For example
Adb pull /system/lib/modules/something.ko c:/something.ko (put the right paths obviously the second path is just where you want to save it on your computer)
Click to expand...
Click to collapse
Got it. When I get my wifi xoom, I'll give this a shot.
d3coy3d said:
As an FYI. coolbho's ocboot.img does not work on the wi-fi version of the xoom yet. To prevent your headaches I have already flashed and it stays at boot screen. Tiamat's seems the only kernel that is working for wi-fi only
Click to expand...
Click to collapse
Tiamat's kernel allows for the 1.5ghz OC
When i command to push the first file, I get all the info on android debug.
chaz03 said:
When i command to push the first file, I get all the info on android debug.
Click to expand...
Click to collapse
Revisit the instructions now - you can just copy and paste them all now
I have a gsm Galaxy Nexus and I just wanted to find out what commands to use to flash a boot image from the terminal. I used to use flash_img command but that doesn't work on the GN.
daggerxXxsin said:
I have a gsm Galaxy Nexus and I just wanted to find out what commands to use to flash a boot image from the terminal. I used to use flash_img command but that doesn't work on the GN.
Click to expand...
Click to collapse
you need to have a working flash_image file in your /system/bin/.
http://forum.xda-developers.com/showthread.php?t=1443017
Will this work? It says ICS on it though..
daggerxXxsin said:
http://forum.xda-developers.com/showthread.php?t=1443017
Will this work? It says ICS on it though..
Click to expand...
Click to collapse
well, there no working flash_image files in that thread. but, there is an alternative method of flashing via terminal there.
simms22 said:
well, there no working flash_image files in that thread. but, there is an alternative method of flashing via terminal there.
Click to expand...
Click to collapse
Oh shoot I think I posted the wrong link. Oh well, I guess I'll see if I can Google the right path for the boot partition and try that command.
Hello everyone!
Here's another release thread for y'all!
What is this?
This is a flashable ClockworkMod recovery for the Optimus G Pro.
Special thanks to @djrbliss
You can safely flash this to your phone's recovery and enjoy modding bliss!
How do I use this, and where do I get it?
Good question!
There are two ways to use the files provided here.
To Flash to Recovery:
Download this file to somewhere on your computer https://github.com/djrbliss/loki/raw/master/bin/loki_flash
Download this file http://downloads.codefi.re/thecubed/lgoptimusg_pro/gkatt/recovery/e98010g/gkatt-cwm-e98010g.lok
Run the following:
Code:
adb push loki_flash /data/local/tmp
adb push gkatt-cwm-e98010g.lok /data/local/tmp
abd shell
su
cd /data/local/tmp
chmod 755 loki_flash
./loki_flash recovery gkatt-cwm-e98010g.lok
To boot
Download this file: http://downloads.codefi.re/thecubed/lgoptimusg_pro/gkatt/recovery/e98010g/gkatt-cwm-e98010g.img
Use fastboot boot to boot it
DO NOT FLASH THE .IMG FILE TO YOUR PHONE. It is only meant for fastboot booting.
Where can I find the source you used to build this?
All on my github!
http://github.com/thecubed/
Or, follow my guide here:
http://forum.xda-developers.com/showthread.php?p=43514195
What can I do with this?
Right now, the possibilities are unlimited. Once a security-lax boot.img is released, we can flash that through recovery and let the modding commence.
Please remember though, modding /system with the stock boot.img will result in a security error!
What works, and what doesnt?
I have so far tested making backup images, however I haven't tested restoring them.
I have also not tested external SD cards, since I don't have one with me at work.
Can you show me a video?
Why yes I can!
As usual, please pardon the crappy camera work.
I <3 you so much, how do I show my love?
You are so kind
I most definitely do not expect donations of any kind, however they are appreciated a lot.
I purchased this phone off-contract just to get it unlocked, if you are a kind soul and would like to send me a token of your appreciation I would love you forever.
XDA has a neat "Donate to me" button that should be on the left side of this page under my name. Donations go to purchasing new hardware to work on and other neat stuff, so they're always appreciated.
Special Thanks!
In no particular order, special thanks to all of you guys!
djrbliss
synergy
Shelnutt2
DeamonFish
If I forgot anyone, let me know and I'll add you here!
Alright guys! Let me know if you find any bugs!
Can I flash this threw dd?
Sent from my LG-E980 using xda premium
Gotroot said:
Can I flash this threw dd?
Sent from my LG-E980 using xda premium
Click to expand...
Click to collapse
We could just run Loki flash from terminal and flash that way if no adb as for the second Part we'd need fastboot on our computer
Sent from my LG-E980 using xda premium
This is some serious progress! :thumbup::thumbup:
Sent from my LG-E980 using Tapatalk 2
Btw cube external sd does work !!!
Sent from my LG-E980 using xda premium
Gotroot said:
Can I flash this threw dd?
Sent from my LG-E980 using xda premium
Click to expand...
Click to collapse
Yes you can, just do the following:
Code:
adb push gkatt-cwm-e98010g.lok /data/local/tmp
adb shell
su
dd if=/data/local/tmp/gkatt-cwm-e98010g.lok of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Getting into recovery is as simple as "adb reboot recovery" or holding the proper volume keys.
I just recommend using Dan's excellent loki_flash utility since it checks to make sure you have the right bootloader in place already.
fastboot info
Would be nice to have more info on how to use fastboot with the .img file. I tried all I know with no results. Thanks!
G0bl1n said:
Would be nice to have more info on how to use fastboot with the .img file. I tried all I know with no results. Thanks!
Click to expand...
Click to collapse
Not sure what you're asking. To flash any .img file without any modifications requires our bootloader to be unlocked. What's going on here is everything needs to be "Loki'ed" so our phones are able to flash unsigned code through a custom recovery, bypassing our locked bootloader.
Fastboot is a way of testing unsigned code without having to necessarily flash it to any partitions.
Anyone correct me if I'm wrong, as I'm definitely not a developer. I just read a lot lol
thecubed said:
Hello everyone!
Here's another release thread for y'all!
What is this?
This is a flashable ClockworkMod recovery for the Optimus G Pro.
Special thanks to @djrbliss
You can safely flash this to your phone's recovery and enjoy modding bliss!
How do I use this, and where do I get it?
Good question!
There are two ways to use the files provided here.
To Flash to Recovery:
Download this file to somewhere on your computer https://github.com/djrbliss/loki/raw/master/bin/loki_flash
Download this file http://downloads.codefi.re/thecubed/lgoptimusg_pro/gkatt/recovery/e98010g/gkatt-cwm-e98010g.lok
Run the following:
Code:
adb push loki_flash /data/local/tmp
adb push gkatt-cwm-e98010g.lok /data/local/tmp
abd shell
su
cd /data/local/tmp
chmod 755 loki_flash
./loki_flash recovery gkatt-cwm-e98010g.lok
To boot
Download this file: http://downloads.codefi.re/thecubed/lgoptimusg_pro/gkatt/recovery/e98010g/gkatt-cwm-e98010g.img
Use fastboot boot to boot it
DO NOT FLASH THE .IMG FILE TO YOUR PHONE. It is only meant for fastboot booting.
What can I do with this?
Right now, the possibilities are unlimited. Once a security-lax boot.img is released, we can flash that through recovery and let the modding commence.
Please remember though, modding /system with the stock boot.img will result in a security error!
What works, and what doesnt?
I have so far tested making backup images, however I haven't tested restoring them.
I have also not tested external SD cards, since I don't have one with me at work.
Can you show me a video?
Why yes I can!
As usual, please pardon the crappy camera work.
I <3 you so much, how do I show my love?
You are so kind
I most definitely do not expect donations of any kind, however they are appreciated a lot.
I purchased this phone off-contract just to get it unlocked, if you are a kind soul and would like to send me a token of your appreciation I would love you forever.
XDA has a neat "Donate to me" button that should be on the left side of this page under my name. Donations go to purchasing new hardware to work on and other neat stuff, so they're always appreciated.
Special Thanks!
In no particular order, special thanks to all of you guys!
djrbliss
synergy
Shelnutt2
DeamonFish
If I forgot anyone, let me know and I'll add you here!
Alright guys! Let me know if you find any bugs!
Click to expand...
Click to collapse
If I have the old ClockworkMod, can I still do this or do I have to get rid of it somehow?
Are there any special precautions someone should take if they have this recovery already flashed to our phones?
Flashing with the latest "loki_flash" from dan's repos is segfaulting here and I'm too lazy to run it in gdb. The recovery works just fine with dd after zeroing the recovery partition out. Thanks mucho :good:
Coming from the Note I'm not use to locked bootloader.
Should we all install this if our goal is to eventually flash custom roms?
Yoreo said:
Are there any special precautions someone should take if they have this recovery already flashed to our phones?
Click to expand...
Click to collapse
Had that recovery and I had one of the first cwm Loki recoveries flashed this one just fine no issues
Sent from my LG-E980 using xda premium
acejoker25000 said:
Had that recovery and I had one of the first cwm Loki recoveries flashed this one just fine no issues
Sent from my LG-E980 using xda premium
Click to expand...
Click to collapse
Sounds good. Thanks.
madmack said:
Flashing with the latest "loki_flash" from dan's repos is segfaulting here and I'm too lazy to run it in gdb. The recovery works just fine with dd after zeroing the recovery partition out. Thanks mucho :good:
Click to expand...
Click to collapse
did the gdb backtrace:
Code:
Program received signal SIGSEGV, Segmentation fault.
0x4016ffa0 in memcmp () from /home/madmack/tmp/gdb/libs/libc.so
(gdb) bt
#0 0x4016ffa0 in memcmp () from /home/madmack/tmp/gdb/libs/libc.so
#1 0x00008868 in main ()
(gdb) bt
#0 0x4016ffa0 in memcmp () from /home/madmack/tmp/gdb/libs/libc.so
#1 0x00008868 in main ()
(gdb) quit
One of the memcmp commands is segfaulting. Perhaps @djrbliss can have a look when he gets some free time.
madmack said:
Flashing with the latest "loki_flash" from dan's repos is segfaulting here and I'm too lazy to run it in gdb. The recovery works just fine with dd after zeroing the recovery partition out. Thanks mucho :good:
Click to expand...
Click to collapse
what do you mean?
need zeroing the recovery partition before using dd to flash recovery image?
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/data/local/tmp/gkatt-cwm-e98010g.lok of=/dev/block/platform/msm_sdcc.1/by-name/recovery
GREAT.... I can using this to "adb reboot recovery" with CWM recovery on my E988 HK version ^^
so what is next, how to try boot my custom boot kernel ???
Timisone said:
If I have the old ClockworkMod, can I still do this or do I have to get rid of it somehow?
Click to expand...
Click to collapse
I have a few a questions. When do I run the commands? Command prompt in windows? What mode does my phone need to be in to flash this?
hkfriends said:
what do you mean?
need zeroing the recovery partition before using dd to flash recovery image?
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/gkatt-cwm-e98010g.lok of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Click to expand...
Click to collapse
It's just an extra step I like taking before flashing a partition with data that might be smaller than the original. And yes, that's pretty much what I typed.
madmack said:
It's just an extra step I like taking before flashing a partition with data that might be smaller than the original. And yes, that's pretty much what I typed.
Click to expand...
Click to collapse
another issue:
I am using loki_patch v1.5 to patch my custom build kernel
then I flash this Loki'ed kernel to my E988 (by CWM recovery) and it keep re-boot loop
(with the wording => Cause: Device Unlock, so boot success!!....) ==> it is the same Ok msg with boot to CWM recovery
which I believe if boot image LOKI'ed should be good
PS: I fixed this by re-flash the good boot image by CWM
Here is the output of the patching msg
[email protected]:/usr/android# ./loki_patch-linux-x86_64 boot aboot.img myboot.img myboot.lok
[+] loki_patch v1.5
[+] Detected target AT&T or HK LG Optimus G Pro build E98010g or E98810b
[+] Output file written to myboot.lok
[email protected]:/usr/android#
call me lazy, is there a zip file I could flash to do this from within the 2nd init recovery? :fingers-crossed:
I have never used adb before...
This guide presupposes that you have Supersu installed as systemless, and that you have access to adb.
This will bypass provisioning checks for builtin tether app. The modded apk should work with future updates without touching /system at all.
Installation
Method 1 - Manual install
Download the attached CarrierEntitlement apk.
If you have su.img su:
Code:
adb push CarrierEntitlement.apk /sdcard/CarrierEntitlement.apk
adb shell
su
mkdir /su/CarrierEntitlement
cp /sdcard/CarrierEntitlement.apk /su/CarrierEntitlement/CarrierEntitlement.apk
chmod 644 /su/CarrierEntitlement/CarrierEntitlement.apk
echo "mount -o bind /su/CarrierEntitlement/CarrierEntitlement.apk /system/priv-app/CarrierEntitlement/CarrierEntitlement.apk" > /su/su.d/05TetherMod
chmod +x /su/su.d/05TetherMod
reboot
If you have sbin su (Android 8.0+)
Code:
adb push CarrierEntitlement.apk /sdcard/CarrierEntitlement.apk
adb shell
su
mkdir /sbin/supersu/CarrierEntitlement
cp /sdcard/CarrierEntitlement.apk /sbin/supersu/CarrierEntitlement/CarrierEntitlement.apk
chmod 644 /sbin/supersu/CarrierEntitlement/CarrierEntitlement.apk
echo "mount -o bind /sbin/supersu/CarrierEntitlement/CarrierEntitlement.apk /system/priv-app/CarrierEntitlement/CarrierEntitlement.apk" > /sbin/supersu/su.d/05TetherMod
chmod +x /sbin/supersu/su.d/05TetherMod
reboot
Method 2 - Flashable Zip (su.img only)
Code:
1. Download attached zip.
2. Flash in TWRP (Last tested in alpha 2)
Information
This mod is accomplished by replacing the following function:
Code:
.method public static getCarrierEntitlement(Landroid/content/Context;)Lcom/google/android/carrierentitlement/CarrierEntitlement;
.registers 2
.param p0, "context" # Landroid/content/Context;
.prologue
.line 56
const/4 v0, 0x0
return-object v0
.end method
NOTE: Post install
You may need to edit your APNs to get tethering working for your carrier.
On sprint, where editing APNs is disabled, the fix is here: Sprint Fix
Be sure to thank @Builtfordtough1 for all his help in diagnosing the issue at this post: The Solution!
Be sure to thank sb1893 for sbin su instructions.
Worked Perfectly
This worked perfectly. Fantastic job!
So I am on stock with unlocked bootloader, twrp installed, and rooted with SuperSU. Because this is an apk file, do i just download onto the phone and install as I would with any other .apk file?
coolhandz said:
So I am on stock with unlocked bootloader, twrp installed, and rooted with SuperSU. Because this is an apk file, do i just download onto the phone and install as I would with any other .apk file?
Click to expand...
Click to collapse
The directions clearly state in adb speak that you need to create a directory for the file. Move to said directory, change permissions, etc etc. Nothing about installing via the apk.
pcriz said:
The directions clearly state in adb speak that you need to create a directory for the file. Move to said directory, change permissions, etc etc. Nothing about installing via the apk.
Click to expand...
Click to collapse
well, i can follow basic commands in minimal adb & fastboot. I think this may be above me unless there is an idiots' guide.
coolhandz said:
well, i can follow basic commands in minimal adb & fastboot. I think this may be above me unless there is an idiots' guide.
Click to expand...
Click to collapse
Do you have access to adb? They are pretty straight forward. May need to view them on the website but if you are using an app it may throw the word wrap off and make the commands seem confusing. The directions are pretty word for word.
pcriz said:
Do you have access to adb? They are pretty straight forward. May need to view them actually on the website but if you are using an app it may throw the word wrap off and make the commands seem confusing. The directs are pretty word for word.
Click to expand...
Click to collapse
If by adb you mean minimal adb & fastboot, then yes I have access and I could probably brave it.
coolhandz said:
If by adb you mean minimal adb & fastboot, then yes I have access and I could probably brave it.
Click to expand...
Click to collapse
I wouldn't suggest doing it how I did it but I downloaded the file to my phone. I created the directory using a root enabled file browser (see mkdir command {make directory}). I even used the file properties option in solid explorer to change the permissions (see chmod 644). Every other command I did on the phone from a terminal emulator. Just had to ignore the adb shell command because I am actually doing them on the device and not through a shell on my computer.
pcriz said:
I wouldn't suggest doing it how I did it but I downloaded the file to my phone. I created the directory using a root enabled file browser (see mkdir command {make directory}). I even used the file properties option in solid explorer to change the permissions (see chmod 644). Every other command I did on the phone from a terminal emulator. Just had to ignore the adb shell command because I am actually doing them on the device and not through a shell on my computer.
Click to expand...
Click to collapse
yeah, all that is definitely outside of my comfort zone, but thank you for the info.
Can you normally update your device with OTA-updates like a un-rooted device, without flashfire or connect to your computer?
Is there an advantage to doing this over adding "net.tethering.noprovisioning=true" to the build.prop file?
airmaxx23 said:
Is there an advantage to doing this over adding "net.tethering.noprovisioning=true" to the build.prop file?
Click to expand...
Click to collapse
This mod is systemless, and should survive OTAs. That mod changes the build.prop on the system partition, which could prevent taking OTAs.
njeri123 said:
Can you normally update your device with OTA-updates like a un-rooted device, without flashfire or connect to your computer?
Click to expand...
Click to collapse
Any modification to the boot image *should* prevent OTAs from working at all. However, you can flash back to stock boot images, and take OTAs as long as you have not modified /system, which this mod does not do.
Furthermore, as long as you don't wipe /data/ this mod will live in su.img and survive when you flash newer system software.
Fenny said:
This mod is systemless, and should survive OTAs. That mod changes the build.prop on the system partition, which could prevent taking OTAs.
Any modification to the boot image *should* prevent OTAs from working at all. However, you can flash back to stock boot images, and take OTAs as long as you have not modified /system, which this mod does not do.
Furthermore, as long as you don't wipe /data/ this mod will live in su.img and survive when you flash newer system software.
Click to expand...
Click to collapse
Thanks for the explanation, I removed the build.prop line and used this method and it's working fine. Thank you.
@Fenny
Thank you so much for putting this into a .zip file. It is greatly appreciated!
is there a non root method to bypass the checks? i dont plan on unlocking or rooting since i use android pay...
ddarvish said:
is there a non root method to bypass the checks? i dont plan on unlocking or rooting since i use android pay...
Click to expand...
Click to collapse
I also use Android pay, so I have two boot images ready to fastboot or flash. I have a boot image with root, and a boot image without root running a kernel that hides the bootloader unlocked flag.
So, the way I handle this, I flash the unrooted (bootloader flag hidden) image as my daily driver kernel, this passes safetynet, and allows me to use Android pay.
I make a backup of that boot image. Then, I install TWRP, my custom kernel, and SuperSU. I make a backup of that image as well.
So I have two backed up boot images:
rooted.img
HideBLUnlock.img
I flash HideBLUnlock.img to boot a, and boot b, safetynet passes.
Whenever I need to tether I have my computer with me, so I "fastboot boot rooted.img" which leaves me rooted until my next reboot.
Depending on your usage you might want to reverse that.
All my mods get stored in su.img, so switching out the boot images is all I need to have the best of both worlds.
Is it possible to fastboot boot twrp and flash the zip without being rooted or having twrp actually installed? O unlocked my bootloader but that's been it
Ocelot13 said:
Is it possible to fastboot boot twrp and flash the zip without being rooted or having twrp actually installed? O unlocked my bootloader but that's been it
Click to expand...
Click to collapse
You can use the fastboot twrp image to install this mod but you MUST have SuperSu. I have basic validation to check that in my update.zip. If you don't have a su.img in /cache or /data, this mod cannot be installed.
Flashed via TWRP and now i finally have a fully functioning hotspot!!
Fenny said:
I also use Android pay, so I have two boot images ready to fastboot or flash. I have a boot image with root, and a boot image without root running a kernel that hides the bootloader unlocked flag.
So, the way I handle this, I flash the unrooted (bootloader flag hidden) image as my daily driver kernel, this passes safetynet, and allows me to use Android pay.
I make a backup of that boot image. Then, I install TWRP, my custom kernel, and SuperSU. I make a backup of that image as well.
So I have two backed up boot images:
rooted.img
HideBLUnlock.img
I flash HideBLUnlock.img to boot a, and boot b, safetynet passes.
Whenever I need to tether I have my computer with me, so I "fastboot boot rooted.img" which leaves me rooted until my next reboot.
Depending on your usage you might want to reverse that.
All my mods get stored in su.img, so switching out the boot images is all I need to have the best of both worlds.
Click to expand...
Click to collapse
This is facinating, do you ever think where we can use boot a and boot b in a multiboot like fashion so that when you turn on the device you can choose what to boot?
if i add some files or remove or add or everything it's just like it's read only, tried with 3 different root capable file manager and nothing, why?
double
has
Code:
fastboot flashing unlock_critical
something to do with that?
Root cannot modify vendor partition, you will need to either manually modify and create a vendor.img or push the modification thru recovery (twrp)..
Twrp or DD command is your best options.
loonycgb2 said:
Root cannot modify vendor partition, you will need to either manually modify and create a vendor.img or push the modification thru recovery (twrp)..
Twrp or DD command is your best options.
Click to expand...
Click to collapse
twrp doesn't work for lgg7 because encryption, already tried, how to use dd?