Related
So, my phone is stuck in a boot loop. I can restore factory setting but first i want to back up my data .. specifically my text messages and pictures. They are very important. Is there a way i can do that ?
the bad news is Im not rooted. now im trying to find ways to save data from my the phone before i do a factory reset. i hope i can sort it out.
Thanks,
runingwild said:
So, my phone is stuck in a boot loop. I can restore factory setting but first i want to back up my data .. specifically my text messages and pictures. They are very important. Is there a way i can do that ?
the bad news is Im not rooted. now im trying to find ways to save data from my the phone before i do a factory reset. i hope i can sort it out.
Thanks,
Click to expand...
Click to collapse
Your pictures should be on your SD and unaffected, but without root I'd say goodbye to your messages.
XperienceD said:
Your pictures should be on your SD and unaffected, but without root I'd say goodbye to your messages.
Click to expand...
Click to collapse
so is there no hope even by using ADB commands for example, or some other way? :crying:
up
runingwild said:
so is there no hope even by using ADB commands for example, or some other way? :crying:
Click to expand...
Click to collapse
I think, without root, you can't view /data, but you can try.
If you can, the sms should be located in this .xml: er /data/data/com.android.providers.telephony/databases/mmssms.db
Then backup it via adb, reflash your rom and replace the file with the backuped one.
If you can't access /data, maybe you can root/flash cwm to your phone too, if it's bootloped? (Phone specific, so I don't know.)
Good luck.
Sent from my GT-I9100 using xda app-developers app
cakebomb said:
I think, without root, you can't view /data, but you can try.
If you can, the sms should be located in this .xml: er /data/data/com.android.providers.telephony/databases/mmssms.db
Then backup it via adb, reflash your rom and replace the file with the backuped one.
If you can't access /data, maybe you can root/flash cwm to your phone too, if it's bootloped? (Phone specific, so I don't know.)
Good luck.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
thanks for the advice,
and how can i view the .xml file? (im not experienced with android..)
btw, its an Htc Desire S. yes its stuck in bootloop now
runingwild said:
thanks for the advice,
and how can i view the .xml file? (im not experienced with android..)
btw, its an Htc Desire S. yes its stuck in bootloop now
Click to expand...
Click to collapse
Connect your phone to your computer, start adb shell and type in su and then cd data
If you can view the directory by typing in ls you should be able, to copy the .xml to your computer.
Sorry for the late reply.^^
cakebomb said:
Connect your phone to your computer, start adb shell and type in su and then cd data
If you can view the directory by typing in ls you should be able, to copy the .xml to your computer.
Sorry for the late reply.^^
Click to expand...
Click to collapse
ok thanks. i downloaded SDK, then installed ADB package. But now i click on Adb icon and it wont open. what am i doing bad??
runingwild said:
ok thanks. i downloaded SDK, then installed ADB package. But now i click on Adb icon and it wont open. what am i doing bad??
Click to expand...
Click to collapse
You have to open cmd.exe and navigate to the location, where the adb file is located.
Then type in ‘adb shell’.
Sent from my Nexus 7 using xda app-developers app
cakebomb said:
You have to open cmd.exe and navigate to the location, where the adb file is located.
Then type in ‘adb shell’.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
when i type in adb shell, it says Error: device not found, while the phone was in the boot menu.
Is it maybe because im missing drivers? I googled a bit and now i have the driver i need, its .exe file , what should i do with this file? if i double click on it, i get an error message.
thanks
runingwild said:
when i type in adb shell, it says Error: device not found, while the phone was in the boot menu.
Is it maybe because im missing drivers? I googled a bit and now i have the driver i need, its .exe file , what should i do with this file? if i double click on it, i get an error message.
thanks
Click to expand...
Click to collapse
Yes, the drivers could be the problem or maybe (but I don't hope so) the phone isn't recognizable in this mode via adb.
If you're using Windows, go to the device manager and check, if there's a android thing with a exclamation, then refresh the driver of this, if it's possible. Simply via right click etc. (Of course, if the device is connected.)
And have you tried this here? http://forum.xda-developers.com/showpost.php?p=15585507&postcount=2
btw: Your phone seems to don't boot up since a few days, do you don't need it? Another idea is, maybe you can backup all your files via fastboot/download mode or something else, but you'll have to post this question in the device specifically forum, because it's different on phones.
Okay, one more time good luck.
hello
cakebomb said:
Yes, the drivers could be the problem or maybe (but I don't hope so) the phone isn't recognizable in this mode via adb.
If you're using Windows, go to the device manager and check, if there's a android thing with a exclamation, then refresh the driver of this, if it's possible. Simply via right click etc. (Of course, if the device is connected.)
And have you tried this here? http://forum.xda-developers.com/showpost.php?p=15585507&postcount=2
btw: Your phone seems to don't boot up since a few days, do you don't need it? Another idea is, maybe you can backup all your files via fastboot/download mode or something else, but you'll have to post this question in the device specifically forum, because it's different on phones.
Okay, one more time good luck.
Click to expand...
Click to collapse
yes, in the device manager there is an android thing with a yellow exclamation. i clicked on refresh the driver and i get the window asking me where i want to get the driver from. since i have the driver in an Sd card, i´ll try that tomorrow.
well, i do need the phone, but now im using my old one. until i can finally fix this issue.
What did you mean with the Fastboot mode? when im in the boot menu, i can select Fastboot, but it wont help much, because it will just start the booting again (bootloop). but i dont know if this is what you meant with fastboot.
thanks
runingwild said:
yes, in the device manager there is an android thing with a yellow exclamation. i clicked on refresh the driver and i get the window asking me where i want to get the driver from. since i have the driver in an Sd card, i´ll try that tomorrow.
well, i do need the phone, but now im using my old one. until i can finally fix this issue.
What did you mean with the Fastboot mode? when im in the boot menu, i can select Fastboot, but it wont help much, because it will just start the booting again (bootloop). but i dont know if this is what you meant with fastboot.
thanks
Click to expand...
Click to collapse
Okay, but you can also let Windows automaticly search the internet for the drivers.
About fastboot, I don't know if you can backup files with this. (Normally you can use this to flash boot.img etc.) And I don't know, how it works on your device, so ask in your device forum.
Sent from my GT-I9100 using xda app-developers app
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
runingwild said:
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
Click to expand...
Click to collapse
Okay.
Are you talking about flashing stock rom, when you said factory reset?
If not, maybe this helps. (There's a link to flash stock rom in this thread.)
http://forum.xda-developers.com/showthread.php?t=1186401
Sent from my GT-I9100 using xda app-developers app
Hello All,
I posted this on the post for Android Revolution and seem to have run out of interest. This was my post.
Hello,
I messed up and flashed the boot file before I installed the rom file in the internal storage. Now the phone wont boot at all. Can you help me fix this please.
I've tried to search for answers but cant find anything.
I can get into fastboot mode and into CMW mode. So I am able to enter sideload mode but cant get the phone to take the sideload.
I'm afraid I may have formatted the storage too.
Can anyone help me please?
Steve the noob.
Right now I am completely bricked. Tried everything, reinstalled SDK, tried sideloading in a couple of ways, stuck in bootloader or CMW. Try to load and sticks on white HTC page.
PLEASE HELP. I followed all of the directions except for loading the boot first.
Is there a factory reset like the old Oden system that could save me?
Can you get into fastboot?
If so you need to then flash the boot.img via fastboot.
Type fastboot flash (name of file).img in command prompt and you should be good to go!
which boot image?
Looks like you took the wrong version for your phone. You have an AT&T / Telus phone. You can not take an International ROM for your phone.
Only AT&T / TELUS ROMs will work on your phone.
I forgot, you can not bricked your phone since our HTC ONE X+ are S-ON, you just missed something to have it going.
stevespens said:
which boot image?
Click to expand...
Click to collapse
Which CWM are you on? Lloir or the other guys? VERIFY YOU HAVE THE PROPER RECOVERY INSTALLED. IF YOU ARE ON THE AT&T MODEL USE THE AT&T RECOVERY
You can run an RUU (verify proper carrier and model) while at the fastboot screen, or install TWRP and try to sideload using that from the SDK PLATFORM TOOLS FOLDER. You mentioned you have the SDK installed but I need to stress DO NOT USE THE TOOL KIT IT IS WORTHLESS. Make sure you have the official HTC drivers installed that come with HTC SYNC using generic drivers from the tool kit usually yields worthless resutls.
I cant get the rom on the phone. It's completely stuck in a boot loop. Only thing I can do is go into bootloader or CWM. I need to sideload a rom. But it wont let me.
stevespens said:
I cant get the rom on the phone. It's completely stuck in a boot loop. Only thing I can do is go into bootloader or CWM. I need to sideload a rom. But it wont let me.
Click to expand...
Click to collapse
I looked at your android revolution thread. STOP USING THE TOOL KIT. It is a POS.
Kraizk said:
I looked at your android revolution thread. STOP USING THE TOOL KIT. It is a POS.
Click to expand...
Click to collapse
OK. Gotcha. Thanks for the help.
Now what do I do? I am bricked.
stevespens said:
OK. Gotcha. Thanks for the help.
Now what do I do? I am bricked.
Click to expand...
Click to collapse
Read my previous post I gave you instructions. http://forum.xda-developers.com/showpost.php?p=39261003&postcount=5
OK...
Let's start with the correct Recovery for your phone, download link -> Click me!
N.B. -> Rename this file like this -> TWRP2recovery
Put this file in your platform-tools of SDK folder.
Put your phone in bootloader (fastboot USB)
Type this : fasboot devices (Enter... you should have your serial in return)
Then type : fastboot flash recovery TWRP2recovery.img (Enter)
Again type : fastboot erase cache (Enter)
Unplug your USB cable and hit Power button one time
Select Recovery
Hit Power button one time to reboot in Recovery
Try to sideload an ATT&T / TELUS ROM ONLY
Go for Elegancia AT&T/TELUS ROM for this time. (Choose one of your choice in the Download section here)
What are the results?
Well, thanks for all your efforts, but it's a lost cause. I tried the last posters suggestions and it wont let me flash the recovery at all. It's done. I have insurance so I'm just going to smash it and file a claim. I give up. I wont do that again.
Which error you have when you try to flash the recovery? Is your phone recognized at least when you are typing : adb devices ?
stevespens said:
Well, thanks for all your efforts, but it's a lost cause. I tried the last posters suggestions and it wont let me flash the recovery at all. It's done. I have insurance so I'm just going to smash it and file a claim. I give up. I wont do that again.
Click to expand...
Click to collapse
Have you tried just running the RUU? People say it takes a few times. Your phone is not bricked if you can get into fastboot.
Sent from my HTC One X+ using xda premium
thanks for coming back.
Lets give this a try.
Lucky Thirteen said:
Which error you have when you try to flash the recovery? Is your phone recognized at least when you are typing : adb devices ?
Click to expand...
Click to collapse
I got this when I typed "fastboot devices",,,
Then when I typed fastboot recovery to load the file, it showed this
just tried a dif file path and got this
Oh, by the way, my bootloader has been relocked. Can I fix this through bootloader?
First let's install your SDK folder correctly then you will see, it will work flawlessly.
Have a look at my screenshot, see how mine look simple compare to yours.... Yes, I have two devices plugged.
Install your SDK tool like it is explained in this thread.
The version numbers are different but the installation stay the same.
EDIT : What is your computer OS? I will point you to the good htc drivers.
Good evening Ladies & Gents.
Firstly can I say, this site has been my bible, and I am so very very grateful for all the work that everyone has put in to making this site what it is.
Now down to business.
I have an HOX+ and have been flashing for about a year now but still consider myself to be a complete nub! first with hox then i broke it and now hox+. Im in a bit of a predicament.
I flashed a version of aosp 4.4 onto the phone, installed from the zip file, cleared the cache, user data and dalvik.
rebooted, and got stuck in a boot loop.
So i went to my backup and restored from there...
boot loop again.
So i went back into bootloader, then fastboot, and reflashed the viper+ 2.0.1 that I had on before.
But when I got stuck on sending boot
Now im stuck in a boot loop, none of my backups will restore properly.
I fear I am hardbricked as I cant get anything to work...
Any help before I have to be back at work tomorrow would be very helpful! and even more appreciated!
Yours
A very frustrated and stressed British nub
Sorry, also, I have checked through xda and I cant seem to find anything that would explain why I am stuck!
flash the boot.img
from a welsh person who can't understand why people cannot flash rom's correctly
Fastboot
Lloir said:
flash the boot.img
from a welsh person who can't understand why people cannot flash rom's correctly
Click to expand...
Click to collapse
I used "fastboot flash boot boot.img" in my cmd, like i always have done, and this time it doesn't want to work...at all
ryutnm said:
I used "fastboot flash boot boot.img" in my cmd, like i always have done, and this time it doesn't want to work...at all
Click to expand...
Click to collapse
you tried fulling wiping? then just flashing the rom + bootimage after
thanks
Lloir said:
you tried fulling wiping? then just flashing the rom + bootimage after
Click to expand...
Click to collapse
No, does that require different fastboot commands?
i have cwm touch recovery installed. Would that make a difference?
Also, could I just say thank you in advance for your help sir!
ryutnm said:
No, does that require different fastboot commands?
i have cwm touch recovery installed. Would that make a difference?
Also, could I just say thank you in advance for your help sir!
Click to expand...
Click to collapse
Unless you mean the user data and cache wipe.
Then yeah i did that
ryutnm said:
Unless you mean the user data and cache wipe.
Then yeah i did that
Click to expand...
Click to collapse
Data/system/cache
Sent from my Nexus 5 using Tapatalk
ryutnm said:
Good evening Ladies & Gents.
Firstly can I say, this site has been my bible, and I am so very very grateful for all the work that everyone has put in to making this site what it is.
Now down to business.
I have an HOX+ and have been flashing for about a year now but still consider myself to be a complete nub! first with hox then i broke it and now hox+. Im in a bit of a predicament.
I flashed a version of aosp 4.4 onto the phone, installed from the zip file, cleared the cache, user data and dalvik.
rebooted, and got stuck in a boot loop.
So i went to my backup and restored from there...
boot loop again.
So i went back into bootloader, then fastboot, and reflashed the viper+ 2.0.1 that I had on before.
But when I got stuck on sending boot
Now im stuck in a boot loop, none of my backups will restore properly.
I fear I am hardbricked as I cant get anything to work...
Any help before I have to be back at work tomorrow would be very helpful! and even more appreciated!
Yours
A very frustrated and stressed British nub
Click to expand...
Click to collapse
Well the bootlooping has something to do with not flashing the boot.img stated by yourself and lloir. About that bug of "Sending boot.img", it happens to me but I fix it by running CMD as administrator , If that doesnt work, try using a different usb port. Preferably one directly to pc/laptop rather than using a hub. Try a 3.0usb port first, if that doesnt work then 2.0usb port.
P.S Without S-Off you can't become hardbricked. Till now I didn't see a single person who bricked their HOX+ unless he received an S-Off developer phone..
Lloir said:
Data/system/cache
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Im now only getting "waiting for device"
which I can only assume means my pc now doesnt even recognise the phone when its booted in bootloader/fastboot usb mode?
ryutnm said:
Im now only getting "waiting for device"
which I can only assume means my pc now doesnt even recognise the phone when its booted in bootloader/fastboot usb mode?
Click to expand...
Click to collapse
stop....Hammer time...
have you got a rom on the sdcard (in cwm) if yes
wipe data/system/cache
then
reboot into bootloader
fastboot flash boot boot.img
if not ----------
full wipe (as above)
adb sideload romname.zip
then reboot into bootloader as above
Lloir said:
stop....Hammer time...
have you got a rom on the sdcard (in cwm) if yes
wipe data/system/cache
then
reboot into bootloader
fastboot flash boot boot.img
if not ----------
full wipe (as above)
adb sideload romname.zip
then reboot into bootloader as above
Click to expand...
Click to collapse
I have the zip on the internal storage as i dont have "sd/ext" or what ever the extention is. When I bought the phone I never had the sd card. Never was able to save anything onto an sd card.
so should i try installing from the zip? even though the fastboot commands arent working?
or would a sideload skip the fastboot commands?
or am i just being completely retarded
Edt - just tried the sideload using the cmd, and i had error: device not found
so windows isnt recognising my phone...it was working this morning
ryutnm said:
I have the zip on the internal storage as i dont have "sd/ext" or what ever the extention is. When I bought the phone I never had the sd card. Never was able to save anything onto an sd card.
so should i try installing from the zip? even though the fastboot commands arent working?
or would a sideload skip the fastboot commands?
or am i just being completely retarded
Click to expand...
Click to collapse
Why am i being ignored you guys lol. Did you try my solution ?
Terribly Sorry
Ghand0ur said:
Why am i being ignored you guys lol. Did you try my solution ?
Click to expand...
Click to collapse
dude, im so sorry - i didnt even see the post!
i will try now!
sorry again
edt - still no joy as for some reason my phone is no longer being recognised by my pc =[
HTC sync uninstalled ?
you have killed adb (if on windows just kick open taskman and kill adb)
or in cmd\terminal adb kill-server
then do adb devices
reboot pc?
try a different usb cable (maybe the one from your charger if you are not using that one)
*edit the above is assuming you are in recovery
IF NOT in recovery, but fastboot_usb mode
then fastboot devices (but you cannot do jack apart from flash boot image)
IF in recovery, you got a few choices
wait 5-10minutes (don't ask, it's a common issue with the X+ and CWM\TWRP)
put the device in adb sideload for a minute or so (^ see above reason)
i have adb issues in CWM\TWRP myself, especially when i have no rom and so on, so i know your frustration, patience young padwan
looking good so far
Ghand0ur said:
Why am i being ignored you guys lol. Did you try my solution ?
Click to expand...
Click to collapse
Lloir said:
HTC sync uninstalled ?
you have killed adb (if on windows just kick open taskman and kill adb)
or in cmd\terminal adb kill-server
then do adb devices
reboot pc?
try a different usb cable (maybe the one from your charger if you are not using that one)
Click to expand...
Click to collapse
So I tried starting cmd in administrator mode [never had to before]
- Didnt work
- Plugged into a different usb slot as lloir suggested, didnt get the "windows does not recognise this device" this time
restarted cmd as admin like Ghandour suggested.
Just managed to install the viperx+ 2.0.1 rom and i am now setting it up!
THANK YOU SO FREAKING MUCH GUYS [and gals if either of you are female]!
do you know why I had to start using cmd as an administrator?
ryutnm said:
So I tried starting cmd in administrator mode [never had to before]
- Didnt work
- Plugged into a different usb slot as lloir suggested, didnt get the "windows does not recognise this device" this time
restarted cmd as admin like Ghandour suggested.
Just managed to install the viperx+ 2.0.1 rom and i am now setting it up!
THANK YOU SO FREAKING MUCH GUYS [and gals if either of you are female]!
do you know why I had to start using cmd as an administrator?
Click to expand...
Click to collapse
might be because of where you have the adb tools. and i'am 100% male
thanks
Lloir said:
might be because of where you have the adb tools. and i'am 100% male
Click to expand...
Click to collapse
well dude, thank you for your help!
I dont understand why though, ive been using this pc the whole time to flash recovery images and boot images and never had to use admin
Thank you
Also a thank you to Ghand0ur for your help as well!
So very much appreciated
ryutnm said:
Also a thank you to Ghand0ur for your help as well!
So very much appreciated
Click to expand...
Click to collapse
Glad you got it working. Just always try those common solutions:
-Restart PC
-Run as admin
-unplug replug
-reboot phone
-try different usb port
-try different usb cable.
Hi there guys,
I'm new to the forum so apologies if this has been posted in the wrong place.
So I was directed to this forum to attempt to solve a different problem but in my hast, I have caused an even bigger problem!
So initially I was having problems with the new Android Wear update with regards to rooting, so I wanted to find a way to roll the software back or restore the device to stock.
I came across this post http://forum.xda-developers.com/g-watch/development/tool-lg-g-watch-return-to-stock-t3158349 and attempt to do as advised, but half way through the process, the program froze. I then tried to reset the watch from the button at the back, but the watch is now stuck on the fastboot menu. I used ADB to see if I could still connect to the device but no devices can be found.
I have checked the device manager and can see the device as "Android Bootloader Interface" but can't seem to get it past the fastboot menu.
Any help would be much appreciated.
Thanks in advance.
just do it again, as long you can get fastboot, you are safe.
Jaocagomez said:
just do it again, as long you can get fastboot, you are safe.
Click to expand...
Click to collapse
The problem is, the program requires a connection via ADB, but ADB can no longer see the device. So when I try to run it again, nothing happens :/
Montezz1 said:
The problem is, the program requires a connection via ADB, but ADB can no longer see the device. So when I try to run it again, nothing happens :/
Click to expand...
Click to collapse
F the program it is outdated as **** get adb minimal here and the last 5.1.1 images here
Extract to the same folder you put adb minimal and open a terminal here.
do these commands:
Code:
fastboot flash boot nameofboot.img
fastboot flash system nameofsystem.img
(optional) fastboot flash recovery recovery.img
fastboot format/erase data
fastboot format/erase cache
Oh yeah btw if the only problem you had was with rooting just use my guide here and system images from here instead
Xmaster24 said:
F the program it is outdated as **** get adb minimal here and the last 5.1.1 images here
Extract to the same folder you put adb minimal and open a terminal here.
do these commands:
Code:
fastboot flash boot nameofboot.img
fastboot flash system nameofsystem.img
(optional) fastboot flash recovery recovery.img
fastboot format/erase data
fastboot format/erase cache
Oh yeah btw if the only problem you had was with rooting just use my guide here and system images from here instead
Click to expand...
Click to collapse
Hi there,
Thanks for the response.
I have just completed the steps as advised, download the minimal ADB and fastboot and extracted the G Watch images into that file. I opened ADB and ran the following command:
Code:
fastboot flash boot nameofboot.img
But received the following error:
http://i.imgur.com/URh0IsF.png
Any ideas on how to solve that error?
Thanks in advance
Montezz1 said:
Hi there,
Thanks for the response.
I have just completed the steps as advised, download the minimal ADB and fastboot and extracted the G Watch images into that file. I opened ADB and ran the following command:
Code:
fastboot flash boot nameofboot.img
But received the following error:
http://i.imgur.com/URh0IsF.png
Any ideas on how to solve that error?
Thanks in advance
Click to expand...
Click to collapse
Check the bootloader lock status and report back
Xmaster24 said:
Check the bootloader lock status and report back
Click to expand...
Click to collapse
Secure boot - Enabled
Lock state - unlocked.
I did try to unlock it again just to make sure and it is showing that is it unlocked.
Montezz1 said:
Secure boot - Enabled
Lock state - unlocked.
I did try to unlock it again just to make sure and it is showing that is it unlocked.
Click to expand...
Click to collapse
Do this command:
flashing get_unlock_ability
and also try and flash another partition eg system and report back what happens
Xmaster24 said:
Do this command:
flashing get_unlock_ability
and also try and flash another partition eg system and report back what happens
Click to expand...
Click to collapse
Hi,
The result from the flashing get_unlock_ability command is provided here:
http://i.imgur.com/jczJRST.png
I attempted to flash the system image and received the following error:
http://i.imgur.com/83RXdFi.png
The watch responses the same as when attempting to flash the boot image and is stuck on "Downloading".
I also tried to flash the recovery image and received the same error as shown when flashing the boot image.
Thanks
Montezz1 said:
Hi,
The result from the flashing get_unlock_ability command is provided here:
http://i.imgur.com/jczJRST.png
I attempted to flash the system image and received the following error:
http://i.imgur.com/83RXdFi.png
The watch responses the same as when attempting to flash the boot image and is stuck on "Downloading".
I also tried to flash the recovery image and received the same error as shown when flashing the boot image.
Thanks
Click to expand...
Click to collapse
Looks like it is either that adb minimal is messed up (I use the full 1gb sdk) or there is a driver problem or you can try running cmd as administrator instead
Xmaster24 said:
Looks like it is either that adb minimal is messed up (I use the full 1gb sdk) or there is a driver problem or you can try running cmd as administrator instead
Click to expand...
Click to collapse
I did try adb from the SDK that you've mentioned and have had the same results.
I also run in Administrator every time.
What I have just noticed with regards to the drivers is the change in the name of the device in device manager. Previously it showed as "Android Composite ADB Interface" but now it is showing as "Android Bootloader Interface".
I believe that might just be because the watch is stuck on the bootloader menu so that is how it is displayed, but it could be the cause.
Montezz1 said:
I did try adb from the SDK that you've mentioned and have had the same results.
I also run in Administrator every time.
What I have just noticed with regards to the drivers is the change in the name of the device in device manager. Previously it showed as "Android Composite ADB Interface" but now it is showing as "Android Bootloader Interface".
I believe that might just be because the watch is stuck on the bootloader menu so that is how it is displayed, but it could be the cause.
Click to expand...
Click to collapse
Your pc seems to be having trouble writing anything to the watch so if it is not the sdk then it must be your driver or bootloader
---------- Post added at 12:49 PM ---------- Previous post was at 12:43 PM ----------
Just checked the tool and it shouldn't do any harm at all to your watch unless you tried the bootloader lock so it must be your drivers
Xmaster24 said:
Your pc seems to be having trouble writing anything to the watch so if it is not the sdk then it must be your driver or bootloader
---------- Post added at 12:49 PM ---------- Previous post was at 12:43 PM ----------
Just checked the tool and it shouldn't do any harm at all to your watch unless you tried the bootloader lock so it must be your drivers
Click to expand...
Click to collapse
Hi there,
I've just tried to update the drivers but they seem to be up to date.
Yeah, the only reason I thought the program had done some damage is because it froze which resulted in getting stuck on the fastboot menu, but you've more knowledge so I guess that's not the issue.
I'm not entirely sure what else can be done here. I think I might have to just get another watch and stop the update as that is when all the problems occurred.
If you can think of anything else to try, I would be willing to give it a go but don't worry yourself too much if you're out of ideas.
I really appreciate your help up to this point anyways
Thanks
Montezz1 said:
Hi there,
I've just tried to update the drivers but they seem to be up to date.
Yeah, the only reason I thought the program had done some damage is because it froze which resulted in getting stuck on the fastboot menu, but you've more knowledge so I guess that's not the issue.
I'm not entirely sure what else can be done here. I think I might have to just get another watch and stop the update as that is when all the problems occurred.
If you can think of anything else to try, I would be willing to give it a go but don't worry yourself too much if you're out of ideas.
I really appreciate your help up to this point anyways
Thanks
Click to expand...
Click to collapse
Try and lock your watch with
fastboot oem lock
then try again with
fastboot oem unlock
Also when was the first time you flashed anything anyway?
Xmaster24 said:
Try and lock your watch with
fastboot oem lock
then try again with
fastboot oem unlock
Also when was the first time you flashed anything anyway?
Click to expand...
Click to collapse
I was able to lock and then unlock, and the device notified me that it was erasing, but when I try to start the device, it still brings be back to the fastboot menu.
Do you mean flashing devices in general or flashing this specific device?
Montezz1 said:
I was able to lock and then unlock, and the device notified me that it was erasing, but when I try to start the device, it still brings be back to the fastboot menu.
Do you mean flashing devices in general or flashing this specific device?
Click to expand...
Click to collapse
This device I just want to know if you ever actually successfully flashed anything to this device
Xmaster24 said:
This device I just want to know if you ever actually successfully flashed anything to this device
Click to expand...
Click to collapse
The first attempting of flashing anything to this device I believe was when using the Return to Stock tool.
I choose the "Install ROM" option which I can see from the script attempts to flash.
So I guess it's never been successful on this device.
Montezz1 said:
The first attempting of flashing anything to this device I believe was when using the Return to Stock tool.
I choose the "Install ROM" option which I can see from the script attempts to flash.
So I guess it's never been successful on this device.
Click to expand...
Click to collapse
This whole problem started due to the fact that I couldn't see the device using ADB, so I tried to look for a method to solve that which then caused the problem I'm having now.
The only variable I can put it down to is an update that was pushed to the watch as prior to that, I had no problems at all.
Montezz1 said:
This whole problem started due to the fact that I couldn't see the device using ADB, so I tried to look for a method to solve that which then caused the problem I'm having now.
The only variable I can put it down to is an update that was pushed to the watch as prior to that, I had no problems at all.
Click to expand...
Click to collapse
Yup sounds like a driver problem for sure uninstall the watch drivers and download the google drivers here
Xmaster24 said:
Yup sounds like a driver problem for sure uninstall the watch drivers and download the google drivers here
Click to expand...
Click to collapse
I do not believe it...
After all of this, it was the drivers...
I don't get it though!! I tried to reinstall them before and nothing changed!
It's only when I completely deleted them and reinstalled that it worked.
Honestly dude, thank you so much for your help and patience. My watch is now working and paired with my phone.
I'm waiting for it to sync but hopefully I will be able to run ADB and all will be well again
Thanks you so much again.
I want to keep this thread short.
So lets get to work.
Everything here is about Huawei y-625xx phones.
Don't try this on any other phone or u gonna get ur phone bricked.
I will not be responsible if anything happens to ur phone.
This things works perfectly as it was tested by many user's.
I don't have this phone,my cousin does and I did it for him.
So it should work for u too.
ROOT
Get the latest kingroot app from here
Turn on data
click root
wait until it reboots ur phone and shows its rooted.
U can easily root using '360 root app' now!
And its completely safe
See reply #50 for details
RECOVERY
here's a video tutorial from The Best about installing T.W.R.P on y-625.
Here's the steps that r shown in this video.
Written by xda member @AkaruiTenshi
First of all, you will need to install abd and fastboot drivers if you're on a windows pc, if you use linux, just install abd and fastboot packages and dependencies for your distro.Connect the phone in the computer using an usb cable, and activate the debug in the phoneNext step, on windows open the command line...
In linux, just open the terminalNow call the abd, just type this (whitout quotes):
"abd -start-server"
Wait a little bit, in your phone will apear a mensage to validare the abd acess to the phone, just say yes...Again in the terminal or command line,
type:"abd reboot bootloader"(do not wait until the phone reboot).
type
"fastboot boot recovery.img".
After this, the twrp will boot in your phone, without installation (if you install the twrp, your warranty is void),
you can use twrp for backup your stock rom for exemple...
If you want to install the twrp, just change the last comand to:
"fastboot flash recovery recovery.img"
Method two---
Simply grab flashify or mobile uncle tool app and flash the recovery.img with those.
These 2 app needs root access.
ROMS
Sorry guys.
No luck for rom yet.
But my friend is trying to port Carbon kk on this device.
If he finishes it,I will post here...
Here's stock rom--
http://forum.xda-developers.com/general/xda-assist/stock-rom-huawei-y625-u43-t3288104
Regards,BatDroid
reserved
no huawei user's??!! :-/
now that's really disheartening
I need stock recovery.img for y625-u51 Please help!
BabaPena said:
I need stock recovery.img for y625-u51 Please help!
Click to expand...
Click to collapse
Here's stock rom.
Get it from here.
http://forum.xda-developers.com/general/xda-assist/stock-rom-huawei-y625-u43-t3288104
bump
Thank you for making this tread! I am very excited to hear that someone is trying to port a ROM for our device! :fingers-crossed:
matevt said:
Thank you for making this tread! I am very excited to hear that someone is trying to port a ROM for our device! :fingers-crossed:
Click to expand...
Click to collapse
Actually my friend stopped for his exam.
And there isn't any reply from user's.
Glad to see someone replied to this thread.
BatDroid said:
Actually my friend stopped for his exam.
And there isn't any reply from user's.
Glad to see someone replied to this thread.
Click to expand...
Click to collapse
Yep. Our device ins't very popular hence the low user activity here :\ but I've seen people asking for ROMs/EMUI updates.
Hope your friend continues development! Fingers crossed!
Btw I have a y625-U51 firmware. I'm not exactly sure what is with the "Uxx" versions.
https://drive.google.com/file/d/0B4mU_jy0onxoV0E0RlBmSFhYeEk/view?usp=sharing
matevt said:
Btw I have a y625-U51 firmware. I'm not exactly sure what is with the "Uxx" versions.
https://drive.google.com/file/d/0B4mU_jy0onxoV0E0RlBmSFhYeEk/view?usp=sharing
Click to expand...
Click to collapse
xx means supported for all.
BatDroid said:
xx means supported for all.
Click to expand...
Click to collapse
Oh I meant it like "U+number" like U21, U32, U48, U51
Can i install version u51 to y625-u21?
nighthawk84 said:
Can i install version u51 to y625-u21?
Click to expand...
Click to collapse
I have asked Huawei support for a simmilar question here's the reply:
"...Given that your device is manufactured for Bulgaria, you may refer to http://consumer.huawei.com/bg/support/index.htm to select your country region of support to be assisted accordingly.
Kindly be inform that Huawei strongly do not suggest the customers to download upgrade from a different region as it will affect the device performance and void the warranty. "
Anyone know how to get into fastboot without pc?
Thank You for creating this thread.Is there any way to port Lollipop Roms to this device?
---------- Post added at 06:13 PM ---------- Previous post was at 06:12 PM ----------
boxter7 said:
Anyone know how to get into fastboot without pc?
Click to expand...
Click to collapse
Remove battery, place it back in and press all physical buttons till phone shows boot logo.
I try this but phone frozen after show logo...
boxter7 said:
I try this but phone frozen after show logo...
Click to expand...
Click to collapse
That's because it is on fastboot?
Tadael said:
That's because it is on fastboot?
Click to expand...
Click to collapse
Hey tadael, I try but always says that devices not connect. But when I try form recovery adb sideload work.