Develop Bugs

[Q] Need Assistance, I brick my Galaxy Nexus

Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!

So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?

cbs2002 said:
Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!
Click to expand...
Click to collapse
The key piece of information for your symptom is in this line:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
The other lines do help provide background as to the other modes such as recovery and download working properly, which indicates the issue is not *serious*.
The symptom you state, where the device does not boot past the boot logo, usually means the device is not able to boot the kernel or boot past the kernel. The boot logo appears while the kernel is being loaded on the device. Generally, after the boot logo and kernel finish loading a boot animation appears which indicates the kernel has usually handed off to the Android OS to continue booting.
My approach would be to load a completely stock ROM in order to restore a working kernel and ROM to the device. I generally perform this step as a baseline to get everything back in working order.
In many instances the ROM is dependent on the kernel. Your situation requires at least a kernel to be loaded and in order to prevent any further issues, it would be best to load a ROM dependent on the kernel being loaded.
A simple way would be to grab the stock factory images from Google's site and load those back onto the device.
Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode.
Hope that helps!

Since you're rooted I'm going to assume you have ADB and the necessary drivers installed.
1.) Download a ROM. It doesn't have to be stock, you can choose any of the ROMs from the development section for your device. Most of the ROMs are packaged with a kernel already.
2.) Save this ROM file to the same folder where you have ADB installed.
3.) Boot your phone into CWM recovery and plug it into your computer.
4.) Use ADB to push the ROM zip file to your phone (/data/media). For example:
Code:
c:\gnex\>adb push rom.zip /data/media/rom.zip
5.) Use CWM to wipe data, cache, and davlik-cache
6.) Install zip from sdcard and flash the rom.zip.

RMarkwald said:
So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?
Click to expand...
Click to collapse
1. I am using GSM
2. Whenever I turn on my mobile, the 'Google' and 'Unlock' logo appears and then freeze, with no more respond at all
* I definitely mess up some system files, but don't know how to restore it because my PC do not recognize my mobile.
Thanks

I am seeing more and more of these threads about "bricked" nexus's is this an issue with how new the phone is or people not following instructions properly as they are too eager to root their phones?
All else fails flash back to stock and count yourself lucky.

To silow,
Thanks for your advice, but fail
1. I put adb.exe, adbwinapi.dll and fastboot.exe (3 files) under my PC C drive (i.e. C
2. I also put a stock Rom (rename as rom.zip) under C drive (i.e. C
3. Boot phone into CWM recovery and plug it into computer.
4. Use cmd command and type c:\gnex\>adb push rom.zip /data/media/rom.zip
5. It fails , It say "Access Denied" (in Chinese, but I translate it into English here)
6. How do I use ADB (it is a ADB.exe file, When I double click it, it only flash up a few page very fast and nothing happen)
Please assist!

To Joeykrim,
I agree that
"Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode."
But how? (according to my symptoms)

The command I gave you was just an example. I didn't spell out the exact details because I thought that you would know how to do it considering you rooted the phone.
If you put the adb.exe and AdbWinApi.dll file in your C: drive, make sure you copy the ROM file to your C: drive too. In the follow example I'm going to use "ROM.zip" but use the name of the ROM file that you downloaded. Also I am assuming you are on Windows XP.
1.) Boot your phone into CWM recovery and then plug it in.
2.) Go to your Start Menu and choose Run. Then type in "cmd" without quotes and hit enter to open a command prompt.
3.) Enter:
Code:
cd c:\
4.) Enter the following to make sure ADB can see your phone:
Code:
adb devices
You should see something similiar to this to confirm ADB can see your device:
List of devices attached
019B756F0C018012 device
5.) Enter the following command to copy the ROM file to your phone. Remember to replace ROM.zip with whatever the name of the ROM file is:
Code:
adb push ROM.zip /data/media/ROM.zip
6.) Use CWM to wipe data, cache, and davlik-cache
7.) Install zip from sdcard and flash the rom.zip.

To Silow,
You have been very helpful, but I fail.
"You should see something similiar to this to confirm ADB can see your device:
List of devices attached"
There is NO device number shown after the phrase 'List of devices attached'
To recap:
a) Phone is already plugged in my PC, under the Clockworkmod Recovery 5.5.0.2
b) adb.exe and AdbWinApi.dll file are under C: drive directly
c) Also type cmd in 'Run', a black Dos window shown C:\windows\system32\cmd.exe
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Pls don't give up on me!
: )

you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot (edit: wrong!)

Sounds like your ADB USB drivers are not correctly installed. While the phone is under CWM, when you plug it in is your computer attempting to install drivers for a new device?
Download these bare ADB Interface drivers.ADB USB Drivers
Go into Device Manager on your computer and check the device list for any unknown devices or "?" devices. If you need to update those drivers by pointing them to the drivers you downloaded and extracted from that link above.
When the ADB Interface drivers are correctly installed you should see Android Phone listed under under your Device Manager when it's plugged in with CWM recovery loaded.
---------- Post added at 02:36 PM ---------- Previous post was at 02:35 PM ----------
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.

silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
edit: i did appear to have one missing driver, my mistake. it was listed in device manager as "unknown - full"
its funny cause i never had to use adb from cwm before, never noticed

cbs2002 said:
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Click to expand...
Click to collapse
This symptom generally occurs from not having loaded the drivers for the hardware. As with the majority of hardware devices when being connected to a Windows machine, the drivers need to be loaded. Sometimes these are automatically loaded and other times they have to be manual loaded.
As an alternative and for future reference, the android-sdk package contains general USB drives which usually work for Google Nexus devices.
Generally, as this providers a *cleaner* install, best practice as recommended by Google is to download the whole android-sdk .zip and then from the installer download/install the pieces needed, such as platform-tools (containing adb) and USB drivers as opposed to extracting out the adb.exe and .dll file and installing manually.
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
Agreed. To add greater clarification so there is no confusion: adb can't be used from the bootloader.
The /sbin/adbd daemon on the device is only loaded while in normal android boot mode or in recovery mode as called by the init.rc (or on some older devices, recovery.rc) file in the boot process.
Bootloader mode will only work with fastboot while it is in fastboot usb mode.
On some devices, the bootloader has a separate menu for fastboot and on other devices, the fastboot mode is directly entered when entering the bootloader.
Hope that helps clarify!

To silow (and all other helpers)
1. I fail
2. The ADB USB drivers in my PC should be fine as in Device Manager , I can see Android Phone with Android Composite ADB Interface. (No exclamation mark)
3. On the other hand, whenever I plug my mobile into PC, I can see "Unknown-Full"
4. In DOS, when I first type "adb devices" it shows
* daemon not running. starting it now on port 5037*
*daemon started successfully *
List of devices attached
(but NO device number shown!)
5. When I enter adb devices second time, it shows
List of devices attached (No device number shown)
Thank you so much , but it is Hong Kong time (my place) at 0511 am , I didn't sleep all night and I am very tired.
If you don't mind (especially big helper Silow), please give me email so that I capture screen picture and show you in detail (hope it may help)
my email is
[email protected]
I need to sleep now, I will check my email and see you guys or come back this Forum later (several hours later, as I really need some sleep right now)
Pls don't give up on me as this is an expensive mobile. I think the hardware is fine, just need to figure out a way to unbrick it.
Thanks, and see you!

