I have an unlocked rooted 4.4 and need to update to the latest os and modem drivers.
What is the best way and how do I get tethering and root back after I do it?
Pay for sunshine get boot loader unlock flash moto x ROM that is modded
I already have it unlocked.
Where can I get the latest 4.4.4 rooted and can I flash it directly over the current rooted 4.4?
Also where can I get the latest modem drivers?
If you are boot loader unlocked you are already good to go, you can root with a quick flash of a custom recovery
Durteedee said:
If you are boot loader unlocked you are already good to go, you can root with a quick flash of a custom recovery
Click to expand...
Click to collapse
I have TWRP and rooted I need the latest modem drivers and os update
http://motofirmware.center/files/
This site was down for a while, but it seems to be back in a limited fashion right now.
You will need to reinstall TWRP and flash Superuser/SuperSU to regain root after flashing the files most likely. As for tethering, if you plan to stay with a Droid Maxx ROM, you can take a look at this link.
http://forum.xda-developers.com/droid-ultra/orig-development/mod-native-tether-build-24-3-7-t3019059
Do I need to remove TWRP first?
gatortuba said:
Do I need to remove TWRP first?
Click to expand...
Click to collapse
You have to flash that image with RSDLite if I recall correctly. If you leave the xml file the way it is, I believe it will wipe your TWRP and flash the stock recovery in the process, not positive as I haven't done it for a few months. You can reinstall TWRP and root afterwards.
Diocat said:
You have to flash that image with RSDLite if I recall correctly. If you leave the xml file the way it is, I believe it will wipe your TWRP and flash the stock recovery in the process, not positive as I haven't done it for a few months. You can reinstall TWRP and root afterwards.
Click to expand...
Click to collapse
All done, just manually flashed everything but the bootloader.
What are the exact steps?
I have an unlocked boot loader on my Droid Maxx. Currently phone is on 4.4.
Now I am interested in updating it to the latest OTA without losing root.
I understand that if I first install TWRP, I would not be able to take OTA updates. In that case I have to download the update files from the link above and flash via RSD Iite. Is that correct?
Is it not simpler for me to take all the OTA's first (and lose root in the process.) Then, I can still install TWRP and then install SuperSU?
So, yesterday I took four OTA updates and moved from 19.xx to the latest 4.4.4.
I am still rooted and with BL unlocked.
No TWRP ever installed.
Temp root with root king droid maxxx4.4.4!!
I upgraded to the new version of king root today and ran it. I was able to get temp root. I have full access to everything for su. Tested multiple root apps. Will you please post this info some where so as to help my fellow droid maxxx4.4.4 peers?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://postimg.org/image/lcg60jaj3
Related
I did root my phone. Just did the root and nothing else.
I wonder if the direct updates from google will fall on my phone, or if I'll need to remove the root to get the updates.
(I know that after upgrading i lost root, but this is no problem).
Thank you for attention
No. This is all covered in the OTA help-desk thread which you can get to via my signature.
Just download the full rooted stock ROM in android development and flash it without wipe from recovery.
It's actually fewer steps anyway.
OTA = revert system changes and/or kernel, reboot into recovery, flash the OTA , boot to bootloader, connect to pc, fastboot flash recovery, reboot into recovery, flash supersu.
Rooted stock = reboot into recovery, flash the ROM.
No brainer really. Flashing an OTA if rooted is a fool's errand.
Sent from my Nexus 5 using Tapatalk
rootSU said:
No. This is all covered in the OTA help-desk thread which you can get to via my signature.
Just download the full rooted stock ROM in android development and flash it without wipe from recovery.
It's actually fewer steps anyway.
OTA = revert system changes and/or kernel, reboot into recovery, flash the OTA , boot to bootloader, connect to pc, fastboot flash recovery, reboot into recovery, flash supersu.
Rooted stock = reboot into recovery, flash the ROM.
No brainer really. Flashing an OTA if rooted is a fool's errand.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Copy + paste?
Lethargy said:
Copy + paste?
Click to expand...
Click to collapse
Yeah.
Sent from my Nexus 5 using Tapatalk
Root with towelroot dont unlock bootloader.
So, if i unroot in settings of SuperSU, OTA is available, no?
joaonds said:
Root with towelroot dont unlock bootloader.
So, if i unroot in settings of SuperSU, OTA is available, no?
Click to expand...
Click to collapse
Read the OTA thread I've already told you about.
Make sure you backup all your data first. Towelroot is not 100% successful so if it fails, you'll have no choice but to unlock bootloader which wipes device
Or better yet, unlock the bootloader with boot unlocker before the update. That way you won't lose anything.
Sent from my Nexus 5 using Tapatalk
Thanks bro.
Note: I want return to stock, and available to OTA updates. Not root. Unroot.
I have installed root with Towelroot (and work fine here), but i uninstalled this root (in app itself of SuperSu), because i want OTA updates. Root is not prioritary to me.
So, please, Check these 2 pictures if my device is enabled to receive direct updates from Google?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Root does NOT prevent OTA. When you get an OTA it will unroot
Sent from my Nexus 5 using Tapatalk
Hi everyone. There are discussion spread on multiple posts about the problems we should have on downgrading from Marshmallow OTA updated. I created this thread in a attempt to centralize this.
Sounds like the previous Moto Gs (2013, 2014) users get a bricked phone when attempting to downgrade from OTA update to factory firmware and re-update it with OTA update again... This is related to the bootloader being modified by the OTA update. Because of this the recommendation for this devices is not to update their phones using OTA update if they want to downgrade someday.
Well, there are some successful reports from osprey (Moto G 2015) users doing this. Users like @drico_649 and @yea55 successful downgraded their phones.
I'm stuck on unlocked bootloader after a failed attempt to root Marshmallow. So, I need to downgrade my OTA updated to Marshmallow.
The obvious way is flash the factory firmware with fastboot and re-update to OTA Marshmallow but this is considered risky.
What are my alternatives?
Ok, I successfully flashed the factory firmware. Working normally!
But I got a unusual message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's portuguese:
Uninstall firmware service sensors Motorola
This will revert firmware to the previous version
! Select uninstall to reboot the phone.
Options: later and uninstall
That is this? I did not answer this.
So you can successfully downgrade the bootloader on your device? or did you skip gpt.bin and bootloader.img
The only thing people need to skip is gpt.bin
Yousvel said:
The only thing people need to skip is gpt.bin
Click to expand...
Click to collapse
i swear the bootloader was thing you wernt meant to downgrade? and what happens if you do flash gpt.bin ?
therealduff1 said:
i swear the bootloader was thing you wernt meant to downgrade? and what happens if you do flash gpt.bin ?
Click to expand...
Click to collapse
If you flash gpt.bin, it will just fail, but it shouldn't cause anything. But for the bootloader, it will be downgraded with no problem at all.
Yousvel said:
If you flash gpt.bin, it will just fail, but it shouldn't cause anything. But for the bootloader, it will be downgraded with no problem at all.
Click to expand...
Click to collapse
So if i were to downgrade my phone via fastboot to lollipop, then upgrade again though ota, it would all be fine ?
therealduff1 said:
So if i were to downgrade my phone via fastboot to lollipop, then upgrade again though ota, it would all be fine ?
Click to expand...
Click to collapse
It's no safe to accept ota after downgrading
I have a 6045I 5.5 and no matter how many times i flash twrp 2.8.7.0 I still boot into stock recovery. I am sure the flash was succesful because the command prompt told me it was but this keeps happening. I heard on some website that this is due to the latest update from alcatel (which I installed ). Does anyone know a method of flashing twrp that still works as of 3 weeks ago? ( this is when I got the phone and updated it). If not does anyone know any other rooting methods that still work as of this month? I've already tried king root and towel root with no success.
P.S : Yes bootloader is unlocked in case that's the first thing you were gonna ask.
Chookthespook said:
I have a 6045I 5.5 and no matter how many times i flash twrp 2.8.7.0 I still boot into stock recovery. I am sure the flash was succesful because the command prompt told me it was but this keeps happening. I heard on some website that this is due to the latest update from alcatel (which I installed ). Does anyone know a method of flashing twrp that still works as of 3 weeks ago? ( this is when I got the phone and updated it). If not does anyone know any other rooting methods that still work as of this month? I've already tried king root and towel root with no success.
P.S : Yes bootloader is unlocked in case that's the first thing you were gonna ask.
Click to expand...
Click to collapse
Did you try to follow the rest of the fastboot instructions in the unlock bootloader /root thread? You can also flash TWRP image with flashify from the play store for free. That is the method I used to achieve success. Hope that helps. Good luck! :good:
dongarritas said:
Did you try to follow the rest of the fastboot instructions in the unlock bootloader /root thread? You can also flash TWRP image with flashify from the play store for free. That is the method I used to achieve success. Hope that helps. Good luck! :good:
Click to expand...
Click to collapse
Don't you need root for flashify? which is so stupid to me because I need to flash to root in the first place
Chookthespook said:
Don't you need root for flashify? which is so stupid to me because I need to flash to root in the first place
Click to expand...
Click to collapse
Yes, you do need root. Follow the rest of the guide and you will have root. Then use Flashify to flash Unjustified's TWRP.
This device needs to be rooted via the guide for a no problems root, starting with the unlocking of the bootloader. If you are having problems, factory reset, install drivers from phone, then read and follow the guide. Then flash TWRP and go on with your setup.
Solved
I ran into the same issue with my 6045O but I spent time and went over the instructions again... as they were vague. You need to make sure you use the correct Fastboot code to permanently install TWRP on your device.
Links to thread where codes and files are located:
http://forum.xda-developers.com/idol-3/general/twrp-custom-recovery-idol3-6045-t3162608
http://forum.xda-developers.com/idol-3/general/guide-unlock-bootloader-root-alcatel-t3161878
***Pay attention tho the Fast boot Codes***
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sunshine was working perfect from 4 month and i was needed to update sunshine version only but after Droid kernel update this message is coming now "sunshine only supports the droid turbo on the SU4TL-44 (5.1) Kernel. Please Update or flash the correct kernel (3.10.40-perf-g90ddf4a) and try again."
What to do now ??????????????????????
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This specific phone bootloader was locked or unlocked before you took the SU4TL-49 update?
You are implying you were already running Sunshine on this phone, and if so the bootloader was UNlocked.
Did you re-lock the bootloader for some reason before flashing SU4TL-49?
1) you can only unlock the XT1254 bootloader once with Sunshine (well, almost impossible to unlock twice) -- even if you don't flash anything else.
2) if you flash SU4TL-49 with a locked bootloader, that closes the bootloader unlock exploit.
OR is this a different XT1254 phone you wish to run Sunshine on?
You have to run Sunshine and UNlock the bootloader BEFORE flashing SU4TL-49.
From Sunshine:
[PSA] DT Android SU4TL-49 5.1 + Updates patch SunShine Unlock, Unlock b4 updating
http://forum.xda-developers.com/droid-turbo/general/psa-droid-turbo-android-6-0-update-t3379894
Are you just running sunshine to gain temp root? There is not a temp root for .49 if you unlocked your boot loader previous to the last update you can simply flash a recovery, then flash root.
Sent from my DROID Turbo using XDA-Developers mobile app
I had Unlocked bootloader before update and did'nt re-locked means its still unlocked, but root access is not open now,
mrkhigh yes i want to use it for Temproot as it was giving me root access before.
alia-khan said:
I had Unlocked bootloader before update and did'nt re-locked means its still unlocked, but root access is not open now,
mrkhigh yes i want to use it for Temproot as it was giving me root access before.
Click to expand...
Click to collapse
So as long as you have an unlocked bootloader you can perment root by installing twrp recovery over stock recovery. You will need a computer and have to use a fastboot command but all the instructions can be found here http://forum.xda-developers.com/showpost.php?p=62363432&postcount=2. Hope this helps
mrkhigh said:
Are you just running sunshine to gain temp root? There is not a temp root for .49 if you unlocked your boot loader previous to the last update you can simply flash a recovery, then flash root.
Sent from my DROID Turbo using XDA-Developers mobile app
Click to expand...
Click to collapse
I didn't even think they might only be using Sunshine for temp root only. To me, that's useless. Just go ahead and root, and install TWRP.
But at least their bootloader is unlocked! So, they are good.
Now they know how to go to the next step and permanently root.
Grynch13 said:
So as long as you have an unlocked bootloader you can perment root by installing twrp recovery over stock recovery. You will need a computer and have to use a fastboot command but all the instructions can be found here http://forum.xda-developers.com/showpost.php?p=62363432&postcount=2. Hope this helps
Click to expand...
Click to collapse
Yep, This is the only way as of now due to no temp root. If you had temp root the PC with fast boot would be optional.
Sent from my DROID Turbo using XDA-Developers mobile app
Frist off Im not responsible for anything that happens to your phone!!!
MUST HAVE UNLOCK BOOTLOADER!!
Steps to root
If you are on 11.2.6.6. and rooted
to take update you must flash stock boot.img can be found in link
reboot to bootloader
fastboot flash boot boot11.2.6.6 .img
once done
fastboot reboot
take update
once update is completed
reboot to bootloader
now down load the PATCHEDBOOT.IMG
and flash
fastboot flash boot patched-11.2.7.7.img
once done
fastboot reboot
BOOM NOW YOUR AR ROOTED!!!
STOCK 11.2.6.6 FIXED AND TESTED THANKS TO
mattie_49
LINKS / HELP
BOOT.IMGS
HELP
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I should have read this beforehand but I did it the same way as always. Magisk, restore images, OTA updates, magisk install to inactive slot and I get this and I can't get it to go away and it didn't update either. Root is gone as well but it didn't update.
Edit: it fixed itself after the 3rd attempted update. Lost root but that's an easy. I don't know why it did it. Leaving for anyone else that might have this issue
Josh McGrath said:
View attachment 5335417
I should have read this beforehand but I did it the same way as always. Magisk, restore images, OTA updates, magisk install to inactive slot and I get this and I can't get it to go away and it didn't update either. Root is gone as well but it didn't update.
Edit: it fixed itself after the 3rd attempted update. Lost root but that's an easy. I don't know why it did it. Leaving for anyone else that might have this issue
Click to expand...
Click to collapse
please try new uploaded stock boot imgs there fixed now sorry
so, what I (a newbie to rooting without TWRP) should understand is that if I am on stock I just have to unlock bootloader and flash the patched .img?
FizzyAps said:
please try new uploaded stock boot imgs there fixed now sorry
Click to expand...
Click to collapse
Just updated through updated stock image. Thanks for all your efforts
In my case I have found that it is not necessary to flash the stock boot image in order to update. I simply installed the update, rebooted to bootloader, booted the patched boot.img (not flashed), and installed Magisk to my boot partition from there. That way you don't permanently mismatch your ROM from your boot partition in case you are not using global ROM (which is the case for me). I don't know if the boot partition actually differs between the ROMs but this feels cleaner
Won't let me download the OTA after going back to stock bootloader. I have my CN OP9 cross flashed to global. I keep getting Couldn't Update Installation Problem. Guess i'll wait for Oxygen Update.
notiflux said:
In my case I have found that it is not necessary to flash the stock boot image in order to update. I simply installed the update, rebooted to bootloader, booted the patched boot.img (not flashed), and installed Magisk to my boot partition from there. That way you don't permanently mismatch your ROM from your boot partition in case you are not using global ROM (which is the case for me). I don't know if the boot partition actually differs between the ROMs but this feels cleaner
Click to expand...
Click to collapse
You can't install they update if rooted it errors out
hmmm. im coming from rooted global 255 and I uninstalled magisk, flashed stock 255 and rebooted. tried to update to the partial 277 but it always fail. What am i missing here? maybe the stock 255 that i have is bad?
infamousvincci said:
hmmm. im coming from rooted global 255 and I uninstalled magisk, flashed stock 255 and rebooted. tried to update to the partial 277 but it always fail. What am i missing here? maybe the stock 255 that i have is bad?
Click to expand...
Click to collapse
please click the help link we have untouched stock 11.2.5.5 there
FizzyAps said:
You can't install they update if rooted it errors out
Click to expand...
Click to collapse
if it detects that your device is rooted, it will switch to downloading the full update instead of the incremental one. Maybe it is different on global ROM, but that's what worked for me
Thanks, updated from 11.2.4.4 with the stock boot img i found in the other thread with this guide.