Related
Just a suggestion and I'm not sure of the long term implications of this, but I was thinking those who want to avoid the hassles of getting the new bootloader that prevents fastboot boot and flash on locked bootloaders could try the following.
Unzip the update patch file to a folder on your computer.
Delete the bootloader.img file.
Use a text editor to open the file called /META-INF/com/google/android/updater-script and edit out/delete the following lines at the very end of the file:
Code:
ui_print("Writing bootloader...");
assert(package_extract_file("bootloader.img", "/tmp/bootloader.img"),
write_raw_image("/tmp/bootloader.img", "bootloader"),
delete("/tmp/bootloader.img"));
Rezip the folder with the altered files in it.
Boot to clockwork recovery and apply the update zip file with CW (since it's now not signed properly and stock won't do it.
We've had success with this type of modification to the update patch file from Google with people who modded /system files (like replacing gmail or the market app) that got failed updates on 2.3.1 and 2.3.2 updates.
I'm a bit pressed for time, but I may try this myself this weekend. I'm not in a big rush to update yet, though. I'm waiting for things like my custom kernel to become 2.3.3 friendly.
I've made a zip file that has the two changes I suggested above if anyone's brave enough to try it: http://dl.dropbox.com/u/432767/NoBo...9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip
Bit late to the party i'm afraid, allready updated and flashed 2.3.3 update zip. I have lost my root and do not want to "fasboot oem unlock" yet...
My bad for being impatient as normal ^^
I will hold any actions and watch what solutions arise if any. Nice to see some methods being worked on
jamiemac1977 said:
Bit late to the party i'm afraid, allready updated and flashed 2.3.3 update zip. I have lost my root and do not want to "fasboot oem unlock" yet...
My bad for being impatient as normal ^^
I will hold any actions and watch what solutions arise if any. Nice to see some methods being worked on
Click to expand...
Click to collapse
Could you not flash back to stock using Odin and then apply the bootloaderless update after? Just an idea . . .
Is there any risk of bricking? If not I don't mind trying it.
Serious_Beans said:
Is there any risk of bricking? If not I don't mind trying it.
Click to expand...
Click to collapse
There is always a risk of bricking especially when playing with the bootloader.
kenvan19 said:
There is always a risk of bricking especially when playing with the bootloader.
Click to expand...
Click to collapse
But we're not messing with the bootloader per se, we're preventing the update script from checking it and reflashing/updating it.
Still, there's always the risk of bricking as you say.
Slightly off topic, buy why go to all the trouble when fastboot oem unlock is painless and 100% reversible? Why intentionally hobble along on a gimped locked bootloader?
mortzz said:
Slightly off topic, buy why go to all the trouble when fastboot oem unlock is painless and 100% reversible? Why intentionally hobble along on a gimped locked bootloader?
Click to expand...
Click to collapse
Because why not try? I'm not being sarcastic, ironic, facetious or anything rude, seriously; Why not? We have a phone that in terms of recent devices has an unprecedented amount of freedom in terms of rooting and unlocking of the device, why not push that to the limit and see just what can be done. Also, lets be honest, having your SD card wiped by the
Code:
fastboot oem unlock
command is kind of sucky. Sure you can copy all of your files to your computer then copy them all back but that isn't a short process and its boring as hell.
EDIT: @distortedloop: You know I trust you man, my point with my earlier comment is that running an outdated bootloader could very easily lead to an unbootable device, moreso than flashing a custom ROM so I was just being as honest and blunt as I could be
I updated the bootloader using:
fastboot flash bootloader bootloader.img
The bootloader stayed unlocked.
jamiemac1977 said:
Bit late to the party i'm afraid, allready updated and flashed 2.3.3 update zip. I have lost my root and do not want to "fasboot oem unlock" yet...
My bad for being impatient as normal ^^
I will hold any actions and watch what solutions arise if any. Nice to see some methods being worked on
Click to expand...
Click to collapse
You can replace the new bootloader in the update with the old bootloader, here's a link for the old bootloader Bootloader_I9020XXJK1
Has it been tested to work properly? It meaning the the old bootloader?
Sent from my MattedBlues CM7 Google Nexus S!
kenvan19 said:
Has it been tested to work properly? It meaning the the old bootloader?
Sent from my MattedBlues CM7 Google Nexus S!
Click to expand...
Click to collapse
I've been using it with 2.3.3 for the past day and it works perfectly, booting CWM and kernels without an OEM unlock.
Sent from my Nexus S using XDA App
Get Root Back With This Restore.
jamiemac1977 said:
Bit late to the party i'm afraid, allready updated and flashed 2.3.3 update zip. I have lost my root and do not want to "fasboot oem unlock" yet...
My bad for being impatient as normal ^^
I will hold any actions and watch what solutions arise if any. Nice to see some methods being worked on
Click to expand...
Click to collapse
if you have clockwork mod use this as a restore and you will have a rooted 2.3.3 its the easiest way to do it.
http://www.mediafire.com/?c1ww7zb837uycbk
just unzip and put the backup folder in your clockworkmod recovery folder boot into recovery and restore 2.3.3 takes 2 minutes and you will boot up with a rooted 2.3.3
also kept my bootloader unlocked. and i can flash back to any of my roms with no hassle keeping everything in tact.
reddv1 said:
You can replace the new bootloader in the update with the old bootloader, here's a link for the old bootloader Bootloader_I9020XXJK1
Click to expand...
Click to collapse
Ah thanks, I've been looking for that...
I'm going to link it in my root without unlock thread to help people who can't root now that they've updated with locked bootloaders.
kenvan19 said:
Because why not try? I'm not being sarcastic, ironic, facetious or anything rude, seriously; Why not? We have a phone that in terms of recent devices has an unprecedented amount of freedom in terms of rooting and unlocking of the device, why not push that to the limit and see just what can be done. Also, lets be honest, having your SD card wiped by the
Code:
fastboot oem unlock
command is kind of sucky. Sure you can copy all of your files to your computer then copy them all back but that isn't a short process and its boring as hell.
EDIT: @distortedloop: You know I trust you man, my point with my earlier comment is that running an outdated bootloader could very easily lead to an unbootable device, moreso than flashing a custom ROM so I was just being as honest and blunt as I could be
Click to expand...
Click to collapse
No worries on the outdated bootloader....that's why I said "I don't know the long term implications of this."
Everything you said, I couldn't have said better myself.
charlieb620 said:
if you have clockwork mod use this as a restore and you will have a rooted 2.3.3 its the easiest way to do it.
http://www.mediafire.com/?c1ww7zb837uycbk
just unzip and put the backup folder in your clockworkmod recovery folder boot into recovery and restore 2.3.3 takes 2 minutes and you will boot up with a rooted 2.3.3
Click to expand...
Click to collapse
But that defeats the whole point of not wanting to lose and restore your data, since the nandroid will write over all your stuff...
It also doesn't help those who end up with a locked bootloader and no root, since they can't access clockwork.
When I did it I kept my root and unlocked bootloader. If people didn't rush to update than they would have kept everything. I was able to restore my apps and all when I updated to the rooted 2.3.3
Sent from my Nexus S using XDA App
Will relocking bootloader wipe the phone?
I did "fastboot oem unlock" and everything is erased (it's not big deal as I always backup data).
mingkee said:
Will relocking bootloader wipe the phone?
I did "fastboot oem unlock" and everything is erased (it's not big deal as I always backup data).
Click to expand...
Click to collapse
No, the lock won't wipe it, just the unlock.
mingkee said:
Will relocking bootloader wipe the phone?
I did "fastboot oem unlock" and everything is erased (it's not big deal as I always backup data).
Click to expand...
Click to collapse
distortedloop said:
No, the lock won't wipe it, just the unlock.
Click to expand...
Click to collapse
Yes it will. Both locking and unlocking (via fastboot oem lock/unlock) will wipe your phone.
I attempted to flash and unroot my Nexus 6 via Wugfresh's tool, and thought it was a success. I hit 'relock' and now the device is bootloader locked with no OS installed.
However, I can connect via fastboot so far, but I am not very good with it. I think I may also be able to push files, but when I attempted to flash SlimLP the device just reset.
TWRP is still present on the device, but I cannot unlock my bootloader without getting a ROM on there... So I am stuck...
I need to mail this phone back in tomorrow for cracked screen, so I am hoping someone can help me. Thank you.
SidedX said:
I attempted to flash and unroot my Nexus 6 via Wugfresh's tool, and thought it was a success. I hit 'relock' and now the device is bootloader locked with no OS installed.
However, I can connect via fastboot so far, but I am not very good with it. I think I may also be able to push files, but when I attempted to flash SlimLP the device just reset.
TWRP is still present on the device, but I cannot unlock my bootloader without getting a ROM on there... So I am stuck...
I need to mail this phone back in tomorrow for cracked screen, so I am hoping someone can help me. Thank you.
Click to expand...
Click to collapse
First check here... http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Get the sdk tools and once set up, see if you can do adb devices and have the phone show up on the PC, if so, do adb push (name of rom file) then boot to twrp and install. If that doesn't work, check the same page above (since you don't have an OS not sure what would happen) try the unlock instructions for fastboot ( I would wait for someone else to comment before trying this). You might want to message this user http://forum.xda-developers.com/member.php?u=2872010 rootSU and see if he can give guidance, he has lots of experience.
Locked Bootloader
I still can't seem to get past the fact that my bootloader is locked...
Thanks though.
SidedX said:
I attempted to flash and unroot my Nexus 6 via Wugfresh's tool, and thought it was a success. I hit 'relock' and now the device is bootloader locked with no OS installed.
However, I can connect via fastboot so far, but I am not very good with it. I think I may also be able to push files, but when I attempted to flash SlimLP the device just reset.
TWRP is still present on the device, but I cannot unlock my bootloader without getting a ROM on there... So I am stuck...
I need to mail this phone back in tomorrow for cracked screen, so I am hoping someone can help me. Thank you.
Click to expand...
Click to collapse
Try this: Reboot to bootloader, select recovery mode, enter TWRP, mount MTP and push/sideload and flash a flashable image from here http://forum.xda-developers.com/nexu...tboot-t3066052.
Flashing
Hey, thanks for the tip.
The link you sent was dead, and can you help me understand the commands for flashing in ADB with a locked bootloader?
SidedX said:
Hey, thanks for the tip.
The link you sent was dead, and can you help me understand the commands for flashing in ADB with a locked bootloader?
Click to expand...
Click to collapse
Sorry my bad, here it is http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Follow the instructions as i posted, place the download rom in the /android-sdk/platform-tools/ folder and boot in bootloader and select recovery, select adb sideload there and type in cmd: adb sideload name.zip.
Unlocked Bootloader
The thread says they are for unlocked bootloader only.
I have TWRP installed, but for some reason at one point my bootloader was relocked.
So now I have No OS to 'enable oem unlock' to unlock my bootloader.
This is my issue.
SidedX said:
The thread says they are for unlocked bootloader only.
I have TWRP installed, but for some reason at one point my bootloader was relocked.
So now I have No OS to 'enable oem unlock' to unlock my bootloader.
This is my issue.
Click to expand...
Click to collapse
It worked for other users, but hey if you have a better option try that.
I don't understand, what do you mean it worked for other users? The thread specifically states the bootloader has to be unlocked, and unfortunately I do not have an unlocked bootloader.
So I cannot fix this issue unless I either get a rom to flash with a locked bootloader, or somehow force unlock the bootloader
SidedX said:
I don't understand, what do you mean it worked for other users? The thread specifically states the bootloader has to be unlocked, and unfortunately I do not have an unlocked bootloader.
So I cannot fix this issue unless I either get a rom to flash with a locked bootloader, or somehow force unlock the bootloader
Click to expand...
Click to collapse
Look in this thread http://forum.xda-developers.com/nex...bootloader-t3116744/post60931367#post60931367, he had the same problem as you (locked bootloader). I`m not a jehova witness trying to convince you to swap sides, i`am trying to help you here.
Thanks
I see, I was able to adb push /sdcard/. a factory image to get back in with a locked bootloader, thank you.
gee2012 said:
Look in this thread http://forum.xda-developers.com/nex...bootloader-t3116744/post60931367#post60931367, he had the same problem as you (locked bootloader). I`m not a jehova witness trying to convince you to swap sides, i`am trying to help you here.
Click to expand...
Click to collapse
hallelujah!
cam30era said:
hallelujah!
Click to expand...
Click to collapse
That covered the spiritual moment of the day
What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.
mlw4428 said:
What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.
Click to expand...
Click to collapse
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.
According to jcase relocking the bootloader it still shows a modified status code. Your warranty is permanently voided.
Are you on an Edge plan? Otherwise I don't know why you would be returning the phone to upgrade. Also not sure what their rules are on permanently modifying the software of one of these essentially "lease-to-own" devices, so might want to check the terms and conditions if this applies to you. If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Sent from my XT1254 using Tapatalk
SpyderPride said:
If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Click to expand...
Click to collapse
A bootloader unlocked, rooted XT1254 would be more valuable to a buyer than one locked down. You've already done all the hard work.
TheSt33v said:
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.
Click to expand...
Click to collapse
Heya so I'm in a serious bind.
I skipped your step 1 and locked my bootloader. I have an unlocked bootloader. I recently upgraded through the normal verizon pushed update the marshmallow update. Anyhow. I now want to return the phone for an upgrade and well... I locked the bootloader. Then turn the phone off and turned it back on and it now says locked, but it says failed to validate system image. I then got freaked out and downloaded all the step 1 files and tried to flash the stock rom (which i already had installed!) and that doesn't seem to work. Did I brick my phone? Is there any way to get it working now that it is locked with any kind of android at all?
You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
TheSt33v said:
You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Click to expand...
Click to collapse
droidfun1 said:
Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
Click to expand...
Click to collapse
Strange. As far as I understand it, RSDlite just automates fastboot, so even if you're using RSDlite, you're actually using fastboot. Whatever works though.
As for the unlocked bootloader message, see my response to that post you made.
Man, I've really done research until my eyes are ready to pop out lol. Can someone please help me.
I'm using this guide to try and unlock my bootloader: https://www.youtube.com/watch?v=cfpehEkhfyg
Problem is, it's for a verizon version, mine's a note 4 T-mobile sm-n910t3
I'm just a noob and never had to do this unlock bootloader crap on my note 2. I need help.
I just want to unlock the bootloader, and flash recovery, supersu, and a cool rom like res. remix or CM remix.
On the video, the part I'm stuck on is he's using a file: "samsung_unlock_n4-2" with no file extension (.xxx)
I'm assuming this is a bootloader file?? I found a bootloader for my version which is a folder with contents:
FOLDER: BL_N910T3_DOK2 CONTENTS: aboot.mbn / NON-HLOS.bin / rpn.mbn / sbl1.mbn / sdi.mbn / tz.mbn
He goes on to use a CMD and fastboot to temporarily root the phone to install TWRP recovery,
but when he pushes this command: "adb push samsung_unlock_n4-fix /data/local/tmp/"
I don't think I can do that with a folder and I don't know which file to use.
QUESTION:
-DOES ANYONE KNOW WHICH FILE I NEED
-OR-
IS THERE A BETTER WAY TO FLASH A CUSTOM KERNEL THAT UNLOCKS THE BOOTLOADER, THEN ROOT, FLASH ROM AND EVERYTHING A LOT EASIER.
Side note, I didn't know I had to unlock FRP and tried to flash recovery. I also tried CFautoroot.
Both are blocked from working so I'm just assuming the bootloader is locked, otherwise it would say "mode developer" on the stock recovery. Off topic, I started reading about CyanogenMod Installer.... wtf ever happened with this program?!?!?! It sounds awesome!! It said it even would unlock bootloaders and everything. It was only after reading that it was put out of service that I stopped doing my happy dance. why in the fudge brownie cheesecake would you delete something so awesome? Anyway, can you guys plesaea help before I commit android suicide. That would be great.
I CAN'T BOOT INTO CUSTOM RECOVERY. IF I COULD DO THAT I COULD DO ANYTHING. UGGGGG
Anything, whatever...
I'm at a loss here......
It's been days and I'm frustrated.
910T3 versions are locked down for good after 6.0.1MM update but you could DO2 it and then just be stuck without wireless and NFC. Lol, its just so dumb isnt it lol. Pretty soon in the future maybe they'll jusf give us an option to have our devices custom made by your own specs??
djscottallen said:
Man, I've really done research until my eyes are ready to pop out lol. Can someone please help me.
I'm using this guide to try and unlock my bootloader: https://www.youtube.com/watch?v=cfpehEkhfyg
Problem is, it's for a verizon version, mine's a note 4 T-mobile sm-n910t3
I'm just a noob and never had to do this unlock bootloader crap on my note 2. I need help.
I just want to unlock the bootloader, and flash recovery, supersu, and a cool rom like res. remix or CM remix.
On the video, the part I'm stuck on is he's using a file: "samsung_unlock_n4-2" with no file extension (.xxx)
I'm assuming this is a bootloader file?? I found a bootloader for my version which is a folder with contents:
FOLDER: BL_N910T3_DOK2 CONTENTS: aboot.mbn / NON-HLOS.bin / rpn.mbn / sbl1.mbn / sdi.mbn / tz.mbn
He goes on to use a CMD and fastboot to temporarily root the phone to install TWRP recovery,
but when he pushes this command: "adb push samsung_unlock_n4-fix /data/local/tmp/"
I don't think I can do that with a folder and I don't know which file to use.
QUESTION:
-DOES ANYONE KNOW WHICH FILE I NEED
-OR-
IS THERE A BETTER WAY TO FLASH A CUSTOM KERNEL THAT UNLOCKS THE BOOTLOADER, THEN ROOT, FLASH ROM AND EVERYTHING A LOT EASIER.
Side note, I didn't know I had to unlock FRP and tried to flash recovery. I also tried CFautoroot.
Both are blocked from working so I'm just assuming the bootloader is locked, otherwise it would say "mode developer" on the stock recovery. Off topic, I started reading about CyanogenMod Installer.... wtf ever happened with this program?!?!?! It sounds awesome!! It said it even would unlock bootloaders and everything. It was only after reading that it was put out of service that I stopped doing my happy dance. why in the fudge brownie cheesecake would you delete something so awesome? Anyway, can you guys plesaea help before I commit android suicide. That would be great.
I CAN'T BOOT INTO CUSTOM RECOVERY. IF I COULD DO THAT I COULD DO ANYTHING. UGGGGG
Anything, whatever...
I'm at a loss here......
It's been days and I'm frustrated.
Click to expand...
Click to collapse
So far i know is N910T3 bootloader is not locked unlike verizon or at&t .
All you have to do is go to settings/about device and hit on build number 7 times .
You will see in settings "developer options" go to OEM UNLOCK and just turn it on this will unlock your bootloader and make sure reactivation lock is turned off in settings/security.
Thats it now you can go to download mode and flash twrp recovery and flash any rom from twrp compatible for your model.
Trex888 said:
So far i know is N910T3 bootloader is not locked unlike verizon or at&t .
All you have to do is go to settings/about device and hit on build number 7 times .
You will see in settings "developer options" go to OEM UNLOCK and just turn it on this will unlock your bootloader and make sure reactivation lock is turned off in settings/security.
Thats it now you can go to download mode and flash twrp recovery and flash any rom from twrp compatible for your model.
Click to expand...
Click to collapse
Did this work, as in actually unlocking the bootloader right then, just by checking that box? I thought that option only got the phone ready for unlocking or something like that. I'm trying to root a T3 and don't want to flash over an unlocked bootloader, of course.
Trex888 said:
So far i know is N910T3 bootloader is not locked unlike verizon or at&t .
All you have to do is go to settings/about device and hit on build number 7 times .
You will see in settings "developer options" go to OEM UNLOCK and just turn it on this will unlock your bootloader and make sure reactivation lock is turned off in settings/security.
Thats it now you can go to download mode and flash twrp recovery and flash any rom from twrp compatible for your model.
Click to expand...
Click to collapse
Has anyone tried this? I have an 910T3 running a custom ROM on lollipop 5.1.1. I wish to try and upgrade to marshmallow 6.0.1, and eventually a new custom ROM, but I am hesitant to do so as I have read that the 910T3 cannot be downgraded, should I like to return back to lollipop.
After setting OEM unlock , don't you need to use a procedure with adb fastboot through a terminal interface to unlock the bootloader?
I would love to know more about this before I attempt and irreversible upgrade.
Any help or advice would be greatly appreciated.
580guy said:
Has anyone tried this? I have an 910T3 running a custom ROM on lollipop 5.1.1. I wish to try and upgrade to marshmallow 6.0.1, and eventually a new custom ROM, but I am hesitant to do so as I have read that the 910T3 cannot be downgraded, should I like to return back to lollipop.
After setting OEM unlock , don't you need to use a procedure with adb fastboot through a terminal interface to unlock the bootloader?
I would love to know more about this before I attempt and irreversible upgrade.
Any help or advice would be greatly appreciated.
Click to expand...
Click to collapse
Once you upgrade to marshmallow you cannot downgrade to lollipop forget it.
To unlock bootloader you just have to turn on oem unlock thats it no need adb.
If you are already running custom rom as you mentioned your bootloader should be already unlocked.
Trex888 said:
Once you upgrade to marshmallow you cannot downgrade to lollipop forget it.
To unlock bootloader you just have to turn on oem unlock thats it no need adb.
If you are already running custom rom as you mentioned your bootloader should be already unlocked.
Click to expand...
Click to collapse
So, trying to clarify, what you are saying is once you upgrade to marshmallow bootloader is permanently locked? From what I understand, locked bootloaders are what prevent you from changing ROMs, so I assume you are saying that OEM unlock will not work under marshmallow?
So no way I could reflash DOK2 Bootloader and return to Lollipop again? Or just flash a stock Lollipop ROM with ODIN?
580guy said:
So, trying to clarify, what you are saying is once you upgrade to marshmallow bootloader is permanently locked? From what I understand, locked bootloaders are what prevent you from changing ROMs, so I assume you are saying that OEM unlock will not work under marshmallow?
So no way I could reflash DOK2 Bootloader and return to Lollipop again? Or just flash a stock Lollipop ROM with ODIN?
Click to expand...
Click to collapse
Oem unlock will work no problem on marshmallow and you can root & flash roms easily same as lollipop.
But you can only flash marshmallow roms once you upgrade.
I was saying only you cannot downgrade from marshmallow to lollipop.
odin will fail if you try to downgrade
Trex888 said:
Oem unlock will work no problem on marshmallow and you can root & flash roms easily same as lollipop.
But you can only flash marshmallow roms once you upgrade.
I was saying only you cannot downgrade from marshmallow to lollipop.
odin will fail if you try to downgrade
Click to expand...
Click to collapse
Thanks for the reply. In doing more searching around I found one of your older posts from 2016 and it sounds to me like it is a idiosyncrasy of the 910t3. I believe you stated you sold the T3 and ended up getting a 910T for that reason, so you could downgrade if you wished. Looks like I will be sticking with lollipop, unless I get another motherboard or phone. Thanks again for the response.
With the Moto Z, after I returned the phone to stock (flashed stock firmware and locked the bootloader), I'd be able to flash stock firmware with the flashing locked.
Not so with the Motorola One Zoom. In other words, flashing stock and re-locking didn't return the phone to its pristine state. Even when flashing stock firmware over stock firmware, I have to unlock the bootloader.
Differences I observed: on the bootloader screen, when re-locked the Z would show "oem_locked" again. On the One Zoom, it shows "flashing_locked" instead. I'm pretty sure it showed "oem_locked" before unlocking.
WIth the Z, every time I wanted to unlock the bootloader, I had to issue "fastboot oem unlock" followed by the unlock code. The code isn't necessary with the re-locked One Zoom.
In other words, maybe it was a one-way trip. It seems that the phone won't return to its original state, it looks it's modified for good. And I'm afraid this means bye-bye to automatic updates.
Am I missing something here?
My bootloader is also unlocked and I dont have any problems with receiving and installing OTAs I also have Magisk and EdExposed installed - no problems at all.
rafikowy said:
My bootloader is also unlocked and I dont have any problems with receiving and installing OTAs I also have Magisk and EdExposed installed - no problems at all.
Click to expand...
Click to collapse
Phew! I'm glad I'll be able to install OTAs. Have you tried flashing it manually or via RSD Lite? Here it won't flash.
Whammamoosha said:
Phew! I'm glad I'll be able to install OTAs. Have you tried flashing it manually or via RSD Lite? Here it won't flash.
Click to expand...
Click to collapse
Hey, yes, flashing manually. I will provide you flashing scripts tomorrow.
rafikowy said:
Hey, yes, flashing manually. I will provide you flashing scripts tomorrow.
Click to expand...
Click to collapse
Don't bother, I have mine. Thanks.
I would like the flash script if someone would share it
Help with unlocking bootloader
I tried to unlock the bootloader and i am now in a menu with an android with his chest open. In the cmd on my pc i try to type fastboot flashing unlock but it just gives me an error.
I dont know if this is the correct place to post this but i have no idea where to post it and i dont want my phone get bricked.
Bodeman12345 said:
I tried to unlock the bootloader and i am now in a menu with an android with his chest open. In the cmd on my pc i try to type fastboot flashing unlock but it just gives me an error.
I dont know if this is the correct place to post this but i have no idea where to post it and i dont want my phone get bricked.
Click to expand...
Click to collapse
In the settings for developers you gave permission for Factory Unlock?
ilia3367 said:
In the settings for developers you gave permission for Factory Unlock?
Click to expand...
Click to collapse
I enabled the setting to unlock oem bootloader is that the same?
Bodeman12345 said:
I enabled the setting to unlock oem bootloader is that the same?
Click to expand...
Click to collapse
yes.
What instruction did you use to unlock the bootloader?
What region is your device manufactured for?
Does your PC see your device connected to the fastboot mod?
What does this command give you:
Code:
fastboot devices
If the device is detected, enter the command:
Code:
fastboot getvar all
And copy the result here.
ilia3367 said:
yes.
Click to expand...
Click to collapse
Yes I did that
Bodeman12345 said:
Yes I did that
Click to expand...
Click to collapse
Answer the other questions, please!
diculpe por que mi pc no ve el fastboot de mi one zoom?
ilia3367 said:
yes.
What instruction did you use to unlock the bootloader?
What region is your device manufactured for?
Does your PC see your device connected to the fastboot mod?
What does this command give you:
If the device is detected, enter the command:
And copy the result here.
Click to expand...
Click to collapse
I used this youtube video
I dont know where it is manifactured but I live in the netherlands.
I dont get the 3th question
I will do the commands in a couple minutes
Hey all,
I have the Moto One Zoom running on Android 9.
Also, It's Rooted with Magisk and have Riru EdXposed installed, can I install my OTA updates without bootloop or do I have to Uninstall Magisk, relock bootloader and factory reset/flash stock firmware to get latest OTA updates?
Any feedback is appreciated.
Thanks