What you need to do is right click on "Unknown-Full" and click on "Update Driver...". Then choose "Install from a list or specific location". Make sure "Search for the best driver in these locations." is checked and "Include this location in the search:" is check. Click on the Browse button and browse to where you extracted the driver files from the link I posted above. Click Next and this should install the correct drivers for you. Afterwards try "adb devices" again to see if ADB now reconizes your device.

To Silow,
Fail.
1. Already installed the drivers you gave me (and there is no 'Exclamation' Mark) in Device manager
2. Situation is the same , Cannot recognize my mobile (i.e. no Device No. after entering adb devices)
3. "List of devices attached" shown in DOS video but without any number.
No other method?
My mobile is really 'bricked' to death?

To Silow and all,
Something important
1. When choose 'install zip from sd card' under CWM, a list of old folder names remains
(e..g gameloft, DCIM, Pictures, etc). That means almost all old files, folders are STILL in my mobile!
2. I have already use the funcion 'Wipe data/factory reset', 'wipe cache partition', ' Wipe Dalvik Cache'
Perhaps my CWM has problem?

What happens when you update drivers for Unknown-Full?
Boot into fastboot and see if your computer recognizes the phone by checking device manager. The key here is to get your computer to see the phone either in fastboot or CWM.
Perhaps try another cable, USB port, or new computer.
The goal is to get Android Phone ADB Composite Interface to show up in device manager either in Fastboot or CWM. Without that done you cannot use Fastboot to flash nor ADB to push a zip file to the phone.
Sent from my Galaxy Nexus using XDA App

Erased EVERYTHING

I accidently erased everything from the KF2, all I have on it now is the recovery.
How can I get a rom back on the device?
When I plugged it in the computer under Device Manager it says Portable Devices >> F:/
When I go to my computer to try to enter f:/ its inaccessible.
How can I fix this?
Thanks!

Same issue here. Understood the instruction to wipe everything before installing ROM to mean "System" and "Internal Storage" as well. Now the downloaded ROM and "gapps" zip files are gone...
Found something called "ADB Sideload" in TWRP, could that help?
Like the OP, would appreciate some help. Kindle is a brick for now...
chipsndukes

Back Up & Running
First You need a Fastboot Cable.
Run The Recovery Tool. (Options 1 then 2)
When its completed unplug the Fastboot Cable and press and hold the power button until the KF2 turns off.
Turn it back on and you are all set to Root it!
Rooting
[ONE-CLICK] Automated Freedom-Boot and TWRP installer

OK, thanks LEGEND94, that helped !
Only difference to above: did not use a Fastboot cable to get into fastboot mode, rather fmkilo's technique here: http://forum.xda-developers.com/showthread.php?t=2117224
Held off button to shut down and restarted without having to do anything else, did not have to type any command to get out of fastboot mode.
Am restarting root and ROM flashing, hopefully will work this time.
Thanks again,
chipsndukes

chipsndukes said:
OK, thanks LEGEND94, that helped !
Only difference to above: did not use a Fastboot cable to get into fastboot mode, rather fmkilo's technique here: http://forum.xda-developers.com/showthread.php?t=2117224
Held off button to shut down and restarted without having to do anything else, did not have to type any command to get out of fastboot mode.
Am restarting root and ROM flashing, hopefully will work this time.
Thanks again,
chipsndukes
Click to expand...
Click to collapse
even though legend was OP, his method was a bit overkill, but totally fine.
Once you have recovery, or even the bootloader, you should NEVER need to restore. From the bootloader you can get into fastboot now, and from fastboot you can get the recovery.
As for putting files on, I'm not sure. I could look it up but you both got your issues solved. If someone coming here does need the help, PM me and I can look it up, but from what i remember on other android devices, usually the recovery somewhere has an option to mount USB like a storage device (probably bad wording there) but basically just like when you "turn on usb storage" in the android OS.
I am ASSUMING TWRP has something similar, and if I'm wrong, I'm sure you can always ADB to push the files onto the device from your PC in fastboot mode.

iytrix said:
even though legend was OP, his method was a bit overkill, but totally fine.
Once you have recovery, or even the bootloader, you should NEVER need to restore. From the bootloader you can get into fastboot now, and from fastboot you can get the recovery.
As for putting files on, I'm not sure. I could look it up but you both got your issues solved. If someone coming here does need the help, PM me and I can look it up, but from what i remember on other android devices, usually the recovery somewhere has an option to mount USB like a storage device (probably bad wording there) but basically just like when you "turn on usb storage" in the android OS.
I am ASSUMING TWRP has something similar, and if I'm wrong, I'm sure you can always ADB to push the files onto the device from your PC in fastboot mode.
Click to expand...
Click to collapse
Unfortunately usb Mount doesn't work in the kf2 twrp. I would love the option.
You CAN adb sideload from twrp though.
--
Sent from my Kindle Fire 2, CM 10.1

What I did above is the easiest way, the sideload didn't even work!

chipsndukes said:
Held off button to shut down and restarted without having to do anything else, did not have to type any command to get out of fastboot mode.
Click to expand...
Click to collapse
One change to the above statement. I did have to get out of fastboot mode, but it was confusing how because the terminal emulator was now gone.
I did this instead via a command window with the Fire plugged into the computer. I sent the "fastboot -i0x1949 oem idme bootmode 1" command while in the root directory for the KF2_SRT_10.2.3 restore package, there is a fastboot.exe file there.
Hope that helps.
chipsndukes

[TUTORIAL] Complete Guide on How to Flash English Rom to China Local Huawei Watch

