Related
Hello guys. I have a Galaxy S3 (Verizon). Specifically, a SCH-I535. It is running Android 4.3. It has been rooted before, when it had 4.2, but after I did the update, I still have the SU app, but I can't use it because im not rooted. (I think) So hypothetically, say I wanted to install CyanogenMod. Could I? If so, what version? I have Android 4.3. Is it still possible to root? Thanks for any help.
bio4554 said:
Hello guys. I have a Galaxy S3 (Verizon). Specifically, a SCH-I535. It is running Android 4.3. It has been rooted before, when it had 4.2, but after I did the update, I still have the SU app, but I can't use it because im not rooted. (I think) So hypothetically, say I wanted to install CyanogenMod. Could I? If so, what version? I have Android 4.3. Is it still possible to root? Thanks for any help.
Click to expand...
Click to collapse
You can root 4.3 using saferoot, but you cannot flash CyanogenMod or any other AOSP based ROMs. You can only flash 4.3 Touchwiz ROMs using safestrap. You need to be on the ML1 version of 4.3, not the NC1 version. Everything you need to know can be found in the below linked thread:
http://forum.xda-developers.com/showthread.php?t=2639337
landshark68 said:
You can root 4.3 using saferoot, but you cannot flash CyanogenMod or any other AOSP based ROMs. You can only flash 4.3 Touchwiz ROMs using safestrap. You need to be on the ML1 version of 4.3, not the NC1 version. Everything you need to know can be found in the below linked thread:
http://forum.xda-developers.com/showthread.php?t=2639337
Click to expand...
Click to collapse
\
Ok so my next question, how do I tell if I have NC1, or ML1? Also, will this void my warranty? It says Saferoot will not. Sorry, im such a noob.
bio4554 said:
\
Ok so my next question, how do I tell if I have NC1, or ML1? Also, will this void my warranty? It says Saferoot will not. Sorry, im such a noob.
Click to expand...
Click to collapse
Go to your about phone screen and look at your baseband version and build number and see what the last 3 characters are. And your warranty is only good for 1 year from the original date of purchase, which I would assume has long since passed. So I wouldn't worry about this voiding your warranty.
landshark68 said:
Go to your about phone screen and look at your baseband version and build number and see what the last 3 characters are. And your warranty is only good for 1 year from the original date of purchase, which I would assume has long since passed. So I wouldn't worry about this voiding your warranty.
Click to expand...
Click to collapse
Ok thanks so much! I have rooted my phone after flashing ML1, and now I was wondering if I could install CWM Recovery? If so, how? Thanks for all the help.
bio4554 said:
Ok thanks so much! I have rooted my phone after flashing ML1, and now I was wondering if I could install CWM Recovery? If so, how? Thanks for all the help.
Click to expand...
Click to collapse
Check out my first response to you in this thread. You cannot install any kind of custom recovery on ML1. Safestrap is basically your custom recovery. Click on the link in my first response and read up. In the thread I linked you will find a link about Safestrap and a bunch of information you will need.
landshark68 said:
Check out my first response to you in this thread. You cannot install any kind of custom recovery on ML1. Safestrap is basically your custom recovery. Click on the link in my first response and read up. In the thread I linked you will find a link about Safestrap and a bunch of information you will need.
Click to expand...
Click to collapse
Ok, so basically I installed Safestrap, Rooted, and all was well. Then I went and looked for some custom Touchwiz ROMs, and found this one.
CoolROM 8 Core Edition
I downloaded it, created a new ROM slot on Safestrap, flashed it to the phone with safestrap, then rebooted. First off, the Samsung logo that appears right when you turn on, with the open padlock, is gone. For a split second, a white line appears. Then it goes to the Safestrap, I hit continue, it does first boot like normal, and gets stuck on the samsung logo again. "The last one before android appears". I pulled battery, rebooted. Same as first time, except it booted into android. The setup appears, and now another problem pops up. I cant turn on WiFi. It says turned off, I press the toggle button, but it doesnt turn to the ON state. Please help! I really want to use CleanROM!
bio4554 said:
Ok, so basically I installed Safestrap, Rooted, and all was well. Then I went and looked for some custom Touchwiz ROMs, and found this one.
CoolROM 8 Core Edition
I downloaded it, created a new ROM slot on Safestrap, flashed it to the phone with safestrap, then rebooted. First off, the Samsung logo that appears right when you turn on, with the open padlock, is gone. For a split second, a white line appears. Then it goes to the Safestrap, I hit continue, it does first boot like normal, and gets stuck on the samsung logo again. "The last one before android appears". I pulled battery, rebooted. Same as first time, except it booted into android. The setup appears, and now another problem pops up. I cant turn on WiFi. It says turned off, I press the toggle button, but it doesnt turn to the ON state. Please help! I really want to use CleanROM!
Click to expand...
Click to collapse
Look in the OP of the safestrap thread. Every time you flash a ROM though safestrap you have to also flash the kernel modules in the same flashing session in order for WiFi to work.
landshark68 said:
Look in the OP of the safestrap thread. Every time you flash a ROM though safestrap you have to also flash the kernel modules in the same flashing session in order for WiFi to work.
Click to expand...
Click to collapse
Omg thank you so much landshark,you have helped me so much. I now have a rooted S3 with Safestrap, and CleanROM 8.1. Everything is working fine. Now my final question(probably not), is there any possible way at all to unlock the bootloader on this thing? If not, is there anyone working on something like that? If not at all, that's ok. Im still satisfied with it so far. Thanks again. Also, on Safestrap, after I hit continue it has a kind of delay before the boot animation is shown(AKA it starts up). Is there any way to change this?
bio4554 said:
Omg thank you so much landshark,you have helped me so much. I now have a rooted S3 with Safestrap, and CleanROM 8.1. Everything is working fine. Now my final question(probably not), is there any possible way at all to unlock the bootloader on this thing? If not, is there anyone working on something like that? If not at all, that's ok. Im still satisfied with it so far. Thanks again. Also, on Safestrap, after I hit continue it has a kind of delay before the boot animation is shown(AKA it starts up). Is there any way to change this?
Click to expand...
Click to collapse
Not possible at all to unlock the bootloader, you are stuck with it. As far as I know, no one is working on trying to figure out a way to unlock the bootloader. All attempts at finding an exploit to unlock the bootloader have not had any success. The bootloader on the S4 was locked down in the same way before the S3, and that hasn't been cracked yet either.
As far as changing the delay on start up with safestrap, best to ask that question in the safestrap thread as I have never used safestrap and just read the thread to stay informed.
i have installed towelroot and superSu on my verizon to enable root.then i install ROM MANAGER app and flash my phone with clockworld recovery using ROM MANAGER.now when i try to start my phone i got and error.
"“System software not authorized by Verizon Wireless has been found on your phone"
i found a way to bypass this error....by pressing volume up bottun ... now my phone is working but want to resolve this issue...can u help me to sort out this issue.
android 4.4.2 is installed in my device.
thanks
m.asghar59 said:
i have installed towelroot and superSu on my verizon to enable root.then i install ROM MANAGER app and flash my phone with clockworld recovery using ROM MANAGER.now when i try to start my phone i got and error.
"“System software not authorized by Verizon Wireless has been found on your phone"
i found a way to bypass this error....by pressing volume up bottun ... now my phone is working but want to resolve this issue...can u help me to sort out this issue.
android 4.4.2 is installed in my device.
thanks
Click to expand...
Click to collapse
Your on a locked bootloader and you can't flash a custom recovery like cwm, twrp or Philz. You can only install safestrap and run TW(Touchwiz) BL roms
From my CM11 S3
ShapesBlue said:
Your on a locked bootloader and you can't flash a custom recovery like cwm, twrp or Philz. You can only install safestrap and run TW(Touchwiz) BL roms
From my CM11 S3
Click to expand...
Click to collapse
thanks for the reply...can you please guide me how to install .... safestrap and touchwiz roms....can i install 4.4.4 ???
m.asghar59 said:
thanks for the reply...can you please guide me how to install .... safestrap and touchwiz roms....can i install 4.4.4 ???
Click to expand...
Click to collapse
No, you can't run anything but bootloader locked roms. Only what is currently available otherwise you will hard brick your phone
Check out this thread for safestrap
http://forum.xda-developers.com/showthread.php?t=2797314
From my CM11 S3
thanks
ShapesBlue said:
No, you can't run anything but bootloader locked roms. Only what is currently available otherwise you will hard brick your phone
Check out this thread for safestrap
http://forum.xda-developers.com/showthread.php?t=2797314
From my CM11 S3
Click to expand...
Click to collapse
well brother thanks...if i install this .. can i use my existing 4.4.2 ? or need to install new one ?
and kitkat 4.4.2 sucks my battery...which rom is best for s3 verizon....i can install with safestrap ???
m.asghar59 said:
and kitkat 4.4.2 sucks my battery...which rom is best for s3 verizon....i can install with safestrap ???
Click to expand...
Click to collapse
You have to decide which ones the best for you. I can't tell you which one is better as I'm not on a locked bootloader. You have to choose for yourself
From my CM11 S3
ShapesBlue said:
You have to decide which ones the best for you. I can't tell you which one is better as I'm not on a locked bootloader. You have to choose for yourself
From my CM11 S3
Click to expand...
Click to collapse
Does CM11 work with Safestrap/Locked Bootloader? The Safestrap thread only shows superliterom are there any others?
Bzy said:
Does CM11 work with Safestrap/Locked Bootloader? The Safestrap thread only shows superliterom are there any others?
Click to expand...
Click to collapse
No CM11 or any aosp roms. Look around the forums, VZW android development and original android development and look for locked bootloader roms
From my CM11 S3
ShapesBlue said:
No CM11 or any aosp roms. Look around the forums, VZW android development and original android development and look for locked bootloader roms
From my CM11 S3
Click to expand...
Click to collapse
So I've been trying my best to learn this stuff from reading EVERYTHING I can, but this is very difficult to get in to from no rooting experience. This Thread shows CM11 for 4.4.4 which I just assumed was an updated 4.4.2 meaning it worked since the thread doesn't say anywhere in the OP that you can't install on a locked bootloader. Is there some other obvious terminology that I'm missing? (realizing it's common knowledge to the community but I don't have this)
So it's very difficult for me discern what other ROM options there actually are.
Bzy said:
So I've been trying my best to learn this stuff from reading EVERYTHING I can, but this is very difficult to get in to from no rooting experience. This Thread shows CM11 for 4.4.4 which I just assumed was an updated 4.4.2 meaning it worked since the thread doesn't say anywhere in the OP that you can't install on a locked bootloader. Is there some other obvious terminology that I'm missing? (realizing it's common knowledge to the community but I don't have this)
So it's very difficult for me discern what other ROM options there actually are.
Click to expand...
Click to collapse
The OP only mentions cwm in that thread and being that you can't run cwm, philz or twrp on a locked bootloader none of that applies. It's verizon who chose to lock the bootloader down as they do on nearly every phone they sell with the exception of the G3 and M8, which devs managed to crack both bootloaders on those
Sometimes it may not always be right where you can find it and a lot of people including a former developer hard bricked his S3 on the first locked bootloader with 4.3 ML1 and has since moved on from the S3 for obvious reasons. When your not sure about something don't be afraid to ask questions. And I commend you for reading first before doing anything. And while yes technically 4.4.4 is an upgrade to 4.4.2 you won't be able to run the newest CM11 On a locked bootloader. The last bootloader that was unlock able was 4.1.2 and if you went beyond that you were basically stuck
From my CM11 S3
ShapesBlue said:
The OP only mentions cwm in that thread and being that you can't run cwm, philz or twrp on a locked bootloader none of that applies.
Click to expand...
Click to collapse
Makes sense, but these are things that I'm still learning and that's why I was confused. I know to keep my eyes peeled for AOSP as a buzzword. I think what throws me off the most is the 4.4.4 in the thread title.
On a separate note, my preference is to activate the phone after I've rooted/installed ROMs such that I have a working (different) phone while I take my time going through the steps. I am nervous that if I activate after I will have issues and then have to bring the phone in for activation which I can't do once rooted.
Bzy said:
Makes sense, but these are things that I'm still learning and that's why I was confused. I know to keep my eyes peeled for AOSP as a buzzword. I think what throws me off the most is the 4.4.4 in the thread title.
On a separate note, my preference is to activate the phone after I've rooted/installed ROMs such that I have a working (different) phone while I take my time going through the steps. I am nervous that if I activate after I will have issues and then have to bring the phone in for activation which I can't do once rooted.
Click to expand...
Click to collapse
There's always a way to unroot devices. I wouldn't worry too much about it
From my CM11 S3
ShapesBlue said:
There's always a way to unroot devices. I wouldn't worry too much about it
From my CM11 S3
Click to expand...
Click to collapse
Ok Thanks. One other thing is about an external SD card. Do I need to get one and do I need to install which specific things directly to it instead of the internal and is there any special way to set that up?
Bzy said:
Ok Thanks. One other thing is about an external SD card. Do I need to get one and do I need to install which specific things directly to it instead of the internal and is there any special way to set that up?
Click to expand...
Click to collapse
Are you referring to putting apps on the SD card?
From my CM11 S3
thanks for this usefull information bro just want to ask one last question.i want to flash "SUPERLITEROM!_V1.0_I535VRUDNE1" .. my question is this i am using this phone in pakistan....my networks remain unlock .. means i can use GSM/3g network ????
sorry i am new so no idea about all these stuff
ShapesBlue said:
Are you referring to putting apps on the SD card?
From my CM11 S3
Click to expand...
Click to collapse
The Superliterom thread says "Copy .zip on ext. sdcard." and made me paranoid that certain things have to be done on the external SD card, is that not the case?
Bzy said:
So I've been trying my best to learn this stuff from reading EVERYTHING I can, but this is very difficult to get in to from no rooting experience. This Thread shows CM11 for 4.4.4 which I just assumed was an updated 4.4.2 meaning it worked since the thread doesn't say anywhere in the OP that you can't install on a locked bootloader. Is there some other obvious terminology that I'm missing? (realizing it's common knowledge to the community but I don't have this)
So it's very difficult for me discern what other ROM options there actually are.
Click to expand...
Click to collapse
That 4.4.4 is AOSP and actually came out before the phone officially had 4.4.2 Touchwiz. You simply have to remember that on a locked bootloader using safestrap, you cannot flash any AOSP based ROMs which includes CM11. You are limited to the Touchwiz based ROMs which are of the same Android version your phone is on currently. For this phone, that means 4.4.2, which I think there are only one or two ROMs available.
landshark68 said:
That 4.4.4 is AOSP and actually came out before the phone officially had 4.4.2 Touchwiz. You simply have to remember that on a locked bootloader using safestrap, you cannot flash any AOSP based ROMs which includes CM11. You are limited to the Touchwiz based ROMs which are of the same Android version your phone is on currently. For this phone, that means 4.4.2, which I think there are only one or two ROMs available.
Click to expand...
Click to collapse
Do I not require an external SD card?
Bzy said:
Do I not require an external SD card?
Click to expand...
Click to collapse
You can use one if you'd like to. That's your own choice
From my CM11 S3
So I have a new shield tablet on the way, in the mail. I'm not sure yet if it will be sent to me on Lollipop or KitKat. It is the 32 gig, LTE variant.
If it is on KitKat, is it best to root it on KK and stay there or should I take the OTA up to Lollipop and then root it from there? Is the best bet to root and stay stock or should I look at some of the roms available? Have people found that the tablet handles emulators well like Reicast, FPSE and more?
If you want root your best bet is to unlock the bootloader. This can be done on kitkat or lollipop.
Sent from my SHIELD Tablet using Tapatalk
T-Keith said:
If you want root your best bet is to unlock the bootloader. This can be done on kitkat or lollipop.
Sent from my SHIELD Tablet using Tapatalk
Click to expand...
Click to collapse
Is it done via the typical fastboot and then oem unlock?
Edit- http://forum.xda-developers.com/showthread.php?t=2399737
Yup. Typical bootloader unlock. Is there a preferred recovery most people like for the tablet? I know for one of my old phones (Rezound), you could use a few but devs preferred usually 1 out of the many. CWM is the way to go for us?
Lollipop root is independent of having root on KitKat or not. As of right now the only way to root is to unlock the bootloader, flash a temporary/permanent custom recovery and then flash the SuperSU. Being that the bootloader wipes the device I recommend doing it before you dig too into the tablet and load it up. Follow this guide and you should be golden ponyboy http://forum.xda-developers.com/shield-tablet/development/root-root-lollipop-t2945044
Or if the tablet already has Lollipop on it then follow these instructions. http://forum.xda-developers.com/showpost.php?p=56888108&postcount=23
The LTE version will come with kk. They haven't pushed lollipop to the LTE version yet as it's pending carrier certification. I rooted and flashed recovery all without unlocking the bootloader. I followed the lollipop root instructions in the dev section. First you root kk, install recovery, flash the ota zip, flash the su zip, flash the rooted boot image then reflash custom recovery if you want. Im now running lollipop rooted with clockwork installed and my bootloader is still locked(follow the locked bootloader root instructions in that thread)
http://forum.xda-developers.com/showthread.php?t=2945044
[ROOT] Root for SHIELD Tablet 2.0 (Lollipop)
graffixnyc said:
The LTE version will come with kk. They haven't pushed lollipop to the LTE version yet as it's pending carrier certification. I rooted and flashed recovery all without unlocking the bootloader. I followed the lollipop root instructions in the dev section. First you root kk, install recovery, flash the ota zip, flash the su zip, flash the rooted boot image then reflash custom recovery if you want. Im now running lollipop rooted with clockwork installed and my bootloader is still locked(follow the locked bootloader root instructions in that thread)
http://forum.xda-developers.com/showthread.php?t=2945044
[ROOT] Root for SHIELD Tablet 2.0 (Lollipop)
Click to expand...
Click to collapse
So you took yours up to Lollipop manually because the LTE version doesn't have the carrier approval yet?
Does lollipop introduce any headaches or anything to be aware of in comparison to KK? The tablet did get cleared for Grid correct?
NapalmDawn said:
So you took yours up to Lollipop manually because the LTE version doesn't have the carrier approval yet?
Does lollipop introduce any headaches or anything to be aware of in comparison to KK? The tablet did get cleared for Grid correct?
Click to expand...
Click to collapse
Yeah I flashed it manually. Honesty, I can't tell you if it brings problems compared to KK.. haha I got the tablet yesterday and as soon as I powered it on I started updating and rooing it so I was only in KK for a few minutes so the only experience I really have with the tablet is on lollipop
NapalmDawn said:
Is it done via the typical fastboot and then oem unlock?
Edit- http://forum.xda-developers.com/showthread.php?t=2399737
Yup. Typical bootloader unlock. Is there a preferred recovery most people like for the tablet? I know for one of my old phones (Rezound), you could use a few but devs preferred usually 1 out of the many. CWM is the way to go for us?
Click to expand...
Click to collapse
I really prefer Philz. I love TWRP but I don't think there's a working TWRP recovery for the Shield tablet yet.
graffixnyc said:
Yeah I flashed it manually. Honesty, I can't tell you if it brings problems compared to KK.. haha I got the tablet yesterday and as soon as I powered it on I started updating and rooing it so I was only in KK for a few minutes so the only experience I really have with the tablet is on lollipop
Click to expand...
Click to collapse
I will plan to do the same. I'm going to unlock/root it before I do any work on it so I don't lose anything during the wipes. Does the tablet handle emulators well like FPS and Reicast? My guess is their performance would be phenomenal on this device.
Just of the lollipop update not too major a problem, battery life seems a little bit worse for me....but I have a question what is that star icon beside my WiFi bar? Idk how to take a screenshot sorry I just got the tablet
butch87402 said:
Just of the lollipop update not too major a problem, battery life seems a little bit worse for me....but I have a question what is that star icon beside my WiFi bar? Idk how to take a screenshot sorry I just got the tablet
Click to expand...
Click to collapse
Star means that you put the tablet into Priority mode - only notifications that you deem as priority will alert you.
Just wondering if anyone has any insight on SU6-7.7 on the Droid line? Whether or not anyone know or hear anything about downgrading to a different SU version? I have the firmware file for the latest SU6-7.7 in case anyone wants it.
https://drive.google.com/open?id=0B7hPMTc_G5VPMFVqZmdMSXJEbjA
It would be nice if Motorola/Lenovo would let us do what we want with a phone they no longer "support".
Thanks, I was looking for this.
RichardCA said:
Thanks, I was looking for this.
Click to expand...
Click to collapse
Sure thing! Let me know if you need anything else!
SalmanJohnson2011 said:
Sure thing! Let me know if you need anything else!
Click to expand...
Click to collapse
OK, since you asked...
On a Motorola phones that still have their stock, factory install intact, they do this clever thing where they cycle between a few different boot logo's, with slightly different colors in the Motorola logo on each boot.
Is there any way to replicate that after you're unlocked?
RichardCA said:
OK, since you asked...
On a Motorola phones that still have their stock, factory install intact, they do this clever thing where they cycle between a few different boot logo's, with slightly different colors in the Motorola logo on each boot.
Is there any way to replicate that after you're unlocked?
Click to expand...
Click to collapse
I believe that you can replace the stock boot logo with an unlocked or locked bootloader. There are a quite a few logos to choose from. When you pick one, you fastboot the image.
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
RichardCA said:
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
Click to expand...
Click to collapse
Not sure at the moment. XD I'll reply back to this post or PM you if I do. Thanks again! If you have any more info, please let me know!
RichardCA said:
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
Click to expand...
Click to collapse
When you flashed it to your mini/ultra, where you on SU6-7.7?
SalmanJohnson2011 said:
When you flashed it to your mini/ultra, where you on SU6-7.7?
Click to expand...
Click to collapse
I jumped around a lot. I was playing with marshmallow and lollipop builds and needed to revert back. But I was on the Motorola stock SU4.21 when I flashed it.
I used the process on this page, and got zero errors:
http://forum.xda-developers.com/showthread.php?t=2580060
Help please!!!
Hi everyone im not so good at rooting and fllashing ect ect. iv done it before but always watching youtube videos lol. so i have the droid mini now its a verizon carrier unlocked with android 4.4.4 SU6.7.7 and i would like to install CM so i can customize my phone more also want to get rid of all the bloatware if anyone could please let me knoe if its possible and walk me through this i would really apreciate it!! Thanks in advance :fingers-crossed:
edgar1994 said:
Hi everyone im not so good at rooting and fllashing ect ect. iv done it before but always watching youtube videos lol. so i have the droid mini now its a verizon carrier unlocked with android 4.4.4 SU6.7.7 and i would like to install CM so i can customize my phone more also want to get rid of all the bloatware if anyone could please let me knoe if its possible and walk me through this i would really apreciate it!! Thanks in advance :fingers-crossed:
Click to expand...
Click to collapse
To my knowledge, I don't think you can install custom roms once you install the latest SU update. Beings that you're on SU6-7.7 like me, there's not much you can do until someone comes out with another exploit.
Can I revert to su6-7 after having su6-7.7 update? I could do that after su6-7.3 update though.
ashal said:
Can I revert to su6-7 after having su6-7.7 update? I could do that after su6-7.3 update though.
Click to expand...
Click to collapse
Nope. I've tried and it doesn't work.
SalmanJohnson2011 said:
To my knowledge, I don't think you can install custom roms once you install the latest SU update. Beings that you're on SU6-7.7 like me, there's not much you can do until someone comes out with another exploit.
Click to expand...
Click to collapse
Man this really sucks i hope someone finds a way around this :crying:
edgar1994 said:
Man this really sucks i hope someone finds a way around this :crying:
Click to expand...
Click to collapse
I Agreed dude. I'm with you! I don't know why I keep getting Verizon phones. XD Regardless of what I learned. Haha
SalmanJohnson2011 said:
Nope. I've tried and it doesn't work.
Click to expand...
Click to collapse
Did you try downgrading directly from SU6-7.7 to SU6-7 or you went like SU6-7.7 to 7.3 to 7.2 to SU6-7?
Because for SU6-7.3 I downgraded one by one.
ashal said:
Did you try downgrading directly from SU6-7.7 to SU6-7 or you went like SU6-7.7 to 7.3 to 7.2 to SU6-7?
Because for SU6-7.3 I downgraded one by one.
Click to expand...
Click to collapse
For me, I tried going down one update at a time and it still doesn't work.
it says devoloper phones only
can I flash to my ultra even tho its not a dev phone??
RichardCA said:
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
Click to expand...
Click to collapse
In case this helps anyone: I recently updated to SU6-7.7 from SU4.21 following the guidance in this thread and referenced resources on a XT1030 (Moto Mini). Initially I tried to get cute and only flashed the system image and modem upgrades; was rewarded with a bootloader loop that did not resolve after a full TWRP restore of the previous build. Next take including everything in the zip except boot.img and recovery.img as my device is unlocked and wasn't sure if flashing boot.img would relock the bootloader. Also wanted to maintain a true recovery. Everything worked fine except the WiFi radio which refused to engage (Bluetooth was ok). After a bit of fiddling dropped back to fastboot and flashed boot.img. Device restarted just fine with bootloader remaining unlocked. Whohoo! I should also note the all of the above was a 'dirty flash'. Never erased the userdata partition; all apps came back just fine. Oh yeah, had to reflash SuperSU but that's pretty standard after a system wipe.
Thanks to all the key contributors in this thread and elsewhere in the forum. After some miserable bootloops a couple years back (foolishly accepted VZW OTA) I froze the rom and vowed never to update it. It's nice to be running the terminal release of KitKat for this device which as several stability/usability features baked in along with the usual security updates (now dated but better than 2014!). I had considered CM 12.1 and CM 13 but needed fully hardware functionality that only seems to come with stock builds.
root successful
Davey126 said:
In case this helps anyone: I recently updated to SU6-7.7 from SU4.21 following the guidance in this thread and referenced resources on a XT1030 (Moto Mini). Initially I tried to get cute and only flashed the system image and modem upgrades; was rewarded with a bootloader loop that did not resolve after a full TWRP restore of the previous build. Next take including everything in the zip except boot.img and recovery.img as my device is unlocked and wasn't sure if flashing boot.img would relock the bootloader. Also wanted to maintain a true recovery. Everything worked fine except the WiFi radio which refused to engage (Bluetooth was ok). After a bit of fiddling dropped back to fastboot and flashed boot.img. Device restarted just fine with bootloader remaining unlocked. Whohoo! I should also note the all of the above was a 'dirty flash'. Never erased the userdata partition; all apps came back just fine. Oh yeah, had to reflash SuperSU but that's pretty standard after a system wipe.
Thanks to all the key contributors in this thread and elsewhere in the forum. After some miserable bootloops a couple years back (foolishly accepted VZW OTA) I froze the rom and vowed never to update it. It's nice to be running the terminal release of KitKat for this device which as several stability/usability features baked in along with the usual security updates (now dated but better than 2014!). I had considered CM 12.1 and CM 13 but needed fully hardware functionality that only seems to come with stock builds.
Click to expand...
Click to collapse
Dear i have successfully rooted mine droid mini su6-7.7 with kingo root (not global) v3.4 successfully now i have superuser app in system directory
---------- Post added at 05:42 AM ---------- Previous post was at 05:20 AM ----------
Dear friends i have successfully root mini droid mini su6-7.7 with kingo root v3.4 (not kingo root global). actually i was trying to flash su4.21 over su6-7.7 with RSD lite v6.1 but failed with max get var and after that tried to flash with RSD lite 5.1 again failed without any error. after all of there method i thought of giving a try to kingo root. i downloaded 2 apps kingo root globalv4.9.7 and kingo root v3.4, kingo root global failed to root but.... kingo root v3.4 succeeded to roo. now i have superuser app in system driectory.
but problem is that after removing system app (amazon) when i restarted the phone all the apps came back and superuser app gone. i don't know why so my request to look into this method .
i have tested this method and worked 100% and i have no intention of making fun of me. i have both the apps but don't know how to upload here
Thanks
This guide is to help out the people who are rooted to know exactly what to do if you get an OTA notification so that there are no errors.
This guide will only work for the Systemless rooting. Guide here
The basic things for achieving OTA after rooting can be found here
Basic things to keep in mind if:
1. Still on soak - Follow this guide and come back to marshmallow and then you should be able to take the OTA.
2. If you are on Stock and rooted - Make a nandroid backup and then the next step is pretty simple, go to SuperSU app and click on the option Full Unroot and click on yes and then again yes and wait for the Phone to reboot. Once it starts back wait for the optimization of the Apps and then download the OTA and then install it. Make sure it is the Stock recovery through which you flash the OTA.
It should go through Smoothly. I have done it twice. Since Nougat doesn't support any known root method yet, so keeping a titanium backup before unrooting is preferred so that as soon as it supports root u can restore all of it back.
Happy updating!
I personally won't install N until we have a rooting method. Because there is no "coming back" if root doesn't materialize.
SoNic67 said:
I personally won't install N until we have a rooting method. Because there is no "coming back" if root doesn't materialize.
Click to expand...
Click to collapse
That's true! But it'll be just a matter of time before we get it!
SoNic67 said:
I personally won't install N until we have a rooting method. Because there is no "coming back" if root doesn't materialize.
Click to expand...
Click to collapse
I have downgraded using my tutorial. And i told you that the firmware that i posted is official...
http://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961
TechBurner said:
I have downgraded using my tutorial. And i told you that the firmware that i posted is official...
http://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961
Click to expand...
Click to collapse
I don't know but XT1643, doesn't come out of the box MPJ24.139-13.1.... it comes out with 23.1 i guess...
That guide did work perfectly!
abhi212b said:
I don't know but XT1643, doesn't come out of the box MPJ24.139-13.1.... it comes out with 23.1 i guess...
That guide did work perfectly!
Click to expand...
Click to collapse
I know that works perfectly right now, the only reason i made the tutorial on how to downgrade is because we had the same scenario for Moto g 1st gen. People got used to downgrading using the normal method, what they didnt realize was that the bootloader and gpt were not being flashed and they showed failed when you did that for the official firmware. But after a month tons of Moto g 1st gens got hard bricked because of that. Anyone who tried to downgrade from modified stock or custom rom based on Lollipop (At that time) Got their phone hard bricked. It's the same for Nougat also and is same for All cross android versions after Kitkat.
With every new update they release a new partition table and a new bootloader . The new bootloader doesnt allow you to flash the previous bootloaders over it and same for partition but for some varients of the phone the warning is not there and the older bootloader is flashed resulting in a hard brick. This is also true for Custom roms based on the official firmware (which will come) and devices in which a custom kernel has been flashed.
I am not saying trust me, i am just saying be careful .
^ That's what I meant when I said "no coming back". You are stuck with a N bootloader and a MM firmware. Might work fine, might not.
Quick question
I have a XT1643
On stock rooted rom with elemental kernel.
Got an update notification yesterday.
I flashed the stock boot.img I found on the forum but the wifi is not working after flashing that.
what do I need to do in order to get it working and get the update?
Thanks
SoNic67 said:
^ That's what I meant when I said "no coming back". You are stuck with a N bootloader and a MM firmware. Might work fine, might not.
Click to expand...
Click to collapse
I agree with you on this. I am stuck with an N Bootloader and and MM firmware.
I can upgrade to an N ROM but I get FP issues (cosmetic, but still not desirable)
I cannot take an official OTA anymore because even if I downgrade to stock, I still have an N Bootloader which prevents me from taking OTA.
Unless we get a stock N rom, I guess we are stuck with this setup.
Sent from my Moto G (4) using Tapatalk
SoNic67 said:
^ That's what I meant when I said "no coming back". You are stuck with a N bootloader and a MM firmware. Might work fine, might not.
Click to expand...
Click to collapse
It will i guess because then again u can take an OTA to N ...
tandon.ayush said:
Quick question
I have a XT1643
On stock rooted rom with elemental kernel.
Got an update notification yesterday.
I flashed the stock boot.img I found on the forum but the wifi is not working after flashing that.
what do I need to do in order to get it working and get the update?
Thanks
Click to expand...
Click to collapse
Everything needs to be on stock! Stock boot, recovery, logo, kernel etc. then it works ! any modifications will lead to an error!