I don't know guys that what is flashing. YU (company) has stated me to do flashing and I have done the same. I want to know that now will I receive ota updates or not.
Does it harmful for device. In future if any updated is rolled out for yureka then will I get the update via ota? Is flashing do rooting of the device?
Related
Check out this link:
http://www.slashgear.com/htc-hero-update-confirmed-imminent-1852644/
Appears as though HTC are gonna address the lagginess expereinced by many (including myself) with an OTA update.
Those with root like me will not get the OTA update as ive read the firmware wont update on rooted phones. Im wondering whether people will put their chef hats on with the new update to create a rom based on it?
You could restore a backup from a point where you had not rooted your phone yet
It basically unroots itself that way.
ammurad said:
Check out this link:
http://www.slashgear.com/htc-hero-update-confirmed-imminent-1852644/
Appears as though HTC are gonna address the lagginess expereinced by many (including myself) with an OTA update.
Click to expand...
Click to collapse
That link makes no mention whatsoever that the update will be OTA - in fact, it says:
“HTC will be providing a software update for the HTC Hero, which will be available via the HTC website in the coming weeks.” HTC statement
Click to expand...
Click to collapse
Via the website almost certainly means download and update manually. Being rooted shouldn't stop you applying the update, though you will probably lose root in the process.
Note that Google pushed OTA updates out for the G1, and the reason they didn't work on most rooted phones was because the procedure used to root the phone specifically switched off the OTA functionality to avoid the phone getting an update and losing root.
Regards,
Dave
It was confirmed prior to release that the Hero would be incapable of receiving OTA updates.
Ok thats useful information. We can just hope now that the update will get rid of the lag.
Someone needs to change the thread topic to
Hero update Iminent, but noT if you have ROOT!
ghoonk said:
Someone needs to change the thread topic to
Hero update Iminent, but noT if you have ROOT!
Click to expand...
Click to collapse
I thought it was only OTA updates that rooted phones couldn't recieve.
Biffert said:
You could restore a backup from a point where you had not rooted your phone yet
It basically unroots itself that way.
Click to expand...
Click to collapse
correct me if i am wrong but even if you back up with nandroid before rooting , running the backup doesnt unroot your phone.
anyway, it is not a problem. all u have to do is just to flash the stock rom posted on this thread and then run the update if this is the case .
I don't think ROOTING is the problem. I think that some people, in the process of rooting, end up changing the recovery.img with test keys which the update may check against and prevent the update.
I updated mine using ADB and used fastboot, so I don't think I actually changed the recovery.img, so future updates will just see my phone as a 'normal' unbranded device (albeit with Superuser.apk and su.apk, and the HTC CIME)
After OTA update, We will get the Custom rom of Hero soon (Like in G1)
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 ...
I am a little confused about what constitues an OTA update and wished to clarify this throughly since all rooting methods have a precautionary message regarding this.
From what I know:
1. OTA updates are "only" firmware updates.
What I am confused about:
Considering my above assumption of it being only a firmware update to be right
1. Does OTA update refer to only certain methods of firmware installation?
2.Are there methods to permanently disable it such that only intentional manual procedure will cause it to happen ( E.g: System settings)
Thanks in advance :good:
nashnir said:
I am a little confused about what constitues an OTA update and wished to clarify this throughly since all rooting methods have a precautionary message regarding this.
From what I know:
1. OTA updates are "only" firmware updates.
What I am confused about:
Considering my above assumption of it being only a firmware update to be right
1. Does OTA update refer to only certain methods of firmware installation?
2.Are there methods to permanently disable it such that only intentional manual procedure will cause it to happen ( E.g: System settings)
Thanks in advance :good:
Click to expand...
Click to collapse
OTA updates will never install automatically, so take that off your worry list
1.) OTA updates are downloaded to the phone after you allow the download to proceed. Even if you accidentally click download, it will confirm with you again before rebooting the phone and installing it.
2.) If it does give you the notification, you can just long click the notification and Force Close the process. Then it won't bother you again until the next update comes out, or you choose to unroot and flash preroot, then update.
cmendonc2 said:
OTA updates will never install automatically, so take that off your worry list
1.) OTA updates are downloaded to the phone after you allow the download to proceed. Even if you accidentally click download, it will confirm with you again before rebooting the phone and installing it.
2.) If it does give you the notification, you can just long click the notification and Force Close the process. Then it won't bother you again until the next update comes out, or you choose to unroot and flash preroot, then update.
Click to expand...
Click to collapse
Rooted my device once then after unrooted after that ota update is not working How to fix this issue thank you
anas214812 said:
Rooted my device once then after unrooted after that ota update is not working How to fix this issue thank you
Click to expand...
Click to collapse
Follow this: http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Hi I just wanted some confirmation that unlocking bootloader doesn't block me from getting OTA updates from Google, since I haven't gotten an OTA for the latest build yet (The May update). I'm hoping this is only cause I'm in India and it hasn't pushed to us yet. I've enrolled in the Android Beta Program to test if OTA is really broken (since it sends an OTA with the Android N image.)
I haven't modified anything, I tried flashing TWRP but it didn't stick cause I didn't know I had to go into the recovery and modify the system/boot, so I still have the stock android recovery.
Any confirmation will give me a lot of peace of mind, cause I value getting OTAs and not having to manually flash it. If it has indeed been broken, I want to know if relocking would fix it and if relocking would wipe data again. Thanks for your help
EDIT: Just got the OTA for the N preview, so I guess it's just a roll out thing then. Just want to leave this here for anyone else who's new to nexus devices and was wondering the same.
AnrgKrshn said:
Hi I just wanted some confirmation that unlocking bootloader doesn't block me from getting OTA updates from Google, since I haven't gotten an OTA for the latest build yet (The May update). I'm hoping this is only cause I'm in India and it hasn't pushed to us yet. I've enrolled in the Android Beta Program to test if OTA is really broken (since it sends an OTA with the Android N image.
I haven't modified anything, I tried flashing TWRP but it didn't stick cause I didn't know I had to go into the recovery and modify the system/boot, so I still have the stock android recovery.
Any confirmation will give me a lot of peace of mind, cause I value getting OTAs and not having to manually flash it. If it has indeed been broken, I want to know if relocking would fix it and if relocking would wipe data again. Thanks for your help
Click to expand...
Click to collapse
Simply having an unlocked bootloader won't stop you from receiving OTAs. I don't believe they've even began pushing the OTA for the May update.
brholt6 said:
Simply having an unlocked bootloader won't stop you from receiving OTAs. I don't believe they've even began pushing the OTA for the May update.
Click to expand...
Click to collapse
Just saw this after I posted my edit lol. Thanks for the confirmation
Will the ota work with systemless root?
94SupraTT said:
Will the ota work with systemless root?
Click to expand...
Click to collapse
You need to flash stock boot and recovery images to receive it or alternatively use chainfires flashfire app.
OTA - You may BRICK your phone if you have a modified recovery(TWRP,etc) and you try to take an OTA.
OTA will fail if magisk is present.
see
https://forum.xda-developers.com/mo...p-flashing-t3813498/post77011495#post77011495
bump
hello
bumpsi
It is well known since ages, at least since Android 4 where this block oriented OTA was first implemented, that OTA will fail if recovery, boot or system partition is modified. Any root solution modifies at least boot or system and will prevent OTA to run through. Modified recovery should also stop the OTA (do not flash TWRP since long time, so I am not that sure about this on newer Android, at least until Android 6 Lollipop it did).
So: No one could ever successfully take OTA without uninstalling root and twrp if installed. This is valid and well known for nearly all Android devices, not only Motorola. It is known.
Brick on Moto devices is dangerous. It happens if you downgrade your system, but bootloader never is able to get downgraded. So the OTA tries to update the bootloader assuming it is old, but it already is current. This may result in a hard brick where flashing is not possible anymore. You are on the safe side if you do not restore a backup of a system with a previous bootloader, and do not flash older firmware.
So: No one is supposed to brick the Motorola smartphone via OTA if no firmware downgrade ever is done.
Just doing OTA with root will NOT do a greater harm than a failed OTA. There will be some installation log mentioning "there is partition xyz modified, I will not install the OTA". The system will run as before without update. If it doesn't because of some error in the update mechanism, it will suffice to flash the currently installed or some newer firmware to recover the device, there should occur no brick. Root is not the reason for brick in combination with OTA. Older firmware is.
So: What is your reason to bump this wrong worded warning?
KrisM22 said:
bumpsi
Click to expand...
Click to collapse
Kris, please stop spamming the forum. You bumped two threads, repeatedly
many thanks for bumping this important post!
interesting sig.