Related
Does anyone know how to root acer iconia a1 tablet?
thanks for the replies
serpe18 said:
Does anyone know how to root acer iconia a1 tablet?
thanks for the replies
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=40425886
Enviado desde mi B1-A71 usando Tapatalk 2
Succesfully run root, but got permisson deny when type su on Iconia A1
Hi,
I used your 0.7.0 (and 0.6.3) root tools and tried to root my Iconia A1.
I had tried Linux (root from scratch method) and Windows root method, the results are the same. All said successfully rooted after finish execution those root tools.
But actually My Iconia A1 can not execute su when I go into shell. (I use adb shell to verify su succeed or not).
The message from shell console shows permission denied.
Is there any steps missed from me?
same here
I had the same prob with my asus.
And still get no solution.
One time the root tool v31 worked, but only Wirth the imfo su is old. Open the supersu and i get the Info that is not possible. Still no root.
Q
does anyone gonna make mods or roms for acer iconia? because im tired of my Acer Iconia A1-810 Tablet!!!!! i bought it 2 days ago!!! waste of money and no HD screen! i should read before i bought it! i could have bought a Nexus 7!
:crying:
a1 811
I have the A1 811 Version and also looking for root.
This tab has a MTK chipset, so i looked at many China Forums and get many root Tools.
But no success. I dont know why. The Ainol 828 has the same chipset. If someone had more luck than i had.
konsolen said:
I have the A1 811 Version and also looking for root.
This tab has a MTK chipset, so i looked at many China Forums and get many root Tools.
But no success. I dont know why. The Ainol 828 has the same chipset. If someone had more luck than i had.
Click to expand...
Click to collapse
If you have a MT65XX CPU then I can help you root it. Download and install the tool from first post of this link then run it, it will tell you which MT65XX CPU you have and then we can get you rooted from there. You will need ADB drivers for MTK Droid Tools to work but I have them also if you need them.
http://forum.xda-developers.com/showthread.php?t=2160490&styleid=18
Hope this helps!
Klown80 said:
If you have a MT65XX CPU then I can help you root it. Download and install the tool from first post of this link then run it, it will tell you which MT65XX CPU you have and then we can get you rooted from there. You will need ADB drivers for MTK Droid Tools to work but I have them also if you need them.
http://forum.xda-developers.com/showthread.php?t=2160490&styleid=18
Hope this helps!
Click to expand...
Click to collapse
Thank you. I hope we can root this Thing.
MKT Tool read it as MT6589 (Fake 8389)
Thats from the scatter:
ADER 0x0
{
}
MBR 0xc00000
{
}
EBR1 0xc80000
{
}
__NODL_PMT 0xd00000
{
}
__NODL_PRO_INFO 0x1100000
{
}
__NODL_NVRAM 0x1400000
{
}
__NODL_PROTECT_F 0x1900000
{
}
__NODL_PROTECT_S 0x2300000
{
}
__NODL_SECCFG 0x2d00000
{
}
UBOOT 0x2d20000
{
}
BOOTIMG 0x2d80000
{
}
RECOVERY 0x3380000
{
}
SEC_RO 0x3d80000
{
}
__NODL_MISC 0x4380000
{
}
LOGO 0x4400000
{
}
__NODL_EXPDB 0x4700000
{
}
ANDROID 0x5100000
{
}
CACHE 0x45100000
{
}
USRDATA 0x70d00000
{
}
__NODL_BMTPOOL 0xffff00a8
{
}
---------- Post added at 03:22 AM ---------- Previous post was at 03:18 AM ----------
konsolen said:
Thank you. I hope we can root this Thing.
MKT Tool read it as MT6589 (Fake 8389)
Thats from the scatter:
ADER 0x0
{
}
MBR 0xc00000
{
}
EBR1 0xc80000
{
}
__NODL_PMT 0xd00000
{
}
__NODL_PRO_INFO 0x1100000
{
}
__NODL_NVRAM 0x1400000
{
}
__NODL_PROTECT_F 0x1900000
{
}
__NODL_PROTECT_S 0x2300000
{
}
__NODL_SECCFG 0x2d00000
{
}
UBOOT 0x2d20000
{
}
BOOTIMG 0x2d80000
{
}
RECOVERY 0x3380000
{
}
SEC_RO 0x3d80000
{
}
__NODL_MISC 0x4380000
{
}
LOGO 0x4400000
{
}
__NODL_EXPDB 0x4700000
{
}
ANDROID 0x5100000
{
}
CACHE 0x45100000
{
}
USRDATA 0x70d00000
{
}
__NODL_BMTPOOL 0xffff00a8
{
}
Click to expand...
Click to collapse
If i push root, device reboot and i get the info Root is possible over CWM.
konsolen said:
Thank you. I hope we can root this Thing.
MKT Tool read it as MT6589 (Fake 8389)
Thats from the scatter:
ADER 0x0
{
}
MBR 0xc00000
{
}
EBR1 0xc80000
{
}
__NODL_PMT 0xd00000
{
}
__NODL_PRO_INFO 0x1100000
{
}
__NODL_NVRAM 0x1400000
{
}
__NODL_PROTECT_F 0x1900000
{
}
__NODL_PROTECT_S 0x2300000
{
}
__NODL_SECCFG 0x2d00000
{
}
UBOOT 0x2d20000
{
}
BOOTIMG 0x2d80000
{
}
RECOVERY 0x3380000
{
}
SEC_RO 0x3d80000
{
}
__NODL_MISC 0x4380000
{
}
LOGO 0x4400000
{
}
__NODL_EXPDB 0x4700000
{
}
ANDROID 0x5100000
{
}
CACHE 0x45100000
{
}
USRDATA 0x70d00000
{
}
__NODL_BMTPOOL 0xffff00a8
{
}
---------- Post added at 03:22 AM ---------- Previous post was at 03:18 AM ----------
If i push root, device reboot and i get the info Root is possible over CWM.
Click to expand...
Click to collapse
Actually since you have a MT6589, you may be in luck and be able to root your device rather quickly. Go to this link and download Motochopper, I know it is from Galaxy S4 thread but it wrks on a number of devices. Make sure you have drivers installed and USB debugging enabled in settings. (If you need help installing drivers you can get them from here: http://www.snappea.com/ )
http://forum.xda-developers.com/showthread.php?t=2252248
If this by chance does not work on your device, let me know and there is another quick root method we can try before having to go the long route and pull the stock recovery to gain root.
Good luck!
Klown80 said:
Actually since you have a MT6589, you may be in luck and be able to root your device rather quickly. Go to this link and download Motochopper, I know it is from Galaxy S4 thread but it wrks on a number of devices. Make sure you have drivers installed and USB debugging enabled in settings. (If you need help installing drivers you can get them from here: http://www.snappea.com/ )
http://forum.xda-developers.com/showthread.php?t=2252248
If this by chance does not work on your device, let me know and there is another quick root method we can try before having to go the long route and pull the stock recovery to gain root.
Good luck!
Click to expand...
Click to collapse
Thx again. I tried snappea and moborobo. No Chance. I triedmotochopper, root with restore and doomlords v17 and eroot 1.3.4
konsolen said:
Thx again. I tried snappea and moborobo. No Chance. I triedmotochopper, root with restore and doomlords v17 and eroot 1.3.4
Click to expand...
Click to collapse
So do you have working drivers now? Also, do you have USB debugging enabled on the device? Once you get drivers working I know of a few other root program you can use.
Once drivers are working you can use this most likely:
http://forum.xda-developers.com/showpost.php?p=43163569&postcount=7&styleid=18
I loadet the last VersionVersion is tool. After the process i get the info root OK. A chinese Version of superuser is also installed but still no root.
When i install a english version i get every time no su binary installed.
konsolen said:
I loadet the last VersionVersion is tool. After the process i get the info root OK. A chinese Version of superuser is also installed but still no root.
When i install a english version i get every time no su binary installed.
Click to expand...
Click to collapse
You do not get a pop up from chinese app when you try to update binary? If so make sure you hit the right hand button. IF not pop up, go into the chinese root app and tap the last choice (I think it says root in the title) then it should show you a list of apps that asked for root access, check to make sure SuperSU did not get denied first. If that still wont work we will move on to the harder root method if you like.
Klown80 said:
You do not get a pop up from chinese app when you try to update binary? If so make sure you hit the right hand button. IF not pop up, go into the chinese root app and tap the last choice (I think it says root in the title) then it should show you a list of apps that asked for root access, check to make sure SuperSU did not get denied first. If that still wont work we will move on to the harder root method if you like.
Click to expand...
Click to collapse
I see the list of apps with a blue switch on right side.
But still no su install possible. Root tools and mobile uncle said no root.
IS this possible that this tool put the binary in a wrong place?
And yes, i want to heck this thing. So harder way are welcome. -
konsolen said:
I see the list of apps with a blue switch on right side.
But still no su install possible. Root tools and mobile uncle said no root.
IS this possible that this tool put the binary in a wrong place?
And yes, i want to heck this thing. So harder way are welcome. -
Click to expand...
Click to collapse
Try this:
http://www.cydiaimpactor.com/
Download Impactor. Extract the files then run the Impactor application. When it opens make sure device is connected to PC and USB debugging is enabled. Then just hit start button. As long as you dont get a fail message try installing SuperSU from Play Store after wards and see if it lets you update bainry now.
If that dont work either I have one more program we can try before we take the long route. Finally try the MTK root all zip I have attached. Let me know how it goes please.
Klown80 said:
Try this:
http://www.cydiaimpactor.com/
Download Impactor. Extract the files then run the Impactor application. When it opens make sure device is connected to PC and USB debugging is enabled. Then just hit start button. As long as you dont get a fail message try installing SuperSU from Play Store after wards and see if it lets you update bainry now.
If that dont work either I have one more program we can try before we take the long route. Finally try the MTK root all zip I have attached. Let me know how it goes please.
Click to expand...
Click to collapse
THe injector i tried 2 days ago. Failes. I will tray your second tool.
THx
konsolen said:
THe injector i tried 2 days ago. Failes. I will tray your second tool.
THx
Click to expand...
Click to collapse
Ok, let me know how the last tool goes. If still no luck we can just take the long route. Your device isnt making this easy is it? lol
Klown80 said:
Ok, let me know how the last tool goes. If still no luck we can just take the long route. Your device isnt making this easy is it? lol
Click to expand...
Click to collapse
OK, second tool also nothing. SH... I dont understand the chinese superuser. If i install an APP, a popup comes. But left or right button, akways the same.
konsolen said:
OK, second tool also nothing. SH... I dont understand the chinese superuser. If i install an APP, a popup comes. But left or right button, akways the same.
Click to expand...
Click to collapse
something does indeed sound messed up. If you have any free time today I will have some time if you would like to install Teamviewer on your PC, I can connect and help you get this issue solved.
Klown80 said:
something does indeed sound messed up. If you have any free time today I will have some time if you would like to install Teamviewer on your PC, I can connect and help you get this issue solved.
Click to expand...
Click to collapse
Wow, thank you. I would really thankfully for that. Because this thing buggibg me,
I rootet from rk chip devices over sony, htc every phone or tablet.
This is the first one, which is really hard to knock.
As my last chance i thinked about about a backup to implement su and write it back.
But i dont know how to open the backup.ba.
What time is ok for you? Iam from austria and here is 17:00.
What do say about 20:00 around?
My wife is looking tv , so i can concentrate me -
Hello @all,
First sorry for my bad english. I try explain my Problem as best as i can in english.
2 Days ago i got 2 pcs from this Phone: mixeshop , Mini s4 1:1 106$
I messed around with one of these phones with mtk droid tools for root / Backup. My hand was faster then my brain.. i have bricked the first phone after the question from droid tools to make cwm and i klicked OK by thequestion of write back boot.bin or similar.. So now my phone is in Bootloop. If i start the phone with vol + and powerbutton the phone starts into 3e recovery. I tried wipe data/factory reset & wipe cache partition but phone is still in bootloop (Samsung startlogo - blackscreen - samsung startlogo - blackscreen ....)
The backup before the bootloop isnt done without errors so i think i can forget do smth with the backup (with many errors)
The 2nd Phone is exact the same phone, same software, same lcd driver and work well (rooted with ADB script)
So what can i do to get the bootloop smartphone working? I´ve tried to make a backup from the working phone and flash this to the bootlooped one but i can´t make a backup because of errors. Maybe i stuck on this becaus i´m newbie. I do not want to be responsible for the fact that my daughter got a destroyed phone by dumb daddy to christmas
Informations about the bootloop stucking phone from backup:
- phone.info
Hardware : MT6572
Model : GT-I9190
Build number : ALPS.JB3.MP.V1
Build date UTC : 20131111-114605
Android v : 4.2.2
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V1.P1, 2013/09/02 13:50
Kernel v : 3.4.5 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP Mon Nov 11 19:44:39 CST 2013
Uboot build v : ----- should be root shell
LCD Driver IC : 1-otm8009a_fwvga_mipi
Click to expand...
Click to collapse
-scatter
PRELOADER 0x0
{
}
__NODL_PRO_INFO 0x100000
{
}
__NODL_NVRAM 0x200000
{
}
__NODL_PROTECT_F 0x500000
{
}
__NODL_PROTECT_S 0x800000
{
}
__NODL_SECCFG 0xb00000
{
}
UBOOT 0xb40000
{
}
BOOTIMG 0xbc0000
{
}
RECOVERY 0x11c0000
{
}
SEC_RO 0x17c0000
{
}
__NODL_MISC 0x1800000
{
}
LOGO 0x18c0000
{
}
__NODL_EXPDB 0x19c0000
{
}
__NODL_FAT 0x1bc0000
{
}
ANDROID 0x2fc0000
{
}
CACHE 0x11fc0000
{
}
USRDATA 0x126c0000
{
}
__NODL_BMTPOOL 0xFFFF0050
{
}
Click to expand...
Click to collapse
The Backup size is 293 MB
Prepare file for flashtool gave me an error.. cant remember exactly
Information about the second working phone with pictures:
{
"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"
}
block info:
I´m really grateful for any help get the bootlooped phone working. I´m new to this stuff with all the tools but i´m ready to learnand hope anyone can help me. shpuld i contact seller to give me stock rom? i really dont know what to do
Thank you
no one can help? .. I tried to readback boot & recovery from the working phone but after prepare files with mtk droid there is a error message:
Error :No UnGZip Recovery Images
no one can help me out with this issue
hey
chillbreak said:
no one can help me out with this issue
Click to expand...
Click to collapse
another brick... ahhhh ...
can you access download mode?
backups wont help in this situation i think. you need to reflash stock firmware via oddin
I think odin ist just for original samsung. The phone i talk about is a samsung s4 mini clone
S4 mini clone
chillbreak said:
Hello @all,
First sorry for my bad english. I try explain my Problem as best as i can in english.
2 Days ago i got 2 pcs from this Phone: mixeshop , Mini s4 1:1 106$
I messed around with one of these phones with mtk droid tools for root / Backup. My hand was faster then my brain.. i have bricked the first phone after the question from droid tools to make cwm and i klicked OK by thequestion of write back boot.bin or similar.. So now my phone is in Bootloop. If i start the phone with vol + and powerbutton the phone starts into 3e recovery. I tried wipe data/factory reset & wipe cache partition but phone is still in bootloop (Samsung startlogo - blackscreen - samsung startlogo - blackscreen ....)
The backup before the bootloop isnt done without errors so i think i can forget do smth with the backup (with many errors)
The 2nd Phone is exact the same phone, same software, same lcd driver and work well (rooted with ADB script)
So what can i do to get the bootloop smartphone working? I´ve tried to make a backup from the working phone and flash this to the bootlooped one but i can´t make a backup because of errors. Maybe i stuck on this becaus i´m newbie. I do not want to be responsible for the fact that my daughter got a destroyed phone by dumb daddy to christmas
Informations about the bootloop stucking phone from backup:
- phone.info
-scatter
The Backup size is 293 MB
Prepare file for flashtool gave me an error.. cant remember exactly
Information about the second working phone with pictures:
block info:
I´m really grateful for any help get the bootlooped phone working. I´m new to this stuff with all the tools but i´m ready to learnand hope anyone can help me. shpuld i contact seller to give me stock rom? i really dont know what to do
Thank you
Click to expand...
Click to collapse
same problem here..please help us
chillbreak said:
Hello @all,
First sorry for my bad english. I try explain my Problem as best as i can in english.
2 Days ago i got 2 pcs from this Phone: mixeshop , Mini s4 1:1 106$
I messed around with one of these phones with mtk droid tools for root / Backup. My hand was faster then my brain.. i have bricked the first phone after the question from droid tools to make cwm and i klicked OK by thequestion of write back boot.bin or similar.. So now my phone is in Bootloop. If i start the phone with vol + and powerbutton the phone starts into 3e recovery. I tried wipe data/factory reset & wipe cache partition but phone is still in bootloop (Samsung startlogo - blackscreen - samsung startlogo - blackscreen ....)
The backup before the bootloop isnt done without errors so i think i can forget do smth with the backup (with many errors)
The 2nd Phone is exact the same phone, same software, same lcd driver and work well (rooted with ADB script)
So what can i do to get the bootloop smartphone working? I´ve tried to make a backup from the working phone and flash this to the bootlooped one but i can´t make a backup because of errors. Maybe i stuck on this becaus i´m newbie. I do not want to be responsible for the fact that my daughter got a destroyed phone by dumb daddy to christmas
Informations about the bootloop stucking phone from backup:
- phone.info
-scatter
The Backup size is 293 MB
Prepare file for flashtool gave me an error.. cant remember exactly
Information about the second working phone with pictures:
block info:
I´m really grateful for any help get the bootlooped phone working. I´m new to this stuff with all the tools but i´m ready to learnand hope anyone can help me. shpuld i contact seller to give me stock rom? i really dont know what to do
Thank you
Click to expand...
Click to collapse
can you post the backup files. i assume it is in zip format
chillbreak said:
Hello @all,
First sorry for my bad english. I try explain my Problem as best as i can in english.
2 Days ago i got 2 pcs from this Phone: mixeshop , Mini s4 1:1 106$
I messed around with one of these phones with mtk droid tools for root / Backup. My hand was faster then my brain.. i have bricked the first phone after the question from droid tools to make cwm and i klicked OK by thequestion of write back boot.bin or similar.. So now my phone is in Bootloop. If i start the phone with vol + and powerbutton the phone starts into 3e recovery. I tried wipe data/factory reset & wipe cache partition but phone is still in bootloop (Samsung startlogo - blackscreen - samsung startlogo - blackscreen ....)
The backup before the bootloop isnt done without errors so i think i can forget do smth with the backup (with many errors)
The 2nd Phone is exact the same phone, same software, same lcd driver and work well (rooted with ADB script)
So what can i do to get the bootloop smartphone working? I´ve tried to make a backup from the working phone and flash this to the bootlooped one but i can´t make a backup because of errors. Maybe i stuck on this becaus i´m newbie. I do not want to be responsible for the fact that my daughter got a destroyed phone by dumb daddy to christmas
Informations about the bootloop stucking phone from backup:
- phone.info
-scatter
The Backup size is 293 MB
Prepare file for flashtool gave me an error.. cant remember exactly
Information about the second working phone with pictures:
block info:
I´m really grateful for any help get the bootlooped phone working. I´m new to this stuff with all the tools but i´m ready to learnand hope anyone can help me. shpuld i contact seller to give me stock rom? i really dont know what to do
Thank you
Click to expand...
Click to collapse
We have same phone and I have bricked the phone I kinda fix the phone but it doesnt have the correct base band. Can you send me your backup files maybe I can get the baseband from it so we both will have a working phone again.
I haven't had enough to get a One now, but I'm pretty interested in the phone. Yesterday I saw a thread on Chinese forum, saying that LOGO.bin contains the image shown in fastboot mode, and thus everyone can choose his preferred image (like CM's) even if he uses ColorOS. So I tried to extract the bitmap from LOGO.bin and replace it with my own picture.
Now I've succeed PARTIALLY in identifying the BIN file format and extracting the images. There's no enough time to dig into replacing the pictures though, but I think it won't be hard.
Here is what I find, for those "aggressive" themers and ROM devs who want custom boot splash screen:
The BIN file starts with the following structure:
C:
struct SPLASHHEADERINDEX {
char magic_code[8]; // = { 'S', 'P', 'L', 'A', 'S', 'H', '!', '!' };
int img_width;
int img_height;
int reserved; // What's this? I haven't figured that out.
int img_offset[6];
char padding[468]; // The header is 512 bytes. Thanks [user=5757424]@chillstep1998[/user] !
};
Right after this structure, the raw data of boot splash image begins. Every pixel is described by 3 bytes in B-G-R order. The pixels begin at the upper left corner and then stored in the order of left to right & up to down. You can read (img_width * img_height * 3) bytes and write them into a BMP file. NOTE that BMP files require 4-pixel alignment for every horizontal row (Google that for details, otherwise you will get a "Broken image" info in image viewers) In order to avoid this problem, I wrote a simple program in VB.NET and used Bitmap.SetPixel and Bitmap.Save to solve it.
This is the VB code for this procedure. (I can't do GUI programs in C++...)
Code:
Dim bmp As New Bitmap(img_width, img_height)
Dim color As Color
For y = 0 To img_height - 1
For x = 0 To img_width - 1
b = fs.ReadByte 'fs is the FileStream of BIN file. Already sought to correct offset.
g = fs.ReadByte
r = fs.ReadByte
If b = -1 Then b = 0
If g = -1 Then g = 0
If r = -1 Then r = 0
color = color.FromArgb(r, g, b)
bmp.SetPixel(x, y, color)
Next
Next
There are some zeros after (img_width * img_height * 3) bytes. I don't know what's for...
Then let's look at the other images. Their offsets are in the img_offset array of SPLASHHEADERINDEX. They have headers like this:
C:
struct SPLASHHEADERNONINDEX {
char magic_code[8]; // "SPLASH!!" without \0
int img_width;
int img_height;
int reserved; //Still don't know
char padding[492];
};
Right after the structure is the raw data. Process that as mentioned above.
The image at img_offset[0] is the one shown in fastboot mode
[1] is AT current test (original Chinese: AT电流测试. What's AT?)
[2] is RF test
[3] is WLAN test
[4] is charging
[5] is low battery warning
Previews for new images are coming soon...
However: there is one bug: the images extracted are "mis-placed". You need to move 0x0 to 164xHEIGHT (163xHEIGHT maybe) area to the right side of the image to get the correct pic. The images extracted from ColorOS' LOGO.bin are listed as follows:
SPOILER:
[0]
{
"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"
}
[1]
[2]
[3]
[4]
[5]
Boot splash
Does anyone know the cause of this mis-place problem? Although that can be solved easily in the code, but it's not very reliable. Maybe it's related to the "reserved" member?
Since the format is rather simple, modding and repacking will be easy. When I get some free time I'll make a tool for this...
still dangerous. We don't know whether there's logo signiture check, even if we know how to make a logo.bin.
But good job!
dlhxr said:
still dangerous. We don't know whether there's logo signiture check, even if we know how to make a logo.bin.
But good job!
Click to expand...
Click to collapse
Can't come up with any reason why there should be signature check for logo, especially when we can use home-made modem fimwares and kernels without any problem... But it's worth considering since there's "reserved" member. ColorOS gets 0x00 0x00 0x00 0x00 and CM 0x00 0x00 0x00 0x01 in boot splash's "reserved" int. Haven't checked other 6 images though.
We already know how to make our own logo.bin...there's a thread in the "Themes and Apps" section.
treChoy said:
We already know how to make our own logo.bin...there's a thread in the "Themes and Apps" section.
Click to expand...
Click to collapse
Wow I didn't notice it before... This thread is revealing secrets of the magic and pushing it further
But he says the header is 512 bytes, which is different from what I've found. I will take a look. However, since there are pics as small as ~300*30, skipping 512bytes may cause visible loss of the content. Maybe that's for splash screen only.
updateing said:
Wow I didn't notice it before... This thread is revealing secrets of the magic.
But he says the header is 512 bytes, which is different from what I've found. I will take a look. However, since there are pics as small as ~300*30, skipping 512bytes may cause visible loss of the content. Maybe that's for splash screen only.
Click to expand...
Click to collapse
As far as they've discovered on the thread, they've only really uncovered the workings of the splash screen. We know that fastboot is also affected by the LOGO partition, but we don't know how that ties in with the bootloader. The ColorOS LOGO.bin displays, "已進人fastboot..." when in fastboot mode, and the International LOGO.bin displays "Fastboot Mode" with the Cyanogen mascot.
One thing is for certain though: this is DANGEROUS. There's a very good possibility of bricking because of the LOGO partition's relationship with the bootloader. I was talking to another developer here about his work with the LOGO partition, and he said he bricked his phone, but recovered it by holding the power button, and then manually writing the correct LOGO partition using the 'dd' command.
I've contacted OnePlus support about this, so we should hear word back around Easter.
treChoy said:
As far as they've discovered on the thread, they've only really uncovered the workings of the splash screen. We know that fastboot is also affected by the LOGO partition, but we don't know how that ties in with the bootloader. The ColorOS LOGO.bin displays, "已進人fastboot..." when in fastboot mode, and the International LOGO.bin displays "Fastboot Mode" with the Cyanogen mascot.
One thing is for certain though: this is DANGEROUS. There's a very good possibility of bricking because of the LOGO partition's relationship with the bootloader. I was talking to another developer here about his work with the LOGO partition, and he said he bricked his phone, but recovered it by holding the power button, and then manually writing the correct LOGO partition using the 'dd' command.
I've contacted OnePlus support about this, so we should hear word back around Easter.
Click to expand...
Click to collapse
Hope OnePlus support team is open to this kind of mod...
As for the developer you mentioned, could you please ask him if he entered Qualcomm DLOAD mode and used some .hex file to boot the phone into mass-storage mode? I know when this (QHSUSB DLOAD device) shows up, the bootloader has already failed and this is the last recovering method of the phone. Seen it on my Xperia TX...
And the method mentioned in this thread will also work on CM's LOGO.bin, except for the 164xH issue.
updateing said:
Hope OnePlus support team is open to this kind of mod...
As for the developer you mentioned, could you please ask him if he entered Qualcomm DLOAD mode and used some .hex file to boot the phone into mass-storage mode? I know when this (QHSUSB DLOAD device) shows up, the bootloader has already failed and this is the last recovering method of the phone. Seen it on my Xperia TX...
And the method mentioned in this thread will also work on CM's LOGO.bin, except for the 164xH issue.
Click to expand...
Click to collapse
The developer is @demkantor . And I was wrong about how he unbricked his device. He said that after messing around with the LOGO partition, he got the dreaded "QHUSB_BULK" error, but after a few seconds, his OPO rebooted on his own. He had to 'dd' the regular LOGO partition to get his bootloader up and running. Original thread here: http://forum.xda-developers.com/oneplus-one/help/qhsusbbulk-help-t2848238
treChoy said:
The developer is @demkantor . And I was wrong about how he unbricked his device. He said that after messing around with the LOGO partition, he got the dreaded "QHUSB_BULK" error, but after a few seconds, his OPO rebooted on his own. He had to 'dd' the regular LOGO partition to get his bootloader up and running. Original thread here: http://forum.xda-developers.com/oneplus-one/help/qhsusbbulk-help-t2848238
Click to expand...
Click to collapse
I have once seen somewhere that you can find specific .hex file (e.g. MPRG8960.hex for MSM8960) to download into the phone by QPST Service Programming. Then the phone will boot into mass storage mode, where computer will recognize the phone as a removable disk drive. Now the whole internal storage is "mounted" on the computer and you can use dd to restore then.
(Google'd and it says only QHSUSB_DLOAD need the hex file. QHSUSB_BULK should be mounting the internal storage to computer automatically and dd will be available. Not sure about that. Example: http://forum.xda-developers.com/showthread.php?t=2582142&page=1)
yeah the header is 512 bytes. Now the images are all correct :victory:
Flashing a bad LOGO.bin did send me to the QHSUB_DLOAD mode and I tired rebooting holding down all three buttons. It did seem to work but after a bit it seemed to just boot on its own. Then I just used an adb shell to run dd commands to flash the proper .bin and all has been well since then
Still have been to busy with our newborn to look into anything deeper but between this thread and the one by @chillstep1998 and treChoy and other it looks to be all good!
Glad all is coming together on this end, keep up the great work all
dear thread creater.. i tell u what is that zeros after anything.
actualy android reads anything in block size.. like this
4,4,4,4,4.....
or 8,8,8,8,8.....
or 16,16,16,16...
or....
or...
or...
or 512,512,512,512...
or......
so.. if block size is 512 then it would read 512 bytes first..
now think what if there is only 50 or 51 bytes.. if will be a error.. if it has code to handle errors.. it is slow.
this is called alignment.. we say header is aligned to 512 bytes.
to make alignment it would add padding of NULLs(chr(0) in vb)
same nulls for the end of file to make it aligned to some size.
thank you.
m9j_cfALt said:
dear thread creater.. i tell u what is that zeros after anything.
actualy android reads anything in block size.. like this
4,4,4,4,4.....
or 8,8,8,8,8.....
or 16,16,16,16...
or....
or...
or...
or 512,512,512,512...
or......
so.. if block size is 512 then it would read 512 bytes first..
now think what if there is only 50 or 51 bytes.. if will be a error.. if it has code to handle errors.. it is slow.
this is called alignment.. we say header is aligned to 512 bytes.
to make alignment it would add padding of NULLs(chr(0) in vb)
same nulls for the end of file to make it aligned to some size.
thank you.
Click to expand...
Click to collapse
Thanks! I know there are some alignment rules, but didn't expect them to be here. I've seen aligning the whole file to 4 bytes or so, but little do I know that a section header needs alignment as well. I guess that's because this LOGO.bin is used in such a low-level "environment" that we don't have enough time & space to handle the non-aligned data. Am I right?
updateing said:
Thanks! I know there are some alignment rules, but didn't expect them to be here. I've seen aligning the whole file to 4 bytes or so, but little do I know that a section header needs alignment as well. I guess that's because this LOGO.bin is used in such a low-level "environment" that we don't have enough time & space to handle the non-aligned data. Am I right?
Click to expand...
Click to collapse
Hi man!
Do you know how change the battery animation when the phone is charging(when is off)?
I've tried to change the imgs in /res/images/charger, but you know, it doesn't work eheheh...
Can you help me?
Reive said:
Hi man!
Do you know how change the battery animation when the phone is charging(when is off)?
I've tried to change the imgs in /res/images/charger, but you know, it doesn't work eheheh...
Can you help me?
Click to expand...
Click to collapse
I don't have a OPO to test, all these analysis are theoretical. So I may not be able to help. Sorry...
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
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?