ive been having issues with the speaker going in and out for the past few days. contacted verizon for a replacement and it should be here in 12 hours with the help of overnight shipping. i was wondering if theres a point in relocking the bootloader and loading a stock image again or just send it out as is?
You better return to stock, relock the bootloader. I would. If Verizon decides that because you rooted the phone, you messed up the speaker, you will have to pay for both of the phones.
Received my new device and relocked the bootloader on the old device.. New device's screen seems better. It doesn't have the weird flickering issue I had with the other one when on low brightness. Such a shame to peal off my red slick wrap that was put on perfectly though.
tommyntpham said:
Received my new device and relocked the bootloader on the old device.. New device's screen seems better. It doesn't have the weird flickering issue I had with the other one when on low brightness. Such a shame to peal off my red slick wrap that was put on perfectly though.
Click to expand...
Click to collapse
Hey man, I'm thinking of relocking my bootloader too so that I can RMA my phone. I plan to reflash the stock image (NDE63X) and relock it. How did you manage to do it? just through fastboot ?
andrep182 said:
Hey man, I'm thinking of relocking my bootloader too so that I can RMA my phone. I plan to reflash the stock image (NDE63X) and relock it. How did you manage to do it? just through fastboot ?
Click to expand...
Click to collapse
Hello,
Just download a Verizon factory image here: https://developers.google.com/android/images
Use the included flash-all script and relock the bootloader afterward. :good:
Cheers...
What update did it come with? Were you able to unlock and root the new one? I went through google for a warranty and thought maybe there was a chance at a google version but it looks like its gonna be a Verizon version. I wasnt unlocked on other one as I got it off of swappa and he had already updated it too far.
Related
Is anybody able to help, for some reason my wifi has stopped working all together, I have flashed different kernels, roms and have now just reflashed the stock google 4.0.2 image but it is still greyed out and just says turning wifi on when i try to turn it on....I have flashed the phone from the stock carrier image so am unsure if they will honor the warranty.
Thanks
Paul
Pranksta02 said:
Is anybody able to help, for some reason my wifi has stopped working all together, I have flashed different kernels, roms and have now just reflashed the stock google 4.0.2 image but it is still greyed out and just says turning wifi on when i try to turn it on....I have flashed the phone from the stock carrier image so am unsure if they will honor the warranty.
Thanks
Paul
Click to expand...
Click to collapse
If restoring the stock image didn't work, you should lock the bootloader and send it to Samsung repair service with warranty
It came with a branded rom when i brought it tho which would mean I have voided the warranty wouldnt it?
Pranksta02 said:
It came with a branded rom when i brought it tho which would mean I have voided the warranty wouldnt it?
Click to expand...
Click to collapse
are you sure it was branded? i might be wrong, but there's no branded galaxy nexus. Maybe you just bought with a mobile provider, but it's not branded
it was a yakjudv i think and i flashed it to yakju..
Pranksta02 said:
it was a yakjudv i think and i flashed it to yakju..
Click to expand...
Click to collapse
ok, but it's still google Stock Image you downloaded from the official website right? I think that cannot invalidate your warranty, unlocking the bootloader does, having a yakju image doesn't
but they would know that flashing the google image requires unlocking the bootloader?
Pranksta02 said:
but they would know that flashing the google image requires unlocking the bootloader?
Click to expand...
Click to collapse
I don't think they'll act like *****es trying to avoid your warranty. But if you really want to be sure, just open a thread requesting yakjudv image; probably someone has it and can share it with you.
Same thing happend to me, in the end I flashed back to stock and relocked my bootloader contacted Negri Electronics and rma'd mine. I'm stuck using my old Dell Streak now while my baby is in the shop. Really sucks especially with AT&T doing all their throtling and such now I was worried that i'd get throtled because I couldnt use my wifi. Good luck to you man.
My nexus 7 is unlocked and rooted etc. I have insurance on it in case of screen damage. If I did drop it and it was damaged would insurance still cover it even though its rooted? I wouldn't see why not but thought I would check.
razormccabe said:
My nexus 7 is unlocked and rooted etc. I have insurance on it in case of screen damage. If I did drop it and it was damaged would insurance still cover it even though its rooted? I wouldn't see why not but thought I would check.
Click to expand...
Click to collapse
Normally the disclaimer said "Warranty is void if you unlock your device", but it's only in case of the problem is caused by the fact of unlocking/rooting the device. In fact they just cover their back ^^.
Your OS cannot break physically your screen (Fortunately ^^). Some people got their devices replaced on custom ROMed devices by Asus. If you want to RMA your device, if your device still running a bit, and to be sure, factory reset and relock your bootloader before sending it.
Sincerely
Cheers, can I unroot and relock all via windows? As in, if the device couldn't be used at all?
razormccabe said:
Cheers, can I unroot and relock all via windows? As in, if the device couldn't be used at all?
Click to expand...
Click to collapse
Yes, you can unroot and relock bootloader all via Windows. You just restore with factory image, and type in fastboot
Code:
fastboot oem lock
If the device is unusable, i mean nothing showing on the screen, i think Asus will not search for unlocking.
A long time ago, i was playing with my San Diego, and bricked it (When i tried to play with the locked bootloader and flash some suckastuff from me) and they accepted it on RMA, fortunately ^^
What is the best way to root G4, whilst keeping it "friendly" for warranty claims?!?
Hi, forgive me if this thread isn't in the appropriate section.
I have a bit of rooting experience, haven't done much in a few years though, (knowing that there are now several ways to root devices), and have just picked up the G4.
Now I'd like to root the G4, but keep the stock rom, (6.0) and mainly will be just running xposed to edit and muck around with LG's ugly skin. I'd still like to be able to receive OTA updates, (even if the OTA update may remove my root,) as well as hopefully still be fine if I needed to return the device under warren.
I've been reading around and apparently you must unlock the bootloader in order to root for Marshmallow? If i were to still do this, could I keep the stock recovery at least, or if not, would I be able to easily revert to stock with a stock recovery and relock the bootloader?
Apologies for my ignorance, just trying to figure out if I should really be rooting or just chuck on Nova launcher and be happy with LG's offerings. Cheers
Keep it on a stock rom and if yoi have a carrier varient then try to not change the boot logo lol idk just a guess.
Jared_Anderson said:
Hi, forgive me if this thread isn't in the appropriate section.
I have a bit of rooting experience, haven't done much in a few years though, (knowing that there are now several ways to root devices), and have just picked up the G4.
Now I'd like to root the G4, but keep the stock rom, (6.0) and mainly will be just running xposed to edit and muck around with LG's ugly skin. I'd still like to be able to receive OTA updates, (even if the OTA update may remove my root,) as well as hopefully still be fine if I needed to return the device under warren.
I've been reading around and apparently you must unlock the bootloader in order to root for Marshmallow? If i were to still do this, could I keep the stock recovery at least, or if not, would I be able to easily revert to stock with a stock recovery and relock the bootloader?
Apologies for my ignorance, just trying to figure out if I should really be rooting or just chuck on Nova launcher and be happy with LG's offerings. Cheers
Click to expand...
Click to collapse
Yes to reflashing stock rom
Yes to relocking the bootloader
So you are clear to make whatever modifications you want, you can always revert safely.
Vseprz said:
Yes to reflashing stock rom
Yes to relocking the bootloader
So you are clear to make whatever modifications you want, you can always revert safely.
Click to expand...
Click to collapse
Once your bootloader is unlocked, you cannot relock it. Your device will always show a message saying "Bootloader unlocked" after turned on. Warranty is likely to be declined then. BTW: You have to get your unlock.bin file from lg, agreeing to void your warranty. So, even if you smash your screen and they cannot see the message, lg knows it is out of warranty.
pen² said:
Once your bootloader is unlocked, you cannot relock it. Your device will always show a message saying "Bootloader unlocked" after turned on. Warranty is likely to be declined then. BTW: You have to get your unlock.bin file from lg, agreeing to void your warranty. So, even if you smash your screen and they cannot see the message, lg knows it is out of warranty.
Click to expand...
Click to collapse
Since when do you have to get the unlock.bin? We unlock from fastboot. Have you confirmed by trying to relock from fastboot? I read otherwise from another thread.
Furthermore, a quick search around indicates people who have unlocked and rooted have had their warranty honored despite software changes.
Vseprz said:
Since when do you have to get the unlock.bin? We unlock from fastboot. Have you confirmed by trying to relock from fastboot? I read otherwise from another thread.
Furthermore, a quick search around indicates people who have unlocked and rooted have had their warranty honored despite software changes.
Click to expand...
Click to collapse
Unlock from fastboot is only possible after flashing said unlock.bin file, which can only be obtained by lg and is unique for each device. Furthermore, I had an unlocked, bootlooping h815 and lg refused warranty to me (in Germany). Got my phone replaced by my vendor on eu law which only applies if the defect strikes in the first six months.
So, while some people are lucky to have their phone repaired despite an unlocked bootloader, I'm really happy for them, but lg is not bound to repair it on warranty
pen² said:
Unlock from fastboot is only possible after flashing said unlock.bin file, which can only be obtained by lg and is unique for each device. Furthermore, I had an unlocked, bootlooping h815 and lg refused warranty to me (in Germany). Got my phone replaced by my vendor on eu law which only applies if the defect strikes in the first six months.
So, while some people are lucky to have their phone repaired despite an unlocked bootloader, I'm really happy for them, but lg is not bound to repair it on warranty
Click to expand...
Click to collapse
Ah I see. You have a h815. I have a h811. Our process differs there.
Hmmm, thanks for the info guys. Its not from a carrier, i bought it outright. Seems like i might just have to keep it stock, its not too bad as is, guess ill just have to live with it. Thanks for the help though.
Jared_Anderson said:
Hmmm, thanks for the info guys. Its not from a carrier, i bought it outright. Seems like i might just have to keep it stock, its not too bad as is, guess ill just have to live with it. Thanks for the help though.
Click to expand...
Click to collapse
At least you can root with locked bootloader
Not under marshmallow
You can do none of things you listed keeping it stock. First of all google change policy and in marshmallow you need to flash modified boot.img in order to flash custom recovery and/or to root it. As you know the bootloader has to be unlocked but there is no way to relock it. So sorry, but impossible.
People need to understand a simple thing.
You either mod your device and lose warranty or you keep it stock.
It's that simple. People worried about warranties and ota updates are on the wrong site.
I unlocked my bootloader several months ago, but now my SIM card readers (both of them) have gone out. I have no idea how, no water damage or anything like that has happened. They just stopped working. So I went complete stock firmware, locked bootloader, everything but I am still unable to take OTA updates like a new phone would be able to. I think this is because they banned my device from OTAs which I believe they do if you have messed with the device. I need to RMA my device so my question is would it be better to say that I didn't tamper with the device and run the risk of them finding out I did, which is pretty likely seeing as how my device has been banned from OTA updates, or tell them that I did unlock it and all of that but that I have relocked it and I am back to stock? If any of you have had a similar issue how did ASUS handle that? Thanks!
E3AANG11E3 said:
I unlocked my bootloader several months ago, but now my SIM card readers (both of them) have gone out. I have no idea how, no water damage or anything like that has happened. They just stopped working. So I went complete stock firmware, locked bootloader, and all of that but that I have relocked it.
Click to expand...
Click to collapse
How to you relock bootloader?
mr_gourav2000 said:
How to you relock bootloader?
Click to expand...
Click to collapse
Since I am a new user I cannot post links. But Google "Zenfone 2 bootloader unlock" and I followed the instructions of Grekky's Blog.
there is no such thing as relocking the bootloader. only thing you can do it flash the stock image to make it look stock (since an unlocked bootloader has a white splash screen) but im sure asus knows of this and will still check and see that the bootloader is indeed unlocked and not warranty it.
This is just something we all accepted as a consequence of unlocking our bootloaders. hell i have a screen thats getting worse and worse with a yellow/brownish line coming from the top of the phone, but alas i have an unlocked phone too.
You can replace the white splash screen by flashing a black splash screen image to try and cover up unlocking your bootloader. http://forum.xda-developers.com/zenfone2/themes-apps/551-black-white-splashscreen-twrp-flash-t3141945 . If the reseller has no clue about custom recoveries and trying to flash a rom you'll be safe.
They fixed it, no questions asked. And yes, I was able to relock the bootloader.
OK so I am going to have to return my pixel xl for a factory refurbished due to hardware issues with the camera flash. How do I relock the bootloader before taking it back?
Fastboot flashing lock? Or oem lock?
Sent from my Pixel XL using Tapatalk
oneandroidnut said:
Fastboot flashing lock? Or oem lock?
Click to expand...
Click to collapse
It's that simple? Just run the fast lock command?
shibbnasty said:
It's that simple? Just run the fast lock command?
Click to expand...
Click to collapse
I think lol it's been awhile since I locked a phone
Sent from my Pixel XL using Tapatalk
oneandroidnut said:
I think lol it's been awhile since I locked a phone
Click to expand...
Click to collapse
I guess I should have mentioned as well it's a Verizon pixel xl and I had to use depixel8 to unlock it
shibbnasty said:
OK so I am going to have to return my pixel xl for a factory refurbished due to hardware issues with the camera flash. How do I relock the bootloader before taking it back?
Click to expand...
Click to collapse
You better be absolutely sure that your device is completely stock before relocking the bootloader. Once you are sure, boot into the bootloader and type, fastboot OEM lock
lyall29 said:
You better be absolutely sure that your device is completely stock before relocking the bootloader. Once you are sure, boot into the bootloader and type, fastboot OEM lock
Click to expand...
Click to collapse
All I have done is unlock it. I have not flashed any kernels or mods or anything.
shibbnasty said:
All I have done is unlock it. I have not flashed any kernels or mods or anything.
Click to expand...
Click to collapse
Ok then. You should be fine. fastboot OEM lock will lock your bootloader and wipe your data at the same time.
lyall29 said:
Ok then. You should be fine. fastboot OEM lock will lock your bootloader and wipe your data at the same time.
Click to expand...
Click to collapse
Thank you very much!
@shibbnasty. Actually, relocking the bootloader may not wipe data. I can't remember. Let me know if it does or not.
Yes it does.
Rank N00b here... just getting that out of the way.
Device: Verizon Pixel XL
Build: NDE63X
Bootloader: unlocked via dePixel8 (done after Nov update)
So the phone is stock and I'm not really keen on modding right now. I don't want to use a alpha build of TWRP and SuperSU seems to be in flux too. These aren't criticisms by the way; I realize this a very new handset and those kinds of tools take time to develop. Nothing happens overnight.
So, anyway, my phone is currently unlocked and I'm wondering if I'm not better off relocking it? As a stock unit, it should still get OTA's, right? Like I said, total n00b here...
@loaba,
There's absolutely no reason to relock your bootloader, unless you are annoyed by the Google bootloader unlock warning during boot, or if you are planning on returning it or selling it. Otherwise, leave it unlocked. Gives you much greater flexibility to recover if something goes wrong.
@cam30era,
Thanks for the reassurance.
loaba said:
@cam30era,
Thanks for the reassurance.
Click to expand...
Click to collapse
Also, Verizon may remove unlock ability via dePixel8 in their December update.
If that happens, you might have to wait awhile to get Unlock on a VZN Pixel again.
michaelbsheldon said:
Also, Verizon may remove unlock ability via dePixel8 in their December update.
If that happens, you might have to wait awhile to get Unlock on a VZN Pixel again.
Click to expand...
Click to collapse
So if I want to maintain an unlocked device I need to act now... Guess I'll see which comes first - the possibly debilitating Dec update or a stable TWRP build (and a correspondingly stable custom ROM).
loaba said:
So if I want to maintain an unlocked device I need to act now... Guess I'll see which comes first - the possibly debilitating Dec update or a stable TWRP build (and a correspondingly stable custom ROM).
Click to expand...
Click to collapse
Yep, do nothing and stay unlocked. You will still receive VZN OTA's and stay up to date as long as you do not install a custom recovery or kernel.
AND since you've remained unlocked, when the time comes that you do want a custom kernel or recovery, you can get them.
If it gets messed up somehow, you can do a clean RUU install as if nothing happened. If it's locked, you can't do that as easily.
michaelbsheldon said:
Yep, do nothing and stay unlocked. You will still receive VZN OTA's and stay up to date as long as you do not install a custom recovery or kernel.
AND since you've remained unlocked, when the time comes that you do want a custom kernel or recovery, you can get them.
If it gets messed up somehow, you can do a clean RUU install as if nothing happened. If it's locked, you can't do that as easily.
Click to expand...
Click to collapse
About the OTA's - that was my big concern for now. Cool.
OP - thread derailed... sorry, man.
You cannot use Android pay on an unlocked phone. Unless there is a workaround.
Khanusma said:
You cannot use Android pay on an unlocked phone. Unless there is a workaround.
Click to expand...
Click to collapse
Most of the custom kernels fix that. Root is the hard one to hide.