Database Info

S-On Problem

Hello people
I have a big problem. I have yesterday flash a Custom Rom and hab in the 4Ext Recovery Format Boot/System and Data and since I'm back to S-On and since I've been running the 4ext recovery on it my device i can't restore my Stock Rom Backup because its 3ext. and now I do not know how to get back S-Off. Can someone help me?
sry for my bad english.

Are you HTCDev Unlocked? If that is the case, you need to flash the ROM's original boot.img via CMD
fastboot flash boot boot.img
Click to expand...
Click to collapse
Read more about the difference here http://forum.xda-developers.com/showthread.php?t=1547851

I have flashed the boot.img via fastboot but when i reboot i come to the recovery and not to the lockscreen
Gesendet von meinem HTC Desire S mit Tapatalk 2

Again. Are you HTCDev unlocked? And I was talking about flashing the STOCK ROM BACKUP boot.img

I am HTCdev unlocked and i have flashed the Stock Backup Boot image via fastboot
Gesendet von meinem HTC Desire S mit Tapatalk 2

Omg.. Here is the way how to do it.
1. Connect your phone to the PC
2. Find on your SD Card /clockwordmod/backup/"your backu name"
3. Copy the boot.img to your computer where the adb shell files are located
4. Make sure Fastboot is off and USB Debugging is on
5. Restart your phone in the recovery
6. Restore your previous ROM
7. Restart you phone in Bootloader
8. Connect your phone to the pc flash the boot.img vai cmd

that's exactly what I've tried it five times and I always come only into recovery.

Specimann said:
that's exactly what I've tried it five times and I always come only into recovery.
Click to expand...
Click to collapse
Oh and a full wipe is necessarily as well.
And have you tried to convert the file using "EXT3 - EXT4 - 4EXT" the option in your recovery?

can i change it in cwm? because i dont have 4ext recovery and i can't install it because the s-off

I get 4ext installed via fastboot. Then tried the back-up to convert 3EXT but this does not help, it is because I have a another radio (20.72.30.0833U_3831.17.00.310)?

[RECOVERY] start loop on TWRP after a backup on x2 gem-702L

good morning,
(escuse me for my english I am french,thank google)
I was passing by Rom KangVIP B015 (Android 5.0) and TWRP TWRP-ENG-5.0,
I was the original B003 702L, all works very well for several days,
I decided to make another backup with TWRP (with compression) externally on my sd,
all goes normally, and I then reboot,
and continually find myself on the recovery TWRP menu.
Can not start the system by download from TWRP.
I restored my backup but always the same.
I can put myself in download from the connected computer,
and I have access to the adb command.
by searching the internet, the problem has already produced on LG2 and other,
and there would execute commands either by download or in TWRP in terminal mode.
but I do not know if that works under the MediaPad x2,
and knows the commands to perform.
thank you in advance to all those who have the solution to this problem

Did you try to Factory reset/Wipe your phone from recovery?

hagba said:
Did you try to Factory reset/Wipe your phone from recovery?
Click to expand...
Click to collapse
yes but screwy does not work, always the same

jeanyann said:
yes but screwy does not work, always the same
Click to expand...
Click to collapse
Try to flash the stock recovery with the ADB, and then install back the original ROM from the sdcard with the local updater.

jeanyann said:
good morning,
(escuse me for my english I am french,thank google)
I was passing by Rom KangVIP B015 (Android 5.0) and TWRP TWRP-ENG-5.0,
I was the original B003 702L, all works very well for several days,
I decided to make another backup with TWRP (with compression) externally on my sd,
all goes normally, and I then reboot,
and continually find myself on the recovery TWRP menu.
Can not start the system by download from TWRP.
I restored my backup but always the same.
I can put myself in download from the connected computer,
and I have access to the adb command.
by searching the internet, the problem has already produced on LG2 and other,
and there would execute commands either by download or in TWRP in terminal mode.
but I do not know if that works under the MediaPad x2,
and knows the commands to perform.
thank you in advance to all those who have the solution to this problem
Click to expand...
Click to collapse
Did you unlock the bootloader before you flashed anything?

