Hello. I downloaded TWRP 2.6.0.0 from here: http://teamw.in/project/twrp2/185 for my SGP311.
And flashed it using instructions on page:
su
dd if=/sdcard/fotakernel.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Then I couldn't figure out how to boot into the recovery! I decided this might be the time to READ the page
They say something about CM. I don't want to flash any ROM yet, I'm on stock 4.1.1 (build 370), I just want to boot the device into my TWRP and couldn't find instructions.
So how do I start TWRP?
My Gnexi said:
Hello. I downloaded TWRP 2.6.0.0 from here: http://teamw.in/project/twrp2/185 for my SGP311.
And flashed it using instructions on page:
su
dd if=/sdcard/fotakernel.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Then I couldn't figure out how to boot into the recovery! I decided this might be the time to READ the page
They say something about CM. I don't want to flash any ROM yet, I'm on stock 4.1.1 (build 370), I just want to boot the device into my TWRP and couldn't find instructions.
So how do I start TWRP?
Click to expand...
Click to collapse
im not sure but i think its volume down instead of volume up
arcsuser said:
im not sure but i think its volume down instead of volume up
Click to expand...
Click to collapse
Not working, volume down starts with "safe mode", other combinations start normally or blinking LED or do nothing at all, how do I get to my TWRP?
should have bought Nexus 10
My Gnexi said:
Not working, volume down starts with "safe mode", other combinations start normally or blinking LED or do nothing at all, how do I get to my TWRP?
should have bought Nexus 10
Click to expand...
Click to collapse
safe mode? i didnt see any safe mode when i tried it.. maybe you're in the wrong way.. lol
anyway i got my twrp from this Post
and to boot to twrp its volume down..
How to use:
At boot, once you feel the phone vibrate and see the green led;
- press VOL-UP for CWM;
- press VOL-DOWN for TWRP.
Click to expand...
Click to collapse
Hope it helps
arcsuser said:
safe mode? i didnt see any safe mode when i tried it.. maybe you're in the wrong way.. lol
anyway i got my twrp from this Post
and to boot to twrp its volume down..
Hope it helps
Click to expand...
Click to collapse
is CWM built-in to the device? or just in case the person is using CWM instead of TWRP? thanks
mrjayviper said:
is CWM built-in to the device? or just in case the person is using CWM instead of TWRP? thanks
Click to expand...
Click to collapse
Its a dual recovery sir
But i believe twrp still has a bug i think, not sure..
Sent from my SGP311 using xda app-developers app
arcsuser said:
Its a dual recovery sir
But i believe twrp still has a bug i think, not sure..
Sent from my SGP311 using xda app-developers app
Click to expand...
Click to collapse
I can have twrp and cwm at the same time? first time I've heard of that. thanks
mrjayviper said:
I can have twrp and cwm at the same time? first time I've heard of that. thanks
Click to expand...
Click to collapse
Yah, you can have it both at the same time from the post i gave..
But like i said twrp on this one has bug..
Sent from my SGP311 using xda app-developers app
arcsuser said:
Its a dual recovery sir
But i believe twrp still has a bug i think, not sure..
Sent from my SGP311 using xda app-developers app
Click to expand...
Click to collapse
Well, I did it!
I dd-restored the fotakernel to what it was before. Then I flashed using the post you linked and indeed I have 2 recoveries.
It seems like booting into recovery is not as easy as in my Galaxy Nexus. You have to tap the volume repeatedly while booting, hoping it will work.
Saying that twrp has a bug is a little understatement. I couldn't get out!
Tried to adb reboot but got "???????????? no permissions"
Eventually solved it by putting
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", ATTR{idProduct}=="6182", MODE="0660", OWNER="<my user name>" in /etc/udev/rules.d/51-android.rules
But for a few minutes I was worried I have to wait until the battery runs out, or worse, use my Windows laptop
My Gnexi said:
Well, I did it!
I dd-restored the fotakernel to what it was before. Then I flashed using the post you linked and indeed I have 2 recoveries.
It seems like booting into recovery is not as easy as in my Galaxy Nexus. You have to tap the volume repeatedly while booting, hoping it will work.
Saying that twrp has a bug is a little understatement. I couldn't get out!
Tried to adb reboot but got "????????????no permissions"
Eventually solved it by putting
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", ATTR{idProduct}=="6182", MODE="0660", OWNER="<my user name>" in /etc/udev/rules.d/51-android.rules
But for a few minutes I was worried I have to wait until the battery runs out, or worse, use my Windows laptop
Click to expand...
Click to collapse
Me too on my first try of twrp i couldnt get out, i got that locked thing lol
But still i managed by hard reset
Sent from my SGP311 using xda app-developers app
arcsuser said:
hard reset
Click to expand...
Click to collapse
How did you do that?
My Gnexi said:
How did you do that?
Click to expand...
Click to collapse
hold volume up and power for 10-15secs or more or until it reboots
Related
Hey guysi have a question...yesterday I flashed the new ruu and I got the ics Leak. While trying to root it I can't seem to be able toboot to recovery or anything...I hold down.volume and power button but it boots straight into the Rom. Did I miss something? Should I feflash recovery with ph85img? I'm not home ATM but id love some advice before I starton it xD
Sent from my HTC_Amaze_4G using XDA
knifeproz said:
Hey guysi have a question...yesterday I flashed the new ruu and I got the ics Leak. While trying to root it I can't seem to be able toboot to recovery or anything...I hold down.volume and power button but it boots straight into the Rom. Did I miss something? Should I feflash recovery with ph85img? I'm not home ATM but id love some advice before I starton it xD
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
You have to battery pull and flash a new recovery since the ruu flashed stock recovery
sportsstar89 said:
You have to battery pull and flash a new recovery since the ruu flashed stock recovery
Click to expand...
Click to collapse
how do i flash another recovery without being able to get to white screen with fastboot etc
knifeproz said:
how do i flash another recovery without being able to get to white screen with fastboot etc
Click to expand...
Click to collapse
You battery pull to get to that screen you take battery out put it back in hold vol down and power then flash new recovery
Sent from my HTC_Amaze_4G using xda premium
sportsstar89 said:
You battery pull to get to that screen you take battery out put it back in hold vol down and power then flash new recovery
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
woah i did what you said and well idk what happened but it started goign through the process of junupuntbear? idk it was the green arrows with a hard drive or whagver in the middle then my phone rebooted???
What i did: flashed the recovery;
got into Hboot; hit recovery
the weird screen happened
phone rebooted
booting up now....
edit: doing this made my whole phone basically...wipe...
knifeproz said:
woah i did what you said and well idk what happened but it started goign through the process of junupuntbear? idk it was the green arrows with a hard drive or whagver in the middle then my phone rebooted???
What i did: flashed the recovery;
got into Hboot; hit recovery
the weird screen happened
phone rebooted
booting up now....
edit: doing this made my whole phone basically...wipe...
Click to expand...
Click to collapse
Install ENG HBOOT. Then boot into bootloader and flash a recovery. I can confirm that it works.
hasoon2000 said:
Install ENG HBOOT. Then boot into bootloader and flash a recovery. I can confirm that it works.
Click to expand...
Click to collapse
I actually did that; i made a video and ill upload it in a sec so you can see what my problem is
Quality is pretty bad because its my old HD2 but yeah i hope you get the gist of it
knifeproz said:
I actually did that; i made a video and ill upload it in a sec so you can see what my problem is
Click to expand...
Click to collapse
Sounds good.
http://www.youtube.com/watch?v=ZKir3r8u0Mc&feature=youtu.be
Video is up
knifeproz said:
http://www.youtube.com/watch?v=ZKir3r8u0Mc&feature=youtu.be
Video is up
Click to expand...
Click to collapse
The Low FPS was killing me lol. When you're in bootloader. Select fastboot. You are in Hboot mode. Click Fastboot, download my toolkit from here.
http://www.android-dev.us/showthrea...ne-Toolkit-V3-1-4-9-2012-PERM-ROOT-Noob-Proof
Flash CWM and you will be good to go.
hasoon2000 said:
The Low FPS was killing me lol. When you're in bootloader. Select fastboot. You are in Hboot mode. Click Fastboot, download my toolkit from here.
http://www.android-dev.us/showthrea...ne-Toolkit-V3-1-4-9-2012-PERM-ROOT-Noob-Proof
Flash CWM and you will be good to go.
Click to expand...
Click to collapse
I'll get on it ^^ thanks
andsorry for the low fps and whatnot xD my HD2's camera is pretty bad lmao
worked like a charm many thakns!
One more question though: i can't seem to normally boot into Hboot or whatever its called now unless i pull battery, is there a fix for that?
So, I downloaded the necessary files too go from CM9 to CM10 via recovery in my nook tablet and I did a factory reset. From there, I flashed the cm10-acclaim-0.05.1-full-of-bugs.zip. After flash I fixed permissions, wiped Dalvik, took out my sd card and hit reboot. It boots into the universal bootloader, but that's about it...please help! I can't find a solution! Please and thank you so much!
kameronamurray said:
So, I downloaded the necessary files too go from CM9 to CM10 via recovery in my nook tablet and I did a factory reset. From there, I flashed the cm10-acclaim-0.05.1-full-of-bugs.zip. After flash I fixed permissions, wiped Dalvik, took out my sd card and hit reboot. It boots into the universal bootloader, but that's about it...please help! I can't find a solution! Please and thank you so much!
Click to expand...
Click to collapse
What recovery did you use to flash the rom? What version?
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
What recovery did you use to flash the rom? What version?
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
I honestly couldn't tell you. I just know that when I boot into recovery, the n screen flashes, than a BIG n flashes then goes to the recovery screen. It's so confusing! Lol
kameronamurray said:
I honestly couldn't tell you. I just know that when I boot into recovery, the n screen flashes, than a BIG n flashes then goes to the recovery screen. It's so confusing! Lol
Click to expand...
Click to collapse
ok lets put it this way... in your recovery how do you navigate the menu? if you do it by the volume up, down and n button then you are using cwm.
if its all touch screen based then its twrp...
ShinnAsuka said:
ok lets put it this way... in your recovery how do you navigate the menu? if you do it by the volume up, down and n button then you are using cwm.
if its all touch screen based then its twrp...
Click to expand...
Click to collapse
Oh it's cwm for sure!
kameronamurray said:
Oh it's cwm for sure!
Click to expand...
Click to collapse
ok can you tell me what version of cwm you have? usually it shows it in the top left corner when you go into cwm.
ShinnAsuka said:
ok can you tell me what version of cwm you have? usually it shows it in the top left corner when you go into cwm.
Click to expand...
Click to collapse
I'm pretty sure it is 5.0.2.8 if I'm not mistaken. I tried to remember it but I'm away from it right now.
I was having reboot issues with that ROM. I ended up putting the original acclaim_update.zip file on a blank SD card, factory resetting it, then rerooting.
kameronamurray said:
I'm pretty sure it is 5.0.2.8 if I'm not mistaken. I tried to remember it but I'm away from it right now.
Click to expand...
Click to collapse
That's your.problem then. Flashing any rom with a 3.0+ kernel using that cwm will result in a bootloop. so eight now you need to flash a newer cwm and then try flashing cm10 again.
look in the dev section for a newer recovery.
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
That's your.problem then. Flashing any rom with a 3.0+ kernel using that cwm will result in a bootloop. so eight now you need to flash a newer cwm and then try flashing cm10 again.
look in the dev section for a newer recovery.
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
You're a genius! Thank you so much!
While using titanium backup i froze all apps. (too hard headed I didn't care about the warning) but I made backups on apps that I think was important. It was working just fine. But when I restarted it. The logo just appeared. It's almost a day and it's still like that please help me gosh I hoped it wasn't bricked.
DearestMartha said:
While using titanium backup i froze all apps. (too hard headed I didn't care about the warning) but I made backups on apps that I think was important. It was working just fine. But when I restarted it. The logo just appeared. It's almost a day and it's still like that please help me gosh I hoped it wasn't bricked.
Click to expand...
Click to collapse
Unless you remember all the apps you froze, which is unlikely, go into recovery mode and factory reset your device.
Sent from my GT-I8190 using Tapatalk
Carlyle_f said:
Unless you remember all the apps you froze, which is unlikely, go into recovery mode and factory reset your device.
Sent from my GT-I8190 using Tapatalk
Click to expand...
Click to collapse
Oh. Thank you. I have tried it. But I don't know.. Is it possible that I froze something that is required for the recovery?
DearestMartha said:
Oh. Thank you. I have tried it. But I don't know.. Is it possible that I froze something that is required for the recovery?
Click to expand...
Click to collapse
If you can get into recovery then no, are the any custom Roms for your device? I suggest you try flashing one. They normally have all the bloatware removed already. Either that or flash your stock ROM again using Odin. Which device do you have?
Sent from my GT-I8190 using Tapatalk
Carlyle_f said:
If you can get into recovery then no, are the any custom Roms for your device? I suggest you try flashing one. They normally have all the bloatware removed already. Either that or flash your stock ROM again using Odin. Which device do you have?
Sent from my GT-I8190 using Tapatalk
Click to expand...
Click to collapse
It's an LG L7 p705 sir. It's rooted but I haven't flashed any custom roms yet.
I really think I froze something that has to do with the recovery. I can't access it.
DearestMartha said:
It's an LG L7 p705 sir. It's rooted but I haven't flashed any custom roms yet.
Click to expand...
Click to collapse
If you prefer stock ROM then use Odin to flash a stock ROM on your device. I don't see any other way out of this
Sent from my GT-I8190 using Tapatalk
DearestMartha said:
I really think I froze something that has to do with the recovery. I can't access it.
Click to expand...
Click to collapse
Can you acces Emergency Mode my friend. Pull out battery. Insert it back then Hold Volume up + Volume down + power button tell me if you see a yellow screen.
I doubt you can use Odin as you say you have an lg device. Many lg devices have fastboot access via bootloader if yours is on then you should be fine. I doubt you froze anything that would keep you from booting to the recovery as you can't freeze your kernel so keep trying to get there. But a factory reset will doubtfully help as you probably removed some system apps that don't return when doing a factory reset, but still worth a try
If you can get into recovery and a factory reset doesn't help then wipe all and then flash a custom ROM.
If this won't work than hope you have fastboot access and or another method such as nvflash or whatever
Sent from my Nexus 4 using XDA Premium 4 mobile app
Acamew revolutions
Ok. Thank you so much for your replies I really appreciate it. I guess that recovery is my only hope.. I'll try to get to it. I was nervous that I think I froze something that have to do with the recovery. I'll try to be more careful now, I'll just post if it's working fine now.
DearestMartha said:
Ok. Thank you so much for your replies I really appreciate it. I guess that recovery is my only hope.. I'll try to get to it. I was nervous that I think I froze something that have to do with the recovery. I'll try to be more careful now, I'll just post if it's working fine now.
Click to expand...
Click to collapse
Man can you enter Emergency Mode tell me so i can give you details on how to flash Stock.
christi9503 said:
Man can you enter Emergency Mode tell me so i can give you details on how to flash Stock.
Click to expand...
Click to collapse
I've tried it again and again. Still can't access it.
DearestMartha said:
I've tried it again and again. Still can't access it.
Click to expand...
Click to collapse
Ok put battery out then try only Volume up + Power button and hold them untill you see the yellow screen.
Hello, I have an i717 and I'm having an extremely annoying issue with LiquidSmooth 3.1. So basically, after the first boot/setup, it runs perfectly fine. Beautifully. But if I turn it off, it won't load the OS when I turn it on again. It'll sit on a black screen for several hours. I've tried reinstalling this ROM about 5 times and had the same issue each time.
Anyone having the same issue, or know a fix?
MoronDroid said:
Hello, I have an i717 and I'm having an extremely annoying issue with LiquidSmooth 3.1. So basically, after the first boot/setup, it runs perfectly fine. Beautifully. But if I turn it off, it won't load the OS when I turn it on again. It'll sit on a black screen for several hours. I've tried reinstalling this ROM about 5 times and had the same issue each time.
Anyone having the same issue, or know a fix?
Click to expand...
Click to collapse
Just restarted the phone, booted after the 12th time.
LS goes through the bootanimation twice so it will look like its boot looping. Plus it does seem to take a while to boot into the os, just gotta be patient with the ROM on initial boot.
sent from my sweetened CandyKat SGH-I717
dzee206 said:
LS goes through the bootanimation twice so it will look like its boot looping. Plus it does seem to take a while to boot into the os, just gotta be patient with the ROM on initial boot.
sent from my sweetened CandyKat SGH-I717
Click to expand...
Click to collapse
This is really weird. I formatted all of the partitions, and did a fresh re-install of LiquidSmooth 3.1. It installed just fine, the Polluti0n V2 patch installed fine as well. But when I tried installing the Gapps (pa gapps stock 4.4.4 20140629), it came up with:
"file_getprop: failed to stat "/system/build.prop": No such file or directory.
E: Error in /sdcard/pa_gapps-stock-4.4.4-20140629-signed.zip
(status 7)
Installation aborted."
MoronDroid said:
This is really weird. I formatted all of the partitions, and did a fresh re-install of LiquidSmooth 3.1. It installed just fine, the Polluti0n V2 patch installed fine as well. But when I tried installing the Gapps (pa gapps stock 4.4.4 20140629), it came up with:
"file_getprop: failed to stat "/system/build.prop": No such file or directory.
E: Error in /sdcard/pa_gapps-stock-4.4.4-20140629-signed.zip
(status 7)
Installation aborted."
Click to expand...
Click to collapse
Status 7 is upgrade your recovery, but I have never seen it hit with gapps or just gapps.
Weird
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
Status 7 is upgrade your recovery, but I have never seen it hit with gapps or just gapps.
Weird
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
How do I fix this?
MoronDroid said:
How do I fix this?
Click to expand...
Click to collapse
What recovery are you running?
Have you tried a different gapps package?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
What recovery are you running?
Have you tried a different gapps package?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
I have tried 3 different Gapps packages, all had the same result. I don't know what recovery version I am using. But I'm using CWM 5.5.0.4
MoronDroid said:
I have tried 3 different Gapps packages, all had the same result. I don't know what recovery version I am using. But I'm using CWM 5.5.0.4
Click to expand...
Click to collapse
CWM is your recovery and your version#
TWRP is also a recovery used.
Let me ask you how long have you been flashing on this version of recovery and is there an updated version?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
CWM is your recovery and your version#
TWRP is also a recovery used.
Let me ask you how long have you been flashing on this version of recovery and is there an updated version?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
I purchased this phone used, and I've had it for 2.5 weeks and have been flashing every couple of days between CM10.1.3 and LS 3.1. I believe there may be an updated version, I'll look around.
MoronDroid said:
I purchased this phone used, and I've had it for 2.5 weeks and have been flashing every couple of days between CM10.1.3 and LS 3.1. I believe there may be an updated version, I'll look around.
Click to expand...
Click to collapse
Oh yeah....if you are flashing CM 10 with it wow. That is quite an older version and LS 3.1 is kit kat. CM 10 is the equivalent of JB so your bouncing back and forth and the up to date recoveries were designed to handle KK.
go to development and find the TWRP thread from "GIMMIEORILLTELL". it is TWRP version 2.8.0.1 ???
TWRP is a touch based recover which is sooooooo simple to use. No more toggle of the volume rocker.
Download and flash like you would any rom.
Once flashed, boot up whatever or pull battery and replace.
Boot back into recovery and it will be there.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
Oh yeah....if you are flashing CM 10 with it wow. That is quite an older version and LS 3.1 is kit kat. CM 10 is the equivalent of JB so your bouncing back and forth and the up to date recoveries were designed to handle KK.
go to development and find the TWRP thread from "GIMMIEORILLTELL". it is TWRP version 2.8.0.1 ???
TWRP is a touch based recover which is sooooooo simple to use. No more toggle of the volume rocker.
Download and flash like you would any rom.
Once flashed, boot up whatever or pull battery and replace.
Boot back into recovery and it will be there.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
I'll surely give it a try, but not at this ungodly hour. I'll be without a phone for the day, but oh well.
captemo said:
Oh yeah....if you are flashing CM 10 with it wow. That is quite an older version and LS 3.1 is kit kat. CM 10 is the equivalent of JB so your bouncing back and forth and the up to date recoveries were designed to handle KK.
go to development and find the TWRP thread from "GIMMIEORILLTELL". it is TWRP version 2.8.0.1 ???
TWRP is a touch based recover which is sooooooo simple to use. No more toggle of the volume rocker.
Download and flash like you would any rom.
Once flashed, boot up whatever or pull battery and replace.
Boot back into recovery and it will be there.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
Flashed... and now it continually boot loops with the Samsung logo flashing. I think it's bricked. This is fantastic...
MoronDroid said:
Flashed... and now it continually boot loops with the Samsung logo flashing. I think it's bricked. This is fantastic...
Click to expand...
Click to collapse
No no no.......deep breath. Relax.
Pull battery.
What were you doing?
And what did you do?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
No no no.......deep breath. Relax.
Pull battery.
What were you doing?
And what did you do?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
I selected the Zip using CWM, and told it to flash it. It successfully flashed, replacing the recovery.img. Then I reboot, and it bricked. Keeps flashing the samsung logo, pressing the recovery buttons (volume up+ power) does nothing. There's nothing I can do. It's dead.
MoronDroid said:
I selected the Zip using CWM, and told it to flash it. It successfully flashed, replacing the recovery.img. Then I reboot, and it bricked. Keeps flashing the samsung logo, pressing the recovery buttons (volume up+ power) does nothing. There's nothing I can do. It's dead.
Click to expand...
Click to collapse
Continually powers off and reboots. Vibrates and such.
MoronDroid said:
Continually powers off and reboots. Vibrates and such.
Click to expand...
Click to collapse
PRAISE THE ANDROID MODDING COMMUNITY
http://forum.xda-developers.com/showthread.php?t=1784857
MoronDroid said:
PRAISE THE ANDROID MODDING COMMUNITY
http://forum.xda-developers.com/showthread.php?t=1784857
Click to expand...
Click to collapse
Could be a stuck power button my friend. Flick the back of the phone behind the power button with your finger.
Dont be shy, but done break your finger either.
Very common problem.
Pull battery. Can you get download mode?
Unless you flashed files for the wrong device, I don't think you are bricked.
If you can get download mode, you are not bricked.
What file did you flash?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
Could be a stuck power button my friend. Flick the back of the phone behind the power button with your finger.
Dont be shy, but done break your finger either.
Very common problem.
Pull battery. Can you get download mode?
Unless you flashed files for the wrong device, I don't think you are bricked.
If you can get download mode, you are not bricked.
What file did you flash?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
I fixed her. All I did was install Odin, and reinstall the stock ROM (md5 file). Also just rooted it with a new verision of CWM.
I want to thank you for your patience.
MoronDroid said:
I fixed her. All I did was install Odin, and reinstall the stock ROM (md5 file). Also just rooted it with a new verision of CWM.
I want to thank you for your patience.
Click to expand...
Click to collapse
We were getting close to that option. Every once in a while, and I have had to do it recently, we have to return to stock. Basically it takes out all the garbage that has accumulated, even though our process is clean.
I couldn't get anything to flash, not even an alternate recovery. Went back to complete stock, Re root and Bob is your uncle. (that means everything as good as new).
Glad your fixed. Dont let it detour you from flashing. It's a lot of fun. Keeps me off the streets.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
LG G Watch - Return to Stock
Current Version Included : LDZ22D (5.1.1)
Prerequisites:
Unlocked Bootloader (fastboot oem unlock)
ADB Debugging Enabled (Settings > About > Tap on build number 7 times > Swipe back > Developer Options > Enable ADB Debugging)
Drivers Installed (Windows)
Donations:
If you happen to like my ROM and find yourself wishing to donate, you can do so by pressing the "Donate to Me" button below my username on the left side of the screen. I spend my free time developing my contributions to the community, and every penny is greatly appreciated!
Changelog:
Version 1.0 (7/15/2015) :
- Initial release based on LDZ22D.
Downloads:
Version 1.0 (md5: 2a0369c8b4bd5fa848a06558c40c0bc6)
Mirror 1
F.A.Q
How do i use the installer?
Extract the archive.
Enter the "Installer" folder.
Enter the folder of the platform you're using (Windows, Linux, or OSX).
Run the installer and follow the on-screen instructions.
Linux and OSX scripts may need the proper permissions in order to run.
Please note: First boot will take some time, and you'll need to re-pair your watch and phone.
Questions? Comments? Concerns?
Leave all questions, comments, and concerns below, and I'll be sure to reply as fast as possible!
Is this restore tool using a rooted system img
Sent from my Nexus 4 using XDA Premium HD app
silent_bob52637 said:
Is this restore tool using a rooted system img
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Completely stock, untouched. Pulled the system.img as soon as I got my g watch and updated it to LDZ22D.
Sent from my SM-G925P using XDA Free mobile app
Thank you just what I needed
Flashed flawlessly relocked perfectly
Sent from my Nexus 4 using XDA Premium HD app
does anyone else have problems getting into stock 3e recovery? I get the android guy on his back but no options will appear after tapping screen
kornklown69 said:
does anyone else have problems getting into stock 3e recovery? I get the android guy on his back but no options will appear after tapping screen
Click to expand...
Click to collapse
I found I have to swipe down instead of tap
Sent from my Nexus 4 using XDA Premium HD app
silent_bob52637 said:
I found I have to swipe down instead of tap
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
ya i tried everything
I am stuck here
http://postimg.org/image/iw76n9v5p/
i waited pretty long. I had to restart the watch and now it only boots into bootloader :/
Install worked, but can't update to the latest android wear as it fails on 61%
kornklown69 said:
does anyone else have problems getting into stock 3e recovery? I get the android guy on his back but no options will appear after tapping screen
Click to expand...
Click to collapse
Me too. Can't get recovery working again. Avoid this!
PainToad said:
Me too. Can't get recovery working again. Avoid this!
Click to expand...
Click to collapse
Try getting into Fastboot with the diagonal swipe or "adb reboot bootloader" and then using the arrows and circle button to go to recovery. Recovery works for me that way.
ApertureAndroid said:
Try getting into Fastboot with the diagonal swipe or "adb reboot bootloader" and then using the arrows and circle button to go to recovery. Recovery works for me that way.
Click to expand...
Click to collapse
problem is when i do that i still get the android guy on back and no recovery, i believe somehow recovery is missing and i can't figure out how to get recovery back..
kornklown69 said:
problem is when i do that i still get the android guy on back and no recovery, i believe somehow recovery is missing and i can't figure out how to get recovery back..
Click to expand...
Click to collapse
Yeah, I had that problem if I did "adb reboot recovery" or went to recovery directly. When I go through Fastboot it's fine.
Maybe the problem is different for you.
Tapping the screen does absolutely nothing?
ApertureAndroid said:
Yeah, I had that problem if I did "adb reboot recovery" or went to recovery directly. When I go through Fastboot it's fine.
Maybe the problem is different for you.
Tapping the screen does absolutely nothing?
Click to expand...
Click to collapse
yup tapping screen does nothing tapped everywhere and swipped and my watch has the update notification now when i swipe to update same thing goes to just the android on his back and doesn't update... frustrating lol maybe somehow I can rewrite recovery somehow... I'm not sure where to begin with that
kornklown69 said:
yup tapping screen does nothing tapped everywhere and swipped and my watch has the update notification now when i swipe to update same thing goes to just the android on his back and doesn't update... frustrating lol maybe somehow I can rewrite recovery somehow... I'm not sure where to begin with that
Click to expand...
Click to collapse
If all else fails I suggest following this post. Be sure to flash a custom recovery like TWRP before starting, though.
ApertureAndroid said:
If all else fails I suggest following this post. Be sure to flash a custom recovery like TWRP before starting, though.
Click to expand...
Click to collapse
I used twrp to wipe everything then used the tool to return to stock and then was able to load the ota update and bam fixed
I've been stuck on "sending userdata" for a really long time...