I have a luge (4.4.2_KPA20.10.1_cid2_CFC_1FF_SVC.xml.zip)
Can I flash M (4.4.2-KDA20.62-10.1_CFC_1FF.xml) over it? Has anyone tried?
Im so sick of Verizon/Moto crap. We might break up. I just love the hardware!
hemanolio said:
I have a luge (4.4.2_KPA20.10.1_cid2_CFC_1FF_SVC.xml.zip)
Can I flash M (4.4.2-KDA20.62-10.1_CFC_1FF.xml) over it? Has anyone tried?
Click to expand...
Click to collapse
You can flash over system partition only from RAZR M, other vital parts flashing is forbidden by internal security procedures.
Im so sick of Verizon/Moto crap. We might break up. I just love the hardware!
Click to expand...
Click to collapse
Or wait for the root possibility. It's almost ready to public )
Or use Debloater. So many choices ))
s5610 said:
You can flash over system partition only from RAZR M, other vital parts flashing is forbidden by internal security procedures.
Or wait for the root possibility. It's almost ready to public )
Or use Debloater. So many choices ))
Click to expand...
Click to collapse
Well, darn it. I just flashed Luge firmware over my M (which was fully successful) to see if I could flash back (haven't tried yet). Hope I'm not stuck!!!
-How public-ready are we talking? Do you think it will allow motopocalyps?
hemanolio said:
Well, darn it. I just flashed Luge firmware over my M (which was fully successful) to see if I could flash back (haven't tried yet). Hope I'm not stuck!!!
Click to expand...
Click to collapse
Wait wait, you wrote you have Luge (smartphone itself). "I have a luge". Flash back is not possible, if bootloader is locked, but read further.
-How public-ready are we talking? Do you think it will allow motopocalyps?
Click to expand...
Click to collapse
Yes, sir, I think so. Kinda motocalypse )) Wait day or two.
s5610 said:
Wait wait, you wrote you have Luge (smartphone itself). "I have a luge". Flash back is not possible, if bootloader is locked, but read further.
Yes, sir, I think so. Kinda motocalypse )) Wait day or two.
Click to expand...
Click to collapse
I have both. After f**king with my M so much, I ended up trashing it a bit. So I bought a Luge to replace it for cheap. Ive been flashing crap back and forth, and you were right. So far, Im unable to flash/overwrite the Luge bootloader with the M bootloader. I was able to flash the system and whatnot, so now I have 2 LOCKED, unrooted Ms..... Im currently flashing my Luge back to Luge firmware and will just have to wait. Thanks for all the info though! it was all worth a shot
hemanolio said:
Im currently flashing my Luge back to Luge firmware and will just have to wait
Click to expand...
Click to collapse
Exploit was published on XDA. Doesn't unlock bootloader, but enables root. Good luck )
s5610 said:
Exploit was published on XDA. Doesn't unlock bootloader, but enables root. Good luck )
Click to expand...
Click to collapse
THANKS!!!!
Related
Need help on how to root my RAZR m on KitKat 4.4.2
penguin74 said:
Need help on how to root my RAZR m on KitKat 4.4.2
Click to expand...
Click to collapse
If your bootloader is locked, you can't.
If your bootloader is unlocked, flash a recovery and then a SuperSU .zip.
penguin74 said:
Need help on how to root my RAZR m on KitKat 4.4.2
Click to expand...
Click to collapse
I'm working on trying to unlock the bootloader
Good luck, you'll need it.
penguin74 said:
I'm working on trying to unlock the bootloader
Click to expand...
Click to collapse
All known methods of unlocking the bootloader were closed off a few updates ago, while we were still on Jellybean. Best of luck with finding one now; unless you (or someone else) succeed, you're permanently on KitKat.
lem22 said:
Good luck, you'll need it.
Click to expand...
Click to collapse
Im new to the phone scene really mess with game Consol's generally how do I tell if my boot loader is or isn't locked
penguin74 said:
Im new to the phone scene really mess with game Consol's generally how do I tell if my boot loader is or isn't locked
Click to expand...
Click to collapse
Considering that you have to ask, it's probably locked. If you really want to check, power on the phone while holding both volume buttons.
The know-how for softmodding a game console isn't going to help much with unlocking or modifying Android devices; they're very different beasts.
WARNING: You REALLY need to UNDERSTAND and read EVERYTHING or you MAY brick your phone!
Purpose of this thread:
To get you, the locked or unlocked Droid Mini owner, from any version to 4.4.4 (SU5-23 [ota] or SU5-24 [newer than ota...use caution]).
Things you will need:
FXZ SU5.23 Mini OTA
FXZ SU5.24 Mini Newer than OTA...use caution. UPDATE: Looks like some people are beginning to get this pushed, so, it looks like this is the "new OTA".
Thanks @stras1234
Instructions:
Use the RSD Flasher with KEEP DATA to flash this on your phone with RSD.
OR
Use the House of Moto with KEEP DATA to flash this to your phone with fastboot.
OR
Flash with RSD Lite.
This will get you a clean OTA install with no data loss. You will lose root.
I am reasonably sure,,,but I thought I would ask anyway,,,is there any downside to flashing this for those who have their BL unlocked? And after this just fastboot flash TWRP to get root back?
SamuriHL said:
WARNING: You REALLY need to UNDERSTAND and read EVERYTHING or you MAY brick your phone!
Purpose of this thread:
To get you, the locked or unlocked Droid Mini owner, from any version to 4.4.4 (SU5-24).
Things you will need:
FXZ SU5.24 Mini Thanks @stras1234
Instructions:
Use the RSD Flasher with KEEP DATA to flash this on your phone with RSD.
OR
Use the House of Moto with KEEP DATA to flash this to your phone with fastboot.
OR
Flash with RSD Lite.
This will get you a clean OTA install with no data loss. You will lose root.
Click to expand...
Click to collapse
Correct. The downside is that even on an unlocked bootloader, downgrading is extremely dangerous and will potentially brick you. But other than that, you should be good to go exactly as you said.
Thanks brother! I dont see a need to downgrade as long as the update is good from Verizon like no battery drain, signal issues etc. Thanks again for the file!
SamuriHL said:
Correct. The downside is that even on an unlocked bootloader, downgrading is extremely dangerous and will potentially brick you. But other than that, you should be good to go exactly as you said.
Click to expand...
Click to collapse
This may be a stupid comment, but are you sure this is the right FXZ link for the Mini? I only ask because I thought the Minis were obakem which is what is in the Ultra/Maxx posting. The link in this thread just has obake which I thought were the Ultras.
I looked at the Ultra/Maxx posting and the XML says it's for the Maxx, but in the past the FXZ has been named obake_maxx.
I don't know how much it really matters since the image files are usually the same.
SamuriHL said:
Correct. The downside is that even on an unlocked bootloader, downgrading is extremely dangerous and will potentially brick you. But other than that, you should be good to go exactly as you said.
Click to expand...
Click to collapse
If you have an unlocked boot loader and somehow brick during the process, can you reflash the newer firmware and start again?
Depends on the nature of "somehow brick" and what that means. If you can get to fastboot you should be able to flash the latest FXZ.
Sent from my SM-P600 using Tapatalk
So, as was pointed out, these images that I got are actually one build newer than the OTA. (Oops). I'm going to leave them up but I'll be posting the proper build 23 images in a little while.
OP updated
SO I take it that if I update to the .24 update then I stand the chance of not being able to flash a lower version?
SamuriHL said:
OP updated
Click to expand...
Click to collapse
Most likely.
Updated to the 24 build and everything works great! Thank you!
SamuriHL said:
Most likely.
Click to expand...
Click to collapse
su5
SamuriHL said:
WARNING: You REALLY need to UNDERSTAND and read EVERYTHING or you MAY brick your phone!
Purpose of this thread:
To get you, the locked or unlocked Droid Mini owner, from any version to 4.4.4 (SU5-23 [ota] or SU5-24 [newer than ota...use caution]).
Things you will need:
FXZ SU5.23 Mini OTA
FXZ SU5.24 Mini Newer than OTA...use caution. UPDATE: Looks like some people are beginning to get this pushed, so, it looks like this is the "new OTA".
Thanks @stras1234
Instructions:
Use the RSD Flasher with KEEP DATA to flash this on your phone with RSD.
OR
Use the House of Moto with KEEP DATA to flash this to your phone with fastboot.
OR
Flash with RSD Lite.
This will get you a clean OTA install with no data loss. You will lose root.
Click to expand...
Click to collapse
heads up...yeah this update cripples data on tmobile/ sim other than verizon...and trying to downgrade gets blocked...so no going back
if someone knows how to keep tmobile data working on su5-24...please let me know thnx
Wow that would suck,,,I have noticed some interesting new features that I never had before like emails when something on my calendar comes up and printing now works for me in this build.
spiral777 said:
heads up...yeah this update cripples data on tmobile/ sim other than verizon...and trying to downgrade gets blocked...so no going back
if someone knows how to keep tmobile data working on su5-24...please let me know thnx
Click to expand...
Click to collapse
spiral777 said:
heads up...yeah this update cripples data on tmobile/ sim other than verizon...and trying to downgrade gets blocked...so no going back
if someone knows how to keep tmobile data working on su5-24...please let me know thnx
Click to expand...
Click to collapse
I am curious to this solution as well. screen pic with current set up. zero experience getting bootloader unlocked or flashing. i only just got used to using adb. so if anyone does find the solution, can the guide be for idiots as well thanks!
Is anyone else getting a 404 for drdevs? I was looking to update but there doesn't seem to be any download links other than on that website.
It does seem like DRDEVS is down. I'll see if I can ping someone about it. I don't have any control over the server.
UPDATE: I'm told it'll be back soon. Keep checking.
Hello, guys!
As you know, Motorola smartphone can be repaired if something was wrong while flashing ROM's or doing smth with your device.
Here is the original service firmware KDF21.128-15_15 Blur_version.21.21.15
download
Just flash it through RSDLite or via BAT-file into archive!
Good flashing
Thank you! This will be very useful once we find some exploits!
thanks
kinglau719 said:
do i need to insert verzion sim card to re-activiate again after flashing this rom?
thanks in advance
Click to expand...
Click to collapse
not absolutely. You can throw verizon sim
thanks
Has anyone been able to get RSDLite to recognize the Turbo? I'm having some problems. I can access ADB fine, but when rebooting to the bootloader, it's not recognized by RSDLite.
Still no luck with RSDLite, but the batch file worked without a problem.
my Turbo is perfectly recognized.
Check well your driver installed
Hahahahaha...... "Flashing ROM's"
......**begins to cry**
MonkeyMouth said:
Hahahahaha...... "Flashing ROM's"
......**begins to cry**
Click to expand...
Click to collapse
Uhm ?
wolfgart said:
Uhm ?
Click to expand...
Click to collapse
Because the Droid Turbo isn't rooted or unlocked. So flashing ROM's is fantasy for now.
Yeah, they are flashing roms, oem roms.
ska4fun said:
Yeah, they are flashing roms, oem roms.
Click to expand...
Click to collapse
del
FXZ are OEM firmwares.
kinglau719 said:
sorry, because i am new
what the different between this FXZ and the system dump?
Click to expand...
Click to collapse
The system dump is just for people to pick through, but this can be used if your device gets bricked.
Was this an update? I'm showing 21.21.12 as my version
Sent from my XT1254
Yes, day one update.
Sent from my Droid Turbo.
Coronado is dead said:
Yes, day one update.
Sent from my Droid Turbo.
Click to expand...
Click to collapse
Strange I haven't been getting harassed by my device to update and I've had it for 2 weeks
Sent from my XT1254
lafont28 said:
Was this an update? I'm showing 21.21.12 as my version
Sent from my XT1254
Click to expand...
Click to collapse
I also have this version. Ive seen the update available for 21.21.15 but was unsure if i should take it in case a root method is found. Not sure if it makes a difference staying with this one or what the update brings.
Had to use this just today to save my phone. Worked like a charm!
This is for turbo?
Hi all,
I receive a lot of private messages about root for Nougat from this website:
http://www.androidinfotech.com/2017/06/root-sony-xperia-xa-ultra-nougat.html
DON'T CLIC ON IT, IT'S A CLICBAIT!
I never released anything for Nougat so please don't ask me why it doesn't work, it's only a scam to win money from ads.
If you can't find my work on Xda you will not find it anywhere.
Is there now for root this phone with nougat?
Araxielfenix said:
Is there now for root this phone with nougat?
Click to expand...
Click to collapse
No root on Nougat for now.
rrvuhpg said:
No root on Nougat for now.
Click to expand...
Click to collapse
...even after unlocked bootloader?
mingkee said:
...even after unlocked bootloader?
Click to expand...
Click to collapse
Hi, technically root is possible, I have it but not released to the public. Why? Because nobody supported my work and as you can see my root guide have only 29 thanks. You will have to wait for a release from an other user or maybe if my guide reaches 100 thanks (don't count on it).
Damn...
I had TA dumped the day I got it and I am ready to root it.
Well, I have to return it because there no root on 7
mingkee said:
Damn...
I had TA dumped the day I got it and I am ready to root it.
Well, I have to return it because there no root on 7
Click to expand...
Click to collapse
DRM fix with TA dump doesn't work on Nougat, bootloop at Sony logo (tested on XA Ultra)
The only good news it that SafetyNet is OK with Magisk Manager app v5.0.4 and zip v13.1 on Nougat.
rrvuhpg said:
Hi, technically root is possible, I have it but not released to the public. Why? Because nobody supported my work and as you can see my root guide have only 29 thanks. You will have to wait for a release from an other user or maybe if my guide reaches 100 thanks (don't count on it).
Click to expand...
Click to collapse
Hey, could you at least guide me on how to proceed ?
I would be grateful
Yooooomi said:
Hey, could you at least guide me on how to proceed ?
I would be grateful
Click to expand...
Click to collapse
You would be grateful by thanking me for my guide and my work on MM but you didn't do it.
I will give you a very good link to help you on how to proceed: www.google.com
rrvuhpg said:
You would be grateful by thanking me for my guide and my work on MM but you didn't do it.
I will give you a very good link to help you on how to proceed: www.google.com
Click to expand...
Click to collapse
Ow ok I'm going to thank you for your guide if you want, I didn't mean any offense you seem a bit nervous ^^'
Which guide are you talking about ?
Nb: I really do appreciate your work btw
Yooooomi said:
Ow ok I'm going to thank you for your guide if you want, I didn't mean any offense you seem a bit nervous ^^'
Which guide are you talking about ?
Nb: I really do appreciate your work btw
Click to expand...
Click to collapse
I'm not nervous but politeness is a minimum when someone spend some time for you, it's not normal to ask for any thank. I talk about my root guide (and root files). I was silly to think this, now I learned a good lesson: work for yourself and you will not have to wait for any thank.
rrvuhpg said:
I'm not nervous but politeness is a minimum when someone spend some time for you, it's not normal to ask for any thank. I talk about my root guide (and root files). I was silly to think this, now I learned a good lesson: work for yourself and you will not have to wait for any thank.
Click to expand...
Click to collapse
I'm not used to thank on xda to be honest but I will , now if you are not willing to help me that's no big deal I can understand
I think most of us who benefited yur work are mostly newbees like myself.. We apologize. I didn't know yu had to give thanks when yu like someones works.. Sorry
I think the OP gave me a bad idea to go back to 6.0.
Now the phone is bricked.
mingkee said:
I think the OP gave me a bad idea to go back to 6.0.
Now the phone is bricked.
Click to expand...
Click to collapse
Me ? I never said to go back to 6.0. Maybe it's your fault because you forgot to exclude TA parts of the firmware or you didn't used the fsc script or you used an old version of Flashtool? I downgraded/flashed my devices many times and never got any problems.
rrvuhpg said:
Me ? I never said to go back to 6.0. Maybe it's your fault because you forgot to exclude TA parts of the firmware or you didn't used the fsc script or you used an old version of Flashtool? I downgraded/flashed my devices many times and never got any problems.
Click to expand...
Click to collapse
Agreed. I rolled back to 6.0 2 times without problems. Btw. I have a spare Z1 and I accidentally flashed those .ta files but they did no harm. I think they are useless even when flashed.
BlueTR said:
Agreed. I rolled back to 6.0 2 times without problems. Btw. I have a spare Z1 and I accidentally flashed those .ta files but they did no harm. I think they are useless even when flashed.
Click to expand...
Click to collapse
I successfully flashed to 6.0 (.160), but after I flashed your kernel from dev section and it has bootloop problem (from either rootpack or individual). Should I flash to earlier version? My choice is
Customized LAM (.182, 7.0)
Customized US (.182, 7.0)
Customized Peru (.160, 6.0)
Service Exchange Unit (.111, 6.0)
Please continue your work, and I always give thanks once I found it's working.
----- update -----
I sucessfully flashed to Service Exchange Unit (.111, 6.0) and everything worked as it's supposed to be, and rooted with SuperSU (but I will move to Magisk in the future)
mingkee said:
I successfully flashed to 6.0 (.160), but after I flashed your kernel from dev section and it has bootloop problem (from either rootpack or individual). Should I flash to earlier version? My choice is
Customized LAM (.182, 7.0)
Customized US (.182, 7.0)
Customized Peru (.160, 6.0)
Service Exchange Unit (.111, 6.0)
Please continue your work, and I always give thanks once I found it's working.
----- update -----
I sucessfully flashed to Service Exchange Unit (.111, 6.0) and everything worked as it's supposed to be, and rooted with SuperSU (but I will move to Magisk in the future)
Click to expand...
Click to collapse
You quoted wrong person. If you flash an older kernel over a new firmware, you get bootloop. I had that too.
I really wish I could do such coding to compile both boot and recovery because XA Ultra is really awesome, but you have to catch up with version.
[/COLOR]
bizzygang said:
I didn't know yu had to give thanks when yu like someones works.. Sorry
Click to expand...
Click to collapse
Yeah, that's really unusual.
erased link sorry
What benefits does flashing this provide?
ktimque said:
What benefits does flashing this provide?
Click to expand...
Click to collapse
None yet, it's the base for getting root, once we find a way to get it to stay rooted. It's mainly for those who upgraded to the 2nd iteration of the bootloader and can't downgrade to a rootable firmware (It's been confirmed by a few to work with the new Cyborg rom, albeit without root).
As of right now, unless you know why you need it, it's best to leave it alone.
podagee said:
IF ANYONE GETS ROOT COULD YOU BE SO KIND AND POST IT HERE THANK YOU.
Click to expand...
Click to collapse
ktimque said:
What benefits does flashing this provide?
Click to expand...
Click to collapse
Well, I may have spoke too soon, you guys might want to take a look here in the Cyborg rom thread, seems they have a modified U2 bootloader they're flashing and retaining root. One member has volunteered to do a factory reset to see if it survives, but if so, v2 bootloader may now be rootable, or at least on the right track for public use.
IJoxer said:
None yet, it's the base for getting root, once we find a way to get it to stay rooted. It's mainly for those who upgraded to the 2nd iteration of the bootloader and can't downgrade to a rootable firmware (It's been confirmed by a few to work with the new Cyborg rom, albeit without root).
As of right now, unless you know why you need it, it's best to leave it alone.
Click to expand...
Click to collapse
Thanks for answering that man. Haha. That's awesome that the guys got stuff moving that quickly. I knew that they had the files also,but, held off as long as they could until I came along.
But another useful feature I've noticed in this combo firmware is that there is an open unlock option now and mine sticks after reboot. I tried build roms, kernels,etc.. in the past that ended in ultimate failure. I'd like to start again. At the moment I just cruise the foreign forums grabbing whatever software I can find. I kinda have building only the tree down, not so much, as it's been years. I used to build Linux OS's a long time ago but forgot. I'll do my own research here if it, anybody wants to teach, I'm all ears, all eyes. Aloha