Develop Bugs

[Q] Endless loop of restarts into recovery

hi everyone,
I am in a quite a pickle here. I tried updating my phone with ARHD43 and after doing it couldn't get the WIFI to turn on. I read a bit and found that this is becuase I do not have the latest firmware. So I tried going back to stock through RUU (flashed stock recovery and boot.img) and in the process flashed new recovery and boot images. Now the my phone keeps booting into stock recovery with the red triangle continuously and I can't boot into the OS. From recovery when I select apply from SD card I throws CID error and reboots into recovery again!
I cannot connect to fastboot so I am stuck bad. :crying:
did I brick my device? can I save it? I am S-ON with unlocked boot loader. region is .707
Appreciate your help.
<I have posted a similar question in the ARHD43 thread but haven't recevied a response so posting in here in the general forum again>

simplyaha said:
I cannot connect to fastboot so I am stuck bad. :crying:
Click to expand...
Click to collapse
This part is your biggest issue. As you know, you can't do much without fastboot.
Make sure you are in bootloader-fastboot mode when issuing fastboot commands. Try to uninstall and re-install fastboot drivers, a different USB post on your computer, even another computer.
Once you get fastboot working, it should be as simple as flashing TWRP again (bootloader must be unlocked) than installing the proper stock nandroid and stock recovery from the following thread (instructions on how to restore the nandroid in Post #3 of the thread, under Questions & Answer). Then OTA to Lollipop.
http://forum.xda-developers.com/showthread.php?t=2701376
---------- Post added at 09:34 AM ---------- Previous post was at 09:33 AM ----------
simplyaha said:
So I tried going back to stock through RUU (flashed stock recovery and boot.img) >
Click to expand...
Click to collapse
Why would you do this? You realize that boot.img is just the kernel (not a full ROM)?

redpoint73 said:
This part is your biggest issue. As you know, you can't do much without fastboot.
Make sure you are in bootloader-fastboot mode when issuing fastboot commands. Try to uninstall and re-install fastboot drivers, a different USB post on your computer, even another computer.
Once you get fastboot working, it should be as simple as flashing TWRP again (bootloader must be unlocked) than installing the proper stock nandroid and stock recovery from the following thread (instructions on how to restore the nandroid in Post #3 of the thread, under Questions & Answer). Then OTA to Lollipop.
http://forum.xda-developers.com/showthread.php?t=2701376
---------- Post added at 09:34 AM ---------- Previous post was at 09:33 AM ----------
Why would you do this? You realize that boot.img is just the kernel (not a full ROM)?
Click to expand...
Click to collapse
thank you for replying.
I have have fast boot on my pic and it is working fine. I have used it to install custom rom on my wife's phone and my phone earlier. the problem is I am not able to get into the boot loader and push commands to my phone through fastboot or adb.
my plan was to actually run RUU and update to stock. I couldn't find the RUU for my 707 M8. I read somewhere that to make this work I should run RUU and extract and flash the boot.img it stores in the temporary folder on the PC. I also saved the stock rom file and was planning to flash that through recovery. but I cannot do that now because I am stuck in recovery.
any idea how I can get into boot loader.. this should give me a lot of options to fix my phone.

simplyaha said:
thank you for replying.
I have have fast boot on my pic and it is working fine. I have used it to install custom rom on my wife's phone and my phone earlier. the problem is I am not able to get into the boot loader and push commands to my phone through fastboot or adb.
any idea how I can get into boot loader.. this should give me a lot of options to fix my phone.
Click to expand...
Click to collapse
To get into bootloader, hold down power and vol up for several seconds (maybe up to 10 seconds or more). Once the screen goes black to reboot, immediately let go of both those buttons, and just hold vol down. Keep holding vol down until bootloader appears. If you fail to get into bootloader, you simply started holding vol down too late, or let go of it too early. Just repeat until you get it right.
Fastboot command only work in fastboot mode. adb commands will only work in OS or in recovery. So if you try to issue adb commands in bootloader or bootloader-fastboot modes, it won't work.
simplyaha said:
my plan was to actually run RUU and update to stock. I couldn't find the RUU for my 707 M8. I read somewhere that to make this work I should run RUU and extract and flash the boot.img it stores in the temporary folder on the PC. I also saved the stock rom file and was planning to flash that through recovery. but I cannot do that now because I am stuck in recovery.
Click to expand...
Click to collapse
Pulling files from another CID's RUU is not the proper way to restore to stock. I linked the proper thread with your stock ROM (which also includes boot.img) and stock recovery for your CID.
Plus, the stock ROM and recovery you restore has to match your firmware number, as indicated as OS number on bootloader screen, or main version on getvar all.

redpoint73 said:
To get into bootloader, hold down power and vol up for several seconds (maybe up to 10 seconds or more). Once the screen goes black to reboot, immediately let go of both those buttons, and just hold vol down. Keep holding vol down until bootloader appears. If you fail to get into bootloader, you simply started holding vol down too late, or let go of it too early. Just repeat until you get it right.
Fastboot command only work in fastboot mode. adb commands will only work in OS or in recovery. So if you try to issue adb commands in bootloader or bootloader-fastboot modes, it won't work.
Pulling files from another CID's RUU is not the proper way to restore to stock. I linked the proper thread with your stock ROM (which also includes boot.img) and stock recovery for your CID.
Plus, the stock ROM and recovery you restore has to match your firmware number, as indicated as OS number on bootloader screen, or main version on getvar all.
Click to expand...
Click to collapse
I did try this combination to get into boot loader but I couldn't successfully do that. I had also tried Hold power then immediately volume up and down at same time. When phone powers off release the volume up button.
I will try again and reply.
I couldn't find the 707 RUU anywhere on the web.. please share the link with me if you got it. I hope I get it into boot loader..

simplyaha said:
I did try this combination to get into boot loader but I couldn't successfully do that. I had also tried Hold power then immediately volume up and down at same time. When phone powers off release the volume up button.
Click to expand...
Click to collapse
You're making it more complicated than it needs to be. Stop trying other button combos, and just do it they way I said previously, this works every time as long as you don't start pressing vol down too late (it has to be while the screen is still black before the HTC logo screen appears - you have about 3 seconds which is plenty of time) or don't let go of vol down too early (don't let go until the bootloader screen appears - should only take a second).
If it doesn't work, its pilot error.
simplyaha said:
I couldn't find the 707 RUU anywhere on the web.. please share the link with me if you got it. I hope I get it into boot loader..
Click to expand...
Click to collapse
Only if you promise to stop messing around with incorrect processes, like trying to pull the recovery and boot.img out of the RUU.

redpoint73 said:
You're making it more complicated than it needs to be. Stop trying other button combos, and just do it they way I said previously, this works every time as long as you don't start pressing vol down too late (it has to be while the screen is still black before the HTC logo screen appears - you have about 3 seconds which is plenty of time) or don't let go of vol down too early (don't let go until the bootloader screen appears - should only take a second).
If it doesn't work, its pilot error.
Only if you promise to stop messing around with incorrect processes, like trying to pull the recovery and boot.img out of the RUU.
Click to expand...
Click to collapse
yeah.. i guess I tried all those random things because I am not very clear on all the processes.. but I am learning :victory:
yes, no more messing around, promise.. :angel:

