Hey all- after noticing my Netflix wouldn't work despite being a WW plastered phone, I discovered that my phone was actually a flashed CN version. I noticed that I can't receive updates- security or otherwise, which was a big motivating factor for me to try and fix it.
Eventually, I posted on Reddit because I was fed up
My build is (was) - WW_16.0650.1908.12_0
One dude sent me to this video- and since I have dealt with rooting before on my Nexus 4 I decided to try it out.
"
ASUS ROG 2 FULLY CONVERTED GLOBAL ROM WITH WORKING THEMES AND UPDATES"
I can't post links because my account is currently too new.
I followed the guide exactly, but when I got to the part where it said to use ADB, my attempt to boot the rootww190812.img failed- someone said to try on B instead, that also failed. It said it "failed to load/authenticate boot image.
From now it has been bootlooping into the Qualcomm
"qualcomm crash dump mode"
"waiting for flashing ramdump"
And I can not boot the device. I can still reach Fastboot, but that is all.
How can I fix my phone- preferably including continuing the boot process but at this point i'd be happy just to have a working phone again.
Edit: I have found factory reset- but i'm not sure if I should do it, or if I risk simply undoing and having to re-do the initial global reflash.
Edit 2: factory reset says WW_I001D and says it will go back to 1908.12. it should be safe I assume-
Edit 3: changing back to A allowed it to boot without factory reset- but it still won't root, build is now WW_16.0640.1908.12_0
https://forum.xda-developers.com/rog-phone-2/how-to/guide-to-check-change-fingerprint-cn-to-t4002279
This guide ended up helping me- I got it fixed, delete this post if you want.
Damn, it's been a while since I was here. Back then it was mostly about Windows PDAs.
Disclaimer:
Your warranty after this process is void and your phone will tell you it can not be trusted because it's unlocked.
This is what worked for me. I did it on Windows 10. I just went through the process and it was a bit of mixing and matching various guides.
I'm not your tech support, the only one responsible for following this is you.
If any part of this guide doesn't work for you: too bad. Maybe Google or other users can help you with your problem.
Needed:
An internet-enabled PC
Huawei P10 Lite phone
USB to Micro-USB cable
HiSuite https://consumer.huawei.com/en/support/hisuite/
DC-Unlocker (comes with abd & fastboot) https://www.dc-unlocker.com/
Optional: Huawei Driver Tools https://mega.nz/file/qrpBUIKA#zaI8Th0ovgyK48VzFUFAzMNWF2r_R12lNc-uJZsIx4w
Note: I recommend not to buy credits until you've come to the part in my guide which says buy credits.
Install HiSuite
Unzip and install HiSuite on your PC
Start it at the end of the installation (it should show a button with "Start")
Connect the phone to your computer with the USB cable and follow the instructions in HiSuite to install HiSuite on your phone
At the bottom of the (Windows) HiSuite there's an option to do a System Upgrade, mine had the option to install an older version (Android 7 with EMUI 5.1) Install this. (This will take some time)
Note: I've read that some people couldn't downgrade because of modern security fixes. It's possible I didn't run the latest updates, but as far as I'm aware everything was up to date.
The following part might be annoying because HiSuite tries to connect to the phone. I uninstalled it at this point, but I had the Driver Tools installed (and did the Install within said tools).
Phone
Once the phone restarted, go through the set-up as quickly as possible (skip WiFi-setup, decline all optional things and skip account creation)
Go to Settings > System > About Phone > Keep tapping the "Build Number" until you're told you're a developer
Find the developer options (Usually in Settings > System and enable USB/ADB debugging
Open the telephone app and type: *#*#2846579#*#* (it should open a menu automatically after the last *)
Click Background Settings > USB Port Settings and select Manufacture Mode
Once Manufacture Mode is selected, leave the phone untouched
DC-Unlocker, part 1
Unzip the contents of the DC-unlocker zip
Start dc-unlocker2client.exe
In the top left, under "Select manufacturer" change "Huawei modems" to "Huawei phones"
Click the button with the magnifying glass, if you did the previous step hovering should say "Detect phone" on hover
Example out put (this might differ for you, but triple-check a port is detected):
Code:
DC - Unlocker 2 Client 1.00.1431
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM3
Model : Huawei HiSilicon Kirin Android phone
Serial NR. : [redacted]
Firmware : System 5.1.0.78(0VVV)
DC-Unlocker, part 2
Check again if a model and port is shown in both the output and above the big buttons.
In the top right, click About > Buy Credits
DC-Unlocker site
Select your payment processor
By default it creates a new account, unless you've used this service before, you probably want to keep it this way.
Fill in a username and an email address
You need 4 credits (€4 for me) at the time of writing this, but do check the link "How much do I need?"
Hit confirm and go through the payment process, wait until everything is processed (if you use a script blocker, you might want to temporarily disable it).
At the end you should get confirmation page with your username, a password and 4 credits. (Username and password will be mailed too.)
DC-Unlocker, part 3
Go back to DC-Unlocker
In the top right, click "Server" and enter the details you've gotten
Click "Check login" and see if the output window shows your username and the credits you have left (which should be 4 at the time of writing)
In the top right, click "Unlocking" and then click "Read bootloader code"
The output should show you the bootloader code once it's done. Copy this to a textfile and save it (and keep it in the memory).
You can close DC unlocker once you've saved the code.
Don't be lazy and try to copy/paste the commands following in the next section, since you want to keep the code in your memory, as seen in step 6. Besides, I'll show you some shortcuts anyway! Keep in mind that our example code is 1111222233334444 (yours most likely isn't, mine sure wasn't) and that [tab] will mean the tab-key on your keyboard.
PowerShell/Command Prompt
In the folder where you unzipped dc-unlocker2client.exe to, press [shift] on your keyboard and hold it while right-clicking in an empty area underneath the files, then click "Open PowerShell (or command prompt) here".
Whatever command-line you started will open, type ad[tab] and adb.exe should be appear (shows up as .\adb.exe in PowerShell)
Follow this by typing reboot bootloader. So it should show as
Code:
./adb.exe reboot bootloader
(no ./ in command prompt)
Hit [enter] and the phone should reboot to a screen with a white background
Once the bootloader screen shows (white background with the android mascot) type fast[tab] in PowerShell/Command prompt and follow it up by oem unlock[space]
If you still have the bootloader code in memory, right-click in PowerShell/Command prompt to paste it. Your entire line should be
Code:
./fastboot.exe oem unlock 1111222233334444
Hit [enter], the unlocking will start and factory reset your phone. My output was:
Code:
(bootloader) The device will reboot and do factory reset...
OKAY [ 10.330s]
If everything went right you'll see the Huawei/Android bootscreen and then a warning that the phone is "unlocked and can not be trusted" to use or something like that. It'll boot into the OS after that.
I'd like to remind you of the disclaimers at the top, but hopefully this will help some of you going through the process.
Edits
Forgot about USB debugging
Added the warning you get after a successful unlock
Changed the build number tapping sentence
Rewrote a sentence for clarity
Very nice guide, if ppl ask about unlocking we just link this from now on...
This is a very helpful guide, thank you so much! My question is, if I wanted to flash twrp when the bootloader is unlocked, is there a way to upgrade it to Oreo once again without locking the bootloader again? I can't seem to find a twrp tutorial where they use Nougat/Emui 5 to flash twrp, and all the tutorials to upgrade to Oreo/Emui 8 look like they're locking the bootloader once again and I don't really want to waste 4 euros to go back to the start.
A bootloader unlock should be permanent? I've been moving between Android 7 (EMUI 5), Android 8 (Emui 8) and Android 10 myself in all kinds of directions.
Besides, I think the code is tied to your device, so you should be able to use it again. (But I'm not sure about this!)
Syrion said:
A bootloader unlock should be permanent? I've been moving between Android 7 (EMUI 5), Android 8 (Emui 8) and Android 10 myself in all kinds of directions.
Besides, I think the code is tied to your device, so you should be able to use it again. (But I'm not sure about this!)
Click to expand...
Click to collapse
Thank you for your quick reply! So after the bootloader unlock, did you flash twrp on Android 7? or did you upgrade your phone to Android 8 and flash twrp then? How did you manage to upgrade it to Android 8?
I really appreciate your help with the previous tutorial, I've done everything until the buy credits part (I'm waiting a bit for that part) and I'm planning on getting to the end of the tutorial at least before August. My idea is to upgrade to Android 8 + flash twrp and Magisk, hopefully I'll be able to do all of that!
I did the above procedure on an up to date, official stock Huawei android. Both EMUI & Android are 8. I'm in the Netherlands, so it'should be the same model as in Spain. (WAS-LX1A)
The HiSuite step is to downgrade from EMUI 8 (Android 8) to EMUI 5 (Android 7), since that seems to have less securities to make it easier to unlock the bootloader.
Oh, I understand now! One more question (sorry if I'm being annoying, it's my first time playing with a Huawei, I must say that Samsungs are far easier to root/unlock lol): If I follow your method, but after getting the bootloader unlock code and right before unlocking the bootloader, I use HiSuite to upgrade back to Android 8/Emui 8, would the procedure be fine? like, it's totally fine to unlock the bootloader either with android 7 or 8, the only time I need android 7 is to get my code because DC unlocker supports them better, right?
Again, thank you so much!!!
I'm not sure to be honest. But I reverted to 7/EMUI 5 because I read around here on the board that's better for trying to unlock.
Thank you,
Only fastboot.exe oem unlock xxxxx failed with the following error: FAILED (remote: Command not allowed)
finished. total time: 0.022s
This was resolved by going back to settings, developer options and check 'enable oem unlocking'. I didn't read that in your guide.
Syrion said:
I did the above procedure on an up to date, official stock Huawei android. Both EMUI & Android are 8. I'm in the Netherlands, so it'should be the same model as in Spain. (WAS-LX1A)
The HiSuite step is to downgrade from EMUI 8 (Android 8) to EMUI 5 (Android 7), since that seems to have less securities to make it easier to unlock the bootloader.
Click to expand...
Click to collapse
Hi, I have the same model. But I can't figure out how to update to EMUI8 again (or which custom recovery works). It doesn't find the update in HiSuite and it doesn't find it via System update. Do you happen to know how? Thank you.
What should I do next?
I did manage to unlock the bootloader thanks to this very clear post. I did downgrade to Android 7 / Emui 5.1.1 and have a working rooted system but he is trying to upgrade again to android 8 / Emui 8. I know by experience that it will lock again with the higher version (the unlock code can be used several time fortunately).
I did try to flash some roms on it, going for instance to Lineage OS 14 but it was all a disaster and I think that I need some guidance now..
I am not a newbee for rooting and flashing but do not understand yet the Huawei system; is that so that I have to choose a new ROM with caution, especially with the Emui version? Looking at the old posts, I find some old ROM's even with Emui 5 version but do not understand the path that I should follow to progressively upgrade.
Thanks in advance for your orientations!
Syrion said:
A bootloader unlock should be permanent? I've been moving between Android 7 (EMUI 5), Android 8 (Emui 8) and Android 10 myself in all kinds of directions.
Besides, I think the code is tied to your device, so you should be able to use it again. (But I'm not sure about this!)
Click to expand...
Click to collapse
For me, I did get to relock by accident but I confirm that the unlock code is permanent (at least, I did use it 3 times with no problem!)
P10 lite Pinout
I would like to know if they have tried to unlock the bootloader with the Pinout method.
Correcaminos604 said:
I did manage to unlock the bootloader thanks to this very clear post. I did downgrade to Android 7 / Emui 5.1.1 and have a working rooted system but he is trying to upgrade again to android 8 / Emui 8. I know by experience that it will lock again with the higher version (the unlock code can be used several time fortunately).
I did try to flash some roms on it, going for instance to Lineage OS 14 but it was all a disaster and I think that I need some guidance now..
I am not a newbee for rooting and flashing but do not understand yet the Huawei system; is that so that I have to choose a new ROM with caution, especially with the Emui version? Looking at the old posts, I find some old ROM's even with Emui 5 version but do not understand the path that I should follow to progressively upgrade.
Thanks in advance for your orientations!
Click to expand...
Click to collapse
I ran into the same problem. Did you find a solution?
I followed this guide, downgraded to EMUI 5.1.1 and tried to install several custom ROMs. But none of them will boot. It is always stuck on the splash screen with the "bootloader unlocked" warning and doesn't get any further.
I tried installing LineageOS 17.1, 15.1, and RR on Android 9 but no luck on any of these. Also, is it possible to revert back to the stock ROM? Maybe that will help...
Thank you all for any help
Nothing unfortunately, I did finally reinstall Android 7 with HWOTA https://www.******.com/huawei-hwota-tool-for-huawei-devices/ and managed to have a working Android 7 / Emui 5 that works perfectly if you do not forget to make a complete wipe/reset when rebooting. The bootloader is still unlocked.
Strange enough this system is upgradable through the normal update system (parameter/system/update) and keeps the unlocked bootloader. Today, I did upgrade to a very last built today - 394(C432) - without problem. Apparently I just have to re-root it through trwp.
I keep it like this now, finally, the Huawei system is not bad! and it is yet rooted
be-rty said:
I ran into the same problem. Did you find a solution?
I followed this guide, downgraded to EMUI 5.1.1 and tried to install several custom ROMs. But none of them will boot. It is always stuck on the splash screen with the "bootloader unlocked" warning and doesn't get any further.
I tried installing LineageOS 17.1, 15.1, and RR on Android 9 but no luck on any of these. Also, is it possible to revert back to the stock ROM? Maybe that will help...
Thank you all for any help
Click to expand...
Click to collapse
Correcaminos604 said:
Nothing unfortunately, I did finally reinstall Android 7 with HWOTA https://www.******.com/huawei-hwota-tool-for-huawei-devices/ and managed to have a working Android 7 / Emui 5 that works perfectly if you do not forget to make a complete wipe/reset when rebooting. The bootloader is still unlocked.
Strange enough this system is upgradable through the normal update system (parameter/system/update) and keeps the unlocked bootloader. Today, I did upgrade to a very last built today - 394(C432) - without problem. Apparently I just have to re-root it through trwp.
I keep it like this now, finally, the Huawei system is not bad! and it is yet rooted
Click to expand...
Click to collapse
Is 394(C432) finally coming as OTA? Back in July I had to download it via firmware finder and flash it with HWOTA after unlocking the bootloader... lol just to relock after updating... However even Huawei support didn't know about 394 and denied it would even exist, not too surprising in hindsight! Still eversince I was wondering if it ever comes as simple OTA, which indeed seems the case eventually!
Sent from my Google Pixel 3 XL using XDA Labs
Yes, WASLX1A 8.0.0.0394(C432) did arrive as OTA around the end of October. I was surprised as I did not expect any new update on this phone!
Sam Nakamura said:
Is 394(C432) finally coming as OTA? Back in July I had to download it via firmware finder and flash it with HWOTA after unlocking the bootloader... lol just to relock after updating... However even Huawei support didn't know about 394 and denied it would even exist, not too surprising in hindsight! Still eversince I was wondering if it ever comes as simple OTA, which indeed seems the case eventually!
Sent from my Google Pixel 3 XL using XDA Labs
Click to expand...
Click to collapse
DC-Unlocker can't find my phone
I followed your instructions, but when I click the magnifying glass on DC-unlocker it says
===================================================================
DC - Unlocker 2 Client 1.00.1431
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM6
===================================================================
But then nothing else is listed .....
My model is WAS-LX1
Correcaminos604 said:
Yes, WASLX1A 8.0.0.0394(C432) did arrive as OTA around the end of October. I was surprised as I did not expect any new update on this phone!
Click to expand...
Click to collapse
Yeah, it's actually crazy cool that it was patched after all this years, I however read it was primary updated to support the coronavirus warning App framework! That's actually the reason for Huawei to push another last update!
Sounds like a crazy conspiracy theory but was written on their Homepage...
Sent from my Google Pixel 3 XL using XDA Labs
Downgrade option doesn't exist for me in Hisuite. My phone is WAS-LX2 8.0.0.370(C185). The last update I got was on 13 February 2019 with the 2019 Feb security patches. Is there a free way to unlock bootloader?
Specs:
T-Mobile-locked Samsung Galaxy Note 8 - N950U
Baseband version: N950USQU1AQI5
Build number: NMF26X.N950USQU1AQI5
Android version: 7.1.1
Samsung Experience version: 8.5
Knox version: 2.9
I recently purchased the above Note8. I have bookmarked a root method[1], but it requires bootloader v7. If I'm decoding my phone's baseband version correctly, its on v1, so probably won't work with this method.
I'm wondering, if I let it do an OTA update to Oreo (Android v8), will it hit the requisite v7 bootloader so I can, according to the instructions on that page, flash it back to a pre-rooted Nougat? ( If there's a better method than what I'm planning to follow, please advise. I'm all ears! )
[1] www (dot) the custom droid (dot) com/root-galaxy-note-8-snapdragon-n950u/
Just stay on firmware you are on and use the old Samfail root method
Sent from my SM-N960U using Tapatalk
Thanks, butchieboy. Would this be the process for this phone?
https://forum.xda-developers.com/galaxy-note-8/development/root-samfail-galaxy-note8-t3685340
Yes [emoji106] The thread is closed but you should still be able to get the files you need. If not I still have them and when I find time I could send them to you with Mega...but you still should be able to get them from the thread.
Sent from my SM-N975U using Tapatalk
The links are still good in that post, but I'm a bit concerned about them. The SamFAIL downloads for the v1 bootloader are designated for N950F ("for the Samsung Galaxy Note 8(SM-N950F)"), which is the European firmware. Mine's N950U (US).
Does this SamFAIL root actually rely on the European firmware? How does that impact the Snapdragon? I thought the European phones/firmwares were designed for a different processor.
No dice
I followed the instructions on that post to the letter. The first flash didn't cause my phone to reboot (as the instructions say it will), so I rebooted it myself and got it back to the "Emergency" screen, whereupon I did the part #2 flash. It reset that time, and now it's stuck in an "Installing update" loop with the Android icon (with a "warning" icon above it) just appearing over and over.
What do I do now? Do I have to try and flash a stock ROM and see if I can recover the phone? Or is there something I can do from here that will help it continue?
Boot to recovery and factory reset
Sent from my SM-N975U using Tapatalk
And the angels sang!
Since I couldn't get the damn thing to shut off anyway, I left the phone in the "Installing" loop overnight (since that was the least risk of screen burn). This morning, the device was dead because the battery had drained to zero, so I put it on the charger. I left it there for only about 30 minutes so it had just enough juice for me to try and get it into recovery mode.
I must not have held the buttons correctly, because it went into a normal boot instead of going into Download or Recovery. I let it go, intending to just try again once it entered the "Installing" loop, and LO! the "SAMSUNG" logo came up. It hadn't done that before. I put the phone aside and didn't touch anything while the logo pulsated, and it eventaully dropped into the setup screen! :victory: Of course, it almost immediately shut down because the battery hadn't charged enough, but I think it somehow reset/corrected itself when it lost all power overnight.
I left it on the charger and monitored the level. It stopped increasing at 80%, which is the expected behavior with this solution. I powered it on again, and everything is as described in the rooting post (except that SuperSU did not prompt me multiple times to update it).
So, at this point, I'd say I'm good. Looks like it reset itself, and the root succeeded. Hopefully anybody coming along later with this same issue on the Note 8 will see this post.
Thanks again, butchieboy.
Hi,
I havent used the Pixelflasher yet, so unfortunately do not have any support files (i went old school side load factory image). But I unknowingly used the latest v34 platform tools and looks like ive hard bricked my phone (completely unresponsive, will not power on, first hard brick EVER in 10+ years!)).
Got the error everyone else has gotten
Code:
Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)
After I got the error, I couldnt restart phone. I then got the:
“Your device is corrupt. It can’t be trusted and may not work properly."
And then when I tried booting to bootloader....it just became unresponsive.
Any ideas on how to bring my P7 back to life?? Or am I at the mercy of Google warranty/repair store??
Use Platform Tools with Factory Image (Flash_all.bat).
It's not as comfortable as other tools but it's official from google and it works.
Platform Tools:
https://developer.android.com/studio/releases/platform-tools
Factory Image (not available for March update till now)
https://developers.google.com/android/images?hl=de#panther
Tutorial from point 2:
https://forum.xda-developers.com/t/...nlock-bootloader-pass-safetynet-more.4505353/
My bad, should have researched all the updates and threads before thinking that the newest releases were bad.
Next time will play it safe and wait another month to see what shakes out. I know, shouldn't have said anything.
rekids said:
Had a similar error with March update as well.
I also update to the newest 34.0.1 of SDK Tools as well.
Flashed March update full image using flash-all.bat without the -w and got the exact same error in OP.
Luckily was able to reboot after flashing February even though it failed as well at the same point in the flashing point of 'super'.
Not sure was wondering if it was the SDK that was bad or not. Going to go back to 33.0.3 and see if I can flash February build back.
UPDATE* I was able to flash February back using 33.0.3, but 34.0.1 would not flash successfully for me
UPDATE # 2 - Platform Tools Version 33.0.3 works with March update, Version 34.0.1 DOES NOT WORK with March or February update for me on windows 10 Pro machine. Maybe its just me but looks like it is broke. Using 34.0.1 resulted the same as error and result as OP, except I was able to back into the bootloader using long key press.
Click to expand...
Click to collapse
By now platform tools 34.0.0 & 34.0.1 is reported being buggy/faulty causing a lot of problems. Stick to platform tools 33.0.3 until further updates, do research before switching to a newer version if updates are released. Pixel Flasher for example warns users by now not to use anything above 33.0.3 atm.
Had the same Problem
June 13, 2023 TQ3A.230605.012 Global - Platform-Tools v34.0.3 has a different bug- Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Pixel 7 Pro [Cheetah] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
June 13, 2023 TQ3A.230605.012 Global - Platform-Tools v34.0.3 has a different bug- Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Pixel 7 Pro [Cheetah] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
Second Link somebody say
Did u try to change the boot slot back to the non-updated one? That's the usual step when an update fails. If slot A is unbootable -> go back to slot B and vice versa.
Click to expand...
Click to collapse
but it was to late for my I wiped