Related
Hello, I have an Xperia Play and since i had it i never flashed it , The only thing i did was rooting by using gingerbreak.
And i was trying to flash the new update http://forum.xda-developers.com/showthread.php?t=1097591
And when i use flashtool to flash it an Error massage appear :
13/013/2011 05:13:49 - ERROR - Error flashing. Aborted
13/013/2011 05:13:49 - INFO - Now unplug the device and power it on
13/013/2011 05:13:49 - INFO - Then go to application settings
13/013/2011 05:13:49 - INFO - turn on Unknown Sources and Debugging
And the problem is i cant boot the phone!!
I tried a different FTF file from here: http://forum.xda-developers.com/showthread.php?t=1048422
And i also tried this http://forum.xda-developers.com/showthread.php?t=1130639
But still nothing new..
So please help me my Phone can't boot.
ddsds said:
Hello, I have an Xperia Play and since i had it i never flashed it , The only thing i did was rooting by using gingerbreak.
And i was trying to flash the new update http://forum.xda-developers.com/showthread.php?t=1097591
And when i use flashtool to flash it an Error massage appear :
13/013/2011 05:13:49 - ERROR - Error flashing. Aborted
13/013/2011 05:13:49 - INFO - Now unplug the device and power it on
13/013/2011 05:13:49 - INFO - Then go to application settings
13/013/2011 05:13:49 - INFO - turn on Unknown Sources and Debugging
And the problem is i cant boot the phone!!
I tried a different FTF file from here: http://forum.xda-developers.com/showthread.php?t=1048422
And i also tried this http://forum.xda-developers.com/showthread.php?t=1130639
But still nothing new..
So please help me my Phone can't boot.
Click to expand...
Click to collapse
why device are you choosing in flashtool :? just pick the first one, i think its the x10
AndroHero said:
why device are you choosing in flashtool :? just pick the first one, i think its the x10
Click to expand...
Click to collapse
Thanks for helping, But how can i choose a file in Flashtool ?
As i understand i can only choose the FTF file , And i chose the Xperia Play one.
OK, After a lot of searching i found out that i had my phone Bootloader Unlocked before flashing,
And after that i tried to flash it and i got the error and it wont boot.
From what i red i only have 2 things to do :
1- Get the phone booting but without radio.
2- give it to sony and tell them that it just crashed while i was updating it.(And don't tell them anything about to root or the bootloadr)
So please if anyone knows any better way to fix it please tell me.
ddsds said:
OK, After a lot of searching i found out that i had my phone Bootloader Unlocked before flashing,
And after that i tried to flash it and i got the error and it wont boot.
From what i red i only have 2 things to do :
1- Get the phone booting but without radio.
2- give it to sony and tell them that it just crashed while i was updating it.(And don't tell them anything about to root or the bootloadr)
So please if anyone knows any better way to fix it please tell me.
Click to expand...
Click to collapse
You didnt need to unlock you bootloader to use flashtool, but now you have just flash a system.img from fastboot, your phone isnt bricked unless you tried to do an OTA updated with an unlocked bootloader
AndroHero said:
You didnt need to unlock you bootloader to use flashtool, but now you have just flash a system.img from fastboot, your phone isnt bricked unless you tried to do an OTA updated with an unlocked bootloader
Click to expand...
Click to collapse
I searched for the system.img file and i found these files :
1.play_modded.img
2.R800i_3.0.1.A.0.145_UK_system.img
3.recoveryPLAY.img
4.system.sin (I know it's an "SIN" file)
And i tried to use fastboot with them all and i allways get the same result:
"sending 'system' (XXXX KB)..."
I watied for very long time but nothing happend.
So please tell me if i am doing any thing wrong.
ddsds said:
I searched for the system.img file and i found these files :
1.play_modded.img
2.R800i_3.0.1.A.0.145_UK_system.img
3.recoveryPLAY.img
4.system.sin (I know it's an "SIN" file)
And i tried to use fastboot with them all and i allways get the same result:
"sending 'system' (XXXX KB)..."
I watied for very long time but nothing happend.
So please tell me if i am doing any thing wrong.
Click to expand...
Click to collapse
Try formatting /system and /boot first,
In fastboot type in
fastboot erase system
fastboot erase boot
Then flash this kernel with the command "fastboot flash boot boot.img"
http://forum.xda-developers.com/showthread.php?t=1176502
finally flash this system image with command "fastboot flash system xxxxxx.img"
http://forum.xda-developers.com/showthread.php?t=1098736
AndroHero said:
Try formatting /system and /boot first,
In fastboot type in
fastboot erase system
fastboot erase boot
Then flash this kernel with the command "fastboot flash boot boot.img"
http://forum.xda-developers.com/showthread.php?t=1176502
finally flash this system image with command "fastboot flash system xxxxxx.img"
http://forum.xda-developers.com/showthread.php?t=1098736
Click to expand...
Click to collapse
Still the same problem stuck with the :
"sending 'boot'"
And i also tried to flash the system but with the same result.
ddsds said:
Still the same problem stuck with the :
"sending 'boot'"
And i also tried to flash the system but with the same result.
Click to expand...
Click to collapse
And you are sure you have unlocked your bootloader maybe you should ask or PM blagus, he is the expert in these sorts of things
AndroHero said:
And you are sure you have unlocked your bootloader maybe you should ask or PM blagus, he is the expert in these sorts of things
Click to expand...
Click to collapse
Yes i just checked and it's unlocke.
And thank you so much for helping and i will PM him and wait .
Finally i got it to work !
I deleted the system with fastboot , Than i used this tool :http://forum.xda-developers.com/showthread.php?t=1134334 to re-lock the bootloader.
And finally i used the SE PC programme to repair the phone with the latest Update.
Thank you AndroHero very much for helping me.
ddsds said:
Finally i got it to work !
I deleted the system with fastboot , Than i used this tool :http://forum.xda-developers.com/showthread.php?t=1134334 to re-lock the bootloader.
And finally i used the SE PC programme to repair the phone with the latest Update.
Thank you AndroHero very much for helping me.
Click to expand...
Click to collapse
Thats great i'm glad you got it soted
Hi people...
Everything was going so smoothly... bootloader unlock... root... some nice root apps... free paid games... and my p8 lite was just feeling so good... until... I flashed twrp with flashify under the name of boot.img... Am I stupid or what?! Now I can only get 2 scenarios... when i turn on the phone it goes directly to twrp. In twrp i get the option to go the bootloader screen... If I choose system it goes back to twrp... I can't get it to start. I downloaded the official tar.gz from emui site but I dont know how can I install it. PLEASE HELP... What should I do in this case?! I miss my baby...
Thanks in advance
You have to restore stock recovery in fastboot mode.
arviit said:
You have to restore stock recovery in fastboot mode.
Click to expand...
Click to collapse
How do I do that?! If I wanted to wipe my phone completely and re-install the OS would be better to do it using twrp or stock recovery?
Thank you very much
Sorry, i misunderstood. If you flashed twrp as boot.img, reflash stock boot in fastboot mode.
flash stock boot.img in fastboot mode
and then flash twrp as recovery
will be like this
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery TWRP.img
fastboot reboot
use the boot.img from stock rom and twrp image you downloaded
Oh no!
Now I made some serious **** to my baby... guess now i'll have to send it to huawei to fix it. I made a full wipe like if it was format c: in computers... everything is gone (i didnt had any personal data) it doesnt have OS even. But when I still had twrp i tried to flash boot.img and recovery.img and now when i start it goes directly to bootloader screen but saying "please update system again" and where it used to say phone unlocked it now says (in red letters):
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
I was able to get to eRecovery with usb connected but when i choose to download e install the new version it gives me the message "wifi starting failed".
It also does not get any instuction with fastboot. but hi suite starts when I connect it. Strange?!
What do you think? Should I send it to huawei? Or is it possible for me to make it work again?
Also tried UPDATE.APP function and all give me fail message.
I'm going crazy!!!! But I love to mess around with android... To me this is the android essence. Fortunately I have a lumia for when my baby doesnt work.loooool
Thank you all
I don't understand why you don't use fastboot. Everybody told you to use it. In our phone situation, without custom kernel or rom, twrp is for experimentation and you cannot mix things.
arviit said:
I don't understand why you don't use fastboot. Everybody told you to use it. In our phone situation, without custom kernel or rom, twrp is for experimentation and you cannot mix things.
Click to expand...
Click to collapse
Well, you warned me... but sometimes i do these kind of *****... So, in this situation you think it's better to send it or is there way to fix this.
By the way, when I enter huawei eRecovery and I get the option to download the firmware through wifi and it says wifi starting failed, is there any way to make this work? And to fastboot do we need to open cmd as administrator to make it work? Because if Hi suite detects the phone I should also be able to fastboot it right?
Thanks for your patience
Just use fastboot aand flash everything
Recovery
Boot
Systme
Cust
jabonloco said:
flash stock boot.img in fastboot mode
and then flash twrp as recovery
will be like this
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery TWRP.img
fastboot reboot
use the boot.img from stock rom and twrp image you downloaded
Click to expand...
Click to collapse
hello I have p8 lite unlocked and rooted, yesterday I wanted to install the TWRP 2.8.7. but I was wrong and I installed twrp for the p8 and not p8 lite.
When I go into recovery mode my phone locks that read huawey, I tried with fastboot command to delete the wrong recovery and install the right of the p8 lite but the result does not change, my phone locks that read huawey
i think The commands that you wrote and that I have quoted are also fine for my case, it's' true?
i have version firmware b133 which boot.img from stock rom?
Try to reflash stock boot.img too.
arviit said:
Try to reflash stock boot.img too.
Click to expand...
Click to collapse
but Ido the extraction of the boot.img from the update version b133?
Hi everyone!!
First of all, thanks to everybody who helped me with this situation.
I now am using my baby again as if it was new. I wiped him completely as i stated before and it was as easy as finding the right firmware (136a) and using the vol down + vol up + power button technique. I put the UPDATE.APP file inside a folder named dload in sdcard using other phone (with my p8 was impossible). After that rebooted the device, pressed those 3 buttons and the instalation started successfully.
I just cant explain how happy i was. I stayed 3 days without it.
After that I have been messing with fastboot so thanks to everyone who made me realize that i didnt need to do all of this, but well, A full wipe is always welcome.
Is there any custom kernel on the way for overclock my baby?
Please explain to me how do I put SOLVED in this thread as my problem is already solved...
Thanks
siul_lasc said:
Hi everyone!!
First of all, thanks to everybody who helped me with this situation.
I now am using my baby again as if it was new. I wiped him completely as i stated before and it was as easy as finding the right firmware (136a) and using the vol down + vol up + power button technique. I put the UPDATE.APP file inside a folder named dload in sdcard using other phone (with my p8 was impossible). After that rebooted the device, pressed those 3 buttons and the instalation started successfully.
I just cant explain how happy i was. I stayed 3 days without it.
After that I have been messing with fastboot so thanks to everyone who made me realize that i didnt need to do all of this, but well, A full wipe is always welcome.
Is there any custom kernel on the way for overclock my baby?
Click to expand...
Click to collapse
I also have same problem. Now i am going to try this. thank you very much.
---------- Post added at 02:22 PM ---------- Previous post was at 01:53 PM ----------
siul_lasc said:
Hi everyone!!
First of all, thanks to everybody who helped me with this situation.
I now am using my baby again as if it was new. I wiped him completely as i stated before and it was as easy as finding the right firmware (136a) and using the vol down + vol up + power button technique. I put the UPDATE.APP file inside a folder named dload in sdcard using other phone (with my p8 was impossible). After that rebooted the device, pressed those 3 buttons and the instalation started successfully.
I just cant explain how happy i was. I stayed 3 days without it.
After that I have been messing with fastboot so thanks to everyone who made me realize that i didnt need to do all of this, but well, A full wipe is always welcome.
Is there any custom kernel on the way for overclock my baby?
Click to expand...
Click to collapse
Yeah finally my phone is working now thanks to you I searched many treads and forums but i cant find a solution. But finally i got an easy solution Thank you again bro.. Good Luck !!!:good::good::good::good::good::good::good:
Just download your firmware version, use huawei extractor to extract boot.img,cust.img,recovery.img and system.img
After that,download mininal adb fastboot copy you files into fastboot folder , enter fastboot mode on your phone and from fastboot folder,open cmd and type these commands:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
After this your phone will boot normally. Once you've done this, copy update.app to your sdcard or internal and install it by local update. Once you've done all this,your phone is fine.
May I know how do you wipe your internal storage? and what if after wiping, im unable to get into recovery mode? does it mean phone is not usable anymore?
SOLUTION
Hello. I'm the bigest mess on androids but i know that flashing stock recovery can remove any TWRP/CWR. If its too powerfull flash stock boot and run fastboot -w.(fastboot -w erases all PERSONAL data)
Guys Help me in this
guys help me
http://forum.xda-developers.com/honor-7/help/stock-emui-recovery-image-lost-twrp-t3442021
thank you !!
VladHD said:
Just download your firmware version, use huawei extractor to extract boot.img,cust.img,recovery.img and system.img
After that,download mininal adb fastboot copy you files into fastboot folder , enter fastboot mode on your phone and from fastboot folder,open cmd and type these commands:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
After this your phone will boot normally. Once you've done this, copy update.app to your sdcard or internal and install it by local update. Once you've done all this,your phone is fine.
Click to expand...
Click to collapse
After days of searching the internet i couldnt find any working solution. then i tried the local update without flashing al those .img's. ( didnt work )
Now after flashing al those .img's my phone works again but its a whole different phone. Only problem is when i try to update him with the update.app file it won't go any further then 5%.
If you know why this happens let me know
Further i wanna thank you one last time .. thank you
Hello all,
I really need help for my ZE500KL. In summary, it stucks on ASUS logo and bootloop. I can't get to welcome screen.
It is not rooted, i've never touched to the original system. I got this problem after an update from OTA. The update was not interrupted for information.
I can get to the recovery menu, can do a wipe data/factory reset, but it solves nothing. Same problem.
I've tried :
- apply update from adb but this stops at 46% and failed with an error like E:failed to verify the whole-file signature
- apply update from microSD but it stops and failed without error message
I don't know if there is another way to fix.
Thanks
Bro go to the asus site and download the whole rom nd flash it thru recovery.
M also had a same problem.
So let me know nd which variant u hav?
Thanks for the reply.
When i said "I have apply update", this means that i've downloaded zip file from Asus website, and loaded it via the recovery but the process stops at 46%.
Maybe it will work for a custom recovery like CWM or TWRP but as i know, there is not a working CWM or TWRP for ZE500KL at this time. Maybe.
For me, the stock recovery don't work for loading the zip file from ASUS. It says something like : Unable to verify the whole-file signature, Process failed
Fus_XDA said:
Thanks for the reply.
When i said "I have apply update", this means that i've downloaded zip file from Asus website, and loaded it via the recovery but the process stops at 46%.
Maybe it will work for a custom recovery like CWM or TWRP but as i know, there is not a working CWM or TWRP for ZE500KL at this time. Maybe.
For me, the stock recovery don't work for loading the zip file from ASUS. It says something like : Unable to verify the whole-file signature, Process failed
Click to expand...
Click to collapse
If your device stops at logo this means that it boots into fastboot mode. I`ve had a same problem. You can take this adb driver . After installing you need to put in C:\adb file boot.img from archive which you dowloaded from official asus.com, then run cmd.
Code:
cd c:\adb
and last command will be...
Code:
fastboot boot boot.img
try it.
kvantor said:
If your device stops at logo this means that it boots into fastboot mode. I`ve had a same problem. You can take this adb driver . After installing you need to put in C:\adb file boot.img from archive which you dowloaded from official asus.com, then run cmd.
Code:
cd c:\adb
and last command will be...
Code:
fastboot boot boot.img
try it.
Click to expand...
Click to collapse
I tried. It doesn't work.
I proceed like this :
1- I've booted the device in recovery mode, connect it to PC and uninstall the device and his driver in to the device manager. I do the same in fastboot mode
2- I've installed the 15 seconds adb ver 1.43. As it is recommanded, I force install of drivers to "Android ADB interface" for recovery mode and "Android Bootloader Interface" for fastboot mode. At this time, adb detects the device via "c:\adb> adb devices"
3-I've extracted the "boot.img" from UL-ASUS Z00E-WW-12 8 5 106-user.zip from Asus Website
4-No problem to proceed with "c:\adb> fastboot boot boot.img" BUT that's all.
--> The device boots, passes the ASUS logo with the powered by android at the bottom", arrives to the second ASUS logo (the one animated), then there are messages "Android upgrading, optimising 1 of 1 app", "Starting apps", then it reboots, and bootloops .... again and again. I have to take out the battery to turn it off.
Have you tried downloading the full ROM image from the ASUS support website again? (yes, download again and try flashing your device again). Usually when it says something about signature verification failed, it is due to the incomplete download of the ROM image (corrupted), or that it has been modified.
Do report back the results.
Download Link (for your convenience): http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500KL/UL-ASUS_Z00E-WW-12.8.5.222-user.zip
Download Link (for your convenience): http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500KL/UL-ASUS_Z00E-WW-12.8.5.222-user.zip
Click to expand...
Click to collapse
I's been thinking to this ...
I've downloaded 3 times the ROM from asus website. The download procees has been interrupted because of internet problem but i was able to resume after. I've even downloaded previous version. I am able to extract the zip file to my computer without error like cooupted file or CRC..
I need to know if other persons have the same problem exactly with this ZE500KL because, i have recently done the same thing with my ZE551ML and i had no problem.
Have you tried flashing the previous updates (software versions) instead? Could be a "bogus" update.
Rizzed said:
Have you tried flashing the previous updates (software versions) instead? Could be a "bogus" update.
Click to expand...
Click to collapse
Yes. Same problem with .172
I was been delighted when i see this TWRP for ZE500KL http://forum.xda-developers.com/zenfone-2-laser/development/recovery-twrp-3-0-0-0-recovery-t3319704 and it works,
But my joy was so short.
It says that it was unable to install the ZIP file because the ZIP is for WW_PHONE, and my phone is an OMNI_ZE500KL !!! What is this ? Never heard about it before. What's weird with this AUS ZIP file !!!??
Can you try to ADB Sideload the ASUS ROM?
sagematt said:
Can you try to ADB Sideload the ASUS ROM?
Click to expand...
Click to collapse
Yes. I've tried every way to install.
Fusxda said:
Yes. I've tried every way to install.
Click to expand...
Click to collapse
Open a thread on ZenTalk: http://www.asus.com/zentalk/
Never heard about this OMNI SKU before.
If someone else has the same exact phone with you with a different SKU (perhaps WW?), you could try asking him to backup the recovery.img on his phone for you to flash. After that, just flash recovery via fastboot and you should be good to go.
up
Rizzed said:
If someone else has the same exact phone with you with a different SKU (perhaps WW?), you could try asking him to backup the recovery.img on his phone for you to flash. After that, just flash recovery via fastboot and you should be good to go.
Click to expand...
Click to collapse
Hello , do you find the solution i have the same problem
could you help me , thanx a lot :good:
2xboy said:
Hello , do you find the solution i have the same problem
could you help me , thanx a lot :good:
Click to expand...
Click to collapse
Stock recovery (and TWRP):
https://github.com/sabpprook/android_device_asus_ze500kl/releases
Guys I Found The Solution For This Problem :
1-Flash TWRP Recovery From The Link : https://github.com/sabpprook/android_device_asus_ze500kl/releases
2- Wipe Data and Cache And dalvik Cache and Very Important (Wipe System).
3-Flash Back The Stock recovery From The Same Link Above.
4-Flash Your .zip Stock Frimware From The Link : https://www.asus.com/support/Download/39/1/0/20/KsY29RCpsJ2bea9O/32/
5-Please if this Helped You Press Thanks! Button And Enjoy.
The Trick: Stock Recovery Cannot Wipe System But TWRP Can.
P.S: You Cannot Flash The Frimware From TWRP ... It Will Give An Error.
Enjoy
I find answer
Bro, download this file failobmennik.usite.pro/updater-script.noext and change \META-INF\com\google\android\updater-script
Hi,
I'll test it, and will give feed-back
Thanks
I have an Asus zenfone 5 which was bricked and for some reason sideloading from the adb stopped after installing 54% of the firmware so I decided to go for cynogenmod, which was sucessfully flashed. I now want the old stock android back and dont know what to do. If i use ADB again after 54% it will just stop and I tried using TWRP too but it said wrong version and all.
I want to know if i can use ODin to flash my device and if yes then how?. Also in odin im required of an md5 file which i dont know where to get. I have a lollipop firmware and please tell if i need more than that or not.
ODIN is only for Samsung phones.
Follow this guide to go back to Stock: http://forum.xda-developers.com/showpost.php?p=65367132&postcount=2
dgadelha said:
ODIN is only for Samsung phones.
Follow this guide to go back to Stock: http://forum.xda-developers.com/showpost.php?p=65367132&postcount=2
Click to expand...
Click to collapse
Thanks for the info. I haven't checked it how it will go but at the end I still have to sideload my lollipop update right. That it the problem here since adb always stops at as I reach 54% of the installation. Is there any other way to update to lollipop and the end when your guide finishes?
And thank you for replying
zaris47 said:
Thanks for the info. I haven't checked it how it will go but at the end I still have to sideload my lollipop update right. That it the problem here since adb always stops at as I reach 54% of the installation. Is there any other way to update to lollipop and the end when your guide finishes?
And thank you for replying
Click to expand...
Click to collapse
Yes. Just download 3.23.40.60 firmware, extract recovery.img from the firmware .zip, boot to Droidboot, flash the recovery.img, reboot to recovery, then sideload the firmware. That's it.
i have the same problem in a501 cg
dgadelha said:
Yes. Just download 3.23.40.60 firmware, extract recovery.img from the firmware .zip, boot to Droidboot, flash the recovery.img, reboot to recovery, then sideload the firmware. That's it.
Click to expand...
Click to collapse
my installation also stops at 54% and i can't go back to droidboot mode. phone always reboots at recovery mode. what can i do??? please help me.
foysal105 said:
my installation also stops at 54% and i can't go back to droidboot mode. phone always reboots at recovery mode. what can i do??? please help me.
Click to expand...
Click to collapse
I had the same issues but I resolved it
U must have the latest adb tools
U must have recovery image of .52 not .60 (lollipop )
.60 firmware ,
First flash the fastboot from .60 firmware ( It will be droidboot)
Then flash the recovery (.52 recovery )
Reboot into recovery then sideload the .60 firmware ( in case the sideload fails try to relock bootloader then sideload the firmware .)
After that u can manually update to .78 and .87 fimwares respectively . @zaris47 try this as I mentioned and plz google for the files .
i was using .78 and now can't get back to droidboot of .78 (lollipop)
Boomshiva said:
I had the same issues but I resolved it
U must have the latest adb tools
U must have recovery image of .52 not .60 (lollipop )
.60 firmware ,
First flash the fastboot from .60 firmware ( It will be droidboot)
Then flash the recovery (.52 recovery )
Reboot into recovery then sideload the .60 firmware ( in case the sideload fails try to relock bootloader then sideload the firmware .)
After that u can manually update to .78 and .87 fimwares respectively . @zaris47 try this as I mentioned and plz google for the files .
Click to expand...
Click to collapse
as i can't get back to droidboot mode, how can i flash the recovery of .52?? is it possible to flash from recovery mode of .78 ??
Try flashing RAW firmware....its the easiest and safest way to do...
Somewhere around the threads, there is a windows cmd prompt based script created by dgadelha(or tank0412, i forgot ?) which allows u to flash the rom in just a single click......try to search it...I'll post the link if i got that post...
Also,note that RAW fw for A500CG also works for A501CG,but only via this script ,not Asus flash tool apllication(only works for a500cg)...
thanks for the advice, lokking forward for your next post
prathmesh pande said:
Try flashing RAW firmware....its the easiest and safest way to do...
Somewhere around the threads, there is a windows cmd prompt based script created by dgadelha(or tank0412, i forgot ��) which allows u to flash the rom in just a single click......try to search it...I'll post the link if i got that post...
Also,note that RAW fw for A500CG also works for A501CG,but only via this script ,not Asus flash tool apllication(only works for a500cg)...
Click to expand...
Click to collapse
thank u so much. i found the asus flash tools, but can't find the raw file for a501cg. i will now search according to ur advice. if u find the link then please post it asap. thanx in advance.
foysal105 said:
thank u so much. i found the asus flash tools, but can't find the raw file for a501cg. i will now search according to ur advice. if u find the link then please post it asap. thanx in advance.
Click to expand...
Click to collapse
There is no RAW fw specifically for a501cg and aft doesnt work with a501cg...
however , raw firmware for a500cg works for a501cg too.....use this guide http://forum.xda-developers.com/showpost.php?p=65367132&postcount=2
Credits to dgadelha
some changes to be made hin the guide:-
Extract the contents too from the raw file to the same folder and also keep the raw file with it...
try running the command file "NOT" as administrator...
hope it helps
Sorry for the late reply, so i did ask all of you suggested and im stuck at dgadelha.
The adb wasn't taking the sideload even though i flashed the recovery and droidboot.
Hi all,
Please help me!
I think i messed up pretty badly here. I tried downgrading from Oreo to Nougat but I think I tried to install a wrong image. Now when i boot i get:
ERROR MODE
Attention! Please update system again
Error!
Fun NO : 15 (bl31 image)
Error NO : 1 (security verify failed)
I've tried the dload method but it doesn't even start. I boot it up holding power, vol+, vol-, and it gets stuck at "your device is booting now."
I can't access twrp, even after flashing it again.
I can get into fastboot and I've tried manually flashing images from an update.app, but after that, the same problem still persists. Trying to relock the boot loader gives an error "command not allowed"
Does anybody have any ideas?
yes i have same because battery is not dead still wait battery remain if dead then plug against work fastboot need firmware rollback version only C432B185 try HWOTA this is the best
Gamkutopolowk said:
yes i have same because battery is not dead still wait battery remain if dead then plug against work fastboot need firmware rollback version only C432B185 try HWOTA this is the best
Click to expand...
Click to collapse
So you're saying that I wait until my battery drains, then go into fastboot and roll back to C432B185? Maybe you could help me by outlining the steps to flash via fastboot?
flash via fastboot by HWOTA follow this link https://romprovider.com/2018/01/download-install-b185-nougat-update-huawei-p10-plus/
only method 1
Gamkutopolowk said:
flash via fastboot by HWOTA follow this link
only method 1
Click to expand...
Click to collapse
So i tried this method, but it didn't work. It flashes TWRP, and instructs me to disconnect the USB cable and boot into TWRP, but i can't boot into TWRP. It goes directly to the error message even when holding the buttons down.
because stuck in fastboot is freeze or corrupted still wait battery drains when dead battery hold vol down + plug USB then run in HWOTA...............
Gamkutopolowk said:
because stuck in fastboot is freeze or corrupted still wait battery drains when dead battery hold vol down + plug USB then run in HWOTA...............
Click to expand...
Click to collapse
So after waiting for the battery to drain, holding vol down, and plugging the USB, I'm back where I was before with being in fastboot. Running HWOTA results in the same problem for when it tells me to reboot to TWRP after install, the phone goes to error mode.
I'm pretty sure the bl31 image corruption is preventing me from booting into recovery.
try other methode if work or not run fastboot need files from huawei firmware extractor open Update.app save files boot.img + recovery.img + system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Test it
Gamkutopolowk said:
try other methode if work or not run fastboot need files from huawei firmware extractor open Update.app save files boot.img + recovery.img + system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Test it
Click to expand...
Click to collapse
Ok so i flashed boot.img, recovery.img, system.img all OKAY.
Reboot and i get the same error..
The problem is with the bl31 image, which is in ARM Trusted Firmware.
Maybe if i could figure out how to flash TRUSTFIRMWARE.img that would work. I tried this, but it doesn't work. I don't know the partition name.
fastboot flash trustfirmware
unknown partition 'trustfirmware'
Try HWOTA flash TWRP then hold power + vol up stay hold vol up long 15 seconds
Gamkutopolowk said:
Try HWOTA flash TWRP then hold power + vol up stay hold vol up long 15 seconds
Click to expand...
Click to collapse
Still goes straight to the error screen.
blahblah31415 said:
Still goes straight to the error screen.
Click to expand...
Click to collapse
Please show me your mobile
blahblah31415 said:
Ok so i flashed boot.img, recovery.img, system.img all OKAY.
Reboot and i get the same error..
The problem is with the bl31 image, which is in ARM Trusted Firmware.
Maybe if i could figure out how to flash TRUSTFIRMWARE.img that would work. I tried this, but it doesn't work. I don't know the partition name.
fastboot flash trustfirmware
unknown partition 'trustfirmware'
Click to expand...
Click to collapse
thank you sir u saved my phone from drowning just flashed this trustedfirmware and hurray my phone got out of error mode
Junaid Shafi said:
thank you sir u saved my phone from drowning just flashed this trustedfirmware and hurray my phone got out of error mode
Click to expand...
Click to collapse
How you did that?
blahblah31415 said:
Hi all,
Please help me!
I think i messed up pretty badly here. I tried downgrading from Oreo to Nougat but I think I tried to install a wrong image. Now when i boot i get:
ERROR MODE
Attention! Please update system again
Error!
Fun NO : 15 (bl31 image)
Error NO : 1 (security verify failed)
I've tried the dload method but it doesn't even start. I boot it up holding power, vol+, vol-, and it gets stuck at "your device is booting now."
I can't access twrp, even after flashing it again.
I can get into fastboot and I've tried manually flashing images from an update.app, but after that, the same problem still persists. Trying to relock the boot loader gives an error "command not allowed"
Does anybody have any ideas?
Click to expand...
Click to collapse
Hi
I have the exact same problem
After trying all of the methods I found (dload, HWOTA, TWRP, etc), I finally took the phone to the service center.
They told me it was an easy fix, then they called me and told me that probably they were going to replace the motherboard
I'm still waiting for them to call me for confirmation.
If you got any news on this, please keep posting
Thanks!
gonzalomorenorovetto said:
Hi
I have the exact same problem
After trying all of the methods I found (dload, HWOTA, TWRP, etc), I finally took the phone to the service center.
They told me it was an easy fix, then they called me and told me that probably they were going to replace the motherboard
I'm still waiting for them to call me for confirmation.
If you got any news on this, please keep posting
Thanks!
Click to expand...
Click to collapse
I actually ended up using dc pheonix to fix it. It worked perfectly. I had to pay about 15 dollars for credits. It used some sort of backdoor and flashed a new ROM from scratch.
blahblah31415 said:
I actually ended up using dc pheonix to fix it. It worked perfectly. I had to pay about 15 dollars for credits. It used some sort of backdoor and flashed a new ROM from scratch.
Click to expand...
Click to collapse
I tried DC Phoenix and It did not work. They returned me my money.
At the service center they finally replaced my motherboard, in warranty, even though the phone was unlocked and I bricked it completely