Development [ROM][11.0][OFFICIAL][ALIOTH/ALIOTHIN] EOL - crDroid v7.22 [12.09.2022] - Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features: https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Sources:
ROM:https://github.com/crdroidandroid
Kernel: kernel Optimus Drunk
Github: raystef66
LATEST crDroid Build
Flashing Instructions: FOLLOW NEW GUIDE
POCO F3 TELEGRAM GROUP
What's working / what's not:
* most of it is working :
ril
audio
wifi
BT
camera
NFC
FP
Faceunlock
GPS
AOD (tile)
hotspot
DT2W (on doze)
DT2S
ambient features
ok google
...
* bugs : DO SEND LOGS WHEN REPORTING BUGS
. . .
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
If you like my work, consider a donation! MY PAYPAL
Contributors
@raystef66
@jomadeto
Source Code: https://github.com/crdroidandroid/android/tree/11.0
ROM OS Version: 11.0
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader, miu v12.0.x or 12.5.x
Status: stable
Sec. Patches : 2022.09.05
Created : 2021.05.07
Last Updated : 2022.09.12

CHANGELOG
Highlights & Device Specific Changes:
Build type: Monthly
Device: POCO F3 (alioth)
Device maintainer: raystef66

raystef66 said:
CHANGELOG
Click to expand...
Click to collapse
Congrats boss for being Official

raystef66 said:
GAPPS INCLUDED for now
Click to expand...
Click to collapse
"for now" gives me hope that it won't be there at some point. Yes?
BTW: Thank you very much for developing/porting this ROM

Fahmid Islam Soumya said:
Congrats boss for being Official
Click to expand...
Click to collapse
Thnx bro

Awesome work

Robert314 said:
Awesome work
Click to expand...
Click to collapse
Waiting for yours

can I flash this from xiaomi*eu latest stable rom, sir?

My poco f3 should be delivered in days, I'm so happy seeing development advancing so fast. Thank you!

Installation is not working on stock (unlocked) alioth_global_images_V12.0.3.0.RKHMIXM rom
H:\crDroidAndroid-11.0-20210507-alioth-v7.5>.\platform-tools-windows\fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
it will boot to a special FASTBOOTD menu and it is stuck with < waiting for any device >
... so i have to select fastboot again..... then it reboot to MI fastboot menu it stuck the same, so i have unplug the usb cable to continue and work..
but in the MI fastboot mode, it cannot flash system.img
H:\crDroidAndroid-11.0-20210507-alioth-v7.5>.\platform-tools-windows\fastboot flash system_a Images/system.img
Sending sparse 'system_a' 1/2 (774900 KB) OKAY [ 17.824s]
Writing 'system_a' FAILED (remote: 'Partition not found')
fastboot: error: Command failed

Does it have OTA?

Can i flash it over base miui 12.6?

So only SSOS has a fully working D2tw right?
so far so good. love crdroid! thanks matey! <3

hkfriends said:
Installation is not working on stock (unlocked) alioth_global_images_V12.0.3.0.RKHMIXM rom
H:\crDroidAndroid-11.0-20210507-alioth-v7.5>.\platform-tools-windows\fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
it will boot to a special FASTBOOTD menu and it is stuck with < waiting for any device >
... so i have to select fastboot again..... then it reboot to MI fastboot menu it stuck the same, so i have unplug the usb cable to continue and work..
but in the MI fastboot mode, it cannot flash system.img
H:\crDroidAndroid-11.0-20210507-alioth-v7.5>.\platform-tools-windows\fastboot flash system_a Images/system.img
Sending sparse 'system_a' 1/2 (774900 KB) OKAY [ 17.824s]
Writing 'system_a' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Click to expand...
Click to collapse
Having the exact same issue with this ROM and Pixel Experience.... coming from a newly flashed 12.0.2 global fastboot and freshly unlocked bootloader...have no problems with xiaomi.eu though

navey said:
Having the exact same issue with this ROM and Pixel Experience.... coming from a newly flashed 12.0.2 global fastboot and freshly unlocked bootloader...
Click to expand...
Click to collapse
replug or use a different cable.
use a different platform tools (adb and fastboot exe) I prefer the one's from google but not the latest fastboot as it borks flashing stock roms via fastboot

Abaddon said:
replug or use a different cable.
use a different platform tools (adb and fastboot exe) I prefer the one's from google but not the latest fastboot as it borks flashing stock roms via fastboot
Click to expand...
Click to collapse
tried several cables and like i said I don't have any issues with xiaomi.eu at all. I see my device just fine in adb and fastboot as well.. will do more research

navey said:
tried several cables and like i said I don't have any issues with xiaomi.eu at all. I see my device just fine in adb and fastboot as well.. will do more research
Click to expand...
Click to collapse
I said those because I had a similar scenario. xiaomi eu fastboot flashes fine but other fastboot roms wont flash properly. its either my port (had to replug), usb drivers and the fastboot exe itself. I fixed it by changing the fastboot.exe to an older one. goodluck with yours hope u get it fixed asap

