Is not there a possibility to totally wipe/blank the phone (bootloader, kernel) and back to epoch, then start from scratch?
Think about these are as:
- radiocomm
- qflash
- or something else ...
even if it is very difficult?
I guess the updated, locked bootloader won't even allow you to do any of that, just like how it rejects flashing custom system/recovery images.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Was thinking to "force bricking" and then somehow unbricking... in any way destroy or replace the current bootloader in order to not be able to prevent the intervention. What do you think about the "blank bootloader", what are the possibilities it gives?
Replace BL -> supposedly not allowed by current BL
Destroy/clear BL -> unable to boot up & lose access to fastboot flash mode -> no way to flash in anything
...at least these are what I think.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
The boot loader is locked this means we do not have access to this. We cannot downgrade the boot loader period if you are on .15 and not previously unlocked
Sent from my XT907 using XDA Free mobile app
Well, that sounds pretty bad. Although this was a very good device, I have to look for other, probably Nexus, which is open ... It was not a good move from Motorola.
I agree it was a bad move but it seems to be the nations standard these days
Sent from my XT907 using XDA Free mobile app
What do you think about the bugreport? Already occurred twice since the KK update (never occurred in JB).
~7MB txt file, the the beginning of the file looks like this:
bugreport-2014-10-13-10-15-59.txt:
========================================================
== dumpstate: 2014-10-13 10:15:59
========================================================
Build: KDA20.62-15
Build fingerprint: 'motorola/XT907_verizon/scorpion_mini:4.4.2/KDA20.62-15/15:user/release-keys'
Bootloader: 0x109B
Radio: msm
Network: Telekom XX
Kernel: Linux version 3.4.42-g46d4525-00001-ga9305fd ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue Jul 29 02:16:18 PDT 2014
Command line: console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2 vmalloc=400M androidboot.emmc=true androidboot.serialno=TA59707LSY androidboot.baseband=msm androidboot.mode=normal androidboot.bootloader=0x109B androidboot.cid=0x2 androidboot.hwrev=0x82A0 battery= mot_sst=1 androidboot.carrier=vzw product=smq androidboot.device=smq androidboot.secure_hardware=1
------ UPTIME (uptime) ------
up time: 5 days, 14:59:52, idle time: 1 days, 03:29:45, sleep time: 4 days, 09:13:57
[uptime: 0.1s elapsed]
...
...
RAZR M towelroot not working
i update razr m from 4.1.2 to stock kk by rsd lite now i want to do cutom rom towelroot giving error this phone isnt supported b\c as geohot says it works on build date prior to 3 june 2014 but my build date is 29 july 2014 with system version 183.46.15.xt907 .verison..... i also try to downgrade to jellybean by rsd lite but my bootloader is locked plz tell me is their any way to unlock the bootloader by any method that i can instal custom recovery. or i need to wait untill geohot release new app to support further builds after 3 june....
abifahad said:
i update razr m from 4.1.2 to stock kk by rsd lite now i want to do cutom rom towelroot giving error this phone isnt supported b\c as geohot says it works on build date prior to 3 june 2014 but my build date is 29 july 2014 with system version 183.46.15.xt907 .verison..... i also try to downgrade to jellybean by rsd lite but my bootloader is locked plz tell me is their any way to unlock the bootloader by any method that i can instal custom recovery. or i need to wait untill geohot release new app to support further builds after 3 june....
Click to expand...
Click to collapse
You're stuck, you can't root .15, you can't unlock it, and you can't downgrade if you're locked. This has been discussed a billion times.
Sent from my HTC6525LVW using Tapatalk
sympatex said:
Well, that sounds pretty bad. Although this was a very good device, I have to look for other, probably Nexus, which is open ... It was not a good move from Motorola.
Click to expand...
Click to collapse
mrkhigh said:
I agree it was a bad move but it seems to be the nations standard these days
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
its more verizon wanting the locked bootloader then motorola
After about a month of use after the experience 183.46.15 verizon update:
- constant cracking sound from the speaker in any event
- 3 random shutdown (while running with endomondo, the result is of course lost)
- 2 random reboots
- continuous battery drain
The latter is probably due to the fastdormant apk, but since there is no root, nothing can be done.
In summary, due to the new update the device completely unusable. Previously, in JB, none of the above error occurred (after >600 miles running with same device)
We can say that Verizon only create the update to prevent the root, and nothing else test the software.
I wonder why it was so urgent to send the .15 OTA? Maybe in order to "destroy" the devices as soon as possible people having to buy another one?
.15 sucks big time
sympatex said:
After about a month of use after the experience 183.46.15 verizon update:
- constant cracking sound from the speaker in any event
- 3 random shutdown (while running with endomondo, the result is of course lost)
- 2 random reboots
- continuous battery drain
The latter is probably due to the fastdormant apk, but since there is no root, nothing can be done.
In summary, due to the new update the device completely unusable. Previously, in JB, none of the above error occurred (after >600 miles running with same device)
We can say that Verizon only create the update to prevent the root, and nothing else test the software.
I wonder why it was so urgent to send the .15 OTA? Maybe in order to "destroy" the devices as soon as possible people having to buy another one?
Click to expand...
Click to collapse
Really bad decision by me not to unlock bootloader. Paying the price now with the update.
For me,
- Phone display or power button stops responding at least 2-3 times a day. This is followed by an automatic reboot
- Battery drains really quickly - clearly because of the Modem FastDormancy Monitor
Things I have tried so far:
- Factory Reset
- Modify the NVM to accommodate GSM
- Kept phone in GSM only mode
- Disabled Modem FastDormancy App
- Kept phone in safe mode
Nothing works. Same behaviour.
Will try to flash 183.46.15 over my 182.46.15 with a complete data wipe. Not many hopes left. :crying:
Changi said:
Really bad decision by me not to unlock bootloader. Paying the price now with the update.
For me,
- Phone display or power button stops responding at least 2-3 times a day. This is followed by an automatic reboot
- Battery drains really quickly - clearly because of the Modem FastDormancy Monitor
Things I have tried so far:
- Factory Reset
- Modify the NVM to accommodate GSM
- Kept phone in GSM only mode
- Disabled Modem FastDormancy App
- Kept phone in safe mode
Nothing works. Same behaviour.
Will try to flash 183.46.15 over my 182.46.15 with a complete data wipe. Not many hopes left. :crying:
Click to expand...
Click to collapse
Me too. I am not stuck I can go back to JB..but can't for few weeks as laptop is not currently here...
So following things are helping me right now to keep my bettry a little (it won't last more then 5-7hrs) but these things helped some
=Iam keeping my phone on safemode
=I am keeping brightness at lowest
=I am using du bettary saver
=most best I am using greenify
Better way to use greenify:
use greenify every time before pressing screen lock button...it closes all apps..allow greenify to auto kill apps (no root need) create a shortcut.. And just bang this shortcut one it will force close each application running automatically... It worked for me a lot saved something like 6hrs on standby and a lot time while using.thanks
RikRong said:
You're stuck, you can't root .15, you can't unlock it, and you can't downgrade if you're locked. This has been discussed a billion times.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
people talk like this too much its like you have seen it so you think we must have seen it
doshjaniels said:
people talk like this too much its like you have seen it so you think we must have seen it
Click to expand...
Click to collapse
I'm not going to argue about it, but it's been discussed in every thread about .15 and there have been many threads about .15.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
I'm not going to argue about it, but it's been discussed in every thread about .15 and there have been many threads about .15.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I think u r same who ruined my post in which I was explaining those .15 can't do anything -_-
livecouk said:
I think u r same who ruined my post in which I was explaining those .15 can't do anything -_-
Click to expand...
Click to collapse
I'm actually the one that let you know you can downgrade since you're unlocked. [emoji6]
Sent from my HTC6525LVW using Tapatalk
rikrong said:
i'm actually the one that let you know you can downgrade since you're unlocked. [emoji6]
sent from my htc6525lvw using tapatalk
Click to expand...
Click to collapse
[deleted] [*apologize]
livecouk said:
Hmm means you are other guy sorry. That guy who ruined by post I hate hm
Click to expand...
Click to collapse
It's me then? Just trying to give some advice, nothing wrong with that, eh?
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Related
So I did the root keeper wrong and updated, losing root. Anyone else in this club with me? It's only been a few hours and I already miss it.
Atleast I have better pictures though....
Sent from my XT1058 using xda app-developers app
You could reflash the software back to before the update with the KXZ firmware and try the process over again. Depends if the hassle is worth it to you.
http://forum.xda-developers.com/showthread.php?t=2411618
Abyssul said:
You could reflash the software back to before the update with the KXZ firmware and try the process over again. Depends if the hassle is worth it to you.
http://forum.xda-developers.com/showthread.php?t=2411618
Click to expand...
Click to collapse
This process is just flashing the firmware through rsdlite which won't happen because it's a downgrade. I tried.
Sent from my XT1058 using xda app-developers app
Maybe this will work? http://forum.xda-developers.com/showthread.php?p=45955669#post45955669
You can't flash with fastboot? I'm new to the Android ecosystem, but there must be some way to downgrade.
freak4dell said:
Maybe this will work? http://forum.xda-developers.com/showthread.php?p=45955669#post45955669
Click to expand...
Click to collapse
just tried, did not work. fails at the boot.img
Abyssul said:
You can't flash with fastboot? I'm new to the Android ecosystem, but there must be some way to downgrade.
Click to expand...
Click to collapse
first things I tried and doesn't work
I did the update and protected root but my wifi was messed up and wouldn't turn on. I did RSDLite to downgrade and redo it all and it worked fine.
BTW I used this http://forum.xda-developers.com/showthread.php?t=2446515
Some of us didn't want root in the first place! #TeamStockMotoX :silly:
I'm confused as to why someone wouldn't just unlock their bootloader if they are going to be making changes to their system. I understand the warranty issue but who uses that? Most people go through asurion and they won't even notice. Haha
Sent from my Moto X using XDA Premium
eyeisdasteve said:
I'm confused as to why someone wouldn't just unlock their bootloader if they are going to be making changes to their system. I understand the warranty issue but who uses that? Most people go through asurion and they won't even notice. Haha
Sent from my Moto X using XDA Premium
Click to expand...
Click to collapse
Because some of us can't unlock our bootloader.
eyeisdasteve said:
I'm confused as to why someone wouldn't just unlock their bootloader if they are going to be making changes to their system. I understand the warranty issue but who uses that? Most people go through asurion and they won't even notice. Haha
Sent from my Moto X using XDA Premium
Click to expand...
Click to collapse
Just remember that Retail AT&T and Verizon and MotoMaker AT&T variants aren't able to have their boot loaders unlocked
Sent from my XT1058 using Tapatalk 4
Lost root don't care. Motorola got this phone right. I'm good with stock.
rivlez said:
I did the update and protected root but my wifi was messed up and wouldn't turn on. I did RSDLite to downgrade and redo it all and it worked fine.
BTW I used this http://forum.xda-developers.com/showthread.php?t=2446515
Click to expand...
Click to collapse
Your wifi was only screwed up within Recovery mode (write off) correct?
I have a similiar issue. Whether its affecting other things or not, i dont know.
But what do you mean you restored via RSD lite and did it all over again and it was fine?
How did you ujse RSD lite to reflash the firmware since you got the updated OTA, it wont let you downgrade
emerica243 said:
Your wifi was only screwed up within Recovery mode (write off) correct?
I have a similiar issue. Whether its affecting other things or not, i dont know.
But what do you mean you restored via RSD lite and did it all over again and it was fine?
How did you ujse RSD lite to reflash the firmware since you got the updated OTA, it wont let you downgrade
Click to expand...
Click to collapse
My wifi was messed up in any mode. It wouldn't turn on for some reason. I restored the 17.51 firmware after the botched update messed up my wifi and it worked fine and I actually ended up doing it 2 times since a titanium backup messed up my phone. I was definitely on the 17.54 update. It definitely let me downgrade. How would you like me to prove it to you?
my wifi messed up in recovery mode but lte works. Normal mode everything is fine. I am rooted now with latest update.
sravanz said:
my wifi messed up in recovery mode but lte works. Normal mode everything is fine. I am rooted now with latest update.
Click to expand...
Click to collapse
Add me in as another one with no wifi in recovery. Normal mode works just fine as well. Would be nice if there was a fix for this but just glad to still have root with the update.
Rask40 said:
Add me in as another one with no wifi in recovery. Normal mode works just fine as well. Would be nice if there was a fix for this but just glad to still have root with the update.
Click to expand...
Click to collapse
Me too. My wifi is FUBARED in recovery. It's because we don't have the new kernel and to be technical were using the old system/recovery in our "recovery mode" I think that's why it's working in the regular mode and not recovery mode..... Or that's what I understand. Though I'm probably wrong.
When I upgraded I got a failed upgrade after final boot. Although it still says the newest version. I'm tempted to RSD back like some others have just to try but I don't want a paper weight.
Sent from non rooted motoX :'(
gunnyman said:
Lost root don't care. Motorola got this phone right. I'm good with stock.
Click to expand...
Click to collapse
While I'm kind of excited to see SafeStrap out, and updated (fixes phone/data, etc...), I'm still hoping some attempt is in the works for unlock on at&t.
Regardless, there aren't any custom roms to really flash anyways.
Had I an unlocked bootloader, I'd have a custom kernel in the works, and maybe some custom roms with some TeamAcid love.
Come see, come saw... Patience wins all.
hey guys, im terrible with Motorola phones for some reason and i cant find a root method for my droid razr m, im looking at tons of threads with "Root 4.4.2" in the title but none of the methods work, im on System version: 182.46.15.xt907 Build number : KDA20.62-15. could i be able to downgrade? thanks guys, sorry for sucking at finding threads...... i use the "Search" Tool like everyone complains but still can never find anything.
Locked bootloader or not? (Go to fastboot mode to check)
If locked, then you're doomed.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
AndyYan said:
Locked bootloader or not? (Go to fastboot mode to check)
If locked, then you're doomed.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Click to expand...
Click to collapse
yeah dang it looks like im doomed, so i read that the update to .15 basically had all the security updates that 4.4.4 had, so Jcases Sunshine does only work on 4.4.3 devices and below (moto x/moto g/mini/ultra) currently 4.4.4 is not supported on shunshine (my moto x has 4.4.4) do you think sunshine would work if we get it updated and try it on .15?
Trozzul said:
yeah dang it looks like im doomed, so i read that the update to .15 basically had all the security updates that 4.4.4 had, so Jcases Sunshine does only work on 4.4.3 devices and below (moto x/moto g/mini/ultra) currently 4.4.4 is not supported on shunshine (my moto x has 4.4.4) do you think sunshine would work if we get it updated and try it on .15?
Click to expand...
Click to collapse
Might as well try, but I think if there's already a working root method then the forum wouldn't have been silent like this.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Yea it wouldn't hurt to try as it says 1.6 doesn't need root and it won't charge you if it doesn't work...
We cannot teach people anything; we can only help them discover it within themselves.
ezknives said:
Yea it wouldn't hurt to try as it says 1.6 doesn't need root and it won't charge you if it doesn't work...
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
ill try my best to find v1.6 and give feedback, i didnt even think of v1.6!
For anyone reading this in the future, the sunshine bootloader unlock did work on my .15 Razr M, and like it says if it doesn't work it won't charge you.
Galaxyninja66 said:
For anyone reading this in the future, the sunshine bootloader unlock did work on my .15 Razr M, and like it says if it doesn't work it won't charge you.
Click to expand...
Click to collapse
I'd reflash stock firmware, Factory reset, and retry Sunshine
Sent from my sailfish using XDA Labs
Ok so my whole problem is that im on system version 183.46.15.XT907 when its supposed to be 183.46.10.XT907. My question is that is there a way to get to 183.46.10.XT907. again? I've been at this for hours and i'm in desperate need for help.
If you would like to see a picture of exactly please PM it will not let me place a picture as i am a new user
rockketman123 said:
Ok so my whole problem is that im on system version 183.46.15.XT907 when its supposed to be 183.46.10.XT907. My question is that is there a way to get to 183.46.10.XT907. again? I've been at this for hours and i'm in desperate need for help.
If you would like to see a picture of exactly please PM it will not let me place a picture as i am a new user
Click to expand...
Click to collapse
As of now there is no way of rooting or downgrading with a locked bootloader.
Sent from my Scorpion Mini
That's a bummer, but for root part, maybe or maybe not. I don't think it's possible as Motorola took out some vital codes from Kit Kat ROM which allows root.
ATTACK said:
As of now there is no way of rooting or downgrading with a locked bootloader.
Sent from my Scorpion Mini[/QUOTEO
I was able to flash it down to .10 but my kernel was after June 3rd, something like July 27th or whatever and yeah this doesnt allow it to work. Oh well, I'm switching to an S3 In less than a month.
Click to expand...
Click to collapse
rockketman123 said:
ATTACK said:
As of now there is no way of rooting or downgrading with a locked bootloader.
Sent from my Scorpion Mini[/QUOTEO
I was able to flash it down to .10 but my kernel was after June 3rd, something like July 27th or whatever and yeah this doesnt allow it to work. Oh well, I'm switching to an S3 In less than a month.
Click to expand...
Click to collapse
Unlocked or locked? Kernel date and screenshot as proof please, including the AP Fastboot screen.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Click to expand...
Click to collapse
I suspect it's already unlocked as it's impossible to downgrade the kernel on a locked RAZR M (OEM signatures, you know).
AndyYan said:
rockketman123 said:
Unlocked or locked? Kernel date and screenshot as proof please, including the AP Fastboot screen.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Click to expand...
Click to collapse
as I'm a new user I cant post a screen shot but the imgur link is i(.)imgur(.)com/xiZuIyq(.)jpg and i(.)imgur(.)com/cA6W6Oi(.)jpg
I went from 4.1.2 Rooted and was never able to unlock the bootloader then flashed to 4.4.2 on the .15 then flashed to .10
Click to expand...
Click to collapse
You're outta luck. You ahould have flashed .10 first and unlocked the bootloader before you hop between the ROM version... .15 version permanently lock the bootloader.
EDIT: I looked at the pictures, however, I am suspicious of the claim. The reason being, the bootloader will check the kernel version, and if it's not agreed with the bootloader security key file (tz.mbn), the bootloader will refuse to touch it. If anyone else with the locked phone tries this harebrained experiment and come out without a softbrick, I may have to eat my sock.
Dr. Mario said:
You're outta luck. You ahould have flashed .10 first and unlocked the bootloader before you hop between the ROM version... .15 version permanently lock the bootloader.
Click to expand...
Click to collapse
yeah when i flashed over i "accidentally" did the wrong version (tut linked me to a wrong version I suppose) and now im piss out of luck, but like i said im not worrying about it since s3 within a few weeks or so. Hopefully one day it's able to Root though B)
EDIT: what exactly are you suspicious of? The claim that I went from 4.1.2 flashed to 4.4.2 but on .15 then down to .10?
If the eventual RAZR M update gets screwed up like the first one, it may get unlocked but I have grave doubt because Verizon have learned their lesson on this one: root = bootloader unlock, at least in the case of early Kit Kat update.
fellas i have received two moto M today and seems like this cant either root because this stupid 9mb of .15 update, since the kernal is after jun 3
towelroot
well any new exploit around the coner to try?
No root exploits right now, unfortunately. It's getting harder and harder to exploit the Kit Kat.
Is there any way to root my phone.
The system version is 183.46.15.
If your boot loader is locked, no.
Sent from my HTC6525LVW using Tapatalk
Nope. Sorry. Both bootloader and root are patched.
RikRong said:
If your boot loader is locked, no.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Is there any guru working on the root? thinking about selling the phone if no hope
everseen said:
Is there any guru working on the root? thinking about selling the phone if no hope
Click to expand...
Click to collapse
Not gonna come as far as I can see from now. Just go ahead and sell it. Plenty of alternatives on the market.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
There are some RAZR M that are unlocked on Swappa as well.
tianor said:
Is there any way to root my phone.
The system version is 183.46.15.
Click to expand...
Click to collapse
Did u get unlocked, i am also stricken with it
Love Cyaan said:
Did u get unlocked, i am also stricken with it
Click to expand...
Click to collapse
No luck yet.
root and unlock 183.46.15
everseen said:
No luck yet.
Click to expand...
Click to collapse
Me too, me too!
Googleing this search daily " unlock 183.46.15 site:forum[.]xda-developers[.]com"
Checked ever corner of XDA, alas no solution on how to root and unlock 183.46.15
Devs @ XDA, come on champs gave us something, so can we also enjoy the privilege of CM12. Many are waiting for it fingers crossed
Mods/all, its only a humble request to Dev & not that if being annoyed.
Qualcomm patched the second layer (sbl2) of the second-stage bootloader, to take care of possible exploitation, effectively making it impenetrable. So for some individuals, we're pretty much out of luck. I wouldn't be sure of the possible exploits (the problem is, after that patch, it makes it even harder, although not impossible). Previous Kit Kat rooting exploitation relies on the permission requestion layer (futex) of the Linux kernel, as discovered by the former PS3 hacker, GeoHot, while it's patched by now. It's possible there is already a new rooting exploit by now, just don't hold the breath.
It's possible there is already a new rooting exploit by now, just don't hold the breath.
Click to expand...
Click to collapse
Can you please be more concretely?
I may not be up to date, been out of town for a bit, and figuring out a way to unbrick a few RAZR Ms.
However, the reason I said not to hold the breath is because of Verizon demanding a hard fix for rooting so that way almost any root exploits simply fail on arrival. This phone company also WANTS locked BIOS so no one can install custom recovery and OS "just because it put customer services in jeopardy".
That's really bad, can't believe that there is no chance to root or bootunlock this device.
By the way, do you know any way to disable/delete/freeze modem fast dormancy service without rooting phone? Or to made some changes in build.prop file?
Simply force close Modem fastdormancy first then disable it in app manager, it will then quit. And, editing build.prop requires root (write protection).
Force close works but disable button is inactive.
Sent from my XT907 using XDA Free mobile app
Ah, right.... I wonder why Verizon would disable some app manager features.
I'm outside of us, my carrier operates in gsm network and does not support fast dormancy, therefore phone reboots and can't wake up on power button when using h+. Thats why I need to edit build.prop and to dothis I need root access to file system.
Sent from my XT907 using XDA Free mobile app
Makes sense. However, I may look for new exploit, but since Futex is removed, it is not so simple.
Dr. Mario, are you developer?
Sent from my XT907 using XDA Free mobile app
Not officially, yet. But I know how the software works underneath the pretty UI, even down to the machine codes. I have been modding Android for 3 years.
just find some information about a lolipop upgrade for motorola droid ultra/mini/maxx from motorola upgrades pages :crying: :crying:
mt021322 said:
just find some information about a lolipop upgrade for motorola droid ultra/mini/maxx from motorola upgrades pages :crying: :crying:
Click to expand...
Click to collapse
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/110262
The link for more details is dead however...
BackCheck said:
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/110262
The link for more details is dead however...
Click to expand...
Click to collapse
thanks,..i forgot for a link :good:
this attachment is what i've got from motorola forums about a dead links
https://forums.motorola.com/posts/19343d1335?page=24
Sad news, they should offer owners the option to unlock their bootloader so they can upgrade to Lollipop themselves.
Sent from my XT1080 using Tapatalk
sign a petition, give us the BL UNLOCK CODE, we don't need a cashback
un1ocked said:
sign a petition, give us the BL UNLOCK CODE, we don't need a cashback
Click to expand...
Click to collapse
Yay,give me a link petition,.i will sign it,i' ll support it..
I found a link
https://www.change.org/p/verizon-dr...source=share_for_starters&utm_medium=copyLink
Let' s go
I signed it I'm number 97 of 100 but don't think it will do any good because the petitions don't seen to ever work out will for any of us.
leerpsp said:
I signed it I'm number 97 of 100 but don't think it will do any good because the petitions don't seen to ever work out will for any of us.
Click to expand...
Click to collapse
At least we' re doing something,no matter what' s a result.
Verizon isn't going to let Motorola bl unlock these phones until they stop selling them like the X
But there is a new unlock exploit coming very soon that *will* work on the 8960/pro, so most of us will at least get 5.1 via cyanogenmod, it should breathe new life into these devices for at least the rest of 2016, maybe longer.
Maybe there is a chance to even get 6 via cyanogenmod eventually if the drivers can be ported from 5.1 ? Or is that an unrealistic expectation?
Let's hope this new 8960/ pro exploit is real for the sake of those who have not had the pleasure of running LP and MM on their machines. My MAXX and OG Moto X have been on LP for over a year now and it ran much better than KK other than the cell standby bug. I just flashed CM13 on this phone and it is even better. Testing out doze now, seems to be pretty good on the battery. This is a great phone, if it is bootloader unlocked!
Sent from my DROID MAXX using Tapatalk
_ck_ said:
.... selling them like the X But there is a new unlock exploit coming very soon that *will* work on the 8960/pro, so most....
Click to expand...
Click to collapse
blasphemy !! rofl
teerout said:
blasphemy !! rofl
Click to expand...
Click to collapse
sorry that went over my head? blasphemy? why?
@beaups
What has a higher probability of happening?
WP = 0 or
Bootloader Unlock
JH1108 said:
@beaups
What has a higher probability of happening?
WP = 0 or
Bootloader Unlock
Click to expand...
Click to collapse
Same.
Sent from my XT1254 using Tapatalk
beaups said:
Same.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
What version Android are these devices running. Are you able to get (temp) root?
Sent from my XT1254 using Tapatalk
beaups said:
What version Android are these devices running. Are you able to get (temp) root?
Click to expand...
Click to collapse
root exists on the (verizon) mini/maxx/ultra (same phone internals) because of work done by crashxxl to bypass the bootloader and write over the rom via qload driver mode - basically he writes the changes needed for root and SU
I believe he figured it out by studying the developer edition of the device which is bl unlocked
it works quite well, we have root and xposed but wp=1 of course
laginimaineb's next announcement will open the device for everyone but I don't think he is releasing a proof of concept, at least not for this phone model, so if you are willing, we could probably really use your help when that happens
I'd be happy to send you a mini (to keep) if that will help motivate you
_ck_ said:
root exists on the (verizon) mini/maxx/ultra (same phone internals) because of work done by crashxxl to bypass the bootloader and write over the rom via qload driver mode - basically he writes the changes needed for root and SU
I believe he figured it out by studying the developer edition of the device which is bl unlocked
it works quite well, we have root and xposed but wp=1 of course
laginimaineb's next announcement will open the device for everyone but I don't think he is releasing a proof of concept, at least not for this phone model, so if you are willing, we could probably really use your help when that happens
I'd be happy to send you a mini (to keep) if that will help motivate you
Click to expand...
Click to collapse
What version Android are most people running?
Sent from my XT1254 using Tapatalk
beaups said:
What version Android are most people running?
Click to expand...
Click to collapse
it's kitkat 4.4.4 - the only option right now unless you have a developer model or paid for sunshine so you can use cyanogenmod, etc.
SU6-7 rom was built December 2014 (sunshine cannot unlock this one)
SU4.21 rom was built June 2014 - sunshine CAN unlock this version but if anyone has accepted the OTA, it's too late because now the phone is SU6-7.3 and fuse blown
I can send you either SU4 or SU6 to play with
_ck_ said:
it's kitkat 4.4.4 - the only option right now unless you have a developer model or paid for sunshine so you can use cyanogenmod, etc.
SU6-7 rom was built December 2014 (sunshine cannot unlock this one)
SU4.21 rom was built June 2014 - sunshine CAN unlock this version but if anyone has accepted the OTA, it's too late because now the phone is SU6-7.3
I can send you either SU4 or SU6 to play with
Click to expand...
Click to collapse
So sunshine is available for these models and people skipped it? Or on too new of firmware to use it?
Sent from my XT1254 using Tapatalk
beaups said:
So sunshine is available for these models and people skipped it? Or on too new of firmware to use it?
Click to expand...
Click to collapse
SU4 hasn't been available for a year now, maybe longer and you cannot downgrade these phones
verizon now ships all of them with SU6, so no sunshine, and verizon refuses to let motorola unlock the bootloader like they did with the X