Database Info

[Q] Will OTA Lollipop unroot/brick me?

Running 4.4.4 - S-OFF and ROOTED - will official OTA unroot/corrupt ROM/brick me?

j006 said:
Running 4.4.4 - S-OFF and ROOTED - will official OTA unroot/corrupt ROM/brick me?
Click to expand...
Click to collapse
Just rooted? No system modifications? Reason I ask is that if you are simply rooted and haven't modified system files AND you have stock recovery installed the update will go through fine...after which you reinstall twrp and flash su.zip

dottat said:
Just rooted? No system modifications? Reason I ask is that if you are simply rooted and haven't modified system files fors AND you have stock recovery installed the update will go through fine...after which you reinstall twrp and flash su.zip
Click to expand...
Click to collapse
Well, I have Xposed installed and a bunch of modules running so technically I have modified some system files, plus I have Clockwork recovery installed...

dottat said:
Just rooted? No system modifications? Reason I ask is that if you are simply rooted and haven't modified system files AND you have stock recovery installed the update will go through fine...after which you reinstall twrp and flash su.zip
Click to expand...
Click to collapse
I'm still on 4.4.3 with a viper rom. I'll probably have to update to 4.4.4 in order to get to 5.0.1 right? Will updating to 4.4.4 then 5.0 allow me to keep root still? Or can I just easily flash supersu.zip through adb sideload to access root again if lost?

I won't be putting lollipop on my phone until it gets Xposed support.

j006 said:
Well, I have Xposed installed and a bunch of modules running so technically I have modified some system files, plus I have Clockwork recovery installed...
Click to expand...
Click to collapse
With custom recovery = no OTA. Anyway, you are on 4.4.4. What do you want to OTA update to?
Just wait a few days after the next OTA release and you'll find the firmware files, RUU and such here on XDA, ready to be flashed in fastboot or via dottat's wonderful .exe's. Wait a few days more and your custom rom will get an update based on the latest release.
I would never chase an OTA......
---------- Post added at 08:23 PM ---------- Previous post was at 08:20 PM ----------
Thejimmynguyen said:
I'm still on 4.4.3 with a viper rom. I'll probably have to update to 4.4.4 in order to get to 5.0.1 right? Will updating to 4.4.4 then 5.0 allow me to keep root still? Or can I just easily flash supersu.zip through adb sideload to access root again if lost?
Click to expand...
Click to collapse
If you are S-off you can always flash a custom recovery and su in recovery.

berndblb said:
With custom recovery = no OTA. Anyway, you are on 4.4.4. What do you want to OTA update to?
Just wait a few days after the next OTA release and you'll find the firmware files, RUU and such here on XDA, ready to be flashed in fastboot or via dottat's wonderful .exe's. Wait a few days more and your custom rom will get an update based on the latest release.
I would never chase an OTA......
---------- Post added at 08:23 PM ---------- Previous post was at 08:20 PM ----------
If you are S-off you can always flash a custom recovery and su in recovery.
Click to expand...
Click to collapse
I don't necessarily want to update, but HTC/Verizon is starting to push out the OTA for Lollipop. When I had my Incredible 2 (S-OFF/CWM recovery/rooted), VZW constantly nagged me with OTA update prompts until I edited a system (build.prop maybe? I can't remember) file to trick them into thinking I already had the latest. I just don't want a repeat of that, plus I'm really not interested in updating until Lollipop has full Xposed support!

j006 said:
I don't necessarily want to update, but HTC/Verizon is starting to push out the OTA for Lollipop. When I had my Incredible 2 (S-OFF/CWM recovery/rooted), VZW constantly nagged me with OTA update prompts until I edited a system (build.prop maybe? I can't remember) file to trick them into thinking I already had the latest. I just don't want a repeat of that, plus I'm really not interested in updating until Lollipop has full Xposed support!
Click to expand...
Click to collapse
Go to Settings > Apps, swipe to All and disable HTC DM. Or, even better, freeze it in TiBu.
That should take care of any update notification.

OI1 Firmware with OH1 Roms

There's been a bit of talk about rooting OI1 in the last few days, but I've got a question on the OH1 roms and compatibility with OI1 firmware. Can we flash the older Oh1 roms with the OI1 firmware and everything will be good? Example, radio issues arising. I don't have access to a PC during the week if something goes wrong.

No issues. Works fine. Just can't Odin back to OH1.

My phone was on Ol1 and I flashed an OH1 rom and it went bad.
From what I've been told, nothing can be done until the Ol1 firmware is released.
---------- Post added at 08:25 PM ---------- Previous post was at 08:18 PM ----------
Cancel that, I cannot read lol
An OH1 should be able to run OL1..... But who has a copy of ol1 available? I've searched everywhere for days and cant find anything.

