[SOLVED] Bootloader and twrp issues - Honor 9 Questions & Answers

Hi there,
New here so thanks in advance for any help you guys could provide.
I need to root my Honor 9 for Android Development purposes so I tried to unlock the bootloader to install a TWRP.
(following this thread : https://forum.xda-developers.com/honor-9/how-to/how-to-root-honor-9-stf-l09c432b360a-t3778110)
When it comes to the "adb reboot recovery_ramdisk", it loads to that error message :
Error Mode
Attention!
Please update system again
Error!
Func no: 11 recovery image
Error no: 2 (load failed!)
Any clues of what i'm doing wrong and how I can get rid of that error message...?
(The goral is to root the phone using that Magisk thing everyone's talking about )
Thanks a lot!

still need help ?

oslo83 said:
still need help ?
Click to expand...
Click to collapse
Hi Oslo83!
Yup, still need help. I don't understand what i'have done wrong :/

Phone is still booting in normal mode ?
You got this error screen only when bootinng to recovery ?
Do you still have access ro bootloader ?
---------- Post added at 12:09 ---------- Previous post was at 12:09 ----------
-ro +to

phone is still booting, no probs with that, and I still have access to bootloader yup.
i get the error message when i boot into recovery with adb reboot recovery_ramdisk
if i boot into nrecovery by pressing the buttons, i have the default honor recovery appearing.

What firmware version and region are you on ?
8.0.0.xxx (Cyyy) ?
Recovery mode is 'recovery_ramdisk'...
You should boot in twrp 0.3 when booting into recovery, as you flashed it, if you typed the right command...
recovery and erecovery are 2 differents mode on differents partition.

oslo83 said:
What firmware version and region are you on ?
8.0.0.xxx (Cyyy) ?
Recovery mode is 'recovery_ramdisk'...
You should boot in twrp 0.3 when booting into recovery, as you flashed it, if you typed the right command...
recovery and erecovery are 2 differents mode on differents partition.
Click to expand...
Click to collapse
Version : 8.0.0.364
Region: C432
Well, as i said, i followed the thread step by step and yet, still no twrp.
Thing is, if I want to flash it again with adb (in case of something went wrong during flash?), well, i get a "FAILED" error

it wont flash with adb, but with fastboot it will...
I really think you messed the command you previously typed. Can you post them ?
You'll have to
Code:
fastboot flash recovery_ramdisk stf-twrp-zxz-0.3.img
again then to boot to recovery mode.
---------- Post added at 12:57 ---------- Previous post was at 12:56 ----------
Fant0hm said:
well, i get a "FAILED" error
Click to expand...
Click to collapse
Post the whole error output...

well, first, i connect the phone with usb debug and OEM enabled.
i do
Code:
adb reboot bootloader
wich give me the "fastboot&rescue mode" with phone unlocked and FRP unlock in red
then i do
Code:
fastboot flash recovery_ramdisk stf-twrp-zxz-0.3.img
and it tells me :
Code:
target didn't report max-dowload-size
sending 'recovery_ramdisk' (0KB)...
FAILED (command write failed 'No error))
finished. total time : 0.016s

You're stf-twrp-zxz-0.3.img is wrong or not i' your working folder. Download it again.
---------- Post added at 13:45 ---------- Previous post was at 13:45 ----------
-you're +your -i' +in

Oh! it worked!
Problem apparently wasn't the .img but the "Minimal adb and fastboot"
I downloaded sdk platform tools on my home personnal computer and managed to install twrp (plus, buttons and flash work correctly, yay!)
So, problem solved i guess.
Thanks a lot for your time, Oslo!

I'm using Minimal adb and fastboot without any problem.

oslo83 said:
I'm using Minimal adb and fastboot without any problem.
Click to expand...
Click to collapse
well, i don't know what else it could be. used the same files, the same commands...

Related

Search root for Archos Diamond 2 Plus

Hi !
I desesperatly seeking a root process for the Archos Diamond 2 Plus.
I can not find it by google.
As it looks like the P9000 of Elephone, I wondered if it was possible to use its recovery.img and supersu 1 and 2.
An idea ? A link for tutorial or for the stock rom (If root process failed) ?
Please ?
ok, no response.
I have tested with unlocked bootloader procedure but :
- i type adb reboot bootloader
- fastboot oem unlock
An normaly we confirm unlock with vol+ . But with archos diamond 2 plus, wol + is not active. There is no reaction at this moment.
So, if not unlocked bootloder, no flashing..
An idea ?
fanfan7110 said:
ok, no response.
I have tested with unlocked bootloader procedure but :
- i type adb reboot bootloader
- fastboot oem unlock
An normaly we confirm unlock with vol+ . But with archos diamond 2 plus, wol + is not active. There is no reaction at this moment.
So, if not unlocked bootloder, no flashing..
An idea ?
Click to expand...
Click to collapse
What android version?
android 6.0 marshmallow
fanfan7110 said:
android 6.0 marshmallow
Click to expand...
Click to collapse
You can boot into fastboot, which is good, in fastboot, type fastboot oem startftm. It will give you an error in the command line but what this allows you to do, is push files into partitions that are mounted R/W, that is of course, if this actually works for your device since every device is different.
Report results!
So after typed fastboot oem startftm i have the message "FAILED (remote: unknown command)"
And after to trying to put img file in boot , i have this : 'FAILED (remote: download for partition 'boot' is not allowed)"
fanfan7110 said:
So after typed fastboot oem startftm i have the message "FAILED (remote: unknown command)"
And after to trying to put img file in boot , i have this : 'FAILED (remote: download for partition 'boot' is not allowed)"
Click to expand...
Click to collapse
Please please please make a whole IMG backup since what we'll do might brick your device. I can't help you till Thursday, hit me up on Thursday with a reply on this thread.
---------- Post added at 08:51 PM ---------- Previous post was at 08:50 PM ----------
fanfan7110 said:
So after typed fastboot oem startftm i have the message "FAILED (remote: unknown command)"
And after to trying to put img file in boot , i have this : 'FAILED (remote: download for partition 'boot' is not allowed)"
Click to expand...
Click to collapse
Also, it is supposed to say failed when you start it.
hummm i can't take a backup of boot.img, because SU is not installed..
fanfan7110 said:
hummm i can't take a backup of boot.img, because SU is not installed..
Click to expand...
Click to collapse
Well, since the device is running mtk, try this. Flash the superuser binary and report, also, I am NOT responsible for anything, YOU are making these changes.
ok tested, but don't work with marshmallow. MTK Droid tools is incompatible with V6
fanfan7110 said:
ok tested, but don't work with marshmallow. MTK Droid tools is incompatible with V6
Click to expand...
Click to collapse
Well, now you have a mission to somehow port a working recovery to your phone.

OPX Remote dtb not found solution

when you update to 3.1.0 twrp recovery is not compactible with the new recovery partition so you need to flash opxstock 3.1.0 recovery so that you will be able to flash android lollipop version of the opx and reroot and install twrp.
the proccess is really simple
1)go to settings about phone and enable developer options by tapping build number 10 times.
2)enable adb and oem unlocking
3)go to the folder you have adb and fastboot installed
4)Place the downloaded recovery file there(the one FROM THIS THREAD!)
5)type 'adb reboot bootloader'
Phone will reboot to bootloader
6)type 'fastboot flash recovery recovery.img'(or the name you gave for the recovery with '.img' at the end)
7)type 'fastboot boot recovery.img'
8)flash update.zip (the 2.1.1 version)If you cannot find the link to the file comment bellow
9)flash the update.zip via stock recovery.
10)your phone is back to stock now and you are able to flash twrp recovery and root your phone now.
Please hit thanks if i helped
EDIT:Unzip the recovery file fist
Post this in General Section
Sorry I can't find the link to update.zip
Please post the update.zip file
adb doesn't recognize my phone anymore, now that I want to try it again with the file from this forum. And it seems to be stuck in fastboot mode.
What should I do?
---------- Post added at 07:31 PM ---------- Previous post was at 07:23 PM ----------
brii_22 said:
adb doesn't recognize my phone anymore, now that I want to try it again with the file from this forum. And it seems to be stuck in fastboot mode.
What should I do?
Click to expand...
Click to collapse
Okay I found it.
Type in adb 'fastboot devices'
it wil recognise your phone
Then 'fastboot reboot'
And my phone works again, and I guess I can just restart the proces now
(replied to myself in case someone else has this problem )
GerasxD said:
when you update to 3.1.0 twrp recovery is not compactible with the new recovery partition so you need to flash opxstock 3.1.0 recovery so that you will be able to flash android lollipop version of the opx and reroot and install twrp.
the proccess is really simple
1)go to settings about phone and enable developer options by tapping build number 10 times.
2)enable adb and oem unlocking
3)go to the folder you have adb and fastboot installed
4)Place the downloaded recovery file there(the one FROM THIS THREAD!)
5)type 'adb reboot bootloader'
Phone will reboot to bootloader
6)type 'fastboot flash recovery recovery.img'(or the name you gave for the recovery with '.img' at the end)
7)type 'fastboot boot recovery.img'
8)flash update.zip (the 2.1.1 version)If you cannot find the link to the file comment bellow
9)flash the update.zip via stock recovery.
10)your phone is back to stock now and you are able to flash twrp recovery and root your phone now.
Please hit thanks if i helped
EDIT:Unzip the recovery file fist
Click to expand...
Click to collapse
many have ask and cannot find the update.zip 2.1.1, where are you?
Hi, It's not working for me.
I still get the same error message: `FAILED (remote: dtb not found)` when I try to boot into recovery.
I would really appreciate some help here
Thanks anyway. I'll keep searching.
---------- Post added at 04:46 AM ---------- Previous post was at 03:51 AM ----------
guiohm said:
Hi, It's not working for me.
I still get the same error message: `FAILED (remote: dtb not found)` when I try to boot into recovery.
I would really appreciate some help here
Thanks anyway. I'll keep searching.
Click to expand...
Click to collapse
Ok, I solved my problem. I had to revert to an older TWRP. I just didn't know that the new updated TWRP is not backward compatible (that's bad) and I couldn't find an older one until I stumbled upon this thread: http://forum.xda-developers.com/showpost.php?p=69170103&postcount=45
guiohm : Thank you SO MUCH ! I searched this solution for hours. I can't tell you how grateful I am.
THANK YOU!
brii_22 said:
adb doesn't recognize my phone anymore, now that I want to try it again with the file from this forum. And it seems to be stuck in fastboot mode.
What should I do?
---------- Post added at 07:31 PM ---------- Previous post was at 07:23 PM ----------
Okay I found it.
Type in adb 'fastboot devices'
it wil recognise your phone
Then 'fastboot reboot'
And my phone works again, and I guess I can just restart the proces now
(replied to myself in case someone else has this problem )
Click to expand...
Click to collapse
Thank you so much! I had the same problem and had no idea what to do.
FingolfinTheEldar said:
Sorry I can't find the link to update.zip
Click to expand...
Click to collapse
You can find it in the One Plus Website for the one plus x. it the rom
Official one okay?
Is it also ok, to take the official twrp 3.1.1-1-onyx from the twrp website?
Thanks
OPforlife said:
Is it also ok, to take the official twrp 3.1.1-1-onyx from the twrp website?
Thanks
Click to expand...
Click to collapse
Not at all. The point is to flash an old offcieal recovery, then OOS 3 to update bootloader.
If you already are on the new bootloader no need to do that.
if you're not, BLupdater.
If already try to flash something not compatible, you may haave to run the Mega unbrick Guide.
Same isse with E1001
I had the same issue "remote: dtb not found" when trying to use recent (3+) versions of TWRP on my E1001 One Plus X. I ended up discovering that only an old version of TWRP (2.8.7) would boot on the device. Here is the version I used successfully on One Plus X E1001 (white): twrp-2.8.7.0-6.0-onyx.img. I cannot post a link to it as the forum is preventing new users to publish external links but I have it if needed.

