Related
Hello Guys!
Seems a huge discussion about android platform but i cannot see my related issue. i am presenting a clear note about all of my issue.
My phone details is
MTK 6737
Name: Symphony
Model: R100
RAM: 3GB
First i have flash my phone using SP Flash tools (format all+download). after that IMEI number not showing and not found anywhere. i have checked huge tutorial, youtube video, forum thread etc a lot but not correct solution. everybody says i must have ROOT ACCESS in order to adjust my IMEI number again.
I got two problem
1. Nvram error (wifi issue)
2. Invalid imei issue
I spend over 14 hours like a whole days with computer & internet to find correct solution. i have downloaded huge driver like ADB driver, CDC driver, MTK USB driver, SN Writer tools AND many more.
Maximum people says "MTK Engineer Mode" then i had opened that, unfortunately, CDC information not available in menu list. more than 10 root app used to get ROOT access but all are failed. i have followed more than 50 tutorial to modify scatter.txt file with navram.bin etc but failed.
Now, i am looking for help from expertise who know about this matter.
Thank you very much.
TWRP 331 Porting Thread for New UMIDIGI Power 4G
New thread for the new model UMIDIGI Power 4G Helio P35 Octa core Mtk 6765
Umidigi Power 4G MT6765 Octa Core 4G 4GB 64GB Android 9 Smartphone 6,3 inches
Everybody are Welcome!:good:
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE
New twrp 331-test 1 for this device is builded!
Now need period of tests...
http://www.mediafire.com/file/cnqw8d2qkjqtp6k/Twrp_331_test1_Umi_Power.rar/file
reserved 1
Reserved 2
TWRP Not Working for Me
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
SeekerofLight.iz said:
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
I confirm the first part of this, same issue here... i'd like to flash a twrp for gsi purposes, but for now no luck
SeekerofLight.iz said:
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
Can you write how you got the root of the law? Instructions for inexperienced users.
Thank you in advance.
Root UMIDIGI Power with Magisk
mr A V said:
Can you write how you got the root of the law? Instructions for inexperienced users.
Thank you in advance.
Click to expand...
Click to collapse
Sure thing! Here's a Magisk root guide for anyone just getting started that I wrote up just now. (All mentioned files are provided in the zip.)
Step 0 - Download the Attached Zip File Below
Google Drive Mirror
Mediafire Mirror
MEGA Mirror
Step 1 - Drivers
Install the MediaTek drivers by running "DriverInstaller.exe". These are the drivers that worked for me. But if you have issues with them in Step 5, Google "Mediatek MT65xx USB VCOM Drivers" (or some variation of that) and try some others you can find.
-----------------------------------
Step 2 - Install ADB Interface
Install the Android SDK (ADB Interface). To do this drop the platform-tools folder (from the Step 2 folder) into your C:\ directory. Press the windows start button and search for "Environment Variables" and click on "Edit environment variables" from the results. Under SYSTEM VARIABLES on the bottom (not User variables above it) click on the "Path" variable, and click edit. In the new window that appears, hit "Browse..." and click on the "platform-tools" folder that you placed in your C:\ directory.
All this does is allows you to easily input adb commands into command prompt with no issues. This will be used to verify that the device is appearing properly and issue commands in case of emergency.
{
"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 3 - Install Magisk
Copy the Magisk.apk to your phone and install it.
(This is where you can then copy the boot.img to your device and patch it via the Magisk app to create the "magisk_patched_boot.img" file, however I have included the already patched file in Step 6 for the UMIDIGI Power so you don't need to.)
Also, this is the Magisk v19.3 Beta, but you can install another version.
-----------------------------------
Step 4 - OEM Unlocking/USB Debugging Mode
On your phone, go to Settings >> System >> Developer Options. (If you haven't activated Developer Options yet, do that by going to About Phone >> Build number, and tap it a bunch of times, but I'm sure you already know this lol)
In Developer Options, turn on "OEM Unlocking" to unlock the bootloader, and USB Debugging.
-----------------------------------
Step 5 - Verify That Your Phone is Detected with ADB
Connect your phone to your PC. Make sure you click "Allow USB debugging" on your phone. Then open up Command Prompt. (Protip: Type "color a" and press Enter if you want to feel like a REAL HACKERMAN.) Now, type in "adb devices" and verify that your phone is detected by your computer. If it's detected, then that's perfect you can move on to Step 6. If not, then uh... you may have to try and find some other MediaTek drivers mentioned in Step 1.
-----------------------------------
Step 6 - Set up SP Flash Tool
Open up SP Flash Tool on your computer by running "flash_tool.exe" in the SP Flash Tool Folder. (If at any time it shows a "Processing" window for some reason, just close and reopen the program if it doesn't go away on its own.)
On the first line choose "MTK_AllInOne_DA.bin". And the third line "Authentication File" can be left blank.
On the second line where it shows "Scatter-loading File", hit "choose" and find the "MT6765_Android_scatter.txt" file in the Step 6 folder. It'll load up and show a bunch of green/white rows in the space below.
Now this looked intimidating to me at first, but it's actually quite simple. As far as I understand (and I could be wrong but), the scatter file just tells the program where to place certain files, like a map for the program to follow. The scatter file I provided is for the UMIDIGI Power. The only thing we'll worry about for now is the boot.img file (but in the future, this is where you could also install a TWRP recovery once we get one that is confirmed to work.)
So in the white/green list, scroll down to where it says "boot" in the "Name" column, and click on the blank area in the "Location" column. It will bring up a window where you can browse to the "magisk_patched_boot.img" that I provided.
-----------------------------------
Step 7 - The Big Huzzah (Rooting)
Power off your phone and make sure it's UNPLUGGED. On SP Flash Tool, click "Download". This prepares the program to begin flashing your phone as soon as it is connected. Grab your phone with one hand, and with your other hand plug in the USB cable (if you only have one hand, use your mouth I guess). Your screen should not turn on at all throughout this process, but if it's successful, you should see that the program begins to flash your device after a second or two. Now just wait until it reaches 100% and says "Download Ok" with a green checkmark. And you're pretty much done!
You can then boot up your phone and check the Magisk app, as well as download a root checker from the Play Store to confirm that your phone has root access! Have fun!
Thank you, far-away friend from me, that you are such a sympathetic person! Thank you for writing everything so quickly and in detail. As soon as I receive my phone, I will definitely try to do everything as you wrote.
Tell me, do you plan to install any firmware on this device? For example, Miui. Or are you satisfied with the stock?
mr A V said:
Thank you, far-away friend from me, that you are such a sympathetic person! Thank you for writing everything so quickly and in detail. As soon as I receive my phone, I will definitely try to do everything as you wrote.
Tell me, do you plan to install any firmware on this device? For example, Miui. Or are you satisfied with the stock?
Click to expand...
Click to collapse
No problem! Unfortunately I don't see many custom ROMs coming to this phone, considering it's not a very popular device. I'd guess our best bet is to hope that the UMIDIGI F1 gets some support, and that anything on there can hopefully be ported over to this phone, but even that device isn't very popular either. For me though, that's not a huge issue because I'm actually quite satisfied with the stock firmware it has on board. It's basically stock Android Pie, and I've been able to add all the extra goodies I want into the phone through Magisk Manager and EdXposed with very minor issues. Most notably Viper4Android to fix the slightly tinny speakers and pump up the overall headphone experience too, and Gravity Box for some extra minor software customization.
Overall, I'd say the biggest downside to this device is the limited camera capabilities, and its somewhat limited performance for heavier tasks like 3D games / game streaming. But other than that, this feels like a very premium device. :good:
I thought about the fact that it is you who can transfer other firmware to this device. As a developer, let's say.
On the F1 already installing the firmware AOSP, LOS and other projects. But need to flash these firmware through TVRP recovery. For our device, there is no such recovery yet.
I have little understanding of the intricacies of the android. Sorry if my questions seem silly.
If we take the firmware for F1, for example AOSP, will it have to be somehow changed for our UD Power? Or can just take the archive, as it is, and flash it?
The processor of our smartphone is not very strong, so it is not for games. It is also not clear what RAM is installed. It looks like the manufacturer has installed a cheap part. Put single-channel LDDR 3. So he made a low price. At the expense of device performance.
mr A V said:
I thought about the fact that it is you who can transfer other firmware to this device. As a developer, let's say.
On the F1 already installing the firmware AOSP, LOS and other projects. But need to flash these firmware through TVRP recovery. For our device, there is no such recovery yet.
I have little understanding of the intricacies of the android. Sorry if my questions seem silly.
If we take the firmware for F1, for example AOSP, will it have to be somehow changed for our UD Power? Or can just take the archive, as it is, and flash it?
The processor of our smartphone is not very strong, so it is not for games. It is also not clear what RAM is installed. It looks like the manufacturer has installed a cheap part. Put single-channel LDDR 3. So he made a low price. At the expense of device performance.
Click to expand...
Click to collapse
I definitely consider myself to be a major noob with the more advanced Android development stuff. I only know enough to find my way around the internet and flash compatible software, haha. I've never looked into creating ports myself, but it's certainly something I think might be worth learning, especially with the limited device support on these phones.
And yeah, in terms of performance I don't expect much out of a phone at this price point, but for all the essentials - music, 1080p YouTube, web browsing, and mid to light gaming, it's surprisingly great considering the price. I haven't had any issues with the memory as of yet, so I wouldn't be too concerned, although you're definitely right in that they probably source some pretty cheap parts for these kind of phones.
SeekerofLight.iz said:
Sure thing! Here's a Magisk root guide for anyone just getting started that I wrote up just now. (All mentioned files are provided in the zip.)
"stubbed guide"
Click to expand...
Click to collapse
It works like a charm, thank you! by the way, were you able to boot that twrp or still nothing? and if you made it, were you able to flash a gsi over that too? i'm unable even to boot that twrp
---------- Post added at 09:30 AM ---------- Previous post was at 09:29 AM ----------
ghost45 said:
TWRP 331 Porting Thread for New UMIDIGI Power 4G
New thread for the new model UMIDIGI Power 4G Helio P35 Octa core Mtk 6765
Umidigi Power 4G MT6765 Octa Core 4G 4GB 64GB Android 9 Smartphone 6,3 inches
Everybody are Welcome!:good:
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE
Click to expand...
Click to collapse
Can i ask you a guide on how were you able to boot it? i'm only getting a bootloop after flashing that from SPFlash
I will build one other version of recovery soon...
mg95tux said:
It works like a charm, thank you! by the way, were you able to boot that twrp or still nothing? and if you made it, were you able to flash a gsi over that too? i'm unable even to boot that twrp
Click to expand...
Click to collapse
Glad to hear it worked for you!
Still nothing. Unfortunately I haven't had any luck with booting into TWRP since I last tried it. Hoping ghost45 will be able to help us out with that when he gets the chance.
Bootloop - Secureboot
Nevermind, bootloader locked.
just type on CMD:
adb reboot bootloader
then
fastboot flashing unlock
Andre_Filho said:
Nevermind, bootloader locked.
just type on CMD:
adb reboot bootloader
then
fastboot flashing unlock
Click to expand...
Click to collapse
remember to allow oem unlock from developer settings in stock rom, otherwise it will fail!
SeekerofLight.iz said:
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
How do you manage to work Viper.
Cause i'm having some problems, tested all versions and my Driver always stays on "Active: NO Format: Unsuported.... Abnormal"
BusyBox also don't seens to work.
:/
Some help?
Andre_Filho said:
How do you manage to work Viper.
Cause i'm having some problems, tested all versions and my Driver always stays on "Active: NO Format: Unsuported.... Abnormal"
BusyBox also don't seens to work.
:/
Some help?
Click to expand...
Click to collapse
The trick to getting Viper4Android to work is to make sure you have SELinux set to "PERMISSIVE" rather than "ENFORCING" on your phone. Here's a handy little app designed to automatically set it to permissive on boot!
https://forum.xda-developers.com/devdb/project/?id=1561#downloads
And for BusyBox, I was having issues too at first because I think with systemless root, BusyBox can only be installed in /sbin, which gets wiped after each boot. So I searched for "BusyBox" in the Magisk app and found a module called "BusyBox for Android NDK" which has worked perfectly for me.
One thing to note...
Sometimes SELinux doesn't always get changed automatically everytime you boot up. It's pretty consistent, but every once in awhile you may need to manually set it to permissive mode again if things don't seem to be working. But it's literally just pressing a single button, so not a big deal.
The other thing is with Viper itself- At times when I launch the app, the driver status says "abnormal" even after I've toggled SELinux to permissive. If you go into settings and toggle "compatibility mode" or "attach audio effects" on and then off that seems to refresh the driver status. Not sure why, but it works.
Let me know if you have any issues.
TWRP for UMIDIGI POWER
I ask for help in creating TWRP for UMIDIGI POWER firmaware ROM v1.5
Please make for this model TWRP
I am very grateful to you - I unlocked the phone and got the rights Root rights.
It remains only to create a TWRP for UMIDIGI POWER
At this forum, competent specialists and for other models everything is already done.
Maybe there is a website where you can make an order to create a TWRP?
Unfortunately, I do not know English and I do not know how to apply.
I would be very grateful and ready to test your work.
Introduction
THIS METHOD IS NOT FREE. I HAVE NO IDEA HOW TO DO THIS FOR FREE, EXCEPT MAYBE WITH THIS : https://forum.dc-unlocker.com/forum/modems-and-phones/huawei/162196-free-hcu-license-offer
Oh my god. I just come out of 3 days of trying to get this to work, non-stop. I feel the need to write this guide so people in the exact same configuration as me won't have to go through what I did.
Yes there are many tutorials about unbricking your Honor 9, but few are very detailed, and I couldn't make them to work for my european STF-L09. Plus, very few of them have a solution for updating to the very latest version (9.1.0 as the time of writing). So here we go.
The device I did this with, and the situation I was in.
There are so many variants of the Honor 9, and I've tried tutorials that weren't the same model as me, they just wouldn't work.
Honor 9 STF-L09, Europe version, Kirin960.
Previous installed ROM before brick was Oreo (the Pie update I tried to make bricked the phone), but I think you can do that on any previous version.
After the brick, I had a completely dead Honor 9 : no reaction at all, whether I plugged it in or tried any buttons combination.
What you need
- The correct Drivers
- A HCU Client Timed License, which is 19 EUR for 72h, and is going to give you access to the main software we need, DC-Phoenix.
- The correct .dgtks Repair File
- The correct ROM file to flash
- HiSuite
- Tools to open the back of your phone
- A metal object to connect the testpoints (anything will do : tweezers, copper cable, paperclip, sim-tool...)
- Read these two tutorials from www.dc-unlocker.com :
https://www.dc-unlocker.com/dc-phoenix-flash-repair-tutorial
https://www.dc-unlocker.com/flash-bricked-huawei-phones-in-huawei-1-mode
Step 1 - Connect the testpoints
Then open the back of your phone to reveal the testpoints that you can see on the image below (thanks to the user 4r44444 for the picture).
Then, open the Device Manager on Windows, and reveal the COM and LPT Ports (so you can see if you failed at connecting the testpoints or not).
You don't need to connect the two testpoints shown in the picture : you only need to connect the bottom one with anything else that's metal inside the phone.
It will take you some trial and error but eventually, your Device Manager should refresh and show you an unknown device called "SER".
Step 2 - Install the drivers
First, install the latest version of HiSuite to get the basic drivers. Make sure to close it completely (taskbar) and disable the fact that it opens itself when you plug your phone, or it might screw things up.
Then, install the two drivers that are on both dc-unlocker.com tutorials I've linked above.
https://files.dc-unlocker.com/share.html?v=share/984CE114852148B5B9A9CDD918BEC235
https://files.dc-unlocker.com/share.html?v=share/18B15B9D02C945A79B1967234CECB423
The first one "Huawei_Android_phone_drivers.rar" was not useful for me, but the second one, "Huawei drivers testpoint.rar", is to make your COM port recognizable instead of this unknown "SER" in device manager.
In Device Manager, right click on "SER", "Update driver", and locate the extracted folder on your computer.
This is all you need I think, but I installed so many random drivers (which I would not recommend) that I'm not even sure anymore.
Step 3 - Repair the phone with DC-Phoenix
Following "Method 3" from this link, but with some differences : https://www.dc-unlocker.com/dc-phoenix-flash-repair-tutorial
As I said, this method is not free. You can buy credits to make DC-Phoenix work for 72 hours (you need 15 of them for that I think), but since we need HCU, you're better off buying a timed license which gives access to DC-Phoenix.
Open DC-Phoenix, and click on the "Download files" button on top. There, search for the file "STF-Full-Repair-NV-included-Board-A051-7.0.0_r1.dgtks" and download it, it's the Repair File.
https://get-file.org/search#q|STF-Full-Repair-NV-included-Board-A051-7.0.0_r1|1
With your phone connected via testpoints (it has to appear in the Device Manager in the COM Ports, and I recommend changing the COM Port to 1 (right click, Port settings, advanced,...)), go to the "Update OEMINFO" tab, and check "Use BOOTLOADER". There, choose "Kirin960_T2_A7.0_V4" (maybe it's a different one for you, but for me only this one worked).
Then check "Update OEMINFO and unlock Huawei ID", and choose "STF-L09". Click Update, and this should run without errors. If it doesn't recognize your device, that means that it's not turned off and connected via testpoints.
Once that is done, your device may show a sign of life by booting into fastboot mode (or sometimes not). Anyway, you can go directly to the "Update Firmware" tab, and in the "Update file" field, choose the file "STF-Full-Repair-NV-included-Board-A051-7.0.0_r1", check "Rescue Revovery" and "Old slow algo", and click "Update".
After completion, your phone should be able to boot (after a very long press) into a chinese test ROM.
Step 4 - Repair the phone infos with DCU
Follow this tutorial : http://hcu-client.com/huawei-phone-repair-as-empty-board/
Don't forget to change your phone to Manufactured mode (as explained) so you can read your phone info.
In the Step 4, they let you choose between Repair UMTS or CDMA tab, I chose CDMA because I think the phone has a MEID.
Then, when they tell you that you just have to click on "Repair as empty board" to make everything fill in automatically, for me this was complete bs : only my IMEIs were added.
So what you have to do is fill your original SN, WiFi and BT MAC adresses, and so on. But since your phone is bricked and you probably dumped the box that states the SN, you're outta luck like me. It seems like it's illegal to change a MAC or SN number, so I can't recommend it, but I personally just chose random numbers (that have the same number of digits).
For model I entered "STF-L09", for vendor "hw", and for country "eu". Don't check "Erase restricted ver.", since it's only for Qualcomm CPUs. Click on Repair.
Once this is done, your phone should be resetting, and able to boot in the same ROM as before, except in english.
Step 5 - Upgrade to the latest Android 9.1.0
Normally you'd have to do this step with DC-Phoenix : just flash one of their Full Stock Roms they have on their file database (click Download Files on DC-Phoenix, and search for "STF-L09").
You can try that (don't forget that you have to be in fastboot mode (Vol down + plug USB) to install), but it really didn't work for me, and even if it did, I don't know how you'd update after it, because your phone probably won't receive OTAs.
So the solution I found was this one : https://www.reddit.com/r/Huawei/comments/az4bl7/finally_managed_to_update_my_mate10_pro_to_pie/
First, uninstall your latest version of HiSuite to be able to follow this tutorial and install the old version.
Then, the file I chose in Firmware Finder was this one :
STF-L09 9.0.1.175(C432E2R1P5)
STF-L09C432E2R1P5B175 (9.0.1.175)
STF-L09C432E2R1P5T8B175 (9.0.1.175)
I chose the "full" version, which gave me this link :
http://update.dbankcdn.com/TDS/data/files/p3/s15/G3757/g1699/v260353/f1/full/update.zip
After following this tutorial, your phone should boot normally. You can then installs OTAs to update to 9.1.0. I'd recommend resetting the phone after this last step, to have a clean install.
If it doesn't work for you, you can also try this method : https://www.getdroidtips.com/full-guide-install-stock-firmware-huawei-smartphone/
I'll try to answer as many questions as fast as possible (since the Timed License is quite stressful), so feel free to ask !
Does the HCU Client unblock the network after doing the full repair?
Hello , Is this solution still works for honor 9 ?
I can't find stock rom on official website also.
Hi there,
So After seen many tutorials I wanted to proceed to unlock the bootloader of my Huawei Mediapad T5 , here are the specs
```
Model: AGS2-W09
Build No: AGS2-W09 8.0.0.360(OCEC431)
CPU : Hisilicon Kirin 659
Android Version: 8.0
```
I have downloaded the last build of `potatoNV` along with the SER Drivers ,
I have booted in untrusted driver mode (on Win10) and have installed `usbser.sys` as far as I recall
I proceed opening the Tablet from inside and shorting the "short point" and I get connection with the Computer , I installed the drivers , and tried on `potatoNV` with `Kirin 65x (A)` .
I get to the end of the progress bar , and then I get the problem as there is no confirmation that the process has been performed correctly. The connection dissapears , and If I try to boot on rescue mode and I do `.\fastboot.exe devices` or `fastbook.exe oem device info` it doesnt show no device at all.
Also the `rescue mode` menu says `Phone locked , FRP Unlocked` So I guess I had no luck
Please see the video on the link (note that the 2 takes are not synchronized)
doubt-mediapadt5-bootloaderunlock.mp4
drive.google.com
What I may be possibly doing wrong ? May it be the USB connection (cables or connectors) ? or the drivers I downloaded?
Please any assitance will be appreciated.
Thanks
Maybe I can help you with this. Recently rooted this tab myself. Please give me a reminder tomorrow
Hey there I just saw the message . Please if you can guide me a bit of what I may be doing wrong? Also If there is a way to share the Drivers files that you used that would be great (I'm not sure if it was a matter of drivers or general clumsiness , please If you have a minute to check the video tell me what may be wrong on my "Technique") Thank you!!
freddieventura said:
Hey there I just saw the message . Please if you can guide me a bit of what I may be doing wrong? Also If there is a way to share the Drivers files that you used that would be great (I'm not sure if it was a matter of drivers or general clumsiness , please If you have a minute to check the video tell me what may be wrong on my "Technique") Thank you!!
Click to expand...
Click to collapse
Just saw your responce now (please use reply next time, I will get an notification then ).
The "Kirin 65x (A)" you've used is the correct bootloader. So guess it would have been something going on with the drivers or the procedure.
I recently (about 1 month ago) rooted this tab myself so I think I will have quite recent files for doing so. Maybe I can send them to you if you like. But I should have save the websites where I got them from too. But need to check it up for you then.
{
"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"
}
Did you have used the settings above?
You did had recieved the "New unlock code" message?
I have to go to work now, but I could help you further later this evening if you need further assistance
Rockel said:
Just saw your responce now (please use reply next time, I will get an notification then ).
The "Kirin 65x (A)" you've used is the correct bootloader. So guess it would have been something going on with the drivers or the procedure.
I recently (about 1 month ago) rooted this tab myself so I think I will have quite recent files for doing so. Maybe I can send them to you if you like. But I should have save the websites where I got them from too. But need to check it up for you then.
View attachment 5391207
Did you have used the settings above?
You did had recieved the "New unlock code" message?
I have to go to work now, but I could help you further later this evening if you need further assistance
Click to expand...
Click to collapse
Hi, thanks for assisting me. Yeah well, the version I used of PotatoNV(the last build) just had the option of Disable FBlock so I did that.
Also I tried wth a previous build that was showing both versions as you are showing and it happened the same thing.
My guess are more focused on 2 probable mistakes by my side either:
- When shorting the short point Im not doing it correctly. (not sure if this, as the device gets detected by PotatoNV and initiates the process)
- (Most likely thisone). Wrong drivers, I have downloaded them through a link found in a youtube video, and the video was not specific about this Tablet. Also there were a bunch of drivers within the same file so I installed one that looked like the correct one (but not 100% sure)
Anyways thanks for taking your time really and appreciate a reply but always whenever you find free time obviously. Take it easy today at work
freddieventura said:
Hi, thanks for assisting me. Yeah well, the version I used of PotatoNV(the last build) just had the option of Disable FBlock so I did that.
Also I tried wth a previous build that was showing both versions as you are showing and it happened the same thing.
My guess are more focused on 2 probable mistakes by my side either:
- When shorting the short point Im not doing it correctly. (not sure if this, as the device gets detected by PotatoNV and initiates the process)
- (Most likely thisone). Wrong drivers, I have downloaded them through a link found in a youtube video, and the video was not specific about this Tablet. Also there were a bunch of drivers within the same file so I installed one that looked like the correct one (but not 100% sure)
Anyways thanks for taking your time really and appreciate a reply but always whenever you find free time obviously. Take it easy today at work
Click to expand...
Click to collapse
Not sure, I should get into it again, but I'm not sure of potato is able to start the procesure or finding the divice if not shorted correctly.
Do you have a screenshot of your potato output/ results?
How are you performing the shorting procedure?
I can see if I can look for you for the right drivers tonight.
Rockel said:
Not sure, I should get into it again, but I'm not sure of potato is able to start the procesure or finding the divice if not shorted correctly.
Do you have a screenshot of your potato output/ results?
How are you performing the shorting procedure?
I can see if I can look for you for the right drivers tonight.
Click to expand...
Click to collapse
I hve uploaded the video which shows all the output and how Im shorting the point. The video though is composed by two takes and are not synced in time but that is how I do it.
doubt-mediapadt5-bootloaderunlock.mp4
drive.google.com
Let me know if you can watch it on there. Thanks
freddieventura said:
I hve uploaded the video which shows all the output and how Im shorting the point. The video though is composed by two takes and are not synced in time but that is how I do it.
doubt-mediapadt5-bootloaderunlock.mp4
drive.google.com
Let me know if you can watch it on there. Thanks
Click to expand...
Click to collapse
Oh yes, forgot about the video in the OP...
Seems you're folowing the wrong procedure with the shorting proces.
And seems your potato version is a bit outdated. But don't think this will be much of an issue.
- Your tablet needs to be turned off.
- cable removed from the tab.
- start potato
- then short the circuit (tab turned off).
- keep it shorted and insert the usb cabel (the other end should be in the computer already)
- the tablet starts (i believe in somekind of flash mode. And i believe you should not be able to see the Huawei logo in this procedure).
- after 2 or 3 seconds after booting, release the shorted circuit.
- i believe it should display you now some info about the tab itself in potato when you press start.
P.s. Don't forget to make a screenshot of the results or write down the newly given unlock code. So you can use it afterwards to lock or unlock your bootloader at a later moment, without opening the tab again.
P.s. 2 I just read in your comment that the recordings are not synchronised. So it's possible you were following the correct steps above. Correct me if I'm wrong please
freddieventura said:
I hve uploaded the video which shows all the output and how Im shorting the point. The video though is composed by two takes and are not synced in time but that is how I do it.
doubt-mediapadt5-bootloaderunlock.mp4
drive.google.com
Let me know if you can watch it on there. Thanks
Click to expand...
Click to collapse
I'm home (finally)...
If the steps mentioned above didn't worked out, I would like to ask you to do axactly as I did. Just unlocked my Mediapad T5 just 1 month ago or so, so everything I've used should be recent enough I guess.
First:
- Un-install your potato version.
- Un-install your Mediapad T5 USB drivers.
So we can begin from scratch
Also:
- turn on OEM-unlock and USB-debugmode in developer settings.
I asume you have a decent and working ADB version installed on your PC?
If not, or when you're not sure, uninstall it too.
I was using the Minimal ADB and Fastboot from here:
[TOOL]Minimal ADB and Fastboot [2-9-18]
Introduction ADB and Fastboot are arguably two of the most indispensable tools used when working with Android devices. If you really want to modify, debug, and tweak along with their countless uses in rooting, and other procedures ADB and...
forum.xda-developers.com
Then:
1) Install the Huawei USB drivers from here:
Support area | files.dc-unlocker.com
(this) or (this) are the "official" sites I got this from.
2) Install the latest version of PotatoNV from here:
GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620 - GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
github.com
Open potatoNV and use these settings marked in red:
3) Plug the USB-cable into your PC already, but don't connect the other side to the tablet. And make sure your tablet is turned off.
4) Now short the testingpoint with a shielded part. I just used a thick copper wire and used it between testingpoint and metalshield just next to it. Metal pliers as used in your video should work too ofcourse.
P.S. I see that you also disconnected your screen in the video? It seems that it's verry important not to see a charging icon in the next step, so maybe it's better to connect it again for this step.
5) While still shorting the testingpoint with the shield, connect the USB cable to your tablet and be sure no charging icon pops up (This can be a bit difficult doing on your own. Easiest way is to have someone around te help in this step). After a few secconds when connected (without seeing an charging icon) remove the shorting between testingpoint and shield.
6) Make sure that the Huawei USB COM is selected in PotatoNV (and that the other settings are the same as the screenshot)
7) And pres "Start!"
8) You should get similar results now:
PotatoNV v2.2.1
User manual: https://kutt.it/pnv-en
Verifying images...
Uploading hisi65x_a...
- xloader
- fastboot
Waiting for any device...
Connecting...
Serial number: FQB***************
Board ID: FQB*************
Model: AGS2-W09
Build number: AGS2-W09 8.0.0.360(OCEC431)
FBLOCK state: unlocked
Saved key: 6BN**************
Writing FBLOCK...
Writing WVLOCK...
Writing USRKEY...
Rebooting...
New unlock code: 3BS*************
p.s. In your video it seemed your device got disconnected somehow while uploading. You should not see that "timeout" message here now annymore.
9) Make a screenshot of your results, copy them to a text file or write down at least your "new unlock code"
So you won't have to open your tablet annymore in the future. You can use this newly obtained unlock code now to lock and unlock your tablet without opening again.
10) You should now see a warning screen everytime you reboot the tab. It warns you about that the device can't be trusted annymore because of the unlocked bootloader.
You can also enter Fastboot to check it
Fastboot/ Bootloader mode:
1. Turn off the device by holding the Power key for a few seconds.
2. Connect tablet to PC/laptop using the USB-cable.
3. Hold down Volume-Down.
4. Hold down the Power button until device starts (while still holding Volume-Down and USB connected).
4. Tablet boots now into Fastboot-mode.
You should see the following screen then (pay attention on the 2 red lines at the bottom):
You can close your tablet now!
Rockel said:
I'm home (finally)...
If the steps mentioned above didn't worked out, I would like to ask you to do axactly as I did. Just unlocked my Mediapad T5 just 1 month ago or so, so everything I've used should be recent enough I guess.
First:
- Un-install your potato version.
- Un-install your Mediapad T5 USB drivers.
So we can begin from scratch
Also:
- turn on OEM-unlock and USB-debugmode in developer settings.
I asume you have a decent and working ADB version installed on your PC?
If not, or when you're not sure, uninstall it too.
I was using the Minimal ADB and Fastboot from here:
[TOOL]Minimal ADB and Fastboot [2-9-18]
Introduction ADB and Fastboot are arguably two of the most indispensable tools used when working with Android devices. If you really want to modify, debug, and tweak along with their countless uses in rooting, and other procedures ADB and...
forum.xda-developers.com
Then:
1) Install the Huawei USB drivers from here:
Support area | files.dc-unlocker.com
(this) or (this) are the "official" sites I got this from.
2) Install the latest version of PotatoNV from here:
GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620 - GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
github.com
Open potatoNV and use these settings marked in red:
View attachment 5391609
3) Plug the USB-cable into your PC already, but don't connect the other side to the tablet. And make sure your tablet is turned off.
4) Now short the testingpoint with a shielded part. I just used a thick copper wire and used it between testingpoint and metalshield just next to it. Metal pliers as used in your video should work too ofcourse.
View attachment 5391623
P.S. I see that you also disconnected your screen in the video? It seems that it's verry important not to see a charging icon in the next step, so maybe it's better to connect it again for this step.
5) While still shorting the testingpoint with the shield, connect the USB cable to your tablet and be sure no charging icon pops up (This can be a bit difficult doing on your own. Easiest way is to have someone around te help in this step). After a few secconds when connected (without seeing an charging icon) remove the shorting between testingpoint and shield.
6) Make sure that the Huawei USB COM is selected in PotatoNV (and that the other settings are the same as the screenshot)
7) And pres "Start!"
8) You should get similar results now:
PotatoNV v2.2.1
User manual: https://kutt.it/pnv-en
Verifying images...
Uploading hisi65x_a...
- xloader
- fastboot
Waiting for any device...
Connecting...
Serial number: FQB***************
Board ID: FQB*************
Model: AGS2-W09
Build number: AGS2-W09 8.0.0.360(OCEC431)
FBLOCK state: unlocked
Saved key: 6BN**************
Writing FBLOCK...
Writing WVLOCK...
Writing USRKEY...
Rebooting...
New unlock code: 3BS*************
p.s. In your video it seemed your device got disconnected somehow while uploading. You should not see that "timeout" message here now annymore.
9) Make a screenshot of your results, copy them to a text file or write down at least your "new unlock code"
So you won't have to open your tablet annymore in the future. You can use this newly obtained unlock code now to lock and unlock your tablet without opening again.
10) You should now see a warning screen everytime you reboot the tab. It warns you about that the device can't be trusted annymore because of the unlocked bootloader.
You can also enter Fastboot to check it
Fastboot/ Bootloader mode:
1. Turn off the device by holding the Power key for a few seconds.
2. Connect tablet to PC/laptop using the USB-cable.
3. Hold down Volume-Down.
4. Hold down the Power button until device starts (while still holding Volume-Down and USB connected).
4. Tablet boots now into Fastboot-mode.
You should see the following screen then (pay attention on the 2 red lines at the bottom):
View attachment 5391639
You can close your tablet now!
Click to expand...
Click to collapse
Thanks very much for your explanation , I will do this when I am back at home and let you know .
Cheers!!
freddieventura said:
Thanks very much for your explanation , I will do this when I am back at home and let you know .
Cheers!!
Click to expand...
Click to collapse
Are you btw sure that the pliers you used in in the video are making a circuit from one point to the other? Maybe worthwile to measure the resistance first?
I just used a thick copper wire and bended it to an easy to use U-shape.
Rockel said:
Are you btw sure that the pliers you used in in the video are making a circuit from one point to the other? Maybe worthwile to measure the resistance first?
I just used a thick copper wire and bended it to an easy to use U-shape.
Click to expand...
Click to collapse
Sorry Rockel I have been very busy this week , I'm gonna try and find a little bit of time to get this done this weekend . Thank you!!
freddieventura said:
Sorry Rockel I have been very busy this week , I'm gonna try and find a little bit of time to get this done this weekend . Thank you!!
Click to expand...
Click to collapse
No problem, take your time. Hope these steps wil solve your problem. Please keep me informed when you have time
Rockel said:
No problem, take your time. Hope these steps wil solve your problem. Please keep me informed when you have time
Click to expand...
Click to collapse
Do angels wear capes? because I haven't seen yours .
Much much much appreciate your help with this, I have just done it perfectly it didn't take me much time to do it.
Whatever I was doing wrong (probably the drivers , probably the shorting point thing not doing it properly) , whatever who cares!!.
I was also a bit not confident to do it that's why it took me time to get into doing it , but you definitely coached me with your messages .
Really thanks very much Rockel . For anything we keep in touch mate
freddieventura said:
Do angels wear capes? because I haven't seen yours .
Much much much appreciate your help with this, I have just done it perfectly it didn't take me much time to do it.
Whatever I was doing wrong (probably the drivers , probably the shorting point thing not doing it properly) , whatever who cares!!.
I was also a bit not confident to do it that's why it took me time to get into doing it , but you definitely coached me with your messages .
Really thanks very much Rockel . For anything we keep in touch mate
Click to expand...
Click to collapse
Hehehehe, thanks for your nice responce!
So I asume You've managed to root unlock the device now!
It was a pleasure assisting you in this.
If you need anny other information regarding this rooted device, please let me know. I'm not a pro with this. But had to solve a few problems myself. And came there with the help of others aswell.
What is the use of New unlock code?
do anyone have system, boot, cust, recovery, userdata.img with you i want to try with multi-tool to unbrick my tab
The unlock code can be used to unlock bootloader (using something like "adb oem unlock <code>" from PC)
I have saved the OTA folder form huawei system update app just before updating from 8.0.0.320(C432) to 8.0.0.371(C432), it can be found in /data/HwOUC folder after updater finished downloading. This version cannot be found on HuaweiFirmwareFinder site but I have temporary shared then here. Perhaps we could contact the authors to upload this version.
You can later use HuaweiFirmwareExtractor to extract different images from the zip files (no clue why there are 3 of them).
You need to disable "Verify Header checksums" in the "Settings" to open the extracted update.app files from the zips.
Good luck!
denzelcris said:
The unlock code can be used to unlock bootloader (using something like "adb oem unlock <code>" from PC)
I have saved the OTA folder form huawei system update app just before updating from 8.0.0.320(C432) to 8.0.0.371(C432), it can be found in /data/HwOUC folder after updater finished downloading. This version cannot be found on HuaweiFirmwareFinder site but I have temporary shared then here. Perhaps we could contact the authors to upload this version.
You can later use HuaweiFirmwareExtractor to extract different images from the zip files (no clue why there are 3 of them).
You need to disable "Verify Header checksums" in the "Settings" to open the extracted update.app files from the zips.
Good luck!
Click to expand...
Click to collapse
thank you .. but i extract app didnt uderstand which img file to install there no exact name for boot.img, recovery.img, cust.img, can you plz tell me which file equal to those file..
I don't think Huawei has boot.img or recovery.img, they may have a different layout and names (someone correct me if I'm wrong). I know the equivalent of boot.img is ramdisk.img or kernel.img (I flash both when restoring to be sure) and recovery should be recovery_ramdisk.img. The names from HuaweiExtractor should match with the images. Cust.img can be found in the other zip: update_full_AGS2-W09_hw_eu.
There is also this partition layout table which I don't know how it works for Huawei but I know that it may change for different firmwares so it is usefull to have remembered what version you had previously or use a safe tool to flash that also.
Hi Fellows,
First of all, I’m newbie to flashing (or so-called) phones. I want to change my phone for de-googled one. I’m thinking about POCO X3 Pro with LineageOS 18.1.
I’ve been recently reading a lot about changing OS, but I feel completely overwhelmed by how complex knowledge it is. Even on the forum there is so much info, so much specific vocabulary/acronyms
Can you advise me, how to start?
Or maybe different way... do you know any reliable service/somebody in the UK, who could help? I've already checked services in my town - no one does software modifications
kamien8 said:
Hi Fellows,
First of all, I’m newbie to flashing (or so-called) phones. I want to change my phone for de-googled one. I’m thinking about POCO X3 Pro with LineageOS 18.1.
I’ve been recently reading a lot about changing OS, but I feel completely overwhelmed by how complex knowledge it is. Even on the forum there is so much info, so much specific vocabulary/acronyms
Can you advise me, how to start?
Or maybe different way... do you know any reliable service/somebody in the UK, who could help? I've already checked services in my town - no one does software modifications
Click to expand...
Click to collapse
You don´t need to pay someone else for that, you can do it by your own.
I will give you the topics in order, one by one, and just search for the info till understand what you are want to achieve.
1-Unlocking bootloader.
2-Flashing a custom recovery.
3-Rooting (optional)
4-installing a custom ROM (like LineageOS)
Search for these topics in your own forum, read carefully and apply them when you are sure what you are doing.
Copied these from my old post in other forums, I updated a little but still might be a little outdated
Spoiler: How to unlock bootloader
Link your poco x3 pro to your MI account
Activate "Find my device" for Mi account
Settings > About Phone > Tab "MIUI version (For POCO)" until developer mode unlocked
Settings > Additional Settings > Developer Options
OEM unlocking - Checked
Mi Unlock status > Add account and device - Do only once, anymore will reset 168 hours unlock counter
Go to https://en.miui.com/unlock/and download the mi unlock software
Latest version to date of this post is https://miuirom.xiaomi.com/rom/u1106245679/5.5.224.55/miflash_unlock-en-5.5.224.55.zip
Prepare for future unlock
Turn off your mobile
Boot into fastboot mode - Volume Down + Power
Run "MiUsbDriver.exe" located in the miflash_unlock_en zip
Connect mobile to PC or laptop
Poco X3 Pro driver should be installed
Run "miflash_unlock.exe" and proceed through the software
If you yet to apply for permission to unlock, you can apply from there (I think, the last I applied was years ago, not sure still a thing now or not)
The software will tell you the countdown which is 168 hours aka 1 week.
Exit fastboot mode on phone by holding the power button.
A week later, time to unlock.
Backup your file, if you have used the phone intensively, unlocking will result in factory reset.
Turn off mobile
Boot into fastboot mode - Volume Down + Power
Run "miflash_unlock.exe"
Connect mobile to PC
Proceed through "miflash_unlock.exe"
Unlocked
Spoiler: How to Flash Custom Recovery
Download google platform tool from https://developer.android.com/studio/releases/platform-tools
Extract the tool
In the tool folder, type "cmd" at "Address bar" to open command prompt to that folder
Press enter after you type "cmd", if it isn't obvious.
Turn off mobile
Boot into fastboot mode - Volume Down + Power
Connect mobile to PC
Go to command prompt window, type "fastboot devices".
Your phone will be shown if detected, otherwise, fix your driver.
Download Custom Recovery
OrangeFox - https://orangefox.download/device/vayu
TWRP - https://forum.xda-developers.com/t/recovery-unofficial-teamwin-recovery-project.4269551/
Lineage OS Recovery - https://download.lineageos.org/vayu
Don't use LOS recovery if you are rooting, it doesn't support OTA data decryption thus magisk need to be reflashed everytime during OTA.
Extract the "img" recovery file to the tool's folder
Type "fastboot flash recovery <filename>"
Done, type "fastboot reboot recovery" or Volume Up + Power on mobile to enter recovery
Spoiler: How to Flash Custom Rom
Connect mobile to PC
Copy files to mobile
Firmware - https://xiaomifirmwareupdater.com/firmware/vayu/
Rom
XDA Roms - https://forum.xda-developers.com/f/xiaomi-poco-x3-pro.12163/?prefix_id=33
Xiaomi EU Rom - https://xiaomi.eu/community/forums/miui-rom-releases.103/
Gapp (if you want)
MindtheGapps
NikGapps
FlameGapps
OpenGapps (Personally Recommended)
Magisk (If rooting) - https://github.com/topjohnwu/Magisk/releases
Boot into recovery - Vol up + Power
install in order
Firmware
Rom
Gapps (if you want)
Magisk (if rooting)
Format data in recovery
Wipe Cache and Dalvik/Art Cache (If the recovery support it)
Reboot into system
Done
If you mess up the format data sequence, don't worry, you can always use "adb sideload". Also, if you use LOS recovery, you need to use sideload.
Look for sideload in recovery
Open command prompt in your tool folder, type "adb sideload <filename>" to install the things you want.
Spoiler: How to flash back or to official rom along with official recovery
Download xiaomi flash tool - https://xiaomiflashtool.com/
Download fastboot package - https://xiaomifirmwareupdater.com/archive/miui/vayu/
Extract xiaomi flash tool, run "XiaoMiFlash.exe"
Extract fastboot package to somewhere, preferably root subfolder of c:\ or whatever drive
Long pathname can cause "XiaoMiFlash.exe" to run into error
Boot mobile into fastboot - Vol down + power
Connect mobile to pc
In "XiaoMiFlash.exe", select folder of fastboot package
Bottom right of the software, choose "clean all" or "clean and lock (bootloader)"
Click flash
Once done, it will auto reboot into MIUI
Spoiler: How to pass safetynet for custom rom
At the moment of this post, most custom roms fail safetynet. It is not absolutely necessary to get safetynet to work. Only do this if the gapps you want to install require it.
Install magisk (No way around it)
Install props config module
Reboot
Run any terminal app - https://play.google.com/store/apps/details?id=com.termux
Type "su" and enter
Grant super user rights to it
Type "props" and enter
Type "1" and enter
Type "f" and enter
Type "22" and enter
Type "6" and enter
Basically, you are choosing "Poco X3 Pro (Global)"
Type "y"
Reboot and test your safetynet
Spoiler: How to make Nasty Anti-Root Apps work with Magisk
In magisk, install Riru module
Download Unshare - https://github.com/vvb2060/riru-unshare/releases
In magisk, install Unshare
In magisk, enable "Magisk Hide" in settings
In magisk, "hide Magisk" in settings, choose some really unpredictable name
In magisk, press "Shield", hide all options (dropdown) for the targetted App
Reboot
Try run the apps multiple times
If fail
Install App Manager - https://f-droid.org/en/packages/io.github.muntashirakon.AppManager/
In App Manager, look for the apps, go to "Services", disable that one "(Isolated)" service.
Double make sure it is applied
Reboot
Try run the apps multiple times
Still fail
Try this, some say it worked
In magisk, install LsPosed module
Install XPrivacyLua - https://repo.xposed.info/module/eu.faircode.xlua
In LsPosed, enable XprivacyLua and Singpass in that same list
Reboot
In XPrivacyLua, look for the app, enable restrict on "Get Applications"
Reboot
Try run the apps multiple times
this is the last resort
Install Shelter - https://play.google.com/store/apps/details?id=net.typeblog.shelter
Clone the App in Shelter
In shelter, under work profile, make sure no rooted apps in there
Reboot
Try run the App in work profile multiple times
SubwayChamp said:
You don´t need to pay someone else for that, you can do it by your own [...]
Click to expand...
Click to collapse
Thanks a lot. It makes sense.
I was also told, that before flashing it is esential to do a backup.
What's your opinion? How to do so?
kamien8 said:
Thanks a lot. It makes sense.
I was also told, that before flashing it is esential to do a backup.
What's your opinion? How to do so?
Click to expand...
Click to collapse
About backup the first important is what is important for one, I mean personal information like messages, call, WhatsApp and so on.
But the most important in other sense is about the well functioning of the device itself, for example EFS where is stored the IMEIs, sometimes vendor, dtbo and persist images depending on the custom recovery if it includes these options.
Particularly, I never need any other partition from recovering eventually my device/s.
I would like to suggest you to try flashing some roms on any other device which you don't use(for ex. an old abandoned phone) and gain some experience before trying on your poco x3 pro.
dey18 said:
I would like to suggest you to try flashing some roms on any other device [...]
Click to expand...
Click to collapse
That was my idea. Unfortunately the only 'old' phone I've got is Huawei P9 Lite 2017 with Android 7. I haven't found any information, that there is a way to install LineageOS on the device.
However, for training purposes I could install any different OS, suitable for the device. Do you know any?
By the way, is the following link the only valid repository for the OS?
LineageOS Downloads
download.lineageos.org
kamien8 said:
That was my idea. Unfortunately the only 'old' phone I've got is Huawei P9 Lite 2017 with Android 7. I haven't found any information, that there is a way to install LineageOS on the device.
However, for training purposes I could install any different OS, suitable for the device. Do you know any?
By the way, is the following link the only valid repository for the OS?
LineageOS Downloads
download.lineageos.org
Click to expand...
Click to collapse
yes, thats the official site
kamien8 said:
That was my idea. Unfortunately the only 'old' phone I've got is Huawei P9 Lite 2017 with Android 7. I haven't found any information, that there is a way to install LineageOS on the device.
However, for training purposes I could install any different OS, suitable for the device. Do you know any?
By the way, is the following link the only valid repository for the OS?
LineageOS Downloads
download.lineageos.org
Click to expand...
Click to collapse
If you had no experience of flashing a phone, read and follow this guide with Pictures :
https://forum.xda-developers.com/t/4288121/post-85137963
It should be sufficient to help you flash a ROM.
No tutorial about backup data from phone in that guide, you have to do it on your own.
pl1992aw said:
If you had no experience of flashing a phone, read and follow this guide with Pictures :
https://forum.xda-developers.com/t/4288121/post-85137963
It should be sufficient to help you flash a ROM.
No tutorial about backup data from phone in that guide, you have to do it on your own.
Click to expand...
Click to collapse
I like this method, and this specific guide is what helped me flash custom rom on my X3 pro.
It is detailed and even gives notice if in case we get lost in a step.
I hope the OP can read this as the guide was really helpful. I know they used arrowOS for example, but I applied the method with different rom.
kamien8 said:
That was my idea. Unfortunately the only 'old' phone I've got is Huawei P9 Lite 2017 with Android 7. I haven't found any information, that there is a way to install LineageOS on the device.
However, for training purposes I could install any different OS, suitable for the device. Do you know any?
By the way, is the following link the only valid repository for the OS?
LineageOS Downloads
download.lineageos.org
Click to expand...
Click to collapse
I suggest you to try any other roms available for your device and not just lineage.
Try flashing multiple roms one by one and identify and rectify your errors.
And don't forget to read documentation provided by the wiki completely and also check out some vids on youtube(people on telegram would tell you to watch yt channel named "Munchy" because he has got this phone).
I wouldn't try and flash an old p9 lite. I remember when I had a p9 and tried to flash it it was a nightmare and was an unorthodox method. If you could grab an old Moto like the Moto g as that would be ideal for a practise flash.
Warren_Orange said:
[...] Moto g [...]
Click to expand...
Click to collapse
I've never used Motorola before. Which G would be good to start gaining an experience?
I'll try to find a pre-owned one.
I'd go for a moto g 2nd or 3rd Gen. You can get them for peanuts on eBay and there is still development for them even now.
I recommend Moto G5.. pretty active community on xda, replacable battery and should be very cheap
k3lcior said:
I recommend Moto G5.. pretty active community on xda, replacable battery and should be very cheap
Click to expand...
Click to collapse
Moto G5
Warren_Orange said:
I'd go for a moto g 2nd or 3rd Gen. You can get them for peanuts on eBay and there is still development for them even now.
Click to expand...
Click to collapse
Do you mean something like this?
gsmarena_moto_g
Will it be possible to go with LineageOS 18.1 on such an old phone?
kamien8 said:
Moto G5
Do you mean something like this?
gsmarena_moto_g
Will it be possible to go with LineageOS 18.1 on such an old phone?
Click to expand...
Click to collapse
Yes that's the one. After having a quick look at the forums I don't think you'd get 18.1 on it. There is a micro g 17.1 rom that seems active.
Is this for practice or for use as well? If it's for using I'd probably go with the g5 for a few bucks extra as the Moto g is quite old but it's not a bad spare spare phone. I picked one up as a backup and I liked the feel of it (if your into small phones) . It reminded me of the first Moto X.