ajsmsg78 said:
Did you unlock the bootloader before you flashed anything?
Click to expand...
Click to collapse
yes , booloader unlock , all works very well for several days, with Rom KangVIP B015 (Android 5.0) and TWRP TWRP-ENG-5.0,

hagba said:
Try to flash the stock recovery with the ADB, and then install back the original ROM from the sdcard with the local updater.
Click to expand...
Click to collapse
flash the stock recovery with the ADB , how I did in adb command, what I use Rom
i have GEM-702L , GEM-703L_B015 , GEM-703L_EMUI3.1_Android5.1_B106 , in dload
and all the rom KANGVIP (B015,B106,B109,B111) in zip

jeanyann said:
flash the stock recovery with the ADB , how I did in adb command, what I use Rom
i have GEM-702L , GEM-703L_B015 , GEM-703L_EMUI3.1_Android5.1_B106 , in dload
and all the rom KANGVIP (B015,B106,B109,B111) in zip
Click to expand...
Click to collapse
You need to boot into bootloader mode and fastboot flash 4 img files. It's mentioned in multiple threads here just use the search button or look in this thread:
http://forum.xda-developers.com/mediapad-x2/general/how-to-flash-rom-x2-gem-703l-gem-702l-t3228915

ajsmsg78 said:
You need to boot into bootloader mode and fastboot flash 4 img files. It's mentioned in multiple threads here just use the search button or look in this thread:
http://forum.xda-developers.com/mediapad-x2/general/how-to-flash-rom-x2-gem-703l-gem-702l-t3228915
Click to expand...
Click to collapse
I extracted the images of the GEM and GEM-702L-703L, but I have an error
when I want flasher fastboot flash system SYSTEM.img, both with
the system images of the 702L and 703L,
LOAD_FILE: could not allocate -2140949684 bytes for 703L
so I did not flash only the boot.img and recovery.img and reflash
the recorery TWRP TWRP-ENG-5.0, then reboot on TWRP,
restoring my last backup, and all is back to normal,
all working again.
thank you again to all

Help I accidentally flashed a bootloader image as recovery image now phone only has b

Hi I'm an amateur enthusiast of rooting and flashingn etc. I have a Google nexus 5 hammerhead and I flashed a bootloader image as a recovery image while in recovery. My phone turns on goes straight to bootloader and if I try to access rec or start phone then screen is just blank. I've tried using a computer to fix but won't detect drivers won't update drivers and I'm not really sure what I'm doing. Can someone please help me . thanks mike

Make yourself familiar with fastboot.
fastboot flash recovery recovery.img

If the phone is recognized in fastboot mode and the phone has an unlocked bootloader, try flashing a stock Google ROM.

He doesn't have to flash the whole factory image. If he wants stock recovery, he can flash that image file only.
Gesendet von meinem Nexus 5 mit Tapatalk

If it was only recovery that was corrupted, I'm not sure why the phone doesn't boot the rom.

Ah, you're right! Sorry!
@OP: Flash the whole factory image then. Remove the -w flag from the flash-all.bat to prevent your data partition from being wiped.
Gesendet von meinem Nexus 5 mit Tapatalk

Bricked honor 8

Hi. I was trying to install cm13 on my honor 8. I unlocked the bootloader, but while trying to install twrp recovery I think I deleted everything off the phone. The huawei erecovery doesn't work, and I tried sooooo many fastboot commands. I can't do adb commands. I can only get into fastboot mode. Is there anyway for me to get out of this? I tried flashing the system.img and boot.img from fastboot but it fails.

