Hey there!
after an unsuccessful try to unlock my bootloader (11w42) my phone is still working, but radio function is disabled.
I can only enter my PIN number...
Is there any way to get it back working again? I already tried repairing with SUS and flashing the firmware with flashtool, but still there is no service.
Some wrote to get back radio function with msm7227_setool2, but i guess thats only for already unlocked bootloaders, right?
Thank you so much for your help!
i think that is related to the "baseband" check the version of your phone maybe you are using the wrong one
Type this using dial pad *#*#4636#*#* go to phone information and check if ur radio is off....
Sent from my E15i using xda app-developers app
I am running on the 015 baseband. Maybe i should flash the baseband itself again.
Typing in the mentioned Code Resultate in nothing. The field gets cleared After the last *
Ill let you know if i found a solution.
Thanks a Lot btw!
devito666 said:
I am running on the 015 baseband. Maybe i should flash the baseband itself again.
Typing in the mentioned Code Resultate in nothing. The field gets cleared After the last *
Ill let you know if i found a solution.
Thanks a Lot btw!
Click to expand...
Click to collapse
Some said unlocking bootloader may sim lock your phone. I think you need to re-unlock it.
---------- Post added at 09:23 PM ---------- Previous post was at 09:22 PM ----------
by the way, how did you do that? and congrats for you! I'm locked bootloader. It's a great news that you can unlock your bootloader without
hard bricking.
1 more time
flash the stock Firmware download from my signature
flash the kernel with SIM card inside your phone during flashing
Little Zed said:
Some said unlocking bootloader may sim lock your phone. I think you need to re-unlock it.
---------- Post added at 09:23 PM ---------- Previous post was at 09:22 PM ----------
by the way, how did you do that? and congrats for you! I'm locked bootloader. It's a great news that you can unlock your bootloader without
hard bricking.
Click to expand...
Click to collapse
As I said: 'unsuccessfull'!
The phone was a gift from one of my friends, he did not read the warnings about the production date but tried unlocking
So now radio is off...
I'll flash 2.1 and baseband later to check if that works
I think it's sim lock but I'm not sure :/ :/
Hi all! Im not a motorola user of any sorts, but a friend of mine, who's not a great english speaker and doesn't have an xda account, bricked, or at least so it seems, his Moto X 2014 (xt1097).
He tells me that Motorola and Google now include a checkbox in the "developer options" which, without being checked, will not allow the user to unlock the bootloader via the almighty fastboot oem unlock command.
That being said, the problem is now pretty clear: he cant access that dev option setting, because of the initial bootloop, thus being stuck with an unlock-able bootloader...
I know that it's a not good practice to go all gung ho flashing roms, without a unlocked bootloader and TWRP installed; at least I wouldn't sleep easy without them.
So... what's next? Is there a RSD method to flash the phone back to complete stock? Is there a way to check that checkbox via ADB? Any input will be much appreciated.
ad astra said:
He tells me that Motorola and Google now include a checkbox in the "developer options" which, without being checked, will not allow the user to unlock the bootloader via the almighty fastboot oem unlock command.
Click to expand...
Click to collapse
This is only true if he upgraded to 5.1, which it sounds like he did.
ad astra said:
That being said, the problem is now pretty clear: he cant access that dev option setting, because of the initial bootloop, thus being stuck with an unlock-able bootloader.
Click to expand...
Click to collapse
First what did he do to get into the bootloop? Was he part of the 5.1 soak test and then he tried to flash back to 5.0 to take the OTA?
He needs to try to get into bootloader mode. When the screen powers on, he needs to press and hold the power button until the screen turns off. Then immediately press and hold the vol down button, then after 2 seconds or so, w/o releasing the volume down, press and hold the power button. Keep pressing both power and vol down and hold them for about 4 seconds then release them both. That should get him into bootloader mode.
ad astra said:
I know that it's a not good practice to go all gung ho flashing roms, without a unlocked bootloader and TWRP installed; at least I wouldn't sleep easy without them.
Click to expand...
Click to collapse
You in fact cannot flash a ROM with a locked bootloader.
ad astra said:
So... what's next? Is there a RSD method to flash the phone back to complete stock? Is there a way to check that checkbox via ADB? Any input will be much appreciated.
Click to expand...
Click to collapse
First, get him into bootloader mode. Then you need to tell us what version of the bootloader is he on? Is it 60.14 or 60.11? And is this the Brazil XT1097?
JulesJam said:
This is only true if he upgraded to 5.1, which it sounds like he did.
Click to expand...
Click to collapse
Yep, that's exactly the case.
JulesJam said:
First what did he do to get into the bootloop? Was he part of the 5.1 soak test and then he tried to flash back to 5.0 to take the OTA?
Click to expand...
Click to collapse
If i'm not mistaken it was the other way around. He tried to update to 5.1 (I believe that the zip was form a different vendor).
JulesJam said:
He needs to try to get into bootloader mode. When the screen powers on, he needs to press and hold the power button until the screen turns off. Then immediately press and hold the vol down button, then after 2 seconds or so, w/o releasing the volume down, press and hold the power button. Keep pressing both power and vol down and hold them for about 4 seconds then release them both. That should get him into bootloader mode.
Click to expand...
Click to collapse
Already tried. The bootloader is locked. Tried to unlock (with fastboot), error appears which points to the checkbox in developer tools not being set to true.
JulesJam said:
You in fact cannot flash a ROM with a locked bootloader.
Click to expand...
Click to collapse
I understand what you mean, I meant that you can flash updates from sdcard with stock recovery.
JulesJam said:
First, get him into bootloader mode. Then you need to tell us what version of the bootloader is he on? Is it 60.14 or 60.11? And is this the Brazil XT1097?
Click to expand...
Click to collapse
Btw, he ended up sending the phone back to his carrier, for RMA, and got a new one. So.. we didn't check that. What's the difference between both? Now he managed to flash (with unlocked bootloader) the 5.1 rom and his bootloader version shows 60.16.
On the other hand, the phone's argentinian made. The flashing process which resulted in brick was as follows: 1) updated the stock 4.x.x movistar argentina rom with a brazilian 4.4.4 rom over stock recovery (he tells me that, as both roms are latinamerican, recovery update of those roms is possible). Then he seems to have updated to 5.1 soak. And then, and I dont reaaaly understand why.... he flashed another 5.1 soak that should have been only used for upgrading directly from 5.0.
The point is, he got locked out of any possible recovery method by being unable to unlock his bootlader (which we could access but was obviously locked for flashing).
Anyway, I think this thread will be of general interest so I'll continue to provide info on the case.
ad astra said:
Already tried. The bootloader is locked. Tried to unlock (with fastboot), error appears which points to the checkbox in developer tools not being set to true.
Click to expand...
Click to collapse
That wasn't the point of getting into bootloader mode. The point was to flash back to stock system. That would stop the bootloop then he could boot into system, go into settings and enable unlocking.
---------- Post added at 12:28 AM ---------- Previous post was at 12:27 AM ----------
ad astra said:
Btw, he ended up sending the phone back to his carrier, for RMA, and got a new one.
Click to expand...
Click to collapse
That is fine if that was an option, but those CLNR devices from the carriers are crap. All he had to do when he was in bootloader mode was flash back to stock.
---------- Post added at 12:29 AM ---------- Previous post was at 12:28 AM ----------
ad astra said:
The point is, he got locked out of any possible recovery method by being unable to unlock his bootlader (which we could access but was obviously locked for flashing).
Click to expand...
Click to collapse
No he did not. If you can get into bootloader mode then you can flash system back to stock, then you can boot and enable the OEM unlocking.
---------- Post added at 12:32 AM ---------- Previous post was at 12:29 AM ----------
ad astra said:
the 5.1 rom and his bootloader version shows 60.16.
Click to expand...
Click to collapse
OK so this is yet another 5.1 bootloader version. The only one I have seen is 60.14.
JulesJam said:
That wasn't the point of getting into bootloader mode. The point was to flash back to stock system. That would stop the bootloop then he could boot into system, go into settings and enable unlocking.
---------- Post added at 12:28 AM ---------- Previous post was at 12:27 AM ----------
That is fine if that was an option, but those CLNR devices from the carriers are crap. All he had to do when he was in bootloader mode was flash back to stock.
---------- Post added at 12:29 AM ---------- Previous post was at 12:28 AM ----------
No he did not. If you can get into bootloader mode then you can flash system back to stock, then you can boot and enable the OEM unlocking.
---------- Post added at 12:32 AM ---------- Previous post was at 12:29 AM ----------
OK so this is yet another 5.1 bootloader version. The only one I have seen is 60.14.
Click to expand...
Click to collapse
But how? His bootloader was locked, and we even tried to use recovery to flash back a stock image which returned an error. We tried this using adb sideload and it didn't work. We even edited the .xml file and tried the nokia flashing tool, which also resulted in a failed attempt.
Maybe im missing something... but I only know of 3 methods of flashing via bootloader:
1) fastboot command.
2) adb sideload.
3) vendor flash tool (like Odin, and nokias RDS or something like that).
ad astra said:
The flashing process which resulted in brick was as follows: 1) updated the stock 4.x.x movistar argentina rom with a brazilian 4.4.4 rom over stock recovery (he tells me that, as both roms are latinamerican, recovery update of those roms is possible). Then he seems to have updated to 5.1 soak. And then, and I dont reaaaly understand why.... he flashed another 5.1 soak that should have been only used for upgrading directly from 5.0. .
Click to expand...
Click to collapse
Thanks, so he tried to take a different model's 5.1 OTA when already on 5.1.
---------- Post added at 12:36 AM ---------- Previous post was at 12:33 AM ----------
ad astra said:
But how?
Click to expand...
Click to collapse
mfastboot flash system system.img
You need the system.img file of course for your model. This is why I encourage everyone to use Motorola Device Manager to upgrade - it leaves a copy of the image files on your computer.
---------- Post added at 12:37 AM ---------- Previous post was at 12:36 AM ----------
ad astra said:
But how? His bootloader was locked,
Click to expand...
Click to collapse
You don't need an unlocked bootloader to flash a signed image. Unlocking your bootloader is only needed to flash unsigned images and to disable write protection.
---------- Post added at 12:38 AM ---------- Previous post was at 12:37 AM ----------
ad astra said:
we even tried to use recovery to flash back a stock image which returned an error. We tried this using adb sideload and it didn't work.
Click to expand...
Click to collapse
You don't do it through recovery - you do it through bootloader mode.
JulesJam said:
Thanks, so he tried to take a different model's 5.1 OTA when already on 5.1.
---------- Post added at 12:36 AM ---------- Previous post was at 12:33 AM ----------
mfastboot flash system system.img
You need the system.img file of course for your model. This is why I encourage everyone to use Motorola Device Manager to upgrade - it leaves a copy of the image files on your computer.
---------- Post added at 12:37 AM ---------- Previous post was at 12:36 AM ----------
You don't need an unlocked bootloader to flash a signed image. Unlocking your bootloader is only needed to flash unsigned images and to disable write protection.
---------- Post added at 12:38 AM ---------- Previous post was at 12:37 AM ----------
You don't do it through recovery - you do it through bootloader mode.
Click to expand...
Click to collapse
Nice. I was about to test that :/ But i desisted because i thought it was the same as the normal fastboot... Damn, why didn't I try that when I stumbled upon that yesterday......
Thanks for the info! And also thanks for the tip on the motorola deivce manager upgrade thing. The LG suite does the same thing and so I keep my stock image safely stored.
ad astra said:
Maybe im missing something... but I only know of 3 methods of flashing via bootloader:
1) fastboot command.
Click to expand...
Click to collapse
Yes, this works. You don't need an unlocked bootloader to do it, but you do need mfastboot if the image file you have is a single image file. If you have the system already broken down into chunks, you can use regular fastboot.
ad astra said:
3) vendor flash tool (like Odin, and nokias RDS or something like that).
Click to expand...
Click to collapse
The one you want for a Moto X is the Motorola tool - RSDLite. RSDLite has mfastboot as a part of it.
You needed mfastboot to flash a single file system.img. Regular fastboot from the SDK won't work. mfastboot is motorola's version of fastboot.
Regular fastboot can only flash chunks of system. I think they have to be 256MB or less in size.
---------- Post added at 12:44 AM ---------- Previous post was at 12:41 AM ----------
ad astra said:
Nice. I was about to test that :/ But i desisted because i thought it was the same as the normal fastboot... Damn, why didn't I try that when I stumbled upon that yesterday......
Click to expand...
Click to collapse
I was trying to help you, but you didn't post back.
JulesJam said:
I was trying to help you, but you didn't post back.
Click to expand...
Click to collapse
Dont get me wrong. You did help me (thats why i left u a thanks) :good: My friend just went and did his thing on his own. I probably live in a different time zone, and my work doesn't allow me to be online the whole day. It was really late when I posted, I wasn't expecting a reply on the fly so I went to sleep. I continued this thread just because of curiosity.
On a side note, my friend checked his phone and, it seem'd alright, closed box and all. He worked a time at Motorola so he knows what was getting into. It seems the whole mess happened because of a forum post which indicated that he was flashing a soak test rom, when it was actually a final release (or something like that). This last, ended up messing up his system.
The only way to recover the original phone would have been to flash 5.1 or newer firmware to it. Had the bootloader been unlocked he could have just flashed 5.0.x without an issue(skipping motoboot and gpt).
Nobody should ever mess around with soak files unless they have an unlocked bootloader.
Steve-x said:
The only way to recover the original phone would have been to flash 5.1 or newer firmware to it. Had the bootloader been unlocked he could have just flashed 5.0.x without an issue(skipping motoboot and gpt).
Nobody should ever mess around with soak files unless they have an unlocked bootloader.
Click to expand...
Click to collapse
Agreed. Very poor judgement on behalf of my friend. Lesson learnt I guess, now he's bootloader is unlocked and he managed to flash 5.1 as previously intended.
It seems that the guy who posted the soak mistakenly posted the wrong file and caused a lot of problems for a lot of people... but, nevertheless u cant trust everything to go right... so that's my friends own fault for not unlocking, backing up and investigating enough.
i had the same problem.... any solution for bootloop Moto X 2014 whith Locked Bootloader?
Lussardi said:
i had the same problem.... any solution for bootloop Moto X 2014 whith Locked Bootloader?
Click to expand...
Click to collapse
Have you tried erasing cache and data? If that does not work you could flash your stock firmware.
Could you tell us what you did to get into your bootloop. More info helps us know how to fix your problem.
Sent from my XT1095 using Tapatalk
AGISCI said:
Have you tried erasing cache and data? If that does not work you could flash your stock firmware.
Could you tell us what you did to get into your bootloop. More info helps us know how to fix your problem.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I tried all options, fastboot erase userdata, fastboot erase cache, Flash lollipop 5.1 via RSD nothing seems works
Lussardi said:
I tried all options, fastboot erase userdata, fastboot erase cache, Flash lollipop 5.1 via RSD nothing seems works
Click to expand...
Click to collapse
You still have not told us what you did that caused the bootloop.
Sent from my XT1095 using Tapatalk
AGISCI said:
You still have not told us what you did that caused the bootloop.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I do not know ... a customer came in for repair, so do not know the reason why he stayed so.
I've unlocked bootloader & I'm on aex. I had my problem with my mic. I flashed stock rom but it didn't worked. So yeah microphone is dead. I gotta lock my bootloader to claim my warranty back. But I've read errors like signed rom needed status is modified etc. Please help me with Perfect solution. If it works I'll paypal you some bucks thank you!
Check post #22
https://forum.xda-developers.com/mo...elock-bootloader-moto-g5s-plus-t3681390/page3
yograjfire18 said:
Check post #22
https://forum.xda-developers.com/mo...elock-bootloader-moto-g5s-plus-t3681390/page3
Click to expand...
Click to collapse
Yeah by that method your bootloader gets locked, but the device status stays modified l, isn't it? If this is so, i can't claim my warranty back
Sent from my ZUK Z1 using Tapatalk
hey man, read that whole thread. seems like you just gotta keep flashing till it works
someone had success with "fastboot oem lock begin
<flashed firmware>
fastboot oem lock"
---------- Post added at 02:08 PM ---------- Previous post was at 02:05 PM ----------
try flashing stock while unlocked, letting it boot, then reboot to fastboot and edit your flash commands to not erase data or cache
THEN lock
I have rooted my phone with no problem before. I have even installed custom ROMs.
However I have had my phone repaired because of a hardware issue. I did the same steps I did before. Tick the OEM unlock found in the developers options on. And began flashing TWRP again. It gave me an "only official released binaries are allowed to be flashed" error when I was on download mode and ODIN said it had failed. This was weird for me because I had OEM unlock switched on. I then read about the RMM.
That's when I found it and the KG state was PRENORMAL. I had followed other posts regarding how to fix this like turning back the date etc. But I could only get the OEM unlock part to work and still get PRENORMAL. HELP PLS! I am on March OneUI build
AlfaM03 said:
I have rooted my phone with no problem before. I have even installed custom ROMs.
However I have had my phone repaired because of a hardware issue. I did the same steps I did before. Tick the OEM unlock found in the developers options on. And began flashing TWRP again. It gave me an "only official released binaries are allowed to be flashed" error when I was on download mode and ODIN said it had failed. This was weird for me because I had OEM unlock switched on. I then read about the RMM.
That's when I found it and the KG state was PRENORMAL. I had followed other posts regarding how to fix this like turning back the date etc. But I could only get the OEM unlock part to work and still get PRENORMAL. HELP PLS! I am on March OneUI build
Click to expand...
Click to collapse
Dr Ketons tutorial under his ROM page on this forum is the most informative. I used it for my phone.
---------- Post added at 06:09 AM ---------- Previous post was at 06:07 AM ----------
GeeAyeZee said:
Dr Ketons tutorial under his ROM page on this forum is the most informative. I used it for my phone.
Click to expand...
Click to collapse
https://forum.xda-developers.com/ga...26-08-18-n960-dr-ketan-rom-jio-volte-t3834184
can you flash custom ROM on galaxy s9 Canadian variant?
Model: SM-G960W.
I don't have OEM unlocking option in my developer settings but when I connect my phone to ODIN it detects it and says added.
Boot into odin and look for "Activation Lock OFF" if it says that, you probably can
Alyee said:
can you flash custom ROM on galaxy s9 Canadian variant?
Model: SM-G960W.
I don't have OEM unlocking option in my developer settings but when I connect my phone to ODIN it detects it and says added.
Click to expand...
Click to collapse
Did you ever find out if you were able to flash a custom rom to it?
Anduril97 said:
Did you ever find out if you were able to flash a custom rom to it?
Click to expand...
Click to collapse
You can't the bootloader is locked and not unlockable
---------- Post added at 07:42 PM ---------- Previous post was at 07:41 PM ----------
AudioMiner said:
Boot into odin and look for "Activation Lock OFF" if it says that, you probably can
Click to expand...
Click to collapse
Please don't answer a post if you don't know the correct information. These devices have permanently locked bootloader and cannot be flashed. All you did is cause confusion
2 years late but it sucks than I can't modify this phone due to bootloader locked