Related
I am stuck my phone. It does not proceed beyond the initial screen after normal boot and does not show adb interface in the device mmanager of my laptop. When I boot into Safe Mode, it does show adb interface in the device manager of my laptop, however, adb on command prompt does not show any device.
This indicates adb interface does not establish for a normal boot and for Safe mode device is not recognised. I can get into recovery and have tried flashing boot.img through update.zip, however, it returns with Installation abroted message. Here, it seems bootlogger is locked.
I have complete romdump of my phone with boot.img and recovery.img.
Please help!!!
vijkap said:
I am stuck my phone. It does not proceed beyond the initial screen after normal boot and does not show adb interface in the device mmanager of my laptop. When I boot into Safe Mode, it does show adb interface in the device manager of my laptop, however, adb on command prompt does not show any device.
This indicates adb interface does not establish for a normal boot and for Safe mode device is not recognised. I can get into recovery and have tried flashing boot.img through update.zip, however, it returns with Installation abroted message. Here, it seems bootlogger is locked.
I have complete romdump of my phone with boot.img and recovery.img.
Please help!!!
Click to expand...
Click to collapse
Give some more info like device name, root status, current recovery, recipe for the mess you created out of it etc.
Sent from my HTC Explorer A310e using Tapatalk
MSF Jarvis said:
Give some more info like device name, root status, current recovery, recipe for the mess you created out of it etc.
Sent from my HTC Explorer A310e using Tapatalk
Click to expand...
Click to collapse
This post was posted on 29th March 2011
Salman Al-Badgail said:
This post was posted on 29th March 2011
Click to expand...
Click to collapse
I've been making these kind of mistakes quite often recently, maybe I need a break after all
MSF Jarvis said:
I've been making these kind of mistakes quite often recently, maybe I need a break after all
Click to expand...
Click to collapse
Doesn't matter, finally he got answer after 5yrs
Salman Al-Badgail said:
Doesn't matter, finally he got answer after 5yrs
Click to expand...
Click to collapse
He actually posted on one of my ROM threads, that led me to here
Salman Al-Badgail said:
Doesn't matter, finally he got answer after 5yrs
Click to expand...
Click to collapse
kill me!
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
Hi,
I'm not a newbie to Android by any measure, but this is my wife's phone, not mine (I have a Nexus 4) so I'm not familiar with a lot of the LG stuff.
Anyways, I rooted her phone to get rid of some of the bloatware and the stupid Qslide thing, and also to edit the build.prop so Netflix will have the Chromecast button. I had deleted quite a few bloatware system apps, and rebooted, everything was fine. I deleted a few more, then edited the build.prop. Rebooted.
Now it shows the LG logo, but then the screen goes blank, but is still on (you can see the backlight) and never boots. I only removed a few more of the LG and Tmobile apps and edited the model and manufacturer in the build.prop
Do I have any easy options to fix this? Or do I need to flash the KDZ?
Flash kdz then install cwm then backup the stock ROM THEN do your mods. Every time every phone. Good luck
Sent from my LG-P769(20F) using the xda-developers app. If I helped you please hit the "thanks" button.
swm5126 said:
Hi,
I'm not a newbie to Android by any measure, but this is my wife's phone, not mine (I have a Nexus 4) so I'm not familiar with a lot of the LG stuff.
Anyways, I rooted her phone to get rid of some of the bloatware and the stupid Qslide thing, and also to edit the build.prop so Netflix will have the Chromecast button. I had deleted quite a few bloatware system apps, and rebooted, everything was fine. I deleted a few more, then edited the build.prop. Rebooted.
Now it shows the LG logo, but then the screen goes blank, but is still on (you can see the backlight) and never boots. I only removed a few more of the LG and Tmobile apps and edited the model and manufacturer in the build.prop
Do I have any easy options to fix this? Or do I need to flash the KDZ?
Click to expand...
Click to collapse
Yes, offline flash the kdz. Always backup your rom whenever you so something like that.
Sent from my LG-P769 using Tapatalk 4
If it's just the build.prop causing it not to boot, you can flash (with fastboot) the boot.img for the kdz you are on. Look at my signature on how to extract it.
If that doesn't work, flash the ice cream x & u partitions for p769 in fastboot, and then run offline flash
Fastboot info and help
http://forum.xda-developers.com/showthread.php?p=43703982
Install the locked bootloader cwm
http://forum.xda-developers.com/showthread.php?t=2095825
And use this busybox
https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete
Next time make a backup (make sure the backup is good, try to restore it)
CM 10.1 P769
kuma82 said:
If it's just the build.prop causing it not to boot, you can flash (with fastboot) the boot.img for the kdz you are on. Look at my signature on how to extract it.
If that doesn't work, flash the ice cream x & u partitions for p769 in fastboot, and then run offline flash
Fastboot info and help
http://forum.xda-developers.com/showthread.php?p=43703982
Install the locked bootloader cwm
http://forum.xda-developers.com/showthread.php?t=2095825
And use this busybox
https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete
Next time make a backup (make sure the backup is good, try to restore it)
CM 10.1 P769
Click to expand...
Click to collapse
Get outta here kuma, no one wants you here. -___- lol im jk.
Sent from my LG-P769 using Tapatalk 4
Lol, okay
NOT!
CM 10.1 P769
kuma82 said:
Lol, okay
NOT!
CM 10.1 P769
Click to expand...
Click to collapse
Thanks for the suggestions guys. I've tried the offline KDZ flashing it, but I can't get my computer (tried two actually, mine and my wife's laptop) to do anything once its in the S/W Upgrade mode. I used the method previously to update her phone the JB when Tmobile pulled the update. Since then it downloaded the most recent OTA. But anyways, I don't know why it wont work. It just continally tells me that my phone isn't connected, even though I'm using the latest drivers and the phone shows up correctly in the device manager. It's driving me nuts since it worked previously!
Any ideas?
swm5126 said:
Thanks for the suggestions guys. I've tried the offline KDZ flashing it, but I can't get my computer (tried two actually, mine and my wife's laptop) to do anything once its in the S/W Upgrade mode. I used the method previously to update her phone the JB when Tmobile pulled the update. Since then it downloaded the most recent OTA. But anyways, I don't know why it wont work. It just continally tells me that my phone isn't connected, even though I'm using the latest drivers and the phone shows up correctly in the device manager. It's driving me nuts since it worked previously!
Any ideas?
Click to expand...
Click to collapse
What variant do you have 769? Flash recovery.img in fastboot.
Sent from my LG-P769 using Tapatalk 4
swm5126 said:
Hi,
I'm not a newbie to Android by any measure, but this is my wife's phone, not mine (I have a Nexus 4) so I'm not familiar with a lot of the LG stuff.
Anyways, I rooted her phone to get rid of some of the bloatware and the stupid Qslide thing, and also to edit the build.prop so Netflix will have the Chromecast button. I had deleted quite a few bloatware system apps, and rebooted, everything was fine. I deleted a few more, then edited the build.prop. Rebooted.
Now it shows the LG logo, but then the screen goes blank, but is still on (you can see the backlight) and never boots. I only removed a few more of the LG and Tmobile apps and edited the model and manufacturer in the build.prop
Do I have any easy options to fix this? Or do I need to flash the KDZ?
Click to expand...
Click to collapse
boot into stock recovery "vol+"&"home"+"power"
adb should work and you can :
adb push busybox /tmp
adb push build.prop /tmp
adb shell
try "su" or "/system/bin/su" or "/system/xbin/su"
chmod 755 /tmp/busybox
/tmp/busybox mount -o remount,rw -t auto /system
/tmp/busybox cp /tmp/build.prop /system
/tmp/busybox chmod 644 /system/build.prop
swm5126 said:
Thanks for the suggestions guys. I've tried the offline KDZ flashing it, but I can't get my computer (tried two actually, mine and my wife's laptop) to do anything once its in the S/W Upgrade mode. I used the method previously to update her phone the JB when Tmobile pulled the update. Since then it downloaded the most recent OTA. But anyways, I don't know why it wont work. It just continally tells me that my phone isn't connected, even though I'm using the latest drivers and the phone shows up correctly in the device manager. It's driving me nuts since it worked previously!
Any ideas?
Click to expand...
Click to collapse
Sorry I didn't break it down enough for you. You have to get fastboot up and running. Jellybean does not operate when starting in S/W mode, that's why you get the connection problem. Now ice cream, does operate when starting in the S/W upgrade mode. With fastboot you can flash everything you need to get the offline flash working. These three links are all the info you need.
Lelus fastboot
Select the option to flash x & u for p769
1. http://forum.xda-developers.com/showthread.php?p=41768774
Help if you can't get fastboot installed
2. http://forum.xda-developers.com/showpost.php?p=43210006&postcount=15
Info on how to use fastboot manually. Not really needed because lelus has everything needed in the first link.
3. http://forum.xda-developers.com/showthread.php?p=43642515
Please read each thread before starting and read the instructions txt found in Lelus fastboot zip
Sorry I told you flashing the boot.IMG will help(was thinking of default.prop), I just remembered the build.prop is in the system partition.
CM 10.1 P769
---------- Post added at 11:00 PM ---------- Previous post was at 10:52 PM ----------
Lelus said:
boot into stock recovery "vol+"&"home"+"power"
adb should work and you can :
adb push busybox /tmp
adb push build.prop /tmp
adb shell
try "su" or "/system/bin/su" or "/system/xbin/su"
chmod 755 /tmp/busybox
/tmp/busybox mount -o remount,rw -t auto /system
/tmp/busybox cp /tmp/build.prop /system
/tmp/busybox chmod 644 /system/build.prop
Click to expand...
Click to collapse
Thanks for sharing, I didn't know stock recovery allowed ADB commands :thumbup:
CM 10.1 P769
swm5126 said:
Hi,
Do I have any easy options to fix this? Or do I need to flash the KDZ?
Click to expand...
Click to collapse
Factory LG mobile support tool has an option to "update recovery" in top right menu. This will download latest factory rom via internet and reflash phone in software update mode to reset everything.
http://www.softpedia.com/get/Mobile-Phone-Tools/Others/LGMobile-Support-Tool.shtml
Works well.
might have to set phone into software update mode by pressing vol up and then inserting usb cable..
kuma82 said:
Please read each thread before starting and read the instructions txt found in Lelus fastboot zip
Click to expand...
Click to collapse
Ok, I got the timing down and fastboot seems to come up, but after I can see the logo on my phone with the v 0.5, the script just says < waiting for device >. Thats where it should flash the ICS xloader? Or am I missing something and I should flash the JB images with fastboot? Where can I get the images?
swm5126 said:
Ok, I got the timing down and fastboot seems to come up, but after I can see the logo on my phone with the v 0.5, the script just says < waiting for device >. Thats where it should flash the ICS xloader? Or am I missing something and I should flash the JB images with fastboot? Where can I get the images?
Click to expand...
Click to collapse
Just kidding, got it figured out. Flashed the ICS xloader. Looks like its letting me restore finally! Thanks!
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.
My son (1.5 years) somehow made a factory reset of my Xperia Z2, Android 6.01, D6503, 23.5.A.0.575.
All photos gone. No, they where not on the SD. No, not in any cloud service.
If I could get a dd of the partition, I might be able to use some linux-tools like scalpel off the phone for deep examination
Found this, but su is required: www dot nburles.co .uk
/android/recovering-data-from-an-android-device-using-dd
(Sorry for url-format First post, not allowed to paste outside links...)
I read hundreds of pages of rooting (but still don't get it) and i have no clue what it does to the internal memory, and I don't wan't to touch it too much as there might be some recoverable data left.
What is the minimum I really need to do?
I.e. I just need "su"!
I already have (on Windows) adb installed and unlocked bootloader using fastboot (with a code from Sony)
regards Martin/
martinwahlstrom said:
My son (1.5 years) somehow made a factory reset of my Xperia Z2, Android 6.01, D6503, 23.5.A.0.575.
All photos gone. No, they where not on the SD. No, not in any cloud service.
If I could get a dd of the partition, I might be able to use some linux-tools like scalpel off the phone for deep examination
Found this, but su is required: www dot nburles.co .uk
/android/recovering-data-from-an-android-device-using-dd
(Sorry for url-format First post, not allowed to paste outside links...)
I read hundreds of pages of rooting (but still don't get it) and i have no clue what it does to the internal memory, and I don't wan't to touch it too much as there might be some recoverable data left.
What is the minimum I really need to do?
I.e. I just need "su"!
I already have (on Windows) adb installed and unlocked bootloader using fastboot (with a code from Sony)
regards Martin/
Click to expand...
Click to collapse
You only have to flash a custom kernel
Ok, which one do you recommend? (Please don't tell I need to create one myself!)
And then just flash it with flashtool?
martinwahlstrom said:
Ok, which one do you recommend? (Please don't tell I need to create one myself!)
And then just flash it with flashtool?
Click to expand...
Click to collapse
Flash abricot kernel 8.1 via flashtool using fastboot mode or via adb
dylanel98 said:
Flash abricot kernel 8.1 via flashtool using fastboot mode or via adb
Click to expand...
Click to collapse
Ok, finally managed to flash the kernel.
Still no root access though... Now what?
(Thx so far anyway!)
martinwahlstrom said:
Ok, finally managed to flash the kernel.
Still no root access though... Now what?
(Thx so far anyway!)
Click to expand...
Click to collapse
Reboot the phone in recovery mode and flash superSU zip and your phone should be rooted
dylanel98 said:
Reboot the phone in recovery mode and flash superSU zip and your phone should be rooted
Click to expand...
Click to collapse
Done - but does not work!
SuperSU app tells me no su is found.
Using adb, su exists but have no apparent effect.
Permission denied when trying a simple "ls -l" of various dir's.
martinwahlstrom said:
Done - but does not work!
SuperSU app tells me no su is found.
Using adb, su exists but have no apparent effect.
Permission denied when trying a simple "ls -l" of various dir's.
Click to expand...
Click to collapse
Btw, installed Update-SuperSU-v2.02.zip from SD using TWRP.
Great... Now in bootloop... Help!
Edit: Recovered from looping.
Still no root after several tries.