You could have been frustrated with all the features that’s supposed to be in your New Huawei Watch is nowhere to be found. Like Wi-Fi, Bluetooth and Language Selection are all hidden in the China Stable Rom of the Huawei Watch.
I have talked to the CSR of Huawei in China, they honestly told me that the Wi-Fi certificate for the watch is not yet certified that’s why they cannot unleash it yet but it is embedded inside the watch should future updates allows the Wi-Fi to be used. Regarding the language selection, local China release is locked to Simplified Chinese, whether you like it or not.
If you happen to buy from China or received a gift with a China local release Huawei Watch, here is the guide on how to flash with an English Rom which I have already tested mine on.
Here is the complete guide:
Step 1: Put the Watch to Fastboot Mode
1) Hold down the power button
2) The screen will go black for about 2 seconds and then boot into the Huawei logo. Keep holding down the power button.
3) Wait for the first vibration, release the power button and then immediately give the power button one short press.
Note: If you feel the second vibration, you waited too long to do the release and press. Start over again with Step 1.
Another alternative for Step 1:
1.) Install ADB SETUP V1.3
https://drive.google.com/file/d/0B_1zjuazXSqbQ0p6NWtvRk9OMzA/edit
2.) Enable ADB and connect to computer
How to Enable ADB:
- Go to About
- Click 5 times on Build Number to access Developer Mode
- Go to Developer Options
- Enable ADB Debugging
3.) Go into command prompt mode
4.) Reboot watch into Fastboot mode using this code:
adb reboot-bootloader
Step 2: Unlock the Bootloader
1.) On command prompt mode, type this command: Fastboot Oem Unlock
2.) accept the prompt on the watch.
Note: If successful, command prompt will say your bootloader is already unlocked.
Step 3: Flashing
Download first the three files before proceeding:
Boot Img: https://mega.nz/#!rgRQHRrb!lgQCvqH-qkuqitPRRXfCad29MdmJ6ynaUHJDr0hjeLM
Recovery Img: https://mega.nz/#!ahgjxA4R!y8Hb0CBVBRwUr0tA3HeFrrqh0ALAiMyqJu0pLsBsAD8
System Img: https://mega.nz/#!2pYVBDpA!wQJT8LDcffk7uxEmrsqna6MKWIODD-FqBO_k4Poml7g
After downloading the three files, lets proceed:
1.) While on Fastboot mode, type this on the command prompt one at a time:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
2.) and then go to recovery and do a wipe data / factory reset.
Congrats! Your done!
Further Reading if you are stuck on flashing System.img
There are some reason beyond my explanation why the system.img cannot be flashed to the watch, here is the workaround:
1.) First of all download the TWRP and fastboot boot it:
TWRP download: http://forum.xda-developers.com/attachment.php?attachmentid=3505656&d=1444766757
Code:
fastboot boot TWRP2.8.7.0-Sturgeon.img
2.) Now your watch is in TWRP and you can no longer use ADB commands, go to your watch and select Advanced, then select ADB Side Load
3.) Going back to command prompt, push the system.img in the sdcard so:
Code:
adb push system.img /sdcard/
4.) Now flash it:
Code:
adb shell dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
5.) Reboot.
Now you may encounter bootloop after flashing which I did, go back to Step 1 Fastboot mode and select Reboot Recovery, then wipe data and then clear cache, then you are good to go!
This is the most complete guide I can come up with based on my own explorations. Hope this helps.

Where can i find the drivers for this watch.
When i plug this watch into my computer Windows doesn't detect the drivers. I've tried looking on the HuaWei website but there are no downloadable drivers. Any help?

coolcaty said:
Where can i find the drivers for this watch.
When i plug this watch into my computer Windows doesn't detect the drivers. I've tried looking on the HuaWei website but there are no downloadable drivers. Any help?
Click to expand...
Click to collapse
Look here : https://m.reddit.com/r/hwatch/comments/3n9ckp/how_to_get_adb_access_over_usb/

"Fastboot Oem Unlock" should be "fastboot oem unlock" otherwise it won't work. Also make sure to have ADB 1.0.32 at least for watches!

hello!
i do all step and complete flash with twrp mode . but when reboot and will go to reboot recovery the watch restart and restart!
sry for weak english!

j.spectator said:
hello!
i do all step and complete flash with twrp mode . but when reboot and will go to reboot recovery the watch restart and restart!
sry for weak english!
Click to expand...
Click to collapse
5.) Reboot.
Now you may encounter bootloop after flashing which I did, go back to Step 1 Fastboot mode and select Reboot Recovery, then wipe data and then clear cache, then you are good to go!

Hi, first of all thanks for this awesome guide.
This is the first thing I am looking for after bought a Chinese watch from China.
Manage to go through ONLY I tried key in "fastboot oem unlock' all in small letters.
Then follow the guide instruction to goto recovery to wipe data after successfully go through the other flashing steps smoothly.
This is where I got stuck in infinite looping in Android lying and screen flashing every few seconds. I got panicked after trying multiple times failed to recover from this symptoms for a while.
Until finally manage to pull back to fastboot menu by keep press holding onto the power button. The steps of holding till first vibration then do a quick short press doesnt work.
I am glad that now I am back to normal with the English screen.
Next I will proceed to flash the TWRP and 1.4 update.
Hopefully everything goes smoothly.
Thank you for the guide once again and wish everyone success in updating and Enjoy!
Update: (9:29am)
Did a system update. Before was something like LBC49A, after system update it becomes LBC43B. I suppose this is 1.4 update as the name is the same.
Hence decided not to flash the TWRP recovery for the time being if it can continue auto system update.
Update (9/3/2016):
Sorry, nvr read through all the posts. Was thinking that (LBC43B) was the latest update.
So proceed to flash TWRP recovery then try to update to MEC23L (latest update) but failed to run "adb sideload update.zip"
Every time once enter into Recovery mode, the connection dropped. Then tried to do OTA update by factory reset as suggested but failed (confirmed my location can OTA as one use from same location didi it.)
This morning went back to PC flash back the original Stock Recovery from here.
Restart the watch and goto System Update, receive message "Charge the watch to update to MEC23L"
My thot - OTA only allow with Stock Recovery?
Update done but still cannot sms. ??
Btw, for LBC43B, many functions cannot work properly like sms, call and no sound at all. Thx n Enjoy.
P.S. Using Minimal ADB and Fastboot, PDAnet driver(for watch USB driver), running on Win7, connect via watch USB charge docking station.

help me please
No OS installed! Are you sure you wish to reboot?
This is my problem, I can´t install it-
I send you a private message Richboy234, can you help me please?

richboy324 said:
You could have been frustrated with all the features that’s supposed to be in your New Huawei Watch is nowhere to be found. Like Wi-Fi, Bluetooth and Language Selection are all hidden in the China Stable Rom of the Huawei Watch.
I have talked to the CSR of Huawei in China, they honestly told me that the Wi-Fi certificate for the watch is not yet certified that’s why they cannot unleash it yet but it is embedded inside the watch should future updates allows the Wi-Fi to be used. Regarding the language selection, local China release is locked to Simplified Chinese, whether you like it or not.
If you happen to buy from China or received a gift with a China local release Huawei Watch, here is the guide on how to flash with an English Rom which I have already tested mine on.
Here is the complete guide:
Step 1: Put the Watch to Fastboot Mode
1) Hold down the power button
2) The screen will go black for about 2 seconds and then boot into the Huawei logo. Keep holding down the power button.
3) Wait for the first vibration, release the power button and then immediately give the power button one short press.
Note: If you feel the second vibration, you waited too long to do the release and press. Start over again with Step 1.
Another alternative for Step 1:
1.) Install ADB SETUP V1.3
https://drive.google.com/file/d/0B_1zjuazXSqbQ0p6NWtvRk9OMzA/edit
2.) Enable ADB and connect to computer
How to Enable ADB:
- Go to About
- Click 5 times on Build Number to access Developer Mode
- Go to Developer Options
- Enable ADB Debugging
3.) Go into command prompt mode
4.) Reboot watch into Fastboot mode using this code:
adb reboot-bootloader
Step 2: Unlock the Bootloader
1.) On command prompt mode, type this command: Fastboot Oem Unlock
2.) accept the prompt on the watch.
Note: If successful, command prompt will say your bootloader is already unlocked.
Step 3: Flashing
Download first the three files before proceeding:
Boot Img: https://mega.nz/#!rgRQHRrb!lgQCvqH-qkuqitPRRXfCad29MdmJ6ynaUHJDr0hjeLM
Recovery Img: https://mega.nz/#!ahgjxA4R!y8Hb0CBVBRwUr0tA3HeFrrqh0ALAiMyqJu0pLsBsAD8
System Img: https://mega.nz/#!2pYVBDpA!wQJT8LDcffk7uxEmrsqna6MKWIODD-FqBO_k4Poml7g
After downloading the three files, lets proceed:
1.) While on Fastboot mode, type this on the command prompt one at a time:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
2.) and then go to recovery and do a wipe data / factory reset.
Congrats! Your done!
Further Reading if you are stuck on flashing System.img
There are some reason beyond my explanation why the system.img cannot be flashed to the watch, here is the workaround:
1.) First of all download the TWRP and fastboot boot it:
TWRP download: http://forum.xda-developers.com/attachment.php?attachmentid=3505656&d=1444766757
Code:
fastboot boot TWRP2.8.7.0-Sturgeon.img
2.) Now your watch is in TWRP and you can no longer use ADB commands, go to your watch and select Advanced, then select ADB Side Load
3.) Going back to command prompt, push the system.img in the sdcard so:
Code:
adb push system.img /sdcard/
4.) Now flash it:
Code:
adb shell dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
5.) Reboot.
Now you may encounter bootloop after flashing which I did, go back to Step 1 Fastboot mode and select Reboot Recovery, then wipe data and then clear cache, then you are good to go!
This is the most complete guide I can come up with based on my own explorations. Hope this helps.
Click to expand...
Click to collapse
Hi, I have a problem, when I do this :
"select Advanced, then select ADB Side Load" after 4 or 5 minutes processing it saids "failed"
and then I can do this step "adb push system.img /sdcard/"
but not this "adb shell dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system"
Any idea please, thank you.

