Hello.
First I'm sorry for my English not so good, but i need you to help me.
Like the title, my zenfone is too slow everywhere before the boot animation begin when i use kitkat bootloader/recovery. You guys can tell me why this happens?
For null imei, i tried this: http://forum.xda-developers.com/zenfone-5/help/rewrite-imei-null-00049-zenfone-5-t3389046
but no success, after this code "sec_provision_v1.1.0.2.exe -c%COM% -i2 %IMEI1% %IMEI2% -u3 28943447 -u1 28943447", nothing happens.
Please, i really need help.
Thanks!
nttL said:
Hello.
First I'm sorry for my English not so good, but i need you to help me.
Like the title, my zenfone is too slow everywhere before the boot animation begin when i use kitkat bootloader/recovery. You guys can tell me why this happens?
For null imei, i tried this: http://forum.xda-developers.com/zenfone-5/help/rewrite-imei-null-00049-zenfone-5-t3389046
but no success, after this code "sec_provision_v1.1.0.2.exe -c%COM% -i2 %IMEI1% %IMEI2% -u3 28943447 -u1 28943447", nothing happens.
Please, i really need help.
Thanks!
Click to expand...
Click to collapse
you're supposed to Replace %IMEI1% and %IMEI2% with your first and second IMEI number, you can find it at the sticker the back of your phone, open the case.
replace %COM% with number of your comport when you open the device manager of your PC.
I'm at lollipop now, but no success rewriting IMEI, look this screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sec_prov seems not responding
double post, sorry.
nttL said:
I'm at lollipop now, but no success rewriting IMEI, look this screenshot.
sec_prov seems not responding
Click to expand...
Click to collapse
@nttL this method need root, open SuperSu app and grant root access
sarbi333 said:
@nttL this method need root, open SuperSu app and grant root access
Click to expand...
Click to collapse
My phone is rooted.
Let us see you logs
Related
Hello. Some time ago I flashed stock rom ALE-L21C22B160 and I got blank page in "Motion control" so I went to Huawei site and I downloaded C432B170. Then I extracted boot, recovery and system, then I flashed it without any problems.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I simply did "fastboot reboot" and my device rebooted with the old firmware, nothing changed at all.
I think you also need to flash to Cust.img
EpicBas said:
I think you also need to flash to Cust.img
Click to expand...
Click to collapse
Thanks, it worked, but I can't get proper firmware, I'm always getting one of those:
- blank "Motion control" page
- phone getting into rescue mode due to some problem with boot.img
Can you give me a link to firmware that actually works and has motion control? Thanks.
Lotherad said:
Thanks, it worked, but I can't get proper firmware, I'm always getting one of those:
- blank "Motion control" page
- phone getting into rescue mode due to some problem with boot.img
Can you give me a link to firmware that actually works and has motion control? Thanks.
Click to expand...
Click to collapse
@Lotherad Try one of these which matches your phone http://huawei-updates.ru/ALE-L21.html
EpicBas said:
@Lotherad Try one of these which matches your phone http://huawei-updates.ru/ALE-L21.html
Click to expand...
Click to collapse
It says "Attention! Please update system again Error! Func NO : 11 (recovery image) Error NO : 2 (load failed!)". Oh man, is there any hope for me? :crying:
did you unlock the bootloader ? and enabled USB bedugging ? ( sorry if it's stupid question )
any way , here is a thread that you do not need to flash with fastboot via commands ( C432B052 Rom version ) , it will automatically do the job , and i think it would work fine for you , and also if you want to have marshmallow , you can simply follow the reste of the thread
Link : http://tundevs.blogspot.com/p/huawei-p8-marshmallow.html
good luck
Since I updated to Marshmallow, when editing an image in Samsung gallery it crashes.
Two scenarios:
1. View a .PNG (for example a screenshot), click edit: crash.
2. View a .JPG, click edit, click effects: crash.
All was fine with Lollipop.
Stock ROM, no root.
30 views and no one who's willing to spend 5 minutes to test this?
Ne problems here, mate. I using much before and after 6.0.1 update. The device is 928f, stock, no rooted. Try to get logcat
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Without root logcat is useless
thegios said:
Without root logcat is useless
Click to expand...
Click to collapse
managed to get logcats thru adb
AndroidRuntime: FATAL EXCEPTION: main
AndroidRuntime: Process: com.sec.android.mimage.photoretouching, PID: 26519
AndroidRuntime: java.lang.RuntimeException: Canvas: trying to use a recycled bitmap [email protected]
thegios said:
managed to get logcats thru adb
Click to expand...
Click to collapse
Clear data and cache. Try editor with random picture the the internet and then with jpeg from the rear camera. Try log again.
I found and solved the problem but to do so I had to reset the phone.
The filter.provider package has to be enabled.
Strange cos with Lollipop it was disabled and editing was working. Even stranger cos after upgrade to Marshmallow even having all enabled editing was crashing.
After reset editing was working so I started disabling apps one by one (instead of in bulk) and found the culprit.
There is a lot of culprits while using disabler. Check every package before and after disable. Thanks for the info above!
Of course, I know, strange thing is that with the exact same disabled app with Lollipop it was working
Hi,
I've hard bricked my Pro 5. No recovery access, no boot to rom, locked bootloader. After many search i see this : https://forum.xda-developers.com/meizu-pro-5/how-to/meizu-customer-service-flash-tools-save-t3447678, but this is bull-****.
I test many manipulations to get something on my phone other than "Bootloader, Locked".
So i dicovered this : Press and holp Vol + and Vol - and press one time power button. We get this :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After research about this, we get this :
http://forum.gsmhosting.com/vbb/f777/galexy-s6-exynos-7420-dead-1975230/#post12369382
And this :
http://www.mediafire.com/file/9qmezaezy1fyzrr/Galaxy_S6_Boot_recovery.pptx
Possible way to unlock hardbricked Pro 5 ?
Same way exist for Qualcomm Processor : http://www.androidbrick.com/unbrick...-have-the-right-kind-of-rom-qhsusb_dload_edl/
Subscribed, i do also have a spare "bricked" device
same problem here bro.tried everything..only mode available is fastboot and locked bootloader.in pc device manager i get unknown android 1.going to investigate the problem futher more.pls keep us in touch.tnx
barbonee said:
same problem here bro.tried everything..only mode available is fastboot and locked bootloader.in pc device manager i get unknown android 1.going to investigate the problem futher more.pls keep us in touch.tnx
Click to expand...
Click to collapse
Hey there. Got the same problem. Tried everything. Nothing happens. Have you got your problem solved yet?
The same problem
Sent from my PRO 5 using Tapatalk
Only way to solve this is taking the phone to technical service. Done it myself. Be careful tought, they will try to make you change the entire mother board (280€), but if you insist they will "find a way" to install the correct software in your phone and leave it as if it was new
it is possible to recovery via dongle ... but sn and imei can be lost
Try this thread.
https://forum.xda-developers.com/me...hard-bricked-lost-t3838461/page2#post79752427
Try this thread; it worked perfectly for me.
In the last week I tried to block the bootloader lara to take it to grant, but I have been marking error at the time of executing the commands and it makes it impossible for me to install the stock ROM in a normal way, since after marking error when executing the Command without the "Re-Lock Bootloader" fails me and I do not install the operating system. Any solution?
This is my problem:
https://drive.google.com/file/d/0B7JDFUG5qbldYTZLdHg4UVBEOEE/view?usp=drivesdk
KevinSYB said:
In the last week I tried to block the bootloader lara to take it to grant, but I have been marking error at the time of executing the commands and it makes it impossible for me to install the stock ROM in a normal way, since after marking error when executing the Command without the "Re-Lock Bootloader" fails me and I do not install the operating system. Any solution?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
ok, not a solution but: why are you trying to relock anyway?
Droidphilev said:
ok, not a solution but: why are you trying to relock anyway?
Click to expand...
Click to collapse
I need to send the equipment to warranty and with the unlocked bootloader I can not.
KevinSYB said:
I need to send the equipment to warranty and with the unlocked bootloader I can not.
Click to expand...
Click to collapse
Ok, fair enough. FYI: the pic that you attached cannot be shown.
Droidphilev said:
Ok, fair enough. FYI: the pic that you attached cannot be shown.
Click to expand...
Click to collapse
Do you mean it is not legal to show it? Or that you can't get it to display?
pastorbob62 said:
Do you mean it is not legal to show it? Or that you can't get it to display?
Click to expand...
Click to collapse
nonono, nothing about being legal/ilegal. Now i see a link but yesterday there was only a broken thumbnail
Droidphilev said:
nonono, nothing about being legal/ilegal. Now i see a link but yesterday there was only a broken thumbnail
Click to expand...
Click to collapse
:good:
SOLVED UPDATED TO LAST OTA AND DID THE WHOLE TUTORIAL AGAIN.
Tried different USB ports. ( 3.0 / 2.0 )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried in 2 different PCs and 6 usb ports 2.0 and 3.0
Windows 8 and windows 10.
Have you tried using cmd (administrator) istead of PowerShell?
Lamizure said:
Have you tried using cmd (administrator) istead of PowerShell?
Click to expand...
Click to collapse
Yes
It's really strange... Have you unlocked the bootloader?
Yes " Device State - Unlocked "
It's due to the filename being too long. I found a different fastboot which allowed long filenames. Rename it to one letter like r.img or something and see if it works.
Had exact the same problem under Linux
People mention to change to another USB port but that did not help
What helped... if all stuff is correctly installed (adb, root rights, etc.)
1. Reboot into the bootloader (even if you are in already)
adb reboot bootloader
Click to expand...
Click to collapse
2. Then directly (use the arrow up key to really be fast enough) send the command for flashing (my file was called twrp.img)
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
If this doesn't work you could try (under Linux) to write a little script with just the two above commands or try
adb reboot bootloader && fastboot flash recovery twrp.img
Click to expand...
Click to collapse
It seems to be a timing problem... One might need to play around with the time between this two commands. E.g. wait until the bootloader screen is on the phone and directly issue the flash command. Sorry after it worked for me I did not bother to investigate it in more detail.