LuneTech said:
Hi. I was trying to install cm13 on my honor 8. I unlocked the bootloader, but while trying to install twrp recovery I think I deleted everything off the phone. The huawei erecovery doesn't work, and I tried sooooo many fastboot commands. I can't do adb commands. I can only get into fastboot mode. Is there anyway for me to get out of this? I tried flashing the system.img and boot.img from fastboot but it fails.
Click to expand...
Click to collapse
Was ur bootloader and frp in unlocked state ?
Sent from my KIW-L22 using Tapatalk

gopinaidu77 said:
Was ur bootloader and frp in unlocked state ?
Click to expand...
Click to collapse
Yes. And it still is

LuneTech said:
Yes. And it still is
Click to expand...
Click to collapse
So u can still recovery your phone
Sent from my KIW-L22 using Tapatalk

LuneTech said:
Hi. I was trying to install cm13 on my honor 8. I unlocked the bootloader, but while trying to install twrp recovery I think I deleted everything off the phone. The huawei erecovery doesn't work, and I tried sooooo many fastboot commands. I can't do adb commands. I can only get into fastboot mode. Is there anyway for me to get out of this? I tried flashing the system.img and boot.img from fastboot but it fails.
Click to expand...
Click to collapse
Hi, i have the exact same problem...
Have you figgerd it out?

Lucas Napik said:
Hi, i have the exact same problem...
Have you figgerd it out?
Click to expand...
Click to collapse
Yes. I installed a roll back update (something like that) by getting into the force update mode. After it finished, I had to then apply the full stock firmware. The problem was that I somehow put the firmware of another phone, because my model number was from a different Huawei phone.

trying to get back to stock
gopinaidu77 said:
So u can still recovery your phone
Sent from my KIW-L22 using Tapatalk
Click to expand...
Click to collapse
Hi. I got tired of CM13, so I tried to go back to stock. I checked a guide online which told me to flash 2 files using TWRP. after that, I lost twrp and now my bootloader is locked. What do I do? I manually did an update with the update.app file, and it says update success, but when it reboots it stays on the honor 8 screen, I waited for 25 minutes and it's still there.

LuneTech said:
Hi. I got tired of CM13, so I tried to go back to stock. I checked a guide online which told me to flash 2 files using TWRP. after that, I lost twrp and now my bootloader is locked. What do I do? I manually did an update with the update.app file, and it says update success, but when it reboots it stays on the honor 8 screen, I waited for 25 minutes and it's still there.
Click to expand...
Click to collapse
Try going into stock recovery and doing a factory reset after you use the update.app. You'll have to unlock the bootloader again and flash twrp if you want root.
Restoring to MM using a full image will typically lock the bootloader.

It happened to me too, it is possible you still didn't use the right image.
This is how I recovered mine:
1. Go here to download the latest firmware for your model: https://www.androidfilehost.com/?w=files&flid=129406
2. Use the Huawei Update Extractor to extract files from the "Update.app". (Ignore the 'profile' drop down list in the app.)
3. Unlock your phone's bootloader.
4. Flash these four images (extracted using the tool from step 2):
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
5. Boot into recovery and do a factory reset. This is needed to reformat the internal storage (and make it encrypted I think). (Power+Vol Up)
6. Put the Update.app file inside the "dload" folder in your SDcard.
7. Boot into flash mode to let the phone flash the Update.app (Power+Vol Up+Vol Down).

eksasol said:
It happened to me too, it is possible you still didn't use the right image.
This is how I recovered mine:
1. Go here to download the latest firmware for your model: https://www.androidfilehost.com/?w=files&flid=129406
2. Use the Huawei Update Extractor to extract files from the "Update.app". (Ignore the 'profile' drop down list in the app.)
3. Unlock your phone's bootloader.
4. Flash these four images (extracted using the tool from step 2):
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
5. Boot into recovery and do a factory reset. This is needed to reformat the internal storage (and make it encrypted I think). (Power+Vol Up)
6. Put the Update.app file inside the "dload" folder in your SDcard.
7. Boot into flash mode to let the phone flash the Update.app (Power+Vol Up+Vol Down).
Click to expand...
Click to collapse
2 things, 1 is that there are 2 recovery files in the UPDATE.APP, and 2 is that I can't do a factory reset from the recovery, because it brings me to the erecovery and it doesn't give me the option to factory reset.