SuperSlow911 said:
My phone was on Ol1 and I flashed an OH1 rom and it went bad.
From what I've been told, nothing can be done until the Ol1 firmware is released.
---------- Post added at 08:25 PM ---------- Previous post was at 08:18 PM ----------
Cancel that, I cannot read lol
An OH1 should be able to run OL1..... But who has a copy of ol1 available? I've searched everywhere for days and cant find anything.
Click to expand...
Click to collapse
OI1 firmware isn't released yet and if you went from OI1 firmware to OH1 you're probably hard bricked. Can you get into recovery? If you need a OI1 rom, you're in luck, I have one

I absolutely can. I originally had access to the stock recovery but could only choose to do a factory default reset which didn't help at all.
Then I used ADB to install TWRP and installed a new firmware which it accepted but, it sticks in a boot loop.
before flashing an OH1 firmware and kernel TWRP informed me there was no OS on the S6 Edge (Sprint) and NOTHING was mounted. Fixed the mounting issues. Re partitioned to factory specs and installed the custom rom.
The Rom fixed the OS and Root issue and is working on the phone as it makes a 5 tone song (supposed to during boot) but constantly loops back. I haven't been able to discover a way to look at the loop, all I know is its stuck on the "powered by" screen.
---------- Post added at 09:32 PM ---------- Previous post was at 09:23 PM ----------
Soooperstar said:
OI1 firmware isn't released yet and if you went from OI1 firmware to OH1 you're probably hard bricked. Can you get into recovery? If you need a OI1 rom, you're in luck, I have one
Click to expand...
Click to collapse
If that ol1 firmware works I will HAPPILY donate to you. BELIEVE ME.

SuperSlow911 said:
I absolutely can. I originally had access to the stock recovery but could only choose to do a factory default reset which didn't help at all.
Then I used ADB to install TWRP and installed a new firmware which it accepted but, it sticks in a boot loop.
before flashing an OH1 firmware and kernel TWRP informed me there was no OS on the S6 Edge (Sprint) and NOTHING was mounted. Fixed the mounting issues. Re partitioned to factory specs and installed the custom rom.
The Rom fixed the OS and Root issue and is working on the phone as it makes a 5 tone song (supposed to during boot) but constantly loops back. I haven't been able to discover a way to look at the loop, all I know is its stuck on the "powered by" screen.
---------- Post added at 09:32 PM ---------- Previous post was at 09:23 PM ----------
If that ol1 firmware works I will HAPPILY donate to you. BELIEVE ME.
Click to expand...
Click to collapse
Its not the full firmware but only a deodexed OI1 rom. I'll pm you

OI1 firmware
http://forum.xda-developers.com/showthread.php?t=3219484

Odin write fail

Ok, I have a Note 5 from Tmobile, the problem i am having is i am not able to go back to 5.1.1 cokc firmware
I had the 6.0.1 Rom from Jovi, in the instructions I had to flash the leaked MM bootloader and Modem, then with TWRP flash the Rom
Everything went fine with no problems, now since Tmobile released MM for their Note 5 I wanted to go back to LP 5.1.1 and take the over the air update
Well before i did that i went to TWRP and ereased everything including Format Data, no operating system, well i though just with Odin and the official LP 5.1.1 would suffice
Now i am getting an error in Odin as failed to flash the Official LP firmware. Can anybody recommend a method to get this thing back to life ??
thanks

MHeat said:
Ok, I have a Note 5 from Tmobile, the problem i am having is i am not able to go back to 5.1.1 cokc firmware
I had the 6.0.1 Rom from Jovi, in the instructions I had to flash the leaked MM bootloader and Modem, then with TWRP flash the Rom
Everything went fine with no problems, now since Tmobile released MM for their Note 5 I wanted to go back to LP 5.1.1 and take the over the air update
Well before i did that i went to TWRP and ereased everything including Format Data, no operating system, well i though just with Odin and the official LP 5.1.1 would suffice
Now i am getting an error in Odin as failed to flash the Official LP firmware. Can anybody recommend a method to get this thing back to life ??
thanks
Click to expand...
Click to collapse
Do a fullwipe system data boot cahhe internal everything via twrp then boot to download mode and odin cokc it should work if not canr help anymore
Sent From My SM-N920T Running Marshmallow 6.0.1 Rooted/TWRP

still fails, going crazy now

UPDATE: got it to work, such a dummy i was selecting the CP slot in Odin instead of AP

Mine is failing as well, where did you get the firmware that is working for you? I am using AP in Odin, fail...
---------- Post added at 01:32 PM ---------- Previous post was at 01:23 PM ----------
Never mind. I just need to read harder next time.

