Hello there,
I am sharing the YU Yureka CM12 Flashable Factory Image Fastboot
use factory images with adb drivers for flashing with pc .
Download Links-----> 1. Factory Image Fastboot zip---> https://drive.google.com/file/d/0B0_IwOvcRE4gcUpnSmVjdDAzOE0/view?usp=sharing
2. Flashing tools---->https://drive.google.com/file/d/0B0_IwOvcRE4gcnNHcF9wNDcxRGs/view?usp=sharing
OR
3. LATEST FASTBOOT ZIP adb 1.2--> https://drive.google.com/file/d/0B1S0LCuXCnnmOWhnUk1ZWVdQakE/view?usp=sharing
Procedure:
1. Download these both zips.
2.Open Flashing tools zip and extract to any place.
3.Open the Factory image and extract it into the flashing tools folder
4.Now open the flashing tools folder
5Switch of the Phone
6.Press Volume Up button and connect to PC or Laaptop, The Phone will be boot in BootLoader (FastBoot Mode)
Connect phone with PC or laptop
7.Open The Flashtool Folder then Select Flash-all.bat , Run as Administrator.
8.Installation will start automatically, all the images will flas and once it will completed
9.Disconnect phone from pc
10.Switch it on the phone and it take some time to load first boot , be patient and you are done. !!
Please Hit Thanks for help me to Increase the THANKS Meter... !!!!
haed brick problems
ive seen on yu forums that many people have bricked their devices using the fastboot method. have you personaly tried this method?
no, but i have collected these info from forum. let we wait for reviews. but i think this would be work
rohitjaiswal said:
no, but i have collected these info from forum. let we wait for reviews. but i think this would be work
Click to expand...
Click to collapse
doomlord has posted to wait for the official instructions to flash using fastboot as many people have bricked their devices.
YES, we have to wait.
I think Bootloader can't be replaced from Fastboot. That is why people flashing CM12 first time through Fastboot are bricking their devices. Once updated through OTA or manually through stock recovery, I think fastboot flashing of CM12 will work fine, but not on CM11 (32 Bit Bootloader)
worked for me!
but, i should put a disclaimer here: i had soft bricked my device while upgrading to lollipop using the stock recovery and the OTA zip.
my phone used to show the YU logo, and switch off itself, I couldnt even go into the recovery. I could only get into the fastboot mode.
I downloaded the files and followed the instructions, and then my phone atleast showed the CYANOGEN logo. But it wouldnt start. I discovered that I could atleast go into the recovery mode, from where I flashed the OTA zip, and voila, the device boots!
BTW, i managed to get my device into a bootloop a short while later. so i flashed the entire zip using fastboot, and didnt relock the bootloader. it works!
worked for me too
i first updated from cm11 to cm12 using ota
then i can install cm12 using this zip easily
does it really worked mate?
xx88 said:
but, i should put a disclaimer here: i had soft bricked my device while upgrading to lollipop using the stock recovery and the OTA zip.
my phone used to show the YU logo, and switch off itself, I couldnt even go into the recovery. I could only get into the fastboot mode.
I downloaded the files and followed the instructions, and then my phone atleast showed the CYANOGEN logo. But it wouldnt start. I discovered that I could atleast go into the recovery mode, from where I flashed the OTA zip, and voila, the device boots!
BTW, i managed to get my device into a bootloop a short while later. so i flashed the entire zip using fastboot, and didnt relock the bootloader. it works!
Click to expand...
Click to collapse
I wish i couldn't ended with hard brick?
:good::good:
Thanks...I can do this successfully...Thanks...Again
:good: Thanks Thanks Thanks Mate
It Worked..... I Just Followed the Instuctions.
You Saved My Ass Bro Thanks a Lot Again.
Back on CM12S after Soft Brick While Rooting CM12S
abhisheksahota said:
It Worked..... I Just Followed the Instuctions.
You Saved My Ass Bro Thanks a Lot Again.
Back on CM12S after Soft Brick While Rooting CM12S
Click to expand...
Click to collapse
same here !
But, still can't root
[email protected] said:
:good::good:
Thanks...I can do this successfully...Thanks...Again
Click to expand...
Click to collapse
Just Hit Thanks button which is on my post. Your compliment will be appreciated
prince.d.emperor said:
same here !
But, still can't root
Click to expand...
Click to collapse
Just Hit Thanks button which is on my post. Your compliment will be appreciated
prince.d.emperor said:
same here !
But, still can't root
Click to expand...
Click to collapse
Just Hit Thanks button which is on my post. Your compliment will be appreciated
abhisheksahota said:
It Worked..... I Just Followed the Instuctions.
You Saved My Ass Bro Thanks a Lot Again.
Back on CM12S after Soft Brick While Rooting CM12S
Click to expand...
Click to collapse
Just Hit Thanks button which is on my post. Your compliment will be appreciated
Rooting ???
Please find out a way for rooting also? It will be very appreciable.
abhisheksahota said:
Please find out a way for rooting also? It will be very appreciable.
Click to expand...
Click to collapse
http://forum.xda-developers.com/yureka/orig-development/recovery-yureka-arm64-t3084714
Download the twrp and install the recovery then dowbload su 2.46zip and flash it.
I confirm this works.
I hard bricked my YUreka somehow and somehow I managed to boot it into fastboot mode.
Then I executed above attached script with deleted bootloader lock/unlock lines.
Thanks for the link buddy. You just saved the day.
moddlerlotes said:
I confirm this works.
I hard bricked my YUreka somehow and somehow I managed to boot it into fastboot mode.
Then I executed above attached script with deleted bootloader lock/unlock lines.
Thanks for the link buddy. You just saved the day.
Click to expand...
Click to collapse
Just Hit Thanks button which is on my post. Your compliment will be appreciated
Related
Edit: I remove the root file,. But I will share my rooted images.
Rooted Image Download(five partitiones, boot.img, firmware.img, baseband.img, recovery.img and system.img)
Just only a few steps, If my guidiance help you out, Please hit thanks button
1. If you are using a rooted firmware(any one can do) , you can jump to step 2. Or, install v18f(leaked 4.0.3 ics) and root it with TPSparkyRoot tool.
2.Press and hold power and volume- button, enter LG's recovery, press power button twice to process a factory reset. reboot, then enable usb debug, connect your PC and P930 with usb cable, download attachement file(all-purpose-ROOT.rar ). Extract it and run before.bat file.
3. Flash V20c_00.kdz. you can follow this http://forum.xda-developers.com/showthread.php?t=1597488 guide to finish this step.
4. After V20c installed, you phone will reboot and stuck in at&t's logo, but don't worried, run after-KDZ-flashed.bat(need usb connected to pc of course) . You can see informations of rooting success Awared: do not process factory reset until you run after-KDZ-flashed.bat! It is very important!
5. Factory reset again then you will get a rooted V20c, Enjoy it.
Basically, this script can help you jump from any rooted firmware to any other one and root it! that is why I suggest to install v18f, because it is easy to flash and root.
View attachment 1227309
View attachment 1227311
can anyone with v20c confirm this !!
thanks for this method OP !
Thanks , please upload the rooted ROM image as well
Thanks , please upload the rooted ROM image as well
brianlili said:
Just only a few steps, If my guidiance help you out, Please hit thanks button
1. If you are using a rooted firmware(any one can do) , you can jump to step 2. Or, install v18f(leaked 4.0.3 ics) and root it with TPSparkyRoot tool.
2.Press and hold power and volume- button, enter LG's recovery, press power button twice to process a factory reset. reboot, then enable usb debug, connect your PC and P930 with usb cable, download attachement file(all-purpose-ROOT.rar ). Extract it and run before.bat file.
3. Flash V20c_00.kdz. you can follow this http://forum.xda-developers.com/showthread.php?t=1597488 guide to finish this step.
4. After V20c installed, you phone will reboot and stuck in at&t's logo, but don't worried, run after-KDZ-flashed.bat(need usb connected to pc of course) . You can see informations of rooting success Awared: do not process factory reset until you run after-KDZ-flashed.bat! It is very important!
5. Factory reset again then you will get a rooted V20c, Enjoy it.
View attachment 1227309
View attachment 1227311
Click to expand...
Click to collapse
For those that don't want to go through the trouble of doing all this, is there anyway you could provide your /boot, /system, /firmware, and /baseband?
brianlili said:
Just only a few steps, If my guidiance help you out, Please hit thanks button
1. If you are using a rooted firmware(any one can do) , you can jump to step 2. Or, install v18f(leaked 4.0.3 ics) and root it with TPSparkyRoot tool.
2.Press and hold power and volume- button, enter LG's recovery, press power button twice to process a factory reset. reboot, then enable usb debug, connect your PC and P930 with usb cable, download attachement file(all-purpose-ROOT.rar ). Extract it and run before.bat file.
3. Flash V20c_00.kdz. you can follow this http://forum.xda-developers.com/showthread.php?t=1597488 guide to finish this step.
4. After V20c installed, you phone will reboot and stuck in at&t's logo, but don't worried, run after-KDZ-flashed.bat(need usb connected to pc of course) . You can see informations of rooting success Awared: do not process factory reset until you run after-KDZ-flashed.bat! It is very important!
5. Factory reset again then you will get a rooted V20c, Enjoy it.
View attachment 1227309
View attachment 1227311
Click to expand...
Click to collapse
How do we run this from CM10 with CWM? You said any rooted FW would do. Should I Factory reset inside CWM and reboot? Then follow the steps?
I almost want to try it... however I would prefer if the instructions were a bit clearer. When flashing anything to my phone I want to be completely clear that I am doing the right steps. Maybe I am just stupid and don't understand. lol
rani9990 said:
How do we run this from CM10 with CWM? You said any rooted FW would do. Should I Factory reset inside CWM and reboot? Then follow the steps?
Click to expand...
Click to collapse
same question !
i am also running cm10 !
so can we factory reset from cwm ?
I'm not seeing how this will work... Why do I have to go to v18f? When we install v20c, the nature of the process is wiping the phone first. You can't not do that.
Also, if the phone is stuck in the AT&T logo, adb is not available.
I looked at the script and it is the same as the one in my signature only split into 2 files.
I will wait for the OP to upload a pre-rooted rom.
mattman86 said:
I'm not seeing how this will work... Why do I have to go to v18f? When we install v20c, the nature of the process is wiping the phone first. You can't not do that.
Also, if the phone is stuck in the AT&T logo, adb is not available.
I looked at the script and it is the same as the one in my signature only split into 2 files.
I will wait for the OP to upload a pre-rooted rom.
Click to expand...
Click to collapse
ADB is also greyed out in developer options. How do I run the second file?
EDIT: ADB works, but now I can't get the second script to work. It always shows up as $ exit not # exit as it should be.
rani9990 said:
ADB is also greyed out in developer options. How do I run the second file?
EDIT: ADB works, but now I can't get the second script to work. It always shows up as $ exit not # exit as it should be.
Click to expand...
Click to collapse
ok !
i am about to try v20c !
so if i am unable to root v20c, does unbricking method revive the phone ?
just asking to be sure !
thanks..
aaki_rocker said:
ok !
i am about to try v20c !
so if i am unable to root v20c, does unbricking method revive the phone ?
just asking to be sure !
thanks..
Click to expand...
Click to collapse
yes it do
HO!NO! said:
yes it do
Click to expand...
Click to collapse
3---2---1-- here i go !! :fingers-crossed:
I know I will be waiting suspense-fully.
I am guessing it didn't go well...lol ... I figured he would be back with an update by now
aaki_rocker said:
3---2---1-- here i go !! :fingers-crossed:
Click to expand...
Click to collapse
i'm rooting for ya! :silly:
scott0 said:
i'm rooting for ya! :silly:
Click to expand...
Click to collapse
please help me over here !!
http://forum.xda-developers.com/showthread.php?t=1801669
aaki_rocker said:
please help me over here !!
http://forum.xda-developers.com/showthread.php?t=1801669
Click to expand...
Click to collapse
i suggest switching to emergency mode.
i am on v20c now !
i have enabled usb debugging but it shows me device not found ?
mattman86 said:
I'm not seeing how this will work... Why do I have to go to v18f? When we install v20c, the nature of the process is wiping the phone first. You can't not do that.
Also, if the phone is stuck in the AT&T logo, adb is not available.
I looked at the script and it is the same as the one in my signature only split into 2 files.
I will wait for the OP to upload a pre-rooted rom.
Click to expand...
Click to collapse
Just try it, ok? adb works fine!
brianlili said:
Just try it, ok? adb works fine!
Click to expand...
Click to collapse
I did... It didn't work
I am new in rooting and custom roms. I have LG SU640 that i have brick two days before.
i was actually trying to mod my LG SU640 rom.
First i root my LG SU640 successfully then i decided to burn avatar rom in it. With the help of CWM recovery i successfully done that also.
After that, i don't know what i was trying to do actually but i changed my recovery mode.
After that i examined that i have done a mistake that i forgot to burn gapps along with the AVATAR rom.
I decided to burn that both again, but after flashing my previous rom and all cache, when i select my sdcard to burn these stuff, my sdcard failed..!!
that was my my sdcard's fault actually but after that my LG SU640 do not getting up, till yet.
When i try to push it on, it just show the initial processing of AVATAR rom, and it keeps doing that till when i stop it..!!!
I have read some forums about it that it is possible to unbrick my LG SU640.
so please help me here..!! please. :crying:
moizullah said:
:
Click to expand...
Click to collapse
Hey, I don't have the same device as yours, however, your in a "bootloop", can you access your custom recovery(through pressing harware keys)? .... if not, then you might be able to put your device in fastboot mode and flash a custom recovery with
fastboot flash recovery nameofrecovery.img
However tell me if you can access your recovery first
Cheers mate
Hi,
I will have your thread moved to your device section.
Good luck!
itouchables said:
Hey, I don't have the same device as yours, however, your in a "bootloop", can you access your custom recovery(through pressing harware keys)? .... if not, then you might be able to put your device in fastboot mode and flash a custom recovery with
fastboot flash recovery nameofrecovery.img
However tell me if you can access your recovery first
Cheers mate
Click to expand...
Click to collapse
Thanks bro..!!
i can't boot in recovery mode, but i surely tray that fastboot recovery process.
i will tell you the results after attempting it.
Thanks again..
Deer itouchables..!!
can you please tell me the procedure to perform THE FASTBOOT?
moizullah said:
Deer itouchables..!!
can you please tell me the procedure to perform THE FASTBOOT?
Click to expand...
Click to collapse
Here's a great guide that helped me when I was a beginner
http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro
Don't hesitate to ask members in your lg phone forum, as I'm not aware of the types of custom recovery you have..
Good luck
Cheers
itouchables said:
Here's a great guide that helped me when I was a beginner
http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro
Don't hesitate to ask members in your lg phone forum, as I'm not aware of the types of custom recovery you have..
Good luck
Cheers
Click to expand...
Click to collapse
Hi,
i appreciate your suggestions but the problrm is i don't know how to be in fastboot mode in my LG SU640...?
THANKs
Hi guys,
I try to update my phone via ADB. ZE551ML (Z00A) and the message in recovery is this,
http://postimg.org/image/7o23fmrkv/
I got the Chinese version and later on, i installed the WW rom.
Some help please?
Hope you've flashed recovery img,boot img & droidboot img of your SKU to the latest firmware you are updating ur phone to..
Sent from my ASUS_Z00AD using Tapatalk
I just want to update so i can unlock my bootloader and install superzen.
There weren't any instructions for the steps you mentioned.
I just take the zip file and sidrload it.
from adb logs nobody can understand something.
CenereZar said:
from adb logs nobody can understand something.
Click to expand...
Click to collapse
Well, in summary.
I bought it from China, installed the rooted ROM.
Then i had some issues and i reset the device.
oXydead said:
Well, in summary.
I bought it from China, installed the rooted ROM.
Then i had some issues and i reset the device.
Click to expand...
Click to collapse
This is a precious guide for updating and changing CN to WW.I had a similar issue.My phone was CN and i didn't know that.solved with this http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835e
Title is not important.following that you will have a updated and WW phone.
CenereZar said:
This is a precious guide for updating and changing CN to WW.I had a similar issue.My phone was CN and i didn't know that.solved with this http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835e
Title is not important.following that you will have a updated and WW phone.
Click to expand...
Click to collapse
It still gives me an error...
oXydead said:
It still gives me an error...
Click to expand...
Click to collapse
i'm sorry...as i told i solved a similar issue in that way.Maybe the others can help you ?
UP
From the beginning, I couldn't enter recovery mode normally. When trying to enter there, it gives me an error. So while on the error screen, I hold the power button and click once the volume up key. Then I enter recovery. The installation of the its begins and the error is status 7. The phone is bought from China. Installed the WW Rom. Afterwards, I flashed the rooted WW Rom.
Any help would be appreciated. Cheers.
Bump...
oXydead said:
Bump...
Click to expand...
Click to collapse
Mate, you need to follow the guide supplied by CenereZar though personally this might help more, especially chapter 4 - http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596.
You're trying to install a WW rom on a CN rom base. You'll get a bootloop...
Unless you flash ALL the files properly you will be stuck with a brick...
ultramag69 said:
Mate, you need to follow the guide supplied by CenereZar though personally this might help more, especially chapter 4 - http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596.
You're trying to install a WW rom on a CN rom base. You'll get a bootloop...
Unless you flash ALL the files properly you will be stuck with a brick...
Click to expand...
Click to collapse
I will give it a try, thanks.
Keep in mind, i use the pre-rooted ROM and i am on 2.15.40.13
oXydead said:
Keep in mind, i use the pre-rooted ROM and i am on 2.15.40.13
Click to expand...
Click to collapse
Yep, so did I...
ultramag69 said:
Yep, so did I...
Click to expand...
Click to collapse
I got the pop-up "Update Found" but when phone powers off, i get an error.
I also get an error, applying it from adb. ''Installation aborted" Status 7
oXydead said:
I got the pop-up "Update Found" but when phone powers off, i get an error.
I also get an error, applying it from adb. ''Installation aborted" Status 7
Click to expand...
Click to collapse
You need to replace boot.img, droidboot.img and recovery with the version of ww android you are trying to flash through fastboot.
Just remember that as you are replacing the bootloader and recovery these files MUST be perfect. If they're corrupt you will end up with a brick.
Don't worry about using ADB to flash stock rom, the pre-rooted image is fine just make sure you wipe all the partitions and then reflash them before flashing the system.img...
You should be able to find the 1st 3 files in the pre-rooted image thread as Shakalaka included them in his download directory with the pre-rooted.img file... Thankyou again Shakalaka...
ultramag69 said:
You need to replace boot.img, droidboot.img and recovery with the version of ww android you are trying to flash through fastboot.
Just remember that as you are replacing the bootloader and recovery these files MUST be perfect. If they're corrupt you will end up with a brick.
Don't worry about using ADB to flash stock rom, the pre-rooted image is fine just make sure you wipe all the partitions and then reflash them before flashing the system.img...
You should be able to find the 1st 3 files in the pre-rooted image thread as Shakalaka included them in his download directory with the pre-rooted.img file... Thankyou again Shakalaka...
Click to expand...
Click to collapse
I am doing it all right. But when my phone restarts, it gives me an error.
I had this problem from the begging. To enter to recovery, error appeared then i have to press power+up volume to enter.
I am going nowhere...
oXydead said:
I am doing it all right. But when my phone restarts, it gives me an error.
I had this problem from the begging. To enter to recovery, error appeared then i have to press power+up volume to enter.
I am going nowhere...
Click to expand...
Click to collapse
Did I say go to recovery?
You just hold Power and volume up from power off or bootloop. This should get you to bootloader mode. It should have a few options the first being "normal boot", pressing down goes through a few options like recovery and so on.
If you press up there are no options displayed. This is fastboot and the safest way to flash with fastboot. If you don't hit power the other options will flash with fastboot too BUT if you hit the power button it will reset to the option displayed.
Go to to bootloader mode, press volume up and use fastboot to either erase cache or flash the rom on your phone. It must be a pre-rooted rom as the stock ones WON'T flash through fastboot...
After several atempts to update to 6.0.1
Bootloop.....
Instal the TWRP....
adb push system.img /sdcard/ ...i can´t CLOSED
ADB recognized but can´t fash recovery
Please i need some help
avelinosilva said:
After several atempts to update to 6.0.1
Bootloop.....
Instal the TWRP....
adb push system.img /sdcard/ ...i can´t CLOSED
ADB recognized but can´t fash recovery
Please i need some help
Click to expand...
Click to collapse
Maybe this can help you:
** For those of you who are interested in the solutions i arrived at (with the help of some good friends) please read my final post @:
https://www.reddit.com/r/hwatch/comm...e_android_man/
avelinosilva said:
After several atempts to update to 6.0.1
Bootloop.....
Instal the TWRP....
adb push system.img /sdcard/ ...i can´t CLOSED
ADB recognized but can´t fash recovery
Please i need some help
Click to expand...
Click to collapse
You are not bricked.
In order to update to the new OTA you need to go back to fully stock LCB43B image. That means flashing stock boot, recovery and system. BUT unfortunately there's a problem when trying to flash the stock system.img in bootloader. So you have to boot into TWRP, use adb push to get the system.img file onto your internal memory and then flash it using adb shell commands. Use this thread: http://forum.xda-developers.com/showthread.php?p=63173308
Then reboot to bootloader and flash the stock recovery and boot files.
Next, download the OTA and reboot into stock recovery (not TWRP) in order to update using adb sideboard. Use the guide here: http://forum.xda-developers.com/showthread.php?p=65607393
Hit thanks if this has helped.
bigdave79 said:
BUT unfortunately there's a problem when trying to flash the stock system.img in bootloader. So you have to boot into TWRP, use adb push to get the system.img file onto your internal memory and then flash it using adb shell commands. Use this thread: http://forum.xda-developers.com/showthread.php?p=63173308
Click to expand...
Click to collapse
Flashing system.img using the latest fastboot from the official Android SDK worked just fine for me.
C3C076 said:
Flashing system.img using the latest fastboot from the official Android SDK worked just fine for me.
Click to expand...
Click to collapse
I had instaled Androi Studio and Sdk is any problema to use W10 64 bits.
Please can you help me with the commands to use?
is this one:
adb devices
In Twrp advance select adb sideload
fastboot flash recovery recovery.img
I´m doing something wrong??
If i will send the Wacth to Huawei assistance they can fix it?
Best regards and thank you all for your help.
avelinosilva said:
I had instaled Androi Studio and Sdk is any problema to use W10 64 bits.
Please can you help me with the commands to use?
is this one:
adb devices
In Twrp advance select adb sideload
fastboot flash recovery recovery.img
I´m doing something wrong??
If i will send the Wacth to Huawei assistance they can fix it?
Best regards and thank you all for your help.
Click to expand...
Click to collapse
No.
Boot to bootloader and type "fastboot flash system system.img"
You should not be in recovery trying to fastboot flash. It will not work.
Latest SDK is fine on Windows 10. Make sure you use the fastboot and ADB from the latest SDK.
C3C076 said:
Flashing system.img using the latest fastboot from the official Android SDK worked just fine for me.
Click to expand...
Click to collapse
/-\
|
|
This
Scott said:
/-\
|
|
This
Click to expand...
Click to collapse
Scott you are my hero.....i got my watch alive......:laugh:
Tank you veryyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyymutchhhhhhhhhhhhhhhhhhhhhhhhhhh mate.:good:
avelinosilva said:
Scott you are my hero.....i got my watch alive......:laugh:
Tank you veryyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyymutchhhhhhhhhhhhhhhhhhhhhhhhhhh mate.:good:
Click to expand...
Click to collapse
Good to hear!
Scott said:
/-\
|
|
This
Click to expand...
Click to collapse
I was stuck for last 12 hours and watch was in bootloop. i tried flashin again and agin . Scott i love you :laugh:
i think it was that i was using old adb and fastboot. the latest ones helped. Also there is no need to flash twrp. Even if you get file sparce issue.
Salute to You :good::good::good:
Now i am back to LCB43B will try to update to 1.4 via stock recovery now
Yeah, the ADB / Fastboot changed with Lolipop. Anything pre-lolipop will give issues.
I've never flashed anything onto my watch, but yesterday after recharging the battery after it going dead, I get stuck at the 4 dots boot animation. I'm able to reboot the watch, and even get into the normal fastboot menu, but clearing cache, data, and resetting to default doesn't help. I'm really hoping what you guys are doing will fix the trick for me. I simply want to return the watch to stock, but I'm seeing conflicting reports on how to proceed with this.
I've downloaded the Android SDK, but have never used it before. I keep hearing things about adb, and flashing system.img using the latest fastboot - I don't know where to find either of these or how to use them. Would you awesome people mind doing a little hand holding with me and give me a bit of detail on how to proceed with the solution from C3C076?
EDIT: So I think I figured it out myself, albiet with the wisdom gained from you awesome folk. I used fastboot to push the 6.0.1 boot and system images from this thread, and things seem back to normal. I haven't rebooted the watch yet, since I didn't load the 6.0.1 recovery image (the only part of the watch that had worked since the problem started), and I'm not sure if I'm going to have the problem reoccur once it does reboot. If anyone has insight on how to best proceed given the steps I've taken so far, it'd be greatly appreciated.
kurosen said:
I've never flashed anything onto my watch, but yesterday after recharging the battery after it going dead, I get stuck at the 4 dots boot animation. I'm able to reboot the watch, and even get into the normal fastboot menu, but clearing cache, data, and resetting to default doesn't help. I'm really hoping what you guys are doing will fix the trick for me. I simply want to return the watch to stock, but I'm seeing conflicting reports on how to proceed with this.
I've downloaded the Android SDK, but have never used it before. I keep hearing things about adb, and flashing system.img using the latest fastboot - I don't know where to find either of these or how to use them. Would you awesome people mind doing a little hand holding with me and give me a bit of detail on how to proceed with the solution from C3C076?
EDIT: So I think I figured it out myself, albiet with the wisdom gained from you awesome folk. I used fastboot to push the 6.0.1 boot and system images from this thread, and things seem back to normal. I haven't rebooted the watch yet, since I didn't load the 6.0.1 recovery image (the only part of the watch that had worked since the problem started), and I'm not sure if I'm going to have the problem reoccur once it does reboot. If anyone has insight on how to best proceed given the steps I've taken so far, it'd be greatly appreciated.
Click to expand...
Click to collapse
If fastboot flashing boot and system images went well, you can safely reboot your watch. First boot might take a while but it should boot OK.
@ausi
ausi said:
Maybe this can help you:
** For those of you who are interested in the solutions i arrived at (with the help of some good friends) please read my final post @:
https://www.reddit.com/r/hwatch/comm...e_android_man/
Click to expand...
Click to collapse
@ausi, can you please post again the solution, the link doesn't work anymore!!!
I really need it!!!
Please help!!!
I am in the same ****!!!
My watch doesn't work anymore!!!
Thank's for anyone help!!!
C3C076 said:
Flashing system.img using the latest fastboot from the official Android SDK worked just fine for me.
Click to expand...
Click to collapse
This DUDE RIGHT HERE. Did it. This was the missing piece. My fastboot files simply weren't good enough. x!!
Android SDK Platform Tools did the trick for me.
Hi guys, I searched around the forum before posting this so I apologize but I recently installed a new rom and possibly a wrong kernel with it. Afterwards, if I try to turn it on, it just shows the logo and then turns right off. I can't even go into recovery since it does the same. The only thing I can do is boot it into fastboot but I'm not sure where to go from here. I tried using a guide with no success.
Any words of wisdom?
reflash your recovery via fastboot, then boot into recovery and do a clean install
fastboot flash [recovery].img
I tried reflashing recovery but all it does is show the old rom logo that was used and then shuts down.
Hi,
Read carefully and try this guide:
forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
which rom did you flash? You need the correct twrp file for your bootloader.
That's the first place I tried. Anytime I hook-up my phone to the PC it shows up as OnePlus Android bootloader interface under Android phone and I can't seem to update the drivers..
matze19999 said:
which rom did you flash? You need the correct twrp file for your bootloader.
Click to expand...
Click to collapse
I used the Freedom Rom 2.0
Arken2121 said:
I used the Freedom Rom 2.0
Click to expand...
Click to collapse
you need this twrp file:
https://forum.xda-developers.com/devdb/project/dl/?id=21835
matze19999 said:
you need this twrp file:
https://forum.xda-developers.com/devdb/project/dl/?id=21835
Click to expand...
Click to collapse
Thank you so much, I guess I installed the wrong TWRP and I can FINALLY get into recovery. Thank you so much.