So, you just got your new Redmi Note 10S and the software sucks. So you decided to flash a GSI, got it working and you still have one problem left, the video look oversharped and the colors might look weird. Well, this vendor will fix it.
{
"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"
}
So what's new in this vendor?
A little bit debloated
And ofcourse, no oversharpening.
Anything else?
Nothing else, literally just that.
Download Link:
Google Drive
Requirements:
1. Unlocked bootloader.
2. A PC with fastboot tools.
3. Reading ability.
Flashing Process:
1. Reboot your phone into bootloader.
2. Check if fastboot detects your device.
3. Type fastboot reboot fastboot to reboot into fastbootd.
4. After that, type fastboot flash vendor path/to/vendor.img
5. That's it. Reboot and enjoy!
KEEP IN MIND
This vendor only has been tested on DotOS 5.1.3. If you possibly can, please try this on MIUI, and if it doesn't boot, report it to me. Thanks.
Now try watching video at 360p, and you might see a difference.
It failed:
target reported max download size of 134217728 bytes
Invalid sparse file format at header magic
sending sparse 'vendor' 1/8 (130795 KB)...
OKAY [ 2.928s]
writing 'vendor' 1/8...
FAILED (remote: This partition doesn't exist)
finished. total time: 2.933s
Any idea what happened?
It actually works with MIUI as well. However, color management seems to be disabled leaving the phone to oversaturate the colors at will.
EDIT 1: It's not just the color management that gets disabled. Changing the color temperature gets disabled, reading mode gets disabled as well. It seems like trying to solve one problem causes more.
EDIT 2: It could be solved by tweaking ro.vendor.mtk_pq_color mode. With this vendor, it's set to 1 which may be the reason why the phone is stuck in the "Saturated" mode.
EL66K said:
It failed:
target reported max download size of 134217728 bytes
Invalid sparse file format at header magic
sending sparse 'vendor' 1/8 (130795 KB)...
OKAY [ 2.928s]
writing 'vendor' 1/8...
FAILED (remote: This partition doesn't exist)
finished. total time: 2.933s
Any idea what happened?
Click to expand...
Click to collapse
you must flash it on fastbootd , using fastboot reboot fastboot or adb reboot fastboot. try to flast it again on every partition (a and b)
jacobpayag said:
It could be solved by tweaking ro.vendor.mtk_pq_color mode
Click to expand...
Click to collapse
How can i change this value? If i try edit build.prop on /vendor folder, this file erased and phone not boot again. Any try for restoring file from adb failed...
hey guys, this project is EOL. Please use my LiteE RN10S ROM instead, the ROM has no oversharpening while maintaining every display color related stuff.
J6idot said:
hey guys, this project is EOL. Please use my LiteE RN10S ROM instead, the ROM has no oversharpening while maintaining every display color related stuff.
Click to expand...
Click to collapse
Hey bro can you please provide device vendor (not .img)
Related
{
"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"
}
1. Download this zip file and extract it.
2. Hold Shift and then Right click inside the extracted folder and then click on
"Open Command Window here"
3. Connect your device to PC (Make sure that usb debugging is enabled).
4. In command window type
"adb reboot bootloader" //This will boot your phone into fastboot mode.
5. Then type
"fastboot boot twrp.img" //This will boot the device into TWRP recovery temporarily.
6. In recovery click mount -> check system.
7. Now type
"adb pull /system/build.prop" //This will copy the build.prop in the fastboot folder.
8. Open the build.prop using notepad++ (simple notepad may corrupt the file)
9. Find "ro.build.type=user" and change it to " ro.build.type=userdebug"
Then save it.
10. Now type
"adb push build.prop /system/" //this will push the edited build.prop.
11. Now type
"adb shell"(press enter)
"cd system"(press enter)
"chmod 644 build.prop"(press enter)
"exit" (press enter)
12. Type "adb reboot" //to reboot your device
13. Now go in Developer options in setting and enable Multi-window mode
14. enjoy:laugh:
HIT THANKS IS YOU LIKE THIS GUIDE
Error: Device offline
It shows me this error. What should I do?
error: device offline
check adb driver in device manager windows,up date
[email protected] said:
It shows me this error. What should I do?
error: device offline
Click to expand...
Click to collapse
Help!!!!!
bro i have extreated the fastboot file i didnt see the build prop file..................................so what can i do now................please help
Do I need an unlocked bootloader for this?
C:\Users\Elias\Desktop\Fastboot\Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.312s]
booting...
FAILED (remote failure)
finished. total time: 0.315s
C:\Users\Elias\Desktop\Fastboot\Fastboot>
Nera2600 said:
Do I need an unlocked bootloader for this?
C:\Users\Elias\Desktop\Fastboot\Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.312s]
booting...
FAILED (remote failure)
finished. total time: 0.315s
C:\Users\Elias\Desktop\Fastboot\Fastboot>
Click to expand...
Click to collapse
failed for me too
ArvinLam said:
failed for me too
Click to expand...
Click to collapse
9. Find "ro.build.type=user" and change it to " ro.build.type=userdebug"
Then save it.
Change these lines in system build.prop then reboot goto developer options nd enable it
dsbhai said:
9. Find "ro.build.type=user" and change it to " ro.build.type=userdebug"
Then save it.
Change these lines in system build.prop then reboot goto developer options nd enable it
Click to expand...
Click to collapse
thanks
me too..
you find any solution?
question
working fine in android one thanks....Does it work only on android one or any rooted phone?
error
device not found!!!
fail
C:\Users\William\Desktop\Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.277s]
booting...
FAILED (remote failure)
finished. total time: 0.294s
what to do?
Device ASUS ZENFONE 4_T00I
Last working firmware was Jellybean 4.2.2 (never upgraded)
Problem started: Consistent FC msgs of almost all msgs.
1. Droidboot State
Droidboot Version: 6.6.3.0
Product : WW_ZENFON
Not Rooted. No Custom Recovery
Bootloader : Could never unlock. Tried the app but never success.
2. Device Status: Was on Stock Jelly bean and was contineously giving com.android.phone failure and other FC closure consistently , hence needed to try flasing a new rom or same version.
3. Read the forums and collected following data:
Stock Firmwares:
UL-ASUS_T00I-WW-6.6.3.0_user.zip
UL-ASUS_T00I-WW-7.4.4.0-user.zip
UL-ASUS_T00I-WW-9.9.9.0-user
Raw Firmware:
Zenfone4V4.3.10.raw
4. All the Tools required to flash the firmwares and study of methods to do so. I used WIN-XP and tools installed on the same. All Drivers installed successfully device recognizing and able to use fastboot and adb.
5.Current device status: To flash UL-ASUS_T00I-WW-6.6.3.0_user.zip
I tried following methods :
FW placed on SD Flashing started but failed everytime
Tried Fastboot flash update FW.zip method by cleaning all partitions- Failed "Problem in creating otp update file-error)
Now left with no system, no userdata or no data partitions on device.
Now trying AFT method to flash .raw firmware which I have downloaded.
AFT not at all listing up my device in Droidbot mode.
Final Status: No System on / No firmware on device at all. Can use Droidboot thats all.
Now please help me to give life to the device...
Thank you in advance.
C:\Zenfone>fastboot flash boot boot.img
sending 'boot' (8661 KB)...
OKAY [ 1.375s]
writing 'boot'...
OKAY [ 1.859s]
finished. total time: 3.234s
C:\Zenfone>fastboot flash fastboot droidboot.img
sending 'fastboot' (11253 KB)...
OKAY [ 1.578s]
writing 'fastboot'...
OKAY [ 2.156s]
finished. total time: 3.734s
C:\Zenfone>fastboot flash update UL-ASUS_T00I-WW-9.9.9.0-user.zip
sending 'update' (825100 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.016s
==================================================
C:\Zenfone>fastboot flash update UL-ASUS_T00I-WW-7.4.4.0-user.zip
sending 'update' (837024 KB)...
OKAY [ 37.469s]
writing 'update'...
FAILED (remote: problem with creating ota update file!)
finished. total time: 37.578s
==================================================
AFT not detecting device and showing this error everytime I connect or disconnect device (in droidboot mode)
{
"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"
}
Maybe you can search this files on google :
1. 6.5.35 system.img.gz file
2. 6.5.35 boot.img file
3. 6.5.35 fastboot img file
Should be the same version, then flash it..
Ok, I will try that.
Although I wanted to know whats d fault and where did I go wrong on procedures? I could not unlock bootloader so will fastboot allow me to flash the mentioned firmware images?
Why AFT dint worked for me and. Lot of questions around.. I AINT NOOB FOR ANDROID but. Dis device does not hv anything similar to axnormal android.
Sorry for behaving noob.
Thnkyou for help
Help me please
the AFT i installed on my pc doesnt detect the raw file i have
i've spend two weeks to solve this still no luck
please give me some advice how do i fixed my zenfone 4 its stuck on ASUS LOGO
Fix it already but got a new problem
Flash image failure(FAILED (remote: ERROR: Image-SKU: 'TW_Zenfone' Device-SKU: 'WW_Zenfone'))
u guys can use this method
http://forum.xda-developers.com/zenfone-4/general/guide-how-to-flash-stock-rom-relock-t3302917
Hi all,
I am sorry for my english.
I have a problem with flashing firmware using ADB. Despite the command fasboot flash passes without errors flashing recovery img even system.img, but my phone just moves into fastboot. Even when using a combination of volume- + power booted only on the home screen, then restart again jumps into fastboot. At the command fastboot erase system or erase recovery appear remote: Command not allowed.
I can not figure out. Does anyone know where is the mistake?
Hey,
is your bootloader unlocked? Sounds like he isn't.
Yes, the bootloader should be unlocked.
{
"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"
}
Hm, could you describe a little more detailed what you did so far, which roms you were on and which one you tried to flash?
Maybe you'll get into the recovery through typing 'fastboot reboot' while holding volume-.
l3Nni said:
Hm, could you describe a little more detailed what you did so far, which roms you were on and which one you tried to flash?
Maybe you'll get into the recovery through typing 'fastboot reboot' while holding volume-.
Click to expand...
Click to collapse
I have created from the stock firmware P7-L10C900B852_eu_channel_SW using HuaweiUpdateExtractor update.zip and install it in the TWRP. Before that, the phone has been installed MyROM v3.3.
I tried your advice command fastboot reboot simultaneously pressing volume-, but the phone again ran into fastboot.
Okay. MyRom is based on a B6xx rom, so extract and flash the recovery.img and boot.img of a B6xx rom.
Hopefully you can now access the recovery. If so first flash a full B6xx rom through dload, then update to B852.
If not extract system.img/cust.img/userdata.img/boot.img/recovery.img of any B6xx rom and flash them in this order. If you can boot only into the recovery, flash a full B6xx rom per dload, if you can boot into the system you could directly go for a B852 update.
l3Nni said:
Okay. MyRom is based on a B6xx rom, so extract and flash the recovery.img and boot.img of a B6xx rom.
Hopefully you can now access the recovery. If so first flash a full B6xx rom through dload, then update to B852.
If not extract system.img/cust.img/userdata.img/boot.img/recovery.img of any B6xx rom and flash them in this order. If you can boot only into the recovery, flash a full B6xx rom per dload, if you can boot into the system you could directly go for a B852 update.
Click to expand...
Click to collapse
I have followed your instructions, but the phone always starts only in fastboot.
Flash ROM B609:
Code:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Všechna práva vyhrazena.
d:\Pracovni\huawei\dload_B609>fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (523522 KB)...
OKAY [ 20.884s]
writing 'system'...
OKAY [ 12.399s]
sending sparse 'system' (523531 KB)...
OKAY [ 21.488s]
writing 'system'...
OKAY [ 11.971s]
sending sparse 'system' (454037 KB)...
OKAY [ 18.280s]
writing 'system'...
OKAY [ 10.371s]
finished. total time: 95.393s
d:\Pracovni\huawei\dload_B609>fastboot flash cust cust.img
target reported max download size of 536870912 bytes
sending 'cust' (400995 KB)...
OKAY [ 15.427s]
writing 'cust'...
OKAY [ 9.175s]
finished. total time: 24.601s
d:\Pracovni\huawei\dload_B609>fastboot flash userdata userdata.img
target reported max download size of 536870912 bytes
sending 'userdata' (132497 KB)...
OKAY [ 5.110s]
writing 'userdata'...
OKAY [ 3.156s]
finished. total time: 8.267s
d:\Pracovni\huawei\dload_B609>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8072 KB)...
OKAY [ 0.314s]
writing 'boot'...
OKAY [ 0.457s]
finished. total time: 0.770s
d:\Pracovni\huawei\dload_B609>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10078 KB)...
OKAY [ 0.391s]
writing 'recovery'...
OKAY [ 0.547s]
finished. total time: 0.938s
d:\Pracovni\huawei\dload_B609>
That's pretty bad news. There's very little to no hope to recover your phone now. For the B852.zip you flashed per twrp, you've probably chosen the partition table of any other device (since the p7 isn't listed) and hardbricked your phone when flashing it.
There are a couple of persons who did this, and as far as I know, noone was able for recover, unfortunately.
The last possibility I know would be to buy e.g. a defect p7 and change the Motherboard.
l3Nni said:
That's pretty bad news. There's very little to no hope to recover your phone now. For the B852.zip you flashed per twrp, you've probably chosen the partition table of any other device (since the p7 isn't listed) and hardbricked your phone when flashing it.
Click to expand...
Click to collapse
I chose the partition table Ascend P6.
[REDACTED FOR PRIVACY REASONS]
[REDACTED FOR PRIVACY REASONS]
Get unlock key from official Motorola site. You will have to enter it to unlock. Obviously it will void warranty
[REDACTED FOR PRIVACY REASONS]
Same here.
Shows some error
{
"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"
}
[REDACTED FOR PRIVACY REASONS]
ava2048 said:
You found a solution buddy?
Let me know when you find something.
Click to expand...
Click to collapse
No.
Tried to unlock many times. No output other than error.
Code:
C:\adb>fastboot oem get_unlock_data
(bootloader) slot-counttas: not found
(bootloader) slot-suffixe: not found
(bootloader) slot-suffi: not found
...
FAILED (remote: unknown command)
finished. total time: 0.001s/CODE]
I have asked in telegram group.
jamespauljose said:
No.
Tried to unlock many times. No output other than error.
Code:
C:\adb>fastboot oem get_unlock_data
(bootloader) slot-counttas: not found
(bootloader) slot-suffixe: not found
(bootloader) slot-suffi: not found
...
FAILED (remote: unknown command)
finished. total time: 0.001s/CODE]
I have asked in telegram group.[/QUOTE]
i am waiting for the answer of same question. please experts give answer.
Click to expand...
Click to collapse
Same problem here
drvikasjoshi said:
Get unlock key from official Motorola site. You will have to enter it to unlock. Obviously it will void warranty
Click to expand...
Click to collapse
I have the same problem here, the "fastboot oem get_unlock_data" command just hangs. I've tried leaving it for a few minutes, but it still doesn't work. Which is especially strange, considering X number of Youtubers/other users get the key in mere seconds! And yes, my model number matches, settings are correct, etc.
You can just use the computer of Windows XP system inside
Sorry,my English is not standard,but you must be understand
caocanhong said:
You can just use the computer of Windows XP system inside
Sorry,my English is not standard,but you must be understand
Click to expand...
Click to collapse
Windows XP won't support modern USB systems. It won't even run ADB, forget about unlocking anything.
{
"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"
}
Supported devices :
sofia
sofiap
sofiap_ao
sofiar
rav
rav_t
Download (GApps included)
Kernel source
Device tree source
MAJOR BUGS:
No data with carriers using Verizon network
you tell me
FLASHING
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot -w (mandatory if coming from stock, warning tho : it will erase all your data)
UPDATE
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
Telegram support group : https://t.me/MotoG8Power
20200821 Changelog :
- Add support for g8/g fast
- Add LED support
- Add selinux enforced for all
- Safetynet should pass for all devices (can't check my self, let me know)
- Fix crash when turning off wifi hotspot
XDA:DevDB Information
OmniROM, ROM for the Moto G Power
Contributors
vache, Dark98
Source Code: https://github.com/omnirom/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Beta Release Date: 2020-08-02
Created 2020-08-02
Last Updated 2020-08-28
I wish I had the G8 power since there is a custom rom.
You may want to move this thread to a dedicated Moto G 8 Power Thread.
One may think this rom is for the Moto G Power.
jhjhjhjhjhjh said:
I wish I had the G8 power since there is a custom rom.
You may want to move this thread to a dedicated Moto G 8 Power Thread.
One may think this rom is for the Moto G Power.
Click to expand...
Click to collapse
I wish such forum exists.
That's why i put that big red warning text.
But making a commonized build shouldn't be hard, if you're ready to test, let me know.
Work on Moto g8 power 2041-1?
wanderleiAlfa said:
Work on Moto g8 power 2041-1?
Click to expand...
Click to collapse
Yes, XT2041-1 and XT2041-3 (sofiar).
Any way to get this without G apps? Trying to degoogle my life.
Is this just the stock rom?
BMO0071 said:
Is this just the stock rom?
Click to expand...
Click to collapse
No, this is OmniROM.
Juno_ said:
Any way to get this without G apps? Trying to degoogle my life.
Click to expand...
Click to collapse
Should be doable for the next build.
Weird. I flashed it and I was still on stock ?
Is OmniSwitch included in this ROM?
Thanks for your work.
Ulfys said:
Is OmniSwitch included in this ROM?
Thanks for your work.
Click to expand...
Click to collapse
Yes.
vache said:
I wish such forum exists.
That's why i put that big red warning text.
But making a commonized build shouldn't be hard, if you're ready to test, let me know.
Click to expand...
Click to collapse
Yes .
Thanks ..
Whenever you upload a build for the Moto g power I'll test it...
@vache
Just tried this on the g power and it bootloops.
Couldn't get a log.
Would be great if a unified build for sofia/sofiar could be achieved
I tried flashing this on my Sofiar (g8), I can flash boot.img and dtbo.img but when I try to flash system.img I get the following error:
sending sparse 'system' (786384 KB)...
OKAY [ 18.328s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 18.343s
I looked it up and this message on Motorola devices usually means that either the bootloader is locked or the .img attempted to flash is older than the one already installed.
My bootloader is unlocked and the last OTA (system) update I applied was on May, so I'm not sure what's going on.
I tried "fastboot erase system" and I get:
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
Ulfys said:
I tried flashing this on my Sofiar (g8), I can flash boot.img and dtbo.img but when I try to flash system.img I get the following error:
sending sparse 'system' (786384 KB)...
OKAY [ 18.328s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 18.343s
I looked it up and this message on Motorola devices usually means that either the bootloader is locked or the .img attempted to flash is older than the one already installed.
My bootloader is unlocked and the last OTA (system) update I applied was on May, so I'm not sure what's going on.
I tried "fastboot erase system" and I get:
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
Click to expand...
Click to collapse
Are you sure you rebooted in fastbootd mode and not fastboot ?
Also you may have to download the file again, previous link was pointing to a build for a different device. Sorry for that. (make sure it's omni-10-20200802-sofiar-IMG.zip)
Q9Nap said:
@vache
Just tried this on the g power and it bootloops.
Couldn't get a log.
Would be great if a unified build for sofia/sofiar could be achieved
Click to expand...
Click to collapse
Unified test build for sofia/sofiar/sofiap/rav : omni-10-20200806-sofia-rav-IMG.zip
vache said:
Are you sure you rebooted in fastbootd mode and not fastboot ?
Also you may have to download the file again, previous link was pointing to a build for a different device. Sorry for that. (make sure it's omni-10-20200802-sofiar-IMG.zip)
Click to expand...
Click to collapse
Hey, you were right. I couldn't boot to fastbootd after installing TWRP, so I was on fastboot mode instead.
I used the Rescue and Smart Assistant and with everything back to stock, including the recovery, I can boot to fastbootd.
However, when I try to flash boot, I get:
sending 'boot' (65536 KB)...
OKAY [ 1.437s]
writing 'boot'...
FAILED (remote: No such file or directory)
finished. total time: 1.437s
It can send "boot" but not write it.
Reflashed today on my g8 power and got a boot loop halp
Edit: flashed unified test build and the rom booted sucessfully
vache said:
Unified test build for sofia/sofiar/sofiap/rav : omni-10-20200806-sofia-rav-IMG.zip
Click to expand...
Click to collapse
Just tried this and it boots, but touchscreen doesn't work.
Popup to enable adb appears on boot, but cannot enable, and so cannot get a log, unfortunately.
Progress though!
Ulfys said:
Hey, you were right. I couldn't boot to fastbootd after installing TWRP, so I was on fastboot mode instead.
I used the Rescue and Smart Assistant and with everything back to stock, including the recovery, I can boot to fastbootd.
However, when I try to flash boot, I get:
sending 'boot' (65536 KB)...
OKAY [ 1.437s]
writing 'boot'...
FAILED (remote: No such file or directory)
finished. total time: 1.437s
It can send "boot" but not write it.
Click to expand...
Click to collapse
Something wrong on your side, make sure you're using the last fastboot version.
Q9Nap said:
Just tried this and it boots, but touchscreen doesn't work.
Popup to enable adb appears on boot, but cannot enable, and so cannot get a log, unfortunately.
Progress though!
Click to expand...
Click to collapse
https://drive.google.com/file/d/19oiGM7yRzbxOsZXd4vYKDpbTW8ajNOU5/view?usp=sharing
By using the product.img you will have adb working.
I would need kernel logs : adb shell dmesg > dmesg.txt