I just purchased a Verizon Galaxy Nexus on eBay (since they were banned in the US...) and It's in the mail on the way now. It's a new phone, although the guy opened it and upgraded it to 4.0.4 and rooted it. I was planning on doing this, but he did it anyway.
Anyway, I want to install Jelly Bean. I'm no noob when it comes to flashing things, but I was just wondering if there would be any problem having it activated if I flash a ROM beforehand?
The phone has a clean ESN and everything, I just want to confirm that I won't have any problems trying to activate after I have installed JB.
For what it's worth, I was going to flash this with Faux's kernel.
Thanks!
KCP100 said:
I just purchased a Verizon Galaxy Nexus on eBay (since they were banned in the US...) and It's in the mail on the way now. It's a new phone, although the guy opened it and upgraded it to 4.0.4 and rooted it. I was planning on doing this, but he did it anyway.
Anyway, I want to install Jelly Bean. I'm no noob when it comes to flashing things, but I was just wondering if there would be any problem having it activated if I flash a ROM beforehand?
The phone has a clean ESN and everything, I just want to confirm that I won't have any problems trying to activate after I have installed JB.
For what it's worth, I was going to flash this with Faux's kernel.
Thanks!
Click to expand...
Click to collapse
No, you shouldn't have any problem. If it were me, I would, flash Nexus factory images, wipe everything (lock bootloader), and then unlock bootloader, flash custom recovery, gain root, then start my own flashing (since it is a used phone, and you can't be too careful with that kind of stuff.)
anton2009 said:
No, you shouldn't have any problem. If it were me, I would, flash Nexus factory images, wipe everything (lock bootloader), and then unlock bootloader, flash custom recovery, gain root, then start my own flashing (since it is a used phone, and you can't be too careful with that kind of stuff.)
Click to expand...
Click to collapse
+1'd :good:
anton2009 said:
No, you shouldn't have any problem. If it were me, I would, flash Nexus factory images, wipe everything (lock bootloader), and then unlock bootloader, flash custom recovery, gain root, then start my own flashing (since it is a used phone, and you can't be too careful with that kind of stuff.)
Click to expand...
Click to collapse
That's what I thought, thank you.
It's a "new" phone that was used for less than a day, but it's still not brand new, so you're right about that.
Related
hey all, I noticed that jelly bean is out, sort of.
i would like to put it on my nexus but am sofar unable to make sense of the development forums pertaining to this so hopefully someone here can help me understand this.
I used the efrant's post:
http://forum.xda-developers.com/showthread.php?p=21113773#post21113773
to take my yakjuux nexus to yakju (4.0.4) using fastboot and the stock image provided from google...
I would like to upgrade further, though from what i can figure out JB is only available on takju (yakju with google wallet (works in US only)).
can someone here help me?
batkinson001 said:
hey all, I noticed that jelly bean is out, sort of.
i would like to put it on my nexus but am sofar unable to make sense of the development forums pertaining to this so hopefully someone here can help me understand this.
I used the efrant's post:
http://forum.xda-developers.com/showthread.php?p=21113773#post21113773
to take my yakjuux nexus to yakju (4.0.4) using fastboot and the stock image provided from google...
I would like to upgrade further, though from what i can figure out JB is only available on takju (yakju with google wallet (works in US only)).
can someone here help me?
Click to expand...
Click to collapse
If you're running stock yakju you don't really need to switch to takju. Just install CWM (The Galaxy Nexus Toolkit is an awesome tool to help you do that) and flash this.
You can go from any rom (custom or stock) to jb as far as you have cwm and xxla2 radios..
Cheers
Sent from my Galaxy Nexus using xda premium
Camazza said:
If you're running stock yakju you don't really need to switch to takju. Just install CWM (The Galaxy Nexus Toolkit is an awesome tool to help you do that) and flash this.
Click to expand...
Click to collapse
got some troubleshooting to do... phone wont show up in fastboot... cant use the toolkit until i figure this out.
edit: reinstalled the naked universal driver... shows up in fastboot now.
Does this method wipe everything?
Camazza said:
If you're running stock yakju you don't really need to switch to takju. Just install CWM (The Galaxy Nexus Toolkit is an awesome tool to help you do that) and flash this.
Click to expand...
Click to collapse
i think it worked, used option 6 for my build of android, then selectedthe option to install cwm touch, followed the instructions in section 3 on:
http://forum.xda-developers.com/showthread.php?t=1614827
Hopefully this will fix the issue i was having with my nexus where the radio would lose all connection to the network... usually have to reboot the phone to get it to work again... a minor annoyance for an awesome phone. Atleast it doesn't take 3-5 min to boot up like my blackberry playbook tablet (that's not cool RIM, please fix)...
nipcarlover said:
Does this method wipe everything?
Click to expand...
Click to collapse
it didn't on my nexus... though i didn't use the 7th option which does steps 3-6 (unlock bootloader, root phone, flash recovery) which would wipe the phone.
I just hope i can still send messages on it, last time i flashed it i had to get telus to resend the info to the phone.
another question, I don't think I got the full JB os, as my phone is still using the xxla2 radio... if i wanted to go back to yakju for the full stock OTA update, supposedly coming next month sometime, and keep my warranty, I would just reflash everything back to yakju, including recovery (CWM - stock)?
I assume I would have to do this with the fastboot in the DOS window since I don't think that I can revert everything back to 4.0.4 with the toolkit.
also how do I tell if the phone is rooted? I don't think i did this but would like to know anyways.
batkinson001 said:
another question, I don't think I got the full JB os, as my phone is still using the xxla2 radio... if i wanted to go back to yakju for the full stock OTA update, supposedly coming next month sometime, and keep my warranty, I would just reflash everything back to yakju, including recovery (CWM - stock)?
I assume I would have to do this with the fastboot in the DOS window since I don't think that I can revert everything back to 4.0.4 with the toolkit.
also how do I tell if the phone is rooted? I don't think i did this but would like to know anyways.
Click to expand...
Click to collapse
Yes, for stock, use adb+fastboot and Nexus Factory Images for everything stock 100%. And to check for superuser, just download an app that requires it and see if you get a command prompt. But even easier than that, SuperUser or SuperSU should be in your app drawer if you have it installed, and also in your /system/app
anton2009 said:
Yes, for stock, use adb+fastboot and Nexus Factory Images for everything stock 100%. And to check for superuser, just download an app that requires it and see if you get a command prompt. But even easier than that, SuperUser or SuperSU should be in your app drawer if you have it installed, and also in your /system/app
Click to expand...
Click to collapse
I don't have those apps installed, guess I am not rooted. Good to know.
Also it should be noted that I no longer have any input lag using poweramp, with ICS 4.0.4 there was always a 1 second (seemed like it anyways) delay between the button press and the phone doing what I want. I hope this extends to using my bluetooth headset as well.
hmmm figured i would try downgrading to takju using the toolkit... it did everything which is nice however i noticed that it still uses the radio from yakju...
is there a way to check what it didn't add to the phone when it downgraded?
edit: I should add that it wiped my phone when I loaded takju...
looking forward to getting the official JB update next month...
batkinson001 said:
hmmm figured i would try downgrading to takju using the toolkit... it did everything which is nice however i noticed that it still uses the radio from yakju...
is there a way to check what it didn't add to the phone when it downgraded?
edit: I should add that it wiped my phone when I loaded takju...
looking forward to getting the official JB update next month...
Click to expand...
Click to collapse
I already had bootloader unlocked, so I just had to install CWM recovery and flash the jb-takju image mentioned earlier. Once the phone has rebooted the CWM was gone, so had to reflash that. Afterwards I downloaded the XLFF1 radios (you can search for radio-i9250-xxlf1.zip) and flashed them as well. Now my phone shows all the same versions as the takju phones passed out at Google I/O. All my settings, etc. were preserved.
dmapr said:
I already had bootloader unlocked, so I just had to install CWM recovery and flash the jb-takju image mentioned earlier. Once the phone has rebooted the CWM was gone, so had to reflash that. Afterwards I downloaded the XLFF1 radios (you can search for radio-i9250-xxlf1.zip) and flashed them as well. Now my phone shows all the same versions as the takju phones passed out at Google I/O. All my settings, etc. were preserved.
Click to expand...
Click to collapse
i really would like to remain stock but get JB as well, what would I need besides that radio to make the takju image from the google site to be prompted to dl the OTA JB update if it is still available to download from google...?
edit: screw that, found efrant's post:
http://forum.xda-developers.com/showpost.php?p=28178320&postcount=2
hopefully the jb-takju.zip linked earlier in this thread is the same as the one in efrants' post....
if not, is it possible to reflash with the newer zip without setting everything up again?
batkinson001 said:
i really would like to remain stock but get JB as well, what would I need besides that radio to make the takju image from the google site to be prompted to dl the OTA JB update if it is still available to download from google...?
edit: screw that, found efrant's post:
http://forum.xda-developers.com/showpost.php?p=28178320&postcount=2
hopefully the jb-takju.zip linked earlier in this thread is the same as the one in efrants' post....
if not, is it possible to reflash with the newer zip without setting everything up again?
Click to expand...
Click to collapse
The linked one produced the same build number (JRN84D) on my phone as the one on the phone that came from Google I/O, which is the same as the one in efrants' post.
dmapr said:
The linked one produced the same build number (JRN84D) on my phone as the one on the phone that came from Google I/O, which is the same as the one in efrants' post.
Click to expand...
Click to collapse
good to know, i compared the url's for both links, the one in efrant's post is missing the ) at the end. I ended up wiping the cache's (except for the one that sounds like some guys name) and flashed the zip from it. working great so far.
at the moment I am reinstalling my apps, and i do not think that all of the apps that were in the google folder last time i reinstalled the os, are there. anyone know what the default apps that are supposed to come with the OS are in that folder? I can only remember Layer which I installed manually...
batkinson001 said:
good to know, i compared the url's for both links, the one in efrant's post is missing the ) at the end. I ended up wiping the cache's (except for the one that sounds like some guys name) and flashed the zip from it. working great so far.
at the moment I am reinstalling my apps, and i do not think that all of the apps that were in the google folder last time i reinstalled the os, are there. anyone know what the default apps that are supposed to come with the OS are in that folder? I can only remember Layer which I installed manually...
Click to expand...
Click to collapse
Sorry, I didn't have to reinstall anything, so the apps in my Google folder are the same as before the update. I do however have Currents in the main app drawer which I don't remember having before.
Hey guys long time lurker here who needs some help,
First off, this is what I have on my phone:
Baseband: I747UCUEMJB
ROM: QuantumRom/QuantumKernel (Latest)
Philz Touch Recovery (slightly old)
Main Question: I want to completely wipe my phone (pretty much nuke it) and reset it all the way to where I still have a rooted phone and can put on a custom ROM. How do I go about doing this?
I want to do this because I may sell my phone later on down the road (approx. 2-3 months) and I want to clean out all the stuff I have, but I still want a phone that is rooted and able to sustain custom ROMs. I know this may seem like a noob question, but I want to make sure I do the process right and not lose my phone.
I'm not 100% sure but wiping data, cache, and Dalvik would pretty much wipe everything on your phone.
Alternatively, you could use Odin to flash a ROM.
The thing is, I wanna go back to pretty much stock with root. Like wipe the whole phone clean.
To go back to stock from MJB, you'll need to flash a stock ROM that has been compiled for flashing in Odin. Don't use any of the ROMs from sammobile.com.
This thread may help you out: http://forum.xda-developers.com/showthread.php?t=2722660
Wouldn't it brick my phone?
Wouldn't this brick my device though? I have the MJ2 Bootloader and I never updated OTA to 4.4 Samsung Stock. Reading through those posts gave me the feeling that the method stated would brick my device.
EDIT: Well I just hard-bricked.
UnknownTroll1 said:
Hey guys long time lurker here who needs some help,
First off, this is what I have on my phone:
Baseband: I747UCUEMJB
ROM: QuantumRom/QuantumKernel (Latest)
Philz Touch Recovery (slightly old)
Main Question: I want to completely wipe my phone (pretty much nuke it) and reset it all the way to where I still have a rooted phone and can put on a custom ROM. How do I go about doing this?
I want to do this because I may sell my phone later on down the road (approx. 2-3 months) and I want to clean out all the stuff I have, but I still want a phone that is rooted and able to sustain custom ROMs. I know this may seem like a noob question, but I want to make sure I do the process right and not lose my phone.
Click to expand...
Click to collapse
UnknownTroll1 said:
Wouldn't this brick my device though? I have the MJ2 Bootloader and I never updated OTA to 4.4 Samsung Stock. Reading through those posts gave me the feeling that the method stated would brick my device.
EDIT: Well I just hard-bricked.
Click to expand...
Click to collapse
Which bootloader did you have? The first post said MJB, the second said MJ2.
With the MJ2, I believe you could have flashed back to stock 4.1.1 and just run OTA updates until you hit 4.4.2.
MJ2 is the leaked bootloader: http://forum.xda-developers.com/showthread.php?t=2498233
I just converted my retail Note 4 to Dev Ed, but was wondering why I can't use stock kernel on a rooted stock Rom or even custom stock rom?
I tried installing the stock kernel from the official firmware thread and maybe misunderstood that it can be used on the dev edition, but maybe there is reason why?
The stock Retail Verizon Note 4 kernal doesn't support the unlocked bootloader so you need to install one that is compatible. The reason is because Verizon wants to charge you extra for a Developer Edition so they don't waste time and money putting support in for it.
To be honest the kernel that I flashed while unlocking device is much better . My battery life if finally back to normal I get approximately 5:30 screen on time while I used to get like 2:30-3
Why should Verizon pay for support if someone f's their phone up because they had no clue to what they were doing. If it was your company, you woukd be in it to make money and not lose it! Stop complaining about Verizon, you knew everything before you signed the contract and agreed to be a part of their services. That's just MHO of course.
Sent from my SM-N910V using Tapatalk
I don't know why everyone is saying the stock kernel & stock ROM won't work with the bootloader unlock, because they're working fine for me.
Running a rooted stock ROM with the stock kernel right now.
outcasted2003 said:
Why should Verizon pay for support if someone f's their phone up because they had no clue to what they were doing. If it was your company, you woukd be in it to make money and not lose it! Stop complaining about Verizon, you knew everything before you signed the contract and agreed to be a part of their services. That's just MHO of course.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
What does this have to do worth the thread or any of the replys?
Deleted.
anrichardson said:
It will work with unlocked bootloader and twrp but not worth root.
Click to expand...
Click to collapse
Did you mean not WITH root?
Because again, I'm rooted right now. No issues.
blindmanpb said:
Did you mean not WITH root?
Because again, I'm rooted right now. No issues.
Click to expand...
Click to collapse
I didn't read the post all the way before posting. Thats why I deleted it.
Every time I install stock kernel I get a bootloop on the verizon screen.
Yeah, I never had any issues with TWRP or root.
The only thing that I might have done differently than everyone else is that after achieving the bootloader unlock, I flashed a stripped down version of the stock firmware (boot, recovery, system, cache, and modem ONLY) to make sure I was 100% KingRoot free, then wiped cache and data.
Only issue I've run into on the stock ROM is that if you delete Facebook or Instagram it breaks screen rotation. Freezing them is fine, though.
EDIT:
Just realized I'm still sitting on build BOG5 / 5.0.1, that might be why. I think it's only people on BPA1 / 5.1.1 that are having issues with that.
anrichardson said:
I didn't read the post all the way before posting. Thats why I deleted it.
Every time I install stock kernel I get a bootloop on the verizon screen.
Click to expand...
Click to collapse
As stated above, it will not work at the kernel doesn't support unlocked bootloader. I had the same issue until I flashed a custom kernel.
My N4 performs well with this multi-system kernel Courtesy of @hsbadr:
Friend bought a used 5x from Swappa and it come with an unlocked bootloader, nbd. We flashed stock firmware and left it as is. He's happy.
Now that Android Pay/Safetynet is detecting his bootloader, he's not having any of it. Wants to lock the bootloader back up to restore AP functionality. I just want to confirm, 1.) this will wipe EVERYTHING on it, correct (I told him to get everything backed up)? And 2.), do I need to flash stock images before locking even though it's a bone stock 7.0 setup?
tallgrasshawk said:
Friend bought a used 5x from Swappa and it come with an unlocked bootloader, nbd. We flashed stock firmware and left it as is. He's happy.
Now that Android Pay/Safetynet is detecting his bootloader, he's not having any of it. Wants to lock the bootloader back up to restore AP functionality. I just want to confirm, 1.) this will wipe EVERYTHING on it, correct (I told him to get everything backed up)? And 2.), do I need to flash stock images before locking even though it's a bone stock 7.0 setup?
Click to expand...
Click to collapse
Never done it but to be safe I'd use a tool like this one.
http://forum.xda-developers.com/nex...olkit-skipsoft-android-toolkit-nexus-t3230444
tallgrasshawk said:
Friend bought a used 5x from Swappa and it come with an unlocked bootloader, nbd. We flashed stock firmware and left it as is. He's happy.
Now that Android Pay/Safetynet is detecting his bootloader, he's not having any of it. Wants to lock the bootloader back up to restore AP functionality. I just want to confirm, 1.) this will wipe EVERYTHING on it, correct (I told him to get everything backed up)? And 2.), do I need to flash stock images before locking even though it's a bone stock 7.0 setup?
Click to expand...
Click to collapse
There is a Heisenberg thread that will walk you thru it all. Download the image you want, factory reset while booted, auto reboot, bootloader, flash every file according to the thread, then fastboot OEM lock. Reboot and done. Don't lock until you flash every file.
Sent from my Nexus 5X using XDA-Developers mobile app
Im replacing my Pixel 6 Pro due to a bad accelerometer sensor. My phone is rooted with latest Magisk, has Kiri kernel installed as well. What's the most efficient way to prep the phone for a return to Google?
Official Google Android Flash Tool
and
Official Instructions for Locking/Unlocking the Bootloader
roirraW edor ehT said:
Official Google Android Flash Tool
and
Official Instructions for Locking/Unlocking the Bootloader
Click to expand...
Click to collapse
So just running the flash tool will remove root, reset to factory default and return kernel to stock? After that just lock the bootloader and good to go?
Starzboy77 said:
So just running the flash tool will remove root, reset to factory default and return kernel to stock? After that just lock the bootloader and good to go?
Click to expand...
Click to collapse
Yes. All of that.
Starzboy77 said:
So just running the flash tool will remove root, reset to factory default and return kernel to stock? After that just lock the bootloader and good to go?
Click to expand...
Click to collapse
If you like, for further explanation, flashing the 100% official stock ROM will both remove root and overwrite whatever kernel you currently have with the stock kernel that's included in the stock ROM. If you choose any option anywhere (on that official stock flashing site of Google's, or via any other method) to *not* factory reset the phone, sure you'd have any root-oriented apps still installed on your phone, but the phone wouldn't be rooted because the stock kernel is 100% official now.
There are many ways to do the same thing, but this is the safest and 100% sure method that it's all stock. i.e. my answering this way isn't dependent on anything you've possibly done to your phone - if you or someone had gone out of the way to modify the software of the phone even more than typically, this method would still completely overwrite any changes you've done, because you're flashing the completely stock ROM.
I haven't used the Official Google Android Flash Tool but countless others in this section alone have reported their situations on their phones being saved by this method - even when flashing the stock ROM in only a slightly more manual way via the official Platform Tools had failed to solve their issues: manually downloading the stock firmware, extracting it, and running the flash-all.bat file included (if on Windows). Since I haven't used it myself, I'm just going by memory of what others have reported about using it and I'm under the impression that it gives you the choice to wipe (factory reset) or not wipe your phone when it flashes it.
I wouldn't be surprised if by default it wipes, as that's what the flash-all.bat script from the manual full factory image zip file does by default.
Also, heads up. You never want to lock the bootloader unless you are 100% certain the phone is 100% stock. Ergo, why even though there are other methods to unroot and "return to stock", there is no good reason to use them unless you just don't have access to a computer, or a cable, or it's some kind of unroot emergency or some other circumstance that calls for more manual methods - which also leave a greater chance for accidental human error and can just plain brick your phone - although that might not matter since you're returning the phone.
roirraW edor ehT said:
If you like, for further explanation, flashing the 100% official stock ROM will both remove root and overwrite whatever kernel you currently have with the stock kernel that's included in the stock ROM. If you choose any option anywhere (on that official stock flashing site of Google's, or via any other method) to *not* factory reset the phone, sure you'd have any root-oriented apps still installed on your phone, but the phone wouldn't be rooted because the stock kernel is 100% official now.
There are many ways to do the same thing, but this is the safest and 100% sure method that it's all stock. i.e. my answering this way isn't dependent on anything you've possibly done to your phone - if you or someone had gone out of the way to modify the software of the phone even more than typically, this method would still completely overwrite any changes you've done, because you're flashing the completely stock ROM.
I haven't used the Official Google Android Flash Tool but countless others in this section alone have reported their situations on their phones being saved by this method - even when flashing the stock ROM in only a slightly more manual way via the official Platform Tools had failed to solve their issues: manually downloading the stock firmware, extracting it, and running the flash-all.bat file included (if on Windows). Since I haven't used it myself, I'm just going by memory of what others have reported about using it and I'm under the impression that it gives you the choice to wipe (factory reset) or not wipe your phone when it flashes it.
I wouldn't be surprised if by default it wipes, as that's what the flash-all.bat script from the manual full factory image zip file does by default.
Also, heads up. You never want to lock the bootloader unless you are 100% certain the phone is 100% stock. Ergo, why even though there are other methods to unroot and "return to stock", there is no good reason to use them unless you just don't have access to a computer, or a cable, or it's some kind of unroot emergency or some other circumstance that calls for more manual methods - which also leave a greater chance for accidental human error and can just plain brick your phone - although that might not matter since you're returning the phone.
Click to expand...
Click to collapse
Thank you for the indepth explanation. Really appreciate it.
Just factory reset it so your data is wiped and send it back. Google has never cared about them being rooted when you return them.
TonikJDK said:
Just factory reset it so your data is wiped and send it back. Google has never cared about them being rooted when you return them.
Click to expand...
Click to collapse
Is this accurate? Can anyone else confirm? What about having a different kernel? Does the bootloader have to be locked?
Starzboy77 said:
Is this accurate? Can anyone else confirm? What about having a different kernel? Does the bootloader have to be locked?
Click to expand...
Click to collapse
As I said, you should not lock the bootloader unless the phone is 100% stock. To me, it doesn't matter what anyone else says about what Google cares about. If it were my phone, I'd restore it 100% stock too. 10 minutes of very little effort for some peace of mind. Rather than meh, they might not care, or meh you might be the unlucky exception. Why take the chance?
But it's your phone, your decision. No one else makes the decision for you.
roirraW edor ehT said:
As I said, you should not lock the bootloader unless the phone is 100% stock. To me, it doesn't matter what anyone else says about what Google cares about. If it were my phone, I'd restore it 100% stock too. 10 minutes of very little effort for some peace of mind. Rather than meh, they might not care, or meh you might be the unlucky exception. Why take the chance?
But it's your phone, your decision. No one else makes the decision for you.
Click to expand...
Click to collapse
This to the millionth degree. and it also goes for when purchasing a used device or a refurbished device. Reflash Android. they make it so simple now that it can be done using another phone. No PC necessary.
Flash Tool changed the game 3 years ago for how easy the process is. Heck I just reflash my phone monthly because it's such great technology (kidding, not kidding?)