hkfriends said:
Installation is not working on stock (unlocked) alioth_global_images_V12.0.3.0.RKHMIXM rom
H:\crDroidAndroid-11.0-20210507-alioth-v7.5>.\platform-tools-windows\fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
it will boot to a special FASTBOOTD menu and it is stuck with < waiting for any device >
... so i have to select fastboot again..... then it reboot to MI fastboot menu it stuck the same, so i have unplug the usb cable to continue and work..
but in the MI fastboot mode, it cannot flash system.img
H:\crDroidAndroid-11.0-20210507-alioth-v7.5>.\platform-tools-windows\fastboot flash system_a Images/system.img
Sending sparse 'system_a' 1/2 (774900 KB) OKAY [ 17.824s]
Writing 'system_a' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Click to expand...
Click to collapse
Fixed this! Enabled system wide ADB on my machine and now its working smoothly so far with no errors whatsoever. Follow this link
Set up System-wide ADB and Fastboot on Windows 10/11
Here's how to set up system-wide ADB and Fastboot on Windows 10 and 11. Download SDK platform tools and enjoy universal ADB and Fastboot.
technastic.com

Abaddon said:
I said those because I had a similar scenario. xiaomi eu fastboot flashes fine but other fastboot roms wont flash properly. its either my port (had to replug), usb drivers and the fastboot exe itself. I fixed it by changing the fastboot.exe to an older one. goodluck with yours hope u get it fixed asap
Click to expand...
Click to collapse
Thanks man i actually got it fixed by installing system wide adb but it was your thoughts that lead me there. THANK YOU!!

navey said:
Fixed this! Enabled system wide ADB on my machine and now its working smoothly so far with no errors whatsoever. Follow this link
Set up System-wide ADB and Fastboot on Windows 10/11
Here's how to set up system-wide ADB and Fastboot on Windows 10 and 11. Download SDK platform tools and enjoy universal ADB and Fastboot.
technastic.com
Click to expand...
Click to collapse
will try this out tonight... strangely it is due to missing system path to execute fastboot?

Related

fastboot flash system: partition not found

Hi All,
used my OP7T for a week before deciding to unlock. That went fine, but when I tried to flash a GSI (no custom ROMs available yet), it says partition not found?? Tried system and system_a.
Code:
[email protected]:~/Downloads/Android$ fastboot flash system system-quack-arm64-ab-vanilla.img
Sending sparse 'system' 1/3 (786428 KB) OKAY [ 24.933s]
Writing sparse 'system' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.950s
[email protected]:~/Downloads/Android$ fastboot flash system_a Havoc-OS-3.0_ARM64-AB.img
Sending sparse 'system_a' 1/3 (786428 KB) OKAY [ 24.953s]
Writing sparse 'system_a' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.965s
[email protected]:~/Downloads/Android$
Hey,
I have the same issue, did you ever find a solution?
You must unlock first
You don't say
In the meantime I found the actual solution, here it is for the record : reboot from fastboot to fastbootd using "fastboot reboot fastboot"
And then the commands will work
natinusala said:
You don't say
In the meantime I found the actual solution, here it is for the record : reboot from fastboot to fastbootd using "fastboot reboot fastboot"
And then the commands will work
Click to expand...
Click to collapse
Got: "fastboot: usage: unknown reboot target fastboot"
bump
SecondSon1 said:
Got: "fastboot: usage: unknown reboot target fastboot"
Click to expand...
Click to collapse
been messing all night with fastboot trying to get it to boot to fastbootd
i keep getting this same error and so my phone is currently bricked as i cannot install the
system.img or anything that follows. also tried booting to fastbootd by doing
fastboot reboot recovery but it cannot find reboot target recovery either.
this is what i did
dosnoventa said:
been messing all night with fastboot trying to get it to boot to fastbootd
i keep getting this same error and so my phone is currently bricked as i cannot install the
system.img or anything that follows. also tried booting to fastbootd by doing
fastboot reboot recovery but it cannot find reboot target recovery either.
Click to expand...
Click to collapse
i got it working
Please help
sathara said:
i got it working
Click to expand...
Click to collapse
I'm getting
remote: Failed operation not permitted
and
remote: value to large for defined data type please help
i had the same problem. solved it by flashing msm extended recovery to both slots. that recovery has option to enter fastbootd
altojd said:
i had the same problem. solved it by flashing msm extended recovery to both slots. that recovery has option to enter fastbootd
Click to expand...
Click to collapse
Can you share that recovery image?
I couldn't find it in the Rom files.
For my 600th post on XDA, I offer this info in hopes it will help.
This one is T-mobile. Don't know if it will help ort harm but it works for me.
I don't have both hands right now; yoiu'll have to search for yourself on how to enter "EDL" mode and possibly an MSM (or is it MDM?) version of stock flashable file for your model and carrier, else maybe try the T-Mobile one at your own risk: Unbrick Tool for T-Mobile
GOOD LUCK
Hi guys,
When I type ' fastboot reboot fastboot ' in windows command prompt, I got the help menu of fastboot, anyone got a solution ?
My phone (Redmi 9 Note Pro) is bricked because I can't flash a system.img
Booting into fastboot using volumedown + power isn't working.
OKAY [ 17.778s]
writing 'system'...
FAILED (remote: Partition not found)
josdehaes said:
Hi All,
used my OP7T for a week before deciding to unlock. That went fine, but when I tried to flash a GSI (no custom ROMs available yet), it says partition not found?? Tried system and system_a.
Code:
[email protected]:~/Downloads/Android$ fastboot flash system system-quack-arm64-ab-vanilla.img
Sending sparse 'system' 1/3 (786428 KB) OKAY [ 24.933s]
Writing sparse 'system' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.950s
[email protected]:~/Downloads/Android$ fastboot flash system_a Havoc-OS-3.0_ARM64-AB.img
Sending sparse 'system_a' 1/3 (786428 KB) OKAY [ 24.953s]
Writing sparse 'system_a' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.965s
[email protected]:~/Downloads/Android$
Click to expand...
Click to collapse
Did you find a solution ?
Download latest fastboot drivers.
From OS:
adb reboot fastboot
Or from bootloader
fastboot reboot fastboot
With devices launched on Android 10 there is a new interface called fastbootd, this is where you flash the system.
Lethien said:
Did you find a solution ?
Click to expand...
Click to collapse
clearly. there is a difference between "old" fastboot (bootloader) and fastbootd (userspace fastboot to support dynamic partitions). You need to be in fastbootd to do most stuff nowadays.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My problem is bit different, can anybody help through this --- System partitioned doesn't exist !!!! while Gsi flashing on Realme 7 RMX2151
So when you see people posting in their tutorial;
fastboot reboot fastboot
NOW we type in;
fastboot reboot fastbootd?
No, same command, but you need stock recovery for this to work (twrp prevents fastbootd entry)
I tried for days to get to work but for TMobile follow guide on here and if it doesn't work even after you install drivers and all then use a different PC bc I have 7t and 8t OnePlus and my 8t unlocked works on my gf PC and her 7t TMobile works on mine figured that out the hard way but it's truthfully a solution when everything won't work
Levi0630 said:
I tried for days to get to work but for TMobile follow guide on here and if it doesn't work even after you install drivers and all then use a different PC bc I have 7t and 8t OnePlus and my 8t unlocked works on my gf PC and her 7t TMobile works on mine figured that out the hard way but it's truthfully a solution when everything won't work
Click to expand...
Click to collapse
Convert TMobile op7t to global using msmtool

