[Q] Lost Recovery after Flashing TWRP Update - G2 Q&A, Help & Troubleshooting

I'm on a VS980 running crDroid LP ROM (therefore with 12B).
I had TWRP 2.8.1.0 I believe and tried upgrading to 2.8.4.0 by downloading/flashing thru Flashify. It looked like it successfully installed, but then when I rebooted into recovery, I got the LG logo screen with small text in the upper left corner (looked like fastboot text see below) for a split second before getting stuck on a black screen. Can only hard reset with power button back into ROM. I tried 2.8.3.0 thru Flashify to see if it was just a problem with the newest version. Same issue. Finally, I tried using the LG G2 Toolkit v1.5 program via USB to install 2.7.0.0 and I still get the same issue happening.
I have no idea what messed up, but it seems I've lost recovery. Ideas to get it back? Although my phone works, I can't change/backup/restore my ROM right now...Help would be appreciated!
UPDATE: Tried using adb to flash different recovery versions and also using FreeGee, didn't work. Still can't access recovery or download mode (only see fastboot text, but not the normal download mode text).
UPDATE #2: After capture a freeze frame of my screen during boot to recovery, I noticed it says I have a secure boot certification error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
UPDATE #3: Not sure that download mode is working since all I get this...
UPDATE #4: AutoRec solved part of my issue, but now I'm stuck on TWRP 2.7.0.0 and can't upgrade recovery without getting myself right back to where I was stuck.
UPDATE #5: I was able to install TWRP via XDABBEB's 26a bootstack and then installed his vs982.5 ROM. I don't want to see if upgrading TWRP any further brings the problem back, so I'll consider this issue "closed" for now. Thanks for all your help!

How about using adb from a normally booted state with usb debugging enabled to dd write the previous version (2.8.3.0) of twrp? Either place the 2.8.3.0 recovery.img on the sdcard using mtp or adb push. Then...
adb shell
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p15
exit
adb reboot recovery
Seems like a workable plan.

iowabowtech said:
How about using adb from a normally booted state with usb debugging enabled to dd write the previous version (2.8.3.0) of twrp? Either place the 2.8.3.0 recovery.img on the sdcard using mtp or adb push. Then...
adb shell
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p15
exit
adb reboot recovery
Seems like a workable plan.
Click to expand...
Click to collapse
Thanks for the response! I've got developer options enabled, usb debugging on, recovery.img extracted from 2.8.4.0 on sdcard, used cmd prompt running as admin get to adb folder....typed in your commands and got the daemon successfully started prompt, and then "dd: /dev/block/mmcblk0p15: permission denied" after I wrote exactly what you said to.

CNordy said:
Thanks for the response! I've got developer options enabled, usb debugging on, recovery.img extracted from 2.8.4.0 on sdcard, used cmd prompt running as admin get to adb folder....typed in your commands and got the daemon successfully started prompt, and then "dd: /dev/block/mmcblk0p15: permission denied" after I wrote exactly what you said to.
Click to expand...
Click to collapse
You many need to evoke su following adb shell...
adb shell
su
If you get a # prompt, then continue as before. And as I said, I'd use 2.8.3.0 instead. I've seen a few accounts of people having issues with 2.8.4.0. Not sure if it was perhaps compiled using a newer kernel or just flukes.

iowabowtech said:
You many need to evoke su following adb shell...
adb shell
su
If you get a # prompt, then continue as before. And as I said, I'd use 2.8.3.0 instead. I've seen a few accounts of people having issues with 2.8.4.0. Not sure if it was perhaps compiled using a newer kernel or just flukes.
Click to expand...
Click to collapse
Didn't fix it. I was successful in following your instructions, but reboot gave me the same fastboot-looking text real quick in the corner before getting a blank screen. Upon trying to boot into recovery using the volume down + power button, I can get the factory reset page where you push power button twice, but then it goes to a blank screen again.

Will AutoRec do anything or mess anything up if I try it? I'm worried when it says downgrade bootloader. Bootloader and 12B baseband is the same thing right?

CNordy said:
I'm on a VS980 running crDroid LP ROM (therefore with 12B).
I had TWRP 2.8.1.0 I believe and tried upgrading to 2.8.4.0 by downloading/flashing thru Flashify. It looked like it successfully installed, but then when I rebooted into recovery, I got the LG logo screen with small text in the upper left corner (looked like fastboot text) for a split second before getting stuck on a black screen. Can only hard reset with power button back into ROM. I tried 2.8.3.0 thru Flashify to see if it was just a problem with the newest version. Same issue. Finally, I tried using the LG G2 Toolkit v1.5 program via USB to install 2.7.0.0 and I still get the same issue happening.
I have no idea what messed up, but it seems I've lost recovery. Ideas to get it back? Although my phone works, I can't change/backup/restore my ROM right now...Help would be appreciated!
Click to expand...
Click to collapse
I hade the exakt samme prob... Just flash back your old recovery (the samme version using odin)

iGordy101 said:
I hade the exakt samme prob... Just flash back your old recovery (the samme version using odin)
Click to expand...
Click to collapse
So flash exactly 2.8.1.0 (which is the one I think I had before I got the issue)? odin meaning....?

CNordy said:
So flash exactly 2.8.1.0 (which is the one I think I had before I got the issue)? odin meaning....?
Click to expand...
Click to collapse
Yes get Twrp for your model and flash it using ODIN
This is a hos to on YouTube http://youtu.be/Asx-v2W7S7w
Good luck!

iGordy101 said:
Yes get Twrp for your model and flash it using ODIN
This is a hos to on YouTube http://youtu.be/Asx-v2W7S7w
Good luck!
Click to expand...
Click to collapse
Isn't ODIN for Samsung phones only? LG phones use something else that's similar like kdz or tot files, but would put me back at stock and erase everything I think....maybe I'm wrong. Maybe someone else can chime in.

Ahaa i have a note 4 so that is what i did.. And only recovery was installed everything else was still ready.. Soo you just need to flash your old Recovery version and im sure it vill boot. Just find a way, m8.. Im new and learning about android

Yea, haha. I've tried installing different versions of recovery though. So I'm thinking it's not the recovery itself, but something with the partitions or the way the phone knows how to boot into recovery that's messed up.