mycomputerisjunk said:
Mine is failing as well, where did you get the firmware that is working for you? I am using AP in Odin, fail...
---------- Post added at 01:32 PM ---------- Previous post was at 01:23 PM ----------
Never mind. I just need to read harder next time.
Click to expand...
Click to collapse
just download from sammobile then wipe everything, reboot to download mode, select AP from Odin and load the image your downloaded from sammobile, cokc firmware 5.1.1

Use Odin-v3-10-7-1 http://samfirm.net/threads/tool-new-odin-v3-10-7-1-support-new-devices-2015-2016-s7-s7e-s6-s6e-s6e-note-5.27/
---------- Post added at 10:35 AM ---------- Previous post was at 10:29 AM ----------
Firmware 6.0.1 aquí http://forum.xda-developers.com/tmobile-galaxy-note5/general/official-link-rom-stock-android-6-0-1-t3361891

Moto G 2015 xt1550 Two new Security Updates

Hi all I just got two new security updates on my xt1550 one after the other. the update versions are as follows
24.71.2.en.03 - July, 2016 Security patch
24.201.5.en.03 - October 1st, 2016 Security Patch
Can anyone else confirm they got the security patches?? my android version is on 6.0.1 and not rooted.

Yes many people have received the security updates...

yes, me too

Yes security updates are rolling out now in India, other varients got july update in late November and October patch with us.

yes i got this too and now when it reboots, it reboots to TWRP and loops back. So i cleared cache date and was able to boot properly. But i was not able to update to that version. mobile is rooted and unlocked. Is there anyway anyone can get me that link so that i can fastboot the update?

manohar1121 said:
yes i got this too and now when it reboots, it reboots to TWRP and loops back. So i cleared cache date and was able to boot properly. But i was not able to update to that version. mobile is rooted and unlocked. Is there anyway anyone can get me that link so that i can fastboot the update?
Click to expand...
Click to collapse
I faced the same issue.
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Go to this page. Download your respective factory image. Unzip. Flash the stock recovery. Now update.
After this, flash twrp if you want.

bin.sayantan said:
I faced the same issue.
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Go to this page. Download your respective factory image. Unzip. Flash the stock recovery. Now update.
After this, flash twrp if you want.
Click to expand...
Click to collapse
I dont wanna flash mobile all over again. just need to update that if possible. I got that 20MB update last month only..

manohar1121 said:
I dont wanna flash mobile all over again. just need to update that if possible. I got that 20MB update last month only..
Click to expand...
Click to collapse
Don't flash the entire stock ROM. Just the recovery image.
But please, don't flash that official update on any custom ROM.

bin.sayantan said:
Don't flash the entire stock ROM. Just the recovery image.
But please, don't flash that official update on any custom ROM.
Click to expand...
Click to collapse
I have flashed newer build in that not long ago.
u mean to say uninstall twrp? is that wat u meant flash recovery image ?

manohar1121 said:
I have flashed newer build in that not long ago.
u mean to say uninstall twrp? is that wat u meant flash recovery image ?
Click to expand...
Click to collapse
No need to wipe recovery. Flash stock recovery on top of TWRP. It will automatically be replaced.

If he is rooted he won't be able to update. OTA updates require pure stock - stock recovery, stock kernel, and an unmodified system. This means no root, xposed, or any other changes to the system including build.prop edits.
Sent from my MotoG3 using Tapatalk

bin.sayantan said:
No need to wipe recovery. Flash stock recovery on top of TWRP. It will automatically be replaced.
Click to expand...
Click to collapse
It worked half way, while it says installing on the stock recovery then error comes with sleeping android with red triangle exclamation mark.
---------- Post added at 02:35 PM ---------- Previous post was at 01:54 PM ----------
riggerman0421 said:
If he is rooted he won't be able to update. OTA updates require pure stock - stock recovery, stock kernel, and an unmodified system. This means no root, xposed, or any other changes to the system including build.prop edits.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
so i should lock my bootloader and flash stock recovery ?

manohar1121 said:
It worked half way, while it says installing on the stock recovery then error comes with sleeping android with red triangle exclamation mark.
---------- Post added at 02:35 PM ---------- Previous post was at 01:54 PM ----------
so i should lock my bootloader and flash stock recovery ?
Click to expand...
Click to collapse
You need not relock the bootloader. I have flashed system updates with stock recovery and unlocked bootloader.
Looks like you have correctly flashed the recovery. Once you get the red exclamation mark, keeping the volume up pressed, press the power button (I don't remember exactly, if it doesn't work, try the reverse).