simplyaha said:
yeah.. i guess I tried all those random things because I am not very clear on all the processes.. but I am learning
Click to expand...
Click to collapse
Yeah, stop doing that (trying random things). You can get yourself in a lot of trouble by "experimenting". Stick to proven solutions provided by knowledgeable XDA members.
Here is a link to the 4.19.707 RUU: http://forum.xda-developers.com/showpost.php?p=61886163&postcount=15
I only know of this, since xunholyx linked to it last week while we were helping another 707 owner. I take no responsibility for it. Just linking you to it by request.

redpoint73 said:
Yeah, stop doing that (trying random things). You can get yourself in a lot of trouble by "experimenting". Stick to proven solutions provided by knowledgeable XDA members.
Here is a link to the 4.19.707 RUU: http://forum.xda-developers.com/showpost.php?p=61886163&postcount=15
I only know of this, since xunholyx linked to it last week while we were helping another 707 owner. I take no responsibility for it. Just linking you to it by request.
Click to expand...
Click to collapse
ccol thank! I will try this tonight and share the outcome.. :good:

eureka! got my phone up and running now. the ruu was perfect. but got my memory card messed up (showing as raw format on the pc). gotta look for a solution for this now :banghead:
but my phone is back! thank you for all the help. much appreciated. :thumbup:
Sent from my HTC One_M8 using XDA Free mobile app

