I tried unlocking my G Watch's boot loader and flashing a new recovery and I left out a couple of things. I downloaded the utility for it and flashed it back to stock. Soon after I got an update to kmv78y and attempted to update it. It went through and kept booting to recovery. I flashed it back to stock. I found there was an update to the utility that would flash the update. It worked and now I got the update to 4.4w1 and tried to install it. I got the status 7 error in recovery and rebooted. I tried a few things to force it to update with no success and a soft bricked watch. I flashed it back to absolute stock and I'm getting a notification to update it to kmv78y. If I try, it boots right into recovery, forcing me to flash it back to absolute stock again. Any thoughts on how to fix it?
tycemang said:
I tried unlocking my G Watch's boot loader and flashing a new recovery and I left out a couple of things. I downloaded the utility for it and flashed it back to stock. Soon after I got an update to kmv78y and attempted to update it. It went through and kept booting to recovery. I flashed it back to stock. I found there was an update to the utility that would flash the update. It worked and now I got the update to 4.4w1 and tried to install it. I got the status 7 error in recovery and rebooted. I tried a few things to force it to update with no success and a soft bricked watch. I flashed it back to absolute stock and I'm getting a notification to update it to kmv78y. If I try, it boots right into recovery, forcing me to flash it back to absolute stock again. Any thoughts on how to fix it?
Click to expand...
Click to collapse
Try flashing it back to stock with lg flash tool.
dude1981 said:
Try flashing it back to stock with lg flash tool.
Click to expand...
Click to collapse
That is what I was using. I thought I had the latest version, but I realized I didn't and got it. Now I have the update but every time an ota update has come through after using it to flash it back, it would boot right into recovery.
What build number? The new update is KGW42Q.
dude1981 said:
What build number? The new update is KGW42Q.
Click to expand...
Click to collapse
I managed to flash that will the tool kit/utility but if I would've attempted to install any of the otas (kgw42q or kmv78y) that would happen.
So you are on the latest update? You cannot take a ota with a custom recovery. This tool helps out a lot http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863. I'm running the latest Gohma ROM. You can get it here http://rootzwiki.com/topic/207402-rom-gohma-10-772014-android-wear/.:good:
dude1981 said:
So you are on the latest update? You cannot take a ota with a custom recovery. This tool helps out a lot http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863. I'm running the latest Gohma ROM. You can get it here http://rootzwiki.com/topic/207402-rom-gohma-10-772014-android-wear/.:good:
Click to expand...
Click to collapse
I got rid of the custom recovery a while ago. I have the stock recovery.
Have you been on stock with custom recovery? And before taking the ota was all stock?
dude1981 said:
Have you been on stock with custom recovery? And before taking the ota was all stock?
Click to expand...
Click to collapse
When I flashed it back yo stock, everything was stock; recovery, boot, and system.
Did you use the lg flash tool?
Related
I was attempting to go back to stock in an effort to Get the update that just dropped. I have rooted, flashed, gone back to stock, rooted and flashed again prior to this with no problems.
I have been running JoshBeach's JellyBomb with no problems.
In trying to flash the stock .tar, it failed, I cannot get it to complete a flash, and it will only boot into emergency or download mode.
Should I try running CF Auto-root again?
GAPO said:
I was attempting to go back to stock in an effort to Get the update that just dropped. I have rooted, flashed, gone back to stock, rooted and flashed again prior to this with no problems.
I have been running JoshBeach's JellyBomb with no problems.
In trying to flash the stock .tar, it failed, I cannot get it to complete a flash, and it will only boot into emergency or download mode.
Should I try running CF Auto-root again?
Click to expand...
Click to collapse
Did you put your phone into download mode when initializing cf-root?
Sprint Galaxy Note 3
Stock rooted 4.3
Mart1an said:
Did you put your phone into download mode when initializing cf-root?
Sprint Galaxy Note 3
Stock rooted 4.3
Click to expand...
Click to collapse
Well, I had thought so. But I tried it again this morning, making sure to do so, and it worked. Still couldn't seem to install stock file, but I ran CF-root again(successfully), flashed TWRP in Odin, then flashed JellyBomb Domination. So, I still don't have the update, but I am functional. Thanks, bud!
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
dar101978 said:
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
Click to expand...
Click to collapse
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
CalcProgrammer1 said:
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
Click to expand...
Click to collapse
Thanks thats what i did, I just basically had to use KIES to use the emergency recovery, then root my phone again. My question is what version of TWRP causes this? cause i used the newest version i could find off GOO. My other concerne is, will it accept or be safe to use a custom ROM? Well i gues ill find out :laugh: THANKS AGAIN!
Everyone with the sgh-i717 is having problems with the latest TWRP and the most stable version is 2.5.0.0. Go with that one or you'll be starting all over again I imagine. And don't just stop at the download link in the OP's, read the thread and find out what's going on. The problems with TWRP have been going on for a while and the development threads have a lot of comments about the latest build causing problems. Good luck! :good:
Earlier today i flashed a stock rom, locked my bootloader, and flashed the stock AT&T recovery in an attempt to recieve the 4.2.2 update. As i was checking for the update, a 13.8 mb update was downloaded, however when it tried to install, a red exclamation point came up. So i restarted and tried it again and no luck. So then i decided to run the RUU and start fresh and try again. However this time, the update is not being recieved. Any ideas or hints that you guys have?
Dash_Skeezy said:
Earlier today i flashed a stock rom, locked my bootloader, and flashed the stock AT&T recovery in an attempt to recieve the 4.2.2 update. As i was checking for the update, a 13.8 mb update was downloaded, however when it tried to install, a red exclamation point came up. So i restarted and tried it again and no luck. So then i decided to run the RUU and start fresh and try again. However this time, the update is not being recieved. Any ideas or hints that you guys have?
Click to expand...
Click to collapse
Try to uncheck the automatic time in settings and put the tine 24 hour ahead. And try to get the update. Some claim it works this way.
Sent from my HTC One X+ using Tapatalk
Same for me
Having exactly the same problem. Made an account because i could not find an answer anywhere else. Just tried the time strategy and it did not work.
I do have the downloaded update file. Is there a way to install it through ADB and pushing, as can be done with nexus devices?
Thanks
Total newbie to all this. First time I've unlocked or rooted android.
I unlocked using the Asus unlocker. Rooted with motochopper. Then I installed fastboot and nvflash and flatline. Messed up here as I was planning to install CM11 and when I tried to install the ROM it failed. Should have read the small details. Soft bricked my tf201 and could only use apx.
Used nvflash to recover to stock jb. Re-rooted and tried to install CWM. Didn't work recovery would freeze in the loading recovery image. But I could still just boot normal into my device. Tried TWRP and had the same problem.
How do I get the recovery to work. Do I need to go back to the stock image and try all over again?
I feel like a real idiot. I was trying to install the oldest version of twrp not the newest. It's amazing what a little sleep does to figure things out. Now onto installing CM11,
JoanneDisFan said:
I feel like a real idiot. I was trying to install the oldest version of twrp not the newest. It's amazing what a little sleep does to figure things out. Now onto installing CM11,
Click to expand...
Click to collapse
Can you put SOLVED in the title of the thread..
Thx Josh
I have the 6833, and I have been rooting by downgrading to .532, rooting, installing recovery, and then flashing which ever ROM I choose. The problem is that if I try to flash anything else after that, the phone no longer boots. I can't even get the SONY screen to come on, nor can I get back into recovery. So when ever I want to try a new ROM, I have to go back to .532, root, and then install the new ROM I want to try.
Surely I am doing something terribly wrong, but I can't figure it out. I'm trying now to install Carbon KK (coming from stock rooted .757) and I once again have a soft brick. Any suggestions would be appreciated. Oh yeah, my bootloader is unlocked.
jfsat said:
I have the 6833, and I have been rooting by downgrading to .532, rooting, installing recovery, and then flashing which ever ROM I choose. The problem is that if I try to flash anything else after that, the phone no longer boots. I can't even get the SONY screen to come on, nor can I get back into recovery. So when ever I want to try a new ROM, I have to go back to .532, root, and then install the new ROM I want to try.
Surely I am doing something terribly wrong, but I can't figure it out. I'm trying now to install Carbon KK (coming from stock rooted .757) and I once again have a soft brick. Any suggestions would be appreciated. Oh yeah, my bootloader is unlocked.
Click to expand...
Click to collapse
First off once you have unlocked the boot loader you nolonger have to do the downgrade/root/recovery dance if you get stuck. Just flasf the latest FTF then a rootable kernel (jackie099 normally has one out in a day or two of an updated firmware) then you can just flash recoveries/supersu/etc as needed.
Not sure why the installs are failing. If you have flashed a custom ROM (carbon/PAC/CM/...) and it doesn't boot at any point the first step is to flash the boot.img file that is inside the zip of the ROM. Do this in flashtool and put the phone into fastboot mode (vol. up when connecting to the PC).