Hi
my nexus 4 stuck on the google logo after updating to kit kat
i tried to flash stock room 4.3 but it is stop on the google logo
i tried to flash stock rooms 4.2.2 and 4.2.1 but the same thing is happen
importnat note:
1-I can not go into recovery mode (when choose recovery mode the phone stop on google logo)
2- I can go into bootloader
3- bootloader it unlocked
4-usb debugging is not enabled
please helpe me it is a challenge for me.
Sideload the ota update. Guide. Files. And make sure adb is properly configured on your pc.
arffrhn said:
Sideload the ota update. Guide. Files. And make sure adb is properly configured on your pc.
Click to expand...
Click to collapse
how i can check the adb configuration on my PC
hralzarwi said:
how i can check the adb configuration on my PC
Click to expand...
Click to collapse
If you don't know it then I assume you haven't have adb set up on your pc. No worries, look here for a step by step guide how to set it up.
Edit: How did you try to flash the 4.3 after a failed 4.4 ota update? Now that I see, if you can't enter recovery, then you can't sideload. Try and download wug's toolkits. Some said that it can work even if your device can't get pass the google screen.
arffrhn said:
If you don't know it then I assume you haven't have adb set up on your pc. No worries, look here for a step by step guide how to set it up.
Edit: How did you try to flash the 4.3 after a failed 4.4 ota update?
Click to expand...
Click to collapse
i did it using nexus 4 toolkit number 9 then 2 after in put the stock room in (put_factory_image_here) folder
also I used nexus root toolkit (flash stock + unroot)
hralzarwi said:
Hi
my nexus 4 stuck on the google logo after updating to kit kat
i tried to flash stock room 4.3 but it is stop on the google logo
i tried to flash stock rooms 4.2.2 and 4.2.1 but the same thing is happen
importnat note:
1-I can not go into recovery mode (when choose recovery mode the phone stop on google logo)
2- I can go into bootloader
3- bootloader it unlocked
4-usb debugging is not enabled
please helpe me it is a challenge for me.
Click to expand...
Click to collapse
Do you have any custom recovery installed?
Do you already tried flash using fastboot or ADB?
(You can use the Unified Android Toolkit and performer a full flash).
davidbranco said:
Do you have any custom recovery installed?
Do you already tried flash using fastboot or ADB?
(You can use the Unified Android Toolkit and performer a full flash).
Click to expand...
Click to collapse
thank you too much
no i do not have any custom recovery
yes i tried to flash more than one room using fastboot but nothing
i will search of unified android toolkit
thanks again
Maybe you should try lock your bootloader and than relock it again? Type in fastboot (when your phone is in bootloader mode) : fastboot oem lock, than fastboot oem unlock. It can help. Regards
Wysłane z mojego Nexus 4 przy użyciu Tapatalka
I used unified android toolkit to flash 4.2.2 but the device still not working it is stuck on google logo
any one can help me please
ProrokX said:
Maybe you should try lock your bootloader and than relock it again? Type in fastboot (when your phone is in bootloader mode) : fastboot oem lock, than fastboot oem unlock. It can help. Regards
Wysłane z mojego Nexus 4 przy użyciu Tapatalka
Click to expand...
Click to collapse
thank you
i did it but still the device is not working
hralzarwi said:
I used unified android toolkit to flash 4.2.2 but the device still not working it is stuck on google logo
any one can help me please
Click to expand...
Click to collapse
Are you sure the factory images got flashed properly? I once had this problem...but in my case adb doesn't work as the phone wasn't detected on pc. But luckily, recovery still works. You're stuck at Google screen because there is no system in your device. Maybe as a result of incomplete flash or broken system.img. Is your phone gets detected in adb? Plug in your phone. Open CMD in platform-tools and type in adb devices. See if your device serial number is listed as device in cmd.
Sent from my Nexus 4 using xda premium
hralzarwi said:
I used unified android toolkit to flash 4.2.2 but the device still not working it is stuck on google logo
any one can help me please
Click to expand...
Click to collapse
Try this.
1. Download a factory image from here. For my instructions, I'm using 4.4 KitKat, feel free to install previous versions of Android.
2. Extract it
3. Drill down into occam-krt16o (or whatever build you're using) Double check to make sure the folder name starts with "occam". That means it's the right image for the Nexus 4
4. Copy all of the contents of that folder, should be 6 files, into your platform-tools folder, where you are issuing adb commands from.
5. Once all 6 files are copied into your platform-tools folder (or wherever fastboot.exe is, really. Where you're issuing commands from.)
6. Boot into your bootloader (Turn phone off, hold power and Vol-, or just use 'adb reboot bootloader')
7. In the command prompt that you should have opened in the same folder as fastboot.exe and the 6 files from the factory image, type 'flash-all.bat'
8. Sit back and wait while it reformats and reflashes every partition on your phone.
9. Boot up and make sure it worked.
Let me know if that worked, or where you're getting hung up on and why and I'll try to walk you through this, step-by-step.
Johmama said:
Try this.
1. Download a factory image from here. For my instructions, I'm using 4.4 KitKat, feel free to install previous versions of Android.
2. Extract it
3. Drill down into occam-krt16o (or whatever build you're using) Double check to make sure the folder name starts with "occam". That means it's the right image for the Nexus 4
4. Copy all of the contents of that folder, should be 6 files, into your platform-tools folder, where you are issuing adb commands from.
5. Once all 6 files are copied into your platform-tools folder (or wherever fastboot.exe is, really. Where you're issuing commands from.)
6. Boot into your bootloader (Turn phone off, hold power and Vol-, or just use 'adb reboot bootloader')
7. In the command prompt that you should have opened in the same folder as fastboot.exe and the 6 files from the factory image, type 'flash-all.bat'
8. Sit back and wait while it reformats and reflashes every partition on your phone.
9. Boot up and make sure it worked.
Let me know if that worked, or where you're getting hung up on and why and I'll try to walk you through this, step-by-step.
Click to expand...
Click to collapse
I did it perfectly but i still have the same problem
but i find this and i do not know if it is an error or what?
{
"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"
}
my phone still stuck on google logo
thank you too much for your concern
arffrhn said:
Are you sure the factory images got flashed properly? I once had this problem...but in my case adb doesn't work as the phone wasn't detected on pc. But luckily, recovery still works. You're stuck at Google screen because there is no system in your device. Maybe as a result of incomplete flash or broken system.img. Is your phone gets detected in adb? Plug in your phone. Open CMD in platform-tools and type in adb devices. See if your device serial number is listed as device in cmd.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I think no , please see the message
hralzarwi said:
I did it perfectly but i still have the same problem
but i find this and i do not know if it is an error or what?
my phone still stuck on google logo
thank you too much for your concern
Click to expand...
Click to collapse
Well that is kind of weird, espeically considering you just got a bunch of 'OKAY' messages. Does a device come up if you type 'fastboot devices' while you're in the bootloader? If not, your drivers aren't quite installed correctly and this is an easier fix than what it could be. If so, then maybe try letting your phone sit at the Google logo. The initial start ups are usually long, maybe it just needs time.
If your device DOES come up in fastboot devices and you think you've given it enough time to start and it won't, then we might try to flash the images manually (even though it says they flashed successfully, which is annoying). Since you already have the factory image inside your platform-tools folder, try this:
1. Extract the image-occam-krt16o.zip into the platform-tools folder
2. You should now have, among other files, 6 .img files in your platform-tools folder Again, make sure those images are from an 'occam' image
3. Run these commands:
Code:
fastboot flash bootloader bootloader-mako-makoz20i.img
Code:
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash system system.img
Code:
fastboot flash userdata userdata.img
4. Once those are all done, try rebooting
This all might seem redundant, but this is a weird case and we're taking everything one step at a time. If you're still stuck, try updating your sdk and getting a newer fastboot.exe. If you have the sdk installed, just open SDK Manager.exe in the sdk\ folder
hralzarwi said:
I think no , please see the message
Click to expand...
Click to collapse
Well the CMD images you post earlier shows no issues when it flashes the factory images. That archive does contain bla bla bla is normal. Seems your device is not properly detected in adb. But the try this, when you are in fastboot type fastboot device. See if your device is listed.
Johmama said:
Well that is kind of weird, espeically considering you just got a bunch of 'OKAY' messages. Does a device come up if you type 'fastboot devices' while you're in the bootloader? If not, your drivers aren't quite installed correctly and this is an easier fix than what it could be. If so, then maybe try letting your phone sit at the Google logo. The initial start ups are usually long, maybe it just needs time.
If your device DOES come up in fastboot devices and you think you've given it enough time to start and it won't, then we might try to flash the images manually (even though it says they flashed successfully, which is annoying). Since you already have the factory image inside your platform-tools folder, try this:
1. Extract the image-occam-krt16o.zip into the platform-tools folder
2. You should now have, among other files, 6 .img files in your platform-tools folder Again, make sure those images are from an 'occam' image
3. Run these commands:
Code:
fastboot flash bootloader bootloader-mako-makoz20i.img
Code:
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash system system.img
Code:
fastboot flash userdata userdata.img
4. Once those are all done, try rebooting
This all might seem redundant, but this is a weird case and we're taking everything one step at a time. If you're still stuck, try updating your sdk and getting a newer fastboot.exe. If you have the sdk installed, just open SDK Manager.exe in the sdk\ folder
Click to expand...
Click to collapse
woooooooooooooooooooow you are great man
after I give him a time but it is very long time about 5 hours my device is work probably but when I restart it it is stuck on goggle logo
LOOOOOOOOOOOOOOOOOOOOOOL
what do you think why it is stuck now?
arffrhn said:
Well the CMD images you post earlier shows no issues when it flashes the factory images. That archive does contain bla bla bla is normal. Seems your device is not properly detected in adb. But the try this, when you are in fastboot type fastboot device. See if your device is listed.
Click to expand...
Click to collapse
MR.arffrhn
thank you too much for your help and what do you think now why it is stuck ?
hralzarwi said:
MR.arffrhn
thank you too much for your help and what do you think now why it is stuck ?
Click to expand...
Click to collapse
So your device is working now? Well there are many that complained that their device got stuck in google screen after upgrading to 4.4. And the solution to that is a simple factory reset. If you can boot into system and still stuck on google screen, you can try this. http://forum.xda-developers.com/showpost.php?p=47846788&postcount=2
Well I'm confused as ****.
Tried to install 4.4. Failed. Was stuck on google circles. Fast forward , I gave up and tried to install 4.3.
....google logo for like 5 minutes. Then the "X" goes on forever.....
bootloader,rooted,etc,etc. Running PA 4.2 before this. Now all I want is a working phone lol.
google factory images ofc
---------- Post added at 01:17 AM ---------- Previous post was at 12:53 AM ----------
arffrhn said:
So your device is working now? Well there are many that complained that their device got stuck in google screen after upgrading to 4.4. And the solution to that is a simple factory reset. If you can boot into system and still stuck on google screen, you can try this. http://forum.xda-developers.com/showpost.php?p=47846788&postcount=2
Click to expand...
Click to collapse
no /system and /cache, can't sideload.... didn't apply that .zip update though?
After redoing it all with the .zip update.. no cache... TWRP still can't sideload.
android can be such a nightmare sometimes. I should have been done like 6 hours ago. Luckily, just a few minutes ago, I found this:
http://forum.xda-developers.com/showpost.php?p=44322165&postcount=30
And found that locking, then unlocking the bootloader FIXED THE PROBLEM!!!!
I hate android so much after this. I'll probably forget all about it like last time (lololol)
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
Was able to wipe OS on my phone, now only ZUK Recovery menu is available. Boot stops showing white ZUK logo on screen.
ADB does not recognize the device.
Is it totally bricked now? or does there exist a solution?
I think you can still flash a factory image with the recovery, but I don't know how. By the way, how do you acces the fasboot menu ? Because I think it is still present on my bricked Z1 but I tried nearly every button combination to acces it, but never succeed...
I get to the ZUK Recovery menu by holding down both volume + and - for 10 sec at the moment phone vibrates at startup.
Hopefully there is a way to flash a recovery image. In the ZUK recovery menu there is an option to install update.zip, but I can't find a way to push the file to the device.
nordream said:
I get to the ZUK Recovery menu by holding down both volume + and - for 10 sec at the moment phone vibrates at startup.
Hopefully there is a way to flash a recovery image. In the ZUK recovery menu there is an option to install update.zip, but I can't find a way to push the file to the device.
Click to expand...
Click to collapse
Download qpst and the zui rom file and flash it and you should be good to go
qpst
https://mega.nz/#!4tom3DqL!4a-rRcLef1yS6HJSrBfne_-r9atg6yF3kI_HW8lDaPY
password: bbs.zuk.cn
zui rom file
https://mega.nz/#!chQkEAwR!IHeYRxWx38QdML6VxjPdVz08BgbZD-Z-xVuSG150qPU
Z1 usb driver (can be troublesome if doing this in windows 10 so try and use a win7 machine)
https://mega.nz/#!l8pVHIpT!UkcW3Jg4B7YilDjZatvLqGBi_R4vVUYVdkrsUL_Ve9k
If you dont know how to flash then ill try and guide you
After you installed qpst, you will get a bunch of programs, start QFIL from the qpst folder
Click browse on the programmer path row and select "prog_emmc_firehose_8974.mbn" and then click browse on the search path row and select the xml file + the other patch file which comes after it.
When thats done, make sure phone is off and then hold vol+ while you are inserting usb cable into phone and QFIL should then detect phone, you may need to select port and be quick with it, took me a few tries before I got it right so just take out the cable and turn off and try again if you fail to make them connect.
Not only you need to select comport, you also need to press the download button aswell as soon as possible or else phone will continue booting as normal
If everything went alrite then you soon got ZUI flashed on your phone and can install recovery etc
Good luck!
tndb said:
Download qpst and the zui rom file and flash it and you should be good to go
qpst
https://mega.nz/#!4tom3DqL!4a-rRcLef1yS6HJSrBfne_-r9atg6yF3kI_HW8lDaPY
zui rom file
uploading, will update as soon as the file is done
Z1 usb driver (can be troublesome if doing this in windows 10 so try and use a win7 machine)
https://mega.nz/#!l8pVHIpT!UkcW3Jg4B7YilDjZatvLqGBi_R4vVUYVdkrsUL_Ve9k
If you dont know how to flash then ill try and guide you
After you installed qpst, you will get a bunch of programs, start QFIL from the qpst folder
Click browse on the programmer path row and select "prog_emmc_firehose_8974.mbn" and then click browse on the search path row and select the xml file + the other patch file which comes after it.
When thats done, make sure phone is off and then hold vol+ while you are inserting usb cable into phone and QFIL should then detect phone, you may need to select port and be quick with it, took me a few tries before I got it right so just take out the cable and turn off and try again if you fail to make them connect.
Not only you need to select comport, you also need to press the download button aswell as soon as possible or else phone will continue booting as normal
If everything went alrite then you soon got ZUI flashed on your phone and can install recovery etc
Good luck!
Click to expand...
Click to collapse
Thanks very much for this guidance and files, so this will be a serial communucation, and I will not need the MTP USB to work? I have trouble with that driver, tried two windows 7 computers without luck.
I will try asap, phone is a christmas present so I'm in a kind off hurry. Plan was to flash ZUI to CM12.1...
nordream said:
Thanks very much for this guidance and files, so this will be a serial communucation, and I will not need the MTP USB to work? I have trouble with that driver, tried two windows 7 computers without luck.
I will try asap, phone is a christmas present so I'm in a kind off hurry. Plan was to flash ZUI to CM12.1...
Click to expand...
Click to collapse
Nah no need for MTP
As soon as you got zui into phone, you can convert back to cyanogen if you prefer that one. Look at modacos guide for example http://www.modaco.com/forums/topic/375804-convert-z1-from-zukui-to-cyanogen-os/
When you got zui loaded onto phone again, its in chinese. On the first screen you are met with just press the button in the bottom (on screen), then press cogwheel (which is the settings), scroll down to yet another cogwheel in here which should be below a lock icon, then press second option in here and then the top option to change language to english incase you cant make out the chinese
tndb said:
Nah no need for MTP
As soon as you got zui into phone, you can convert back to cyanogen if you prefer that one. Look at modacos guide for example http://www.modaco.com/forums/topic/375804-convert-z1-from-zukui-to-cyanogen-os/
Click to expand...
Click to collapse
Christmas is saved ! I'm back in business Thanks to tndb !
But last problem is to flash to CM. These steps below are unclear for me, tried "Wipe Data" and then "install using adb" but the sideload command fails with error "no device"
Select the option to wipe the device (important!)
Select the install update / from USB option
Type 'adb sideload z1.cyanogen.convert.signed.zip'
There are several Wipe options data or partitions?
Don't get any update / from USB option in the recovery menu. Only install using adb, but it fails
nordream said:
Christmas is saved ! I'm back in business Thanks to tndb !
But last problem is to flash to CM. These steps below are unclear for me, tried "Wipe Data" and then "install using adb" but the sideload command fails with error "no device"
Select the option to wipe the device (important!)
Select the install update / from USB option
Type 'adb sideload z1.cyanogen.convert.signed.zip'
There are several Wipe options data or partitions?
Don't get any update / from USB option in the recovery menu. Only install using adb, but it fails
Click to expand...
Click to collapse
Not sure where you got stuck?
If you already are as far as in cyanogen recovery, then its prob that your phone isnt detected in device manager as it may be detected as yet another device. Install driver again and then run the "adb sideload z1.cyanogen.convert.signed.zip" command (make sure the zip is in the same folder as your adb working folder)
otherwise read below
Did you manage to get into bootloader mode by typing "adb reboot bootloader"?
If you are already in bootloader mode, have you checked device manager if phone is detected here?
Have you made sure bootloader is unlocked aswell? Check with "fastboot -i 0x2b4c oem device-info" and if its still locked then type "fastboot -i 0x2b4c oem unlock"
and then "fastboot -i 0x2b4c boot z1.recovery.testkeys.img" to load cyanogen recovery.
Let me know if you still cant get it working, if you got google hangouts just pm me with details and ill help you from there
tndb said:
Not sure where you got stuck?
If you already are as far as in cyanogen recovery, then its prob that your phone isnt detected in device manager as it may be detected as yet another device. Install driver again and then run the "adb sideload z1.cyanogen.convert.signed.zip" command (make sure the zip is in the same folder as your adb working folder)
Click to expand...
Click to collapse
Thanks tndb, you put me in the right direction again, did a "adb kill-server" before adb sideload command and voila the sideload command connected and soon I'm ready to wrap the christmas present.
Merry Christmas ! and thanks
nordream said:
Thanks tndb, you put me in the right direction again, did a "adb kill-server" before adb sideload command and voila the sideload command connected and soon I'm ready to wrap the christmas present.
Merry Christmas ! and thanks
Click to expand...
Click to collapse
Aaah awesome!
Merry xmas to you too and have a happy new year!
hi
I have the same problem. When i try to falsh, by pressing download, i get this error:
Download Fail:Switch To EDL FailSystem.Exception: FireHose Fail
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
at QFIL.Tech.DownloadTech.SwitchToEDL()
Finish Download
Any thoughts?
How can i flash anything? i can acces fastboot, recovery menu.
nordream said:
I get to the ZUK Recovery menu by holding down both volume + and - for 10 sec at the moment phone vibrates at startup.
Hopefully there is a way to flash a recovery image. In the ZUK recovery menu there is an option to install update.zip, but I can't find a way to push the file to the device.
Click to expand...
Click to collapse
if you find a way, please tell me, i m in the same boat
Extentho said:
I have the same problem. When i try to falsh, by pressing download, i get this error:
Download Fail:Switch To EDL FailSystem.Exception: FireHose Fail
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
at QFIL.Tech.DownloadTech.SwitchToEDL()
Finish Download
Any thoughts?
How can i flash anything? i can acces fastboot, recovery menu.
Click to expand...
Click to collapse
If you can boot in fasboot mode and you are able to connect to your device from your pc you can just download the fastboot flashable stock image from Cyanogen Inc. Unzip it and flash it with fastboot. There are a a lot of guides how to do that on xda.
Planet X said:
If you can boot in favor mode and you are able to connect to your device from your pc you can just download the fastboot flashable stock image from Canon Inc. Unzip it and flash it with fastboot. There are a a lot of guides how to do that on xda.
Click to expand...
Click to collapse
Can you give me some links please? thank you very much. Qufil seems not to work for me. What is Canon inc, and where i can donwload the fastboot flashable stock image for lenovo zuk z1? And most important, how do i do that?
Extentho said:
Can you give me some links please? thank you very much. Qufil seems not to work for me. What is Canon inc, and where i can donwload the fastboot flashable stock image for lenovo zuk z1? And most important, how do i do that?
Click to expand...
Click to collapse
Download the fast signed image of COS 12.1 here http://builds.cyngn.com/factory/ham/...d-fastboot.zip
Unzip it
Open cmd or terminal
Go to the unzipped folder
Execute this step by step:
fastboot -i 0x2b4c flash aboot emmc_appsboot.mbn
fastboot -i 0x2b4c flash modem NON-HLOS.bin
fastboot -i 0x2b4c flash rpm rpm.mbn
fastboot -i 0x2b4c flash sbl1 sbl1.mbn
fastboot -i 0x2b4c flash dbi sdi.mbn
fastboot -i 0x2b4c flash splash splash.img
fastboot -i 0x2b4c flash tz tz.mbn
fastboot -i 0x2b4c flash persist persist.img
This will restore your bootloader to stock Cyanogen OS. It will remain unlocked. You can add cache.img, system.img and userdata yourself I guess. Otherwise Google for flash fastboot nexus. That should give you an idea how to flash with fastboot.
Planet X said:
Download the fast signed image of COS 12.1 here http://builds.cyngn.com/factory/ham/...d-fastboot.zip
Unzip it
Open cmd or terminal
Go to the unzipped folder
Execute this step by step:
fastboot -i 0x2b4c flash aboot emmc_appsboot.mbn
fastboot -i 0x2b4c flash modem NON-HLOS.bin
fastboot -i 0x2b4c flash rpm rpm.mbn
fastboot -i 0x2b4c flash sbl1 sbl1.mbn
fastboot -i 0x2b4c flash dbi sdi.mbn
fastboot -i 0x2b4c flash splash splash.img
fastboot -i 0x2b4c flash tz tz.mbn
fastboot -i 0x2b4c flash persist persist.img
This will restore your bootloader to stock Cyanogen OS. It will remain unlocked. You can add cache.img, system.img and userdata yourself I guess. Otherwise Google for flash fastboot nexus. That should give you an idea how to flash with fastboot.
Click to expand...
Click to collapse
Tried the first command and i got 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"
}
I think the computer doesn t see the phone, because when i try command adb reboot bootloader in cmd i get device not found.
I have in installed the universal adb driver for android, but still doesn t work.
Extentho said:
Tried the first command and i got this:
I think the computer doesn t see the phone, because when i try command adb reboot bootloader in cmd i get device not found.
I have in installed the universal adb driver for android, but still doesn t work.
Click to expand...
Click to collapse
You have had an answer from the phone. So there was a connection. You can always test beforehand with the command fastboot -i 0x4b2c devices. It should then let you see the serial number of your phone.
But your answer was device is locked. That means you still have an locked bootloader. For to be able to use adb you have to add 0x4b2c to your usb_adb.ini file. Please look a bit more to the solutions that already have been given in the other threads. To unlock your bootloader you need to use the toolkit. You will find that in the development thread. The toolkit: http://forum.xda-developers.com/zuk-z1/development/win-zuk-z1-toolkit-0-1-alpha-t3235964
You will than have the possibility to flash a TWRP recovery too. With that you could also just flash the full rom as a zip.
Planet X said:
You have had an answer from the phone. So there was a connection. You can always test beforehand with the command fastboot -i 0x4b2c devices. It should then let you see the serial number of your phone.
But your answer was device is locked. That means you still have an locked bootloader. For to be able to use adb you have to add 0x4b2c to your usb_adb.ini file. Please look a bit more to the solutions that already have been given in the other threads. To unlock your bootloader you need to use the toolkit. You will find that in the development thread. The toolkit: http://forum.xda-developers.com/zuk-z1/development/win-zuk-z1-toolkit-0-1-alpha-t3235964
You will than have the possibility to flash a TWRP recovery too. With that you could also just flash the full rom as a zip.
Click to expand...
Click to collapse
I have played a while with this tool, and now the phone boots only into zuk logo(not the cyanogen anymore), also now i have access only to recovery and fastboot. Think i ve messed it up. Tried to sideload the stock rom and worked up to 47% with this tool, then gave me error on the phone. So, there is a working connection between phone and pc but i don t know what i can do. However i can t unlock the bootloader , when i try, it shows press any key and nothing happens. When i check the devices connected to the pc in adb tool, it shows me nothing. The only connection i was able to put up, was only sideload update.
None of the other commands is working. I can t install twrp recovery, i can, t unlock bootloader. I can t do anything.
I was able to use some fastboot commands in fastboot mode however. I managed to reboot phone in android using command in zuk tool from pc. When tried to flash stock rom in fastboot with the command from the tool, i got the same error : DEVICE IS LOCKED . CANNOT FLASH IMAGES
Extentho said:
I have played a while with this tool, and now the phone boots only into zuk logo(not the cyanogen anymore), also now i have access only to recovery and fastboot. Think i ve messed it up. Tried to sideload the stock rom and worked up to 47% with this tool, then gave me error on the phone. So, there is a working connection between phone and pc but i don t know what i can do. However i can t unlock the bootloader , when i try, it shows press any key and nothing happens. When i check the devices connected to the pc in adb tool, it shows me nothing. The only connection i was able to put up, was only sideload update.
None of the other commands is working. I can t install twrp recovery, i can, t unlock bootloader. I can t do anything.
I was able to use some fastboot commands in fastboot mode however. I managed to reboot phone in android using command in zuk tool from pc.
Click to expand...
Click to collapse
Thank you for the information. You should be able to flash the stock Cyanogen recovery with fastboot. Than you could do a factory reset in that recovery. That's all you need to have a working phone again. But with that recovery you could also flash the signed zip from Cyanogen.
Planet X said:
Thank you for the information. You should be able to flash the stock Cyanogen recovery with fastboot. Than you could do a factory reset in that recovery. That's all you need to have a working phone again. But with that recovery you could also flash the signed zip from Cyanogen.
Click to expand...
Click to collapse
I CANNOT flash the stock rom using fastboot. I have tried, many times. Also, the USB debugging was not activate befor the bricking. The only option i can use to flash something seems to be sideload. Also, where can i find the stock recovery?? I acces the fastboot mode from stock recovery. Isn t this enough?
That is what i recieve when i try to install a recovery using the tool. I can wait all day long.
Also, wehn i try to use the command [FASTBOOT]REBOOT INTO ANY CUSTOM RECOVERY WITHOU INSTALL i recieve this:
When i use the command [FASTBOOT] REFLASH THE STOCK USING MANUALLY DOWNLOADED FACTORY IMAGE i get this. (i donwloaded the official signed fastboot rom and followed the instructions)
And that is what i get when i try to sideload the cm signed rom with the [ADB]SIDELOAD A ZIP FILE command
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.
My phone been stuck at Asus logo..i had been to customer care , they said its motherboard issue so my mobile according to them cannot be done anything to make it right. I searhed in the forum. Some people had faced the same problem as me. I tried to follow the been mentioned but of no use.
So please anybond kindly help me out to deal with the problem.
I already tried flashing the firmware on my own but it was not successfull due to E failed to mount....nothing works like factory reset or clear partition cache.. right now i can access to recovery mode
Please help me..
can you go to fastboot? (turn off phone, hold ON button and volume +)
dkm91 said:
My phone been stuck at Asus logo..i had been to customer care , they said its motherboard issue so my mobile according to them cannot be done anything to make it right. I searhed in the forum. Some people had faced the same problem as me. I tried to follow the been mentioned but of no use.
So please anybond kindly help me out to deal with the problem.
I already tried flashing the firmware on my own but it was not successfull due to E failed to mount....nothing works like factory reset or clear partition cache.. right now i can access to recovery mode
Please help me..
Click to expand...
Click to collapse
What firmware? Lollipop?
If you using lollipop, first you must flash recovery from kitkat.
Then flash again rom lollipop via adb
Sent from my Asus Zenfone 5 using XDA Labs
ekifakhruddin said:
What firmware? Lollipop?
If you using lollipop, first you must flash recovery from kitkat.
Then flash again rom lollipop via adb
Sent from my Asus Zenfone 5 using XDA Labs
Click to expand...
Click to collapse
I can go to fastboot and recovery mode too. I also tried to flash lollipop .87 kitkat .54 .540 .44 and also jelly bean 1.17.40.16 raw and zip both...non works..
Actually whenever I flash the kitkat recovery via cmd it says its done but when restart to bootloarder it stay still in lollipop recovery. I mean it is not possible to revert the recovery mode of kit Kat from lollipop though it is saying okay.
Again I tried to flash twrp ZenFone 5 that's also not happening coz again the bootloarder is still in lollipop recovery only.. not going back to twrp or kitkat recovery or even the lollipop firmware it is not able to flash..
While flashing raw firmware through flashtool it says unknown oem command.
While flashing through adb sideload it says ref :0.00x error something ...
What I should do now ??
ekifakhruddin said:
What firmware? Lollipop?
If you using lollipop, first you must flash recovery from kitkat.
Then flash again rom lollipop via adb
Sent from my Asus Zenfone 5 using XDA Labs
Click to expand...
Click to collapse
whether my phone has been bricked?
dkm91 said:
I can go to fastboot and recovery mode too. I also tried to flash lollipop .87 kitkat .54 .540 .44 and also jelly bean 1.17.40.16 raw and zip both...non works..
Actually whenever I flash the kitkat recovery via cmd it says its done but when restart to bootloarder it stay still in lollipop recovery. I mean it is not possible to revert the recovery mode of kit Kat from lollipop though it is saying okay.
Again I tried to flash twrp ZenFone 5 that's also not happening coz again the bootloarder is still in lollipop recovery only.. not going back to twrp or kitkat recovery or even the lollipop firmware it is not able to flash..
While flashing raw firmware through flashtool it says unknown oem command.
While flashing through adb sideload it says ref :0.00x error something ...
What I should do now ??
Click to expand...
Click to collapse
dkm91 said:
whether my phone has been bricked?
Click to expand...
Click to collapse
Can you sent screenshot here?
Because i never found this problem.
Sent from my Asus Zenfone 5 using XDA Labs
{
"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"
}
ekifakhruddin said:
Can you sent screenshot here?
Because i never found this problem.
Sent from my Asus Zenfone 5 using XDA Labs
Click to expand...
Click to collapse
ekifakhruddin said:
Can you sent screenshot here?
Because i never found this problem.
Sent from my Asus Zenfone 5 using XDA Labs
Click to expand...
Click to collapse
https://www.asus.com/zentalk/in/forum.php?mod=viewthread&tid=126829&extra=page=1&mobile=2
https://www.asus.com/zentalk/in/forum.php?mod=viewthread&tid=126829&extra=page=1&mobile=2
dkm91 said:
https://www.asus.com/zentalk/in/forum.php?mod=viewthread&tid=126829&extra=page=1&mobile=2
https://www.asus.com/zentalk/in/forum.php?mod=viewthread&tid=126829&extra=page=1&mobile=2
Click to expand...
Click to collapse
What you already flash recovery from latest kitkat ?
Try this one bro.
https://forum.xda-developers.com/zenfone-5/help/bootlooped-bricked-returning-to-stock-t3358662
ekifakhruddin said:
What you already flash recovery from latest kitkat ?
Try this one bro.
https://forum.xda-developers.com/zenfone-5/help/bootlooped-bricked-returning-to-stock-t3358662
Click to expand...
Click to collapse
i think my bootloader has been unlocked and now its not locking anymore...
as my bootloader has been showhing IFWI version is 59.41.
(according to https://forum.xda-developers.com/zenfone-5/help/how-to-bootloader-lock-unlock-zf5-t3365542)
when i am trying to lock it its say its done but not locking after reboot.
dkm91 said:
i think my bootloader has been unlocked and now its not locking anymore...
as my bootloader has been showhing IFWI version is 59.41.
(according to https://forum.xda-developers.com/zenfone-5/help/how-to-bootloader-lock-unlock-zf5-t3365542)
when i am trying to lock it its say its done but not locking after reboot.
Click to expand...
Click to collapse
Dont worry about relocking your bootloader.
Nothing is wrong with an unlocked bootloader.
However the error : E/Failed to mount did you get that while sideloading your Stock Firmware ??Or while booting into recovery ??
DroidNoob123 said:
Dont worry about relocking your bootloader.
Nothing is wrong with an unlocked bootloader.
However the error : E/Failed to mount did you get that while sideloading your Stock Firmware ??Or while booting into recovery ??
Click to expand...
Click to collapse
it is while flashing the firmware ..any version from jb to kitkat to lollipop. Normally I can go to to recovery mode and bootloarder. Even I tried to flash the kit Kat recovery but it is not reverting back.
Even while going to rerecovery mode there is no issue but below the recovery mode options that E failed to mount is showing.
The key rule is having PATIENCE.
My guess would be that you tried force rebooting your phone during the sideload process and hence there is a problem in mounting cache(Did You ?).
I hope that you have you have Intel Android Drv and Minimal ADB and Fastboot, If not get them.
Step 1: Download the stock firmware for your model(https://www.asus.com/support/Download/39/1/0/2/96nqlxHp1VKV4Rdz/32/)
Step 2: Its preferred that you paste this file in the C drive where your Minimal ADB and Fastboot is.
Step 3: Open the zip and extract two files fastboot.img and recovery.img in the same location as the zip file.Close the zip file now.
Step 4: Run Minimal ADB and Fastboot now.Connect your phone to the PC and enter fastboot.
To check if your phone is connected or not,enter in cmd
Code:
fastboot devices
a unique value will be returned.You are set now to install your firmware.
Please be patient through the upcoming steps,because these steps can take long to finish.
Step 5: Enter this command in cmd prompt.
Code:
fastboot flash fastboot fastboot.img
(30 Seconds Max)
Step 6: Enter this command in cmd prompt.
Code:
fastboot reboot-bootloader
(30 Seconds Max)
Step 7: Enter this command in cmd prompt.
Code:
fastboot flash recovery recovery.img
(30 Seconds Max)
Step 8: Enter Recovery now.Press Vol+ and Vol- buttons together, hold and release the Vol+ button first followed by Vol-.
A set of options should come up(if not, retry) with adb sideload among them.Select adb sideload.
Step 9: Enter this command in cmd prompt.
Code:
adb sideload <firmwarename.zip>
(This is a very long process.Clearing Old Dictionaries being the longest 15 mins approx.)Dont disconnect your phone, just let it go on.
Step 10: Factory Reset and clear Cache.Dont worry about unlocked bootloader it will automatically be locked.
Step 11: Reboot.
This should definitely help.
Thank me if this works.
If it doesnt, inform me i'll try to help. :highfive:
DroidNoob123 said:
The key rule is having PATIENCE.
My guess would be that you tried force rebooting your phone during the sideload process and hence there is a problem in mounting cache(Did You ?).
I hope that you have you have Intel Android Drv and Minimal ADB and Fastboot, If not get them.
Step 1: Download the stock firmware for your model(https://www.asus.com/support/Download/39/1/0/2/96nqlxHp1VKV4Rdz/32/)
Step 2: Its preferred that you paste this file in the C drive where your Minimal ADB and Fastboot is.
Step 3: Open the zip and extract two files fastboot.img and recovery.img in the same location as the zip file.Close the zip file now.
Step 4: Run Minimal ADB and Fastboot now.Connect your phone to the PC and enter fastboot.
To check if your phone is connected or not,enter in cmd
Code:
fastboot devices
a unique value will be returned.You are set now to install your firmware.
Please be patient through the upcoming steps,because these steps can take long to finish.
Step 5: Enter this command in cmd prompt.
Code:
fastboot flash fastboot fastboot.img
(30 Seconds Max)
Step 6: Enter this command in cmd prompt.
Code:
fastboot reboot-bootloader
(30 Seconds Max)
Step 7: Enter this command in cmd prompt.
Code:
fastboot flash recovery recovery.img
(30 Seconds Max)
Step 8: Enter Recovery now.Press Vol+ and Vol- buttons together, hold and release the Vol+ button first followed by Vol-.
A set of options should come up(if not, retry) with adb sideload among them.Select adb sideload.
Step 9: Enter this command in cmd prompt.
Code:
adb sideload <firmwarename.zip>
(This is a very long process.Clearing Old Dictionaries being the longest 15 mins approx.)Dont disconnect your phone, just let it go on.
Step 10: Factory Reset and clear Cache.Dont worry about unlocked bootloader it will automatically be locked.
Step 11: Reboot.
This should definitely help.
Thank me if this works.
If it doesnt, inform me i'll try to help. :highfive:
Click to expand...
Click to collapse
i tried steps mentioned by you. but not happening. its showing some error Total xfer: 0.00x in cmd window and in mobile it is showing same E:failed to mount /cache
dkm91 said:
i tried steps mentioned by you. but not happening. its showing some error Total xfer: 0.00x in cmd window and in mobile it is showing same E:failed to mount /cache
Click to expand...
Click to collapse
Can you please upload a screenshot ?I cant work with incomplete data input.
You didnt even bother mentioning Total xfer:0.00x.
Does it show No OS ??
If so then there is a mismatch between the firmware and recovery.
DroidNoob123 said:
Can you please upload a screenshot ?I cant work with incomplete data input.
You didnt even bother mentioning Total xfer:0.00x.
Does it show No OS ??
If so then there is a mismatch between the firmware and recovery.
Click to expand...
Click to collapse
I had given a link of screen shot at the beginning of thread. If you want anymore then do tell me I 'll post it once again. Its does not say anything like NO OS... Only those errors are coming. I don't know whether it has some OS or not. But I got the error I posted to you. Yeah there may be mismatch if u r saying as that too I have no knowledge about..so what is way forward..what need to be done? Or if u want more information then tell me I 'll try to give you..
And thank you so much for helping me..
dkm91 said:
I had given a link of screen shot at the beginning of thread. If you want anymore then do tell me I 'll post it once again. Its does not say anything like NO OS... Only those errors are coming. I don't know whether it has some OS or not. But I got the error I posted to you. Yeah there may be mismatch if u r saying as that too I have no knowledge about..so what is way forward..what need to be done? Or if u want more information then tell me I 'll try to give you..
And thank you so much for helping me..
Click to expand...
Click to collapse
I see that you are trying to restore the lolipop firmware.
Hv you tried the Kitkat firmware(V2.22.40.540 (Kitkat) for WW SKU) ?
DroidNoob123 said:
I see that you are trying to restore the lolipop firmware.
Hv you tried the Kitkat firmware(V2.22.40.540 (Kitkat) for WW SKU) ?
Click to expand...
Click to collapse
yeah I tried both kitkat (v .540 v .54 and other versions also) and jb (v .16) but none worked. Actually while flashing recovery.img of either kitkat or jb it is showing done in the mobile and cmd window but after rebooting it again reboot to lollipop boot loader ,,, doesn't boot to kit Kat or jb bootloader...
DroidNoob123 said:
The key rule is having PATIENCE.
My guess would be that you tried force rebooting your phone during the sideload process and hence there is a problem in mounting cache(Did You ?).
I hope that you have you have Intel Android Drv and Minimal ADB and Fastboot, If not get them.
Step 1: Download the stock firmware for your model(https://www.asus.com/support/Download/39/1/0/2/96nqlxHp1VKV4Rdz/32/)
Step 2: Its preferred that you paste this file in the C drive where your Minimal ADB and Fastboot is.
Step 3: Open the zip and extract two files fastboot.img and recovery.img in the same location as the zip file.Close the zip file now.
Step 4: Run Minimal ADB and Fastboot now.Connect your phone to the PC and enter fastboot.
To check if your phone is connected or not,enter in cmd
Code:
fastboot devices
a unique value will be returned.You are set now to install your firmware.
Please be patient through the upcoming steps,because these steps can take long to finish.
Step 5: Enter this command in cmd prompt.
Code:
fastboot flash fastboot fastboot.img
(30 Seconds Max)
Step 6: Enter this command in cmd prompt.
Code:
fastboot reboot-bootloader
(30 Seconds Max)
Step 7: Enter this command in cmd prompt.
Code:
fastboot flash recovery recovery.img
(30 Seconds Max)
Step 8: Enter Recovery now.Press Vol+ and Vol- buttons together, hold and release the Vol+ button first followed by Vol-.
A set of options should come up(if not, retry) with adb sideload among them.Select adb sideload.
Step 9: Enter this command in cmd prompt.
Code:
adb sideload <firmwarename.zip>
(This is a very long process.Clearing Old Dictionaries being the longest 15 mins approx.)Dont disconnect your phone, just let it go on.
Step 10: Factory Reset and clear Cache.Dont worry about unlocked bootloader it will automatically be locked.
Step 11: Reboot.
This should definitely help.
Thank me if this works.
If it doesnt, inform me i'll try to help. :highfive:
Click to expand...
Click to collapse
dkm91 said:
yeah I tried both kitkat (v .540 v .54 and other versions also) and jb (v .16) but none worked. Actually while flashing recovery.img of either kitkat or jb it is showing done in the mobile and cmd window but after rebooting it again reboot to lollipop boot loader ,,, doesn't boot to kit Kat or jb bootloader...
Click to expand...
Click to collapse
In step 5,u r changing the fastboot(bootloader) too.
Dont reboot after flashing recovery.img go straight into recovery.
DroidNoob123 said:
In step 5,u r changing the fastboot(bootloader) too.
Dont reboot after flashing recovery.img go straight into recovery.
Click to expand...
Click to collapse
its not done..again same error ...in cmd window error total xfer: 0.00x and in mob E failed to mount cache.....
actually the step 8 of holding both volume key is also not working to go to recovery mode. i can only go recovery mode after holding power+volume up button from the android symbol...
{
"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.