LuneTech said:
2 things, 1 is that there are 2 recovery files in the UPDATE.APP, and 2 is that I can't do a factory reset from the recovery, because it brings me to the erecovery and it doesn't give me the option to factory reset.
Click to expand...
Click to collapse
You need to hold VOLUME UP and POWER button with the phone off to get into the recovery to do a factory reset. Once the honor logo pops up, you can release the power and volume up buttons.
Recovery.img = Stock recovery
Recovery2.img = eRecovery

eksasol said:
It happened to me too, it is possible you still didn't use the right image.
This is how I recovered mine:
1. Go here to download the latest firmware for your model: https://www.androidfilehost.com/?w=files&flid=129406
2. Use the Huawei Update Extractor to extract files from the "Update.app". (Ignore the 'profile' drop down list in the app.)
3. Unlock your phone's bootloader.
4. Flash these four images (extracted using the tool from step 2):
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
5. Boot into recovery and do a factory reset. This is needed to reformat the internal storage (and make it encrypted I think). (Power+Vol Up)
6. Put the Update.app file inside the "dload" folder in your SDcard.
7. Boot into flash mode to let the phone flash the Update.app (Power+Vol Up+Vol Down).
Click to expand...
Click to collapse
I just did everything exactly the way you said. But it still stays at the honor boot logo. I don't mind waiting over night for it to boot up if I have to, but I've never had a phone take this long to boot up, even on first boot.