[Q] Need help with ASUS ME302KL

I just install TWRP RECOVERY without unlock tablet.
Now, when booting i have the message "ERROR: Can't load invalid boot image" with the ASUS Logo.
And fastboot mode shows the message "Invalid boot image !!!".
Fastboot mode is fine. I try flash boot.img recovery.img i can find.
But it still not work.
I download ASUS website firmware V10.10.3.39.
I try fastboot update, but get the message "update package has no android-info.txt"
Because i dont unlock bootloader first, i cant fastboot boot twrp.img.
Does anyone have stock boot.img recovery.img system.img or update.zip for ME302KL? Or anything I can try?
wch0503 said:
I just install TWRP RECOVERY without unlock tablet.
Now, when booting i have the message "ERROR: Can't load invalid boot image" with the ASUS Logo.
And fastboot mode shows the message "Invalid boot image !!!".
Fastboot mode is fine. I try flash boot.img recovery.img i can find.
But it still not work.
I download ASUS website firmware V10.10.3.39.
I try fastboot update, but get the message "update package has no android-info.txt"
Because i dont unlock bootloader first, i cant fastboot boot twrp.img.
Does anyone have stock boot.img recovery.img system.img or update.zip for ME302KL? Or anything I can try?
Click to expand...
Click to collapse
Did you find any solution? İ have same problem.
wch0503 said:
I just install TWRP RECOVERY without unlock tablet.
Now, when booting i have the message "ERROR: Can't load invalid boot image" with the ASUS Logo.
And fastboot mode shows the message "Invalid boot image !!!".
Fastboot mode is fine. I try flash boot.img recovery.img i can find.
But it still not work.
I download ASUS website firmware V10.10.3.39.
I try fastboot update, but get the message "update package has no android-info.txt"
Because i dont unlock bootloader first, i cant fastboot boot twrp.img.
Does anyone have stock boot.img recovery.img system.img or update.zip for ME302KL? Or anything I can try?
Click to expand...
Click to collapse
Try unlocking bootloader type in
* Fastboot OEM unlock
Danyaelgaina said:
Try unlocking bootloader type in
* Fastboot OEM unlock
Click to expand...
Click to collapse
I've got the same problem when I was installing And 7 on the device. Unfortunately I need a step by step leading! I'm not exactly expert.
MikeHugi said:
I've got the same problem when I was installing And 7 on the device. Unfortunately I need a step by step leading! I'm not exactly expert bbbbbiiiittttccchhhheeesssss.
Click to expand...
Click to collapse
Type in fastboot oem unlock
Or get tutorial for bootload3r unlock for ur phone
---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------
MikeHugi said:
I've got the same problem when I was installing And 7 on the device. Unfortunately I need a step by step leading! I'm not exactly expert bbbbbiiiittttccchhhheeesssss.
Click to expand...
Click to collapse
Ok
I have done it already , but nothing happened by typing "Fastboot OEM unlock"!
I couldn't find any tutorial for bootloader unlocking for ME302KL
I have the same problem and my pad does not unlock. What solution is there and where should I write fastboot oem unlock?
Thank you
---------- Post added at 04:11 PM ---------- Previous post was at 04:04 PM ----------
Danyaelgaina said:
Try unlocking bootloader type in
* Fastboot OEM unlock
Click to expand...
Click to collapse
please help me
im in the iran
me302kl-unluck app writing .
an unknown error occurs. which may be a network connection issue.
please help me