CNordy said:
Yea, haha. I've tried installing different versions of recovery though. So I'm thinking it's not the recovery itself, but something with the partitions or the way the phone knows how to boot into recovery that's messed up.
Click to expand...
Click to collapse
I'll now explain on how exactly everything went for me. (I'm Swedish so therefore ask your pardon for my bad english)
1. I have TWRP v2.8.1 all good, but then when I installed TWRP manager from Google Play, I was then told that there was a TWRP update and so I updated.
2. rebooted the phone immediately went into Download Mode, no matter what i did I ended up into Download Mode.
3. I the downloaded odin installed TWRP different but the same problem occurred, the cell phone could start after flash via Odin but then when you disconnect the USB and restart, it went directly to the download mode again. so i had an idea to test the version I had before, and only that same twrp version could fix my problem! Sorry again for my bad english!

A fellow Swede!...well, I'm an American, but mostly Swedish heritage. I appreciate the effort, but I don't think that's going to work on an LG phone. I'll try going back to my old version, but so far no matter what version I try, I can't get into recovery. Even download mode seems broken since I only get fastboot commands that show up and then it sits there doing nothing.

iGordy101 said:
I'll now explain on how exactly everything went for me. (I'm Swedish so therefore ask your pardon for my bad english)
Oh, okey but sorry i could help you.. Hoppe you found a cure!
---------- Post added at 04:37 AM ---------- Previous post was at 04:33 AM ----------
CNordy said:
A fellow Swede!...well, I'm an American, but mostly Swedish heritage. I appreciate the effort, but I don't think that's going to work on an LG phone. I'll try going back to my old version, but so far no matter what version I try, I can't get into recovery. Even download mode seems broken since I only get fastboot commands that show up and then it sits there doing nothing.
Click to expand...
Click to collapse
Oh, sorry i was not so big of a help bu i hoppe o find a cute freind!
Click to expand...
Click to collapse

Update to my situation posted in post #1. It's a secure boot certification error. How do I fix this?

CNordy said:
Update to my situation posted in post #1. It's a secure boot certification error. How do I fix this?
Click to expand...
Click to collapse
have you try go back to your stock through download mode?
at least if you still can enter download mode, maybe you can try to back to your stock first,
just afraid if your system's script was changed due to some errors and that's why it prevent further change into your bootloader. similar case happened to me, but for me it was my booting way script that makes my nav bar disappear, no matter how many kind of ROMs I used, the problem still there until my phone goes back to stock, lost everything inside (internal data, recovery) and gladly lost the problem too...

What do you see when you try to boot into download mode? Fastboot screen? Other?

iowabowtech said:
What do you see when you try to boot into download mode? Fastboot screen? Other?
Click to expand...
Click to collapse
Sorry for being blurry, but I was trying to use my laptop's camera since I can't screen capture. Download mode shows the download mode blue dots or whatever and then it switches to this fastboot message and nothing happens beyond this.

Rei Zazie said:
have you try go back to your stock through download mode?
at least if you still can enter download mode, maybe you can try to back to your stock first,
just afraid if your system's script was changed due to some errors and that's why it prevent further change into your bootloader. similar case happened to me, but for me it was my booting way script that makes my nav bar disappear, no matter how many kind of ROMs I used, the problem still there until my phone goes back to stock, lost everything inside (internal data, recovery) and gladly lost the problem too...
Click to expand...
Click to collapse
I have not tried reverting to stock because I didn't want to erase my sdcard yet if I didn't have to. I'd rather fix my recovery/bootloader and just change my ROM like normal.
Does anyone know if AutoRec will fix my issue? Or can it make things worse because it's made for KitKat and I'm on Lollipop (using a 12B baseband)?

Related

Unbrick method.

