Related
My Vibrant is telling me that T-Mobile has kindly sent me an update. I think it must be the GPS fix. It is rather persistent in that it won't let me choose when to install it. It will only allow me to delay for at most a day. This is quite annoying as I am preparing for a trip and really don't want to mess around with my phone right now.
I am running Vibrant9. Do I want to install this update? Is it gonna break anything? Thanks!
JJMT said:
My Vibrant is telling me that T-Mobile has kindly sent me an update. I think it must be the GPS fix. It is rather persistent in that it won't let me choose when to install it. It will only allow me to delay for at most a day. This is quite annoying as I am preparing for a trip and really don't want to mess around with my phone right now.
I am running Vibrant9. Do I want to install this update? Is it gonna break anything? Thanks!
Click to expand...
Click to collapse
Shouldn't break anything. Most are still waiting for the update. Personally I was impatient and flashed it through ODIN last night.
OK. I accepted the update. Phone is now stuck on "Vibrant" at reboot. Sigh. Proceeding to trying to restore ROM.
JJMT said:
OK. I accepted the update. Phone is now stuck on "Vibrant" at reboot. Sigh. Proceeding to trying to restore ROM.
Click to expand...
Click to collapse
Go to the Development section that are a few threads about this. I looks like anyone with a lag fix, or GPS fix (from JI2) where having this issue, plus I have seen stock people having it too.
Or you can go read my blog post here. the post tells the steps I took to get back the JFD, but you could flash JI6 instead.
you will need to flash JI6 with ODIN to restore, you can not just do a nandroid restore, it is an issue with the kernel and nandroid does not restore/backup the kernel.
*facepalm*@Samsung
http://forum.xda-developers.com/showthread.php?t=803492
Anderdroid said:
*facepalm*@Samsung
Click to expand...
Click to collapse
It's not Samsung or T-Mobile.. its that the OP performed tweaks so the ROM wasn't a 100.00% version of Stock. Tweaks including lag fixes, GPS fix, etc can cause this.
Personally, I don't know why if you're performing tweaks on your phone and are on a stock ROM. If you're going to tweak your phone, go the full way and tweak everything.
This is why t-mobile had the G2 nand locked..... so this type of user error won't cost them millions, replacing phones that the user messed up with blind stupidity.... that's only for the ones under warranty, you can still call in a lost phone and get replacements..
dan0zone said:
This is why t-mobile had the G2 nand locked..... so this type of user error won't cost them millions, replacing phones that the user messed up with blind stupidity.... that's only for the ones under warranty, you can still call in a lost phone and get replacements..
Click to expand...
Click to collapse
So now instead, they get flooded with returns because the phone isn't what people expected.
zephiK said:
It's not Samsung or T-Mobile.. its that the OP performed tweaks so the ROM wasn't a 100.00% version of Stock. Tweaks including lag fixes, GPS fix, etc can cause this.
Personally, I don't know why if you're performing tweaks on your phone and are on a stock ROM. If you're going to tweak your phone, go the full way and tweak everything.
Click to expand...
Click to collapse
That's not true, it is Samsung/T-Mobile fault. I know 3 people with 100% stock, unrooted, vibrants, 2 of them got stuck when they updated. the t-mobile forums filled with stock users with their phone stuck at the vibrant screen as well.
camalot said:
That's not true, it is Samsung/T-Mobile fault. I know 3 people with 100% stock, unrooted, vibrants, 2 of them got stuck when they updated. the t-mobile forums filled with stock users with their phone stuck at the vibrant screen as well.
Click to expand...
Click to collapse
And what are the chances of this?
Everybody lies.. especially when they're desperate and unwilling to accept the fact that they modified their phone. I don't see any reason why they wouldn't lie to T-Mobile and say that they didn't modify their phones if its "bricked." Because it is not bricked, all it takes is download mode and Odin. There are threads out there that break down on how to use Odin, it's not that difficult to do.
This is why I don't endorse "One Click" anything unless it is a long process. Sure, it makes everything easier but it makes people not think about what they're doing before they do it. Before one clicking, rooting was so simple, put something on your internal sd and boot into recovery and hit reinstall packages. If something like that is too difficult then they shouldn't be doing any modifications in the first place unless they understanding what they're doing.
The T-Mobile forum is not a valid source because there is no concrete proof that they didn't root their phone and modified something. Even rooting and removing bloatware then removing access to root would cause this.
Edit: Looking at the OP's recent posts.. he did indeed run a custom ROM but has possibly did some tweaking after reverting back to stock?
zephiK said:
And what are the chances of this?
Everybody lies.. especially when they're desperate and unwilling to accept the fact that they modified their phone. I don't see any reason why they wouldn't lie to T-Mobile and say that they didn't modify their phones if its "bricked." Because it is not bricked, all it takes is download mode and Odin. There are threads out there that break down on how to use Odin, it's not that difficult to do.
This is why I don't endorse "One Click" anything unless it is a long process. Sure, it makes everything easier but it makes people not think about what they're doing before they do it. Before one clicking, rooting was so simple, put something on your internal sd and boot into recovery and hit reinstall packages. If something like that is too difficult then they shouldn't be doing any modifications in the first place unless they understanding what they're doing.
The T-Mobile forum is not a valid source because there is no concrete proof that they didn't root their phone and modified something. Even rooting and removing bloatware then removing access to root would cause this.
Edit: Looking at the OP's recent posts.. he did indeed run a custom ROM but has possibly did some tweaking after reverting back to stock?
Click to expand...
Click to collapse
Well, I know the 2 people that updated stock and got stuck at the vibrant screen were 100% stock because they both called me on what they need to do. one came over and I fixed it with ODIN back to stock (JI6) and the other just said he'd call TMO and get a replacement. they dont even know what rooting is, or that there is a site like that that they can get files to do "one click root"
OK. I'm the OP and I'm back. I was traveling today (with a phone flashed back to stock - that's as far as I got before getting kicked out of the hotel). I've now got the ROM restored and I'm where I was before trying to install the update.
My question is this (probably simple): my phone still wants to do the update. How do I make it go away? I can't install it, and I don't want to have to postpone it every day. Is there a cache I can clear or something?
You could just update it through Odin. I'm on stock with root and JAC's oc/uv kernel and the OTA failed but Odin worked perfectly.
Yes, I will try to flash it with odin when I have the time and interest, but for now I have neither, and I just want the phone to stop bugging me. Ideas?
JJMT said:
Yes, I will try to flash it with odin when I have the time and interest, but for now I have neither, and I just want the phone to stop bugging me. Ideas?
Click to expand...
Click to collapse
It will only stop once you are on JI6
camalot said:
It will only stop once you are on JI6
Click to expand...
Click to collapse
OK. I guess I will have to try to push the update through odin. Can someone point me to a link to the files?
I'm kind of irritated by this whole thing. I'm pleased with tmo for pushing the update out, but I mean, really, even Windows allows you to decline to install an update.
http://forum.xda-developers.com/showthread.php?t=798125
chad658eku said:
http://forum.xda-developers.com/showthread.php?t=798125
Click to expand...
Click to collapse
Thanks for the link. It really looks to me that I'm going to need to flash to a stock ROM before flashing JI6. That, as they say, is a bummer.
As I am actually quite content at the moment with Vibrant9, it really seems to me that it would be easier to somehow remove whatever it is on my phone that is requesting that I update. Presumably there is an update.zip file sitting somewhere, that will be copied into sdcard before the updater involves reboot recovery. Any ideas where to look?
I would really rather not do any further flashing until is an official Froyo to flash to.
JWhipple said:
So now instead, they get flooded with returns because the phone isn't what people expected.
Click to expand...
Click to collapse
Flooded with returns by morons who think they are smart.
hi i just got an atrix, switched over from jailbroken iphone.
I went through rooting it and installed rom manager but when i try to reset permissions i get an error and when i try to reboot into recovery it says "failed to boot 2 starting rsd" and hangs.
I just want to reset the phone to stock and start the process over, can someone give me some help on this....
Id like to install the ninja rom. but im lost about what order to do things, root, backup/nandroid, and install new rom etc.
thanks
First, it would be nice to know what was on the phone when you started? 1.8.3, 1.2.6 or 4.9.1?
Next, where are you trying to go? You installed the ROM Manager, does that mean you were going to try to use a particular ROM?
Probably more important, the ROM Manager is not fully compatible with the Atrix (see thread).
Before going forward, I would suggest reading (and re-reading) this thread about the bricking potential. Don't get me wrong, it is possible to add custom ROMs to your Atrix, you just need to be cautious.
At this point, it doesn't sound like your Atrix is hard bricked. However, to help out, we need a little more information.
kwick60073 said:
First, it would be nice to know what was on the phone when you started? 1.8.3, 1.2.6 or 4.9.1?
Next, where are you trying to go? You installed the ROM Manager, does that mean you were going to try to use a particular ROM?
Probably more important, the ROM Manager is not fully compatible with the Atrix (see thread).
Before going forward, I would suggest reading (and re-reading) this thread about the bricking potential. Don't get me wrong, it is possible to add custom ROMs to your Atrix, you just need to be cautious.
At this point, it doesn't sound like your Atrix is hard bricked. However, to help out, we need a little more information.
Click to expand...
Click to collapse
ya its not hard bricked, i pulled out the battery and it starts and runs normal. it says its android ver. 2.3.4 and baseband 1.77.30p build number 4.5.91
you know to be honest im pretty happy with it out of the box... adding non-market apps would be nice and id like to be able to make full backups to boot from if i need to. id like to delete some apps i dont need.
it seemed like there was a problem with the rooting i did cause some stuff wasnt working like 'shootme' screengrab app and the permissions fixing wasnt working.
thanks for your help i really appreciate it!
You can try this to root:
http://forum.xda-developers.com/showthread.php?t=1182871
I don't know if that allows for enabling side-loading or not.
cmontboober said:
ya its not hard bricked, i pulled out the battery and it starts and runs normal. it says its android ver. 2.3.4 and baseband 1.77.30p build number 4.5.91
you know to be honest im pretty happy with it out of the box... adding non-market apps would be nice and id like to be able to make full backups to boot from if i need to. id like to delete some apps i dont need.
it seemed like there was a problem with the rooting i did cause some stuff wasnt working like 'shootme' screengrab app and the permissions fixing wasnt working.
thanks for your help i really appreciate it!
Click to expand...
Click to collapse
Enabling non-market apps is a built in feature for 2.3.4, go to Settings -> Applications, and put a check mark next to "Unknown Sources".
For rooting, try Gingerbreak.
For backing up, there's a CWM version that doesn't need an unlocked bootloader, but I am unlocked so I don't have experience installing it / using it.
Since most people are unlocked, I am not sure if the non-unlocked version of CWM was kept up to date, it might be obsolete / non functional by now.
xploited said:
Enabling non-market apps is a built in feature for 2.3.4, go to Settings -> Applications, and put a check mark next to "Unknown Sources".
For rooting, try Gingerbreak.
For backing up, there's a CWM version that doesn't need an unlocked bootloader, but I am unlocked so I don't have experience installing it / using it.
Since most people are unlocked, I am not sure if the non-unlocked version of CWM was kept up to date, it might be obsolete / non functional by now.
Click to expand...
Click to collapse
for rooting it again do i need to get it back to completely stock or just use gingerbreak on it as it is now?
thanks for all the help everyone.
cmontboober said:
for rooting it again do i need to get it back to completely stock or just use gingerbreak on it as it is now?
thanks for all the help everyone.
Click to expand...
Click to collapse
You can root at any point. Gingerbreak should work fine if you have usb debugging enabled.
how can i do a factory restore, setting it back to how it came out of the box? also, any tips on maintenance to keep it running fast?
thanks again for all the help
cmontboober said:
how can i do a factory restore, setting it back to how it came out of the box? also, any tips on maintenance to keep it running fast?
thanks again for all the help
Click to expand...
Click to collapse
That largely depends on your setup BL / CWM ,etc...
You might wanna read this guide to clear up many things:
http://forum.xda-developers.com/showthread.php?t=1154600
Hi,
I need help guys.
I have S4 and I was trying to mess with it and now I don't have it at all. (pic 1)
the Samsung logo and unlock lock icon are as far as my phone goes now, and after that u cant even power it off u have get battery out. (pic 2)
I am able to go to download mode (pic 3)
and I was able to get to there (up+menu+power key), but now I cant even go there. I get black screen when I am trying to do it. (pic 4)
Thanks for your time,
Ps. Help me
Did you flash a ROM? In you pictures it appears that you can still get to recovery, is that true? What steps did you take for root? We need more information.
answer
Eeiden said:
Did you flash a ROM? In you pictures it appears that you can still get to recovery, is that true? What steps did you take for root? We need more information.
Click to expand...
Click to collapse
I was trying to flash rom, I was trying to make in international phone so it could work in Europe with out any Verizon build in stuff, just pure Samsung.
I can go do download mode, I was able to go for recovery before. That why there is the 4th picture, in stead of regular recovery a had that "teamwin" screen. Now when I press up menu and power is saying its going to recovery boot but then it resets it self and going back to Samsung unlock icon screen and just stays there...
You hold volume down + power to get to download mode. Then connect to a pc and download the all in one tool found in the development thread. Ignore the messages about having your phone in USB debugging and tell it to flash twrp 2.6.0.0. If it doesn't take In download mode, try rebooting your phone while it tries to flash twrp.
If that doesn't work flash stock with Odin and re-root and unlock the phone.
Sent from my SCH-I545 using xda app-developers app
I'm having the exact same problems right now. I tried flashing a 4.3 i9505 rom and now I can't get back into recovery and I can't boot into the OS. I can get into download mode and use ODIN, but I don't know what to do from there. I tried using the All-In-One tool to install TWRP, but it just says Device Not Found. I also tried flashing the stock sch-i545 kernel in ODIN, and it completed successfully, rebooted, and its still doing the same thing. Is there some other way that I've missed to return to stock? I'm kinda bummin here.. but thats what comes with the territory I suppose. Any help you can offer would be greatly appreciated. Thanks.
Found the factory image thread. Going to follow instructions. Will report back.
it works but not completly
So guys going back to my problem I was trying to do everything like lahma69 was trying too...
in odin was error that device not found, all off that...
but what I did, I look more online and I found this one guy...
and what I did in download mode I use odin, and in PDA selection I use this file stockroms(dot)net/file/GalaxyS4/SCH-i545/VRUAMDK_NoWipe.tar.zip
now boom... its kinda works... I am back with my os, I got the android root.
but some things are not right... my phone is very hot, maybe because its charging its self for the first time in weeks.
more important is Whats is happening right now, in boot menu I get errors, no commands, it was not able to do factory reset until I went into os and did it over there... and I cant do software update from Verizon... it goes to root and its trying but then gets error and going back to os...
and I am worry about that file that I download...
so we got little progress and lahma69 I can at least operate os and I have back stock root...
but until we will not going to make it 100% hold on with what I did...
U cant flash a rom thats not made specifically for the verizon variant (i545). The i9505 is the international version of the phone. Hence your phone not booting. Youre going to have to flash the stock mdk firmware through odin and start over (reroot, etc).
SCH-I545 using Tapatalk 2
sannek, I actually got it back up and running doing the same thing you did. I flashed the factory image in this thread: http://forum.xda-developers.com/showthread.php?t=2301259
I haven't noticed any problems yet. I'm fixing to reroot and flash my nandroid. I will let you know if I run into any problems.
I know you can't typically flash a i9505 rom on a verizon gs4, but the author of a i9505 4.3 rom gave me some instructions to try in order to get it working. I'm inserting a 4.3 ramdisk into a 4.2 AOSP ktoonsez verizon gs4 kernel, and replacing the boot.img in the 4.3 i9505 rom. I now know that I had accidentally inserted the wrong version kernel, and thats what caused my problems.
lahma69 said:
sannek, I actually got it back up and running doing the same thing you did. I flashed the factory image in this thread: http://forum.xda-developers.com/showthread.php?t=2301259
I haven't noticed any problems yet. I'm fixing to reroot and flash my nandroid. I will let you know if I run into any problems.
I know you can't typically flash a i9505 rom on a verizon gs4, but the author of a i9505 4.3 rom gave me some instructions to try in order to get it working. I'm inserting a 4.3 ramdisk into a 4.2 AOSP ktoonsez verizon gs4 kernel, and replacing the boot.img in the 4.3 i9505 rom. I now know that I had accidentally inserted the wrong version kernel, and thats what caused my problems.
Click to expand...
Click to collapse
lahma69 were u able to do software upgrade on your phone?
and I am happy for you, mine still have same problems like I mentions up there, I still get error and no command in root and I cant get software update... as soon I will be able to figure this out that will mean that my phone is 100% able to go back to Verizon that's one thing but then I will now for future because really want to make this phone a Europe compatible phone...
SaNNeK said:
lahma69 were u able to do software upgrade on your phone?
and I am happy for you, mine still have same problems like I mentions up there, I still get error and no command in root and I cant get software update... as soon I will be able to figure this out that will mean that my phone is 100% able to go back to Verizon that's one thing but then I will now for future because really want to make this phone a Europe compatible phone...
Click to expand...
Click to collapse
My phone seems to be at 100%. I never do software updates through Verizon so I would not know if thats working or not. After I flashed the stock image in ODIN and rerooted my device, I immediately flashed TWRP through Goomanager and reflashed my nandroid (Eclipse TW rom.) Everything is running well and my phone isn't warm. Why are you trying to do a software update? I think there is an update now that can't be rooted, so you definitely don't want to do that...
I tried several things to get the i9505 4.3 rom running on my device. You can get an idea of what I did by reading this thread: http://forum.xda-developers.com/showthread.php?t=2253528&page=779 Scroll down to post #7785 and that is mine. I never did get it to boot... Let me know if you need anything else.
root problem and upgrate
So I did exactly how xda web site was saying about going back to stock and all of that.
It worked, I can run to os and I have original root.
Still have couple of problems,
1.when u in recovery I see error and no command right below android guy. also I see new info in yellow color, below regular blue recovery screen option. (pic1)
2. information in yellow color is follow: (pic 2)
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the csc-code:VZN
successfully applied multi-CSC.
never see in before, don't know what to do..
3. I cant do regular Verizon software update. S4 resets it self and goes to recovery where is trying to do update but ends um saying error and then is going back to os and its saying that update was not that and that there were no changes applied...(pic 3)
I still need your help guys...
SaNNeK said:
So I did exactly how xda web site was saying about going back to stock and all of that.
It worked, I can run to os and I have original root.
Still have couple of problems,
1.when u in recovery I see error and no command right below android guy. also I see new info in yellow color, below regular blue recovery screen option. (pic1)
2. information in yellow color is follow: (pic 2)
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the csc-code:VZN
successfully applied multi-CSC.
never see in before, don't know what to do..
3. I cant do regular Verizon software update. S4 resets it self and goes to recovery where is trying to do update but ends um saying error and then is going back to os and its saying that update was not that and that there were no changes applied...(pic 3)
I still need your help guys...
Click to expand...
Click to collapse
Did you see what I said about doing Samsung software updates? The rooting threads for the Verizon GS4 say that the new VRUAME7 OTA update can't be rooted. After flashing the stock image from oden, why don't you reroot your device according to http://forum.xda-developers.com/showthread.php?t=2290798 and then install Goomanager, click the menu key, click "Install open recovery script" and that will install TWRP recovery. From there, flash a verizon rom of your choice and all should be well, no? I only use TWRP so I can't give you any input on other recoveries. Make sure you didn't somehow get updated to VRUAME7.
township japinove
lahma69 said:
My phone seems to be at 100%. I never do software updates through Verizon so I would not know if thats working or not. After I flashed the stock image in ODIN and rerooted my device, I immediately flashed TWRP through Goomanager and reflashed my nandroid (Eclipse TW rom.) Everything is running well and my phone isn't warm. Why are you trying to do a software update? I think there is an update now that can't be rooted, so you definitely don't want to do that...
I tried several things to get the i9505 4.3 rom running on my device. You can get an idea of what I did by reading this thread: http://forum.xda-developers.com/showthread.php?t=2253528&page=779 Scroll down to post #7785 and that is mine. I never did get it to boot... Let me know if you need anything else.
Click to expand...
Click to collapse
Well I am not that good with all of it... I don't know a lot of meanings of all this like TWRP, Eclipse TW rom, or what you said u did on post #7785
so I am just trying to be able to make it run like new, and then if I do that I will try to work on my s3 and practice on that...
I am beginner in it... plus my English abilities are not that great, so I really don't know which root is the best or how to do it with out messing up entire phone. I love to dig into it, and my s4 was just laying broken for past month and I worked on in today with you guys and its almost working... I almost made claim from insurance for new phone but this one starts working today..
and looks like everything is fine with it
except root errors and no commands ,I cant wipe cash because its crashing and restarting and I cant do that software update, and I have that manual multi csc note in recovery system like I mention just on top with pictures...
SaNNeK said:
Well I am not that good with all of it... I don't know a lot of meanings of all this like TWRP, Eclipse TW rom, or what you said u did on post #7785
so I am just trying to be able to make it run like new, and then if I do that I will try to work on my s3 and practice on that...
I am beginner in it... plus my English abilities are not that great, so I really don't know which root is the best or how to do it with out messing up entire phone. I love to dig into it, and my s4 was just laying broken for past month and I worked on in today with you guys and its almost working... I almost made claim from insurance for new phone but this one starts working today..
and looks like everything is fine with it
except root errors and no commands ,I cant wipe cash because its crashing and restarting and I cant do that software update, and I have that manual multi csc note in recovery system like I mention just on top with pictures...
Click to expand...
Click to collapse
Whats your build number in Settings -> About Phone ?
lahma69 said:
whats your build number in settings -> about phone ?
Click to expand...
Click to collapse
jdq39.i545vruamdk
Working progress
SaNNeK said:
jdq39.i545vruamdk
Click to expand...
Click to collapse
so when I will learn how to fix my phone to 100%.
Then I will experiment with it and try to learn and install more roots if I will learn how to fix first... so I will not panic like I did this time... I was just completely lost, and I need to take is step by step... don't get me wrong... I love doing that kinda stuff I build my first pc when I was 10 years old... back on old good windows 95
SaNNeK said:
so when I will learn how to fix my phone to 100%.
Then I will experiment with it and try to learn and install more roots if I will learn how to fix first... so I will not panic like I did this time... I was just completely lost, and I need to take is step by step... don't get me wrong... I love doing that kinda stuff I build my first pc when I was 10 years old... back on old good windows 95
Click to expand...
Click to collapse
Do you currently have root? To check, you can run the "SuperUser" app. If you don't have it, download it from the Play store. After installing it, run it, and a box should pop up asking you for superuser permissions. Click "Grant." If a message pops up that says something like "Superuser has been granted superuser permissions," then you have root. If you don't have root, you need to get it. Follow the instructions at http://forum.xda-developers.com/showthread.php?t=2290798 . After performing those instructions, and verifying you have root, you need to download an application called "Goomanager" from the play store. After installing and opening it, click your "Menu" key (bottom left hand corner of your phone.) A menu will pop up. Click "Install open recovery script." Click Yes or Ok to all the pop up messages. After that completes, you will have TWRP recovery installed. Your recovery is what you boot your phone to in order to flash new roms, kernels, etc. In order to boot into recovery, turn off your phone completely, click and hold your volume up button, and power on your phone (while still holding volume up.) You should see some tiny blue text pop up in the top left hand corner of your screen that saying "Opening recovery" (or something to that effect.) Once you see that text, you can let go of volume up, and you will boot into TWRP. Let me know if you get this far...
And by the way, for the love of God, do not do any Samsung system updates.
lahma69 said:
And by the way,for the love of God, do not do any Samsung system updates.
Click to expand...
Click to collapse
And thats the most important part, because if you do you will lose root and your ability to customize your phone. In layman's terms? You will be re-VZ-navigated.
I am having a similar issue. Got the "Samsung Custom" boot screen with no boot to the OS after clean wipe and install of Hyperdrive 7. Since then I have been troubleshooting the issue and have tried many things including the "No-Wipe Factory Image". Once complete I am still getting the Samsung Custom boot screen and no loading of the OS.
Any ideas as to what I can try.
Thanks in advance,
Tony
lahma69 said:
Do you currently have root? To check, you can run the "SuperUser" app. If you don't have it, download it from the Play store. After installing it, run it, and a box should pop up asking you for superuser permissions. Click "Grant." If a message pops up that says something like "Superuser has been granted superuser permissions," then you have root. If you don't have root, you need to get it. Follow the instructions at http://forum.xda-developers.com/showthread.php?t=2290798 . After performing those instructions, and verifying you have root, you need to download an application called "Goomanager" from the play store. After installing and opening it, click your "Menu" key (bottom left hand corner of your phone.) A menu will pop up. Click "Install open recovery script." Click Yes or Ok to all the pop up messages. After that completes, you will have TWRP recovery installed. Your recovery is what you boot your phone to in order to flash new roms, kernels, etc. In order to boot into recovery, turn off your phone completely, click and hold your volume up button, and power on your phone (while still holding volume up.) You should see some tiny blue text pop up in the top left hand corner of your screen that saying "Opening recovery" (or something to that effect.) Once you see that text, you can let go of volume up, and you will boot into TWRP. Let me know if you get this far...
And by the way, for the love of God, do not do any Samsung system updates.
Click to expand...
Click to collapse
as my understanding its not.. I just did that no wipe recovery...
sorry I was out of town today... so I assume I will have to do root but which one is the best? there is so many different ones...
Apparently there is a new update out there.
http://www.androidpolice.com/2015/0...2-update-starts-rolling-google-fit-fixes-tow/
Apoplectic1 said:
Apparently there is a new update out there.
http://www.androidpolice.com/2015/0...2-update-starts-rolling-google-fit-fixes-tow/
Click to expand...
Click to collapse
Yeah I don't want to update. I wish there was a way on Gomer 2.3 I could dismiss it permanently.
alansupra94 said:
Yeah I don't want to update. I wish there was a way on Gomer 2.3 I could dismiss it permanently.
Click to expand...
Click to collapse
I do, but that's because I've been having a lot of bugs lately, from apps force closing upon opening to the watch just plain not wanting to show any notifications.
Unfortunately, since I'm rooted any attempt at updating will abort.
Oh I mean I have the update downloaded and it keeps saying "system update" and I just want it to go away but I don't see a way to remove it.
alansupra94 said:
Oh I mean I have the update downloaded and it keeps saying "system update" and I just want it to go away but I don't see a way to remove it.
Click to expand...
Click to collapse
If you know the path to the OTA file you could delete it from your system through adb and the notification should go away.
I have no idea what that path is though. I've got a post on Q&A asking for where it might be, I'll let you know when I find out.
Apoplectic1 said:
If you know the path to the OTA file you could delete it from your system through adb and the notification should go away.
I have no idea what that path is though. I've got a post on Q&A asking for where it might be, I'll let you know when I find out.
Click to expand...
Click to collapse
Once the OTA is downloaded and Android prompts to install it should be stored in '/cache'.
Actually i tried installing even though im rooted and my installation was aborted. How can i make it appear again? (I will try go back to stock for a moment from Gohma and after update, flash Gohma again). In "system updates" it's now showing "up to date" but of course it wasnt updated
Lasiu said:
Actually i tried installing even though im rooted and my installation was aborted. How can i make it appear again? (I will try go back to stock for a moment from Gohma and after update, flash Gohma again). In "system updates" it's now showing "up to date" but of course it wasnt updated
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=58963155&postcount=175
You can adb push it to /cache/, but it will only fail again if you have rooted it.
There are a few guys playing around with the update to see if they can get it to flash, and some trying to see if they can make a bash file to take your watch back to stock in order to take the OTA.
Lasiu said:
Actually i tried installing even though im rooted and my installation was aborted. How can i make it appear again? (I will try go back to stock for a moment from Gohma and after update, flash Gohma again). In "system updates" it's now showing "up to date" but of course it wasnt updated
Click to expand...
Click to collapse
At this point even going back to "stock" will NOT work as the "stock" image has been pre-rooted which breaks the OTA update files. We are all currently waiting for the amazing XDA developers for updated roms / OTA fix capabilities. Until released, even if you have reverted back to "stock" and locked the bootloader etc. if you get the notification it will FAIL to install.
Moguledyouth said:
At this point even going back to "stock" will NOT work as the "stock" image has been pre-rooted which breaks the OTA update files. We are all currently waiting for the amazing XDA developers for updated roms / OTA fix capabilities. Until released, even if you have reverted back to "stock" and locked the bootloader etc. if you get the notification it will FAIL to install.
Click to expand...
Click to collapse
What I meant by going back to stock was by flashing a completely stock image to the watch, not the return to stock option in the LG G Watch Toolkit.
I think I read that Tomsgt is working on a tool that will completely reimage the watch in order to take the OTA.
Here it is: http://forum.xda-developers.com/showpost.php?p=58967268&postcount=257
Apoplectic1 said:
http://forum.xda-developers.com/showpost.php?p=58963155&postcount=175
You can adb push it to /cache/, but it will only fail again if you have rooted it.
There are a few guys playing around with the update to see if they can get it to flash, and some trying to see if they can make a bash file to take your watch back to stock in order to take the OTA.
Click to expand...
Click to collapse
I wanted to go back to stock and install it and then flash Gohma again but i see, that its pointless I have to wait... Actually im REALLY hyped for these improvements. The only thing i hated about 5.0 release were crashes and bugs
Lasiu said:
I wanted to go back to stock and install it and then flash Gohma again but i see, that its pointless I have to wait... Actually im REALLY hyped for these improvements. The only thing i hated about 5.0 release were crashes and bugs
Click to expand...
Click to collapse
You and me both brother.
Apoplectic1 said:
You and me both brother.
Click to expand...
Click to collapse
It seems i wasnt alone with that Most annoying thing was "android wear is not responding. Do you want to close it?" Hell yeah i want to close system, maybe even delete it, huh google? xD
Lasiu said:
It seems i wasnt alone with that Most annoying thing was "android wear is not responding. Do you want to close it?" Hell yeah i want to close system, maybe even delete it, huh google? xD
Click to expand...
Click to collapse
I never had that, mainly just having to try two or three times to open settings because it would always force close a split second after opening, every now and then it's go full retard and tell me that I had to open the Maps app on my phone to use Navigation (REALLY annoying if you're driving), and it would randomly stop getting notifications for no reason until I rebooted it.
Apoplectic1 said:
I never had that, mainly just having to try two or three times to open settings because it would always force close a split second after opening, every now and then it's go full retard and tell me that I had to open the Maps app on my phone to use Navigation (REALLY annoying if you're driving), and it would randomly stop getting notifications for no reason until I rebooted it.
Click to expand...
Click to collapse
It seems that you even experienced worse bugs than I did I hope that this update will fix everything!
Wife's moto 360 updated yesterday but my LG still no update
Got the update but not sure if I want to revert to stock to install it. Anyone varify what it fixes?
Just by the way, considerating that i have no problem with reseting my watch data. What should i do to take this update? Go back to stock? Relock bootloader? Then take ota, and then unlock bootloader and flash gohma again? Or there is no point in this cuz gohma is not 5.0.2 compatible? (though somewhere on rootwiki dev stated that it should work anyway, but also there was statement that ota shouldnt fail, so now im not sure if i can believe in this part xd)
---------- Post added at 12:40 PM ---------- Previous post was at 11:51 AM ----------
Is it possible to flash this ota through TWRP?
Lasiu said:
Just by the way, considerating that i have no problem with reseting my watch data. What should i do to take this update? Go back to stock? Relock bootloader? Then take ota, and then unlock bootloader and flash gohma again? Or there is no point in this cuz gohma is not 5.0.2 compatible? (though somewhere on rootwiki dev stated that it should work anyway, but also there was statement that ota shouldnt fail, so now im not sure if i can believe in this part xd)
---------- Post added at 12:40 PM ---------- Previous post was at 11:51 AM ----------
Is it possible to flash this ota through TWRP?
Click to expand...
Click to collapse
I was trying to figure this out as well. I'd even be OK if I could disable the notification for the update. I'm on an unlocked bootloader and Arter97's kernel, no custom ROM. Seems as though this device is suffering from a lack of devs or or a lack or interest or probably both.
altivoid said:
I was trying to figure this out as well. I'd even be OK if I could disable the notification for the update. I'm on an unlocked bootloader and Arter97's kernel, no custom ROM. Seems as though this device is suffering from a lack of devs or or a lack or interest or probably both.
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/moto-360/development/rom-gohma-2-3-1-11-2015-t2999582/page15
Or this:
"It took me a while to figure out how to edit build.prop to stop the OTA notifications, so I thought I would tell you what worked for me.
adb kill-server
adb start-server
adb pull /system/build.prop build.prop
I then edited the build.prop file and did 2 global replacements:
5.0.1 --> 5.0.2
LWX48P --> LWX49L
a diff between the old a new version gave:
# diff build.prop build.prop.ORG
4c4
< ro.build.id=LWX49L
---
> ro.build.id=LWX48P
10c10
< ro.build.version.release=5.0.2
---
> ro.build.version.release=5.0.1
35,36c35,36
< ro.build.description=platina-user 5.0.2 LWX49L 1627902 release-keys
< ro.build.fingerprint=lge/platina/dory:5.0.2/LWX49L/1627902:user/release-keys
---
> ro.build.description=platina-user 5.0.1 LWX48P 1627902 release-keys
> ro.build.fingerprint=lge/platina/dory:5.0.1/LWX48P/1627902:user/release-keys
Finally, I moved the new files to the watch:
adb push build.prop /sdcard/build.prop
adb push build.prop.ORG /sdcard/build.prop.ORG
adb shell
su
mount -o rw,remount /system
cp /sdcard/build.prop* /system/
exit
exit
adb reboot
This seems to be working for me."
Second one is by haltriumph from rootzwiki (Y) Didnt try them. Decided to go to 5.0.2 and just run script for longer vibrations But it might help you.
Hello guys, a few days ago, I rooted my lg magna H500f, but now LG is starting releasing Marshmallow update. Now... I rooted it by King Root, I unlocked the bootloader and installed TWRP v2.7 (Or something like this... I'm just sure of 2.x), then I installed xposed obviously flashing it, having android 5.0.1... I haven't touched the Stock android ROM, will I receive OTA updates? And what if I uninstall the framework, and uninstall king root/unroot my phone? If there's no way to update it, can someone try to find the file to flash as an update? I tried with no succes. A last question... Is the ROM "Modified" since I flashed the xposed framework? I mean... I red that if you haven't installed a custom ROM, you might receive OTA updates... but I also red that from lollipop, google disabled OTA updates with ANY customziation, even root... Wich one is true? If it's the first, did having installed the framework modified the rom such as a "Custom Rom"?
You can't have made any changes to the system partition, which both root and xposed do. So you will have to either go through and remove every system change they made or flash a stock rom for the device. Sometimes they are not released by the oem.
zelendel said:
You can't have made any changes to the system partition, which both root and xposed do. So you will have to either go through and remove every system change they made or flash a stock rom for the device. Sometimes they are not released by the oem.
Click to expand...
Click to collapse
And how do I find them if they are not released?
TheMasterSimo said:
And how do I find them if they are not released?
Click to expand...
Click to collapse
If the OEM didnt release them then you cant. It is one of the risks you run when you mess with your device. Most of the time unless it is a major flagship release then they dont post them.
zelendel said:
If the OEM didnt release them then you cant. It is one of the risks you run when you mess with your device. Most of the time unless it is a major flagship release then they dont post them.
Click to expand...
Click to collapse
I connected my lg to lg mobile support tool, but as I said I changed the recovery... It finds an update, but if I start it, will it work since I modified the recovery?
TheMasterSimo said:
I connected my lg to lg mobile support tool, but as I said I changed the recovery... It finds an update, but if I start it, will it work since I modified the recovery?
Click to expand...
Click to collapse
No it wont. It will leave you with a bricked device. Welcome to the world of modding. Your best bet will be to wait for someone to make an update rom for your device.
zelendel said:
No it wont. It will leave you with a bricked device. Welcome to the world of modding. Your best bet will be to wait for someone to make an update rom for your device.
Click to expand...
Click to collapse
I found a rom, I just don't know how to step back at this time if the flash won't work... I mean... I need 4GB free for a nandroid backup and my SD card can't reach that space... Anyway... just another question... During power off, I can't access recovery mod, my only way to do it, is with quick boot. Is it possible? If it is how do i change it?