Hi all. I bought my Evo 3D phone from someone and the wifi is not working. Trying to turn it on just results in "Error". Apparently this is rooted and/or has custom firmware. The software is NegaLite BluROM with android 4.0.3. I was wondering if anyone could help a root/cfw newbie with step by step instructions on how to get wifi working again. My google research showed something about a Mobster ROM being the best firmware, but have no idea about anything.
i like negalite the best, but what release is it?
i also liked mobster lite and unsenseable.
negalite blurom cdma vm r115
try the official thread here:
http://forum.xda-developers.com/showthread.php?t=1745093
i use jcfunk's fork, its more recent and you might even get something hot off the press if you check out his svn.
midnight rom deserves a mention:
http://forum.xda-developers.com/showthread.php?t=2141207
i'm not sure where mobster went, i'll hunt a link down later if you need. same with unsenseable.
jawbonegroove said:
try the official thread here:
http://forum.xda-developers.com/showthread.php?t=1745093
i use jcfunk's fork, its more recent and you might even get something hot off the press if you check out his svn.
midnight rom deserves a mention:
http://forum.xda-developers.com/showthread.php?t=2141207
i'm not sure where mobster went, i'll hunt a link down later if you need. same with unsenseable.
Click to expand...
Click to collapse
I yes, latest is on svn, but latest zip negalite-funk_mod_v3.zip
hey jcfunk i replied to the official thread. i tried the update but wifi still won't work
Are you s-off or just unlocked?
jcfunk said:
Are you s-off or just unlocked?
Click to expand...
Click to collapse
i never knew what s-off was. i rebooted into recovery and it turns out i have s-on. then i googled and found Unrevoked, but the download doesn't work.
Here I can quick fix your phone, download recovery on computer.
ReBoot phone into bootloader.
From computer,
fastboot boot recovery.img
This will upload recovery.img to phone, and boot recovery with write access to boot partition. Which HTC has locked, this is first method found to by pass. Other would be dumb-lock. But that's your wifi issue, because your still using stock kernel, but wifi drivers are built for my kernel
jcfunk said:
Here I can quick fix your phone, download recovery on computer.
it just says Bootloader, Reboot, Reboot Bootloader. those are my options i'm not sure what to do
Click to expand...
Click to collapse
Also, can use Flashify to install a boot.img but won't work with installer zip for my kernel, because boot.img is made during install.
May look like this, fastboot shows when usb is plugged in.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
yeah the screens look like that but i tried all the options. i don't know how to install your image
InvisiSource said:
Home of the ORIGINAL hboot 1.50 'how to flash'
less than 48 hours after HTC released their web based unlocker, i walked a user thru the process below in public chat (the public Synergy Chat room) - two hours later some one posted it on XDA and claimed creait for it, even copied/pasted my spelling errors. when called out with screen shots of the chat with timestamps, they still claimed credit. - this is the ORIGINAL.
This is a cleaned up and detailed version of the chat, I included it as 2nd post to my roms and always posted it when someone needed help. so a few weeks later, i finally decided to make a post here.
---
so, you unlocked using HTC's unlocker located at HTCDEV.com
some background on this unlock method:
-when you unlock using HTC's unlock method, the boot partition is still read only, and you cant flash to it. (kernels and ramdisks go here - so no 2.3.3 rom will boot, and most 2.3.4 roms will not work correctly)
when you unlocked your bootloader using HTC's method, you should have downloaded a file that contained some program files, mainly fastboot.exe and adb.exe, as well as the device drivers you would have to install to unlock
- you will need these
to get around this problem HTC has created, we will be using the fastboot.exe program to force the ramdisk/kernel onto the phone. anytime you use fastboot to flash a partition, you risk bricking your phone, so please do this at your own risk.
I have walked several people thru this, and no one had any problems, but if something dont go right, or the connection between the pc and the phone gets interrupted, your phone may become bricked.
I am going to assume you know the basics of flashing a rom, and that you have either teamwin or clockwork's recover tool installed on your phone (and you know how to use them). if not please see series #3 below.
SERIES 1 - INSTALL A ROM AND RAMDISK/KERNEL
Step 1 - backup everything on your phone, nandroid backup
step 2 - if you want to flash the ext4 optimizer for /data, read the info and directions here -> http://forum.xda-developers.com/show...postcount=6329
------>everything should be backed up now
Step 3 - flash Virus's superwipe tool.
Step 4 - flash the /data optimizer tool - the download can be found in the post linked in step 2
Step 5 - open the rom you downloaded using winrar, or 7zip, and copy the boot.img file somewhere (the same folder that contains the tools you used to unlock your phone would be a perfect place)
Step 6 - open a command prompt (or terminal window), and goto the window that contains the tools you used to unlock your boot loader
Step 7 - reboot your phone into fastboot (adb reboot bootloader)
Step 8 - from the command prompt enter the following command:
fastboot flash boot boot.img
then press [enter]
Step 9 - once complete, exit fastboot, and boot back into recovery
Step 10 - flash the rom's zip file using recovery
Step 11 - enjoy
SERIES 2 - INSTALL A RAMDISK/KERNEL (ROM ALREADY FLASHED)
*signs of a failed ramdisk flash include broken wifi, 4g, poor performance and just weirdness in general. the updater scripts used to install a rom will not flash ramdisk with S-ON.
Step 1 - open the rom you downloaded using winrar, or 7zip, and copy the boot.img file somewhere (the same folder that contains the tools you used to unlock your phone would be a perfect place)
Step 2 - open a command prompt (or terminal window), and goto the window that contains the tools you used to unlock your boot loader
Step 3 - reboot your phone into fastboot (abd reboot bootloader)
Step 4 - from the command prompt enter the following command:
fastboot flash boot boot.img
then press [enter]
Step 5 - reboot your phone and enjoy (fastboot reboot)
SERIES 3 - INSTALL A RECOVERY TOOL
*you may need to do this before each flash, some phones somehow break recovery after a rom is flashed, and recovery will not launch until re-flashed for some reason (Kathy.. )
Step 1 - download TeamWin's recovery here (IMG format) -> http://dl.dropbox.com/u/24995663/recovery.img
Step 2 - copy this file to the same directory as your fastboot and adb files HTC had you download to unlock your phone.
Step 3 - goto your dos prompt (or terminal if on linux)
Step 4 - change directories to the folder your files are in (recovery.img and fastboot)
Step 5 - flash your recovery using the following command
fastboot flash recovery recovery.img
Step 6 - reboot your phone (fastboot reboot)
*disclaimer - you do this at your own risk. as of yet, the processes listed above work 100% and not 1 failure has been reported. make sure your usb cable is good, and your pc has good power during any fastboot process. most of this comes from a chat i had in the synergy public/general chat room 2 hours prior to it being posted on XDA by others claiming credit. kangers goto hell.
fastboot for mac and linux attached below:
ADB and FASTBOOT for windows:
View attachment 330
Click to expand...
Click to collapse
Here is a quote from other site
I assume Series 3 is the part I need to follow? Do I do this during recovery mode or normal phone mode? Because I don't know the file directory of my phone
kracovwolf said:
I assume Series 3 is the part I need to follow? Do I do this during recovery mode or normal phone mode? Because I don't know the file directory of my phone
Click to expand...
Click to collapse
Yes, but post was very old, use recovery I posted. Also if you use command
Code:
fastboot boot recovery.img
instead of
Code:
fastboot flash recovery recovery.img
It will load/run recovery from computer, then install kernel from recovery.
Who took the credit for your guide?, just wondering
PiggyFlooper said:
Who took the credit for your guide?, just wondering
Click to expand...
Click to collapse
What do you mean? The quote I posted?
Related
So its time to have some fun flashing your phone.Rooting means getting acess to the Root of the Phone Rom.Once rooted you can install Custom Roms [Operating Systems],Remove Crappy apps, get better performance and Battery etc. Rooting your phone is Not Big job ,But a Bit lengthy at the first time..But you will end up in trouble if you dont know the actual procedure.That doesn't mean you will brick your phone.Android phones are based on Flash ROMs ,just like a memory card. So flashing a 100 or1000 times wont destroy it.It is completely Safe and there is nothing much to worry about .But make sure sure you have an un interrupted power supply if you are using a PC. So here i am taking effort to bring out a step by step description of the process.
Understanding what it is...
Many people still doesn't know what actually is rooting and a custom rom mean. The Process is to completely Remove your Current Phone OS and Install a Fresh copy of another OS. If you have installed a windows /Linux formatting your pc its easy to understand.Your device has a 440MB flash memory for OS and 420 Mb Internal memory for installing apps etc.When the phone comes to you not the entire memory of 420 Mb is available to u ,because sony has included some stock Bolt wares in ur OS.So rooting provides a larger internal memory as well .In your pc you might have come across the bootloader /boot menu .In your sony phone this boot-loader is Locked to prevent alterations. But android being an opensource stuff , it is required that the phone manufacturer should allow you to install Custom androids. So in order to access the Boot-loader u will have to unlock it first. After unlocking a recovery Mode is to be installed.That's what u call kernelling. After that , u will wipe the User memory 420mb ,Format[Done auto] & install the Zip file containing android os onto the 440Mb memory.The zip file contains the Customized android OS.Its called the rom .MiUi is one such rom.
Benefits: Lots of Customization , More features ,Better battery ,A faster OS,Latest Android versions.
Negatives: Voids warranty .
Why it voids warranty ?
Simply because Sony cant take up the responsibility if you destroy your phone hardware by your mistake. For example if u overclock [Possible only after rooting] the CPU there are chances that it smokes out.
Warning : Unlocking Boot loader voids Sony Service Center warranty.
Rooting involves 3 steps,
1-Unlocking Bootloader
2-Installing a Custom Bootloader /Kernel/Recovery
3-Installing the Rom /Android OS.
Tools Required [Download all of them before starting ]
1.Sony Xperia Flashtool *[Optional]
2.Drivers
3.android_winusb.inf Driver[Click to Download]
4.ROM & Kernel (Once downloaded , Copy the Rom File to the Micro SD[Important, if u don't wanna end up searching for a card reader ] )
OR
ROM-2 [Lasans's MiUi ] ( If u find any issues with the other one Try this Rom,Download only the Rom File )
*Actually you do not need the Complete Xperia flasher tool. you are only using the Fastboot from Xperia flasher. If u don't have time to download the Flash tool just download only the Fastboot tool and Drivers from HERE or Here .But its better to download Flash tool as u can perform some additional operations like Installing apks , Uninstalling features etc . using the tool.
Step 1 : Unlocking the Bootloader
1. Unlocking the Bootloader requires the Unlock Code.You can get it from the sony website at the Following link .
http://unlockbootloader.sonymobile.com/
Enter your Phone IMEI ,Email etc. and Get the unlock Code.While you enter the IMEI take care not to Include the last DIGIT of your IMEI.IMEI should be 14 digits long.
2. Now Install the SONY Xperia Flash tool from Here
http://androxyde.github.com/ OR JUST UNZIP THE FASTBOOT.ZIP TO C:\
3. You will need fastboot on the computer to unlock the bootloader of the Sony Ericsson Live with Walkman . Fastboot is available in Xperia Flashtool folder in C:\Flashtool or where you have installed Flash tool OR IN C:\ WHERE U HAVE UNZIPPED IT TO.
4. Now Power off your Sony Ericsson Live with Walkman.
5. Press & hold the Volume Up button while connecting the Sony Ericsson Live with Walkman to the computer.The Notification LED will now glow in Blue color.This is called Fastboot Mode.
[ Press and Hold Vol Down key while connecting to USB will Boot in Flash Mode ]
6. If the drivers are not installed automatically ,go to the Drivers folder in Xperia flash tool folder and install the drivers.You can check if the drivers are properly installed by going to the windows device manager and see if there is any Unidentified device .If properly installed it will shown in device manager.If u find an entry "s1 boot fastboot " with Missing drivers in device manager ,Right Click there -> Update Driver ->Browse My computer ->Let me Pick -> Have Disk >> Then Point to the Downloaded "android_winusb.inf" file. >> Choose "Android Bootloader device".Now your drivers Should be installed.In the device manager You will find an Android device.
7. Go to Terminal or Command prompt in windows and change directory to "C:\Flashtool\x10flasher_lib" .You will find the fastboot.exe file there.
See the Image attached at Bottom of this page .
Enter following commands to navigate
cd\
cd flashtool\x10flasher_lib or cd fastboot
Now you are int the folder containing fastboot.exe
8. Now check if the phone is properly connceted and detected by Typing the following in the cmd .
fastboot -i 0x0fce getvar version .It must return the version of fastboot .Eg: .3
If it shows "Waiting for device" the device is not connected properly.If it returns anything else [ like .3 ] the device is detected .
9. Now type the Following and press ENTER
fastboot -i 0x0fce oem unlock 0xKEY
where KEY should be replaced by the Unlock key you generated from the Sonymobile website .
10. Once it display Flash operation complete , you are Done .Your phone Bootloader is no more locked.
PS:If you find any problems using this method you may follow one these links.
http://unlockbootloader.sonymobile.com/instructions
http://forum.xda-developers.com/showthread.php?t=1560613
Step 2 : Installing the Kernel
Android is based on the Linux kernel.A kernel is actually a link between the OS and the hardware.It controls the hardware.So obviously it has got something to do with the performance & battery life. The kernels contain the RECOVERY MODE+ROOTING. You may read more about kernels on xda-developers.com .So there are a number of kernels available for Sony live . You may find it in the rom download pages usually.
Two of the popular kernels are
1. X-Kernel
2. Rage kernel
Download one of these kernels, a ROM file and flash your phone.
Here we are working with the Expeacers MiUi Rom.
Steps
1. Once you are done with Unlocking Rest is So easy .Do not disconnect the phone .We are going to use the phone in Fast boot mode. If u have disconnected ,don't worry ,just shut down [Or pullout & Re-insert the battery ]the device and Reconnect it to PC Holding the Vol+ key pressed.Now the notification led will turn Blue.You are back in fast boot mode.
2. Copy the Downloaded kernel img file into the folder where fast boot is located and rename it to "Boot.img" .
3. Now go to Command prompt , Navigate to the x10flasher_lib[As done before ] ,Enter the following command.
fastboot flash boot boot.img or
if it doesn't do anything
fastboot -i 0xfce flash boot boot.img
4. Now you are done ."Flash operation complete " will be displayed. Disconnect your phone from PC.
Before you proceed to next step you should have copied the ROM[Zip file ] to your Memory card in the phone.
Step 3 : Installing the ROM
This is the easiest part.Just turn on your phone ,after a few 5-10 seconds the notification led will glow .
At this time Press the vol+ key once. Phone will enter the Boot loader . Now you can see a number of option.Use the Vol+/- key to navigate ,Home key to select . Choose the wipe Cache ,Wipe Rom/factory Reset options[in some boot loaders ] .This is important as this will clean up all the previous user data and installed apps. Wipe actually cleans the internal memory and Cache. This is called clean install.
Now after cleaning up ,Choose the "Install Zip From SD Card" . Now follow the on screen instructions Rest is self explanatory. Once you finish installing the Rom Reboot the device. In most of the cases First time booting might be so long. All you have to do is be patient.If its taking longer than usual try pressing the Home key once.
So its time to Enjoy a new android... A yummy Ice cream Sandwich. Now you may try as many ROMs as u wish by simply following the step 3 only.
Happy Flashing... Enjoy ...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Combined Unlocking and Burning kernel .[Click Me For Full size ]
Burning Kernel [Step 2 ]
Unlocking Bootloader [Step 1]
Man, I think you've worked long time on that, but look at the sticked threads. There's my rooting guide and bootloader unlocking, yet. You tell the same again.
And in my signature there's how to install custom kernels/roms, in the pinned thread by someguyfromhell you can read the same...
Its k..
Dude .. I made it for my Blog...:angel::angel: .. :angel::angel:
Its not tailored for XDA. Posted it here just in case somebody find it usefull
Yeah, it could help somebody...
Sent from my GT-I9100 using xda premium
THANKS MAN IT HELPED ME AS IAM STILL A NOOB and i still stuck at few steps to un lock bootloader byt at last did it
thnQ
I found an app called package signer from https://forum.xda-developers.com/android/software/tool-package-signer-1-0-t3533073 to sign the zip files in android to fix signature verfication error in some recoveries....
Developer stopped development of that app...
and also that thread is closed...
It signs correctly but one issue is, it can't able to sign zips that are greater than 20mb ......
It force closes when working with large zip files...
It is open source is github....
Sir osm0sis i have seen you are helping in zip signers..
Can you please help....
I hope some developer can fix this and post below.....
Please help by fixing that force close error of signing big zip files......
Thanks in advance...!
Edit:- See https://forum.xda-developers.com/t/...-apk-zip-within-android.3835975/post-81324327 for solution.
Nope, you should use zipsigner.jar from my Complete Shell Zip + Signing thread.
osm0sis said:
Nope, you should use zipsigner.jar from my Complete Shell Zip + Signing thread.
Click to expand...
Click to collapse
Since I dont have pc... i am using that sir...
HemanthJabalpuri said:
Since I dont have pc... i am using that sir...
Click to expand...
Click to collapse
It should work on device too if dexed, I'll add it to my thread and post instructions soon.
Reserved this too
DISCLAIMERS (please read !)
The content seen in this thread is targeted at this specific forum's device, the Realme C12, codenamed RMX2189.
Follow the instructions shown in this thread at your own risks, I will not be held responsible for bricking your device, you did this yourself.
That said, the information will be kept up to date relatively frequently, and should you follow the steps and ask questions below when unsure, everything will be fine!
No files will be directly provided. Do not use pre-created/re-uploaded content. Instead I'll teach you to gather the required files from official websites, and create the other ones yourself.
ROM (GSI) Recommendations:
Ordered by personal preference:
1) CAOS
2) LOSQ (LineageOS GSI)
3) crDroid
I'm more than open to feedback, suggested changes & improvements!
Prerequisites for most manipulations:
Your phone, well charged if possible
The USB cable used to link your phone to your computer (the one on your charger works just fine)
A computer, with recent ADB & Fastboot (Platform Tools)
Some time, patience, and the ability to read and follow instructions!
Unlock your bootloader (otherwise this thread is useless to you as it's required for rooting as well as installing custom ROMs)
Tutorial:
Step 0 - Great! You're ready to go. Make sure to backup your phone's data before continuing on with this tutorial, as unlocking will make it factory reset (wipe)!
Step 1 - Download and Open In Depth Tool ( Attached With the Guide Down)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 2 - Click “Start applying”.
Step 3 - Please read the disclaimer in detail, select the checkbox, and submit your application
Step 4 - The Application Will be checked by realme Servers..(Wait 10 mins)
Step 5 - The unlock tool apk will show the status of the unlock request- Successful
Step 6 - You can now click “Start the in-depth test” and the device will reboot automatically. The following string will display on the screen: fast boot_unlock_verify ok
Step 7 - Now Download and install the fastboot tool on your PC and ready to unlock it.
Step 8 - Now in Fastboot Mode type this command
Code:
fastboot flashing unlock
and Press enter.
Step 9 - On your phone press the Volume Up key to select "UNLOCK THE BOOTLOADER” (or press the Volume Down key if you have changed your mind to select "DO NOT UNLOCK THE BOOTLOADER”). When you click the Volume Up, your phone will reboot and enter the in-depth test mode - all user data on the phone will be erased - I recommend you perform a data backup prior to applying.
Step 10 - Now type
Code:
fastboot reboot
And there you go! Your phone will reboot and you can set it all up again, with the ability to follow the rooting tutorial below, and you can also install GSIs/custom ROMs/recovery!
Rooting with Magisk
Tutorial:
The procedure is the same whether you're on the stock RealmeUI Rom or on a custom GSI (treble) one.
Step 1 - Download the latest Magisk Manager on your phone.
Go to the link above, click the latest MagiskManager-vX.X.X.apk you see in the list to start the download, open the file and install.
Step 2 - Download the latest Realme Official Rom from Software Update - realme depending on your region.
Step 3 - Get your ROM you downloaded above, it should be a .ozip archive. Add .zip extension to it. Extract it.
Step 4 - You should now get a folder like shown below, and..
Copy the boot.img to your phone's /sdcard/ folder (where the Android, DCIM, Download, and more are present, just drop it in there).
And here's how it shoud look inside your phone's storage in the end.
Step 5 - On your phone, open up Magisk Manager.
Click the Magisk Install button as shown below.
Then Select and Patch a File.
Go look for your boot.img you previously copied to your phone and pick it.
Click Let's go! and wait for Magisk to complete the process!
Step 6 - Link your phone to your PC, and grab the file the Magisk Manager created. It's located in your downloads folder, called magisk_patched.img.
Step 7 - Paste it where your ADB & Fastboot (Platform Tools) are located, along with the vbmeta.img file located in Stock ROM's images folder from earlier, where you grabbed the original boot.img.
You should now have a folder like this with:
adb(.exe)
fastboot(.exe)
magisk_patched.img
vbmeta.img
Extra files from the platform tools
Step 8 - Alright, we're ready to root! Turn off your phone, and get in fastboot mode like we did during the bootloader unlocking (Power + Volume Down).
Step 9 - Link your phone to your PC with the USB cable if not done already.
Step 10 - Shift + Right click in an empty space inside the folder we prepared in Step 7, and click Open Command window here.
Inside the Command window, input the following commands line by line, in order.
Code:
adb reboot bootloader
fastboot devices
And make sure your device shows up, should be a bunch of numbers and letters, a couple spaces, and fastboot.
If nothing does, go back to Step 8 and try again.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched.img
fastboot reboot
You're done! Your phone will reboot, hopefully, without a hitch! Open up Magisk Manager, and check that it's installed.
That said, you will have issues leaving it like this. You need to hide the fact that your phone is rooted, there's no downside to doing it.
Check out the Passing SafetyNet tutorial further down below, it's quick and easy.
Getting EdXposed (Not recommended unless really needed, requires Magisk)
I very much do not recommend to EdXposed your phone unless you have a very good reason for it. It's a pain to pass SafetyNet, doesn't get updated as often as it could/should and has very niche use cases for which it's worth it.
That said, I do include it here for people who know what they're getting into and want the up-to-date instructions on how to do it.
Tutorial:
This procedure requires to be rooted with Magisk. See the tutorial above.
Step 1 - Inside Magisk Manager, go to the Modules tab (4th icon), click the search button (bottom right) and search Riru.
Step 2 - Install the Riru (Riru - Core) module, Activate it and Reboot.
Step 3 - Install the Riru - EdXposed (YAHFA or SandHook, both work fine) module, Activate it and Reboot.
Step 4 - Download and install the latest EdXposed Manager in the exact same way you did with Magisk Manager.
Step 5 - Open it up, it should say EdXposed Framework is active!
You're done! You should now be able to install EdXposed modules.
That said, you will have issues leaving it like this. You need to hide the fact that your phone is EdXposed.
It's a bit more complicated than hiding Magisk, but it's doable! Check out the Passing SafetyNet tutorial further down below, it's quick and easy.
Passing SafetyNet (Only possible with Magisk. Not with SuperSU on GSI's)
Tutorial:
For Magisk Rooted PhonesEnable Magisk Hide inside Magisk Manager's settings.For EdXposed PhonesAgain, I highly recommend not EdXposing your phone and sticking to just Magisk if you can help it.
You should also know that this method will show you're passing SafetyNet inside Magisk but it's a pain to do and isn't as well hidden as Magisk alone.
Step 1 - Do the step for Rooted phones listed above if not done already.
Step 2 - In EdXposed Manager, get the HiddenCore Module and activate it.
Step 3 - Now, in the side-menu: Compat List > tick HiddenCore Module.
Step 4 - Then, go to Settings > Framework > Enable "App List mode".
Step 5 - Finally, Applications(Black List) and tick: Android Services Library, Chrome, Google Play services, Google Play Store, Google Services FrameworkReboot and enjoy! You're all set and SafetyNet should pass just fine.
Installing GSI's (Custom ROMs)
Tutorial:
Step 1 - Pick your poison in the Treble Forums!
Check the top of this thread if you want to see my recommendations with links to them.
Step 2 - Download the chosen ROM, A/B Arm64 version (usually nicknamed b), with (g) or without GApps (v), rooted (S) or not (N), that's entirely up to you.
It should be an .img.xz file, extract it and you'll get an .img file.
You're ready to flash. Make sure to backup your phone's data before continuing on with this tutorial, as wiping it is required for installation!
Step 3 - Put your phone into fastboot mode (Power + Volume Up) and link it to your PC.
Step 4 - Move the .img file you downloaded to your ADB & Fastboot (Platform Tools) folder, and rename it to system.img.
Step 5 - Shift + Right click in an empty space inside the folder, and click Open Command window here.
Inside the Command window, input the following commands line by line, in order.
Code:
fastboot reboot fastboot
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot flash system system.img
fastboot -w
fastboot reboot
Your phone will now reboot on its own, using the new ROM you picked earlier, set it all up and enjoy!
Relock your bootloader
Tutorial:
Step 0 - Back to stock ROM by flashing it in stock recovery.
Step 1 - Download the unlock tool again to apply to exit the in-depth test.
Step 2 - Click “Apply to exit in-depth test”. You should manual operation enter the Fastboot mode(Press both the Volume up button and the Power button when power is off).
Step 3 - In the Fastboot mode, use the engineering command below on your PC to re-lock the bootloader.
- Enter the command: adb reboot bootloader
- Press “Enter” on your keyboard
- Enter the command: fastboot flashing lock
- Press “Enter” on your keyboardStep 4 - Press the Volume Up button to select the “Lock bootloader” option (or press the Volume Down button to select “Do not lock bootloader" and keep it unlocked).
Step 5 - Then enter command fastboot reboot. The phone will reboot and exit the in-depth test mode. All user data on the phone will be erased - we recommend you perform a data backup prior to applying.
Frequently Asked Questions (FAQ)
Q: Will unlocking my bootloader void my warranty?
A: No, it will not. Unless you brick your device.
Q: Hey, I rooted/edXposed my phone, and now Netflix won't even open, or doesn't work properly, what's up with that?
A: Well, fortunately, there's an easy fix if you have Magisk. Install the liboemcrypto disabler Magisk module, activate it and reboot.
Q: I tried unlocking my bootloader but, PC doesn't detect my phone, even though it's in fastboot mode and connected. Help?
A: Here are some things you can try:
- Try another USB port.
- Try another USB cable.
- Install the Realme USB Drivers manually from here.
Q: Alright, I did a bunch of manipulations but something went wrong, or I'm tired of it, how do I reset everything, etc..
A:
Step 1 - Backup all the data you might have on your phone to restore it after the manipulation!
Step 2 - Download the stock ROM corresponding to your region from Software Update - realme.
Step 3 - Put the stock rom in your mobile Internal Storage or in Memory Card.
Step 4 - Put your device into recovery mode (Turn it off, then Power + Volume Down) and flash that in recovery.
Step 5 - Reboot to stock rom, all good and fresh!
If you want to repost this guide to other websites, please let me know before you repost.
For Chinese users: 中文版教程将会在dospy发布。
Click to expand...
Click to collapse
So after you unlock the bootloader successfully, you definitely want to install custom ROM, or at least root the phone, right?
Here's the guide about rooting Nokia 3.2 / 4.2.
This guide could probably work on Nokia 6.2 / 7.2 in the future.
Step 1: Unlock the bootloader
https://forum.xda-developers.com/nokia-4-2/how-to/guide-how-to-unlock-bootloader-nokia-4-2-t3962402
For Nokia 3.2, you'll need to read this as well: https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841
Step 2: Acknowledge current slot
You have two methods.
Method 1: After USB debugging enabled, execute this command:
Code:
adb shell getprop ro.boot.slot_suffix
Method 2: Under fastboot mode, execute this command:
Code:
fastboot getvar current-slot
We assume the current slot is b.
Step 3: Trigger the phone to EDL mode again
There's a hidden command in aboot known as "fastboot reboot-emergency".
However, normal fastboot binary doesn't have that command at all, so we need to compile a binary or hack the binary.
For Windows users, I've provided the fastboot binary that can use this command, and I renamed it to edl-fastboot.exe. You can download it on the attachment below.
For macOS/Linux distro users, I'm afraid you have to fork the source code, edit related content and compile yourself.
So with this special version of fastboot binary, we can boot the phone to EDL mode directly:
Code:
edl-fastboot.exe reboot-emergency
But wait, why didn't you mention this command when you released bootloader unlock guide?
That's because, if you attempt to use this command under locked bootloader, bootloader will response "Permission denied, auth needed. " and refuse to proceed the command.
I don't know how the authentication is done yet, but it's definitely not something that average developers can access to.
Click to expand...
Click to collapse
Step 4: Use partition manager to dump the partition
If you've came so far when unlocking the bootloader, you have already know the great partition manager.
Still, we assume the COM port number is 8 (COM8).
When the partition list appears, find "boot_b" (or boot_a if the current slot is a), right click on it, choose "Manage Partition Data" and click "Read Data". Then fh_loader binary will dump the boot image to your PC.
For Windows users, it's located at
Code:
%AppData%\Qualcomm\QFIL\COMPORT_8
Where %AppData% is actually C:\Users\your_user_name\AppData\Roaming .
The filename looks like this: ReadData_emmc_Lun0_0x3a000_Len65536_DT_07_09_2019_13_55_54.bin
Now close the partition manager, your phone will exit EDL mode and boot normally.
If you're interested in dumping full eMMC storage, you may want to read this: https://forum.xda-developers.com/android/general/guide-how-to-dump-write-storage-t3949588
Step 5: Install Magisk Manager and patch the boot image you dumped
I think everyone who reading this guide knows where to download Magisk Manager.
Copy the boot image you dumped with QFIL to Download directory in your phone's internal storage, and rename it to boot.img for your convenience.
In case you don't know how to patch, read this guide: https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
Step 6: Flash patched boot image and reinstall Magisk for ensurance
After you pulled patched boot image from your phone, reboot your phone to fastboot mode, then execute these commands:
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Note, temporarily boot method introduced back for old A/B devices like Nokia 7 Plus no longer works on Nokia 3.2 / 4.2 - it will boot your phone to Qualcomm 900E mode.
Once your phone booted to normal OS, open Magisk Manager, and reinstall Magisk and required runtime to make the root much more effective.
You may want to read this guide if you want to inherit root along with OTA update: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Extra info about custom rom:
I've tested PHH-Treble GSI on Nokia 4.2 and it made me disappointed.
The vendor compatibility is worse than FIH made Android Phones.
You may want to read this for more details: https://github.com/phhusson/treble_experimentations/wiki/Nokia-4.2
Next preview: Stock firmware reinstallation guide. Note, Nokia 3.2 / 4.2 are not made by FIH, so OST LA no longer works on both devices.
Special thanks:
@topjohnwu for Magisk
Wingtech for leaking prototype units
Reserved
not detected
my pc doesn't detect the phone when its in edl mode. before people start asking I unlocked the bootloader by enabling oem unlock in the phone settings.
I have a TA-1156 (a 3.2 variant) that has a different mainboard layout. For quite a while, I tried in vain to bring it into EDL mode - until I just tried the fastboot command "flash unlock" which worked.
I guess I should have tried that right away as I did have the OEM unlocking option in the developer setup.
Anyway, now I'm unlocked but can't access the partitions with the QFIL partition manager. I suspect the phone expects a different programmer than prog_emmc_firehose_8937_ddr.
I can enter EDL mode easily now with the patched fastboot exe. The correct driver is active and QFIL detects the phone. However, as soon as I follow the instructions by setting the programmer, and then try to start the partition manager, the phone stops responding.
After a while, I get a "sahara" error about no reply from the phone.
I wonder if someone has a stock boot.img of the Nokia 3.2 (build 00EEA) lying around ...
Here is someone else's photo of the mainboard (I just realized that it's actually from hikari_calyx!) but on mine, the right one of the test points you marked in your 3.2 variant does not exist, so I edited it out in the photo:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
JFDee said:
Anyway, now I'm unlocked but can't access the partitions with the QFIL partition manager. I suspect the phone expects a different programmer than prog_emmc_firehose_8937_ddr.
Click to expand...
Click to collapse
My guess was right. Now I'm able to reply to myself with a solution.
I tried a different prog_emmc_firehose_8937_ddr than the one provided by @hikari_calyx in the unlock thread
There is a programmer with the same name in this firmware:
sprout-015B-0-00WW-B01 .rar
It's provided by @bouyhy01 in his rooting thread.
The size of the programmer file is slightly different:
Code:
hikari_calyx: 428,936 bytes
Firmware: 428,944 bytes
Long story short: the different programmer worked in QFIL, so the partition manager worked as well, I got my own boot image, patched, flashed and had root - finally ... Thanks for all the research work, hikari_calyx and bouyhy01 !
Attached is the working programmer file, in case anyone else stumbles upon the same problem. By the way, my phone has the October security patch installed which is currently the latest available.
View attachment prog_emmc_firehose_8937_ddr_from_fw.zip
.
JFDee said:
Here is someone else's photo of the mainboard (I just realized that it's actually from hikari_calyx!) but on mine, the right one of the test points you marked in your 3.2 variant does not exist, so I edited it out in the photo:
View attachment 4867461
Click to expand...
Click to collapse
I guess the only point can be connected to the ground, for example, the RF shield is grounded.
JFDee said:
Attached is the working programmer file, in case anyone else stumbles upon the same problem. By the way, my phone has the October security patch installed which is currently the latest available.
View attachment 4869373
.
Click to expand...
Click to collapse
Thanks for info. Mine Nokia 3.2 is a prototype unit, so I don't know the situation of other versions of Nokia 3.2.
Hello, I have tried this manual for rooting Nokia 4.2 with last security update of 5th of November. After 5 step (flashing patched boot image) my phone try to reboot and then asked for factory reset (Can't load android system - Your data may be corrupt). After making factory reset there were no root at all.
What can i do next ?
PS. It's strange enough when i download boot_b image it was 63.4 Mb snd when i have patched it by Magisk manager - the size od magisk_patched.img became 10.2 Mb
Source: https://unofficialtwrp.com/xiaomi-redmi-9-root-twrp-3-4-1/ The author wrote this: all issues fixed!
Thanks to the developer for the energy and time. Developer: wzsx150.
This is a working unofficial TWRP recovery for Redmi 9 for Miui 11. Tested on android 10, Miui Global 11.0.6 rom.
Miui 12 is work? I do not know. Everyone doesn't know. It probably won't work.
Original file: https://www.mediafire.com/file/auj2wh2lh8lzp47/3.4.2+Redmi+9+CN+EN.rar/file I modified this a bit.
What is required for installation:
Twrp img (blue) (recovery.img): Download
vbmeta_redmi9.img Download
1: Unlock bootloader
2: installed adb & fastboot drivers Download
3: Optional: Mtk usb driver Download
3a: Let the phone battery be charged to more than 50% !!!
(4: Everyone is at their own risk)
(5: Backup all data, recommended. Save idea 1, Save idea 2
6: Turn off the phone
7: Then press the volume down button + power on button to enter fastboot succes fastboot screen
8: Now connect your phone to your computer (windows emits a connection sound)
9: Open one a cmd/command line, where you downloaded the files cmd
10: Issue the two commands one after the other
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta_redmi9.img
11: You ready. Restart the phone in recovery mode
fastboot reboot recovery
12: If you did everything right, this picture will welcome you
12.a: If recovery asks you for a security pattern, enter what you use on your phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
12: If you messed up something, don't worry. Someone here will help. (It can usually be restored with Adb or fastboot, which is broken)
13: A few pictures of the program
14: Four colors are available: blue, red, brown, purple.
Blue TWRP Recovery: Download
Red TWRP Recovery: Download
Braun TWRP Recovery: Download
Purple TWRP Recovery: Download
For now, only Chinese and English language are available! The other languages are being prepared. Soon. As there will be time for it.
It doesn't hurt to have these:
Qualcomm HS-USB QDLoader 9008 Driver 64-bit [Windows] Qualcomm driver
MediaTek MT65xx Preloader VCOM USB Driver [32-bit & 64-bit] Mediatek Vcom driver
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 Adb & fastboot drivers
MTK usb driver Download
SDK Platform tools Download
Google usb driver Download
Thanks for watching. If you liked my job, you can invite me for a beer.
Paypal: [email protected]
Crypto: 3FJuZGaw98oefj45AiypytaJzyATuRn7dE
Reserved
I saw this at telegram yesterday
Is this updated version?
SunuWijaya said:
I saw this at telegram yesterday
Is this updated version?
Click to expand...
Click to collapse
Where did you see that? (I don't understand) Two versions of this have been made. This is the second.
short question,what have you modified and how did you testet which things,we have no custom rom,what about backup and restore,did you testet,what about flashing zips in general and are all partitions rw?Thanx!!!!
-CALIBAN666- said:
short question,what have you modified and how did you testet which things,we have no custom rom,what about backup and restore,did you testet,what about flashing zips in general and are all partitions rw?Thanx!!!!
Click to expand...
Click to collapse
Hello. Well ... there weren't many tests available yet.
What I modified:
1: Skins / colors
2: Spelling mistakes
3: Syntax errors 2-3 pieces
What I was able to test in recovery:
1: Install zip / img: works
2: Backup and restore partition / data: works
3: Mount partitions: works
4: Wipe / advanced wipe: works
5: Reboot "all: works
6: Terminal: works
7: ADB Sideload: works
8: File manager: works
9: Settings "all works, except multilanguage.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Other. For everyone. It also became a fifth skin. Orange / black. Download
------------------------------------------------------------------------------------------------------------------------------------------------------------------------It's different again. For everyone. I noticed a mistake yet. I haven’t used recovery in a long time, so I didn’t notice the error. After a while, twrp recovery disappears. And the original recovery will be again. I don't understand why .... If you twrp recovery in flash fastboot mode again, you have twrp again. For a while.
Can dis twrp flash kernel?
Meggyi said:
Hello. Well ... there weren't many tests available yet.
What I modified:
1: Skins / colors
2: Spelling mistakes
3: Syntax errors 2-3 pieces
What I was able to test in recovery:
1: Install zip / img: works
2: Backup and restore partition / data: works
3: Mount partitions: works
4: Wipe / advanced wipe: works
5: Reboot "all: works
6: Terminal: works
7: ADB Sideload: works
8: File manager: works
9: Settings "all works, except multilanguage.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Other. For everyone. It also became a fifth skin. Orange / black. Download
View attachment 5164259
------------------------------------------------------------------------------------------------------------------------------------------------------------------------It's different again. For everyone. I noticed a mistake yet. I haven’t used recovery in a long time, so I didn’t notice the error. After a while, twrp recovery disappears. And the original recovery will be again. I don't understand why .... If you twrp recovery in flash fastboot mode again, you have twrp again. For a while.
Click to expand...
Click to collapse
Ok,big thanx for info.Cheers!!!
SunuWijaya said:
Can dis twrp flash kernel?
Click to expand...
Click to collapse
Does it have a custom kernel? Modified kernel? Has anyone tried kernel flash? I don't think so. (Zip and img flash, it knows) Do you know of a modified kernel?
Meggyi said:
Does it have a custom kernel? Modified kernel? Has anyone tried kernel flash? I don't think so. (Zip and img flash, it knows) Do you know of a modified kernel?
Click to expand...
Click to collapse
Just try to flash stock kernel
Afaik the issue with the missing twrp recovery is normal and only on miui based rom,on custom roms there is no issue like that.Most Xiaomi/Redmi devices do that.
Meggyi said:
Does it have a custom kernel? Modified kernel? Has anyone tried kernel flash? I don't think so. (Zip and img flash, it knows) Do you know of a modified kernel?
Click to expand...
Click to collapse
Yes it is have custom kernel named Minati-Xenodrome
How to use twrp to flash GSI ?
-CALIBAN666- said:
Afaik the issue with the missing twrp recovery is normal and only on miui based rom,on custom roms there is no issue like that.Most Xiaomi/Redmi devices do that.
Click to expand...
Click to collapse
Yeah, I get it. I didn’t have many phones that miui had. That makes sense. Stupid miui
Good job....I flash custom kernal...and it successful...but can this twrp able to go fastbootd as you mentioned and flash gsi like stock recovery?
Have you flashed a rom?
The solution for the issue that twrp is gone after some times is to flash the no-verity-opt-encrypt file for the device directly after flash of recovery,after this twrp is permanent,for the file check source link in first post.Cheers!!!!
Thank you very much, but my Redmi 9 China version cannot boot after flashing into twrp.
On Redmi 9 China version, I sorted out this version to be available.It seems that it can only be used for MIUI11
zhihuiyuze channel
论坛附件，Redmi9 twrp且可以在中国版使用
t.me
Google Drive Education Edition cannot share files (so use Telegram
There is another problem. It seems that if I use your modified version, /cust fails.
What we can do with this TWRP on lancelot?
I have the Redmi 9 (lancelot) with MIUI 11 installed. My bootloader is unlocked, I've the adb & fastboot drivers installed. I would really like to install that TWRP. While I'm flashing both files, cmd gives no errors, everything is fine. But at the end, I can not boot into recovery with "fastboot reboot recovery" from the cmd, it gives me an error. If I leave fastboot mode and try to enter TWRP manually by holding the volume and power key, it doesn't work. My device will get stuck inside a bootloop.
I'm able to fix the bootloop with disabling DAA & SLA protection in the MTK mode and flashing back the stock firmware with SP Flashtool. I tried it 3 times, every time the same issue and having to flash back the stock firmware. Do you have any tips to fix that? Or is there another or updated version I could try?
Edit: Nvm, got it working
Solution below.
For those with the same device, I was able to successfully root + pass safetynet, without TWRP or custom recovery. Since this device isn't yet on the forums I thought I should share my findings.
At the time of rooting, I was currently updated to the newest version available (10) and did this through the regular OTA updates.
Preparations
1. Download Magisk Manager Beta from https://magiskmanager.com/magisk-beta/
2. Download the stock firmware for your tablet from https://mirrors.lolinet.com/firmware/lenovo/Yoga_Smart_Tab/YT-X705F/
3. Download kdrag0n's SafetyNet Fix from: https://github.com/kdrag0n/safetynet-fix/releases
Edit: looks like I missed a step, thanks for the feedback! Point 4 has been corrected to include instructions on how to unlock the bootloader specifically.
4. Unlock your bootloader, instructions on how to enable USB debugging which is needed, can be found here: https://www.shizhub.com/2018/12/how-to-enable-disable-usb-debugging.html, from there you can open your command prompt, navigate to the directory where you have your fastboot and ADB stored, and type "adb devices" to confirm your device is found (a serial number will display on success) - next type "adb reboot bootloader" to force your tablet to restart into it, finally type "fastboot oem unlock-go" to unlock the bootloader. This voids your warranty.
-- end of edit.
5. Enable USB debugging through developer options (go to settings->about->find build # and tap a handful of times until it says you are a developer.
6. Plug the tablet into your PC, and set the default option to Charge only, or go to file transfer mode and enable USB debugging over file transfer.
Steps
1. Unzip the firmware, there should be a folder called Maincode, in it contains "boot.img" as well as adb/fastboot.
2. Copy the boot.img and Magisk apk to the tablet.
3. Install Magisk
4. Tap on "Install" or "Update" beside Magisk in the app and follow the prompts.
5. You will be asked to select a file, select the boot.img you copied earlier.
6. This will generate a file (it will tell you the path) of a patched boot image.
7. Reboot, and copy the patched boot image to the "Maincode" folder from the tablet.
8. In command prompt, type adb devices and make sure your serial number is shown. If not, review the preparations.
9. Type adb reboot bootloader and you'll see a cute little Tux (penguin)
10. Type fastboot devices and ensure your device is shown, if not then it could be bad drivers on your PC or a crappy USB cable. Check device manager on your computer and make sure you see Lenovo ADB. You may have to force it to install it, or you may see a yellow exclaimation mark - right click on the device and force it to install the Lenovo Bootloader option.
11. Next, in the "Maincode" folder where you put the patched image, rename the old "boot.img" to "stock_boot.img" and the patched version to "boot.img"
12. Back in the command prompt, type fastboot flash boot boot.img
13. Reboot by typing fastboot reboot.
Magisk should now be installed, and your tablet should be rooted. Next, you'll want to go into Magisk and do the following:
Steps:
1. Click on the modules button (bottom of the screen, far right option) and at the top you're given an option to install from storage.
2. Navigate to the SafetyNet Fix zip file and select it, then proceed.
3. You will be given the option to reboot - do this. The first time it may go into recovery, but rebooting brings you back to the home screen.
4. Go back to Magisk, click on the gear at the top right - there is an option to hide Magisk from the system, do this and name it whatever you'd like (just not Magisk) - wait a moment, as the app will restart after it installs.
You can check to make sure you pass SafetyNet in the Magisk (now renamed) app, and root status by downloading one of the countless root checking apps on Google Play Store.
Could you let me know a clear way to unlock the bootloader on the Yoga Tab YT-X705F? The instructions you've provided don't point to anything helpful beyond activating USB Debugging.
"4. Unlock your bootloader, instructions: https://www.shizhub.com/2018/12/how-to-enable-disable-usb-debugging.html - do not proceed beyond where it starts talking about TWRP."
I'm looking to root my tablet but cannot as trying to find info on unlocking the bootloader is proving difficult.
Thanks in advance
Bobmat34 said:
Could you let me know a clear way to unlock the bootloader on the Yoga Tab YT-X705F? The instructions you've provided don't point to anything helpful beyond activating USB Debugging.
"4. Unlock your bootloader, instructions: https://www.shizhub.com/2018/12/how-to-enable-disable-usb-debugging.html - do not proceed beyond where it starts talking about TWRP."
I'm looking to root my tablet but cannot as trying to find info on unlocking the bootloader is proving difficult.
Thanks in advance
Click to expand...
Click to collapse
Thanks for pointing that out! - I've updated my notes above, but if your familiar with fastboot the command is simply "fastboot oem unlock-go", no unlock code needed for these guys. It will wipe your device and void your warranty though, in case you're not already aware.
Cheers!
Thanks for this rooting guide! I was able to root my YT-X705F
Here some comments/hints:
- At first make sure your downloading the right stock firmware. I've tried a different one which results into a boot loop. One way to find out the right version is to start into the recovery mode. In the header you will find the right version. In my case it was YT-X705F_S001130_210508_ROW
- Make sure you have actually unlocked the boot loader. "fastboot flash x y.img" worked, so I didn't recognized that the boot loader was not unlocked. This was reason for "fastboot boot y.img" shows errors "FAILED (status read failed (Too many links))".
- The extracted stock firmware have no "Mainfolder". All files, including boot.img and recovery.img, contained in the root directory of the ZIP file.
- After installing Magisk app (v23.0) it shows me: Installed: N/A, Ramdisk: No, A/B: No, SAR: Yes. According to this Magisk installation guide you have to patch the recovery image instead of the boot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Patching the recovery image was fine with Magisk. No errors was shown. Please note I used the recovery.img
After this I was able to boot the patched image without flashing it:
After "fastboot boot patched_recovery.img" nothing happens. The tablet keeps showing me the Linux Tux image. I have to disconnect the USB cable and then I booted into system.
*Upd. never mind, I download the official rom file from lenovo\
Crap. I patched the boot image with Magisk, and by the time I flashed it - the system got updated from S001133 to S001135, and I'm getting a bootloop. Can someone maybe upload original boot img from S001135?
Or what else can I do? the update isn't on the mirror server yet https://mirrors.lolinet.com/firmware/lenovo/Yoga_Smart_Tab/YT-X705F/
Rooting was successful! Thanks for the guide. Since I cannot find any section in the forum for the YT-x705 tablet, I thought I can have a follow up question in here. The reason I rooted was because alexa app keeps getting removed after each reboot. I rooted as I wanted to convert it into a system app.
So far, I've been unsuccessful . I have tried with the systemizer module and titanium backup. Anyone have any idea how we can retain alexa app after a reboot? Interestingly enough, titanium backup shows alexa as frozen after I install alexa from playstore, despite it appearing in my app launcher. I am unable to unfreeze it. Alexa is then removed after I reboot.
Quick question: What do i do if i don't have a "MainCode" folder, on the tablet or in the extracted folder.
or is that just the folder with the maincode, in it?
Thanks, looks like a good guide!
Jim
you're just going into the zip file from step 2 where the boot.img file is. I just followed all these instructions and got my yoga rooted.
ugh...I don't have a device that I can root for a couple of years... and it feels like I'm a complete noob, now!
when i try to flash the boot image I'm getting: FAILED (remote: Partition flashing is not allowed)
When i run fastboot oem device-info i get this:
PS C:\Users\Jim\Downloads\YT-X705F_S001135_210909_ROW (1)> ./fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.007s]
Finished. Total time: 0.010s
So i don't think i am unlocked. even after following the steps. I've got Developer options, Debugging is obviously working, OEM Unlocking is toggled on.
I feel like on my phones we had to run an adb or fastboot command, and then the device would reboot and reset it and it would then be unlocked.
Am i missing something?
Thanks again!!
Jim
p.s. and once i get it working, what roms can i flash? any of the "yoga" roms? or do i need to look at something specific like the 3 or 4?
answered my own question!
i had to run: fastboot oem unlock-go
the device rebooted and reset
now i get this:
PS C:\Users\Jim\Downloads\YT-X705F_S001135_210909_ROW (1)> ./fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.007s]
Now on to the next step!
So anyone know what ROMs i should use and how best to install them, i don't think we have a working TWRP, do we?
... after crash of my booting Android 10 system last stock rom my yt-x705F 210909 can't be rooted anymore!
i use some app and this app ask for busybox .... so crash !!!
i reset tablet by system recovery .
"wipe data/ factory reset"
after restart my tablet is working again.
Bootloader is still open
also develover mode is working USB Debugging etc.
but no rooting alowed by patching root img .. see next
now i try to install stock rom NEW but some error
"apply update from external storage " get error
same is from "Apply update from ADB" abd sideload file.img
are this zip files from this server corrupt? mirros lolinet ?
i use magisk 25.2 i try all option with hook on recovery also vbmeta
patch both boot.img and recovery.img
after patch one of these img device runs into the bootloader , tux start up.
if i patch stock boot.img device booting normal but NO ROOT
also twrp can't no flash only option "fastboot boot twrp.img"
"fastboot boot flash recovery twrp.img" not working
if i use twrp by "fastboot boot twrp.img" zip stockrom makes also error
someone knows about RESCUE and SMART ASSISTENT" LMSA Tool ?
any suggestion
how is this working ?
go on settings > about tablet > push a view times on Hardware-Version
NEW Firmware update YT_X705F_S001137_220721_ROW for yoga
what's new?
looserintheend said:
NEW Firmware update YT_X705F_S001137_220721_ROW for yoga
what's new?
Click to expand...
Click to collapse
Know where can I find this firmware?