So you've bricked your phone. Well as long as the boot loader works then your "brick" is just a soft-brick. Follow this simple guide and flash a custom rom in a couple of minutes. I am not claiming ownership of this method, but its the first time Ive seen it and it helped me so here Good Luck!
Download the attachments.
Unzip both files to a folder on your desktop.
Run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
Need any additional help? Feel free to ask This should work on all Moto G models that have a TWRP image and have a bootloader unlocked.
eg0097 said:
So you've bricked your phone. Well as long as the boot loader works then your "brick" is just a soft-brick. Follow this simple guide and flash a custom rom in a couple of minutes. I am not claiming ownership of this method, but its the first time Ive seen it and it helped me so here Good Luck!
Download the attachments.
Unzip both files to a folder on your desktop.
Run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder. Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
Need any additional help? Feel free to ask This should work on all Moto G models that have a TWRP image and have a bootloader unlocked.
Click to expand...
Click to collapse
Everything went well till step 5.
In terminal window of phone i could find select..... but after that how to proceed I donot know.......... what commands should i use on TWRP terminal...........
Phone didn't get detected in ADB even in TWRP terminal
pl. help
subodhverma21 said:
Everything went well till step 5.
In terminal window of phone i could find select..... but after that how to proceed I donot know.......... what commands should i use on TWRP terminal...........
Phone didn't get detected in ADB even in TWRP terminal
pl. help
Click to expand...
Click to collapse
TWRP termnal is just so that your phone will connect as adb to your pc.
eg0097 said:
TWRP termnal is just so that your phone will connect as adb to your pc.
Click to expand...
Click to collapse
my problem got resolved.........
actually driver was the only problem which was not allowing ADB to detect device in RECOVERY mode, though device was detected in FASTBOOT mode
So I reinstall the driver to get ADB Interface installed in system> device manager
and then followed your remaining steps i.e. 6 onwards
Thanks a lot.....
Not really sure about the following, but I hard-bricked my phone while rooting it a few days ago. Black screen, phone wasn't visible in ADB / fastboot, LED didn't change after plugging in the charger etc.
The only thing that helped: holding the power button for at least 2 minutes. The device restarted afterwards w/o any issues.
Can't find the source of it anymore ...
Very useful guide, I revived my soft - bricked Moto G
still not working
on my xt1032 moto g 16gb version I just have the warning screen that the bootloader is unlocked.
followed a lot threads but nothing helped till now.
tried your verswion and from point 1 to 7 all went well.
But I can't flash the rom. i've tried out about 6 various rom's but everything it says fail. on the screen in the twrp always stands unable to mount /data /system /storage
what can I do to fix this problem?
sascha-1102 said:
on my xt1032 moto g 16gb version I just have the warning screen that the bootloader is unlocked.
followed a lot threads but nothing helped till now.
tried your verswion and from point 1 to 7 all went well.
But I can't flash the rom. i've tried out about 6 various rom's but everything it says fail. on the screen in the twrp always stands unable to mount /data /system /storage
what can I do to fix this problem?
Click to expand...
Click to collapse
|Could someone help please? I am in the same boat and when try to run the above command, I also get this error and no file appears in the sdcard hence cant flash it.
Thanks
My Moto G is working again since one week with stock 4.4.2. I had to do it ain a bit different way...
First, I could get into bootloader and recovery. after several hours my pc recognizes my phone again, but till now I don't know why and how.
Wanted to reflash stock 4.4.2 kitkat again, but this won#t work. so I figured out that after unpacking, I had to replace the gpt.bin with the one from the 4.4.4 stock update. (see down as zip file)
Then I flashed the 4.4.2 stock again to my phone and all went well. It started again. (now I'm on stock recovery)
If you want to do the OTA 4.4.4 Update, there have to be a few things on your phone, otherwise update always fails.
1. if you have x-posed frameworks installed - uninstall it completely
2. if rooted, go into super su preferences and activate unroot all
3. do not activate developper options, or if done before, just uncheck the mark
4. you must be on stock recovery!
5. restart your phone
6. now search after update in about phone.
if bootloader is unlocked - doesn't matter - can stay unlocked
with me it first installed the 176.* OTA because my flashed stock was still 175.*
this went well, then again searched for update and 210.* (4.4.4 kitkat) could be downloaded ota. after it was done, click to install and it should work well - took a bit time.
now you are on stock 4.4.4, but without root atm.
if you want root back - now flash the newest twpr recovery 2.7.7.1 to phone, because here an OTG USB stick will be also recognized - OTG cable needed before. (don't need to push files first to phone)
copied before the su.zip to usb stick and sticked it to phone, then go into recovery. here you can install super user or better su.zip. restart phone and you got your root back on 4.4.4 stock kitkat rom
I solved this issue with twrp sideload.It worked great.
Thanks it worked for me..BUT !!!
Hi and thanks a lot.. it worked for me but you have to add some more option for who are still having troubled in unbricking. like i had..
but it can't be done without your method as on OP..
how i got bricked !!! my Moto g dual (indian)
i tried to downgrade from 4.4.4 to 4.4.2 to flash custom Rom and got system partition corrupt.
again i tried to flash stock images but no use, actual problem was System and data was not formatting.
even if you try million times and you can never successfully flash stock images without error..
however i was checking many threads in xda to resolve this problem but couldn't figured it out, as i was not new to XDA i had confidence that i can come out from this issue. until this thread gave me a hint but not a solution but still this thread is a part of the solution
let come to the unbricking method (only for those who cant flash Stock firmware from fastboot)
Reboot to fastboot..
flash Philz recovery first. get it from here.. http://forum.xda-developers.com/showthread.php?t=2639626
better to use Kernel Flasher by my old buddy Ghostfreak NB http://forum.xda-developers.com/showthread.php?t=2214724,
you just need to extract and copy the recovery to extracted kernel Kernel_Flashing_Tool_v2.0 in IMG folder and run kernel Kernel_Flashing_Tool_v2.0.bat.
press 1 and it will flash recovery, press enter it will reboot to Philz recovery,
now format System, data and whatever you can!!\
next reboot to Bootloader from Recovery,
and then follow procedure as OP
if you want to flash stock rom get from here http://forum.xda-developers.com/moto-g/development/4-4-3-moto-g-stock-rom-t2804891 and adb push as advise by OP. now you have stock rom running without any issues
Edit..
You can also flash custom ROMs with ease.
Note you better flash recovery through kernel flasher tool..
Ysharief said:
Hi and thanks a lot.. it worked for me but you have to add some more option for who are still having troubled in unbricking. like i had..
but it can't be done without your method as on OP..
how i got bricked !!! my Moto g dual (indian)
i tried to downgrade from 4.4.4 to 4.4.2 to flash custom Rom and got system partition corrupt.
again i tried to flash stock images but no use, actual problem was System and data was not formatting.
even if you try million times and you can never successfully flash stock images without error..
however i was checking many threads in xda to resolve this problem but couldn't figured it out, as i was not new to XDA i had confidence that i can come out from this issue. until this thread gave me a hint but not a solution but still this thread is a part of the solution
let come to the unbricking method (only for those who cant flash Stock firmware from fastboot)
Reboot to fastboot..
flash Philz recovery first. get it from here.. http://forum.xda-developers.com/showthread.php?t=2639626
better to use Kernel Flasher by my old buddy Ghostfreak NB http://forum.xda-developers.com/showthread.php?t=2214724,
you just need to extract and copy the recovery to extracted kernel Kernel_Flashing_Tool_v2.0 in IMG folder and run kernel Kernel_Flashing_Tool_v2.0.bat.
press 1 and it will flash recovery, press enter it will reboot to Philz recovery,
now format System, data and whatever you can!!\
next reboot to Bootloader from Recovery,
and then follow procedure as OP
if you want to flash stock rom get from here http://forum.xda-developers.com/moto-g/development/4-4-3-moto-g-stock-rom-t2804891 and adb push as advise by OP. now you have stock rom running without any issues
Edit..
You can also flash custom ROMs with ease.
Note you better flash recovery through kernel flasher tool..
Click to expand...
Click to collapse
I get this error
When im typing adb push AOSP ( i renamed to that name ) /sdcard/ attacks me this: not found. Any help?:crying: Plez :c
eg0097 said:
So you've bricked your phone. Well as long as the boot loader works then your "brick" is just a soft-brick. Follow this simple guide and flash a custom rom in a couple of minutes. I am not claiming ownership of this method, but its the first time Ive seen it and it helped me so here Good Luck!
Download the attachments.
Unzip both files to a folder on your desktop.
Run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder.
Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
Need any additional help? Feel free to ask This should work on all Moto G models that have a TWRP image and have a bootloader unlocked.
Click to expand...
Click to collapse
I haven't actually bricked my phone but looks like my ROM.
So, I am trying to make a ROM previously in First Built the ROM didn't even wrote System [That was my fault as I wrote the the 'system' folder in Zip as 'System' and in update scripts 'system' to be extracted in '/system']
But , now the ROM has written /system but remains on Warning Boot loader Locked screen and starts to warm up I have tried Installing Kernels to fix it but no luck please help.
Device->Moto G Falcon XT1033
ROM Details->Custom ROM based on stock 5.1
Priority of problem->5 ,as I use MultiRom and have this Custom ROM as Secondary and CM 13 as primary ,but suggest a fix ASAP .
@Sid_Sun - Flash the latest factory firmware image for your model. Once that boots, proceed to custom ROMs if desired.
Factory Firmware Image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
@Sid_Sun - Flash the latest factory firmware image for your model. Once that boots, proceed to custom ROMs if desired.
Factory Firmware Image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
My device is booting up I am trying to make a ROM which is not booting and the booting method is by MultiRom the not booting ROM is as secondary so I can use CM 13 as primary but not boot my Custom ROM I want a fix to that issue.
Sid_Sun said:
My device is booting up I am trying to make a ROM which is not booting and the booting method is by MultiRom the not booting ROM is as secondary so I can use CM 13 as primary but not boot my Custom ROM I want a fix to that issue.
Click to expand...
Click to collapse
The MultiROM thread would be the place to ask:
http://forum.xda-developers.com/moto-g/development/modmultirom-v30wip08-01-2014-t2997071​
I have no experience with MultiROM, but I believe a Kernel with kexec-hardboot support is required.
lost101 said:
The MultiROM thread would be the place to ask:
http://forum.xda-developers.com/moto-g/development/modmultirom-v30wip08-01-2014-t2997071​
I have no experience with MultiROM, but I believe a Kernel with kexec-hardboot support is required.
Click to expand...
Click to collapse
This isn't MiltiRom's Fault probably but nvm I will flash The Custom ROM as primary and see how it goes .
Friend in step 3 you say "Run the adb setup file and press (Y) all 3 times." But what is the file?
In the list there are only 2 to download files
adb-setup-1.3.zip
twrp.zip
Where do i put the command in the 4th step?
Please help

HELPPPP LG G2 black screen but phone is still ON

alright fixed the problem
but after flashin KDZ , i have this line in my screen!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
freshbooy said:
guys just check out the video and help me plzzzzzzz
:crying::crying::crying::crying:
Click to expand...
Click to collapse
Are you full on stock?
Did you rooted your phone?
What did you do before it went like that?
Are you flashing custom roms? Maybe that you are now on a custom stock rom?
I saw that the screen was also showing later LG logo which is a good sign that it's probably caused software related. If you have custom recovery then I suggest to flash another custom rom.
If you have not rooted it/no custom recovery then I suggest to download the firmware for your phone and flash it with the lg flashing software.
wulsic said:
Are you full on stock?
Did you rooted your phone?
What did you do before it went like that?
Are you flashing custom roms? Maybe that you are now on a custom stock rom?
I saw that the screen was also showing later LG logo which is a good sign that it's probably caused software related. If you have custom recovery then I suggest to flash another custom rom.
If you have not rooted it/no custom recovery then I suggest to download the firmware for your phone and flash it with the lg flashing software.
Click to expand...
Click to collapse
i was on Lollipop vanir and then wrongly wiped everything and the tried to flash vanir again and then git an error and then rebooted the phone and it goes like this
i can see the LG logo and i can go to download mod , but no recovery mods
is there anyway to flash recovery via download mode?
freshbooy said:
i was on Lollipop vanir and then wrongly wiped everything and the tried to flash vanir again and then git an error and then rebooted the phone and it goes like this
i can see the LG logo and i can go to download mod , but no recovery mods
is there anyway to flash recovery via download mode?
Click to expand...
Click to collapse
Well if you cant boot into recoverymode you can still maybe to try to install recovery with adb if your phone is getting detected else you have to flash stock again completely on downloaf mode.
If you can get into download mode, you've got a way out by means of flashing a kdz (or tot) to return it to a stock firmware. Then you'll have to root again and whatnot but your phone will be saved. You can't really flash just a recovery from download mode, it's either full stock or nothing. That's why some developers like to wipe the laf partition so that you boot into fastboot instead, where recovery can be flashed. But at this point you really don't have that option, so I would suggest finding the right kdz for your variant, and the LG flash tool, and restoring it to stock. There are numerous guides on here. No need to panic, if you're able to get into download mode your phone should be fully recoverable with this method. It's a bit of a pain, and it will wipe your storage, but you'll save your phone.
wulsic said:
Well if you cant boot into recoverymode you can still maybe to try to install recovery with adb if your phone is getting detected else you have to flash stock again completely on downloaf mode.
Click to expand...
Click to collapse
when i use adb , it shows the phone Offline
so i cant do anything with adb
DHM078 said:
If you can get into download mode, you've got a way out by means of flashing a kdz (or tot) to return it to a stock firmware. Then you'll have to root again and whatnot but your phone will be saved. You can't really flash just a recovery from download mode, it's either full stock or nothing. That's why some developers like to wipe the laf partition so that you boot into fastboot instead, where recovery can be flashed. But at this point you really don't have that option, so I would suggest finding the right kdz for your variant, and the LG flash tool, and restoring it to stock. There are numerous guides on here. No need to panic, if you're able to get into download mode your phone should be fully recoverable with this method. It's a bit of a pain, and it will wipe your storage, but you'll save your phone.
Click to expand...
Click to collapse
btw i do all of these steps:
http://forum.xda-developers.com/showthread.php?t=2582142
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
and i tried flashing twrp and philz but , after i reboot the phone and connecting all connectors , still no recovery
can u tell me exactly about g2 fastboot mode ? because its so easy to flash boot from fastboot mode and thenflashinf the rom again
freshbooy said:
btw i do all of these steps:
http://forum.xda-developers.com/showthread.php?t=2582142
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
and i tried flashing twrp and philz but , after i reboot the phone and connecting all connectors , still no recovery
can u tell me exactly about g2 fastboot mode ? because its so easy to flash boot from fastboot mode and thenflashinf the rom again
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2432476
Try this instead, Btw did you already got your display back working in the stock rom?
Also, I believe that your phone is rooted try to reboot into recovery with root.
Try to flash the first time the recovery etc with Autorec and then flash the newer TWRP from here. You can use the one from Dees_troy but I suggest to maybe use blastagator's version instead as it got some safety things also built-in.
Well the problem is that you just can't normally boot into the fastboot mode without any mods or what. And those mods are just going to give you more a pain in the ass so yeah I suggest to get it normally working. We maybe will have normal access to fastboot once LG will give us a unlocking method. I am also missing sometimes the Fastboot which I had on my N4 but still you don't practically need fastboot if you got basic knowledge and a working twrp then nothing could go wrong.
wulsic said:
http://forum.xda-developers.com/showthread.php?t=2432476
Try this instead, Btw did you already got your display back working in the stock rom?
Also, I believe that your phone is rooted try to reboot into recovery with root.
Try to flash the first time the recovery etc with Autorec and then flash the newer TWRP from here. You can use the one from Dees_troy but I suggest to maybe use blastagator's version instead as it got some safety things also built-in.
Well the problem is that you just can't normally boot into the fastboot mode without any mods or what. And those mods are just going to give you more a pain in the ass so yeah I suggest to get it normally working. We maybe will have normal access to fastboot once LG will give us a unlocking method. I am also missing sometimes the Fastboot which I had on my N4 but still you don't practically need fastboot if you got basic knowledge and a working twrp then nothing could go wrong.
Click to expand...
Click to collapse
the problem is for downloading 1.6Gb i have to wait 4hrs!
is there anyway instead of that?
on my last sony z , when it breaks , i go fastboot and flash recovery and then rom . why its so hard for lg g2
and tell me the way that u put this ****ty device in fastboot mode
i really want to try it out
freshbooy said:
the problem is for downloading 1.6Gb i have to wait 4hrs!
is there anyway instead of that?
on my last sony z , when it breaks , i go fastboot and flash recovery and then rom . why its so hard for lg g2
and tell me the way that u put this ****ty device in fastboot mode
i really want to try it out
Click to expand...
Click to collapse
Try to search another faster link for the stock rom.
Calm down with your language :l
Well you have savoca's autoboot. Try that.
The difference is that your sony Z bootloader can be also unlocked and lg not yet.
guys plz check the first post again. i flashed the KDZ and now i have this black line on my screen. is it because i opened the phone for test point or its a software problem?
freshbooy said:
guys plz check the first post again. i flashed the KDZ and now i have this black line on my screen. is it because i opened the phone for test point or its a software problem?
Click to expand...
Click to collapse
Hehh that thing, did it happend after flashing the KDZ or was it already there maybe before your screen was black?
Did you flashed maybe roms before your screen was black or was your phone totally clean, without root etc? Sorry if you have said this before.
Try some stuck pixel app from the playstore and hope for you that it works. The problem is that it could be a hardware issue but we aren't totally sure yet. Just try that app for some time and report back:good: hope it will end up good.

Error mode: error 11 no recovery, error 2 failed to load

Help
I tried to relock my bootloader but when the device restarted it went straight to error mode.
I managed to boot straight back to full system but whenever I restart it goes back to error mode. I cant enter fastboot or recovery mode.
I sont know what to do now any help
Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try to boot it again in the full system and from there try to unlock your bootloader.
If you done that, reinstall the software.
How can I unlock bootloader without fastboot? If I attempt to enter fastboot or anything that requires reboot I end up on that screen.
Hmm....
Have you tried rebooting to fastboot using adb?
Johnny TDN said:
Try to boot it again in the full system and from there try to unlock your bootloader.
If you done that, reinstall the software.
Click to expand...
Click to collapse
Johnny TDN said:
Hmm....
Have you tried rebooting to fastboot using adb?
Click to expand...
Click to collapse
I tried but still get to error mode.....I have tried many times
Then i don't know anymore dude. Have you tried reinstalling the firmware using the 3 button method?
elliotn said:
I tried but still get to error mode.....I have tried many times
Click to expand...
Click to collapse
Hello
tested with the toolkit 0.0.0.12.
to see if he recognizes the phone.
he should at least write your serial number.
if that is the case.
you can use DC-unlocker. to open FRP and can be the bootloader.
just an idea.
Dc unlocker needs cash and it doesn t always work.
I am doubting buying DC,unlocker in case,it doesn't work and I will lose money.... I will try toolkit.
3 button upgrade doesn't work either.
I have the same problem after I tried to relock my bootloader using SRKToolHuawei-STABLE-V1.3-20160619 with my bootloader code.
Have you found a solution?
I can boot back into os b394 after I let the battery run out to 0%
I haven't found a way to repair my recovery and fastboot yet because rebooting into fastboot always get's me back to that first error
Func NO: 11 (recovery image)
Error NO: 2 (load failed!)
Then I have to wait for my battery to run out again
Any help to get fast boot and a working recovery back would be appreciated.
Use Huawei multi tool ,then flash system, custom,recovery image ,
If stock recovery opens then use Dload method
shankarjdhv125 said:
Use Huawei multi tool ,then flash system, custom,recovery image ,
If stock recovery opens then use Dload method
Click to expand...
Click to collapse
I got stock recovery back with the warning that my device is unlocked. Now I get stuck at 'Your device is booting now'. After some time it reboots and opens eRecovery which I cannot use.
How do I get anything on my phone to continue with dload and which firmware would you advice me to flash if I finally get there.
Should I, if even possible at the moment, choose an older firmware version?
Edit: Would the original service rom help? Found it here https://forum.xda-developers.com/huawei-p9lite/help/original-service-rom-huawei-p9-lite-vns-t3688120 but my build number seems too high as the version I need only mentions b381 and b383 not the 394 I currently have..
Same problem for me
No way to shutdown the phone, someone have solved?
Now I'm waiting for the battery to full drain
Hi guys i ve made mistake because i wanted to update to latest release media pad m3 but i could not be able to boot to stock recovery after i flash recovery img extracted from update.app and second time i flash recovery2.img to erecovery partition and i got the same issue error Func No 11(recovery image) and Error NO 2 (load failed) . I also put the update.app to dload folder on sd card but update system is not starting i press volume up and down and power button at same time but is not working.I tried also with huawei multitool but is not working is not recognize my device. Please guys is any other solution to fix this ?Thank You!
I just fixed after power off device and then press volume down and plug the usb cable to pc and i was able to recognize my device and i have use huawei multiTool to unbrick my tablet media pad m3 and has work.
Almost the same problem, help please!!!
Hi guys someone can help me? I have a Honor 9 lite(LLD-L31). Android version 8.0
I apologize but I'm a new user and i don't have much practice with modding in general.
I tried to install root permission in my device. I get bootloader unlock code by DC-unlocker and installed TWPR on my device.
When i went in recovery the error " Failed to unmount '/system'(Device or resource busy)" rushed, so I tried to format data in order to give partition available. I tried again to flash file.zip but the search was empty so I downloaded a most recent version(3.2.3) of TWPR in recovery ramdisk.
Now if i try to log into recovery mode appear the same error (Error! func NO 11 / NO 2).
I can do everything aside going in recovery mode. How can I resolve it? Is it possible to reset to factory settings and try again?
I hope I have explained well the problem.
elliotn said:
3 button upgrade doesn't work either.
Click to expand...
Click to collapse
how about this 3 button method??
Astarothkun said:
I got stock recovery back with the warning that my device is unlocked. Now I get stuck at 'Your device is booting now'. After some time it reboots and opens eRecovery which I cannot use.
How do I get anything on my phone to continue with dload and which firmware would you advice me to flash if I finally get there.
Should I, if even possible at the moment, choose an older firmware version?
Edit: Would the original service rom help? Found it here https://forum.xda-developers.com/huawei-p9lite/help/original-service-rom-huawei-p9-lite-vns-t3688120 but my build number seems too high as the version I need only mentions b381 and b383 not the 394 I currently have..
Click to expand...
Click to collapse
Could you write down the steps you took to get back in fastboot for me? I'm having troule geting there myself after draining battery.
I fixed it after nothing else here worked.
So this is mostly so I dont ever forget the solution again, but also to possibly help others.
I also have to say that I had the problem with an P8 Lite, but all my problems matched almost exaclty, so It might help you too.
And a third disclaimer: I have no idea if you can flash the stock firmware without having the bootloader unlocked.
If you dont have it unlocked, try this wonderful updated guide: [Links are disabled for me so google this: "Droidhunter unlock huawei bootloader" and pick the article by droithunter.com]
And yes DC-Unlocker, suprisingly actually works (at least for me) and buying their bootloader unlock code was worth the 4 bucks.
So here is the solution:
1. Somehow, however needed get into fastboot. As I couldn't use the volume/power key combo myself, I somehow force reset the phone, pressing various buttons until I managed to boot into it again. I then used the adb bridge to boot into fastboot (google how to connect adb, then use "adb reboot bootloader" to get into the fastboot menu).
2. Download your phone models default stock rom/Update.app (also google that).
3. Extract the Update.app file.
4. Download and use the HuaweiUpdateExtractor tool and open the Update.app file (google again helps).
5. Select the "09.recovery.img" entry (the one with the green arrow on the left), rightclick and select "extract selected" and save it somewhere where you can find it.
6. Open your Fastboot console on PC (its often the same as the ADB console used before, especially if you use Minimal Fastboot and ADB, which I would recommend).
7. Make sure your phone is in Fastboot mode (not recovery) and connected to the pc.
7.1 Make sure your bootloader is unlocked. It might work with a locked one because youre just flashing stock firmware but eh might break more. Its worth the 4 bucks to unlock the bootloader first. (and yes DC unlocker looks super sketchy but somehow it actually worked for me and wasnt a scam).
8. Flash a custom recovery onto the phone (pretty much the same way you flash twrp, but instead of the twrp image you use the .img file you just extracted from the Update.app; Also dont try flashing twrp directly, it will probably not work).
The command to do so is: "fastboot flash recovery [filepath to the .img file without the brackets]".
9. Use the command "fastboot reboot".
10. If your phone doesnt boot normally, use the key combinations to get into the normal recovery screen and recover from a file or whatever (other guides should work from here).
Extra Steps:
As my recovery image was obviously so broken that even flashing twrp on top of it didnt work until I flashed the original reovery image, I went into my phones settings and did a factory reset. Directly after I installed twrps (see google) and set it up so it had full control. Afterwards I rooted and installed LinageOS cause frick EMUI rn).
Hope this helps anyone. If you have any questions feel free to ask me.

[TWRP & ROOT] Ticwatch E/S & Unroot Instructions for Updates - v003

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DISCLAIMER:
I'm not responsible for any damaged watches or other broken things! All of this is still heavily in development and mainly a developer release, not at all recommended for normal usage!
The following tutorial CAN brick your watch if you're not careful enough! Once again I'm not taking any responsibility!
This has only been tested on Android N so far, Android O is not yet fully tested!​
---------------------------------------------------------
Please read before doing anything:
This is a port of TWRP for the Ticwatch E. Currently we're not able to boot it via fastboot (well, it technically does but there's an issue with the video driver) and when trying to flash it the watch will instantly flash the stock recovery over it upon reboot.
To avoid this we have to do a little workaround! Once you reboot your watch it'll restore the stock recovery again! After following these steps your watch will be stuck in a bootloop which we'll fix too tho.
Please keep the Changelog below in mind and read what's working and what's not before asking. We may or may not have seen this issue before already.
Files you'll need:
v003 of "TWRP for Ticwatch E" (and most likely S) - OneDrive Mirror
Stock Recovery for Ticwatch E (and most likely S) - OneDrive Mirror
ADB and Fastboot drivers installed (I recommend "15 Seconds ADB Installer")
Changelog:
Updated Instructions:
Slightly updated the instructions so you won't lose any data if you're already on an bootloader unlocked watch!
v003 (OneDrive Mirror):
Managed to make TWRP persistent! Check Instructions on how to.
v002 (OneDrive Mirror):
Now includes systemless root package inside the TWRP image so you're able to root your watch!
v001 (OneDrive Mirror):
Initial release, no ADB so far. Can't be booted from fastboot directly either due to weird fastboot behavior and has to be flashed first. However upon normal reboot Mobvoi decided to flash over the stock recovery again so we have to do a workaround.
Instructions:
The new Instructions by Luxios require a few less steps AND if you've already unlocked your watch before you won't even lose data!
Enable ADB in the Developer Settings
Once done connect your watch to your computer and do "adb reboot bootloader"
THIS WILL RESET YOUR WATCH:*Once in fastboot mode type "fastboot oem unlock" (if you already have an unlocked bootloader you [font=Verdana, Arial, Helvetica, sans-serif]can skip this[/font])
Follow the on-screen instructions on your watch to unlock it (if you already have an unlocked bootloader you can skip this)
Reboot via "fastboot reboot" and wait until Android Wear fully starts up
One started reboot to the bootloader via the same command as above
Once the bootloader shows up again type "fastboot flash recovery TWRP_TicwatchE_v003.img"
After that type "fastboot oem reboot-recovery" to reboot to the TWRP recovery
In order to make TWRP persistent you need to go to "Install" > "Install ZIP" > "supersu" > "TicwatchE_TWRP_keeper.zip" and flash it
Upon rebooting you may notice it'll get stuck in an infinite TWRP bootloop. To fix this boot into TWRP, then choose "Reboot" > "Bootloader", back in fastboot type "fastboot boot StockRecovery_TicwatchE.img" and wait a few seconds, a few reboots later Android Wear should start right up again.
If you want to root your watch reboot it once again with "adb reboot recovery" and go to the same folder as above, tho this time flash "SuperSU-2.79-wear_systemless.zip"
Unroot/Remove TWRP for Android O Update:
Go to this thread to also update directly to the last Android O update and revert all customizations: https://forum.xda-developers.com/sm...es/android-o-super-easy-ticwatch-e-s-t3789835
Have fun!
You're the best! I'm gonna try as soon as I can, and let you know.
Ok, I'm trying to flash it.
Problem is, it flashes, but when I do fastboot reboot, it will boot in android wear instead that TWRP.
If then I reboot in the recovery with adb reboot recovery, it will be already the stock recovery again... Any tip?
Piereligio said:
Ok, I'm trying to flash it.
Problem is, it flashes, but when I do fastboot reboot, it will boot in android wear instead that TWRP.
If then I reboot in the recovery with adb reboot recovery, it will be already the stock recovery again... Any tip?
Click to expand...
Click to collapse
If your bootloader is (or was) already unlocked you have to lock and then unlock it again for it to work.
Yes sorry, I noticed that right after posting, but I've bad network.
Now seems to have gone all fine, I'm booting it, I'm only unsure it flashed SuperSU well, since it shown an error at the end of the script, although the rest of the log seemed to report all to go fine.
Piereligio said:
Yes sorry, I noticed that right after posting, but I've bad network.
Now seems to have gone all fine, I'm booting it, I'm only unsure it flashed SuperSU well, since it shown an error at the end of the script, although the rest of the log seemed to report all to go fine.
Click to expand...
Click to collapse
The guy who made it initially did send me a picture of it successfully rooted. Should work, errors can happen since TWRP can't write to all partitions yet.
Sadly it looks like SuperSU failed to root. It gave a data partition mounting error at the end of the script, don't know if it is normal. TWRP isn't able to mount data either.
EDIT: Looks like I found a way to boot TWRP without having to lock/unlock bootloader.
Doing this, I managed to boot TWRP after setting the watch up, and in this way, it didn't fail to mount /data. Let's see...
EDIT2: now SuperSU still fails, but for a different reason. I'm gonna ensure that it failed though.
EDIT3: su command responded, so seems that root works. I'll do some more tests.
TWRP is now persistent! Check the updated guide
Rooting succeeded!
Seems like I managed to root the smartwatch using the version 2. For the moment I'm happy like this, next times I'll indeed use new procedures.
EDIT: Yes, I rooted it.
My steps (the ones on OP are the recommended ones):
-Bootloader unlock;
-Boot in Android Wear to enable ADB from Settings;
-Reboot in bootloader with "adb reboot bootloader";
-Flashed this TWRP v2;
-"fastboot reboot", then "adb reboot recovery" as soon as adb was detected while booting.
In this way I managed to avoid the system to flash stock recovery over TWRP.
By the way, I don't recommend my way of rooting it, it's less safe, just follow the updated instructions in OP.
Huge thanks to @EpicLPer
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
BackCheck said:
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
Click to expand...
Click to collapse
If the watch doesn't turn off even after holding the button for a minute then you've damaged something else than just the recovery. Holding down the button normally triggers all the time no matter what, even if you'd have bricked it.
BackCheck said:
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
Click to expand...
Click to collapse
You can flash again the stock recovery with spflash tool.
EpicLPer said:
If the watch doesn't turn off even after holding the button for a minute then you've damaged something else than just the recovery. Holding down the button normally triggers all the time no matter what, even if you'd have bricked it.
Click to expand...
Click to collapse
I really wish I knew what. All I did was flash a bad recovery, pretty sure something was was wrong with the ram disk. All I get is the splash logo for 3 seconds and a brief vibrate.
Luxios said:
You can flash again the stock recovery with spflash tool.
Click to expand...
Click to collapse
I think I need a scatter file to even get started. I've never used the tool so any other instructions would be greatly appreciated.
Great to hear someone that it is working on this! What about Android Wear updates? Did you try if it is possible to install them using TWRP?
Edit 1: Just tried to install twrp but inside "supersu" folder there is only "SuperSU-2.79-wear_systemless.zip", where can I find "TicwatchE_TWRP_keeper.zip"?
elios93 said:
Great to hear someone that it is working on this! What about Android Wear updates? Did you try if it is possible to install them using TWRP?
Edit 1: Just tried to install twrp but inside "supersu" folder there is only "SuperSU-2.79-wear_systemless.zip", where can I find "TicwatchE_TWRP_keeper.zip"?
Click to expand...
Click to collapse
I have the same problem...
EDIT: I have a Ticwatch S.
Niktendo said:
I have the same problem...
EDIT: I have a Ticwatch S.
Click to expand...
Click to collapse
I've managed to install it anyway. First check if it is not already installed using command
Code:
adb reboot recovery
If it does not work try this after you are in bootloader:
Code:
fastboot flash recovery TWRP_TicwatchE_v003.img
fastboot reboot
Then, as suggested by @Piereligio send this command as soon as possible while the watch is booting:
Code:
adb reboot recovery
This should work
However it is interesting that you have a S model. By sharing the build.prop of your device should be possible unlock all watchfaces for E model for instance!
elios93 said:
I've managed to install it anyway. First check if it is not already installed using command
Code:
adb reboot recovery
If it does not work try this after you are in bootloader:
Code:
fastboot flash recovery TWRP_TicwatchE_v003.img
fastboot reboot
Then, as suggested by @Piereligio send this command as soon as possible while the watch is booting:
Code:
adb reboot recovery
This should work
However it is interesting that you have a S model. By sharing the build.prop of your device should be possible unlock all watchfaces for E model for instance!
Click to expand...
Click to collapse
This is the best way i found to install the TWRP recovery:
- Unlock the boot loader
- Reboot, wait until android start again
- Reboot again in boot loader mode
- flash the twrp v003 recovery
- type:
Code:
fastboot oem reboot-recovery
- Flash the twrp keeper zip package
- flash the root zip package (if you want root)
EpicLPer said:
The guy who made it initially did send me a picture of it successfully rooted. Should work, errors can happen since TWRP can't write to all partitions yet.
Click to expand...
Click to collapse
Can you get me the device tree or at least BoardConfig.mk used for this? I have a working watch (still working on recovering the old one) and I think I can get the rest of the partitions working but I would really like to avoid any more mistakes.
Luxios said:
This is the best way i found to install the TWRP recovery:
- Unlock the boot loader
- Reboot, wait until android start again
- Reboot again in boot loader mode
- flash the twrp v003 recovery
- type:
Code:
fastboot oem reboot-recovery
- Flash the twrp keeper zip package
- flash the root zip package (if you want root)
Click to expand...
Click to collapse
That 'fastboot oem reboot-recovery' command sure is a nice find!
Hey, bought my ticwatch e used online.
The watch is almost new and everything works as it should, but it has these two developer orriented apps preinstalled and can’t be uninstalled via settings neither with a factory reset.
They dont do anything but i just want to remove them
https://photos.app.goo.gl/gTNg5QCPzBtKgnzy1
And yeah the watch also generates a bug report by itself everyday i also want to stop that lol
hassanabid94 said:
Hey, bought my ticwatch e used online.
The watch is almost new and everything works as it should, but it has these two developer orriented apps preinstalled and can’t be uninstalled via settings neither with a factory reset.
They dont do anything but i just want to remove them
https://photos.app.goo.gl/gTNg5QCPzBtKgnzy1
And yeah the watch also generates a bug report by itself everyday i also want to stop that lol
Click to expand...
Click to collapse
Maybe it's a specific developer unit. Don't do anything with it yet, we could loom further into this if it is something special.

