Database Develop

[DEV] Official Kernel Sources & Ramdisk for Xperia 2011 devices [posted at GITHUB]

[DEV] Official Kernel Sources & Ramdisk for Xperia 2011 devices [posted at GITHUB]
------\\ IMP INFO //-------
LAST UPDATED:
26/March/2012
Latest Kernel Sources:
4.0.2.A.0.74
Latest Ramdisk:
4.0.2.A.0.42
------// IMP INFO \\-------
hello guys,
i have pushed the Official kernel sources and ramdisks for various Xperia 2011 devices to my github account... to keep the various FW versions at same place i have created branches for each kernel/ramdisk... i think this will help other dev/advance users as they can now easily get all relevant files at one place and easily compare changes in firmware sources...
Xperia-2011-Official-Kernel-Sources
(INCLUDES THESE FW VERSIONS)
Xperia-2011-Official-Ramdisks
(INCLUDES THESE FW VERSIONS)
i will try my best to keep those sources updated
regards,
DooMLoRD

Kernel sources for following firmware:
4.0.2.A.0.74
4.0.2.D.0.5
4.1.C.0.7
4.1.C.0.6
4.0.2.A.0.61_62
3.0.1.E.0.88
4.0.2.A.0.58
4.0.2.A.0.42
4.0.2.A.0.9
4.0.1.A.0.284
4.0.1.A.0.283
4.0.A.2.377
4.0.A.2.368
3.0.1.A.0.145_146_148

Ramdisks for following firmware:
4.0.2.A.0.42
4.0.1.A.0.283
4.0.A.2.368
3.0.1.A.0.145
Devices for which ramdisks are posted:
Code:
ST17 - coconut - ACTIVE
LT15 - anzu - ARC
LT18 - ayame - ARC S
WT19 - satsuma - LIVE WALKMAN
ST15 - smultron - MINI
SK17 - mango - MINI PRO
MT15 - hallon - NEO
MT11 - haida - NEO V
R800 - zeus,zeusc - PLAY
MK16 - iyokan - PRO
ST18 - urushi - RAY

Nice work,Doom

Great work. Just to ask... Could you publish the one for Xperia Pro? Thanks.

alvaroag said:
Great work. Just to ask... Could you publish the one for Xperia Pro? Thanks.
Click to expand...
Click to collapse
You want ramdisk for it?
Sent from my LT15i using XDA App

Yes, please, it would be nice and I can't find a way to get it from my phone

