hello evryone ,
i am here for having some help on my brickd huawei , when i turn it on it stuck on the boot screen and the led turn on to red red blue red something like that , i can enter the the recovory mode [ it cwm recobory ] i tierd to install update.zip with install zip function ( the propre update file that the phone downloaded ) but i get a error ( status 7) file_getprop faild to start . .
i realy need helo guys ; ' ( it my 2thrd huawei phone that get briked , the reason why my phone is briked i tierd to install a rom that i downloaded from the huawei website for the phone , and it was compatible the info of the update was chc-04 g play mini android 5
anyway guys thxs for reading my problem hope someone can help me !
sorry for bad english !
download stock firmware and flash it via force upgrade by pressing 3 button..
ALHYUMA said:
hello evryone ,
i am here for having some help on my brickd huawei , when i turn it on it stuck on the boot screen and the led turn on to red red blue red something like that , i can enter the the recovory mode [ it cwm recobory ] i tierd to install update.zip with install zip function ( the propre update file that the phone downloaded ) but i get a error ( status 7) file_getprop faild to start . .
i realy need helo guys ; ' ( it my 2thrd huawei phone that get briked , the reason why my phone is briked i tierd to install a rom that i downloaded from the huawei website for the phone , and it was compatible the info of the update was chc-04 g play mini android 5
anyway guys thxs for reading my problem hope someone can help me !
sorry for bad english !
Click to expand...
Click to collapse
Fixed your device?
ALHYUMA said:
hello evryone ,
i am here for having some help on my brickd huawei , when i turn it on it stuck on the boot screen and the led turn on to red red blue red something like that , i can enter the the recovory mode [ it cwm recobory ] i tierd to install update.zip with install zip function ( the propre update file that the phone downloaded ) but i get a error ( status 7) file_getprop faild to start . .
i realy need helo guys ; ' ( it my 2thrd huawei phone that get briked , the reason why my phone is briked i tierd to install a rom that i downloaded from the huawei website for the phone , and it was compatible the info of the update was chc-04 g play mini android 5
anyway guys thxs for reading my problem hope someone can help me !
sorry for bad english !
Click to expand...
Click to collapse
Have you solved your issues?
If not provide me the following info
what emui version were you before
which recovery you installed
what emui version u downloaded
Related
Hi ! I have an Acer P300 Windows Mobile based device . I have tried to install Android on it ( i was able to install the rom from a device named GeeksPhone ONE which has the same hardware specs. ) , after the installation the screen was on , but all black . After that I've reinstalled my original FW . All went good , only that my phone wasn't reading my SIM CARD and no WI-FI connections ( although I was able to connect with the wifi at a point ).
After a Soft-Reset ( shutdown and startup ) the phone shows the Acer logo with the FW version , and after that the same black screen as with Android .
It might Android damaged my hardware ???
Now my device won't turn on at all .... No vibration on power button , no bootloader , nothing . Please Someone can help me ?? At least some notes ... One reply from you won't hurt !
P.S. Still waiting for some answer !
Now my device won't start at all ... Is completely DEAD !!! ...
If someone will want to answer , I need some help with the battery , I believe that is not charging anymore ! ...
Anybody with the same problem around here ?
lol have your same problem mate xD tell me if u managed to fix this pls
Just now i rooted my device and still running fine . Then i flash cwm that was intended for other firmware , just trying my luck . Then i try to boot from it , the recovery showing double sided screen and its blinking . Then i realized its not compatible . When i try to boot back my device , it turned off by itself after the sony and battery logo . First sony logo , then battery logo , Then it turned off :crying: :crying: .
Still a newbie . Urgent helpp pleasee . Please dont say its too late :crying: :crying:
umarnisme said:
Just now i rooted my device and still running fine . Then i flash cwm that was intended for other firmware , just trying my luck . Then i try to boot from it , the recovery showing double sided screen and its blinking . Then i realized its not compatible . When i try to boot back my device , it turned off by itself after the sony and battery logo . First sony logo , then battery logo , Then it turned off :crying: :crying: .
Still a newbie . Urgent helpp pleasee . Please dont say its too late :crying: :crying:
Click to expand...
Click to collapse
Uhm, try flashing the stock ftf file using flashtool.:cyclops:
umarnisme said:
Just now i rooted my device and still running fine . Then i flash cwm that was intended for other firmware , just trying my luck . Then i try to boot from it , the recovery showing double sided screen and its blinking . Then i realized its not compatible . When i try to boot back my device , it turned off by itself after the sony and battery logo . First sony logo , then battery logo , Then it turned off :crying: :crying: .
Still a newbie . Urgent helpp pleasee . Please dont say its too late :crying: :crying:
Click to expand...
Click to collapse
As far as i know, your partitions will be all messed up.
I guess all recoveries have recovery.fstab. All mountpoints should exist in this file and it is crucial this information be correct or else very bad things can happen, such as a recovery flash writing to the wrong location.
I don't think you will have any success with it, but still try flashing the ftf file
Hello , this is my first post here , so sorry if i missed a detail or something
So as in the title , My friend's ZOPO C2 (B version) is bricked :
this is what happened , I rooted the phone for him , used Mobile Uncle Tools to run a custom recovery (TWRP) and downloaded this custom ROM MIUI7 (u can find it on Needrom.com
Everything went well at first , until I started getting these errors :
1) warning: no file_context
2) symlink: some symlinks failed
the option after was Reboot , i did so and (Great ! -_-) a bootloop , the phone is stuck on the ZOPO logo (the one u see at boot) and I can't access the recovery (Tried Volume Up + Power Button and Volume Down + Power button .... nothing)
Please help me , some tutorial online , say .. use SP flash tool , and I found some "Scatter files or something " to use with , but I can get it to work .
Is there any solution ?
Stormix_thedev said:
Hello , this is my first post here , so sorry if i missed a detail or something
So as in the title , My friend's ZOPO C2 (B version) is bricked :
this is what happened , I rooted the phone for him , used Mobile Uncle Tools to run a custom recovery (TWRP) and downloaded this custom ROM MIUI7 (u can find it on Needrom.com
Everything went well at first , until I started getting these errors :
1) warning: no file_context
2) symlink: some symlinks failed
the option after was Reboot , i did so and (Great ! -_-) a bootloop , the phone is stuck on the ZOPO logo (the one u see at boot) and I can't access the recovery (Tried Volume Up + Power Button and Volume Down + Power button .... nothing)
Please help me , some tutorial online , say .. use SP flash tool , and I found some "Scatter files or something " to use with , but I can get it to work .
Is there any solution ?
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. There aren't any specific forums for your device on XDA. However, you may ask your questions here:
Android Q&A, Help & Troubleshooting
You will find expert help there. Good luck!
Hello everyone, this my first post/question here so sorry if it's in the wrong place.
Shortly about 20 days ago I got a new Huawei y6 smartphone (which doesn't has warranty), it had some problems so I decided to just reflash the official ROM which I hardly found online, and since the phone is MT6582 (MTK based) I used the SP flasher (as I did in an Infinix one before and everything went fine !!), I turned off the phone, uploaded the scatter file, pressed download then connected the phone, and every thing went fine and I had a message "Done". just after that the phone won't turn on at all !
nor even a bootloop nothing just a black screen with the small nearly invisible red LED of the sensor as I think flashing.
And trying to reflash the ROM tells me that Error 4032,dram failed !!
Please help me I don't know what to do now and this really put me in a big problem now ! :crying:
Is it a bad ROM or because I (accidentally) marked the preloader to be downloaded with the file or what !?
Some tutorials say that it needs a preloader_fix.bin file which I can't find for that phone ... please help any suggestion will be acceptable. Thanks
Note : Before I did this I took a backup of the phone info :-
*BB Chip : MT6582
*MS Board : hwSCL-U31
*SW : ALPS.KK1.MP1.V2.11
*Custom build : 1467958675
*SW Version : C900B130
The ROM I downloaded : mega.nz/#!RU11EJ5b!4fjxZl9_G9uixtmHyfYnWrh_97gr3ozExFKuq3atGAs
dear
did you find a solution ??
i guess you can still access bootloader ?
try to flash the img through it
I had the same problrm but ( solved ) succesfully.
Hello MMavrick23
I had the same problem before ( error 4032 ). I solved it many times by using ( bin format flash file ) extracted from living device using ( Miracle Box ). Try to find the ( bin ) file or just look for living device and extract the rom in ( bin ) format and flash it to your dead device using ( Miracle Box ) . This's the best solution for ( error 4032 ) ever .
Regards
hii everyone
after a battery drain my lg velvet is stuck in a bootloop , i tried to flash many roms android 10 , 11 and 12 ,after the flash done the phone keep restarting showing this message " erasing......" , i was thinking that is a rom region probleme , after cheking the imei with lgromup it says is a ROY region so i download it , after flashing it is the same probleme constantly rebooting with erasing message .
anyone can help ! thank you