Can someone please help me

I was trying to update my phone and something most likely went wrong. Then the update installed and screwed up my phone. When I turned it on it stayed on the startup for so long. I tried to clear cache through the bootloader, but now it shows the android screen of death except it flashes. This occurs even outside the bootloader.
I am rooted with stock os.
Thanks in advance to whoever helps

Flash it with the original firmware

anfalanl said:
Flash it with the original firmware
Click to expand...
Click to collapse
Yup, same thing happened to me, I had to reflash it to stock firmware.

How would i flash
Magister54 said:
Yup, same thing happened to me, I had to reflash it to stock firmware.
Click to expand...
Click to collapse
Hey, thanks for the response.
Could you please elaborate on how I would do this. Because I do not understand how to do this if the bootloader doesn't work.
Thanks, your response and input means alot

Take the firmware from Asus website, for me I took UL-Z00A-WW-2.19.40.22-user.zip
Boot the phone in bootloader and try to go in the recovery screen, it took me a lot of tries to get in it!!!
From here you can select "insall update from ADB"
From your PC you do a "adb sideload UL-Z00A-WW-2.19.40.22-user.zip"

Magister54 said:
Take the firmware from Asus website, for me I took UL-Z00A-WW-2.19.40.22-user.zip
Boot the phone in bootloader and try to go in the recovery screen, it took me a lot of tries to get in it!!!
From here you can select "insall update from ADB"
From your PC you do a "adb sideload UL-Z00A-WW-2.19.40.22-user.zip"
Click to expand...
Click to collapse
When i try to do this, i see the error sign but it is flashing

hudasameer450 said:
When i try to do this, i see the error sign but it is flashing
Click to expand...
Click to collapse
That's normal. When you get the error sign when booting into stock recovery, hold power down and press volume up and quickly release both buttons at the same time. If done correctly recovery menu will pop up and then you can start actually flashing.

Flashing
does this still work if the screen is flashing, because I tried before and it did not work, maybe I pressed it wrong or there is some other issue.
Thanks

Help!!!! Bricked one m9! No fastboot commands, no adb, just a blue screen!

