Database Info

[Q] RAZR HD stuck in fastboot, cannot flash

Hi everyone, my XT925 is stuck in fastboot, and whenerver I try to flash it everything just fails; RSD shows this when I try to flash:
Failed flashing process. 1/20 flash partition "partition signed" -> Phone returned FAIL
I tried to flash this stock rom: XT925_vffr-user 4.1.2 9.8.2Q-8-XT925_VQU-26 1359487946
I had already rooted the phone and unlocked the bootloader too, and when I did an OTA update all hell broke loose, the phone now goes directly to fastboot mode, and shows this:
Downgraded secutiry version
Update gpt_main version failed
Failed to hab check for gpt_backup:0x35
failed to load GPT
CID read failure
Invalid CID status 0x69
No SP partition found
Fastboot reason: Invalid GPT
It also says Phone is LOCKED, Status Code:0
I think this means that somehow the bootloader is locked but I have already unlocked it; I don't know what to do, please help

Some Help
Hi, the same thing happened to me when I tried a ROM from a VFR on my LATAM RAZR HD. The OTA messed everything up.
You can check how I solved it on the thread I created asking for help:
http://forum.xda-developers.com/showthread.php?t=2273574
Basically you need to treat your phone as LOCKED bootloader, meaning only flashing of a version that belongs to the region of your phone and newer or same version as the failed OTA will allow you to flash. Since this is the only way LOCKED bootloader phones will flash.
Rokwenelenya said:
Hi everyone, my XT925 is stuck in fastboot, and whenerver I try to flash it everything just fails; RSD shows this when I try to flash:
Failed flashing process. 1/20 flash partition "partition signed" -> Phone returned FAIL
I tried to flash this stock rom: XT925_vffr-user 4.1.2 9.8.2Q-8-XT925_VQU-26 1359487946
I had already rooted the phone and unlocked the bootloader too, and when I did an OTA update all hell broke loose, the phone now goes directly to fastboot mode, and shows this:
Downgraded secutiry version
Update gpt_main version failed
Failed to hab check for gpt_backup:0x35
failed to load GPT
CID read failure
Invalid CID status 0x69
No SP partition found
Fastboot reason: Invalid GPT
It also says Phone is LOCKED, Status Code:0
I think this means that somehow the bootloader is locked but I have already unlocked it; I don't know what to do, please help
Click to expand...
Click to collapse

still cannot flash
I tried to flash this firmware, it's the more recent from telcel: 9.8.2Q-50-XT925_VQLM-21_AmericaMovil_MX_SIGNED_S12_USAVANQUTELMXLA020.0R_VANQJBTELMXLA_P009_A013_S1FF_v2_CFCv2_fb.xml
it didn't work
what can I do????

Is your phone from Telcel Mexico originally?
I ask because on my case it is. The firmware you need to flash has to be the latest one based on your phone region, on my case I flashed the Brasil Retail. Because my phone is from Latin America. So it will depend on were your phone is from. This is all because your phone is acting up as LOCKED bootloader so flashing a version from another region is not possible.
Also because your phone got stuck on an OTA you need to make sure the version you flash is at least the same one as the OTA, newer if possible.
Rokwenelenya said:
I tried to flash this firmware, it's the more recent from telcel: 9.8.2Q-50-XT925_VQLM-21_AmericaMovil_MX_SIGNED_S12_USAVANQUTELMXLA020.0R_VANQJBTELMXLA_P009_A013_S1FF_v2_CFCv2_fb.xml
it didn't work
what can I do????
Click to expand...
Click to collapse

Worked but not completely
Ok, I flashed the rom that you recomended, the phone finally boots into android, but now is always on "emergency calls only" mode, with or without Sim card any suggestions?

Phone should be back as unlocked bootloader
If you flashed a version fine now, I'm sure that at least you should be able to go into fastboot and see your bootloader as unlocked.
If this is true, then you can go ahead and flash any version available, either being an older Stock version (downgrade) or any custom ROM of your liking, like CM 10.1. You should try them and see if you get a proper signal.
Also in your case, if your bootloader is unlocked again, I recommend you installing the version that you know worked fine for you. It won't matter that it's older than the one you flashed right now. It's just a matter of following the guide for unlocked bootloaders to downgrade versions.
Good luck! :fingers-crossed:

