Bricked Huawei CAM L21 or Y6II - General Questions and Answers

So I had just recently rooted my phone using this tutorial rooting-huawei-y6-ii-cam-l21-t3501162 in xda forums.
It was working fine until I did the following: There was a recent update popping up all the time for which I tried many times updating through the Software Update but every time it failed (Don't know what may be the issue, thought this might be due to the root). Then I had this crazy idea to update it forcibly using HiSuite in my PC. Well, it updated successfully but BRICKED my phone (Blank Screen after Boot). Too bad that I didn't backup my phone using TWRP.
And now I cannot restore it to any working state.
I have tried firmware updates using the following Stock ROMs but it fails every time, sometimes it goes to 50% and fails,
C185B141
C464B151
C432B179
Please help if anyone knows how to fix this, I need to restore my phone to any working state.

I've got this problem too
Is your Y6II for Asia?
I've got this problem today and I found this topic before I managed to fix it.
So now, after I solved this problem, I will tell you what I did; Hope that helps.
I downloaded the rom with this code: CAM-L21C10B141 from hwmt.ru
At first, when I tried to update the phone with default software updater. I got same problem as you: It stopped at about 50% with this line : 'failed to check the update package please download the package again'
So I was about to give up and then I tried to open the phone with TWRP, I copied the zip file of the rom and flashed it to the phone using 'install zip' from TWRP.
After that, when the phone reboot, it showed the Huawei logo (A big change for me, since the last time, it stucked at the black screen with the line 'The phone is booting now'.)
So I tried Volume up and Power button. It show EMUI recovery, it will let you choose to reset to factory. I did it and reboot.
Magically, the phone backed to normal state

:good:

Hi all.Need help in changing locations.
If the owners of Huawei CAM-L21 have the opportunity to share oeminfo from this unit - please help. Interested in hw/eu & hw/spcseas and others. I have in the presence of a hw/ru & cmccelectric/cn. This file helps you flash any firmware of any region. I would be grateful)

مرحبا انا اريد ادخال #الرووت . بكن انا خائف من ان يحصل شيئ للهاتف .هل ستمحى بياناتي الشخصية . و ما اضراره

