Related
I've been trying to replace the images in my Doogee X5pro with custom rom.
My host PC environment is:
Ubuntu 14.04.5 Trusty, 64bit
fastboot (using the one installed along with Android Studio SDK)
I have unlocked the bootloader ('fastboot oem unlock' and have checked the variable 'unlock=yes' with 'fastboot getvar all')
At this point, I tried to replace the images in the custom rom zip file.
However, I found that while boot.img, recovery.img is flashed without any problems,
when I try to flash system.img, cache.img, and other images, it simply returns an error(FAILED. unknown command)
BTW, i have the scatter file and have been adding the 'base address' option to every fastboot flash command.
(ex: 'fastboot flash boot boot.img -b 0x2de000000' , where I simply retrieved the base address of each partition from the scatter file).
Also, I have specified the '-S' option which will sparse the image file when the image file to be flashed exceeds the size specified with the '-S' option
(ex: 'fastboot flash system system.img -b 0x2f000000 -S 100M).
Could someone point me in the right direction to solve this issue?
Hi and welcome to assist,
Please see this thread about rooting your device here:
Root Doogee X5 Pro
I'm sure you will find an answer there.
Additional info: [Guide] How To Setup And Use Fastboot
Good luck
Thread Closed Per OP Request
Don't work,
I give up
Thanks in advanced. All comments can help!
I have a tablet I can depure via USB and where I can root the tablet. But if I connect to the internet, the "registration and password" of university program enters and is saved (even after formatting it is stuck on this screen) blocking the tablet, I believe that after the internet loads, it installs this locking program ... What would be the name of this type of application? I'd like to know, how remove this app, to If connect in internet, we can block (and try install TWRP via internet with TWRP Management)...
C.Modica said:
Hello everyone !
I've been trying to resolve this issue for weeks. I have a tablet that I can't unlock (it's super hard, it's like Dark Souls of tablets). Well let's start.
He has a program that blocks asking for password and user (this a old from a university), where you request access via wireless or 2G/3G. without it you can't access it, so I believe I have to change his firmware instaled in, but I'm having a hard time to make it.
• Let's go to basic product information:
The chip is a RK3066 (same from TV BOX based on rockchip).
The model is YPY L1050 from POSITIVO (it's from Brazil).
- Software and Items
I have the drivers installed (correctly);
I have adb installed;
I have SD_Card;
I have acess from PC;
The tablet is unroot;
• Back to the items:
So, the good news is that I have the same tablet model, unlocked (with another type of ROM that I am unaware of). That works normally, without problems. Well, I saw a procedure that basically it is possible to extract this image from the good tablet, to the locked tablet. I did that, I ended up extracting a series of .img files from the unlocked tablet: boot, cache, kernel, system, etc... ok.
• Trying a extract from unlock same tablet:
I try transfer the copied files from "good unlock tablet" (extrated with AndroidTool), and put in (with the same tool) in the lock tablet... There is a problem, even before starting the operation, I have the error "Test Device Fail ", in the last is not possible to transfer files via USB (I can only do commands like" ResetDevice ", or export the images from the blocked tablet via AndroidTool... and yes I have the drivers instaled, commands like adb sideloader in the fastboot works).
• Trying a firmware found in internet:
Well, I tryed to download the firmware found on the internet corresponding to the device model, but unfortunately I have the same error as above. I download the .img firware original and using the RKBatchTool and have the same error (the operation don't start, give "Test Device Fail" in "Upgrade" and "Restore").
I believe that both operations do not accept transferring via USB.
PS: The tablet unlocked the command of "TestDevice" works fine.
• What I was thinking of doing:
1 - I think I need to take the all .img(s) files extracted from the unlocked device, put it in a single image (.img), put it in a SD_Card and in the "fastboot" take the option "update rkimage from external storage". But I don't know how to do this. (I try search for it);
2 - Somehow being able to do "apply update from external storage", maybe doing the same procedure above with an "update.img", but I also don't know how to do that (put all img. files together in the form of a one update.img).
3 - Have anothers options, like "apply update from ADB", the PC response this conection with tablet, (I can see the device with ''adb device'' cmds in sideload mode in PC). The problem is that I don't know how I'm going to send the .img file, if I send it inside a .zip (I even tried that, send all the .img files inside a .zip to see if it works. The tablet arrives to read the files but in the end the operation aborts). So my knowledge is lacking in this part.
4 - Another would be such a "ROM Dump." I'd like to do a "ROM dump" with an SD card, I even researched it on the internet but I didn't find this procedure to rockchip (only for Amlogic).
With SD Card:
There was a youtube that managed to unlock a tablet like that, but it was a previous model that I'd like to unlock (and different version of firmware, android etc). His method was to put a bootable sd_card, but he doesn't explain how he does it (he only gives the file done) and looking at the files internally, I just think they were converted to linux formats (system.tar.gz, userdata.tar.gz, some .sh .so files, and a bootenv.img, uImage etc) and with completely different names from .img... It is a pity that it is not for my Tablet model .
Well, that's it in the end, I need to change the firmware and I don't know how to do it.
PS: I tried other operations/methods as well, but I will not comment so that this post doesn't get big.
Thanks in advanced. All comments can help!
Click to expand...
Click to collapse
Instead of trying to package the .img files into one file, you should try flashing each .img individually via fastboot using commands with the following structure:
fastboot flash <name of partition> <name of partition.img>
The following commands are examples.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash kernel kernel.img
You will need to use a separate command for each individual .img.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Instead of trying to package the .img files into one file, you should try flashing each .img individually via fastboot using commands with the following structure:
fastboot flash <name of partition> <name of partition.img>
The following commands are examples.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash kernel kernel.img
You will need to use a separate command for each individual .img.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Hi, thanks for the reply. Well I can make it via adb sideload? I can't use the command "adb reboot fastboot". Because this command "adb reboot fastboot" only turns off the tablet don't restarting into fastboot/download mode (just turns off). But If I manually enter on the bootloader, I can access the adb sideload option, where the adb install on computer can detects the device via the "adb devices command" with sideload.
C.Modica said:
Hi, thanks for the reply. Well I can make it via adb sideload? I can't use the command "adb reboot fastboot". Because this command "adb reboot fastboot" only turns off the tablet don't restarting into fastboot/download mode (just turns off). But If I manually enter on the bootloader, I can access the adb sideload option, where the adb install on computer can detects the device via the "adb devices command" with sideload.
Click to expand...
Click to collapse
It isn't going to work via adb unless the device is rooted and then it won't be via adb sideload, it would be done by using dd commands to dd the .img files directly to their partitions.
Sent from my SM-S767VL using Tapatalk
I just found a solution. It requires some tinkering, though.
I had to use a machine running windows 7, because that's the only OS that the drivers worked.
Download the firmware for the Ypy L1050F here: https://www.stockrom.net/2018/07/l1050.html
It comes with the drivers, the ROM, and a tool called RKBatchtool 1.8
You'll have to decompress everything, open RKBatchtool and choose the firmware that is in the ROM folder (Not the DEMO one).
Now comes the tricky part: You gotta undo the 3 screws aroud the tablet, then pry it open with your fingers(remember to remove microSD and SIM first, to avoid breaking stuff!). I recommend startind by the side with the usb, hdmi and power ports to get some leverage. The back cover should pop right off. Then you have to locate the NAND chip in it. Should be a Micron one with 48 pins. The small circle at one of the corners of the chip represents pin 1. Plug your usb cable to the tablet. With the tablet TURNED OFF, use a SIM removal tool or very fine tip metallic screwdriver to short pins 17 and 18 on the NAND chip and plug the power jack into the tablet. RKBatchtool should show that a device was connected. You can release the screwdriver now and just click the "Upgrade" button in RKBatchtool. Now this is very important: DO NOT UNPLUG your tablet until everything is done. It'll tell you when it's done uploading the firmware and checking it. Enjoy your new usable tablet!
I scoured the internet and found this procedure being used for TV Boxes with the same RK3066 SoC. AFAIK, nobody else managed to do it so far, so spread the word.
You are awesome. Broke the internet! I will follow your procedures to try to unlock it. Many thanks again xmas for you.
[edit] don't work
Guide for flashing GSI on mediatek devices is uploaded- checkout [ Works on IMEI erased phones too! ]
This method is for mediatek chipset devices only
Spoiler: Jump to rooting
Open python directory and open mtkclient folder inside it
Run cmd inside mtkclient folder by typing cmd inside address bar of file explorer and press Enter
Turn off your phone and connect to PC with usb cable while holding Vol up and Vol down together
Run these commands inside cmd one by one
python mtk r boot,vbmeta boot.img,vbmeta.img
python mtk reset
Your phone will reboot now
There will two files created inside mtkclient folder called boot.img and vbmeta.img
Copy boot.img file to your phone
Download this masigk app only and install on phone
Open magisk and patch the boot.img file, a new file will be created inside Downloads folder named magisk_patched.img
Rename this file to boot.patched and copy it to your PC
Move this file into mtkclient folder inside python directory and replace old boot.img
Open cmd inside mtkclient folder by typing cmd inside address bar of file manager and press Enter
Now run the following command inside cmd
python mtk w boot,vbmeta boot.patched,vbmeta.img.empty
Turn off your phone and connect to PC with usb cable while holding Vol up and Vol down together
python mtk reset
Your phone will reboot now
Your device is rooted now ╰(*°▽°*)╯
Spoiler: Rooting files for devices on C.12 [ RMX2117 ]
Rooting files for devices on C.12: Download here
Place the downloaded files into mtkclient folder inside python directory and execute
python mtk w boot,vbmeta boot.patched,vbmeta.img.empty
python mtk reset
Prerequisite :
1. Mediatek drivers
Extract the zip and open Driver folder
Run the exe files, after the installation process is complete restart your PC
To check if drivers were installed and are working, turn off your phone and connect it to PC using USB Cable while holding both volume up and down buttons
There will be a prompt sound if device is connected
If your device still isn't detected, open MTK_USB_All_v1.0.8 folder and run MTK_USB_All_v1.0.8.exe
After the installation process is complete, restart your PC
2. Python Download and install python.
Go to python directory
Search python in start menu, right click python and click on open file location, again right click on python and click open file location | This is the python directory.
Open cmd inside it by typing cmd at the address bar of file explorer and press Enter
Inside cmd exectue following commands one by one
Thanks Bjoern Kerler
git clone https://github.com/bkerler/mtkclient
cd mtkclient
pip3 install -r requirements.txt
3. Unlocked Bootloader [ User data will be formatted ]
Turn off your phone
Open mtkclient folder inside python directory and open cmd inside folder by typing cmd inside address bar of file manager
Now run below command
python mtk e metadata,userdata,md_udc
Connect phone to PC with USB Cable while holding Vol+ and Vol- together
Now run below commands one by one
python mtk da seccfg unlock
python mtk reset
After the script completes, disconnect phone and reboot by holding power button
Your device's bootloader is unlcoked now ╰(*°▽°*)╯
Note: Bootloader can't be used whatsoever but 'unlocked bootloader' is a requirement before flashing any partition to your phone
Now comes actual rooting part
Open python directory and open mtkclient folder inside it
Run cmd inside mtkclient folder by typing cmd inside address bar of file explorer and press Enter
Turn off your phone and connect to PC with usb cable while holding Vol up and Vol down together
Run these commands inside cmd one by one
python mtk r boot,vbmeta boot.img,vbmeta.img
python mtk reset
Your phone will reboot now
There will two files created inside mtkclient folder called boot.img and vbmeta.img
Copy boot.img file to your phone
Download this masigk app only and install on phone
Open magisk and patch the boot.img file, a new file will be created inside Downloads folder named magisk_patched.img
Rename this file to boot.patched and copy it to your PC
Move this file into mtkclient folder inside python directory and replace old boot.img
Open cmd inside mtkclient folder by typing cmd inside address bar of file manager and press Enter
Now run the following command inside cmd
python mtk w boot,vbmeta boot.patched,vbmeta.img.empty
Turn off your phone and connect to PC with usb cable while holding Vol up and Vol down together
python mtk reset
Your phone will reboot now
Your device is rooted now ╰(*°▽°*)╯
Rooting files for devices on C.12: Download here
Place the downloaded files into mtkclient folder inside python directory and execute
python mtk w boot,vbmeta boot.patched,vbmeta.img.empty
python mtk reset
why are you linking your own github? why alpha build?
aIecxs said:
why are you linking your own github? why alpha build?
Click to expand...
Click to collapse
its patched magisk for mediatek devices, using other version of magisk for patching boot file results in bootloop
hm.. I have Xiaomi Redmi 6 it doesn't boot-loop. but I have other issue. will try...
nope! same issue as on any magisk. but this one does not even give root. Do not link that apk without note what exactly is "patched" - it's not recommended!
Code:
cereus:/ $ su
No daemon is currently running!
aIecxs said:
hm.. I have Xiaomi Redmi 6 it doesn't boot-loop. but I have other issue. will try...
nope! same issue as on any magisk. but this one does not even give root. Do not link that apk without note what exactly is "patched" - it's not recommended!
Code:
cereus:/ $ su
No daemon is currently running!
Click to expand...
Click to collapse
You have missed something, it definitely works and the issue you have mentioned isn't related to this thread, if its caused by magisk then try other rooting solutions.
I just proofed that (outdated) patched alpha apk isn't working for my mediatek device (doesn't give root), furthermore the official stable apk doesn't boot-loop my mediatek device.
https://github.com/topjohnwu/Magisk
yes, my linked issue is unrelated. but you can find magisk logs there, proof that canary is working.
So if Magisk boot-loop for you, obviously you are the one who has missed something (maybe checkbox for preserving encryption?)
Did you tried with steps mentioned in this thread ?
If yes then, if you read this command,
Code:
python mtk w boot,vbmeta boot.patched,vbmeta.img.empty
Here the boot.img is named boot.patched to avoid unpatched boot image to be flashed on device
Did you renamed patched boot.img as boot.patched ?
my bootloader is unlocked already, so I just flashed magisk_patched_23001.img from fastboot. as you can see in post #4 su respond with No daemon is currently running! so obviously magisk is somehow present.
Maybe I should delete /data/adb next time trying older Magisk. but baseband unknown occurred regardless of su daemon was not running, therefore I have no interest in this v23 alpha build anyway.
But thx for trying to help me
aIecxs said:
my bootloader is unlocked already, so I just flashed magisk_patched_23001.img from fastboot. as you can see in post #4 su respond with No daemon is currently running! so obviously magisk is somehow present.
Maybe I should delete /data/adb next time trying older Magisk. but baseband unknown occurred regardless of su daemon was not running, therefore I have no interest in this v23 alpha build anyway.
But thx for trying to help me
Click to expand...
Click to collapse
you can easily fix unknown baseband using twrp
you mean patching fstab with nvram nvdata nvcfg? how can I do this systemless? or do you mean I should patch twrp.fstab? thought that is only used for recovery mode.
aIecxs said:
you mean patching fstab with nvram nvdata nvcfg? how can I do this systemless? or do you mean I should patch twrp.fstab? thought that is only used for recovery mode.
Click to expand...
Click to collapse
You need to delete a certain files in a directory in root file system it works well in android 10 and above
what? magisk is systemless-root method. I won't touch anything inside system partition for sure (I would just use Magisk systemless REPLACE function if you tell me what exactly files must deleted?) But my baseband is working fine on normal boot, just when booted into Magisk baseband disappears. Have you even read my issue on github (linked in post #4)?
Bro i know what circumstances you have here regarding magisk, but why are u using alpha build if you can use the normal apk? And what android are yoi?
Regarding in unknown baseband you can try this method to fix it android 9 and up root/nvdata/nvram then delete all files inside for android 8 and lower root/nvram delete all files inside
I am using latest magisk. what is root/nvram? do you mean (rootdir) / namely /nvram? that is just a mountpoint for nvram partition. why should I delete nvram partition, as I stated baseband is working? please read the github issue first...
https://github.com/topjohnwu/Magisk/issues/6570
aIecxs said:
I am using latest magisk. what is root/nvram? do you mean (rootdir) / namely /nvram? that is just a mountpoint for nvram partition. why should I delete nvram partition, as I stated baseband is working? please read the github issue first...
https://github.com/topjohnwu/Magisk/issues/6570
Click to expand...
Click to collapse
Look bro your phone has dm-verity right and you know how it works right? I meant to delete the files inside thay folder you cant easily delete partition in twrp file manager you know that is only the mount point but not the actual partition thos files might be duplicate or blocking something that might be the cause of the error in baseband if you delete that files inside it moght fix your phone and u dont need to worry if you have dm verity its ok because it will restore your deleted files in root folder
Anonymous V said:
Look bro your phone has dm-verity right and you know how it works right? I meant to delete the files inside thay folder you cant easily delete partition in twrp file manager you know that is only the mount point but not the actual partition thos files might be duplicate or blocking something that might be the cause of the error in baseband if you delete that files inside it moght fix your phone and u dont need to worry if you have dm verity its ok because it will restore your deleted files in root folder
You know im just suggesting you a solution just try it might help
Click to expand...
Click to collapse
.
I just installed mentioned drivers and python .
After that I cloned the github repo mentioned in tutorial.
Then I did execute cmd in mtkclient folder.
Now I am stucked on this step where I have to connect my phone through USB with pressing vol+ & vol- buttons.
Just give me some idea about how to get through this error,
please suggest me solutions for this error.
Please help me with the preloader error.
While Pressing Vol+ with Vol- Buttons the Handshake failed error pops on screen.
Please Help me to fix this error.
I just want to unlock the bootloader of my rmx2117.
Please specify Android version of your phone. If drivers are installed correctly, there must COM port displayed in Device Manger on your PC
and most important, device must powered off for the handshake. if you miss it, it will powered on by usb (which is too late)
Hi,
during the update the phone got stuck, daughter restarted couple of times but it always got to the 76%, hang there and then restarted itself in the endless loop.
I've tried the the hard reset (Power+VolUP) and it got to the screen saying "No Command". Then I pressed the same combo again to get to the bootloader and tried the wipe / reset. During that process I got the error message "E: Can't send SPI message. Try again" and then it said it was successful, but rebooting did nothing, got stuck in the restart loop.
So I've done the research and wanted to to upload the OTA update, have done that but that didn't do anything.
So I've found some articles on how to upload the stock rom/image but I'm unable to do so as sending adb commands is disabled due to the phone being LOCKED. I've learned that the USB debugging needs to be enabled, however I'm unable to get into the OS to set it up, so found this article:
How to enable USB Debugging in Android using recovery mode?
One million questions, Is it possible to Enable USB Debugging in Android Using Recovery Mode or any other technique? Well, the answer is Yes! It is now
www.isrgrajan.com
which outlines the following steps (in summary):
Download the Stock ROM for your device- Google it, I am dam sure you can find it. [DONE]
Download SuperSU from UPDATE-SuperSU-v1.65.zip [DONE][looks pretty old though]
Steps to Enable USB Debugging Using Recovery Mode
Unzip the stock ROM. [DONE]
Within the extracted folder, you will find the system.img well extract it too using Ext4 Unpacker [DONE but plenty of folder are empty, but eventually plentu of APK along]
Also, extract the Update-SuperSU.v1.65.zip file. [DONE, again, looks pretty old]
Now open the folder where you have extracted the system.img files [DONE]
Grab any .apk file from this folder and change the extension from .apk to .zip [PROBLEM: the apks are all over the shop. Which APK shall I pick up?]
And Copy the RSA Certificated to the Update-SuperSU.v1.65 folder (delete previous files if exist) [PROBLEM: unable to find any "RSA Certificated" like files once I open ANY apk]
Also, copy the build.prop to the system folder located within Update-SuperSU.v1.65 folder [BLOCKED by previous step]
Locate the update-script file within this folder and edit it using Notepad++ [BLOCKED by previous step]
You need to update the build.prop file after adding the following line at the bottom [BLOCKED by previous step]
persist.service.adb.enable=1
Next step is updating SQLite Database [WHERE would I do this step?]
Which can be done by adding the following code to the update-script file
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "UPDATE global SET value=1 WHERE name='adb_enabled'"
What would I do then? How to actually apply the changes back to the phone?
Does anyone know of better / latest step by step process of enabling / unlocking the device or is my device now completely and unrepairably bricked?
Thank you.
Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
jwoegerbauer said:
https://gist.github.com/varhub/7b9555cdd1e5ad785ffde2300fcfd0bd
Click to expand...
Click to collapse
For a while (since when, I don't know) persistent properties are not shared as individual files in /data/property.
They are all packed inside /data/property/persistent_properties.
Try setprop instead.
jwoegerbauer said:
Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
Click to expand...
Click to collapse
will give it a go. thank you.
jwoegerbauer said:
Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
Click to expand...
Click to collapse
I've tried the steps but I'm crashing on sending any commands to the device. While I'm in the recovery, I see the following details and options:
```
Android Recovery
google/blueline/blueline
12/SP1A.210812.016.B2/8602260
user/release-keys
Use volume up/down and power
Warning: Previous installation has failed. Your device may fail to boot if you reboot or power off now
- Reboot system now
- Reboot to bootloader
- Enter Fastboot
- Apply Update from ADB
- Apply update from SD card
- Wipe data/factory reset
- Mount /system
- View recovery logs
- Run Graphics Test
- Run Locale Test
- Power Off
```
where I run the adb command:
`adb shell mount data` I get the `adb.exe: no devices/emulators found`.
when I go to the `Apply update from ADB` and run the command above I get `error: closed`.
Basically I'm unable to run any adb commands as of the first message, and the only place I can it's from within the update. I've noticed that while in the 'Update via ADB', then in the Win Device Manager I can see that the driver is changed to `Android Composite ADB Interface` and only now it's accepting very limited commands. `adb devices` command generates: `<device id number>: sideload`.
When in the fastboot, it switches to `Android Bootloader Interface` in the DEvice manager.
When in recovery, the device is disconnected from the computer. (is not listed in the device manager)
any thoughts. thanks
Note: that phone was never rooted.
Bootloader looks like this at the moment:
```
Fastboot Mode
Product revision: blueline MP1.0(ROW)
Bootloader version: b1c1-0.4-7617406
Basebandversion...
serial number:
secure booth: PRODUCTION
NOS Production: yes
DRAM: 4GB
Device State: Locked
Boot slot: a
```
vajnorcan said:
I've tried the steps but I'm crashing on sending any commands to the device. While I'm in the recovery, I see the following details and options:
```
Android Recovery
google/blueline/blueline
12/SP1A.210812.016.B2/8602260
user/release-keys
Use volume up/down and power
Warning: Previous installation has failed. Your device may fail to boot if you reboot or power off now
- Reboot system now
- Reboot to bootloader
- Enter Fastboot
- Apply Update from ADB
- Apply update from SD card
- Wipe data/factory reset
- Mount /system
- View recovery logs
- Run Graphics Test
- Run Locale Test
- Power Off
```
where I run the adb command:
`adb shell mount data` I get the `adb.exe: no devices/emulators found`.
when I go to the `Apply update from ADB` and run the command above I get `error: closed`.
Basically I'm unable to run any adb commands as of the first message, and the only place I can it's from within the update. I've noticed that while in the 'Update via ADB', then in the Win Device Manager I can see that the driver is changed to `Android Composite ADB Interface` and only now it's accepting very limited commands. `adb devices` command generates: `<device id number>: sideload`.
When in the fastboot, it switches to `Android Bootloader Interface` in the DEvice manager.
When in recovery, the device is disconnected from the computer. (is not listed in the device manager)
any thoughts. thanks
Note: that phone was never rooted.
Bootloader looks like this at the moment:
```
Fastboot Mode
Product revision: blueline MP1.0(ROW)
Bootloader version: b1c1-0.4-7617406
Basebandversion...
serial number:
secure booth: PRODUCTION
NOS Production: yes
DRAM: 4GB
Device State: Locked
Boot slot: a
```
Click to expand...
Click to collapse
On my pixel3, /dev/block/dm-4 is mounted to /data. Try "adb shell mount /dev/block/dm-4 /data".
The instructions you are following are very old, and likely obsolete. SuperSu is also obsolete. Try to find a newer method.
dcarvil said:
On my pixel3, /dev/block/dm-4 is mounted to /data. Try "adb shell mount /dev/block/dm-4 /data".
The instructions you are following are very old, and likely obsolete. SuperSu is also obsolete. Try to find a newer method.
Click to expand...
Click to collapse
the issue is I'm unable to run that command `adb shell mount...` with the `no devices/emulator found` message. I believe it's because the device is not even listed in the device manager (windows) when in recovery mode. When in the update mode, then it's listed in the DM. See my post above, I've updated it few times. Thanks
Btw on that link if you check the posts there are newer ones (1.5y back) claiming it works so might actually work
If you're unable to sideload the OTA via PC, I don't think there's any other option besides paying for a repair, or replacing the device. A locked bootloader definitely makes recovery a lot harder.
V0latyle said:
If you're unable to sideload the OTA via PC, I don't think there's any other option besides paying for a repair, or replacing the device. A locked bootloader definitely makes recovery a lot harder.
Click to expand...
Click to collapse
I'm able to sideload the OTA, but restart goes into start being stuck and back and forth but never gets any further than the first google load screen
vajnorcan said:
I'm able to sideload the OTA, but restart goes into start being stuck and back and forth but never gets any further than the first google load screen
Click to expand...
Click to collapse
Were you using adb/fastboot before this happened? Was the device recognised then? If not, are you sure you have the right drivers?
AlexKarimov said:
Were you using adb/fastboot before this happened? Was the device recognised then? If not, are you sure you have the right drivers?
Click to expand...
Click to collapse
I've used the adb to upload the ota and that went, according the message ok, but the system won't start up. Device is recognized only when I choose the "Apply update from ADB" option in recovery mode. The moment I choose it, it shows up as a device in device manager and "adb devices" lists it ok. In fastboot mode it does list it in device manager, but "adb devices" doesn't list it.
It's the latest driver
vajnorcan said:
I've used the adb to upload the ota and that went, according the message ok, but the system won't start up. Device is recognized only when I choose the "Apply update from ADB" option in recovery mode. The moment I choose it, it shows up as a device in device manager and "adb devices" lists it ok. In fastboot mode it does list it in device manager, but "adb devices" doesn't list it.
It's the latest driver
Click to expand...
Click to collapse
If I understand correctly, you're using "adb devices" when in fastboot mode? You need to use "fastboot devices". If that works and lists the phone then you may be able to use the flash tool on the Google website
AlexKarimov said:
If I understand correctly, you're using "adb devices" when in fastboot mode? You need to use "fastboot devices". If that works and lists the phone then you may be able to use the flash tool on the Google website
Click to expand...
Click to collapse
This requires OEM Unlocking to be enabled so it won't be much help here.
Rescue Mode might work though.
@vajnorcan try this:
Boot to bootloader and select Rescue Mode using the volume buttons, then press Power to enter it.
On your PC, go to pixelrepair.withgoogle.com and connect the USB cable to your device. Select your carrier or select "Other" if device is unlocked.
I don't know whether this will actually work...I haven't heard of anyone using this tool to successfully recover.
AlexKarimov said:
If I understand correctly, you're using "adb devices" when in fastboot mode? You need to use "fastboot devices". If that works and lists the phone then you may be able to use the flash tool on the Google website
Click to expand...
Click to collapse
'fastboot devices' is reading the device, which is good. but trying the online flash tool fails due to the device being locked. :/
V0latyle said:
This requires OEM Unlocking to be enabled so it won't be much help here.
Rescue Mode might work though.
@vajnorcan try this:
Boot to bootloader and select Rescue Mode using the volume buttons, then press Power to enter it.
On your PC, go to pixelrepair.withgoogle.com and connect the USB cable to your device. Select your carrier or select "Other" if device is unlocked.
I don't know whether this will actually work...I haven't heard of anyone using this tool to successfully recover.
Click to expand...
Click to collapse
The google tool has found and connected to the device, but it ends up in an error (on the device) and saying "disconnected", looked promising, but not for long. thanks.
root infinix XOS 12 (Android 12)
Infinix Zero 5G Ant-Man and the Wasp: Quantumania Edition
Easy unlock
1. Enable developer options and turn on/allow OEM unlocking and enable USB debugging
2. Reboot to fastoot
Code:
Code:
adb reboot bootloader
3. Unlock bootloader via fastboot (you will be prompted to accept yes with volume up on phone.
Code:
fastboot flashing unlock
4. Setup and install MTK client Linux (fallow guide)
[GUIDE] [MTK] How to use MTKClient and set it up!
So most of you probably don't know what mtkclient is. It is basically an exploit which is used to boot any (mtk) phone into BROM mode (basically EDL for mtk) I am writing this guide especially for the RM6785 community. This tool is very useful...
forum.xda-developers.com
4. backup all partitions with MTKClient/MTKTool GUI (launch the mtk_GUI with su/root)
in mtk_GUI
Go to,
Read Partition(s) Tab and tick all boxes to be read/backup the partitions except data partition (internal storage)
Now you should have a backup of your files/.bin
5. copy boot_a.bin to your phone internal for magisk patching manually on phone
(Time of writing latest)
https://github.com/topjohnwu/Magisk/releases/download/v25.2/Magisk-v25.2.apk
6. Rename (magisk renames the default .bin)
patched_boot_a.img to patched_boot_a.bin
7. Copy patched boot_a back to your computer/home folder.
8. flashing.
From fresh started Android reboot to fastboot.
Code:
adb reboot bootloader
DO THE NEXT 2 STEPS AT THE SAME TIME IN FASTBOOT.
(Fastboot commands)
Code: terminal
Code:
fastboot flash boot_a /path/to/patched_boot_a.bin
Code2: (disable verity/secure boot) use vbmeta_a.bin that you backed up from you're phone.
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a /path/to/vbmeta_a.bin
AFTER flashing above you should now have root
############## system r/w#############
If you want system R/W writable (full root) fallow next steps.
1. go to system r/w website and get this version tested here.
Official SYSTEM-RW v1.41 by lebigmac for Samsung Galaxy S23 Ultra and other devices
lebigmac's software
lebigmac
www.systemrw.com
Link to file above
11.21 MB file on MEGA
mega.nz
This must be run on the phone!
Step 1
Decompress (7zip) SYSTEM-RW_v1.41.zip to this directory on device. sysrw_1.41
Code:
/data/local/tmp
Step 2 in Android terminal type
Code:
Code:
su
cd /data/local/tmp/sysrw_1.41
chmod +x sysrw
./sysrw
This will build the new patched r/w super.bin in /data/local/tmp/sysrw_1.41/IMG
Use file explorer (fx-file explorer) to copy patched_super.bin to phones internal/storage and then copy to computer to flash with fastboot.
Step 3
Code:
On computer/PC with adb and fastboot flash super. (Should be around 8gb file)
Code:
Code:
sudo adb reboot bootloader
sudo fastboot flash super /path/to/patched_super.bin
sudo fastboot reboot
########################
Enjoy system r/w[/code]
Lposed
CPU Demensity 1080, can play most emulators (dolphin/athersx2) at 30-60 FPS,a really powerful gaming phone
Phone
Infinix Zero 5G Ant-Man and the Wasp Quantumania Edition
Any help please
Can elaborate this please. Im stuck at this step
Mtk-client has a user interface see photo
Step4 in mtk_GUI
Go to,
Read Partition(s) Tab and tick all boxes to be read/backup the partitions except data partition (internal storage)
Now you should have a backup of your files/.bin
Still can not change SELinux to permissive or install.... some madgisk modules..?? Assuming because the boot is reed only, wish system r/w worked on boot to as it contains the kennel..
Hi what version is your device? Is it v810? I was wondering if your device can boot into BROM mode.
Build number:
X6815C-H777A-S-GL-221010V451
Should work on
X6815
X6815B
And to get into BROM mode (to my understanding) on any mediatek CPU/phone simply power the device off with no USB connected...
Launch mtk_GUI with root, and it will ask to hold volume up or down while connecting the USB from a powered off state (try different button combinations)
Mtk _GUI is touchy!... with how it connects it usually takes me 2-3 attempts of rebooting and powering off my phone to get it connect/recognize in brom mode
(Might be worth noting)
If your Linux sysctl.conf has these security JIT settings
net.core.bpf_jit_harden=2
kernel.unprivileged_bpf_disabled=1
kernel.kexec_load_disabled=1
Or more...
mtk client will not recognize your devices... Simply move sysctrl.conf temporarily and reboot your Linux machine and try again
notreal456789 said:
Build number:
X6815C-H777A-S-GL-221010V451
Should work on
X6815
X6815B
And to get into BROM mode (to my understanding) on any mediatek CPU/phone simply power the device off with no USB connected...
Launch mtk_GUI with root, and it will ask to hold volume up or down while connecting the USB from a powered off state (try different button combinations)
Mtk _GUI is touchy!... with how it connects it usually takes me 2-3 attempts of rebooting and powering off my phone to get it connect/recognize in brom mode
(Might be worth noting)
If your Linux sysctl.conf has these security JIT settings
net.core.bpf_jit_harden=2
kernel.unprivileged_bpf_disabled=1
kernel.kexec_load_disabled=1
Or more...
mtk client will not recognize your devices... Simply move sysctrl.conf temporarily and reboot your Linux machine and try again
Click to expand...
Click to collapse
Damn sadly im on v810 now and it doesn't enter into BROM mode anymore or maybe am i doing something wrong but idk. I hope infinix will enable it again
Hnojohn said:
Damn sadly im on v810 now and it doesn't enter into BROM mode anymore or maybe am i doing something wrong but idk. I hope infinix will enable it again
Click to expand...
Click to collapse
This is why I don't update things, also it could be the setup Maby I'll post a Linux.iso with mtk client setup correctly
I still use Android apps from 2008 that still work on Android 12 fine