jbctiong said:
Hi, first of all thanks for this awesome guide.
This is the first thing I am looking for after bought a Chinese watch from China.
Manage to go through ONLY I tried key in "fastboot oem unlock' all in small letters.
Then follow the guide instruction to goto recovery to wipe data after successfully go through the other flashing steps smoothly.
This is where I got stuck in infinite looping in Android lying and screen flashing every few seconds. I got panicked after trying multiple times failed to recover from this symptoms for a while.
Until finally manage to pull back to fastboot menu by keep press holding onto the power button. The steps of holding till first vibration then do a quick short press doesnt work.
I am glad that now I am back to normal with the English screen.
Next I will proceed to flash the TWRP and 1.4 update.
Hopefully everything goes smoothly.
Thank you for the guide once again and wish everyone success in updating and Enjoy!
Update: (9:29am)
Did a system update. Before was something like LBC49A, after system update it becomes LBC43B. I suppose this is 1.4 update as the name is the same.
Hence decided not to flash the TWRP recovery for the time being if it can continue auto system update.
Update (9/3/2016):
Sorry, nvr read through all the posts. Was thinking that (LBC43B) was the latest update.
So proceed to flash TWRP recovery then try to update to MEC23L (latest update) but failed to run "adb sideload update.zip"
Every time once enter into Recovery mode, the connection dropped. Then tried to do OTA update by factory reset as suggested but failed (confirmed my location can OTA as one use from same location didi it.)
This morning went back to PC flash back the original Stock Recovery from here.
Restart the watch and goto System Update, receive message "Charge the watch to update to MEC23L"
My thot - OTA only allow with Stock Recovery?
Update done but still cannot sms. ??
Btw, for LBC43B, many functions cannot work properly like sms, call and no sound at all. Thx n Enjoy.
P.S. Using Minimal ADB and Fastboot, PDAnet driver(for watch USB driver), running on Win7, connect via watch USB charge docking station.
Click to expand...
Click to collapse
Hi there
All i know is you can flash the stock rom then update via OTA
mine is running marshmallow already now MEC23L
This is the safer way coz i never tried to flash in the MEC23L
Cheers!

alesramosfj said:
Hi, I have a problem, when I do this :
"select Advanced, then select ADB Side Load" after 4 or 5 minutes processing it saids "failed"
and then I can do this step "adb push system.img /sdcard/"
but not this "adb shell dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system"
Any idea please, thank you.
Click to expand...
Click to collapse
I did not encounter this error
did you try the first method before doing the TWRP?

A Problem
Hi. I have a problem. I complete step3. I code command: fastboot oem reboot-recovery . Its Failed. I seclected recovery on watch. But when selecting this plan is faulty. Only flashing screen icon Android. I tried again, but still the same. Can you help me?

h**ps://drive.google.com/file/d/0B0F7_Vdg_eg3Nms3M2oyVmZ1RjA/view?usp=sharing

begioxx said:
Hi. I have a problem. I complete step3. I code command: fastboot oem reboot-recovery . Its Failed. I seclected recovery on watch. But when selecting this plan is faulty. Only flashing screen icon Android. I tried again, but still the same. Can you help me?
Click to expand...
Click to collapse
hi there
i think you need to do a further reading on the one after step three
there are chances that you will get stuck in flashing the system image file
there is a workaround.
try it again
hope it helps.

richboy324 said:
I did not encounter this error
did you try the first method before doing the TWRP?
Click to expand...
Click to collapse
Hello,
I'm also encountering this error. I did try the first method, and I'm getting stuck on activating ADB Side Load. Any tips?

Hi, there's a problem and i can't mount partition /data and /cache
plz help

Thanks a lot man you are a gem
I in hurry formatted system from twrp and was without OS. very detailed tutorial for beginners with adb. I am back with watch booting fine now

Just a note. I tried doing this while in China without vpn access for my phone. This made it so I couldn't sync up or pair because it kept trying to access google which was blocked. Once I got back to Canada I was able to do everything and update to newest OTA. If you leave it on chinese rom you can use in china and pair with the Android Wear China version app.

alesramosfj said:
No OS installed! Are you sure you wish to reboot?
This is my problem, I can´t install it-
I send you a private message Richboy234, can you help me please?
Click to expand...
Click to collapse
Hey, did he ever get back to you? I've got the same thing going on right now.

alesramosfj said:
No OS installed! Are you sure you wish to reboot?
This is my problem, I can´t install it-
I send you a private message Richboy234, can you help me please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/hua...ock-huawei-watch-t3219596/page11#post66771952
Not sure if he got back to you. I had the same problem, and it involved the system.img that I downloaded from the link above. It wasn't complete for some reason. On this thread attached, it has a zip that has it all. My watch works fine now. I want to thank the OP here for showing me the steps to take. You all ROCK!

[GUIDE] HOW TO FLASH STOCK - when all else fails [NOOB EDITION]

