Accidentally when i updated from B360 to B365, i immediately got prompted with the update to B367, and due my motivation to go on latest security patch i didn't stored the B367 package on my HDD, so i didn't had the chance to extract from it the stock boot and recovery images for future updates. Now B368 is out and obviously I'm in need of those files; someone have a copy of them to share with me (and other members too)?
RedSkull23 said:
Accidentally when i updated from B360 to B365, i immediately got prompted with the update to B367, and due my motivation to go on latest security patch i didn't stored the B367 package on my HDD, so i didn't had the chance to extract from it the stock boot and recovery images for future updates. Now B368 is out and obviously I'm in need of those files; someone have a copy of them to share with me (and other members too)?
Click to expand...
Click to collapse
I think you can use the recovery and boot.img of B360/B365 etc. if you have mate can try else let me know I will download the file and share.
Edit- last file I see available on FF is B366 that too OTA file and full firmware is available only for B365.
shashank1320 said:
I think you can use the recovery and boot.img of B360/B365 etc. if you have mate can try else let me know I will download the file and share.
Edit- last file I see available on FF is B366 that too OTA file and full firmware is available only for B365.
Click to expand...
Click to collapse
Yeah already gave a check on FF bro and as you said it's since B365 that other updates aren't uploaded, so I'll give a try with B365 files... If it should work, I'll report it here... Hope so.
RedSkull23 said:
Yeah already gave a check on FF bro and as you said it's since B365 that other updates aren't uploaded, so I'll give a try with B365 files... If it should work, I'll report it here... Hope so.
Click to expand...
Click to collapse
It will work 99.99%. i have tested this many times..good luck bro
shashank1320 said:
It will work 99.99%. i have tested this many times..good luck bro
Click to expand...
Click to collapse
Nice to hear that, i thought about this some day ago but i was afraid that every recovery.img had its own signature, md5 or SHA calc incompatible if found unmatched by next recovery. Gonna try that, thanks friend
shashank1320 said:
It will work 99.99%. i have tested this many times..good luck bro
Click to expand...
Click to collapse
Today i flashed B365 boot and recovery files: at phone startup I've encountered bizzare things, like an unmatching PIN of screen unlock (never changed it in months), and so I wasn't able to access the phone anymore; luckily i always have with me on my external SD my previous backup, so i reflashed TWRP by fastboot and restored the backup, recovering the access to my device. Anyway i took the files requested by me by myself; for everyone that could ever need 'em, you can find those here
BLN-L21C432B367 boot.img - https://www.dropbox.com/sh/5ltsb3h1ad7yc8y/AAALUixZJTSVIPDcvf__GM-ga
BLN-L21C432B367 recovery.img - https://www.dropbox.com/sh/x28ch38regyzcy9/AAAoXz1w_zqMdqBldBdpF37ta
RedSkull23 said:
Today i flashed B365 boot and recovery files: at phone startup I've encountered bizzare things, like an unmatching PIN of screen unlock (never changed it in months), and so I wasn't able to access the phone anymore; luckily i always have with me on my external SD my previous backup, so i reflashed TWRP by fastboot and restored the backup, recovering the access to my device. Anyway i took the files requested by me by myself; for everyone that could ever need 'em, you can find those here
BLN-L21C432B367 boot.img - https://www.dropbox.com/sh/5ltsb3h1ad7yc8y/AAALUixZJTSVIPDcvf__GM-ga
BLN-L21C432B367 recovery.img - https://www.dropbox.com/sh/x28ch38regyzcy9/AAAoXz1w_zqMdqBldBdpF37ta
Click to expand...
Click to collapse
Sorry to hear about the problem. I am confused now as I had only b357 recovery that i used on many, starting from b350,357,360,365,375,379 and all worked fine for me. But its Huawei so can't say anything new things every day.
shashank1320 said:
Sorry to hear about the problem. I am confused now as I had only b357 recovery that i used on many, starting from b350,357,360,365,375,379 and all worked fine for me. But its Huawei so can't say anything new things every day.
Click to expand...
Click to collapse
Don't worry pal, nothing hard to solve. Huawei devices improved my problem solving :laugh: Recovery sounds ok to use, in fact i think that it was surely boot.img faults.
RedSkull23 said:
Don't worry pal, nothing hard to solve. Huawei devices improved my problem solving :laugh:.
Click to expand...
Click to collapse
Ain't that the truth!! I only used the device for a short time but I learned so much in those few weeks.
Dazed No More said:
Ain't that the truth!! I only used the device for a short time but I learned so much in those few weeks.
Click to expand...
Click to collapse
Ahah! Well everything's a problem on Huawei devices, from updating till various recovery procedures... All experience achieved for future tweaking! Always if there won't be a new Huawei :cyclops:
RedSkull23 said:
All experience achieved for future tweaking! Always if there won't be a new Huawei :cyclops:
Click to expand...
Click to collapse
Exactly. I'll never buy another Huawei phone but it was a great learning experience. My OnePlus 5T came two days ago so my sister got a new phone and I got a great device with tons of development....a win win situation:good:
Dazed No More said:
Exactly. I'll never buy another Huawei phone but it was a great learning experience. My OnePlus 5T came two days ago so my sister got a new phone and I got a great device with tons of development....a win win situation:good:
Click to expand...
Click to collapse
If only 1+ was cheaper, I'd went for it too! Awesome performances but great community support also... I found better support on my previous device, a Galaxy S4 Mini, than here on Honor. You surely did a nice switch
Related
I was able to flash the rooted boot.img, but it seems to have caused a problem with the fingerprint sensor. It works a little after a fresh reboot, but then it stops working completely. Anyone have an idea as to why and maybe how I can fix it?
i have the same problem, you fix it?
Probably, incompatible Boot
Try flash stock Boot back and check Fingerprint
5[Strogino] said:
Probably, incompatible Boot
Try flash stock Boot back and check Fingerprint
Click to expand...
Click to collapse
yeah, but we dont have the stock boot, we have tha us version c567 and its not online yet
Same problem
Abumarf said:
I was able to flash the rooted boot.img, but it seems to have caused a problem with the fingerprint sensor. It works a little after a fresh reboot, but then it stops working completely. Anyone have an idea as to why and maybe how I can fix it?
Click to expand...
Click to collapse
Hi Abumarf and depooltrd,
I have the same symptoms. I've flashed boot.img from C432 (rooted now) to my C567. It was the only way to unbrick it.
What region is rooted boot.img you flashed from. Do you think it is a software problem, not a hardware one?
Also, could anyone who has rooted MHA-L29C567B138 confirm that the fingerprint sensor works fine?
night_wind said:
Hi Abumarf and depooltrd,
I have the same symptoms. I've flashed boot.img from C432 (rooted now) to my C567. It was the only way to unbrick it.
What region is rooted boot.img you flashed from. Do you think it is a software problem, not a hardware one?
Also, could anyone who has rooted MHA-L29C567B138 confirm that the fingerprint sensor works fine?
Click to expand...
Click to collapse
I'm not sure as to what region I flashed but I can guarantee you it's a software problem. After checking the System/Bin/ it was clear that the fingerprintID folder and a few others were missing. This is most likely what causes the Fingerprint sensor to no longer work. All we can do is wait for Huawei to release the complete C567 update so we can revert to complete stock.
Abumarf said:
I can guarantee you it's a software problem. After checking the System/Bin/ it was clear that the fingerprintID folder and a few others were missing.
Click to expand...
Click to collapse
That is promising. So did you notice these problems right after you had flashed the boot.img?
BTW, it could work for hours after a fresh restart for me. What about yours?
night_wind said:
That is promising. So did you notice these problems right after you had flashed the boot.img?
BTW, it could work for hours after a fresh restart for me. What about yours?
Click to expand...
Click to collapse
Yes, as soon as I flashed both boot images that I had. One with root and the other with stock. I asked around and a dev buddy of mine told me that the KangVIP root isn't always interchangeable with the non-KangVIP roms. It was the same case for the Mate 8. Mine works for a few minutes at most, but I did flash an unknown stock boot image though it did nothing. It's a pain to live without a fingerprint sensor
Abumarf said:
Yes, as soon as I flashed both boot images that I had. One with root and the other with stock. I asked around and a dev buddy of mine told me that the KangVIP root isn't always interchangeable with the non-KangVIP roms. It was the same case for the Mate 8. Mine works for a few minutes at most, but I did flash an unknown stock boot image though it did nothing. It's a pain to live without a fingerprint sensor
Click to expand...
Click to collapse
I've just ran into this same issue, you think someone could just upload the missing files?
posydon1 said:
I've just ran into this same issue, you think someone could just upload the missing files?
Click to expand...
Click to collapse
I don't think so but I think there may be some hope. Ajsmsg78 released a full root and encryption guide (https://forum.xda-developers.com/mate-9/development/root-root-mate-9-t3556590) which I'm going to try from the complete beginning later to see if it'll restore functionality.
Abumarf said:
I don't think so but I think there may be some hope. Ajsmsg78 released a full root and encryption guide (https://forum.xda-developers.com/mate-9/development/root-root-mate-9-t3556590) which I'm going to try from the complete beginning later to see if it'll restore functionality.
Click to expand...
Click to collapse
That's exactly how I ended up here lol. His method works great but some file are still missing.
posydon1 said:
That's exactly how I ended up here lol. His method works great but some file are still missing.
Click to expand...
Click to collapse
Then we may be stuck until Huawei releases the C567 update. It's pretty disappointing that we seem to be the only version without an update even after almost a month and a half from release. :crying:
Abumarf said:
Then we may be stuck until Huawei releases the C567 update. It's pretty disappointing that we seem to be the only version without an update even after almost a month and a half from release. :crying:
Click to expand...
Click to collapse
Hey Abumarf,
Looks like Huawei released the new MHA-L29C567B167 and also decrypted-boot-MHA-L29C567B138.img has appeared as well. Did you try to flash any of them? Did it fix the fingerprint sensor?
night_wind said:
Hey Abumarf,
Looks like Huawei released the new MHA-L29C567B167 and also decrypted-boot-MHA-L29C567B138.img has appeared as well. Did you try to flash any of them? Did it fix the fingerprint sensor?
Click to expand...
Click to collapse
No I haven't as of yet. I've been trying to download the C567B167 OTA through Firmware Finder but it wasn't working for me. I also haven't had much time to look into it. If you or anyone else do end up trying either of the solutions, please let me know.
Abumarf said:
No I haven't as of yet. I've been trying to download the C567B167 OTA through Firmware Finder but it wasn't working for me. I also haven't had much time to look into it. If you or anyone else do end up trying either of the solutions, please let me know.
Click to expand...
Click to collapse
I tried decrypted-boot-MHA-L29C567B138.img and it fixed the fingerprint sensor, but I didn't manage to restore data partitions and the ROM wasn't full. Finally, I updated through FunkyHuawei and everything works fine now.
night_wind said:
I tried decrypted-boot-MHA-L29C567B138.img and it fixed the fingerprint sensor, but I didn't manage to restore data partitions and the ROM wasn't full. Finally, I updated through FunkyHuawei and everything works fine now.
Click to expand...
Click to collapse
I also did just that but just fixed the problem with the Huawei apps and system update by changing a few file names. Works like a charm now. Will wait till Monday and attempt to flash the B167 update. But as of now, I'm fully root, decrypted, and enjoying life!
what is the official update for my phone it is BLL-L22 and it is now on b160 (marshmallow)
i have installed the b360 but it has few issues such as 1) no update app 2) build no is tester not official no and so on
yoko89 said:
what is the official update for my phone it is BLL-L22 and it is now on b160 (marshmallow)
i have installed the b360 but it has few issues such as 1) no update app 2) build no is tester not official no and so on
Click to expand...
Click to collapse
It may be because you flashed it manually. And unless we have rollback package for your model you may not be able to rollback to MM. Are you planning to install custom ROM or want to be on stock rom only.
Updater is not there means tou wont get OTA bit test build wont impact anything.
You may need to flash the oeminfo of your model as well.
shashank1320 said:
It may be because you flashed it manually. And unless we have rollback package for your model you may not be able to rollback to MM. Are you planning to install custom ROM or want to be on stock rom only.
Updater is not there means tou wont get OTA bit test build wont impact anything.
You may beed to flash the oeminfo of your model as well.
Click to expand...
Click to collapse
I forgot to update oeminfo now i am updating to 370 as it is the latest and will update oeminfo
yoko89 said:
I forgot to update oeminfo now i am updating to 370 as it is the latest and will update oeminfo
Click to expand...
Click to collapse
Good luck. If need help just post it with details. We will try as much as we can
shashank1320 said:
Good luck. If need help just post it with details. We will try as much as we can
Click to expand...
Click to collapse
Updated successfully using firmware finder
yoko89 said:
Updated successfully using firmware finder
Click to expand...
Click to collapse
I knew from the first post that it was Firmware Finder's fault!! Now your build number is correct?
RedSkull23 said:
I knew from the first post that it was Firmware Finder's fault!! Now your build number is correct?
Click to expand...
Click to collapse
Yes
yoko89 said:
Yes
Click to expand...
Click to collapse
Ok perfect
yoko89 said:
Yes
Click to expand...
Click to collapse
Hide IMEI.
Also, updater in setting visible? How about FM, manager, theme etc?
shashank1320 said:
Hide IMEI.
Also, updater in setting visible? How about FM, manager, theme etc?
Click to expand...
Click to collapse
Yes every thing is working more tha fine
yoko89 said:
Yes every thing is working more tha fine
Click to expand...
Click to collapse
That is cool. Few reported one or the other things missing
Bll-l22c636 b160 to nougat
shashank1320 said:
That is cool. Few reported one or the other things missing
Click to expand...
Click to collapse
Hi.
Bought gr 5 '17 yesterday. Running MM.
I want to update to Nougat, cant find my build number in firmware finder list.
Fb group admin (also member here...) suggested to download a B 370 package.
I want to ask will it work for B160?
Also, any link to step by step instructions for update? Sorry, non tech person here...
Note: if i click to dl a package from Firmware finder, it shows dl as a zip file. Once download is complete, then what?
Thanks in Advance.
GR5_17 said:
Hi.
Bought gr 5 '17 yesterday. Running MM.
I want to update to Nougat, cant find my build number in firmware finder list.
Fb group admin (also member here...) suggested to download a B 370 package.
I want to ask will it work for B160?
Also, any link to step by step instructions for update? Sorry, non tech person here...
Note: if i click to dl a package from Firmware finder, it shows dl as a zip file. Once download is complete, then what?
Thanks in Advance.
Click to expand...
Click to collapse
Give me your exact current build number
shashank1320 said:
Give me your exact current build number
Click to expand...
Click to collapse
Thank you for your reply.
Build number : BLL-L22C636B160
GR5_17 said:
Thank you for your reply.
Build number : BLL-L22C636B160
Click to expand...
Click to collapse
I would advise to wait for official OTA (as you got the phone yesterday) but if you really want to do it-
Download this- http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1279/g104/v82620/f2/full/update.zip
and this http://update.hicloud.com:8180/TDS/...cseas/update_data_full_BLL-L22_hw_spcseas.zip
Flash first file and boot to system. Then 2nd and boot.
You need to use dload method as below
Unzip 1st file and extract the package. You will get few files including update.app.
Few suggest to use only update.app file but I would advise, based on my personal experience for all dload method I tried, use all the files.
Create a folder dload under SD card and copy all the files to this folder.
Power off the phone. Remove USB cable, if connected.
Press volume up+volume down keys and simultaneously press power button (3 keys together)
Your phone will automatically detect the package and will start the update process.
Once the update process is successful, you will get a message as update was successful and your phone will restart automatically.
During restart, phone will verify the system image.
This verification and 1st boot may take upto 2-3 minutes so do not panic.
Repeat the same with 2nd zip file.
Good luck. Happy Flashing.
shashank1320 said:
I would advise to wait for official OTA (as you got the phone yesterday) but if you really want to do it-
Download this- http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1279/g104/v82620/f2/full/update.zip
and this http://update.hicloud.com:8180/TDS/...cseas/update_data_full_BLL-L22_hw_spcseas.zip
Flash first file and boot to system. Then 2nd and boot.
You need to use dload method as below
Unzip 1st file and extract the package. You will get few files including update.app.
Few suggest to use only update.app file but I would advise, based on my personal experience for all dload method I tried, use all the files.
Create a folder dload under SD card and copy all the files to this folder.
Power off the phone. Remove USB cable, if connected.
Press volume up+volume down keys and simultaneously press power button (3 keys together)
Your phone will automatically detect the package and will start the update process.
Once the update process is successful, you will get a message as update was successful and your phone will restart automatically.
During restart, phone will verify the system image.
This verification and 1st boot may take upto 2-3 minutes so do not panic.
Repeat the same with 2nd zip file.
Good luck. Happy Flashing.
Click to expand...
Click to collapse
Thank you very much for the detailed instructions and links.
I think I will take your advice and wait for OTA update.
As mentioned, I am not too 'tech' and am worried might do the wrong thing.
Is it normal for my build # not to have nougat update yet?....
I will bookmark this post and report back in a week. Hopefully I will have an update by then.
Thank you again shashank1320
GR5_17 said:
Thank you very much for the detailed instructions and links.
I think I will take your advice and wait for OTA update.
As mentioned, I am not too 'tech' and am worried might do the wrong thing.
Is it normal for my build # not to have nougat update yet?....
I will bookmark this post and report back in a week. Hopefully I will have an update by then.
Thank you again shashank1320
Click to expand...
Click to collapse
You welcome. Welcome to XDA and tech stuff.
Yes it is normal. Update may pop up anytime. Have you inserted the SIM yet? If not, putting the SIM may help. Also it may take upto a week for your phone to register and get update.
Regards,
Shashank
shashank1320 said:
You welcome. Welcome to XDA and tech stuff.
Yes it is normal. Update may pop up anytime. Have you inserted the SIM yet? If not, putting the SIM may help. Also it may take upto a week for your phone to register and get update.
Regards,
Shashank
Click to expand...
Click to collapse
Thank you for your Welcome Shashank I hope to learn alot from the XDA Forum and you, since this is my 1st Android phone o).
I had not inserted the SIM before, since I'm still learning how the phone works and was playing around with the GR 5 17 without the SIM.
I have inserted the SIM and just like you said; I got an update from the Settings menu.
I am downloading update : BLL-L22C636B360 as we speak.
I am worried since I read on this thread that it might have some problems....
I will post an update once completed.
I am excited to learn more about Android from the XDA Forum, and how I can keep my GR 5 17 in the best condition.
Thank you again for your support Shashank. Stay Well
GR5_17 said:
Thank you for your Welcome Shashank I hope to learn alot from the XDA Forum and you, since this is my 1st Android phone o).
I had not inserted the SIM before, since I'm still learning how the phone works and was playing around with the GR 5 17 without the SIM.
I have inserted the SIM and just like you said; I got an update from the Settings menu.
I am downloading update : BLL-L22C636B360 as we speak.
I am worried since I read on this thread that it might have some problems....
I will post an update once completed.
I am excited to learn more about Android from the XDA Forum, and how I can keep my GR 5 17 in the best condition.
Thank you again for your support Shashank. Stay Well
Click to expand...
Click to collapse
Don't worry, download and install it. If there is any issue you may download further updates. There will few more if your model has it. I got a phone couple of days back amd got 3 updates(different model though)
shashank1320 said:
Don't worry, download and install it. If there is any issue you may download further updates. There will few more if your model has it. I got a phone couple of days back amd got 3 updates(different model though)
Click to expand...
Click to collapse
I have downloaded the B360 update. As you mentioned, I have received another update and am now on : Build number ~: BLL-L22C636B384 , EMUI : 5.0.1, Android : 7.0
Things seem to be working fine for now.
I wanted to ask you about any good Dark theme for the GR5-17.
Do you suggest from the Huawei themes (built in) or from :EMUI theme factory? (an app I dl from PlayStore.
Thank you, Stay Well
Hello everyone,
Today around 12:00, my phone did install the latest EMUI update available (365). However, I didn't noticed it and then I couldn't stop it ...
It messed up my system and I wasn't able to boot. eRecovery wasn't working either (unable to get packages).
I had twrp so I thought this was no big deal, but I couldn't manage to reinstall a stock rom, nor install a custom rom (I've tried them all, and none was working : blackscreens all the time), even thought I have experience in flashing roms and messing around with smartphones
I tried to rollback to an older version of my stock rom using huawei's rollback package (even if the manual says that I shouldn't do this since I unlocked my bootloader). The installation was flawless, and then it rebooted to reset my user data. The reset failed, and still couldn't boot.
I've tried to install custom roms again after that, but I was missing "/vendor" and "/product".
I am desperate and out of ideas.
I have access to bootloader, I have fastboot, twrp, and I have experience in flashing and all this stuff.
If you like challenges and you wanna proove that you're the very best like no one ever was, your help is much appreciated
Best regards,
Hazreath
PS : sorry for any english mistake
Can you boot to erecovery?
Sent from my Honor 8 Pro using XDA Labs
adriansticoid said:
Can you boot to erecovery?
Sent from my Honor 8 Pro using XDA Labs
Click to expand...
Click to collapse
Yes I can boot into eRecovery !
Thanks for your interest sir
Hazreath said:
If eRecovery is the thing that you boot in when you press VOL +, VOL - and POWER, I have access to it.
However, if you're talking about the eRecovery we can boot in with a normal boot and 3sec VOL+ press, I'm afraid I can't ...
Thanks for your interest sir
Click to expand...
Click to collapse
I was talking about the second one. The first one was ghe dload flash. You use it if you want to manually flash a firmware. Maybe you cantry that too. Download a full firmware for your model (more or less 2GB in size), extract the update.app inside and put it in dload folder inside storage, and press the volume up, volume down and power buttons.
Sent from my Honor 8 Pro using XDA Labs
I already tried that and it led me to nothing :/
I tried both the EMUI 5.0 firmware and the rollback to EMUI 4.1. They were the only ones availables.
5.0 install failed(uncompatible), and rollback install worked but then user data reset failed...
What was your idea with the second one ? I can access to it, I was wrong (I modified my post a minute ago )
Thanks again
Problem solved !
I made a dload with a update.zip that I found here -> http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v74972/f1/full/update.zip
I'm in EMUI 4.1 and everything works fine (I miss the drawer but it works).
Thanks for your investment sir, and have a nice day
Hazreath said:
Problem solved !
I made a dload with a update.zip that I found here -> http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v74972/f1/full/update.zip
I'm in EMUI 4.1 and everything works fine (I miss the drawer but it works).
Thanks for your investment sir, and have a nice day
Click to expand...
Click to collapse
Glad you fixed it. Have a nice day as well. :highfive:
Sent from my Honor 8 Pro using XDA Labs
I M HAVING SAME PROBLEM HOW U MADE zip
when i click it downloads a zip
what to do now?
i have only twrp and fastboot a screen where it shows ur devices is unlocked in yellow text
where to flash this file?
will this file save my phone?
hey guys when i flash wipe or do anything in twrp it says unable to mount vendor product, invalid arguments.
i got this by flashing an vendor.img provided in a rom(eliterom)
after that my devices waas not booting after waiting for an hour i gone to twrp and tried restoring my backup of stock emui 5 but it fails to wipe vendor and product partitions.
what to do now
how to unbrick
i have working fastboot and working fastboot
is there any file which can i flash??
plz help me its so urgent
narshi shukla said:
I M HAVING SAME PROBLEM HOW U MADE zip
when i click it downloads a zip
what to do now?
i have only twrp and fastboot a screen where it shows ur devices is unlocked in yellow text
where to flash this file?
will this file save my phone?
hey guys when i flash wipe or do anything in twrp it says unable to mount vendor product, invalid arguments.
i got this by flashing an vendor.img provided in a rom(eliterom)
after that my devices waas not booting after waiting for an hour i gone to twrp and tried restoring my backup of stock emui 5 but it fails to wipe vendor and product partitions.
what to do now
how to unbrick
i have working fastboot and working fastboot
is there any file which can i flash??
plz help me its so urgent
Click to expand...
Click to collapse
Get the zip file and extract it in a "dload" folder (create it) to your sdcard.
Put the sdcard into your phone and boot by pressing vol+,vol- and power, then click on the first option and wait !
Sorry I saw your answer a bit late :/
Hazreath said:
Get the zip file and extract it in a "dload" folder (create it) to your sdcard.
Put the sdcard into your phone and boot by pressing vol+,vol- and power, then click on the first option and wait !
Sorry I saw your answer a bit late :/
Click to expand...
Click to collapse
He fixed his device. Guided him step by step on telegram and all is fine now and he is back on BLN-L22 b340 with everything working perfectly fine :good:
shashank1320 said:
He fixed his device. Guided him step by step on telegram and all is fine now and he is back on BLN-L22 b340 with everything working perfectly fine :good:
Click to expand...
Click to collapse
On telegram ? You're a pretty retro dude haha
Well thanks a lot I was worried that he had already threw his phone away !
Take care !
Good to hear this.
Hazreath said:
On telegram ? You're a pretty retro dude haha
Well thanks a lot I was worried that he had already threw his phone away !
Take care !
Click to expand...
Click to collapse
Telegram took me to the past centuries lol.
Anything to help in real time to avoid much of the mess is Ok. I was free for a while so helped quickly and he was quick to understand the things and follow everything as per instructions and was able to restore the phone.
shashank1320 said:
He fixed his device. Guided him step by step on telegram and all is fine now and he is back on BLN-L22 b340 with everything working perfectly fine :good:
Click to expand...
Click to collapse
I am having a similar problem can i get some assistance please? I am trying various update.zip via dload method and none works for me
shashank1320 said:
Telegram took me to the past centuries lol.
Anything to help in real time to avoid much of the mess is Ok. I was free for a while so helped quickly and he was quick to understand the things and follow everything as per instructions and was able to restore the phone.
Click to expand...
Click to collapse
I'm having a hard time with my Honor 6x, will you please provide some help ? I saw your guide for dload method but I couldn't get it to work.
anthony1876 said:
I am having a similar problem can i get some assistance please? I am trying various update.zip via dload method and none works for me
Click to expand...
Click to collapse
Lets connect on Telegram Friday please. been stuck with few things.
id- shashank1320
---------- Post added at 11:52 PM ---------- Previous post was at 11:52 PM ----------
oneprivy said:
I'm having a hard time with my Honor 6x, will you please provide some help ? I saw your guide for dload method but I couldn't get it to work.
Click to expand...
Click to collapse
Lets connect on Telegram Friday please. been stuck with few things.
id- shashank1320
Anybody tried to install it? Is it possible that this is the oreo Update we have been waiting for since it ends with B401 instead of the usual B3XX?
Lukke2804 said:
Anybody tried to install it? Is it possible that this is the oreo Update we have been waiting for since it ends with B401 instead of the usual B3XX?
Click to expand...
Click to collapse
UPDATE: I tried to install it, doesnt work.(Via Dload)
It's nougat.
Changelog: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1774/g1755/v111861/f1/full/changelog.xml
It looks like security patches. The best thing is that we are not receiving these updates, they only showss on FF...i'm still waiting for B399 in Italy..
Giuskiller said:
It looks like security patches. The best thing is that we are not receiving these updates, they only showss on FF...i'm still waiting for B399 in Italy..
Click to expand...
Click to collapse
Same here in Germany. I am still on B394 and have the security patch from August. This is awful. The worst thing is to see them every month making a version with the current security patches but dont rolling them out. How hard could it be. Seriously, Honor has to improve this.
Lukke2804 said:
Same here in Germany. I am still on B394 and have the security patch from August. This is awful. The worst thing is to see them every month making a version with the current security patches but dont rolling them out. How hard could it be. Seriously, Honor has to improve this.
Click to expand...
Click to collapse
What more can i say? Just totally agree with you. Today i've read that Honor 8 Pro has received official beta Oreo in India, and we don't even know if we're in or out. We just know "the device is under testing phase". What the hell, i'm not an exited guy about updates and i know i shouldn't "expect" Oreo because usually Huawei/Honor just give one major update, but i can't give up to marketing needs. I can't believe and i can't give up to the idea that one day they could easily tell us that our device "hasn't passed the compatibility test" because we all know the our H8 can handle oreo on the hardware side. Even lower specs device can, why could our device be "incompatible"? Well, i think that a company has to put users first rather than money. If they made the same thing about H7 i can't trust them anymore and i will look to other companies.
P.s i know hat the CEO told H8 is in list to be updated, then removed this part...but without any official news at today i won't believe it.
P.P.s I know i bought a great device that works well and still better compared to other, in fact i'm not judging the product itself but the market strategy behind Honor products, wich should really be revisioned because you can't produce for example 10 device a year and fully support just few of them and for less time than they deserve.
I tried it by TWRP, i get error 7 on update.zip Someone know why?
I think this is the Spectre patch for this device. How b**tards the people are at Huawei/Honor that they can't release this critical security update for the Honor 8 (FRD-L09C432)!
The update is still Nougat with the Android patch level now at 1st January 2018. Attached is the screenshot from About Phone.
Anonshe said:
The update is still Nougat with the Android patch level now at 1st January 2018. Attached is the screenshot from About Phone.
Click to expand...
Click to collapse
You flashed it ? if so how.
Anonshe said:
The update is still Nougat with the Android patch level now at 1st January 2018. Attached is the screenshot from About Phone.
Click to expand...
Click to collapse
please tell us how you made to flash it. I tried it with TWRP and i bricked my phone :laugh:
Sheldd said:
please tell us how you made to flash it. I tried it with TWRP and i bricked my phone :laugh:
Click to expand...
Click to collapse
How did you brick your phone? I bricked my phone too when trying to flash B140 I was able to recover it only with DU Phoenix, nothing else worked xD
You could just proxy update to B398 via FF. It's the december security patch but better than nothing
Sent from my OnePlus5 using XDA Labs
Sheldd said:
please tell us how you made to flash it. I tried it with TWRP and i bricked my phone :laugh:
Click to expand...
Click to collapse
Just extracted the .img for UPDATE.APP then converted using simg2img and booted into recovery to use dd to copy to the right partition following the guide here
Rommco05 said:
Hi mate, when I try to use simg2img... What they mean, see attachement. thx
Click to expand...
Click to collapse
Code:
simg2img source.img destination.img
P.S. Please proceed with caution otherwise you may end up bricking.
Del
Lukke2804 said:
How did you brick your phone? I bricked my phone too when trying to flash B140 I was able to recover it only with DU Phoenix, nothing else worked xD
Click to expand...
Click to collapse
I tried to flash the update.zip in TWRP and i got error 7, then my phone bootloped, even with factory reset didnt worked. So i made wiped even the system partition, i flashed the recovery.img by ADB and after i flashed the service rom. I made the B131 rollback and updated back to B399. headache......
Sheldd said:
please tell us how you made to flash it. I tried it with TWRP and i bricked my phone :laugh:
Click to expand...
Click to collapse
The safest method is to use my Flashing Unapproved Firmwares guide. With it, you not only update the partitions but also the data partition.
hackslash said:
The safest method is to use my Flashing Unapproved Firmwares guide. With it, you not only update the partitions but also the data partition.
Click to expand...
Click to collapse
Can you post a link to your guide please?
Hey guys, some italian sites report that's EMUI 5.1 instead 5.0.1. Is that correct? I can't tell anything about because i haven't received the update yet
Okay... I've been searching all over the net for this problem and I keep getting posts that skirt the issue. At least, that's what it seems. So I will begin and you can decide... and thanks for whatever info you can throw my way.
Brand new OnePlus 8T. I want to root it. Duh. So, Got the Tiny ADB and Fastboot package and all the rest, but the issue is with unlocking the bootloader. Other problems may appear later, but this is the issue now.
So, connect phone to PC (Windows 8.1) and the only way that ABD recognizes my phone is when the USB prefs are set to 'No Data Transfer". Yes, I have installed the proper drivers from the phone. So, when the 'No Data Transfer' is selected, ADB recognizes the phone and will issue the command, ABD Reboot Bootloader and the phone reboots to the bootloader. Nice! Unfortunately, it appears that once the phone has booted to the bootloader, it has changed the USB Prefs and now ADB and fastboot do not see the phone. Obviously this sucks. And here is the problem. As far as I know, I have ticked off on all the proper settings. USB Debugging, etc. No joy!
I found a post elsewhere that showed how to set the default USB mode and that didn't work either. My experience has been that ADB used to see the phone under the 'File Transfer' and PTP options before, but it doesn't now. I can't explain this.
So, pretty frustrated. This shouldn't be so bloody difficult. It's only a couple of commands and I have done this with other phones in the past so it's not like I have no previous experience. But I have already wasted way too much time here this go around. Anyone have an answer? I'll be your best friend!!
Thanks all..
R
Try nother USB C cable. Some not able to handle data.
rogerebert said:
Try nother USB C cable. Some not able to handle data.
Click to expand...
Click to collapse
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Ran Doid said:
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Click to expand...
Click to collapse
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
BillGoss said:
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
Click to expand...
Click to collapse
Hey Thanks, Bill. I"ll give this a whirl and see how it goes. I'll report back after. Cheers!
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Ran Doid said:
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Click to expand...
Click to collapse
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
BillGoss said:
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
Click to expand...
Click to collapse
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Ran Doid said:
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Click to expand...
Click to collapse
Sorry, I've no idea about that. Try flashing TWRP again.
BillGoss said:
Sorry, I've no idea about that. Try flashing TWRP again.
Click to expand...
Click to collapse
Okay, well.. I'll have to figure it out then. Thanks much, Bill. Appreciate your help. Happy Holidays!
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
BillGoss said:
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
Click to expand...
Click to collapse
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Mickade said:
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Click to expand...
Click to collapse
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
BillGoss said:
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
Click to expand...
Click to collapse
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Thx,
Mickade said:
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Click to expand...
Click to collapse
If they could fix the interminable start up time for TWRP that would be brilliant. But I believe the problem is with a file system check rather than the actual decryption which is quite fast.
Sorry, croquettes and mash aren't in my menu. But empanadas - absolutely!
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Ran Doid said:
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Click to expand...
Click to collapse
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
BillGoss said:
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
Click to expand...
Click to collapse
There-in why I asked if you might point me at something reliable. But I guess not...
Thanks anyway..
Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
Actually a trick you can use is in twrp if you have the magisk APK change the ext to zip and install in twrp it patches the boot img for you in right slot so you don't have to pull img from phone