Hi!
I always root devices when I can but i have got two questions, I understand that you loose DRM keys upon unlocking the bootloader, what is the side effects of this?
Also if I use the Flash Tool to flash the latest stock firmware will it be delayed compared to an OTA update or will the firmware be released at the same time as ota?
Thanks!
Follow this thread: https://forum.xda-developers.com/xa1/development/xperia-xa1-plus-stock-kernel-advanced-t3729856
Related
I got my new Xperia Arc today, ive rooted it and unlocked the bootloader but now whenever i try and update it bricks the phone.
Im on 2.3.2 and the irst thing I did was unlock the bootloader via fastboot, then used gingerbreak to root the phone, i then tried an ota update which bricked the phone.
I used Flashtool FOTAUnbrick, this got the phone working again, so I tried again, I flashed the generic UK 2.3.2 which worked fine, re-rooted and tried an OTA Update again and rebricked do used the FOTAUnlock again, working again, tried the PC Companion which said there was modified software and that it couldn't update.
So its not possible for me to use the phone companion and its not possible or me to use the OTA how do I get my phone onto 2.3.3 as the 2 official ways i've tried are bricking my phone
Any idea
Well there is a topic about this problem in the development forum:
http://forum.xda-developers.com/showthread.php?t=1126358
The idea is that when you unlock the bootloader you can't use OTA updates or pc companion updates to update your phone because you will brick it. In fact it should not even be possible to get the OTA update but this is bug at SE.
If you want to get the update there is 2 possibilities. First is to relock the bootloader and update either through OTA or through PC companion. Second is to just flash generic or rooted official image using fastboot. Here is the latest official firmware for the second method:
http://forum.xda-developers.com/showthread.php?t=1202441
So even though the thread says its for the neo this is actually for arc, right well ill give it a flash now see what the end damage is
Sorry this is for Neo. I gave a link for Neo by mistake because i have Neo. You should use one for Arc.
Hey guys
I was having the battery drain issue mentioned by siddharthsai R800i 4.0.A.2.368 as i used the pc companion update method
i've now downgraded to
R800i_3.0.1.A.0.145 (OLD firmware) using flashtool
My plan is now to OTA from R800i_3.0.1.A.0.145 to a newer firmware
siddharthsai said the battery drain issue is not evident through OTA only through pc companion.
I brought the r800i unbranded, it has a unlocked bootloader already from the factory, i've never ROOTED or touched the BOOTLOADER !
will i be able to OTA to newer firmware, I'm worried by using flashtool to flash firmwares will the OTA brick my phone because of this.
thanks in advance
harlzden
Afaik there's no plays that comes bootloader unlocked from factory, it would conflict with warranty. SE says unlocking might void the warranty, but to send out devices that might not fall under warranty would be very odd.
I don't think the newest FW is available through OTA yet (2.3.4).
You should be good to go with an OTA update if you bought it from new (not used) and never unlocked the bootlader. A rooted phone won't brick updating OTA nor will it any other way of updating (Pc Companion/SEUS/flashtool). Rooting and then removing/freezing/modding bloat/system aps can cause it not to be able to update OTA.
Regards Dousan...
I did exactly what you are asking and my phone is working like a charm,while you're at it,root your phone with gingerbreak(that's why I did this).
Btw your issue might be fixed since OTA and PC Companion updates are a little bit diffrent,so might be that SE overlooked a bug
Hi,
I got a Gnex from Singapore singtel.
I didn't want to wait for OTA to 4.1.1 so I rooted and flashed JB 4.1.1
I am running the stock rom from google..
Now that 4.1.2 is released and lot of people seem to have got the OTA, I am yet to get my OTA ...
I am wondering if it is because of the Unlocking and rooting done to my device...
Does Unlocking bootloader and Rooting the device stop OTA update to 4.1.2?
Also pls tell me if you have got your OTA yet or not ...
[email protected]$#eR said:
Hi,
I got a Gnex from Singapore singtel.
I didn't want to wait for OTA to 4.1.1 so I rooted and flashed JB 4.1.1
I am running the stock rom from google..
Click to expand...
Click to collapse
If you're running the stock ROM images from Google, then you didn't have to root. All you did was unlock the bootloader to flash those. If you rooted after, that was completely unnecessary to the process of switching.
(Sorry just a little pet peeve. People apparently have trouble grasping the difference between rooting and unlocking a bootloader, and the difference between a custom ROM and an official Google factory image.)
Now that 4.1.2 is released and lot of people seem to have got the OTA, I am yet to get my OTA ...
I am wondering if it is because of the Unlocking and rooting done to my device...
Does Unlocking bootloader and Rooting the device stop OTA update to 4.1.2?
Click to expand...
Click to collapse
NO. Unlocking your bootloader and rooting does not at all stop your device from notifying you that an OTA is ready to download and install. I don't know how many times this has to be posted in these forums before people understand...
Unlocked bootloader does nothing to the OTA process.
Rooting on its own does nothing to the OTA process. If you've kept a custom recovery, the OTA will not install automatically. The custom recovery does give you the option to flash it manually if you'd like, and keep the custom recovery. If you've changed/removed any system files or flashed a different radio, that will prevent the OTA from applying both automatically and manually. If you've started to modify the device this much, you shouldn't be expecting OTAs to work (this is where a lot of "status 7" errors occur).
If you've rooted and returned to a stock recovery, you can let the OTA automatically install, but you will lose root. It takes ~5min to root again, no big deal. You can also try one of the popular apps that "saves" root while you OTA, like OTA Rootkeeper.
Also pls tell me if you have got your OTA yet or not ...
Click to expand...
Click to collapse
Just because a couple dozen people on a forum have gotten the OTA doesn't mean that you should have gotten it already. Its a tad frustrating, but the OTA has a staggered roll out. It doesn't depend on your location or carrier (assuming you've got takju or yakju firmware from Google), and will get to all devices eventually.
If you'd simply point your browser to the general forum, you'll already see several threads talking about the 4.1.2 update.
Got my OTA update
I got my OTA update yesternight ...
Hello community,
I got a Note 4 N910V and the jump was something incredible. I am in love with the thing.
My note 2 was rooted and had the Resurrection Remix rom. I felt free to customize it since I didn't have to worry about the bootloader or anything but it was really sluggish.
My note 4 came with 5.0.1(stock rom) and skiming through the forums I'm seeing things like 'safely upgrade to MM'. Makes me thing the OTA update ain't working right for everyone.
I'm not getting any OTA updates, could be because I'm not in the US and my phone is unlocked for a local telco.
I have a couple of questions
- Is the MM update fine? Battery, performance, root? how would I update if I'm not getting any OTA updates?
- I know about kingroot but is it recommended as the root option for my OS version. I found this but It's been a long time since I rooted a phone.
- Any popular ROM/Mods? RR was a big thing in the note 2 community (also a couple of custom kernels).
Pics of what I got down below.
Thank you for your time.
I'm using this phone on Bell Mobility in Canada and was unable to get the OTA. I have no intention of rooting this phone yet.
I was able to get the stock 6.0.1 OTA file from here:
http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
I was able to update using the stock recovery without issue....
crutzulee said:
I'm using this phone on Bell Mobility in Canada and was unable to get the OTA. I have no intention of rooting this phone yet.
I was able to get the stock 6.0.1 OTA file from here:
http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
I was able to update using the stock recovery without issue....
Click to expand...
Click to collapse
Hey man thank you for your answer!
Did you have any problems with the unlocked properties (telco wise, no bootloader) when flashing these things?
I also checked my download mode and doesn't say anything about developer. Seems fine showing up Odin mode so I'm going to assume this is a retail version.
demiorkan said:
Hey man thank you for your answer!
Did you have any problems with the unlocked properties (telco wise, no bootloader) when flashing these things?
I also checked my download mode and doesn't say anything about developer. Seems fine showing up Odin mode so I'm going to assume this is a retail version.
Click to expand...
Click to collapse
The only way to get an ota is to be on Verizon. Other wise you'll need to download the update and flash with Odin or flash with stock recovery.
The reason for the "safe update to mm" threads are for people who rooted and unlocked the boot loader. You'll need to follow one of those threads if you want root. Nothing wrong with just updating to mm other than you'll have to downgrade to 5.1.1 if you later decide you want root and unlocked boot loader
These phones become really unstable if you just try to root and you lose root once you restart the phone.
Sent from my SM-N910V using Tapatalk
Hey all, I'm still on June 1st security patch (NCX26.2), T-Mobile variant and stock, with bootloader unlocked which seems to be preventing my phone from updating to the latest OTA. I'm getting served with NCX26.7, but the update keeps failing.
Could someone post step by step on how to update my phone to the most recent rootable OTA (perhaps sideload?), and then what would be the easiest way to root. I don't mind wiping the entire device as long as it gets me to the latest software patch.
*EDIT* Now looking at the settings, it seems like I've flashed my Kernel months ago, which is likely what's causing my phone not to update. If I follow the Flash-all guide, will that reset the kernel to stock? Screenshot attached.
Many thanks!
milan03 said:
Hey all, I'm still on June 1st security patch (NCX26.2), T-Mobile variant and stock, with bootloader unlocked which seems to be preventing my phone from updating to the latest OTA. I'm getting served with NCX26.7, but the update keeps failing.
Could someone post step by step on how to update my phone to the most recent rootable OTA (perhaps sideload?), and then what would be the easiest way to root. I don't mind wiping the entire device as long as it gets me to the latest software patch.
*EDIT* Now looking at the settings, it seems like I've flashed my Kernel months ago, which is likely what's causing my phone not to update. If I follow the Flash-all guide, will that reset the kernel to stock? Screenshot attached.
Many thanks!
Click to expand...
Click to collapse
yes