This How-to is special. This is for when all else fails or you've just reached a point when the device's software is broken and doesn't flash or run correctly.
I'd messed up my device pretty badly. This will also work for you if you are having key_info issues.
If your partitions are broken. If your phone is refusing to flash. If your phone is bootlooping without reason.
Performance issues of any other sort including but not limited to Fingerprint, Bluetooth, Audio, Wi-Fi, NFC and MSIM.
READ IT A FEW TIMES. DO NOT MISS ANY STEPS.​
Code:
[B][CENTER]*** DISCLAIMER***[/CENTER][/B]
DOING THIS WILL ABSOLUTELY WIPE EVERYTHING ON YOUR DEVICE. PARTITIONS INCLUDED.
I AM NOT RESPONSIBLE FOR ANY OUTCOME FROM IT.
EVEN IF IT MEANS THERMONUCLEAR WAR OR YOUR SIGNIFICANT OTHER/ FAMILY ATTEMPTING TO KILL YOU
REQUIREMENTS - ALL MUST BE MET​
WINDOWS COMPUTER with functioning USB 2.0 ports. I said 2.0.
Original cable or one you know for SURE has no issues in it. I personally prefer the OnePlus cables.
ORIGINAL SOFTWARE(Linked in the post)
UNLOCKED ROBIN [MUST]
Lots of patience (SERIOUSLY)
SOFTWARE​The USB driver for your Robin and ONLY the 7.1.1 N108 image. LINK
ADB and FASTBOOT from this XDA Thread -> LINK
HOW TO - READ TWICE. EXECUTE ONCE.​1. Start with USB Driver I used windows 10 to do this.
Right Click downloaded Robin USB Driver.
Properties -> Compatibility -> Run this program in compatibility mode-> Windows XP SP3
Hit Apply -> Ok -> Run installer -> Follow Steps.
Finish Installer -> REBOOT (I mean it)
2. Unzip your rom to a folder. For Example C:\N108
3. Go to the folder where you have unpacked your ROM. Unzip the contents of the Minimal ADB and Fastboot into that folder. Overwrite ALL existing files.
4. Click FILE-> Open Command Promt -> Open Command Prompt as ADMINISTRATOR -> Click Allow. CD to your folder. If you are using another drive you'll have to go X: followed by cd X:\<your folder name>
5.Type this in the command window
Code:
set ANDROID_PRODUCT_OUT=<LOCATION OF YOUR ROM>
LEAVE THIS COMMAND WINDOW OPEN.
6. inside your rom folder Right Click -> New - >Text Document
7. Copy the following into the first line of your document and save it.
Code:
board=NBQ_BSP
Save the file as
Code:
android-info.txt
8. Recheck that you did all those steps. You CANNOT miss a single one.
9. Put the phone into FASTBOOT mode. Hit the power button -> First screen -> Press any volume key -> Navigate to Fastboot and hit the power button. Your phone is now in fastbooot mode.
10. Connect the cable and DO NOT move it once it is connected. Do NOT connect ANY other phone during this process.
11. Check your Device Manager. It should say that there is an Android Fastboot Device connected.
12. Switch back to your command window. NOW READ THE NEXT STEPS AND COPY PASTE THEM ONE AT A TIME> DON'T MAKE A MISTAKE.
13. TYPE
Code:
fastboot devices
you will get a response with fastboot and a device number.
Make sure only the Robin is connected. NOTHING ELSE.
If it does not come up you messed up the Fastboot/ADB install.
14. NOW; THIS IS THE TRICKY PART. DON'T mess up. DON'T disturb the phone/cable/computer. Don't do ANYTHING else.
WAIT​Then next step will leave the phone looking like it is doing NOTHING. That's ok. It takes a VERY long time.
type the following into the command prompt
Code:
fastboot -i 0x2c3f -w flashall
AT THIS POINT it will say something like
Code:
Target report size <number>
LEAVE THE DEVICE AND WALK AWAY. Get a snack.
15. After sometime. The script will say succeeded and the phone will reboot.
16. Congratulate yourself on your patience. you have a fresh installed device.
If you want to custom ROM read on ->
1. Download the latest TWRP here
2. Reboot to fastboot mode.
3. fastboot "fastboot -i 0x2c3f flash recovery <twrp image name>"
4. Reboot to recovery
5. Swipe to allow modifications.
6. Wipe -> Format Data -> Yes.
7. Copy your favourite ROM to internal storage.
8. Flash it. You are one your way!

Saving it. Just in case.

