So I just had a pixel that popped up that's either stuck or dead. I've tried the apps in the play store to try and fix it, but no luck. I have 7 days to return to amazon wireless. The question is, should I. Its really not that bad, and its a hassle to have to redo my phone, but I notice it, no one else does.
My question is, If I did return it (exchange or whatever) should I relock the bootloader, unroot etc? Or....who really cares...send it back as is? I would obviously nandroid back to my stock image at least though and do a factory reset.
chugger93 said:
So I just had a pixel that popped up that's either stuck or dead. I've tried the apps in the play store to try and fix it, but no luck. I have 7 days to return to amazon wireless. The question is, should I. Its really not that bad, and its a hassle to have to redo my phone, but I notice it, no one else does.
My question is, If I did return it (exchange or whatever) should I relock the bootloader, unroot etc? Or....who really cares...send it back as is? I would obviously nandroid back to my stock image at least though and do a factory reset.
Click to expand...
Click to collapse
Backup your current system/data with a nandroid.
Transfer it to your computer along with whatever "sdcard" data you want to keep.
Then restore whenever you get your replacement.
Flash back to stock and relock.
You might as well...it takes 10 minutes. And what if they have a problem with it not being stock and locked?
I don't know their policies but they might charge you full retail to get an exchange...half price...or return your original phone.
Whatever the case may be, it's just not worth it.
I'm ready to do this today. My concern is this....if I flash back to my stock image, won't it still have SuperSU installed? Also, my recovery will still be on there as well won't it? Or will relocking the bootloader eliminate Clockwork?
Related
Hello All,
I've seen multiple threads but none that exactly answered that question I had, two part question actually.
1. So I have a replacement battery waiting for my at a Verizon store. What are the chances they will want to troubleshoot the phoen before making the swap, possibly seeing it's unlocked and rooted, then giving me some textbook well the problem might have been you unlocking your phone and voiding the warranty. Do you think they would check?
2. If it's probable, I would flash back to stock. Now I've done the unlocking and rooting manually as per suggested and had tons of fun flashing new ROMs, bricking, and restoring, but I have yet to do a full flash back to stock/relock. Will this wipe all of my current Nandroid backups or remove CWM? Or is flashing back to stock and relocking, just like any other factory reset/data wipe I do in between ROMS? I'm just curious of the workload I'd have to put in all to flash back to stock for 5 min to swap the battery, then literally flash my next favorite ROM in the parking lot.
I apologize for the newbness, still learning.
Thanks all.
For me what I do is that I restore to stock and wipe so they have no evidence or what you could try and do is go to stock download an app called bootunlocker and lock the phone. You can unlock the bootloader again without wiping. Then to hide the root apps just install a third party launcher with a hidden apps feature.
Galaxy Nexus-codenameandroid rom
Chances are 50/50. They might check hardware and software to see if it is the problem with the battery or just a phone.
Going back to stock using this guide.
Personally, I would do a nandroid first, transfer it to computer, so you won't lose nothing at all when you get it back.
For a while now I've been getting system updates but they've always failed during application (ie the red exclamation icon after reboot). This wasn't bothering me too much but now that Sprint has finally decided to roll out Jellybean I'm trying to figure out what the issue is. I've never rooted the phone (although I nearly did yesterday before hearing the news re:Sprint). I've gone so far as backing up everything on my phone and doing a factory reset and I still have this happening. Does anyone have any possible idea what might be wrong or what I could check to see what is wrong, like an error log or something similar. The build is IMM76D if that helps.
becktionary said:
For a while now I've been getting system updates but they've always failed during application (ie the red exclamation icon after reboot). This wasn't bothering me too much but now that Sprint has finally decided to roll out Jellybean I'm trying to figure out what the issue is. I've never rooted the phone (although I nearly did yesterday before hearing the news re:Sprint). I've gone so far as backing up everything on my phone and doing a factory reset and I still have this happening. Does anyone have any possible idea what might be wrong or what I could check to see what is wrong, like an error log or something similar. The build is IMM76D if that helps.
Click to expand...
Click to collapse
That is the stock recovery image. You are probably seeing it because you have something that is not stock (i.e., something that you change), whether it be a radio, a kernel, or a system file. If you remember what you change, change it back. Otherwise flash everything back to stock.
efrant said:
That is the stock recovery image. You are probably seeing it because you have something that is not stock (i.e., something that you change), whether it be a radio, a kernel, or a system file. If you remember what you change, change it back. Otherwise flash everything back to stock.
Click to expand...
Click to collapse
Ok, since then I had rooted my phone but decided to reverse it. I've since used WugFresh's Nexus Root Toolkit to flash back to stock, unroot and lock the phone.
Even after doing all of that I'm still getting the same stock recovery image. I haven't done anything since flashing it back to the stock image aside from setting up my google account on it.
Even when returning to stock you likely didn't flash all parts of the image, so you're missing something like the proper bootloader, radio, or recovery for that specific build. This is another great example of why toolkits are a bad idea. You have no idea what you've flashed.
op, go and ask your question in that toolkit thread
Sent from my i9250
Hello,
My Gnex was in a bootloop 1 week after purchasing it, (I was running ICS then) now I have JB, after wiping all my data, I decided I should root it, (stock ROM) and unlock it, so I could make Nandroids, now once again, it got in a bootloop, I know how to relock it, but I can`t unroot it for some reason( I am using WugfreshDkit).
My problem is now, my computer crashed with the back up I made before installing Custom blue Softkeys, I need to send it back to the service center, and I am afraid I will get the response ""This is your own mistake for tampering with your phone"" I already backed everything up, and I am able to Lock the device, but it still has root, Will they mind this? does anyone have experience with this? and does anyone know for a fix for the softkeys?
I know it has one hardware defect,( Connecting the chargedock to the Motherboard) and the bootloops...
Also, If I get a new phone, is it save to just Unlock & Root it and use my Nandroid backups on it? or does this give a chance that it will get bootloops again?
I know Sprint and Verizon make a big deal about this, and even charge people for it... Will samsung do this too?
Already got it, Also after Wiping I got updates to 4.2.1
I want to love the OnePlus 3 but I'm not feeling it. I'm unlocked, rooted and running X-Posed framework and gravitybox on the 3.1.2 update.
Things that are really bugging me right now compared to the LG G3 I came from:
Lack of SD card. I thought I wouldn't care but I do. The 64GB of storage is enough but it was kind of safety blanket with flashing ROMs that I miss.
Inability to change out the battery. I know, only LG has that now, but it was so easy to carry an extra battery in my pocket compared to a charger or a some device and a cord and look for someplace to charge it. It was great while traveling on long flights or walking around all day to never have to think about where and when I need to charge my phone. I don't know that I want to carry that Dash charger everywhere with me.
The power button on the side - this is where I grab the phone when putting it in my pocket so it keeps turning on when I actually want the screen to stay off. LG buttons are on the back.
The screen - I'm fine with the 1080p and I don't need Super pixel whatever, but the light reflections in various environments are very annoying compared to an LCD screen.
I knew these trade-offs when I bought the phone but I didn't think through how I would feel about them.
Maybe I'm overplaying these in my head and they aren't as important as I think they are but again, I'm not feeling the love because of these trade-offs.
I think want to return the OnePlus 3 and get an LG 5 which has all of the features I want (at a higher price). Or maybe just go back to the G3.
But two things...
1) Now that I'm unlocked and rooted, how should I go about restoring the phone to factory (or near factory)? Should I just restore the nandroid backup I took? Or does it not matter?
2) I can't start the return process because the One Plus system doesn't show I've received it yet - I'm going to call and see if I can get an RMA over the phone, but probably not.
You have just noted all of my worries.
I have a G3 at the minute and i said id upgrade when i found a phone that had :
1) SD slot
2) Swapable battery
3) NFC
I've ordered the OP3 but 2 out of my 3 reasons i "forgot" about.
Not sure how i will cope with side buttons again, or a fingerprint scanner on the front.
After this post, i will for sure not be rooting for a while just in case i end up in the same boat.
A
So do I just go into TWRP, clear the caches, and then install the stock recovery.img file over the top? Then, by not installing the SU binaries I'm no longer rooted, correct? I don't care if the bootloader remains unlocked because they should take it back even if it is.
Its better whene you relock the bootloader.
I found the link - seems straightforward. I already put in a return request.
http://forum.xda-developers.com/oneplus-3/how-to/how-to-unroot-oneplus-3-to-stock-oxygen-t3403324
I'm still not sure why the bootloader needs to be re-locked. It seems like that's something that could result in bootloops and other problems.
The LG G5 is what I want but even the H860 (LTE) is not yet unlocked, only the H850. So, I would get some of the features I want back, but then I couldn't root. If I can't root, then I'm stuck having to make software trade-offs. I may have to just stick with the OnePlus 3 now.
digger16309 said:
I found the link - seems straightforward. I already put in a return request.
http://forum.xda-developers.com/oneplus-3/how-to/how-to-unroot-oneplus-3-to-stock-oxygen-t3403324
I'm still not sure why the bootloader needs to be re-locked. It seems like that's something that could result in bootloops and other problems.
The LG G5 is what I want but even the H860 (LTE) is not yet unlocked, only the H850. So, I would get some of the features I want back, but then I couldn't root. If I can't root, then I'm stuck having to make software trade-offs. I may have to just stick with the OnePlus 3 now.
Click to expand...
Click to collapse
Did you have any luck with this? I can't find stock recovery anywhere.
I did not. I'm not returning the phone. I would have returned it with TWRP anyway. A bug in the bootloader puts me into stock recovery half the time anyway.
digger16309 said:
I did not. I'm not returning the phone. I would have returned it with TWRP anyway. A bug in the bootloader puts me into stock recovery half the time anyway.
Click to expand...
Click to collapse
Yeah I think I'm just going to have to return mine with TWRP. I can't help that they haven't released OOS or the recovery yet.
The stock recovery appears to be available with one of the toolkits I forgot which one it's the one with the cmd prompts just download and get the file from there or use it
So I recently had the great idea to root my razer phone after a friend talked me into it, I get the root on but I can't get wifi to turn on, I spend a few hours trying a bunch of different methods to get it working but none of them work. I read magisk can cause an issue, so I delete that and someone says wipe the cache as well in twrp so I do that, switch my slot from b to a and the thing boots straight back to twrp after sitting on the first boot logo for a good 10 minutes. Try the other slot same issue except it boots straight to twrp. So I try and use my backup I made, low and behold its corrupt, at this point I go straight to ****.exe. I try literally everything I can think of and I can't get this thing to take a custom rom, not even a nexbit rom, or a one plus 5t rom. Anyone have any ideas? I've contacted razer and I asked them if there was some way they can fix this without me buying a new phone.
Boltrag said:
So I recently had the great idea to root my razer phone after a friend talked me into it, I get the root on but I can't get wifi to turn on, I spend a few hours trying a bunch of different methods to get it working but none of them work. I read magisk can cause an issue, so I delete that and someone says wipe the cache as well in twrp so I do that, switch my slot from b to a and the thing boots straight back to twrp after sitting on the first boot logo for a good 10 minutes. Try the other slot same issue except it boots straight to twrp. So I try and use my backup I made, low and behold its corrupt, at this point I go straight to ****.exe. I try literally everything I can think of and I can't get this thing to take a custom rom, not even a nexbit rom, or a one plus 5t rom. Anyone have any ideas? I've contacted razer and I asked them if there was some way they can fix this without me buying a new phone.
Click to expand...
Click to collapse
First of all, roms from other phones are not compatible with phones other than what it was designed for. If you tried others, that's why it won't boot up. Secondly, if you read all the posting about how do install twrp, it also said there wasn't any way back EXCEPT for your backups. Unfortunately there is no factory images for the Razer phone released as of yet. If you are unable to restore from your backup (or skipped the step and didn't create one) your only choice is to attempt to restore via the backups Xshooter726 made and posted, and if they don't work, you need to wait till the factory images are released and we don't know when they will be out other then a vague "soon" from a community manager on their forums.
Boltrag said:
So I recently had the great idea to root my razer phone after a friend talked me into it, I get the root on but I can't get wifi to turn on, I spend a few hours trying a bunch of different methods to get it working but none of them work. I read magisk can cause an issue, so I delete that and someone says wipe the cache as well in twrp so I do that, switch my slot from b to a and the thing boots straight back to twrp after sitting on the first boot logo for a good 10 minutes. Try the other slot same issue except it boots straight to twrp. So I try and use my backup I made, low and behold its corrupt, at this point I go straight to ****.exe. I try literally everything I can think of and I can't get this thing to take a custom rom, not even a nexbit rom, or a one plus 5t rom. Anyone have any ideas? I've contacted razer and I asked them if there was some way they can fix this without me buying a new phone.
Click to expand...
Click to collapse
If you're flashing roms for other Devices but now much experience do you have with flashing etc? Ignoring that fact unless backups from other devices work then youve no choice but to wait for razer to put up full factory images in January and flash those. Razer won't help you as you've voided your warranty.
Roxas598 said:
If you're flashing roms for other Devices but now much experience do you have with flashing etc? Ignoring that fact unless backups from other devices work then youve no choice but to wait for razer to put up full factory images in January and flash those. Razer won't help you as you've voided your warranty.
Click to expand...
Click to collapse
I had a decent bit, we only tried to flash another rom after we couldnt find the stock image, it was a last ditch effort.
Boltrag said:
I had a decent bit, we only tried to flash another rom after we couldnt find the stock image, it was a last ditch effort.
Click to expand...
Click to collapse
Well you're lucky none worked it could have made your problem a lot worse. When factory images release you can flash those if the backup doesn't work but until then you're out of luck unfortunately.
Side note if razer ask for imie etc don't give them it. Might be able to list the device as have being unlocked etc.