Phone almost repaired
Ok, I flashed the latest stock rom from telcel, the phone is no longer on emergency call mode, the wifi and data connection works fine, but it always shows that there is no reception from my carrier, I can't make calls or send sms because when I try it the phone shows "mobile network not available", the funny thing is that I can connect to de data network from my carrier. What can be causing this trouble?

Honestly I have not faced this before it sounds very weird!
I can think of two possibilities, one your phone lost it's IMEI. You should check if it's still there, either by going through configuration and Phone Information or by the "secret code" on the dialer: *#*#4636#*#*
And in the following menu go into Phone Information. The first thing you should see is your IMEI. If it's not there, look for the how to restore your IMEI thread on here. I know it's there somewhere.
The second thing I can think of is to try to force your phone into your carrier, go into Cellular Networks area and manually choose your provider, this could force the registration.
Hopefully this will be of help!
Rokwenelenya said:
Ok, I flashed the latest stock rom from telcel, the phone is no longer on emergency call mode, the wifi and data connection works fine, but it always shows that there is no reception from my carrier, I can't make calls or send sms because when I try it the phone shows "mobile network not available", the funny thing is that I can connect to de data network from my carrier. What can be causing this trouble?
Click to expand...
Click to collapse

Fastboot Error / Invalid GPT
Rokwenelenya said:
Hi everyone, my XT925 is stuck in fastboot, and whenerver I try to flash it everything just fails; RSD shows this when I try to flash:
Failed flashing process. 1/20 flash partition "partition signed" -> Phone returned FAIL
I tried to flash this stock rom: XT925_vffr-user 4.1.2 9.8.2Q-8-XT925_VQU-26 1359487946
I had already rooted the phone and unlocked the bootloader too, and when I did an OTA update all hell broke loose, the phone now goes directly to fastboot mode, and shows this:
Downgraded secutiry version
Update gpt_main version failed
Failed to hab check for gpt_backup:0x35
failed to load GPT
CID read failure
Invalid CID status 0x69
No SP partition found
Fastboot reason: Invalid GPT
It also says Phone is LOCKED, Status Code:0
I think this means that somehow the bootloader is locked but I have already unlocked it; I don't know what to do, please help
Click to expand...
Click to collapse
adolfovm said:
Hi, the same thing happened to me when I tried a ROM from a VFR on my LATAM RAZR HD. The OTA messed everything up.
You can check how I solved it on the thread I created asking for help:
http://forum.xda-developers.com/showthread.php?t=2273574
Basically you need to treat your phone as LOCKED bootloader, meaning only flashing of a version that belongs to the region of your phone and newer or same version as the failed OTA will allow you to flash. Since this is the only way LOCKED bootloader phones will flash.
Click to expand...
Click to collapse
Hello,
I have an xt926 and I tried to take the latest OTA upgrade.
My bootloader was unlocked, and I temporarily un-rooted with Voodoo OTA Rootkeeper.
My phone then got stuck in Fastboot with the same errors:
Phone is LOCKED, Status Code:0
Downgraded secutiry version
Update gpt_main version failed
Failed to hab check for gpt_backup:0x35
failed to load GPT
CID read failure
Invalid CID status 0x69
No SP partition found
Fastboot reason: Invalid GPT
I can't get the phone out of fastboot with the error messages.
The Windows Utility returned <remote access failure>
RSD returned <getvar errors>
(I tried deleting the 2 <getvar> lines in the .xml files, but then RSD said phone returned failure "sbl1.mbn".
I downloaded & installed the adb package, and I got the phone to respond to fastboot commands, but it still ended up in Fastboot with the above list of errors.
Any suggestions?
Thanks

doctorwho2 said:
Hello,
I have an xt926 and I tried to take the latest OTA upgrade.
My bootloader was unlocked, and I temporarily un-rooted with Voodoo OTA Rootkeeper.
My phone then got stuck in Fastboot with the same errors:
Phone is LOCKED, Status Code:0
Downgraded secutiry version
Update gpt_main version failed
Failed to hab check for gpt_backup:0x35
failed to load GPT
CID read failure
Invalid CID status 0x69
No SP partition found
Fastboot reason: Invalid GPT
I can't get the phone out of fastboot with the error messages.
The Windows Utility returned <remote access failure>
RSD returned <getvar errors>
(I tried deleting the 2 <getvar> lines in the .xml files, but then RSD said phone returned failure "sbl1.mbn".
I downloaded & installed the adb package, and I got the phone to respond to fastboot commands, but it still ended up in Fastboot with the above list of errors.
Any suggestions?
Thanks
Click to expand...
Click to collapse
try this and let me know if it works please. its a test build to fix this issue.
http://www.mediafire.com/download/987490ykl14j4t8/DROID_RAZR_HD_Utility_1.3.gpt_fix.rar
thanks

Thanks
bweN diorD said:
try this and let me know if it works please. its a test build to fix this issue.
link
thanks
Click to expand...
Click to collapse
Thanks to you, it really work for me. My Motorola RAZR HD its now alive.

other possible solution that worked for me is
flashing this
http://sbf.droid-developers.org/download.php?device=6&file=119 (CLARO PR Jelly Bean)
Thanks!

suggestions for XT 925 please?
bweN diorD said:
try this and let me know if it works please. its a test build to fix this issue.
http://www.mediafire.com/download/987490ykl14j4t8/DROID_RAZR_HD_Utility_1.3.gpt_fix.rar
thanks
Click to expand...
Click to collapse

hbenz2008 said:
suggestions for XT 925 please?
Click to expand...
Click to collapse
replace the files in the tool with the files for your region. delete all the files for the 926 if any are left in there before flashing, so they arent flashed by mistake. also if any of your file names are not exactly the same as the current files inside, you will need to edit the batch file and fix the names.
if you dont want to do all that, you can get Mfastboot and flash your files to the phone manually one at a time starting with the partition file.

unable to flash partition signed
Hi.
I downloaded the SBF from sbf.droid-developers.org/phone.php?device=6 for my region(canada).
I proceeded to try to do universal through the RSD:
Filename: UNIVERSAL.xml
Creation Date: 11/23/2014 09:11:58
File size: 1589
Sofware Version: XT925_rcica-user 4.1.2 9.8.2Q-8-XT925_VQL-12.2 1356031681 release-keysVANQUISH_U_BP_100700.220.65.33P
For Phone Model: VANQUISH_U
I got failed flash process 1/18 flash partition "partition_signed"
Before this, my phone was working fine. Got the kitkat update pushed to me and after update it was working fine. I was using it until my battery ran out so i turned it off. Afterwards, it just got stuck at the motorola logo. I tried to update it with xt926 didn't realize that my phone is xt925. Anyways, i got the bootloader unlocked. Tried the above but failed.
Any help is appreciated!
Thanks!

what did you have on your phone before flashing it the first time? you can try reflash and edit xml before doing that, delete "getvar" line from it.

hbenz2008 said:
what did you have on your phone before flashing it the first time? you can try reflash and edit xml before doing that, delete "getvar" line from it.
Click to expand...
Click to collapse
I just got help from another thread. Followed it and it worked!!
http://forum.xda-developers.com/showthread.php?t=2760840&page=72

bweN diorD said:
replace the files in the tool with the files for your region. delete all the files for the 926 if any are left in there before flashing, so they arent flashed by mistake. also if any of your file names are not exactly the same as the current files inside, you will need to edit the batch file and fix the names.
if you dont want to do all that, you can get Mfastboot and flash your files to the phone manually one at a time starting with the partition file.
Click to expand...
Click to collapse
Originally had my RAZR HD firmware Telstra Australia, having unlocked bootloader I pass Retail Retail France and then to Brazil to upgrade to KitKat, where brick. I you explain how serious the replace files.
I have the Firmware Jelly bean in all regions, but are replaced with files jelly bean? and addresses of the partitions also be accommodated to those that are in the XML file jelly bean?

edwint290 said:
Originally had my RAZR HD firmware Telstra Australia, having unlocked bootloader I pass Retail Retail France and then to Brazil to upgrade to KitKat, where brick. I you explain how serious the replace files.
I have the Firmware Jelly bean in all regions, but are replaced with files jelly bean? and addresses of the partitions also be accommodated to those that are in the XML file jelly bean?
Click to expand...
Click to collapse
i dont really understand what you are asking.
you need to figure out which is the most recent partition table you have put on the phone successfully and flash that first. nothing will work correctly until you do. after you get a successful partition flash, you can flash whatever you want, just DO NOT flash the partition file again from any other version. old builds will work on the newer partition table.

Stuck at chinesse region

Please someone help me. I did something(I don't know what) with my L09(Eu version) to update it to Marshmallow. Somehow,my region shows Vendor:cmccchannel, Country:cn. I can't downgrade,root,install twrp,and update it. When I try to flash twrp through adb it says Command not allowed,but my bootloader is unlocked. My build number is MT7-C900B522. How can I fix all that? Thanks

nidzatb said:
Please someone help me. I did something(I don't know what) with my L09(Eu version) to update it to Marshmallow. Somehow,my region shows Vendor:cmccchannel, Country:cn. I can't downgrade,root,install twrp,and update it. When I try to flash twrp through adb it says Command not allowed,but my bootloader is unlocked. My build number is MT7-C900B522. How can I fix all that? Thanks
Click to expand...
Click to collapse
if you used SRK tools, it locked bootloader you should unlock bootloader(fastboot oem unlock YOURUNLOCKCODE),then if you want to use any backups region is important.you must change region(eg:you are in b522 and region must be hw/eu) on succesfull rom then you can use downgrade package and backups too...

[Sony Xperia E5][Bootloader][Root][ETC...]

So i was thinking that we dont have any thread to this device so i made this.
Can someone help me to unlock bootloader to this beatiful device. i cant get it open.
when im trying to unlock it with the code(adb or flashtool) it gives me error saying "command not allowed" i have tried many times and re installing the drivers and tried different os and nothing helps.
tried to make some research from google etc like stackflow but just cant find nothing. i have the imei right and everything. and tried to unlock with the sonys dev site. and i did out the device as e4g or e4. nothing

command not allowed
to my device xperia e5 f3311 but it also writes in the service menu * # * # 7378423 # * # * service info\configuration is line "rooring status:" bootloader unlock alloved: yes
I'm now looking for a custom recovery for my xperia e5 f3311 and install an supersu.zip and rooting proces is complete but

GameboyZA said:
to my device xperia e5 f3311 but it also writes in the service menu * # * # 7378423 # * # * service info\configuration is line "rooring status:" bootloader unlock alloved: yes
I'm now looking for a custom recovery for my xperia e5 f3311 and install an supersu.zip and rooting proces is complete but
Click to expand...
Click to collapse
Solved the command not allowed proplem . just go in your phone top the developer settings and enable the oem thing. and make sure that usb debugging is on. thats it! hope it helps you out

pottu221 said:
Solved the command not allowed proplem . just go in your phone top the developer settings and enable the oem thing. and make sure that usb debugging is on. thats it! hope it helps you out
Click to expand...
Click to collapse
pottu221 thanks....

Hey, does the root works with your method?
If this work how do you proceed for that (Install CWM and install super su ?)?
Thanks

toinedu27 said:
Hey, does the root works with your method?
If this work how do you proceed for that (Install CWM and install super su ?)?
Thanks
Click to expand...
Click to collapse
aint gonna happen. none of the tools doesnt support mtk 6735 with android 6.0. so we should have rooted phone to get recovery.img so i think that our only hope is to wait that kingroot or something will work on our device

You don't need to wait for the Kingroot as it is not possible to root locked bootloader with drm-verify enabled.
What You need is to create recovery.img to flash on /recovery partition (it should exist, as Sony started to adding them before E5).
There are autotools for MTK devices (they create recovery for specific SoC/CPU not model), but I'm not sure if it is safe to flash on Sony firmware as it is different than generic firmware used on standard (Chinese) devices.
Than using it should be possible to root it by flashing SuperSU zip.

ch3mn3y said:
You don't need to wait for the Kingroot as it is not possible to root locked bootloader with drm-verify enabled.
What You need is to create recovery.img to flash on /recovery partition (it should exist, as Sony started to adding them before E5).
There are autotools for MTK devices (they create recovery for specific SoC/CPU not model), but I'm not sure if it is safe to flash on Sony firmware as it is different than generic firmware used on standard (Chinese) devices.
Than using it should be possible to root it by flashing SuperSU zip.
Click to expand...
Click to collapse
The proplem is that cant get the recovery.img out from anywhere :/

So there's still no way to root this phone ? I really need to install Viper4Android on it ^^

Hey,
I saw the "Dirty Cow" fault on the Linux systems.
I also saw that fault should works on Android, I will see if I can root my device with that
I will be back soon

toinedu27 said:
Hey,
I saw the "Dirty Cow" fault on the Linux systems.
I also saw that fault should works on Android, I will see if I can root my device with that
I will be back soon
Click to expand...
Click to collapse
Have you managed to root your device?
I've been trying to make a working cwm or twrp recovery, but I need to extract the stock recovery.img to do so.
And that requires root.
Can you send me a dm if you managed to root it with the dirty cow exploit? Thanks.

Hey,
I didn't find time to try this exploit but the thing I should do is just install the package dirty cow for android (released on github) and after use the "run-as" command for install super su...
I'm not certain that can work but it should if Sony didn't correct this fault, else I will always can recover via FlashTool to a factory version.

toinedu27 said:
Hey,
I didn't find time to try this exploit but the thing I should do is just install the package dirty cow for android (released on github) and after use the "run-as" command for install super su...
I'm not certain that can work but it should if Sony didn't correct this fault, else I will always can recover via FlashTool to a factory version.
Click to expand...
Click to collapse
Can you check if it works?
I just need a confirmation that you got your phone rooted safely with that fault, then I'll start working on twrp and hopefully we'll have our first rom on this device soon.
But since I recently bought this phone and I can't get my pc to work (for flashtool, in case anything goes wrong), I need someone to test if the dirty cow fault still works on our devices.
If you have time, please check it out.

Hey,
I try but I need to install a tool called "NDK" for the "NDK-Build" command
I'm progressing

I am waiting for a miracle. I also installed Kingroot and in it I found that in 1497 people have applied for root so that we are not alone. ?

Hey there,
I've managed to set up fastboot and finding alternative drivers to work on our device.
Finally, I can now use adb with full fastboot access.
I've also managed to unlock my bootloader, so now I will have to find a recovery that will work on our mediatek 6735 chipset, build based on API 23 (marshmallow).
If necessary, I can try to port cwm from some different device.
When we have a working recovery, we can most likely flash anything, so I might make a prerooted version of the stock firmware.
Expect the first development for this device any soon.
Edit1: Due to health reasons, I might have to delay this for a week, my appologies.

I'm sorry I don't have the time to exploit the Dirty Cow fault (lot of Home Work) and I don't have the knowledges that I need :/
I hope @mrmarvin_16 will got the root access (Thanks a lot )

Hello. Excuse me for my English writing through translayte google. I am writing with Russian Forum 4PDA. We were able to unlock bootloader is a link to my post on this forum 4pda.ru/forum/index.php?showtopic=753685&st=160#entry54277601 . And TWP recovery we also gathered, the download link yadi.sk/d/Vq0jgohxymPCG . Problem Only here we do not know how to sew it into the phone itself.

I flash recovery but i dont have boot to recovery menu

And as you flashed? I just have all the time an error in piercing through ADB.

[Discussion] Hard-Brick Infos, Success or Failure of Updates.

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

Update Issues after rooting my U12+

Hello,
I have some issues to update my U12.
I bought the phone near the release (carrier free) and tried to root it. It worked, but I used the boot.img method (flashing rooted boot.img via adb) instead of waiting for TWRP. In addition I can´t found the right boot.img for my firmware number, so I had to use a different one.
After some days the first update message showed up. (Version numbers at the end)
Because of that I removed root through the Magisk App, but my phone don´t want to update. I think it´s because of the different boot.img.
In addition it seems that fastboot can´t find the device anymore, so I can´t root it again. (adb is working, only fastboot, but I´m not shure after all)
Now my question: Can I repair and update it by flashing update.zip from SD Card?
-Will it replace the wrong boot.img (it should flash the updatet version)
-Should I flash the current firmware at first to get back to original boot.img or can I directly flash the update?
-Can I root it again after update (because the update surely will reinstall crap apps)
-Will my changes (below) doing anything against the update?
My current firmware: 1.15.708.6
update: 1.21.708.3
Things I did with root:
-delete crap (bloatware and the *** screenshot sound)
-adblock app with hosts
-giving root to screen recorder app so it can record internal sound

If you deleted some system apps you will not able to take update. Be sure to bring stock system back to take update . The simplest way is to find right ruu. from here https://docs.google.com/spreadsheets/d/1wIRrVQawd5rD-t9VKPQ-SdRK20RcJVZhwD7lhmPIK8w/htmlview
Beware that all stuff will be deleted from your phone after ruu

do you know your CID?

fabrizio b92 said:
do you know your CID?
Click to expand...
Click to collapse
Simple CID Getter says
HTC_622
Asia-HK-CHT

ClickDE said:
Simple CID Getter says
HTC_622
Asia-HK-CHT
Click to expand...
Click to collapse
Ok, we need to restore smartphone functioning, download Ruu corrispondind CID
from here----> https://docs.google.com/spreadsheets/d/1wIRrVQawd5rD-t9VKPQ-SdRK20RcJVZhwD7lhmPIK8w/edit#gid=0
-After download rename the file with 2Q5510000 and copy it on sda card
-Reboot your smartphone in downlado mode adn automatically detect the file,if ask use buttons to flash the file
-Once the file has been flashed, your phone will reboot into the stock ROM
-IMPORTANT: this methos erase all your data, so make a backup
---------- Post added at 09:54 ---------- Previous post was at 09:41 ----------
if you have a rooted smartphone you can't update the firmware trought Ota,never,maybe brick smartphone.
There are 2 ways:
- RUU method, like above
- Restore backup recovery with update firmware

(If you have a rooted smartphone you can't update the firmware trought Ota,never,maybe brick smartphone.
There are 2 ways:
- RUU method, like above
- Restore backup recovery with update firmware)
(As I wrote in my question, I removed root to update)
I think there is a misunderstand. I want to install all updates in one day, AFTER I repaired the firmware flashing RUU. And I want to wait till Android 9 is released, because I want to root it again after update.
(Android 9 Release)>flashing Ruu to repair>install all updates till Android 9>root

ClickDE said:
(As I wrote in my question, I removed root to update)
Click to expand...
Click to collapse
Did you have restore stock recovery and relock the bootloader?

fabrizio b92 said:
Did you have restore stock recovery and relock the bootloader?
Click to expand...
Click to collapse
-I have stock recovery, I only flashed the boot.img with root
-bootloader is still unlocked. In additon I can´t lock it, because my phone won't be recognized in fastboot mode (as I wrote in my question.)

Please forget what I´ve written before. Start again.
At the very beginning there was no TWRP for U12, so I used the boot.img method to root my phone. But I used the from .img.
My question: Is there anyone with a boot.img from 1.15.708.6 (can´t found it in the Google Spreadsheet, only from 1.25.708.3)
Could I use the other boot.img?
Will I be able to update after flashing the original img or will I have to relock the bootloader?
Or can I only relock the bootloader and update without the correct boot.img?
In addition I´ve downloaded the Ruu for my CID 622 (from the Google Spreadsheet). But its 1.25.708.3. Can I flash it from SD card even with this big version difference? And can I flash it without relock the bootloader?
Thats my last try to update, if this won´t work I won´t annoy you anymore.