If i downgrade my Xt1541 which has marshmallow stock rom on it , without flashing bootloader.img or gpt.bin , would that all go to plan ?
Also, if I accepted an ota update when on lollipop, would it hard brick my phone, and if it did , would there be a recovery method?
Because if I accepted an upgrade back to marshmallow via ota, surely it would not break the bootloader because it is upgrading to the one which is already there? correct me if I am wrong.
Thank you for any advice with this
I downgraded mine without flashing those two files and it worked perfectly and I see no reason why an OTA wouldn't work. You'll have to unlock your bootloader to downgrade though.
Related
Hello. This thread is mainly for questioning/research/knowledge, as I don't have any major issue with my phone right now. I had retail ar firmware 4.4.4 with locked LB, converted to 4.4.4 Retail BR, tried to install the ota, it didn't (because locked bl) and when I tried to go back to retail AR i bricked (downgraded for boot) and I couldn't flash it properly due to preflash validation error (locked bl) so I unlocked BL and now everything works fine, and I sucessfully installed the XT1033 OTA on my XT1032, runs pretty good.
I've been reading on the incompatibility between bootloaders of 4.4 and 5.0.
For now I will wait to official update for XT1032 and flash that, but couldn't you just use the reflash bootloader tool that is around this forum and flash a 4.4.4 bootloader and all the stock firmware files? In case I for some reason wanna go back for 4.4.4.
If you install 5.0 on a 4.4 bootloader using cwm, does it work correctly? If it does, why do they update the bootloader in the first place?
Is there any working custom recovery for L? or in development? In case In the future when the OTA gets released I wanted to flash viper4audio (I'm priving myself of that beauty that I used on old phones just for the locked BL [warranty brah] but obviously not a problem now..) or I could just root and use one of those zip flashing apps? (I cant remember its name)
Thanks.
ianxblog said:
Hello. This thread is mainly for questioning/research/knowledge, as I don't have any major issue with my phone right now. I had retail ar firmware 4.4.4 with locked LB, converted to 4.4.4 Retail BR, tried to install the ota, it didn't (because locked bl) and when I tried to go back to retail AR i bricked (downgraded for boot) and I couldn't flash it properly due to preflash validation error (locked bl) so I unlocked BL and now everything works fine, and I sucessfully installed the XT1033 OTA on my XT1032, runs pretty good.
I've been reading on the incompatibility between bootloaders of 4.4 and 5.0.
For now I will wait to official update for XT1032 and flash that, but couldn't you just use the reflash bootloader tool that is around this forum and flash a 4.4.4 bootloader and all the stock firmware files? In case I for some reason wanna go back for 4.4.4.
If you install 5.0 on a 4.4 bootloader using cwm, does it work correctly? If it does, why do they update the bootloader in the first place?
Is there any working custom recovery for L? or in development? In case In the future when the OTA gets released I wanted to flash viper4audio (I'm priving myself of that beauty that I used on old phones just for the locked BL [warranty brah] but obviously not a problem now..) or I could just root and use one of those zip flashing apps? (I cant remember its name)
Thanks.
Click to expand...
Click to collapse
my phone now DEAD
Dead After downgrade to 4.4.3 then Update to 4.4.4 from 5.0
Sandivisi said:
my phone now DEAD
Dead After downgrade to 4.4.3 then Update to 4.4.4 from 5.0
Click to expand...
Click to collapse
you mean the hard brick when your pc only detects it as qcom-something? that's bad for you
I only softbricked mine luckily, but I'll let you know anyway I felt damn stupid when I couldn't boot my phone because of my sudden impatience after waiting months from this update, just because didn't wait a little more
iirc there are some methods on the forum I think using that tool I mentioned to get it back, good luck with that
ianxblog said:
Hello. This thread is mainly for questioning/research/knowledge, as I don't have any major issue with my phone right now. I had retail ar firmware 4.4.4 with locked LB, converted to 4.4.4 Retail BR, tried to install the ota, it didn't (because locked bl) and when I tried to go back to retail AR i bricked (downgraded for boot) and I couldn't flash it properly due to preflash validation error (locked bl) so I unlocked BL and now everything works fine, and I sucessfully installed the XT1033 OTA on my XT1032, runs pretty good.
I've been reading on the incompatibility between bootloaders of 4.4 and 5.0.
For now I will wait to official update for XT1032 and flash that, but couldn't you just use the reflash bootloader tool that is around this forum and flash a 4.4.4 bootloader and all the stock firmware files? In case I for some reason wanna go back for 4.4.4.
If you install 5.0 on a 4.4 bootloader using cwm, does it work correctly? If it does, why do they update the bootloader in the first place?
Is there any working custom recovery for L? or in development? In case In the future when the OTA gets released I wanted to flash viper4audio (I'm priving myself of that beauty that I used on old phones just for the locked BL [warranty brah] but obviously not a problem now..) or I could just root and use one of those zip flashing apps? (I cant remember its name)
Thanks.
Click to expand...
Click to collapse
I suggest you not to downgrade to 4.4.4 as of now. you flashed OTA and you are in lollipop now.. Enjoy.... And wait for official release OTA for Xt1032 and firmware files. Once it released, Devs will surely create flashable zips... then you can reflash your version lollipop... People reporting bricks and many dspaly issue when they tried downgrading it..
---------- Post added at 10:53 AM ---------- Previous post was at 10:47 AM ----------
Sandivisi said:
my phone now DEAD
Dead After downgrade to 4.4.3 then Update to 4.4.4 from 5.0
Click to expand...
Click to collapse
Why did you downgrade to 4.4.3 instead of 4.4.4 ?
padhu1989 said:
I suggest you not to downgrade to 4.4.4 as of now. you flashed OTA and you are in lollipop now.. Enjoy.... And wait for official release OTA for Xt1032 and firmware files. Once it released, Devs will surely create flashable zips... then you can reflash your version lollipop... People reporting bricks and many dspaly issue when they tried downgrading it..
---------- Post added at 10:53 AM ---------- Previous post was at 10:47 AM ----------
Why did you downgrade to 4.4.3 instead of 4.4.4 ?
Click to expand...
Click to collapse
because i dont have image file 4.4.4 . only file 4.4.3 on my pc
Here's the scenario:
I converted Moto G XT1033 4.4.4 to GPE 4.4.2
Then upgraded to GPE 4.4.4 and GPE 5.0.1, both by OTA
GPE 5.0.1 OTA ended up in softbrick
So now I cannot repeat the process beacause of the new bootloader, GPE 5.0.1 OTA brought with itself. And that bootloader would cause a hardbrick if I tried GPE 4.4.4 OTA on the device now
Questions: (No question is related to the other)
Would I be able to install Stock Lollipop OTA when I get one on 'Stock rom'? (I can revert to Stock 4.4.4) Would Stock Lollipop OTA mess up with the current bootloader, GPE Lollipop OTA has installed?
Is there any way I could flash Lollipop Stock image later, when it's available?
What can I do to set things right with the 'bootloader messup' that's caused right now?
Thanks, in advance!
emarld2011 said:
Here's the scenario:
I converted Moto G XT1033 4.4.4 to GPE 4.4.2
Then upgraded to GPE 4.4.4 and GPE 5.0.1, both by OTA
GPE 5.0.1 OTA ended up in softbrick
So now I cannot repeat the process beacause of the new bootloader, GPE 5.0.1 OTA brought with itself. And that bootloader would cause a hardbrick if I tried GPE 4.4.4 OTA on the device now
Questions: (No question is related to the other)
Would I be able to install Stock Lollipop OTA when I get one on 'Stock rom'? (I can revert to Stock 4.4.4) Would Stock Lollipop OTA mess up with the current bootloader, GPE Lollipop OTA has installed?
Is there any way I could flash Lollipop Stock image later, when it's available?
What can I do to set things right with the 'bootloader messup' that's caused right now?
Thanks, in advance!
Click to expand...
Click to collapse
You are another who has made a stupid mistake, you should HAVE READ MY THREAD!
You need to wait untill the Lollipop Factory images are published, then we can get a blankflasher and restore your bootloader.
Once your bootloader is working again, you can flash Lollipop without problems.
You need to wait 1 or 2 months.
GI0\/\NNI said:
You are another who has made a stupid mistake, you should HAVE READ MY THREAD!
You need to wait untill the Lollipop Factory images are published, then we can get a blankflasher and restore your bootloader.
Once your bootloader is working again, you can flash Lollipop without problems.
You need to wait 1 or 2 months.
Click to expand...
Click to collapse
Nope. I did read your thread after softbrick. And that's why I didn't install any OTA's after v5's.
I flashed 4.4.4. It's not an OTA!
I'm currently running 4.4.4 on 5.x bootloader.
Now what I'm asking is,
Would I be able to install 5.x OTA when I get it?
Before the factory image and all that thing.
PS: 5.x hasn't arrived for general public in INDIA yet. What I was trying was Brazil OTA.
Hi all,
I just tried to upgrade my old CyanogenMod from January to a recent nightly and got hit by an error caused by my old KK bootloader (http://forum.xda-developers.com/mot...uently-questions-t2996087/page24#post59520890). The guy in that thread offers a supposedly official Brazilian Lollipop bootloader, but I'm a bit hesitant 1) downloading something like that from unknown origin on the net and 2) I have a UK XT1032 (I think it was unbranded, bought in Tesco), not Brazilian. So what are my options?
Can I get the official bootloader from Motorola, by downgrading to 4.4.4 and then get the OTA? Or is it not available yet for my phone?
If I were to do that, can I unlock/root the phone again and get a custom ROM or is there no unlock yet for the Moto stock LP stuff?
What are my options, besides staying on my January CM ROM?
Thank you very much for any input!
You could manually flash the GB 4.4.4 stock ROM for the xt1032, update apps, take the 5.02 OTA update, and be running a Lollipop bootloader.
I just flash manually stock 5.0.2
Mister Muscle said:
I just flash manually stock 5.0.2
Click to expand...
Click to collapse
Which version do you recommend for the xt1032?
Or, if you're skilled enough, just manually fastboot flash the tz, rpm, sdi, aboot and sbl1 partitions extracted from any 5.0.x OTA package for XT1032. I did the procedure on my 1031 (with corresponding files for the 1031, of course) and it worked nicely.
Sent from Google Nexus 4 @ CM12
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
here's one more option http://forum.xda-developers.com/moto-g/help/rc-faq-cm12-frequently-questions-t2996087/post59520890#post59520890 .
it doesn't need the ota-update-way
audit13 said:
You could manually flash the GB 4.4.4 stock ROM for the xt1032, update apps, take the 5.02 OTA update, and be running a Lollipop bootloader.
Click to expand...
Click to collapse
That sounds like a good plan. So
1) GB 5.02 OTA is already out for all XT1032 devices? I read somewhere else we're still waiting?
2) Is my phone still unlocked after this, i.e. can I install a custom recovery, root etc. and custom roms afterwards?
Thanks =)
The 5.02 OTA for GB ROM has been released from what I have read.
Once the phone is sim and bootloader unlocked, flashing ROMs, recoveries, etc. will not relock the bootloader or sim lock the phone.
audit13 said:
The 5.02 OTA for GB ROM has been released from what I have read.
Once the phone is sim and bootloader unlocked, flashing ROMs, recoveries, etc. will not relock the bootloader or sim lock the phone.
Click to expand...
Click to collapse
That's great to know! My worries was about that flashing the bootloader could result in a newly locked one. Thank you very much!
Is there any way I can get back to Lollipop. Am new to XDA so, please forgive anything wrong I have posted.
We need more information. Is your phone rooted? Bootloader unlocked? TWRP installed? Are you on a custom ROM or OTA?
ajinkya.nazare said:
We need more information. Is your phone rooted? Bootloader unlocked? TWRP installed? Are you on a custom ROM or OTA?
Click to expand...
Click to collapse
No my isn't rooted, Completely stock.
I downgraded my XT1541 Moto G3 to Lollipop yesterday. I had to unlock the bootloader first. Then I downloaded a suitable 5.1.1 stock ROM and flashed everything except gpt.bin and bootloader.img. Worked perfectly and I got the Stagefright update after setting up the phone. I had terrible scrolling issues with Marshmallow and am much happier back on Lollipop.
It's not for the faint hearted though. You need to install adb and other Android tools first.
downgrade to lollipop in xt1550
rec71 said:
I downgraded my XT1541 Moto G3 to Lollipop yesterday. I had to unlock the bootloader first. Then I downloaded a suitable 5.1.1 stock ROM and flashed everything except gpt.bin and bootloader.img. Worked perfectly and I got the Stagefright update after setting up the phone. I had terrible scrolling issues with Marshmallow and am much happier back on Lollipop.
It's not for the faint hearted though. You need to install adb and other Android tools first.
Click to expand...
Click to collapse
Are you sure? Can you please tell me in detail. What to do for downgrading my xt1550 to lollipop from marshmallow stock OTA updated! Thank you in advance?
Please anybody tried to downgrade from MM to LP & phone still works
as before my xt1032 bricked from long time cuz of downgrade fro LP to KK
Any help will be appreciated
I've switched to LP from MM and again LP, sometimes on KK no problem faced. if there any problem we should clean flash through p.c.
usually I used flashable zip (stock/custom) file, via TWRP.
I believe one line, someone says "no word like brick/dead on today's phone".
so, why fear?
you can downgrade the ROM but NOT the bootloader.
most bricking of devices is due to risky bootloader swaps. the particular scenario that you are referring to is a result of KK OTA update trying to upgrade the bootloader to LP bootloader and failing to do so (if you have been using stock LP ROM before, the bootloader most probably were upgraded then).