alvaroag said:
Yes, please, it would be nice and I can't find a way to get it from my phone
Click to expand...
Click to collapse
i was not able to get new firmware (kernel.sin file)...
since u have the device have u rooted it yet?
use this: http://forum.xda-developers.com/showthread.php?t=1302037
and find the newest superuser update.zip
then after the device is rooted reboot it once... connect device to pc via adb and pull the following files:
Code:
/*
/sbin/*
e.g.: file list from ARC: https://github.com/DooMLoRD/Xperia-2011-Official-Ramdisks/tree/master/ARC

updated kernel sources with 4.0.2.A.0.9 FW sources

Finally, I managed to get the sin files from PC Companion. You can download the kernel SIN from:
http://soporte.opensysperu.com/downloads/kernel_S1-SW-LIVE-883F-PID1-0001-S1-PARTITION.sin
My build number is 4.0.1.A.0.283.
Also, as you have experience developing custom kernels, I would like to ask somethingto you(sorry if it's our of thread)... I've compiled a kernel based on the SE source code(just added the tun/tap driver as built in) following the instructions published by SE, then used the original ramdisk/taken from the kernel image, then used mkbootimg to create the bootable image, and finally booted into it with "fastboot boot boot.img". It showed the SE logo(just the words, not the bootanim) and then the phone turned off. The same happens when I used "fastboot boot" with the stock kernel image. I use "fastboot boot" instead of "fastboot flash kernel" so I can test the kernel without risk bricking my device... Is there somerthing I'm doing wrong? Thanks.

alvaroag said:
Finally, I managed to get the sin files from PC Companion. You can download the kernel SIN from:
http://soporte.opensysperu.com/downloads/kernel_S1-SW-LIVE-883F-PID1-0001-S1-PARTITION.sin
My build number is 4.0.1.A.0.283.
Also, as you have experience developing custom kernels, I would like to ask somethingto you(sorry if it's our of thread)... I've compiled a kernel based on the SE source code(just added the tun/tap driver as built in) following the instructions published by SE, then used the original ramdisk/taken from the kernel image, then used mkbootimg to create the bootable image, and finally booted into it with "fastboot boot boot.img". It showed the SE logo(just the words, not the bootanim) and then the phone turned off. The same happens when I used "fastboot boot" with the stock kernel image. I use "fastboot boot" instead of "fastboot flash kernel" so I can test the kernel without risk bricking my device... Is there somerthing I'm doing wrong? Thanks.
Click to expand...
Click to collapse
the link that u posted is for Xperia Pro right? i will update my gitrepo with the ramdisk from this device...
which defconfig did u use?
are u unpacking/repacking ramdisk or just using the stock ramdisk.cpio.gz and then mkbootimg?

Yes, the image is for Xperia Pro(MK16a).
The exact command I'm using to configure the kernel is:
ARCH=arm CROSS_COMPILE=/opt/android-ndk-r5b/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/arm-eabi- make semc_iyokan_defconfig​
I've tried using the original ramdisk as well as unpack & repack(changing the logo.rle). The command I used to create the boot image is:
./mkbootimg --base 0x00200000 --kernel /usr/src/android/4.0.A.2.364/kernel/arch/arm/boot/zImage --ramdisk ramdisk.img -o boot.img​
Any idea? Thanks.

alvaroag said:
Yes, the image is for Xperia Pro(MK16a).
The exact command I'm using to configure the kernel is:
ARCH=arm CROSS_COMPILE=/opt/android-ndk-r5b/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/arm-eabi- make semc_iyokan_defconfig​
I've tried using the original ramdisk as well as unpack & repack(changing the logo.rle). The command I used to create the boot image is:
./mkbootimg --base 0x00200000 --kernel /usr/src/android/4.0.A.2.364/kernel/arch/arm/boot/zImage --ramdisk ramdisk.img -o boot.img​
Any idea? Thanks.
Click to expand...
Click to collapse
Use stock ramdisk as is
Sent from my LT15i using XDA App

pushed 4.0.1.A.0.283 ramdisks for NEO V & PRO

DooMLoRD said:
Use stock ramdisk as is
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
I ran the following commands:
cd /usr/src/android/4.0.A.2.364/kernel
ARCH=arm CROSS_COMPILE=/opt/android-ndk-r5b/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/arm-eabi- make semc_iyokan_defconfig
nano -w .config
# Add CONFIG_TUN=y
ARCH=arm CROSS_COMPILE=/opt/android-ndk-r5b/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/arm-eabi- make
cd ../bootimg
cp /usr/src/android/4.0.A.2.364/kernel/arch/arm/boot/zImage .
./unpack-bootimg.pl kernel_S1-SW-LIVE-883F-PID1-0001-S1-PARTITION.sin
cp kernel_S1-SW-LIVE-883F-PID1-0001-S1-PARTITION.sin-ramdisk.cpio.gz ramdisk.cpio.gz
./mkbootimg --base 0x00200000 --kernel zImage --ramdisk ramdisk.cpio.gz -o boot.img
./fastboot boot boot.img​
But it didn't worked. the workds "Sony Ericsson" appear, then the screen gets filled with black and finally the phone turns off.
I tried also with the kernel image, but still the same problem.

alvaroag said:
I ran the following commands:
cd /usr/src/android/4.0.A.2.364/kernel
ARCH=arm CROSS_COMPILE=/opt/android-ndk-r5b/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/arm-eabi- make semc_iyokan_defconfig
nano -w .config
# Add CONFIG_TUN=y
ARCH=arm CROSS_COMPILE=/opt/android-ndk-r5b/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/arm-eabi- make
cd ../bootimg
cp /usr/src/android/4.0.A.2.364/kernel/arch/arm/boot/zImage .
./unpack-bootimg.pl kernel_S1-SW-LIVE-883F-PID1-0001-S1-PARTITION.sin
cp kernel_S1-SW-LIVE-883F-PID1-0001-S1-PARTITION.sin-ramdisk.cpio.gz ramdisk.cpio.gz
./mkbootimg --base 0x00200000 --kernel zImage --ramdisk ramdisk.cpio.gz -o boot.img
./fastboot boot boot.img​
But it didn't worked. the workds "Sony Ericsson" appear, then the screen gets filled with black and finally the phone turns off.
I tried also with the kernel image, but still the same problem.
Click to expand...
Click to collapse
unpack-bootimg.pl wont work directly on kernel.sin files
use this:
http://forum.xda-developers.com/showthread.php?t=1262656

I used your script to split the kernel.sin, get the ramdisk, deleted my old boot.img, and then ran mkbootimg again, but nothing, still the same simptom. Any idea?

alvaroag said:
I used your script to split the kernel.sin, get the ramdisk, deleted my old boot.img, and then ran mkbootimg again, but nothing, still the same simptom. Any idea?
Click to expand...
Click to collapse
sorry mate no idea... wht u described should work...

pushed FW 4.0.2.A.0.42 ramdisks for all devices

updated kernel sources with 4.0.2.A.0.42 FW sources

[TOOL] New universal method of rooted for the Optimus 2x | Linux/Mac | (beta)

New universal method of rooted for the Optimus 2x
After much programming and experimenting with another great part, already I can deliver my latest work.
So far have only made for Linux and Mac. (there are methods to not be as done in CMD)
Apparently it seems very simple, but it cheats, it is quite complex, since I've programmed detection of errors and possible solutions to the problems of communication.
The program is smart, detects the operating system that we are using, Linux or iOS, and detects the version of ROM installed to determine installation done.
Also installs the CWM Recovery, and also knows which install depending on the GB ROM or ICS, all automatic, without having to think that option used.
Before you root it will ask you if the CWM Recovery is installed and if it is not you can do it at that time.
The method used is not new, I already used it in earlier versions of GB, the difference with the other methods is that you don't have to copy anything to the SD and things of these, simple and clean installation.
Well I hope that you have Linux or a Mac can root without having to boot the "tedious" Windows.
CHANGELOG
V-0.5
-Implemented detecting permissions
-Implemented detection system 32/64b
-Fixed bug, was not working in Ubuntu 11.04 and higher
V-0.4
-Detection of new possible connection failures.
-Detection of errors in routines Android
-Optimized routines
V-0.3
-Fixed bug of execution, did not work on some current versions of Ubuntu and derivatives
-New start menu.
-New header
V-0.2
-Re-raise with correction error in English language, it only pulled in Spanish
-Includes English language
-Changing the graphic appearance
V-0.1
-Only in Spanish
Click to expand...
Click to collapse
DOWNLOAD
Toolkit_ICS-Root_Stock-v-0.5_LINUX-MAC_by_Homero.rar - 13.40 MB

Thank's Man...and have a nice year 2013!!!...

Nice, it should became sticked.
Also... your program must be also noob-proof

Great work, homero! Thank you.
Sent from my LG-P990 using xda app-developers app

Homero again back with a bang...you're hulk of lg optimus forum..you rock bro

Finally some Linux love.... :thumbup:
Sent from my LG-P990 using xda app-developers app

Thanks homero
Enviado desde mi O2X

I have committed an error, and the English version, and does not run.
You can download the new corrected version or edit and modify.
Edit the root file and look for this line:
Code:
if [ "$ANSWER" = 1 ]; then
tools/es.sh
elif [ "$ANSWER" = 2 ]; then
tools/es.sh
elif [ "$ANSWER" = "x" ] || [ "$ANSWER" = "X" ]; then
Changing this:
Code:
elif [ "$ANSWER" = 2 ]; then
tools/es.sh
why another:
Code:
elif [ "$ANSWER" = 2 ]; then
tools/en.sh
Save and ready, already operates the English version

Homero2 said:
I have committed an error, and the English version, and does not run.
You can download the new corrected version or edit and modify.
Edit the root file and look for this line:
Code:
if [ "$ANSWER" = 1 ]; then
tools/es.sh
elif [ "$ANSWER" = 2 ]; then
tools/es.sh
elif [ "$ANSWER" = "x" ] || [ "$ANSWER" = "X" ]; then
Changing this:
Code:
elif [ "$ANSWER" = 2 ]; then
tools/es.sh
why another:
Code:
elif [ "$ANSWER" = 2 ]; then
tools/en.sh
Save and ready, already operates the English version
Click to expand...
Click to collapse
Beware of #!/bin/sh ... read -n command is bash command, and it does not work well in /bin/sh ...
Confirmed on NetRunner (kubuntu 12.10 ).
You should use #!/bin/bash. That applies to all *.sh scripts.

asmerito said:
Beware of #!/bin/sh ... read -n command is bash command, and it does not work well in /bin/sh ...
Confirmed on NetRunner (kubuntu 12.10 ).
You should use #!/bin/bash. That applies to all *.sh scripts.
Click to expand...
Click to collapse
OK, that is the answer that was waiting, since neither worked in Ubuntu 12.04
EDIT:
Re-raise corrected v-0.3

Though your tool says that flashing the recovery worked successful, I can't boot into recovery. When pushing vol- and power I'm just stuck at the pink LG logo (it's in a boot loop while holding vol- and power). Since the system is not rooted, yet, I also cannot boot into recovery with the CWM app.

thorstenhirsch said:
Though your tool says that flashing the recovery worked successful, I can't boot into recovery. When pushing vol- and power I'm just stuck at the pink LG logo (it's in a boot loop while holding vol- and power). Since the system is not rooted, yet, I also cannot boot into recovery with the CWM app.
Click to expand...
Click to collapse
Don't worry in excess, can be retrieved very easily, but before answer to these questions.
Android version?
did CWM previously installed?.
Terminal type? (P990, P990, etc.)

on slackware 14.0, expanded in /opt:
two patches applied;
files are executables with right permissions;
dir 'tools' is accessible;
lg2x is connected via USB (on, off, MTP, PC Suite, without battery and vol -, ...?)
but same result
Terminal: P990 (EU)
ROM: ICS stock
Previous ver: CM 7.2 stable
Previous CWM: 5.0.2

Homero2 said:
Android version?
did CWM previously installed?.
Terminal type? (P990, P990, etc.)
Click to expand...
Click to collapse
Android 4.0.4 (official V30A)
CWM - well, under GB layout I could install it (I was on CWM5 first and later switched to CWM6), but this was my first try on ICS layout
Terminal type - you mean the shell? I'm using Ubuntu 12.10, so /bin/sh did not work and I replaced all /bin/sh with /bin/bash, that means I was running bash when I "bricked" my phone.

kanzy said:
on slackware 14.0, expanded in /opt:
two patches applied;
files are executables with right permissions;
dir 'tools' is accessible;
lg2x is connected via USB (on, off, MTP, PC Suite, without battery and vol -, ...?)
but same result
Terminal: P990 (EU)
ROM: ICS stock
Previous ver: CM 7.2 stable
Previous CWM: 5.0.2
Click to expand...
Click to collapse
Is about understands that this method of single rooted is for Stock ROM versions.
Clarified the issue, I see errors jump to run ADB.
Try with the latest version that I uploaded, the V-0.4
thorstenhirsch said:
Android 4.0.4 (official V30A)
CWM - well, under GB layout I could install it (I was on CWM5 first and later switched to CWM6), but this was my first try on ICS layout
Terminal type - you mean the shell? I'm using Ubuntu 12.10, so /bin/sh did not work and I replaced all /bin/sh with /bin/bash, that means I was running bash when I "bricked" my phone.
Click to expand...
Click to collapse
Not be what could happen...
Doing tests I found that if you are in Recovery, and the SYSTEM partition is not mounted, the program cannot determine partition type should be used.
That error is already fixed in the V-0.4.
It can reflash the Recovery with one of the many versions that we have in the Forum, one in Flash only recovery or All in one.
I say this because it is the only thing that could have happened, since the rooted is not harmful, only copy two files in the system.

Using V-0.4, and it does not work...
Homero2 said:
Is about understands that this method of single rooted is for Stock ROM versions.
Clarified the issue, I see errors jump to run ADB.
Try with the latest version that I uploaded, the V-0.4
Not be what could happen...
Doing tests I found that if you are in Recovery, and the SYSTEM partition is not mounted, the program cannot determine partition type should be used.
That error is already fixed in the V-0.4.
It can reflash the Recovery with one of the many versions that we have in the Forum, one in Flash only recovery or All in one.
I say this because it is the only thing that could have happened, since the rooted is not harmful, only copy two files in the system.
Click to expand...
Click to collapse
Same problem as on slackware, got booloop after flashing recovery. Cannot enter recovery
After this step:
INSTRUCTIONS
CWM will be installed for version ICS V-4.0.4 of Android
Nvflash started
rcm version 0X20001_____________________________________________________________
System Information:
chip name: unknownh Recovery CWM
chip id: 0x20 major: 1 minor: 4
chip sku: 0xf
chip uid: 0x045070c04120b4d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: tools/fastboot.bin
/ 1027184/1027184 bytes sent
tools/fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: tools/recovery_cwm-6_ics_opti.img
\ 7145472/7145472 bytes sent
tools/recovery_cwm-6_ics_opti.img sent successfully
everything went wrong, and my stock ICS got bootloop.
Using Kubuntu 12.10, stock ICS and V-0.4 of your tool.

Thank you mate! Gonna share it like a bee

asmerito said:
Same problem as on slackware, got booloop after flashing recovery. Cannot enter recovery
...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=921169

Fixed bug, now works in Ubuntu 11.04, 11.10, 12.04 and 12.10
An error has been detected by Jonki, Thank you!!

Homero2 said:
Fixed bug, now works in Ubuntu 11.04, 11.10, 12.04 and 12.10
An error has been detected by Jonki, Thank you!!
Click to expand...
Click to collapse
What was the problem?

Error in flashing most of CM based ROMs in Moto X XT1052 EU version

I have Moto x XT1052 EU version and could not flash most of CM based ROMs. It fails with error message as "This package is for device:
xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc,xt1056,ghost_sprint,xt1058,ghost_att,ghost_rcica,xt1060,ghost_verizon; this device is " + getprop("ro.product.device") + ".")".
This error is very much annoying. I found some tweak to successfully flash this ROM by following few simple steps:
ROMs causing this issue are,
[ROM] [4.4.4] [OFFICIAL] Ehndroix V 14.10.14 - Ghost
[Rom] [4.4.4] Cyanogenmod 11 for Moto X
N5X Experience ROM
1. Using 7z app, open flashable ROM zip file
2. go to META-INF\com\google\android\
3. drag and drop updater-script on your desktop
4. Open this script file with Notepad++
5. Delete the lines starting from "assert (getprop............ upto abort("this package....." (see screenshot attached)
6. Save the script in Notepad++
7. drag and drop this amended script file back to META-INF\com\google\android\
8. Close zip file
9. Copy to your phone sdcard memory
10. Don't forget to copy relevant gapps file as well
All done. Use your recovery (I prefer latest TWRP) and flash ROM and GAPPS.
Enjoy!!

IDK if I'm doing it wrong but the above edit did not fix the flash error for my xt1052 device. OP could you maybe redo your example picture by selecting/highlighting whatever text/lines need to go... Just to make it absolutely error proof. thx

Or in 7zip, find the updater-script and right-click, then edit.

What recovery are you using? Some XT1052 user reported that the newer twrp recoveries were not functional and we should hence use, 2.6.3.1. I am using the earlier build ( 2.6.3.1 ) and did face any problems. Flashing is easy and quick. Backing up and restoring is a piece of cake. No need of all these steps.
Cheers

TWRP 2.6.3.1 download link below for everybodies reference: Unfortunatly I don't have enough posts to my name to post the link fully so please attach both of the below lines
goo.
im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img/
This also worked for me.

omnomnomkimiiee said:
Or in 7zip, find the updater-script and right-click, then edit.
Click to expand...
Click to collapse
Did that but no go..
flasherruts said:
What recovery are you using? Some XT1052 user reported that the newer twrp recoveries were not functional and we should hence use, 2.6.3.1. I am using the earlier build ( 2.6.3.1 ) and did face any problems. Flashing is easy and quick. Backing up and restoring is a piece of cake. No need of all these steps.
Cheers
Click to expand...
Click to collapse
Was using latest TWRP and yeah you right 2.6.3.1 works flawlessly no more flash errors! No vibration feedback on 2.6.3.1 though...
JordTOC said:
TWRP 2.6.3.1 download link below for everybodies reference: Unfortunatly I don't have enough posts to my name to post the link fully so please attach both of the below lines
goo.
im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img/
This also worked for me.
Click to expand...
Click to collapse
Thanks for the link it worked!

TWRP 2.8.5.0 for cm/ghost
The problem is in the "properties" TWRP sets; the official TWRP builds have
Code:
ro.build.product=moto_msm8960dt
and nothing for
Code:
ro.product.device
. moto_msm8960dt isn't listed in the CM12 script. So I unpacked the official 2.8.5.0, set the ro.product.device=ghost and packed it back. You can do it yourself or just grab the attachment and flash it.
- get the official TWRP image for ghost here: (ok, I'm new and not allowed to post links; it's something with techerrata, twrp2 and ghost)
- get CM12 source (search the net for something like build cyanogenmod 12 lollipop, there's plenty of posts)
(this will take like forever; I *think* you only need the folder android/system/system/core)
- fire up a terminal; notice the paths, make sure you execute the commands in the same directory
- first build mkbootimg and unpackbootimg
Code:
[email protected]:~/android/system/system/core > gcc -o /tmp/mkbootimg libmincrypt/*.c mkbootimg/mkbootimg.c -Iinclude
[email protected]:~/android/system/system/core > gcc -o /tmp/unpackbootimg libmincrypt/*.c mkbootimg/unpackbootimg.c -Iinclude
- unpack the official TWRP image:
Code:
[email protected]:~/twrp/work > /tmp/unpackbootimg -i ../openrecovery-twrp-2.8.5.0-ghost.img
Android magic found at: 0
BOARD_KERNEL_CMDLINE console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2 vmalloc=400M androidboot.write_protect=0 zcache
BOARD_KERNEL_BASE 80200000
BOARD_RAMDISK_OFFSET 02200000
BOARD_SECOND_OFFSET 00f00000
BOARD_TAGS_OFFSET 00000100
BOARD_PAGE_SIZE 2048
BOARD_SECOND_SIZE 0
BOARD_DT_SIZE 835240
- make a new folder, cd to it and extract the ramdisk
Code:
[email protected]:~/twrp/work/rd > gunzip -c ../openrecovery-twrp-2.8.5.0-ghost.img-ramdisk.gz | cpio -i
15231 blocks
- edit the file
Code:
default.prop
(add line ro.product.device=ghost)
- pack the ramdisk back:
Code:
[email protected]:~/twrp/work/rd > find . | cpio -o -H newc | gzip > ../newramdisk.gz
15231 blocks
- make the recovery image (I got the arguments from the output of unpackbootimage, see above)
Code:
[email protected]:~/twrp/work > /tmp/mkbootimg --kernel openrecovery-twrp-2.8.5.0-ghost.img-zImage --ramdisk newramdisk.gz --cmdline 'console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2 vmalloc=400M androidboot.write_protect=0 zcache' --base 0x80200000 --pagesize 2048 --dt openrecovery-twrp-2.8.5.0-ghost.img-dt --ramdisk_offset 0x02200000 -o twrp-2.8.5.0-ghost-modified-for-cm12.img

rrvvrr said:
The problem is in the "properties" TWRP sets; the official TWRP builds have
Code:
ro.build.product=moto_msm8960dt
and nothing for
Code:
ro.product.device
. moto_msm8960dt isn't listed in the CM12 script. So I unpacked the official 2.8.5.0, set the ro.product.device=ghost and packed it back. You can do it yourself or just grab the attachment and flash it.
- get the official TWRP image for ghost here: (ok, I'm new and not allowed to post links; it's something with techerrata, twrp2 and ghost)
- get CM12 source (search the net for something like build cyanogenmod 12 lollipop, there's plenty of posts)
(this will take like forever; I *think* you only need the folder android/system/system/core)
- fire up a terminal; notice the paths, make sure you execute the commands in the same directory
- first build mkbootimg and unpackbootimg
Code:
[email protected]:~/android/system/system/core > gcc -o /tmp/mkbootimg libmincrypt/*.c mkbootimg/mkbootimg.c -Iinclude
[email protected]:~/android/system/system/core > gcc -o /tmp/unpackbootimg libmincrypt/*.c mkbootimg/unpackbootimg.c -Iinclude
- unpack the official TWRP image:
Code:
[email protected]:~/twrp/work > /tmp/unpackbootimg -i ../openrecovery-twrp-2.8.5.0-ghost.img
Android magic found at: 0
BOARD_KERNEL_CMDLINE console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2 vmalloc=400M androidboot.write_protect=0 zcache
BOARD_KERNEL_BASE 80200000
BOARD_RAMDISK_OFFSET 02200000
BOARD_SECOND_OFFSET 00f00000
BOARD_TAGS_OFFSET 00000100
BOARD_PAGE_SIZE 2048
BOARD_SECOND_SIZE 0
BOARD_DT_SIZE 835240
- make a new folder, cd to it and extract the ramdisk
Code:
[email protected]:~/twrp/work/rd > gunzip -c ../openrecovery-twrp-2.8.5.0-ghost.img-ramdisk.gz | cpio -i
15231 blocks
- edit the file
Code:
default.prop
(add line ro.product.device=ghost)
- pack the ramdisk back:
Code:
[email protected]:~/twrp/work/rd > find . | cpio -o -H newc | gzip > ../newramdisk.gz
15231 blocks
- make the recovery image (I got the arguments from the output of unpackbootimage, see above)
Code:
[email protected]:~/twrp/work > /tmp/mkbootimg --kernel openrecovery-twrp-2.8.5.0-ghost.img-zImage --ramdisk newramdisk.gz --cmdline 'console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2 vmalloc=400M androidboot.write_protect=0 zcache' --base 0x80200000 --pagesize 2048 --dt openrecovery-twrp-2.8.5.0-ghost.img-dt --ramdisk_offset 0x02200000 -o twrp-2.8.5.0-ghost-modified-for-cm12.img
Click to expand...
Click to collapse
Hi!
Can you edit newest twrp-2.8.7.0?

BossToroech said:
Hi!
Can you edit newest twrp-2.8.7.0?
Click to expand...
Click to collapse
Done, attached 2.8.7

rrvvrr said:
Done, attached 2.8.7
Click to expand...
Click to collapse
Twrp 2.8.7 does not detect the SD card on my phone. It would be great if you edit twrp 2.8.6 as that worked.

Ishaan Gupta said:
Twrp 2.8.7 does not detect the SD card on my phone. It would be great if you edit twrp 2.8.6 as that worked.
Click to expand...
Click to collapse
I could, it only takes about 10 minutes... But I'm pretty sure you are looking for something else - this thread is about ghost, that's Moto X 2013, which doesn't have an SD card.
Please correct me if I'm wrong.

You are right. Moto X 2013 doesn't have an SD Card slot.

rrvvrr said:
I could, it only takes about 10 minutes... But I'm pretty sure you are looking for something else - this thread is about ghost, that's Moto X 2013, which doesn't have an SD card.
Please correct me if I'm wrong.
Click to expand...
Click to collapse
BossToroech said:
You are right. Moto X 2013 doesn't have an SD Card slot.
Click to expand...
Click to collapse
Thanks for your quick reply.
I am sorry I said wrong. I mean the /data partition. The internal storage.
I am on windows so I could not build the recovery. No idea how to do it.
Thanks for your work. It saved me from editing the updater-script every time.
EDIT: Got it to finally mount /data. Had to wipe everything then flash twrp 2.8.6.0 and then your edited 2.8.7.0.

smohanv said:
I have Moto x XT1052 EU version and could not flash most of CM based ROMs. It fails with error message as "This package is for device:
xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc,xt1056,ghost_sprint,xt1058,ghost_att,ghost_rcica,xt1060,ghost_verizon; this device is " + getprop("ro.product.device") + ".")".
This error is very much annoying. I found some tweak to successfully flash this ROM by following few simple steps:
ROMs causing this issue are,
[ROM] [4.4.4] [OFFICIAL] Ehndroix V 14.10.14 - Ghost
[Rom] [4.4.4] Cyanogenmod 11 for Moto X
N5X Experience ROM
1. Using 7z app, open flashable ROM zip file
2. go to META-INF\com\google\android\
3. drag and drop updater-script on your desktop
4. Open this script file with Notepad++
5. Delete the lines starting from "assert (getprop............ upto abort("this package....." (see screenshot attached)
6. Save the script in Notepad++
7. drag and drop this amended script file back to META-INF\com\google\android\
8. Close zip file
9. Copy to your phone sdcard memory
10. Don't forget to copy relevant gapps file as well
All done. Use your recovery (I prefer latest TWRP) and flash ROM and GAPPS.
Enjoy!!
Click to expand...
Click to collapse
I'm getting the same error for cm 12.1 on my moto x 2013 xt1052. What do i do?

Use the modified recovery @rrvvrr posted a few posts back.

Flashing Error
I recently rooted my XT 1052 (Asian version) using TWRP 2.8.6. However, when installing CM 12.1's 30/8 nightly build, I got an error reading "error executing updater binary in zip". Someone help me to solve this problem. I have installed the latest official TWRP 2.8.7.

vamshi03 said:
I'm getting the same error for cm 12.1 on my moto x 2013 xt1052. What do i do?
Click to expand...
Click to collapse
Exit the recovery and try again. If that doesn't work then unzip the Rom.zip file, if it opens with error then re download the Rom, otherwise if it opens without error then make a complete wipe of the phone and try again.
Chimax said:
I recently rooted my XT 1052 (Asian version) using TWRP 2.8.6. However, when installing CM 12.1's 30/8 nightly build, I got an error reading "error executing updater binary in zip". Someone help me to solve this problem. I have installed the latest official TWRP 2.8.7.
Click to expand...
Click to collapse
Sent from my Moto X

Thanks... The file is intact.... I will try it today again...
Sent from my XT1052 using XDA Free mobile app

No use
bushako said:
Exit the recovery and try again. If that doesn't work then unzip the Rom.zip file, if it opens with error then re download the Rom, otherwise if it opens without error then make a complete wipe of the phone and try again.
Sent from my Moto X
Click to expand...
Click to collapse
I did as you had instructed but still no use... The same error keeps on popping up... It's pathetic... even after rooting I can't install CM

Chimax said:
I did as you had instructed but still no use... The same error keeps on popping up... It's pathetic... even after rooting I can't install CM
Click to expand...
Click to collapse
Can you confirm that you are running the latest bootloader version? You could still be on the older bootloader and that's why it returns with errors.
However, if you are reluctant to upgrade bootloader for whatever reason, then you can try and flash an older version of twrp from before 5.1 was released or use another recovery such as cynagoen recovery or cmw if available.
I can explain to you as to why this happens but I prefer you first give it a try.
Sent from my Moto X

General Mobile 4G Brick

===Kamu Spotu===
Sorry for my bad language
===============
I did root with Kingo Root. When 1 minute after the root is completed, i restart my phone.
My phone stuck in android start screen.
What should I do?
I tried flash ROM but i can't do this.
I got some errors. ADB doesn't see my device and i try "fastboot oem unlock" command. i get this error:
FAILED (remote: oem unlock is not allowed).

SerhanCeetin said:
===Kamu Spotu===
Sorry for my bad language
===============
I did root with Kingo Root. When 1 minute after the root is completed, i restart my phone.
My phone stuck in android start screen.
What should I do?
I tried flash ROM but i can't do this.
I got some errors. ADB doesn't see my device and i try "fastboot oem unlock" command. i get this error:
FAILED (remote: oem unlock is not allowed).
Click to expand...
Click to collapse
Did you switch on oem unlock in developer settings before you done any of this kardeş?

Sorry for my bad language (I use an online translator.)
===============
Hi , phone doesn't run, the run logo and eternal reset, phone empty only burns, except a recovery there is nothing isn't present (The friend unintentionally removed everything, fairly itself I don't know as). And I don't know phone as to unlock, insertions, other recovery not a updatet. I tried in the different ways. Costs custom TWRP recovery. I tried to alter insertions and other recovery through TWRP, it is impossible gives out a mistake. And by the way yes my friend made full wipe. I come into the menu backup on TWRP and there volumes for a backup
System 2 mb
Data 0 mb
Cache 0 mb
Bootloader 32 mb
Recovery 32 mb
C:\fastboot>fastboot -i 0x2b4c oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.006s]
finished. total time: 0.006s
C:\fastboot>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.003s
Thank you

No need to unlock now (won't work anyway).
Flash a "system.img" from your backup via fastboot.
If you don`t have a backup, may be someone with a rooted device can pull it from the phone via "dd"..
First check the partition number of system (most likely mmcblk0p25):
Code:
ls -al /dev/block/platform/7824900.sdhci/by-name
pull it from the phone to sdcard:
Code:
dd if=/dev/block/mmcblk0p25 of=/sdcard/system.img bs=4096
Flash this system.img with fastboot:
Code:
fastboot flash system system.img
EDIT: And please, use another translator.

General Mobile 4G Unbrick (Motorola Factory Cable) Is it possible?
======Kamu Spotu======
Sorry for my bad English.
=====================
I saw a thread in other forum.
Can i unbrick my device (General Mobile 4G Android One) with this cable(Motorola Factory Cable)?
goo. gl/ZTdSRH
Rygebin™' dateline='1456518567 said:
Merhabalar arkadaşlar,
Bugün sizlere bir çok kişinin yakındığı General Mobile 4G'de Hardbrick (Susma , Hiç açılmama) sorunun çözümünü belirteceğim.
Gerekenler
5 Pinli USB Kablo
Snapdragon Usb Driver
QFIL Tool
GM 4G LUZ59F Full Firmware
5 PİNLİ USB KABLOSU
Motorola Factory Cable olarakta geçmektedir.
Yukarıda verdiğim şemadan yapabilirsiniz.
Ya da verdiğim fotoğrafa tıklayarak kabloyu satın alma linkine gidebilirsiniz.
Kurulum
QFIL Tool'u indirin.
Qualcoom Driverlar'ını indirin
Adb Driver ve Google USB Driver'ı indirin
Tüm driverları kurun ve daha sonrasında cihazınızı aldığınız kablo yardımıyla toola birlikte açın.
Not: Eğer driverları aygıt yöneticisinden ayarlamassanız ya da görülmesse kurulum gerçekleşmez
Aşağıda verdiğim şemadan işlemlere devam edin.
Yukarıdaki işlemler sonunda cihazınınız 5.1.1 sürümüyle açılacaktır.
İndirme Bağlantıları
QFIL Tool (2.7.422)
Google USB Driver
Qualcomm_USB_Drivers
ADB.rar
* General Mobile 4G Tek Sim Full Firmware
* General Mobile 4G Dual Sim Full Firmware {Yüklemeye başlanacak}
Click to expand...
Click to collapse
======Kamu Spotu======
Dikkat! Türkçe içerik.
Attention! Turkish content.
=====================
Beyler adam bi forumda Motorola Factory Cable ile GM 4G cihazımı unbrick yapabileceğimi söylüyor. Yani öyle bir konu açmış. Mümkün mü sizce?

@SerhanCeetin why don't you send to tech support? If they notice it's out of warranty you just pay 20TL (7$) for this. If they don't they'll fix it and send back in 1 to 5 days without any payment. Second generation forum in XDA is too small for this heavy jobs

Question [SOLVED] Bricked device - can only access MIUI Recovery and Fastboot

I f****d up.
Hi everyone. I may have bitten more than I can chew. I'm trying to install a custom ROM to my recently unlocked Redmi Note 10 Pro. It's crDroid in case that's necessary.
I did a lot of things but I forgot most of them. Here's what I remember doing:
Connected my phone to my Linux computer.
Go into fastboot modevia the following command:
Code:
adb reboot bootloader
Use TWRP by running this in a terminal:
Code:
fastboot boot twrp.img
Went in to the wipe option in TWRP and do a complete factory reset and format data.
Pushed the custom ROM file to /sdcard.
Attempted to install the zip file via TWRP.
Got an error code. Forgot the code and I didn't take note of it. (Please make fun of me).
Attempted to reboot TWRP recovery by going to Reboot > Recovery
Reached stock MIUI Recovery.
And here I am.
I can only access MIUI Recovery 5.0 and fastboot mode, both by pressing the right buttons on the device.
I don't know what a bricked device is, but it sure does feel like my device is one.
Is there a way to solve this?

zepolyerf said:
I f****d up.
Hi everyone. I may have bitten more than I can chew. I'm trying to install a custom ROM to my recently unlocked Redmi Note 10 Pro. It's crDroid in case that's necessary.
I did a lot of things but I forgot most of them. Here's what I remember doing:
Connected my phone to my Linux computer.
Go into fastboot modevia the following command:
Code:
adb reboot bootloader
Use TWRP by running this in a terminal:
Code:
fastboot boot twrp.img
Went in to the wipe option in TWRP and do a complete factory reset and format data.
Pushed the custom ROM file to /sdcard.
Attempted to install the zip file via TWRP.
Got an error code. Forgot the code and I didn't take note of it. (Please make fun of me).
Attempted to reboot TWRP recovery by going to Reboot > Recovery
Reached stock MIUI Recovery.
And here I am.
I can only access MIUI Recovery 5.0 and fastboot mode, both by pressing the right buttons on the device.
I don't know what a bricked device is, but it sure does feel like my device is one.
Is there a way to solve this?
Click to expand...
Click to collapse
Drivers installed?

Hi! How can I check if drivers are installed? I'm on Linux, if that matters.

Your device isn't bricked until you can do absolutely nothing with it. Start by reflashing the factory firmware; this should get your device running again.
You should also still be able to boot TWRP just like you did. What ROM were you trying to use?

V0latyle said:
Your device isn't bricked until you can do absolutely nothing with it. Start by reflashing the factory firmware; this should get your device running again.
You should also still be able to boot TWRP just like you did. What ROM were you trying to use?
Click to expand...
Click to collapse
That's good to hear.
I'm trying to make another attempt to boot to TWRP. I'm currently in fastboot mode: running fastboot -l devices shows this:
Code:
f8b471a6 fastboot
usb:1-5
I tried to following official TWRP instructions to flash it. Ran fastboot flash recovery twrp.img and all I get is <waiting for device> as a response after running the command in the terminal.
I unplug the cable, then plug it back in to the computer, then this is what I got:
Code:
Sending 'recovery' (131072 KB) FAILED (Write to device failed (Device or resource busy))
fastboot: error: Command failed
Any ideas on how to get around this?

zepolyerf said:
That's good to hear.
I'm trying to make another attempt to boot to TWRP. I'm currently in fastboot mode: running fastboot -l devices shows this:
Code:
f8b471a6 fastboot
usb:1-5
I tried to following official TWRP instructions to flash it. Ran fastboot flash recovery twrp.img and all I get is <waiting for device> as a response after running the command in the terminal.
I unplug the cable, then plug it back in to the computer, then this is what I got:
Code:
Sending 'recovery' (131072 KB) FAILED (Write to device failed (Device or resource busy))
fastboot: error: Command failed
Any ideas on how to get around this?
Click to expand...
Click to collapse
Your device might not have a recovery partition; in A/B partition layout devices, recovery lives in the boot image.
A bit of an explanation:
When you use fastboot boot <image> you're telling the device to load the image you're sending - so if you use fastboot boot twrp.img you're telling it to load the TWRP.img on your computer. This is what you should be using if you want to boot TWRP.
When you use fastboot flash <partition> <image> you're telling bootloader to flash the specified partition with the specified image. So, if you used fastboot flash boot twrp.img, bootloader will overwrite /boot with the TWRP image...meaning the device will only boot into TWRP.
As for why the device would only boot into stock recovery after you flashed the custom ROM, I suspect that it didn't flash the kernel, or otherwise may have corrupted the boot image. So, when the device tries to start the kernel, it failed and just boots into recovery instead.

What should I do at this point if I can't do fasboot boot <image> or fastboot flash <parition> <image> because of the <waiting for device> thing I get everytime I run those commands?

zepolyerf said:
What should I do at this point if I can't do fasboot boot <image> or fastboot flash <parition> <image> because of the <waiting for device> thing I get everytime I run those commands?
Click to expand...
Click to collapse
Reboot to bootloader. If you're currently in recovery mode, cancel the command (Ctrl+C) and use adb reboot bootloader. If you're currently in bootloader but it's not responding, just use the button combo to force a reset.
Remember, you can only use fastboot commands in bootloader mode. If you're in recovery, you can only use some ADB commands, but in this case, I don't think that will be much help.

This is just soft brick. A hard brick means no life in the device as well. In your case, you can still access recovery and fastboot. You can either use MiFlash and use fastboot to flash the stock rom (your choice if you want to relock the bootloader or not) or flash miui recovery rom directly in the custom recovery.
If I remember correctly too, crDroid requires it's provided recovery instead of TWRP so maybe that's why the installation failed.

I went into fastboot mode by pressing Vol Down + Power buttons.
Plugged the phone in to my Linux machine. Have VirtualBox recognize my device.
Opened MiFlash tool. Selected the flash rom from Xiaomi's site. Got an Antirollback error. Here's the logs:
Code:
[4:41:24 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:41:25 AM]:GetScriptDevices
[4:41:28 AM]:add device f8b471a6 index 0
[4:41:48 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:41:48 AM]:GetScriptDevices
[4:41:51 AM]:FlashingDevice.flashDeviceList.Remove f8b471a6
[4:41:51 AM]:add device f8b471a6 index 0
[4:41:51 AM]:Thread start,thread id 11,thread name f8b471a6
[4:41:51 AM]:start process id 4212 name cmd
[4:49:16 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:49:16 AM]:GetScriptDevices
[4:49:16 AM]:add device f8b471a6 index 1
[4:49:24 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:49:24 AM]:GetScriptDevices
[4:49:24 AM]:FlashingDevice.flashDeviceList.Remove f8b471a6
[4:49:24 AM]:add device f8b471a6 index 1
[4:49:24 AM]:Thread start,thread id 12,thread name f8b471a6
[4:49:24 AM]:start process id 1704 name cmd
[4:49:25 AM]:Thread stopped, thread id 12, thread name f8b471a6
[4:51:22 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:51:23 AM]:GetScriptDevices
[4:51:23 AM]:FlashingDevice.flashDeviceList.Remove f8b471a6
[4:51:23 AM]:add device f8b471a6 index 1
[4:51:23 AM]:Thread start,thread id 19,thread name f8b471a6
[4:51:23 AM]:start process id 3400 name cmd
[4:52:26 AM]:GetUserInfo
[4:52:39 AM]:authentication edl error:Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
[4:56:31 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:56:31 AM]:GetScriptDevices
[6:00:17 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:18 AM]:driver oem5.inf exists,uninstall,reuslt True,GetLastWin32Error
[6:00:19 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Google\Driver\android_winusb.inf to C:\Windows\INF\oem5.inf,result True,GetLastWin32Error
[6:00:19 AM]:set RegistryKey value:android_winusb.inf--oem5.inf
[6:00:19 AM]:mkdir "C:\Users\IEUser\.android"
[6:00:19 AM]:output:A subdirectory or file C:\Users\IEUser\.android already exists.
[6:00:19 AM]: echo 0x2717 >>"C:\Users\IEUser\.android\adb_usb.ini"
[6:00:19 AM]:output:
[6:00:19 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:19 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Nvidia\Driver\NvidiaUsb.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[6:00:19 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:20 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Microsoft\Driver\tetherxp.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[6:00:20 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:21 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Microsoft\Driver\wpdmtphw.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[6:00:21 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:21 AM]:driver oem6.inf exists,uninstall,reuslt True,GetLastWin32Error
[6:00:22 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\Driver\qcser.inf to C:\Windows\INF\oem6.inf,result True,GetLastWin32Error
[6:00:22 AM]:set RegistryKey value:qcser.inf--oem6.inf
[6:01:33 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[6:01:34 AM]:GetScriptDevices
[6:01:34 AM]:add device f8b471a6 index 1
[6:01:55 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[6:01:55 AM]:GetScriptDevices
[6:01:55 AM]:FlashingDevice.flashDeviceList.Remove f8b471a6
[6:01:55 AM]:add device f8b471a6 index 1
[6:01:55 AM]:Thread start,thread id 12,thread name f8b471a6
[6:01:55 AM]:start process id 6280 name cmd
[6:01:56 AM]:Thread stopped, thread id 12, thread name f8b471a6
Any idea on what to do next?

BigChungus321 said:
This is just soft brick. A hard brick means no life in the device as well. In your case, you can still access recovery and fastboot. You can either use MiFlash and use fastboot to flash the stock rom (your choice if you want to relock the bootloader or not) or flash miui recovery rom directly in the custom recovery.
If I remember correctly too, crDroid requires it's provided recovery instead of TWRP so maybe that's why the installation failed.
Click to expand...
Click to collapse
It might as well be a brick haha. I must be dumb (very likely) or there's just not a lot of clear and comprehensive resources out there to fix this kind of thing.

Ahh anti roll back error is pretty simple to fix, you just have to remove the check from the .bat files, there are tutorials on YT that can help, after that reflash stock rom in MiFlash.
If you're worried about anti roll back, don't worry, ARB value for the device has been 3 so far so it's safe to downgrade. Goodluck

Seeing a ton of Bricked Notes on here this last week, Y`all making me nervous about doing anything with mine lol

I faced this problem in linux got around it with usb 2.0 interface doesn't worked with usb 3.0 and above but my device was different when I got this recovery flash waiting problem. Also try to updated the platform tools.

So the solution was to entirely ditch Linux and use Windows to play with fastboot and adb commands via the terminal.
I don't understand why it worked when I did it on Windows when I was using the same platform tools on Linux. Oh well.