Related
Hi Everyone
This is Guide how to repair your phone who was dead
My phone doesn't worked for 3 days so i get small trick and successfully repaired from dead
My phone was 5 times not worked like dead,Screen not Works ...only LED works,when i connect to pc usb device not recognized and nothing....
Explanation about my Problem:
IN MY CASE!
and the worst In my case Power button and Volume Buttons doesn't working so i open the BACK COVER eject the cable from volume button and insert small cable in slots to cover the pins like pressing volume up and down and finally connected to pc with usb
So we are starting the GUIDE:
1.First you need the drivers so you can get from this https://drive.google.com/folderview?id=0B1T7tp6tJ_3kX3p6SUxWb2NfWTQ&usp=sharing
2.After you installed the Drivers go to. Download mode if not goes try this... Press Volume UP and Volume DOWN and connect to usb to your pc
3.Go to device Manager to view the Port ,so the port can be "Android HS-USB QDLoader 9008 (COM3)"
4.Download the Panasonic Firmware Eluga and Extract (don't worry this is the same like idol 3 only name changed)https://docs.google.com/uc?id=0B01OmzpKE6vAVDhaSFN2aVFzaVU
5. After Extract you wil find EB-90S55EWLv1009.exe so run as administrator wait to load data
6.select 6045 and in the list down you can find your phone
7.and press the button "download"
8.So process starting ..indetifying your device you will get informations about imei..rooted or no .....
9.so automatically started to flashing the firmware (my it's go to 45 % and then i get error)
10.Don't worry press the button Reboot Device
11.and your device will reboot and you will view 'the screen powered by android and then panasonic so i get message Encrypted device just click the button "reset" and automatically device will be reseted and when wil finish with reset automatically reboots and wait to first boot you will get welcome screen set up and finished.....
12.So device successfully repaired from dead
If you want to go to CM or Stock for Idol 3
-i will write guide to unlock bootloader and flash TWRP recovery
-You must have Minimal Adb and Fastboot
-type "adb reboot-bootloader" to reboot into bootloader. The device should reboot to the screen showing " .powered by android". This is bootloader mode.
-Then type "fastboot -i 0x1bbb devices" should show some numbers and "fastboot" after the numbers
-Type "fastboot -i 0x1bbb oem device-info" shows device info including bootloader status (e.g. locked).
-Type "fastboot -i 0x1bbb oem unlock" to unlock the bootloader; after this you should get, for device info,
-Type "fastboot -i 0x1bbb oem device-info" and you should see "Device unlocked: true"
-You successfully unlocked the bootloader one step more to flash the recovery
-Download the TWRP RECOVERY FROM THIS LINK:
https://www.androidfilehost.com/?fid=24421527759881858
-Then copy from when you downlaod and paste the recovery in C:\Program Files\Minimal ADB and Fastboot
-Press Shift in the directory and click Right on mouse and open command promt here
-Type fastboot -i 0x1bbb flash recovery twrp-3.0.0-1.img or fastboot -i 0x1bbb boot twrp-3.0.0-1.img (if you want to test before installation)
-so successfully installed recovery and flash CM Or whatever you want
[/SIZE][/COLOR][/B]
Sorry for Grammatical Errors!
This guide will repair from dead....
in my case , buttons also doesn't work , how did you opened the back cover?
xZrender said:
in my case , buttons also doesn't work , how did you opened the back cover?
Click to expand...
Click to collapse
here's video how you can open
https://www.youtube.com/watch?v=FrFE8FdTXrY
Alek Dev said:
Hi Everyone
IN MY CASE!
and the worst In my case Power button and Volume Buttons doesn't working so i open the BACK COVER eject the cable from volume button and insert small cable in slots to cover the pins like pressing volume up and down and finally connected to pc with usb
Click to expand...
Click to collapse
i opened back cover , but how did you press the volume button , it doesnt work for me , i ont know what to do ;/
xZrender said:
i opened back cover , but how did you press the volume button , it doesnt work for me , i ont know what to do ;/
Click to expand...
Click to collapse
Eject cable from motherboatd....insert small cable in slots to cover the pins like pressing volume up and down and finally connected to pc with usb
problem with idol 3 4.7 6039K
Hi there,
I don't know if this is the correct section, I hope so, otherwise I really appreciate you can drive me to the appropriate one, it's new for me this forum!
I have an idol 3 4.7, where I have installed kingroot and after I took out (I didn´t reset the phone, Just unistall the app),
yesterday i received the update system message, I imagine for the marshmallow update, so I say Yes, install it.
But the phone entered in bootloop. I only have the initial screen with the options as Reboot system, adb and so on.
I tried to wipe but nothing. So now my phone stucked. I tried with an assistance center in Quito but they could't
My questions are:
may I use this system for 6039K?
Or does anybody hear about a solution in this case?
Should I open and take out the battery?
Please, any suggestion will be really welcome in order to make the phone work again.
P.
nipozzano said:
Hi there,
I don't know if this is the correct section, I hope so, otherwise I really appreciate you can drive me to the appropriate one, it's new for me this forum!
I have an idol 3 4.7, where I have installed kingroot and after I took out (I didn´t reset the phone, Just unistall the app),
yesterday i received the update system message, I imagine for the marshmallow update, so I say Yes, install it.
But the phone entered in bootloop. I only have the initial screen with the options as Reboot system, adb and so on.
I tried to wipe but nothing. So now my phone stucked. I tried with an assistance center in Quito but they could't
My questions are:
may I use this system for 6039K?
Or does anybody hear about a solution in this case?
Should I open and take out the battery?
Please, any suggestion will be really welcome in order to make the phone work again.
P.
Click to expand...
Click to collapse
Hello
This Guide only works with Idol 3 5.5
but i will explain how to restore your device
Can you try with Mobile upgrade Q to restore,if doesn't work
Use this guide from wiemar ,it should help to you because it's for your model
http://forum.xda-developers.com/showpost.php?p=63709274&postcount=113
If you any questions ask me
Hi ! I follow the guide up to the section 9, unfortunately, in the Panasonic Firmware Eluga and Extract after pressing download it stops after 2% and I have got the error message "load nprg error error code 5002". Does someone know how to fix that ?
Thanks !
Error
I get: "Master Clear: FAIL Flash Status: [COM3->PC[3]] COM3->PC[3] failed to erase misc (Error code = 40016) " :crying:
Now I get the same error that matcail... did you solved it ???
Good tutorial but it does not help me. My phone keeps on rebooting.
Schumi_wk said:
Good tutorial but it does not help me. My phone keeps on rebooting.
Click to expand...
Click to collapse
Tell me info About your phone? Model,Country,ROM...../?
All is standard, no root, no twrp and the latest software from alcatel, the model is 6045Y. But all of a sudden my phone decided to random reboot and it didn't stop
So i looked to unbrick it and came with a couple of options, first i tried to sideload software but that didn't work, than i tried it with Mobile upgrade from alcatel and that didn't work.
Than i saw this thread and tried it twice but after Panasonic and the sound it starts to reboot again. Now i'm trying again with Mobile upgrade.
All that is changed is the recovery interface it looks now like it is from MM.
Schumi_wk said:
All is standard, no root, no twrp and the latest software from alcatel, the model is 6045Y. But all of a sudden my phone decided to random reboot and it didn't stop
So i looked to unbrick it and came with a couple of options, first i tried to sideload software but that didn't work, than i tried it with Mobile upgrade from alcatel and that didn't work.
Than i saw this thread and tried it twice but after Panasonic and the sound it starts to reboot again. Now i'm trying again with Mobile upgrade.
All that is changed is the recovery interface it looks now like it is from MM.
Click to expand...
Click to collapse
More Looks like Hardware Problem Try again with Mobile q if not works...Send to warranty repair.....
Alek, thank you for this great guide. It saved my 6045k model.
I was messing around with AlekOS 3.0, had issues with lock screen and experimented with modems. I managed to permanently disable secondary sim slot (was using famewolf's modem backups). I forgot to copy modem.img backup to my PC! Also tried bunch of TWRP backups with no luck. My last hope was Mobile Upgrade Q and reverting back tu 5.0.2. Unfortunately with no success (only one sim slot is recognized again).
Finally I found this thread, followed the guide and I can confirm that it did solve sim issue. The setup finished with no errors that you mentioned. It got stuck at 45%, but after a while (10min) it completed successfully.
Cheers!
I'm in the same situation as you,but my problem is that Panasonic Eluga doesn't recognice my devide,drivers are correctly installed,I checked everything but nothing:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I´ve tried everything to downgrade my device (Mobile Q doesn't work) but nothing :crying:
peito said:
I'm in the same situation as you,but my problem is that Panasonic Eluga doesn't recognice my devide,drivers are correctly installed,I checked everything but nothing:
I´ve tried everything to downgrade my device (Mobile Q doesn't work) but nothing :crying:
Click to expand...
Click to collapse
You must do something Wrong...Press Pwr button and Volume up and down and thern connect to PC and then you will get RED SCREEN....Press Volume Up until you get Black screen and then press Download and if you get again same Send me Pm with Teamviewer ID AND PASS and i will try to help you
eXoSaX said:
Alek, thank you for this great guide. It saved my 6045k model.
I was messing around with AlekOS 3.0, had issues with lock screen and experimented with modems. I managed to permanently disable secondary sim slot (was using famewolf's modem backups). I forgot to copy modem.img backup to my PC! Also tried bunch of TWRP backups with no luck. My last hope was Mobile Upgrade Q and reverting back tu 5.0.2. Unfortunately with no success (only one sim slot is recognized again).
Finally I found this thread, followed the guide and I can confirm that it did solve sim issue. The setup finished with no errors that you mentioned. It got stuck at 45%, but after a while (10min) it completed successfully.
Cheers!
Click to expand...
Click to collapse
Alek Dev said:
You must do something Wrong...Press Pwr button and Volume up and down and thern connect to PC and then you will get RED SCREEN....Press Volume Up until you get Black screen and then press Download and if you get again same Send me Pm with Teamviewer ID AND PASS and i will try to help you
Click to expand...
Click to collapse
That is exactly what I'm doing,entering in Download mode and then download in the Panasonic software,but nothing,the program cannot read my phone,I'm really tired of trying this,I will stuck in your Alek rom (btw,no matter how many times I flash your modem,I cannot get the lock screen ).Ty anyway Alek and keep it up!!!!
Was on alek 3.0 before bootloop appear after a strange warning on android about battery, now got bootloop, no twrp access etc
try ur solution but after 45% and error, reboot and no screen about panasonic only bootloop
11.and your device will reboot and you will view 'the screen powered by android and then panasonic so i get message Encrypted device just click the button "reset" and automatically device will be reseted and when wil finish with reset automatically reboots and wait to first boot you will get welcome screen set up and finished.....
Click to expand...
Click to collapse
already tried SUGAR+QCT_SP+v10.5.1(4pda source) and mobile upgrade q 5.0.9, both finished without error after 100% but still bootloop
i think it s total broke with motherboard pb or battery
thorfr said:
Was on alek 3.0 before bootloop appear after a strange warning on android about battery, now got bootloop, no twrp access etc
try ur solution but after 45% and error, reboot and no screen about panasonic only bootloop
already tried SUGAR+QCT_SP+v10.5.1(4pda source) and mobile upgrade q 5.0.9, both finished without error after 100% but still bootloop
i think it s total broke with motherboard pb or battery
Click to expand...
Click to collapse
Looks Like Problem With Motherboard and Battery ..you can try again with Panasonic Firmware Tool and if this not help Send it to Warranty Repair
ok i m gonna send it to warr:crying:antly
retry mobil q upgrage wo success bootloop again
I have seen a lot of posts regarding this method but it didn't help me a lot, so I thought I should write one myself which should help people clear problems and issues related to their problems.
IMPORTANT : First of all you should always have all the drivers installed on your PC.
READ EVERYTHING CAREFULLY AND MAKE SURE YOU HAVE FOLLOWED THE STEPS CAREFULLY AND THEN POST QUERIES.
The following drivers are needed for this task:
1. Lenovo USB Drivers.
2. QDLoader QFIL Drivers
Search for them on google and you will find them very easily. Most of the time they are there in the stock rom zip folder under a folder named Drivers.
Install all of them.
1. Download the Stock ROM you need for your phone from here:
DOWNLOAD STOCK FIRMWARE (Thanks to Shreps)
2. Extract the above zip to a folder. You will get three folders: Drivers, Images and Tools.
3. From the Drivers folder, Install all drivers.
4.IMPORTANT:: "DO NOT" install the QPST Tool from Tools folder. SEE F.A.Qs below.
5. Power Off your device.
6. Open QFIL TOOL.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
7. Now On top you will see two options: 1. Flat Build 2. Meta Build
Select FLAT BUILD
8. In "PROGRAMMER PATH" click Browse and go to the folder named Images and select the one file it displays (something like prog_emmc....mbn).
9. Now click "Load XML" and select "rawprogram0.xml" file and then another dialog box will open. Here select "patch0.xml".
PC WORK IS DONE. DO NOT CLICK DOWNLOAD.
Your device should be switched off.
NOTE CAREFULLY: Hold "VOLUME UP + VOLUME DOWN" key (Do not press POWER button). and connect the USB Cable from PC to the phone.
Your phone should now display RED LED LIGHT and the QFIL Tool should now change from NO PORT to QUALCOMM.....Something like that.
You are now ready. Click on Download button on QFIL TOOL and then wait for atleast 15 minutes.
After the dialog at bottom shows "DOWNLOAD SUCCESSFUL" in blue color, UNPLUG your device. Wait for a few seconds or a minute and then POWER ON your device.
First boot takes about 8-10 minutes.
This method should work really good as it did in my case.
If you have any issues. Post here.
F.A.Qs
Q: SAHARA FAIL ERROR?
A: I DID A LOT OF RESEARCH AND FOUND OUT THAT IT WAS DUE TO WRONG VERSION OF QFIL.
USE THIS VERSION:
https://docs.google.com/uc?id=0B_MAL3K1CFyUWUZNTTBVcmtzNGs&export=download
IT SHOULD FIX THAT PROBLEM.
Q. UPDATES NOT INSTALLING AFTER FLASHING OR ROOTING
Follow these steps:
1. Download Lenovo Smart Assistant.
2. Connect your phone and click Update ROM on the side menu. It will download the update.
3. When it says "Transferring" disconnect your phone.
4. Open C:/Program Files/LenovoSmartAssistant/plugins/7eabdc.. . (Something like that folder)/download
5. U will find update.zip. Extract the zip folder and find SYSTEM.ZIP.
6. Flash this system.zip from the recovery and you are good to go.
Hello, I have a bricked lenovo vibe k5 A6020I37 and get sahara fail.
I'm using Windows 7, disable the signature drivers, I do everything and I just get that sahara fail.
My phone enters automatically in download mode (red led light on when is plugged in).
I hope you can help me with this.
Enviado desde mi hi6210sft mediante Tapatalk
Turbonanox said:
Hello, I have a bricked lenovo vibe k5 A6020I37 and get sahara fail.
I'm using Windows 7, disable the signature drivers, I do everything and I just get that sahara fail.
My phone enters automatically in download mode (red led light on when is plugged in).
I hope you can help me with this.
Enviado desde mi hi6210sft mediante Tapatalk
Click to expand...
Click to collapse
Did you use the correct firmware? Mostly this occurs when you do not select the correct firmware according to your phone!
TeKnoGin said:
I have seen a lot of posts regarding this method but it didn't help me a lot, so I thought I should write one myself which should help people clear problems and issues related to their problems.
IMPORTANT : First of all you should always have all the drivers installed on your PC.
READ EVERYTHING CAREFULLY AND MAKE SURE YOU HAVE FOLLOWED THE STEPS CAREFULLY AND THEN POST QUERIES.
The following drivers are needed for this task:
1. Lenovo USB Drivers.
2. QDLoader QFIL Drivers
Search for them on google and you will find them very easily. Most of the time they are there in the stock rom zip folder under a folder named Drivers.
Install all of them.
1. Download the Stock ROM you need for your phone from here:
DOWNLOAD STOCK FIRMWARE (Thanks to Shreps)
2. Extract the above zip to a folder. You will get three folders: Drivers, Images and Tools.
3. From the Drivers folder, Install all drivers.
4. From the Tools folder, install the QPST Tool. In your Start Menu it will come as QFIL. Don't worry about that.
5. Power Off your device.
6. Open QFIL TOOL.
7. Now On top you will see two options: 1. Flat Build 2. Meta Build
Select FLAT BUILD
8. In "PROGRAMMER PATH" click Browse and go to the folder named Images and select the one file it displays (something like prog_emmc....mbn).
9. Now click "Load XML" and select "rawprogram0.xml" file and then another dialog box will open. Here select "patch0.xml".
PC WORK IS DONE. DO NOT CLICK DOWNLOAD.
Your device should be switched off.
NOTE CAREFULLY: Hold "VOLUME UP + VOLUME DOWN" key (Do not press POWER button). and connect the USB Cable from PC to the phone.
Your phone should now display RED LED LIGHT and the QFIL Tool should now change from NO PORT to QUALCOMM.....Something like that.
You are now ready. Click on Download button on QFIL TOOL and then wait for atleast 15 minutes.
After the dialog at bottom shows "DOWNLOAD SUCCESSFUL" in blue color, UNPLUG your device. Wait for a few seconds or a minute and then POWER ON your device.
First boot takes about 8-10 minutes.
This method should work really good as it did in my case.
If you have any issues. Post here.
Click to expand...
Click to collapse
Thanks Successfully works...but system update are not installing[emoji26]
sagar03 said:
Thanks Successfully works...but system update are not installing[emoji26]
Click to expand...
Click to collapse
Yeah! I know! I have a solution for that!
Follow these steps:
1. Download Lenovo Smart Assistant.
2. Connect your phone and click Update ROM on the side menu. It will download the update.
3. When it says "Transferring" disconnect your phone.
4. Open C:/Program Files/LenovoSmartAssistant/plugins/7eabdc.. . (Something like that folder)/download
5. U will find update.zip. Extract the zip folder and find SYSTEM.ZIP.
6. Flash this system.zip from the recovery and you are good to go.
Thank you
Should I install system.zip using custom recovery or stock recovery
Sent from my Lenovo A6020a40 using XDA-Developers mobile app
sagar03 said:
Should I install system.zip using custom recovery or stock recovery
Click to expand...
Click to collapse
Install it using stock recovery:
Select "Install update from sdcard" and select system.zip
Thank you
Sent from my Lenovo A6020a40 using XDA-Developers mobile app
TeKnoGin said:
Did you use the correct firmware? Mostly this occurs when you do not select the correct firmware according to your phone!
Click to expand...
Click to collapse
Hello, thanks for replying.
Yes, in fact I'm using the lenovo smart assistance's stock downloaded ROM
Enviado desde mi hi6210sft mediante Tapatalk
Turbonanox said:
Hello, thanks for replying.
Yes, in fact I'm using the lenovo smart assistance's stock downloaded ROM
Enviado desde mi hi6210sft mediante Tapatalk
Click to expand...
Click to collapse
Ohh! Then it shouldn't happen! I need to see what sahara fail is? Can you copy the log file and paste here so i can see the problem?
Can I use this method for vibe k5 a6020a40???
And can I get stock ROM & recovery in vibe k5???
Please answer sir
Sent from my Lenovo A6020a40 using XDA-Developers mobile app
sagar8070 said:
Can I use this method for vibe k5 a6020a40???
And can I get stock ROM & recovery in vibe k5???
Please answer sir
Click to expand...
Click to collapse
I don't know, but most probably it should. There is no major difference in the process and the arch ROM file so I guess it should work.
TeKnoGin said:
I don't know, but most probably it should. There is no major difference in the process and the arch ROM file so I guess it should work.
Click to expand...
Click to collapse
Sir muje flashing process mil gayi hai...
Aur a6020a40 ki stock ROM bhi mil gayi hai.. Lekin muje janana hai...
Kya har country ki ROM aalag hoti hai ya same hoti hai kyon ki Maine Jo ROM download ki hai wo ek Russian website par thi...
Sent from my Lenovo A6020a40 using XDA-Developers mobile app
sagar8070 said:
Sir muje flashing process mil gayi hai...
Aur a6020a40 ki stock ROM bhi mil gayi hai.. Lekin muje janana hai...
Kya har country ki ROM aalag hoti hai ya same hoti hai kyon ki Maine Jo ROM download ki hai wo ek Russian website par thi...
Click to expand...
Click to collapse
Tum ROM file ka full name batao main batata hun kahan ka hai?
TeKnoGin said:
Tum ROM file ka full name batao main batata hun kahan ka hai?
Click to expand...
Click to collapse
A6020a40_S029_160705_16G_ROW_qpst.7z
Sent from my Lenovo A6020a40 using XDA-Developers mobile app
sagar8070 said:
A6020a40_S029_160705_16G_ROW_qpst.7z
Click to expand...
Click to collapse
Yeah it is good! It should work definitely. Open it and see if it has the same images folder and also cross check your device model twice with the ROM you are flashing.
TeKnoGin said:
Yeah it is good! It should work definitely. Open it and see if it has the same images folder and also cross check your device model twice with the ROM you are flashing.
Click to expand...
Click to collapse
OK...
Thank you sir.[emoji120]
Sent from my Lenovo A6020a40 using XDA-Developers mobile app
sagar8070 said:
OK...
Thank you sir.[emoji120]
Click to expand...
Click to collapse
Try it out and please report.
Thank you!
No, look to me and listen up: THANK YOU!
Hi there ! Hope you're doing all right
I had a lot of issues recently with my phone : Crosscall Trekker M1
It all begin when I started to remove entirely Google from the phone.
I rooted it and took the liberty to delete all that mention google.
I unfortunately delete a system file and that how my problems began.
(I called couple of times the Technique Assistance from Crosscall's Website but they weren't able to help me and I had the same story with the SAV --> the after selling's services. I gave up about asking them help and I decided to solve the issue by my own.)
So for now the phone start on bootloop, (I cannot use the OS anymore) so I can launch it in Recovery mod only.
After days of researchs I found the original stock rom for the Trekker M1 !!
On the recovery : After I wiped data and cache of course :
I tried to install the Rom with the option : "Apply update from sd card" but it didn't worked.
So I tried to install differents Custom Recovery like CWM and even renamed them update.zip but I had the exact same issue:
"E : failed to verify whole-file signature
E : signature verification failed
Installation aborted."
I also wanted to try Odin but apparently Crosscall's phones doesn't have a recuperation mod (I dream that someone got me wrong on this :crying: )
I've got a few clues about all this :
I guess the Debugging USB Mod isn't enable anymore on the phone
Maybe the versions of ClockWorkMod weren't compatible at all with my phone.
All I know is that the phone is rooted;
The recovery's version is : "Android system recovery <3e> LMY47V release-keys"
So know you know everything
Does someone think, he or she can help me with this ?
Thank you for your attention !
Brazyxs said:
Hi there ! Hope you're doing all right
I had a lot of issues recently with my phone : Crosscall Trekker M1
It all begin when I started to remove entirely Google from the phone.
I rooted it and took the liberty to delete all that mention google.
I unfortunately delete a system file and that how my problems began.
(I called couple of times the Technique Assistance from Crosscall's Website but they weren't able to help me and I had the same story with the SAV --> the after selling's services. I gave up about asking them help and I decided to solve the issue by my own.)
So for now the phone start on bootloop, (I cannot use the OS anymore) so I can launch it in Recovery mod only.
After days of researchs I found the original stock rom for the Trekker M1 !!
On the recovery : After I wiped data and cache of course :
I tried to install the Rom with the option : "Apply update from sd card" but it didn't worked.
So I tried to install differents Custom Recovery like CWM and even renamed them update.zip but I had the exact same issue:
"E : failed to verify whole-file signature
E : signature verification failed
Installation aborted."
I also wanted to try Odin but apparently Crosscall's phones doesn't have a recuperation mod (I dream that someone got me wrong on this :crying: )
I've got a few clues about all this :
I guess the Debugging USB Mod isn't enable anymore on the phone
Maybe the versions of ClockWorkMod weren't compatible at all with my phone.
All I know is that the phone is rooted;
The recovery's version is : "Android system recovery <3e> LMY47V release-keys"
So know you know everything
Does someone think, he or she can help me with this ?
Thank you for your attention !
Click to expand...
Click to collapse
Hello,
Can you capture files included in update.zip?
-Hope- said:
Hello,
Can you capture files included in update.zip?
Click to expand...
Click to collapse
By uptade.zip do you think about the Rom or the Custom Recovery ?
And yes I can
Brazyxs said:
By uptade.zip do you think about the Rom or the Custom Recovery ?
And yes I can
Click to expand...
Click to collapse
Can u copy the stock ROM name before renaming it to update.zip and yeah I meant the update.zip
-Hope- said:
Can u copy the stock ROM name before renaming it to update.zip and yeah I meant the update.zip
Click to expand...
Click to collapse
Here's the name of the stock rom :
LU652R(HS-L635)_L1185.6.02.00.EU00_MultiDownload_201601292005_user.tar.gz
To correct what I said first : I didn't renamed the Rom in fact, I did it only with the CWM file who was actually in zip format
(Sorry about that)
I couldn't even try to install the Rom because the Recovery doesn't recognize it
Brazyxs said:
Here's the name of the stock rom :
LU652R(HS-L635)_L1185.6.02.00.EU00_MultiDownload_201601292005_user.tar.gz
To correct what I said first : I didn't renamed the Rom in fact, I did it only with the CWM file who was actually in zip format
(Sorry about that)
I couldn't even try to install the Rom because the Recovery doesn't recognize it
Click to expand...
Click to collapse
Can u provide me with a pic of the tar.gz file (the files inside it)
-Hope- said:
Can u provide me with a pic of the tar.gz file (the files inside it)
Click to expand...
Click to collapse
Here's 4 captures of the tar.gz opened with Winzip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
View attachment 4279786
View attachment 4279787
View attachment 4279788
Brazyxs said:
Here's 4 captures of the tar.gz opened with Winzip
View attachment 4279785
View attachment 4279786
View attachment 4279787
View attachment 4279788
Click to expand...
Click to collapse
Sorry for late reply however these files aren't falshable through recovery
they are flashed through QFIL
there are files called prog_emmc_firehose,rawprogram.xml, and patch.xml which is used to flash through qfil
-Hope- said:
Sorry for late reply however these files aren't falshable through recovery
they are flashed through QFIL
there are files called prog_emmc_firehose,rawprogram.xml, and patch.xml which is used to flash through qfil
Click to expand...
Click to collapse
Thank you very much ! I will check about QFIL by myself. For now I'm happy that someone care about my issues
I tell you if there is something new !
-Hope- said:
Sorry for late reply however these files aren't falshable through recovery
they are flashed through QFIL
there are files called prog_emmc_firehose,rawprogram.xml, and patch.xml which is used to flash through qfil
Click to expand...
Click to collapse
So it appear that the Crosscall M1 got an emergency mode. I can launch it by pressing Vol + and Vol - when I'm plugging the phone to a computer by USB.
At this moment a message show up :
"Authority indentification not found !"
"Long press power key to continue ..."
and if I do it :
No update file in TFcard!
X
Update failed!
Long press power key to power off.
If I start the phone on Emergency Mode with QFIL working (what I need to do) nothing happen.
I still have the message No Port Available on the top of QFIL.
So I'm wondering,
Do you think I can fix in some ways that problem of unrecognized device ?
or
Is there a way that I can install the Rom by choosing to install it as an update with the Emergency Mode. The Rom files would be the update that i put before in a "TFcard" in some format ?
Brazyxs said:
So it appear that the Crosscall M1 got an emergency mode. I can launch it by pressing Vol + and Vol - when I'm plugging the phone to a computer by USB.
At this moment a message show up :
"Authority indentification not found !"
"Long press power key to continue ..."
and if I do it :
No update file in TFcard!
X
Update failed!
Long press power key to power off.
If I start the phone on Emergency Mode with QFIL working (what I need to do) nothing happen.
I still have the message No Port Available on the top of QFIL.
So I'm wondering,
Do you think I can fix in some ways that problem of unrecognized device ?
or
Is there a way that I can install the Rom by choosing to install it as an update with the Emergency Mode. The Rom files would be the update that i put before in a "TFcard" in some format ?
Click to expand...
Click to collapse
Can you try to run it as an admin then choose the right com and try again ?
-Hope- said:
Can you try to run it as an admin then choose the right com and try again ?
Click to expand...
Click to collapse
I tried to run QFIL as an admin but it doesn't make a difference. The thing is that my device isn't recognize at all by my computer.
I sorry but what do you mean what "choose the right com" ?
Brazyxs said:
I tried to run QFIL as an admin but it doesn't make a difference. The thing is that my device isn't recognize at all by my computer.
I sorry but what do you mean what "choose the right com" ?
Click to expand...
Click to collapse
Did you install the qcom drivers
-Hope- said:
Did you install the qcom drivers ?
Click to expand...
Click to collapse
Hi, Here's the list of all the drivers I installed :
Qualcomm_USB_Driver_V1.0
MTK_USB_All_V1.0.8
ADBDriverInstaller
I also installed :
Android-sdk
Java SE Development Kit
After a lot of research my device still isn't showing on QFIL.
But for a time he showed up on "ADB Driver installer". I plugged the phone by USB and started it with a special combinaison (almost like the Emergency Mode's combinaison) that I'm still trying to remember.
There is also another a new thing. If I start my device that I plug before by USB and only with the power button :
My computer recognize it and the Driver Software Installation try to install MTP USB Device.
The operation failed everytime but for now I'm happy that the device is recognize.
Brazyxs said:
After a lot of research my device still isn't showing on QFIL.
But for a time he showed up on "ADB Driver installer". I plugged the phone by USB and started it with a special combinaison (almost like the Emergency Mode's combinaison) that I'm still trying to remember.
There is also another a new thing. If I start my device that I plug before by USB and only with the power button :
My computer recognize it and the Driver Software Installation try to install MTP USB Device.
The operation failed everytime but for now I'm happy that the device is recognize.
View attachment 4284734
Click to expand...
Click to collapse
Just reread the post, try to do a factory reset
-Hope- said:
Just reread the post, try to do a factory reset
Click to expand...
Click to collapse
The factory reset isn't working (and I just tried one more time), that is why I need to flash my rom.
Brazyxs said:
The factory reset isn't working (and I just tried one more time), that is why I need to flash my rom.
Click to expand...
Click to collapse
wait you said that adb works, if you can find the file system from an exact phone uploaded or you know that its common you can push it using adb if you are rooted
-Hope- said:
wait you said that adb works, if you can find the file system from an exact phone uploaded or you know that its common you can push it using adb if you are rooted
Click to expand...
Click to collapse
Yes I did said that, adb worked for a time.
I'm not sure to understand what you mean by "the file system" and "push it " with adb
The thing I'm sure of is that I'm rooted :good:
I'll continue my researchs.
Hello, I bought Redmi Note 7 from aliexpress, it came with EU Rom and unlocked bootloader, i thougth it was official so i decided to lock the bootloader so it will be more secure and i think it got bricked. And now i'm stuck in the recovery "This MIUI version can't be installed on this device", tried to unlock bootloader officially (i had permissions on my old Note 3), but i got "Current account is not bound to this device", tried flashing rom with chinese MI PC suite to no avail.
I'm out of options. Can it be unbricked, can services access edl mode and flash official rom or can i do something?
7enas said:
Hello, I bought Redmi Note 7 from aliexpress, it came with EU Rom and unlocked bootloader, i thougth it was official so i decided to lock the bootloader so it will be more secure and i think it got bricked. And now i'm stuck in the recovery "This MIUI version can't be installed on this device", tried to unlock bootloader officially (i had permissions on my old Note 3), but i got "Current account is not bound to this device", tried flashing rom with chinese MI PC suite to no avail.
I'm out of options. Can it be unbricked, can services access edl mode and flash official rom or can i do something?
Click to expand...
Click to collapse
youtube. com/watch?v=K4rDNl3GGPs (delete the empty part of the link)
use this method, use miflash and stable chinese rom. Remember after your phone alive again you have to wait for 7-15 days to unlock it again.
7enas said:
Hello, I bought Redmi Note 7 from aliexpress, it came with EU Rom and unlocked bootloader, i thougth it was official so i decided to lock the bootloader so it will be more secure and i think it got bricked. And now i'm stuck in the recovery "This MIUI version can't be installed on this device", tried to unlock bootloader officially (i had permissions on my old Note 3), but i got "Current account is not bound to this device", tried flashing rom with chinese MI PC suite to no avail.
I'm out of options. Can it be unbricked, can services access edl mode and flash official rom or can i do something?
Click to expand...
Click to collapse
Download MiFlasher and fastboot rom, Youtube the instruction. FIXED.
h0p3l3ss_s0ul said:
youtube. com/watch?v=K4rDNl3GGPs (delete the empty part of the link)
use this method, use miflash and stable chinese rom. Remember after your phone alive again you have to wait for 7-15 days to unlock it again.
Click to expand...
Click to collapse
So without opening the phone there is no way?
enzeruh said:
Download MiFlasher and fastboot rom, Youtube the instruction. FIXED.
Click to expand...
Click to collapse
Tried, got xbl error, if i would fix that, i would probably get error "can't flash in lock state".
7enas said:
Tried, got xbl error, if i would fix that, i would probably get error "can't flash in lock state".[/QUO
Dont know if you could flash from edl mode.
Click to expand...
Click to collapse
Try sideloading that fastboot rom to your device..
This might not be of help, but here's what I had to do to install the Polish MIUI/Xiaomi.eu variant (as I'm from Poland).
The first thing you need to do is to download Xiaomi's adb / fastboot tools ( https://miui.blog/any-devices/xiaomi-adb-fastboot-usb-drivers-tool/ ). After that, we connect the phone to the computer using the cable that was in the box with it. After connecting, locate the folder where the adb / fastboot tools are, press Shift + Right mouse button and choose the PowerShell window. After that, enter "adb devices" and if the correct phone name appears, enter "adb reboot bootloader". Thanks to this, the phone will go into Fastboot mode (you can skip this & go straight to fastboot). If possible, enter "fastboot devices" to check if the phone is still being detected. If it is, enter "fastboot flash recovery twrp.img" (after downloading the proper TWRP ), but DO NOT PRESS ENTER. At this point, disconnect the USB cable from the computer, press Enter in PowerShell and connect the phone again. If everything went correctly, you should have TWRP flashed without problems. Then, press the Power button on the phone until it vibrates, then immediately hold Power and Volume + until the phone enters TWRP itself. If everything went correctly, you can now upload MIUI immediately after the phone is in TWRP. Then, you can enjoy the new system.
Sithhy™ said:
This might not be of help, but here's what I had to do to install the Polish MIUI/Xiaomi.eu variant (as I'm from Poland).
The first thing you need to do is to download Xiaomi's adb / fastboot tools ( https://miui.blog/any-devices/xiaomi-adb-fastboot-usb-drivers-tool/ ). After that, we connect the phone to the computer using the cable that was in the box with it. After connecting, locate the folder where the adb / fastboot tools are, press Shift + Right mouse button and choose the PowerShell window. After that, enter "adb devices" and if the correct phone name appears, enter "adb reboot bootloader". Thanks to this, the phone will go into Fastboot mode (you can skip this & go straight to fastboot). If possible, enter "fastboot devices" to check if the phone is still being detected. If it is, enter "fastboot flash recovery twrp.img" (after downloading the proper TWRP ), but DO NOT PRESS ENTER. At this point, disconnect the USB cable from the computer, press Enter in PowerShell and connect the phone again. If everything went correctly, you should have TWRP flashed without problems. Then, press the Power button on the phone until it vibrates, then immediately hold Power and Volume + until the phone enters TWRP itself. If everything went correctly, you can now upload MIUI immediately after the phone is in TWRP. Then, you can enjoy the new system.
Click to expand...
Click to collapse
^ this something new i've seen, unfortunately i sent it to service, they said will try to reflash (they even said i might need a new mobo with is a nonsense), if they fail i will try this. Thank you.
Im in the same condition, full brick, no image, no vibration, nothing. The only thing that can save him is an authorized account, but I live in Argentina and I'm a student, I can't pay $ 30, it's a lot of money here. If you find a solution please post it. I'm desperate
Try flashing the global fastboot rom via miflash tool.It will surely work
Infiniction said:
Try flashing the global fastboot rom via miflash tool.It will surely work
Click to expand...
Click to collapse
Error: Flashing is not allowed in the lock state
Downloaded latest europe fastboot and now i get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi there! How are you? Could you solve the problem? How did you do it? Thank you!
TinoSantos said:
Hi there! How are you? Could you solve the problem? How did you do it? Thank you!
Click to expand...
Click to collapse
Just open your phone back ( https://www.youtube.com/watch?v=arV7POS-iiM ) i used hairdryer instead ( safer ), remove screws and disconnect the battery (yellow screws, blue battery connector) or just follow the vid ). Test point ( https://www.youtube.com/watch?v=XzknDcBovWw ) then flash china rom if you have chinese variant. Then apply for BL unlocking, after unlocking flash GLOBAL or whatever version you want with MiFlasher ( DON"T CHOOSE FLASH AND LOCK). Never lock again if not on china rom (on china variant)
7enas said:
Just open your phone back ( https://www.youtube.com/watch?v=arV7POS-iiM ) i used hairdryer instead ( safer ), remove screws and disconnect the battery (yellow screws, blue battery connector) or just follow the vid ). Test point ( https://www.youtube.com/watch?v=XzknDcBovWw ) then flash china rom if you have chinese variant. Then apply for BL unlocking, after unlocking flash GLOBAL or whatever version you want with MiFlasher ( DON"T CHOOSE FLASH AND LOCK). Never lock again if not on china rom (on china variant)
Click to expand...
Click to collapse
Thanks, it doesn`t work for me because the phone is in edl mode already, when try to flash says "only nup and sig tag can be received before flash anything", so only with an edl authorized account, even with QFIL and SDM660 modified programmer. I will have to pay a person who has it and never buy a xiaomi again, this has already happened to me with other brands (I like modding) and solved it easily with a pc in 15 min. Thank you.
(GTranslate)
TinoSantos said:
Thanks, it doesn`t work for me because the phone is in edl mode already, when try to flash says "only nup and sig tag can be received before flash anything", so only with an edl authorized account, even with QFIL and SDM660 modified programmer. I will have to pay a person who has it and never buy a xiaomi again, this has already happened to me with other brands (I like modding) and solved it easily with a pc in 15 min. Thank you.
(GTranslate)
Click to expand...
Click to collapse
Hola, tenías el cel desbloqueado? podes explicarme que te paso en una de esas te puedo dar una mano. levanta el cel? llega al sistema? si tenias el sistema desbloqueado se supone que debiste haberte logueado con una cuenta de xiomi/miui por lo cual deberias poder usarla para desbloquear, sino te levanta el cel pero esta desbloqueado deberias poder acceder por adb para entrar en un recovery y de ahi flashearlo. avisame cual es el problema exacto a ver.
Hi people, noob user here
My Mate 9 MHA-L09 stays bricked after i rebrand via HWOTA or update by any method, but i can bring it back to life only with IDT and board software (EMUI 5 - Android 7). Tried differents methods with nougat and oreo firmwares:
HWOTA update from sdcard or windows (brick)
Twrp, then supersu or magisk and update zip (brick)
dload folder with sd card upgrade or 3 button method (brick)
fastboot flash images with Huawei Update extractor (brick)
After that, phone stays bricked, no fastboot, recovery, battery charge, nothing. I plug it to usb and its recognized as huawei com usb (without using testpoint), and then i return to the beginning flashing board software (made that like 20 times by now :crying::crying::crying::crying Pleaseee send some help !!
OK I can help you, it's really easy by the way, did you know which version do you have before the disaster?
Version and cust?
lefkiller said:
OK I can help you, it's really easy by the way, did you know which version do you have before the disaster?
Version and cust?
Click to expand...
Click to collapse
Hi, in fact I had no cust because I sent my phone to a technician and he left it like Build System 8.0.0.x(xxx), I couldn't unlock bootloader with dc unlocker because not supported. So I thought the only way was to downgrade with board software and flash new firmware but now I'm in a loop for like 1 week with this problem.
Do you have access to recovery? Bootloader? It allows you flash something?
lefkiller said:
Do you have access to recovery? Bootloader? It allows you flash something?
Click to expand...
Click to collapse
Yes, I can do everything, but after EMUI update process shows "Finished, device will restart" it doesn't, gets bricked. Then I have to flash board software again to boot my phone
OK, what method are you using to flash?
DC Phoenix or dload?
And what firmware are you trying to flash?
Wen all this happens to you what firmware has you in the phone?
Are trying to install your same region?
Answer me all Tha questions and probably I can give you the way to solve you problem
lefkiller said:
OK, what method are you using to flash?
DC Phoenix or dload?
And what firmware are you trying to flash?
Wen all this happens to you what firmware has you in the phone?
Are trying to install your same region?
Answer me all Tha questions and probably I can give you the way to solve you problem
Click to expand...
Click to collapse
HWOTA update from sdcard or windows (brick)
Twrp, then supersu or magisk and update zip (brick)
dload folder with sd card upgrade or 3 button method (brick)
fastboot flash images with Huawei Update extractor (brick)
Click to expand...
Click to collapse
Tried Nougat and Oreo firmwares, rebrand, same model or L29, AL00 (C636, C432, C605). Maybe its an xloader thing, i don't know
OK, but you are not answering my questions, what is you older version, original oeminfo, etc, needed to have success fixing your phone.
Try this:
1 Flash board firmware (idt)
2 Boot on maintenance system and check in manufacturer menu background USB port, manufacturer mode (*#*#2846579#*#*)
3 on HCU client (paid) unlock your phone if needed and fix numbers if your device has Meid use CDMA fix if not use UMTS (imei, model, vendor, country, etc)
Unmark flash as empty board and the opción for QC
4 now you most have a pretty nice Boot loop, so you need to enter fastboot mode, in fastboot mode disconnect the cable USB and press volume bottoms at the same time you are now in fastboot submeno, just luck for shut down opción
5 flash you stock rom in force mode pressing all de buttons at the same time, using a SD card/dload/UPDATE. APP
the rom most be one newest than the one you have before, that's why I ask to you but you don't answer me
That's it, welcome back to your phone
I'm my case I use the rom MHA-L29C605B375 downloaded from androidhost.ru, lock for one whit only 2 archives.
lefkiller said:
OK, but you are not answering my questions, what is you older version, original oeminfo, etc, needed to have success fixing your phone.
Try this:
1 Flash board firmware (idt)
2 Boot on maintenance system and check in manufacturer menu background USB port, manufacturer mode (*#*#2846579#*#*)
3 on HCU client (paid) unlock your phone if needed and fix numbers if your device has Meid use CDMA fix if not use UMTS (imei, model, vendor, country, etc)
Unmark flash as empty board and the opción for QC
4 now you most have a pretty nice Boot loop, so you need to enter fastboot mode, in fastboot mode disconnect the cable USB and press volume bottoms at the same time you are now in fastboot submeno, just luck for shut down opción
5 flash you stock rom in force mode pressing all de buttons at the same time, using a SD card/dload/UPDATE. APP
the rom most be one newest than the one you have before, that's why I ask to you but you don't answer me
That's it, welcome back to your phone
I'm my case I use the rom MHA-L29C605B375 downloaded from androidhost.ru, lock for one whit only 2 archives.
Click to expand...
Click to collapse
Like I said, my phone was running Oreo (I think) and build was System 8.0.0.0xx, could't use themes, bank apps also didn't work, that's why I tried to downgrade so I could flash new firmware :angel: I have no idea what oeminfo was, I'm sorry . I will give a try to HCU
Oeminfo contains model, vendor, country, etc, if you don't know fixed whit HCU, they have tutorial for that
https://hcu-client.com/huawei-phone-country-vendor-repair/
Just follow that and you will be OK, be sure to flash a proper rom, dload method
lefkiller said:
OK, but you are not answering my questions, what is you older version, original oeminfo, etc, needed to have success fixing your phone.
Try this:
1 Flash board firmware (idt)
2 Boot on maintenance system and check in manufacturer menu background USB port, manufacturer mode (*#*#2846579#*#*)
3 on HCU client (paid) unlock your phone if needed and fix numbers if your device has Meid use CDMA fix if not use UMTS (imei, model, vendor, country, etc)
Unmark flash as empty board and the opción for QC
4 now you most have a pretty nice Boot loop, so you need to enter fastboot mode, in fastboot mode disconnect the cable USB and press volume bottoms at the same time you are now in fastboot submeno, just luck for shut down opción
5 flash you stock rom in force mode pressing all de buttons at the same time, using a SD card/dload/UPDATE. APP
the rom most be one newest than the one you have before, that's why I ask to you but you don't answer me
That's it, welcome back to your phone
I'm my case I use the rom MHA-L29C605B375 downloaded from androidhost.ru, lock for one whit only 2 archives.
Click to expand...
Click to collapse
No success on step 5, I tried to install MHA-L09C605B360 (8.0.0.360) with HWOTA, same problem, device restart then hard brick.
Flashed board software again (100th time), HCU thing, dload update (this time with MHA-L09C605B375 8.0.0.375) with 3 buttons and then "Software Update Failed" at 5%
Can you show me the image of HCU Wen you repair UMTS or CDMA
lefkiller said:
can you show me the image of hcu wen you repair umts or cdma
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pabl0cv said:
No success on step 5, I tried to install MHA-L09C605B360 (8.0.0.360) with HWOTA, same problem, device restart then hard brick.
Flashed board software again (100th time), HCU thing, dload update (this time with MHA-L09C605B375 8.0.0.375) with 3 buttons and then "Software Update Failed" at 5%
Click to expand...
Click to collapse
This update is the one whit just 2 files?
Download this https://androidhost.ru/SG5
Okay, after hours of trying, reading a lot of threads, I concluded this:
Neither B360, 361, 362, etc., worked, UNTIL B375. How did I realize that? earlier I said something about the xloader partition, I don't know clearly what it means but what I did was extract the XLOADER partition image from UPDATE.APP of every build (with huawei update extractor). Then I flashed with fastboot (fastboot flash xloader xloaderfile.img). Every image I tried FAILED image xloader1 verification error, until I tried with XLOADER.img from B375, it said OKAY. Finally, as I knew that build would work, flashed the whole firmware (3 files), following this GUIDE from mankindtw. Btw I repaired imei, vendor, country with hcu after flashing board software
Now I have a second problem, I can't unlock my sim. If someone could help me here, HCU says Error, not supported
View attachment 5091113
lefkiller said:
OK, but you are not answering my questions, what is you older version, original oeminfo, etc, needed to have success fixing your phone.
Try this:
1 Flash board firmware (idt)
2 Boot on maintenance system and check in manufacturer menu background USB port, manufacturer mode (*#*#2846579#*#*)
3 on HCU client (paid) unlock your phone if needed and fix numbers if your device has Meid use CDMA fix if not use UMTS (imei, model, vendor, country, etc)
Unmark flash as empty board and the opción for QC
4 now you most have a pretty nice Boot loop, so you need to enter fastboot mode, in fastboot mode disconnect the cable USB and press volume bottoms at the same time you are now in fastboot submeno, just luck for shut down opción
5 flash you stock rom in force mode pressing all de buttons at the same time, using a SD card/dload/UPDATE. APP
the rom most be one newest than the one you have before, that's why I ask to you but you don't answer me
That's it, welcome back to your phone
I'm my case I use the rom MHA-L29C605B375 downloaded from androidhost.ru, lock for one whit only 2 archives.
Click to expand...
Click to collapse
Te lo dije en el número 3, primera linea
Te lo dije en el número 3, primera linea
Click to expand...
Click to collapse
You were right, I should have done that before repair with hcu. "Read sim unlock codes" did nothing, only "direct sim unlock" worked for me.
So, finally after more than a week , what I did was:
Flash board software with IDT and testpoint
Repair phone with "Direct sim unlock" in HCU (paid 3 euro)
Repair umts (imei, model, vendor, country) (paid 8 euro, 24h timed license)
Flashed B375 ROM with HWOTA guide
After boot system, unlocked frp and bootloader, then upgraded to Pie build 9.0.1.189 with HWOTA9 guide as I didn't receive any official update from huawei
Now my phone is receiving ota updates :highfive::victory: thank you so much :laugh:
The step with HWOTA was not necessary, with dload it was more than enough, all the updates came to me until reaching 9.1.0.252, after that I have not received anything else, in FF I see that there is up to 9.1.0.275, I have my doubts whether to do it by dload
lefkiller said:
The step with HWOTA was not necessary, with dload it was more than enough, all the updates came to me until reaching 9.1.0.252, after that I have not received anything else, in FF I see that there is up to 9.1.0.275, I have my doubts whether to do it by dload
Click to expand...
Click to collapse
dload update (this time with MHA-L09C605B375 8.0.0.375) with 3 buttons and then "Software Update Failed" at 5%
Click to expand...
Click to collapse
Dload method didn't make it for me, for sure I missed or did something wrong
lefkiller said:
This update is the one whit just 2 files?
Download this https://androidhost.ru/SG5
Click to expand...
Click to collapse
This works nice whit dload method, just 2 files in it
The important thing is that you managed to recover the equipment and now everything is functional