Ciao tutti!
I have a T-Mobile DE2118 with Android 12 DE2118_11_C.16, SIM and bootloader unlocked. The goal is to get TWRP installed and to root the device. When I try to fastboot from Linux using either of the TWRP images from EnumC (twrp-3.5.2-11-holi.img and twrp-3.5.2-11-2-dre8t.img) I get this:
Code:
fastboot boot twrp-3.5.2-11-2-dre8t.img
downloading 'boot.img'...
OKAY [ 2.752s]
booting...
FAILED (remote: unknown command)
finished. total time: 2.752s
Is this expected because I have done something wrong? There are some additional steps for the DE2118? A different TWRP? Perhaps there is a special Windows fastboot as I have seen references to fastboot enhanced? I see detailed references for how to do things for the DE2117 but I believe I am missing something with this DE2118.
Thanks for some clues or help!
A working TWRP has not been ported to this device.
You can convert your device to STOCK OEM and root with my guides and this will also bring you up to C_17.
Thanks! In fact, yesterday I used your "Full Convert Tmobile...dummies" to prepare an old Windows-7 partition to do this but I have been working up the courage to make the attempt. It is reassuring to hear that I am on the right track.
katooom said:
Thanks! In fact, yesterday I used your "Full Convert Tmobile...dummies" to prepare an old Windows-7 partition to do this but I have been working up the courage to make the attempt. It is reassuring to hear that I am on the right track.
Click to expand...
Click to collapse
Make sure you install .net v4.5 on there before you install Fastboot Enhance
scanman0 said:
Make sure you install .net v4.5 on there before you install Fastboot Enhance
Click to expand...
Click to collapse
Thanks! By chance, it seems that I already had .net 4.8 installed from 2019. However, during setup I did have to setup the Visual Studio 2015 redistributable package.
katooom said:
Ciao tutti!
I have a T-Mobile DE2118 with Android 12 DE2118_11_C.16, SIM and bootloader unlocked. The goal is to get TWRP installed and to root the device. When I try to fastboot from Linux using either of the TWRP images from EnumC (twrp-3.5.2-11-holi.img and twrp-3.5.2-11-2-dre8t.img) I get this:
Code:
fastboot boot twrp-3.5.2-11-2-dre8t.img
downloading 'boot.img'...
OKAY [ 2.752s]
booting...
FAILED (remote: unknown command)
finished. total time: 2.752s
Is this expected because I have done something wrong? There are some additional steps for the DE2118? A different TWRP? Perhaps there is a special Windows fastboot as I have seen references to fastboot enhanced? I see detailed references for how to do things for the DE2117 but I believe I am missing something with this DE2118.
Thanks for some clues or help
Click to expand...
Click to collapse
here is a working .IMG file for the Nord N200 DE2118. for some reason it won't let me upload it
Working TWRP for OnePlus Nord N200 .img file why won't it let me upload it
The problem is that's for Android 11, your running android 12. Best case scenario you brick your device
I know this from personal experience lol
katooom said:
Ciao tutti!
I have a T-Mobile DE2118 with Android 12 DE2118_11_C.16, SIM and bootloader unlocked. The goal is to get TWRP installed and to root the device. When I try to fastboot from Linux using either of the TWRP images from EnumC (twrp-3.5.2-11-holi.img and twrp-3.5.2-11-2-dre8t.img) I get this:
Code:
fastboot boot twrp-3.5.2-11-2-dre8t.img
downloading 'boot.img'...
OKAY [ 2.752s]
booting...
FAILED (remote: unknown command)
finished. total time: 2.752s
Is this expected because I have done something wrong? There are some additional steps for the DE2118? A different TWRP? Perhaps there is a special Windows fastboot as I have seen references to fastboot enhanced? I see detailed references for how to do things for the DE2117 but I believe I am missing something with this DE2118.
Thanks for some clues or help!
Click to expand...
Click to collapse
If your trying to root, use magisk.
Related
WiFi version obviously. Doing this on a Mac, trying to flash the new 5.1.1
I unlocked the bootloader successfully today, downloaded the most recent version of Android SDK and am operating out of /Library/Android/sdk/platform-tools
When I go to 'fastboot flash system system.img,' it gives this:
Code:
fastboot flash system system.img
sending 'system' (1850429 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.007s
no idea what to do, any help is appreciated
sF groth said:
WiFi version obviously. Doing this on a Mac, trying to flash the new 5.1.1
I unlocked the bootloader successfully today, downloaded the most recent version of Android SDK and am operating out of /Library/Android/sdk/platform-tools
When I go to 'fastboot flash system system.img,' it gives this:
Code:
fastboot flash system system.img
sending 'system' (1850429 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.007s
no idea what to do, any help is appreciated
Click to expand...
Click to collapse
I'm not familiar with Mac. But on Windows and Linux machines that is usually a sign of an old(er) install of SDK. But you did say you just updated to the latest, so I'm stumped.
Yeah I'm trying it on a Windows PC at work now, gonna do a fresh SDK install and a fresh image install. Maybe it didn't DL the image right? Gonna try every option
It worked on the PC with a fresh ADB and fastboot, just couldn't find one for my Mac
sF groth said:
It worked on the PC with a fresh ADB and fastboot, just couldn't find one for my Mac
Click to expand...
Click to collapse
Glad to hear it. As I said before, I'm not familiar with Mac's, but I've got a question for you. On Linux, one can install "ADB & fastboot" from the local repositories, rather than the full Android SDK download from Google. Is that what you did? Or did you download the full Android SDK?
Hello Everyone!
I unlocked and installed TWRP on my P20 lite, but now I want to be able to install the updates of Huawei again (especially when Android P is about to release).
So how do I uninstall TWRP and if it's possbile lock my phone again?
(am not that amazing with Smartphone software, so just saying...)
Greets Louis
LouisJ444 said:
Hello Everyone!
I unlocked and installed TWRP on my P20 lite, but now I want to be able to install the updates of Huawei again (especially when Android P is about to release).
So how do I uninstall TWRP and if it's possbile lock my phone again?
(am not that amazing with Smartphone software, so just saying...)
Greets Louis
Click to expand...
Click to collapse
Maybe this thread somehow can helps you:
https://forum.xda-developers.com/huawei-p20-lite/help/req-stock-recovery-p20-lite-t3803027
Don't need lock bootloader to install or receive via OTA official updates.
Lock the bootloader is not possible (maybe it is, but is a pay service).
You can relock instead of lock, but don't do it if your device is not completely stock.
Within the little experience that I have with this team I have investigated the following, when flasheas the official roms by twrp the boatloader is blocked again and the twrp is erased
kilroystyx said:
Maybe this thread somehow can helps you:
https://forum.xda-developers.com/huawei-p20-lite/help/req-stock-recovery-p20-lite-t3803027
Don't need lock bootloader to install or receive via OTA official updates.
Lock the bootloader is not possible (maybe it is, but is a pay service).
You can relock instead of lock, but don't do it if your device is not completely stock.
Click to expand...
Click to collapse
I still don't really understand how it works:
I downloaded the huawei extractor and extracted the files in a folder on my computer.
I got a update.zip file from my phone and extracted it on my computer.
But when I try to open the update.app file I get an error message saying:
https://i.gyazo.com/abce07c696fb31f15b95c832e3baa899.png
(if it doesn't work: ERECOVERY_VBMET.img: Invalid header crc - Expected: 42613 Got 18415)
LouisJ444 said:
I still don't really understand how it works:
I downloaded the huawei extractor and extracted the files in a folder on my computer.
I got a update.zip file from my phone and extracted it on my computer.
But when I try to open the update.app file I get an error message saying:
https://i.gyazo.com/abce07c696fb31f15b95c832e3baa899.png
(if it doesn't work: ERECOVERY_VBMET.img: Invalid header crc - Expected: 42613 Got 18415)
Click to expand...
Click to collapse
Remove the verification on the settings, check pic enclosed.
Mannuok said:
Within the little experience that I have with this team I have investigated the following, when flasheas the official roms by twrp the boatloader is blocked again and the twrp is erased
Click to expand...
Click to collapse
Your are partially correct.
Flashing official firmware with TWRP, have to be done with HuRUpdater, during installation the TWRP is replaced by stock recovery, then is your decision keep it or not.
About lock bootloader, mine is unlocked since day one and every time that I install new firmware it keep it unlocked. My experience so far is installing ANE-LX1 firmware in my ANE-LX1 device, probably with other firmware like ANE-AL00 or ANE-TL00 it can be different.
kilroystyx said:
Remove the verification on the settings, check pic enclosed.
Click to expand...
Click to collapse
So I can't seem to do "adb reboot bootloader" It will just go to the system.
And when I manually go into the bootloader and try to flash it, I get this error
Before this I tried to flash an other recovery on it which I found on a guide, but after I did that TWRP did get removed but I can't get on the recovery anymore and updating doesn't work either.
LouisJ444 said:
So I can't seem to do "adb reboot bootloader" It will just go to the system.
And when I manually go into the bootloader and try to flash it, I get this error
Before this I tried to flash an other recovery on it which I found on a guide, but after I did that TWRP did get removed but I can't get on the recovery anymore and updating doesn't work either.
Click to expand...
Click to collapse
In the Fastboot&Rescue Mode screen did you see phone unlocked and FRP unlock ?
Can you share all commands that you are using, can be text like you see bellow:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery_ramdisk TWRP_3.2.1-0_ANE-LX1_Full_01.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24962 KB)...
OKAY [ 0.861s]
writing 'recovery_ramdisk'...
OKAY [ 0.109s]
finished. total time: 0.970s
Are you trying to use command recovery instead of recovery_ramdisk?
kilroystyx said:
In the Fastboot&Rescue Mode screen did you see phone unlocked and FRP unlock ?
Can you share all commands that you are using, can be text like you see bellow:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery_ramdisk TWRP_3.2.1-0_ANE-LX1_Full_01.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24962 KB)...
OKAY [ 0.861s]
writing 'recovery_ramdisk'...
OKAY [ 0.109s]
finished. total time: 0.970s
Are you trying to use command recovery instead of recovery_ramdisk?
Click to expand...
Click to collapse
1. It says: Phone Unlocked
FRP Unlock
2. When I was in this screen I do:
- cd C:\Users\Louis\Desktop\platform-tools
- fastboot flash recovery RECOVERY_RAMDIS.img
then it gives the error
3. When I try to do it normally, I do:
- cd C:\Users\Louis\Desktop\platform-tools
- adb reboot bootloader
LouisJ444 said:
1. It says: Phone Unlocked
FRP Unlock
2. When I was in this screen I do:
- cd C:\Users\Louis\Desktop\platform-tools
- fastboot flash recovery RECOVERY_RAMDIS.img
then it gives the error
3. When I try to do it normally, I do:
- cd C:\Users\Louis\Desktop\platform-tools
- adb reboot bootloader
Click to expand...
Click to collapse
You have to use recovery_ramdisk because this is the name of the partition in this Android version.
I assume that you didn't change the name of the stock recovery extracted, for your case the right command is:
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
kilroystyx said:
You have to use recovery_ramdisk because this is the name of the partition in this Android version.
I assume that you didn't change the name of the stock recovery extracted, for your case the right command is:
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
Click to expand...
Click to collapse
Thanks, that seemed to work!
kilroystyx said:
Your are partially correct.
Flashing official firmware with TWRP, have to be done with HuRUpdater, during installation the TWRP is replaced by stock recovery, then is your decision keep it or not.
About lock bootloader, mine is unlocked since day one and every time that I install new firmware it keep it unlocked. My experience so far is installing ANE-LX1 firmware in my ANE-LX1 device, probably with other firmware like ANE-AL00 or ANE-TL00 it can be different.
Click to expand...
Click to collapse
Where I get the original romes of Huawei???
Mannuok said:
Where I get the original romes of Huawei???
Click to expand...
Click to collapse
web version:
http://pro-teammt.ru/firmware-database/?firmware_model=&firmware_page=0
android version:
https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder
some tips:
https://forum.xda-developers.com/hu...om-official-emui-8-0-huawei-p20-lite-t3773999
kilroystyx said:
Your are partially correct.
Flashing official firmware with TWRP, have to be done with HuRUpdater, during installation the TWRP is replaced by stock recovery, then is your decision keep it or not.
About lock bootloader, mine is unlocked since day one and every time that I install new firmware it keep it unlocked. My experience so far is installing ANE-LX1 firmware in my ANE-LX1 device, probably with other firmware like ANE-AL00 or ANE-TL00 it can be different.
Click to expand...
Click to collapse
ANE LX3 no funciona asi,
Mannuok said:
ANE LX3 no funciona asi,
Click to expand...
Click to collapse
what do you mean by that?
kilroystyx said:
Maybe this thread somehow can helps you:
https://forum.xda-developers.com/huawei-p20-lite/help/req-stock-recovery-p20-lite-t3803027
Don't need lock bootloader to install or receive via OTA official updates.
Lock the bootloader is not possible (maybe it is, but is a pay service).
You can relock instead of lock, but don't do it if your device is not completely stock.
Click to expand...
Click to collapse
Hi all,
Getting a "lock" state is possible indeed. I believe you @kilroystyx had seen it as well on @Merlin_99 's thread:
https://forum.xda-developers.com/huawei-p20-lite/how-to/root-how-to-install-update-t3841557
This will erase all data, except from sdcards of course
Cheers,
AS
Mannuok said:
ANE LX3 no funciona asi,
Click to expand...
Click to collapse
ars_chelsea said:
Hi all,
Getting a "lock" state is possible indeed. I believe you @kilroystyx had seen it as well on @Merlin_99 's thread:
https://forum.xda-developers.com/huawei-p20-lite/how-to/root-how-to-install-update-t3841557
This will erase all data, except from sdcards of course
Cheers,
AS
Click to expand...
Click to collapse
You are right, first post was on the August 20th, at that time I didn't knew that was possible lock bootloader, only after Merlin_99 create that thread on September 12th.
I'm familiar with ADB and fastboot and all the rooting stuff, but I have no idea how to create a TWRP build for this device. Someone had a similar problem with a similar model (U673C) here: https://forum.xda-developers.com/android/help/umx-u673c-root-t3719328 . If I can post my stock recovery (which is extracted through fastboot, right?), could someone make a TWRP build from it? Then I could just send over magisk or something to remove all the bloatware, right?
Sorry for being a pain. Thanks for your time.
EDIT: This phone has an unlockable bootloader and I'm already in fastboot, if that helps.
EDIT 2: Running "fastboot oem unlock" gives me
...
FAILED (remote: unknown command)
finished. total time: 0.002s
Am I boned?
Since there's no section for this phone, I decided to post it in here.
So my next question is that if it's possible somewhat to install TWRP on Archos Oxygen 63?
I tried several ways but none of them worked, And i'm not familiar yet with this phone's SoC which is Unisoc.
The fastboot method worked fine until i tried to unlock the OEM.
fastboot flashing unlock
...
FAILED (remote: Not implemet.)
finished. total time: 0.011s
Click to expand...
Click to collapse
I will try now to see if it works without a password set for security after posting this.
And hopefully there's someone out there who dealt with breaking into this phone or has one and got into same scenario.
The reason why i'm trying to modify it is that somehow it doesn't let me download certain extension files, which are most media files (mp4, mp3, etc.)
@c00lkidd
TWRP recovery doesn't depend on device's SoC.
If a TWRP recovery for your phone isn't already available then you have to compile it by your own.
How-to: https://forum.xda-developers.com/showthread.php?t=1943625
With regards to Fastboot: The Fastboot program implemented on your phone obviously isn't the default AOSP Fastboot, means OEM/Carrier has removed some functionality.
Hi everyone.
Yesterday I unlocked the bootloader of my P20 Lite through DC-Unlocked (paid 4 euro) and I rooted it by flashing a patched ramdisk. It was on android 8 because I had to roll back the version to allow DC-Unlocker to get the bootloader code. Anyways, I wanted to upgrade to android 9.0 again but I ran into a major issue. Like an idiot, I tried flashing the update through the TWRP, and so now the phone is hard bricked.
On boot, I get the ERROR MODE screen which gives
Code:
Func NO: 10(recovery image)
Error No: 2(load failed!)
I tried flashing every single .img possible from the UPDATE.APP, but that doesn't do the trick. One thing that I've noticed is that the RAMDISK partition seems to have vanished, because when I try to flash it through fastboot, it gives me
Code:
FAILED (remote: partition length get error)
So I don't actually know how to flash the boot partitions, which is probably the culprit of the issue. I can only flash KERNEL.img but not RAMDISK.IMG.
Oh, and also, as you may have guessed, I can't even boot in recovery anymore.
Now I'm trying to download a FULLOTA-MF which, they say, should unbrick the phone via forced DLOAD method.
Anyone had this experience? Thanks in advance.
andreasaracino said:
Hi everyone.
Yesterday I unlocked the bootloader of my P20 Lite through DC-Unlocked (paid 4 euro) and I rooted it by flashing a patched ramdisk. It was on android 8 because I had to roll back the version to allow DC-Unlocker to get the bootloader code. Anyways, I wanted to upgrade to android 9.0 again but I ran into a major issue. Like an idiot, I tried flashing the update through the TWRP, and so now the phone is hard bricked.
On boot, I get the ERROR MODE screen which gives
Code:
Func NO: 10(recovery image)
Error No: 2(load failed!)
I tried flashing every single .img possible from the UPDATE.APP, but that doesn't do the trick. One thing that I've noticed is that the RAMDISK partition seems to have vanished, because when I try to flash it through fastboot, it gives me
Code:
FAILED (remote: partition length get error)
So I don't actually know how to flash the boot partitions, which is probably the culprit of the issue. I can only flash KERNEL.img but not RAMDISK.IMG.
Oh, and also, as you may have guessed, I can't even boot in recovery anymore.
Now I'm trying to download a FULLOTA-MF which, they say, should unbrick the phone via forced DLOAD method.
Anyone had this experience? Thanks in advance.
Click to expand...
Click to collapse
Hello,
- In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
-Alf- said:
Hello,
- In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Click to expand...
Click to collapse
Hi, thanks for your fast answer!
fastboot oem get-build-number
Code:
(bootloader) :System 8.0.0.046(09B8)
OKAY [ 0.012s]
finished. total time: 0.012s
fastboot oem get-product-model
Code:
(bootloader) ANE-LX1
OKAY [ 0.011s]
finished. total time: 0.011s
fastboot getvar vendorcountry
Code:
vendorcountry: ti/it
finished. total time: 0.012s
fastboot oem oeminforead-CUSTOM_VERSION
Code:
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.019s
fastboot oem oeminforead-SYSTEM_VERSION
Code:
(bootloader) :ANE-LX1 8.0.0.151(C55)
OKAY [ 0.013s]
finished. total time: 0.014s
I don't know why but the CUSTOM_VERSION reading failed...
according to the results from the fastboot you have a branded phone, maybe a single sim?
Good news is that you are still on A8, bad news is "ti/it ".
Try this :
- Download and flash stock recovery_ramdisk for Oreo
recovery_ramdisk
Use command
fastboot flash recovery_ramdisk (file_name).img
Then try boot into recovery and let me know, thanks.
What is (was) your region in your phone build number ? (for example C432, C10, C185...)
-Alf- said:
What is (was) your region in your phone build number ? (for example C432, C10, C185...)
Click to expand...
Click to collapse
I think it's C55 , correct me if I'm wrong...
-Alf- said:
according to the results from the fastboot you have a branded phone, maybe a single sim?
Good news is that you are still on A8, bad news is "ti/it ".
Try this :
- Download and flash stock recovery_ramdisk for Oreo
recovery_ramdisk
Use command
fastboot flash recovery_ramdisk (file_name).img
Then try boot into recovery and let me know, thanks.
Click to expand...
Click to collapse
I tried, but doesn't work at all...
-Alf- said:
I think it's C55 , correct me if I'm wrong...
Click to expand...
Click to collapse
Yeah, it is C55. I don't know what to do anymore
andreasaracino said:
I tried, but doesn't work at all...
Yeah, it is C55. I don't know what to do anymore
Click to expand...
Click to collapse
recovery_ramdisk installing using command fastboot flash recovery_ramdisk etc.
was unsuccessful?
Have you tried boot into eRecovery? There's an option in eRecovery "Download latest ....."
andreasaracino said:
Hi everyone.
Yesterday I unlocked the bootloader of my P20 Lite through DC-Unlocked (paid 4 euro) and I rooted it by flashing a patched ramdisk. It was on android 8 because I had to roll back the version to allow DC-Unlocker to get the bootloader code. Anyways, I wanted to upgrade to android 9.0 again but I ran into a major issue. Like an idiot, I tried flashing the update through the TWRP, and so now the phone is hard bricked.
On boot, I get the ERROR MODE screen which gives
Code:
Func NO: 10(recovery image)
Error No: 2(load failed!)
I tried flashing every single .img possible from the UPDATE.APP, but that doesn't do the trick. One thing that I've noticed is that the RAMDISK partition seems to have vanished, because when I try to flash it through fastboot, it gives me
Code:
FAILED (remote: partition length get error)
So I don't actually know how to flash the boot partitions, which is probably the culprit of the issue. I can only flash KERNEL.img but not RAMDISK.IMG.
Oh, and also, as you may have guessed, I can't even boot in recovery anymore.
Now I'm trying to download a FULLOTA-MF which, they say, should unbrick the phone via forced DLOAD method.
Anyone had this experience? Thanks in advance.
Click to expand...
Click to collapse
I did this once to my kiwi (5x) then it went totally blank when i tried flashing an Huawei related system flashing tool. Do not try that.
-Alf- said:
recovery_ramdisk installing using command fastboot flash recovery_ramdisk etc.
was unsuccessful?
Have you tried boot into eRecovery? There's an option in eRecovery "Download latest ....."
Click to expand...
Click to collapse
I can't manage to boot in eRecovery, I always get the Func No error...
But the flashing was successful, only it doesn't fix the issue with the recovery.
andreasaracino said:
I can't manage to boot in eRecovery, I always get the Func No error...
But the flashing was successful, only it doesn't fix the issue with the recovery.
Click to expand...
Click to collapse
Okay, try this way out...
- download Service ROM
- unpack, extract from UPDATE.APP files:
CUST.img, RAMDISK.img, SYSTEM.img , RECOVERY_RAMDISK.img using Huawei update extractor, and flash .img files through fastboot. (CUST.img can be found in second UPDATE.APP (update_sd_ANE-L01_hw......zip) folder.
-Alf- said:
Okay, try this way out...
- download Service ROM
- unpack, extract from UPDATE.APP files:
CUST.img, RAMDISK.img, SYSTEM.img , RECOVERY_RAMDISK.img using Huawei update extractor, and flash .img files through fastboot. (CUST.img can be found in second UPDATE.APP (update_sd_ANE-L01_hw......zip) folder.
Click to expand...
Click to collapse
Thank you very much Alf for your time, but I finally managed to unbrick the phone by dloading the FULLOTA-MF of which I wrote about in OP.
andreasaracino said:
Now I'm trying to download a FULLOTA-MF which, they say, should unbrick the phone via forced DLOAD method.
Click to expand...
Click to collapse
andreasaracino said:
Thank you very much Alf for your time, but I finally managed to unbrick the phone by dloading the FULLOTA-MF of which I wrote about in OP.
Click to expand...
Click to collapse
then it is not FULLOTA-MF but Service ROM, bro ...okay, it doesn't matter now.