Related
UPDATE 2: Tutorial and Patched Boot.imgs available here.
UPDATE: Chainfire's suggestion to patch sepolicy in the ramdisk for Samsung LL ROMS works perfectly. For unknown reasons, ODIN flash would not work, but flashing the patched boot.img with TWRP allowed me to successfully achieve root with a fully stock kernel and SEAndroid Enforcing. All the information you need is in the sources I quote below. Once I am confident that everything is working fine, I will create another thread with a concise guide and my patched boot.img for those who don't want to get their hands dirty. In the meantime, anybody who sees this should know that the same process can be done with the P605 as well, with your native ROM instead of a ROM from a different region. Also, stock kernel means no wifi dropping problems either!
@garyd9
This thread is to discuss the possibility of rooting the Samsung Note 10.1 (2014 Edition) without resorting to a permissive kernel. The background information for this thread can be found from the following posts:
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Chainfire's method of patching the device's sepolicy with a reference device to give sudaemon the required permissions that open the doors for rooting and more.
http://forum.xda-developers.com/showpost.php?p=63250893&postcount=26
garyd9's application of Chainfire's idea to the Note 5, which appears to have worked successfully.
http://forum.xda-developers.com/showpost.php?p=63552454&postcount=2375
My attempt to replicate garyd9's method on the P607T, which failed.
http://forum.xda-developers.com/showpost.php?p=63555137&postcount=2376
garyd9's recommendation on how to troubleshoot.
And finally the results from following Gary's advice:
0 - Check
1 - Check
2 - Fail
Tools and Process: Listing all of them. The one I followed for this methodical approach is the first one. Including the others for context, in the hopes that it will indicate what the next step should be.
1) Carliv's Kitchen
Followed instructions, placed boot.img in the boot_resources folder, unpacked it with the tool, changed nothing, repacked with the same tool, made tar using "tar -cf boot_stock_repack.tar bootxxx.img" bootxxx.img is what Carliv generated, of course. To compare, made tar of the stock boot.img as well, naming it boot_stock.tar. Flashing boot_stock.tar works, device boots, no problems. Flashing the boot_stock_repack.tar fails with "Unsupport dev_type" on the device.
Additional Info:
------------------------------------------------
2) bootimg_tools
split_boot to extract the kernel and ramdisk and unpack the ramdisk. No warnings are issued, nothing suggests there is any problem.
repack_ramdisk to repack ramdisk, no problems here either.
mkbootimg to create new boot.img; no arguments are specified since apparently it would automatically create the right image.
tar -cf to create ODIN flashable tar.
Flashing this would succeed in ODIN, but the device would reboot in Download Mode with "Unable to boot normal mode" showing on the device. 3 suggests an explanation why.
3) To extract the kernel and ramdisk, used umkbootimg instead of split_boot from the same toolset. This time, it issued a warning about the original img being created with a non-standard mkbootimg, said I should edit mkbootimg.c before making the new image. Despite the warning, it also provided a mkbootimg command to use to ensure the new img is created correctly. Googling the warning suggested downloading android source code to get the mkbootimg.c file, but nothing beyond that on what needs to be done.
While not optimistic, I still tried the mkbootimg command it gave me, as well as with extra arguments to correct the addresses till boot_info in the toolkit matched for the stock and new images. SAME outcome as with 2.
4) Modding_My_Mind/SHM's toolset
This one claimed to automatically make the necessary corrections for a non-standard boot image and definitely did something different. Unlike the other generated images which were smaller in size than the original, this one was the same size. Making a tar and flashing it though failed with Unsupport dev_type showing on the device. I have contacted SHM to see if he can shed some light on this.
NOTE: In the thread where I got this from, when dealing with a non-standard image, his output seems to show this warning. BUT, I got no such warning when I did this on my image.
5) Carliv's as in the first item here. It generated a boot.img that matched in size and failed with the same error as the previous, suggesting it is definitely making SOME changes to the mkbootimg arguments to work with the 'non-standard stock image', BUT I have no idea what these changes are, nor where to look for them.
Next Step?
I never tried a full manual repacking of the ramdisk and generation of the image. Not sure if the error could be in the way the ramdisk is being repacked (which seems improbable, since its a gzip + cpio command that does this, not much to mess up there), or if its the way in which the new img is being created (seems probable, given that many arguments need to be passed here and Im using binaries that I do not know and understand at all).
I tried to look for other ways to create the img file, BUT pretty much everything keeps pointing to these same toolsets and binaries. With regards process, I have not been able to find anything on how to make 'manual adjustments' to the addresses/offsets.
Any advice on where to go/look next?
Click to expand...
Click to collapse
This thread is started to continue exploring this option specifically for the Note 10.1 (2014 Edition). The idea is to achieve root by modifying only the ramdisk and not touching the kernel, and definitely NOT going to the extreme step of using a permissive kernel.
Can you post a boot.img that's known good? I don't use kitchens, dining rooms, or even bathrooms. I use my own compiled tools... (Are you doing all this work in linux or using win-blows?)
I've attached "imgtools.zip." Within are the linux binaries I use for unpacking and repacking boot images. They should work under ubuntu 64-bit 14.04.
Here's some idea of how you might use them (again, linux..)
Code:
# assumes "boot.img" in the cwd is the original boot image.
mkdir stockboot
# unpack the boot image into a new directory called "stockboot"
unpackbootimg -i boot.img -o stockboot
That will dump a bunch of files into that new directory...
Now, to remake it:
Code:
cd stockboot
mkbootimg --kernel boot.img-zImage --ramdisk boot.img-ramdisk.gz --base `cat boot.img-base` --pagesize `cat boot.img-pagesize` --kernel_offset `cat boot.img-kerneloff` --ramdisk_offset `cat boot.img-ramdiskoff` --tags_offset `cat boot.img-tagsoff` --dt boot.img-dtb -o ../newboot.img
What that does is goes into the directory we unpacked the original image to, and then just puts it back together in the original directory under a new name (newboot.img.) For all the parameters, we just re-use the values and items extracted from the stock boot image. The new image won't be identical to the old one, but the sizes should be close.
garyd9 said:
Can you post a boot.img that's known good? I don't use kitchens, dining rooms, or even bathrooms. I use my own compiled tools... (Are you doing all this work in linux or using win-blows?)
Click to expand...
Click to collapse
tar of stock boot.img attached. Until Carliv's kitchen, all attempts were on Slackware 14.1. Only Carliv's was done on Win 10.
garyd9 said:
I've attached "imgtools.zip." Within are the linux binaries I use for unpacking and repacking boot images. They should work under ubuntu 64-bit 14.04.
Click to expand...
Click to collapse
Will take a shot at it tomorrow with your binaries and post results.
karthikrr said:
tar of stock boot.img attached. Until Carliv's kitchen, all attempts were on Slackware 14.1. Only Carliv's was done on Win 10.
Click to expand...
Click to collapse
I'm not going to talk about that. I have a semi-religious belief that anyone using windows to manipulate linux kernel images is BEGGING for trouble. (It's not that I'm anti-windows. I'm just against mixing the platforms.)
Anyway, followed my own directions to unpack and repack your boot.img. I took the resulting newboot.img and zip'd it up (and attached it here.) This is NOT a TWRP/CWM flashable zip. It's just archived to save space (and make XDA's file manager happy.)
I didn't see any strange messages about non-standard images or anything like that. In fact, the process was outright boring.
(FYI, I might not be capable of responding to messages again until late tomorrow night or Sunday...)
Code:
~/temp$ unpackbootimg -i boot.img -o stockboot
BOARD_KERNEL_CMDLINE console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3
BOARD_KERNEL_BASE 00000000
BOARD_PAGE_SIZE 2048
BOARD_KERNEL_OFFSET 00008000
BOARD_RAMDISK_OFFSET 02000000
BOARD_TAGS_OFFSET 01e00000
BOARD_DT_SIZE 1574912
oh, that might not boot for you. my repack cmdline doesn't pull in the cmdline from the kernel unpack. Add something like this to the mkbootimg cmdline:
Code:
--cmdline "`cat boot.img-cmdline`"
(You might have to actually type out the cmdline inside the quotes instead)
garyd9 said:
I didn't see any strange messages about non-standard images or anything like that. In fact, the process was outright boring.
Click to expand...
Click to collapse
Not surprised . Most tools available won't give this information. Its typically only available as a cosmetic feature. My work is derived from Xialou's as seen here but modified to work for Linux and ARM alike.
I have attached images showing me unpacking and repacking his stock boot.img from my device.
{
"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"
}
With that said, I have been researching this error, "unsupported dev_type", and most of what I have came across points to it being a specific issue with Odin itself. However, I can't really rule this out because his device does not have root so I presume he can't write the boot image to his boot partition using the dd command in a terminal to verify if it will boot up using this method. If it were to boot up then it would clearly point the problem towards the Odin program being used.
Sent from my Ascend Mate 2 using Tapatalk
---------- Post added at 02:21 PM ---------- Previous post was at 01:59 PM ----------
@karthikrr, when making an Odin compatible package you are using the command:
Code:
tar -cf
I don't own a Samsung device but I have helped build TWRP for some so given my experience shouldn't the command actually be:
Code:
tar -H ustar -c boot.img > Odin_boot.tar
Where Odin_boot.tar is the package used to install via Odin.
Please use that command i just shared with you and try again.
Sent from my Ascend Mate 2 using Tapatalk
garyd9 said:
oh, that might not boot for you. my repack cmdline doesn't pull in the cmdline from the kernel unpack. Add something like this to the mkbootimg cmdline:
Code:
--cmdline "`cat boot.img-cmdline`"
(You might have to actually type out the cmdline inside the quotes instead)
Click to expand...
Click to collapse
SHM said:
I don't own a Samsung device but I have helped build TWRP for some so given my experience shouldn't the command actually be:
Code:
tar -H ustar -c boot.img > Odin_boot.tar
Where Odin_boot.tar is the package used to install via Odin.
Please use that command i just shared with you and try again.
Click to expand...
Click to collapse
Short version: No luck!
Long version:
In all cases, just unpack stock boot.img and make new stock boot.img, no changes.
Gary, everything except for the ODIN flash was done on Linux for the following.
SHM, all tars created using your command.
1) Used Gary's tools following all instructions including cmdline to create garyboot.img and then .tar
2) Used SHM's tools to try again, this time with his tar cmd to create shmboot.tar
3) Found a mkbootimg binary in the P607T KK Source from Samsung's opensource portal. Used that to create P607Tboot.tar from the img unpacked by Gary's tools.
4) This might have been completely off-base, but ... Used xialou's mkboot-master source code; edited mkbootimg.c with the Non-Standard addresses from SHM's image above. Ran make to compile a new binary, used it to create recboot1.tar
5) umkbootimg from another toolset gave me a different set of addresses to change in the mkbootimg.c file, this time to change kernel offset, ramdisk offset and second offset. New binary again, after make clean and make, used it to create recboot2.tar
ODIN 3.10.6 failed with the same unsupport dev_type error with ALL of these images.
Tried the first two with ODIN 3.09, no difference, same error again.
Questions:
SHM, your image above, as well as the warning on umkbootimg both say Modify mkbootimg.c and try again ... Should I look into this more?
Is there ANY chance that the problem is not with mkbootimg, but with unpackbootimg?
SHM, you mentioned unsupport dev_type in context with ODIN problems. Where can I find more info on this? FWIW, I have never had ODIN problems before, flashing firmware updates and twrp on this tablet, as well as on my Note 2 phone. Can't think why only in this case, it should fail like this.
What are my alternatives to ODIN? Can I flash using twrp? I have never created a twrp flashable zip, so will go read up on that some now, but do you think it makes sense to try that? If not, are there any other methods of flashing to try before being absolutely sure the problem is with mkbootimg?
@karthikrr, if you have the latest twrp for your device than there is something you need to try to see if in fact this is a problem with Odin specifically. I want you to take your boot.img that has been unpacked and repacked but don't make it into a tar. Leave it as an image. Boot up TWRP then select Install. At the bottom right of your screen will be a button that says, zip. If you click on it you will see it change to, image. This allows you to install either a flashable zip or flash a boot/recovery.img. Select to install the boot.img. The next screen will ask you to select either the boot or recovery partition based upon the image you chosen. In this case, choose the boot partition. Swipe to proceed. When done, reboot your system. If your device boots up successfully then your problem lays with Odin. Let me know if these instructions are a bit confusing.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
@karthikrr, if you have the latest twrp for your device than there is something you need to try to see if in fact this is a problem with Odin specifically.
Click to expand...
Click to collapse
No confusion, I even have all the imgs loaded on the device to try this. Two reasons I did not try it yet, perhaps you can clarify whether these are legitimate concerns:
1) TWRP is formally not out for LL on my device yet. I, like everybody else out there, is using the latest KK img on this device and it SEEMS to be working properly. The only noticeable difference I have seen is that it seems to take a lot longer to get into twrp than usual. But I made some 5 backups of the device yesterday and all of them seemed to be fine. Given this is not official for LL, I wasn't sure if it was wise to try to flash an image from twrp.
2) I was also concerned that PERHAPS Odin is doing me a favour and aborting the flash because there was something wrong, and that if I went with twrp and it flashed it without any problems, I might find that it killed my device. I was discussing this with a friend (no experience with Android flashing, but a developer who knows these things) and he said it was highly unlikely that this would happen, as long as the img I was flashing was within the size limit for my device, which I believe is 11mb. All the images are 10.5mb. Thoughts?
karthikrr said:
No confusion, I even have all the imgs loaded on the device to try this. Two reasons I did not try it yet, perhaps you can clarify whether these are legitimate concerns:
1) TWRP is formally not out for LL on my device yet. I, like everybody else out there, is using the latest KK img on this device and it SEEMS to be working properly. The only noticeable difference I have seen is that it seems to take a lot longer to get into twrp than usual. But I made some 5 backups of the device yesterday and all of them seemed to be fine. Given this is not official for LL, I wasn't sure if it was wise to try to flash an image from twrp.
2) I was also concerned that PERHAPS Odin is doing me a favour and aborting the flash because there was something wrong, and that if I went with twrp and it flashed it without any problems, I might find that it killed my device. I was discussing this with a friend (no experience with Android flashing, but a developer who knows these things) and he said it was highly unlikely that this would happen, as long as the img I was flashing was within the size limit for my device, which I believe is 11mb. All the images are 10.5mb. Thoughts?
Click to expand...
Click to collapse
If the partition table between KK and LP does not vary on your device then it will be fine.
As for flashing a boot image to your boot partition via twrp, this will not brick your device. Worse case, device doesn't get past the bootloader or the boot animation. In this case, use twrp to install your stock boot.img to your boot partition.. If you have a backup of your boot image then restore that. Either way you will be OK.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
If the partition table between KK and LP does not vary on your device then it will be fine.
As for flashing a boot image to your boot partition via twrp, this will not brick your device. Worse case, device doesn't get past the bootloader or the boot animation. In this case, use twrp to install your stock boot.img to your boot partition.. If you have a backup of your boot image then restore that. Either way you will be OK.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
IT WORKS!!!
Flashed a stock boot.img using TWRP to be safe, was fine. Patched the ramdisk again, created a new patchedboot.img using the binary I pulled from the P607T sources, crossed my fingers and flashed it with TWRP, the device booted successfully. There was a SEAndroid Not Enforcing; Set Warranty Bit Kernel message while it booted, but I don't care about Knox. Once I confirmed that it booted and worked alright, back to recovery, flashed SuperSU Beta 2.52, rebooted, and I HAVE ROOT!!!
No idea why Odin would fail to flash, but confirmed working with TWRP. Do you know what the policy is on me creating a thread and uploading my patchedboot.img for others to use? I am no developer, and I have no idea if the rules prohibit me from putting this up. I do know though that not everybody is going to go through this whole manual process to get root, and too many are resorting to permissive kernels to get root. Ideally, I will also repeat this process is someone sent me a P605 boot.img, so they too can have root with stock kernel. Just not sure where this thread should go, and if I can even make one.
In anycase, THANK YOU SO MUCH BOTH OF YOU FOR TAKING THE TIME TO WALK ME THROUGH THIS! Much appreciated
Glad you got it working. If you want to post the image, I'd suggest posting in the dev section for the device. (If it's just a repack of the stock kernel, don't use the original dev...) Yes, it is allowed to do that. Being that you aren't recompiling anything, there's no need for you to post any source code (but it might be nice to link to the source from samsung's site. We all know that Samsung doesn't update that anyway.)
Take care
Gary
Thanks for the suggestions on how and where to post. I think I will take the time to write out a decent tutorial and then post it with this image in the dev forum. Im sure the P605 users will also want to do this with theirs, so they are not stuck with an unsecure kernel!
karthikrr said:
Thanks for the suggestions on how and where to post. I think I will take the time to write out a decent tutorial and then post it with this image in the dev forum. Im sure the P605 users will also want to do this with theirs, so they are not stuck with an unsecure kernel!
Click to expand...
Click to collapse
Good luck with your future endeavors. I'm currently fighting with sepolicy right now with my CM13 builds lol. Whole other battle right there haha.
Sent from my Ascend Mate 2 using Tapatalk
THIS GUIDE IS FOR THE MOTO G6 PLUS ONLY
2: Returning to Stock
If for any reason your phone is no longer functioning properly such as a bootloop (the phone is restarting itself over and over), "Can't Load Android System," "Startup Failed", or any such error you can fix this by flashing the stock firmware using fastboot.
I have taken stock firmware version OPW27.113-89 and packaged it with a few extras. XDA Member luiz_neto has provided a modified logo.bin that removes the unlocked bootloader warning during boot. A special thanks to XDA Member lohanbarth for providing the stock firmware. I have included the fastboot file for Windows, Linux and Mac users. Windows users can run the .bat file to execute all the necessary commands. For Linux and Mac users, I have included a bash script. You will need access to a PC and connect your phone via a USB cable.
*Downloads:
Modified Stock Firmware OPW27.113-89: (Download)
MD5: 3a1d984a8a3d0c57fb21931a8004eb27
Instructions:
*On your phone:
2A. With the phone powered off(even if for just a moment between the phone rebooting) hold the Power button and the Volume Down(Vol -) at the same time. You should boot into what is called the bootloader. It should display information on the screen and state "AP Fastboot Flash Mode" in orange lettering.
*On your PC:
2B: Extract the firmware which is in tar.xz container/file extension. Windows user probably need to use Winrar, 7Zip or PeaZip to extract the file.
2C: Using Windows Explorer, navigate to the folder EVERT_OPW27.113-89_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml and click on it to open it.
2D: Hold the Shift Key on your Keyboard. While holding Shift, Right Click in the window(not on the file). Depending on your windows version you should see either "Open PowerShell Window here" or "Open Command Window here." Select which ever one applies.
2E: You will see a black and white screen or a blue and white screen. The steps are the same no matter which screen you see. Simply type(or copy and paste) the following command:
Windows:
Code:
flash_rom.bat
For Linux and Mac you need to make the script file executable. It will make the fastboot binary executable for you. From a terminal run these 2 commands one at a time:
Linux:
Code:
chmod a+x flash_rom.sh
./flash_rom.sh
Mac:
Code:
chmod a+x flash_rom_mac.sh
./flash_rom_mac.sh
Your phone should reboot on it's own. If for some reason it doesn't try tapping the enter key on your keyboard or use the volume keys to make sure “Start” is selected on the right side of the phone and pres the power key on the phone. It should successfully boot the stock firmware.
Xplorer4x4 Hello good afternoon is on is corrupted When it unzips it says that header is corrupted! @Xplorer4x4
carlosgeraldo said:
Xplorer4x4 Hello good afternoon is on is corrupted When it unzips it says that header is corrupted! @Xplorer4x4
Click to expand...
Click to collapse
Did you try to download the package again?
Does anyone know whether It's possible to remove the "Your device has loaded a different operating system." after flashing stock rom through fastboot and relocking bootloader? I was looking to sell the phone...
Mara-X said:
Does anyone know whether It's possible to remove the "Your device has loaded a different operating system." after flashing stock rom through fastboot and relocking bootloader? I was looking to sell the phone...
Click to expand...
Click to collapse
Flash the stock firmware in my op.
Sent from my Moto G6 Plus using XDA Labs
Xplorer4x4 said:
Flash the stock firmware in my op.
Sent from my Moto G6 Plus using XDA Labs
Click to expand...
Click to collapse
No, I'm not talking about the unlocked bootloader warning, but the message that appears after you lock the bootloader. "Your device has loaded a different operating system"
Mara-X said:
No, I'm not talking about the unlocked bootloader warning, but the message that appears after you lock the bootloader. "Your device has loaded a different operating system"
Click to expand...
Click to collapse
I have never relocked my bootloader so I can't say for sure but this sounds out of the ordinary. Did it boot fine with an unlocked bootloader?
Sent from my Phh-Treble vanilla using Tapatalk
weazie said:
Did you try to download the package again?
Click to expand...
Click to collapse
I found the error: it was in my PC I started a program to fix the registry and after that unzipped the file normally!
Mara-X said:
No, I'm not talking about the unlocked bootloader warning, but the message that appears after you lock the bootloader. "Your device has loaded a different operating system"
Click to expand...
Click to collapse
Hi! have you succeed with your issue flashing this stock firmware ?
Does this stock firmware helps to remove warnings "This device has loaded a different operating system", and "Verity mode disabled" during boot?
And the worst thing is the message "System integrity compromized" and hens - GooglePay disabled and no software updates., when bootloader is re-locked?
MrMatnenko said:
Hi! have you succeed with your issue flashing this stock firmware ?
Does this stock firmware helps to remove warnings "This device has loaded a different operating system", and "Verity mode disabled" during boot?
And the worst thing is the message "System integrity compromized" and hens - GooglePay disabled and no software updates., when bootloader is re-locked?
Click to expand...
Click to collapse
Same problem here. I hate this messages
<bootloader> flash permission denied
friends, any command I give appeared this, someone knows how to solve?
Failed anything I've tried... Can you help @Xplorer4x4 ?
andreym_costa said:
Failed anything I've tried... Can you help @Xplorer4x4 ?
Click to expand...
Click to collapse
Shows the message "Failed Remote ' ' and "Flash permission denied"
andreym_costa said:
Shows the message "Failed Remote ' ' and "Flash permission denied"
Click to expand...
Click to collapse
You MUST provide MORE information! Screenshots, a detailed error description and not only a piece of your error.
WoKoschekk said:
You MUST provide MORE information! Screenshots, a detailed error description and not only a piece of your error.
Click to expand...
Click to collapse
I'm trying again... And now seeing this, can you help?
{
"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"
}
andreym_costa said:
I'm trying again... And now seeing this, can you help?
Click to expand...
Click to collapse
Please follow my guide below. That would be much easier I think, because it seems you are doing several things wrong.
1. download ADB/Fastboot tools from here and extract the downloaded zip to 'C:\' to create the path 'C:\platform-tools'
2. download your current firmware build here.
You use 116-16-22 but the latest build is 11-16-29 for RETBR.
3. extract the firmware.zip to 'C:\platform-tools'
Watch out to extract only single files and images to that path and do not create a subfolder => see screenshot attached
4. extract attached flashfile.zip to 'C:\platform-tools'
5. open 'C:\platform-tools' in Explorer and type 'cmd' in the address bar and hit 'Enter'
=> opens a new cmd window
6. boot your Moto into fastboot mode, connect it to your PC and run 'fastboot devices'
=> output: <SERIAL-NO> fastboot
7. execute 'flashfile.bat' and start flashing
WoKoschekk said:
Please follow my guide below. That would be much easier I think, because it seems you are doing several things wrong.
1. download ADB/Fastboot tools from here and extract the downloaded zip to 'C:\' to create the path 'C:\platform-tools'
2. download your current firmware build here.
You use 116-16-22 but the latest build is 11-16-29 for RETBR.
3. extract the firmware.zip to 'C:\platform-tools'
Watch out to extract only single files and images to that path and do not create a subfolder => see screenshot attached
4. extract attached flashfile.zip to 'C:\platform-tools'
5. open 'C:\platform-tools' in Explorer and type 'cmd' in the address bar and hit 'Enter'
=> opens a new cmd window
View attachment 5654883
6. boot your Moto into fastboot mode, connect it to your PC and run 'fastboot devices'
=> output: <SERIAL-NO> fastboot
7. execute 'flashfile.bat' and start flashing
Click to expand...
Click to collapse
I tried again and now these errors occur. I thought it might be a locked bootloader, but apparently everything is ok, at startup it has an unlocked bootloader warning. And really thank you to helping me.
andreym_costa said:
I tried again and now these errors occur. I thought it might be a locked bootloader, but apparently everything is ok, at startup it has an unlocked bootloader warning. And really thank you to helping me.
Click to expand...
Click to collapse
No, your bootloader isn't unlocked. The OEM-Unlock toggle would be inactive (greyed out) in case of an unlocked bootloader.
Looking for Official firmware for my AllCall S1 X
Tried to flash original firmware but for non X version, which has different display (version from date 20180817)
After flashing my phone boots up but i have black screen - because i have newer X version with different LCD...
Anybody from AllCall or some AllCall S1 X user can post official rom ?
(When you go to settings-about phone you should see ALLCALL_S1_X - firmware version should be from date 20180912)
Thank you very much !
[screenshot - about phone] ibb.co/bKiuNA
{
"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"
}
G_0phy said:
Looking for Official firmware for my AllCall S1 X
Tried to flash original firmware but for non X version, which has different display (version from date 20180817)
After flashing my phone boots up but i have black screen - because i have newer X version with different LCD...
Anybody from AllCall or some AllCall S1 X user can post official rom ?
(When you go to settings-about phone you should see ALLCALL_S1_X - firmware version should be from date 20180912)
Thank you very much !
[screenshot - about phone] ibb.co/bKiuNA
Click to expand...
Click to collapse
Have you found the firmware, I need it too.
No I Wrote to AllCall support / forum several times but they weren't online for more than 45 days...
Finally ! - Also I made a how to video : https://www.youtube.com/watch?v=OehWqUvGb78
Warning warning warning!!!
WARNING! To anyone using this video, the creator of the video was a bit reckless and FAILED to inform you about a number of CRITICAL items, and you may end up messing up your phone if you do not do the following:
First of all, you cannot even do a Write Memory flash unless you first have the SCATTER text file (MT6580_Android_scatter.txt) and the PRE-LOADER file (preloader_a600w_v1_a_hxgj_ac18_allcall_o.bin) for the S1 X phone.
Where do you get them? Well these are EXACTLY the same as for the S1 phone. So you must first download the firmware for the S1 phone (search online and you will find it, usually in zip file format). Extract the S1 firmware from the zip and save ONLY the scatter file and the preloader file. Delete everything else. Then download the EMMC-USER file from this load from video. Note that it is a compressed file in 7-Zip format. So you SHOULD use 7 Zip software to unzip it (search online and you will find it).
But BEFORE you flash this EMMC file, you MUST first READBACK and SAVE certain partitions from the phone using the SP Flash Tool. Use the Readback tab. You will need to open the scatter file in a text editor to find the location of the TEE1, TEE2 and NVDATA partitions (the linear start address and partition size are the numbers you want to note for each of these partitions). Read these partitions back using the SP Flash Tool and save them in the same folder where you saved the scatter file and the preloader. If you do not save these partitions, YOU WILL LOSE YOUR EMEI NUMBERS AND YOU WILL GET AN ANNOYING AND PERMANENT MESSAGE IN RED (unwritten tee key unwritten google key) ON THE BOTTOM OF YOUR PHONE SCREENS AFTER YOU FLASH THE EMMC-USER FILE.
After you have readback and saved the Tee1, Tee2 and Nvdata partitions, you can proceed to flash the EMMC-USER file via the Write Memory tab as described in the video (but you will first need to check the preloader box in the Download tab otherwise Sp Flash Tool won't let you flash the EMMC-USER file).
Once you have flashed the EMMC-USER file, you should then flash the Tee1, then the Tee2, then the Nvdata files that you saved from your phone.
Now you can restart your phone and everything should be fine.
IF YOU DID NOT BACKUP YOUR TEE KEYS AND NVDATA, YOU CAN FIX THIS ANNOYING PROBLEM USING THE SN WRITE TOOL (https://androidmtk.com/use-sn-write-tool).
They have already updated their website - they added S1 X rom (with scatter and other things included) http://bbs.allcall.hk/thread-10845-1.html
You can remove that red text when you root your phone (which is now possible when they uploaded rom for S1 X)
When you have root you can hide the red text too i think...
How to root MTK device https://www.youtube.com/watch?v=sATW0cPT_uQ
(make your custom boot.img file and flash it with WHOLE ROM - don't flash just boot.img as shown in video - so use original scatter file and flash everything except original boot.img - use your patched file and rename it as boot.img. then install magisk.apk on your device, now your device should be rooted)
How to hide text - use SP flash tool they have on their web site - enable generate BT and WIFI from IMEI - and write your imei which is on the phones battery case...
Tee1 and Tee2 lost
I have come upon this issue with an Oukitel K10 as well now. Having followed the EXACT procedure provided by the manufacturer themselves, I now have the "tee key" message on screen.
No amount of fiddling about with the SN WRITE tool appears to have fixed this either.
CVAngelo said:
WARNING! To anyone using this video, the creator of the video was a bit reckless and FAILED to inform you about a number of CRITICAL items, and you may end up messing up your phone if you do not do the following:
First of all, you cannot even do a Write Memory flash unless you first have the SCATTER text file (MT6580_Android_scatter.txt) and the PRE-LOADER file (preloader_a600w_v1_a_hxgj_ac18_allcall_o.bin) for the S1 X phone.
Where do you get them? Well these are EXACTLY the same as for the S1 phone. So you must first download the firmware for the S1 phone (search online and you will find it, usually in zip file format). Extract the S1 firmware from the zip and save ONLY the scatter file and the preloader file. Delete everything else. Then download the EMMC-USER file from this load from video. Note that it is a compressed file in 7-Zip format. So you SHOULD use 7 Zip software to unzip it (search online and you will find it).
But BEFORE you flash this EMMC file, you MUST first READBACK and SAVE certain partitions from the phone using the SP Flash Tool. Use the Readback tab. You will need to open the scatter file in a text editor to find the location of the TEE1, TEE2 and NVDATA partitions (the linear start address and partition size are the numbers you want to note for each of these partitions). Read these partitions back using the SP Flash Tool and save them in the same folder where you saved the scatter file and the preloader. If you do not save these partitions, YOU WILL LOSE YOUR EMEI NUMBERS AND YOU WILL GET AN ANNOYING AND PERMANENT MESSAGE IN RED (unwritten tee key unwritten google key) ON THE BOTTOM OF YOUR PHONE SCREENS AFTER YOU FLASH THE EMMC-USER FILE.
After you have readback and saved the Tee1, Tee2 and Nvdata partitions, you can proceed to flash the EMMC-USER file via the Write Memory tab as described in the video (but you will first need to check the preloader box in the Download tab otherwise Sp Flash Tool won't let you flash the EMMC-USER file).
Once you have flashed the EMMC-USER file, you should then flash the Tee1, then the Tee2, then the Nvdata files that you saved from your phone.
Now you can restart your phone and everything should be fine.
IF YOU DID NOT BACKUP YOUR TEE KEYS AND NVDATA, YOU CAN FIX THIS ANNOYING PROBLEM USING THE SN WRITE TOOL (https://androidmtk.com/use-sn-write-tool).
Click to expand...
Click to collapse
Hi. Got my A40 rooted and wasen't happy about the look of the boot logo & warning text, so I did some changes to it.
WARNING:
THIS WILL TRIP KNOX SO DON'T FLASH UNLESS YOU KNOW WHAT YOU'RE DOING.
THIS IS MEANT FOR USERS THAT UNLOCKED BOOTLOADER AND GOT KNOX WARRANTY BIT BLOWN ALREADY
UPDATE, TWRP METHOD
----------------------------------------------------------------------------------------------------------------------------------------------
Now with warning (booting_warning.jpg) completly removed so that we can use full screen custom logos.
1/ Flash "View attachment A405-red_warn_remover.zip".
2/ Reboot to recovery.
3/ Flash "View attachment A405_logo_leafes.zip"
{
"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"
}
----------------------------------------------------------------------------------------------------------------------------------------------
Wanna make your own logo mod?
Make sure that the images you're doing has the same characteristics as the original files.
Raplace the images in "A405_logo_leafes.zip" and rename the zip to whatever fits.
Edit the "ui_print" in the update-binary if you wish, but please keep the credit to @moluntic for this awesome script.
(Original thread):[Tutorial][Boot Logo Changer]
read the info there as you can easily brick your phone if it's done wrong.
Remember that param partition acts as an image cache for bootloader and is indeed part of the bootloader partitions.
With that said, please don't share files unless you've tested it yourself first.
----------------------------------------------------------------------------------------------------------------------------------------------
OLDER METHOD:
Original ---> Changed to:
Original---> Changed to:
This blacked out so that it won't show on the black logo background.
Unzip View attachment SM-A405FN-param_mod.tar.zip and put the tar.md5 in AP slot in Odin. Connect phone in download mode and start flash.
--------------------------------------------------------------------------------------------------------------------------------------------------------
Hi
To flash this do we need to reset/wipe after? I spent already too much time customizing this device, don't wanna do everything all over again
The warning that warns about booloader and asks to press power couldn't also be blackened or even replaced it with something nicer ((maybe text in black "Custom firmware initializing" ))? If I don't press power device continues boot anyway after a few seconds.
Can you give any tips, or any special care when creating/modified bootlogo? Or, if you have time to make more versions it will be appreciated
Many thanks.
Please do for TWRP
Got no feedback, so I decided to create my own bootlogo and sucessfully flashed it using Odin.
Even put the Magisk logo on it :laugh:
A quick how-to using Windows:
You know the drill, if you manage to damage your device when doing this, it's your own fault!
1. Download the firmware for your device from your preferred server (samfrew updato , select region, version), alternatively jump to the end for faster approach, but you may need knowledge described in next steps anyway
2. Have installed 7zs
3. Right-click the firmware file > 7Zip ZS > Open Archive > then double-click (dc) file that starts "BL.." > again dc param.bin.lz4 > again dc param.bin > extract all files
4. Files to customize are:
booting_warning.jpg
logo.jpg
svb_orange.jpg
Use favorite image editor (Paint works!)
Make sure you keep the default resolution and do not create much bigger files than the originals, a little bit smaller or bigger it's okay, but not too much.
5. Again using 7zs create a tar archive format with the files you edited and the rest you have extracted before, name the archive param.bin (literal, NOT param.bin.tar)
(7Zip ZS > Add to Archive > Archive Format: tar > Archive (name): param.bin)
6. And then again, create another tar file with the param.bin in it (archive name may be anything)
7. Using Odin, load the tar file you created on the previous step to the AP slot, connect the phone in download mode and flash
Alternatively, to save data and time download bootlogo mod from first post, just extract files, edit and repack again using similar manner as described above
(in the end you should have a file with tar extension instead of MD5 because archive does not have MD5 checksum attached, so Odin will not check data integrity)
I tried to load file but says error binary is invalid
Sparko612 said:
I tried to load file but says error binary is invalid
Click to expand...
Click to collapse
What are you trying to do? Flashing bootlogo mod from first post or creating your own?
pomaxa said:
Please do for TWRP
Click to expand...
Click to collapse
I've been working some more on this "project" and twrp flashable is working. I will upload tomorrow hopefully.
I managed to remove the black warning as well so that we can have full screen custom logos, like this:
There will be two zip's to flash the first time.
One with stock param, but witout the "red warning" and one zip to finally change the logo / svb_orange by unpacking param in device and replace the images inside.
This will be easier, as we from there on only have to replace two images in a zip to get new flashable logo.
Have already done
pomaxa said:
Have already done
Click to expand...
Click to collapse
Guess I was late then
Anyway, I've updated OP with new method, files and instructions.
tys0n said:
I managed to remove the black warning as well so that we can have full screen custom logos, like this:
View attachment 4846485 View attachment 4846487
Click to expand...
Click to collapse
Couldn't we had 'fullscreen custom logos' before?
Why did you choose to leave the message of the "svb_orange"? We all know bootloader is unlocked, message is useless and undesirable since boot continues anyway after a few secs (no need to press power).
Anyway, that's what I've done on mine, replaced it with a nice screen, acting as second (boot)logo.
Tony il Capo said:
Couldn't we had 'fullscreen custom logos' before?
Why did you choose to leave the message of the "svb_orange"? We all know bootloader is unlocked, message is useless and undesirable since boot continues anyway after a few secs (no need to press power).
Anyway, that's what I've done on mine, replaced it with a nice screen, acting as second (boot)logo.
Click to expand...
Click to collapse
That message doesn't really bother me so I just kept it.
We could have used full screen, but it would have looked like this cause the image is still there, just blacked out.
tys0n said:
We could have used full screen, but it would have looked like this cause the image is still there, just blacked out.
View attachment 4847521
Click to expand...
Click to collapse
Yes, of course, I forgot that it just gets overlayed on top of logo image, because my logo is mainly black and booting_warning is black too, it's there but invisible.
Tony il Capo said:
What are you trying to do? Flashing bootlogo mod from first post or creating your own?
Click to expand...
Click to collapse
Sorry I was trying to flash mod from first post
Thanks
Sent from my SM-A305GT using XDA Labs
Tony il Capo said:
Got no feedback, so I decided to create my own bootlogo and sucessfully flashed it using Odin.
Even put the Magisk logo on it :laugh:
A quick how-to using Windows:
You know the drill, if you manage to damage your device when doing this, it's your own fault!
1. Download the firmware for your device from your preferred server (samfrew updato , select region, version), alternatively jump to the end for faster approach, but you may need knowledge described in next steps anyway
2. Have installed 7zs
3. Right-click the firmware file > 7Zip ZS > Open Archive > then double-click (dc) file that starts "BL.." > again dc param.bin.lz4 > again dc param.bin > extract all files
4. Files to customize are:
booting_warning.jpg
logo.jpg
svb_orange.jpg
Use favorite image editor (Paint works!)
Make sure you keep the default resolution and do not create much bigger files than the originals, a little bit smaller or bigger it's okay, but not too much.
5. Again using 7zs create a tar archive format with the files you edited and the rest you have extracted before, name the archive param.bin (literal, NOT param.bin.tar)
(7Zip ZS > Add to Archive > Archive Format: tar > Archive (name): param.bin)
6. And then again, create another tar file with the param.bin in it (archive name may be anything)
7. Using Odin, load the tar file you created on the previous step to the AP slot, connect the phone in download mode and flash
Alternatively, to save data and time download bootlogo mod from first post, just extract files, edit and repack again using similar manner as described above
(in the end you should have a file with tar extension instead of MD5 because archive does not have MD5 checksum attached, so Odin will not check data integrity)
Click to expand...
Click to collapse
Thank you Bro !!
It works like a charm.
Very happy with this mod
Fred.
i know how to make it work with Odin but i was wondering if with the stock recovery it's possible to sign an update.zip containing this mod....
i tried an old zip signer with no luck ( probably it was with an old Android version).
tys0n said:
OLDER METHOD:
View attachment 4790669 Original ---> Changed to: View attachment 4790670
View attachment 4790672 Original---> Changed to: View attachment 4790673
View attachment 4790671
This blacked out so that it won't show on the black logo background.
Unzip View attachment 4790675 and put the tar.md5 in AP slot in Odin. Connect phone in download mode and start flash.
Click to expand...
Click to collapse
Hello. I installed this patch last july (release without leaves):
- is that version (no-leaves) still available / usable with ASJ firmware ?
- in general, how could I revert mod to the original ? Flashing full stock firmware doesn't affect bootloader area, it seems
I don't have TWRP so I'm talking about Odin releases
Thanks a lot for your work
tys0n said:
[...]
Click to expand...
Click to collapse
Hi tys0n, nice work!! Could that procedure (or something similar) also work for a A70 (SM-705FN/DS) with TWRP?
Swordfishx86 said:
Hi tys0n, nice work!! Could that procedure (or something similar) also work for a A70 (SM-705FN/DS) with TWRP?
Click to expand...
Click to collapse
Twrp with an update.zip style
Or flash with Odin
Perhaps files and directories are différents...
Envoyé de mon SM-A405FN en utilisant Tapatalk
fredapied said:
Perhaps files and directories are différents...
Click to expand...
Click to collapse
There is no param.bin in the BL-file of A70s firmware ...
I just received an Ulefone armor 18t and I'm trying to get the phone rooted through a magisk patched boot image. Whenever I attempt to flash the patched image, the phone always ends up bootlooping and gives me the 'android system may be corrupt' message. I've tried flashing an empty vbmeta in order to try to disable secure boot, but it still isn't working.
Does anyone have any other suggestions or have any ideas as to what could be causing my phone to not boot?
Posted this on reddit; just reposting this for more exposure
EDIT: I managed to root my phone by patching my boot.img with an older version of magisk (24.3) and then updating to v25 after.
I used Magisk 24.3 to patch my boot.img per your suggestion, but when I flashed it, something went wrong and now I'm stuck in a boot loop. Factory reset doesn't help, and I can't get into fastboot either. How did you get out of your boot loop?
foamrotreturns said:
I used Magisk 24.3 to patch my boot.img per your suggestion, but when I flashed it, something went wrong and now I'm stuck in a boot loop. Factory reset doesn't help, and I can't get into fastboot either. How did you get out of your boot loop?
Click to expand...
Click to collapse
Are you the guy that replied to me on the reddit thread? Sorry about the slow replies but I put a response in that should help hopefully. I'll repost it here just in case:
Well, to get back into fastboot, I had to hold the power button until it shuts off and spam the volume up button super fast until you see either the recovery or the boot selection options
I should mention that the process is super finicky and you'll most likely fail a couple of times. I don't remember needing a vbmeta to root the device but i did try one here, using this command (in the bootloader, not fastbootd): fastboot flash --disable-verity --disable-verification vbmeta "name of vbmeta"
If that doesn't work, you can try using the stock vbmeta with the command above, or try this command with the stock or null vbmeta: fastboot flash vbmeta "name of stock or empty vbmeta"
Have you tried flashing boot.img in fastboot to sort out bootlooping?
I managed to get it booting again, but I'm now dealing with an entirely different problem. The FLIR camera is highly unstable (it frequently crashes, and sometimes stops working completely until I reboot the phone), and I cannot get the infrared image to line up with the camera image. I've tried the automatic calibration and the image realignment utility. No matter what I do, the infrared image is always way too big to line up with the camera image.
This only started happening after I flashed the phone back to "factory" using the ROM provided by Ulefone on their Google Drive. The ROM that was on the phone when it arrived didn't have any problems, but I don't have a backup of that because I assumed that it would be the same as what I could get from Ulefone. But the ROM that Ulefone provides has a bunch of weird stuff, like a red "未写入google key 和tee key" watermark on the screen that can only be removed by running a command in a root adb shell, as well as this thing with the FLIR camera.
Anyone know where I can get a copy of the ROM that was actually installed on the phone when it shipped, as opposed to the one provided by Ulefone on their Google Drive?
Generic123. said:
Are you the guy that replied to me on the reddit thread? Sorry about the slow replies but I put a response in that should help hopefully. I'll repost it here just in case:
Well, to get back into fastboot, I had to hold the power button until it shuts off and spam the volume up button super fast until you see either the recovery or the boot selection options
I should mention that the process is super finicky and you'll most likely fail a couple of times. I don't remember needing a vbmeta to root the device but i did try one here, using this command (in the bootloader, not fastbootd): fastboot flash --disable-verity --disable-verification vbmeta "name of vbmeta"
If that doesn't work, you can try using the stock vbmeta with the command above, or try this command with the stock or null vbmeta: fastboot flash vbmeta "name of stock or empty vbmeta"
Click to expand...
Click to collapse
Yes, I was the person replying to you on Reddit. Thank you again for the help over there.
wenyendev said:
Have you tried flashing boot.img in fastboot to sort out bootlooping?
Click to expand...
Click to collapse
The problem was that I couldn't even get to fastboot. The device was softbricked. I had to use SP Flash Tool to get it back into a condition where I could even use fastboot at all.
foamrotreturns said:
I managed to get it booting again, but I'm now dealing with an entirely different problem. The FLIR camera is highly unstable (it frequently crashes, and sometimes stops working completely until I reboot the phone), and I cannot get the infrared image to line up with the camera image. I've tried the automatic calibration and the image realignment utility. No matter what I do, the infrared image is always way too big to line up with the camera image.
This only started happening after I flashed the phone back to "factory" using the ROM provided by Ulefone on their Google Drive. The ROM that was on the phone when it arrived didn't have any problems, but I don't have a backup of that because I assumed that it would be the same as what I could get from Ulefone. But the ROM that Ulefone provides has a bunch of weird stuff, like a red "未写入google key 和tee key" watermark on the screen that can only be removed by running a command in a root adb shell, as well as this thing with the FLIR camera.
Anyone know where I can get a copy of the ROM that was actually installed on the phone when it shipped, as opposed to the one provided by Ulefone on their Google Drive?
Yes, I was the person replying to you on Reddit. Thank you again for the help over there.
The problem was that I couldn't even get to fastboot. The device was softbricked. I had to use SP Flash Tool to get it back into a condition where I could even use fastboot at all.
Click to expand...
Click to collapse
I am no specialist in unbricking devices. But you may try as follows
- Download the ROM, GApps (Optional), Magisk (Optional).
- Wipe System, Data, Dalvik, Cache.
- Flash the ROM, GApps (Optional), Magisk (Optional).
- Reboot and Enjoy.
I tried to root mine, but I was unsuccessful.
I used mtkclient to pull out the boot_b.img and vbmeta_b.img from my device. Having these backups were helpful to get me out of bootloops.
I tried 3 different magisk versions: 24.3, 25.2, and a patched version linked in mtkclient's github readme.
I also tried the vbmeta recommendations described by OP in this thread, but I still could not get myself past the 'android system may be corrupt' loop.
I reverted my boot and vbmeta partitions back to the version I backed up via mtkclient, and escaped the bootloop. But no root.
Interestingly, the checksum of the boot_b.img in my phone does not match the checksum of the boot.img provided in Ulefone's official release. I am assuming my phone received an OTA update while the version in the Ulefone official GoogleDrive remained old, but I was not able to track down a changelog for rom updates/release history.
Unsure what to try next, open to ideas.
Hello, try this page i think the firmware is more update (have all models), is also from Ulefone.
454.93 GB folder on MEGA
905 files and 654 subfolders
mega.nz
I have donwload a new firmware to my Armor X7 Pro and is very stable.
914mrx said:
Hello, try this page i think the firmware is more update (have all models), is also from Ulefone.
454.93 GB folder on MEGA
905 files and 654 subfolders
mega.nz
I have donwload a new firmware to my Armor X7 Pro and is very stable.
Click to expand...
Click to collapse
I checked the Mega link you provided, and the latest version for the Power Armor 18T is the same as in the Ulefone Google Drive location. I did not compare checksums though, so I cannot confirm the content is identical.
Where did you find this mega folder link? Any chance Ulefone also publishes a changelog or provides older firmware releases in the same location you found the Mega link?
Hello, found this link on 4PDA a long time ago, about the others questions i don´t know. Sorry.
I spent whole night doing everything but all failed. Unlocked OEM and Usb debugging enabled, tried kingroot, vroot, supersu, downloaded drivers and everything...but somehow I couldn't get through any of it.
Any idea anyone how to do this?
Here's why the phone is not being rooted as per the customer service.
{
"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"
}
914mrx said:
Hello, try this page i think the firmware is more update (have all models), is also from Ulefone.
454.93 GB folder on MEGA
905 files and 654 subfolders
mega.nz
I have donwload a new firmware to my Armor X7 Pro and is very stable.
Click to expand...
Click to collapse
hello,
i download ROM file from mega. I have SPMDT tool. Scatter files can be to set. DA files is not correct to select. What is wrong?
Hello, i don´t know, there is also a video and a instruction sheet, as I said on Armor 7 Pro everything went well 100%.
914mrx said:
Hello, i don´t know, there is also a video and a instruction sheet, as I said on Armor 7 Pro everything went well 100%.
Click to expand...
Click to collapse
Hello,
I am solved problem with upgrade. Now have problem with FLIR kamera. No have icon for start IR camera. I can't start it.I think that new upgrade no made for all ulefone model.
How is Foamrotreturns solved problem with FLIR camera?
Samo-z said:
Hello,
I am solved problem with upgrade. Now have problem with FLIR kamera. No have icon for start IR camera. I can't start it.I think that new upgrade no made for all ulefone model.
How is Foamrotreturns solved problem with FLIR camera?
Click to expand...
Click to collapse
Were you able to root the phone and flash custom ROM?
I am trying to rot my mediatek device following the instruction on this page:-
Unlock Bootloader on MediaTek Devices using MTKClient
In this comprehensive tutorial, we will show you detailed steps to unlock the bootloader on your MediaTek device using MTKClient.
Everything has went smooth but I am getting I/O error and I am not sure how do i unlock bootloader, and hnce install TWRP to install a better ROM.
Here is the log:-
Port – Device detected
Preloader – CPU: MT6877(Dimensity 900)
Preloader – HW version: 0x0
Preloader – WDT: 0x10007000
Preloader – Uart: 0x11002000
Preloader – Brom payload addr: 0x100a00
Preloader – DA payload addr: 0x201000
Preloader – CQ_DMA addr: 0x10212000
Preloader – Var1: 0xa
Preloader – Disabling Watchdog…
Preloader – HW code: 0x959
Preloader – Target config: 0xe0
Preloader – SBC enabled: False
Preloader – SLA enabled: False
Preloader – DAA enabled: False
Preloader – SWJTAG enabled: False
Preloader – EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader – Root cert required: False
Preloader – Mem read auth: True
Preloader – Mem write auth: True
Preloader – Cmd 0xC8 blocked: True
Preloader – Get Target info
Preloader – BROM mode detected.
Preloader – HW subcode: 0x8a00
Preloader – HW Ver: 0xca00
Preloader – SW Ver: 0x0
Preloader – ME_ID: 32993668EB4B4D231D8C1EBAAE7B7B58
Preloader – SOC_ID: 70D2AEEC41FAFC8277AC77DAC843F110913450DFDAC62279F70FD82135670657
DA_handler – Device is unprotected.
DA_handler – Device is in BROM-Mode. Bypassing security.
PLTools – Loading payload from mt6877_payload.bin, 0x264 bytes
PLTools – Kamakiri / DA Run
Kamakiri – Trying kamakiri2..
DeviceClass – USBError(5, ‘Input/Output Error’)
Traceback (most recent call last):
File “C:\Python 3.10.9\mtk”, line 814, in
mtk = Main(args).run(parser)
File “C:\Python 3.10.9\mtkclient\Library\mtk_main.py”, line 615, in run
mtk = da_handler.configure_da(mtk, preloader)
File “C:\Python 3.10.9\mtkclient\Library\mtk_da_cmd.py”, line 101, in configure_da
mtk = mtk.bypass_security() # Needed for dumping preloader
File “C:\Python 3.10.9\mtkclient\Library\mtk_class.py”, line 155, in bypass_security
if plt.runpayload(filename=self.config.payloadfile):
File “C:\Python 3.10.9\mtkclient\Library\pltools.py”, line 102, in runpayload
if self.kama.payload(payload, addr, True, exploittype):
File “C:\Python 3.10.9\mtkclient\Library\kamakiri.py”, line 139, in payload
if self.exploit2(payload, addr):
File “C:\Python 3.10.9\mtkclient\Library\kamakiri.py”, line 117, in exploit2
ptr_send = unpack(“<I", self.da_read(self.mtk.config.chipconfig.send_ptr[0][1], 4))[0] + 8
TypeError: a bytes-like object is required, not 'NoneType'
What do i do now? I've followed all the steps, not sure why is it giving I/O error. I tried with second usb on other port but got the same message.
Kindly suggest how to rectify this.
My device is Ulefone Armour 18t, Processor: MediaTek Dimensity 900
Phone tech specs:-
Ulefone Power Armor 18T
Please help.. :-(
Kind Regards
Hitanshu Gaur
Generic123. said:
I just received an Ulefone armor 18t and I'm trying to get the phone rooted through a magisk patched boot image. Whenever I attempt to flash the patched image, the phone always ends up bootlooping and gives me the 'android system may be corrupt' message. I've tried flashing an empty vbmeta in order to try to disable secure boot, but it still isn't working.
Does anyone have any other suggestions or have any ideas as to what could be causing my phone to not boot?
Posted this on reddit; just reposting this for more exposure
EDIT: I managed to root my phone by patching my boot.img with an older version of magisk (24.3) and then updating to v25 after.
Click to expand...
Click to collapse
Hi mate, I patched the boot.img of the official ROM with Magisk after installing it on the phone and then selecting 'install' button and selecting boot.ing file of the official ROM and it was successful. But what do I do next? How do I root the phone after this?
hitanshugaur said:
Hi mate, I patched the boot.img of the official ROM with Magisk after installing it on the phone and then selecting 'install' button and selecting boot.ing file of the official ROM and it was successful. But what do I do next? How do I root the phone after this?
Click to expand...
Click to collapse
Here a complete how to https://www.droidwin.com/patch-stock-boot-image-flash-magisk/
joke19 said:
Here a complete how to https://www.droidwin.com/patch-stock-boot-image-flash-magisk/
Click to expand...
Click to collapse
I have been able to do everything, now the instructions in the last one are confusing.
Step 2A and 2B are causing confusion and hence a bootloop error.
In 2A he is asking to 'copy' the patched file to the platform-tools folder and the file as per him is stored by the name of magisk_patched.img whereas in reality when I did it was saved as magisk_patched._1vjUh.img. I have copied this to the platform-tools folder as directed
In 2B he is asking to patch again with a newer version and yet again as per him that file will be saved as magisk_patched.img too. Now how can one folder have two files with the exact same name?
Now the confusion is: Does he want us to 'cut paste' the patched image from the older version to the platform-tools folder and rename it to magisk_patched.img ; and leave the new version's patched file in the phone's internal memory and rename that one too magisk_patched.img as well?
If this is done then won't there be a conflict while rooting? because two patched .img are from different versions of a software?