Hi guys, do you find other methods to fix this problem? I didn't nothing, just the phone updated itself and camera started to say "not found" with black screen.
I tried to back in stock rom WW-2.21.40.30 (possible fix method), now it don't says nothing but the screen still remains black, when i change to front camera it crashes.
{
"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"
}
Picture is not me, just found in google with same problem.
Asus update did this and i can't send my phone to them, so my camera is gone?
Blak3n said:
Hi guys, do you find other methods to fix this problem? I didn't nothing, just the phone updated itself and camera started to say "not found" with black screen.
I tried to back in stock rom WW-2.21.40.30 (possible fix method), now it don't says nothing but the screen still remains black, when i change to front camera it crashes.
Picture is not me, just found in google with same problem.
Asus update did this and i can't send my phone to them, so my camera is gone?
Click to expand...
Click to collapse
Is your phone rooted?
it's happen to me too, my camera gone blank/missing/not found
for me it's happen after i install TWRP, doesn't matter what TWRP version i install,
but it's can be fix.
drive.google.com/folderview?id=0B5XJj7Sujx-DWmhoY1N4UzNsblE&usp=sharing (its my first time posting so i can't post url copy it to browser)
This is the fix data on my google drive, it's for to use with WW-3.24.40.87
the problem is if you got TWRP installed, after fixing you got your camera back but you lose the TWRP.
Downgrade to KK 2.22.40.54 and follow this, http://forum.xda-developers.com/zenfone-5/general/asus-zenfone-5-root-ww-2-22-40-54-4-4-2-t3128704 or this for non-Linux, https://github.com/sigo/asus-zenfone-5-root/blob/master/README.md#usage-for-other-systems
jephimax said:
Downgrade to KK 2.22.40.54 and follow this, http://forum.xda-developers.com/zenfone-5/general/asus-zenfone-5-root-ww-2-22-40-54-4-4-2-t3128704 or this for non-Linux, https://github.com/sigo/asus-zenfone-5-root/blob/master/README.md#usage-for-other-systems
Click to expand...
Click to collapse
Thanks but i tried and nothing changed
FairuzOnn said:
Is your phone rooted?
it's happen to me too, my camera gone blank/missing/not found
for me it's happen after i install TWRP, doesn't matter what TWRP version i install,
but it's can be fix.
drive.google.com/folderview?id=0B5XJj7Sujx-DWmhoY1N4UzNsblE&usp=sharing (its my first time posting so i can't post url copy it to browser)
This is the fix data on my google drive, it's for to use with WW-3.24.40.87
the problem is if you got TWRP installed, after fixing you got your camera back but you lose the TWRP.
Click to expand...
Click to collapse
Thanks for write your first post to solve my problem
Story of my asus: the phone was working properly, once it fell and the glass broke so I waited for the new glass and when I repaired it, the camera was not working anymore. I tried to reconnect and everything but nothing, the only cause can be an update before or after as has happened to many.
I'll try your method as last chance on software issue because i never flashed in .87, if it doesn't works i'll buy a new camera and lets see. I tried every software fix in the web, maybe it really broke when it fell.
It happens when u unlock ur bootloader
@Blak3n.........I had this issue several times. It's nothing serious and happens when u unlock ur bootloader to flash any custom recovery. This is the only fix if you face the "NO CAMERA" issue for unocking.
Please follow the below instructions:
1. TURN OFF the device
2. Press and hold Volume Up+Power to enter to fastboot/droidboot. When the ASUS logo shows up, release the power button and keep on pressed the Volume UP button. This will take you to droidboot/fastboot mode.
3. check whether your PC detects the fastboot...
Code:
fastboot devices
if not, go to device manager and install the fastboot driver(by online). if fails, install from the PC by selecting the android device from the list.
4. You must start with this version UL-ASUS_T00F-WW-2.21.40.30-user.zip to get ur camera working. download this image UL-ASUS_T00F-WW-2.21.40.30-user.zip: http://dlcdnet.asus.com/pub/ASUS/Ze...user.zip?_ga=1.61130092.1708615694.1457697474
5. extract fastboot.img, boot.img, recovery.img from the zip file and copy to ADB folder to flash. Copy UL-ASUS_T00F-WW-2.21.40.30-user.zip to ADB folder as well.
6. run the below commands:
Code:
fastboot flash fastboot fastboot.img
fastboot reboot-bootloader
wait for reboot.....
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
7. then go to recovery by selecting from the menu
8. in the recovery, select wipe data/factory reset
9. select wipe cache partition
10. select apply update over adb sideload
11. Now check whether your PC detects the ADB over USB. if not, go to your PC's device manager and install the ADB driver online. if fails, install from the PC by selecting the android device from the list.
12. after successful detection, run below command
Code:
adb sideload UL-ASUS_T00F-WW-2.21.40.30-user.zip
13. Reboot ur device. Your camera should work.
14. Now upgrade to lollipop following the version I mention sequentially. Otherwise it will fail. Just copy them to ur SD card and disconnect USB cable. your phone will automatically detect the update. no need to flash anything in fastboot.
>> UL-ASUS_T00F-WW-2.21.40.30-user
>> UL-ASUS_T00F-WW-2.22.40.54-user
>> UL-ASUS_T00F-WW-3.24.40.78-user
>> UL-ASUS_T00F-WW-3.24.40.87-user
15. if it works hit thanks
I did a lot of research on it but no luck. there few Zen5 devices where u can't unlock the bootloader. I'm also a victim. For better understanding: http://forum.xda-developers.com/showpost.php?p=66307220&postcount=16
Good luck.
a8962383 said:
@Blak3n.........I had this issue several times. It's nothing serious and happens when u unlock ur bootloader to flash any custom recovery. This is the only fix if you face the "NO CAMERA" issue for unocking.
Please follow the below instructions:
1. TURN OFF the device
2. Press and hold Volume Up+Power to enter to fastboot/droidboot. When the ASUS logo shows up, release the power button and keep on pressed the Volume UP button. This will take you to droidboot/fastboot mode.
3. check whether your PC detects the fastboot...
Code:
fastboot devices
if not, go to device manager and install the fastboot driver(by online). if fails, install from the PC by selecting the android device from the list.
4. You must start with this version UL-ASUS_T00F-WW-2.21.40.30-user.zip to get ur camera working. download this image UL-ASUS_T00F-WW-2.21.40.30-user.zip: http://dlcdnet.asus.com/pub/ASUS/Ze...user.zip?_ga=1.61130092.1708615694.1457697474
5. extract fastboot.img, boot.img, recovery.img from the zip file and copy to ADB folder to flash. Copy UL-ASUS_T00F-WW-2.21.40.30-user.zip to ADB folder as well.
6. run the below commands:
Code:
fastboot flash fastboot fastboot.img
fastboot reboot-bootloader
wait for reboot.....
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
7. then go to recovery by selecting from the menu
8. in the recovery, select wipe data/factory reset
9. select wipe cache partition
10. select apply update over adb sideload
11. Now check whether your PC detects the ADB over USB. if not, go to your PC's device manager and install the ADB driver online. if fails, install from the PC by selecting the android device from the list.
12. after successful detection, run below command
Code:
adb sideload UL-ASUS_T00F-WW-2.21.40.30-user.zip
13. Reboot ur device. Your camera should work.
14. Now upgrade to lollipop following the version I mention sequentially. Otherwise it will fail. Just copy them to ur SD card and disconnect USB cable. your phone will automatically detect the update. no need to flash anything in fastboot.
>> UL-ASUS_T00F-WW-2.21.40.30-user
>> UL-ASUS_T00F-WW-2.22.40.54-user
>> UL-ASUS_T00F-WW-3.24.40.78-user
>> UL-ASUS_T00F-WW-3.24.40.87-user
15. if it works hit thanks
I did a lot of research on it but no luck. there few Zen5 devices where u can't unlock the bootloader. I'm also a victim. For better understanding: http://forum.xda-developers.com/showpost.php?p=66307220&postcount=16
Good luck.
Click to expand...
Click to collapse
I know, right? Why TF does A**-US need to do s#!t like mess-up the motherboards of every 5th ZenFone 5, WTF. I'm stuck in these suckly stock ROMs while others are enjoying the feature-rich environment of the custom ROM community. Well, done A**-US. If I wanted "unhackable", I'd buy an iPhone.
cnswico said:
I know, right? Why TF does A**-US need to do s#!t like mess-up the motherboards of every 5th ZenFone 5, WTF. I'm stuck in these suckly stock ROMs while others are enjoying the feature-rich environment of the custom ROM community. Well, done A**-US. If I wanted "unhackable", I'd buy an iPhone.
Click to expand...
Click to collapse
You can flash custom rom but can't ensure your camera will be working as before. I have no camera issue but to me, taking snap is less important and I'm using RR rom with the camera bug. I'm fine with that. The camera is black/dark but it captures photos at least.
a8962383 said:
You can flash custom rom but can't ensure your camera will be working as before. I have no camera issue but to me, taking snap is less important and I'm using RR rom with the camera bug. I'm fine with that. The camera is black/dark but it captures photos at least.
Click to expand...
Click to collapse
Naw. mine doesn't lose its camera when the bootloader is unlocked. I'm one of the owners of a ZenFone 5 that freezes/hangs then restarts randomly. Those are the only issues that affect the ZF5 users with their defective motherboards.
cnswico said:
Naw. mine doesn't lose its camera when the bootloader is unlocked. I'm one of the owners of a ZenFone 5 that freezes/hangs then restarts randomly. Those are the only issues that affect the ZF5 users with their defective motherboards.
Click to expand...
Click to collapse
Bro, there are no defects on the motherboard. It's because of the unlocked bootloader. If you want to unlock it properly, then check it out: http://forum.xda-developers.com/showthread.php?t=3389883
Sent from my ASUS_T00F using XDA-Developers mobile app
a8962383 said:
Bro, there are no defects on the motherboard. It's because of the unlocked bootloader. If you want to unlock it properly, then check it out: http://forum.xda-developers.com/showthread.php?t=3389883
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
A'right, mate! I'll give this a shot. I'll notify you via your post regarding the results.
a8962383 said:
Bro, there are no defects on the motherboard. It's because of the unlocked bootloader. If you want to unlock it properly, then check it out: http://forum.xda-developers.com/showthread.php?t=3389883
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
Well, still it doesn't work. I've tried every single method regarding that here on XDA. I've even tried those from EDA, Windroidica, and InfoBros. They all don't work.
The only method that managed to make a difference is ozank's automated script. It didn't completely stop the freezes, but I noticed that the reboots are a whole lot less frequent:
NO METHOD/OTHER METHODS - freezes about every 3 minutes. A few seconds when using any app.
ozank's AUTO-SCRIPT - freezes about every 20 - 30 minutes ONLY WHEN USING APPS. Haven't encountered the freezes when the device is on standby or daydream mode.
cnswico said:
Well, still it doesn't work. I've tried every single method regarding that here on XDA. I've even tried those from EDA, Windroidica, and InfoBros. They all don't work.
Click to expand...
Click to collapse
It's been 10days for me. no freeze/reboot so far.
a8962383 said:
It's been 10days for me. no freeze/reboot so far.
Click to expand...
Click to collapse
I'm glad to hear that some have managed to fix it. But as for me, and maybe some others, we'll just have to lay in the dust until a savior picks us up. (no religion, okay? )
Either that, or I'm switching phones.
CM 13.1
Hi.. I flashed CM 13.1 latest stable build on asus Zenfone 5 (T00F). I am facing the same camera issue. Is there any fix for this camera Issue other than Downgrade?Is there any change that can be done to system/framework/bspcapability.jar in order to make it work?
Thanks in advance.
Blak3n said:
Hi guys, do you find other methods to fix this problem? I didn't nothing, just the phone updated itself and camera started to say "not found" with black screen.
I tried to back in stock rom WW-2.21.40.30 (possible fix method), now it don't says nothing but the screen still remains black, when i change to front camera it crashes.
Picture is not me, just found in google with same problem.
Asus update did this and i can't send my phone to them, so my camera is gone?
Click to expand...
Click to collapse
Dear all;
I find a solution for this error..
İf you have only black screen from back camera and th front camera has been stopped error pls read this steps..
1.. download ZenfoneAssist
I cant give you a link for zenfone assist because of the site rules (10 posts). but you can google zenfoneassist. and download from XDA..
2.Run as administrator..
3. RELOCK YoUR BOOTLOADER. wait a little minute while the ifwi and dnx files has been downloading..
4.Program says you what will you do. open droidboot menu and pls wait.
5. phone will restart and you will use your camera immediatly..
For more questions pls write me "[email protected]"
PS: the program is quotation but I tried and worked my camera..
Sorry for my english..
a8962383 said:
@Blak3n.........I had this issue several times. It's nothing serious and happens when u unlock ur bootloader to flash any custom recovery. This is the only fix if you face the "NO CAMERA" issue for unocking.
Please follow the below instructions:
1. TURN OFF the device
2. Press and hold Volume Up+Power to enter to fastboot/droidboot. When the ASUS logo shows up, release the power button and keep on pressed the Volume UP button. This will take you to droidboot/fastboot mode.
3. check whether your PC detects the fastboot...
Code:
fastboot devices
if not, go to device manager and install the fastboot driver(by online). if fails, install from the PC by selecting the android device from the list.
4. You must start with this version UL-ASUS_T00F-WW-2.21.40.30-user.zip to get ur camera working. download this image UL-ASUS_T00F-WW-2.21.40.30-user.zip: http://dlcdnet.asus.com/pub/ASUS/Ze...user.zip?_ga=1.61130092.1708615694.1457697474
5. extract fastboot.img, boot.img, recovery.img from the zip file and copy to ADB folder to flash. Copy UL-ASUS_T00F-WW-2.21.40.30-user.zip to ADB folder as well.
6. run the below commands:
Code:
fastboot flash fastboot fastboot.img
fastboot reboot-bootloader
wait for reboot.....
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
7. then go to recovery by selecting from the menu
8. in the recovery, select wipe data/factory reset
9. select wipe cache partition
10. select apply update over adb sideload
11. Now check whether your PC detects the ADB over USB. if not, go to your PC's device manager and install the ADB driver online. if fails, install from the PC by selecting the android device from the list.
12. after successful detection, run below command
Code:
adb sideload UL-ASUS_T00F-WW-2.21.40.30-user.zip
13. Reboot ur device. Your camera should work.
Click to expand...
Click to collapse
I did this (more specifically "asus-zenfone.com/2015/08/how-to-fix-unfortunetely-camera-not-found-zenfone.html") and returned to stock room UL-ASUS_T00F-WW-2.21.40.30 And the camera still does not work.
Has anyone found any other solution?
niquelfer said:
I did this (more specifically "asus-zenfone.com/2015/08/how-to-fix-unfortunetely-camera-not-found-zenfone.html") and returned to stock room UL-ASUS_T00F-WW-2.21.40.30 And the camera still does not work.
Has anyone found any other solution?
Click to expand...
Click to collapse
The URL you have given, won't work. It didn't work for me as well. Seems like you didn't try my steps but you are quoting me. Would please try/retry the steps again and report it here?
a8962383 said:
The URL you have given, won't work. It didn't work for me as well. Seems like you didn't try my steps but you are quoting me. Would please try/retry the steps again and report it here?
Click to expand...
Click to collapse
Okay, I tried your steps. The problem remains the same.
This time I used the fastboot.img, boot.img, recovery.img files from the room as you suggested in step 5 and not the same files from de url.
niquelfer said:
Okay, I tried your steps. The problem remains the same.
This time I used the fastboot.img, boot.img, recovery.img files from the room as you suggested in step 5 and not the same files from de url.
Click to expand...
Click to collapse
Did you somehow kept your bootloader unlocked? There are few devices (mine as well) where the camera doesn't work if you unlock bootloader. If you port any custom ROM, you have to sacrifice your camera and vice-versa. Please relock the bootloader with a signed boot.img, fastboot.img, and recovery.img.
Related
So you've bricked your phone. Well as long as the boot loader works then your "brick" is just a soft-brick. Follow this simple guide and flash a custom rom in a couple of minutes. I am not claiming ownership of this method, but its the first time Ive seen it and it helped me so here Good Luck!
Download the attachments.
Unzip both files to a folder on your desktop.
Run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder.
{
"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"
}
Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
Need any additional help? Feel free to ask This should work on all Moto G models that have a TWRP image and have a bootloader unlocked.
eg0097 said:
So you've bricked your phone. Well as long as the boot loader works then your "brick" is just a soft-brick. Follow this simple guide and flash a custom rom in a couple of minutes. I am not claiming ownership of this method, but its the first time Ive seen it and it helped me so here Good Luck!
Download the attachments.
Unzip both files to a folder on your desktop.
Run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder. Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
Need any additional help? Feel free to ask This should work on all Moto G models that have a TWRP image and have a bootloader unlocked.
Click to expand...
Click to collapse
Everything went well till step 5.
In terminal window of phone i could find select..... but after that how to proceed I donot know.......... what commands should i use on TWRP terminal...........
Phone didn't get detected in ADB even in TWRP terminal
pl. help
subodhverma21 said:
Everything went well till step 5.
In terminal window of phone i could find select..... but after that how to proceed I donot know.......... what commands should i use on TWRP terminal...........
Phone didn't get detected in ADB even in TWRP terminal
pl. help
Click to expand...
Click to collapse
TWRP termnal is just so that your phone will connect as adb to your pc.
eg0097 said:
TWRP termnal is just so that your phone will connect as adb to your pc.
Click to expand...
Click to collapse
my problem got resolved.........
actually driver was the only problem which was not allowing ADB to detect device in RECOVERY mode, though device was detected in FASTBOOT mode
So I reinstall the driver to get ADB Interface installed in system> device manager
and then followed your remaining steps i.e. 6 onwards
Thanks a lot.....
Not really sure about the following, but I hard-bricked my phone while rooting it a few days ago. Black screen, phone wasn't visible in ADB / fastboot, LED didn't change after plugging in the charger etc.
The only thing that helped: holding the power button for at least 2 minutes. The device restarted afterwards w/o any issues.
Can't find the source of it anymore ...
Very useful guide, I revived my soft - bricked Moto G
still not working
on my xt1032 moto g 16gb version I just have the warning screen that the bootloader is unlocked.
followed a lot threads but nothing helped till now.
tried your verswion and from point 1 to 7 all went well.
But I can't flash the rom. i've tried out about 6 various rom's but everything it says fail. on the screen in the twrp always stands unable to mount /data /system /storage
what can I do to fix this problem?
sascha-1102 said:
on my xt1032 moto g 16gb version I just have the warning screen that the bootloader is unlocked.
followed a lot threads but nothing helped till now.
tried your verswion and from point 1 to 7 all went well.
But I can't flash the rom. i've tried out about 6 various rom's but everything it says fail. on the screen in the twrp always stands unable to mount /data /system /storage
what can I do to fix this problem?
Click to expand...
Click to collapse
|Could someone help please? I am in the same boat and when try to run the above command, I also get this error and no file appears in the sdcard hence cant flash it.
Thanks
My Moto G is working again since one week with stock 4.4.2. I had to do it ain a bit different way...
First, I could get into bootloader and recovery. after several hours my pc recognizes my phone again, but till now I don't know why and how.
Wanted to reflash stock 4.4.2 kitkat again, but this won#t work. so I figured out that after unpacking, I had to replace the gpt.bin with the one from the 4.4.4 stock update. (see down as zip file)
Then I flashed the 4.4.2 stock again to my phone and all went well. It started again. (now I'm on stock recovery)
If you want to do the OTA 4.4.4 Update, there have to be a few things on your phone, otherwise update always fails.
1. if you have x-posed frameworks installed - uninstall it completely
2. if rooted, go into super su preferences and activate unroot all
3. do not activate developper options, or if done before, just uncheck the mark
4. you must be on stock recovery!
5. restart your phone
6. now search after update in about phone.
if bootloader is unlocked - doesn't matter - can stay unlocked
with me it first installed the 176.* OTA because my flashed stock was still 175.*
this went well, then again searched for update and 210.* (4.4.4 kitkat) could be downloaded ota. after it was done, click to install and it should work well - took a bit time.
now you are on stock 4.4.4, but without root atm.
if you want root back - now flash the newest twpr recovery 2.7.7.1 to phone, because here an OTG USB stick will be also recognized - OTG cable needed before. (don't need to push files first to phone)
copied before the su.zip to usb stick and sticked it to phone, then go into recovery. here you can install super user or better su.zip. restart phone and you got your root back on 4.4.4 stock kitkat rom
I solved this issue with twrp sideload.It worked great.
Thanks it worked for me..BUT !!!
Hi and thanks a lot.. it worked for me but you have to add some more option for who are still having troubled in unbricking. like i had..
but it can't be done without your method as on OP..
how i got bricked !!! my Moto g dual (indian)
i tried to downgrade from 4.4.4 to 4.4.2 to flash custom Rom and got system partition corrupt.
again i tried to flash stock images but no use, actual problem was System and data was not formatting.
even if you try million times and you can never successfully flash stock images without error..
however i was checking many threads in xda to resolve this problem but couldn't figured it out, as i was not new to XDA i had confidence that i can come out from this issue. until this thread gave me a hint but not a solution but still this thread is a part of the solution
let come to the unbricking method (only for those who cant flash Stock firmware from fastboot)
Reboot to fastboot..
flash Philz recovery first. get it from here.. http://forum.xda-developers.com/showthread.php?t=2639626
better to use Kernel Flasher by my old buddy Ghostfreak NB http://forum.xda-developers.com/showthread.php?t=2214724,
you just need to extract and copy the recovery to extracted kernel Kernel_Flashing_Tool_v2.0 in IMG folder and run kernel Kernel_Flashing_Tool_v2.0.bat.
press 1 and it will flash recovery, press enter it will reboot to Philz recovery,
now format System, data and whatever you can!!\
next reboot to Bootloader from Recovery,
and then follow procedure as OP
if you want to flash stock rom get from here http://forum.xda-developers.com/moto-g/development/4-4-3-moto-g-stock-rom-t2804891 and adb push as advise by OP. now you have stock rom running without any issues
Edit..
You can also flash custom ROMs with ease.
Note you better flash recovery through kernel flasher tool..
Ysharief said:
Hi and thanks a lot.. it worked for me but you have to add some more option for who are still having troubled in unbricking. like i had..
but it can't be done without your method as on OP..
how i got bricked !!! my Moto g dual (indian)
i tried to downgrade from 4.4.4 to 4.4.2 to flash custom Rom and got system partition corrupt.
again i tried to flash stock images but no use, actual problem was System and data was not formatting.
even if you try million times and you can never successfully flash stock images without error..
however i was checking many threads in xda to resolve this problem but couldn't figured it out, as i was not new to XDA i had confidence that i can come out from this issue. until this thread gave me a hint but not a solution but still this thread is a part of the solution
let come to the unbricking method (only for those who cant flash Stock firmware from fastboot)
Reboot to fastboot..
flash Philz recovery first. get it from here.. http://forum.xda-developers.com/showthread.php?t=2639626
better to use Kernel Flasher by my old buddy Ghostfreak NB http://forum.xda-developers.com/showthread.php?t=2214724,
you just need to extract and copy the recovery to extracted kernel Kernel_Flashing_Tool_v2.0 in IMG folder and run kernel Kernel_Flashing_Tool_v2.0.bat.
press 1 and it will flash recovery, press enter it will reboot to Philz recovery,
now format System, data and whatever you can!!\
next reboot to Bootloader from Recovery,
and then follow procedure as OP
if you want to flash stock rom get from here http://forum.xda-developers.com/moto-g/development/4-4-3-moto-g-stock-rom-t2804891 and adb push as advise by OP. now you have stock rom running without any issues
Edit..
You can also flash custom ROMs with ease.
Note you better flash recovery through kernel flasher tool..
Click to expand...
Click to collapse
I get this error
When im typing adb push AOSP ( i renamed to that name ) /sdcard/ attacks me this: not found. Any help?:crying: Plez :c
eg0097 said:
So you've bricked your phone. Well as long as the boot loader works then your "brick" is just a soft-brick. Follow this simple guide and flash a custom rom in a couple of minutes. I am not claiming ownership of this method, but its the first time Ive seen it and it helped me so here Good Luck!
Download the attachments.
Unzip both files to a folder on your desktop.
Run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder.
Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
Need any additional help? Feel free to ask This should work on all Moto G models that have a TWRP image and have a bootloader unlocked.
Click to expand...
Click to collapse
I haven't actually bricked my phone but looks like my ROM.
So, I am trying to make a ROM previously in First Built the ROM didn't even wrote System [That was my fault as I wrote the the 'system' folder in Zip as 'System' and in update scripts 'system' to be extracted in '/system']
But , now the ROM has written /system but remains on Warning Boot loader Locked screen and starts to warm up I have tried Installing Kernels to fix it but no luck please help.
Device->Moto G Falcon XT1033
ROM Details->Custom ROM based on stock 5.1
Priority of problem->5 ,as I use MultiRom and have this Custom ROM as Secondary and CM 13 as primary ,but suggest a fix ASAP .
@Sid_Sun - Flash the latest factory firmware image for your model. Once that boots, proceed to custom ROMs if desired.
Factory Firmware Image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
@Sid_Sun - Flash the latest factory firmware image for your model. Once that boots, proceed to custom ROMs if desired.
Factory Firmware Image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
My device is booting up I am trying to make a ROM which is not booting and the booting method is by MultiRom the not booting ROM is as secondary so I can use CM 13 as primary but not boot my Custom ROM I want a fix to that issue.
Sid_Sun said:
My device is booting up I am trying to make a ROM which is not booting and the booting method is by MultiRom the not booting ROM is as secondary so I can use CM 13 as primary but not boot my Custom ROM I want a fix to that issue.
Click to expand...
Click to collapse
The MultiROM thread would be the place to ask:
http://forum.xda-developers.com/moto-g/development/modmultirom-v30wip08-01-2014-t2997071
I have no experience with MultiROM, but I believe a Kernel with kexec-hardboot support is required.
lost101 said:
The MultiROM thread would be the place to ask:
http://forum.xda-developers.com/moto-g/development/modmultirom-v30wip08-01-2014-t2997071
I have no experience with MultiROM, but I believe a Kernel with kexec-hardboot support is required.
Click to expand...
Click to collapse
This isn't MiltiRom's Fault probably but nvm I will flash The Custom ROM as primary and see how it goes .
Friend in step 3 you say "Run the adb setup file and press (Y) all 3 times." But what is the file?
In the list there are only 2 to download files
adb-setup-1.3.zip
twrp.zip
Where do i put the command in the 4th step?
Please help
Recently I unlocked the bootloader on my ZF5 to flash a modded cm 13 ROM, but after that I found out that the camera stopped working. I know somehow it is happening because I unlocked the bootloader incorrectly. I searched many solutions but any of them corrected the problem. When I open any camera app, all I see is a black image. Some one please help me with this. Thx.
The only fix...
Dude, i have that problem too. No custom rom can fix our camera as we have Zen5(A500CG/A501CG) with different hardware models. Most of the zen5 devices work fine after unlocking bootloader but my friend....our cameras won't work if we unlock bootloader. I have tried each and every methods to unlock and each and every custom rom available over the net but no luck. Camera remains black/dark/blank. The only solution is to revert back to stock OS. Start flashing with this version UL-ASUS_T00F-WW-2.21.40.30-user.zip, otherwise the camera won't work in stock too.
If u want to stay on custom rom(as im doing right now, i love CM), then install pixelmaster camera from play store, turn ON flash, set focus to INFINITY.......the camera will be blank but at least it will capture images.
a8962383 said:
Dude, i have that problem too. No custom rom can fix our camera as we have Zen5(A500CG/A501CG) with different hardware models. Most of the zen5 devices works fine after unlocking bootloader but my friend....our cameras won't work if we unlock bootloader. I have tried each and every methods to unlock and each and every custom rom available over the net but no luck. Camera remains black/dark/blank. The only solution is to revert back to stock OS. Start flashing with this version UL-ASUS_T00F-WW-2.21.40.30-user.zip, otherwise the camera won't work in stock too.
If u want to stay on custom rom(as im doing right now, i love CM), then install pixelmaster camera from play store, turn ON flash, set focus to INFINITY.......the camera will be blank but at least it will capture images.
Click to expand...
Click to collapse
Do you know a guide to go back to stock rom and relock the bootloader?
soares7vinicius said:
Do you know a guide to go back to stock rom and relock the bootloader?
Click to expand...
Click to collapse
The proper way to revert back to stock is as below:
1. Download ADB folder and extract: https://drive.google.com/file/d/0B-Fin8UxrD6PUmN6SkVPMXR3UTA/view
2. Download UL-ASUS_T00F-WW-2.21.40.30-user.zip(for WW model only ) and copy to ADB folder: http://dlcdnet.asus.com/pub/ASUS/Ze...ser.zip?_ga=1.182320871.1398112610.1460908265
3. If you have other than WW model, please search and download the UL-ASUS_T00F-WW-2.21.40.30-user.zip here: https://www.asus.com/id/support/Download/39/1/0/2/96nqlxHp1VKV4Rdz/32/
4. Extract the fastboot.img, boot.img, and recovery.img files from the downloaded rom/zip file and copy to ADB folder
5. Reboot your device to bootloader. Turn off device > press volume up+power button together > after asus logo appears, release power but keep vol up pressed > you are in bootloader mode. Go to ADB folder and open command window(CMD) there by pressing shift+right mouse click
6. Run this commands,
Code:
fastboot flash fastboot fastboot.img
fastboot reboot-bootloader
wait for reboot...
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
7. Now select recovery from the fastboot menu and wait for reboot to recovery
8. In the recovery select wipe/factory reset data, this may take some time
9. Then select wipe cache
10. Then select apply update from ADB
11. Run this command,
Code:
adb sideload UL-ASUS_T00F-WW-2.21.40.30-user.zip
12. Let it be installed. It will take around 10mins, then reboot system.
13. You will find kitkat is installed.
14. Download UL-ASUS_T00F-WW-2.22.40.54-user.zip, UL-ASUS_T00F-WW-3.24.40.78-user.zip, UL-ASUS_T00F-WW-3.24.40.87-user.zip from this link for your model: https://www.asus.com/id/support/Download/39/1/0/2/96nqlxHp1VKV4Rdz/32/
15. Copy the UL-ASUS_T00F-WW-2.22.40.54-user.zip file into your SDCard/internal storage, then disconnect usb cable. Your phone will detect an update and proceed with the update.
16. Do step 15 for other two files as well. Please follow the sequence of the files, otherwise the update will fail.
17. Enjoy stock lollipop on your zen 5.
Hope it helps.
a8962383 said:
The proper way to revert back to stock is as below:
1. Download ADB folder and extract:
2. Download UL-ASUS_T00F-WW-2.21.40.30-user.zip(for WW model only ) and copy to ADB folder:
3. If you have other than WW model, please search and download the UL-ASUS_T00F-WW-2.21.40.30-user.zip here:
4. Extract the fastboot.img, boot.img, and recovery.img files from the downloaded rom/zip file and copy to ADB folder
5. Reboot your device to bootloader. Turn off device > press volume up+power button together > after asus logo appears, release power but keep vol up pressed > you are in bootloader mode. Go to ADB folder and open command window(CMD) there by pressing shift+right mouse click
6. Run this commands,
Code:
fastboot flash fastboot fastboot.img
fastboot reboot-bootloader
wait for reboot...
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
7. Now select recovery from the fastboot menu and wait for reboot to recovery
8. In the recovery select wipe/factory reset data, this may take some time
9. Then select wipe cache
10. Then select apply update from ADB
11. Run this command,
Code:
adb sideload UL-ASUS_T00F-WW-2.21.40.30-user.zip
12. Let it be installed. It will take around 10mins, then reboot system.
13. You will find kitkat is installed.
14. Download UL-ASUS_T00F-WW-2.22.40.54-user.zip, UL-ASUS_T00F-WW-3.24.40.78-user.zip, UL-ASUS_T00F-WW-3.24.40.87-user.zip from this link for your model:
15. Copy the UL-ASUS_T00F-WW-2.22.40.54-user.zip file into your SDCard/internal storage, then disconnect usb cable. Your phone will detect an update and proceed with the update.
16. Do step 15 for other two files as well. Please follow the sequence of the files, otherwise the update will fail.
17. Enjoy stock lollipop on your zen 5.
Hope it helps.
Click to expand...
Click to collapse
Thanks! I'll try it. But after that the bootloader will be relocked?
soares7vinicius said:
Thanks! I'll try it. But after that the bootloader will be relocked?
Click to expand...
Click to collapse
yes, it will be locked.
a8962383 said:
yes, it will be locked.
Click to expand...
Click to collapse
After doing step 6, I can't boot into recovery. What's wrong?
soares7vinicius said:
After doing step 6, I can't boot into recovery. What's wrong?
Click to expand...
Click to collapse
when u reboot into recovery, u will see an android logo with "!" sign. Now, press.......Power + Vol Down + Vol UP sequentially at a time.
a8962383 said:
when u reboot into recovery, u will see an android logo with "!" sign. Now, press.......Power + Vol Down + Vol UP sequentially at a time.
Click to expand...
Click to collapse
Thanks, but I found another problem, when i sideload this package to recovery it shows that i need to upgrade to newest 4.3 image first. What package is that?
Edit: Forget it, it worked! Thanks!
soares7vinicius said:
Thanks, but I found another problem, when i sideload this package to recovery it shows that i need to upgrade to newest 4.3 image first. What package is that?
Click to expand...
Click to collapse
If the firmware flashing is successful, just follow the steps. Don't read or worry about anything in the console. Please follow the firmware up-gradation version as I mentioned, otherwise it will fail.
Btw, did you check the how many cores online with your kernel from kernel adiutor?
If you use hotplug as governor, camera won't start and you need 4 of 4 cores.
soares7vinicius said:
Recently I unlocked the bootloader on my ZF5 to flash a modded cm 13 ROM, but after that I found out that the camera stopped working. I know somehow it is happening because I unlocked the bootloader incorrectly. I searched many solutions but any of them corrected the problem. When I open any camera app, all I see is a black image. Some one please help me with this. Thx.
Click to expand...
Click to collapse
Delete
a8962383 said:
Dude, i have that problem too. No custom rom can fix our camera as we have Zen5(A500CG/A501CG) with different hardware models. Most of the zen5 devices work fine after unlocking bootloader but my friend....our cameras won't work if we unlock bootloader. I have tried each and every methods to unlock and each and every custom rom available over the net but no luck. Camera remains black/dark/blank. The only solution is to revert back to stock OS. Start flashing with this version UL-ASUS_T00F-WW-2.21.40.30-user.zip, otherwise the camera won't work in stock too.
If u want to stay on custom rom(as im doing right now, i love CM), then install pixelmaster camera from play store, turn ON flash, set focus to INFINITY.......the camera will be blank but at least it will capture images.
Click to expand...
Click to collapse
Man, so this is a error on a Drive ?!
So, why the mans can put the Asus camera on the roms, or, can fix this ?
I think this is a driver error and can be solved ?
JulianoJr said:
Man, so this is a error on a Drive ?!
So, why the mans can put the Asus camera on the roms, or, can fix this ?
I think this is a driver error and can be solved ?
Click to expand...
Click to collapse
It's not a driver error. Many developers have already ported Asus Pixelmaster camera with their ROMs and with proper drivers as well. The main problem is, there are few Zen5 devices which use camera api in a different manner like mine. Cyanogenmod source doesn't have it's api calls as per these certain devices needed. As most of the custom ROMs are based on CM, so none of them could make camera working. It's basically a firmware issue which is still unresolved.
So we can't use any roms :c
JulianoJr said:
So we can't use any roms :c
Click to expand...
Click to collapse
lolz.....no bro, we can't. If u really want to use custom ROM, then install Pixelmaster camera and use with this settings:
Go to settings>Resolution to 8MP>focus to infinity>turn on flash>Optimization ON>Anti-shake Auto>Image quality FINE.
This setting will at least capture images but the screen will be black. After taking the first image, u will see the camera screen but with very low light/brightness. It won't help much though. Honestly, I have tried all the custom ROMs over the net.If u want, u can. Good luck.
After trying to flash the latest 7.1.1 cm 14 ropms many people ended up in bootloop where your phone switch on ,shows mi logo and rebbot again. Many where not able to enter recovey mode also.. Now i come up with a perfect soluton for you all on how to fix these issues in your phone..Lets Get started..
If anything goes wrong iam not responsible.Do it At your Own Risk.
Requirements
------------------
1. Enter edl .rar (attached below)
2.Miui Stock Rom (FastBoot). Download it from(only use this version) here
3.Phone Must have Charge of 50% or more.
4.Unlock Boot loader.zip (Attched Below)
6.MIPhone Tools and install it .Get it from here
6.Extract all the file
7. PDA Net.(Optional,but installing will be useful). Get it from here
Once you have all of the file we can move on
Steps
------
1. Put Your Phone into fastboot mode by pressing Vol Down and power button at same time.
2.Connect your Phone With Your PC
3.Run EDL Mode.exe from the zip Enter edl.. Now your phone must be in edl mode. You can see a light blinking at the top of your phone.
4. From the Unlock Boot Loader folder copy "emmc_appsboot.mbn" to the rom folder ie)
kenzo_global_images_V7.1.8.0.LHOMICL_20160129.0000.14_5.1_global--> images--> paste it there (replace/overwrite if existing)
5. Once the above step is done, Open MIFlash tool as administrator. Browse the folder
kenzo_global_images_V7.1.8.0.LHOMICL_20160129.0000.14_5.1_global and select it..
{
"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"
}
6.From the drop Down Menu Select Advanced.
7.Set Fastboot Script As Flash_ALL.Bat.
8.Set Flash Programmer As prog_emmc_firehose_8976_ddr.mbn from images folder.
9. Set RAW Xml File as rawprogram*.xml from images folder
10. Set Patch XML File as patch*.xml from images folder.
11. Video Help HERE.... Watch from 2.40 (Ignore the other portion,We dont need that Part)
Special [email protected] for the video.. I didn't made that video..
12. Once The Above step is done. Click REFRESH OPTION,and you will see Phone detected By The Name COMXX.(XX will be a number)
13.Click Flash and Wait for some time and allow the phone to reboot.
14.Once all the step is done your phone will be good to use..:fingers-crossed: :fingers-crossed:
UNLOCKING BOOT LOADER AND INSTALLING TWRP AGAIN
-------------------------------------------------------------------------
1.Once Your Phone Reboots successfully enable USB Debugginf From Developer Option.
2.Connect Your phone to your PC and Open CMD as administrator.
3.Type in "adb devices".
4. Cmd will show a random number and Device (Everyone will be knowing this,but for info only iam writing it here)
5.Type "adb reboot bootloader". Now your phone will boot into fastboot mode.
6.Type "fastboot oem device-info" to get device status.
7.Type "fastboot oem unlock-go" to unlock bootloader.
8.Again type "fastboot oem device-info" to check to find if device is unlocked.(Do not reboot YET)
9. Now Downlaod TWRP from HERE
10. Now Got to the folder containig TWRP . By holding the Shift Key Of key Board ,right click the mouse and select OPEN COMMAND WINDOW HERE.
11. Type "fastboot flash recovery recovery_filename.img"
12.Type "fastboot reboot".
You Phone will be good to go. If anything goes wrong or you have any doubt Comment Below do not pm me..i will not reply..
If this thread helpef you thumbs up and do comment and shre this post
So i do not need to unlock the boot loader before using MiTool to flash phone via EDL
ahh988 said:
So i do not need to unlock the boot loader before using MiTool to flash phone via EDL
Click to expand...
Click to collapse
Nope if phone is bricked enter fastboot mode and run enter edl.exe to enter edl,flash ROM using mi flash tool
adithyan25 said:
Nope if phone is bricked enter fastboot mode and run enter edl.exe to enter edl,flash ROM using mi flash tool
Click to expand...
Click to collapse
I did that but phone is still stuck . I'm getting infinite boot animation ?
ahh988 said:
I did that but phone is still stuck . I'm getting infinite boot animation ?
Click to expand...
Click to collapse
Boot animation or simply mi logo and then vibrating and again rebooting???
If mi flash tool shows successfully done without any errors then
Try this
Roeboot to fast boot and type
fastboot oem unlock-go
I guess it will be fixed
adithyan25 said:
Boot animation or simply mi logo and then vibrating and again rebooting???
If mi flash tool shows successfully done without any errors then
Try this
Roeboot to fast boot and type
fastboot oem unlock-go
I guess it will be fixed
Click to expand...
Click to collapse
I am stuck at boot animation with the three white dots spinning for ever ? will try to do as you said
I tried fastboot oem unlock-go but i get response: token verification failed and device still stuck on bootanimation
well, i think this caused by relocking bootloader after we flash a new firmware. if that happens, just go in fastboot mode by hold power button + volume down, then unlock it again using mi unlock. reboot it..your twrp is back.
no need to enter edl mode & install twrp again, btw thanks..this is helpful
nitephoenix said:
well, i think this caused by relocking bootloader after we flash a new firmware. if that happens, just go in fastboot mode by hold power button + volume down, then unlock it again using mi unlock. reboot it..your twrp is back.
no need to enter edl mode & install twrp again, btw thanks..this is helpful
Click to expand...
Click to collapse
always my pleasure
For some mi unlock stucks at 50%.. I was one of them...every time I try fails...so I found this was the only way for those who can't access it using mi unlock
tips to avoid relocking bootloader, when u want to flash a new firmware..just delete emmc apsbot.mbn file inside the firmware using winrar or etc, or u can use psy-man firmware because the emmc file has been deleted
nitephoenix said:
tips to avoid relocking bootloader, when u want to flash a new firmware..just delete emmc apsbot.mbn file inside the firmware using winrar or etc, or u can use psy-man firmware because the emmc file has been deleted
Click to expand...
Click to collapse
Yeah...I know that...but it does not support volte. .only abhisheks fw sprt volte
nitephoenix said:
tips to avoid relocking bootloader, when u want to flash a new firmware..just delete emmc apsbot.mbn file inside the firmware using winrar or etc, or u can use psy-man firmware because the emmc file has been deleted
Click to expand...
Click to collapse
@nitephoenix
Can we then flash update marshmallow global firmware this way? (Just delete emmc apsbot.mbn file inside the firmware). Thanks
Pleroma said:
@nitephoenix
Can we then flash update marshmallow global firmware this way? (Just delete emmc apsbot.mbn file inside the firmware). Thanks
Click to expand...
Click to collapse
don't flash official miui from twrp (you better do it in edl mode), but yes you can flash custom miui like miui eu, miuipro, multirom, epic miui etc from twrp. and..after u delete the emmc file inside the firmware which is included on every miui rom, your bootloader will be safe
nitephoenix said:
don't flash official miui from twrp (you better do it in edl mode), but yes you can flash custom miui like miui eu, miuipro, multirom, epic miui etc from twrp. and..after u delete the emmc file inside the firmware which is included on every miui rom, your bootloader will be safe
Click to expand...
Click to collapse
I used to flash it via twrp ..(by deleting bootllader file) followed by flashing lazyflasher...I didn't faced any prblm yet
Mine behaves different
I tried restoring the backup it started to back up and completed sucessfully but when i reboot there comes Mi logo and again it boots to TWRP Recovery .... Same case with any ROM ... Kindly tell me what to do.
ZCX recovery i have.
sarabeshsab said:
I tried restoring the backup it started to back up and completed sucessfully but when i reboot there comes Mi logo and again it boots to TWRP Recovery .... Same case with any ROM ... Kindly tell me what to do.
ZCX recovery i have.
Click to expand...
Click to collapse
Probably the problem with bootloader file
not a whole lot of talk anywhere else so i'll try here. i just got my kenzo few days ago, jumped the gun and started trying to get twrp on it. i'm assuming the bootloader was locked. As of right now it wont boot up, its in edl mode maybe... red led flashes and i can upgrade driver to 9008. sometimes its recognized by miflash and when it is and i try to flash stock fastboot it gives me an error. i know thats a lot to take in but i'm trying to cover all my bases. the phone came from overseas so sending it back isnt really an option. any help is appreciated.
Jjleininger said:
not a whole lot of talk anywhere else so i'll try here. i just got my kenzo few days ago, jumped the gun and started trying to get twrp on it. i'm assuming the bootloader was locked. As of right now it wont boot up, its in edl mode maybe... red led flashes and i can upgrade driver to 9008. sometimes its recognized by miflash and when it is and i try to flash stock fastboot it gives me an error. i know thats a lot to take in but i'm trying to cover all my bases. the phone came from overseas so sending it back isnt really an option. any help is appreciated.
Click to expand...
Click to collapse
Download eiter China based ROM or ROM from post.
Mi flash tool have many prolems.
Some tips:-
Make sure driver enforcement is disabled in PC.
All drivers including PDA net is installed.
Copy paste the unlocked bootloade file inside images folder and replace original one. Even after tryig this method it fails try my other method unbrick viafasrboot
uhm, this does not work for some reason...
i did everything as you said but in the end it just says cathasrophic error and something
After flashing i get Mi logo, vibration and reboot, please help
Warning
Before Proceeding backup your data
TRY at OWN risk I'm NOT Responsibe if you BRICK YOUR DEVICE
Update- This method is tested & working with latest ota update NMB26.54-74
[/CENTER][/B][/SIZE][/COLOR]
IF ANYTHING GOES WRONG Download & Flash Stock ROM
Stock ROM link
SPFlashTool link
Updated Stock ROM 54-74 GDrive - here
New Oreo 27.43-20 Link
Old version Stock ROM Google Drive Link Stock Rom
nvram backup file by @peacelover94 - here
Solution For
>Tool img DL fail
Just check/tick these option in spflashtool settings & Flash stock rom again
{
"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"
}
Video Guide For Stock Rom Flashing - Youtube
How to Flash Stock Rom via Fastboot Method -
1. Open CMD by Shift + Right Click in Folder where your stock firmware .img files are.
2. Reboot to Fastboot Mode by using cmd command
adb fastboot rebootOr
Switch off then Press & Hold Vol Up + Power button for while once menu appeared Select fastboot by using Vol Up key & confirm by pressing Vol Down Key
3. In fastboot type following command in CMD Window
For checking devices is connected in fastboot enter
fastboot devicesIf Connected then proceed following commands
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img flashing system takes 10+ mins
fastboot flash data userdata.img
fastboot reboot
Download & Install ADB from here
First Unlock your bootloader
1. First of all, enable the Developer Option
To Enable the Developer Option, Go to your Settings -> About -> Software Information -> More -> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled"
2. Go back to settings -> Now you need to enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging
3. Now connect your phone to Computer using USB Cable.
4. When you connect your Phone to Computer, please wait until all the drivers get installed.
5. Open a command prompt window by pressing Shift Key + Right Mouse Click.
6. Now type the command below to reboot your phone to bootloader
adb reboot bootloader7. If you see a pop up to allow USB Debugging on your phone, Click OK.
8. proceed to unlock the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
fastboot oem unlockSay Yes to unlock bootloader and then it will some time format your data
9. Reboot Your Device , You will see Orange Status bla bla bla Don't panic Its normal thing now setup your device but do not restore backup yet
Flashing TWRP and ROOT
Updated Black Screen Fix TWRP - Download
Old Download TWRP
Download latest Magisk zip from here
Or
SuperSu zip from here
Flahed & Tested SuperSU v2.82 works fine but SafetyNet Fails
Sock Recovery if needed Link
1. Connect your device to PC
2. Open CMD by Shift+Right click open cmd where your TWRP_3.1.1.0.img is downloaded.
3. Reboot to Bootloader by
adb reboot bootloader4. Now enter following command in fastboot
fastboot flash recovery TWRP_3.1.1.0.img5. DO NOT USE fastboot reboot
Use "vol up + down + power button" to manually switch off you k8 note, otherwise twrp will restore to stock if you use fastboot reboot command.
6. After Switch Off Press & hold vol up + power button then select recovery by vol up & press vol down key to enter in recovery.
7. Now Wait for 30 Sec/ till phone vibrates, Then press power button + vol up simultaneously until you see twrp lock screen.
8. Just Cancel if It asks for Enter password to decrypt and Allow modification by swipe.
9. If you see internal storage 0mb Then GoTo Wipe and FORMAT DATA once & reboot to recovery
10. GoTo install browse and select Magisk.zip or SuperSU.zip & flash.(optional if needed install Busybox for Android NDK by osm0sis magisk module for busybox)
11. Reboot Enjoy.
Known bug in TWRP-
Battery always shows 50% in TWRP
Video Guide https://youtu.be/HrbppEWlOhs
Join Lenovo K8 Note Development Group on Telegram for direct Conversation Link
WhatsApp Group Link
Enable Wireless Display/MiraCast Magisk Module - Video
Thanks to:
@andy_zhang - for stock rom post link
and me @ysalunke007 for TWRP
NEXT CUSTOM ROM
Big Thanks for the Tutorial. If anything happens wrong while rooting like boot loop or something worse, is there stock rom or firmware to flash or push through adb ?
Yes
peacelover94 said:
Big Thanks for the Tutorial. If anything happens wrong while rooting like boot loop or something worse, is there stock rom or firmware to flash or push through adb ?
Click to expand...
Click to collapse
yes, there is stock ROM
link also provided in this post end.
btw here's direct link Stock ROM
FlashTool link
ysalunke007 said:
yes, there is stock ROM
link also provided in this post end.
btw here's direct link Stock ROM
FlashTool link
Click to expand...
Click to collapse
Thank you very much. The flash tool link does not seems to work. Hope its SP flash tool you are talking about.
flash via adb fastboot methoad i have succesfully flash adb method
peacelover94 said:
Big Thanks for the Tutorial. If anything happens wrong while rooting like boot loop or something worse, is there stock rom or firmware to flash or push through adb ?
Click to expand...
Click to collapse
Nice Job
Finally rooting tutorial for Lenovo K8 Note has become available.
Does SuperSu work fine?
Anas Rahman said:
Does SuperSu work fine?
Click to expand...
Click to collapse
Not tested by me but some user says in original rom post that he flashed superSU from old twrp also works fine.
peacelover94 said:
Thank you very much. The flash tool link does not seems to work. Hope its SP flash tool you are talking about.
Click to expand...
Click to collapse
Yes it's SP flash tool but you can use adb fastboot also
ysalunke007 said:
Not tested by me but some user says in original rom post that he flashed superSU from old twrp also works fine.
Click to expand...
Click to collapse
I'll confirm it tomorrow
ysalunke007 said:
Yes it's SP flash tool but you can use adb fastboot also
Click to expand...
Click to collapse
Please tell me how to flash firmware.Im new to this device firmware flashing
lenrussel said:
Please tell me how to flash firmware.Im new to this device firmware flashing
Click to expand...
Click to collapse
It's easy bro check this guide
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Fastboot Guide
http://www.stupdroid.com/2016/08/flash-stock-rom-via-fastboot-on-android.html?m=1
Does the rom link given here unzips perfectly?
Because i saw in another thread of Lenovo K8note titled firmware, users unable to unzip due to error in system img. Also downloading from baidu needs a user id. If its possible could you or anyone else reading this upload it in some other online storage drive. Im little bit worried about getting a worse situation while rooting. Even if it goes wrong i can use the stock firmware to make it back.
peacelover94 said:
Does the rom link given here unzips perfectly?
Because i saw in another thread of Lenovo K8note titled firmware, users unable to unzip due to error in system img. Also downloading from baidu needs a user id. If its possible could you or anyone else reading this upload it in some other online storage drive. Im little bit worried about getting a worse situation while rooting. Even if it goes wrong i can use the stock firmware to make it back.
Click to expand...
Click to collapse
There is mega download link available too
https://forum.xda-developers.com/an...8note-original-firmware-t3679499/post73946000
lenrussel said:
There is mega download link available too
https://forum.xda-developers.com/an...8note-original-firmware-t3679499/post73946000
Click to expand...
Click to collapse
Thanks for the reply. Anyhow got a work around for downloading from baidu using chrome extension, without account. Just wanted to confirm whether the firmware zip is working fine. If some one used it and been successful, please do tell me.
ysalunke007 said:
It's easy bro check this guide
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Fastboot Guide
http://www.stupdroid.com/2016/08/flash-stock-rom-via-fastboot-on-android.html?m=1
Click to expand...
Click to collapse
Do i have to unlock bootloader again after flashing the firmware in order to root the device?
lenrussel said:
Do i have to unlock bootloader again after flashing the firmware in order to root the device?
Click to expand...
Click to collapse
Yes, I think so. Anyhow there is no need to unlock oem again if you are flashing the rom via TWRP. Anyhow let someone confirm about it.
peacelover94 said:
Yes, I think so. Anyhow there is no need to unlock oem again if you are flashing the rom via TWRP. Anyhow let someone confirm about it.
Click to expand...
Click to collapse
There is a error while extracting zip file of the firmware .just checked, I downloaded it from mega.i want to confirm if its the same for baidu also
lenrussel said:
Do i have to unlock bootloader again after flashing the firmware in order to root the device?
Click to expand...
Click to collapse
No need to unlock bootloader again if you use fastboot method to flash stock firmware , & for spflashtool I'm not sure but I think it remains unlocked
lenrussel said:
There is a error while extracting zip file of the firmware .just checked, I downloaded it from mega.i want to confirm if its the same for baidu also
Click to expand...
Click to collapse
No error while extracting firmware downloaded from baidu
{
"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"
}
DISCLAIMER:
I'm not responsible for any damaged watches or other broken things! All of this is still heavily in development and mainly a developer release, not at all recommended for normal usage!
The following tutorial CAN brick your watch if you're not careful enough! Once again I'm not taking any responsibility!
This has only been tested on Android N so far, Android O is not yet fully tested!
---------------------------------------------------------
Please read before doing anything:
This is a port of TWRP for the Ticwatch E. Currently we're not able to boot it via fastboot (well, it technically does but there's an issue with the video driver) and when trying to flash it the watch will instantly flash the stock recovery over it upon reboot.
To avoid this we have to do a little workaround! Once you reboot your watch it'll restore the stock recovery again! After following these steps your watch will be stuck in a bootloop which we'll fix too tho.
Please keep the Changelog below in mind and read what's working and what's not before asking. We may or may not have seen this issue before already.
Files you'll need:
v003 of "TWRP for Ticwatch E" (and most likely S) - OneDrive Mirror
Stock Recovery for Ticwatch E (and most likely S) - OneDrive Mirror
ADB and Fastboot drivers installed (I recommend "15 Seconds ADB Installer")
Changelog:
Updated Instructions:
Slightly updated the instructions so you won't lose any data if you're already on an bootloader unlocked watch!
v003 (OneDrive Mirror):
Managed to make TWRP persistent! Check Instructions on how to.
v002 (OneDrive Mirror):
Now includes systemless root package inside the TWRP image so you're able to root your watch!
v001 (OneDrive Mirror):
Initial release, no ADB so far. Can't be booted from fastboot directly either due to weird fastboot behavior and has to be flashed first. However upon normal reboot Mobvoi decided to flash over the stock recovery again so we have to do a workaround.
Instructions:
The new Instructions by Luxios require a few less steps AND if you've already unlocked your watch before you won't even lose data!
Enable ADB in the Developer Settings
Once done connect your watch to your computer and do "adb reboot bootloader"
THIS WILL RESET YOUR WATCH:*Once in fastboot mode type "fastboot oem unlock" (if you already have an unlocked bootloader you [font=Verdana, Arial, Helvetica, sans-serif]can skip this[/font])
Follow the on-screen instructions on your watch to unlock it (if you already have an unlocked bootloader you can skip this)
Reboot via "fastboot reboot" and wait until Android Wear fully starts up
One started reboot to the bootloader via the same command as above
Once the bootloader shows up again type "fastboot flash recovery TWRP_TicwatchE_v003.img"
After that type "fastboot oem reboot-recovery" to reboot to the TWRP recovery
In order to make TWRP persistent you need to go to "Install" > "Install ZIP" > "supersu" > "TicwatchE_TWRP_keeper.zip" and flash it
Upon rebooting you may notice it'll get stuck in an infinite TWRP bootloop. To fix this boot into TWRP, then choose "Reboot" > "Bootloader", back in fastboot type "fastboot boot StockRecovery_TicwatchE.img" and wait a few seconds, a few reboots later Android Wear should start right up again.
If you want to root your watch reboot it once again with "adb reboot recovery" and go to the same folder as above, tho this time flash "SuperSU-2.79-wear_systemless.zip"
Unroot/Remove TWRP for Android O Update:
Go to this thread to also update directly to the last Android O update and revert all customizations: https://forum.xda-developers.com/sm...es/android-o-super-easy-ticwatch-e-s-t3789835
Have fun!
You're the best! I'm gonna try as soon as I can, and let you know.
Ok, I'm trying to flash it.
Problem is, it flashes, but when I do fastboot reboot, it will boot in android wear instead that TWRP.
If then I reboot in the recovery with adb reboot recovery, it will be already the stock recovery again... Any tip?
Piereligio said:
Ok, I'm trying to flash it.
Problem is, it flashes, but when I do fastboot reboot, it will boot in android wear instead that TWRP.
If then I reboot in the recovery with adb reboot recovery, it will be already the stock recovery again... Any tip?
Click to expand...
Click to collapse
If your bootloader is (or was) already unlocked you have to lock and then unlock it again for it to work.
Yes sorry, I noticed that right after posting, but I've bad network.
Now seems to have gone all fine, I'm booting it, I'm only unsure it flashed SuperSU well, since it shown an error at the end of the script, although the rest of the log seemed to report all to go fine.
Piereligio said:
Yes sorry, I noticed that right after posting, but I've bad network.
Now seems to have gone all fine, I'm booting it, I'm only unsure it flashed SuperSU well, since it shown an error at the end of the script, although the rest of the log seemed to report all to go fine.
Click to expand...
Click to collapse
The guy who made it initially did send me a picture of it successfully rooted. Should work, errors can happen since TWRP can't write to all partitions yet.
Sadly it looks like SuperSU failed to root. It gave a data partition mounting error at the end of the script, don't know if it is normal. TWRP isn't able to mount data either.
EDIT: Looks like I found a way to boot TWRP without having to lock/unlock bootloader.
Doing this, I managed to boot TWRP after setting the watch up, and in this way, it didn't fail to mount /data. Let's see...
EDIT2: now SuperSU still fails, but for a different reason. I'm gonna ensure that it failed though.
EDIT3: su command responded, so seems that root works. I'll do some more tests.
TWRP is now persistent! Check the updated guide
Rooting succeeded!
Seems like I managed to root the smartwatch using the version 2. For the moment I'm happy like this, next times I'll indeed use new procedures.
EDIT: Yes, I rooted it.
My steps (the ones on OP are the recommended ones):
-Bootloader unlock;
-Boot in Android Wear to enable ADB from Settings;
-Reboot in bootloader with "adb reboot bootloader";
-Flashed this TWRP v2;
-"fastboot reboot", then "adb reboot recovery" as soon as adb was detected while booting.
In this way I managed to avoid the system to flash stock recovery over TWRP.
By the way, I don't recommend my way of rooting it, it's less safe, just follow the updated instructions in OP.
Huge thanks to @EpicLPer
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
BackCheck said:
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
Click to expand...
Click to collapse
If the watch doesn't turn off even after holding the button for a minute then you've damaged something else than just the recovery. Holding down the button normally triggers all the time no matter what, even if you'd have bricked it.
BackCheck said:
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
Click to expand...
Click to collapse
You can flash again the stock recovery with spflash tool.
EpicLPer said:
If the watch doesn't turn off even after holding the button for a minute then you've damaged something else than just the recovery. Holding down the button normally triggers all the time no matter what, even if you'd have bricked it.
Click to expand...
Click to collapse
I really wish I knew what. All I did was flash a bad recovery, pretty sure something was was wrong with the ram disk. All I get is the splash logo for 3 seconds and a brief vibrate.
Luxios said:
You can flash again the stock recovery with spflash tool.
Click to expand...
Click to collapse
I think I need a scatter file to even get started. I've never used the tool so any other instructions would be greatly appreciated.
Great to hear someone that it is working on this! What about Android Wear updates? Did you try if it is possible to install them using TWRP?
Edit 1: Just tried to install twrp but inside "supersu" folder there is only "SuperSU-2.79-wear_systemless.zip", where can I find "TicwatchE_TWRP_keeper.zip"?
elios93 said:
Great to hear someone that it is working on this! What about Android Wear updates? Did you try if it is possible to install them using TWRP?
Edit 1: Just tried to install twrp but inside "supersu" folder there is only "SuperSU-2.79-wear_systemless.zip", where can I find "TicwatchE_TWRP_keeper.zip"?
Click to expand...
Click to collapse
I have the same problem...
EDIT: I have a Ticwatch S.
Niktendo said:
I have the same problem...
EDIT: I have a Ticwatch S.
Click to expand...
Click to collapse
I've managed to install it anyway. First check if it is not already installed using command
Code:
adb reboot recovery
If it does not work try this after you are in bootloader:
Code:
fastboot flash recovery TWRP_TicwatchE_v003.img
fastboot reboot
Then, as suggested by @Piereligio send this command as soon as possible while the watch is booting:
Code:
adb reboot recovery
This should work
However it is interesting that you have a S model. By sharing the build.prop of your device should be possible unlock all watchfaces for E model for instance!
elios93 said:
I've managed to install it anyway. First check if it is not already installed using command
Code:
adb reboot recovery
If it does not work try this after you are in bootloader:
Code:
fastboot flash recovery TWRP_TicwatchE_v003.img
fastboot reboot
Then, as suggested by @Piereligio send this command as soon as possible while the watch is booting:
Code:
adb reboot recovery
This should work
However it is interesting that you have a S model. By sharing the build.prop of your device should be possible unlock all watchfaces for E model for instance!
Click to expand...
Click to collapse
This is the best way i found to install the TWRP recovery:
- Unlock the boot loader
- Reboot, wait until android start again
- Reboot again in boot loader mode
- flash the twrp v003 recovery
- type:
Code:
fastboot oem reboot-recovery
- Flash the twrp keeper zip package
- flash the root zip package (if you want root)
EpicLPer said:
The guy who made it initially did send me a picture of it successfully rooted. Should work, errors can happen since TWRP can't write to all partitions yet.
Click to expand...
Click to collapse
Can you get me the device tree or at least BoardConfig.mk used for this? I have a working watch (still working on recovering the old one) and I think I can get the rest of the partitions working but I would really like to avoid any more mistakes.
Luxios said:
This is the best way i found to install the TWRP recovery:
- Unlock the boot loader
- Reboot, wait until android start again
- Reboot again in boot loader mode
- flash the twrp v003 recovery
- type:
Code:
fastboot oem reboot-recovery
- Flash the twrp keeper zip package
- flash the root zip package (if you want root)
Click to expand...
Click to collapse
That 'fastboot oem reboot-recovery' command sure is a nice find!
Hey, bought my ticwatch e used online.
The watch is almost new and everything works as it should, but it has these two developer orriented apps preinstalled and can’t be uninstalled via settings neither with a factory reset.
They dont do anything but i just want to remove them
https://photos.app.goo.gl/gTNg5QCPzBtKgnzy1
And yeah the watch also generates a bug report by itself everyday i also want to stop that lol
hassanabid94 said:
Hey, bought my ticwatch e used online.
The watch is almost new and everything works as it should, but it has these two developer orriented apps preinstalled and can’t be uninstalled via settings neither with a factory reset.
They dont do anything but i just want to remove them
https://photos.app.goo.gl/gTNg5QCPzBtKgnzy1
And yeah the watch also generates a bug report by itself everyday i also want to stop that lol
Click to expand...
Click to collapse
Maybe it's a specific developer unit. Don't do anything with it yet, we could loom further into this if it is something special.