Related
What would be the difference between these 2 methods of rooting for XPERIA Arc?
I know Gingerbreak is much easier to do than the other one. But, is there any limitations to what Gingerbreak can do compared with the other method ?
Since bootloader is still in locked state, that means those who did it with Gingerbreak still have their warranty valid, right? What about the installation of future custom ROM ? Would the devices rooted with Gingerbreak have no chance to install custom ROM because the bootloader is locked ?
Sorry, I'm pretty much confused atm about rooting the Arc.
My understanding is unlocking the bootloader does not give you root. Even those with unlocked bootloaders must root using either ginger break or the other method.
Having the bootloader unlocked will allow for installing custom roms though, when recovery is sorted. Those of us with locked bootloaders will have to hope for a workaround at a later date.
As for warranties...who knows on this one. SE have allowed the unlocking of bootloaders saying it "may" void warranty. Theres nothing to say rooting will void it. Personally I think the only way you will void it is if you brick it whilst fiddling with it. I think any hardware issues will be sorted regardless. (but thats my opinion, dont take it as gospel)
Rooting is rooting, it doesn't really matter what the mechanics of it are, if it's successful then the outcome is the same.
As for the two methods, yes, GingerBreak seems to be the simplest so for most people there's really no reason not to do that. If it fails and you have a handset you can unlock the bootloader on, then you can always do it the other way if need be.
When it comes to custom ROMs, there's a good chance that having an unlocked bootloader will be a requirement, to begin with at least.
It's possible that someone will find a way to offer custom ROMs for locked bootloaders but it's just more work.
if the buutloader remains unlocked your phone can ALWAYS be repaired through seus, the bootloader needs to be unlocked for the phone to be bricked . also flashing of custom roms may not require the bootloader to be unlocked - as is the case with the x10. as far as i know though the bootloader needs to be unlocked to flash new kernals but there is a workaround that for the time being with the ability to flash the various basebands. my bootloader will remain locked for the timebeing - its a sure failsafe if anything goes wrong
Thanks for the replies everyone.
I had this concept of "If you don't root your phone, you can't install custom ROM" and "If your bootloader is locked, you can't install custom ROM" before I found this Gingerbreak rooting method. (i.e. boot loader unlock -> can root -> can install custom ROM)
But just before it was conflicting because with Gingerbreak root your phone, but it seemed to me that you can't install custom ROM because the bootloader is locked. However they said "If you root your phone you can install custom ROM".
So for this time being, taking out the question whether custom ROM (which no one yet to make it for Arc) can be installed, I think it's safe to say : "Gingerbreak rooting with busybox installed gives you the same capabilities to bootloader unlocking + fastboot flashing", right?
more or less......
x10 was never unlocked bootloader,how many custom ROM out there?
cheers
Sent from my LT15i using XDA Premium App
ArcOnFire said:
"Gingerbreak rooting with busybox installed gives you the same capabilities to bootloader unlocking + fastboot flashing", right?
Click to expand...
Click to collapse
Not exactly. You can't flash custom .imgs via fastboot if you don't unlock the bootloader.
And I don't understand why people think that phone can be totally bricked if you unlock the bootloader...
sorry to say that,unlock bootloader seems waste of wait of time,if gingerbreak works
Sent from my LT15i using XDA Premium App
blagus said:
Not exactly. You can't flash custom .imgs via fastboot if you don't unlock the bootloader.
Click to expand...
Click to collapse
Well... yes, I already thrown that factor out when I asked my question.
But looking at the history, is there any case a custom ROM can be installed on a phone with bootloader still in locked state?
This is AFAIK
SE uses locked bootloaders for three reasons
1- A secure place to put DRM certificates.
2- A secure place to SIM lock the phone
3- A secure way to forbid modifying the software, as the bootloader will require a signed software in order for it to boot it ( If I'm not mistaken this is the problem with X10 unlockable bootloader as it's just hard to sign an image, correct me if I'm wrong ). the signed software thing is meant to be for not bringing bad software that may damage the phone
After SE saw that a lot of peoples want to install custom ROM's into their phones without too much hassle and a lot of them understand the risks of this so they decided to make it possible to unlock the bootloader but they want it to be the right way...
1- First the DRM certificates will be deleted as installing custom ROM's with exposed DRM certificates can bring serious legal problems to SE ( as this will mean the ability to save a digital unprotected copy of a DRM protected media )
2- SIM locked phones are excluded from this bootloader unlocking as this can make it easy to unlock the SIM lock so this will put SE in a bad position between operators..
3- As the main reason for unlocking the bootloader is installing custom ROM's and this is what the community want's SE made a bold statement here that doing so will violate the warranty as SE can't guarantee what a custom ROM may do to the phone...
but x10 has recovery
Sent from my LT15i using XDA App
The Arc isn't the X10.
Boring. This is a first time i use SE phone. I think this is also a last time. I will come back with HTC. There are no custom and no one with cook custom rom for SE device already
justbenice said:
Boring. This is a first time i use SE phone. I think this is also a last time. I will come back with HTC. There are no custom and no one with cook custom rom for SE device already
Click to expand...
Click to collapse
How many time passed from exit of ARC???
justbenice said:
Boring. This is a first time i use SE phone. I think this is also a last time. I will come back with HTC. There are no custom and no one with cook custom rom for SE device already
Click to expand...
Click to collapse
sorry ... I have from only 3 weeks the Arc and already have bootloader unlocked and Root ...
I think you're just a little patience
From what I gather, they can't refuse a warantee repair if it is a hardware fault, not caused by the unlocked software (as it is a problem with their manufacturing, and therefore their fault), but if you mess your phone up with something due to the unlocked bootloader they can (for example, you overheat your CPU with an overclock or something).
chriscpritchard said:
From what I gather, they can't refuse a warantee repair if it is a hardware fault, not caused by the unlocked software (as it is a problem with their manufacturing, and therefore their fault), but if you mess your phone up with something due to the unlocked bootloader they can (for example, you overheat your CPU with an overclock or something).
Click to expand...
Click to collapse
That's what I heard too. As long as you didn't mess with you phone in some way, they can't prove that the hardware fault came from the modified software and should therefore repair your phone nonetheless. I guess that's why they say that unlocking the bootloader MAY void one's warranty.
have rooted thro' gingerbreak - but am am getting frequent random reboots. while calling or recieving. can anyone help me with this.
I had to submit an RMA to get a new device and return this one. I haven't unlocked/rooted yet, and don't want to return it with an unlocked bootloader.
Will I be able to "fastboot oem unlock" then get Root on the device (WITHOUT CWM), backup with Titanium, then "fastboot oem lock"
Can I get root on the device without putting CWM on there?
Unlocking the bootloader wipes the data partition, including the virtual SD
And AFAIK, there's no way to root without unlocking the bootloader for the N4
Your best bet would be ADB backup I think
http://www.thesuperusersguide.com/adb-backup--restore.html
Ah, ADB Backup - that's a new one to me. Thank you!
Given his original question, will relocking leave any traces? I.E. can it go back for warranty if it's been previously unlocked?
Fmstrat said:
Given his original question, will relocking leave any traces? I.E. can it go back for warranty if it's been previously unlocked?
Click to expand...
Click to collapse
Even if it did leave any traces, I doubt you would ever have an issue from it. I've warranty returned a few rooted/unlocked phones including a Galaxy Nexus and a Nexus One and never had an issue with the warranty. Hell, I even sent one Nexus One back to Google still fully rooted and unlocked and never heard anything.
adb backup works well for me. I don't even need root anymore actually! When I upgraded from my stock gnex, I just backed up the few apps that I wanted to preserve data and restored it directly to the N4.
Through the many android devices I've owned, I've gone from flashing roms/modems every other day to leaving the device absolutely stock! With that thought, why am I still on XDA?
New Nexus 7 wifi. I've unlocked bootloader, rooted, new recovery, new 4.2.2 ROM.
I notice on some of the toolkits I'm able to re-lock bootloader. Assuming I'm not returning it to stock, is there any advantage to doing this?
harry_fine said:
New Nexus 7 wifi. I've unlocked bootloader, rooted, new recovery, new 4.2.2 ROM.
I notice on some of the toolkits I'm able to re-lock bootloader. Assuming I'm not returning it to stock, is there any advantage to doing this?
Click to expand...
Click to collapse
Any advantage to relocking it I would say no.. I believe I remember reading (and i could be totally wrong here) that there is a counter that gets changed when you unlock it.. I would guess so they could deny you warranty if they wanted even if you flashed back to stock and relocked it they would know. But I unlocked mine 15 minutes after opening it up and flashed TWRP with fastboot then installed a new rom and faux kernel and relocked mine just to see if it wouldn't run the non stock recovery or a non stock rom and kernel.. it still did. I leave it unlocked.. im thinking the whole locking thing is just a warranty scare tactic
And if you relock the bootloader, you won't be able to use fastboot anymore...
Nico_60 said:
And if you relock the bootloader, you won't be able to use fastboot anymore...
Click to expand...
Click to collapse
Extremely untrue. You can use fastboot all day long to flash stock roms, recoveries and such with a locked bootloader. That is the entire purpose of fastboot. You just cant flash custom recoveries, custom roms and such. Fastboot itself it completely intact and useable. It is the Nexus stock flashing tool. That is how you UNLOCK the bootloader in the first place. Even if you use a toolkit, it is merely a gui that is still utilizing fastboot for you in the background.
Sent from my Nexus 7 using xda premium
rebel1699 said:
Extremely untrue. You can use fastboot all day long to flash stock roms, recoveries and such with a locked bootloader. That is the entire purpose of fastboot. You just cant flash custom recoveries, custom roms and such. Fastboot itself it completely intact and useable. It is the Nexus stock flashing tool. That is how you UNLOCK the bootloader in the first place. Even if you use a toolkit, it is merely a gui that is still utilizing fastboot for you in the background.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
sorry, it's true I have not precised this
DaMadOne said:
Any advantage to relocking it I would say no.. I believe I remember reading (and i could be totally wrong here) that there is a counter that gets changed when you unlock it.. I would guess so they could deny you warranty if they wanted even if you flashed back to stock and relocked it they would know. But I unlocked mine 15 minutes after opening it up and flashed TWRP with fastboot then installed a new rom and faux kernel and relocked mine just to see if it wouldn't run the non stock recovery or a non stock rom and kernel.. it still did. I leave it unlocked.. im thinking the whole locking thing is just a warranty scare tactic
Click to expand...
Click to collapse
Same, I unlocked mine the moment I got it. Also the lock isn't really a warranty scare tactic but rather a security feature, with it locked (which can only be unlocked via fastboot anyways) would prevent the system from replacing the components such as system, recovery or bootloader that wasn't officially signed.
It's also a way for warranty to only be applied to software or components that they are actually responsible for, since damage caused by something they don't make wouldn't be covered anyways.
Also even if you did have it unlocked, and the device was suffering from a hardware-based manufacture defect, it would still be covered under warranty, even if they deny you at first, would just have to push the nature of the defect. (And besides, far as Nexus devices go, would seem as if they were sold to be tinkered with).
rebel1699 said:
Extremely untrue. You can use fastboot all day long to flash stock roms, recoveries and such with a locked bootloader. That is the entire purpose of fastboot. You just cant flash custom recoveries, custom roms and such. Fastboot itself it completely intact and useable. It is the Nexus stock flashing tool. That is how you UNLOCK the bootloader in the first place. Even if you use a toolkit, it is merely a gui that is still utilizing fastboot for you in the background.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
what about Locking Bootloader on MultiROM ?!?!?!
Hi There,
My colleague complained that he had an OTA update on his Nexus 6P and the after the update it was stuck in a boot loop where the Google logo keep on displaying.
When he bought back, he had showed it a shop already which they said they couldn't fix. However, the phone was later given to me for help and I have somehow manage to connect the device on fastboot and adb. Tried all the possible options such as unlocking the bootloader, loading .img's one by one... sideloading... etc.
No matter what I do, it keeps on doing the same boot loop. And when I leave the bootloader unlocked, it gives an error at first, then again goes back to the same.
Not sure whether what I am doing wrong or whether am I choosing the wrong build or so... would anyone care to advise?
.G33K said:
Hi There,
My colleague complained that he had an OTA update on his Nexus 6P and the after the update it was stuck in a boot loop where the Google logo keep on displaying.
When he bought back, he had showed it a shop already which they said they couldn't fix. However, the phone was later given to me for help and I have somehow manage to connect the device on fastboot and adb. Tried all the possible options such as unlocking the bootloader, loading .img's one by one... sideloading... etc.
No matter what I do, it keeps on doing the same boot loop. And when I leave the bootloader unlocked, it gives an error at first, then again goes back to the same.
Not sure whether what I am doing wrong or whether am I choosing the wrong build or so... would anyone care to advise?
Click to expand...
Click to collapse
So the bootloader is unlocked? Exactly which build have you attempted to flash with fastboot? Have you tried flashing one of the full OTA zips with the stock recovery?
PS. Whatever you do don't lock the bootloader. And don't worry about the warning you get with the bootloader unlocked, that's normal.
Heisenberg said:
So the bootloader is unlocked? Exactly which build have you attempted to flash with fastboot? Have you tried flashing one of the full OTA zips with the stock recovery?
PS. Whatever you do don't lock the bootloader. And don't worry about the warning you get with the bootloader unlocked, that's normal.
Click to expand...
Click to collapse
Thank you for the reply.. I have only locked the bootloader when I'm done with flashing... etc as it was giving me error. Regardless of the bootloader state, it kept on going through the bootloop like it didn't care.
I tried to flashing the factory image which is MTC19T and also tried the OTA which is MTC19V as said in here.
Still there's not luck!
.G33K said:
Thank you for the reply.. I have only locked the bootloader when I'm done with flashing... etc as it was giving me error. Regardless of the bootloader state, it kept on going through the bootloop like it didn't care.
I tried to flashing the factory image which is MTC19T and also tried the OTA which is MTC19V as said in here.
Still there's not luck!
Click to expand...
Click to collapse
Don't worry about the warning and definitely don't lock the bootloader because if it gets stuck locked you'll really be screwed. Go to my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 10 (use the latest MTC19X build). Skip the part at the beginning about performing a factory reset because you can't actually get the phone to boot to do that. Make sure you include the "fastboot format userdata" command at the end (this will erase all data on the device). Leave the bootloader unlocked.
Heisenberg said:
Don't worry about the warning and definitely don't lock the bootloader because if it gets stuck locked you'll really be screwed. Go to my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 10 (use the latest MTC19X build). Skip the part at the beginning about performing a factory reset because you can't actually get the phone to boot to do that. Make sure you include the "fastboot format userdata" command at the end (this will erase all data on the device). Leave the bootloader unlocked.
Click to expand...
Click to collapse
I have actually tried doing what section 10 says but with a different stock build.. Does that effect as well? However, let me give another shot with your said build and post back.
.G33K said:
I have actually tried doing what section 10 says but with a different stock build.. Does that effect as well? However, let me give another shot with your said build and post back.
Click to expand...
Click to collapse
Did you format userdata? It's worth a try.
Heisenberg said:
Did you format userdata? It's worth a try.
Click to expand...
Click to collapse
Yes, sire! I did all the possible things I could do without harming or bricking the device... Read each and every instruction carefully to do... but turned with no luck... however, I'm due to try the method and build you have suggested, I shall try that and get back to you!
.G33K said:
Yes, sire! I did all the possible things I could do without harming or bricking the device... Read each and every instruction carefully to do... but turned with no luck... however, I'm due to try the method and build you have suggested, I shall try that and get back to you!
Click to expand...
Click to collapse
It probably won't work, any build should work, but it's worth a try. If that fails I can only suggest flashing TWRP recovery and trying to flash a custom ROM to see if that works.
So long as you have the bootloader.img and radio.img files, you can try to format boot as well, however Heisenberg may yell at me for even typing that
I had a similar issue - bootloop, but it was getting to the boot animation for about 3 seconds, then rebooting. When I formatted all the areas before flashing them from the stock image, it allowed me to boot up as normal. Stable ever since.
Hi There,
Coming back to the issue, I have just downloaded the build that was suggested by "Heisenberg" and tried it. It was still the same, as in the Google logo keep on flashing but the android bot just appeared once with the logo. But still there not luck as the device stays with Google logo but does nothing.
However, I'm able to see the device on fastboot. Nevertheless, I cannot seem to use adb command.. it doesn't even list on devices. Does that mean the adb isn't working?
Meanwhile, all my fastboot commands are working with no issues at all.
EDIT: When I tried the TWRP recovery, I can flash the recover, but I can seem to go to the recovery window at all as the device keep on showing "The device software can't be checked for corruption". When I pass that also the same boot loop.
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
bcjk8210 said:
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
Click to expand...
Click to collapse
Unfortunately yes. Unless you enabled OEM Unlocking in the developers menu before your phone went sideways you probably have a hard bricked phone. Is it under warranty?
I went through this in November with a completely stock Nexus 6P. I was 3 days past my one year warranty! Google would not send me a new phone. It was completely bricked by the OTA update I received! I was put in touch with Huawei. I had to send the bricked phone to them. 10 days later I received a working model back. Unacceptable that an OTA update trashes a one year old $650 phone. Luckily I had my OnePlus One still, and was able to use that while I waited. I was even able to update that to 7.1.1 since it was rooted. Obviously there is some sort of issue that we are not being told of regarding the dangers of accepting OTA updates on a stock/bootlocked phone.
TemplesOfSyrinx said:
I went through this in November with a completely stock Nexus 6P. I was 3 days past my one year warranty! Google would not send me a new phone. It was completely bricked by the OTA update I received! I was put in touch with Huawei. I had to send the bricked phone to them. 10 days later I received a working model back. Unacceptable that an OTA update trashes a one year old $650 phone. Luckily I had my OnePlus One still, and was able to use that while I waited. I was even able to update that to 7.1.1 since it was rooted. Obviously there is some sort of issue that we are not being told of regarding the dangers of accepting OTA updates on a stock/bootlocked phone.
Click to expand...
Click to collapse
Bootloop issues are common on the 6P even with custom ROMs--it just happens to be much more likely you can recover with the custom ROMs installed since the bootloader is unlocked. I think it's a hardware issue with the 6P rather than an OTA issue. It's probably not an accident that Huawei didn't make the Pixels.
Doesn't seem right that I have to "void" my warranty and install a custom ROM on an unlocked, rooted phone in order to recover from a hardware defect. That's BS pure and simple. I want to use the latest software, that's why I bought a Nexus. I want to use all the conveniences like Android Pay. That's why I don't unlock or root anymore. I rooted every Android phone I ever had until now, starting with the original Motorola Droid. Now that security is so important to Google, and you can't use all the Android features with an unlocked bootloader, they need to step up to fix these problems.
This happened to my wife's phone, sent back to Bell. Will see what happens.
TemplesOfSyrinx said:
Doesn't seem right that I have to "void" my warranty and install a custom ROM on an unlocked, rooted phone in order to recover from a hardware defect. That's BS pure and simple. I want to use the latest software, that's why I bought a Nexus. I want to use all the conveniences like Android Pay. That's why I don't unlock or root anymore. I rooted every Android phone I ever had until now, starting with the original Motorola Droid. Now that security is so important to Google, and you can't use all the Android features with an unlocked bootloader, they need to step up to fix these problems.
Click to expand...
Click to collapse
Unlocking the bootloader doesn't void the warranty on the Nexus 6P. If you are under warranty then just RMA the phone if an OTA bootloops your phone. It's your choice whether to keep the bootloader locked or not but if you keep the bootloader locked it's probably impossible to recover from a bootloop. Google keeps factory images for Nexus and Pixel phones on its website but you can't flash those images with a locked bootloader. Why would they provide the images if using them voided your warranty?
You are missing my point. If I unlock my bootloader so I can recover from a boot loop that may happen, I will no longer be able to use a huge feature of the phone. Android Pay will no longer function. In days passed the rumour was your warranty was void if you unlock. I assume that was started to keep people from doing it. All I know is I paid good money for a phone that is a disaster waiting to happen it seems.
If having an unlocked bootloader is so important to recover from a bricked phone, why do they lock it in the first place? And why won't Android Pay work with it unlocked? The answer is that you no longer have a secure phone if you unlock the bootloader.
bcjk8210 said:
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
Click to expand...
Click to collapse
What Android version you had on your phone? What's your emmc name and ram name in bootloader? What's the manufacturing date in bootloader?
TemplesOfSyrinx said:
You are missing my point. If I unlock my bootloader so I can recover from a boot loop that may happen, I will no longer be able to use a huge feature of the phone. Android Pay will no longer function. In days passed the rumour was your warranty was void if you unlock. I assume that was started to keep people from doing it. All I know is I paid good money for a phone that is a disaster waiting to happen it seems.
If having an unlocked bootloader is so important to recover from a bricked phone, why do they lock it in the first place? And why won't Android Pay work with it unlocked? The answer is that you no longer have a secure phone if you unlock the bootloader.
Click to expand...
Click to collapse
I think you bought the wrong phone. Nexus devices were never available commercially through carriers and were made for developers and people who like to flash things with their phones. There are ways to use Android Pay with an unlocked bootloader if you are so inclined. You are right that an unlocked bootloader is considered less secure but if you only install apps from Google Play or another trusted source you shouldn't have problems. You can also simply enable allow Oem Unlock in the developer menu. This doesn't actually unlock your bootloader but makes it possible for you to unlock it via fastboot if you get bootlooped and need to flash a factory image to restore. This way you can unlock the bootloader in an emergency but your phone is still secure. I think this should be enabled by default when the phones are shipped. Too many people with locked bootloaders end up with hard bricked phones where the Nexus 6P is concerned. Honestly, you would probably be better off selling your Nexus and getting something else that's more stable and made for people who have no Interest in flashing anything.
My old Moto G5 Plus suddenly shutdown and was stuck in a bootloop after an update install (not sure if that caused it), is there a risk that the same thing will happen if I update to 93? I RMAd my old phone and Motorola sent me a completely new one after 3 days. My old phone didn't have OEM unlocked so I couldn't even unlock its bootloader, so my only choice was to send it back to Motorola.
Would it be a better option to unlock bootloader, root and install twrp instead? If the same thing happens to my new phone, since I have it rooted and all I can flash new ROMs and firmware so it works again, right? Is it not worth it to void my warranty?
cidlc said:
My old Moto G5 Plus suddenly shutdown and was stuck in a bootloop after an update install (not sure if that caused it), is there a risk that the same thing will happen if I update to 93? I RMAd my old phone and Motorola sent me a completely new one after 3 days. My old phone didn't have OEM unlocked so I couldn't even unlock its bootloader, so my only choice was to send it back to Motorola.
Would it be a better option to unlock bootloader, root and install twrp instead? If the same thing happens to my new phone, since I have it rooted and all I can flash new ROMs and firmware so it works again, right? Is it not worth it to void my warranty?
Click to expand...
Click to collapse
Should you take the update? Yes, there is no reason not to.
Is there a risk it could brick in the process? Yes, but honestly if your device is stock that risk is minimal
Would it be a better option to unlock bootloader, root and install twrp instead? No, it will void your warranty
The question is, what do you want in the end, a stock device with a warranty or a modified device without one? If you want a modified device without a warranty, go for it. If you want a stock device with one, although I understand your hesitation due to previous issues, go ahead and take the OTA, worst case scenario Moto will replace it again, although you are unlikely to have issues.
You do have the option to make that decision later... Enable Developer Options and go into it and enable OEM Unlocking but DO NOT actually unlock the bootloader, then take the upgrade. If it succeeds, just turn off OEM Unlocking, if it fails you have option to try something to recover it. Be aware if actually unlock the bootloader the warranty is gone, so if on the off-chance it does fail don't panic and try to think clearly.