Related
I rooted my kindle fire using kfu 9.8. As of this moment when I install roms they do not boot up and they stay at the boot logo. I dont know if it has to do with TWRP or the roms, but I have tried 2 cm10 roms and one AOSP 4.2.2 rom. I will tell you exactly what I did.
1. Rooted with kfu
2. went straight to recovery, flashed the aosp rom + google apps
3. Booted up and it stayed at the boot screen
4. Tried another rom, put it onto the device through usb mounting with twrp
5. Still stuck at boot logo
6. Tried the last rom but still stuck!!
After that I tried to flash back to stock using this
(doesnt let me post a link if requested I will pm)
But twrp gave an error and it did not install, it said somewhere an error doesnt matter and you would boot up fine but I didnt
Between installing all Roms I wiped cache, dalvik, and factory reset.
Thanks in advnce!
EDIT
Used this to try to bring to stock
theunlockr DOT com/2012/10/29/how-to-unroot-the-amazon-kindle-fire
Used these roms (all on xda)
/showthread.php?t=2100963
/showthread.php?t=2041694
cant find the third rom
EDIT
I have no problem using adb or fastboot so feel free to try and fix my problem with those.
Ilia Goro said:
But twrp gave an error and it did not install it said somewhere an error doesnt matter and you would boot up fine but I didn't
Click to expand...
Click to collapse
It would be very helpful to know exactly what error you are receiving.
soupmagnet said:
It would be very helpful to know exactly what error you are receiving.
Click to expand...
Click to collapse
assert failed:getprop ("ro.product.device") == "blaze" l l
E:unknown command {err_string}
getprop ("ro.product.device") == "blaze"
E:unknown command {err_string}
E:Error in sdcard/update.zip
Status 7
Error flashing zip /sdcard/update.zip
Updating partition details
That is exactly what I get while flashing
Im sorry for making the topic and/or wasting your time, before installing the rom I wiped every single thing possible and it succesfully nstalled.
I have no problem if you lock.
Ilia Goro said:
assert failed:getprop ("ro.product.device") == "blaze" l l
E:unknown command {err_string}
getprop ("ro.product.device") == "blaze"
E:unknown command {err_string}
E:Error in sdcard/update.zip
Status 7
Error flashing zip /sdcard/update.zip
Updating partition details
That is exactly what I get while flashing
Im sorry for making the topic and/or wasting your time, before installing the rom I wiped every single thing possible and it succesfully nstalled.
I have no problem if you lock.
Click to expand...
Click to collapse
Any update on this? I'm getting the same issue on mine.
Runaround said:
Any update on this? I'm getting the same issue on mine.
Click to expand...
Click to collapse
I had the same issue using TWRP 2.4.x.x. I was able to return to stock by downgrading to TWRP 2.2.2.1. Good luck.
Sent from my Nexus 7 using xda app-developers app
philipsw said:
I had the same issue using TWRP 2.4.x.x. I was able to return to stock by downgrading to TWRP 2.2.2.1. Good luck.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
By any chance, can you please give me the link to the TWRP 2.2.2.1?
TIA.
votinh said:
By any chance, can you please give me the link to the TWRP 2.2.2.1?
TIA.
Click to expand...
Click to collapse
http://www.teamw.in/project/twrp2/79
Sent from my Nexus 7 using xda app-developers app
philipsw said:
http://www.teamw.in/project/twrp2/79
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks philipsw, I found the 2.2.2.1 flashable zip file too.
2.2.2.1 zip?
votinh said:
Thanks philipsw, I found the 2.2.2.1 flashable zip file too.
Click to expand...
Click to collapse
where did you find the zip file?
TWRP
You need TWRP 2.6.3.1 too install KitKat Roms here is the link for your first gen fires you need the otter.img
TWRP
PLEASE HELP! Kindle Fire 1st Gen. I've looked everywhere for answers
Okay, This is the first time Ive ever posted anything on this site. Normally I just search for answers and people usually have already solved the problem so I just go off what other people post. But now I cannot seem to find any fix I rooted my Kindle Fire 1st Generation. I was running TWRP 2.2.2. and a Hellfire ROM. I went on vacation and left my Kindle at home. When I got back, most of my apps weren't working properly and my keyboard was glitching so I tried to update my ROM. It was unsuccessful. So I thought maybe if I upgraded my TWRP Recovery to the latest version It would fix the problem... I was wrong. Whenever I try to flash any ROM I get an error like this... (E:Error executing updater binary) I have searched for answers for about a month now and nothing seems to work. I dont know what to do and I feel like crying. Can someone please help me? Please?
Feedback
DroidLover93 said:
Okay, This is the first time Ive ever posted anything on this site. Normally I just search for answers and people usually have already solved the problem so I just go off what other people post. But now I cannot seem to find any fix I rooted my Kindle Fire 1st Generation. I was running TWRP 2.2.2. and a Hellfire ROM. I went on vacation and left my Kindle at home. When I got back, most of my apps weren't working properly and my keyboard was glitching so I tried to update my ROM. It was unsuccessful. So I thought maybe if I upgraded my TWRP Recovery to the latest version It would fix the problem... I was wrong. Whenever I try to flash any ROM I get an error like this... (E:Error executing updater binary) I have searched for answers for about a month now and nothing seems to work. I dont know what to do and I feel like crying. Can someone please help me? Please?
Click to expand...
Click to collapse
Just need a little more info... What TWRP version are you running?? What android version are you trying to flash??
lj50036 said:
Just need a little more info... What TWRP version are you running?? What android version are you trying to flash??
Click to expand...
Click to collapse
I'm currently running TWRP v2.6.0.0
And I'm trying to flash ANY android version.
So far I have tried flashing the latest HellFire, Kit Kat, and Jellybean Stock Roms, All have been unsuccessful.
All I want is to be able to use my kindle without wanting to smash it to pieces, lol. I'm tired of getting booted off the internet every 2 minutes and my apps to force closing on me.
DroidLover93 said:
I'm currently running TWRP v2.6.0.0
And I'm trying to flash ANY android version.
So far I have tried flashing the latest HellFire, Kit Kat, and Jellybean Stock Roms, All have been unsuccessful.
All I want is to be able to use my kindle without wanting to smash it to pieces, lol. I'm tired of getting booted off the internet every 2 minutes and my apps to force closing on me.
Click to expand...
Click to collapse
And you are using the firefirefire utility??
lj50036 said:
And you are using the firefirefire utility??
Click to expand...
Click to collapse
Yes, I believe so.
TWRP
DroidLover93 said:
Yes, I believe so.
Click to expand...
Click to collapse
We need to get you on the latest version of twrp....http://techerrata.com/browse/twrp2/blaze
Go here and get version 2.6.3.1 make sure your get the otter.img as the blaze is for the 2nd gen fire....
Let me know if you need any help with this.. Let me know when you have it installed....Thx lj
---------- Post added at 10:51 PM ---------- Previous post was at 10:46 PM ----------
Do you have fastboot and adb drivers for your PC?? Do you have fastboot.exe and adb.exe... I assume your running windows....
@lj50036
Do you have fastboot and adb drivers for your PC?? Do you have fastboot.exe and adb.exe... I assume your running windows...
Thank you! I will do this now and I will let you know when I have it installed. Do I just flash it through recovery or?...
Also, I do not have fastboot and adb drivers on my PC. Where do I go to get them? Running Windows 7
Feedback
DroidLover93 said:
@lj50036
Do you have fastboot and adb drivers for your PC?? Do you have fastboot.exe and adb.exe... I assume your running windows...
Thank you! I will do this now and I will let you know when I have it installed. Do I just flash it through recovery or?...
Also, I do not have fastboot and adb drivers on my PC. Where do I go to get them? Running Windows 7
Click to expand...
Click to collapse
Check this forum for your fastboot adb driver needs...http://forum.xda-developers.com/showthread.php?t=2588979
Hold on a sec I will make you a flashable recovery zip for easy of installation...
TWRP 2.6.3.1
Here is a flashable zip twrp recovery v 2.6.3.1... Just flash it than do a reboot before trying to enter recovery... Let me know if that fastboot/adb stuff is working for you we will still need adb drivers and adb installed on your PC...Thx lj
View attachment 2578399
lj50036 said:
Here is a flashable zip twrp recovery v 2.6.3.1... Just flash it than do a reboot before trying to enter recovery... Let me know if that fastboot/adb stuff is working for you we will still need adb drivers and adb installed on your PC...Thx lj
View attachment 2578399
Click to expand...
Click to collapse
Thanks! Okay so TWRP update was successful. Then I followed the link for ADB and fastboot. I installed them to PC. Now, just to be clear.. Was I supposed to do that with the USB connected to my device? or was that just for my PC? I just dont want to mess anything up.
hi,
My phone is soft bricked and stuck at boot logo. I am trying to flash stock recovery/kdz file using flash tool but getting stuck at"low battery" error.
Could you please help how i can bypass this error? I have spend a lot of time online and tried few methods but always getting stuck at this error. I dont have any alternative phone and this is really disappointing.
I am using E988 India model.
CLICK HERE MATE. LET ME KNOW IF IT HELPS. IF NOT USE THE INSTRUCTIONS BELOW
I'm using same phone and have the same problem. I still can't flash stock with the tool but I can tell you how to get out of soft brick. Download madmacks e980 lokified TWRP recovery and also CM 11 latest version. Get in to recovery mode and go to install file (sideload) and flash the recovery first then reboot in to recovery again and sideload CM 11. When I get a definitive solution to flash stock I will let you know mate. If you have problems or don't know what I'm talking about then reply here. You well need adb installed on computer and open a new command window by holding shift and click right noise button at the same time. Make sure you perform this from the same directory as where there files are that your flashing. Once your phone prompts you to sideload type in to the command window adb sideload (the exact file name of the file you want to flash.zip) but without the brackets
uppon2 said:
CLICK HERE MATE. LET ME KNOW IF IT HELPS. IF NOT USE THE INSTRUCTIONS BELOW
I'm using same phone and have the same problem. I still can't flash stock with the tool but I can tell you how to get out of soft brick. Download madmacks e980 lokified TWRP recovery and also CM 11 latest version. Get in to recovery mode and go to install file (sideload) and flash the recovery first then reboot in to recovery again and sideload CM 11. When I get a definitive solution to flash stock I will let you know mate. If you have problems or don't know what I'm talking about then reply here. You well need adb installed on computer and open a new command window by holding shift and click right noise button at the same time. Make sure you perform this from the same directory as where there files are that your flashing. Once your phone prompts you to sideload type in to the command window adb sideload (the exact file name of the file you want to flash.zip) but without the brackets
Click to expand...
Click to collapse
Thank you very much for this help. I have never tried adb. Probably I shall now learn it and then try to do as you suggested. I am not particular about stock ROM. In fact I will be happy if there is stable cm ROM for this phone.
I juts bought this phone two days back. There are too many model numbers n am little scared now about choosing the right ROM. Do you mind sharing link for correct cm11 ROM please?,
Thanks again for your help!
Sent from my GT-I9500 using xda app-developers app
I'm trying to root my phone to install CM 10.2. I've been searching for a few hours and am getting more and more frustrated. I've read that Firewater is the easiest way to unlock the bootloader on my phone. I've downloaded Firewater, but I don't know what to do with it. Its just a file called "Firewater" with no extension. I don't know how to run it.
I've also tried RumRunner, and have had no success.
I'm not sure what ADB and Fastboot are, but I think I have some ADB stuff installed on my comp [ C:\Program Files (x86)\Minimal ADB and Fastboot ] and I have that path in my Environment Variables>path directory. I don't know what to do with it.
Please help me get started. Step by step instructions would be great. I saw a thread that isn't very old where someone was having root trouble w/ KitKat but they were able to run Firewater. I need help getting that started at least. Thank you.
Edit: Fastboot is Off
USB Debugging Enabled
HTC Sync (can't find it anywhere on my comp, or in the programs list ((control panel)) so I assume its not installed)
Drivers are installed on my comp.
I've downloaded an ADB toolkit, and have it pathed. I opened the command prompt and ran "adb devices" to check. My phone showed up with no problem.
I then moved firewater to the current directory cmd was using c:\Users\MYNAME.
adb reboot
adb wait-for-device push firewater /data/local/tmp
adb shell
after this it displays:
127:[email protected]:/ $
I entered "su"
/system/bin/sh: su: not found
Could anyone explain what I'm doing exactly by following these directions, and explain what I can do next to correct the problem?
Edit: su means Super User, correct? I've tried installing SuperSU, but It says that there is no SU binary installed. I haven't found out how to install the binary.
Pharva said:
I've downloaded an ADB toolkit, and have it pathed. I opened the command prompt and ran "adb devices" to check. My phone showed up with no problem.
I then moved firewater to the current directory cmd was using c:\Users\MYNAME.
adb reboot
adb wait-for-device push firewater /data/local/tmp
adb shell
after this it displays:
127:[email protected]:/ $
I entered "su"
/system/bin/sh: su: not found
Could anyone explain what I'm doing exactly by following these directions, and explain what I can do next to correct the problem?
Edit: su means Super User, correct? I've tried installing SuperSU, but It says that there is no SU binary installed. I haven't found out how to install the binary.
Click to expand...
Click to collapse
you need temp root... goto http://firewater-soff.com/ everything is right there. If you have kitkat from the OTA the other day, i dont believe it works on kitkat yet.
Thanks. I've read that temproot doesn't work on KitKat either. For now, it would seem that my only option is to wait, right?
Pharva said:
Thanks. I've read that temproot doesn't work on KitKat either. For now, it would seem that my only option is to wait, right?
Click to expand...
Click to collapse
Yes you are correct temp root method does not work for the newest OTA update and unfortunately there is no method for the CDMA version of the htc one so hopefully we will see a new method soon!
S-Off not working
nty123 said:
Yes you are correct temp root method does not work for the newest OTA update and unfortunately there is no method for the CDMA version of the htc one so hopefully we will see a new method soon!
Click to expand...
Click to collapse
I am having this problem also. I am trying to s-off with firewater and can't get past the SU also...it tells me SU can't be found.
Debugging enabled
Developer Mode enabled
Network band set to LTE/CDMA
No passcode or other security lock
My Fastboot and ADB are working fine. I am able to run the Temproot instructions, but it stops at SU. WHY?
payrovi2 said:
I am having this problem also. I am trying to s-off with firewater and can't get past the SU also...it tells me SU can't be found.
Debugging enabled
Developer Mode enabled
Network band set to LTE/CDMA
No passcode or other security lock
My Fastboot and ADB are working fine. I am able to run the Temproot instructions, but it stops at SU. WHY?
Click to expand...
Click to collapse
just what the above post's stated, you need temp-root to, along with firewater. and if you are on the newest ota (kitkat 4.4.2) then you have no other choice but to wait. that mean's no downgrading either.
nty123 said:
just what the above post's stated, you need temp-root to, along with firewater. and if you are on the newest ota (kitkat 4.4.2) then you have no other choice but to wait. that mean's no downgrading either.
Click to expand...
Click to collapse
Thanks. Yes, I was able to temproot and firewater and get s-off.
I'm trying to load Cyanogenmod for my HTC One Verizon ( cm-10.2.0-RC1-m7vzw.zip ) through clockworkmod recovery 6.0.4.7
When I wiped the data/factory reset...it seemed to get stuck for >20minutes. I powered down and up...and it looked like some partial factory reset had happened.
I went ahead with the cyanogenmod zip update, through cwm recovery, and it seems to be stuck at Installing Update. Nothing is happening or moving.
Any thoughts?
Thanks for all the developer help.
payrovi2 said:
Thanks. Yes, I was able to temproot and firewater and get s-off.
I'm trying to load Cyanogenmod for my HTC One Verizon ( cm-10.2.0-RC1-m7vzw.zip ) through clockworkmod recovery 6.0.4.7
When I wiped the data/factory reset...it seemed to get stuck for >20minutes. I powered down and up...and it looked like some partial factory reset had happened.
I went ahead with the cyanogenmod zip update, through cwm recovery, and it seems to be stuck at Installing Update. Nothing is happening or moving.
Any thoughts?
Thanks for all the developer help.
Click to expand...
Click to collapse
can you power off device and boot into recovery? (not sure what the problem is yet but you could try using a different recovery, twrp instead of cwm. before you try out twrp (if you do) make sure you have the latest version of cwm installed
nty123 said:
can you power off device and boot into recovery? (not sure what the problem is yet but you could try using a different recovery, twrp instead of cwm. before you try out twrp (if you do) make sure you have the latest version of cwm installed
Click to expand...
Click to collapse
I can boot into recovery, but can't boot the phone up.
payrovi2 said:
I can boot into recovery, but can't boot the phone up.
Click to expand...
Click to collapse
ok, what i would try is backup to the rom you have before you tried installing CM( only if you made a backup). if you didn't then i would try clearing all data and that rom and try installing a different one, maybe the one you have has a bug and is not working properly.
nty123 said:
ok, what i would try is backup to the rom you have before you tried installing CM( only if you made a backup). if you didn't then i would try clearing all data and that rom and try installing a different one, maybe the one you have has a bug and is not working properly.
Click to expand...
Click to collapse
It kept getting stuck at "installing update" no matter whether it was a previous rom or the Cyanogenmod rom. I tried it numerous times...and then finally once it said "...update complete"
I'm rebooting and loading cyanogenmod now...hope that it moves past this CM boot screen.
payrovi2 said:
It kept getting stuck at "installing update" no matter whether it was a previous rom or the Cyanogenmod rom. I tried it numerous times...and then finally once it said "...update complete"
I'm rebooting and loading cyanogenmod now...hope that it moves past this CM boot screen.
Click to expand...
Click to collapse
Nope. still stuck at this boot loop.
Any ideas?
payrovi2 said:
Nope. still stuck at this boot loop.
Any ideas?
Click to expand...
Click to collapse
try restoring from you backup again but this time wipe all your data and factory reset before yo restore
payrovi2 said:
Nope. still stuck at this boot loop.
Any ideas?
Click to expand...
Click to collapse
I would do a decrypted RUU at this point, it will at least get you back on a sense rom (as long as you download the decrypted one, it wont break your SOFF and bootloader unlock). then from there i would reinstall PHILZ or TWRP, then make sure the MD5 is right on the rom you want to install
Hi all!I've bought from China the ascend p6,which looks like having a custom rom on it,but it just doesn't allow me to use the play store.The build number of the software is p6-u06v100r001c11b506,the kernel version is [email protected] #2.To get rid of the chinese language recovery,I've installed the twrp which was working fine,until I decided to follow,not pretty well,the guide here,on xda,to go from the chinese firmware to the international one,and I've installed the stock rom.From that time,I'm just not able to enter into the recovery anymore,if I keep pressed the volume buttons plus the power button,the phone remains stuck on the logo screen,if I keep pressed it for around 3 seconds it reboot normally into the system,but no recovery or fastboot even from my linux pc.I've tried to download rom manager to install a custom recovery but looks like this model is not supported,so nada.What can I do to install a recovery and get it back to work to install a custom recovery that will allow me to use the play store?
Thank you so much guys,any help is really appreciated!
Marco
marco981 said:
Hi all!I've bought from China the ascend p6,which looks like having a custom rom on it,but it just doesn't allow me to use the play store.The build number of the software is p6-u06v100r001c11b506,the kernel version is [email protected] #2.To get rid of the chinese language recovery,I've installed the twrp which was working fine,until I decided to follow,not pretty well,the guide here,on xda,to go from the chinese firmware to the international one,and I've installed the stock rom.From that time,I'm just not able to enter into the recovery anymore,if I keep pressed the volume buttons plus the power button,the phone remains stuck on the logo screen,if I keep pressed it for around 3 seconds it reboot normally into the system,but no recovery or fastboot even from my linux pc.I've tried to download rom manager to install a custom recovery but looks like this model is not supported,so nada.What can I do to install a recovery and get it back to work to install a custom recovery that will allow me to use the play store?
Thank you so much guys,any help is really appreciated!
Marco
Click to expand...
Click to collapse
If you can boot up your phone normaly into system then turn usb debugging on and try to use adb commands to enter either recovery or fastboot mode.
Sent from my SM-G850F
tileeq said:
If you can boot up your phone normaly into system then turn usb debugging on and try to use adb commands to enter either recovery or fastboot mode.
Sent from my SM-G850F
Click to expand...
Click to collapse
But how?Because everytime I give the command through adb reboot fastboot,the phone shows just the logo and I can't go further
marco981 said:
But how?Because everytime I give the command through adb reboot fastboot,the phone shows just the logo and I can't go further
Click to expand...
Click to collapse
That is the fastboot node on the P6, which means that you can use fastboot commands now to flash what you need. That is either new recovery or new system.
Sent from my P6-U06
tileeq said:
That is the fastboot node on the P6, which means that you can use fastboot commands now to flash what you need. That is either new recovery or new system.
Sent from my P6-U06
Click to expand...
Click to collapse
Thank you for the reply,but everytime the terminal is stuck on waiting for device and doesn't do anything...Which commands should I type to install the recovery?
Thank you!
marco981 said:
Thank you for the reply,but everytime the terminal is stuck on waiting for device and doesn't do anything...Which commands should I type to install the recovery?
Thank you!
Click to expand...
Click to collapse
The proper command in fastboot mode should be FASTBOOT FLASH RECOVERY RECOVERY.IMG where recovery.img should be the name of the recovery file that you have on your computer.
Sent from my P6-U06
tileeq said:
The proper command in fastboot mode should be FASTBOOT FLASH RECOVERY RECOVERY.IMG where recovery.img should be the name of the recovery file that you have on your computer.
Sent from my P6-U06
Click to expand...
Click to collapse
I've tried it several times,but the terminal keeps being stuck saying waiting for device and nothing happens..
marco981 said:
I've tried it several times,but the terminal keeps being stuck saying waiting for device and nothing happens..
Click to expand...
Click to collapse
Then you need to reinstall usb drivers. To make sure that its all installed good before you try to flash the file type this command - fasbtboot devices - if it shows up a device with random numbers and letters then you can use the flashing commands.
Sent from my P6-U06
I have a linux operating system,do I need to install any driver for the device?
Also if you only doing this for the play store i can upload it on a server and you can download and install it from there. As for the recovery you can search on the store for an app called RASHR and flash recovery through it, but only if you have root permissions on the phone.
Sent from my P6-U06
I can try,but I actually have the play store,it just doesn't communicate with the server,that's why i thought that was a problem related to the chinese version of the firmware.I don't actually think that the phone is rooted,as I've tried to install a couple of apks and they say that there are no root permissions on it
marco981 said:
I can try,but I actually have the play store,it just doesn't communicate with the server,that's why i thought that was a problem related to the chinese version of the firmware.I don't actually think that the phone is rooted,as I've tried to install a couple of apks and they say that there are no root permissions on it
Click to expand...
Click to collapse
https://mega.co.nz/#!KkwHzI4I!WEyvdMOUucW6rAONY8ERyz6aIOSIzSI1UGWa0M4nesM
This is the link and for the drivers i think you do need them no matter what system are you using.
Sent from my P6-U06
Nada.It just says that there is a problem communicating with servers everytime I try to register...
marco981 said:
Nada.It just says that there is a problem communicating with servers everytime I try to register...
Click to expand...
Click to collapse
This might get long so if you have a skype add me tileeq15 and ill try to help real time.
Sent from my P6-U06
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.