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.
I have just rooted my Photon. Pretty happy with it. Wasn't as hard as I thought it was gonna be. Now to overclock it am I gonna have to flash a custom ROM? And if I indeed have to flash a custom ROM, do I have to unlock my bootloader? Or is there a way around that? Thanks for all the info.
There's a few threads floating around about unlocking your bootloader; id be careful though you could possibly break 4G. As far as kernels go, the source was released a week ago so you cant overclock until a dev releases a kernel. You'd need to flash a custom kernel in order to flash roms...
I rooted my phone and left it stock just for a few root apps at least until a new bootloader unlocking method is found and a kernel is ready!
Bootloader thread. Fyi there are ways to retain 4G just check development section.
http://forum.xda-developers.com/showthread.php?t=1216097
As soon as android.git.kernel.org comes back up I'm going to pull in some source code and see if I can cook up a CyanogenMod kernel.
Cool appreciate all the info guys. And as for the 4G. I don't use it and it's not in my area. So I'm not very worried about that to be quite honest. I'm having trouble tryin' to flash a custom ROM on my phone as of now. I don't seem to be doing it right.
Okay. As you two seem to know what's going on. I just flashed the Laser ROM onto my phone. And the su binary is outdated. But when I update, the superuser force closes. Is this common with custom ROM's? I tried to ask in the development page, but as I don't have enough posts, it wouldn't let me post there. Thanks! Also, as a side note. I didn't seem to have to unlock my bootloader to do the laser ROM but the Alien one says I do? Is this true? Again, I know this isn't the right area. but it's the only place I can post. Thanks again guys.
xTMFxOffshore said:
Okay. As you two seem to know what's going on. I just flashed the Laser ROM onto my phone. And the su binary is outdated. But when I update, the superuser force closes. Is this common with custom ROM's? I tried to ask in the development page, but as I don't have enough posts, it wouldn't let me post there. Thanks! Also, as a side note. I didn't seem to have to unlock my bootloader to do the laser ROM but the Alien one says I do? Is this true? Again, I know this isn't the right area. but it's the only place I can post. Thanks again guys.
Click to expand...
Click to collapse
Assuming you flashed the latest custom recovery right? Also there's an app in the market that helps with the updating of superuser if it fails. Its called "superuser update fixer"; maybe that will help as i didnt have that issue. Yes with alien rom you do but there's a guide that lets you retain 4G with the alien rom.
Bootloader unlock instructions with alien link.
http://forum.xda-developers.com/showthread.php?t=1227867
Thanks Kenny. I appreciate the info. I got that first issue with the su fixed. And I flashed the Laser P-Rom with cwm or whatever it's called. As for 4G, not too concerned with that. But I will see about unlocking the bootloader today. I appreciate all the info.
xTMFxOffshore said:
Thanks Kenny. I appreciate the info. I got that first issue with the su fixed. And I flashed the Laser P-Rom with cwm or whatever it's called. As for 4G, not too concerned with that. But I will see about unlocking the bootloader today. I appreciate all the info.
Click to expand...
Click to collapse
If you don't need 4G then flash away and unlock bootloader dude you should have no issues
Yeah. I'm gonna run out and do some stuff, come home then unlock my bootloader and flash that Alien ROM. How difficult is it to unlock the bootloader?
xTMFxOffshore said:
Yeah. I'm gonna run out and do some stuff, come home then unlock my bootloader and flash that Alien ROM. How difficult is it to unlock the bootloader?
Click to expand...
Click to collapse
Not difficult at all if you managed to root your phone lol
Overclock photon pleaseee
I want to know who's gonna be the first to post a overclock kernel for the photon
Cool Thanks again Man. I'm gonna try to do this tonight. But I keep getting caught up working on someones car or doing something of that nature. ha. But tonight hopefully! I'll post back once I do it and get the Alien ROM flashed.
No such luck, I can't flash the SDF file or something like that. and I'm not really all that intune with what I'm doing. So I don't know what's wrong and I keep getting a failed when I try to flash it. So I think I'm just kinda stuck not having an unlocked bootloader.
Okay. As I wanted to throw my phone at the wall but though better of it. And I really don't understand the Pudding thread. As I read through it. I used this http://briefmobile.com/motorola-photon-4g-bootloader-unlocked to no avail. I got a fail to flash on RSD Lite when attempting to flash the derpun.spf So now that I've come to a point of impass. Any ideas?
xTMFxOffshore said:
Okay. As I wanted to throw my phone at the wall but though better of it. And I really don't understand the Pudding thread. As I read through it. I used this http://briefmobile.com/motorola-photon-4g-bootloader-unlocked to no avail. I got a fail to flash on RSD Lite when attempting to flash the derpun.spf So now that I've come to a point of impass. Any ideas?
Click to expand...
Click to collapse
Was your phone at least 50% charged when you attempted it? If it wasn't you will get errors! Maybe you skipped out on a command? You should try posting the error you're getting in the bootloader thread so a few devs can see it. I would imagine many of them hang around their section and not general lol.
http://forum.xda-developers.com/showthread.php?t=1216097
It's the same error that photon pudding thread spoke of, Tried to use that fix. Didn't work. And the rest of it I can't make any sense of. I don't follow it, and the stupid site I used didn't work. So unless there is an easier way that is more clear to unlock it. I think I'm SOL.
xTMFxOffshore said:
It's the same error that photon pudding thread spoke of, Tried to use that fix. Didn't work. And the rest of it I can't make any sense of. I don't follow it, and the stupid site I used didn't work. So unless there is an easier way that is more clear to unlock it. I think I'm SOL.
Click to expand...
Click to collapse
Im waiting for an easier method myself that doesn't break 4G. Lol.
Yeah, someone was saying that his flash failed, but to run the fastboot. now I'm stuck at that. How the hell do I run the fastboot? haha.
Got it done. :]
xTMFxOffshore said:
Got it done. :]
Click to expand...
Click to collapse
Nice!!!! Im sure you're ready to flash away lol. Congrats dude!
Hello, I rooted and unlocked my hox+ bootloader but i started to notice that my phone may have come with camera problems, you know that problem that makes your pictures look blurry, i read in other post it is a hardware problem (i tried wiping, re installing stock firmware and is the same) so i have been contacting htc support service and i know that if i sent my phone due to the bootloader thing they are going to return it, so the case is, is there any way i can remove the relocked status? you know that it says jus "locked" i read in the one x thread there is a solution but i dont know if is going to work on my device, any help would be appreciated, thanks
Uniquetx said:
Hello, I rooted and unlocked my hox+ bootloader but i started to notice that my phone may have come with camera problems, you know that problem that makes your pictures look blurry, i read in other post it is a hardware problem (i tried wiping, re installing stock firmware and is the same) so i have been contacting htc support service and i know that if i sent my phone due to the bootloader thing they are going to return it, so the case is, is there any way i can remove the relocked status? you know that it says jus "locked" i read in the one x thread there is a solution but i dont know if is going to work on my device, any help would be appreciated, thanks
Click to expand...
Click to collapse
Do you know much about adb?
When I had my Sensation, this thread explained how to do it with adb, or with flashable zips. Maybe, if you understand the workaround with adb (I don't really understand it), you can try to find out what to change in order to make it work for HOX+
However, if you don't know much about it, I certainly don't advice you to do ANYTHING, in case you brick your device
http://forum.xda-developers.com/showthread.php?t=2047214
TatoValverde said:
Do you know much about adb?
When I had my Sensation, this thread explained how to do it with adb, or with flashable zips. Maybe, if you understand the workaround with adb (I don't really understand it), you can try to find out what to change in order to make it work for HOX+
However, if you don't know much about it, I certainly don't advice you to do ANYTHING, in case you brick your device
http://forum.xda-developers.com/showthread.php?t=2047214
Click to expand...
Click to collapse
hello! thanks for your reply, to be honest i do not know that mucho about adb, guess i am going to start reading about it, then try this, thanks
Hey guys. Sorry if this has been answered before. I've looked and didn't see it in here so I figured I'd ask. I really don't want to set my phone into "custom" status in case I drop it or break it somehow Anyway, my question is will installing TWRP recovery from GooManager get me a "custom" status? Also, if I install a custom ROM, is there anyway to "trick" it into saying "Official" when I have ROMs and TWRP installed? I really wanted to install ROMs, but I'm too afraid of dropping it or something while the ROM is installed. Thanks!
I believe the "Custom" shows up periodically if you have a custom ROM installed. But really, it shouldn't bother people so much. It's pretty easy to tell if a custom ROM is installed without rebooting the phone. If Verizon cared that much, they could find out. FWIW, I didn't see "Custom" with the open padlock at boot when running stock rooted (aside from during the root process using the pre-release kernel.) It was only after installing a custom ROM that I see it periodically now.
Tortuga said:
I believe the "Custom" shows up periodically if you have a custom ROM installed. But really, it shouldn't bother people so much. It's pretty easy to tell if a custom ROM is installed without rebooting the phone. If Verizon cared that much, they could find out. FWIW, I didn't see "Custom" with the open padlock at boot when running stock rooted (aside from during the root process using the pre-release kernel.) It was only after installing a custom ROM that I see it periodically now.
Click to expand...
Click to collapse
Thanks for your reply But the reason I'm asking is because I wanted to know if there's any way to install a recovery or custom ROM while keeping the "official" status for warranty reasons. Is there?
Dark_Spark said:
Thanks for your reply But the reason I'm asking is because I wanted to know if there's any way to install a recovery or custom ROM while keeping the "official" status for warranty reasons. Is there?
Click to expand...
Click to collapse
If you were to physically damage it, you would likely still be able to boot to download mode and Odin back to 100% stock. In that case you'd have what you are asking for. I don't believe there is a way to spoof the phone into thinking it's fully official. Like I said, if Verizon/Asurion/etc care enough, they should be able to find out unless you flash back to pre-root stock. Someone else can correct me if I'm wrong.
Tortuga said:
If you were to physically damage it, you would likely still be able to boot to download mode and Odin back to 100% stock. In that case you'd have what you are asking for. I don't believe there is a way to spoof the phone into thinking it's fully official. Like I said, if Verizon/Asurion/etc care enough, they should be able to find out unless you flash back to pre-root stock. Someone else can correct me if I'm wrong.
Click to expand...
Click to collapse
Sorry to ask a million questions, but I used to have my GS4 on the stock ROM but rooted but with TWRP recovery. The statuses everywhere read as Samsung Official. I mean even in ODIN mode too. Is that what they check for in the warranty process? Or can they detect if it was just rooted or have a custom recovery and deny a warranty claim? Thanks for your patience with me.
Dark_Spark said:
Sorry to ask a million questions, but I used to have my GS4 on the stock ROM but rooted but with TWRP recovery. The statuses everywhere read as Samsung Official. I mean even in ODIN mode too. Is that what they check for in the warranty process? Or can they detect if it was just rooted or have a custom recovery and deny a warranty claim? Thanks for your patience with me.
Click to expand...
Click to collapse
Happy to help...but I really don't know what Verizon or the insurance provider would check. Some individuals within those places will probably check more thoroughly than others. But I've heard several stories of people taking their phone to Verizon, the tech seeing that it's rooted/fully custom, and replacing it anyway.
If you ever need to take it in for a warranty claim (hardware issue) I'd go back to stock first, but that's my personal opinion.
Edit: Even if it's just stock w/ root, a decently savvy tech could tell just by looking into your app list and seeing "SuperSU" or "SuperUser" or any other root-required apps.
Dark_Spark said:
Hey guys. Sorry if this has been answered before. I've looked and didn't see it in here so I figured I'd ask. I really don't want to set my phone into "custom" status in case I drop it or break it somehow Anyway, my question is will installing TWRP recovery from GooManager get me a "custom" status? Also, if I install a custom ROM, is there anyway to "trick" it into saying "Official" when I have ROMs and TWRP installed? I really wanted to install ROMs, but I'm too afraid of dropping it or something while the ROM is installed. Thanks!
Click to expand...
Click to collapse
No ,there is no method published till now. Possibility to do that is less then 20% since we cant access the hidden scripts for analysing binary counts..
Sent from my GT-I8552 using xda app-developers app
Tortuga said:
Happy to help...but I really don't know what Verizon or the insurance provider would check. Some individuals within those places will probably check more thoroughly than others. But I've heard several stories of people taking their phone to Verizon, the tech seeing that it's rooted/fully custom, and replacing it anyway.
If you ever need to take it in for a warranty claim (hardware issue) I'd go back to stock first, but that's my personal opinion.
Edit: Even if it's just stock w/ root, a decently savvy tech could tell just by looking into your app list and seeing "SuperSU" or "SuperUser" or any other root-required apps.
Click to expand...
Click to collapse
Thank you!
so i had this thought. we talk alot in the "rom's" thread about the progression of the custom recovery.
although my phone is on servide and i cant do much ar this point but i hope i get it back in a couple of weeks.
but my thought was this.. everyone here should post all files they can to make this work.
what they have tried and what did not work so people dont have to try it again.
whos working hard on this and what theire progression is, or if anyone can post files that could work and perhaps some tutorials for it.
i think that would be better then to update this OP and write everything down that have been tried and so on.
it was just a thought to make this work out its best way. ive been sending PM's to som developers and asked if they could give me some tutorials on this but non has answeres yet. ive been trying alot of different adb reboot commands, nothing work. i also was that stupid and tried autorec for lg g2 and that bricked my phone HARD so dont ever try that.
Loki is the key for this phone, I don't think that anything else works.
Garcia98 said:
Loki is the key for this phone, I don't think that anything else works.
Click to expand...
Click to collapse
okej then. loki it is. now how do we go about to port this to our device?
found this, my phone like i said is on service so yeah, take a look
http://androidforums.com/motion-4g-all-things-root/733454-tried-port-loki-failed.html
and have a look at this http://forum.xda-developers.com/showpost.php?p=43480931&postcount=11
perhaps if we give djrbliss this info he can help us out?