Hi @valhallen.282,
I followed your instructions and all went well, however, when flashing system image I am getting the following error. Am I doing something wrong here? Appreciate your help.
sending sparse 'system' (516282 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 12.979s

minhajlk said:
Hi @valhallen.282,
I followed your instructions and all went well, however, when flashing system image I am getting the following error. Am I doing something wrong here? Appreciate your help.
sending sparse 'system' (516282 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 12.979s
Click to expand...
Click to collapse
What cable are you on and what port? That sounds like it is starting the wipe and not finishing it.

valhallen.282 said:
What cable are you on and what port? That sounds like it is starting the wipe and not finishing it.
Click to expand...
Click to collapse
I am using the original cable on USB 2 port.
Sent from my Nexus 5 using XDA Labs

minhajlk said:
I am using the original cable on USB 2 port.
Click to expand...
Click to collapse
I'd start with trying a different cable or using it the other way around. (yes I know it sounds stupid.) But that's just the way it is. (I know this because my stock cable has stopped working. ) You could try the One Plus cables. They seem to be of exceptional build quality.

valhallen.282 said:
I'd start with trying a different cable or using it the other way around. (yes I know it sounds stupid.) But that's just the way it is. (I know this because my stock cable has stopped working. ) You could try the One Plus cables. They seem to be of exceptional build quality.
Click to expand...
Click to collapse
Ok I will try that out and get back to you. Thanks mate.
Sent from my Nexus 5 using XDA Labs

Did this but got an error
Here's how my steps went
Code:
set ANDROID_PRODUCT_OUT=C:\User\[USER]\Documents\N108
created the text file, placed it into the n108 folder
then after flash all i got this
Code:
fastboot -i 0x2c3f -w flashal
load_file: could not allocate -1373637176 bytes
error could not load system.img
what do

JaxXzTwitch said:
Here's how my steps went
created the text file, placed it into the n108 folder
then after flash all i got this
what do
Click to expand...
Click to collapse
Are you unlocked is the first question.
Second is - adb is running from within the specified folder or outside it.
Third is what cable. Without details it's difficult to analyze what you've faced.

valhallen.282 said:
Are you unlocked is the first question.
Second is - adb is running from within the specified folder or outside it.
Third is what cable. Without details it's difficult to analyze what you've faced.
Click to expand...
Click to collapse
Yes i'm unlocked
it's within the target folder,
using stock cable, i've used it on adb before and it's only a few days old so i think it isn't ruined

Do you currently have a working TWRP? If you do suggest you go in and wipe EVERYTHING.
INCLUDING System + Data + Caches + Internal. Immediately reboot to bootloader. Yes it warms you of no OS loaded that's fine.
Then try again.
Yes it needs that drastic sometimes. As long as you have fastboot you can always come back to TWRP and an empty device.

valhallen.282 said:
Do you currently have a working TWRP? If you do suggest you go in and wipe EVERYTHING.
INCLUDING System + Data + Caches + Internal. Immediately reboot to bootloader. Yes it warms you of no OS loaded that's fine.
Then try again.
Yes it needs that drastic sometimes. As long as you have fastboot you can always come back to TWRP and an empty device.
Click to expand...
Click to collapse
i'm kind of hesitant to do that, because i get errors when plugging in my phone and it won't recognize it sometimes, and fastboot won't complete flashes.

JaxXzTwitch said:
i'm kind of hesitant to do that, because i get errors when plugging in my phone and it won't recognize it sometimes, and fastboot won't complete flashes.
Click to expand...
Click to collapse
see now that's important information. That means your cable IS on it's way out! NextBit built a fantastic phone but an utterly design oriented non functional cable.I'd suggest buying or borrowing a One Plus USB-C cable.
However - explain your errors please.

it could be the cable, but it's only days old, i get "this usb device has malfunctioned and is not recognized by windows" errors, or my device will read as connected, but offline, when i execute "adb devices", running "adb kill-server" doesn't bring it back either

JaxXzTwitch said:
Here's how my steps went
Code:
set ANDROID_PRODUCT_OUT=C:\User\[USER]\Documents\N108
created the text file, placed it into the n108 folder
then after flash all i got this
Code:
fastboot -i 0x2c3f -w flashal
load_file: could not allocate -1373637176 bytes
error could not load system.img
what do
Click to expand...
Click to collapse
I had this issue with N88 and N108, here is what I did:
Once the flash has failed, reboot back to bootloader by holding Volume Down and Power until the screen goes off, then release Power, then press Power again to boot, all while still holding Volume Down.
Once back into Fastboot mode, open a new Command prompt (cmd.exe), change to the directory with the files and type "fastboot -1 0x2c3f flash system system.img" and wait for it to finish (parse 6/6).
Once that has finished type "fastboot reboot" to reboot and then leave it alone until you see the purple "Welcome" screen.
Hope this helps.

DJ_SpaRky said:
I had this issue with N88 and N108, here is what I did:
Once the flash has failed, reboot back to bootloader by holding Volume Down and Power until the screen goes off, then release Power, then press Power again to boot, all while still holding Volume Down.
Once back into Fastboot mode, open a new Command prompt (cmd.exe), change to the directory with the files and type "fastboot -1 0x2c3f flash system system.img" and wait for it to finish (parse 6/6).
Once that has finished type "fastboot reboot" to reboot and then leave it alone until you see the purple "Welcome" screen.
Hope this helps.
Click to expand...
Click to collapse
+DJ_SpaRky
is the net result of your flash method same as the original intentions ie
This will also work for you if you are having key_info issues.
If your partitions are broken.
If your phone is refusing to flash.
If your phone is bootlooping without reason.
Performance issues of any other sort

iluvatrix said:
+DJ_SpaRky
is the net result of your flash method same as the original intentions ie
This will also work for you if you are having key_info issues.
If your partitions are broken.
If your phone is refusing to flash.
If your phone is bootlooping without reason.
Performance issues of any other sort
Click to expand...
Click to collapse
Just a fix for the "cannot find system.img" error.

DJ_SpaRky said:
Just a fix for the "cannot find system.img" error.
Click to expand...
Click to collapse
so would this be considered a successful flash back to stock?
& fixed broken partitions as well?

iluvatrix said:
so would this be considered a successful flash back to stock?
& fixed broken partitions as well?
Click to expand...
Click to collapse
Yes, back to Stock, not sure about broken partitions, never had that problem.

Yes back to stock and fully repaired partitions. The OP says so specifically.
The NextBit method is simply a wipe and overwrite. This is wipe, rebuild, rewrite from scratch.

XT1676 - Stuck in Unlocked Bootloader, after Wipe Cache(?!)

Some informations at first:
XT1676 Moto G5, Fine Gold, 16GB
(TYPE M2675/ FCC ID: <known>/ SEQ#: <known>)
2017-10-30
Problem: Stuck in unlocked Bootloader
Hi all,
i am stuck on bootloader and cant get out.
On my PC I have "Minimal ADB and Fastboot"(v. 1.4.2.) installed and after i open a command prompt(admin) and type
- "fastboot devices" my phone is listed as <NR> fastboot
so that works as the only positive thing i can say
- "adb reboot", *daemon not running. starting it now on port 5037*
*daemon started successfully*
error: no devices/ emulators found
- "adb reconnect", error: no devices/ emulators found
i am not into the adb commands at all, i am a dummy and i would be so glad if someone could lead me out of my problem.
Maybe a word how i got into there:
1) i installed the minimal adb and fastboot(v1.4.2.)
2) i unlocked the bootloader by doing that over the Motorola UNLOCK Bootloader site
3) then i rooted & Flash Twrp Recovery (twrp-3.1.1-0-cedric)
with "fastboot flash recovery twrp-3.1.1-0-cedric.img"
4) first time entered into twrp recovery and i did the following:
A) a factory wipe-> reboot back to recovery mode->
B) install no-verity-opt-encrypt-5.1-> reboot and let system start before i turn off phone and enter bootloader(vol down+start) again
C) after entering recovery mode again, i install Magisk-v11.6 -> reboot->
D) now everything seemed to work, the system started properly rooted.
E) but then i decided to flash once again the Magisk-v11.6 followed by wipe data/ factory reset cause i wanted to completly do the flashing all over.
(dont ask me why i did it.. i could explain and tell you my intention but well it happened anyway and brought me to where i am stuck now)
but that was on this move not all yet: i also wipe dalvik cache
so after wipedalvik/ cache , since that moment i couldnt access to my SD Card anymore as it simply didnt show up anymore.
after a restart i was my first time in an endless bootloop of that Screen with "Erasing"(, the letters sourrounded by a spectral colored circle)
i had to disconnect the phone from power . also i tried to remove the battery for a day. but it would only get me back into that bootloop and only get me out by removing the battery...
i dont know anymore what happened then when the phone now got stuck in the bootloader instead of the bootloop. But yea, now i am stuck here, appreciating any help :highfive:
more infromation from my bootloader screen:
AP Fastboot Flash Mode(secure)
BLB8.12 (<known>, 2017-04-19 11:00:47)
Baseband <known>
Product/ Variant: cedric XT1676 16GB P5
Serial Number: <known>
CPU: MSM8937
eMMC: <known>
DRAM: <known>
Console [NULL]: null
Tools Mode Config: DISABLED
Battery OK
flashing_unlocked
Software status: Official
Connect USB Data Cable
- When pressing <Start>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone drops back to Bootloader
when pressing <RESTART BOOTLOADER>
it restarts to BOOTLOADER
- When pressing <Start Recovery>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
after 10 seconds another screen poops up:
"Erasing", the letters sourrounded by a spectral colored circle for 3 seconds,
bevor the Phone just drops back to Bootloader
(talking about Erasing ..)
- When pressing <POWER OFF>
Power Off works
- When pressing <FACTORY RESET>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <BARCODES>
Barcodes are shown
- When pressing <BP TOOLS>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <QCOM>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <BOOTLOADER LOGS>
Display shows:
AP Fastboot Flash Mode(secure)
Fastboot Reason: UTAG "bootmode" configured as fastboot
When connecting an USC- cable
Transfer Mode: USB Connected
...shows up but i cant get any adb commands to work tho ofc i am a dummy at it...

oh my, i just helped myself by reading my first poste here on the forum from 2016.
i made it now to start twrp by downloading the twrp_cedric_3.1.1-0 once again putting the recovery in my adb folder and type
<fastboot flash recovery twrp.img>
followed by <fastboot reboot-bootloader>
i am curious if i can get going now and if my SD card will be read and if i can get a new flash going...

