I am currently running the 3-6 build of chroma which is the final 5.0.2 version. I am currently on baseband mdm9625_104335.118.02.55.03R and bootloader moto-apq8084-71.05.
I am wanting to try 5.1 roms like meanpop and chroma when its stable but i dont want to brick my nexus. I know meanpop says to flash the radio/firmware. Is that the radio and bootloader? Should i update my bootloader to 5.1? Should i go all the way back to stock everything and flash the new 5.1 update and start over? What can i do to keep from breaking my phone?
Not sure what they mean by "firmware". I'm guessing he means the radio still. Just flash ROM.zips and if you want, radios..
Manalow88 said:
I am currently running the 3-6 build of chroma which is the final 5.0.2 version. I am currently on baseband mdm9625_104335.118.02.55.03R and bootloader moto-apq8084-71.05.
I am wanting to try 5.1 roms like meanpop and chroma when its stable but i dont want to brick my nexus. I know meanpop says to flash the radio/firmware. Is that the radio and bootloader? Should i update my bootloader to 5.1? Should i go all the way back to stock everything and flash the new 5.1 update and start over? What can i do to keep from breaking my phone?
Click to expand...
Click to collapse
IME you should not attempt to downgrade either the bootloader or the partition table on a motorola phone. And you should make sure your bootloader is unlocked and USB debugging and OEM unlock are enabled b/f flashing.
JulesJam said:
IME you should not attempt to downgrade either the bootloader or the partition table on a motorola phone. And you should make sure your bootloader is unlocked and USB debugging and OEM unlock are enabled b/f flashing.
Click to expand...
Click to collapse
IM not asking if its a good idea to downgrade the bootloader. I am asking if it is necessary to update the bootloader and radio for 5.1 roms.
Manalow88 said:
IM not asking if its a good idea to downgrade the bootloader. I am asking if it is necessary to update the bootloader and radio for 5.1 roms.
Click to expand...
Click to collapse
no, its not necessary. im on the older bootloader, and am using an older radio, in a 5.1 rom. no issues.
simms22 said:
no, its not necessary. im on the older bootloader, and am using an older radio, in a 5.1 rom. no issues.
Click to expand...
Click to collapse
Do you mind posting what version your bootloader is
simms22 said:
no, its not necessary. im on the older bootloader, and am using an older radio, in a 5.1 rom. no issues.
Click to expand...
Click to collapse
Is there some reason you didn't upgrade to the new bootloader and radio? Just want to see if people have issues before upgrading?
simms22 said:
no, its not necessary. im on the older bootloader, and am using an older radio, in a 5.1 rom. no issues.
Click to expand...
Click to collapse
Do you mind answering my question along with the question below me? And also what radio you are using
Manalow88 said:
Do you mind posting what version your bootloader is
Click to expand...
Click to collapse
the one that came with the n6, originally.
---------- Post added at 01:48 PM ---------- Previous post was at 01:48 PM ----------
JulesJam said:
Is there some reason you didn't upgrade to the new bootloader and radio? Just want to see if people have issues before upgrading?
Click to expand...
Click to collapse
no real reason. everything us working, its not broken, so i didnt update it.
---------- Post added at 01:55 PM ---------- Previous post was at 01:48 PM ----------
Manalow88 said:
Do you mind answering my question along with the question below me? And also what radio you are using
Click to expand...
Click to collapse
if you are on a 5.0.2 rom, you can just try dirty flashing a 5.1 rom over what you have(make a nandroid backup in recovery first). if that doesnt work, you can restore your backup or wipe data and reflash. you dont need to flash stock first. i reflashed the lrx22c radio after trying the new radio. but im on tmobile and didnt receive calls while on lte, so i reflashed the older radio. btw, im using rastapop 5.1 at the moment(and dirty flashed over to it from android 5.0.2.
Related
I have new Verizon Moto X Dev Edition. Messed up. Thought it was already on 4.4.2. Not, it's on 4.2.2. Unlocked bootloader and installed twrp and rooted. Wanting to update it to 4.4.2. Thinking from reading that I need to get back to stock recovery for OTA update if that is possible over wifi since phone is not activated yet. Can't find 4.2.2 stock recovery and not sure if that is what I need to do anyway. Is that what I need to do and/or is there a better way? Thanks
dukeoid said:
I have new Verizon Moto X Dev Edition. Messed up. Thought it was already on 4.4.2. Not, it's on 4.2.2. Unlocked bootloader and installed twrp and rooted. Wanting to update it to 4.4.2. Thinking from reading that I need to get back to stock recovery for OTA update if that is possible over wifi since phone is not activated yet. Can't find 4.2.2 stock recovery and not sure if that is what I need to do anyway. Is that what I need to do and/or is there a better way? Thanks
Click to expand...
Click to collapse
Well I too have a Dev Edition but is SIM-Unlocked so it isn't Verizon.
If all you want to do is update, you could install Custom ROM although you will lose Motorola's Active Display, Always Listening etc...
If you want complete stock and have to reflash TWRP and root your phone, you will need to flash the stock firmware using fastboot or a utility.
Finally found 4.2.2 . When trying RSD fail at gpt bin, also fails there with manual flashing. Any ideas?
Edit...Finally got it. Different version of 4.2.2 did it.
Alecegonce101 said:
Well I too have a Dev Edition but is SIM-Unlocked so it isn't Verizon.
Click to expand...
Click to collapse
Um, all VZW Moto Xs are SIM-unlocked.
dukeoid said:
Finally found 4.2.2 . When trying RSD fail at gpt bin, also fails there with manual flashing. Any ideas?
Edit...Finally got it. Different version of 4.2.2 did it.
Click to expand...
Click to collapse
I hope it wasn't the pre-camera 4.2.2....or you might be in a tough spot now.... Risking a brick. ?
---------- Post added at 10:09 AM ---------- Previous post was at 10:08 AM ----------
Unless the first firmware was also pre camera... Then you're OK.
dukeoid said:
I have new Verizon Moto X Dev Edition. Messed up. Thought it was already on 4.4.2. Not, it's on 4.2.2. Unlocked bootloader and installed twrp and rooted. Wanting to update it to 4.4.2. Thinking from reading that I need to get back to stock recovery for OTA update if that is possible over wifi since phone is not activated yet. Can't find 4.2.2 stock recovery and not sure if that is what I need to do anyway. Is that what I need to do and/or is there a better way? Thanks
Click to expand...
Click to collapse
dukeoid said:
Finally found 4.2.2 . When trying RSD fail at gpt bin, also fails there with manual flashing. Any ideas?
Edit...Finally got it. Different version of 4.2.2 did it.
Click to expand...
Click to collapse
Taking OTA's is incremental, so if you are the initial shipping 4.2.2 you need to take the first 4.2.2 w/camera OTA, then the 4.4 OTA, then the 4.4.2 OTA... a real time waster and pain in the rear.
Best way... Grab the SBF for the version you want to be on, and flash it... i.e. you mention going to 4.4.2, so... grab the 4.4.2 SBF and flash it.
Since you have a Dev Edition, why not just go to 4.4.4? it has a few bug fixes, and is stable. For me and many others its no worse than 4.4.2 as far as performance and battery.
Once you arrive on the ROM you want, you can flash TWRP and root.
KidJoe said:
Best way... Grab the SBF for the version you want to be on, and flash it... i.e. you mention going to 4.4.2, so... grab the 4.4.2 SBF and flash it.
t.
Click to expand...
Click to collapse
OTA'ed to 4.4.2. But for future reference you can skip versions and SBF to the one you want??
dukeoid said:
OTA'ed to 4.4.2. But for future reference you can skip versions and SBF to the one you want??
Click to expand...
Click to collapse
Yup! ?
As long as it's not a lower version.
dukeoid said:
OTA'ed to 4.4.2. But for future reference you can skip versions and SBF to the one you want??
Click to expand...
Click to collapse
OTA = Incremental. Only patches the changed/updated parts.
SBF/FXZ = "all inclusive" or "image files".. and overwrites entire partitions/parts.
So yes. You can just flash the newer SBF file. (As @Darth said... as long as the SBF you are flashing is NEWER than the version on your phone... i.e. NEVER DOWNGRADE)
Greetings;
I just received my Moto X 1097 Canadian Variant and was
wondering if there are any files that I can get from a virgin
device before I attempt to root & etc.?
Or backup files that one day I might need to bring back my
device to life from Bricked status?!!
Thank you.
As long as you can get your hands on factory images, I wouldn't worry too much about system files. Otherwise, you should be able to find ways to make a system image; however that might require root or custom recovery.
korockinout13 said:
As long as you can get your hands on factory images, I wouldn't worry too much about system files. Otherwise, you should be able to find ways to make a system image; however that might require root or custom recovery.
Click to expand...
Click to collapse
Yes I usually unlock the Bootloader and Root, but since being a Canadian means not having a choice when it comes to "Communication Industries"
I couldn't buy a "Developer Edition" or any "32Gb" version for that matter!! Hence getting a XT1097.
I was wondering about downgrading, I understand once I upgrade to Lollipop, there is no way back, right? If that is the case, can I just ignore the OTA? And stay on KK?
Thank you.
samteeee said:
Yes I usually unlock the Bootloader and Root, but since being a Canadian means not having a choice when it comes to "Communication Industries"
I couldn't buy a "Developer Edition" or any "32Gb" version for that matter!! Hence getting a XT1097.
I was wondering about downgrading, I understand once I upgrade to Lollipop, there is no way back, right? If that is the case, can I just ignore the OTA? And stay on KK?
Thank you.
Click to expand...
Click to collapse
Without factory images or a full backup, there is no way back. However, it is safe to downgrade as long as you don't try to downgrade the bootloader or partition table. You can ignore the OTA, but it will probably be annoying. You might as well upgrade.
samteeee said:
Yes I usually unlock the Bootloader and Root, but since being a Canadian means not having a choice when it comes to "Communication Industries"
I couldn't buy a "Developer Edition" or any "32Gb" version for that matter!! Hence getting a XT1097.
Click to expand...
Click to collapse
I have a thread on this in the General forum. If you update to lollipop using Motorola Device Manager, you will have a copy of fastboot flashable Lollipop files on your computer. Search for my post on General.
If you want the fastboot flashable Kit Kat files, you can request them from Motorola. If they won't give them to you, then you can search to see if anyone has copies of them. This is for Telus right? You also can specifically ask if anyone has them, they may.
The other thing you can do is after you unlock the bootloader and flash TWRP recovery, is to make a nandroid of your stock system on kit kat and save it on your computer. Then flash back to stock recovery and upgrade to lollipop using MDM. Then flash TWRP recovery again and make a nandroid of stock lollipop, save it to your computer, then root.
---------- Post added at 10:08 PM ---------- Previous post was at 10:02 PM ----------
samteeee said:
I couldn't buy a "Developer Edition" or any "32Gb" version for that matter!! Hence getting a XT1097.
I was wondering about downgrading, I understand once I upgrade to Lollipop, there is no way back, right?
Click to expand...
Click to collapse
First off are you sure your device shipped with kitkat? Double check on that.
Once you upgrade to lollipop, you cannot downgrade the bootloader or the partition table back to kit kat, but you should be able to downgrade the kernel and the system back to kit kat w/o any issues. Idk about trying to downgrade the radios.
JulesJam said:
I have a thread on this in the General forum. If you update to lollipop using Motorola Device Manager, you will have a copy of fastboot flashable Lollipop files on your computer. Search for my post on General.
If you want the fastboot flashable Kit Kat files, you can request them from Motorola. If they won't give them to you, then you can search to see if anyone has copies of them. This is for Telus right? You also can specifically ask if anyone has them, they may.
The other thing you can do is after you unlock the bootloader and flash TWRP recovery, is to make a nandroid of your stock system on kit kat and save it on your computer. Then flash back to stock recovery and upgrade to lollipop using MDM. Then flash TWRP recovery again and make a nandroid of stock lollipop, save it to your computer, then root.
---------- Post added at 10:08 PM ---------- Previous post was at 10:02 PM ----------
First off are you sure your device shipped with kitkat? Double check on that.
Once you upgrade to lollipop, you cannot downgrade the bootloader or the partition table back to kit kat, but you should be able to downgrade the kernel and the system back to kit kat w/o any issues. Idk about trying to downgrade the radios.
Click to expand...
Click to collapse
Thank you for your reply.
I just turned it on for the very first time! And I can confirm that it is on KK.
I like your solutions and will email Motorola tonight for the KK files. I will however upgrade to Lollipop via MDM so that I do have a copy of the "Fastboot Flashable Lollipop files".
Any suggestion on Rooting method? Also to copy the Nandroid to Pc, do I pull it with ADB? or just copy them from internal storage? And lastly I think once I upgrade, doesn't make sense to downgrade with so many complications, eh?
Thank you again.
korockinout13 said:
Without factory images or a full backup, there is no way back. However, it is safe to downgrade as long as you don't try to downgrade the bootloader or partition table. You can ignore the OTA, but it will probably be annoying. You might as well upgrade.
Click to expand...
Click to collapse
Thanks bro.
Is your phone Telus or Wind mobile?
The original kitkat files for both can be downloaded no problem.
The 5.0.1 lollipop image for Telus can also be downloaded.
You can safely downgrade from Lollipop to Kitkat as long as you unlock your bootloader.
Steve-x said:
Is your phone Telus or Wind mobile?
The original kitkat files for both can be downloaded no problem.
The 5.0.1 lollipop image for Telus can also be downloaded.
You can safely downgrade from Lollipop to Kitkat as long as you unlock your bootloader.
Click to expand...
Click to collapse
Hi
My phone is Telus Mobility.
Are the files on Motorola site?
Thank you.
Hi guys and gals,
Hopefully this hasn't been asked before, but, here goes:
I just got my N6 today and i wanted to put a custom rom on the device.. I've unlocked the bootloader, installed TWRP and got root, but everytime i try to flash a rom it give me this error:
this package supports bootloader(s) moto-apq8084-71.5 0x7105 moto-apq8084-71.08, 0x7108; this device has bootloader 0x7110
Any help is greatly appreciated.
dpruim said:
Hi guys and gals,
Hopefully this hasn't been asked before, but, here goes:
I just got my N6 today and i wanted to put a custom rom on the device.. I've unlocked the bootloader, installed TWRP and got root, but everytime i try to flash a rom it give me this error:
this package supports bootloader(s) moto-apq8084-71.5 0x7105 moto-apq8084-71.08, 0x7108; this device has bootloader 0x7110
Any help is greatly appreciated.
Click to expand...
Click to collapse
What is the name of the rom you we`re trying to flash?
I've tried several. All failed with the exact same "error"
update your bootloader
simms22 said:
update your bootloader
Click to expand...
Click to collapse
Isn`t 71.10 the latest besides the one from the M preview? Besides that its something i never experienced that a custom rom didn`t install because of the bootloader version.
gee2012 said:
Isn`t 71.10 the latest besides the one from the M preview? Besides that its something i never experienced that a custom rom didn`t install because of the bootloader version.
Click to expand...
Click to collapse
latest, i have no clue, ill have to boot to the bootloader to look, but im using the m bootloader. i think either 5.0.1 or 5.1 had a new bootloader, that you had to flash to boot 5.0.1 or 5.1 roms. i had to install the m bootloader to boot m, or it wouldnt boot.
if the op just got his n6 today, it would probably still be on 5.0, so it makes sense that it needs to be updated.
simms22 said:
latest, i have no clue, ill have to boot to the bootloader to look, but im using the m bootloader. i think either 5 or 5.1 had a new bootloader, that you had to flash to boot 5 or 5.1 roms. i had to install the m bootloader to boot m, or it wouldnt boot.
Click to expand...
Click to collapse
Strange, my bootloader from LMY47Z (71.10) boots fine with Chroma for instance and even CM 12.1 isn`t a problem.
gee2012 said:
Strange, my bootloader from LMY47Z (71.10) boots fine with Chroma for instance and even CM 12.1 isn`t a problem.
Click to expand...
Click to collapse
yea, but thats the latest, 5.1.1, only m is "newer" than that.
simms22 said:
yea, but thats the latest, 5.1.1, only m is "newer" than that.
Click to expand...
Click to collapse
True, but OP states custom roms don`t boot with the 71.10 bootloader. That would be strange unless he is trying to flash a custom M based rom.
gee2012 said:
True, but OP states custom roms don`t boot with the 71.10 bootloader. That would be strange unless he is trying to flash a custom M based rom.
Click to expand...
Click to collapse
it says he has a 7110 bootloader and needs a 7105 or 7108 bootloader. maybe he is flashing an old rom?
---------- Post added at 02:09 PM ---------- Previous post was at 02:04 PM ----------
btw, m bootloader is 71.11
simms22 said:
it says he has a 7110 bootloader and needs a 7105 or 7108 bootloader. maybe he is flashing an old rom?
---------- Post added at 02:09 PM ---------- Previous post was at 02:04 PM ----------
btw, m bootloader is 71.11
Click to expand...
Click to collapse
Right, the second preview is supposed to be released coming monday the 29th.
I'd be interested in what roms are being flashed that have an older boot loader dependency. Maybe they're stock based?
I've still got the original bootloader and flashing aosp 5.1.1 roma no issue
I'm hating 5.1.. Might be a one off case on my phone but it is simply way too buggy and the battery life is awful compared to what I had going on my rooted 5.0
Like the thread title says, does anyone know if it's doable to get back to 5.0 so I can get back a rooted/stable phone?
Try a cache clearing first, that usually helps with those kind of issues.
bik2101 said:
I'm hating 5.1.. Might be a one off case on my phone but it is simply way too buggy and the battery life is awful compared to what I had going on my rooted 5.0
Like the thread title says, does anyone know if it's doable to get back to 5.0 so I can get back a rooted/stable phone?
Click to expand...
Click to collapse
If your bootloader is unlocked just flash the system.img and boot.img files from 5.0 or 444 through mfastboot. DO NOT FLASH ANYTHING ELSE
chrisrozon said:
Try a cache clearing first, that usually helps with those kind of issues.
Click to expand...
Click to collapse
Yeah.. Unfortunately have done a few of those and factory reset as well.
Sent from my XT1096 using Tapatalk
I am also wondering if it is possible to flash back. Are you saying you have flashed system.img and boot.img and were able to? Wouldnt flashing boot.img give you the old bootloader and possibly brick?
bik2101 said:
I'm hating 5.1.. Might be a one off case on my phone but it is simply way too buggy and the battery life is awful compared to what I had going on my rooted 5.0
Like the thread title says, does anyone know if it's doable to get back to 5.0 so I can get back a rooted/stable phone?
Click to expand...
Click to collapse
Did you take the OTA to get to 5.1?
---------- Post added at 07:10 AM ---------- Previous post was at 07:09 AM ----------
d33dvb said:
I am also wondering if it is possible to flash back. Are you saying you have flashed system.img and boot.img and were able to? Wouldnt flashing boot.img give you the old bootloader and possibly brick?
Click to expand...
Click to collapse
boot.img is not the bootloader. It is the kernel and the ramdisk.
motoboot.img is the bootloader.
JulesJam said:
Did you take the OTA to get to 5.1?
---------- Post added at 07:10 AM ---------- Previous post was at 07:09 AM ----------
boot.img is not the bootloader. It is the kernel and the ramdisk.
motoboot.img is the bootloader.
Click to expand...
Click to collapse
Thank you for the clarification. I took the OTA, like a doof. Do you think its possible to flash back by flashing system and boot for 5.0 with fastboot and the rooted 5.0 with mofo? Will 5.0 boot on the new 5.1 bootloader and partition table?
Woke up this morning to a plugged in phone @92% and scorching hot. Thanks 5.1
d33dvb said:
Thank you for the clarification. I took the OTA, like a doof. Do you think its possible to flash back by flashing system and boot for 5.0 with fastboot and the rooted 5.0 with mofo? Will 5.0 boot on the new 5.1 bootloader and partition table?
Click to expand...
Click to collapse
You definitely cannot flash using mofo if you upgraded your bootloader to 5.1. Your copy of Mofo was specific not only for your device, but for 4.4.4 and 5.0 or 5.0.2 bootloader depending on your device. I put all of that in the noob guide.
d33dvb said:
Woke up this morning to a plugged in phone @92% and scorching hot. Thanks 5.1
Click to expand...
Click to collapse
Back up your data and do a factory reset.
---------- Post added at 06:36 PM ---------- Previous post was at 06:16 PM ----------
d33dvb said:
Will 5.0 boot on the new 5.1 bootloader and partition table?
Click to expand...
Click to collapse
Idk b/c I didn't upgrade my bootloader to 5.1. What version of the 5.1 bootloader are you on, 60.16?
JulesJam said:
Did you take the OTA to get to 5.1?
---------- Post added at 07:10 AM ---------- Previous post was at 07:09 AM ----------
boot.img is not the bootloader. It is the kernel and the ramdisk.
motoboot.img is the bootloader.
Click to expand...
Click to collapse
I was on mofo 5.0.2 (?) then flashed the stock 5.0 then the 5.1 update that's floating around here somewhere. are you saying that it might be possible to get back to mofo 5.0? since i didn't take OTA?! that would be amazing.
bik2101 said:
I was on mofo 5.0.2 (?) then flashed the stock 5.0 then the 5.1 update that's floating around here somewhere. are you saying that it might be possible to get back to mofo 5.0? since i didn't take OTA?! that would be amazing.
Click to expand...
Click to collapse
What verison of the bootloader are you running - 60.11, 60.14 or 60.16?
I am on 60.16, and so bummed. I am guessing it is safe to try with normal fastboot to just try flashing system.img from stock 5.0 worst that could happen is I get a failed message or have to reflash 5.1 stock. I wonder if fastboot will allow me to flash system.img of an older version. I'm willing to take one for the team if someone can confirm the safest route to try, obviously not flashing gpt motoboot or anything else I read.
---------- Post added at 04:30 AM ---------- Previous post was at 04:27 AM ----------
I hate being the idiot example. I knew better than to flash 5.1 ota. I had just gotten zAnti and cSploit working with iptables and arp poisoning too. If anyone is curious, find all the com.zAnti and com.cSploit folders and make them all 777.
JulesJam said:
What verison of the bootloader are you running - 60.11, 60.14 or 60.16?
Click to expand...
Click to collapse
60.16 ..... is that workable? or am I stuck
bik2101 said:
60.16 ..... is that workable? or am I stuck
Click to expand...
Click to collapse
MoFo won't work on the 60.16 or 60.14 bootloaders. With 60.14, which was the 5.1 soak test bootloader, people have reported being able to downgrade back to 60.11 bootloader, but not with the 60.16.
---------- Post added at 01:51 AM ---------- Previous post was at 01:43 AM ----------
d33dvb said:
I am on 60.16, and so bummed. I am guessing it is safe to try with normal fastboot to just try flashing system.img from stock 5.0 worst that could happen is I get a failed message or have to reflash 5.1 stock. I wonder if fastboot will allow me to flash system.img of an older version.
Click to expand...
Click to collapse
IME you can flash stock, signed earlier system.img using mfastboot no problem. But you may need to flash the 5.0 boot.img and radios, too. If you have the system in sparsechunks you can use regular fastboot.
---------- Post added at 01:54 AM ---------- Previous post was at 01:51 AM ----------
d33dvb said:
I hate being the idiot example. I knew better than to flash 5.1 ota. I had just gotten zAnti and cSploit working with iptables and arp poisoning too. If anyone is curious, find all the com.zAnti and com.cSploit folders and make them all 777.
Click to expand...
Click to collapse
I had started a thread about plans for the update back in May to discuss these issues.
http://forum.xda-developers.com/moto-x-2014/general/xt0196-rooted-mofo-plans-5-1-update-t3107088
Is it a safe strategy to root by rolling back everything except the partition table (gpt.bin) and bootloader(motoboot.bin) from a stock 5.0 image via fastboot like normal, and then use kingroot to root 5.0, install sunshine and bob is your uncle? I have been unsuccessful at rooting 5.1 even after trying the UAF vulnerabilities recently. Will 5.0 boot on the 60.16 bootloader?
Hello
I have a moto g titan xt1068 dual sim which was originally running stock lollipop 5.02 and was updated with the OTA stagefright update and then the OTA MM6.0 official by motorola.
I have since installed custom roms cyanogen 13.0 and cyanpop 6.2
I know my bootloader is now the latest, so my question is can I now only install MM based roms? or can I still install KK & LP based custom roms?
or will installing LP or KK based roms hard brick my device?
Many thanks for any help
i'd like to know it too...
I'm not sure, but I can't really see why not. The bootloader being the latest changes jack squat on the question of being able to install older versions of Android or not. I mean, I WAS able to install the stock LP ROM on the MM bootloader, but your mileage may vary.
Yeah you can. Just don't try to downgrade your bootloader while downgrading to previous stock Android version. Itll brick your phone.
But just flashing custom Roms is safe.
sagar846 said:
Yeah you can. Just don't try to downgrade your bootloader while downgrading to previous stock Android version. Itll brick your phone.
But just flashing custom Roms is safe.
Click to expand...
Click to collapse
ooh yeah, i remember i installed the MM Stock, and after installed the KK Stock, and with KK made a OTA update to LP and bricked my phone :/
sagar846 said:
Yeah you can. Just don't try to downgrade your bootloader while downgrading to previous stock Android version. Itll brick your phone.
But just flashing custom Roms is safe.
Click to expand...
Click to collapse
That's bullsh-t.. You can always downgrade your rom, but you have to be sure you're not downgrading your bootloader. So if you're using oneclick installer you have to remove the command from the script which will try to downgrade your bootloader. Also after downgrading you have to be super sure that you will not update it with OTA!
Btw.: I'm not sure downgrading through fastboot can even brick your phone.
zman01 said:
That's bullsh-t.. You can always downgrade your rom, but you have to be sure you're not downgrading your bootloader. So if you're using oneclick installer you have to remove the command from the script which will try to downgrade your bootloader. Also after downgrading you have to be super sure that you will not update it with OTA!
Btw.: I'm not sure downgrading through fastboot can even brick your phone.
Click to expand...
Click to collapse
What if i downgrade to kk without downgrading the bootloader and then i flash back mm firmware? (with rsd lite for example)
h4ck3r00 said:
What if i downgrade to kk without downgrading the bootloader and then i flash back mm firmware? (with rsd lite for example)
Click to expand...
Click to collapse
You can flash whatever version you want if you're not downgrading your BL
zman01 said:
You can flash whatever version you want if you're not downgrading your BL
Click to expand...
Click to collapse
So, if am right, i can do whatever i want but i must not touch the bootloader.
Thanks man! :good:
h4ck3r00 said:
So, if am right, i can do whatever i want but i must not touch the bootloader.
Thanks man! :good:
Click to expand...
Click to collapse
That's right.. You can touch your bootloader only when you have to upgrade it, for example in case of updating to Android N. Which I think will never happen (of course officially).
Here you can find a nice guide to downgrade your Android version.
zman01 said:
That's bullsh-t.. You can always downgrade your rom, but you have to be sure you're not downgrading your bootloader. So if you're using oneclick installer you have to remove the command from the script which will try to downgrade your bootloader. Also after downgrading you have to be super sure that you will not update it with OTA!
Btw.: I'm not sure downgrading through fastboot can even brick your phone.
Click to expand...
Click to collapse
FFS, Did you actually read my post. I said NOT to Downgrade the bootloader while downgrading to a previous stock version via fastboot.
sagar846 said:
FFS, Did you actually read my post. I said NOT to Downgrade the bootloader while downgrading to a previous stock version via fastboot.
Click to expand...
Click to collapse
Yeah sorry, I was a bit tired.
Thank you all for your help it is much appreciated.