Related
Hi,
I was in the process of flashing new firmware (iI have a thread for this when asking advice and followed the steps on my previous thread) I was flashing firmware 5.11.401.11 which loaded succesfully and rebooted to bootloader.
When it rebooted a driver message cam up I think regarding Qsub or something and the device has frozen or dead.
In the command window it says "wating for device"...i cant seem to get it to do anything!!
My device shows as other devices in my computerQHSUSB-DLOAD and the message I recall was about drivers ...do i need to update them?
Any help please?
Shepps
shepppster said:
Hi,
I was in the process of flashing new firmware (iI have a thread for this when asking advice and followed the steps on my previous thread) I was flashing firmware 5.11.401.11 which loaded succesfully and rebooted to bootloader.
When it rebooted a driver message cam up I think regarding Qsub or something and the device has frozen or dead.
In the command window it says "wating for device"...i cant seem to get it to do anything!!
My device shows as other devices in my computerQHSUSB-DLOAD and the message I recall was about drivers ...do i need to update them?
Any help please?
Shepps
Click to expand...
Click to collapse
Seem's like you may have skipped an important firmware update, which firmware number were you updating from?
If you skipped a firmware version e.g 3.xx.401.x to 5.xx.401.x then you will be needing the Unbrick project here http://forum.xda-developers.com/showthread.php?t=2770684
Danny201281 said:
Seem's like you may have skipped an important firmware update, which firmware number were you updating from?
If you skipped a firmware version e.g 3.xx.401.x to 5.xx.401.x then you will be needing the Unbrick project here http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
I did go consecutively fro 3-4-5 but..I guess It happens. The firmware seemed to flash ok.
I will try the link.
Thanks
shepppster said:
I did go consecutively fro 3-4-5 but..I guess It happens. The firmware seemed to flash ok.
I will try the link.
Thanks
Click to expand...
Click to collapse
Ok the unbricking has worked so far....can someone confirm the fastboot commands in Linux are the same as on a windows CMD prompt please?
I dont want to get this far and not flash the firmware properly.
Danny201281 said:
Seem's like you may have skipped an important firmware update, which firmware number were you updating from?
If you skipped a firmware version e.g 3.xx.401.x to 5.xx.401.x then you will be needing the Unbrick project here http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
Is there a guide on the forum for using Linux so i get the last part (Flashing firmware) perfect please?
shepppster said:
Is there a guide on the forum for using Linux so i get the last part (Flashing firmware) perfect please?
Click to expand...
Click to collapse
Fastboot works just the same in Linux as in Windows with the exception of you must use "sudo"
So
Code:
fastboot devices
becomes
Code:
sudo fastboot devices
Code:
fastboot flash zip firmware.zip
becomes
Code:
sudo fastboot flash zip firmware.zip
and so on if you forget to use sudo you will just see "waiting for device" in which case press ctrl+c to cancel and do command again with sudo :good:
shepppster said:
I did go consecutively fro 3-4-5 but..I guess It happens. The firmware seemed to flash ok.
I will try the link.
Thanks
Click to expand...
Click to collapse
What actually happened is when I was flashing from 4****** to 5***** when I tried to reboot to booloader my PC wanted to reinstall device drivers ,which I think I cancelled by mistake causing the hang up?
I have unbricked and now in bootloader waiting for the device to recharge fully.
I have then got to flash the 5****** series of firmware again(as instructed by the unbrick software).
I will then either install a custom recovery and flash my jellybean back-up or a custom ROM, do you think ARHD 84 will install on the 5***** firmware? I dont fancy going to 6**** until all is ok.
Or is there a way of flashing a stock o/s that can be flashed from TWRP? for the WWE firmware?
Shepps
shepppster said:
What actually happened is when I was flashing from 4****** to 5***** when I tried to reboot to booloader my PC wanted to reinstall device drivers ,which I think I cancelled by mistake causing the hang up?
I have unbricked and now in bootloader waiting for the device to recharge fully.
I have then got to flash the 5****** series of firmware again(as instructed by the unbrick software).
I will then either install a custom recovery and flash my jellybean back-up or a custom ROM, do you think ARHD 84 will install on the 5***** firmware? I dont fancy going to 6**** until all is ok.
Or is there a way of flashing a stock o/s that can be flashed from TWRP? for the WWE firmware?
Shepps
Click to expand...
Click to collapse
Ok I have unbricked my device and used TWRP to recover my back up....however after flashing up to 5******** firmware ,the firmware seems to have reverted back to the 2******* series I started with??? Is that correct?
If so I have to start all over again?
shepppster said:
Ok I have unbricked my device and used TWRP to recover my back up....however after flashing up to 5******** firmware ,the firmware seems to have reverted back to the 2******* series I started with??? Is that correct?
If so I have to start all over again?
Click to expand...
Click to collapse
no firmware does not revert back .. where are you getting these files ?
clsA said:
no firmware does not revert back .. where are you getting these files ?
Click to expand...
Click to collapse
This is the information from my phone the "about" section in settings. software number 2.24.161.1 i havent gone as far as a getvar cmd in fastboot yet,if thats where the correct info will be?
shepppster said:
This is the information from my phone the "about" section in settings. software number 2.24.161.1 i havent gone as far as a getvar cmd in fastboot yet,if thats where the correct info will be?
Click to expand...
Click to collapse
I see in the Unbrick Project Thread your device is fixed But for the record the Software Number in settings is the software number of the rom not the firmware :good: Glad to hear your back up though good job. :highfive:
Danny201281 said:
I see in the Unbrick Project Thread your device is fixed But for the record the Software Number in settings is the software number of the rom not the firmware :good: Glad to hear your back up though good job. :highfive:
Click to expand...
Click to collapse
Ah I thought it might be...all I need know is to move to 6**401 firmware so I can flash the latest ktkt roms (not lolipop) I was a bit of a mare but find it easier to my Ubuntu pc as I dont have to worry about drivers and the like.
Thanks Danny
shepppster said:
Ah I thought it might be...all I need know is to move to 6**401 firmware so I can flash the latest ktkt roms (not lolipop) I was a bit of a mare but find it easier to my Ubuntu pc as I dont have to worry about drivers and the like.
Thanks Danny
Click to expand...
Click to collapse
No Problem, And yeah i'm a Linux user myself and it is the shizzle when it comes to android phones
Danny201281 said:
No Problem, And yeah i'm a Linux user myself and it is the shizzle when it comes to android phones
Click to expand...
Click to collapse
I intend to carry on where I left off...I havent got as far a flashing the new rom.
The 401 firmware I am using is currently 5.11.401.10 ,next step is the 6 series.
Is it best to flash 6.09.401.5 then 401.10,401.11,401.12 consecutively or jump straight to 12?(clearly I dont want to go through the bricking stuff again!!)
Is there a link to a good source of firmware,i looked on the Vomer guide but they are decribed as the dual simHTC one at the download page, is this going to be an issue as I will get them from there as a reliably good source?
http://forum.xda-developers.com/showthread.php?t=2365506
shepppster said:
I intend to carry on where I left off...I havent got as far a flashing the new rom.
The 401 firmware I am using is currently 5.11.401.10 ,next step is the 6 series.
Is it best to flash 6.09.401.5 then 401.10,401.11,401.12 consecutively or jump straight to 12?(clearly I dont want to go through the bricking stuff again!!)
Is there a link to a good source of firmware,i looked on the Vomer guide but they are decribed as the dual simHTC one at the download page, is this going to be an issue as I will get them from there as a reliably good source?
http://forum.xda-developers.com/showthread.php?t=2365506
Click to expand...
Click to collapse
I know that some have jumped strait to the latest without any problems and the theory goes as Lon as you don't skip a version number e.g 3.xx to 5.xx then it should be safe.
Obviously the safest option is to flash each update so you know your not missing anything important. As for a good source I prefer to stick with HTC signed firmware from official OTA updates all of which you can find here http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
Danny201281 said:
I know that some have jumped strait to the latest without any problems and the theory goes as Lon as you don't skip a version number e.g 3.xx to 5.xx then it should be safe.
Obviously the safest option is to flash each update so you know your not missing anything important. As for a good source I prefer to stick with HTC signed firmware from official OTA updates all of which you can find here http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
Click to expand...
Click to collapse
@Danny201281 and @clsA Thanks for all your help...successfully flashed up to the latest 6******** firmware and flashed a custom rom.
Perhaps minscule to u guys but massive step forward for me !
Few nailbiting moments anticipating a brick again..but it worked fine using Ubuntu which is much less finicky than windows to use and my weapon of choice from now on!
:good::good:
So I tried FunkyHuawei to downgrade from pie beta to official. Now i'm bricked totally. Only getting into fastboot and are not unlocked. My guess is i'm screwed. Can't access Erecovery neither. Stupidity pays it price.
Any ideas at all? Cant really do anything, and the screen is all black too.
superior888 said:
So I tried FunkyHuawei to downgrade from pie beta to official. Now i'm bricked totally. Only getting into fastboot and are not unlocked. My guess is i'm screwed. Can't access Erecovery neither. Stupidity pays it price.
Any ideas at all? Cant really do anything, and the screen is all black too.
Click to expand...
Click to collapse
What model do you have (rebranded or not) , what firmware did you choose on funky site?
If you still can boot into fastboot mode funky should be able to recover it.
forever_lol said:
What model do you have (rebranded or not) , what firmware did you choose on funky site?
If you still can boot into fastboot mode funky should be able to recover it.
Click to expand...
Click to collapse
I have CLT29C432. Tried the downgrade method through hisuite. I'll check with em
superior888 said:
I have CLT29C432. Tried the downgrade method through hisuite. I'll check with em
Click to expand...
Click to collapse
Please specify What firmware you tried to flash
Did you modify your phone somehow? Rebrand/bootloader unlock?
forever_lol said:
Please specify What firmware you tried to flash
Did you modify your phone somehow? Rebrand/bootloader unlock?
Click to expand...
Click to collapse
Downgrade from EMUI9 to EMUI8 CLT-L29 8.1.0.156(C432)
that one. No nothing. it was on the beta program as i bought it.
Tried to install it again but getting fail when installig recovery in Hisuite...
superior8888 said:
Downgrade from EMUI9 to EMUI8 CLT-L29 8.1.0.156(C432)
that one. No nothing. it was on the beta program as i bought it.
Tried to install it again but getting fail when installig recovery in Hisuite...
Click to expand...
Click to collapse
This thing remains mystery to me.
I have literally the same model, and I've downgraded from Pie (both beta and stable 163) using the same method and firmware several times. I've never had any issues. In the changelog for rollback firmware you've chosen you can find:
"1. Please make sure you are currently using the official version of Huawei EMUI, and that no unofficial updates have been installed. Otherwise, there will be risk of an unsuccessful rollback, and an unknown error may occur. 2. Make sure that the current version has not been unlocked or rooted. "
But since you've never fiddled with your handset, never unlocked your bootloader this warning shouldn't apply to you.
Have you tried flashing pie again via OTG?
I would but i cant access recovery. I mean the otg is ready to go..i tried several firmware
from funky with same error when flashing recovery. I usually solve bricks but this got me :-\
How about extracting the erecovery source from the update package and try installing erecovery via fastboot instead of hisuite?
VinCme said:
How about extracting the erecovery source from the update package and try installing erecovery via fastboot instead of hisuite?
Click to expand...
Click to collapse
Wouldnt be possible i guess. As i said bootloader is locked...
Skickat från min G3311 via Tapatalk
Going to send it for repair. Still warranty and they probably never know what happend..so.
superior888 said:
So I tried FunkyHuawei to downgrade from pie beta to official. Now i'm bricked totally. Only getting into fastboot and are not unlocked. My guess is i'm screwed. Can't access Erecovery neither. Stupidity pays it price.
Any ideas at all? Cant really do anything, and the screen is all black too.
Click to expand...
Click to collapse
My case is similar. I downgraded from B195 to rollback B161. Now I am literally doomed. No erecovery, no huawei logo, just plain black fastboot screen. My bootlodaer is unlocked and I'm unable to relock it. Huawei is denying service, is there any way to revive my black dead phone???
twrp.img gets flashed succesfully but doesnt boot into it.
I can only speak for BLA-L29C432B197 (Probably B179 too), but I assume this will cover any Pie firmware released in January.
In these releases Huawei disabled custom kernel, so phone won't boot with a custom kernel flashed.
This had me wanting to downgrade to B161 where it does work. So I try with NoCheck, which is fine to update with, Software install failed.
I try with FH (I happened to have a credit left) HiSuite method, Software install failed.
I tried with Dload package, same result.
So I figure I can use Rollback, as it worked fine on Beta to get back to Oreo with it...
It failed after 7% (or so, I didn't actually watch), device reboot to a black screen. Fastboot was working though.
So it most likely only flashed Oreo bootloader, and device was hardbricked. I managed to get it back using test point and IDT, this will void your warranty though.
So, do not downgrade using NoCheck recovery and rollback package, it's not worth the time to get device back.
Edit: Downgrade from Pie B197 to Oreo B157 is fine using NoCheck.
ante0 said:
So, do not downgrade using NoCheck recovery and rollback package, it's not worth the time to get device back.
Click to expand...
Click to collapse
So, there are no options to downgrade from 197? WTF is wrong with Huawei?
ante0 said:
So, do not downgrade using NoCheck recovery and rollback package, it's not worth the time to get device back.
Click to expand...
Click to collapse
And probably will also require spending money on other tools. Backups are also important, so people with rooted devices should use Partitions Backup (by wanam) and backup nvme, oeminfo and modem partitions.
As for downgrading with DLOAD or HiSuite we have no idea if it will work or if it will brick. Original recovery/eRecovery might have a fail safe mechanism.
badmania98 said:
So, there are no options to downgrade from 197? WTF is wrong with Huawei?
Click to expand...
Click to collapse
Dload might work or just refuse to downgrade, but i don't think it will brick.
Pretoriano80 said:
Partitions Backup (by wanam) and backup nvme, oeminfo and modem partitions.
Click to expand...
Click to collapse
Where I can find this app, and what version I have to use?
I installed Partitions Backup & Restore 2.0.1.
LE. Backup Done.
also.it's happened in alp-al00（mate10 china）.
Sent from my HUAWEI ALP-AL00 using XDA Labs
”5. This system version can be rolled back to the official version of EMUI 8.0 in Phone Manager. Rolling back the system version will erase your personal data. For more information, please contact the customer service hotline.” - according to description of v.197 firmware.
Where is this option in the phone menu? It is written in v.179 firmware, also.
badmania98 said:
”5. This system version can be rolled back to the official version of EMUI 8.0 in Phone Manager. Rolling back the system version will erase your personal data. For more information, please contact the customer service hotline.” - according to description of v.197 firmware.
Where is this option in the phone menu? It is written in v.179 firmware, also.
Click to expand...
Click to collapse
There's none! I don't know what they mean with Phone Manager. My guess is that HiSuite = Phone Manager.
zt379 said:
also.it's happened in alp-al00（mate10 china）.
Click to expand...
Click to collapse
When downgrading with No_check recovery?
I asked Huawei centre about downgrade and they told me that is possible in service centre only.
ante0 said:
I can only speak for BLA-L29C432B197 (Probably B179 too), but I assume this will cover any Pie firmware released in January.
In these releases Huawei disabled custom kernel, so phone won't boot with a custom kernel flashed.
This had me wanting to downgrade to B161 where it does work. So I try with NoCheck, which is fine to update with, Software install failed.
I try with FH (I happened to have a credit left) HiSuite method, Software install failed.
I tried with Dload package, same result.
So I figure I can use Rollback, as it worked fine on Beta to get back to Oreo with it...
It failed after 7% (or so, I didn't actually watch), device reboot to a black screen. Fastboot was working though.
So it most likely only flashed Oreo bootloader, and device was hardbricked. I managed to get it back using test point and IDT, this will void your warranty though.
So, do not downgrade using NoCheck recovery and rollback package, it's not worth the time to get device back.
Click to expand...
Click to collapse
Hey there, search on forum a tool for P20 Pro. From 179 i came back on 158 Oreo
Pretoriano80 said:
There's none! I don't know what they mean with Phone Manager. My guess is that HiSuite = Phone Manager.
When downgrading with No_check recovery?
Click to expand...
Click to collapse
perhaps never! and now hope xda developers could handle this bad things
Sent from my HUAWEI ALP-AL00 using XDA Labs
lorenzomeini56 said:
Hey there, search on forum a tool for P20 Pro. From 179 i came back on 158 Oreo
Click to expand...
Click to collapse
Can you put a link to this tool.?
badmania98 said:
Can you put a link to this tool.?
Click to expand...
Click to collapse
https://forum.xda-developers.com/huawei-p20/how-to/guide-how-to-rollback-emui-9-beta-to-t3841687
lorenzomeini56 said:
Hey there, search on forum a tool for P20 Pro. From 179 i came back on 158 Oreo
Click to expand...
Click to collapse
does it works in other kirin970 devices of emui9 to emui8？？
Sent from my HUAWEI ALP-AL00 using XDA Labs
lorenzomeini56 said:
https://forum.xda-developers.com/huawei-p20/how-to/guide-how-to-rollback-emui-9-beta-to-t3841687
Click to expand...
Click to collapse
This tool we already have it. I dont know if ante0 used it this time, but I think he did ( contains nocheck.img).
badmania98 said:
This tool we already have it. I dont know if ante0 used it this time, but I think he did ( contains nocheck.img).
Click to expand...
Click to collapse
Yep. Same NoCheck.img.
Edit: well, unless that nocheck is for p20... That might be why.
I will compare them.
I can confirm that in connecting my ALP-29 to my Windows 10 PC with HiSuite, I get offered the choice to roll back to Oreo. But the small print warns that your device should not be rooted or unlocked. I'm happy with Pie, so I'm not tempted to check whether this works without bricking your device, but just letting folks know about the purported option. Presumably if you try, you should at minimum unroot first......You also will be factory wiped.
ante0 said:
to get back to Oreo .
Click to expand...
Click to collapse
To what version of Oreo did you tried to get back?
badmania98 said:
To what version of Oreo did you tried to get back?
Click to expand...
Click to collapse
B150, the rollback version. I figured that would work as it is a rollback. But I should maybe have gone with B158.
Either way, don't do it with NoCheck for BLA
I'm almost done repairing device!
ante0 said:
B150, the rollback version. I figured that would work as it is a rollback. But I should maybe have gone with B158.
Click to expand...
Click to collapse
B150 was the roll back from Pie Beta. According to FF, I think that B156 and 157 are the roll back from official Pie.
badmania98 said:
B150 was the roll back from Pie Beta. According to FF, I think that B156 and 157 are the roll back from official Pie.
Click to expand...
Click to collapse
B157 should be the roll-back version. But a P20 Pro owner bricked when downgrading with HiSuite, with a completely stock device, so....
Success is disgusted by some people, and will not share any files for free in the future.
That's all good but 2 questions
1. How to unlock BL
2. And is it possible to cross china to global and vise versa
ilia1985 said:
That's all good but 2 questions
1. How to unlock BL
2. And is it possible to cross china to global and vise versa
Click to expand...
Click to collapse
I know how to unlock the bootloader, but I am not going to release it.
johnny886 said:
I know how to unlock the bootloader, but I am not going to release it.
Click to expand...
Click to collapse
Ok, it's your choice but what the point of the firmwares? You would rather share something that's is useless to most without BL unlock and keep it to your self. I personally wouldn't mind paying for BL unlock if that is your game here.
ilia1985 said:
Ok, it's your choice but what the point of the firmwares? You would rather share something that's is useless to most without BL unlock and keep it to your self. I personally wouldn't mind paying for BL unlock if that is your game here.
Click to expand...
Click to collapse
https://forum.xda-developers.com/bl...ckshark-3-3-pro-3s-unlock-bootloader-t4141537
thank you
Do you have china joy ui 12 update zip ?
I need global rom ota for update bs3
http://cdn-test-ota.blackshark.com/KLE-A0/20201113095044-klein-ota-signed_by_xiaomi_50fbd88a4e23e10d3f4cbb7e2d11add1.zip
http://cdn-test-ota.blackshark.com/KLE-A0/20201113095044-klein-ota-signed_by_xiaomi_50fbd88a4e23e10d3f4cbb7e2d11add1.zip
hello XDA team
I need help with this Xiaomi Black Shark 3
Model: SHARK KLE-A0
it only stays in Fastboot, I have the bootloader unlocked
any solution to fix my problem please
I try to flash twrp but it always fails, it doesn't go into recovery mode, it only shows fastboot mode
tomelich said:
hello XDA team
I need help with this Xiaomi Black Shark 3
Model: SHARK KLE-A0
it only stays in Fastboot, I have the bootloader unlocked
any solution to fix my problem please
I try to flash twrp but it always fails, it doesn't go into recovery mode, it only shows fastboot mode
Click to expand...
Click to collapse
I recently had this issue and fixed it after a lot of trial and error. Try flashing twrp through a different usb port l. Let me know what error you are getting when you flash recovery in adb cmd. You can pm me.
how to flash this?
aerial4ce said:
I recently had this issue and fixed it after a lot of trial and error. Try flashing twrp through a different usb port l. Let me know what error you are getting when you flash recovery in adb cmd. You can pm me.
Click to expand...
Click to collapse
thank you very much for answering bro
the problem is that it already passed several versions of twrp it shows that it flashed successfully
but it does not enter recovery, it returns to fastboot mode
I searched many sides for firmware for EDL mode and only came across this software, but I can't download it
http : //www. viprom. cn/list/9451. html
unbrick
tomelich said:
hello XDA team
I need help with this Xiaomi Black Shark 3
Model: SHARK KLE-A0
it only stays in Fastboot, I have the bootloader unlocked
any solution to fix my problem please
I try to flash twrp but it always fails, it doesn't go into recovery mode, it only shows fastboot mode
Click to expand...
Click to collapse
Better you flash factory rom. Flash by Qfil application on pc. On me for further information
Can anyone provide
CN-ROM - KLEN2107141CN00MR0
I Can pay thx
is cn ota rom KLEN2105310CN00DRX joyUI 12.5
KLEN2106230CN00MR0.zip
drive.google.com
-https://drive.google.com/file/d/1iWN1TvUEP9AdWL1CxIyK7Oi-bf_lkscg/view?usp=sharing-
here is joyui12.5 MR0 rom
kevin mitnick said:
-https://drive.google.com/file/d/1iWN1TvUEP9AdWL1CxIyK7Oi-bf_lkscg/view?usp=sharing-
here is joyui12.5 MR0 rom
Click to expand...
Click to collapse
Im converted to global. How to flash bro?
Jbazt_katuforzs said:
Im converted to global. How to flash bro?
Click to expand...
Click to collapse
just flash firmware by Qfil application
kevin mitnick said:
-https://drive.google.com/file/d/1iWN1TvUEP9AdWL1CxIyK7Oi-bf_lkscg/view?usp=sharing-
here is joyui12.5 MR0 rom
Click to expand...
Click to collapse
Hey man thx for the share, i tried to flash it with TWRP but is says that the zip is corrupted.
Hi, I've tryed to install realme UI 2.0, but during the installation i have an error and the update arrested ,i never unlock the bootloader and my versione Is C.38, can anyone help me?
Did you succeed?
If not,
How did you try to install RUI 2.0?
Have you ever tried to format your phone through the recovery mode?
Kydaix said:
Did you succeed?
If not,
How did you try to install RUI 2.0?
Have you ever tried to format your phone through the recovery mode?
Click to expand...
Click to collapse
Nope, I'm still in c38
I tryed in recovery and on file explorer
Yes, wipe all data
But, you didn't get the update in the settings?
If no, wait for it.
If yes,
Ok so, even after that, it still doesn't want to do the update?
Then, you should try that: Realme flash Guide (If you haven't already), then update! (need to unlock bootloader first)
Kydaix said:
But, you didn't get the update in the settings?
If no, wait for it.
If yes,
Ok so, even after that, it still doesn't want to do the update?
Then, you should try that: Realme flash Guide (If you haven't already), then update! (need to unlock bootloader first)
Click to expand...
Click to collapse
Nope , however many people have updated so and then it worked, I do not know what my problem is ...
I know that before upgrading it is better to keep the bootloader locked
antonio96ct said:
Nope , however many people have updated so and then it worked, I do not know what my problem is ...
I know that before upgrading it is better to keep the bootloader locked
Click to expand...
Click to collapse
Personally, I haven't had any problems even though I have an unlocked bootloader since I got my smartphone.
I think you should just wait in this case to avoid problems. ^^