now back in twrp i go first again to wipe/ factory reset.
now going to reboot, and reboot back into recovery. only gets me back to bootloader from where i can enter twrp manually now(but there is already an indication of the problem i have?)
also before the reboot, it doesnt ask me to install the twrp app anymore where i usually choose "do not install".
now i go to install the <no-verity-opt-encrypt-5.1>, flashing it successfully as it says at the end of the process but there is also some error message in the log before the ...done:
Failed to mount '/data' (invalid argument)
now i thought i should be able to boot the system again but i only get back into the bootloader...
can someone help me how to proceed correctly?
did i miss something to flash?

Techcri said:
now back in twrp i go first again to wipe/ factory reset.
now going to reboot, and reboot back into recovery. only gets me back to bootloader from where i can enter twrp manually now(but there is already an indication of the problem i have?)
also before the reboot, it doesnt ask me to install the twrp app anymore where i usually choose "do not install".
now i go to install the <no-verity-opt-encrypt-5.1>, flashing it successfully as it says at the end of the process but there is also some error message in the log before the ...done:
Failed to mount '/data' (invalid argument)
now i thought i should be able to boot the system again but i only get back into the bootloader...
can someone help me how to proceed correctly?
did i miss something to flash?
Click to expand...
Click to collapse
For failed mount data goto wipe & select format data (option on the right)
Reboot to recovery
For always going into recovery either you don't have a rom installed or read the faq section on my twrp thread as the answer is there

First of all thanks TheFixItMan, that you are behind it and your thread looks really cool and i will immediatly read and try to understand it!
For now i am stuck in the following:
TheFixItMan said:
For failed mount data goto wipe & select format data (option on the right)
Reboot to recoverye
Click to expand...
Click to collapse
i went to "wipe" & "select format data"
the process shows successfully and "...done" but in the log there is a line of red letter:
<Red Letter>"Failed to unmount '/data' ( Device or resource busy)"
<White Letter> You may need to reboot recovery to be able to use / data again.
i went back and to reboot and recovery.
but recovery wouldnt be booted but i get back to the bootloader(maybe that is still an indication of the problem i have here?)
manually entered recovery i did the select format data again but <red letter> line remains.
TheFixItMan said:
For always going into recovery either you don't have a rom installed or read the faq section on my twrp thread as the answer is there
Click to expand...
Click to collapse
i will parallel read your thread now, thx for being behind it solving the questions! :good:

Techcri said:
First of all thanks TheFixItMan, that you are behind it and your thread looks really cool and i will immediatly read and try to understand it!
For now i am stuck in the following:
i went to "wipe" & "select format data"
the process shows successfully and "...done" but in the log there is a line of red letter:
<Red Letter>"Failed to unmount '/data' ( Device or resource busy)"
<White Letter> You may need to reboot recovery to be able to use / data again.
i went back and to reboot and recovery.
but recovery wouldnt be booted but i get back to the bootloader(maybe that is still an indication of the problem i have here?)
manually entered recovery i did the select format data again but <red letter> line remains.
i will parallel read your thread now, thx for being behind it solving the questions! :good:
Click to expand...
Click to collapse
You have to select recovery from the bootloader menu to enter recovery
You can also type in a terminal window whilst phone connected to pc in fastboot
fastboot erase userdata
This will erase all internal data (the same as format data in twrp)

Important Notes For Stock Rom Users
When you first start TWRP it will ask you to swipe to allow modifications - If you do this your stock rom will no longer boot unless you disable dm-verity.
This can be done either by flashing a disable dm-verity zip or by flashing SuperSu zip which will disable it for you
Click to expand...
Click to collapse
ok, stock rom didnt boot so i flashed the "no-verity-opt-encrypt-5.1" .zip
and voila, i could boot the stock again finally! yipie!
but three things i noticed:
1) the boot progress is suspicous / wrong/ stuck at a moment:
"hello" and "moto" i still see and before the letters of moto start spinning around, the screen freezes for like 2-3 seconds and the next ting i see is the red mouth and cameleon and so on
2) i tried to test camera real quick and it says camera is busy
camera unable to start. if this repeats please power off your phone and restart.
(i did already 5 restarts now and still same problem)
anyway, i wanted to install a ROM now, something like Cyanogenmod.
in this context i wonder what the Magisk-v11.6 does? Does it just give superuser permission and is it always required?
3) system only gives me option to Power Off System(no reboot possible)
and that power off and turn on always gets me first into bootloader tho i dont press vol down+start
Edit:
ok, i have here 3 issues still but it goes offtopic already. i throw a thanks first of all at TheFixItMan and then i think thread cna be closed.
I will soon try to install a ROM, like LineageOS 15.1 , and hope that my previous 3 issues will be solved in the process. . .

Techcri said:
ok, stock rom didnt boot so i flashed the "no-verity-opt-encrypt-5.1" .zip
and voila, i could boot the stock again finally! yipie!
anyway, i wanted to install a ROM now, something like Cyanogenmod.
in this context i wonder what the Magisk-v11.6 does? Does it just give superuser permission and is it always required?
Click to expand...
Click to collapse
Cyanogenmod is now lineageos
Use the latest version of magisk to root (see official magisk thread on xda)
You can run modules to mod phone without tripping integrity or dm-verity which if false will stop apps that check if you are rooted from working
Magisk hide can hide apps from detecting you are rooted on a per app selected basis
3) system only gives me option to Power Off System(no reboot possible)
and that power off and turn on always gets me first into bootloader tho i dont press vol down+start
Click to expand...
Click to collapse
Phone should power off normally
If it can't be started normally without going in bootloader and selecting normal startup see my faqs in twrp thread & follow guide to wiping the misc partition
Note if flashing lineageos 15.1 you will require the 64bit version of TWRP available on the lineageos thread - I did not compile this & don't support it
It also doesn't support encryption as far as I know so if you are encrypted you will need to format data & remove it else the rom will get stuck at the decryption screen

TheFixItMan said:
Phone should power off normally
Click to expand...
Click to collapse
it can be powered off normally as long as its not connected per usb (power or pc)
If it can't be started normally without going in bootloader and selecting normal startup see my faqs in twrp thread & follow guide to wiping the misc partition
Click to expand...
Click to collapse
that was not exactly the problem. my problem is that either i press restart system from system or from recovery, i first get a stop at the bootloader. from there i can just toggle to START and confirm. then my system boots. its just that i first need to confirm in bootloader the Start, always!
at this point i tried now anyways from your Official TWRP For Moto G5 Cedric- Thread |||||| your solution from your faq. But yea, it obviously doesnt fit my problem cause putting the lines in cmd prompt gave me that result and boot still does a stop at bootloader.. before i can start system or recovery..
So yea, after the first codeline didnt trigger for an unknown reason for me...
i hadnt the courage to even try the second more relevant codeline!
Note if flashing lineageos 15.1 you will require the 64bit version of TWRP available on the lineageos thread - I did not compile this & don't support it
It also doesn't support encryption as far as I know so if you are encrypted you will need to format data & remove it else the rom will get stuck at the decryption screen
Click to expand...
Click to collapse
btw, Thx a lot for the information, i appreciate it! i choose LineageOs 15.1 and it runs now. atm i am reading myself into magisk. Also big thanks for your tipp looking up the official thread.

