Hovatek Forum DEVELOPMENT Android How to root Lenovo A5 (L18021) using Magisk
Can't login? Please, reset your password.
Hovatek is recruiting! Apply Now


How to root Lenovo A5 (L18021) using Magisk

How to root Lenovo A5 (L18021) using Magisk

Pages (2): 1 2 Next
El-Degza
El-Degza
El-Degza
Techie Member
42
29-11-2019, 09:52 PM
#1



.txt
MT6739_Android_scatter.txt
Size: 14.63 KB / Downloads: 6
Good evening sir, I'm opening this thread so you can fully pay attention to my phone's issue.
I've already checked the error ' STATUS_PRELOADER_INVALID', but I didn't understand the given solution so well. Let me drop the scatter file for my phone. So you'll be able to help me better.
xerxes
xerxes
xerxes
Senior Member
8,355
29-11-2019, 10:52 PM
#2
(29-11-2019, 09:52 PM)El-Degza Good evening sir, I'm opening this thread so you can fully pay attention to my phone's issue.
I've already checked the error ' STATUS_PRELOADER_INVALID', but I didn't understand the given solution so well. Let me drop the scatter file for my phone. So you'll be able to help me better.

Did you patch your phone’s boot.img using magisk app?
El-Degza
El-Degza
El-Degza
Techie Member
42
30-11-2019, 05:33 AM
#3
Yes, I did.
xerxes
xerxes
xerxes
Senior Member
8,355
30-11-2019, 10:20 AM
#4
(30-11-2019, 05:33 AM)El-Degza Yes, I did.

try flashing patched boot using the 'Write Memory' tab in SP flash tool.
To activate write memory tab, press 'Ctrl + Alt + V' to enabled advanced mode then click Window > Write Memory, you can get the boot partition start and length address in scatter file you attached.
El-Degza
El-Degza
El-Degza
Techie Member
42
01-12-2019, 07:37 AM
#5



.jpg
Screenshot_2019-11-30-19-34-48.png.jpg
Size: 49.26 KB / Downloads: 5
 In this case, the 'partition size' will be the length right??
X3non
X3non
X3non
Recognized Contributor
22,062
02-12-2019, 01:16 AM
#6
(01-12-2019, 07:37 AM)El-Degza  In this case, the 'partition size' will be the length right??

you don't need this to attempt using write memory
in the write memory tab,

file path: select the flash you intend to write e.g boot.img
begin address: linear_start_addr from your scatter file e.g 0x10e20000
region: region from your scatter file e.g emmc_user



meanwhile the initial error you got when you attempted to flash using download only, did you select and tick any other files asides from boot?
El-Degza
El-Degza
El-Degza
Techie Member
42
02-12-2019, 05:17 AM
#7
No, I selected only boot.

Sent from my Lenovo L18021 using Hovatek Mobile
X3non
X3non
X3non
Recognized Contributor
22,062
02-12-2019, 02:37 PM
#8
(02-12-2019, 05:17 AM)El-Degza No, I selected only boot.

Sent from my Lenovo L18021 using Hovatek Mobile

that rules out flashing using download only, what about using write memory?
El-Degza
El-Degza
El-Degza
Techie Member
42
03-12-2019, 09:31 AM
#9
.jpg
Screenshot_2019-12-03-09-12-49.png.jpg
Size: 84.62 KB / Downloads: 3
I was able to use the write memory to flash my patched-boot.img, but my phone prompted an error and it didn't start up....like boot loop, but it boot up immediately I flashed the normal boot.img, the original boot I patched.
The error says,
"RED STATE
YOUR DEVICE HAS FAILED VERIFICATION AND MAY NOT WORK PROPERLY. YOUR DEVICE WILL BOOT IN 5 SECONDS"
After it reboot, it will prompt it and reboot again, prompting the same massage over and over again. It only boot up when I flashed the original "boot-verified.img"
What could be the issue behind this please??? I've attached a picture of the error message.
X3non
X3non
X3non
Recognized Contributor
22,062
03-12-2019, 12:18 PM
#10



(03-12-2019, 09:31 AM)El-Degza I was able to use the write memory to flash my patched-boot.img, but my phone prompted an error and it didn't start up....like boot loop, but it boot up immediately I flashed the normal boot.img, the original boot I patched.
The error says,
"RED STATE
YOUR DEVICE HAS FAILED VERIFICATION AND MAY NOT WORK PROPERLY. YOUR DEVICE WILL BOOT IN 5 SECONDS"
After it reboot, it will prompt it and reboot again, prompting the same massage over and over again. It only boot up when I flashed the original "boot-verified.img"
What could be the issue behind this please??? I've attached a picture of the error message.


you might recall i already answered this indirectly @ https://www.hovatek.com/forum/thread-300...#pid182433
not all devices will allow booting non factory images and yours just happens to be one of them

you can try rooting using mtk-su method @ https://forum.xda-developers.com/android...8-t3922213 ; as usual, no guarantees it'll work for you but it's worth a try since it doesn't involving patching boot
This post was last modified: 03-12-2019, 12:19 PM by X3non.
Pages (2): 1 2 Next
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram