Related
Hi !
I have a Oneplus X which was using CM13 in the official nightly build. Without any reasons it began to crash all the applications, so I rebooted it.
Then it was keeping rebooting and recompile all the apps.
I tried to sideload the last CM13 update, then the oxygenOS stock rom. I also tried to wipe the partition before to sideload again. Nothing works.
I thought then the cm recovery doesn't have enough features and retry the bootloader flashing with twrp.
Well, basically I don't have the adb permissions and I can't unlock the bootloader in order to flash the recovery as you can see in the code blocks below
Code:
c:\adb>fastboot devices
f54b3af3 fastboot
c:\adb>fastboot oem unlock
...
OKAY [ 0.015s]
finished. total time: 0.016s
c:\adb>adb devices
List of devices attached
f54b3af3 unauthorized
c:\adb>adb reboot bootloader
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
c:\adb>echo "Restarting the device into fastboot manually then..."
"Restarting the device into fastboot manually then..."
c:\adb>fastboot devices
f54b3af3 fastboot
c:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.007s]
finished. total time: 0.007s
c:\adb>
Flash stock firmware,
Stock firmware doesn't require unlocked bootloader
Sent from my Moto G 2014 using XDA-Developers mobile app
---------- Post added at 01:56 PM ---------- Previous post was at 01:53 PM ----------
But why you want adb permission, just fastboot required for unlocking, flashing.
Sent from my Moto G 2014 using XDA-Developers mobile app
Well I tried to install the recovery and the oxygenOS from the official website. It didn't really works, it's the same problem but I don't really know if you consider them as the stock firmware.
So I tried something else to go further. I tried the tuto "[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus X" (I don't have the right to post some links).
The result is not like expected. The phone is keeping booting. The bootloader and the recovery is unreachable.
If I click on "Verify" of the MsmDownloadTool V2.0, I have :
Code:
8974_msimage.mbn: OK
dynamic_nvbk.bin: OK
emmc_appsboot.mbn: OK
gpt_backup0.bin: OK
gpt_main0.bin: OK
rawprogram0.xml: FAILED
NON-HLOS.bin: OK
MPRG8974.mbn: OK
rpm.mbn: OK
sbl1.mbn: OK
sdi.mbn: OK
static_nvbk.bin: OK
tz.mbn: OK
persist.img: OK
recovery.img: OK
Any ideas to try ? :/
-- EDIT --
I just find out that I can boot on fastboot mod but the oem is disabled. But there is no way to unlock it by the graphical interface because the phone is in a boot loop.
I found a compromise
Hi guys.
I had to face that my bootloader can't be unlock like some other people. A simple "fastboot oem unlock" doesn't change the unlock bit but it changes the tampered one.
Anyway, I wanted my phone to be operational. With a friend we tried to flash it with MsmDownloaderV2, the qualcomm tool and a lot of different packages. The result was the same : impossible to boot, no recovery avalaible.
Well to go throught this problem, we tried to change the recovery.img of the flashing package with the image given by twrp. It worked, we finally had a recovery working !
Then I tried to reinstall CM13. Without errors messages the installation failed. With a wipe before the installation, at the end, twrp said "No os installed".
I tried to install the last version of OxygenOS. It said that the device was uncompatible even if I downloaded the right version. So I edited the updater-script and updated its hash in the manifest. It doesn't work either because it didn't find the update binary at the correct path even if it was here.
Anyway, I was tired of this sh*t. I tried to install the first version of OxygenOS. It worked.
So now, my phone works with an outdated version. The tamper bit is true while the unlock bit is false, and I have a the last version of twrp for my recovery.
I pass this post in a solved status, but if you have an idea to pass my unlock bit to true or to put an updated version, I will appreciate it
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.
And yeah, despite the fact that I'm flashing phones since a long time,
I've tried to flash my Pxl6 to the November factory image with adb and fastboot coming from a 2 years old tools pack (adb, fastboot)
- unlock bootloader
- flash recovery image was done
- fastboot reboot ok
- flash radio was done
- fastboot reboot failed
- fastboot reboot restarted
- flash system image fails every time I try trough command line or online with Android Flash Tool (whetever wiping option I choose with the online tool)
when the process reboots to Fasbootd
Code:
Writing 'vendor_boot_a' OKAY [ 0.079s]
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
or
Code:
Writing 'vendor_boot_a' OKAY [ 0.112s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Sending 'super' (4 KB) FAILED (Status read failed (Too many links))
fastboot: error: Command failed
the update process fails despite that fasbootd initiates and appears.
When trying to boot fastboot manually with the device, it's difficult to make it appear but possible.
Bootlooping on starting the OS otherwise.
I've updated to the latest commandline tools from Google but the issue remains.
The driver works ok, the usb cable allows flashing the recovery and the radio, so should not be the issue.
SDK is not installed on the PC.
I'm blocked, can someone help me to even reinstall the december or whatever version ?
I fear it's bricked this time
cAnArdtichAud said:
And yeah, despite the fact that I'm flashing phones since a long time,
I've tried to flash my Pxl6 to the November factory image with adb and fastboot coming from a 2 years old tools pack (adb, fastboot)
- unlock bootloader
- flash recovery image was done
- fastboot reboot ok
- flash radio was done
- fastboot reboot failed
- fastboot reboot restarted
- flash system image fails every time I try trough command line or online with Android Flash Tool (whetever wiping option I choose with the online tool)
when the process reboots to Fasbootd
Code:
Writing 'vendor_boot_a' OKAY [ 0.079s]
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
or
Code:
Writing 'vendor_boot_a' OKAY [ 0.112s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Sending 'super' (4 KB) FAILED (Status read failed (Too many links))
fastboot: error: Command failed
the update process fails despite that fasbootd initiates and appears.
When trying to boot fastboot manually with the device, it's difficult to make it appear but possible.
Bootlooping on starting the OS otherwise.
I've updated to the latest commandline tools from Google but the issue remains.
The driver works ok, the usb cable allows flashing the recovery and the radio, so should not be the issue.
SDK is not installed on the PC.
I'm blocked, can someone help me to even reinstall the december or whatever version ?
I fear it's bricked this time
Click to expand...
Click to collapse
You definitely have to wipe to go back. Did you remove the -w from the install bat file?
You should update your platform tools and you'll need to format data to go back to the November factory image.
Tulsadiver said:
You definitely have to wipe to go back. Did you remove the -w from the install bat file?
Click to expand...
Click to collapse
Uh no, it was the 1st time I was trying to use directly the flash-all script, so no I used the fastboot -w parameter.
Later I tried the flash online tool from Google and I ticked wipe.
Yeah sorry that's not the exact code I used, so yes..w was used.
What are my options? Fastbootd seem broken because flashing fails when rebooting to fastbootd.
Edmontonchef said:
You should update your platform tools and you'll need to format data to go back to the November factory image.
Click to expand...
Click to collapse
Yeah thanks I updated them after I had the issue and retried without working.
cAnArdtichAud said:
Uh no, it was the 1st time I was trying to use directly the flash-all script, so no I used the fastboot -w parameter.
Later I tried the flash online tool from Google and I ticked wipe.
Yeah sorry that's not the exact code I used, so yes..w was used.
What are my options? Fastbootd seem broken because flashing fails when rebooting to fastbootd.
Click to expand...
Click to collapse
Perhaps you didn't get a good download of your firmware. Try downloading it again.
Edit: usual things, try a different usb port on your pc, try a different pc, use a different cable. Check version. fastboot -- version
Tulsadiver said:
Perhaps you didn't get a good download of your firmware. Try downloading it again.
Edit: usual things, try a different usb port on your pc, try a different pc, use a different cable. Check version. fastboot -- version
Click to expand...
Click to collapse
This. Make sure you're using the latest Platform Tools - current version is 31.0.3, Aug '21.
I am going to take a wild guess that the reason for the rollback. Is because of the data issues.
If so,
Just flash the November radio image on top of the December update.
"Fastboot flash radio radio.img"
The above is what I did. And it has worked well for me.
vandyman said:
I am going to take a wild guess that the reason for the rollback. Is because of the data issues.
If so,
Just flash the November radio image on top of the December update.
"Fastboot flash radio radio.img"
The above is what I did. And it has worked well for me.
Click to expand...
Click to collapse
Yeah but I've already flashed back recovery and radio the OS part is failing
V0latyle said:
This. Make sure you're using the latest Platform Tools - current version is 31.0.3, Aug '21.
Click to expand...
Click to collapse
thx. I tried several images but will retry on another port, another cable same PC (only one...)
I have 31.03 command tools
funkin' love you guys: ensuring I was on a powered usb port, changing cable made me flash the data/os files
funkin' pixel 6 reverted back to the entire previous rom
funkin Xmas to you guys , #heartWithFingers!
vandyman said:
I am going to take a wild guess that the reason for the rollback. Is because of the data issues.
If so,
Just flash the November radio image on top of the December update.
"Fastboot flash radio radio.img"
The above is what I did. And it has worked well for me.
Click to expand...
Click to collapse
I have the Dec update on my P6 unlocked on Verizon but would like to revert back to the Nov one without doing a complete wipe of my phone. Is this what you did?
sniff1 said:
I have the Dec update on my P6 unlocked on Verizon but would like to revert back to the Nov one without doing a complete wipe of my phone. Is this what you did?
Click to expand...
Click to collapse
You can't go back without a full wipe.
Tulsadiver said:
You can't go back without a full wipe.
Click to expand...
Click to collapse
Because when you unlock the bootloader prior to flashing, the phone is wiped.
cAnArdtichAud said:
Because when you unlock the bootloader prior to flashing, the phone is wiped.
Click to expand...
Click to collapse
Even if your bootloader is already unlocked.
sniff1 said:
I have the Dec update on my P6 unlocked on Verizon but would like to revert back to the Nov one without doing a complete wipe of my phone. Is this what you did?
Click to expand...
Click to collapse
No. I have the Dec. 15th update and the mid November radio.
If you would like to install the older radios. You will need to download the older factory image and extract the radio image.
Than flash the older radio image with fastboot on your PC.
You need to have the USB devloper checked to use adb/fastboot on your PC.
vandyman said:
No. I have the Dec. 15th update and the mid November radio.
If you would like to install the older radios. You will need to download the older factory image and extract the radio image.
Than flash the older radio image with fastboot on your PC.
You need to have the USB devloper checked to use adb/fastboot on your PC.
Click to expand...
Click to collapse
That is just the radio.....not the system.
vandyman said:
No. I have the Dec. 15th update and the mid November radio.
If you would like to install the older radios. You will need to download the older factory image and extract the radio image.
Than flash the older radio image with fastboot on your PC.
You need to have the USB devloper checked to use adb/fastboot on your PC.
Click to expand...
Click to collapse
This is exactly what I want to do. I know how to extract the radio image, but not too certain on the fastboot commands to do it
Tulsadiver said:
That is just the radio.....not the system.
Click to expand...
Click to collapse
Yes ,just the radio image from November on top of the complete December image.
What I did;
Flash-all (December factory image with the -w removed for no data wipe)
Next, I extracted the November radio image from the November factory image.
Than , fastboot flash radio radio.img.
I know it sounds confusing. Lol..
sniff1 said:
This is exactly what I want to do. I know how to extract the radio image, but not too certain on the fastboot commands to do it
Click to expand...
Click to collapse
Fastboot flash radio yourradio.img
Yes the radio command needs to be there after the flash command and before your radio.img.
Very similar to to flashing a boot image,
Example, fastboot flash boot boot.img
Help! Installed CallX, which has very good reviews, but instantly I could no longer hear anyone who called nor who I call. If I turn on the speaker we can converse but not clearly in a noisy environment.
I immediately deinstalled CallX... but, the problem remained.
In desperation I completely installed new firmware on the phone (Havoc 4.12, previously Havoc 4.8) and lost all my config which takes me a day to rebuild, and guess what? NO CHANGE. I can't hear anyone as a normal phone.
The developer of CallX is unresponsive. Isn't that dynamite? I think he must have been packing the reviews.
Does anyone know where the problem could be? I can't believe installing new firmware did not fix it.
Quantumstate said:
Help! Installed CallX, which has very good reviews, but instantly I could no longer hear anyone who called nor who I call. If I turn on the speaker we can converse but not clearly in a noisy environment.
I immediately deinstalled CallX... but, the problem remained.
In desperation I completely installed new firmware on the phone (Havoc 4.12, previously Havoc 4.8) and lost all my config which takes me a day to rebuild, and guess what? NO CHANGE. I can't hear anyone as a normal phone.
The developer of CallX is unresponsive. Isn't that dynamite? I think he must have been packing the reviews.
Does anyone know where the problem could be? I can't believe installing new firmware did not fix it.
Click to expand...
Click to collapse
Sounds like you need to flash stock Motorola firmware.
I never thought an app could do such damage to a phone even after reinstalling firmware.
I've now also lost all of my Signal SMS history (Havoc 4.12) because in Permissions the only ones available for Signal are Media Only or None. It needs Files permission to restore the backups, but it is just not an option.
It's worse now. I installed Stock using my instructions over here, but I installed Android 11, not having seen Beetle's post below. In TWRP I got all kinds of permission denied errors on /data/. So I then downloaded Android 10 from here, and
# fastboot flash partition gpt.bin
...which went fine. But then
# fastboot flash bootloader bootloader.img
Sending 'bootloader' (14204 KB) OKAY [ 0.414s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
No idea what is wrong. The partitions should have been written. My phone's down hard now. Booting into fastboot I do not get the normal way it looks, but a mostly blank screen with Start in the center, and text at bottom acknowleging it's connected. And it does answer up to # fastboot devices. I've downloaded the stock image twice and same issue.
I can't find an older Android 10, in the hope that it will fix this. I believe that Android 10 is required for all versions of Havoc, but I can't even get to Stock at this point. Feel like drinking but won't,
# fastboot flash bootloader bootloader.img
Sending 'bootloader' (14204 KB) OKAY [ 0.385s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
In TWRP I get "failed to mount /metadata" "invalid argument". There is no way to recover from this. I suspect this happened because I tried to roll back from stock Android 11 to 10. I've tried going back to 11 and every which way.
Looks like this phone is ruined. I've tried everything I can think of. out of ideas.
Yep, did a complete fastboot flash reinstall of Stock 11, and still the earpiece does not work. Phone is the default calling app.
This phone is unusable except in speakerphone. I've ordered another Moto G Power 2020 as it's so good otherwise, even without call recording. But AVOID CallX!
Beetle84 once said to not install Stock 11 then Havoc, that it must be Stock 10, but it is unclear whether that applies to the current Havoc 4.12 which is based on Android 11?
What I know for sure is that when you install Stock Android 11, you can NOT go back to Android 10 as G**gle has thoughtfully put in anti-rollback measures. And Android 12 makes things much more difficult for us modders.
Quantumstate said:
What I know for sure is that when you install Stock Android 11, you can NOT go back to Android 10 as G**gle has thoughtfully put in anti-rollback measures. And Android 12 makes things much more difficult for us modders.
Click to expand...
Click to collapse
That's not good. May I suggest supporting the efforts of the Pine64 folks?
Quantumstate said:
In TWRP I get "failed to mount /metadata" "invalid argument". There is no way to recover from this.
Click to expand...
Click to collapse
Did you try wiping metadata entirely?
I had the same problem with the bootloader refusing to allow downgrading the bootloader after installing Motorola's Android 11 firmware. Even so LineageOS is running fine on the device's Slot A right now. Read my post over here.
I did something like: (Exact steps weren't noted. Sorry, no desire to retest on a now working device used by a family member.)
Booted into the bootloader and flashed Motorola's Android 11 stock firmware from XT2041-4_SOFIA_RETUS_11_RPMS31.Q1-54-13-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip on Slot A, minus vbmeta and super
fastboot set_active a
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot oem fb_mode_clear
Rebooted into fastbootd (fastboot reboot fastboot) and flashed LineageOS fastbootd images from lineage-18.1-20211219-UNOFFICIAL-FASTBOOTD-sofiar.zip
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash product product.img
Returned to the bootloader (fastboot reboot bootloader) and wiped data
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
Rebooted (fastboot reboot) into LineageOS, it booted successfully and runs fine. Rooting wasn't tested. Before trying LineageOS fastbootd images I installed crDroid through TWRP and booted it with success. It had some weird bugs unfortunately, most importantly being unable to serve as a working phone. My family member was very happy with an older version of crDroid from around June on the Android 10 firmware.
I fixed the /medadata error by (in TWRP)
- Unmount /metadata
- Disable MBR
- Format /metadata.
Problem is metadata was encrypted and 11 couldn't tell from 10.
Now all the /loop's on inactive slot b are inaccessible. I could keep jacking with it but ran out of time. And running Stock in slot a I find I still have the earphone problem so gave up and ordered another phone. It should never be possible for an app to do this kind of damage.
Yes I've noticed the Pine64 project, although one thing I require is a water-resistant phone. There will come a point, in view of the awful changes in Android 12, where I may move to a Pine phone. As it is, for years I've run no gapps, do not use the Play store, nor anything else G**gle except the OS. And I choke the OS off with AFWall+ in F-Droid.
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.