Develop Bugs

Huawei G510 - Solved - Cannot connect to the camera

This document shows how solve problem "cannot connect to the camera" after ROOT Huawei G510-0010 with B165 boot.img.
1 - Requeriments:
- Download Google adb-toolkit - http://www.adbtoolkit.com/
- Download boot.img, better if you use same version of your firmware (mine is B182)
You can find firmware version on Settings -> About Phone
http://www.toplinetec.com.br/pub/other/boot_g510_B182.zip
2 - Connection with PC
- Install ADB drivers for your device on PC.
- On device, disable Settings -> Fast Boot
- Turn off device, wait some seconds, turn on again pushing volume down and start button for 10 seconds and connect to USB.
- Unzip files to C:\, go Windows Prompt (CMD), and follow next commands:
- cd\adb-toolkit\bin\files
- fastboot devices (if return a code in next line, is because your device is connected)
- fastboot flash boot c:\boot.img
- fastboot reboot
The whole process should look something like this in your CMD:
{
"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"
}
References:
http://forum.xda-developers.com/showthread.php?t=1752270
http://forum.xda-developers.com/showthread.php?t=2315932

Issue on Install Boot
Hi, thanks for your post.
i followed all steps, but, when i install the boot.img to my device it returns me this:
sending 'boot': OK
writing 'boot': Failed (remote: command not allowed)
Do you know, by chance, why is it failing?
Thank you very mutch.

re: Issue on Install Boot
MosKRt said:
Hi, thanks for your post.
i followed all steps, but, when i install the boot.img to my device it returns me this:
sending 'boot': OK
writing 'boot': Failed (remote: command not allowed)
Do you know, by chance, why is it failing?
Thank you very mutch.
Click to expand...
Click to collapse
I don't know exactly, but did you ulnlock boot loader before ?
Is a good option to start.
Follow these steps:
1 - See entire model behind phone battery: G510- (0010, 0100 or 0200).
2 - Request unlock code for Huawei
huaweidevice.com/worldwide/servicePolicy.do?method=toApplyUnlock
If you phone is 0010, you'll need to find chinese site for this.
3 - Apply code
huaweidevice.com/worldwide/servicePolicy.do?method=getUnlockStep
PS: put www before links, because I can't post.