[ROM] [10] OmniRom for OnePlus7T Pro [EXPERT]

CLOSED PER OP REQUEST
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download unoficial:
DOWNLOAD Unofficial
Kernel source:
Source
Selinux Status:
Enforcing
Safetynet Status:
PASS (didnt test, should pass)
MAJOR BUGS:
huh ?
Minor bugs:
?
flash on your own risk.
FLASHING
This is for experianced people only, because theres no working TWRP yet. If you dont know how to read stop here (funny eh ?). Also if you dont wanna follow steps bellow because u know better. Goodbye. I dont wanna listen to you cry here. I will not help you.
opposite of what happens if you flash in twrp, this procedure will flash to the slot whis is active now. if you know what u r doing u can flash to any slot u like.
Despite the red text theres really no big danger here if you follow the steps. I just wana scare away newbs.
BU!
android 10 shipped devices have fastboot like we know it and its pretty much useless. and they have the new fastbootd (google it). Make sure u download the latest fastboot from google.
1st. get into fastbootd.
option a) from old fastboot, type: fastboot reboot fastboot (funny eh ?) another google miracle to not name it fastbootd.
option b) if you have a running os with adb: adb reboot fastboot
this will bring you to OOS chinese recovery look a like, but its fastboot. to test that u r in the right place try a fastboot command. fastboot getvar all for example.
2nd. flash
unzip ROM.
option a) if you are on linux
fastboot -w //this will wipe all your data. you need to do this only on first install, not on updates.
sh ./fastboot_flash.sh
option b)
again! fastboot -w // will wipe all your data and is needed only on first flash
Code:
fastboot -w
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash dtbo dtbo.img
fastboot reboot
3rd. enjoy opensource
unfortunately because of the flashing procedure I have included gapps. when twrp exists they will be gone.
Updating: (WILL WORK ONCE OFFICIAL)
Use OTA inside rom for updates
if u did something else. we dont need/wanna know about it in the thread
May the force be with you
Device Maintainers
@vache,
@maxwen
XDA:DevDB Information
OmniRom, ROM for the OnePlus 7T Pro
Contributors
darkobas, maxwen
Source Code: https://github.com/omnirom/android_kernel_oneplus_sm8150/tree/android-10
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: 10
Version Information
Status: Beta
Created 2019-11-14
Last Updated 2020-01-08
first
Wahoo. Thanks for this.
Oooo nice ?
new build is up
fingerprint should be fine now
10.0x whatever is the latest release blobs.
other little stuff
and whats below:
darkobas said:
Download unoficial:
DOWNLOAD Unofficial
Kernel source:
Source
Selinux Status:
Enforcing
Safetynet Status:
PASS (didnt test, should pass)
MAJOR BUGS:
huh ?
Minor bugs:
?
flash on your own risk.
FLASHING
This is for experianced people only, because theres no working TWRP yet. If you dont know how to read stop here (funny eh ?). Also if you dont wanna follow steps bellow because u know better. Goodbye. I dont wanna listen to you cry here. I will not help you.
opposite of what happens if you flash in twrp, this procedure will flash to the slot whis is active now. if you know what u r doing u can flash to any slot u like.
Despite the red text theres really no big danger here if you follow the steps. I just wana scare away newbs.
BU!
android 10 shipped devices have fastboot like we know it and its pretty much useless. and they have the new fastbootd (google it). Make sure u download the latest fastboot from google.
1st. get into fastbootd.
option a) from old fastboot, type: fastboot reboot fastboot (funny eh ?) another google miracle to not name it fastbootd.
option b) if you have a running os with adb: adb reboot fastboot
this will bring you to OOS chinese recovery look a like, but its fastboot. to test that u r in the right place try a fastboot command. fastboot getvar all for example.
2nd. flash
unzip ROM.
option a) if you are on linux
fastboot -w //this will wipe all your data. you need to do this only on first install, not on updates.
sh ./fastboot_flash.sh
option b)
again! fastboot -w // will wipe all your data and is needed only on first flash
Code:
fastboot -w
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash dtbo dtbo.img
fastboot reboot
3rd. enjoy opensource
unfortunately because of the flashing procedure I have included gapps. when twrp exists they will be gone.
Updating: (WILL WORK ONCE OFFICIAL)
Use OTA inside rom for updates
if u did something else. we dont need/wanna know about it in the thread
May the force be with you
Device Maintainers
@vache,
@maxwen
XDA:DevDB Information
OmniRom, ROM for the OnePlus 7T Pro
Contributors
darkobas, maxwen
Source Code: https://github.com/omnirom/android_kernel_oneplus_sm8150/tree/android-10
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: 10
Version Information
Status: Beta
Created 2019-11-14
Last Updated 2019-11-19
Click to expand...
Click to collapse
download error!
Thx. How to root??
Just_Pisces said:
Thx. How to root??
Click to expand...
Click to collapse
Mate if you can't find out how to root I really don't think you should be flashing this. Look thro the forum the answer is there.
p70shooter said:
Mate if you can't find out how to root I really don't think you should be flashing this. Look thro the forum the answer is there.
Click to expand...
Click to collapse
Thx. Just forgot to check“Preserve AVB 2.0/dm-verity”. Now Successfully
Hello to all ..... Unfortunately, the download link is not up to date or the destination host is not available ... could someone please upload the ZIP or create a new link to download? many thanks
its back online
darkobas said:
Download unoficial:
DOWNLOAD Unofficial
Kernel source:
Source
Selinux Status:
Enforcing
Safetynet Status:
PASS (didnt test, should pass)
MAJOR BUGS:
huh ?
Minor bugs:
?
flash on your own risk.
FLASHING
This is for experianced people only, because theres no working TWRP yet. If you dont know how to read stop here (funny eh ?). Also if you dont wanna follow steps bellow because u know better. Goodbye. I dont wanna listen to you cry here. I will not help you.
opposite of what happens if you flash in twrp, this procedure will flash to the slot whis is active now. if you know what u r doing u can flash to any slot u like.
Despite the red text theres really no big danger here if you follow the steps. I just wana scare away newbs.
BU!
android 10 shipped devices have fastboot like we know it and its pretty much useless. and they have the new fastbootd (google it). Make sure u download the latest fastboot from google.
1st. get into fastbootd.
option a) from old fastboot, type: fastboot reboot fastboot (funny eh ?) another google miracle to not name it fastbootd.
option b) if you have a running os with adb: adb reboot fastboot
this will bring you to OOS chinese recovery look a like, but its fastboot. to test that u r in the right place try a fastboot command. fastboot getvar all for example.
2nd. flash
unzip ROM.
option a) if you are on linux
fastboot -w //this will wipe all your data. you need to do this only on first install, not on updates.
sh ./fastboot_flash.sh
option b)
again! fastboot -w // will wipe all your data and is needed only on first flash
Code:
fastboot -w
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash dtbo dtbo.img
fastboot reboot
3rd. enjoy opensource
unfortunately because of the flashing procedure I have included gapps. when twrp exists they will be gone.
Updating: (WILL WORK ONCE OFFICIAL)
Use OTA inside rom for updates
if u did something else. we dont need/wanna know about it in the thread
May the force be with you
Device Maintainers
@vache,
@maxwen
XDA:DevDB Information
OmniRom, ROM for the OnePlus 7T Pro
Contributors
darkobas, maxwen
Source Code: https://github.com/omnirom/android_kernel_oneplus_sm8150/tree/android-10
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: 10
Version Information
Status: Beta
Created 2019-11-14
Last Updated 2019-11-22
Click to expand...
Click to collapse
Hi for some reason it didn't work for me
Wipe successful could not partition
Error message Failed remote not discoverable when flashing images.
I'm paraphrasing I accidentally closed the command prompt after rebooting.
It clearly says its only for people that can read and follow instructions.
Hm, I can't write system neither to 'a' or 'b' slot ... boot image is looking ok.
What I am doing wrong?
I am on latest 10.0.4.
Code:
PS C:\op7t\omni-10-20191201-oneplus7tpro-IMG> fastboot flash boot boot.img
Sending 'boot_a' (98304 KB) OKAY [ 2.309s]
Writing 'boot_a' OKAY [ 0.314s]
Finished. Total time: 2.651s
PS C:\op7t\omni-10-20191201-oneplus7tpro-IMG> fastboot flash system system.img
Sending sparse 'system' 1/2 (786428 KB) OKAY [ 18.412s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
PS C:\op7t\omni-10-20191201-oneplus7tpro-IMG> fastboot --set-active=b
Setting current slot to 'b' OKAY [ 0.039s]
Finished. Total time: 0.047s
PS C:\op7t\omni-10-20191201-oneplus7tpro-IMG> fastboot flash boot boot.img
Sending 'boot_b' (98304 KB) OKAY [ 2.317s]
Writing 'boot_b' OKAY [ 0.410s]
Finished. Total time: 2.753s
PS C:\op7t\omni-10-20191201-oneplus7tpro-IMG> fastboot flash system system.img
Sending sparse 'system' 1/2 (786428 KB) OKAY [ 18.450s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
EDIT:
Not sure if it helps but this is what I get from "fastboot getvar all"
Code:
(bootloader) has-slot:system:no
Also tried it from 10.0.3 base to check if it's bootloader issue with no change.
EDIT2:
Oh well, I am an idiot who can't read instructions properly and didn't realize there are two fastboots
You need to reboot to fastbootd from fastboot !!
I will leave this here for people like me.
@darkobas thanks for the amazing rom!!! it works flawlesly
guys does anyone know if any other kernel work with this rom? I have issues with usb dac which I connect with usb type c to female usb, it`s otg cable but when I connect it somehowpower from the kernel is not enough to power it. Had same issue on stock oos until I flashed ElementalX but this kernel throw the phone is bootloop. Probably someone more experienced have info how to fix this? Thanks
darkoj2007 said:
guys does anyone know if any other kernel work with this rom? I have issues with usb dac which I connect with usb type c to female usb, it`s otg cable but when I connect it somehowpower from the kernel is not enough to power it. Had same issue on stock oos until I flashed ElementalX but this kernel throw the phone is bootloop. Probably someone more experienced have info how to fix this? Thanks
Click to expand...
Click to collapse
Find the kernel patch then we can continue to talk
maxwen said:
Find the kernel patch then we can continue to talk
Click to expand...
Click to collapse
Can we talk about Wireguard?
maxwen said:
Find the kernel patch then we can continue to talk
Click to expand...
Click to collapse
interesting thing is I flashed other kernels and get them to work but none of them actually does the job. returned to stock oos also I can`t get it working tried same combo on wife`s samsung phone all works as it should. I have Dragonfly dac whic i connect with usb type c to female usb, the dac has incorporated mechanism to change colour dependant from what khz comes to him. but when I connect it to a phone shows colour like 96khz which is maximum and when I start playing music goes to blue which is equal to 44.1 khz which is android native. anyone can provide solution for connecting properly with otg?
houmles said:
Can we talk about Wireguard?
Click to expand...
Click to collapse
No - somr things never change
---------- Post added at 08:01 PM ---------- Previous post was at 08:00 PM ----------
darkoj2007 said:
interesting thing is I flashed other kernels and get them to work but none of them actually does the job. returned to stock oos also I can`t get it working tried same combo on wife`s samsung phone all works as it should. I have Dragonfly dac whic i connect with usb type c to female usb, the dac has incorporated mechanism to change colour dependant from what khz comes to him. but when I connect it to a phone shows colour like 96khz which is maximum and when I start playing music goes to blue which is equal to 44.1 khz which is android native. anyone can provide solution for connecting properly with otg?
Click to expand...
Click to collapse
BORING!!!

[ROM][10][UNOFFICIAL] OmniROM

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download :
GApps : https://dl.omnirom.org/tmp/def/
microG : https://dl.omnirom.org/def/
Kernel source
Device tree source
MAJOR BUGS:
you tell me
FLASHING
Android 10 shipped devices have fastboot like we know it and its pretty much useless. and they have the new fastbootd (google it).
Get into fastbootd.
option a) from old fastboot, type: fastboot reboot fastboot (funny eh ?) another google miracle to not name it fastbootd.
option b) if you have a running os with adb: adb reboot fastboot
You should see a recovery like screen with a red "fastbood" message
Extract payload.bin using payload dumper (google it for tutorials)
fastboot -w (warning : this will wipe all your data)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
UPDATE
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
Telegram group for One Hyper : https://t.me/MotoOneHyper
XDA:DevDB Information
OmniROM, ROM for the Motorola One Hyper
Contributors
vache
Source Code: https://github.com/omnirom/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked bootloader
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2020-02-02
Created 2020-02-02
Last Updated 2020-08-15
I unlocked my bootloader of my Motorola One Hyper and tried to install this rom.
The flashing is ok untill the flashing of the system. When I run :
fastboot flash system system.img
Resizing 'system_b' FAILED (remote: '')
fastboot: error: Command failed
I get an error as response. Any clue ?
orimigato said:
I unlocked my bootloader of my Motorola One Hyper and tried to install this rom.
The flashing is ok untill the flashing of the system. When I run :
fastboot flash system system.img
Resizing 'system_b' FAILED (remote: '')
fastboot: error: Command failed
I get an error as response. Any clue ?
Click to expand...
Click to collapse
I don't get why it's trying to flash on slot b, did you get an OTA since you got the phone ?
vache said:
I don't get why it's trying to flash on slot b, did you get an OTA since you got the phone ?
Click to expand...
Click to collapse
Yes I got an OTA when I got my phone today.
orimigato said:
Yes I got an OTA when I got my phone today.
Click to expand...
Click to collapse
Download stock ROM that match your current version from https://mirrors.lolinet.com/firmware/moto/def/official/
Then flash super image and try to flash ROM again.
Code:
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
vache said:
Download stock ROM that match your current version from ...
Then flash super image and try to flash ROM again.
Code:
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
Click to expand...
Click to collapse
I have downloaded the official firmware (RETEU) which matches my device and carried out the flashing steps as you described. After that I tried to reflash your your rom and now got the following error :
fastboot flash system system.img
Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed
orimigato said:
I have downloaded the official firmware (RETEU) which matches my device and carried out the flashing steps as you described. After that I tried to reflash your your rom and now got the following error :
fastboot flash system system.img
Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
Weird.
1. Are you sure that you're in fastbootd and not bootloader mode ?
2. Make sure to run the latest version of fastboot : https://dl.google.com/android/repository/platform-tools-latest-windows.zip
vache said:
Weird.
1. Are you sure that you're in fastbootd and not bootloader mode ?
2. Make sure to run the latest version of fastboot : https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Click to expand...
Click to collapse
That was the problem. When I did a fastboot reboot fastboot and retried the install. It succeeded.
Rom is now succesfully installed. First impression : its really fast compared to stock !
Thanks for your kind and quick help !!!
orimigato said:
That was the problem. When I did a fastboot reboot fastboot and retried the install. It succeeded.
Rom is now succesfully installed. First impression : its really fast compared to stock !
Thanks for your kind and quick help !!!
Click to expand...
Click to collapse
Wew cool it worked, i was running out of ideas xD
First impression after a few days of running this rom :
-Stable
-Uptime good
-Fast
-Clean
A few things that are not working/not present :
-I have 3 bluetooth devices. 2 headsets, and one car (profile audio & telephone). The 2 headsets will connect fine, but no audio is send trough the bluetooth connection. Audio is still output to the internal speaker. The car is connecting to telephone bluetooth profile but will refuse to connect to bluetooth audio profile.
-The camera does not include support for the wideangle (0,5x zoom) camera (or I cant find it...)
-The interal SIP client is not working. It says it is connected and accepting calls but no calls are received. I used the same SIP account with exactly the same settings on my other phone running Lineage with the same internal SIP client, and this one is running fine and receiving calls.
One note : I turned off all google apps including Play services and Google partner setup. However when switching these on, I got the same issues as described above.
Very happy with this ROM so far, keep up the good work !
orimigato said:
First impression after a few days of running this rom :
-Stable
-Uptime good
-Fast
-Clean
A few things that are not working/not present :
-I have 3 bluetooth devices. 2 headsets, and one car (profile audio & telephone). The 2 headsets will connect fine, but no audio is send trough the bluetooth connection. Audio is still output to the internal speaker. The car is connecting to telephone bluetooth profile but will refuse to connect to bluetooth audio profile.
-The camera does not include support for the wideangle (0,5x zoom) camera (or I cant find it...)
-The interal SIP client is not working. It says it is connected and accepting calls but no calls are received. I used the same SIP account with exactly the same settings on my other phone running Lineage with the same internal SIP client, and this one is running fine and receiving calls.
One note : I turned off all google apps including Play services and Google partner setup. However when switching these on, I got the same issues as described above.
Very happy with this ROM so far, keep up the good work !
Click to expand...
Click to collapse
Thanks for the detailed report.
1. About bluetooth, noticed that later while testing, already fixed.
2. You'd better install back Moto Camera 2 from Play Store if you want to get all stock features.
3. Never used that feature tbh, could you grab some logs ? (i'll make some tests on my side anyway)
I'll try to release the new build later today.
Edit : Created an account here : https://www.linphone.org/freesip/home
Then used https://freephonebox.net/ to call me, and it seems to work. (see attached screenshots)
SIP
Retried the SIP and now it is working. Possible was not working earlier since my old phone was still registered. Thanks for checking:good:
Any idea when you could have a build available? Thanks in advance for your efforts :good:
orimigato said:
Any idea when you could have a build available? Thanks in advance for your efforts :good:
Click to expand...
Click to collapse
Sorry, it was delayed cause i was working on dolby. Ill post it tomorrow.
Edit : New build ->https://www.androidfilehost.com/?fid=4349826312261718849 (check OP for update instruction)
Changelog :
- Fix bluetooth audio playback
- Added Dolby audio (Use QS Tile to open it for now)
- Added Google Feed to launcher
- February security patch
- Fixed tap to wake
- Synced kernel source with CAF
https://gerrit.omnirom.org/q/status:merged
https://github.com/boulzordev/device_motorola_def/commits/android-10
https://github.com/boulzordev/kernel_motorola_sm6150/commits/android-10
Bluetooth works perfectly now. Dolby is also very nice. Many thanks!
Can we install magisk and install root apps
Also what is the camera sensor used in this phone, Sony IMX686 or Samsung GW1?
htcmusic said:
Can we install magisk and install root apps
Also what is the camera sensor used in this phone, Sony IMX686 or Samsung GW1?
Click to expand...
Click to collapse
Yes what's the best root method you guys using?
young-ster said:
Yes what's the best root method you guys using?
Click to expand...
Click to collapse
I will receive this phone next week (US version) and I will use patching boot.img method
mingkee said:
I will receive this phone next week (US version) and I will use patching boot.img method
Click to expand...
Click to collapse
I'm waiting around first to see more updates, also patching boot.img I could not find the same firmware version. mine ends with a 7
young-ster said:
Yes what's the best root method you guys using?
Click to expand...
Click to collapse
young-ster said:
I'm waiting around first to see more updates, also patching boot.img I could not find the same firmware version. mine ends with a 7
Click to expand...
Click to collapse
I see it
https://mirrors.lolinet.com/firmware/moto/def/official/RETUS/

The System has been destroyed - only fastboot possible

Hello,
I bricked my Redmi Note 8T and I have no idea how to save my phone!
What did I do?
I unlocked my phone with XiaomiTool V2 and added Magisk, installed TWRP and trieed to add LineageOS.
So I tried to restart but the system stocked in a "boot - shutdown - boot - shutdown..."
I read in a description, that I have to delete in TWRP-mode some folders in WIPE so I deleted "System", "Data", "Cache", and maybe some other folders! I'm so stupid!
So there is only "The System has been destroyed", after around 30 seconds the system starts again and the bad massage comes again...
It is just possible to start the fastboot mode!
So I tried again to flash and boot TWRP:
sudo fastboot flash recovery twrp.img
target reported max download size of 804274176 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.617s]
writing 'recovery'...
OKAY [ 0.349s]
finished. total time: 1.967s
sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.615s]
booting...
FAILED (status read failed (No such device))
finished. total time: 37.120s
Afterwards the system says again "The System has been destroyed".
So now I don't have any idea to save my phone!
Please help me! I trust in you!
My OS on the PC is Ubuntu for your information...
Best wishes
De Blasmuskant
Blasmuskant said:
Hello,
I bricked my Redmi Note 8T and I have no idea how to save my phone!
What did I do?
I unlocked my phone with XiaomiTool V2 and added Magisk, installed TWRP and trieed to add LineageOS.
So I tried to restart but the system stocked in a "boot - shutdown - boot - shutdown..."
I read in a description, that I have to delete in TWRP-mode some folders in WIPE so I deleted "System", "Data", "Cache", and maybe some other folders! I'm so stupid!
So there is only "The System has been destroyed", after around 30 seconds the system starts again and the bad massage comes again...
It is just possible to start the fastboot mode!
So I tried again to flash and boot TWRP:
sudo fastboot flash recovery twrp.img
target reported max download size of 804274176 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.617s]
writing 'recovery'...
OKAY [ 0.349s]
finished. total time: 1.967s
sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.615s]
booting...
FAILED (status read failed (No such device))
finished. total time: 37.120s
Afterwards the system says again "The System has been destroyed".
So now I don't have any idea to save my phone!
Please help me! I trust in you!
My OS on the PC is Ubuntu for your information...
Best wishes
De Blasmuskant
Click to expand...
Click to collapse
Doesn't sound so bad. And of you had searched the forum before panic posting, you would have easily found at least 3 similar threads already started.
Not knowing what you had wiped from twrp before, leaves the best option for you is to flash the factory fastboot ROM, and then start over.
There is a thread here about fastboot ROM i beleive.
just miflash
Blasmuskant said:
Afterwards the system says again "The System has been destroyed".
So now I don't have any idea to save my phone!
Please help me! I trust in you!
My OS on the PC is Ubuntu for your information...
Best wishes
De Blasmuskant
Click to expand...
Click to collapse
in fastboot rom there must be a file vbmeta.img....if you don't want to download the fastboot rom then download vbmeta.img from here or here..
then download latest platform tools.
extract the plaform tools zip...copy vbmeta.img in this folder,open cmd/terminal in this folder path and flash vbmeta with phone in fastboot mode by this command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after this flash recovery.
Thank you for your fast answers! I tried already the search function but it seemed to me beeing different problems!
wsdyleon said:
just miflash
Click to expand...
Click to collapse
How can I do it in fastboot mode with Linux?
the_weird_aquarian said:
in fastboot rom there must be a file vbmeta.img....if you don't want to download the fastboot rom then download vbmeta.img from ...
then download ...
extract the plaform tools zip...copy vbmeta.img in this folder,open cmd/terminal in this folder path and flash vbmeta with phone in fastboot mode by this command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after this flash recovery.
Click to expand...
Click to collapse
I tried it with the vbmeta.img from the fastboot Redmi Note 8 – Global Stable ROM (V11.0.9.0.PCOMIXM | MIUI 11 | Android 9.0) and the platform-tools for linux from xiaomifirmware.com.
sudo fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
< waiting for any device >
On the phone then is "Press any key to shutdown"
After trying again I got:
target didn't report max-download-size
sending 'vbmeta' (4 KB)...
But then nothing happens...
What is wrong?
Blasmuskant said:
I tried it with the vbmeta.img from the fastboot Redmi Note 8 – Global Stable ROM (V11.0.9.0.PCOMIXM | MIUI 11 | Android 9.0) and the platform-tools for linux from xiaomifirmware.com.
sudo fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
< waiting for any device >
On the phone then is "Press any key to shutdown"
After trying again I got:
target didn't report max-download-size
sending 'vbmeta' (4 KB)...
But then nothing happens...
What is wrong?
Click to expand...
Click to collapse
Was your phone connected in fastboot?
the_weird_aquarian said:
Was your phone connected in fastboot?
Click to expand...
Click to collapse
Yes, it has been connected in fastboot mode... I pressed "Power-On" and "Volume-Down" before and on screen it says FASTBOOT...
Blasmuskant said:
Yes, it has been connected in fastboot mode... I pressed "Power-On" and "Volume-Down" before and on screen it says FASTBOOT...
Click to expand...
Click to collapse
Is it working now? Why don't you try flashing the stock firmware again?
Blasmuskant said:
Yes, it has been connected in fastboot mode... I pressed "Power-On" and "Volume-Down" before and on screen it says FASTBOOT...
Click to expand...
Click to collapse
Download the latest platform tools and try again once
It works!
[email protected] said:
Is it working now? Why don't you try flashing the stock firmware again?
Click to expand...
Click to collapse
It worked, I installed the Stock recovery and then TWRP (all with fastboot) and so it was possible for me to install LineageOS!
Thank you very much for your support!