jiaulhaq said:
So I had just recently rooted my phone using this tutorial rooting-huawei-y6-ii-cam-l21-t3501162 in xda forums.
It was working fine until I did the following: There was a recent update popping up all the time for which I tried many times updating through the Software Update but every time it failed (Don't know what may be the issue, thought this might be due to the root). Then I had this crazy idea to update it forcibly using HiSuite in my PC. Well, it updated successfully but BRICKED my phone (Blank Screen after Boot). Too bad that I didn't backup my phone using TWRP.
And now I cannot restore it to any working state.
I have tried firmware updates using the following Stock ROMs but it fails every time, sometimes it goes to 50% and fails,
C185B141
C464B151
C432B179
Please help if anyone knows how to fix this, I need to restore my phone to any working state.
Click to expand...
Click to collapse
can you help me ? i cannot root cause need bootloader and the huawei website they dont have no more to unlock bootloader please give the idea how to do in may 2018 because i saw ppl old time they can root now not work

Related

Bricked after update to MM

Hi,
I did something stupid - I wanted to update my phone by creating a dload folder on internal memory and updating to EMUI 4.0 beta that's floating around on the internet (I got it from carbontesla). I knew it required a B326 version, I had B324 and still went through with it, because I mistakenly thought that B326 is only required for L10 (I have L09). Now the phone is stuck in bootloop.
I have tried the following:
1. Forced update - it was apparently successful, but still the phone kept resetting
2. I reset to factory settings and wiped cache - still keeps resetting
3. I tried to force update again, this time I get an 'update failed' info and asks me to reboot. Still the same.
4. Tried to reset to factory settings and wipe cache again - still no luck.
I can't even turn the phone off, so for now I keep it in recovery mode.
Any idea what can I do? Am I screwed for good?
I searched around on XDA and other forums but couldn't find anything - if anyone can help me, I will be very grateful. I just bought this phone 3 months ago and I can't afford a new one at the moment.
Khasim83 said:
Hi,
I did something stupid - I wanted to update my phone by creating a dload folder on internal memory and updating to EMUI 4.0 beta that's floating around on the internet (I got it from carbontesla). I knew it required a B326 version, I had B324 and still went through with it, because I mistakenly thought that B326 is only required for L10 (I have L09). Now the phone is stuck in bootloop.
I have tried the following:
1. Forced update - it was apparently successful, but still the phone kept resetting
2. I reset to factory settings and wiped cache - still keeps resetting
3. I tried to force update again, this time I get an 'update failed' info and asks me to reboot. Still the same.
4. Tried to reset to factory settings and wipe cache again - still no luck.
I can't even turn the phone off, so for now I keep it in recovery mode.
Any idea what can I do? Am I screwed for good?
I searched around on XDA and other forums but couldn't find anything - if anyone can help me, I will be very grateful. I just bought this phone 3 months ago and I can't afford a new one at the moment.
Click to expand...
Click to collapse
Experienced all. Tsk. Should have stayed away from the Marshmallow upgrade thread.
Khasim83 said:
Hi,
I did something stupid - I wanted to update my phone by creating a dload folder on internal memory and updating to EMUI 4.0 beta that's floating around on the internet (I got it from carbontesla). I knew it required a B326 version, I had B324 and still went through with it, because I mistakenly thought that B326 is only required for L10 (I have L09). Now the phone is stuck in bootloop.
I have tried the following:
1. Forced update - it was apparently successful, but still the phone kept resetting
2. I reset to factory settings and wiped cache - still keeps resetting
3. I tried to force update again, this time I get an 'update failed' info and asks me to reboot. Still the same.
4. Tried to reset to factory settings and wipe cache again - still no luck.
I can't even turn the phone off, so for now I keep it in recovery mode.
Any idea what can I do? Am I screwed for good?
I searched around on XDA and other forums but couldn't find anything - if anyone can help me, I will be very grateful. I just bought this phone 3 months ago and I can't afford a new one at the moment.
Click to expand...
Click to collapse
Uh-oh... Another Mate 7 phone bricked by the Marshmallow beta B511 update...
I guess you'll just have to wait for the full official marshmallow update (no longer beta) for your TL09 phone for your region, or at least, wait for the official TL09 marshmallow to lollipop downgrade package for your region. When Huawei releases one or both, then you can install one or both via forced update (power + volume up + volume down) and have a functioning phone again.
For now, there's nothing you can do but wait and wait... unless you know your way around rooting, unlocking bootloaders and custom ROMs. There are actually quite a lot of Mate 7 owners in the similar situation as you. If only you can BAND together with a common cause/objective, your 'bricked by Marshmallow B511' group could somehow be a FORCE to reckon with that Huawei cannot ignore. Your group can petition Huawei with emails to release at least the 'marshmallow to lollipop downgrade package' for other non-China regions NOW, or the EARLIEST humanly possible...
You may want to read other users similar experiences with their bricked mate 7 phone (by installing the beta marshmallow b511 update) here: http://forum.xda-developers.com/mat...-marshmallow-b511-t3304178/page2#post65176950
It will make you feel much better knowing you are not alone. Alternately, you can just vent out your frustrations to Huawei in another thread. Not sure if its allowed in XDA though.
Those with bricked mate 7 phones:
Can you try and see if this suggestion works?
=========== (quoted from http://www.carbontesla.com/2016/01/download-ascend-mate-7-b511-marshmallow-ota-zip/) by wissam marrash
wissam marrash • a day ago
Guys I have mt7-l09 and its working with marshmallow, yes it drains more battery and some lagging in some areas but this should happen because its a beta and incremental release. For people who got spoil their phone while installing, you should read the requirements very well before downloading this rom. Its clearly mentioned for B326 and for un-rooted phones. so before you install you should install the B326 (you can download using this link: http://m.huawei.com/pkmobile/c... make sure to choose mt7-l09 or mt7-l10 and after installing the B326 install marshmallow beta.
For people who wants to downgrade, yes you can but you have to choose a full release like the B326-B327-B328.
N.B. ONLY Marshmallow BETA rom, Don't unzip the after downloading, its not like the other updates. You should copy the zipped file as is to inside "dload" folder.
Just a tip, some releases are not supporting 4G lte especially when it marked Europe.
For people who keep rebooting, try to connect you phone to pc or take out the memory card and use card reader and access your files and then delete the files from the "dload" folder and then download using your pc any full release rom (b326 or b327 or b328) and extract it and then copy the "UPDATE" file to the dload folder and then turn off the phone and then boot your phone while holding Vol up + Vol down + Power buttons at same time to automatically trigger the update installation and should go smooth.
Hope my comments will help
==============
Here are the links to full ROMs:
TL10: B326 full ROM:
http://consumer.huawei.com/pk/support/downloads/detail/index.htm?id=62450&key4=MATE7
L09: B326 full ROM:
http://consumer.huawei.com/pk/support/downloads/detail/index.htm?id=62371&key4=MATE7
reboot
Hi Don
We tried to follow Wassim's nstructions unfortunately it didn't work. As you said there are so many mate 7 users' faced this problem.
Any way thanks a lot for your attention.
maksudbek said:
Hi Don
We tried to follow Wassim's nstructions unfortunately it didn't work. As you said there are so many mate 7 users' faced this problem.
Any way thanks a lot for your attention.
Click to expand...
Click to collapse
i had that problem when tray to update it to MM tray it all the way no LUUUUUUUUCK
last i went to the Huawei Services the joke is they also can noooooooooooot do anything ??
last they decide it to change the main board of the phone then .. phone start with KK after that no problem
but i will never ever buy this brand again !!!!!!

HELP: Need Europe HTC__034 Nougat Backup (FW: 2.17.401.2)

Hello out there!
Upon trying to install HTC music widget I got really f**ked. Random force closes, so I restarted the phone in hope it would be OK, but guess what ... bootloop.
I guess that widget wrote something to the system partition... Nevertheless, tried to reflash the OTA FW + SW with the same issuing number: no success (Error 9)
Decided to unlock bootloader & flash respectively something else ... yet no success. Only thing that I could flash properly is Vanyr Rom, but it's stuck onto a page
saying Decription unsuccessfull. Tried formatting & so on & so forth, with yet no trace of success whatsoever.
If somebody has a TWRP nandroid backup for that FW and is willing to share it, I would be more than thankful (can at least arrange a beer/wine treat ). I have the brick for 2 days only, so it's pretty sad it died so fast and not even because of being rooted ot tampered anyhow, but just a stupid widget...
... Thank you all in advance!

Need help with my S6!

Hello there,
Please forgive me if i posted this thread on the wrong place.
-I would've not posted a thread here unless this got serious, so i own a Samsung Galaxy S6, it's 1 year old phone, when i first got it, i used it normally like everyone else and had no problem with it, but my curiosity got me to root the phone, i still did not get any problem with it until i chose to add a ROM. I used NNE 5.1 S8 port and it was working well until it got my phone broken somehow.
-My phone started acting really strange after 2 months of activity of that new ROM, my phone just started restarting randomly and it got me worried, i thought it's an application problem so i first just factory reset it. It seemed it was not the problem on an application, so i chose to change my firmware to a stock one. I searched up recently on the newest firmware for S6 and i found out it's: XEF (France) , PDA (AP): G920FXXU6ERC1 and CSC : G920FOXA6ERC1 on 2018-03-22. I Downloaded 4 files: BL,AP,CP,CSC , and i found out about PIT on one of the posts in this forum (Filename: SM-G920F-ZEROFLTE_EUR_OPEN.pit).
-Before i flashed with Odin, i wiped System, Data, Cache and Dalvrik Cache. The firmware worked well but after 1 hour it started doing the same thing but now differently. It happend to me only 1 time that it froze up on an application, but i think that is just an app problem. The main problem is that when i lock my screen, i cannot unlock it anymore, it just freezes there until it restarts after a short period of time. After the restart, it just keeps going, restarts, asks for pin, restarts and so on.
I tried removing the sim card and putting it back in, did not work.
I tried Safe mode, still same.
Model of phone: SM-G920F
Current firmware: XEF (G920FXXU6ERC1)
Android version: Nougat (7.0)
If you can help me, or you know something about this problem, please repost here, i would be really grateful since this is my only phone
Ininstall twrp backup everything most important efs partition.
Install samsung switch and pray that it asks you to do an update. If not try to flash a diferent version of nougat for example November security patch and try again with samsung switch
lenovot said:
Ininstall twrp backup everything most important efs partition.
Install samsung switch and pray that it asks you to do an update. If not try to flash a diferent version of nougat for example November security patch and try again with samsung switch
Click to expand...
Click to collapse
How could samsung switch possibly help?
I did flash it with different versions already, but no luck :/.
I've been praying a lot for this lately but it is not working lol
Please Bump this!
try doing this.
1) go here: https://updato.com/
2) choose download 2 roms. 1 nougat and another marshmallow (to my knowledge, stock roms are one file. no more splits and unless otherwise stated... no need for pit)
3) first flash nougat using oden
4) try the phone for a few some time.
if after a set amount of time, phone works fancy and no issues present then it's solved.
if not... install marshmallow. then try again.
if all this fails then...
install nougat. as soon as possible afterwards install twrp.
boot into twrp and just leave it there. my twrp locks after a while and screen goes dark until user interaction (just like it's supposed to)
if the same thing happens then its a hardware issue... probably... (i have had my main board fail... kinda similar not similar issue... hope you dont have the same issue and that its just software related)
good luck.
In my case every time there was an update available it would download the whole firmware and by doing so you would get the most fresh and updated version. Also it updates every partition to match

Bootloop after installing Xposed on Oreo, Bit of help would be appreciated.

After searching around and not being 100% sure on how I should go about fixing this particular bootloop I decided to post a thread. Bootloader unlocked, phone unlocked, FRP unlocked, and TWRP installed. Can't seem to get the phone recognized when plugged in no matter where I'm at and hisuite recovery doesn't work, nor does the erecovery or whatever it's called. I had the phone running just fine with supersu but after installing my usual Xposed/Busybox and rebooting I got caught in a bootloop. (might have been caused by being on Oreo and having some problems with a version made for Nougat or something). I've seen there are various ways to exit the loop and at this point I'd be open to any but I do notice some posts saying they almost bricked their phone while doing so. Currently on my microSD I've got a hwota update I was going to try to use. I've got no backups in TWRP either because I'm irresponsible (my fault). What can I do to just wipe the phone, reinstall any version of android and get back to where I was at. I'm a little new to this as I've only ever rooted my tablet. Thanks for the help and all the info I've taken from this forum before and hopefully now. Forgot to mention I don't know my full device number only MHA-L29 in the US.
Ok Well after laying in bed and thinking about it I wound up running HWOTA8 from TWRP since I could access that. Seemed to just bring me back to eRecovery, and I factory reset my phone. I'll reinstall TWRP and flash supersu then make a backup and try again. Not sure what happened but I seemed to be in a pretty good spot since I could access TWRP even though my phone wouldn't show up on my computer while in fastboot/Recovery mode.
edit: oh I got a new problem now. I'm on testkeys firmware, camera, sim, and bluetooth work but I can't update from 7 back to 8. I'll do more testing around before bothering to unlock bootloader or install TWRP.
I've been trying to follow the guide in this thread but to no avail. I just get software install failed and then I have to start again.
Well another day of searching google and XDA trying to figure out guides and I don't think I'm any closer to a solution to getting off test-keys. Some seem to suggest that you need to go back to MM, some suggest running HWOTA, some suggest the three button recovery and others say that won't work at all. I'm not sure I've ever felt this confused haha. I'll keep at it but there has to be some way to get to a build that has the updater on it since that's all I seem to be lacking to get off test-keys. I can even search the settings for the updater but when you press it nothing happens. It's like they completely removed any sort of updating this build can do.
KittyCat5eUTP said:
Well another day of searching google and XDA trying to figure out guides and I don't think I'm any closer to a solution to getting off test-keys. Some seem to suggest that you need to go back to MM, some suggest running HWOTA, some suggest the three button recovery and others say that won't work at all. I'm not sure I've ever felt this confused haha. I'll keep at it but there has to be some way to get to a build that has the updater on it since that's all I seem to be lacking to get off test-keys. I can even search the settings for the updater but when you press it nothing happens. It's like they completely removed any sort of updating this build can do.
Click to expand...
Click to collapse
What is your full build number? Please, post screenshot.
5[Strogino] said:
What is your full build number? Please, post screenshot.
Click to expand...
Click to collapse
Model: MHA-L29
Build: NRD90M test-keys
EMUI version: 5.0.1
Android version: 7.0
I believe I was originally on some variant of MHA-L29C567 since I'm US based and its the dual sim version
I've tried using HWOTA a few times to either upgrade/update or rebrand and no matter what I choose when my phone restarts to install I just get software install failed. Usually I'll have to run through first time setup again. I've read that some people said this particular issue had to do with the update zips but mine seem to be named correctly so all I can think of doing is getting another firmware and trying again with that.
haha okay so I found out I was putting the update zips in the wrong folder. I fixed that and re ran HWOTA. update started/finished and my phone started booting and restarting a lot then went into erecovery. I'm downloading the update package right now and it's slow as hell but it's moving. And that failed leaving me to boot a few times and then get back to erecovery. I'll try getting into fastboot or recovery.
Edit: Well that seems to have resolved itself now. After having the erecovery fail I wiped/factory reset and booted the phone into oreo 8.0.0.321 with all the apps and updater. Thanks to everyone who dropped in and I'll be getting emails if someone replies that needs help too. I'm not very knowledgeable but I can give it a shot.

Downgrade from Nougat 7 to Oreo 8 G955FD

First thing i searched everywhere and find out am the only one with this problem....
The problem start after Oreo update first with random restarts and finally freezing screen.
i am now on Oreo update U4 september and the phone is very unstable with rabdom restarts and freezing on a black screen THAT EVEN DONT RESPOND TO FORCE RESTART !!!
So i need to wate till the phone loss all is battery then charging it, power it on to be able to flash official rom again and agian everytime this happen.
the phone can hold sometimes for 400-600 hours after flashing the offical rom and the the problem occure again
i start to believe theres something wrong with Oreo on this phone..So the last thing to do to make sure there is nothing wrong with Hardware i need to Downgrade to Nougat 7 but when i do that using Oden (flashing AP and BL) it show me error ..So i hope someone can help me with another method to downgrade to Nougate or even figure out whats the main problem that cause all this...
sorry for my bad english hope you can help
heider.raheem said:
First thing i searched everywhere and find out am the only one with this problem....
The problem start after Oreo update first with random restarts and finally freezing screen.
i am now on Oreo update U4 september and the phone is very unstable with rabdom restarts and freezing on a black screen THAT EVEN DONT RESPOND TO FORCE RESTART !!!
So i need to wate till the phone loss all is battery then charging it, power it on to be able to flash official rom again and agian everytime this happen.
the phone can hold sometimes for 400-600 hours after flashing the offical rom and the the problem occure again
i start to believe theres something wrong with Oreo on this phone..So the last thing to do to make sure there is nothing wrong with Hardware i need to Downgrade to Nougat 7 but when i do that using Oden (flashing AP and BL) it show me error ..So i hope someone can help me with another method to downgrade to Nougate or even figure out whats the main problem that cause all this...
sorry for my bad english hope you can help
Click to expand...
Click to collapse
Since your on bootloader version 4 (u4) you won't be able to downgrade to nougat which is why you are getting errors in Odin. When flashing firmware do you use CSC or home CSC.
Not sure if it's hardware related or not but if you are getting up to 400 - 600 hrs out of it I would say it:s software related. There are some apps on playstore for hardware test to try if you like. One issue I have had is the processor running to hot and causes me some issues to the point you can't do anything until it cools down.
spawnlives said:
Since your on bootloader version 4 (u4) you won't be able to downgrade to nougat which is why you are getting errors in Odin. When flashing firmware do you use CSC or home CSC.
Not sure if it's hardware related or not but if you are getting up to 400 - 600 hrs out of it I would say it:s software related. There are some apps on playstore for hardware test to try if you like. One issue I have had is the processor running to hot and causes me some issues to the point you can't do anything until it cools down.
Click to expand...
Click to collapse
i use Home CSC ... and i am sure its not the heat that cause the freezing its happen even when device cool.... This weird behavior doesnt have a constant form... most of the time the freezing happen during the first few minuts during setup device ...FORGET TO MENTION ....in TWRP recovery the device is feeling very well and run smooth without any issue at all... is there something to do now in your openion can solve this?
and if not... what samsung can do for the device to bring it life again?... thanks for your replays
heider.raheem said:
i use Home CSC ... and i am sure its not the heat that cause the freezing its happen even when device cool.... This weird behavior doesnt have a constant form... most of the time the freezing happen during the first few minuts during setup device ...FORGET TO MENTION ....in TWRP recovery the device is feeling very well and run smooth without any issue at all... is there something to do now in your openion can solve this?
and if not... what samsung can do for the device to bring it life again?... thanks for your replays
Click to expand...
Click to collapse
I would think if it is hardware related than the issues would also happen in recovery and/or download mode. I have heard of other people having issues when flashing firmware with home CSC.
Some things I would personally try are:
1. You could try smart switch and check for latest firmware or recovery option.
2. Run in safe mode see if that makes a difference
3. In recovery wipe cache/dalvik and reboot
4. In recovery factory reset
5. Flash firmware again with CSC not home CSC.
Problems with options 1,4,5 is you will need to backup your apps and data etc. Option 5 you will have to reinstall twrp.
These options aren't in any order so I would start with 3 first see how it goes then 2 see how it goes then ,1,4 and 5 and see how it goes for each step.
Let me know how it goes
spawnlives said:
I would think if it is hardware related than the issues would also happen in recovery and/or download mode. I have heard of other people having issues when flashing firmware with home CSC.
Some things I would personally try are:
1. You could try smart switch and check for latest firmware or recovery option.
2. Run in safe mode see if that makes a difference
3. In recovery wipe cache/dalvik and reboot
4. In recovery factory reset
5. Flash firmware again with CSC not home CSC.
Problems with options 1,4,5 is you will need to backup your apps and data etc. Option 5 you will have to reinstall twrp.
These options aren't in any order so I would start with 3 first see how it goes then 2 see how it goes then ,1,4 and 5 and see how it goes for each step.
Let me know how it goes
Click to expand...
Click to collapse
Actually steps 1,3,4,5 all have been tried before without making difference but i never tried to run in safe mode (step 2)... i should tried it.... but now i cant cause one of the freezing form and the most occuring one is when blue screen with android logo at the center that appear befor the samsung logo (trying to erasing data befor the first boot after flashing a new rom)...so i have to download a nother oreo firmware from sammobile to make it run ...sorry if i make it complicated for you but this is how my device acting very weird....
Do you think its somthing wrong with Oreo in this s8+ that can be solved when downgraded to Nougat or Upgaraded to Pie maybe?
heider.raheem said:
Actually steps 1,3,4,5 all have been tried before without making difference but i never tried to run in safe mode (step 2)... i should tried it.... but now i cant cause one of the freezing form and the most occuring one is when blue screen with android logo at the center that appear befor the samsung logo (trying to erasing data befor the first boot after flashing a new rom)...so i have to download a nother oreo firmware from sammobile to make it run ...sorry if i make it complicated for you but this is how my device acting very weird....
Do you think its somthing wrong with Oreo in this s8+ that can be solved when downgraded to Nougat or Upgaraded to Pie maybe?
Click to expand...
Click to collapse
Just curious what firmware version are you using.
spawnlives said:
Just curious what firmware version are you using.
Click to expand...
Click to collapse
i use now Oreo G955FXXU4CRI5
heider.raheem said:
i use now Oreo G955FXXU4CRI5
Click to expand...
Click to collapse
Is it working ok or still same problem
spawnlives said:
Is it working ok or still same problem
Click to expand...
Click to collapse
its froze right now it cant even get to samsung logo...and even if i flash the ROM again and get it work it will freez after maximum 600 hours (thats happened 3 times)

Categories

Resources