Please help urgently! So I just S-OFF'd my phone (right after unlocking my bootloader via htcdev) and I was excited to finally manually flash a 5.1 update to my EE UK One m9. I sort of made it a European version by changing one of its update numbers to [BLANK].401.[BLANK]. I then spent the whole night booting my phone into download mode and using fastboot commands: "htc_fastboot flash zip...".
Each zip was the previous update to the other, I.e. I was already on 1.32.401.6, so I used fastboot to get to 1.32.401.8 as the cmd. prompt said that it was successfully installed on my phone (p.s. I didn't have an sd card big enough to exfat 32 and put the update zips on it). I then repeated the steps again, but then fastboot flashed "2.10.401.", this was the update that would hopefully bring my phone to 5.1 . The cmd. prompt said that it was a success so I booted my phone up as normal, but I went to the settings to check software information and it was still on 1.32.401.6! It then said an update was ready to install so I just installed it as normal. Once it went into the bootloader it flashed it without any problems and tried to boot back up again. It then lit up a blue screen for 10 seconds and then went into the black HTC RUU screen with the grey htc logo. My phone has now, for the last hour, been stuck in this infinite loop of blue screen, vibrate, ruu screen and REPEAT. I've tried pressing vol. down and power as well as up to get into other modes like download mode, but it doesn't work. I CAN'T EVEN TURN IT OFF! I HAVE TO WAIT FOR IT TO RUN OUT OF BATTERY! MORE IMPORTANTLY, ADB DOESNT RECOGNISE IT, NOR DOES FASTBOOT!!!! SO I CAN'T EVEN FLASH A STOCK RECOVERY, SYSTEM IMG, ETC! PLEASE IF ANYONE CAN, HELP ME. I REALLY DON'T WANT TO HAVE TO BUY A NEW ONE AND PAY S-OFF AGAIN!

Louis118 said:
Please help urgently! So I just S-OFF'd my phone and I was excited to finally manually flash a 5.1 update to my EE UK One m9. I sort of made it a European version by changing one of its update numbers to [BLANK].401.[BLANK]. I then spent the whole night booting my phone into download mode and using fastboot commands: "htc_fastboot flash zip...".
Each zip was the previous update to the other, I.e. I was already on 1.32.401.6, so I used fastboot to get to 1.32.401.8 as the cmd. prompt said that it was successfully installed on my phone (p.s. I didn't have an sd card big enough to exfat 32 and put the update zips on it). I then repeated the steps again, but then fastboot flashed "2.10.401.", this was the update that would hopefully bring my phone to 5.1 . The cmd. prompt said that it was a success so I booted my phone up as normal, but I went to the settings to check software information and it was still on 1.32.401.6! It then said an update was ready to install so I just installed it as normal. Once it went into the bootloader it flashed it without any problems and tried to boot back up again. It then lit up a blue screen for 10 seconds and then went into the black HTC RUU screen with the grey htc logo. My phone has now, for the last hour, been stuck in this infinite loop of blue screen, vibrate, ruu screen and REPEAT. I've tried pressing vol. down and power as well as up to get into other modes like download mode, but it doesn't work. I CAN'T EVEN TURN IT OFF! I HAVE TO WAIT FOR IT TO RUN OUT OF BATTERY! MORE IMPORTANTLY, ADB DOESNT RECOGNISE IT, NOR DOES FASTBOOT!!!! SO I CAN'T EVEN FLASH A STOCK RECOVERY, SYSTEM IMG, ETC! PLEASE IF ANYONE CAN, HELP ME. I REALLY DON'T WANT TO HAVE TO BUY A NEW ONE AND PAY S-OFF AGAIN!
Click to expand...
Click to collapse
hold power and vol up and vol down all at the same time will get you to bootloader, we hope

Aldo101t said:
hold power and vol up and vol down all at the same time will get you to bootloader, we hope
Click to expand...
Click to collapse
That helped thanks, but I still can't boot into anything else... I'm pretty sure I can't install anything through fastboot without download or run mode...

Louis118 said:
That helped thanks, but I still can't boot into anything else... I'm pretty sure I can't install anything through fastboot without download or run mode...
Click to expand...
Click to collapse
you can't boot into download mode from bootloader?
or boot into recovery and restore a backup,

Aldo101t said:
you can't boot into download mode from bootloader?
or boot into recovery and restore a backup,
Click to expand...
Click to collapse
nope, NOTHING. THE ONLY THING THAT WORKS IS THE POWER OFF OPTION.

Aldo101t said:
you can't boot into download mode from bootloader?
or boot into recovery and restore a backup,
Click to expand...
Click to collapse
what you should do is if you can restore a backup, put a 5.1 rom on your sd card and after you flash the latest firmware 2.10.401.xx. then boot to recovery and install the 5.1 rom.
---------- Post added at 07:43 PM ---------- Previous post was at 07:41 PM ----------
Louis118 said:
nope, NOTHING. THE ONLY THING THAT WORKS IS THE POWER OFF OPTION.
Click to expand...
Click to collapse
you still have TWRP INSTALLED, do you have a backup.

Aldo101t said:
what you should do is if you can restore a backup, put a 5.1 rom on your sd card and after you flash the latest firmware 2.10.401.xx. then boot to recovery and install the 5.1 rom.
---------- Post added at 07:43 PM ---------- Previous post was at 07:41 PM ----------
you still have TWRP INSTALLED, do you have a backup.
Click to expand...
Click to collapse
How do you expect me to boot into it? I told you, pressing any other mode besides power off, causes the blue screen loop

Louis118 said:
nope, NOTHING. THE ONLY THING THAT WORKS IS THE POWER OFF OPTION.
Click to expand...
Click to collapse
try powering it off then go back to bootloader and try to get to recovery again

Aldo101t said:
try powering it off then go back to bootloader and try to get to recovery again
Click to expand...
Click to collapse
Nope, still does the blue loop.

Louis118 said:
Nope, still does the blue loop.
Click to expand...
Click to collapse
well, that's the sh^ts, I don't know at this point.maybe someone else can chime in here that can help.

I've seen this before, and there is no fix that I'm aware of. You've corrupted something important in your firmware, probably by flashing all those firmware packages.
You made several mistakes here, the first in thinking you needed to flash every firmware for your phone. All you needed was the last one. The other mistake was confusing your OS version with your firmware version. You were still on 1.32 base but your firmware was updated.
The last mistake, and the one that probably did the damage, was trying to take an OTA after all that. You were stock enough for it to run, but since your firmware was already updated, the OTA broke something.
As far as I know, the only thing you can do is return it to HTC for service.
Sent from my HTC One M9 using Tapatalk

iElvis said:
I've seen this before, and there is no fix that I'm aware of. You've corrupted something important in your firmware, probably by flashing all those firmware packages.
You made several mistakes here, the first in thinking you needed to flash every firmware for your phone. All you needed was the last one. The other mistake was confusing your OS version with your firmware version. You were still on 1.32 base but your firmware was updated.
The last mistake, and the one that probably did the damage, was trying to take an OTA after all that. You were stock enough for it to run, but since your firmware was already updated, the OTA broke something.
As far as I know, the only thing you can do is return it to HTC for service.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Thanks for trying to help anyway. Also, I got this under contract from EE, so do I have UH OH protection automatically from htc? Or will it cost me to get it serviced?

Louis118 said:
Thanks for trying to help anyway. Also, I got this under contract from EE, so do I have UH OH protection automatically from htc? Or will it cost me to get it serviced?
Click to expand...
Click to collapse
Uh Oh protection isn't available in the UK.
As you unlocked your bootloader and got S-OFF, they will almost certainly charge you for repairs as this isn't a hardware issue and was actually caused by you flashing your phone.
Sent from my HTC One M9 using Tapatalk

Questions............
Did u install any recovery like twrp?
Did you root?
Post pictures of bootloader/try to post any other screen you may be able to enter

LLegion said:
Questions............
Did u install any recovery like twrp?
Did you root?
Post pictures of bootloader/try to post any other screen you may be able to enter
Click to expand...
Click to collapse
I'm able to enter the boot loader menu (with the options to reboot, power down, download mode and bootloader). Unfortunately, clicking any of the options (apart from power down) causes the blue screen boot loop to continue.

This wasn't really Crazy you now All You have to do is go to the bootloader menu and from there Ashley you can actually flash the Recovery ebusiness Leave me and if you don't believe me godaddy redirect link to the Team Win recovery project Website Just follow the instructions to flash recovery as they say
---------- Post added at 05:17 PM ---------- Previous post was at 05:13 PM ----------
You can flash recovery from bootloader menu i did that way when by mistake did erease all my internal card including system.img.....i was lost my phone didnt boot line yours also getting the bluescreen and voilaaa!!! I did flash on bootloader menu but download the 2.8.7.1 beta here the proof link....https://twrp.me/devices/htconem9.html

LLegion said:
This wasn't really Crazy you now All You have to do is go to the bootloader menu and from there Ashley you can actually flash the Recovery ebusiness Leave me and if you don't believe me godaddy redirect link to the Team Win recovery project Website Just follow the instructions to flash recovery as they say
---------- Post added at 05:17 PM ---------- Previous post was at 05:13 PM ----------
You can flash recovery from bootloader menu i did that way when by mistake did erease all my internal card including system.img.....i was lost my phone didnt boot line yours also getting the bluescreen and voilaaa!!! I did flash on bootloader menu but download the 2.8.7.1 beta here the proof link....https://twrp.me/devices/htconem9.html
Click to expand...
Click to collapse
I flashed the recovery file successfully (according to the command window) but when I click the "reboot recovery mode" option it brings up the red development text and then goes back into the bluescreen loop.

Louis118 said:
I flashed the recovery file successfully (according to the command window) but when I click the "reboot recovery mode" option it brings up the red development text and then goes back into the bluescreen loop.
Click to expand...
Click to collapse
You said before that fastboot wasn't working. It's working now? Does it show up in fastboot devices?
If so, you might try running a RUU from bootloader.

The trixk is to flash and just after reboot press power and down vol to wnter immediatly into rexovery twrp just as it says in the link...just do it and will go into twrp once you have entered justflash any nandroid or flash a zip ruu from sd card in a sexond boot

I'm not able to enter RUU mode...

Bricked Watch -- Help!!

I rooted the watch successfully and then attempted to revert to stock using the instructions here: http://forum.xda-developers.com/huawei-watch/development/guide-return-to-stock-huawei-watch-t3219596
. Midway through the restore of the system.img, my computer crashed and now the watch is stuck at the Huwaei logo. I can no longer connect to the watch over adb - attemps to do so show that the watch is "offline." Is all hope lost or is there anything I can try?

No one has figured out a way to boot directly to the boot loader yet...there has to be a way, just need to find it.
Edit...if it shows connected but offline, just try unplugging it and plugging it back in again.
Sent from my Nexus 6 using Tapatalk

brizey said:
No one has figured out a way to boot directly to the boot loader yet...there has to be a way, just need to find it.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Okay. I'll keep checking back. BTW, I looked back at the terminal window which reopened when my computer restarted and the last thing posted there was "restored" so it may not have been my computer restarting which caused the issue. For this reason, I would strongly caution anyone who is thinking about using the system restore files in the linked thread. Better safe than sorry.

davpel said:
Okay. I'll keep checking back. BTW, I looked back at the terminal window which reopened when my computer restarted and the last thing posted there was "restored" so it may not have been my computer restarting which caused the issue. For this reason, I would strongly caution anyone who is thinking about using the system restore files in the linked thread. Better safe than sorry.
Click to expand...
Click to collapse
Hey man, try unplugging and plugging it back in, then quickly doing an adb reboot bootloader. I have found that adb goes offline when in ambient mode, so you may get a brief chance to get it to the bootloader.
Edit:
Ah hah! You have to adb root to get it to work in ambient mode.
Man, we need a mechanical way to boot to bootloader.

brizey said:
Hey man, try unplugging and plugging it back in, then quickly doing an adb reboot bootloader. I have found that adb goes offline when in ambient mode, so you may get a brief chance to get it to the bootloader.
Edit:
Ah hah! You have to adb root to get it to work in ambient mode.
Man, we need a mechanical way to boot to bootloader.
Click to expand...
Click to collapse
Yeah, I think I'm screwed. When I do adb devices, my computer sees the watch and gives back the serial number but shows its offline. I've tried some of the tricks to get into the LG Watch and 360 bootloaders, but they don't work with the H watch. Also, my watch never really shuts off. It is stuck at the logo. If I hold down the power button, it will eventually turn to black for about a 1/2 second, then boot immediately back into the log and give two vibrations. But never the bootloader. Ugh!

If you can get into the bootloader, maybe try restoring these instead? http://forum.xda-developers.com/huawei-watch/general/huawei-watch-stock-rooted-images-t3224930

davpel said:
Yeah, I think I'm screwed. When I do adb devices, my computer sees the watch and gives back the serial number but shows its offline. I've tried some of the tricks to get into the LG Watch and 360 bootloaders, but they don't work with the H watch. Also, my watch never really shuts off. It is stuck at the logo. If I hold down the power button, it will eventually turn to black for about a 1/2 second, then boot immediately back into the log and give two vibrations. But never the bootloader. Ugh!
Click to expand...
Click to collapse
I have my TWRP backup if you need it. I looked at it and it looks OK...typical image with the folders and SELinux context files. But...it is a rooted image.

brizey said:
I have my TWRP backup if you need it. I looked at it and it looks OK...typical image with the folders and SELinux context files. But...it is a rooted image.
Click to expand...
Click to collapse
Thanks, but unless/until I can get into the bootloader, I'm stuck. Right?

davpel said:
Yeah, I think I'm screwed. When I do adb devices, my computer sees the watch and gives back the serial number but shows its offline. I've tried some of the tricks to get into the LG Watch and 360 bootloaders, but they don't work with the H watch. Also, my watch never really shuts off. It is stuck at the logo. If I hold down the power button, it will eventually turn to black for about a 1/2 second, then boot immediately back into the log and give two vibrations. But never the bootloader. Ugh!
Click to expand...
Click to collapse
Hmmm...just noticed that tiny's and skin's system images are not the same. Different sizes.

davpel said:
Thanks, but unless/until I can get into the bootloader, I'm stuck. Right?
Click to expand...
Click to collapse
If if's anything like the Moto 360, you should be able to power the watch off, and then hold the power button for ~30 seconds to achieve boot to bootloader.

1/4 Life said:
If if's anything like the Moto 360, you should be able to power the watch off, and then hold the power button for ~30 seconds to achieve boot to bootloader.
Click to expand...
Click to collapse
Tried that. I get the double vibration, but no bootloader.

FWIW, I just looked at a few of the 5.1 OTAs for other watches. I think the OTAs will work even if rooted. I looked at skin1980's init autoroot script, and I don't think it really touches any of the base system files...it only adds in the binaries. The updater script does a hash on all of the files that it is going to patch, then patches them if the hashes are OK. Given that we are not really touching the system files by flashing a custom ROM, I think we can make the OTA zips work. The kernel will likely not flash, but we can always build a new one from source if needed.

brizey said:
Hmmm...just noticed that tiny's and skin's system images are not the same. Different sizes.
Click to expand...
Click to collapse
And i dont know why. I dd them like i said and they are completely stock.

davpel said:
Tried that. I get the double vibration, but no bootloader.
Click to expand...
Click to collapse
http://forum.xda-developers.com/g-watch-r/development/fastboot-mode-lg-g-watch-r-t2946955 (?)

1/4 Life said:
http://forum.xda-developers.com/g-watch-r/development/fastboot-mode-lg-g-watch-r-t2946955 (?)
Click to expand...
Click to collapse
Thanks, but tried the LG method as well (both the swipe and the tap) and had the same results -- or lack thereof.

Has anyone else tried restoring to stock with success from Skin's files?

myke66 said:
Has anyone else tried restoring to stock with success from Skin's files?
Click to expand...
Click to collapse
@davpel watch has been successfully restored with the system.img i posted. BTW the fastboot flash system system.img doesn't work properly, i will update my thread with the new HOWTO.

Skin1980 said:
@davpel watch has been successfully restored with the system.img i posted. BTW the fastboot flash system system.img doesn't work properly, i will update my thread with the new HOWTO.
Click to expand...
Click to collapse
Yes, my watch is working great, thanks to Skin1980. This community is very lucky to have him!

Skin1980 said:
@davpel watch has been successfully restored with the system.img i posted. BTW the fastboot flash system system.img doesn't work properly, i will update my thread with the new HOWTO.
Click to expand...
Click to collapse
davpel said:
Yes, my watch is working great, thanks to Skin1980. This community is very lucky to have him!
Click to expand...
Click to collapse
Agree 100%. I am returning my first watch, and flashed it back to stock and relocked the bootloader with no issues using the revised instructions. Going to keep my new one stock I think...got to cut down on the toys (Nexus 6, Nexus 7, iPhone 5s, custom PC, G37, surveillance system, house LED lighting conversion, etc. etc. Momma ain't happy, and I really want to spend more time with the kiddos.)

Who the hell needs to ROOT a damn smart watch?! I could see when it was 2 years ago with the first Samsung smart watch to sideload Android apps but this.... This is just stupid. Congrats
Sent from my SM-N910T using Tapatalk

Help! I think it died!!

So I was scrolling through some Magisk Modules and I think I installed the wrong one by not paying attention, as I installed it I couldn't stop the process and either way I was screwed, afterwards it showed up in the "Modules" section and I hit the trash can and rebooted. Afterwards the phone does not boot and cannot get to the recovery.
Can one of you good people give me steps to when I get to my computer. please and thank you!!

InfinityXDA said:
So I was scrolling through some Magisk Modules and I think I installed the wrong one by not paying attention, as I installed it I couldn't stop the process and either way I was screwed, afterwards it showed up in the "Modules" section and I hit the trash can and rebooted. Afterwards the phone does not boot and cannot get to the recovery.
Can one of you good people give me steps to when I get to my computer. please and thank you!!
Click to expand...
Click to collapse
If your bootloader is unlocked, while phone is booting press power button for 7-8 seconds or more this will restart your phone, when you see the black screen press vol down button to enter fastboot mode.
After fastboot mode you can flash stock rom with mi flash

Kineceleran said:
If your bootloader is unlocked, while phone is booting press power button for 7-8 seconds or more this will restart your phone, when you see the black screen press vol down button to enter fastboot mode.
After fastboot mode you can flash stock rom with mi flash
Click to expand...
Click to collapse
Thanks man I appreciate it! So after I do this do I have to re-unlock my bootloader?

InfinityXDA said:
Thanks man I appreciate it! So after I do this do I have to re-unlock my bootloader?
Click to expand...
Click to collapse
No you don't have to relock. You can use it as like that.
You should keep bootloader unlocked always in my opinion. It's not a bad or dangereous thing.

Kineceleran said:
No you don't have to relock. You can use it as like that.
You should keep bootloader unlocked always in my opinion. It's not a bad or dangereous thing.
Click to expand...
Click to collapse
When I go to the boot loader it reboots after like 1 minute then it stays on the android one screen until I reboot it to recovery. So I think my device is done and over with?

InfinityXDA said:
When I go to the boot loader it reboots after like 1 minute then it stays on the android one screen until I reboot it to recovery. So I think my device is done and over with?
Click to expand...
Click to collapse
Could you take a photo or video of that

This is a full video of what happens when I go to the bootloader

InfinityXDA said:
This is a full video of what happens when I go to the bootloader
Click to expand...
Click to collapse
prepare mi flash with rom and everything so you just have to enter fastboot and quickly plug in usb then start flashing.
Fastboot maybe just quits automatic if there is no input?

merlin.berlin said:
prepare mi flash with rom and everything so you just have to enter fastboot and quickly plug in usb then start flashing.
Fastboot maybe just quits automatic if there is no input?
Click to expand...
Click to collapse
Yes you right at that point but fastboot hasnt a timer
He should flash quickly.
Or using sideload method will be a good way to flash pixel experience and after that, turn to stock

Indeed thank you for so much help I'm indeed new to Xiaomi Devices, weird setup from my first rooted device which was much more complex. Thanks for both of your assistance
In less than 45 minutes I'll fill you in upon what I will do

InfinityXDA said:
Indeed thank you for so much help I'm indeed new to Xiaomi Devices, weird setup from my first rooted device which was much more complex. Thanks for both of your assistance
In less than 45 minutes I'll fill you in upon what I will do
Click to expand...
Click to collapse
Do you have MIFlash installed?
I had the same automatic reebots while in fastboot
regardless of the input but that was because i had the wrong drivers
When I installed MIFlash the right drivers were also installed
Hope this helps.