Related
Hi does anyone know where I can find the stock recovery for the nexus 5? I have not found him namely: (
There's a thread in general with a link to all recoveries including stock
Sent from my Nexus 5 using Tapatalk
APP-Maker said:
Hi does anyone know where I can find the stock recovery for the nexus 5? I have not found him namely: (
Click to expand...
Click to collapse
Google recovery zip collection xda
http://forum.xda-developers.com/showthread.php?t=2513701
Scroll to method 2 and download the recovery
APP-Maker said:
Hi does anyone know where I can find the stock recovery for the nexus 5? I have not found him namely: (
Click to expand...
Click to collapse
If you go to Google's page for "Factory Images for Nexus Devices" then you can download a script which will install the official stock image, this will also give you the latest baseband (currently version M8974A-1.0.25.0.23 I think) but you should have that already if you ever did the official 4.4.1 or 4.4.2 stock OTA update, you can check your baseband version in fastboot.
Charlular said:
If you Google's page for "Factory Images for Nexus Devices" then you can download a script which will install the official stock image, this will also give you the latest baseband (currently version M8974A-1.0.25.0.23 I think) but you should have that already if you ever did the official 4.4.1 or 4.4.2 stock OTA update, you can check your baseband version in fastboot. I'd link to the page I mentioned earlier but I can only link once I have made ten posts.
Click to expand...
Click to collapse
Dude, he's looking for the recovery not the whole factory image. One will wipe your whole device, the other won't. If you're looking for your 10 posts there's better ways to do it
jd1639 said:
Dude, he's looking for the recovery not the whole factory image. One will wipe your whole device, the other won't. If you're looking for your 10 posts there's better ways to do it
Click to expand...
Click to collapse
Well if they want the stock recovery then it's likely that they want stock Android too. They may also prefer to use an official script from Google or may have been unaware of the updated baseband and may want it, don't be angry at me for suggesting completely legitimate alternatives.
Charlular said:
Well if they want the stock recovery then it's likely that they want stock Android too. He may also prefer to use an official script from Google or may have been unaware of the updated baseband and may want it, don't be angry at me for suggesting completely legitimate alternatives.
Click to expand...
Click to collapse
Not angry, just like to see productive ways to get a post count up. I'd suggest reading the pinned, stickies, threads in the general section to learn as much as you can about your device. Then ask questions there if you have any.
Easily Switch Between JB/KK/LP Bootloader
!! d800 ONLY !!
Make sure you flash the right model!
With the advent of BUMP, we can now use the KK bootloader. A lot of projects preserved the old JB bootloader, since that was needed due to loki. This is the easy way to update your JB bootloader to the new KK bootloader.
Inspired by @dorimanx who did this for the d802. I followed suit and made this for the d800.
What this is:
As it simply says, it upgrades (or downgrades) the bootloader. This includes several other small partitions, in addition to aboot and sbl1.
Sources:
10d & 20c - Extracted from TOT file
20y & 30f - I started with 20d, then did FOTA to 20y and extracted the partitions. Then I did FOTA to 30f and again extracted the partitions.
What this is NOT:
This does not touch your boot, recovery, or modem/radio partitions. You must make sure those are compatible BEFORE flashing this.
WARNING: You can easily brick your phone if you mess this up! This is for d800 ONLY!!! Also, you must have BUMPed boot and recovery images already on your phone to use KK bootloader or you will get fastboot error (or it just won't boot). JB supports BUMP images and LOKI images. KK only supports BUMP.
Lollipop Information:
Special LOLLIPOP WARNING: At this time, the Lollipop BL is not exploitable. Therefore, if you flash Stock LP BL, you will probably brick, or at a minimum, you will lose access to recovery.
To use a BUMPED lollipop ROM, you should install the Lollipop Bump bootstack on my site. It is all of the 30f Lollipop partitions, with a 20y aboot (so bump will work).
Download:
Did you read the warning above? If not, DO NOT DOWNLOAD.
Did you read it twice? If not, DO NOT DOWNLOAD.
Do you understand everything it says? If not, DO NOT DOWNLOAD.
Do you know how to recover if you mess your phone up? If not, DO NOT DOWNLOAD.
I do not want any posts saying "HALP I MESSED THIS UP."
Which bootloader am I currently on?
The only sure way to know is to flash one, or know which one you flashed last.
You can get an idea of your bl when you use the button combo to enter recovery (VolDwn+Pwr, release and repress when LG logo comes up, hold until menu comes up) the screen looks different. On JB the phone asks you to repeatedly press power for factory reset. On KK the phone has you use the volume rocker to pick different menu options.
Download:
https://www.gregtwallace.com/lg-g2/d800_d801-bootloaders/
Again, thanks to @dorimanx.
Shameless plug for donations:
Venmo Preferred (No Fee)
Zelle, send to [email protected]
Backup (Charges Fee)
Paypal
Update 2015.07.29
-Version 1.1 does NOT flash misc partition.
+Misc contains things like MAC addresses and doesn't need to be flashed.
Update 2015.05.12
I have added the 20y KK bootloader, which appears to be different than the originally posted 20c. Both are now posted.
Additionally, I added the LP 30f bootloader. WARNING: This bootloader is not (yet?) exploitable! Flashing it will likely brick your device, or at the very least it will break your recovery. You have been warned!
Reserved2
Reserved2
Cool thing! And nice work! I was just looking around to learn more stuff about bootloaders ..did dorimanx made a thread for d802?
Your awesome version of TWRP is bumped, dorimanxs kernel is bumped too thats all i need to switch on kk bootloader
raulx222 said:
Cool thing! And nice work! I was just looking around to learn more stuff about bootloaders ..did dorimanx made a thread for d802?
Your awesome version of TWRP is bumped, dorimanxs kernel is bumped too thats all i need to switch on kk bootloader
Click to expand...
Click to collapse
No he didn't, but he posted the d802 version under his kernel thread, which is linked in my signature.
Great initiative, @blastagator!
Now... On to the actual bootloader... stuff.
EDIT : Nevermind. Just noticed that this is for the D800 only... and I have a D802, lol.
You, sir, are a badass. Thank you for this
Sent from my LG-D800 using XDA Free mobile app
Formhault said:
Great initiative, @blastagator!
Now... On to the actual bootloader... stuff.
EDIT : Nevermind. Just noticed that this is for the D800 only... and I have a D802, lol.
Click to expand...
Click to collapse
As stated in the OP, dorimanx made exactly the same zip for the d802 to update the bootloader and the other necessary partitions.
You'll just need a bumped recovery + bumped kernel.
Just in case you would like to upgrade to KK bootloader
I'm just waiting for render to release bumped R26 and the first thing I'll do is update the bootloader
Could someone please be kind enough to make one for vs980? I tried making one myself by picking the same exact files off of vs980 kdz but it didn't work.
Voltaine said:
I'm just waiting for render to release bumped R26 and the first thing I'll do is update the bootloader
Click to expand...
Click to collapse
Me too, I guess :silly:
idoluvizsick said:
Could someone please be kind enough to make one for vs980? I tried making one myself by picking the same exact files off of vs980 kdz but it didn't work.
Click to expand...
Click to collapse
I used this: http://forum.xda-developers.com/showthread.php?t=2600575
Extract the partitions out of the stock tot, then just use a simple flash script. Again, if you don't know what you're doing - it is VERY easy to mess up and DIFFICULT to recover from.
Noticing this says bumped boot and recovery required in the op. Was wondering even if I'm on stock everything, boot included, do I still need to be bumped. I would say yes on the recovery due to the nature of how autorec worked. But what about boot, since it is bone stock? Thanks for the info. Thanks for your work on this phone.
Yikes I tried this with 12/5 AICP 5.0 drgravy d800, Render5, and blastagators bumped TWRP 2.8.2.0.
Installed the KK-20C bootloader, the device spent a long time on on the LG logo with a few vibrates, then it blackscreened. While blackscreened plugging into PC started charging and gave me access to Internal Storage. Tried a power off and back on again with same result.
Luckily, manually going into TWRP and flashing the JB-10D bootloader got things back to normal.
EDIT: Just dawned on me that I had the dr87 Working Rotation JB Baseband installed. Perhaps I should have tried with the KK Baseband?
buffal0b1ll said:
Yikes I tried this with 12/5 AICP 5.0 drgravy d800, Render5, and blastagators bumped TWRP 2.8.2.0.
Installed the KK-20C bootloader, the device spent a long time on on the LG logo with a few vibrates, then it blackscreened. While blackscreened plugging into PC started charging and gave me access to Internal Storage. Tried a power off and back on again with same result.
Luckily, manually going into TWRP and flashing the JB-10D bootloader got things back to normal.
EDIT: Just dawned on me that I had the dr87 Working Rotation JB Baseband installed. Perhaps I should have tried with the KK Baseband?
Click to expand...
Click to collapse
I don't think it works with JB based kernels.
sr20ryda said:
I don't think it works with JB based kernels.
Click to expand...
Click to collapse
I used Render 5 which is a L Kernel. Is this JB based?
buffal0b1ll said:
I used Render 5 which is a L Kernel. Is this JB based?
Click to expand...
Click to collapse
Yes. All the LP builds have JB based kernels AFAIK.
sr20ryda said:
Yes.
Click to expand...
Click to collapse
Is there a bumped kernel that d800 can use on L with KK bootloader then?
I don't believe so.
It works only with dorimanx on stock based rom, no cm aosp aicp et
_____________________________Write less read more and be smart
siggey said:
It works only with dorimanx on stock based rom, no cm aosp aicp et
_____________________________Write less read more and be smart
Click to expand...
Click to collapse
After reading ALOT of info heres where i am. I think our good guy render is trying to get his kernel working bumped for KK bootloader and lollipop builds.. heres where i got sad.
It seems recently there is ALOT of dev arguements on the nature of opensource bump so much so that the the orginators have actually closed down and stopped development on the project. lets not go any further with that disucssion, there are other threads for that if you care to read.
So basically i dont have a build environment right now to try to bump any kernels using the instructions and I'm not sure what to think right now considering what i HAVE read. I actually stay away from posting alot of things on XDA that i do on my own, because of this very nature i have seen pop up to many times to count. So to summerize:
Dont have a build environment where i am right now to try...even when i get home im not sure how i will feel since i do respect the codefire guys but understand why someone would have done what they did. If i am successful getting someone elses work say renders kernel, to finally boot ill let him know but im sure render will figure it before i even do that :highfive:
Dump of Stock Partitions
Lollipop d800-30f
Since we don't have a d80030f KDZ or TOT yet, I decided I would try to do the next best thing. I did a back to factory 20c -> 20y -> 30f upgrade progression. Then I did a factory reset, followed by one click root. Then I dumped all of the partitions that are normally part of the KDZ.
The zip includes Stock 30f images of:
aboot
dbi
laf
misc (removed, not needed - specific to each phone)
persist
rpm
sbl1
tz
I have the modem partition, which will get its own zip and its own post. (http://forum.xda-developers.com/att-g2/development/modems-att-stock-modems-t3106221)
I also dumped system, but it is huge. Please don't download it if you're not a ROM maker (it'll make Google mad at me): https://drive.google.com/folderview...NEb0dUVlpQenhrOHZsaGYyQ3ZiOGV0LWM&usp=sharing
Download:
https://www.gregtwallace.com/lg-g2/d800_d801-bootloaders/
-Bootloader stack is under the bootloader section.
Shameless plug for donations:
Venmo Preferred (No Fee)
Zelle, send to [email protected]
Backup (Charges Fee)
Paypal
-Empty-
Good. If you post are system, there all I needed to go to the lp?
qweewq22 said:
Good. If you post are system, there all I needed to go to the lp?
Click to expand...
Click to collapse
I'm not posting it for that. Use OTA if you want stock lollipop.
blastagator said:
I'm not posting it for that. Use OTA if you want stock lollipop.
Click to expand...
Click to collapse
can u give me the stock d800 framework-res.apk? i flashed a wrong one and i have a bootloop
Abrilabr said:
can u give me the stock d800 framework-res.apk? i flashed a wrong one and i have a bootloop
Click to expand...
Click to collapse
Here ya go.
Flashable zip of the whole ROM will be soon (probably work on it tonight).
@blastgator, what will be the difference between your flashable zip and the stock OTA, other than the fact that it's a zip? Also, do you find it preferable to use stock LP on our device vs BlissPop or other 5.1.1 ROMs? I spend a lot of time and computing power building nightlies, want to know if it's pointless. I don't think so, but now that we have LP, I needed to ask you. PMing you!
berryman13 said:
@blastgator, what will be the difference between your flashable zip and the stock OTA, other than the fact that it's a zip? Also, do you find it preferable to use stock LP on our device vs BlissPop or other 5.1.1 ROMs? I spend a lot of time and computing power building nightlies, want to know if it's pointless. I don't think so, but now that we have LP, I needed to ask you. PMing you!
Click to expand...
Click to collapse
I still run KK. I am just doing some of this stuff to get ready for the upcoming move. I was going to start looking into ROM creation, based on stock ROM (since we don't really have any at this point).
Therefore, I don't really know the answer to your question - "is it worth it?"
And yes, the zip is just what I recovered after doing the FOTA. Much easier grabbing these instead of having to flash 20c and then force 2x FOTAs.
berryman13 said:
@blastgator, what will be the difference between your flashable zip and the stock OTA, other than the fact that it's a zip? Also, do you find it preferable to use stock LP on our device vs BlissPop or other 5.1.1 ROMs? I spend a lot of time and computing power building nightlies, want to know if it's pointless. I don't think so, but now that we have LP, I needed to ask you. PMing you!
Click to expand...
Click to collapse
blastagator said:
I still run KK. I am just doing some of this stuff to get ready for the upcoming move. I was going to start looking into ROM creation, based on stock ROM (since we don't really have any at this point).
Therefore, I don't really know the answer to your question - "is it worth it?"
And yes, the zip is just what I recovered after doing the FOTA. Much easier grabbing these instead of having to flash 20c and then force 2x FOTAs.
Click to expand...
Click to collapse
that's exactly what i was going to say, i don't use blisspop, i don't like custom roms, i prefer stock experience and i cant upgrade since im not on AT&T network, and what he is doing is exactly what i (and many others alike) need, a flashable zip of the Lollipop update
Gemc666 said:
that's exactly what i was going to say, i don't use blisspop, i don't like custom roms, i prefer stock experience and i cant upgrade since im not on AT&T network, and what he is doing is exactly what i (and many others alike) need, a flashable zip of the Lollipop update
Click to expand...
Click to collapse
I slapped a zip together earlier for the stock ROM - it wasn't cooperative and made me mad so I gave up for the evening. Kept getting error:
E: Failed to sysMapFile
It was >2GB so that might have been part of the problem.
Gemc666 said:
that's exactly what i was going to say, i don't use blisspop, i don't like custom roms, i prefer stock experience and i cant upgrade since im not on AT&T network, and what he is doing is exactly what i (and many others alike) need, a flashable zip of the Lollipop update
Click to expand...
Click to collapse
Exactly what I'm looking/waiting for as well. 100% stock Lollipop rom in a flashable zip format. Well, a debloated version would be better but I'll debloat myself if need be. Our Devs are amazing, I'll hang tight and wait for it
Awesome, thank you so much! There hasn't been much movement for a stock LP ROM for the D800, so I'm glad you're doing it!
<Deleted> Test build info was here.
blastagator said:
If any brave testers dare:
http://blastagator.ddns.net/testing.php - beta1
It might not work! Please make sure you know how to recover!!!
I would not post something I would not try on my phone.
HOWEVER, I have NOT tried this on my phone because I had some family issues come up and I can't be "off the grid" so to speak to test things in recovery.
This flashes 20y bootstack, 30f modem, 30f system, and 30f bumped boot.img. Nothing else /should/ be modified. Root may or may not work. It appears installed, but you may need to run "One-Click-Root" or some similar thing after install.
Also, I modified nothing other than root and doing a bump. FOTA will still be functional as well as any other nasties that could cause issues down the line. This is STOCK!
If anyone tries, please report back, for everyone's sake.
Click to expand...
Click to collapse
Downloading, i'll report back later thank you very much
Question can i flash that from 20k? or do i need to be on something specific?
<Deleted> - Old test build info.
I downloaded the beta earlier but ran out of time today to do the install. Before I get brave and attempt it tonight or tomorrow, has anyone done it already and if so what were the results? Thanks.
ItsDon said:
I downloaded the beta earlier but ran out of time today to do the install. Before I get brave and attempt it tonight or tomorrow, has anyone done it already and if so what were the results? Thanks.
Click to expand...
Click to collapse
Didn't work. I had a bad update-binary in there. Once I fixed that I kept playing mix and match because of fastboot error. Still no luck, and needed my phone back. I'll tinker more later.
Tried full 20y bootstack. Tried just aboot and laf 20y, rest as LP. Tried each of this with bumped and unbumped stock LP boot.img.
Bumping gave me a padding error, guessing it might be partially related to that. Unsure.
Thanks for the update, saved me a few headaches I'll hang in there until you get a version that boots. Thanks for doing this!
ItsDon said:
Thanks for the update, saved me a few headaches I'll hang in there until you get a version that boots. Thanks for doing this!
Click to expand...
Click to collapse
I won't be messing with it for awhile. I have to work all weekend. 12 straight days of work, woohoo!
Thank you @blastagator for all your help. No rush. To know someone is looking into it will hopefully spark some interest in the d800 community! Once again - your contributions around here have been invaluable.
I bought this nexus 5 from a previous user, noticed bootloader unlocked, diferente kernel(althought i flashed another already), but something caught my eye, im not sure if i have the stock rom, as i get an update of 16mb and fails.
"devcheck app"
Under system = Codename: Hammerhead
5.1.1
Build: LMY48I
Is this stock?
Help?
Sent from my Nexus 5 using XDA Free mobile app
I think nobody wants help a KILLER
HIGKILLER said:
I bought this nexus 5 from a previous user, noticed bootloader unlocked, diferente kernel(althought i flashed another already), but something caught my eye, im not sure if i have the stock rom, as i get an update of 16mb and fails.
"devcheck app"
Under system = Codename: Hammerhead
5.1.1
Build: LMY48I
Is this stock?
Click to expand...
Click to collapse
It is not stock. Unlocked bootloader is fine, everything else is a no-go. The different kernel is the glaring problem, you can not apply an OTA with that non-stock kernel. The first, most complete, easiest option is to flash the latest factory image. Seeing as this is a new phone to you, I can't imagine that you have a ton of personal info to save. For me personally, I'd flash the image just so I know that I'm starting with a fresh clean slate. Then you can read up and root/mod how you'd prefer.
Yaz75 said:
It is not stock. Unlocked bootloader is fine, everything else is a no-go. The different kernel is the glaring problem, you can not apply an OTA with that non-stock kernel. The first, most complete, easiest option is to flash the latest factory image. Seeing as this is a new phone to you, I can't imagine that you have a ton of personal info to save. For me personally, I'd flash the image just so I know that I'm starting with a fresh clean slate. Then you can read up and root/mod how you'd prefer.
Click to expand...
Click to collapse
I have experience with custom roms all that, i did flash this kernel, but the room, is what bothers me. and thank you, i was kinda sure this wasent stock rom! Thank you
HIGKILLER said:
"devcheck app"
Under system = Codename: Hammerhead
5.1.1
Build: LMY48I
Is this stock?
Click to expand...
Click to collapse
Not enough information from this to say. The custom kernel you installed is enough to prevent OTA updating.
Wakamatsu said:
Not enough information from this to say. The custom kernel you installed is enough to prevent OTA updating.
Click to expand...
Click to collapse
i can never find a decent post, how can i be sure this is stock rom, without having to flash the stock one?
HIGKILLER said:
i can never find a decent post, how can i be sure this is stock rom, without having to flash the stock one?
Click to expand...
Click to collapse
It would be easy to say if the build didn't match a legit N5 image. If the build info in build.prop isn't informative, look for apps/features that shouldn't be in a stock image, eg. AOSP apps replacing the Google versions. Unfortunately, you do have to have some familiarity with stock Google to be able to spot something that's out of place.
Wakamatsu said:
It would be easy to say if the build didn't match a legit N5 image. If the build info in build.prop isn't informative, look for apps/features that shouldn't be in a stock image, eg. AOSP apps replacing the Google versions. Unfortunately, you do have to have some familiarity with stock Google to be able to spot something that's out of place.
Click to expand...
Click to collapse
thank you sir
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