P9 soft brick, tried quite everything - Huawei P9 Plus Questions & Answers

Hi
So I've been trying to set my P9 Plus back to stock, unless I experienced an unknown error during the flash and I got stuck outside the OS, with the black screen warning me that " the phone is unlocked and it can't be trusted". I tested some other firmware but no luck, also for some reason now I can't even access the TWRP. I'm stuck even outer at the moment, I can access only the white bootloader. I since tried to flash TWRP again, following this guide https://forum.xda-developers.com/p9/how-to/huawei-p9-brick-easiest-to-unbrick-t3662348 for the update extractor, but from adb/fastboot I get the FAILED (remote: Command not allowed) error. Looked for most of the solutionfor this step but none of them worked.
I gave a chance to the HWOTA7 tool, to HiSuite, to automatic update too, no progress at all
What could be the next move?
Thanks a lot for the support

Same
Exactly same issue here. Phone boots (when it wants to) but unresponsive (apps won´t open).
Somehow either partition became read only or partition completely gone.

Micro sd download gyári Rom

Related

Help with Encryption Unsuccessful

Hi, I need help with my huawei p9, when I power up and the system start, a screen says Encryption Unsuccessful, and that I should do a factory reset for resume using the phone. I do the cleaning in TWRP and I install fRomFuture - NewWorld V4.1, the installation is performed without errors, but the message remains.
How could resolve this situation?
PS: sorry for my English
I have similar problem
Hi, I have the same thing here, but it has stock recovery, which I can't boot into. I can get to Encryption unsuccessful screen and to fastboot. It is customers phone, he was messing around with SW, and I think he didn't allow oem unlocking, debbugging is disabled aswell I think. I can't flash anything to it, whatever I try I get 'FAILED (remote: command not allowed). Tried force-flashing it via SD card, it gets stuck at Huawei logo. Any thoughts? Or to tell him to use it for smashing nuts?

[Solved]Bricked. Can't recover stock ROM after installing TWRP 3.1.0-3. Nothing works

