So the easiest way to do this as I understand it is to use @somboons srk tool unfortunately I'm having trouble with adb.
Running the srk tool the process gets stuck on the command waiting for device
I have tried different adb/fastboot installers and when I run the adb devices command I always get returned "device number Offline"
http://cloud.tapatalk.com/s/58a18bc141157/IMG_20170213_113246.jpg
But funny enough running fastboot devices with phone in fastboot mode return correct respond and I can flash file via fastboot so I don't think it's the USB drives.
So I'm now trying to find a manual way to do it, searching for the past few days have lead me to the following, but I would like someone to confirm that this is the way to go:
1. Take oeminfo from srk tool folders and place it at
/dev/blocl/platform/hi_mci.0/by-name/oeminfo
2. Take custom.bin from srk tool folder and place it at
/data
3. Change build.prop file at /System
And changing the line
ro.build.display.id=NextL00C432B011 for C432
Additional questions I have is that currently am on C636B320 and if I restart my phone will it boot up if I change above thing?
Since I need to change the build.prop file I need to use a file browser/Explorer on the phone... Or is it possible to do the changes above from TWRP?
My ultimate goal is to go to C432B560.
System info:
Unlocked bootloader
Rooted
L29C900B320 (belive it was C636 update.img)
Phone was originally AL10
Computer info:
Windows 10
Skickat från min NEXT via Tapatalk
No one? Anyone? [emoji20]
Skickat från min NEXT via Tapatalk
dexz said:
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
Click to expand...
Click to collapse
I'll reply to you in this thread since my initially problem is connected to the question I have in this thread.
To answer your question my phone shows C900B320 same as @EGOiST1991 did. My issue is that I can't use adb commands which means I can't use the srk tool to rebrand. I belive that is why I cannot follow the guide stated in the other thread about updating to nougat. If you read op on this thread you see the issue I have, like you said one step at a time. My goal is to upgrade to nougat... I'm wondering if wouldn't be easier to go stock and update via official update and then root once on C432B560. But if I can get it to work with TWRP which always had been easier until now I would rather do that, then I don't need to redo as many steps.
PS. I appreciate if you point me in the correct direction.
Leo_83 said:
I'll reply to you in this thread since my initially problem is connected to the question I have in this thread.
To answer your question my phone shows C900B320 same as @EGOiST1991 did. My issue is that I can't use adb commands which means I can't use the srk tool to rebrand. I belive that is why I cannot follow the guide stated in the other thread about updating to nougat. If you read op on this thread you see the issue I have, like you said one step at a time. My goal is to upgrade to nougat... I'm wondering if wouldn't be easier to go stock and update via official update and then root once on C432B560. But if I can get it to work with TWRP which always had been easier until now I would rather do that, then I don't need to redo as many steps.
PS. I appreciate if you point me in the correct direction.
Click to expand...
Click to collapse
Ok. Let's settle your adb first because it's much easier having adb working for now and in the future.
1. Which adb version are you using? SRK tools adb should be fine. Make sure run SRK Tools as administrator.
2. Did you installed latest HiSuite (for latest debug driver)?
3. Did you tried different usb port/usb cable?
Sorry you have to do the checklist. Just bare with me on this.
Edit:
One more thing you can try. Plug in your phone to your computer. Make sure the usb debugging icon showing. In Developer Options, select "Revoke USB debugging authorisation" then press OK. Unplug the usb cable then replug it again. You should get message "Allow USB debugging". Tick Always allow and press OK. After that try the "adb devices" again. Hope this will solve your adb issue.
dexz said:
Ok. Let's settle your adb first because it's much easier having adb working for now and in the future.
1. Which adb version are you using? SRK tools adb should be fine. Make sure run SRK Tools as administrator.
2. Did you installed latest HiSuite (for latest debug driver)?
3. Did you tried different usb port/usb cable?
Sorry you have to do the checklist. Just bare with me on this.
Edit:
One more thing you can try. Plug in your phone to your computer. Make sure the usb debugging icon showing. In Developer Options, select "Revoke USB debugging authorisation" then press OK. Unplug the usb cable then replug it again. You should get message "Allow USB debugging". Tick Always allow and press OK. After that try the "adb devices" again. Hope this will solve your adb issue.
Click to expand...
Click to collapse
1. I have used minimal_adb_fastboot_v1.4 and also tried from the srk commadn folder, in both I have run adb kill-server and adb start-server and then adb devices but I always get respond "Device number Offline".
Yes I have run the tool as administrator but it always get stuck on "Waiting for device..."
2. HiSuite version: 5.0.1.300_OVE
3. Different cable and port
4. USB debugging enabled
I dont have that option in Developer Option
The only Revoke option there is when I search is the following
Leo_83 said:
1. I have used minimal_adb_fastboot_v1.4 and also tried from the srk commadn folder, in both I have run adb kill-server and adb start-server and then adb devices but I always get respond "Device number Offline". 
Yes I have run the tool as administrator but it always get stuck on "Waiting for device..."

2. HiSuite version: 5.0.1.300_OVE
3. Different cable and port
4. USB debugging enabled 
I dont have that option in Developer Option 
The only Revoke option there is when I search is the following
2. HiSuite version: 5.0.1.300_OVE
3. Different cable and port
4. USB debugging enabled
I dont have that option in Developer Option
Yes I have run the tool as administrator but it always get stuck on "Waiting for device..."

