Related
I find myself with a big problem. I just got a new Huawei Ascend D1 (not quad) and I am having MAJOR issues. My programing friend decided that he was going to root it for me and add the play store to it. He didn't and now now it won't boot. Near as I can tell, he did something to the system file, based on how gapps seems to be installed. Anyway, I can boot to the splash screen and put it in download mode. I can get to the bootloader, but it fails to allow me to flash the factory ROM back....something about a signature failure. I really need help. I have some knowledge of ADB, but seem to be failing. Can anyone help me?
Any pro. expert help you
danaber11 said:
I find myself with a big problem. I just got a new Huawei Ascend D1 (not quad) and I am having MAJOR issues. My programing friend decided that he was going to root it for me and add the play store to it. He didn't and now now it won't boot. Near as I can tell, he did something to the system file, based on how gapps seems to be installed. Anyway, I can boot to the splash screen and put it in download mode. I can get to the bootloader, but it fails to allow me to flash the factory ROM back....something about a signature failure. I really need help. I have some knowledge of ADB, but seem to be failing. Can anyone help me?
Click to expand...
Click to collapse
My Suggestion is to take back to the Huawei service centre , might they help you !
Or any expert will help you here and get you out of trouble
danaber11 said:
I find myself with a big problem. I just got a new Huawei Ascend D1 (not quad) and I am having MAJOR issues. My programing friend decided that he was going to root it for me and add the play store to it. He didn't and now now it won't boot. Near as I can tell, he did something to the system file, based on how gapps seems to be installed. Anyway, I can boot to the splash screen and put it in download mode. I can get to the bootloader, but it fails to allow me to flash the factory ROM back....something about a signature failure. I really need help. I have some knowledge of ADB, but seem to be failing. Can anyone help me?
Click to expand...
Click to collapse
I need more detailed description of actions your friend perfomed, and version of your firmware. Also, if you do not afraid of russian language, you can check this thread (to download any attachments, you must be logged in, or it give you 404).
SionGrey said:
I need more detailed description of actions your friend perfomed, and version of your firmware. Also, if you do not afraid of russian language, you can check this thread (to download any attachments, you must be logged in, or it give you 404).
Click to expand...
Click to collapse
I was able to get some info on what Z did. After rooting the phone with Root Bin4ry v18, he copied the contents of the System folder in the gapps package, using es file explorer, into the system folder of the phone. He then restarted the phone and now it goes straight to bootloader and will not flash the ROM. Unfortunately, I could not tell you what firmware was on it other than the latest one. The one bright spot in all of this is that Z made a copy of original system folder. I think I just need to get that back into the system folder on the phone and I should be all set.
danaber11 said:
I was able to get some info on what Z did. After rooting the phone with Root Bin4ry v18, he copied the contents of the System folder in the gapps package, using es file explorer, into the system folder of the phone. He then restarted the phone and now it goes straight to bootloader and will not flash the ROM. Unfortunately, I could not tell you what firmware was on it other than the latest one. The one bright spot in all of this is that Z made a copy of original system folder. I think I just need to get that back into the system folder on the phone and I should be all set.
Click to expand...
Click to collapse
have you try data wipe in recovery ?
if no so check and try wiping :good:
That was the first thing I tried.
I exhausted everything by this point so im relying on this forum.
If anyone knows a way to install custom recovery on this phone or just some info in general would be appreciated..
Here's more detailed specs:
LG K8 (K350n)
SoC MediaTek MT6735
CPU Quad-core 1.3 GHz Cortex-A53
GPU Mali-T720
1.5GB Ram
Android 6.0
Help me xda , you're my only hope
Laitas said:
I exhausted everything by this point so im relying on this forum.
If anyone knows a way to install custom recovery on this phone or just some info in general would be appreciated..
Here's more detailed specs:
LG K8 (K350n)
SoC MediaTek MT6735
CPU Quad-core 1.3 GHz Cortex-A53
GPU Mali-T720
1.5GB Ram
Android 6.0
Help me xda , you're my only hope
Click to expand...
Click to collapse
I don't have a solution for you, but I can tell you what I've tried (I have the K350N also) and what doesn't work, for me anyway, so that you don't have to waste a week trying them yourself and get extremely frustrated like I did.
You need a scatter file, so that tools for MTK chips can copy your phone's boot and recovery images. One for the MT6735 exists but is not for the K8 and won't work. Supposedly you can create your own by using block info given by MTK Droid Tools, and manually editing the scatter file, but even the latest version (2.5.3d) does not support the MT6735 and does not give the info needed.
SP Flash Tool needs correct address info (which is gotten from a scatter file), it doesn't seem to take it from your phone. Without it, you'd not be able to pull the correct parts which make up your boot.img and recovery.img, so it's useless without the exact scatter file for your phone (whether it's the same SoC or not).
If you can get Miracle Box to stay connected to your phone, you can try its "Read" function. That didn't work for me, even after dozens and dozens of tries and messing about with different drivers.
Your best bet is probably to try using ADB to get the block/address/size info of the internal partitions, and editing that into a scatter file. Also, apparently the K8 uses a "standard Android" header, not MTK header like older MediaTek chipsets do. (Not quite sure what it means, but knowing so will probably be useful).
That's what I plan to try anyways, and if I manage to do it, I'll post again.
Aerieana said:
I don't have a solution for you, but I can tell you what I've tried (I have the K350N also) and what doesn't work, for me anyway, so that you don't have to waste a week trying them yourself and get extremely frustrated like I did.
You need a scatter file, so that tools for MTK chips can copy your phone's boot and recovery images. One for the MT6735 exists but is not for the K8 and won't work. Supposedly you can create your own by using block info given by MTK Droid Tools, and manually editing the scatter file, but even the latest version (2.5.3d) does not support the MT6735 and does not give the info needed.
SP Flash Tool needs correct address info (which is gotten from a scatter file), it doesn't seem to take it from your phone. Without it, you'd not be able to pull the correct parts which make up your boot.img and recovery.img, so it's useless without the exact scatter file for your phone (whether it's the same SoC or not).
If you can get Miracle Box to stay connected to your phone, you can try its "Read" function. That didn't work for me, even after dozens and dozens of tries and messing about with different drivers.
Your best bet is probably to try using ADB to get the block/address/size info of the internal partitions, and editing that into a scatter file. Also, apparently the K8 uses a "standard Android" header, not MTK header like older MediaTek chipsets do. (Not quite sure what it means, but knowing so will probably be useful).
That's what I plan to try anyways, and if I manage to do it, I'll post again.
Click to expand...
Click to collapse
Well i spend best part of this morning trying to a different aproach , i managed to find a ROM file (in kdz format, whitch woulve been useless for mtk tools anyway) whitch i extracted for a Recovery.img and tried to port the various recovieries with no awail for now. From what i've seen the filesystem inside the rom is a mess some of the files have the MTK headers others have the android ones and I'm trying to make this work entirely by trial and error.. If I'll manage to boot into the recovery I'll let you know. Wish me luck
Ok I managed to make a port from K10 that actually boots to recovery. I'll post updates as I work on it (all trial and error~)
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery : https://www.mediafire.com/?xopqenbvgrswgxm
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Laitas said:
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery : https://www.mediafire.com/?xopqenbvgrswgxm
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Click to expand...
Click to collapse
what K8 do you have? MTK or Qualcomm Version?
Laitas said:
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery :
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Click to expand...
Click to collapse
how you extract the recovery img from the kdz? thanks.
tomi.gutierrez.i said:
how you extract the recovery img from the kdz? thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2600575
Was using this . At this point only thing left is to wait for SuperSU update as it doesnt work on K8 yet
Laitas said:
http://forum.xda-developers.com/showthread.php?t=2600575
Was using this . At this point only thing left is to wait for SuperSU update as it doesnt work on K8 yet
Click to expand...
Click to collapse
i flash the image you give, and it cant mount system, so it cant flash supersu, the lg k10 have the same problem that this recovery (it might be for the port), so we have to wait a super su version for lg k10 and k8 and a functional TWRP
Laitas said:
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery : LINK
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Click to expand...
Click to collapse
Can you please show me how to install this recovery on my LG K8 (K350z)
and did you have any luck rooting this phone
all i want is Xposed installed and working but apparently i need root and recovery to install it
Yasser Da Silva said:
Can you please show me how to install this recovery on my LG K8 (K350z)
and did you have any luck rooting this phone
all i want is Xposed installed and working but apparently i need root and recovery to install it
Click to expand...
Click to collapse
I need the same thing like you :c
I dont know how to root my LG K8 in order to install Xposed
Have u found a way to root a lg k8
Maveroik said:
I need the same thing like you :c
I dont know how to root my LG K8 in order to install Xposed
Click to expand...
Click to collapse
Have u found a way to root a lg k8
Declan nalced said:
Have u found a way to root a lg k8
Click to expand...
Click to collapse
Nope man :'c
Laitas said:
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery : xxxxxxxxxxxxxxxx
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Click to expand...
Click to collapse
did u managed to unlock your bootloader? From the strategy of rooting HTC, LG also need a bootloader unlock before you having some privilege in flashing recovery... or rooting...
hackwilliam said:
did u managed to unlock your bootloader? From the strategy of rooting HTC, LG also need a bootloader unlock before you having some privilege in flashing recovery... or rooting...
Click to expand...
Click to collapse
That was step 1 you have to go to fastboot form adb and unlock it from there
I've got the k8 us375 model today and its running 6.0 with an update waiting to install. I'm sure it won't matter much but I'm going to avoid updating anytime soon.
With little research into the device I'm reading people trying kingroot and getting stuck with a semi brick and error. From what I've read about marshmallow is the root needs to be accepted from the boot.img which also needs to be insecure.
So unlocking the bootloader is first.
Second is modifying the kernel and
Then recovery needs to be made so that superSu can be flashed.
I'm no expert but neither am i a newbie to this process, however I'm a little rusty. If anyone knows a better way to describe the processes needed please enlighten me. I'll be away from my PC till this weekend but have a laptop i can tinker with tonight. Until i completely understand what needs to be done I'll continue to do research. Thanks
Sent from my LGUS375 using Tapatalk
justlovejoy said:
If anyone knows a better way to describe the processes needed please enlighten me.
Sent from my LGUS375 using Tapatalk
Click to expand...
Click to collapse
I've been trying to root my k8 (k350n) - european version the last few weeks... so far i got:
(here i try to post a url i can't yet... you can find my topic on chinaphonearena - i describe everything there - search "lg k8 k350n twrp" on google - it will be the second result)
the twrp boots but i'm afraid it's not a perfect port so it migth not handling the partitions well... i mean when i try to install supersu i think it cannot find the boot.img (it seems to find but can't patch it).
The newest supersu supposed to patch the boot.img automatically so i believe the only thing we should manage to get a working twrp...
if you want to try i have to warn you that sometimes when i mess with the twrp i have to make a hard reset the get my phone working again. When you boot to the twrp it asks if you want to make your system writeable - you don't have to do that in order to install supersu - however if you allow twrp to make your system writeable you might lose data (i only lost data if i did a format in the twrp but only writeability doesnt clear data in my case...)
edit1:
so i found that supersu can only patch boot images compress by "gzip". The boot im. of our k8 is compress using "lz4" method. I also realized that my twrp works so far as the supersu tries to decompress the boot image... so
We either wait till supersu deals with lz4 or if we could somehow take (dump to pc) the boot image in fastboot "re"compress to gzip - flash back to the device - restart twrp (not boot to android yet - which obviously would not work), install supersu - restart to fastboot take the boot image "re"compress to lz4 and flash the patched boot.img back to the device.
well it's just an idea which actually stucks at dumping the image without root and who knows what other reasons...
or if we knew what tweaks needs to be done to the boot image and we could just make it on pc and flash it in fastboot (i have the stock boot image - i have the whole firmware actually)...
Any advice would be appriciated
Here we go guys...
http://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807
I actually had to return it. It was brand new in the box but the imei was linked to a delinquent account and I couldnt activate it. I'm subscribed if anything.
Hi all,
Just thought i share a little something i came across from playing about with the phone, I found you can flash any of the ROMs that the HiSilicon Kirin 650 chip set uses. Currently only two phones (5c and P9 lite)
First off you'll need the huawei update extractor http://forum.xda-developers.com/showthread.php?t=2433454 and the ROM from the model of phone you want to flash.
Use the update extractor to extract the boot.img and system.img file from the update.app file, then just flash the files on you phone (fastboot flash boot boot.img and fastboot flash system system.img)
Currently im using a stripped down P9 lite VNS L31 B130 ROM with GAPPS on a honor 5c nem-ul10 chinese phone. Working pretty good, seems fast and smooth. Battery life is not better or worse. Everything seems to be working fine.
Post any questions and i'll try to answer
Cheers
Paul
Liffeyman said:
Hi all,
Just thought i share a little something i came across from playing about with the phone, I found you can flash any of the ROMs that the HiSilicon Kirin 650 chip set uses. Currently only two phones (5c and P9 lite)
First off you'll need the huawei update extractor http://forum.xda-developers.com/showthread.php?t=2433454 and the ROM from the model of phone you want to flash.
Use the update extractor to extract the boot.img and system.img file from the update.app file, then just flash the files on you phone (fastboot flash boot boot.img and fastboot flash system system.img)
Currently im using a stripped down P9 lite VNS L31 B130 ROM with GAPPS on a honor 5c nem-ul10 chinese phone. Working pretty good, seems fast and smooth. Battery life is not better or worse. Everything seems to be working fine.
Post any questions and i'll try to answer
Cheers
Paul
Click to expand...
Click to collapse
Could you post the rom here..and does it support the fingerprint
How did you do that
PalakMi said:
How did you do that
Click to expand...
Click to collapse
First off you need fastboot tools installed and the Huawei Update Extractor downloaded http://forum.xda-developers.com/showthread.php?t=2433454
Download b131 p9 lite rom http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1164/g104/v53991/f1/full/update.zip. There is a later ROM for the p9 lite (b151) but the finger print sensor doesn't work with this ROM
Use the extractor to extract the boot.img and system.img files.
Use trwp to complete backup of phone to the micro SD card. Use trwp and select advanced wipe, wipe everything except the micro SD
Reboot to bootloader
Open command prompt from the folder you have extracted the boot and system images, type the following commands
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
If you have the 5c chinese phone this rom is great, much more stock feel.
If like me you are having issues with the POB trwp, use the trwp made for the p9 lite
Any question let us know
Great, no questions now so far
Can I port a P9 Lite Rom to an european Honor 5c (without finger print sensor and NFC) ??
minisaurio said:
Can I port a P9 Lite Rom to an european Honor 5c (without finger print sensor and NFC) ??
Click to expand...
Click to collapse
Not sure, don't have the european phone. Once you have a complete backup to revert to, you can't really do much harm testing
has anyone figured out, if this works for european copies of the phone as well?
and if yes, is there a chance to run the CM ROM from Meticulus?
i'd really love to see CM on my phone
Thx nice work
johdost said:
has anyone figured out, if this works for european copies of the phone as well?
and if yes, is there a chance to run the CM ROM from Meticulus?
i'd really love to see CM on my phone
Click to expand...
Click to collapse
Yes, I've got the beta build of CM running on my european 5C - you need to follow the install instructions carefully, and there's a couple of extra steps for the 5C - you need to change the install script as described in this post to get it to install (this goes for the TWRP install too):
http://forum.xda-developers.com/showpost.php?p=69989870&postcount=225
Once you've booted up, to get the camera to work you need to follow the instructions in this post:
http://forum.xda-developers.com/showpost.php?p=69990309&postcount=226
I've added the camera fix to a boot script so that I don't need to do it after every reboot. Once you've done that the ROM is working brilliantly (though with the same small issues the P9-lite users are having).
Malcolm52 said:
Yes, I've got the beta build of CM running on my european 5C - you need to follow the install instructions carefully, and there's a couple of extra steps for the 5C - you need to change the install script as described in this post to get it to install (this goes for the TWRP install too):
http://forum.xda-developers.com/showpost.php?p=69989870&postcount=225
Once you've booted up, to get the camera to work you need to follow the instructions in this post:
http://forum.xda-developers.com/showpost.php?p=69990309&postcount=226
I've added the camera fix to a boot script so that I don't need to do it after every reboot. Once you've done that the ROM is working brilliantly (though with the same small issues the P9-lite users are having).
Click to expand...
Click to collapse
Have tried the following from an adb shell, but the camera still doesn't work. It doesn't give the error about not been able to connect, it just hangs and displays nothing.
How did you go about adding the fix to the boot script?
Thanks
Paul
Here's the script I used, there may have been a typo in Meticulous' original:
#!/system/bin/sh
stop HwCamCfgSvr
HwCamCfgSvr hi6250 NEMO &
restart media
If you put those 4 lines in a file called:
/system/etc/init.d/99camerafix
Then make sure it's executable (chmod +x /system/etc/init.d/99camerafix) it should run on startup.
Malcolm52 said:
Here's the script I used, there may have been a typo in Meticulous' original:
#!/system/bin/sh
stop HwCamCfgSvr
HwCamCfgSvr hi6250 NEMO &
restart media
If you put those 4 lines in a file called:
/system/etc/init.d/99camerafix
Then make sure it's executable (chmod +x /system/etc/init.d/99camerafix) it should run on startup.
Click to expand...
Click to collapse
Should i name the file 99camerafix.sh or just 99camerafix?
Thanks again
Paul
Liffeyman said:
Should i name the file 99camerafix.sh or just 99camerafix?
Thanks again
Paul
Click to expand...
Click to collapse
Not sure it matters, but I created it without the .sh
Malcolm52 said:
Not sure it matters, but I created it without the .sh
Click to expand...
Click to collapse
Cool, im using the app solid explorer to give the file permissions. I gave it 777, were i think it should be 775. Let me try again.
Just out of curiosity, did you dirty flash the CM over an earlier version? Just reading some of the posts over on the p9 forms. Users are reporting a smoother rom when dirty flashing
Thanks
Paul
Liffeyman said:
Cool, im using the app solid explorer to give the file permissions. I gave it 777, were i think it should be 775. Let me try again.
Just out of curiosity, did you dirty flash the CM over an earlier version? Just reading some of the posts over on the p9 forms. Users are reporting a smoother rom when dirty flashing
Thanks
Paul
Click to expand...
Click to collapse
No, beta was the first build I tried. Nice and smooth for me, except when night mode is on or occasionally when balanced battery mode is selected - but performance battery mode seems to have reasonable battery life so I'm using that for now.
solved problem already, had some troubles packing the zip together again (mac issues...)
it works fine on my phone now (including camera) thanks a lot for the help!
With a little help.... http://forum.xda-developers.com/honor-5c/help/dev-info-support-honor-5c-cm-13-builds-t3517159
Thanks @Liffeyman.
Gonna try installing ur twrp backup of the p9-lite rom (stripped down of bloat + xtra app goodies). My model is the honor 5c Nem-l51. It's the uk 2gb ram/16gb storage without fingerprint sensor. I realize yours was the Chinese model so I'll let u know how I get on and hopefully it works just as well . Like u says, as long u perform a backup, there should be nothing to worry about :fingers-crossed:
If all goes well with that....I might download the B151 rom and extract the boot&system images and flash them as per your instructions previously. Hopefully that build will be even more stable/fast and the fact that the fingerprint sensor does not work is no problem for me as the uk model has no such sensor ?
Will post the outcome of my efforts in the next few days....
iantechie1979 said:
Thanks @Liffeyman.
Gonna try installing ur twrp backup of the p9-lite rom (stripped down of bloat + xtra app goodies). My model is the honor 5c Nem-l51. It's the uk 2gb ram/16gb storage without fingerprint sensor. I realize yours was the Chinese model so I'll let u know how I get on and hopefully it works just as well . Like u says, as long u perform a backup, there should be nothing to worry about :fingers-crossed:
If all goes well with that....I might download the B151 rom and extract the boot&system images and flash them as per your instructions previously. Hopefully that build will be even more stable/fast and the fact that the fingerprint sensor does not work is no problem for me as the uk model has no such sensor
Will post the outcome of my efforts in the next few days....
Click to expand...
Click to collapse
Just noticed with this, you will need to disable the Wi-Fi privacy police or it'll keep disbaling you wifi. I'll try upload a newer version of this shortly
I know this is a dumb question
Can i root Vivo y53 through flashing supersu/twrp through stock using the first script to verify the device?
Cause i just noticed the updater script have a first long script it is verified or just something where it can go through the recovery (it just putting a few mbn files)....then the a line shows up saying start changing here where you can see the common assert command flashing files...i have a little knowledge about the updater script but i know how to use it
Pls help us
I cant do this cause this is my daily driver
I know nobody rooted this device
Note i got the updater script in the official update
Here's the file
I know I need to have an unlocked bootloader to root Huawei phones. But I have found a new solution where there is no need to unlock the bootloader. Now I want to explain it. Huawei has a feature called sdcard update which flashes phone from sdcard. It made me think if I unpacked update.app and patched ramdisk_recovery by magic manager, I also replaced the real img with the patched img. Now I flashed it, result success. I magically checked the app and magically it was successfully installed. I have root access now.
Sorry for my poor English, I used Google translate.
Jonas336ts said:
I know I need to have an unlocked bootloader to root Huawei phones. But I have found a new solution where there is no need to unlock the bootloader. Now I want to explain it. Huawei has a feature called sdcard update which flashes phone from sdcard. It made me think if I unpacked update.app and patched ramdisk_recovery by magic manager, I also replaced the real img with the patched img. Now I flashed it, result success. I magically checked the app and magically it was successfully installed. I have root access now.
Sorry for my poor English, I used Google translate.
Click to expand...
Click to collapse
i would like to hear more about this
Can you make a video?
I too would love to hear more about this and exactly what to do
Yap please tutorial post how to do this
Used that method on p20 pro Indeed...but seemed that it did not work anymore since Android 9.0 or 9.1
deltaman83 said:
Used that method on p20 pro Indeed...but seemed that it did not work anymore since Android 9.0 or 9.1
Click to expand...
Click to collapse
Will Work, if you have a pc and Micro sdcard in phone.
Tabs78 said:
Can you make a video?
Click to expand...
Click to collapse
I make a video. Video will Come on Friday this month. I send link.
Have anybody tried this method? Any success?
Jonas336ts said:
I know I need to have an unlocked bootloader to root Huawei phones. But I have found a new solution where there is no need to unlock the bootloader. Now I want to explain it. Huawei has a feature called sdcard update which flashes phone from sdcard. It made me think if I unpacked update.app and patched ramdisk_recovery by magic manager, I also replaced the real img with the patched img. Now I flashed it, result success. I magically checked the app and magically it was successfully installed. I have root access now.
Sorry for my poor English, I used Google translate.
Click to expand...
Click to collapse
Interesting. I think you should provide more details:
1. Emui Version
2. Apps or tools used to unpacked repacked update app.
3. If there needs sign some files and tools used for that
4. other infos.
Jonas336ts said:
Will Work, if you have a pc and Micro sdcard in phone.
I make a video. Video will Come on Friday this month. I send link.
Click to expand...
Click to collapse
Where is the video link?
Jonas336ts said:
I know I need to have an unlocked bootloader to root Huawei phones. But I have found a new solution where there is no need to unlock the bootloader. Now I want to explain it. Huawei has a feature called sdcard update which flashes phone from sdcard. It made me think if I unpacked update.app and patched ramdisk_recovery by magic manager, I also replaced the real img with the patched img. Now I flashed it, result success. I magically checked the app and magically it was successfully installed. I have root access now.
Sorry for my poor English, I used Google translate.
Click to expand...
Click to collapse
As it successfull rooted as you say that so next we must go to work to cook some custom ROM
Josh said:
As it successfull rooted as you say that so next we must go to work to cook some custom ROM
Click to expand...
Click to collapse
You can't make a custom rom without sources. Besides, we still haven't got any tutorial regarding how to do this method.
Please, can you make a tutorial and show us a video @Jonas336ts
Too many pictures on first post.
Ok so I think I understand how he did it. Magisk has an option to manually patch a file. So basically, we use this guide to patch ramdisk_recovery.img : https://www.ytechb.com/how-to-patch-a-file-in-magisk-manager/
Now here comes another question : How do we get ramdisk_recovery.img? Simple. Find your ROM's update.zip file. Then, open update.app (or whatever it is called) using 7-zip and extract ramdisk_recovery from within. Then patch it with Magisk and then put it inside the update.app. Put update.app in your sdcard/flash drive and flash it using *#*#2846579#*#* method. Does it sound simple? Not really. There are a few issues with this and it sounds pretty strange that it works.
1.You need to sign the update.app file using Huawei keys. How did OP get these keys?
2.You can't simply replace files inside the update.app, unless you unpack and pack it, but again check reason 1 (unless the method has changed/I knew it wrong all this time)
3.It's impossible for the ROM to boot after doing this method. How can you still have root access when your bootloader is locked?
4.Doesn't EMUI know the update.app file was tempered? If it was that simple to flash stuff then we would have had a root guide like this a while ago.
Either way, this is my 2 cents. I am waiting for OP's video. But judging he/she's been inactive for a week, I doubt it.
EDIT
This method is impossible to be done. Reason being : There is absolutely no WAY you can get the update.app file for your rom MANUALLY. Unless you find a way to get Firmware Finder back, don't get your hope so high. I am sorry.
Another update : Ramdisk_recovery is not the type of IMG that Magisk patches. You need ramdisk.img. So basically this seems very fake. Still no tutorial.
AnotyClaws said:
Another update : Ramdisk_recovery is not the type of IMG that Magisk patches. You need ramdisk.img. So basically this seems very fake. Still no tutorial.
Click to expand...
Click to collapse
Try to find his other posts or topics. Pay attention to the date.
badmania98 said:
Try to find his other posts or topics. Pay attention to the date.
Click to expand...
Click to collapse
I did. Still nothing
I am trying my own method of rooting however I might risk bricking my phone. idk how I will sign the update.app or how to flash the img file with a locked bootloader...
In theory you should modify a dload firmware that can be written. But I suggest you to stay away.