Related
https://threatpost.com/another-linux...access/137800/
Would be awesome if that works
I played around a little and this happened...
https://photos.app.goo.gl/TiEXrdKmWydRM8RZ9
S8ntsHaz3 said:
I played around a little and this happened...
https://photos.app.goo.gl/TiEXrdKmWydRM8RZ9
Click to expand...
Click to collapse
Unlock critical is allowed and already known thing but this is for flashing bootloader and stuff. It doesn't help us at all for now.
There are already many rooted tmobile g7 sold in China.
I found a possible root it looks like it will work with any lg g710 Oreo. Is this not the case?
https://www.androidinfotech.com/2018/06/root-lg-g7-thinq-lmg710-oreo.html
curster said:
I found a possible root it looks like it will work with any lg g710 Oreo. Is this not the case?
https://www.androidinfotech.com/2018/06/root-lg-g7-thinq-lmg710-oreo.html
Click to expand...
Click to collapse
anyone tried it yet?
kasuma_asuma said:
anyone tried it yet?
Click to expand...
Click to collapse
So it's a fake post for one (actually not exactly fake I would say more clickbait then anything) two I believe the T-Mobile version is the G710TM, three we have a gimped fastboot as in it doesn't work at all. And four I think our only option is something to do with LAF
---------- Post added at 11:22 AM ---------- Previous post was at 11:21 AM ----------
curster said:
I found a possible root it looks like it will work with any lg g710 Oreo. Is this not the case?
https://www.androidinfotech.com/2018/06/root-lg-g7-thinq-lmg710-oreo.html
Click to expand...
Click to collapse
No it's not the case see my previous answer
We should be able to get around this gimped fastboot by incorperating that boot.img from the EM varient into an "update" once the phone is cross flashed. To 710EM it will have "adb update" command (it will also think the update is for itself since the firmware matches what were flashing we can put this into a flashable.zip (im like 75% sure this is how its done). Then use the command "adb update boot /path to patch boot/" alternatively could we incorperate our patched boot.img into a kdz and flash it with a patched LGup? Once the phone is rooted with magisk we could use the twrp app to flash twrp and fastboot commands wont be extremely relevant
The problem is, how to remove or get around the correct oem unlock allowed verification system. Unpacking a .img and editing is not a problem, i am just not exactly sure what to edit.
alecthenice said:
We should be able to get around this gimped fastboot by incorperating that boot.img from the EM varient into an "update" once the phone is cross flashed. To 710EM it will have "adb update" command (it will also think the update is for itself since the firmware matches what were flashing we can put this into a flashable.zip (im like 75% sure this is how its done). Then use the command "adb update boot /path to patch boot/" alternatively could we incorperate our patched boot.img into a kdz and flash it with a patched LGup? Once the phone is rooted with magisk we could use the twrp app to flash twrp and fastboot commands wont be extremely relevant
The problem is, how to remove or get around the correct oem unlock allowed verification system. Unpacking a .img and editing is not a problem, i am just not exactly sure what to edit.
Click to expand...
Click to collapse
I'm will definitely get root on every other device but there's two things that stop us.
1) it's impossible to extract anything from a kdz and a .up file (LGs way of updating)
2) dm-verify (but it's possible to get around)
LameMonster82 said:
I'm will definitely get root on every other device but there's two things that stop us.
1) it's impossible to extract anything from a kdz and a .up file (LGs way of updating)
2) dm-verify (but it's possible to get around)
Click to expand...
Click to collapse
So for dm-verify I know how to manually get around that and the patch thats floating around via flashable.zip. What do we need to extract from the .up or .kdz? Im pretty sure there is a full kdz dump for the 710EM in a thread I read through just last night? I really believe the only obstacle we have is making the bootloader unlock through a command line independent of the official unlock code. This should be able to be acheived by editing that in a way to where it doesnt check much like dm-verity. Then you can flash your (patched by deletion) boot.img run fastboot oem unlock ( btw did you know that "fastboot oem flashing unlock critical works) **could run that then flash an unlock.bin, then fastboot oem unlock unlock.bin** I am working with a 710pm varient. And am speaking from experience rooting the v30 ls version currently using G7 as daily driver
This leaves me thinking that we have lots of wiggle room here (also leaves me thinking how weird LG is for having a lot of variation within G7)
LameMonster82 said:
I'm will definitely get root on every other device but there's two things that stop us.
1) it's impossible to extract anything from a kdz and a .up file (LGs way of updating)
2) dm-verify (but it's possible to get around)
Click to expand...
Click to collapse
I use LG Firmware Extract to get the DLL's out, the problem is theres no firmware yet for the LG G7 Sprint version:
View attachment 4667707
GROOVYJOSHCLARK said:
I use LG Firmware Extract to get the DLL's out, the problem is theres no firmware yet for the LG G7 Sprint version:
Click to expand...
Click to collapse
Amazingly this week I was able to extract everything from any kdz file. The problem is that repacking requires certificate and we don't have it.
LameMonster82 said:
Amazingly this week I was able to extract everything from any kdz file. The problem is that repacking requires certificate and we don't have it.
Click to expand...
Click to collapse
Yes but we will figure it out eventually. I'm on Sprint myself and actively trying to figure out the LG cross flashing issue.
GROOVYJOSHCLARK said:
Yes but we will figure it out eventually. I'm on Sprint myself and actively trying to figure out the LG cross flashing issue.
Click to expand...
Click to collapse
So, do you want to cross flash or just the Sprint firmware
LameMonster82 said:
So, do you want to cross flash or just the Sprint firmware
Click to expand...
Click to collapse
There is no cross flashing on the G7 (or V35 or V40) unless you want a brick. LG got smart after the V30 WTF exploit and now uses a different RSA cert for every model.
Don't take my word for it, please feel free to try -- make sure you have insurance
-- Brian
runningnak3d said:
There is no cross flashing on the G7 (or V35 or V40) unless you want a brick. LG got smart after the V30 WTF exploit and now uses a different RSA cert for every model.
Don't take my word for it, please feel free to try -- make sure you have insurance
-- Brian
Click to expand...
Click to collapse
Yes but we will figure it out eventually so we can flash the EM firmware and unlock the bootloader then root and install TWRP then AOSP. I am waiting on my octoplus box to arrive then I'll be testing cross flashing for others to sort out what's needed.
GROOVYJOSHCLARK said:
Yes but we will figure it out eventually so we can flash the EM firmware and unlock the bootloader then root and install TWRP then AOSP. I am waiting on my octoplus box to arrive then I'll be testing cross flashing for others to sort out what's needed.
Click to expand...
Click to collapse
Awesome! But octoplus will not allow you to cross flashing, right?
any news on this ? would love to change my T-mobile software. and get the fingerprint to work for that matter
TLDR: i did everything people say except adb and reflash
like god damn man my phone is so damn slow i wanna install lineage os
im trying to root my a10e but no oem
im connected to a google account
im connected to a samsung account
i havent turned it off
i have over 1 week uptime
im connected to wifi
ive had dev options thisnhole time
ive tried everything to no avail
do i need to reflash the firmware????
ive heard that before
do i need to enable via adb
and yes i have tried to disable auto update change the date
do a update nothing works
if i need to enable via adb then whats the command is not on android webpage for change system settings via adb
also does this work with heimdall on osx
i have an old windows 10 pc tho
does heimdall need some sort of drivers?
the drivers on samsung website
are only for windows
i have heard it working with wine tho
odin also works on wine ive heard
newrandomaccountbruh said:
TLDR: i did everything people say except adb and reflash
like god damn man my phone is so damn slow i wanna install lineage os
im trying to root my a10e but no oem
im connected to a google account
im connected to a samsung account
i havent turned it off
i have over 1 week uptime
im connected to wifi
ive had dev options thisnhole time
ive tried everything to no avail
do i need to reflash the firmware????
ive heard that before
do i need to enable via adb
and yes i have tried to disable auto update change the date
do a update nothing works
if i need to enable via adb then whats the command is not on android webpage for change system settings via adb
also does this work with heimdall on osx
i have an old windows 10 pc tho
does heimdall need some sort of drivers?
the drivers on samsung website
are only for windows
i have heard it working with wine tho
odin also works on wine ive heard
Click to expand...
Click to collapse
So any solution on how to bypass the waiting problem? Im on the a11 115mu. Same boat as you.
Fandroid Tech said:
So any solution on how to bypass the waiting problem? Im on the a11 115mu. Same boat as you.
Click to expand...
Click to collapse
Watch this video:
jwoegerbauer said:
Watch this video:
Click to expand...
Click to collapse
Watched it before, it seems I need to wait 7 days for it to get unlocked. I read something about changing dates to trick it.
Fandroid Tech said:
Watched it before, it seems I need to wait 7 days for it to get unlocked. I read something about changing dates to trick it.
Click to expand...
Click to collapse
Is your phone a US phone? If so it's not possible. There are many other posts on here that have gone to great detail about why you can't OEM bootloader unlock US Samsung phones. If you have an international version or an Asian phone you might be in luck.
richaardvark said:
Is your phone a US phone? If so it's not possible. There are many other posts on here that have gone to great detail about why you can't OEM bootloader unlock US Samsung phones. If you have an international version or an Asian phone you might be in luck.
Click to expand...
Click to collapse
no, its some mexican or brazilian. i reflaherd the bootloader so it relocked
richaardvark well would it be the same model number if it was diffrent region mines a sm-a102u1 and fandroid i have over 300 hr uptime i did my research i need a sim card im buying a textnow sim card
Success is disgusted by some people, and will not share any files for free in the future.
Once again you proved it bro. Amazing job will test now and confirm.
Working perfectly tested and rooted. Steps are easy to follow.
1) Download the ENG firmware and flash it following the steps.
2) Then follow this post and the commands to extract asuskey4 and add ISN to the asuskey4.
3) Flash WW ROM back to the phone.
4) Use Unlock tool and then done.
by far one of the best contributions of the forum, I don't usually comment, but I had to thank you
This is huge! The answer everyone with Tencent WW phones were looking for! Thank you
Could anyone please elaborate step 1 (flashing the ENG firmware provided)?
My phone enters edl mode and I see port 9008 in the device manager.
What should I do next?
arjun_m4 said:
Working perfectly tested and rooted. Steps are easy to follow.
1) Download the ENG firmware and flash it following the steps.
2) Then follow this post and the commands to extract asuskey4 and add ISN to the asuskey4.
3) Flash WW ROM back to the phone.
4) Use Unlock tool and then done.
Click to expand...
Click to collapse
yes,very easy
Can NOT flash ENG firmware..
Method # 1 : "0-update_image_EDL.bat" does not even start
Method # 2 : ERROR_UNSUPPORTED_TYPE
Method # 3 : Download Fail:FireHose Fail: FHLoader Fail: process fail
SOS guys! I am in deep sh*t!!
I cant find the SSN in the device.txt ... Only ISN is available .. ?
JazonX said:
I cant find the SSN in the device.txt ... Only ISN is available .. ?
Click to expand...
Click to collapse
You can see SSN on our phone when you boot up ENG firmware just type urself to the editor.
Find the address mentioned and start typing from first 0 u will see the HEX changing and then verify it's correct and save
aimsjahan said:
Can NOT flash ENG firmware..
Method # 1 : "0-update_image_EDL.bat" does not even start
Method # 2 : ERROR_UNSUPPORTED_TYPE
Method # 3 : Download Fail:FireHose Fail: FHLoader Fail: process fail
SOS guys! I am in deep sh*t!!
Click to expand...
Click to collapse
Can you check if your phone is being recognized as EDL maybe the drivers are installed wrong. I can verify that the files provided works 100% and you have to use left side type c of the Asus not the bottom.
JazonX said:
I cant find the SSN in the device.txt ... Only ISN is available .. ?
Click to expand...
Click to collapse
SSN can be seen on the homepage of the mobile phone after flashing the ENG firmware, or on the packaging box of your mobile phone.
Asuskey4 software download link please
Thanks, @johnny886! Btw, can you change your post to "General" instead of "Question", and pin it to this forum so people would use it as a reference in the future?
arjun_m4 said:
Can you check if your phone is being recognized as EDL maybe the drivers are installed wrong. I can verify that the files provided works 100% and you have to use left side type c of the Asus not the bottom.
Click to expand...
Click to collapse
My ROG5 is being shown in Device Manager as Qualcomm 9008. So I guess it has entered in EDL mode.
aimsjahan said:
My ROG5 is being shown in Device Manager as Qualcomm 9008. So I guess it has entered in EDL mode.
Click to expand...
Click to collapse
Could you reinstall the drivers I have faced issues like this before with other Qualcomm devices. Reinstall Qualcomm drivers it should work. And remember to install with disable signature enforcement.
Akkaya34 said:
Asuskey4 software download link please
Click to expand...
Click to collapse
I think you haven't figured out how to do it. Please read the steps carefully before proceeding. . .
arjun_m4 said:
Could you reinstall the drivers I have faced issues like this before with other Qualcomm devices. Reinstall Qualcomm drivers it should work. And remember to install with disable signature enforcement.
Click to expand...
Click to collapse
Appreciate your response mate! I will try again after reinstalling QCOM drivers. Could you please share that driver you are using?
Also, my PC does NOT detect ROG5 when using the official USB-C on both end cable. I have to use another cable with USB in one end and USB-C in the other end. Do you think that might be an issue?
With lost imei , imei=0 , I correct imei , SN in asuskey4 but it not unlock
nguyenhung9x2018 said:
With lost imei , imei=0 , I correct imei , SN in asuskey4 but it not unlock
Click to expand...
Click to collapse
The asuskey4 should contain SSN and ISN then only it will unlock. Make sure it's there and how come you lost your IMEI I tried this for 2 separate devices and I didn't face any issue.
I attempted to convert my t-mobile oneplus 9 to international firmware by first flashing the Indian firmware.
I mistakenly downloaded the oneplus 9 PRO Indian msm.
I didn't realize this as the file has a very similar name. Lemonade_22.I.07_210412 vs Lemonadep_22_I.07_210412
I've tried everything since then, with no success. I tried to flash the correct oneplus 9 indian msm but it says incorrect device.
So I'm stuck with the oneplus 9 pro Indian firmware and can't get back to indian oneplus 9 firmware....
I have been developing and flashing android devices since the early days of Cyanogenmod... dozens of devices. And guess what? I did EXACTLY the same thing as you.
The link I downloaded from said it was Oneplus 9 firmware, and given the filenames being virtually identical, I never noticed it was the Oneplus 9 PRO firmware.
So don't feel too bad. Even experienced people can make mistakes when trying to flash phones!
I am working on a solution, but so far no luck because:
1. Msm Tool will not flash the Oneplus 9 firmware as it thinks it is the incorrect device (why did it let us flash the incorrect device firmware before???)
2. The bootloader is re-locked and the OEM Unlocking feature is greyed out in Developer options, therefore fastboot can't be used to re-flash the correct firmware.
3. The System Update "local upgrade" feature does not find ZIP files in the root folder and will not allow us to browse to the correct file.
So for now, we are stuck. I think solving #3 will be the solution. If we can make the "local upgrade" work, we should be able to flash the stock firmware ZIP.
@Derek6091 @mightysween did you fix it yet? I had my device screw up so bad today that the only MSM I could use on my global unit was the Indian 9 Pro firmware and I have gotten my device mostly working.
You can see my drama with it and how I finally got it working here.
[SOLVED] Can anyone help me unbrick? I have tried lite firehose, MSM for global, MSM for Indian 9 Pro, none work
I modded the global MSM so that it will flash to this frankenphone. https://forum.xda-developers.com/t/all-of-those-stuck-on-indian-firmware-rejoice-i-modded-the-global-msm.4442473/ EDIT: For anyone else trying this and getting unsupported...
forum.xda-developers.com
I can get it working with 11.2.10.10 but not OOS 12, in OOS 12 the touchscreen doesn't work and it shows dual SIM icons so it's still doing something that makes it think it's a foreign variant. I ended up just going back to StagOS where I was before everything got mucked up.
Unfortunately the MSMs still see it as an Indian variant so I can only flash the Indian OP9P firmware to it, tried all the other MSMs and none work. I have been reading threads here and people claim they got it back to global but I tried all of the suggestions and none of them restored the device enough to where the global MSM Tool didn't see it as an Indian model and refuse to flash so I think we are stuck with this frankendevice.
@EtherealRemnant Yes I had to do oem unlock while on the Indian firmware. If your phone has the oem unlock greyed out, there's a guide on how to fix that with a simple command line.
Then I unlocked bootloader, flashed lineage recovery then a custom ROM. Haven't tried to get back to stock rom, and I don't think we can.... But I love this rom I'm currently on which is stagos.
Feel free to message me for any questions you may have!
[ROM][OOS Cam][Android 12.1]StagOS 12.1[lemonade][FINAL][08/09/2022]
Hey another day another rom, that's what you might be thinking. but we at stag aim towards elegance. We are learners just like everyone out there, This is small project we have started which helps us learn every single day. Why Stag, you might...
forum.xda-developers.com
@Derek6091 I have modded the global firmware so that it will flash on a device recognized as the Indian variant. If you would like to give it a shot (I already tested it on my own device and am happy to say, it worked perfectly and my device is back on global firmware), here's the link
LE2115_11.2.4.4_India_fix.zip
Compressed (zipped) Folder
1drv.ms
EtherealRemnant said:
@Derek6091 I have modded the global firmware so that it will flash on a device recognized as the Indian variant. If you would like to give it a shot (I already tested it on my own device and am happy to say, it worked perfectly and my device is back on global firmware), here's the link
LE2115_11.2.4.4_India_fix.zip
Compressed (zipped) Folder
1drv.ms
Click to expand...
Click to collapse
Nice glad you figured it out.
go17lyonjon said:
Nice glad you figured it out.
Click to expand...
Click to collapse
haha yeah I was a dog with a bone, wasn't gonna drop it lol.
EtherealRemnant said:
@Derek6091 I have modded the global firmware so that it will flash on a device recognized as the Indian variant. If you would like to give it a shot (I already tested it on my own device and am happy to say, it worked perfectly and my device is back on global firmware), here's the link
LE2115_11.2.4.4_India_fix.zip
Compressed (zipped) Folder
1drv.ms
Click to expand...
Click to collapse
Excellent. How did you do it? I would like to try with the T-Mobile MSM
Derek6091 said:
@EtherealRemnant Yes I had to do oem unlock while on the Indian firmware. If your phone has the oem unlock greyed out, there's a guide on how to fix that with a simple command line.
Then I unlocked bootloader, flashed lineage recovery then a custom ROM. Haven't tried to get back to stock rom, and I don't think we can.... But I love this rom I'm currently on which is stagos.
Feel free to message me for any questions you may have!
[ROM][OOS Cam][Android 12.1]StagOS 12.1[lemonade][FINAL][08/09/2022]
Hey another day another rom, that's what you might be thinking. but we at stag aim towards elegance. We are learners just like everyone out there, This is small project we have started which helps us learn every single day. Why Stag, you might...
forum.xda-developers.com
Click to expand...
Click to collapse
I can't find a working command line fix for the greyed out OEM unlock... which one did you use?
mightysween said:
I can't find a working command line fix for the greyed out OEM unlock... which one did you use?
Click to expand...
Click to collapse
Go to your home screen on your phone and connect to computer with usb debugging and run this command in cmd,
adb shell pm disable-user com.qualcomm.qti.uim
Then go to developer options and oem unlock should be able to toggle.
mightysween said:
Excellent. How did you do it? I would like to try with the T-Mobile MSM
Click to expand...
Click to collapse
You have to use the Oppo Decrypter tools. Decrypt the OPS file and open settings.xml. At the bottom of it there's a Target area. I just edited that to IN instead of O2 and re-packed it.
Derek6091 said:
Go to your home screen on your phone and connect to computer with usb debugging and run this command in cmd,
adb shell pm disable-user com.qualcomm.qti.uim
Then go to developer options and oem unlock should be able to toggle.
Click to expand...
Click to collapse
Perfect... thanks.
EtherealRemnant said:
You have to use the Oppo Decrypter tools. Decrypt the OPS file and open settings.xml. At the bottom of it there's a Target area. I just edited that to IN instead of O2 and re-packed it.
Click to expand...
Click to collapse
Nice...
I tried it with the T-Mobile MSM but it still failed on "unsupported target". Did you only change the text value for O2 to IN, or did you need to change the numerical Target ID as well?
I am pretty content leaving this phone on StagOS anyway, but would be nice to figure out a way to return to T-Mobile stock after recovering from a brick.
mightysween said:
Nice...
I tried it with the T-Mobile MSM but it still failed on "unsupported target". Did you only change the text value for O2 to IN, or did you need to change the numerical Target ID as well?
I am pretty content leaving this phone on StagOS anyway, but would be nice to figure out a way to return to T-Mobile stock after recovering from a brick.
Click to expand...
Click to collapse
Manually flashing partitions in Fastboot does work, FYI. So it is possible to go back to stock that way once the bootoader is re-unlocked.
I wonder where the "target" data is stored on the actual device. If it is simply a numerical/text value in an accessible partition, seems like it would be pretty easy to make a TWRP flashable that can change it.
mightysween said:
Nice...
I tried it with the T-Mobile MSM but it still failed on "unsupported target". Did you only change the text value for O2 to IN, or did you need to change the numerical Target ID as well?
I am pretty content leaving this phone on StagOS anyway, but would be nice to figure out a way to return to T-Mobile stock after recovering from a brick.
Click to expand...
Click to collapse
Strange that it didn't work for you. That was indeed all I changed. Did you change it to what the unsupported target message said your device was? I was comparing the settings between India and global and besides the change of target ID, the target number on India was 3 instead of 1. No idea if that makes a difference though because I didn't try it.
You made sure to re-encrypt and replace the OPS, right?
Also yeah you can flash with fastboot, it doesn't fix that flag though and when I tried to go back to OOS 12 with the messed up flag it thought my device was a dual SIM device so there was no signal and the touchscreen didn't work. Happened twice. With the modified MSM I went back to global and am running OOS 12 right now.
EtherealRemnant said:
@Derek6091 I have modded the global firmware so that it will flash on a device recognized as the Indian variant. If you would like to give it a shot (I already tested it on my own device and am happy to say, it worked perfectly and my device is back on global firmware), here's the link
LE2115_11.2.4.4_India_fix.zip
Compressed (zipped) Folder
1drv.ms
Click to expand...
Click to collapse
Do you still have this file ? I flashed the OnePlus 9 pro indian firmware in msm since it's the only thing that worked and I want to go back to global
taintsx said:
Do you still have this file ? I flashed the OnePlus 9 pro indian firmware in msm since it's the only thing that worked and I want to go back to global
Click to expand...
Click to collapse
All you have to do to go back to global is download the full OTA for your device and flash it with the system updater.
EtherealRemnant said:
All you have to do to go back to global is download the full OTA for your device and flash it with the system updater.
Click to expand...
Click to collapse
Yea I tried that and had touchscreen not responding issues
taintsx said:
Yea I tried that and had touchscreen not responding issues
Click to expand...
Click to collapse
Then use the downgrade package. It will wipe your phone again but I will get you back to full OOS11 firmware and that issue won't happen.
EtherealRemnant said:
Then use the downgrade package. It will wipe your phone again but I will get you back to full OOS11 firmware and that issue won't happen.
Click to expand...
Click to collapse
Yea i tried that with
[OnePlus 9][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
downgrade indian version 11.2.5.5 , unfortunately it just tells me it cannot read the file when i attempt to sideload
Hi all. I'm new to the Lenovo space, so please bear with me. After some searching, I can't quite seem to figure out what the model number of the P11 Plus is? Can anyone enlighten me?
Tab P11 Plus | 11" Family Tablet
Meet the Lenovo Tab P11 Plus, an Android tablet featuring an 11" 2K display and quad speakers for immersive multimedia, plus Google Kids Space and Entertainment Space for family fun and education.
www.lenovo.com
Knowing that, can this particular model's bootloader be unlocked and the OS rooted? Cheers.
Found the model number: TB-J616F or TB-J616X
Android Upgrade Matrix - Lenovo Support US
support.lenovo.com
molohov said:
Found the model number: TB-J616F or TB-J616X
Android Upgrade Matrix - Lenovo Support US
support.lenovo.com
Click to expand...
Click to collapse
Have you found the answer whether the Lenovo P11 Plus (TB-J616F) model can be rooted?
I am thinking of buying this tab. Is it stock unlocked or is it not?
kanines said:
Have you found the answer whether the Lenovo P11 Plus (TB-J616F) model can be rooted?
Click to expand...
Click to collapse
The answer is yes.
First, using Rescue and Smart Assist, DL the latest rom for this model this model. I used TB_J616F_S000046_220311_ROW.
Next go to C:\ProgramData\RSA\Download\RomFiles\TB_J616F_S000046_220311_ROW and you will find the boot.img files. Copy it to a folder on the tablet. Remember where.... duh.
Install Magisk 25.2 which is the version that I used. Follow Magisk instructions to "patch" the copied boot.img file. When complete, copy the patch boot image file back to your Adb/Fastboot folder, normally X:\platform-tools.
Put your tablet in fastboot mode and run: fastboot flash boot <name of patched boot.img file>.
So, there's no need to ask questions as there are a least a bizzion guides on the internet on how to do a "Magisk boot.img patch and flash".
I am stuck on unlocking the bootloader as, when I use adb reboot bootloader. I am greeted with => FASTBOOT mode..., and when i go to fastbootd using recovery mode. I am stuck with Download is not allowed on locked devices, and when trying to unlock. Stuck with Command is not supported in default implentation.
levrx said:
I am stuck on unlocking the bootloader as, when I use adb reboot bootloader. I am greeted with => FASTBOOT mode..., and when i go to fastbootd using recovery mode. I am stuck with Download is not allowed on locked devices, and when trying to unlock. Stuck with Command is not supported in default implentation.
Click to expand...
Click to collapse
every android ive unlocked bootloader, you click on the build number in settings 7 times, after aprox 3 it shows a count down until its unlocked, then it depends on the device im pretty sure, it was diff between my phone n table so it depends on ur device here is some resources
Locking/Unlocking the Bootloader | Android Open Source Project
source.android.com
How To: Unlock Bootloader
How To Unlock Bootloader Galaxy A12. *** Disclaimer I am not responsible for any damage you made to your device You have been warned - Go to Settings -> About phone and find your build number. - Tap on your build number 6 times until you see...
forum.xda-developers.com
Unlocking the bootloader and rooting
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
there is a diff between download mode and fastboot, just so u know, you need adb and fastboot from Androids SDK tools, you can find online, depending on ur computers OS. Also, ADB commands work with ur device on n plugged into the computer fastboot is for commands when ur in fastboot mode
levrx said:
I am stuck on unlocking the bootloader as, when I use adb reboot bootloader. I am greeted with => FASTBOOT mode..., and when i go to fastbootd using recovery mode. I am stuck with Download is not allowed on locked devices, and when trying to unlock. Stuck with Command is not supported in default implentation.
Click to expand...
Click to collapse
I have the same issue!!! It seems a problem with the Fastboot mode.
19blacktiger77 said:
I have the same issue!!! It seems a problem with the Fastboot mode.
Click to expand...
Click to collapse
I solved!!!
I just had to download the latest version of ABD and Fastboot!
Hi. i rooted with this video.. it is in portuguese, but the codes are in english, 15 minutes and it´s done..
I also want to root this device but I am waiting for their Android 12 update. Is anyone running Android 12 ?
I've successfully rooted my Lenovo P11 Plus (J616F) tablet via the latest stock rom + Magisk 25.2, and it was much more painless than I'd thought it'd be. But I can't figure out how to get TWRP or any other custom recovery, and I'd be happy to hear if anyone has had any success with it...
HackVasant said:
I also want to root this device but I am waiting for their Android 12 update. Is anyone running Android 12 ?
Click to expand...
Click to collapse
Yes...
1.) Install USB drivers (I used this to detect fastboot mode: https://motorola-global-en-uk.custhelp.com/app/usb-drivers/)
>> NOTE: With your tablet in fastboot mode, you might have to go into device manager and manually update the drivers for your "unknown android device", pointing it to the usb drivers from the previous step)
2.) Install the lastest ADB and Fastboot software
3.) Unlock your bootloader!
3a.) Enable developer options -> Enable OEM unlocking
3b.) Enter fastboot mode (turn tablet off then hold power + volume up until just after it vibrates)
3c.) With your device connected to your PC, type fastboot flashing unlock in command prompt
4.) Look for the current latest stock rom TB-J616F_S240138_221026_ROW_SVC.ZIP
5.) Extract it somewhere on your PC, and copy boot.img to somewhere on your device
6.) Install Magisk v25.2 on your device
7.) Follow the rest of the installation instructions here: https://topjohnwu.github.io/Magisk/install.html
If all went well, after rebooting you might get a warning about your device being in "Orange State" and therefore cannot be trusted because the bootloader was unlocked... This is normal, and your instinct might be to run the command fastboot flashing lock to get rid of it, but THS IS A BAD IDEA because it could place your device into a "Red State" requiring you to unlock it again, effectively wiping your device
Can it play Redbox (free video app) OK after rooted?
If it's OK, I think Netflix and Amazon Prime will be OK as well
mingkee said:
Can it play Redbox (free video app) OK after rooted?
If it's OK, I think Netflix and Amazon Prime will be OK as well
Click to expand...
Click to collapse
Yes, but you will need to do the following...
1.) In Magisk, make sure you have Zygisk enabled in the settings
2.) Install this Magisk module, then reboot your device:
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
3.) Use YASNAC (from the app store) to verify that you pass the safetynet check (it passes for me)
4.) Uninstall Netflix, then manually download and install the latest Netflix APK from your favorite APK site
I didn't test Redbox or Amazon Prime, but I would imagine it'd just be repeating step 4 for each additional app you wish to install
You can also read this for more detailed information about Magisk & SafetyNet:
SafetyNet:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
SpectreCular said:
Yes, but you will need to do the following...
1.) In Magisk, make sure you have Zygisk enabled in the settings
2.) Install this Magisk module, then reboot your device:
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
3.) Use YASNAC (from the app store) to verify that you pass the safetynet check (it passes for me)
4.) Uninstall Netflix, then manually download and install the latest Netflix APK from your favorite APK site
I didn't test Redbox or Amazon Prime, but I would imagine it'd just be repeating step 4 for each additional app you wish to install
You can also read this for more detailed information about Magisk & SafetyNet:
SafetyNet:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
Click to expand...
Click to collapse
The reason why I asked because A12 can make those video apps don't work even after passed safetynet and play integrity (2/3) and apps installed
However, those apps work on OnePlus N200 and 8T but NOT on Moto Edge 2021
mingkee said:
The reason why I asked because A12 can make those video apps don't work even after passed safetynet and play integrity (2/3) and apps installed
However, those apps work on OnePlus N200 and 8T but NOT on Moto Edge 2021
Click to expand...
Click to collapse
Alright well I decided to take the time to check Redbox, and it works (or at least the Watch Free feature does)... And I don't have a prime account, but the prime video app makes it to the sign in screen, if that helps
SpectreCular said:
Alright well I decided to take the time to check Redbox, and it works (or at least the Watch Free feature does)... And I don't have a prime account, but the prime video app makes it to the sign in screen, if that helps
Click to expand...
Click to collapse
Good!
I will make a backup on mine (I have Yoga 11 and practically they're the same) and unlock the bootloader and root it.
The reason why I root it so I can do adb on other device without laptop.
Actually, I have a lot of experience to root variety of machines, but what happened on Edge 2021 A12 puts me on hold on other Moto/Lenovo
I have Netflix and cable apps (Sling and Philo) and Discovery+.
Well just so we're on the same page, the steps I've posted were specifically for J616F, so your mileage may vary if you're using a different device. Also, I would maybe use a more specific stock ROM, since the one I posted is also specifically for J616F
SpectreCular said:
Well just so we're on the same page, the steps I've posted were specifically for J616F, so your mileage may vary if you're using a different device. Also, I would maybe use a more specific stock ROM, since the one I posted is also specifically for J616F
Click to expand...
Click to collapse
I have to make it clear. I have both P11 plus and Yoga 11
I have the P11 Plus J616F model and cannot get the device to unlock after many attempts with wiping device reinstalling firmware reinstalling device drivers. Does failed (unknown status code) after (bootloader) sysytem-fingerprint:Lenovo/TB-J616F/TB-J616F:12/SP1A.210812.0 mean anything to anyone. I can adb reboot recovery, from recovery I can use the keys to choose fastboot and tab goes into fastbootd and fastboot devices returns my device fashboot flashing unlock starts but ends with the failed message above. fastboot getvar all returns a bunch of information about the device but also stops with same failed message. If I choose reboot bootloader using the keys on my tab while in fastbootd tab reboots to FASTBOOT... shows up in device manager as you would expect but typing fastboot flashing unlock returns waiting for device. Any thoughts or ideas would be greatly appreciated.