2. HiSuite version: 5.0.1.300_OVE
3. Different cable and port
4. USB debugging enabled 
I dont have that option in Developer Option 
The only Revoke option there is when I search is the following

Click to expand...
Click to collapse
Ok. I think that's the reason why your adb detect offline because of usb debugging authorisation issue. Maybe you can extract boot.img & recovery.img from update.app B320 and then flash it via fastboot. After that do factory reset. Backup if needed. After enter to the system. Enable developer option again then check if revoke usb debugging showing.
dexz said:
Ok. I think that's the reason why your adb detect offline because of usb debugging authorisation issue. Maybe you can extract boot.img & recovery.img from update.app B320 and then flash it via fastboot. After that do factory reset. Backup if needed. After enter to the system. Enable developer option again then check if revoke usb debugging showing.
Click to expand...
Click to collapse
That did the trick!!! Cheers!!!
Now shall we go back to the other thread?
Edit: So I felt adventures (I know I know ) and started trying to debrand, initially didn't get it to work but now I'm half way there...
I managed to flash oeminfo and custom.bin for C432 via srk tool when I look in About Phone the following is stated:
Model Number: NXT-L29
Build Number: NXT-C900B320 I believe it is because I haven't changed the build prop
Now to the "issue" when changing the oeminfo and custom.bin with the srk tool the phone did a factory reset and I now I see that in fastboot it states:
Phone Locked
FRP Locked
So this was what I was trying to avoid initially but since it happened I wonder which is the best way forward. Unlocking bootloader once again, installing TWRP and rooting or with the bootloader locked try to go completely stock and down to C432B192....?
Leo_83 said:
That did the trick!!! Cheers!!!
Now shall we go back to the other thread?
Edit: So I felt adventures (I know I know ) and started trying to debrand, initially didn't get it to work but now I'm half way there...
I managed to flash oeminfo and custom.bin for C432 via srk tool when I look in About Phone the following is stated:
Model Number: NXT-L29
Build Number: NXT-C900B320 I believe it is because I haven't changed the build prop
Now to the "issue" when changing the oeminfo and custom.bin with the srk tool the phone did a factory reset and I now I see that in fastboot it states:
Phone Locked
FRP Locked
So this was what I was trying to avoid initially but since it happened I wonder which is the best way forward. Unlocking bootloader once again, installing TWRP and rooting or with the bootloader locked try to go completely stock and down to C432B192....?
Click to expand...
Click to collapse
Glad you managed to get adb back.
Before you do anything please make sure FRP is unlock first (This step is very important before you go Nougat). In developer option under Enable Oem Unlocked is turn on and once you flashed oeminfo it will lock your phone again. Just unlock your Bootloader using SRK Tools. I assumed you have BL code right? Once you have Unlocked BL, Unlocked FRP, TWRP, Root & Debrand. Now you are ready to go Nougat. Report me back.
Good luck
dexz said:
Glad you managed to get adb back.
Before you do anything please make sure FRP is unlock first (This step is very important before you go Nougat). In developer option under Enable Oem Unlocked is turn on and once you flashed oeminfo it will lock your phone again. Just unlock your Bootloader using SRK Tools. I assumed you have BL code right? Once you have Unlocked BL, Unlocked FRP, TWRP, Root & Debrand. Now you are ready to go Nougat. Report me back.
Good luck
Click to expand...
Click to collapse
Before I do complete rebrand... Shouldn't I go to a C432 rom first otherwise I will get bootloop, because of incompatible rom and "model", right?
Sent from my NX507J using Tapatalk
Leo_83 said:
Before I do complete rebrand... Shouldn't I go to a C432 rom first otherwise I will get bootloop, because of incompatible rom and "model", right?
Click to expand...
Click to collapse
Yes. You should debrand first. I mean debrand should be done before going to Nougat.
dexz said:
Yes. You should debrand first.
Click to expand...
Click to collapse
Sorry I think I need step by step instructions now...
I have unlocked bootloader, TWRP for EMUI 4.1 is installed and I think I'm running C636B320 but it is shown as C900B320.
If I change build.prop to C432 I won't be able to boot up on my current C636B320 update.zip so I will download C432B320. And install it from TWRP 4.1 after changing build.prop or maybe do first hmmm...
An other option could be to change build.prop, get bootloop, go to fastboot flash TWRP 4.0 and then flash C432B192.
Which do you think is the better option going forward and keeping in mind I want to go to L29C432B560?
Sent from my NX507J using Tapatalk
Leo_83 said:
Sorry I think I need step by step instructions now...
I have unlocked bootloader, TWRP for EMUI 4.1 is installed and I think I'm running C636B320 but it is shown as C900B320.
If I change build.prop to C432 I won't be able to boot up on my current C636B320 update.zip so I will download C432B320. And install it from TWRP 4.1 after changing build.prop or maybe do first hmmm...
An other option could be to change build.prop, get bootloop, go to fastboot flash TWRP 4.0 and then flash C432B192.
Which do you think is the better option going forward and keeping in mind I want to go to L29C432B560?
Click to expand...
Click to collapse
I would suggest use C432B180/192 then in TWRP do format data, wipe (cache, dalvik, system and data) After that flash C432B180/192.zip then reboot to system. You can do debrand from here before going to b560. Once debrand. Go to https://forum.xda-developers.com/mate-8/general/how-to-install-nxt-l29c432b560-official-t3540042/ follow the steps.
PS: Remember build number must not be C900**** before proceed to B560 or else you end up become test-keys
dexz said:
I would suggest use C432B180/192 then in TWRP do format data, wipe (cache, dalvik, system and data) After that flash C432B180/192.zip then reboot to system. You can do debrand from here before going to b560. Once debrand. Go to https://forum.xda-developers.com/mate-8/general/how-to-install-nxt-l29c432b560-official-t3540042/ follow the steps.
PS: Remember build number must not be C900**** before proceed to B560 or else you end up become test-keys
Click to expand...
Click to collapse
Check! Here goes nothing... [emoji38] wish me luck [emoji12]
Sent from my NX507J using Tapatalk
Leo_83 said:
Check! Here goes nothing... [emoji38] wish me luck [emoji12]
Click to expand...
Click to collapse
Good luck :laugh:
dexz said:
Good luck [emoji23]
Click to expand...
Click to collapse
Haha to late... The phone won't boot into recovery after flashing TWRP 4.0 which is needed if I'm going to flash C432B180 or C432B192
Sent from my NX507J using Tapatalk
Leo_83 said:
Haha to late... The phone won't boot into recovery after flashing TWRP 4.0 which is needed if I'm going to flash C432B180 or C432B190
Click to expand...
Click to collapse
You can't used TWRP 4.0 because you are still in EMUI 4.1 . Try flashing TWRP 4.1 then install C432B180/B192
dexz said:
You can't used TWRP 4.0 because you are still in EMUI 4.1 . Try flashing TWRP 4.1 then install C432B180/B192
Click to expand...
Click to collapse
It's either C432B180 or C432B192?
Or both in sequence i.e first B180 and then B192?
Sent from my NX507J using Tapatalk
Leo_83 said:
It's either C432B180 or C432B192?
Or both in sequence i.e first B180 and then B192?
Click to expand...
Click to collapse
It's either one. If you can flash B192 then B192 it is.
dexz said:
I would suggest use C432B180/192 then in TWRP do format data, wipe (cache, dalvik, system and data) After that flash C432B180/192.zip then reboot to system. You can do debrand from here before going to b560. Once debrand. Go to https://forum.xda-developers.com/mate-8/general/how-to-install-nxt-l29c432b560-official-t3540042/ follow the steps.
PS: Remember build number must not be C900**** before proceed to B560 or else you end up become test-keys
Click to expand...
Click to collapse
Success!!!
I ddidn't need to change build.prop via srk tool after flashing B192 it already showed C432!!
I checked the updater and it shows B560, should I still do it via https://forum.xda-developers.com/mate-8/general/how-to-install-nxt-l29c432b560-official-t3540042/
I goes it will be harder to get rooted if I first go to B560 instead of following sillanwali guide
Leo_83 said:
Success!!! 
I ddidn't need to change build.prop via srk tool after flashing B192 it already showed C432!!
I checked the updater and it shows B560, should I still do it via https://forum.xda-developers.com/mate-8/general/how-to-install-nxt-l29c432b560-official-t3540042/
I ddidn't need to change build.prop via srk tool after flashing B192 it already showed C432!!
I checked the updater and it shows B560, should I still do it via https://forum.xda-developers.com/mate-8/general/how-to-install-nxt-l29c432b560-official-t3540042/