For a "brick" thread, it seems odd that the model is never mentioned so that someone can really point you to the right spot. If you keep going to erecovery, then it has to do with whether or not your cable is plugged in (likely you've been keeping it plugged in for your fastboot attempts, or that's a guess). I only go to erecovery with both up/down & power if the cable is plugged in. If I want to get to stock recovery (regardless of what the hell is in the "recovery" partition, TWRP, or who knows?) then I unplug it before trying any key combo from power off to get there.
Lastly, if you use this sort of thing as a template (I'm just going to use one for the frd-l09 as an example, but stick the right model in there for you) ::
Example to plug into Google to find your rollback with instructions:: site:consumer.huawei.com honor 8 frd-l09 rollback
Click to expand...
Click to collapse
So if you've got an frd-l04 then plug that in where frd-l09 is. It'll just look on the site consumer.huawei.com just above where the various country/variant breakdowns are, like US/ZH/HU/Etc. are.
Pick the one out that is closest to what it seems you want. All the pages are in the local languages so I'm guessing the .pdf that explains what to do is in the language you'll want as well.
Good luck:: Let us know what model phone you have.
More: Contents of first "intermediate" update.app is 8 image files. I'm sure the 2nd one that is specifically your own phone's version of b162 has a lot more files in it. I've not looked for awhile but I think it's 21 or 22 files. This is a two step process, first is all the crap that comes in update.app from the rollback page (just a 100K file which sets you up in intermediate state for rollback) and 2nd you find your exactly right b162 for your model phone, and pretty much repeat the process.
Yet More: One odd thing about the Honor 8: I've not seen it on other phones is the partition layout is not really "trustworthy" unless you really have gotten to understand it. There appears to be at least 3 or 4 places you can get to that I used to think would all have to be in the recovery partition, but apparently the Honor 8 works differently, so no matter how bleak your odds seem, .. maybe not. I got to both erecovery and stock recovery and rollback while TWRP was installed and it worked just following the directions from their website.

Agreed on this thing.

eksasol said:
It happened to me too, it is possible you still didn't use the right image.
This is how I recovered mine:
1. Go here to download the latest firmware for your model: https://www.androidfilehost.com/?w=files&flid=129406
2. Use the Huawei Update Extractor to extract files from the "Update.app". (Ignore the 'profile' drop down list in the app.)
3. Unlock your phone's bootloader.
4. Flash these four images (extracted using the tool from step 2):
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
5. Boot into recovery and do a factory reset. This is needed to reformat the internal storage (and make it encrypted I think). (Power+Vol Up)
6. Put the Update.app file inside the "dload" folder in your SDcard.
7. Boot into flash mode to let the phone flash the Update.app (Power+Vol Up+Vol Down).
Click to expand...
Click to collapse
Thank you very much, you saved me and my phone !!!
I made a mistake: my phone was under android m and I flashed by mistake the rollback update (to go m from n), then my honor was bricked on bootloop, no recovery, no update by dload....nothing worked....
Your solution was the right one !! again thank you very much

Interesting observation with the eRecovery (recovery2 partition). So I have TWRP installed, the system partition modified and user storage not encrypted. I was still able to to use eRecovery to connect to WiFi and download the factory image and it automatically repaired the phone to factory state. I noticed it doesn't re-lock the bootloader afterward. This seems to be the easiest method to unbrick.
Getting into eRecovery.

hi! Or extract the files? sorry for my english

eksasol said:
It happened to me too, it is possible you still didn't use the right image.
This is how I recovered mine:
1. Go here to download the latest firmware for your model: https://www.androidfilehost.com/?w=files&flid=129406
2. Use the Huawei Update Extractor to extract files from the "Update.app". (Ignore the 'profile' drop down list in the app.)
3. Unlock your phone's bootloader.
4. Flash these four images (extracted using the tool from step 2):
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
5. Boot into recovery and do a factory reset. This is needed to reformat the internal storage (and make it encrypted I think). (Power+Vol Up)
6. Put the Update.app file inside the "dload" folder in your SDcard.
7. Boot into flash mode to let the phone flash the Update.app (Power+Vol Up+Vol Down).
Click to expand...
Click to collapse
Ok after the factory reset (which is peppered with mounting errors)...
failed to mount /data (invalid arguments)
unable to mount storage
When I try to flash cust.img and system.img they both fail.
I cannot check what firmware I was on before I started all this, but I believe it was the latest one. This is a FRD-04. I flashed TWRP 3.1.0.1 erecovery and I can access it and fastboot.
I have tried various different things and nothing I do can unbrick the phone. Any help would be appreciated.

menriquez said:
Ok after the factory reset (which is peppered with mounting errors)...
failed to mount /data (invalid arguments)
unable to mount storage
When I try to flash cust.img and system.img they both fail.
I cannot check what firmware I was on before I started all this, but I believe it was the latest one. This is a FRD-04. I flashed TWRP 3.1.0.1 erecovery and I can access it and fastboot.
I have tried various different things and nothing I do can unbrick the phone. Any help would be appreciated.
Click to expand...
Click to collapse
have the same problem as you on my FRD-09.

I don't have this phone anymore, but the easiest way I find to restore it is using eRecovery.

L-29C900B*** Problem no C432

Hello XDA-Guys,
i think i might found a Problem - i wanted to flash Nougat (B560)... it didnt worked via TWRP.
So i wanted to go back to stock B152 to upgrade via OTA Update.
And then i relised that my TWRP is backing up everyrom with C900B170! My Huawei Mate8 says its C900B180!
but the most thing that ****s up is that i install C432B152 from here - and when its done im on C900B152...
so orignal it should be C432 since im from Germany but i only get C900 - that sucks because only C432 get Nougat, right?
Or to sort the Topic:
Is the b560 still beta? I got my eyes on a online article that says huawei is rolling out B560!
If someone has some infos for me that would be fine.
The C900/C432 is not a problem for me so no troubleshooting needed - but if it denies me the Nougat Update then i need help ( if its not beta anymore).
Thanks guys

can you fix it? I have the same problem and nothing

senseijulio said:
can you fix it? I have the same problem and nothing
Click to expand...
Click to collapse
since no one is helping here, no i still have the problem.

EGOiST1991 said:
since no one is helping here, no i still have the problem.
Click to expand...
Click to collapse
Root you phone then change ro.build = NextL09C999B100 and oeminfo = C432 by using SRK Tools
Sent from my HUAWEI NXT-L29 using XDA Labs

I allready rooted my PHone then i try the srk-tool thanks a lot.

EGOiST1991 said:
I allready rooted my PHone then i try the srk-tool thanks a lot.
Click to expand...
Click to collapse
Glad you managed to rooted your phone.
Sent from my HUAWEI NXT-L29 using XDA Labs

@EGOiST1991 and @dexz I'm having the same problem. I am on C636B320 but it's shown as C900B320 so when I try to follow the guide to update to C432B560 it fails.
My plan was first to get the phone recognised as C636 and then via the srk tool debrand to C432 and then when in TWRP 3.0.2 emui 4.1 follow the guide to get to C432B560.
Now the problem I am having is that I don't know how to get my phone to go from C900 to C636... I'm the srk tool my phone isn't recognised when the tool runs adb server. I belive that is because it is on C900 to begin with, I have HiSuite installed on the computer (Win 10). The files, oeminfo and custom.bin, for C636 are in the tools folder can't I just manually put them in the correct location?
Edit: I have unlocked bootloader and I'm rooted FYI
Edit2: Gotten the computer to recognise the phone. But when I run the srk tool to flash oeminfo and custom.bin it stops at "waiting for device". If I run adb devices I can see my device number but after it says Offline.
An other problem I have noticed is that TWRP 3.0.2-0-next.img doesn't seem to accept my decrypted/insecure_boot_B320.img which is need to format data before flashing B560. The only TWRP version that accepts/hold the decrypted/insecure boot.img is TWRP_3.0.2-0_BLACK_BLUE_EMUI4.1.img
http://cloud.tapatalk.com/s/589fa1f505b9e/Screenshot_2017-02-12-00-35-19.png
Skickat från min NEXT via Tapatalk

Don't everyone answer all at once lol
@EGOiST1991 how has it gone for you, have you managed to update?
Skickat från min NEXT via Tapatalk

@Leo - SRK tool worked fine fro me (im also c900 and rooted so should be your fault) REMEMBER u need to plug your phone in booted up! NOT in fastboot mode!!!
no i didnt managed it yet. i tryd to go back to stock recovery and then the dload method but it failed. so i guess its bc im c900....

EGOiST1991 said:
@Leo - SRK tool worked fine fro me (im also c900 and rooted so should be your fault) REMEMBER u need to plug your phone in booted up! NOT in fastboot mode!!!
no i didnt managed it yet. i tryd to go back to stock recovery and then the dload method but it failed. so i guess its bc im c900....
Click to expand...
Click to collapse
Yeah I am in boot mode but the srk tool still doesn't find my device or rather running adb devices returns device number with comment Offline. Which is strange because if instead go to fastboot and run fastboot devices I can see my device with no problem, so that to me seem like it's not an USB driver issue.
As soon as I am able to debrand to C432 I will give it a go again. At the moment I'm trying to find a way to manually change. I'm going to post a comment on QA for that.
Skickat från min NEXT via Tapatalk

DUDE ! AGAIN! FOR THE SRK TOOL DONT!!!! GO IN FASTBOOT!
just plug your phone to your computer when its on and ready to use!
SRK will boot your phone in fastboot

EGOiST1991 said:
DUDE ! AGAIN! FOR THE SRK TOOL DONT!!!! GO IN FASTBOOT!
just plug your phone to your computer when its on and ready to use!
SRK will boot your phone in fastboot
Click to expand...
Click to collapse
Dude!!! read my reply again, I'm not in fastboot when running the srk tool or running the adb commands...
Skickat från min NEXT via Tapatalk

Leo_83 said:
Dude!!! read my reply again, I'm not in fastboot when running the srk tool or running the adb commands...
Skickat från min NEXT via Tapatalk
Click to expand...
Click to collapse
DUDE! then im sorry

quick update worked for me with srk tool!
im downloading now b560 via my phone official OTA! wuhu

EGOiST1991 said:
quick update worked for me with srk tool!
im downloading now b560 via my phone official OTA! wuhu
Click to expand...
Click to collapse
I hate you lol [emoji8] I'm going to try one last time otherwise I'm gonna try the custom rom based B386 Twisted Mate 8
Skickat från min NEXT via Tapatalk

maybe i can help you via teamviewer bro?

EGOiST1991 said:
maybe i can help you via teamviewer bro?
Click to expand...
Click to collapse
No I give up! I love this phone but damn it is complicated to flash roms. All other phones are simple.
Today I tried again, this time by manually testing some steps which I don't know if they are correct since no one seems to be able to answer me. Any way which ever twrp I flash that isn't the one I'm using for flashing B320 won't boot or won't wipe data.
First Attempt:
1. Change build.prop (C432)
2. Change oeminfo file (C432)
3. Change custom.bin (C432)
4. Flash insecure_boot_b560.img by @franzyroy
5. Flash twrp-3.0.3_EMUI5.0.img
6. Boot loop booting to TWRP so FAILED
Second Attempt:
1. Flash decrypted insecure_boot_B320.img
2. Flash TWRP_3.0.2-0_BLACK_BLUE_EMUI4.1.img
3. Wipe Data
4. Factory Reset
5. Flash insecure_boot_b560.img
6. Flash twrp-3.0.2-0-next-modaco-rc3-emui41.img as suggested by @franzyroy
6. Boot loop booting to TWRP so FAIL AGAIN.
Third Attempt:
1. Flash decrypted insecure_boot_b560.img
2. Flash TWRP_3.0.2-0_BLACK_BLUE_EMUI4.1.img
3. Try flashing supersu_v2.79_sr2.zip get error about mounting memory
4. Try flashing
update_full_hw_eu.zip get error 7
Fourth Attempt:
1. Flash decrypted insecure_boot_B320.img
2. Flash twrp-3.0.2-0-next.img
3. Successfully booted to TWRP (woho! Maybe just maybe...)
4. Wipe Data failed, can't mount memory *cry*
Fifth Attempt, let's go back:
1. Flash insecure_boot_b180.img
2. Flash TWRP-3.0.2-BLACK-BLUE_EMUI4.0.img
3. Boot loop booting into recovery so FAILED
F*ck it, went back to B320!
I really don't know what I'm doing any more lol. I guess the last thing could do is go completely stock again (unroot and lock bootloader) by dload(?), rebrand from AL10 to L29C432, update via OTA to nougat and then unlock bootloader and root again. I just feel it shouldn't be necessary and secondly I don't know how to go completely stock again [emoji13]

Leo_83 said:
No I give up! I love this phone but damn it is complicated to flash roms. All other phones are simple.
Today I tried again, this time by manually testing some steps which I don't know if they are correct since no one seems to be able to answer me. Any way which ever twrp I flash that isn't the one I'm using for flashing B320 won't boot or won't wipe data.
First Attempt:
1. Change build.prop (C432)
2. Change oeminfo file (C432)
3. Change custom.bin (C432)
4. Flash insecure_boot_b560.img by @franzyroy
5. Flash twrp-3.0.3_EMUI5.0.img
6. Boot loop booting to TWRP so FAILED
Second Attempt:
1. Flash decrypted insecure_boot_B320.img
2. Flash TWRP_3.0.2-0_BLACK_BLUE_EMUI4.1.img
3. Wipe Data
4. Factory Reset
5. Flash insecure_boot_b560.img
6. Flash twrp-3.0.2-0-next-modaco-rc3-emui41.img as suggested by @franzyroy
6. Boot loop booting to TWRP so FAIL AGAIN.
Third Attempt:
1. Flash decrypted insecure_boot_b560.img
2. Flash TWRP_3.0.2-0_BLACK_BLUE_EMUI4.1.img
3. Try flashing supersu_v2.79_sr2.zip get error about mounting memory
4. Try flashing
update_full_hw_eu.zip get error 7
Fourth Attempt:
1. Flash decrypted insecure_boot_B320.img
2. Flash twrp-3.0.2-0-next.img
3. Successfully booted to TWRP (woho! Maybe just maybe...)
4. Wipe Data failed, can't mount memory *cry*
Fifth Attempt, let's go back:
1. Flash insecure_boot_b180.img
2. Flash TWRP-3.0.2-BLACK-BLUE_EMUI4.0.img
3. Boot loop booting into recovery so FAILED
F*ck it, went back to B320!
I really don't know what I'm doing any more lol. I guess the last thing could do is go completely stock again (unroot and lock bootloader) by dload(?), rebrand from AL10 to L29C432, update via OTA to nougat and then unlock bootloader and root again. I just feel it shouldn't be necessary and secondly I don't know how to go completely stock again [emoji13]
Click to expand...
Click to collapse
Okay. I will try to guide you. Let's do it one by one. Bare with me. So are you in C432B320 right now? Are you able to load into the system?
Sent from my HUAWEI NXT-L29 using XDA Labs

Leo_83 said:
No I give up! I love this phone but damn it is complicated to flash roms. All other phones are simple.
Today I tried again, this time by manually testing some steps which I don't know if they are correct since no one seems to be able to answer me. Any way which ever twrp I flash that isn't the one I'm using for flashing B320 won't boot or won't wipe data.
First Attempt:
1. Change build.prop (C432)
2. Change oeminfo file (C432)
3. Change custom.bin (C432)
4. Flash insecure_boot_b560.img by @franzyroy
5. Flash twrp-3.0.3_EMUI5.0.img
6. Boot loop booting to TWRP so FAILED
Second Attempt:
1. Flash decrypted insecure_boot_B320.img
2. Flash TWRP_3.0.2-0_BLACK_BLUE_EMUI4.1.img
3. Wipe Data
4. Factory Reset
5. Flash insecure_boot_b560.img
6. Flash twrp-3.0.2-0-next-modaco-rc3-emui41.img as suggested by @franzyroy
6. Boot loop booting to TWRP so FAIL AGAIN.
Third Attempt:
1. Flash decrypted insecure_boot_b560.img
2. Flash TWRP_3.0.2-0_BLACK_BLUE_EMUI4.1.img
3. Try flashing supersu_v2.79_sr2.zip get error about mounting memory
4. Try flashing
update_full_hw_eu.zip get error 7
Fourth Attempt:
1. Flash decrypted insecure_boot_B320.img
2. Flash twrp-3.0.2-0-next.img
3. Successfully booted to TWRP (woho! Maybe just maybe...)
4. Wipe Data failed, can't mount memory *cry*
Fifth Attempt, let's go back:
1. Flash insecure_boot_b180.img
2. Flash TWRP-3.0.2-BLACK-BLUE_EMUI4.0.img
3. Boot loop booting into recovery so FAILED
F*ck it, went back to B320!
I really don't know what I'm doing any more lol. I guess the last thing could do is go completely stock again (unroot and lock bootloader) by dload(?), rebrand from AL10 to L29C432, update via OTA to nougat and then unlock bootloader and root again. I just feel it shouldn't be necessary and secondly I don't know how to go completely stock again [emoji13]
Click to expand...
Click to collapse
i made it like this:
SRK TOOL C432 cust
then install via TWRP c432b192 (just take the zip and install it with twrp 2.8.)
then let the update magic begin in the c432b192 rom with unlooked bootloader -worked good
maybe that helps you
oh btw now im using the frd-twrp and i CANT backup my rom... any solution for that?