[ROM] AOSP 11.0 - SODP [11.0.0_r38]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What's AOSP?
AOSP is Android as Google publish without any modifications. .
What's working :
Boots
RIL (Calls, SMS, Data)
Fingerprint
Wi-Fi
Bluetooth
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
LED
GPS
ROM Updated : 7th July 2020
Changelog :
Kernel upstreamed to 4.14.232
Imported stock sensors stack as SODP needs to be worked on right now.
Used lineage as base
June 21 Security Patch.
Instructions to install up ROM :
Flash latest available Stock ROM(47.2.A.10.107) and boot into it once.
Reboot to Fastboot and flash this TWRP recovery ( recovery.img)
fastboot flash recovery recovery.img
Download the latest OEM Image from HERE, Extract and Flash it.
fastboot flash oem SW_binaries_for_Xperia_Android_11_4.14_v5b_yoshino.img
Flash the userdata image (Will wipe all the userdata).
fastboot flash userdata userdata.img
Boot into twrp and wipe
system
cache
dalvik cache
DO NOT WIPE DATA from twrp, you will have issues with internal storage.
TWRP is not yet able to decrypt the internal storage, so please use adb sideload to flash the rom.
Advanced > Enable adb sideload
adb sideload ***rom zip file***
Install Magisk/Gapps(Optional).
Reboot
Downloads :
G8142 : https://sourceforge.net/projects/xz...1-20210706-UNOFFICIAL-maple_dsds.zip/download
G8141 : https://sourceforge.net/projects/xz...e-18.1-20210706-UNOFFICIAL-maple.zip/download
Source Code: https://github.com/xperiadev
Questions :
Q) How to flash Gapps?
A) Flash this TWRP in fastboot mode (fastboot flash recovery <path to recovery>.img
Boot to the recovery, This recovery is not yet compatible with encryption so use adb sideload ( Advanced >> Adb sideload).
on your PC open cmd/terminal and type adb sideload <opengapps>.zip
Q) How to flash Magisk?
A) Adb sideload.
I really like your amazing work! I hope that one day you will also bring the pixel experience to android 11
thanks matee for your work
Hal3 support? (does gcam work?)
Thank you a lot Shujat!
P.s. read in "notes"
Flashing user data is not mandatory...do you mean erase them? Otherwise i don't get what this means
Ok, my mistake, reread all and found what i needed
Bymn.38 said:
Hal3 support? (does gcam work?)
Click to expand...
Click to collapse
Camera2api support?
Yes its full, test out which gcam mod works best on maple and share it with us too
Shujath said:
Camera2api support?
Yes its full, test out which gcam mod works best on maple and share it with us too
[/ALINTI]
I did the steps right
but remained black screen (shaking)
Click to expand...
Click to collapse
Can you please write the steps down what all you did?
Shujath said:
Can you please write the steps down what all you did?
Click to expand...
Click to collapse
latest stock software(newflasher)
fastboot flash oem
fastboot flash boot
fastboot flash system(
erasing 'system'...
OKAY [ 0.149s]
sending sparse 'system' (517140 KB)...
OKAY [ 11.929s]
writing 'system'...
OKAY [ 0.004s]
sending sparse 'system' (516144 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 13.004s)
fastboot flash userdata
fastboot flash twrp and adb sideload gapps and magisk
Let's face it people, these phones are pretty much toast. they may very well work with some carriers but they will be getting few and far between. When 5G becomes more prevalent 4G will become almost useless just as 3G became. Web content will be so data heavy 4G won't be able to keep up. So I bid adieu to Sony as I have moved on to a Pixel 5. I mean, that's what we're trying to turn our phones into, right? Carrier and manufacturer bloatware free? It was fun messing with these phones but, just too much hassle in the end. Good luck to all that press on.
Bymn.38 said:
latest stock software(newflasher)
fastboot flash oem
fastboot flash boot
fastboot flash system(
erasing 'system'...
OKAY [ 0.149s]
sending sparse 'system' (517140 KB)...
OKAY [ 11.929s]
writing 'system'...
OKAY [ 0.004s]
sending sparse 'system' (516144 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 13.004s)
fastboot flash userdata
fastboot flash twrp and adb sideload gapps and magisk
Click to expand...
Click to collapse
System image did not get flashed correctly
Re download the file and try again
Shujath said:
System image did not get flashed correctly
Re download the file and try again
Click to expand...
Click to collapse
didn't happen with cmd
I have been successful with flashtool
thanks for the rom
Bymn.38 said:
didn't happen with cmd
I have been successful with flashtool
thanks for the rom
Click to expand...
Click to collapse
so were you able to boot ?
sim kart görmüyor mu?
Bymn.38 said:
sim kart görmüyor mu?
Click to expand...
Click to collapse
Did you boot into stock ROM once?
[QUOTE = "Shujath, gönderi: 84193105, üye: 6427265"]
Stok ROM'a bir kez önyükleme yaptınız mı?
[/ ALINTI]
Evet
bazen okumak
my device G8141 ? not dual
Bymn.38 said:
[QUOTE = "Shujath, gönderi: 84193105, üye: 6427265"]
Stok ROM'a bir kez önyükleme yaptınız mı?
[/ ALINTI]
Evet
bazen okumak
my device G8141 ? not dual
Click to expand...
Click to collapse
Download Single SIM ROM from Here
thanks for ur hard work!love u,bro
Shujath said:
Download Single SIM ROM from
Click to expand...
Click to collapse
better now but
wifi is breaking
writes factory data reset and turns off won't turn on

Categories

Resources