I have successfully unlocked the bootloader and managed to install TWRP 3.1.0-3 but that's about it. I cannot install any other TWRP version but the one I mentioned. I tried installing Magic Rainbow custom ROM but it doesn't work properly (apps are super slow, entering developer settings makes the settings app crash, can't set a password etc.). So with that I can at least access the phone interface with limited options. Developer settings crashes when I choose it; if I can get through then I can't enable USB debugging, it keeps turning itself off right as I enable it. I can't use update function so I have to use 3 button installation, which randomly fails to work very often. Due to this I haven't been able to install any updates.
I kinda gave up on rooting already, I just want to get my old firmware back at this point but I can't even do that. SRKTools stock marshmallow recovery doesn't work either. It's as if TWRP 3.1.0 has taken over everything. On the rare occasions that I managed to get EMUI update via 3 button installation it would say that the update doesn't match the current version (or something like that). I tried using recover for b378 and managed to run the 3 button update but it always gets stuck at 5%. It gives up after a while, tries booting twice and then goes into eRecovery screen. My bootloader PHONE unlocked text is in red if it matters.
I've been actively trying to fix this for the last 11 hours (yes I'm not exaggerating at all). Please, PLEASE someone help me out with this!
I've also tried using the unbrick tool of the latest SRK Tool 2.0 for b378. It goes flawless, phone restarts and does a factory wipe but then doesn't boot after the Huawei screen. It tries booting twice and then it goes into eRecovery screen. Have I ruined some hardware here?
It seems like 3 button upgrade is my salvation and it doesn't work. Many times I hold it down, I get a slightly different screen but it again hangs at booting text. I managed to flash all recovery, boot and system image files and got the installing update screen in my b378 update, but it hangs at 5%. I couldn't even manage to get the installing update screen for common b136. Also when I try to flash system.img I get an error with flashing system which is FAILED (remote:sparse flash write failure).
First at all: The Magic Rainbow custom ROM is based on B383 so it wont work on B378 firmware thats your fault here.
Just flash the rollback package (find it in my signature) and after this flash B383 or if it not work start with B136. U have to do all with the dload method.
Fast solution?
https://forum.xda-developers.com/p9/development/p9-moonlight-rom-v1-0-b378-stock-t3567223
flash the B378 version. probably your problem is solved by this.
I'm very well aware that Magic Rainbow doesn't work with b378. That's probably the reason I have those issues with it. But it's the only way I can access the phone's interface in case I need to use it for a fix.
I tried flashing b378 already multiple times, without rollback and it did not work. Is it safe to use the rollback though? My oem is c432, would it create any issues to use that? Should I flash c900 oem first or can I go with the rollback right away? I literally cannot install any stock rom without having frozen/looping bootscreen atm so I can't complete any step that requires me to do that.
I've also tried flashing b136 plenty of times already. I can't even flash the system.img. I can't flash the system of any of the b100 series.
Lauran_N said:
I'm very well aware that Magic Rainbow doesn't work with b378. That's probably the reason I have those issues with it. But it's the only way I can access the phone's interface in case I need to use it for a fix.
I tried flashing b378 already multiple times, without rollback and it did not work. Is it safe to use the rollback though? My oem is c432, would it create any issues to use that? Should I flash c900 oem first or can I go with the rollback right away? I literally cannot install any stock rom without having frozen/looping bootscreen atm so I can't complete any step that requires me to do that.
I've also tried flashing b136 plenty of times already. I can't even flash the system.img. I can't flash the system of any of the b100 series.
Click to expand...
Click to collapse
u tried the rom i mentioned?
it is safe to use the rollback package. any firmware after will retrive your oem to c432. so you dont need to flash the oem info package.
1. flash rollback package via dload (watch out to have only the UPDATE.APP file in dload folder)
2. flash B383 via dload (2 files need to be flashed!)
3. flash special SuperSU_for_EMUI5.zip
4. have fun
again if u can boot magic rom then you can flash and use Moonlight rom v1.0
xtcislove said:
u tried the rom i mentioned?
it is safe to use the rollback package. any firmware after will retrive your oem to c432. so you dont need to flash the oem info package.
1. flash rollback package via dload (watch out to have only the UPDATE.APP file in dload folder)
2. flash B383 via dload (2 files need to be flashed!)
3. flash special SuperSU_for_EMUI5.zip
4. have fun
again if u can boot magic rom then you can flash and use Moonlight rom v1.0
Click to expand...
Click to collapse
I cannot flash rollback using 3 buttons method. I see the "your device is booting now" text and then it goes to TWRP menu. Nothing happens. This is what I mean with 3 button method not working. Every single update fails probably because of this. Is there anything else I can do to flash it?
I've also tried flashing b378 and then doing the rollback. Still doesn't work: It hangs at 5% as it did with the b378 update.
Also, is there a special way of flashing those 2 files of b383? Is it just one after another? I doubt I can flash them at the same time since they have the same name.
YES IT WORKED! Thank you the rollback actually made the difference. I had to go for b136 and then upgrade manually through there with the stock OS though. And I believe rollback changed the status to LOCKED instead of RELOCKED. And I was a complete moron for I couldn't do 3 button update because my cable was still plugged in. I had a moment of epiphany when I noticed what the symbol actually represents. It was like discovering who Keyser Soze was lol. Let this idiocy stay here for there might be others like me; this way they might fix it without embarrassing themselves like I did.
Glad it worked for you.
Next time just read the threads in this forum.
There are several toturials how to flash the p9 the right way.
Lauran_N said:
YES IT WORKED! Thank you the rollback actually made the difference. I had to go for b136 and then upgrade manually through there with the stock OS though. And I believe rollback changed the status to LOCKED instead of RELOCKED. And I was a complete moron for I couldn't do 3 button update because my cable was still plugged in. I had a moment of epiphany when I noticed what the symbol actually represents. It was like discovering who Keyser Soze was lol. Let this idiocy stay here for there might be others like me; this way they might fix it without embarrassing themselves like I did.
Click to expand...
Click to collapse
Can you explain in detail how your fact? That would be nice
Genysix said:
Can you explain in detail how your fact? That would be nice
Click to expand...
Click to collapse
1. Flash Rollback Package
2. Flash Firmware Package/s
3.Unlock booloader
4.Flash twrp
5.Flash SuperSU
6.Ready
Just read the threads in this forum guys and you errors will magically dissappear or not even happen
xtcislove said:
1. Flash Rollback Package
2. Flash Firmware Package/s
3.Unlock booloader
4.Flash twrp
5.Flash SuperSU
6.Ready
Just read the threads in this forum guys and you errors will magically dissappear or not even happen
Click to expand...
Click to collapse
Every time I try to flash, with 3 buttons method, it puts me "software install failed"
I tried to flash official rom with twrp but he can't finish the process.
I tried to flash custom rom. When I want to boot, he bootloop.
Hi,
I am at a complete loss and going round in circles. My phone has bootlocker unlocked message at moment. In adb fastboot devices finds the phone, but the SRK tool fails to find it sticking on 'waiting for phone'. I tried to flasg the Huawei rollback but that fails (presumably due to being unlocked). I cannot relock via fastboot as that gives 'remote: command not allowed' error.
Update
- I have just checked fastboot - it says Phone Unlocked & FRP Unlock.
- Next I used Huawei Update Extractor to get boot, recovery, cust & system img from the "HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0_EMUI 4.1_C432B166_United Kingdom_Channel-Others" Package.
It seems I still cannot boot and device still says unlocked etc..
Update 2 :-
Copied the dload/update.app file from the HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0 zip. Managed to get it to start installing, only to get Software Install Failed msg. However reboot let me start the phone. So currently have Build No: EVA-L09C432B166 on.
At this point I just want my phone either back to initial factory state or able to flash roms, whichever is easier to get to. Any help greatly appreciated. I've been getting nowhere following guides I have found, so would really appreciate some help here.
Thank You
Genysix said:
Every time I try to flash, with 3 buttons method, it puts me "software install failed"
I tried to flash official rom with twrp but he can't finish the process.
I tried to flash custom rom. When I want to boot, he bootloop.
Click to expand...
Click to collapse
Ok first of all, using TWRP back up everything you have there (backing up SD card isn't really needed unless you plan to wipe it too). Then, using TWRP again just wipe everything but OEM and SD card (external storage). Then, create a folder called "dload" in the main SD card directory and put ONLY the update.app in it (use the stock b136 as suggested). Now you need to flash a stock recovery using bootloader again. Just use the Huawei Update Extractor and get both recovery.img and boot.img from the rom that you're using to flash (in this case b136). Put them in the same folder as adb. Run adb cmd, write commands "fastboot flash recovery recovery.img" and then "fastboot flash boot boot.img" and finally "fastboot reboot". Quickly unplug your usb cable and use the 3 button force update (Vol Up+Vol Down+Power button all held together and don't let go until you see the update start). It should work without a problem if you had managed to wipe everything using TWRP. If it still doesn't work you could try deleting OEM info as well and flashing a new one (c432) which you can find on the forums. Back up is important in case it still doesn't work, you might need them to undo things.
If it boots, it means you've learned how to do it and you can probably unbrick it as much as you want haha. You can update to Nougat (7.0) and EMUI 5 using Huawei Updater 2.0 along with HiSuite, there is a guide here on the forums to do so by updating to b182 then to b360/b361>b378>b383 which I was unable to find for now. After that you can install a custom rom without an issue. I figured I wouldn't mess with it anymore but frankly it's likely that you are just soft bricking by skipping something very simple and failing because of that unless you went ahead and did things that you are explicitly told not to do so. If you end up having it unlocked/relocked might as well try and get a custom rom really.
If the update gets stuck at 5% or you have the icon of a usb cable end with a lightning on it your mistake is that you didn't unplug it. If the update keeps failing without these it's likely that you're using the wrong firmware and you could try using another one (FULL+PV+MV ones if you're going for a higher one). Or you could try to follow the rollback and then the update as I did. if you do the rollback then the update, your phone might get a LOCKED status again (yes not relocked).
If you are missing something or you think you have a stupid question and too shy to ask it here just PM me.
Phil_UK said:
Hi,
I am at a complete loss and going round in circles. My phone has bootlocker unlocked message at moment. In adb fastboot devices finds the phone, but the SRK tool fails to find it sticking on 'waiting for phone'. I tried to flasg the Huawei rollback but that fails (presumably due to being unlocked). I cannot relock via fastboot as that gives 'remote: command not allowed' error.
Update
- I have just checked fastboot - it says Phone Unlocked & FRP Unlock.
- Next I used Huawei Update Extractor to get boot, recovery, cust & system img from the "HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0_EMUI 4.1_C432B166_United Kingdom_Channel-Others" Package.
It seems I still cannot boot and device still says unlocked etc..
Update 2 :-
Copied the dload/update.app file from the HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0 zip. Managed to get it to start installing, only to get Software Install Failed msg. However reboot let me start the phone. So currently have Build No: EVA-L09C432B166 on.
At this point I just want my phone either back to initial factory state or able to flash roms, whichever is easier to get to. Any help greatly appreciated. I've been getting nowhere following guides I have found, so would really appreciate some help here.
Thank You
Click to expand...
Click to collapse
So you're saying that you're able to boot your phone on stock b166? Then update it to b182 first. I had to keep pressing the check update for a while before it popped up. I was busy at the time so I didn't mind the wait time but I bet you can do it faster forcefully, got to be a guide around here somewhere. Here is the guide to update it all the way to b383 from b182.
Lauran_N said:
So you're saying that you're able to boot your phone on stock b166? Then update it to b182 first. I had to keep pressing the check update for a while before it popped up. I was busy at the time so I didn't mind the wait time but I bet you can do it faster forcefully, got to be a guide around here somewhere. Here is the guide to update it all the way to b383 from b182.
Click to expand...
Click to collapse
I'm on B166 currently. Phone tells me it has update for B182, on reboot I get the device unlocked message and it sticks on 'Your device is booting now'.
Also tried Huawei updater....that sticks at 'Listened on Port 41279'
Thanks
Phil_UK said:
I'm on B166 currently. Phone tells me it has update for B182, on reboot I get the device unlocked message and it sticks on 'Your device is booting now'.
Also tried Huawei updater....that sticks at 'Listened on Port 41279'
Thanks
Click to expand...
Click to collapse
Getting the device unlocked message shouldn't indicate anything, only that you didn't lock it again. It might be that you didn't install your current rom correctly. You could try flashing TWRP, backing up everything and then wiping all of it f. It means you'll be romless for a while but worst case you can recover what you backed up with TWRP and then flash it with a stock rom again. There are guides to flashing everywhere and I've made my own guide here. I can't really give you advice on your situation since I haven't ever been there. I just dabble with these things, so I can't really find a solution for everything.
You are connected to HiSuite while running Huawei Updater right? It needs to be able to see your phone (usb debugging on or HDB mode) and set to usage via proxy.
Lauran_N said:
Getting the device unlocked message shouldn't indicate anything, only that you didn't lock it again. It might be that you didn't install your current rom correctly. You could try flashing TWRP, backing up everything and then wiping all of it f. It means you'll be romless for a while but worst case you can recover what you backed up with TWRP and then flash it with a stock rom again. There are guides to flashing everywhere and I've made my own guide here. I can't really give you advice on your situation since I haven't ever been there. I just dabble with these things, so I can't really find a solution for everything.
You are connected to HiSuite while running Huawei Updater right? It needs to be able to see your phone (usb debugging on or HDB mode) and set to usage via proxy.
Click to expand...
Click to collapse
Thanks for your help. Where do you set the usage to via proxy? Perhaps thats my issue.
Phil_UK said:
Thanks for your help. Where do you set the usage to via proxy? Perhaps thats my issue.
Click to expand...
Click to collapse
Run HiSuite. Make sure your phone is connected to it. Top right you'll see 4 buttons: 3 horizontal stripes, minimise, full screen and X. Press 3 stripes one and choose settings. In the first tab called General under the 4th section you'll see Proxy. Enable it and enter 127.0.0.1 for address and the given listening port as the port. Leave the username and password blank. Press apply. Then you probably have to choose the system upgrade from the main screen of HiSuite. I don't recall exactly but this is about how it goes.
Lauran_N said:
Run HiSuite. Make sure your phone is connected to it. Top right you'll see 4 buttons: 3 horizontal stripes, minimise, full screen and X. Press 3 stripes one and choose settings. In the first tab called General under the 4th section you'll see Proxy. Enable it and enter 127.0.0.1 for address and the given listening port as the port. Leave the username and password blank. Press apply. Then you probably have to choose the system upgrade from the main screen of HiSuite. I don't recall exactly but this is about how it goes.
Click to expand...
Click to collapse
Many Thanks
I managed to flash B360_update.zip via recovery instead. I also have a B360_update_data_full_hw_eu.zip but not sure what that is for.

[Solved] Bricked Honor 5C NEM-L51/NEM-UL10

Good morning,
I unlocked the bootloader and rooted my Honor 5C a few months ago already, installed a TWRP and had since then no problem my phone.
However, a few days ago, I simply put my phone into my pocket, and half an hour later the screen showed a Huawei eRecovery page, without having done anything.
I then said no to whatever it was showing and proceeded to restart the device, only to get a bootloop leading me to the eRecovery page once again.
I tried to get the phone to be repaired through the eRecovery app but it says Getting package info failed each time.
I made some research and it seems like everyone is saying to flash the stock recovery and then to do the three button install with the dload folder.
Problem is, I don't know the exact reference of my phone. On the bill it says NEM-UL10 (NEM-L51), this version has a fingerprint sensor, and there are some Chinese characters followed by NEM-UL10 on the back of the phone. So, I don't know which version of stock recovery and which firmware I should use.
I can access my device through fastboot, and tried several update.app, but don't really know which one to use, and everytime it says wrong version.
The transfer from the computer to the sd card takes a long time and I don't really want to do the combination of all possible stock recoveries with all possible stock firmwares.
Could someone help me ? Try going a little bit into details as I'm not a pro, I know how to use basic commands of fastboot like flash recovery or flash boot but don't know anything about the rest.
Thank you for reading.
where you bought your device from?
thelous said:
where you bought your device from?
Click to expand...
Click to collapse
I bought it on a French website (since I'm French).
I'm trying to flash different versions using Huawei Multi-Tool, but each time it fails at writing the cust with a (remote: partition error), and with system it says (remote: sparse flash write failure).
MichelFou said:
I'm trying to flash different versions using Huawei Multi-Tool, but each time it fails at writing the cust with a (remote: partition error), and with system it says (remote: sparse flash write failure).
Click to expand...
Click to collapse
You might need oeminfo file of the version you are trying to move to
Thank you so much !
I installed the oemfile from this link https://forum.xda-developers.com/honor-5c/help/flash-european-rom-honor-5c-chinese-t3456794 and downloaded the rom accordingly.
At first the three button install told me "failed to check package content" at 50% but the only thing in the dload folder you had to have was UPDATE.APP, otherwise it won't work.
I updated to the latest version and everything is back to normal (except the fingerprint sensor which doesn't work anymore, saying Enroll failed instantly when trying to setup a new fingerprint, but I'll deal with it later).
Regards.
MichelFou said:
Thank you so much !
I installed the oemfile from this link https://forum.xda-developers.com/honor-5c/help/flash-european-rom-honor-5c-chinese-t3456794 and downloaded the rom accordingly.
At first the three button install told me "failed to check package content" at 50% but the only thing in the dload folder you had to have was UPDATE.APP, otherwise it won't work.
I updated to the latest version and everything is back to normal (except the fingerprint sensor which doesn't work anymore, saying Enroll failed instantly when trying to setup a new fingerprint, but I'll deal with it later).
Regards.
Click to expand...
Click to collapse
Great. Try doing the factory reset and finger print may work fine. Good luck

Semi working PRA-LX1C432

Hi !
I bought in January the nice P8 Lite 2017 and received a PRA-LX1C432 (dual sim europe no carrier).
It was with Android 7.0 and EMUI 5.0 and i wanted to root it.
I did it well, and was with the firmware PRA-LXA1C432B182 in stock and rooted with the tuto from this thread
https://forum.xda-developers.com/p8...ck-rom-huawei-prague-pra-xxxc432b182-t3727816
and uninstalled TWRP to put back stock recovery.
Later, I wanted to unroot my phone, and that's where things went wrong. I tried to do it with the superSU option and after a hard reset it was working and not rooted, but i'd still have the message "this phone can't be trust" so i tried to relock the bootloader and it did hard reset the phone again and now, i'm stuck with a phone that can send sms or go through the internet with LTE, but can't access fm, camera, google music, nfc is going on and off, calls don't work, etc... In dev options, Allow OEM unlock is greyed and I can't change anything. Phone is recognized by computer and I can acces memory of the phone.
I can hard reset it won't change, i ca also accessFastboot, or recovery or eRecovery, but in Fastboot mode it says "PHONE Unlock FRP Lock" and from my computer i can't do anything : if i try to flash twrp with fastboot command, i have the message "FAILED remote the command is not allowed", if i try to lock/unlock/relock bootloader it says "FAILED remote root type is risk".
Clearly, I don't know what to do. I'm used with rooting/unrooting smartphones from different brands (Samsung, LG, Sony, Huawei...), even though i'm far from being a master, and using Fastboot/ADB commands, but... I don't know.
If someone has any idea, I'm taking. I'm thinking about dload method but, of cooourse, I do NOT have a sdcard, so it's the last thing i would have tried from all i have seen on xda and elsewhere.
Thanks for reading and taking time to answer and help me, and sorry for not perfect english, i'm french but trying my best !
Run a eRecovery restore , it restore the entire smartphone to stock and also lock bootloader. Idk if this can solve your problems but i had ur same problem a days ago and i restored my phone enterely.
Fr0nK said:
Run a eRecovery restore , it restore the entire smartphone to stock and also lock bootloader. Idk if this can solve your problems but i had ur same problem a days ago and i restored my phone enterely.
Click to expand...
Click to collapse
I can't, it says that it can not get package infos from server. :/
MrCrumble34 said:
I can't, it says that it can not get package infos from server. :/
Click to expand...
Click to collapse
If you have twrp or if you can install it in someway , i can provide to you and ominfo.img to flash via twrp in ominfo partition to restore and remove package info error.
Fr0nK said:
If you have twrp or if you can install it in someway , i can provide to you and ominfo.img to flash via twrp in ominfo partition to restore and remove package info error.
Click to expand...
Click to collapse
TWRP is not installed, and I can't flash it in any way. Fastboot says "FAILED (remote : command not allowed)" if I try flashing recovery or system or anything. It also says "FAILED (remote : root type is risk) if I try to lock/unlock/relock the bootloader.
Ok, I'm actually trying something. I plugged the phone into my computer, and HiSuite told there was an update available for my phone, so I just clicked on it. It's doing right now, I will edit my post after it has finished (for good or bad).
EDIT : Ok, si it did work ! My phone is now on PRA-LX1C432B194, everything is working, not rooted. I relocked the bootloader with Fastboot, the command did work (guess I can root it again if I need now). But I think I'll leave it like that ^^'
Allow OEM unlock isn't greyed anymore, I came back to the original state of my phone but with an update not (yet) available in my country, no more "Device can't be trusted" message. Like if nothing had ever happened (expect it will be written PHONE Relocked).
This phone is really sensitive, haha^^
But as anyway I made it
Thanks anyway for trying to help !

Huawei G620s problem - No IMEI, locked bootloader

I found one of my Huawei G620s phones, I remember in 2019 it was rooted and started haviing problems, for example it was stuck at the bootanimation or did not work at all (red,green,blue LED), then in 2022 I turned it on just to find no reaction at all, nothing. I ran a flashing tool for Huawei and got it to turn on and display a green screen with 2 boxes, one blue and one red, along with the text:
"bootloader lock state: widevine disable mode"
"press and hold poewr key for 10s or more to forcibly reboot."
and surprisingly, i booted twrp 2.8.6.0 using the fastboot command from my PC. However when it loads i keep getting errors, for example:
"E: Primary block device '/dev/block/bootdevice/by-name/userdata' for mount point '/data' is not present!"
"E: Unable to mount '/data'" and it goes on with '/data/media' , '/boot' '/recovery' '/cache' '/system'.
It also says internal storage is 0MB.
I have tried everything, I wiped everything, I tried the file system changing trick, I tried to repair SELinux contexts and permissions, and it all resulted in nothing. Backup shows no partitions too, mount shows the names but clicking on them to mount does nothing, MTP enabled makes the phone show up in This PC but also nothing appears, and if I had a SD card then it would only show it. I tried to install a custom ROM for example, also nothing. Flashing for example TWRP to the recovery or boot partition using the fastboot command on my PC results in: "FAILED (remote: "partition table doesn't exist").
Now before you say the NAND failed, I once found a random paid tool and downloaded a free version of it. It was called something like Miko service tool and I flashed it in the boardsoft section because the other ones didn't work. And guess what? It flashed the stock ROM for me, but I had to use the phone's testpoint. Then the phone started booting but I noticed something was off, the bootanimation was playing kinda too fast, and it took not so long to boot. Then it booted to a lockscreen with a red wallpaper with the qualcomm logo. After swiping up I just saw like 5 hoem screen pages with only test apps, no google apps no huawei services apps, the phone didn't even have a theme applied and looked like old generations of EMUI, just some apps like settings,browser, camera, dialer etc. The test ones were named "MMI Test" or something. I was happy and decided to just ignore this until I put my SIM card into the phone, reboot it, just to see the error that network communication is unavailable because the device ID was altered. then I opened settings, went to the about phone section just to see my IMEI appear as "0", and serial number was "0123456789AB". Then I ran some codes and got into a test menu, and saw that the device mode was "Factory". I tried everything to disable it but I couldn't, then I got the idea to update the phone with the branded rom that was on it when I got it. And it updated, installed the stock applications but the IMEI and S/N were still gone, bootanimation was still the same (I checked in the ROM zip and it was the branded one so I didn't get the wrong ZIP). Then I booted into fastboot to see the thing that made me scared to death, Fastboot said "Phone LOCKED". I was scared thinking that the phone is done forever, because the bootloader relocked itself. Tried to boot TWRP just for the error saying that it's not allowed to appear, I also tried fastboot oem unlock but it asked for the code. Then I started the phone from the test point again and used an program to reflash it, the program failed and the phone rebooted to the green screen again, then I tried to boot TWRP and it worked. Reflashed the phone again with miko's service tool and same result as before.
Is there anyone that had a similiar problem? I really wanna get this phone back to work, I still have the battery with the IMEI written on it along with the S/N. I just don't know why TWRP is refusing to work, I tried the 3.2 build too but same result. Maybe it's because the bootloader is "locked" ? I ran the command to unlock it in the cmd (fastboot oem unlock) and it said "OKAY [ 0.006s]". It's weird because don't huawei phones need a code to be unlocked? And when I had the OS installed it didn't let me run the command and asked for the code.
Sorry if it's the wrong section but I saw the G620s custom ROMs only being posted in the honor 4x section so I thought it's good.

Categories

Resources