Bricked Honor 9

[you can use this tool to solve brick problems https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279]
Hi everyone, I'm "new" on the forum. "New" because they are days looking for answers to repair my Honor 9...
After unlocking it, installed twrp and RRos 6.0 I made a mistake, I uninstalled the gapps from the system manually, and after restarting the phone, various error messages continued on terminated processes (com.google... stopped working).
I tried again to reinstall the gapps via twrp but nothing to do, after trying to reinstall the RRos (with full wipe), new error messages kept going out, but this time not only the gapps.. (trebuchet etc ...).
Trying several wipes and reinstallations of the RRos, I tried to go back to the EMUI 8.0, so I tried to install the European firmware via SD and folder DLOAD, but once I got to 5% the installation crashes.
Via fastboot I also tried to install the twrp again, but the recovery stock continues to appear.
Looking on xda and generally on the internet I have found various people with this problem and they have tried to solve with programs like DC-Unlocker or Phoenix, but they had locked bootloader or frp .. I from fastboot I have PHONE Unlocked and FRP Unlock.
I also tried to flash the img contained in the UPDATE.APP file, but nothing happens ... just recovery stock. Help please i am desperate :crying: and sorry for my english.
EDIT - 27/03/2018
-I solved many of the problems I had in this post, now I'm still in the twrp and I can not flash the stock firmware.
-I'm trying to format the microsd in exfat and then install update.app.
-I can not copy the 4.66GB update.app file to the MicroSD in exfat, fat or ext4 via twrp / PC. I will try with another SD reader.
-I formatted the sd in exfat and I managed to copy the dload folder, run the restore and no longer blocked at 5% (gave a 99% error). The system started and I went back to the b130 with nougat, now I try again to install the b120 to restore the captive keys. (trying again with hwota)
-Hwota worked, now with the b120 everything works correctly, now I'm looking for a way to restore OTA Updates.(I will try to install the b183)
-With the b183 ota works, but not the keys / flash. I will try to downgrade to b120, than reupdate to b183 without wipe anything .
-b120 keys working, update to b183 and not working again, I try update ota oreo and search for a kernel.
-Almost everything resolved! After switching from the b183 to the b360, I reunlocked the Honor and installed the kernel with the fix to the capacitive keys. Relock the phone but the Google Logo appears at boot, even after installing the stock kernel.
Kodex_99 said:
Trying several wipes and reinstallations of the RRos, I tried to go back to the EMUI 8.0, so I tried to install the European firmware via SD and folder DLOAD, but once I got to 5% the installation crashes.
Via fastboot I also tried to install the twrp again, but the recovery stock continues to appear.
Click to expand...
Click to collapse
If you were on oreo, it's normal the nougat service repair files don't work with dload.
You're still on RRos ?
oslo83 said:
If you were on oreo, it's normal the nougat service repair files don't work with dload.
Click to expand...
Click to collapse
Can I try with non-European firmware such as Russian or Chinese upgraded to Oreo?
oslo83 said:
You're still on RRos ?
Click to expand...
Click to collapse
No, I did several wipe and tried to restore other system.img
Kodex_99 said:
Can I try with non-European firmware such as Russian or Chinese upgraded to Oreo?
No, I did several wipe and tried to restore other system.img
Click to expand...
Click to collapse
To my knowledge, they are no oreo service repair firmware publicly available yet. So, for now, no flashing firmware with dload once on oreo.
You could use HWOTA8to8 or HWOTA8to7 or the translated russian TOOL from last febuary.
oslo83 said:
You could use HWOTA8to8 or HWOTA8to7 or the translated russian TOOL from last febuary.
Click to expand...
Click to collapse
I only find missing files
Honor 9 multitool eng (feb2018)
https://forum.xda-developers.com/hon...5#post75662105
oslo83 said:
Honor 9 multitool eng (feb2018)
https://forum.xda-developers.com/hon...5#post75662105
Click to expand...
Click to collapse
========================================================================================
Copying the firmware files to the SD card
Please wait ....
========================================================================================
adb: error: failed to get feature set: no devices/emulators found
unfortunately when I try to install the EMUI 8 (the one I had previously installed) from fastboot I get this error message..
Kodex_99 said:
Copying the firmware files to the SD card
Please wait ....
========================================================================================
adb: error: failed to get feature set: no devices/emulators found
unfortunately when I try to install the EMUI 8 (the one I had previously installed) from fastboot I get this error message..
Click to expand...
Click to collapse
You need to be in twrp or system to copy file from your pc to sdcard with adb.
oslo83 said:
You need to be in twrp or system to copy file from your pc to sdcard with adb.
Click to expand...
Click to collapse
The problem is just that... also flash system or twrp, I always get eRecovery, I can try to copy the files on sd from another system however (as I did previously with the dload) but erecovery stucks at 5%
Kodex_99 said:
The problem is just that... also flash system or twrp, I always get eRecovery, I can try to copy the files on sd from another system however (as I did previously with the dload) but erecovery stucks at 5%
Click to expand...
Click to collapse
Once in fastboot boot, what command did you typed to flash stock recovery ?
---------- Post added at 20:20 ---------- Previous post was at 20:20 ----------
Or twrp
oslo83 said:
Once in fastboot boot, what command did you typed to flash stock recovery ?
---------- Post added at 20:20 ---------- Previous post was at 20:20 ----------
Or twrp
Click to expand...
Click to collapse
As I had an official oreo, I used it "fastboot flash recovery_ramdisk twrp.img"
I have just discovered that I can not even wipe from the recovery stock :/
Good, maybe you're doing the key combination wrong:
https://4pda.ru/forum/index.ph...72246&st=800#entry55689846
---------- Post added at 20:27 ---------- Previous post was at 20:26 ----------
So you manage to boot to stock recovery or was it erecovery again ?
oslo83 said:
Good, maybe you're doing the key combination wrong:
https://4pda.ru/forum/index.ph...72246&st=800#entry55689846
Click to expand...
Click to collapse
404
oslo83 said:
So you manage to boot to stock recovery or was it erecovery again ?
Click to expand...
Click to collapse
I have Stock recovery with + button, eRecovery with normal system boot and Fastboot with - button
So, boot to fastboot and flash oreo twrp.
Then boot to twrp recovery like you would have done for booting to stock recovery.
---------- Post added at 20:37 ---------- Previous post was at 20:31 ----------
https://4pda.ru/forum/index.php?showtopic=772246&st=800#entry55689846
oslo83 said:
So, boot to fastboot and flash oreo twrp.
Click to expand...
Click to collapse
I flash it, but when I try to start it I always go back to the recovery stock...
Previously I had installed the twrp but I do not know why the stock returned after several wipes
Do again:
fastboot devices
Then
fastboot flash recovery_ramdisk twrp.img
Then
fastboot reboot recovery
Paste us your output.
What twrp do you used ? 0.2 or 0.3 ?
oslo83 said:
Do again:
fastboot devices
Then
fastboot flash recovery_ramdisk twrp.img
Then
fastboot reboot recovery
Paste us your output.
Click to expand...
Click to collapse
" PS C:\Users\Kodex\Downloads> fastboot devices
7BK0217B04002898 fastboot
PS C:\Users\Kodex\Downloads> fastboot flash recovery_ramdisk twrp.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (27144 KB)...
OKAY [ 0.689s]
writing 'recovery_ramdisk'...
OKAY [ 0.289s]
finished. total time: 0.979s "
unrecognized reboot command.
oslo83 said:
What twrp do you used ? 0.2 or 0.3 ?
Click to expand...
Click to collapse
Up to a few hours ago the 0.2, now the 0.3 but does not change anything...
Keep trying to boot to twrp recovery
---------- Post added at 21:03 ---------- Previous post was at 21:02 ----------
Usb must be unpgugged
oslo83 said:
Keep trying to boot to twrp recovery
Click to expand...
Click to collapse
nothing.. only stock recovery
oslo83 said:
Usb must be unpgugged
Click to expand...
Click to collapse
i tried this
PS C:\Users\Kodex\Downloads> fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.690s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.696s