phone keeps booting into essentail logo after flashing

i tried to follow every guide but no help. tried flashing back to factory still nothing. first when booting from twrp it would say no OS. i finally got that to go away but now it just keeps booting into android power loop. tried erasing all data nothing helps. it also tells me software is corrupted. can someone help plzzz
dumberthandumb said:
i tried to follow every guide but no help. tried flashing back to factory still nothing. first when booting from twrp it would say no OS. i finally got that to go away but now it just keeps booting into android power loop. tried erasing all data nothing helps. it also tells me software is corrupted. can someone help plzzz
Click to expand...
Click to collapse
go into fastboot mode and do.... fastboot -w
Tech_Savvy said:
go into fastboot mode and do.... fastboot -w
Click to expand...
Click to collapse
I did that and it didn’t work
dumberthandumb said:
I did that and it didn’t work
Click to expand...
Click to collapse
Make sure you have unlocked the bootloader AND unlocked critical partitions, then flash the latest factory image found on essentials support page. DO NOT flash TWRP or anything like that.
Nick80835 said:
Make sure you have unlocked the bootloader AND unlocked critical partitions, then flash the latest factory image found on essentials support page. DO NOT flash TWRP or anything like that.
Click to expand...
Click to collapse
How do I unlock critical partitions? Also I have already flashed TWRP. If I try to push the factory image without TWRP it tells me not enough space.
I suspect you need to change the slot that's loading... I had a similar thing recently. .. Try going into fastboot and typing "fastboot --set-active=slot" where slot is "a" or "b", depending on where you flashed TWRP (you need to load the opposite slot).
If that doesn't work, flash the original boot file in fastboot and keep everything crossed...!
nstirton said:
I suspect you need to change the slot that's loading... I had a similar thing recently. .. Try going into fastboot and typing "fastboot --set-active=slot" where slot is "a" or "b", depending on where you flashed TWRP (you need to load the opposite slot).
If that doesn't work, flash the original boot file in fastboot and keep everything crossed...!
Click to expand...
Click to collapse
My slot b has been fleshed with TWRP and a with the original os. I still can’t get it to boot. Is there anyways that I can just flash everything back to factory setting? I don’t care about personal data. I even tried flashing both slots with the os and still no luck
flash OTA via adb sideload , it will fix your issue
Just do the fastboot flashall from the Essential download page and start over. I flashed the october update the other day and my phone has been running so much better since then.
galakanokis said:
Just do the fastboot flashall from the Essential download page and start over. I flashed the october update the other day and my phone has been running so much better since then.
Click to expand...
Click to collapse
Flash all? How do I get to that? I have tried doing a side load through TWRP but nothing helped
dumberthandumb said:
Flash all? How do I get to that? I have tried doing a side load through TWRP but nothing helped
Click to expand...
Click to collapse
Instructions are on the Essential website where you can grab the downloads. Basically download the fastboot image, unzip it and run the flashall script inside the unzip. Easier if your fastboot path is setup properly. It will flash stock to both slots and away you go.
You NEED to unlock critical partitions to flash all of them.
galakanokis said:
Instructions are on the Essential website where you can grab the downloads. Basically download the fastboot image, unzip it and run the flashall script inside the unzip. Easier if your fastboot path is setup properly. It will flash stock to both slots and away you go.
Click to expand...
Click to collapse
Flash all? How do I do this?
dumberthandumb said:
Flash all? How do I do this?
Click to expand...
Click to collapse
https://www.essential.com/developer/current-builds
galakanokis said:
Instructions are on the Essential website where you can grab the downloads. Basically download the fastboot image, unzip it and run the flashall script inside the unzip. Easier if your fastboot path is setup properly. It will flash stock to both slots and away you go.
Click to expand...
Click to collapse
I tried doing that it flashes and everything but it till wont boot up, its still stuck on the essential logo.
when i try to go into recovery mode it says no command
dumberthandumb said:
I tried doing that it flashes and everything but it till wont boot up, its still stuck on the essential logo.
when i try to go into recovery mode it says no command
Click to expand...
Click to collapse
You can see it flash both slots and all the images? Should be able to get a screen grab of it.
If your environment is setup correctly and you say it flashes I can't be of much help unfortunately.
dumberthandumb said:
I tried doing that it flashes and everything but it till wont boot up, its still stuck on the essential logo.
when i try to go into recovery mode it says no command
Click to expand...
Click to collapse
Seems you don't know how to boot into recovery,when you see this Android guy you need to press volume up and power.
Hi, can someone help me with this problem?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
galakanokis said:
You can see it flash both slots and all the images? Should be able to get a screen grab of it.
If your environment is setup correctly and you say it flashes I can't be of much help unfortunately.
Click to expand...
Click to collapse
Thank you I finally got it to work, Apparently only my boot loader was unlocked and I did not have critical partitions unlocked, ones I unlocked critical partitions the flash I was able to go through
Thank you everyone for your help
nibera said:
Hi, can someone help me with this problem?
View attachment 4612857
Click to expand...
Click to collapse
Do you have creitical partitions unlocked ?

Categories

Resources