Related
Hey guys,
Can someone post a step by step "for dummies" guide to flashing the stock unbranded firmware to over right the UK Tesco firmware?
I've already downloaded the unbranded UK RETAIL firmware and unlocked my phone to use in other networks, that's as far as I've got.
Not looking to root or anything else, just to apply the stock unbranded firmware so that I can get future updates from Motorola and not Tesco.
Thanks.
You need to unlock the bootloader, then either use RSD Lite or fastboot flash the images in the archive.
Give that, from the FAQ, the 'adb' access seems to work with the Moto G would the 'adb sideload' method not work? I assume this would avoid the need to unlock the bootloader.
Rusty! said:
You need to unlock the bootloader, then either use RSD Lite or fastboot flash the images in the archive.
Click to expand...
Click to collapse
Any chance for a step by step? And is this a confirmed working method?
Ydnaroo said:
Give that, from the FAQ, the 'adb' access seems to work with the Moto G would the 'adb sideload' method not work? I assume this would avoid the need to unlock the bootloader.
Click to expand...
Click to collapse
No. Sideload is for OTA updates. Completely different scenario.
Rusty! said:
No. Sideload is for OTA updates. Completely different scenario.
Click to expand...
Click to collapse
Ah! Of course. Brain fade here.
failed system.img when flashing unbranded stock
I have attempted to flash the stock unbranded firmware but am having no succes
The fastboot instructions given by Motorola website are as follows:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
Click to expand...
Click to collapse
Although I'm guessing that may be for the motox as the .xml included in the MotoG zip is as follows:
<?xml version="1.0"?>
-<flashing>-<header><phone_model model="QC8x26_CFC"/><software_version version="falcon_retgb-user 4.3 14.10.0Q3.X-76-LGG-8 54 release-keysMSM8626BP_1032.3051.51.00R"/><sparsing max-sparse-size="268435456" enabled="true"/>-<interfaces><interface name="AP"/></interfaces></header>-<steps interface="AP"><step MD5="173f47c2b411e291f8b0f512b8935190" filename="gpt.bin" partition="partition" operation="flash"/><step MD5="a2a1c181283543186f7ef069a9f63374" filename="motoboot.img" partition="motoboot" operation="flash"/><step MD5="187908e994f5b42710d13dbb5126d6d2" filename="logo.bin" partition="logo" operation="flash"/><step MD5="c99ebf47655a7609f10a8673ea229b72" filename="boot.img" partition="boot" operation="flash"/><step MD5="f79ca6436a8214fc7728dd927bd16898" filename="recovery.img" partition="recovery" operation="flash"/><step MD5="28ed691836a16e09be1edb7736086a49" filename="system.img_sparsechunk.0" partition="system" operation="flash"/><step MD5="9a188eb562f2abf336b66d1db53ab1f1" filename="system.img_sparsechunk.1" partition="system" operation="flash"/><step MD5="6a6ca5174610c48a855a7d16be75f948" filename="system.img_sparsechunk.2" partition="system" operation="flash"/><step MD5="b298426137783b6163fcda3621bed159" filename="NON-HLOS.bin" partition="modem" operation="flash"/><step partition="modemst1" operation="erase"/><step partition="modemst2" operation="erase"/><step MD5="73941708b28eb41f54b7c2326feec38a" filename="fsg.mbn" partition="fsg" operation="flash"/><step partition="cache" operation="erase"/><step partition="userdata" operation="erase"/></steps></flashing>
Click to expand...
Click to collapse
This seems to work via fastboot untill I get to the system.img files, they all fail when I try to flash them in order, or if I just try to flash one system.img as a whole.
I have also tried using the RSD tool, the phone is recognised when plugged in & booted up normally, after you select the .xml & click start it reboots to fastboot then can no longer see the device so the flash fails.
Unable to get the tool to see the phone if I manually reboot to fastboot first.
Any Ideas? Im guessing that manually flashing via fastboot is the only way, but cant get that 3 part system.img to install
>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.047s
Click to expand...
Click to collapse
Have you gone through the bootloader unlock process?
Rusty! said:
Have you gone through the bootloader unlock process?
Click to expand...
Click to collapse
Yes by following the steps on the Motorola website.
I have that annoying white warning screen now every time I reboot
How about adb sideload? Shouldnt it work just like on nexus devices? Just guessing, dont own the phone... Yet
Sent from my LG-P760 using xda app-developers app
N00BY0815 said:
How about adb sideload? Shouldnt it work just like on nexus devices? Just guessing, dont own the phone... Yet
Sent from my LG-P760 using xda app-developers app
Click to expand...
Click to collapse
Coming from a nexus, I thought that also, but I'm sure on another thread it is mentioned that ADB sideload only applies to OTA update files.
I tried pushing the whole zip to the phone but as expected it did nothing.
Fastboot flash should work but the bootloader won't give permission so something isn't right.
Although on the instructions from motorola website it says not to use android fastboot, but use RSD tool instead. I have 2 potential issus with that #1 the software itself hasn't been updated to support the MotoG or #2 it wont work with my 64bit copy of windows 7.
You need too bit the phone into BP Tools mode from fastboot for RSD Lite if you haven't been
Rusty! said:
You need too bit the phone into BP Tools mode from fastboot for RSD Lite if you haven't been
Click to expand...
Click to collapse
Yep, tried that the 1st time you posted it, still no luck.
I have noticed that after every reboot the usb debugging has switched itself off, could this be causing the permission problem?
Paul over at Modaco has created a root tool (says so on his twitter).
not sure if that will be any help in applying a stock Retrail rom on the Tesco phones. he also says RSD should work?
hope you guys can figure it out .
TeamKilo said:
Hey guys,
Can someone post a step by step "for dummies" guide to flashing the stock unbranded firmware to over right the UK Tesco firmware?
I've already downloaded the unbranded UK RETAIL firmware and unlocked my phone to use in other networks, that's as far as I've got.
Not looking to root or anything else, just to apply the stock unbranded firmware so that I can get future updates from Motorola and not Tesco.
Thanks.
Click to expand...
Click to collapse
Where did you download it from?
he's in the process of uploading it. called Superboot?
The Jones said:
Where did you download it from?
Click to expand...
Click to collapse
Moto G aka Falcon aka Motorola G (XT1032, XT1033) firmwares
http://sbf.droid-developers.org/falcon/list.php
---------- Post added at 04:20 PM ---------- Previous post was at 03:35 PM ----------
seapoint said:
Moto G aka Falcon aka Motorola G (XT1032, XT1033) firmwares
http://sbf.droid-developers.org/falcon/list.php
Click to expand...
Click to collapse
Code:
Motorola G (XT1032, XT1033)
Back
Size MD5 Carrier File
382.6 MiB 2E5FADFE1F8DE917AF0ABE6B9610AEC1 O2 Germany O2-DE_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.xml.zip
398.7 MiB 18394D6F7268A9D489CFCFAE3B63E803 O2 Great Britain O2SL-GB_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.xml.zip
382.6 MiB BD4BA4AE781BDB3DE20FD53D185E8C2C Retail Germany RETAIL-DE_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.xml.zip
394.1 MiB DA99BD447878CDF35E7D2929E8E2A61E Retail French RETAIL-FR_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.xml.zip
397.9 MiB 2D45BDDDA22C46EF4C4023B78F9EE172 Retail British RETAIL-GB_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF_svc.xml.zip
398.7 MiB 1B5988BD4CDB676E217F87891AB4667F Tesco Great Britain TESCOSL-GB_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.xml.zip
382.6 MiB 12B83CD9B0F945C9D25881843AC50AC8 SFR France VODAFONE-DE_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.xml.zip
396.7 MiB F69CE3807C2FEE310987F83144E8CABC SFR France VODAFONESL-FR_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF_v2.xml.zip
409.2 MiB 9E782FA758557C526599F723E5A33F69 Claro Brazil fastboot_falcon_amxbr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_43_release-keys-cid12-AmericaMovil_BR.tar.gz
409.1 MiB 3768338F742347A22DF8568B4B927449 Claro Brazil fastboot_falcon_amxbr_user_4.3_14.10.0Q3.X-76-LCG-8_53_release-keys-cid12-AmericaMovil_BR.tar.gz
403.4 MiB 1B4D1C455C16D2526D08D117B15C3EA6 Telcel Mexico fastboot_falcon_amxmx_user_4.3_14.10.0Q3.X-76-LCG-8-1_1_release-keys-cid12-AmericaMovil_MX.tar.gz
409.2 MiB AB46415C9D344B45F7954ADD834BC215 OI Brazil fastboot_falcon_oibr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_57_release-keys-cid12-Oi_BR.tar.gz
409.2 MiB 4C194E4FCBF508743EE7D5309281A0AE Retail Brazilian fastboot_falcon_retbr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_60_release-keys-cid12-Brasil_BR.tar.gz
409.1 MiB FA7B72E00EB3141E8B614C2022FBB9CB Retail Brazilian fastboot_falcon_retbr_user_4.3_14.10.0Q3.X-76-LCG-8_41_release-keys-cid12-Brasil_BR.tar.gz
396.6 MiB E8580CDCCB9E669D5CA1ECA8B6D4F9DF Movistar Chile fastboot_falcon_tefcl_user_4.3_14.10.0Q3.X-76-LCG-8_53_release-keys-cid12-Movistar_CL.tar.gz
396.6 MiB 38BE1E4EAA8A938CE78DB7B2678B0481 Movistar Peru fastboot_falcon_tefpe_user_4.3_14.10.0Q3.X-76-LCG-8_53_release-keys-cid12-Movistar_PE.tar.gz
We have 6.22 GiB of firmwares for Motorola Motorola G.
Actually, it seems the South American firmwares are pachaged , and named, differently. They're specifically labelled beginning with fastboot, and the archives let you expand to a directory giving you a single image for system.img The only one of interest to me is Brazil - I wonder will the Brazil system image work instead of the GB, FR or DE retail devices. If we get root I suppose we can edit build prop.
There has to be a way of concatenating the system images in the European retail images?
I wonder is this
jusumgeezer said:
Coming from a nexus, I thought that also, but I'm sure on another thread it is mentioned that ADB sideload only applies to OTA update files.
I tried pushing the whole zip to the phone but as expected it did nothing.
Fastboot flash should work but the bootloader won't give permission so something isn't right.
Although on the instructions from motorola website it says not to use android fastboot, but use RSD tool instead. I have 2 potential issus with that #1 the software itself hasn't been updated to support the MotoG or #2 it wont work with my 64bit copy of windows 7.
Click to expand...
Click to collapse
I am wondering if you need to use the Motorola version of fastboot which is different to the normal Android one. Sorry, I dont have a link to it, but I think it is in the Moto X section somewhere.
The Jones said:
I am wondering if you need to use the Motorola version of fastboot which is different to the normal Android one. Sorry, I dont have a link to it, but I think it is in the Moto X section somewhere.
Click to expand...
Click to collapse
The Motorola version is in a "Windows" folder in the Brazil firmware download!
heres root http://www.modaco.com/topic/366771-superboot-moto-g-root-solution/
I deleted my /system/priv-app/LGConciergeBoard by error and i would like to have the smart-notice widget again. Someone can send me a zip with that folder.
I have a Sprint unit LS996 on ZV6 firmware
Thanks in advance
why dont you just dd send_command your backup or the rootedsystem.img ?
Alex_XV6700 said:
why dont you just dd send_command your backup or the rootedsystem.img ?
Click to expand...
Click to collapse
Where i am bandwidth is a real issue and i was hopping not to download the rooted ZV6 i am currently downloading the stock ZV6 to OTA to ZV8 and then download the rooted ZV8 to install it. Guess i will wait ...
Thanks you so much for your answer.
BTW prior to delete that folder did not make a bakup... shame on me...
Hello as you all know that we are be to downgrade to 5.1.1 using combination firmware and by flashing engineered bootloader sboot.bin. here https://forum.xda-developers.com/galaxy-s6/general/guide-how-to-downgrade-to-lolipop-t3545903
now the problem is fingerprint scanner is not working to get it working we need to flash cm.bin and sboot.bin from 5.1.1 firmware it gives sw rev error when flashing with odin. so I'm finding other ways to do it. i have tried dd commands from adb shell / su terminal like:
dd if=/sdcard/sboot.bin of=/dev/block/platform/15570000.ufs/by-name/BOTA0
dd if=/sdcard/cm.bin of=/dev/block/platform/15570000.ufs/by-name/BOTA1
also used bs and count
dd if=/sdcard/sboot.bin of=/dev/block/platform/15570000.ufs/by-name/BOTA0 bs=4096 count=1
it flashes ok but after reboot fingerprint don't work neither these two sboot and cm are downgraded
i also tried twrp to flash these same things happens now the question is there somebody more expert and experienced dev? who can help those many people who want to downgrade to 5.1.1 real original ui who don't like mm and grace ux.
how can we forcefully overwrite these bootloader files? please comment bellow i hope there could be a way. I''m on 5.1.1 reply any idea i can test instantly.
qasim799 said:
Hello as you all know that we are be to downgrade to 5.1.1 using combination firmware and by flashing engineered bootloader sboot.bin. here https://forum.xda-developers.com/galaxy-s6/general/guide-how-to-downgrade-to-lolipop-t3545903
now the problem is fingerprint scanner is not working to get it working we need to flash cm.bin and sboot.bin from 5.1.1 firmware it gives sw rev error when flashing with odin. so I'm finding other ways to do it. i have tried dd commands from adb shell / su terminal like:
dd if=/sdcard/sboot.bin of=/dev/block/platform/15570000.ufs/by-name/BOTA0
dd if=/sdcard/cm.bin of=/dev/block/platform/15570000.ufs/by-name/BOTA1
also used bs and count
dd if=/sdcard/sboot.bin of=/dev/block/platform/15570000.ufs/by-name/BOTA0 bs=4096 count=1
it flashes ok but after reboot fingerprint don't work neither these two sboot and cm are downgraded
i also tried twrp to flash these same things happens now the question is there somebody more expert and experienced dev? who can help those many people who want to downgrade to 5.1.1 real original ui who don't like mm and grace ux.
how can we forcefully overwrite these bootloader files? please comment bellow i hope there could be a way. I''m on 5.1.1 reply any idea i can test instantly.
Click to expand...
Click to collapse
This is risky but maybe if you format the partitions before you flash it may work.?
UltraGamerHD said:
This is risky but maybe if you format the partitions before you flash it may work.?
Click to expand...
Click to collapse
how can i format them if you are talking about twrp then can you give me correct updater script to format these partition and then flash files afterwards.
they are not ext4
Stock Firmware H850 v20k OPEN EU ROM
There is a newer version available: H850 v20q. Thread: https://forum.xda-developers.com/lg-g5/development/stock-h850-20q-eu-rom-flashable-zips-kdz-t3707040
[Update 14-12-2017] Downloads removed to gain storage for newer versions.
KDZ-File: H85020k_00_OPEN_EU_OP_0822.kdz (MD5)
Flashable ZIP Complete: LG-H85020K-Flashable.COMPLETE.zip (MD5)
Flashable ZIP Boot: LG-H85020K-Flashable.Boot.zip (MD5)
Flashable ZIP Bootloader: LG-H85020K-Flashable.Bootloader.zip (MD5)
Flashable ZIP Modem: LG-H85020K-Flashable.Modem.zip (MD5)
Android 7.0
Patch level: 1st August 2017
Baseband: MPSS.TH.2.0.c1.4-00047-M8996FAAAANAZM-1.101802.1.109832.1
Kernel: 3.18.31
Build: NRD90U
Tested it with TWRP 3.1.1 and SuperSu v2.82.
Instructions: Please use autoprime's H850 20D install directions here: https://forum.xda-developers.com/lg-g5/development/stock-h850-20d-eu-rom-flashable-zips-t3592762.
To build the ZIPs I used parts of autoprime's previous files. Thx to him.
Has anyone already tried to upgrade from v20a to v20k using the complete.zip?
Thanks a lot. I have to go back from LineageOS because there are so much bugs
Nice that you upload all these images. What is your source?
cleaned
Can I upgrade my stock LG G5 ( 20i ) to this, using LGUP?
Is this the latest Android version for G5? Can I root it?
@DavidFlint
I'm on Fulmics ROM 4.5. To flash Bootloader zip, do I need to do full wipe or can I just flash bootloader and then boot back into the rom without loosing any data?
Sent from my LG-H850 using XDA-Developers Legacy app
Kirparon said:
Thanks a lot. [...] Nice that you upload all these images. What is your source?
Click to expand...
Click to collapse
You're welcome. The source for the KDZ is LG. I did the the ZIP files by myself using the KDZ data and parts of autoprime's work.
SergiuStatache said:
Can I upgrade my stock LG G5 ( 20i ) to this, using LGUP?
Click to expand...
Click to collapse
Yes, should work with the kdz file.
giebeka said:
Is this the latest Android version for G5? Can I root it?
Click to expand...
Click to collapse
At the moment, yes. H850 20K implements some security updates (small update). Rooting as I mentioned works with SuperSU 2.82: just flash it in TWRP after the H850 20K ZIP.
I flashed this rom with the latest twrp but now every time my phone reboots in recovery. I tries to reflash or re-download but it's the same... Please help me. I'm with H850
sseleman13 said:
I flashed this rom with the latest twrp but now every time my phone reboots in recovery. I tries to reflash or re-download but it's the same... Please help me. I'm with H850
Click to expand...
Click to collapse
Sounds like the famous twrp bootloop.
Try entering through the terminal:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
You might then need to install SU s well..
Randomuser666 said:
Sounds like the famous twrp bootloop.
Try entering through the terminal:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
You might then need to install SU s well..
Click to expand...
Click to collapse
I solved flashing stock european firmware with LG-UP and uppercut. So i re-flashed fulmics rom.
ATZ-007 said:
@DavidFlint
I'm on Fulmics ROM 4.5. To flash Bootloader zip, do I need to do full wipe or can I just flash bootloader and then boot back into the rom without loosing any data?
Sent from my LG-H850 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I would really appreciate a reply to this this.
Thanks [emoji2]
Sent from my LG-H850 using XDA-Developers Legacy app
Randomuser666 said:
Sounds like the famous twrp bootloop.
Try entering through the terminal:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
You might then need to install SU s well..
Click to expand...
Click to collapse
Didn't work, unfortunately.
I thought I did everything right, but got into the recovery loop, fixed by flashing a KDZ via LGUP. What caused the issue in the first place? Should I now re-root the damn thing?
totalnoob34 said:
Didn't work, unfortunately.
I thought I did everything right, but got into the recovery loop, fixed by flashing a KDZ via LGUP. What caused the issue in the first place? Should I now re-root the damn thing?
Click to expand...
Click to collapse
Hmm, I had the twrp boot loop when I flashed LOS, so I'm pretty sure it is a twrp-problem.
try one of the solutions described here:
https://forum.xda-developers.com/lg-g5/help/stuck-twrp-recovery-t3587077
There are several other entries about the twrp-loop and the G5 as well...
It is very, very easy to lose twrp or end up in the twrp loop with the G5. I had both problems and figured out that you have to be very careful about how how flash new roms, or update roms, or when to flash SU etc.. you will have to google it...
I think it's a bit of a hit and miss situation here...
I guess the reason why you had the problem was, coz you didn't flash SU immediately after flashing the rom but probably tried to boot it first...
When I was trying to figure out why I was constantly ending up in a twrp loops or losing twrp (actually not being able to access it, was not lost...) or root.. I was thinking for days WTF, WTF...
sseleman13 said:
I flashed this rom with the latest twrp but now every time my phone reboots in recovery. I tries to reflash or re-download but it's the same... Please help me. I'm with H850
Click to expand...
Click to collapse
My G5 did the same a while ago. When I remember right I was able to fix that with re-flash of TWRP in bootloader, then flash COMPLETE ZIP and SuperSU in TWRP. Have you tried this?
Take it as a rule, flash rom+supersu always, without to reboot betweem
Sent from my P027 using XDA-Developers Legacy app
Maybe a stupid question, but since I got magik I have to flash the rom, then magisk again...without reboot.
What about the screen retention? Fixed?
Anyone know if Anti rollback is still 00? Also I noticed 20P is out already.
rosboy said:
Anyone know if Anti rollback is still 00? Also I noticed 20P is out already.
Click to expand...
Click to collapse
It is. See attached screenshot.
Thanks, I tested 20P and it is also able to rollback. I'm back to Marshmallow. Couldn't get xposed working.
Considering that lately there were quite a few hard-bricks, I invite the users that experienced such bricks to post more details here.
Please use this model when you post :
Similar discussion is done in Mate 10 forums ( https://forum.xda-developers.com/mate-10/how-to/discussion-hard-brick-infos-t3789044 ) too I request all to share their experience.
Please also read this thread made by @ante0 - > https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241 <- you will also find a tool that will help you check the xloader.img
Upload your xloader.img to any file hosting and share us the link so that we can together find a solution for the issues.
1) Device = device codename (COL-L29 C432, AL-10 C00, etc)
2) Firmware and Region before Brick = exact firmware and region (B134 C636, B141 C432)
3) Firmware that lead to brick = The firmware version that lead to bricking
4) You were trying to just update your device or you were also trying to rebrand
5) Your device was rebranded or used stock region?
6) Other infos of modifications, update procedures, etc that you did before bricking
7) xloader.img image
8) Result of Xloader.img check tool ( https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241 ) if possible screen shots.
Thank you and please stay on topic!
Credits for @Pretoriano80 for the idea and @ante0 for the xloader check tool.
1) Device = Honor 10 (COL-L29)
2) Firmware and Region before Brick = COL-L29 8.1.0.106 (SP6C900)
3) Firmware that lead to brick =COL-L29C432B120 (8.1.0.120)
4) Trying to just update the device and also trying to rebrand from SP6C900 to C432
5) Used stock region and not rebranded.
6) Used HuRUpdater to update from COL-L29 8.1.0.106 (SP6C900) to COL-L29C432B120 but gave wrong device info so tried to use no check recovery from Honor V10 but it failed so again tried HuRUpdater to flash COL-L29C432B104 and boom got a hard bricked device. Except black screen nothing happened.
DELETED
@flattervieh , @NekoMichi , @mrspeccy , @awells845 can you please share your experience while updating.
My device did not brick, and the update was applied successfully.
1. Device - Honor 10 (COL-L29)
2. FW before update - COL-L29C432B120 (8.1.0.120)
3. FW after update - COL-L29C432B145 (8.1.0.145)
4. Update only, did not attempt to rebrand.
5. Device had not been rebranded beforehand.
6. Device was originally rooted by flashing ramdisk image from here.
Magisk version 16.4
Magisk manager version 5.8.3 (129)
Xposed 3.1.4 was also installed
Custom recovery used: TWRP
HuRUpdater used: Version 0.3
Prior to updating, I had removed all passwords/fingerprints/face unlock data.
After the installation was complete in TWRP, I cleared cache and Dalvik cache before rebooting.
I haven't used Xloader.
miststudent2011 said:
1) Device = Honor 10 (COL-L29)
2) Firmware and Region before Brick = COL-L29 8.1.0.106 (SP6C900)
3) Firmware that lead to brick =COL-L29C432B120 (8.1.0.120)
4) Trying to just update the device and also trying to rebrand from SP6C900 to C432
5) Used stock region and not rebranded.
6) Used HuRUpdater to update from COL-L29 8.1.0.106 (SP6C900) to COL-L29C432B120 but gave wrong device info so tried to use no check recovery from Honor V10 but it failed so again tried HuRUpdater to flash COL-L29C432B104 and boom got a hard bricked device. Except black screen nothing happened.
Click to expand...
Click to collapse
Well, HuRUpdater is not intended for rebrand and that was your first mistake (even if it wasn't the real problem).
Second, you tried to downgrade instead of trying to rebrand with NoCheck Recovery (that would have fixed your initial issue).
Third, there's not much to do for your device now and only a fix/replacement from Huawei will revive it.
You should check the xloader.img for COL-L29C432B120 and COL-L29C432B104, at least you could understand if xloader was the culprit or just the downgrade (mixed-up operations you did previously).
Pretoriano80 said:
Well, HuRUpdater is not intended for rebrand and that was your first mistake (even if it wasn't the real problem).
Second, you tried to downgrade instead of trying to rebrand with NoCheck Recovery (that would have fixed your initial issue).
Third, there's not much to do for your device now and only a fix/replacement from Huawei will revive it.
You should check the xloader.img for COL-L29C432B120 and COL-L29C432B104, at least you could understand if xloader was the culprit or just the downgrade (mixed-up operations you did previously).
Click to expand...
Click to collapse
Well, HuRUpdater is not intended for rebrand and that was your first mistake -- >Mine shows region as EU only which is COL-L29 so I dont think I am trying to rebrand (may be wrong).
Second, you tried to downgrade instead of trying to rebrand with NoCheck Recovery --> Tried with the same build but it did not work just failed installation, so tried with lower build it too gave same error.
You should check the xloader.img for COL-L29C432B120 and COL-L29C432B104 --> Currently dont have the files will re download and check them.
BTW do you have any idea of how to check extract currently installed build Xloader from mobile ?
miststudent2011 said:
Well, HuRUpdater is not intended for rebrand and that was your first mistake -- >Mine shows region as EU only which is COL-L29 so I dont think I am trying to rebrand (may be wrong).
Second, you tried to downgrade instead of trying to rebrand with NoCheck Recovery --> Tried with the same build but it did not work just failed installation, so tried with lower build it too gave same error.
You should check the xloader.img for COL-L29C432B120 and COL-L29C432B104 --> Currently dont have the files will re download and check them.
BTW do you have any idea of how to check extract currently installed build Xloader from mobile ?
Click to expand...
Click to collapse
2) Firmware and Region before Brick = COL-L29 8.1.0.106 (SP6C900) <- this looks like demo unit or something,clearly not C432 (hw/eu).
So it seems that you tried to flash a firmware not intended for your region. Or maybe i'm missing something?
Pretoriano80 said:
2) Firmware and Region before Brick = COL-L29 8.1.0.106 (SP6C900) <- this looks like demo unit or something,clearly not C432 (hw/eu).
So it seems that you tried to flash a firmware not intended for your region. Or maybe i'm missing something?
Click to expand...
Click to collapse
Yes it is a Demo unit , In settings while I looked for device info it showed as International and hw/eu . So I am assuming its a EU variant(not sure).
miststudent2011 said:
Yes it is a Demo unit , In settings while I looked for device info it showed as International and hw/eu . So I am assuming its a EU variant(not sure).
Click to expand...
Click to collapse
The correct procedure would have been this:
1)Rebrand with NoCheck Recovery from demo to C432
2)Flash a FullOTA for C432,profit!
miststudent2011 said:
BTW do you have any idea of how to check extract currently installed build Xloader from mobile ?
Click to expand...
Click to collapse
From a terminal:
dd if=/dev/block/sda of=/sdcard/xloader.img
(This requires TWRP at least)
Then transfer to computer to check manually or:
You can then run the xxd command, though this requires busybox
xxd -s 0x1a8 -l 1 /sdcard/XLOADER.img | grep '000001a8: 01'> /dev/null && echo "01 XLOADER. Safe when going 01 to 01, 01 to 02. 02 to 01 WILL brick" || echo "02 XLOADER. Safe when going 02 to 02. 02 to 01 WILL brick
ante0 said:
From a terminal:
dd if=/dev/block/sda of=/sdcard/xloader.img
(This requires TWRP at least)
Then transfer to computer to check manually or:
You can then run the xxd command, though this requires busybox
xxd -s 0x1a8 -l 1 /sdcard/XLOADER.img | grep '000001a8: 01'> /dev/null && echo "01 XLOADER. Safe when going 01 to 01, 01 to 02. 02 to 01 WILL brick" || echo "02 XLOADER. Safe when going 02 to 02. 02 to 01 WILL brick
Click to expand...
Click to collapse
Thanks for the command I will try it, can you also give commands to backup stock recovery before flashing twrp , and similar command for all other partitions
miststudent2011 said:
Thanks for the command I will try it, can you also give commands to backup stock recovery before flashing twrp , and similar command for all other partitions
Click to expand...
Click to collapse
For recovery you can actually do
dd if=/dev/block/bootdevice/by-name/erecovery_ramdisk of=/dev/block/bootdevice/by-name/recovery_ramdisk
This will write erecovery ramdisk to recovery ramdisk, as they both use the same image.
For other partitions you can use dd too, but they become rather large as dd copies the whole partition rather than just occupied data.
Example: dd if=/dev/block/bootdevice/by-name/system of=/sdcard/system.img
If it complains about /dev/block/bootdevice you have to use the full platform path or figure out whats linked to what.
You can 'cd' to /dev/block/platform/xxxxxxx/by-name/
Xxxxxx= platform dependent, not sure what Honor 10 uses.
Then use 'ls -la' there to show where symlinks go, and you should then see that system is linked to /dev/block/sdd59
Then you can just dd if=/dev/block/sdd59 of=/sdcard/system.img
miststudent2011 said:
Thanks for the command I will try it, can you also give commands to backup stock recovery before flashing twrp , and similar command for all other partitions
Click to expand...
Click to collapse
If you don't have busybox installed, you can open the xloader.img from sdcard with this app - > https://play.google.com/store/apps/details?id=com.kos.binaryviewer <- go to "000001a8" offset and check if it has the 01 or 02 switch.
ante0 said:
For recovery you can actually do
dd if=/dev/block/bootdevice/by-name/erecovery_ramdisk of=/dev/block/bootdevice/by-name/recovery_ramdisk
This will write erecovery ramdisk to recovery ramdisk, as they both use the same image.
For other partitions you can use dd too, but they become rather large as dd copies the whole partition rather than just occupied data.
Example: dd if=/dev/block/bootdevice/by-name/system of=/sdcard/system.img
If it complains about /dev/block/bootdevice you have to use the full platform path or figure out whats linked to what.
You can 'cd' to /dev/block/platform/xxxxxxx/by-name/
Xxxxxx= platform dependent, not sure what Honor 10 uses.
Then use 'ls -la' there to show where symlinks go, and you should then see that system is linked to /dev/block/sdd59
Then you can just dd if=/dev/block/sdd59 of=/sdcard/system.img
Click to expand...
Click to collapse
Do I need root for this or just stock is enough ? or as suggested above do i need twrp ?
Firmware for my version is not available so wanted to make sure before proceeding. Doesnt want to hard brick one more device.
miststudent2011 said:
Do I need root for this or just stock is enough ? or as suggested above do i need twrp ?
Firmware for my version is not available so wanted to make sure before proceeding. Doesnt want to hard brick one more device.
Click to expand...
Click to collapse
Root is mandatory if TWRP is not installed.
Pretoriano80 said:
Root is mandatory if TWRP is not installed.
Click to expand...
Click to collapse
Image link from your previous post is broken ?
miststudent2011 said:
Do I need root for this or just stock is enough ? or as suggested above do i need twrp ?
Firmware for my version is not available so wanted to make sure before proceeding. Doesnt want to hard brick one more device.
Click to expand...
Click to collapse
Pretoriano80 said:
Root is mandatory if TWRP is not installed.
Click to expand...
Click to collapse
And TWRP is fine if no root
dd works even with the adb enabled mankindtw recovery, so you would just need that if you don't want to flash TWRP.
But you will need one if them... I guess TWRP would be better as you can backup ramdisk that way and keep it stock.
But if Honor 10 was released with 8.1 I'm pretty sure it has a 02 xloader already, P20 has had it since the first firmware and its most likely why dc/fh doesn't work for it.
ante0 said:
And TWRP is fine if no root [emoji14]
dd works even with the adb enabled mankindtw recovery, so you would just need that if you don't want to flash TWRP.
But you will need one if them... I guess TWRP would be better as you can backup ramdisk that way and keep it stock.
But if Honor 10 was released with 8.1 I'm pretty sure it has a 02 xloader already, P20 has had it since the first firmware and its most likely why dc/fh doesn't work for it.
Click to expand...
Click to collapse
That's why i'm curious if COL-L29C432B104 has 01 or 02 xloader. [emoji6]
Pretoriano80 said:
That's why i'm curious if COL-L29C432B104 has 01 or 02 xloader. [emoji6]
Click to expand...
Click to collapse
Oh, it's 01
http://imgur.com/a/qMCjPDi