*PLEASE BE SURE TO READ EVERYTHING BEFORE ROOTING YOUR PHONE!!!*
This guide will help you to root your UMIDIGI A11 Pro Max. Aside from my own knowledge, I used many sources (and I’ll add the respective references, of course) to create this specific manual. In that regard, I organized the information in many sections due to its size.
Also, please be aware this is a guide for UMIDIGI A11 Pro Max, not UMIDIGI A11 Pro, or UMIDIGI A11, or UMIDIGI A13, or any similar model. You’re free to adapt this guide to a different UMIDIGI model though, so you can copy nearly everything here (with the necessary changes) if you want to.
DISCLAIMER: ALL I WROTE HERE WORKED PERFECTLY WITH MY UMIDIGI A11 PRO MAX, BUILD NUMBER UMIDIGI_A11_PRO_MAX_V1.0_20220108, WHICH I ROOTED WITH MAGISK 24.3, BUT I’M NOT A PROFFESIONAL. THIS MEANS I CANNOT GUARANTEE YOU THIS WILL ALWAYS WORK WITH ANOTHER BUILD NUMBER OR MAGISK VERSION, ALTHOUGH I HONESTLY THINK THERE SHOULDN’T BE ANY PROBLEM. FINALLY, ROOTING IS YOUR DECISION, AND IT'S OWN YOUR RESPONSIBILITY IN CASE YOU BRICK YOUR DEVICE, AS I’M NOT COERCING YOU TO DO IT.
With that said, let’s begin!
Things you need to know:• Currently, there is no custom recovery (like TWRP) for this smartphone. This will make the whole process a bit more complex, but it’s still possible to get root.
• While I think the rooting itself doesn’t void your warranty, the previous and unavoidable step—unlocking the bootloader—does.
• Another thing about unlocking the bootloader: the process will make a FACTORY RESET to your device, so better have a back-up ready.
• We’ll use Magisk, so it’ll still be possible to get FOTA, also named OTA, updates. I’ll elaborate more at the end of this guide.
• As I said, I’m not responsible If you brick your device, but I can give you a hand! (More details just below.)
Preparations:• Identify your build number to find your stock ROM online. Go to “Settings”, now go to the bottom to “About phone”, and then go again to the bottom and you will find something like this: “Build number: UMIDIGI_A11_PRO_MAX_V1.0_20220108”.
• Go to your PC and download your stock ROM in UMIDIGI’s official forum. Remember there are main releases’ variations for specific regions (like Europe), so be sure to check if EACH LETTER of the names match. If you made a mistake, you’ll be trapped in a boot loop (bricked device). Here is the forum:
https://community.umidigi.com/forum.php?mod=forumdisplay&fid=293&page=1
Click to expand...
Click to collapse
*THIS STOCK ROM IS NECESSARY TO UNBRICK YOUR DEVICE BY GETTING A FRESH INSTALATION IN CASE OF EMERGENCY, SO PLEASE DO NEVER DELETE IT, PRESERVE IT EVEN AFTER YOU GET ROOT. IF YOU MESSED UP READING THIS GUIDE OR LATER, READ YOUR RESPECTIVE THREAD TO UNBRICK YOUR PHONE. FROM HERE ONWARDS, YOU’LL BE IN THEIR HANDS*
• Open the RAR and extract vbmeta.img and boot.img (DO NEVER DELETE THE ORIGINALS).
• Now you need to unlock “Developer options” in your device, as the basic permissions aren’t enough to root. Go to: Settings > About phone > Status. Now go to the bottom and tap “Build number” seven or eight times until a message saying that you’re now a developer appears.
• Go to Settings > System > Advanced > Developer options. Active them if they’re “Off”, now activate “OEM unlocking” and “USB debugging”. This will allow you to: move files between your phone and PC, and use your PC to modify your phone (explained just below).
Installing Android Debug Bridge (ADB) on your PC:This “simple” interface, as it uses a terminal window (like CMD or PowerShell in Windows), will allow you to control your device from a computer by using methods hidden to simple mortals (mostly for their own security, because the average user could easily brick their device by accident).
The process to do this may vary depending on your OS (Windows 10, Windows 11, Linux, etc.) or even between different updates or drivers of said OS, so I cannot give you specific steps. You can use this guide, which I’m sure is better than anything I could ever write about this topic:
https://www.xda-developers.com/install-adb-windows-macos-linux/
Click to expand...
Click to collapse
Feel free to search for all the guides you need until installing ADB. Take your time, we’re not doing anything that could brick your device if you make a mistake… yet.
Unlocking the bootloader:• Make sure ADB is correctly installed or you won’t be able to do anything from this point onwards.
• Remember, this specific step will make a FACTORY RESET to your device, so better have a back-up ready. You need this extra permission to root your phone, or install a custom recovery or ROM if you want (sadly there is neither of them to date).
• Connect your device to your PC.
• Open your ADB terminal on your PC and write:
Code:
adb reboot bootloader
*If doesn’t work, write ./adb instead adb, or the variation your terminal uses, and keep using it from now on. Your device will reboot and now you’ll be in fastboot mode (make sure to read the small > FASTBOOT mode… message on the bottom left corner of your device).
• Now the time has come, after this you’ll have a factory reset. Write:
Code:
fastboot flashing unlock
*Again, if fastboot doesn’t work, use ./fastboot, etc.) and a new message will appear on your device. Read it, it won’t say anything new if you’re with this guide, and press the Volume up button to unlock your bootloader.
• To reboot your device, write:
Code:
fastboot reboot
While rebooting, you will read this just below UMIGIDI’s logo:
Orange state:
Your device has been unlocked and can’t be trusted
Your device will boot in 5 seconds
*Spoiler: it won’t reboot in 5 seconds, but 1 or 2 minutes.
• Congratulations! Now you have a brand-new unlocked phone! No more factory resets (unless you brick your phone), so feel free to make the initial configuration.
This section was based on these guides:
https://www.mobilewithdrivers.com/download/unlock-bootloader/umidigi-a11-pro-max
https://www.droidwin.com/how-to-unlock-bootloader-on-umidigi/
Click to expand...
Click to collapse
Patching images:• Now this process is the rooting itself, time to get Magisk, the rooting tool and the future manager of your root permission (under your orders, of course). Download its latest version on your device and install it.
• Connect your device to your PC and send boot.img (you extracted it at the beginning of this tutorial) to your smartphone and open Magisk app. On the Magisk section, tap “Install” and then “Select and patch a file” and search for your boot.img to patch it.
• The installation (flashing) will continue in a terminal-like screen. Once finished, the direction of the patched file will appear, along an All done! message.
• Now send this new patched file and the vbmeta.img (you extracted it at the beginning of this tutorial) to your ADB folder in your computer.
• Now turn off your phone and hold Power button and Volume up button for 5 seconds, and select Fastboot Mode.
• Open your ADB window and DO NOT CLOSE IT BEFORE FLASHING THE NEXT 2 FILES, OR YOU'LL BRICK YOUR DEVICE:
THE FIRST FILE: Write the following command:
Code:
fastboot --disable-verity --disable-verification flash boot (insert here the name of your magisk patched file, don’t forget to add the “.img” extension)
Example: My file is called magisk_patched-24300_UuPmm.img, so I wrote:
Code:
fastboot --disable-verity --disable-verification flash boot magisk_patched-24300_UuPmm.img
Don’t forget, write ./fastboot or any command’s variation you’ve been using so far.
THE SECOND FILE: Write the following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
• Write this and you’re done:
Code:
fastboot reboot
Enjoy your rooted UMIDIGI A11 Pro Max!
This section was based on these guides:
https://topjohnwu.github.io/Magisk/install.html
https://forum.xda-developers.com/t/umidigi-a11-pro-max-rooted.4366121/
Click to expand...
Click to collapse
About getting FOTA/OTA updates (PLEASE READ THIS TOO OR YOU MAY LOSE YOUR ROOT SOMEDAY!!!):First, what are FOTA/OTA updates? In short, you could say their function is similar to Windows updates. Usually, rooting with alternatives to Magisk, or installing a custom recovery, prevents you from getting them.
This a rooting guide so, while I won’t help you to getting those updates, I can still give you this comprehensive guide:
https://www.thecustomdroid.com/install-ota-update-rooted-android-device-guide/
Click to expand...
Click to collapse
Lastly, the true reason I wrote this is to alert you that even if you don’t care about FOTA/OTA you still NEED TO DEACTIVATE THE AUTOMATIC UPDATES, otherwise you may lose your root someday or cause problems to your phone (you can search online for the technical reasons of this if you want). From now on, if you want updates, you’ll do it manually.
To deactivate them, go to Settings > System > Advanced > Developer options and turn off "Automatic system updates".
A useful thread about Magisk:I’ll also leave you this sticky thread of XDA Developers, I’m sure it’ll help you in the future:
https://forum.xda-developers.com/f/magisk.5903/
Click to expand...
Click to collapse
AND THAT’S ALL, THANKS FOR READING!
thank you for this tutorial I routed my phone but I have orange state at each start which lasts 30 seconds then starts normally what is the problem please and thank you again
hachelfig said:
thank you for this tutorial I routed my phone but I have orange state at each start which lasts 30 seconds then starts normally what is the problem please and thank you again
Click to expand...
Click to collapse
I've tried to find more about that because it kinda annoyed me too, but at the end, it seems to be some sort of "indicator" that you were able to successfully unlock your phone's bootloader. In any case, I'll keep searching and the guide will be updated if I find a way to remove that message.
I used this tutorial https://www.droidwin.com/how-to-remove-red-and-orange-state-warning-in-mediatek-devices/ and it works well thank you
Which vbmeta.img file am I using, when I unpac the file there are:
vbmeta_product.img
vbmeta-sign.img
vbmeta_system.img
vbmeta_sysem_ext.img
vbmeta_vendor.img
Which one should I be using to root?
Oops galeta, would it not have a custom rom or GSI compatible with the Umidigi A11 pro max? I've been looking for something like this for days and I haven't found anything like this, do you know something like this?
hachelfig said:
Eu usei este tutorial https://www.droidwin.com/how-to-remove-red-and-orange-state-warning-in-mediatek-devices/ e funciona bem, obrigado
Click to expand...
Click to collapse
Usei este método! porém meu smatphone morreu! não da sinal de nada
Patrickcnnp said:
Usei este método! porém meu smatphone morreu! não da sinal de nada
Click to expand...
Click to collapse
Foi tudo coreto! ai dei o FASTBOOT REBOOT e não liga mais
I am just wondering if anybody has managed to root the
Umidigi A13 Pro Max 5G
marisaleh said:
Eu só estou querendo saber se alguém conseguiu enraizar o
Umidigi A13 Pro Max 5G
Click to expand...
Click to collapse
Ainda não tive êxito!
Patrickcnnp said:
Ainda não tive êxito!
Click to expand...
Click to collapse
UMIDIGI A13 Pro Max 5G is it a dual slot device?
Be aware guys,
I followed the same procedure above to root UMIDIGI A13 Pro Max 5G
I adapted the procedure to my phone, obviously
It didn't work, ended up with a completely damaged phone.
The only way to recover it was to flash it with the SPFT tool
using firmware mode of flashing,,,
I am just wondering if anybody has managed to
root UMIDIGI A13 Pro Max 5G YET....
marisaleh said:
Be aware guys,
I followed the same procedure above to root UMIDIGI A13 Pro Max 5G
I adapted the procedure to my phone, obviously
It didn't work, ended up with a completely damaged phone.
The only way to recover it was to flash it with the SPFT tool
using firmware mode of flashing,,,
I am just wondering if anybody has managed to
root UMIDIGI A13 Pro Max 5G YET....
Click to expand...
Click to collapse
marisaleh said:
Be aware guys,
I followed the same procedure above to root UMIDIGI A13 Pro Max 5G
I adapted the procedure to my phone, obviously
It didn't work, ended up with a completely damaged phone.
The only way to recover it was to flash it with the SPFT tool
using firmware mode of flashing,,,
I am just wondering if anybody has managed to
root UMIDIGI A13 Pro Max 5G YET....
Click to expand...
Click to collapse
I believe this might be a dual slot device this work only if it is.
Mchlbenner51 said:
I believe this might be a dual slot device this work only if it is.
Click to expand...
Click to collapse
Yes you are right I have just confirmed that using Treble Check app,
it is a dual slot device.
I will now give it another go, and report back
Thanks for you help
Yes Yes Yes
I have just finally succeeded in rooting the Umidigi A13 Pro Max 5G
Yes it is a dual slot device
I rooted it using this simple procedure:
flashed the latest stock rom from Umidigi
Patched boot.img using the latest version of Magisk Manager (magisk_patched.img)
With the phone unlocked and in fastboot mode, I run the following:
fastboot flash boot magisk_patched.img
Fastboot flash vbmeta vbmeta.img
fastboot set_active a
fastboot reboot
The phone rebooted, I completed Magisk install
I now have full root
The orange state warning that pops up on reboot is annoying
and I don't know how to get rid of it yet.
I will be grateful if anyone can help!!!
marisaleh said:
Yes Yes Yes
I have just finally succeeded in rooting the Umidigi A13 Pro Max 5G
Yes it is a dual slot device
I rooted it using this simple procedure:
flashed the latest stock rom from Umidigi
Patched boot.img using the latest version of Magisk Manager (magisk_patched.img)
With the phone unlocked and in fastboot mode, I run the following:
fastboot flash boot magisk_patched.img
Fastboot flash vbmeta vbmeta.img
fastboot set_active a
fastboot reboot
The phone rebooted, I completed Magisk install
I now have full root
The orange state warning that pops up on reboot is annoying
and I don't know how to get rid of it yet.
I will be grateful if anyone can help!!!
Click to expand...
Click to collapse
Does it say your bootloader is unlocked!
Mchlbenner51 said:
Does it say your bootloader is unlocked!
Click to expand...
Click to collapse
It says your device has been unlocked
and cannot be trusted
I'll be grateful if you can help me
get rid of it, it's annoying
marisaleh said:
It says your device has been unlocked
and cannot be trusted
I'll be grateful if you can help me
get rid of it, it's annoying
Click to expand...
Click to collapse
I don't have this phone yet l.
I was pretty sure how to root it so left directions on how to do that.
I would for know l would leave it alone.
When get this phone I will see what I can do about that.
Do not try the remedy that is in this post it could brick your phone.
Mchlbenner51 said:
I don't have this phone yet l.
I was pretty sure how to root it so left directions on how to do that.
I would for know l would leave it alone.
When get this phone I will see what I can do about that.
Do not try the remedy that is in this post it could brick your phone.
Click to expand...
Click to collapse
Thank you very much
I have rooted it with your help
You can see the procedure I
Followed, it's really easy
It's the orange state warning that
I don't know how to remove
I'll wait for you help on that
Mchlbenner51 said:
I don't have this phone yet l.
I was pretty sure how to root it so left directions on how to do that.
I would for know l would leave it alone.
When get this phone I will see what I can do about that.
Do not try the remedy that is in this post it could brick your phone.
Click to expand...
Click to collapse
Good news, I have just managed to remove the orange state warning
Used a Hex editor, modified the stock lk.img and flashed it in fastboot
fastboot flash lk lk.img
Very simple worked perfectly
I am still having a problem with changing selinux mode from
Enforcing to permissive.
I have tried all existing methods and workarounds
I even tried terminal commands like getenforce and setenforce
Nothing will work to change it to permissive
I think it's android 12 security
I will be grateful if anybody can help
Some mods like viper4android will only work if
selinux is in permissive mode
Related
Hello there
I bought a Samsung J7 Neo (SM -J701M) on another country than mine (Im from Argentina, device bought on Paraguay). Anyway, I started to look another way to get some space on the internal storage and I remember that android had an option to expand it, using a SD Card. Unfortunately, i realize this option is not allowed on samsungs device, but it works (i read it, because can't do it) if you get root user.
So I looked how to do it and i found a group of files
ODIN v3.12
Magisk v.14.5
twrp v.3.1.1 -j7 neo
Im not sure if I downloaded the right files, but im start the process anyway.
I followed point by point
First I installed TWRP Recovery v3.1.1 (which is supposed to be correct to my model) and then already on twrp rom I installed magisk 14.5 from sd card and did wipe data.
Turned on the phone and I restored all apps from a google backups, and I realized I cant find app "Magisk" on the device, so I decided to reboot the phone and it starts to do a bootloop with this error "kernel rev. check fail, device:2 binary:1"
At this point, I failed every attempt to fix this error
I tried installing the last official firmware that i found (and Im not sure if its the correct one)
J701MUBU3ARC2_J701MUWT3ARC1_UFN
And I got this error
"SW REV. CHECK Fail (BOOTLOADER) Device :5 Binary 3:
I searched on google this kind of error, and I found that I have to downgrade the bootloader. And this is why im here beacause I dont know how to do this, and if its works, i don´t know how to continue the process to root and expand my internal storage. So I really appreciate if someone one could help me with this. I can learn fast and I love to do this things by myself.
Thanks for your time!
Fernando
If you have to downgrade the boot loader, it means the firmware you are flashing is older than the one on your fon.
Go to www.updato.com and look for the he latest J701M firmware.
You can sort the list by date and by region.
And the site is download manager friendly ?
Good luck!
Sent from my SM-J700F using Tapatalk
Thanks for your answer! One more question about the region. Should I download firmware from the country that I bought the phone or firmware from the country that I am?
Look for your country specific firmware first.
Otherwise Samsung usually has regional software - i.e for several countries in a region e.g. Argentina, Paraguay.
Sent from my SM-J700F using Tapatalk
MikeEinziger said:
Hello there
I bought a Samsung J7 Neo (SM -J701M) on another country than mine (Im from Argentina, device bought on Paraguay). Anyway, I started to look another way to get some space on the internal storage and I remember that android had an option to expand it, using a SD Card. Unfortunately, i realize this option is not allowed on samsungs device, but it works (i read it, because can't do it) if you get root user.
So I looked how to do it and i found a group of files
ODIN v3.12
Magisk v.14.5
twrp v.3.1.1 -j7 neo
Im not sure if I downloaded the right files, but im start the process anyway.
I followed point by point
First I installed TWRP Recovery v3.1.1 (which is supposed to be correct to my model) and then already on twrp rom I installed magisk 14.5 from sd card and did wipe data.
Turned on the phone and I restored all apps from a google backups, and I realized I cant find app "Magisk" on the device, so I decided to reboot the phone and it starts to do a bootloop with this error "kernel rev. check fail, device:2 binary:1"
At this point, I failed every attempt to fix this error
I tried installing the last official firmware that i found (and Im not sure if its the correct one)
J701MUBU3ARC2_J701MUWT3ARC1_UFN
And I got this error
"SW REV. CHECK Fail (BOOTLOADER) Device :5 Binary 3:
I searched on google this kind of error, and I found that I have to downgrade the bootloader. And this is why im here beacause I dont know how to do this, and if its works, i don´t know how to continue the process to root and expand my internal storage. So I really appreciate if someone one could help me with this. I can learn fast and I love to do this things by myself.
Thanks for your time!
Fernando
Click to expand...
Click to collapse
@MikeEinziger
Hi There,
Did you have any luck with your Phone? I have the same exact model but I have Android Version 8.1.0, Samsung Experience version 9.5; Android security patch level -Feb 1, 2019; Baseband version: J701MUBS6BSB3 and like you, I love doing things myself, and I can't seem to abide a smartphone that's not rooted.
I'm not exactly a newbie, I've been assisting devs with testing and such on AT&T SGS3 for quite some time. But I can't seem to find a stable method for rooting for this phone, no one seems to be doing any development on it.
I would love to hear your story thus far.
im needing help myself, i have the SM-J701M (J7 NEO), with android pie 9 official, but the binary is 7 (because Argentina Geniuses of course) and of all the things i tried nothing works, and the only thing they did was brick the phone, so i flash and stock firmnware to be usable again
Ezeka93 said:
im needing help myself, i have the SM-J701M (J7 NEO), with android pie 9 official, but the binary is 7 (because Argentina Geniuses of course) and of all the things i tried nothing works, and the only thing they did was brick the phone, so i flash and stock firmnware to be usable again
Click to expand...
Click to collapse
What have you done? I saw your messages on TG but everyone ignores usually, I had another problem and footbed the solution myself as I got ignored for days.
So, what have you done? Maybe we can figure it out a way to root it, but to avoid telling you things that you may have already done it is better if you let us know your already followed steps.
Jemec26 said:
What have you done? I saw your messages on TG but everyone ignores usually, I had another problem and footbed the solution myself as I got ignored for days.
So, what have you done? Maybe we can figure it out a way to root it, but to avoid telling you things that you may have already done it is better if you let us know your already followed steps.
Click to expand...
Click to collapse
i tried flashing TWRP like a guide said (Latest version) but then got stuck with a boot loop in the Samsung Galaxy Logo, then when i enter to flash the latest global firmware it didn't work because it was binary 6, so i searched for the version in Argentina that has binary 7, after that i didn't try anything else in fears of getting fully bricked, i was thinking of the magisk canary way of rooting (patching the AP) but i don't know what happen if it fails the flash
Hi, i have the same device, SM-J701M, but when i try to flash the stock, it says that the device binary is 9 and the rom is 8, but i cant find the binary 9 rom in any place, only 8. I have the trwp installed, so I was thinking if I format all data (system and files) and try to flash again, it will work ?
Also im from Brazil (SM-J701MT), and the device was buyed in Paraguay (SM-J701M) too. Should i install the SM-J701MT ROM right ?
Some success.
iKmaster01 said:
Hi, i have the same device, SM-J701M, but when i try to flash the stock, it says that the device binary is 9 and the rom is 8, but i cant find the binary 9 rom in any place, only 8. I have the trwp installed, so I was thinking if I format all data (system and files) and try to flash again, it will work ?
Also I'm from Brazil (SM-J701MT), and the device was buyed in Paraguay (SM-J701M) too. Should i install the SM-J701MT ROM right ?
Click to expand...
Click to collapse
Ok, guys, I've had a bit of progress with my device Samsung Galaxy J 7 Neo (SM-J701M- Android version 8.01)
On this phone, the option to unlock the bootloader was missing in Dev Opt and I knew that in order to achieve anything I was going to have to unlock the bootloader.
I searched and found that, via adb/fastboot (Google's Platform Tools) rebooting the phone to the bootloader you could enter the code: 'fastboot oem unlock' or 'fastboot flashing unlock' and voila! everything would be fixed...But...my device wasn't even being recognized by "fastboot" ! adb yes but no fastboot! Always the message: "Waiting on any device". Trying to find and install the drivers to do this was next to impossible.
It actually caused me soft brick my device. However, it was a blessing in disguise; I knew what had to be done, I was going to have to reinstall the firmware via Odin. I searched the site (Sammobile - you'll have to create an account.) and found the Oreo and the Pie Firmware, I downloaded both but played it safe and restored my device with the Oreo first.
And lo and behold the option to unlock bootloader was there! No hesitation, clicked that sucker fast!!
Now, I'm running PIE (No one has done a Custom ROM for this baby just yet) and with the unofficial TWRP in the first link below, it's a bit buggy but until they make an official one for us ... I guess we'll have to wait.
Oh! And don't forget to make a backup with Smart Switch!
And pay attention to the advice here:
Code:
1. Extract the firmware file you just downloaded. You should get 5 files:
AP (System &Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC_*** (Country / Region / Operator)
HOME_CSC_*** (Country / Region / Operator)
2. Add each file to its respective field in Odin v3.14.4. Use CSC_*** if you want to do a clean flash or HOME_CSC_*** if you want to keep your apps and data.
3. Reboot your phone in Download / Odin mode (make sure your device is off) with the following button combo: POWER + VOLUME DOWN + BIXBY
Other options in case first option did not work or isn't possible.
Option 2 VOLUME DOWN + VOLUME UP then USB cable
Option 3 POWER + VOLUME DOWN + VOLUME UP
Option 4 POWER + VOLUME DOWN + HOME BUTTON
Option 5 (Note9) USB cable + VOLUME DOWN + BIXBY
Option 6 (Note10) POWER + VOLUME UP
4. Once in download mode, connect your phone to the PC, preferably using the original USB cable you got with your phone. Odin should detect your device and a BLUE box will show up with the COM port number. (Be sure, the SAMSUNG-drivers are installed on your PC!)
Do NOT tick any extra boxes. The only options to be ticked are F.Reset Time and Auto-Reboot.
5. Click the start button, wait for Odin to say 'PASS' in a GREEN box. Once the flash is complete, your phone will reboot, and you can disconnect your phone from the PC
These are some of the links I found helpful:
https://unofficialtwrp.com/root-twrp-galaxy-j7-neo-sm-j701m/
https://www.androidexplained.com/galaxy-note-9-restore-firmware/
https://forum.xda-developers.com/galaxy-j7/samsung-galaxy-j7-prime--j7-on-nxt-exynos7870/recovery-twrp-3-2-0-galaxy-j7-prime-t3716355
---------- Post added at 01:39 PM ---------- Previous post was at 01:30 PM ----------
iKmaster01 said:
Hi, i have the same device, SM-J701M, but when i try to flash the stock, it says that the device binary is 9 and the rom is 8, but i cant find the binary 9 rom in any place, only 8. I have the trwp installed, so I was thinking if I format all data (system and files) and try to flash again, it will work ?
Also im from Brazil (SM-J701MT), and the device was buyed in Paraguay (SM-J701M) too. Should i install the SM-J701MT ROM right ?
Click to expand...
Click to collapse
I think that's because you have to be specific with the carrier; Orange; Nextel; Movistar...that makes a lot of difference in with the firmware. If you can, check to see what you had before and try that first.
CoperaN said:
Ok, guys, I've had a bit of progress with my device Samsung Galaxy J 7 Neo (SM-J701M- Android version 8.01)
On this phone, the option to unlock the bootloader was missing in Dev Opt and I knew that in order to achieve anything I was going to have to unlock the bootloader.
I searched and found that, via adb/fastboot (Google's Platform Tools) rebooting the phone to the bootloader you could enter the code: 'fastboot oem unlock' or 'fastboot flashing unlock' and voila! everything would be fixed...But...my device wasn't even being recognized by "fastboot" ! adb yes but no fastboot! Always the message: "Waiting on any device". Trying to find and install the drivers to do this was next to impossible.
It actually caused me soft brick my device. However, it was a blessing in disguise; I knew what had to be done, I was going to have to reinstall the firmware via Odin. I searched the site (Sammobile - you'll have to create an account.) and found the Oreo and the Pie Firmware, I downloaded both but played it safe and restored my device with the Oreo first.
And lo and behold the option to unlock bootloader was there! No hesitation, clicked that sucker fast!!
Now, I'm running PIE (No one has done a Custom ROM for this baby just yet) and with the unofficial TWRP in the first link below, it's a bit buggy but until they make an official one for us ... I guess we'll have to wait.
Oh! And don't forget to make a backup with Smart Switch!
And pay attention to the advice here:
Code:
1. Extract the firmware file you just downloaded. You should get 5 files:
AP (System &Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC_*** (Country / Region / Operator)
HOME_CSC_*** (Country / Region / Operator)
2. Add each file to its respective field in Odin v3.14.4. Use CSC_*** if you want to do a clean flash or HOME_CSC_*** if you want to keep your apps and data.
3. Reboot your phone in Download / Odin mode (make sure your device is off) with the following button combo: POWER + VOLUME DOWN + BIXBY
Other options in case first option did not work or isn't possible.
Option 2 VOLUME DOWN + VOLUME UP then USB cable
Option 3 POWER + VOLUME DOWN + VOLUME UP
Option 4 POWER + VOLUME DOWN + HOME BUTTON
Option 5 (Note9) USB cable + VOLUME DOWN + BIXBY
Option 6 (Note10) POWER + VOLUME UP
4. Once in download mode, connect your phone to the PC, preferably using the original USB cable you got with your phone. Odin should detect your device and a BLUE box will show up with the COM port number. (Be sure, the SAMSUNG-drivers are installed on your PC!)
Do NOT tick any extra boxes. The only options to be ticked are F.Reset Time and Auto-Reboot.
5. Click the start button, wait for Odin to say 'PASS' in a GREEN box. Once the flash is complete, your phone will reboot, and you can disconnect your phone from the PC
These are some of the links I found helpful:
https://unofficialtwrp.com/root-twrp-galaxy-j7-neo-sm-j701m/
https://www.androidexplained.com/galaxy-note-9-restore-firmware/
https://forum.xda-developers.com/galaxy-j7/samsung-galaxy-j7-prime--j7-on-nxt-exynos7870/recovery-twrp-3-2-0-galaxy-j7-prime-t3716355
---------- Post added at 01:39 PM ---------- Previous post was at 01:30 PM ----------
I think that's because you have to be specific with the carrier; Orange; Nextel; Movistar...that makes a lot of difference in with the firmware. If you can, check to see what you had before and try that first.
Click to expand...
Click to collapse
Hey, I noticed we have the same android version and and phone model, I wanted to know which version of Twrp you used . I am guessing version 3.1.1?
It's an Un-official version of TWRP, so the version #( 3.2.1-0) may not count, you can check the links out to get more information.
hola tengo un problema, tengo un sm-j701m binario 11 android 9 y quiero intalarle un twrp pero no se cual descargar y que funcione
Don't know if anyone's still following this thread or even still has this phone but there's been quite some progress with this device. (i.e: SM-J701M) The posts below will certainly help to bring your device up to date re: rooting; flashing etc.
https://forum.xda-developers.com/t/...or-galaxy-j7-nxt-neo-core-10-08-2021.4222703/
https://forum.xda-developers.com/t/...laxy-j7-nxt-neo-core-j701-02-02-2021.4227921/
These posts contain links to ROMS and recoveries which have been sucessful, I can personally attest to this, my device was rooted and a custom ROM installed. I hope you will find them helpful.
Good Luck
Hello everyone. I purchased a new Tripletek Pro tablet (running Android 10) for use with my drone due to the super-bright screen it has. I also want to root it so I can use it for other tasks. I don't see a group for this tablet specifically, so is there a generic root process I can perform to do so? Thanks! Please advise.
robroy90 said:
Hello everyone. I purchased a new Tripletek Pro tablet (running Android 10) for use with my drone due to the super-bright screen it has. I also want to root it so I can use it for other tasks. I don't see a group for this tablet specifically, so is there a generic root process I can perform to do so? Thanks! Please advise.
Click to expand...
Click to collapse
Here is the link to root, including instructions, for the Tripltek 8 Pro. This is officially from the company.
Tripltek 8 Pro Root
Thanks. I see the firmware download, but nothing about root. Are you saying this download is pre-rooted?
robroy90 said:
Thanks. I see the firmware download, but nothing about root. Are you saying this download is pre-rooted?
Click to expand...
Click to collapse
The company told me that link was for rooting. Unfortunately, that wasn't the case. I had to do quite a bit of research outside of that link in order to gain root, including unlocking the bootloader. Send me a PM and I can share the steps with you that I did in order to gain root, because it wasn't an easy process.
robroy90 said:
Hello everyone. I purchased a new Tripletek Pro tablet (running Android 10) for use with my drone due to the super-bright screen it has. I also want to root it so I can use it for other tasks. I don't see a group for this tablet specifically, so is there a generic root process I can perform to do so? Thanks! Please advise.
Click to expand...
Click to collapse
Did you figure it out? I pre-ordered the new 9 Pro that just came out. In messaging they told me the bootloader was unlock-able but they weren't exactly keen on telling me the steps to do it.
Figured it out. The link they sent was indeed for rooting as it was the original firmware zip with the boot.img inside that you need for rooting with magisk.
1) Go into settings and enable dev options. (do the tap tap tap thing until it tells you that you are now a dev).
2) Enable USB debugging and check the enable bootloader unlocking option as well inside dev options.
3) Make sure latest version of ADB is installed on a PC.
4) Run these commands ADB devices, ADB reboot bootloader, fastboot flashing unlock, click volume button to proceed, fastboot reboot. Boot Loader will now be unlocked.
5) From the zip of the original firmware, extract boot.img and put it on the tablet somewhere easy to find.
6) Install Magisk app, then click install by patching a file. Choose the boot.img from the zip thats now on the tablet.
7) Take the new magisk_patched.img from the tablet and put back on PC in adb tools folder.
8) Run these commands ADB reboot bootloader, fastboot flash boot magisk_patched.img, fastboot reboot.
Done.
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.
Hi so today I Recieved a Motorola Moto G22 that I'd brought online.
Now upon booting the phone a number of things became apparent.
1) the stock image the phone comes with is seriously bad, from further inspection it appears google bloatware eats the ram.
2) upon thinking okay prehaps i should use a custom rom , however after many hours looking and trying diffrent things I've had no success.
So from trying many of the basic guides for unlocking motorola's bootloader, I've found an issue where i can't unlock it, when trying fastboot oem get_unlock_data
i get the following error " FAILED (remote: 'unknown command') " , I got this error with many other commands other guides suggested the only command that actually worked was "fastboot getvar all " which returned the varibles but with nothing really useful other than that the bootloader is locked.
so my question is : is it possible to unlock this thing and put better software on it?
software details which might help:
version: Moto G22 (XT2231-2} with android 12 RETGB 4GB ram 64GB space
I brought it to replace a sadly broken S9 which was working until the microphone stopped working for evering. (that and the buttons falling off)
Many Thanks in advance.
Josh
UPDATE: So after Many hours of trying to unlock I found a way to unlock the phone, however unlocking the bootloader triggers the dm-verity to loose it's mind.
for inromation if anyone is curious, I used MediaTekbootloaderunlock program which unlocked the bootloader.
So far Rooting this phone has not been anywhere near successful, i can tell they really don't want you changing the ROM.
Further Update: I have unfortunately Managed to Brick The G22 , Honestly I'd avoid this phone anyone who maybe thinking of getting this probably chose something else as the ROM it comes with is sluggish to say the least and (at least with my G22) would become unresponsive at random and lock up.
from what i can tell (and i'm no expert) they seem to really not want you to root this phone as the filesystem by default is read-only and by default you cant access certain directories either.
I`ve managed to get rid of Google bloatware on my Moto G22 using ADBAAppControl application. (https://adbappcontrol.com/en/) The phone has stock ROM and locked bootloader, as well.
janokv said:
I`ve managed to get rid of Google bloatware on my Moto G22 using ADBAAppControl application. (https://adbappcontrol.com/en/) The phone has stock ROM and locked bootloader, as well.
Click to expand...
Click to collapse
i wish i knew of this before i managed to brick mine, the hardware is good but the software is absolutely crap as far as i know.
HI GUYS I FOUND A WAY TO FLASH GSI IMAGE ON MOTO G22
now its better than moto edge 20
I WILL POST A TUTORIAL ON FLASHING ANY GSI ANDROID 12 ABOVE FOR THIS DEVICE
THERE ARE NO BUGS AS IHAVE FLASHED ON STOCK MOTO VENDOR
THE STEPS ARE PRETTY EASY IF YOU KNOW TO USE ANDROID SDK COMMANDS
THE FIRST STEP WILL BE TO DOWNLOAD LATEST ANDROID SDK (PLATFORM TOOLS)
THEN YOU HAVE TO DOWNLOAD THE GSI ANY GSI WILL WORK ABOVE ANDROID 12 FOR THIS I HAVE CHOSEN https://forum.xda-developers.com/t/gsi-unofficial-12-pixel-experience.4354695/
YOU COULD ALSO USE ANDROID 13 GSI BUT IT IS BIT LAGGY
AFTER DOWNLOAD IS DONE OPEN CMD ON YOUR PLATFORM TOOLS FOLDER AND USE THE COMMANDS GIVEN BELOW
fastboot devices
fastboot set_active a
fastboot flash product product_gsi.img
fastboot erase system
fastboot flash system system.img
after it is done reboot your phone
use the product image given here otherwise you will get error
you can get a message to format your device dont worry and just format it , also use fastbootd for the gsi flash
Now you will experiance some lag in system ui but dont worry just open settings select phh treble settings then misc features and there you will see the option force fps click on it and select [email protected] this will set the refresh rate to 90 and boom the phone will work smooth like a butter
gsi image
:note this will only work if have unlocked bootloader and use fastbootd to flash the gsi
Does this fix the stock UI lag? Even though it's on 90Hz I experience great lag. The app launches are slow and stutter. Does this image support fingerprint scanner, NFC tap to pay Google wallet, Netflix?
MAKEN7666 said:
gsi image
Click to expand...
Click to collapse
AndroSanDev said:
Does this fix the stock UI lag? Even though it's on 90Hz I experience great lag. The app launches are slow and stutter. Does this image support fingerprint scanner, NFC tap to pay Google wallet, Netflix?
Click to expand...
Click to collapse
yes the system ui wont lag after setting the refresh rate to 90 and everything is working perfect because it is stockk motorola vendor
the gsi is far better than the stock rom i got improvement in performance and increase in fps in games like mcpe and cod
Joshch96 said:
Hi so today I Recieved a Motorola Moto G22 that I'd brought online.
Now upon booting the phone a number of things became apparent.
1) the stock image the phone comes with is seriously bad, from further inspection it appears google bloatware eats the ram.
2) upon thinking okay prehaps i should use a custom rom , however after many hours looking and trying diffrent things I've had no success.
So from trying many of the basic guides for unlocking motorola's bootloader, I've found an issue where i can't unlock it, when trying fastboot oem get_unlock_data
i get the following error " FAILED (remote: 'unknown command') " , I got this error with many other commands other guides suggested the only command that actually worked was "fastboot getvar all " which returned the varibles but with nothing really useful other than that the bootloader is locked.
so my question is : is it possible to unlock this thing and put better software on it?
software details which might help:
version: Moto G22 (XT2231-2} with android 12 RETGB 4GB ram 64GB space
I brought it to replace a sadly broken S9 which was working until the microphone stopped working for evering. (that and the buttons falling off)
Many Thanks in advance.
Josh
Click to expand...
Click to collapse
You we’re getting unknown command error because you were using normal fast boot use fastbootd to open it enter fastboot select recovery after few sec you wil see no command then hold and press repeatedly volume up and power button after that the recovery will appear then select enter fastboot then give commands it will work
thanks for posting this tutorial I successfully installed android 13 pixel gsi on my Moto g22 it’s way much better than the stock rom
I'm getting this error
platform-tools> ./fastboot set_active a
(bootloader) version-bootloader:0x0923
(bootloader) unlocked:yes
fastboot: error: Device does not support slots
Arthursmithlik said:
You we’re getting unknown command error because you were using normal fast boot use fastbootd to open it enter fastboot select recovery after few sec you wil see no command then hold and press repeatedly volume up and power button after that the recovery will appear then select enter fastboot then give commands it will work
Click to expand...
Click to collapse
please explain how to unlock the bootloader, because I've done everything and I can't unlock it.
Vinniciusf said:
please explain how to unlock the bootloader, because I've done everything and I can't unlock it.
Click to expand...
Click to collapse
I managed to unlock the bootloader through this video (
) and I installed the pixel and I liked it
I was able to unlock bootloader and install Android 13 gsi. I had to delete and recreate partitions since the stock system partition size was not sufficient for gsi 13 build.
Its smooth and great but gsi images are bare minimal and the stock dialer app is not working properly. It doesnt show the inprogress call and hence cant end it.
Is there a way to download a stable custom gsi like maybe pixel experience and install it? I tried to download a img file from an unofficial source and sideload it but it fails. Also is there a working twrp build that I can flash for moto g22?
MAKEN7666 said:
:note isso só funcionará se tiver desbloqueado o bootloader e usar fastbootd para piscar o gsi
Click to expand...
Click to collapse
amigo, você poderia colocar o link de download desta versão de 12 pixels?
AndroSanDev said:
I was able to unlock bootloader and install Android 13 gsi. I had to delete and recreate partitions since the stock system partition size was not sufficient for gsi 13 build.
Its smooth and great but gsi images are bare minimal and the stock dialer app is not working properly. It doesnt show the inprogress call and hence cant end it.
Is there a way to download a stable custom gsi like maybe pixel experience and install it? I tried to download a img file from an unofficial source and sideload it but it fails. Also is there a working twrp build that I can flash for moto g22?
Click to expand...
Click to collapse
i tried setting refresh rate to 90 on gsi and its good now and you could easily resize the partition by just flashing the product image . currently iam working on twrp for this device i tried to patch magisk but failed . you could try the linage os gsi or phh treble they provide updates so i suggest phh treble
Just finished rooting my new Tablet.
Unlocked bootloader, Flashed new factory image and patched Magisk all by manual methods.
PixelFlasher didn't work as it does on Pixel 7 Pro, so save some time and wait for the official support.
Happy to help if anyone gets stuck.
Thanks for the update. Which file did you patch with Magisk to get root?
Are you passing Safetynet?
Rooted the thing 5 minutes out of the box.
Magisk stable. Passes safety net.
Follow a Pixel 7 rooting thread use the latest posted images, patch init_boot.img
I disabled verity too in case a custom kernel is done in the future.
bleez99 said:
Rooted the thing 5 minutes out of the box.
Magisk stable. Passes safety net.
Follow a Pixel 7 rooting thread use the latest posted images, patch init_boot.img
I disabled verity too in case a custom kernel is done in the future.
Click to expand...
Click to collapse
Would do the same. Thank you
MArtyChubbs said:
Just finished rooting my new Tablet.
Unlocked bootloader, Flashed new factory image and patched Magisk all by manual methods.
PixelFlasher didn't work as it does on Pixel 7 Pro, so save some time and wait for the official support.
Happy to help if anyone gets stuck.
Click to expand...
Click to collapse
I don't have the tablet, so the support file would greatly help to add official support for it.
Would you be able to provide it?
If not do you recall what exactly happened?
Was it during processing, patching or flashing?
Thanks
Update:
Aside from flashing, which I can't because I don't have the tablet, the latest version of PixelFlasher is able to process, extract init_boot and create a patch without any issues both for factory image and full OTA.
I even went as far as attempting to flash factory (without actually flashing) to inspect the final flashing script, and everything in there looked right.
I don't see how / where it could have failed, based on what I've seen it should work.
Hence a support file would greatly help if there is any issue to identify.
Thanks
just unlocking the bootloader w/PixelFlasher (latest ver.) "corrupted" my Slot B boot (Your device is corrupted) and it refuses to boot (grin).
Also, I'm pretty sure it said "no init_boot found" as part of device info. I can't confirm as I'm not with the tablet today.
ntegra said:
just unlocking the bootloader w/PixelFlasher (latest ver.) "corrupted" my Slot B boot (Your device is corrupted) and it refuses to boot (grin).
Also, I'm pretty sure it said "no init_boot found" as part of device info. I can't confirm as I'm not with the tablet today.
Click to expand...
Click to collapse
If you could provide a support file from PixelFlasher I can check, and you don't need to repeat the steps to get a support file, just launch PF and hit the support button or from the help menu.
If the unlock command has not changed, I don't see how it would cause that.
All the unlock button does is
if it is in adb mode, it reboots to bootloader mode and then issues the command
fastboot flashing unlock
If it is already in bootloader mode, it just issues the command.
I'm baffled and would really like to get to the bottom of this.
badabing2003 said:
If you could provide a support file from PixelFlasher I can check, and you don't need to repeat the steps to get a support file, just launch PF and hit the support button or from the help menu.
If the unlock command has not changed, I don't see how it would cause that.
All the unlock button does is
if it is in adb mode, it reboots to bootloader mode and then issues the command
fastboot flashing unlock
If it is already in bootloader mode, it just issues the command.
I'm baffled and would really like to get to the bottom of this.
Click to expand...
Click to collapse
soonest I could provide is 6 hours or so..
@badabing2003 yeah, I'll try to get that support file within the next hour. The tool said everything was successful but it always rebooted back to the bootloader when unlocking the bootloader or flashing a new image, thus I had to do everything manually
Update: @badabing2003 Support file is attached. Thanks!
I plan on rooting mine right away. Did anyone have a delay on their order? I have a trip coming up and it's supposed to arrive the day before.
Thanks @MArtyChubbs and @ntegra for providing support files.
@ntegra
Comments / observations based on your support file.
You started with Pixel 7pro,
You had an error during flashing
Code:
Sending sparse 'vendor_b' 3/3 (130768 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
rebooting to bootloader ...
Rebooting into bootloader FAILED (Write to device failed (no link))
fastboot: error: Command failed
Sleeping 5-10 seconds ...
flashing pf_boot ...
This is communication issue, phone unplugged or disconnected during flash or wire loose or bad driver / port / cable ...
But then you flashed p7p ok,
Moved to the tablet, which was locked at this point
Code:
Selected Device on 2023-06-20 20:00:50:
Device ID: REDACTED
Device Model: tangorpro
Device Active Slot: a
Device Mode: adb
Has init_boot partition: False
Device is Rooted: False
Device Build: TD2A.230203.028
Device API Level: 33
Device Architecture: arm64-v8a
sys_oem_unlock_allowed: 1
ro.boot.flash.locked: 1
ro.boot.vbmeta.device_state: locked
vendor.boot.verifiedbootstate:
ro.product.first_api_level: 33
ro.boot.verifiedbootstate: green
vendor.boot.vbmeta.device_state:
ro.boot.warranty_bit:
ro.warranty_bit:
ro.secure: 1
ro.zygote: zygote64
ro.vendor.product.cpu.abilist: arm64-v8a
ro.vendor.product.cpu.abilist32:
Device Bootloader Version: tangorpro-1.0-9584303
Magisk Manager Version:
Magisk Path: None
Checked for Package: com.topjohnwu.magisk
You proceeded to unlock the bootloader with PF
Which it did successfully
Code:
Selected Device on 2023-06-21 06:09:09:
Device ID: REDACTED
Device Model: tangorpro
Device Active Slot: a
Device Mode: f.b
Has init_boot partition: False
Device Unlocked: True
One thing to point out, after bootloader unlock, PF keeps the phone in bootloader mode (in case you might want to do other stuff)
But I think people tend to expect it to reboot to system, because I noticed this might have thrown you off seeing it in bootloader mode.
What I'll do for the next release is that unless you select no reboot option, PF should automatically reboot.
Another thing I noticed is that you attempted to create a patch while the phone is in bootloader mode
Which does not work, because that can only work in ADB mode.
In the next version I'll disable the patch button so that when in bootloader mode, you can't press it.
I see that you rebooted to system and the device was unlocked
Code:
Selected Device on 2023-06-21 06:14:41:
Device ID: REDACTED
Device Model: tangorpro
Device Active Slot: a
Device Mode: adb
Has init_boot partition: False
Device is Rooted: False
Device Build: TD2A.230203.028
Device API Level: 33
Device Architecture: arm64-v8a
sys_oem_unlock_allowed: 1
ro.boot.flash.locked: 0
ro.boot.vbmeta.device_state: unlocked
vendor.boot.verifiedbootstate:
ro.product.first_api_level: 33
ro.boot.verifiedbootstate: orange
vendor.boot.vbmeta.device_state:
ro.boot.warranty_bit:
ro.warranty_bit:
ro.secure: 1
ro.zygote: zygote64
ro.vendor.product.cpu.abilist: arm64-v8a
ro.vendor.product.cpu.abilist32:
Device Bootloader Version: tangorpro-1.0-9584303
Magisk Manager Version:
Magisk Path: None
Checked for Package: com.topjohnwu.magisk
Installed Magisk and created a patch.
All good.
You then proceeded to flash with
Flash To Inactive Slot: True
Everything about the flashing went well, but the phone stayed in bootloader mode.
I see now why that happened.
It flashed ok, but then it tried to flash the patched image to boot partition instead of init_boot partition.
PF detects if it needs to flash into init_boot partition or boot partition by doing two checks.
1- If it is defined in PF, and up to version 5.3.2.1 only defined are 'panther', 'cheetah', 'lynx' because at the time of the release only those were known. (tangorpro added in the next version)
2- By checking partitions and seeing if there is a init_boot partition, this way it would be forward working with future devices, but sadly due to oversight the code was looking for init_boot and expecting to find it, but there is init_boot_a and init_boot_b, and not init_boot, (fixed in the next version)
@MArtyChubbs
The flashing your tablet had the same fate as above, PF tried flashing boot partition instead of init_boot.
Fixed, I should have a release later today.
For anyone who cannot wait, and wants to use PF, all you have to do is before hitting OK to continue flashing, hit the Edit script before continuing button and modify the line
Code:
flash boot pf_boot.img
to
Code:
flash init_boot pf_boot.img
As for unlocking, I don't see errors, but I see that the phone was not detected,
Do you recall exactly what happened? perhaps it was showing the wipe message and hence why it was not really yet to be detected?
Code:
2023-06-20 16:58:12 Unlock Bootloader
*** Dialog ***
WARNING!!! THIS WILL ERASE ALL USER DATA FROM THE DEVICE
Make sure you first read either of the guides linked in the help menu.
Failing to follow the proper steps could potentially brick your phone.
Note: Pressing OK button will invoke a script that will utilize
fastboot commands, if your PC fastboot drivers are not propely setup,
fastboot will wait forever, and PixelFlasher will appear hung.
In such cases, killing the fastboot process will resume to normalcy.
Do you want to continue to Unlock the device bootloader?
Press OK to continue or CANCEL to abort.
______________
2023-06-20 16:58:14 User Pressed Ok.
Rebooting device REDACTED to bootloader ...
Waiting 5 seconds ...
2023-06-20 16:58:31 No Device is selected!
2023-06-20 17:12:46 Scanning for Devices ...
No Devices found.
@badabing2003,
Thanks for the response. great program, excellent support. For me, the first p7p failed (I agree with you) due to comm problem. I forget that the USB ports on one side of my laptop are flakey. I watched it bomb out writing system_b (I think) and just moved the cable to the other side and reran the flash to 100%.
For the tablet... I ran unlock twice (was still locked after first attempt). I "want" to say that the "your device is corrupt" was in between the two runs (unlock / reboot / device corrupt / unlock again) but definitely showing corrupt before first flash attempt. After a couple attempts to boot, I put it back into bootloader (and also download & recovery modes) and flashed the patched image, but it didn't help I'm guessing because of the init_boot(_b). Will be patiently waiting (neither slot are booting-grin) for your next release. I'm in no rush.
@badabing2003 I'd like to thank you as well! Love the tool and your excellent support. You and @Freak07 are such an asset to the community as are soo many other devs...
rester555 said:
I plan on rooting mine right away. Did anyone have a delay on their order? I have a trip coming up and it's supposed to arrive the day before.
Click to expand...
Click to collapse
No, arrived right on time.
MArtyChubbs said:
No, arrived right on time.
Click to expand...
Click to collapse
Looks like mine is coming on the earliest day of the planned shipping dates.
@MArtyChubbs and @ntegra
PixelFlasher 5.3.2.0 is released which adds support for Pixel Tablet.
There is also a dedicated support thread.
📳🔥PixelFlasher for Google Tablet Support Thread.
This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...
forum.xda-developers.com
Thanks for your support.
badabing2003 said:
@MArtyChubbs and @ntegra
PixelFlasher 5.3.2.0 is released which adds support for Pixel Tablet.
works a treat!
Click to expand...
Click to collapse
I got my tablet. Made the painstakingly slow mistake of updating the OTA before unlocking. The OTA takes forever.
Got my tablet. Had it rooted in less than 30 minutes.
rester555 said:
I got my tablet. Made the painstakingly slow mistake of updating the OTA before unlocking. The OTA takes forever.
Click to expand...
Click to collapse
Yep OTA on a device is very slow and is incremental, specially if you have to flash several times if you are free months behind.
Even if you don't unlock your bootloader, you can sideload OTA in PixelFlasher.