manohar1121 said:
It worked half way, while it says installing on the stock recovery then error comes with sleeping android with red triangle exclamation mark.
---------- Post added at 02:35 PM ---------- Previous post was at 01:54 PM ----------
so i should lock my bootloader and flash stock recovery ?
Click to expand...
Click to collapse
No need to lock the bootloader, but if you were rooted as stated in your first post, you will the stock system and kernel. You can not update if ANY system files, kernel, or recovery are not FULL stock. Your best bet right now is to flash the stock ROM via fastboot, if you need the update.

riggerman0421 said:
No need to lock the bootloader, but if you were rooted as stated in your first post, you will the stock system and kernel. You can not update if ANY system files, kernel, or recovery are not FULL stock. Your best bet right now is to flash the stock ROM via fastboot, if you need the update.
Click to expand...
Click to collapse
I have stock ROM. 3.10.49-ge6a5415
system version - 24.71.2.osprey_retasia_ds_2gb.retasia.en.03 retin
i got OTA update. so its not possible to update if mobile is rooted is it ?

manohar1121 said:
I have stock ROM. 3.10.49-ge6a5415
system version - 24.71.2.osprey_retasia_ds_2gb.retasia.en.03 retin
i got OTA update. so its not possible to update if mobile is rooted is it ?
Click to expand...
Click to collapse
The updater script checks the system, recovery and kernel. If they do not match what is expected (full stock), then the update will fail. I can't say it any more clearly, you need FULL STOCK, ie no modifications to system files (xposed, added or deleted system apps, build.prop edits, root, custom recovery). If you have done any of this, even one, the update will fail. Flash the stock ROM via fastboot.

Got a new update Jan 2017
Moto g3 xt1550 Osprey

So, to revert back to stock 6.0.1 from custom 7.1.1, do i need to wipe system, data, cache, etc before restoring my back up of the stock?

M-in-M said:
So, to revert back to stock 6.0.1 from custom 7.1.1, do i need to wipe system, data, cache, etc before restoring my back up of the stock?
Click to expand...
Click to collapse
You should. But I think it can be done right after flashing stock ROM also.

After getting these brutal update messages every few minutes on Android 6.0 and not being to update because of root and TWRP, rather than going back to stock, I finally cracked and bit the bullet yesterday and installed Lineage. I am now on Android 7.1.2 with the April security update, and going forward new OS and security updates will be simple updates; in fact the May update as noted by the OP is due this week, and I can either install it OTA from Lineage with a press of a button, or via TWRP if I so desire . I understand others don't want to install a custom ROM for various reasons, but for me it was a no-brainer.

Newer Stock ROM

Hi,
I am a noobie so just any help would be much appreciated: for some reason my Moto G 2015 occasionally messes up its baseband and wifi mac address and I have in the past successfully revived it by flashing an appropriate stock ROM with RSD lite. However, this time around that didn´t work and I got failure at .gpt bin. Since then, I have rooted my phone and installed TWRP and tried flashing it again but get a preflash validation error. Installing Lineage has fixed the wifi mac address but the baseband issue remains.
I suppose that this has to be do with the fact that my BL in the fastboot boot reads 80.cf (sha 8bfe213, 2017-03-13) which is more recent than the stock ROM. Is that a correct assumption? What can I do to get my baseband working?
Thanks!

Just skip gpt.bin and bootloader while flashing the firmware u r getting this error cus latest firmware image of Moto g3 has not being flashed,as it's not available

Is this possible to do via TWRP? How so? Unfortunately I am travelling and dont have access to a PC so I was wondering if this can only be done via cmd prompt. In any case, could you please guide me through the steps for skipping these two and flashing the rest?
Thanks a lot for your help!

You can use flash fire to flash stock firmware
---------- Post added at 06:11 PM ---------- Previous post was at 06:07 PM ----------
Or these links may help
https://forum.xda-developers.com/20...m-stock-motorola-roms-twrp-flashable-t3621387
https://forum.xda-developers.com/2015-moto-g/development/rom-stock-rom-6-0-1-optimized-t3609991
https://forum.xda-developers.com/20...m-moto-g-2015-unmodified-stock-6-0-1-t3587390
---------- Post added at 06:14 PM ---------- Previous post was at 06:11 PM ----------
Check your model no. before flashing it not available flashfire is the only way

So the flashfire method didn't work. I just ended up with a phone that needed to be revived manually by flashing through fastboot. I managed to flash the 6.0.1 version for the Osprey by skipping gpt.bin. However, the baseband is still missing. Can anyone help me out with a newer stock image that I can try to flash? Or is there a particular patch? Please do let me know what I can do get the baseband back....[and really what a strange issue to lose your baseband because of low battery...]
Thanks!

So flashing via fastboot a couple of times ended up fixing the baseband issue--it shows up in the bootloader and in the settings tab. However, the sim isn't still detected. This is a dual sim phone. I have tried wiping the partition cache and using other sims but without luck. Any ideas?
Thanks!