Techcri said:
it can be powered off normally as long as its not connected per usb (power or pc)
that was not exactly the problem. my problem is that either i press restart system from system or from recovery, i first get a stop at the bootloader. from there i can just toggle to START and confirm. then my system boots. its just that i first need to confirm in bootloader the Start, always!
at this point i tried now anyways from your Official TWRP For Moto G5 Cedric- Thread |||||| your solution from your faq. But yea, it obviously doesnt fit my problem cause putting the lines in cmd prompt gave me that result and boot still does a stop at bootloader.. before i can start system or recovery..
So yea, after the first codeline didnt trigger for an unknown reason for me...
i hadnt the courage to even try the second more relevant codeline!
btw, Thx a lot for the information, i appreciate it! i choose LineageOs 15.1 and it runs now. atm i am reading myself into magisk. Also big thanks for your tipp looking up the official thread.
Click to expand...
Click to collapse
That error means your phone is not connected to your pc
Make sure you have enabled adb debugging in phones dev settings before booting into recovery
If you type
adb devices
It will list all devices attached
Once your device is listed the commands will work

TheFixItMan said:
That error means your phone is not connected to your pc
Make sure you have enabled adb debugging in phones dev settings before booting into recovery
If you type
adb devices
It will list all devices attached
Once your device is listed the commands will work
Click to expand...
Click to collapse
and you think that your commands fromyour solution here helps me with my issue that i can start straight to everywhere i want? Cause atm I just always have to go over the bootloader -"stop". From there i have then to manually "START" in order to start system (now: LineageOS 15.1:victory or where i have to manually toggle down to "RECOVERY MODE" and start TWRP.
Well, i would give it a try, but yea dunno what i am doing wrong here atm. i just realized that the command "adb devices" never worked for me yet, cause i got in conflict with the command fastboot adb devices which effectivly works for me. Cause before i installed lineageOS 15.1 i had to flash the twrp cedric 3.2.1-0 x64. i did that over the adb command prompt:
Code:
fastboot flash recovery twrp.img
and in that process i even let my phone restart to bootloader with
Code:
fastboot reboot bootloader
.
now i went to tab build nummer 7 times-> dev options "on" -> android debugging enabled.
when i go to bootloader now or to recovery, and connect my device, for a strange reason in command prompt "adb devices" shows that:
... i dont know why the cmd "adb devices" doesnt show my device. maybe there is a twrp setting i need to change?

Techcri said:
and you think that your commands fromyour solution here helps me with my issue that i can start straight to everywhere i want? Cause atm I just always have to go over the bootloader -"stop". From there i have then to manually "START" in order to start system (now: LineageOS 15.1:victory or where i have to manually toggle down to "RECOVERY MODE" and start TWRP.
Well, i would give it a try, but yea dunno what i am doing wrong here atm. i just realized that the command "adb devices" never worked for me yet, cause i got in conflict with the command fastboot adb devices which effectivly works for me. Cause before i installed lineageOS 15.1 i had to flash the twrp cedric 3.2.1-0 x64. i did that over the adb command prompt:
Code:
fastboot flash recovery twrp.img
and in that process i even let my phone restart to bootloader with
Code:
fastboot reboot bootloader
.
now i went to tab build nummer 7 times-> dev options "on" -> android debugging enabled.
when i go to bootloader now or to recovery, and connect my device, for a strange reason in command prompt "adb devices" shows that:
... i dont know why the cmd "adb devices" doesnt show my device. maybe there is a twrp setting i need to change?
Click to expand...
Click to collapse
Does it display a device when the phone is fully booted
If yes than the recovery you are using doesn't support adb (my official recovery does)
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)

Hello, thx for your support.
I linked the wrong picture. This Screeny shows the related cmd (when dev enabled, booted to recovery, connected via usb to pc and typed adb devices).
Does it display a device when the phone is fully booted. If yes than the recovery you are using doesn't support adb (my official recovery does)
Click to expand...
Click to collapse
it shows the same like linked above and when in recovery mode
so no , the 64bit version of twrp cedric 3.2.1-0 prolly isnt the problem.
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Click to expand...
Click to collapse
ok i will try that. and the command prompt i have to open from the directoryy<platform tools folder> then right?
would you deinstall minimal ADB and fastboot before installing full android sdk?

TheFixItMan said:
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Click to expand...
Click to collapse
still my phone isnt found
- sdk tools installed
- dev enabled
- adb debugging enabled
- command prompt opened at "...\android-sdk\platform-tools"
either in recovery nor in booted system nor in bootloader "adb devices" finds my phone
so the problem with the "bootstop" (have always to manually press "START" at bootloader) persists..
oh wait... i am not connected as admin! is it possible to open an admin command promp:silly:t?
so i am am reading here atm how to open command prompt in specific folder(platform-tools)
but wife is waiting for dinner so i better do that first..

Techcri said:
still my phone isnt found
- sdk tools installed
- dev enabled
- adb debugging enabled
- command prompt opened at "...\android-sdk\platform-tools"
either in recovery nor in booted system nor in bootloader "adb devices" finds my phone
so the problem with the "bootstop" (have always to manually press "START" at bootloader) persists..
oh wait... i am not connected as admin! is it possible to open an admin command promp:silly:t?
so i am am reading here atm how to open command prompt in specific folder(platform-tools)
but wife is waiting for dinner so i better do that first..
Click to expand...
Click to collapse
On windows 7 - hold shift then right click a white empty space of the window where adb is & select open command prompt here
Windows 7 or 10 - search for cmd then right click on cmd and select run as administrator then navigate using cd commands to adb location or copy & paste location (if any spaces in path then put the entire path in quotation marks)

On windows 7 - hold shift then right click a white empty space of the window where adb is & select open command prompt here
Click to expand...
Click to collapse
yes i did that before as non admin
Windows 7 or 10 - search for cmd then right click on cmd and select run as administrator then navigate using cd commands to adb location or copy & paste location (if any spaces in path then put the entire path in quotation marks)
Click to expand...
Click to collapse
i use win7 and cd'ing to the path was almost getting annoying
as screenshot shows, it still doesnt work

in my desperation i deinstalled now all adb drivers(minimal+ sdk)
ran a ccleaner and cleaned registry and reinstalled minimal adb again (btw, there was a new version by now out, 1.4.3)
so the episodes still goes on and i could figure out some new details
because i bought the same phone again for a relative who needed a phone..
in the process of setting it up correctly( thankfully xda is around ) i enabled dev options and the adb debugging
here is the result for the new phone
that shows now that executing as admin or standard user wasnt the problem. i just did it as standard user..
then i thought "hey cool, wait, i connect now my own G5 and see if i can get the phones' Nr displayed there and make sure my phone can communicate with my pc over adb( dunno if the sentence just made sense- greetz from a dummy)"
what happened is shown in this screenshot .. same picture as before! :crying:
(dont get irritated by the screeny because i used the same command prompt for
first, the new phone and
second, my "old" phone which doesnt boot properly, if you look at the command and the result
i am lost!
is it possible to reinstall a bootloader? or how come my phone doesnt communicate with the pc anymore?
and how come that effects the booting process so that i always get this "stop" at the bootloader although i pressed for a restart?
can i do any more tests that indicates what problem i have here?