I need help flashing to boot partition. (MediaTek Device)

I own an Alcatel 3(5052A) shipped with Android 8.1.0. It has a Mediatek MT6739 chipset. I managed to do fastboot oem unlock to unlock the bootloader and flash the official Resurrection Remix GSI successfully but when I attempt to flash Magisk patched boot image I get a fastboot error.
Code:
FAILED (remote: Only system partition can be flashed)
Does anyone know a method to unlock flashing for the other partitions?
I already tried 'fastboot flashing unlock_critical' to no success.
Thanks.
The same on alcatel 1
Im having the same issue at flashing twrp on alcatel 1 :crying:
Ya, me too, having the same issue. It says " Only system partition can be flashed", what does that even mean??? I've unlocked the bootloader Alcatel 1 & yet I get this error.
Is it something to do with the firmware we're on??
Bythos73 said:
I own an Alcatel 3(5052A) shipped with Android 8.1.0. It has a Mediatek MT6739 chipset. I managed to do fastboot oem unlock to unlock the bootloader and flash the official Resurrection Remix GSI successfully but when I attempt to flash Magisk patched boot image I get a fastboot error.
Does anyone know a method to unlock flashing for the other partitions?
I already tried 'fastboot flashing unlock_critical' to no success.
Thanks.
Click to expand...
Click to collapse
If you have your boot.img file go look up mtk-su (I've used this before it's a really good tool). if you don't already have root access then you can use that and run the following in the root shell:
mtk-su gives you a temp root shell for that session and your free to do as you please with it so hopefully that helps you guys
dd if=/sdcard/boot.img if=/dev/block/<path to boot>
Also if you need to try these both:
fastboot oem unlock_critical
fastboot flashing unlock_critical
And you should be good to go
Ensure you place boot.img under /sdcard or similar to where you'd like to flash
---------- Post added at 01:19 AM ---------- Previous post was at 01:18 AM ----------
dagman5 said:
Im having the same issue at flashing twrp on alcatel 1 :crying:
Click to expand...
Click to collapse
Do the same with what I expla below but do the recovery partition
---------- Post added at 01:20 AM ---------- Previous post was at 01:19 AM ----------
sachb_htc said:
Ya, me too, having the same issue. It says " Only system partition can be flashed", what does that even mean??? I've unlocked the bootloader Alcatel 1 & yet I get this error.
Is it something to do with the firmware we're on??
Click to expand...
Click to collapse
This means even with the bootloader unlocked the OEM has still restricted flashing other partitions. It's a custom implementation they have in place
TheExploitedOne said:
If you have your boot.img file go look up mtk-su (I've used this before it's a really good tool). if you don't already have root access then you can use that and run the following in the root shell:
mtk-su gives you a temp root shell for that session and your free to do as you please with it so hopefully that helps you guys
dd if=/sdcard/boot.img if=/dev/block/<path to boot>
Also if you need to try these both:
fastboot oem unlock_critical
fastboot flashing unlock_critical
And you should be good to go
Ensure you place boot.img under /sdcard or similar to where you'd like to flash
---------- Post added at 01:19 AM ---------- Previous post was at 01:18 AM ----------
Do the same with what I expla below but do the recovery partition
---------- Post added at 01:20 AM ---------- Previous post was at 01:19 AM ----------
This means even with the bootloader unlocked the OEM has still restricted flashing other partitions. It's a custom implementation they have in place
Click to expand...
Click to collapse
But, there are many sources claiming that you can install a custom recovery like "Twrp" on the Alcatel 1.
Sent from my LM-G710 using Tapatalk
sachb_htc said:
But, there are many sources claiming that you can install a custom recovery like "Twrp" on the Alcatel 1.
Click to expand...
Click to collapse
Yes their Bootloader's are able to be unlocked. If that's the case your able to flash a custom recovery because signature verification is disabled in this state. You'd probably have to build the source code to be able to flash if not already available
TheExploitedOne said:
Yes their Bootloader's are able to be unlocked. If that's the case your able to flash a custom recovery because signature verification is disabled in this state. You'd probably have to build the source code to be able to flash if not already available
Click to expand...
Click to collapse
This is one of the site, which claims to have twrp installed on Alcatel 1: https://unofficialtwrp.com/twrp-3-3-0-root-alcatel-5033d/
sachb_htc said:
This is one of the site, which claims to have twrp installed on Alcatel 1: https://unofficialtwrp.com/twrp-3-3-0-root-alcatel-5033d/
Click to expand...
Click to collapse
Looking at said site it don't seem to be legit
So I found this thread and my long dead hopes of dropping a twrp into my device twitched, I mean after so many road blocks I'm surprised my hopes even budged but anyway here goes.
AOSP v32 android 8.1 installed on my Alcatel 5033A su version so I have root... ish
I can't write anything to the system and it stays there (after moving if it goes it's removed on reboot) and that's if I remount to RW cause otherwise even with root moving anything fails, all along I've been flashing my recovery with flashify and keep breaking recovery only to try fastboot method after realizing I can install a TWRP built for MediaTek MT6739 Chipset but that's how I saw the problem, it seems to be the same I get this error too >only system partition can be flashed<.
fastboot oem unlock_critical
fastboot flashing unlock_critical
Tried these codes and yeah I was able to do the unlock but afterwards I typed
Fastboot flash recovery <path> do you see my suffering T_T do you see cause I see no (-u)
rubbed it in my own face to see if I'd laugh too didn't even realize I typed this like three times without -u
So on reboot I see the start button checked logs on my pc I'm back at square 1 this phone is cursed like someone from the dev team just sat chanting for hours just to make my life miserable.

Categories

Resources