I goes it will be harder to get rooted if I first go to B560 instead of following sillanwali guide
Click to expand...
Click to collapse
Thats great. :good:
It's depend what method you want to try. you can try to follow some of the thread here
Good luck
Related
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?
[FRD_L09]
Ok, here's the deal.
I recently got myself an unofficial version of TWRP.
Installed it, fine. I then downloaded SuperSu .zip and flashed it.
Tried booting my phone; nothing. OEM was unlocked, and i already made
a twrp backup, before making any changes. I am now stuck with a phone
that wont boot up (nothing happens upon boot), and FRP being locked in bootloader.
I realised some ROMs require a custom version of TWRP, which i cannot flash as FRP is locked
in boot loader, and i dont have access to "USB Debugging" since it wont boot. I tried installing
several different ROMs, including LineAge, CM14 and some others. No luck.
I also went to the manufacturer website (Huawei) to see if they would help me with this issue; no luck. Please help me restore
my device to its original state. Thanks a lot.
Rommco05 said:
Enter to fastboot (plug device to USB and turn on with vol down + on/off) and whats status is your phone? (...fastboot devices...)
Click to expand...
Click to collapse
It shows up in fastboot, but FRP is locked. I guess FRP is usb debugging, since i cant make any changes.
Rommco05 said:
Try reinstal HiSuite (latest version) and after type adb command in fastboot: fastboot devices
Click to expand...
Click to collapse
yeah, it shows up in fastboot when i do devices command. i have latest hisuite.
but when i try to flash something, it doesnt allow.
gives:
73QDU16A20004317 fastboot
Rommco05 said:
You allready try install MM via dload?
Click to expand...
Click to collapse
I tried, but idk why it didnt find my update.app thing on my sd card. is it because i have twrp flashed?
Rommco05 said:
I think no, can you enter to recovery? If no flash recovery via HuaweiMultitool https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923
Click to expand...
Click to collapse
How can i use it?
Also it is russian.
Rommco05 said:
Try another version that isnt russian (I know that) and it is easy to use, just follow steps
Click to expand...
Click to collapse
ok, ill try that.
Rommco05 said:
Try another version that isnt russian (I know that) and it is easy to use, just follow steps
Click to expand...
Click to collapse
No luck. Remmember, usb debugging cant be enabled...
What is the best way to root this device with the stock firmware, the latest SuperSU.zip, Magisk, other?
loner. said:
What is the best way to root this device with the stock firmware, the latest SuperSU.zip, Magisk, other?
Click to expand...
Click to collapse
I'm using bad boys Rom atm, it works pretty well assuming your in the US
ticklemepinks said:
I'm using bad boys Rom atm, it works pretty well assuming your in the US
Click to expand...
Click to collapse
is that a pre-rooted ROM ?
just flash and done?
AllGamer said:
is that a pre-rooted ROM ?
just flash and done?
Click to expand...
Click to collapse
yes
Unlock bootloader via HTCDev (Select all other models)
Flash TWRP
Flash Magisk
Profit
Galactus said:
Unlock bootloader via HTCDev (Select all other models)
Flash TWRP
Flash Magisk
Profit
Click to expand...
Click to collapse
And store stock recovery matching firmware mid/cid/ version somewhere for later OTA, right? This still needed for official ota, isn't it?
tbalden said:
And store stock recovery matching firmware mid/cid/ version somewhere for later OTA, right? This still needed for official ota, isn't it?
Click to expand...
Click to collapse
No clue, I backed up the recovery by booting TWRP first rather than flashing but I have no idea what mid/cid is lol, I haven't used a HTC device in 4 years
Galactus said:
No clue, I backed up the recovery by booting TWRP first rather than flashing but I have no idea what mid/cid is lol, I haven't used a HTC device in 4 years
Click to expand...
Click to collapse
Can anyone provide a sample /command line for booting TWRP in MS Windows to back up before flashing?
loner. said:
Can anyone provide a sample /command line for booting TWRP in MS Windows to back up before flashing?
Click to expand...
Click to collapse
I just did
fastboot boot twrp.img
Galactus said:
I just did
fastboot boot twrp.img
Click to expand...
Click to collapse
Simple and all these years messing with fasboot I never even thought of it.
loner. said:
Simple and all these years messing with fasboot I never even thought of it.
Click to expand...
Click to collapse
Happens to all of us lol
Did you guys find HTC drivers for ADB to get USB debugging to work?
My fastboot (Google's as well as HTC's) says "Waiting for device."
"fastboot.exe devices" sees no device, but the Win10_x64 PC sees it. I have enabled developer mode, selected "Enable Bootloader Unlock" and "Enable USB Debugging." Usually this is all I need.
BoulderGeek said:
Did you guys find HTC drivers for ADB to get USB debugging to work?
My fastboot (Google's as well as HTC's) says "Waiting for device."
"fastboot.exe devices" sees no device, but the Win10_x64 PC sees it. I have enabled developer mode, selected "Enable Bootloader Unlock" and "Enable USB Debugging." Usually this is all I need.
Click to expand...
Click to collapse
i get the token but my computer keep copying everything
BoulderGeek said:
Did you guys find HTC drivers for ADB to get USB debugging to work?
My fastboot (Google's as well as HTC's) says "Waiting for device."
"fastboot.exe devices" sees no device, but the Win10_x64 PC sees it. I have enabled developer mode, selected "Enable Bootloader Unlock" and "Enable USB Debugging." Usually this is all I need.
Click to expand...
Click to collapse
If you already have HTC sync manager, uninstall it and download and install the updated one. This should update your HTC drivers.
tbalden said:
And store stock recovery matching firmware mid/cid/ version somewhere for later OTA, right? This still needed for official ota, isn't it?
Click to expand...
Click to collapse
TWRP can install the system part of an official OTA - the firmware portion just has to be pre-extracted and flashed manually.
Knuckle Head Here
Hello all.
I'm waiting for my HTC U11 (my first HTC phone) to be delivered.
I'm new to this and reading through the posts I'm somewhat overwhelmed.
It would be great to have a sticky "fastboot for dummies" for HTC phones for those like me that are clueless.
Download mode
Bootloader Mode
Fastboot Mode
Flash
Reboot and on and on.
Holy Smoke!
Wouldn't have to be an encyclopedia (I see there are many) just something explaining usage for the most common commands.
I hope this is the correct place for this post, if not, apologies in advance.
Thanks,
Scooter
Scoot805 said:
Hello all.
I'm waiting for my HTC U11 (my first HTC phone) to be delivered.
I'm new to this and reading through the posts I'm somewhat overwhelmed.
It would be great to have a sticky "fastboot for dummies" for HTC phones for those like me that are clueless.
Download mode
Bootloader Mode
Fastboot Mode
Flash
Reboot and on and on.
Holy Smoke!
Wouldn't have to be an encyclopedia (I see there are many) just something explaining usage for the most common commands.
I hope this is the correct place for this post, if not, apologies in advance.
Thanks,
Scooter
Click to expand...
Click to collapse
it's not too difficult...what are you trying to do? these are the minimum steps for root:
1. create account @ https://www.htcdev.com/
2. follow steps to unlock bootloader, choose "all other supported models"
3. install fastboot either from step 4 or from HERE
4. continue to follow steps until bootloader is unlocked, it will factory reset the device
5. boot into download mode, flash twrp, use cmd fastboot flash recovery nameofrecovery.img
6. boot to bootloader, then recovery
7. I would advise u to keep read only for /system, then immediately do a system & boot img backup
8. flash/install either supersu or magisk (my preference)
Captain_Throwback said:
TWRP can install the system part of an official OTA - the firmware portion just has to be pre-extracted and flashed manually.
Click to expand...
Click to collapse
Does your TWRP permit booting to TWRP from stock aboot/recovery (so that stock can be backed up).
hgoldner said:
Does your TWRP permit booting to TWRP from stock aboot/recovery (so that stock can be backed up).
Click to expand...
Click to collapse
That's not a TWRP function - it's dependent on the bootloader. And yes, fastboot boot works fine on the U11 from bootloader mode.
GAH! I'm an idiot. RTFM, I should have done, to quote Yoda.
Totally failed to see:
Required Resources
Please make sure all items are installed and up to date.
Google Android SDK zip:
http://developer.android.com/sdk/index.html
Java Runtime Environment:
http://java.com
HTC Sync Manager:
http://www.htc.com/hsm
Thank you, @Loner!
I am coming from an LG, and haven't had an HTC since the Thunderbolt, so I am rusty.
OK, now my fastboot works!
Hi I just bought my honor 8, i unlocked my bootloader, then tried flashing twrp, it said it worked, but it just went to EMUI recovery. I must of flashed the wrong one, it was the american one from twrp.me. I am on emui 5.0. So then i went to developer option and accidently clicked revert to default settings, which turned off my oem unlock. so this turned FRP lock back on. I had the bootloader still unlocked so i tried flashing surdas twrp this time, and it failed. so i rebooted my phone and it went to the recovry and said it got seriously data corrupt or something and said to repair so i did, then i rebooted and it went to setup. but now it wont let me get through the setup because i cant type.. it just brings up google voice typing. So somethings messed up.
Model is FRD-L14
Emui 5.0
the bootloader is currently locked.
FRP lock is on.
I can get to fastboot, recovery and it boots up to setup.
Any help would be greatly appreciated! I don;t know how i can fix this.
Is there any way i can flash stock rom and recovery in like download mode or something?
I have simlar issue to this https://forum.xda-developers.com/honor-8/help/help-keyboard-google-voice-t3629372
Rommco05 said:
Big mistake and double post... downgrade
Click to expand...
Click to collapse
I dont understand how I downgrade. I have a locked bootloader and no custom recovery.
Use a sdcard and create a directory "dload". In this directory first place the rollback UPDATE.APP. Use the 3-button combo to enter dload mode. Then once done change that UPDATE.APP with the B130 (EMUI 4.1) UPDATE.APP of your device. Again enter dload mode and you should have successfully downgraded.
You can now upgrade from software updater to EMUI 5.0.
Anonshe said:
Use a sdcard and create a directory "dload". In this directory first place the rollback UPDATE.APP. Use the 3-button combo to enter dload mode. Then once done change that UPDATE.APP with the B130 (EMUI 4.1) UPDATE.APP of your device. Again enter dload mode and you should have successfully downgraded.
You can now upgrade from software updater to EMUI 5.0.
Click to expand...
Click to collapse
Where do I get the rollback update.app? I'm model FRD-L14 but theirs so many versions in firmware finder.
Do i have to extract the UPDATE.APP file into the dload folder?
OathYvne said:
Where do I get the rollback update.app? I'm model FRD-L14 but theirs so many versions in firmware finder.
Do i have to extract the UPDATE.APP file into the dload folder?
Click to expand...
Click to collapse
http://download-c1.huawei.com/download/downloadCenter?downloadId=92790&version=363861&siteCode=pt
Download the rollback from above and after extraction copy the UPDATE.APP file into the dload folder. Once done replace this with the B120/B130 UPDATE.APP.
You don't need to extract the UPDATE.APP but extract the update.zip which would give you the UPDATE.APP to be copied into the dload folder.
Anonshe said:
http://download-c1.huawei.com/download/downloadCenter?downloadId=92790&version=363861&siteCode=pt
Download the rollback from above and after extraction copy the UPDATE.APP file into the dload folder. Once done replace this with the B120/B130 UPDATE.APP.
You don't need to extract the UPDATE.APP but extract the update.zip which would give you the UPDATE.APP to be copied into the dload folder.
Click to expand...
Click to collapse
Okay thanks for explaining it well for me :]. One last question (hopefully lol) where do i get the b120/b130 update app for my frd-L14 model? thanks!
OathYvne said:
Okay thanks for explaining it well for me :]. One last question (hopefully lol) where do i get the b120/b130 update app for my frd-L14 model? thanks!
Click to expand...
Click to collapse
For your model the EMUI 4.1 version is B162 which you can download from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1201/g88/v66294/f1/full/update.zip
Anonshe said:
For your model the EMUI 4.1 version is B162 which you can download from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1201/g88/v66294/f1/full/update.zip
Click to expand...
Click to collapse
Thanks alot man :].
once i do all of this, and then after i update my emui to 5.0. How exactly do I properly install twrp? lol.
I figured out how to unlock my bootloader, but i don't know how to install the proper twrp version without bricking my device. Then i'd be installing a lineage os rom after i have twrp, which i know how to do from using my galaxy s4 .
OathYvne said:
Thanks alot man :].
once i do all of this, and then after i update my emui to 5.0. How exactly do I properly install twrp? lol.
I figured out how to unlock my bootloader, but i don't know how to install the proper twrp version without bricking my device. Then i'd be installing a lineage os rom after i have twrp, which i know how to do from using my galaxy s4 .
Click to expand...
Click to collapse
Once you are on emui 5.0, make sure you enable developer options and keep the oem unlock option ON. Then enable usb debugging and reboot to fastboot using your PC and typing "adb reboot fastboot".
Once in fast boot mode, first unlock your boot loader using "fastboot oem unlock CODE". This will prompt for a factory reset and once done repeat the above in developer options and enter fast boot mode again. You can simply type "fastboot flash recovery /path/to/recovery.img" where the recovery.img is the one you download from https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Voila you have successfully flashed twrp and now can flash whichever rom you want.
Anonshe said:
Once you are on emui 5.0, make sure you enable developer options and keep the oem unlock option ON. Then enable usb debugging and reboot to fastboot using your PC and typing "adb reboot fastboot".
Once in fast boot mode, first unlock your boot loader using "fastboot oem unlock CODE". This will prompt for a factory reset and once done repeat the above in developer options and enter fast boot mode again. You can simply type "fastboot flash recovery /path/to/recovery.img" where the recovery.img is the one you download from https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Voila you have successfully flashed twrp and now can flash whichever rom you want.
Click to expand...
Click to collapse
Thanks so much!
Anonshe said:
Once you are on emui 5.0, make sure you enable developer options and keep the oem unlock option ON. Then enable usb debugging and reboot to fastboot using your PC and typing "adb reboot fastboot".
Once in fast boot mode, first unlock your boot loader using "fastboot oem unlock CODE". This will prompt for a factory reset and once done repeat the above in developer options and enter fast boot mode again. You can simply type "fastboot flash recovery /path/to/recovery.img" where the recovery.img is the one you download from https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Voila you have successfully flashed twrp and now can flash whichever rom you want.
Click to expand...
Click to collapse
I've come into a problem. I've installed twrp and everything, but now im trying to flash a lineageos rom. when i try to wipe and format the data it says it failed: failed to mount /data device or resource busy unable to mount storage.
I went into mount and i have cache, vendor, and micro sdcard selected. also "mount system partition read-only" selected aswell. my storage selected says 0 MB.
Any idea what to do?
Rommco05 said:
Which twrp u flash?
Click to expand...
Click to collapse
https://forum.xda-developers.com/honor-8/development/twrp-t3566563 this one
OathYvne said:
https://forum.xda-developers.com/honor-8/development/twrp-t3566563 this one
Click to expand...
Click to collapse
Make sure you turn off FRP lock.
If you have FRP locked it is because you didn't enable OEM Unlock in EMUI 4.1
Read https://forum.xda-developers.com/showpost.php?p=71618439&postcount=275 and the subsequent posts for clarity.
Anonshe said:
If you have FRP locked it is because you didn't enable OEM Unlock in EMUI 4.1
Read https://forum.xda-developers.com/showpost.php?p=71618439&postcount=275 and the subsequent posts for clarity.
Click to expand...
Click to collapse
I fixed the issue. FRP was already unlocked. But I just advance wiped the data on those and it fixed the issue. Thanks man. Do you know what the most stable 7.1.2 ROM is? Cause I just used the lineageos 14.1 one and it randomly reboots on me when I have music playing, actually its just random in general.
OathYvne said:
I fixed the issue. FRP was already unlocked. But I just advance wiped the data on those and it fixed the issue. Thanks man. Do you know what the most stable 7.1.2 ROM is? Cause I just used the lineageos 14.1 one and it randomly reboots on me when I have music playing, actually its just random in general.
Click to expand...
Click to collapse
Try RR.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
Try RR.
Click to expand...
Click to collapse
Carbon is my choice
gopinaidu77 said:
Carbon is my choice
Click to expand...
Click to collapse
Awesome ROM there.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
Awesome ROM there.
Click to expand...
Click to collapse
Yeah it is
Anonshe said:
If you have FRP locked it is because you didn't enable OEM Unlock in EMUI 4.1
Read https://forum.xda-developers.com/showpost.php?p=71618439&postcount=275 and the subsequent posts for clarity.
Click to expand...
Click to collapse
I have come into a bit of a problem. I turned off or unlocking in developer options, then I rebooted my phone and it just bootlooped. So I did the thing you told me to do before with the roll back and the 4.1 emui. That all went fine, but after it finished installing 4.1 and restarted it's in bootloops still :/
So I purchased a tmobile op8 and it arrived yesterday, after setting up the phone and network unlocking (which happened basically instantaneously after applying for it which i found odd), I am currently trying to unlock bootloader in the hopes of converting it to the international firmware. I am on software version 11.0.5.7.IN55CB
The problem I am facing is that whenever i try to do "adb devices" while the phone is powered on it works and lists it, but when the phone is in fastboot mode it does not list the device. Also when i do "fastboot oem get_unloock_code" it gets stuck at waiting for devices. I have read through numerous posts both here and on the op forums talking about this and some listed solutions such as going into windows optional updates and updating google bootloader or something, while others said to check that bootloader is unlocked (i did both and didnt work). Any tips? Also, could someone please link to the correct adb and driver downloads as I am getting mixed results when searching which is the correct download.
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Thanks, worked like a charm. Now to wait 7 business days fml
if you just want the bootloader unlocked there's another way to do it instantly using EDL it's how I unlocked mine , instructions and files are here.. only works on Android 11 btw https://androidfilehost.com/?fid=7161016148664833753 if you really don't feel like installing edl and what not there is a Linux live distro that's already ready to go on the edl GitHub page you can download but just forewarning it's extremely glitchy and not used friendly lol if you need help , I can help you tho just lmk
PrivyetCyka said:
if you just want the bootloader unlocked there's another way to do it instantly using EDL it's how I unlocked mine , instructions and files are here.. only works on Android 11 btw https://androidfilehost.com/?fid=7161016148664833753 if you really don't feel like installing edl and what not there is a Linux live distro that's already ready to go on the edl GitHub page you can download but just forewarning it's extremely glitchy and not used friendly lol if you need help , I can help you tho just lmk
Click to expand...
Click to collapse
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
DamianF7 said:
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
Click to expand...
Click to collapse
i have t-m version and i have converted it to international software firmware also gets changed but by your self you won't be able to get 2 sim support because there is only one imei in phone. all the rom's work exacly the same as they do on global version not a single difference currently running a12 aex rom no problems at all
DamianF7 said:
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
Click to expand...
Click to collapse
don't forget to backup your persist.img there is some % chance it may get lost and you will have to recalibrate firngerprint sensor also back up the modem.img from twrp beacause that's has imei of your phone and if somehow you get your phone hardbricked that would be nice thing to have as a peace of mind
d.tat said:
don't forget to backup your persist.img there is some % chance it may get lost and you will have to recalibrate firngerprint sensor also back up the modem.img from twrp beacause that's has imei of your phone and if somehow you get your phone hardbricked that would be nice thing to have as a peace of mind
Click to expand...
Click to collapse
Can this be done without TWRP or does this have to be done after I root?
DamianF7 said:
Can this be done without TWRP or does this have to be done after I root?
Click to expand...
Click to collapse
you can backup persist without twrp. i'm sure modem could be backed up without twrp too but that's how i did it even tho i did not need persist nor modem image but i would suggest you do it anyways just to be safe booting into twrp in not hard at all you have to do is go info fastboot and through adb file boot into recovery ( fastboot boot "recovery" ) device will reboot in twrp and from there you just backup persist and modem take that file and save it on your computer
also important note for android 10 use twrp 3.4 and for android 11 use 3.6 and most importantly if you read the instructions on converting to global or installing twrp or custom rom carefully it will work 100% i was lazy and did it old way i used to do it on some other android phones and bricked few times but it was all good with msm tool you could restore phone from almost every state that's what made oneplus great
DamianF7 said:
Can this be done without TWRP or does this have to be done after I root?
Click to expand...
Click to collapse
no root needed to install or boot into twrp
d.tat said:
you can backup persist without twrp. i'm sure modem could be backed up without twrp too but that's how i did it even tho i did not need persist nor modem image but i would suggest you do it anyways just to be safe booting into twrp in not hard at all you have to do is go info fastboot and through adb file boot into recovery ( fastboot boot "recovery" ) device will reboot in twrp and from there you just backup persist and modem take that file and save it on your computer
also important note for android 10 use twrp 3.4 and for android 11 use 3.6 and most importantly if you read the instructions on converting to global or installing twrp or custom rom carefully it will work 100% i was lazy and did it old way i used to do it on some other android phones and bricked few times but it was all good with msm tool you could restore phone from almost every state that's what made oneplus great
Click to expand...
Click to collapse
Ok, thanks for clarification
FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Ive run into an issue with edl mode and you seem knowledgeable. I tried to flash the international firmware with an unlocked bootloader but it turned out to be an older build and now my phone is in crash dump mode. I planned on using msmtool to downgrade to android 10 and just restart but my phone isnt detected by my pc even though i have the qualcomm drivers installed. Any tips?
edit: btw can still access fastboot mode (download mode)
so phone is recognized in fastboot but not as qhusnhub or whatever its supposed to be, its just called oneplus android bootloader interface
DamianF7 said:
Ive run into an issue with edl mode and you seem knowledgeable. I tried to flash the international firmware with an unlocked bootloader but it turned out to be an older build and now my phone is in crash dump mode. I planned on using msmtool to downgrade to android 10 and just restart but my phone isnt detected by my pc even though i have the qualcomm drivers installed. Any tips?
edit: btw can still access fastboot mode (download mode)
so phone is recognized in fastboot but not as qhusnhub or whatever its supposed to be, its just called oneplus android bootloader interface
Click to expand...
Click to collapse
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery. Make sure you put it in your fastboot/platform-tools folder.
2. Flash that recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery lineage-18.1-20211218-recovery-instantnoodle.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Make sure you're plugged in and use this command on your PC. "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
FoxyDrew said:
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery.
2. Flash recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery NAMEOFFILE.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Use this command "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
Click to expand...
Click to collapse
Thanks for the reply man. Believe it or not this is exactly what I did lol. Got it working again and am now rooted on international oos 11.
FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Just wanted to say that this solved my issue of not being able to make it past the reboot into fastboot when flashing from TMo to Global using the flash-all.bat guides. I ran the batch file on a newly MSM'd 10.5.22 and when it got stuck at "waiting for device" I followed these steps and as soon as the driver was installed the batch file kicked back in and finished the flashing. Cheers!
SilverZero said:
Just wanted to say that this solved my issue of not being able to make it past the reboot into fastboot when flashing from TMo to Global using the flash-all.bat guides. I ran the batch file on a newly MSM'd 10.5.22 and when it got stuck at "waiting for device" I followed these steps and as soon as the driver was installed the batch file kicked back in and finished the flashing. Cheers!
Click to expand...
Click to collapse
Glad you got it man, worth all the trouble to get to a clean version of OOS without T-MO's junk and spying xD
FoxyDrew said:
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery. Make sure you put it in your fastboot/platform-tools folder.
2. Flash that recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery lineage-18.1-20211218-recovery-instantnoodle.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Make sure you're plugged on and use this command on your PC. "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
Click to expand...
Click to collapse
Thanks SO MUCH for this!! This is the only thing that allowed me to get into EDL Mode. I'm a bit stuck using MSM though. It shows my device as connected, but when I click the "Target" dropdown O2 is not an option. The only option I see is TMO. Any ideas?
UPDATE: i was able to get MSM going. Selecting the target was not needed, just needed to reboot the phone into EDL again and quickly press Start.
I'm back to stock now and just unlocked my bootloader again.
I now have a follow up question: My goal is to install Pixel Experience on my OPO8. Do I need to flash the Global ROM first or can I go straight into Pixel Experience?
UPDATE 2: no matter what I try flashing to my device I always end up getting "not allowed" errors with the critical partition. I've done the fresh MSM process three times already and always end up hitting these critical partition errors when trying to flash the global rom (or any other rom for that matter). any ideas?
nmuntz said:
Thanks SO MUCH for this!! This is the only thing that allowed me to get into EDL Mode. I'm a bit stuck using MSM though. It shows my device as connected, but when I click the "Target" dropdown O2 is not an option. The only option I see is TMO. Any ideas?
UPDATE: i was able to get MSM going. Selecting the target was not needed, just needed to reboot the phone into EDL again and quickly press Start.
I'm back to stock now and just unlocked my bootloader again.
I now have a follow up question: My goal is to install Pixel Experience on my OPO8. Do I need to flash the Global ROM first or can I go straight into Pixel Experience?
UPDATE 2: no matter what I try flashing to my device I always end up getting "not allowed" errors with the critical partition. I've done the fresh MSM process three times already and always end up hitting these critical partition errors when trying to flash the global rom (or any other rom for that matter). any ideas?
Click to expand...
Click to collapse
Do you have a T-Mobile device? If so you SHOULD be selecting "TMO" from the dropdown in MSM. Not O2 or leaving it blank. If you don't have a T-Mobile device, your using the wrong MSM tool as TMO shouldn't be an option.
Did you unlock your bootloader after MSMing back to stock? MSM Tool will automatically lock your bootloader. Also what recovery are you using to try to flash ROMs?
Also PixelExperience is dead for op8 it stopped getting updates. I'd recommend HavocOS for a "Pixel Experience". Also a well polished ROM in general.
FoxyDrew said:
Do you have a T-Mobile device? If so you SHOULD be selecting "TMO" from the dropdown in MSM. Not O2 or leaving it blank. If you don't have a T-Mobile device, your using the wrong MSM tool as TMO shouldn't be an option.
Did you unlock your bootloader after MSMing back to stock? MSM Tool will automatically lock your bootloader. Also what recovery are you using to try to flash ROMs?
Also PixelExperience is dead for op8 it stopped getting updates. I'd recommend HavocOS for a "Pixel Experience". Also a well polished ROM in general.
Click to expand...
Click to collapse
I'm pretty sure that this is a T-Mobile device. It registers as IN2017 which matches the description of the phone I bought off amazon but not exactly sure how else can i verify this.
I did unlock the bootloader after MSMing back to stock. One thing I noticed is that the stock image that MSM flashed has Sprint branding and not T-Mobile. maybe i'm using the wrong MSM tool? I'm using the one from this guide
I just re-did MSM; this time selecting TMO and I still got Sprint branding. is this expected?
I've been trying with multiple recoverys: the stock one, TWRP and the one that pixelexperience had. The LineageOS one you provided I only used for doing the ADB thing to boot into EDL. What recovery do you recommend I use?
I did read about PixelExperience being dead so downloaded Havoc.
can you please confirm if I should be flashing the Global ROM before flashing HavocOS? regarding the critical partition errors any ideas whats causing those?
last question is regarding adb/fastboot - been reading different things about what version to use. been doing all my last experiments using the ones from https://developer.android.com/studio/releases/platform-tools but got the same results. sorry to spam you with so many questions - appreciate your help!
nmuntz said:
I'm pretty sure that this is a T-Mobile device. It registers as IN2017 which matches the description of the phone I bought off amazon but not exactly sure how else can i verify this.
I did unlock the bootloader after MSMing back to stock. One thing I noticed is that the stock image that MSM flashed has Sprint branding and not T-Mobile. maybe i'm using the wrong MSM tool? I'm using the one from this guide
I just re-did MSM; this time selecting TMO and I still got Sprint branding. is this expected?
I've been trying with multiple recoverys: the stock one, TWRP and the one that pixelexperience had. The LineageOS one you provided I only used for doing the ADB thing to boot into EDL. What recovery do you recommend I use?
I did read about PixelExperience being dead so downloaded Havoc.
can you please confirm if I should be flashing the Global ROM before flashing HavocOS? regarding the critical partition errors any ideas whats causing those?
last question is regarding adb/fastboot - been reading different things about what version to use. been doing all my last experiments using the ones from https://developer.android.com/studio/releases/platform-tools but got the same results. sorry to spam you with so many questions - appreciate your help!
Click to expand...
Click to collapse
I've never seen that MSM tool, but the one I use doesn't have any Sprint files at all. Not sure where you found that MSM but use this one for future reference.
No you don't need to flash global before a ROM.