Solved
Hi again!
Yes you was right, the problem was that i didnt unlock the boot loader. I found some problems for do that.
The problem was that they don't have the 0010 model listed in their site and, a chinese site for ask it dosen't exists (I've gone crazy looking for it :crying: :crying
I had to send an email directly to Huawei support channel whit the mobile data (IMEI, S/N, model, ...). They answered me in 48h more or less with the unlock code.
And after that all was perfect. :highfive: :highfive:
shalonbr said:
I don't know exactly, but did you ulnlock boot loader before ?
Is a good option to start.
Follow these steps:
1 - See entire model behind phone battery: G510- (0010, 0100 or 0200).
2 - Request unlock code for Huawei
huaweidevice.com/worldwide/servicePolicy.do?method=toApplyUnlock
If you phone is 0010, you'll need to find chinese site for this.
3 - Apply code
huaweidevice.com/worldwide/servicePolicy.do?method=getUnlockStep
PS: put www before links, because I can't post.
Click to expand...
Click to collapse

Link not working ...
cany anyone upload
..

Failed to flash

Hey there,
I want to switch to these htt ps://download .lineageos. org/oneplus2 LOS 14.1 builds as I'm currently using LOS 14.1 by daktak. (Sorry, not allowed to post links right now..)
There haven't been any updates for almost 3 weeks now and I don't think that this will be updated any further.
Well, simply booting into recovery mode and flashing the newest LOS zip doesn't work for me. I guess it's because I'm not wiping my system partition, just data + dalvik cache... I thought I can simply switch/update from an older version of LOS? Do I really need to wipe everything again so I can install the LOS builds I've mentioned above?
Also I don't really understand the difference between signed and unsigned zips. The zip I want to flash is signed. Is this why I get "Failed to flash" as an error message in recovery? Does "signed" mean, I need to root my OP2 again and my current root will be removed?
Current LOS version 14.1-20170213-UNOFFICIAL-oneplus2 by daktak

Yakumichan said:
Hey there,
I want to switch to these htt ps://download .lineageos. org/oneplus2 LOS 14.1 builds as I'm currently using LOS 14.1 by daktak. (Sorry, not allowed to post links right now..)
There haven't been any updates for almost 3 weeks now and I don't think that this will be updated any further.
Well, simply booting into recovery mode and flashing the newest LOS zip doesn't work for me. I guess it's because I'm not wiping my system partition, just data + dalvik cache... I thought I can simply switch/update from an older version of LOS? Do I really need to wipe everything again so I can install the LOS builds I've mentioned above?
Also I don't really understand the difference between signed and unsigned zips. The zip I want to flash is signed. Is this why I get "Failed to flash" as an error message in recovery? Does "signed" mean, I need to root my OP2 again and my current root will be removed?
Current LOS version 14.1-20170213-UNOFFICIAL-oneplus2 by daktak
Click to expand...
Click to collapse
It is all explained here:
http://lineageos.org/Update-and-Build-Prep/

jhedfors said:
It is all explained here:
http://lineageos.org/Update-and-Build-Prep/
Click to expand...
Click to collapse
Thank you for your quick reply! After some issues using adb I could not fix (but I don't need to as I already did this somehow earlier for CM13) I managed to install LOS14.1 HYPE!
Maybe you could help me with my problem?
"No command 'fastboot' found"... But I can find my phone using adb devices.
Screenshot attached...
{
"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"
}

Yakumichan said:
Thank you for your quick reply! After some issues using adb I could not fix (but I don't need to as I already did dis somehow earlier for CM13) I managed to install LOS14.1 HYPE!
Maybe you could help me with my problem?
"No command 'fastboot' found"... But I can find my phone using adb devices.
Screenshot attached...
Click to expand...
Click to collapse
I am not an expert on adb/fastboot, but is the fastboot binary in the directory? It is also a little difficult to interpret the language in your sceenshot.

jhedfors said:
I am not an expert on adb/fastboot, but is the fastboot binary in the directory? It is also a little difficult to interpret the language in your sceenshot.
Click to expand...
Click to collapse
Right, sorry. It's German and it says that the command "fastboot" either has been written wrong or hasn't been found.
And also: Yes, it is:

I think you need to check your drivers
The device should be connected via adb interface driver or android driver
After that you should be able to see ur device

V350AWM30e ATT_US stock & rooted partitions

V350AWM30e.zip (3.7GB)
I pulled the stock unmodified slot partitions from a fully updated AT&T V35.
I modified them with Magisk and TWRP, and disabled Dm-Verity and ForceEncrypt
I flashed them to another V35AWM that had previously been crossflashed with V350ULM 20f.
Now I stock rooted Android 10 working nicely on my main driver.
I can think of several ways to flash the partitions:
• Using ADB in TWRP (what I did)
• Using ADP from a running rooted system
• One by one with QFIL
The archive includes the unmodified partions, the modified partitions, the packages that I used to modify the partions, some notes, and a script that I used to flash them in TWRP.
If I were doing it again from the start, I would not cross flash, because there are differences in the partition tables. Despite what the guides say, I think that the bootloader can be unlocked from Android 9 or 10, using QFIL. I think that this would work: enable bootloader unlock in developer settings,, flash the engineering bootloader with QFIL, wipe laf, unlock with fastboot, flash the modified boot.img with QFIL, boot into recovery, flash the other partitions from there.
These files are for developers only. You can easily brick your phone and I won't help.

Thank you for this!

amazing
let's hope something useful comes to the end user

Thanks so much for putting this together. Should I anticipate any issues doing TWRP ADB sideload coming from a Korean rom?

Hi! Yesterday I tried to download from the link, but the following error popped up on Mac OS. On Windows, the link just doesn't open. In short, it just can't download...
{
"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"
}

smir_ant said:
Hi! Yesterday I tried to download from the link, but the following error popped up on Mac OS. On Windows, the link just doesn't open. In short, it just can't download...
Click to expand...
Click to collapse
I can download it on windows, it's just extremely slow at 0.5 Mb/s

ghylander said:
I can download it on windows, it's just extremely slow at 0.5 Mb/s
Click to expand...
Click to collapse
yeap, from sative safari (without addblock and another addons) i download too, slow, but success,
thanks for reply

jacob019 said:
V350AWM30e.zip (3.7GB)
I pulled the stock unmodified slot partitions from a fully updated AT&T V35.
I modified them with Magisk and TWRP, and disabled Dm-Verity and ForceEncrypt
I flashed them to another V35AWM that had previously been crossflashed with V350ULM 20f.
Now I stock rooted Android 10 working nicely on my main driver.
I can think of several ways to flash the partitions:
• Using ADB in TWRP (what I did)
• Using ADP from a running rooted system
• One by one with QFIL
The archive includes the unmodified partions, the modified partitions, the packages that I used to modify the partions, some notes, and a script that I used to flash them in TWRP.
If I were doing it again from the start, I would not cross flash, because there are differences in the partition tables. Despite what the guides say, I think that the bootloader can be unlocked from Android 9 or 10, using QFIL. I think that this would work: enable bootloader unlock in developer settings,, flash the engineering bootloader with QFIL, wipe laf, unlock with fastboot, flash the modified boot.img with QFIL, boot into recovery, flash the other partitions from there.
These files are for developers only. You can easily brick your phone and I won't help.
Click to expand...
Click to collapse
Could you reporst the download? I just installed windows 11, so maybe that's the issue, but I keep getting "v350awm30e.zip cannot be downloaded securely." and it refuses to even start the download. Any help would be appreciated.

Working fine for me. Try using https instead of http:
https://jacobstoner.com/V350AWM30e.zip

jacob019 said:
Working fine for me. Try using https instead of http:
https://jacobstoner.com/V350AWM30e.zip
Click to expand...
Click to collapse
Thanks for the fast reply here and in a DM. For anyone new to windows 11 like me, if you try to download from any website that doesn't have that S in it (http vs https), it will not let you download. After a quick google, you can still download from places like this by right-clicking on the download and selecting "keep this".
You can also click on the lock icon in the url bar and then going to permissions and selecting the option to download unsecure content from this website.
Cheers.

Hi everyone. Do you know where can I download a stock ATT firmware for lg v35? Mine is network locked and I have the code to unlock it but I have to be on original firmware. Please help me if you can. Thanks

Question Mtkclient bootloader unlock brakes fastboot?

Hi, just i had an experience with the realme 8g bootloader, I unlocked it by using fastboot and installed magisk with some mods, but I didn't like it so i wanna get back stock, so I reinstalled stock and stock recovery back, and also locking the bootloader again but ended with phone boot/recovery omg destroyed so I searched I way to recover the phone, I found out that I can use mtkclient to do that, using broom mode and unlocking the bootloader but came with consequences. They will be dm-verify on boot that's meaning that will have to press the power button in 5 seconds, and can't boot to custom recovery.
If someone has any idea? Please reply!

Did you Exit deep testing of realme

Julian_10 said:
Hi, just i had an experience with the realme 8g bootloader, I unlocked it by using fastboot and installed magisk with some mods, but I didn't like it so i wanna get back stock, so I reinstalled stock and stock recovery back, and also locking the bootloader again but ended with phone boot/recovery omg destroyed so I searched I way to recover the phone, I found out that I can use mtkclient to do that, using broom mode and unlocking the bootloader but came with consequences. They will be dm-verify on boot that's meaning that will have to press the power button in 5 seconds, and can't boot to custom recovery.
If someone has any idea? Please reply!
Click to expand...
Click to collapse
Did you get your phone fixed? If so, how?
Please reply soon as I did something wrong after unlocking bootloader on my realme 8 5G too and now I need to flash stock ROM. I got it to BROM mode (using that payload trick), but still got errors like STATUS_BROM_CMD_STARTCMD_FAIL in SPFT.

LegendProBeast said:
Did you get your phone fixed? If so, how?
Please reply soon as I did something wrong after unlocking bootloader on my realme 8 5G too and now I need to flash stock ROM. I got it to BROM mode (using that payload trick), but still got errors like STATUS_BROM_CMD_STARTCMD_FAIL in SPFT.
Click to expand...
Click to collapse
I got it fixed, also running android 12, it was challenging with broom mode but in the end I fixed it. The most errors I got when using broom mode was that payload things, or SP flash version didn't supported my processor.
Try to follow this guide.
https://forum.xda-developers.com/t/guide-unbrick-realme-8-unbrick-upgrade-downgrade-rmx3085.4392095/

Julian_10 said:
I got it fixed, also running android 12, it was challenging with broom mode but in the end I fixed it. The most errors I got when using broom mode was that payload things, or SP flash version didn't supported my processor.
Try to follow this guide.
https://forum.xda-developers.com/t/guide-unbrick-realme-8-unbrick-upgrade-downgrade-rmx3085.4392095/
Click to expand...
Click to collapse
Bro can you say how you bypassed the brom? I couldn't do it using the method they used in the guide...

DeviceMesser said:
Bro can you say how you bypassed the brom? I couldn't do it using the method they used in the guide...
Click to expand...
Click to collapse
What errors do you get?

Julian_10 said:
What errors do you get?
Click to expand...
Click to collapse
All other tools except MTK Auth Bypass 6.0.0.1 aren't working, and even this just bypasses my phone and then SP Foash shows error STATUS_BROM_CMD_STARTCMD FAIL....

DeviceMesser said:
All other tools except MTK Auth Bypass 6.0.0.1 aren't working, and even this just bypasses my phone and then SP Foash shows error STATUS_BROM_CMD_STARTCMD FAIL....
Click to expand...
Click to collapse
You have any social media like discord, maybe I can help you more directly, and get more feedback from you

Julian_10 said:
You have any social media like discord, maybe I can help you more directly, and get more feedback from you
Click to expand...
Click to collapse
I do have discord.
{
"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"
}
Julian_10 said:
You have any social media like discord, maybe I can help you more directly, and get more feedback from you
Click to expand...
Click to collapse
Bro please help, I have shared my Discord ID

Question Custom ROM install fails

After custom ROM installation fails, I can re-install the stock ROM to try again.
i.e. lisa_eea_global_images_V12.5.8.0.RKOEUXM_20211209.0000.00_11.0_eea_607b867ac2.tgz
I can install SHRP (HimanshuRaj's version) and Magisk v24.3.
I can switch between Fastboot, Recovery and Android.
Both SHRP and Magisk Manager both show that Magisk 24.3 is intalled.
After I install a ROM, only fastboot works. Whether issuing the reboot command via the attached PC or by pressing the relevant phone buttons, only fastboot works.
The process I am using to install the custom ROM is:
On the phone:
Reboot into SHRP recovery
Wipe => Format Data => yes
Click blue tick
Advanced => Sideload => click tick button
Displays:
ADB Sideload
Starting ADB sideload feature
On the PC:
adb sideload c:\users\miui\downloads\Android\evolution_lisa-ota-sp2a.220405.004-05021724-unsigned.zip
serving: 'c:\users\miui\downloads\Android\evolution_lisa-ota-sp2a.220405.004-05021724-unsigned.zip' (~47%) adb: failed to read command: No error
...or...
adb sideload c:\users\miui\downloads\Android\Arrow-v11.0-lisa-OFFICIAL-20211219-GAPPS.zip
serving: 'c:\users\miui\downloads\Android\Arrow-v11.0-lisa-OFFICIAL-20211219-GAPPS.zip' (~47%) adb: failed to read command: No error
What am I doing wrong?

When flashing SHRP, there is an error:
mount -w /system_root process ended wih ERROR: 1
Is that normal? Does it matter?
{
"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"
}

When wiping, there is the same error. This time it says 'Failed' at the top.

The sideload says is is successful, but lots of error messages.
I've been going round in circles for days. Any suggestions gratefully received.

Gigajules said:
After custom ROM installation fails, I can re-install the stock ROM to try again.
i.e. lisa_eea_global_images_V12.5.8.0.RKOEUXM_20211209.0000.00_11.0_eea_607b867ac2.tgz
Click to expand...
Click to collapse
Have you tried unrooting before?
Using TWRP: https://androidfilehost.com/?w=files&flid=324804

NOSS8 said:
Have you tried unrooting before?
Using TWRP: https://androidfilehost.com/?w=files&flid=324804
Click to expand...
Click to collapse
No I haven't. Is re-instaling the stock rom the same as unrooting?

Gigajules said:
No I haven't. Is re-instaling the stock rom the same as unrooting?
Click to expand...
Click to collapse
sometimes root is a problem, it is better to unroot then install the stock rom corresponding to the firmware of the aosp rom you want to install.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/

NOSS8 said:
sometimes root is a problem, it is better to unroot then install the stock rom
Click to expand...
Click to collapse
OK, I will give that a try.
NOSS8 said:
then install the stock rom corresponding to the firmware of the aosp rom you want to install.
Click to expand...
Click to collapse
OK, so that would be the stock ROM V12.5.8.0 I mentioned in the OP, corresponding to the Arrow/Evolution I also mentioned in the OP, right?
Is there a list of which stock + custom ROMs work together?

Gigajules said:
OK, I will give that a try.
OK, so that would be the stock ROM V12.5.8.0 I mentioned in the OP, corresponding to the Arrow/Evolution I also mentioned in the OP, right?
Is there a list of which stock + custom ROMs work together?
Click to expand...
Click to collapse
right.
All roms do not necessarily use the same firmware.
try Xiaomi eu rom like stock but better with more options and easy to flash,play store certified without root/original camera:
https://xiaomi.eu/community/threads/22-5-18.65921/
https://xiaomi.eu/community/threads/22-5-18.65921/

better to flash xiaomi.eu rom first. easy to install 1 click while phone is on fastboot, then use different recovery. try pixelos recovery.