no simcard dected - LG Optimus 4X HD

Hi All,
i've got a weird problem, first of all i got root acces and unlocked bootloader.
after that i installed cwm. 6.0.3.1 as recovery.
i made a nandroid backup of my standard LG rom and tried a lot of different roms (carbon, CM10.1.2 stable, CM10.1.2 nigtly)
but every time i get the same error,
no simcard dected please turn of the telephone place simcard and reboot.
but my simcard is in place when i put back my nandroid backup everything is fine.
but i'm still on the standard LG rom.
first i thought maby my bootloader wasn't unlocked propperly but i can flash kernels and i have cwm running.
please help me out i really would like to use the great roms for the dev. here.
Greetings
Wim

Ok a little update.
i got something weird. i got cwm running
i thought i had my booloader unlocked propperly but...
if i do first
adb reboot-bootloader
than
fastboot oem unlock
i unlock the bootloader and take out battery put it back in reboot in recovery flash everything i want start up.
and it works. no errors at all.
but.... when i reboot my phone it looks like the bootloader get locked again because after reboot the error gets back again no simcard dected.
maby anybody could help me out with finding out how to fully unlock my bootloader?
i really think its a bootloader error.
C:\adb>fastboot getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: 015d2578a9040009
(bootloader) mid: 001
(bootloader) product: X3
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) partition-size:bootloader:
(bootloader) partition-type:bootloader:
(bootloader) partition-size:recovery: 0x0000000000a00000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000a00000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system:
(bootloader) partition-type:system:
(bootloader) partition-size:cache:
(bootloader) partition-type:cache:
(bootloader) partition-size:userdata:
(bootloader) partition-type:userdata:
all:
finished. total time: 0.329s
C:\adb>
but in hidden menu its says unlocked

Read this and the posts above it.
Sent from my LG-P880

Thank you for your reply
the weird thing is when i look in the hidden menu it says unlocked.
all the comments is see there is people not getting the unlocked sign in the hidden menu
Iam able to flash a custom rom bu after a reboot i think the bootloader is locked again even it says in hidden menu unlocked
Sent from my LG-P880 using xda app-developers app

Ok guy's maby you got tiered of my messages but i hope someone is willing to think together with me.
like i mentiond in my post above a got a simcard error when installing any custom rom.
i tried these things.
first complete factory reset in hidden menu and lg-update tool (after installing with LG tool all my apps where still there?)
check if my bootloader is unlocked in hidden menu and it's unlocked
reroot my device
install cwm
install custom rom ----> no simcard dected.
i'm still thinking it's something with my bootloader so.
what i did install custom rom.
adb reboot bootloader
fastboot oem unlock
reboot ---> simcard dected and i got connection.
but after a reboot i got no simcard dected again.
when i do
adb reboot bootloader
fastboot oem unlock
reboot
again the simcard is dected.....
so as long is i don't reboot my device it's possible to run a custom rom but if i reboot accedently i've got no simcard acces..
maby i try this? to fully clean install
http://forum.xda-developers.com/showthread.php?t=2069723
i'm getting desperate.....

For whatever reason it seems like your phone isn't actually unlocked. I'd roll back to official JB, root and do the whole unlock procedure from scratch to make sure it is done correctly.

Was your phone SIM unlocked by default or was it on some providers network? Had faced similar issue when I routed my Desire HD which was on AT&T network. Had to patch it with superCID and all started to work fine. Try looking into SuperCID for your set . I hope this helps.
Also see if it works well if original ROM is installed again.
Sent from my HTC Explorer using xda premium

sam214 said:
Was your phone SIM unlocked by default or was it on some providers network? Had faced similar issue when I routed my Desire HD which was on AT&T network. Had to patch it with superCID and all started to work fine. Try looking into SuperCID for your set . I hope this helps.
Also see if it works well if original ROM is installed again.
Click to expand...
Click to collapse
We don't use SuperCID on this device (I'm used to that from my old Desire S). The 'official' JB with bootloader unlock route is reported to have provided SIM unlock as well, but I can't verify as my device was unlocked when I got it - I never buy network locked devices.

Thanks for the reply's
as far as i know i've bought a unlocked phone non branded (on stock rom it accepts all different simcards).
i did a new rom install with the LG-software and i did re-root my device and i installed cwm agian. but.... all my apps were still there, so i'm unsure if it was a real fresh install.
http://forum.xda-developers.com/showthread.php?t=2069723 maby i have to try this....
if i use the offical command to unlock my device it say's welcome to fastboot.....
when i use the unoffical way it keeps saying your device is allready unlocked....
but as mentiond in fastboot commands
(bootloader) secure: yes
(bootloader) unlocked: no
what does that bootloader secure mean? when i look in the thread http://forum.xda-developers.com/showthread.php?t=2069723 it says's off...
thinking and trying really hard.
:silly:

Official bootloader unlock procedure from LG AND the one that works for everyone
Some people still think that
adb reboot bootloader
fastboot oem unlock
is the right command, but guess what: it isn't so please don't use it
Please follow below directions to unlock bootloader.
1. Turn on the phone with SIM card, and wait for connection to the real network.
2. Wait for couple of hours.
3. Connect your handset to local PC with USB cable.
4. Enter "adb reboot oem-unlock" in DOS command window.
5. Reboot handset and you can see the bootloader unlock guide on your phone.
6-1. If you press volume up key, handset is bootloader unlock status.
You can download custom image using fastboot command.
6-2 If you press power on key, user doesnot accept unlock bootlaoder and handset normally power on.
Click to expand...
Click to collapse
I couldn't get this method to work, so ended up using the 'alternate' method (the one you have been trying), but this should be the way to do it.

thank you tomorrow i'll try to get a complete clean install of my JB by flashing it manaly with .kdz files.
when i do this right now
adb reboot oem-unlock i get in the welcome screen of fastboot and no unlock option.
(i think it's because it should be unlocked?)
but first of all tommorow try to get a complete fresh JB, maby first rollback to ics?? and than flash again JB?
will try a bit tommorow.
if somebody else got some great idea's please shoot them here i'm willing to try almost everything.:silly:

From the security and unlock status, it seems obvious that the phone is still locked... Don't know how it is allowing custom ROMs...
Sent from my HTC Explorer using xda premium

nope i don't understand it eighter, but i can't get in the unlock mode again....
so maby first revert back to ICS? flash JB again. and try again.
the weird thing is the rom accepts custom kernels....i've tried to flash werewolfjb kernel and iodak and it doesn't give any error as long as i'm in the stock rom...
greetins wim

That seems like a good idea... If you have original ROM backup, restore it and start from scratch...maybe things get a bit clear then..
Sent from my HTC Explorer using xda premium

ok did a rollback to ICS but forgot to put back the simcard and when i did i did it the worng way big big dummy mistake.
tomorrow new try and after i installed a fresh JB ill install a fresh CM10.1.2 fingers crossed

ok small update,
i've tried to install some custom roms after i did the whole flashing and rollback to stock.
i got EternityProject's CyanogenMod 10.1 for LG Optimus 4X HD running with data connection BUT... at the first start up it showed again no simcard dected. after playing a bit i saw there was an connection and i were able to surf on the internet on my mobile data.
i did a reboot and i saw again no data connection but after like 15 secconds there was it again.
so it looks like it's worken with some little hiks but it works
maby it needed the complete fresh install.
i'll wait until kholk finishes his android 4.3 project so i'll give that a try untill than i'm on stock rom with Optimus Prime 2.53 and i love it i got 2.5 hours screen on time.
Greetings
Wim

Related

Moto X won't update to KitKat

I purchased a Moto X today. It is currently on 4.2.2. Whenever I update it, it says that device is fully updated. I tried searching on Xda but couldn't find a relevant thread. I don't want to root it or flash a Rom, I want to avoid all that. Also I am new to Xda, if this is not the right place to post this then please let me know.
Best way would be to go to the return to stock thread and flash your carriers sbf for 4.4.4
You can flash it via mfastboot or with rsd. There is also a toolkit in the development section. Good luck and ask if you have questions.
There is no way of updating through OTA?
Being on 4.2.2, invest in Sunshine to unlock the bootloader. Why worry about OTAs when you have the option to update manually?
nhizzat said:
Being on 4.2.2, invest in Sunshine to unlock the bootloader. Why worry about OTAs when you have the option to update manually?
Click to expand...
Click to collapse
Why do I need to unlock the bootloader? I am new to this so sorry for the noob questions
mateen1994 said:
Why do I need to unlock the bootloader? I am new to this so sorry for the noob questions
Click to expand...
Click to collapse
Once you update to 4.4.4, you will not be able to unlock your bootloader, or root. If that doesn't matter to you, then no worries.
But if you ever want to Root, unlocking your bootloader now is the best option. With Sunshine, for $25.
Sunshine won't work on 4.4.4, and you'll be stuck, with no chance to Root as of now. ?
mateen1994 said:
I purchased a Moto X today. It is currently on 4.2.2. Whenever I update it, it says that device is fully updated. I tried searching on Xda but couldn't find a relevant thread. I don't want to root it or flash a Rom, I want to avoid all that. Also I am new to Xda, if this is not the right place to post this then please let me know.
Click to expand...
Click to collapse
A few questions...
Did you buy it new or used?
Can you boot into Fastboot/Bootloader mode what is listed on the 2nd line of the phone's screen?
Your screen shots indicate this is an ATT Branded XT1058. Is that correct? do you have the ATT logo on its back? do you see XT1058 in the very small fine print on the back of the phone?
That being said, IF you ever want to root, and your phone is fully on the 4.2.2 rom (including the correct bootloader version), then you will want to use Sunshine to unlock the bootloader NOW before you worry about updates. Once your phone has been updated to 4.4.4 you wont be able to bootloader unlock it.
Once you are ready to upgrade, the best option is to figure out what Android version you want, grab the correct SBF for your carrier/model/android version, and flash it. Taking OTA's are incremental. You need to install one after the other to get to the version you want to be on. SBF files are FULL/All-Inclusive roms, so you just flash the latest you want to be on, so its quicker and Easier.
One final thing.. since I've seen something like this before... IF you have the latest android sdk/platform tools installed on your PC, and USB Debugging turned on (on your phone), then while still in Fastboot/Bootloader mode, connect the phone to your PC, and do a fastboot getvar all what does your phone say for the following...
(bootloader) unlocked:
(bootloader) iswarrantyvoid:
(bootloader) cid:
and does it show the proper IMEI?
KidJoe said:
A few questions...
Did you buy it new or used?
Can you boot into Fastboot/Bootloader mode what is listed on the 2nd line of the phone's screen?
Your screen shots indicate this is an ATT Branded XT1058. Is that correct? do you have the ATT logo on its back? do you see XT1058 in the very small fine print on the back of the phone?
Click to expand...
Click to collapse
1- Used. Also, don't know if it's important to mention or not, I live in Pakistan.
2- I just copy pasted the whole thing for you
AP Fastboot Flash Mode (NS)
30.70 (sha-88483d6, 2013-07-02 15:32:03)
eMMC: 16GB Toshiba RV=06 PV=00 TY=17
DRAM: 2048MB Elpida S4 SDRAM DIE=4Gb
Up Time: 5 minutes
Device is UNLOCKED. Status Code: 1
Battery OK
Connect USB Data Cable
Boot Mode Selection Menu
Vol Up Selects, Vol Down Scrolls
Normal Powerup
Recovery
Factory
Switch console (NULL: null)
Barcodes
BP Tools
Fastboot Reason: Key pressed.
3- Yes it is an AT&T branded XT1058. It doesnt have a logo on its back but when I plug in the phone it says XT1058.
Device is UNLOCKED. Status Code: 1 <--- Does this mean my bootloader is unlocked?
KidJoe said:
(bootloader) unlocked:
(bootloader) iswarrantyvoid:
(bootloader) cid:
and does it show the proper IMEI?
Click to expand...
Click to collapse
(bootloader) unlocked: Not Supported
(bootloader) iswarrantyvoid: Not Supported
(bootloader) cid: 0xdead
And no it doesnt, showing a bunch of zeroes
mateen1994 said:
(bootloader) unlocked: Not Supported
(bootloader) iswarrantyvoid: Not Supported
(bootloader) cid: 0xdead
And no it doesn't, showing a bunch of zeroes
Click to expand...
Click to collapse
UGH... Not another one!!
see -> http://forum.xda-developers.com/moto-x/moto-x-qa/otas-att-xt1058-t2963150 and the tale end of... http://forum.xda-developers.com/moto-x/moto-x-qa/xt1058-sim-lock-mystery-t2755476/page3
I don't know where these devices are coming from, or what is being done to them... but.. yikes..
Where did you buy yours??
My suggestion... if you are SURE its an ATT XT1058, use mfastbooot to flash the 4.4.2 ATT SBF, make sure the phone works, if it does, try sunshine to get the Unlocked status to 3. Then you can try flashing 4.4.4 SBF
*IF* that works, without bricking, count your self lucky.
KidJoe said:
Where did you buy yours??
My suggestion... if you are SURE its an ATT XT1058, use mfastbooot to flash the 4.4.2 ATT SBF, make sure the phone works, if it does, try sunshine to get the Unlocked status to 3. Then you can try flashing 4.4.4 SBF
*IF* that works, without bricking, count your self lucky.
Click to expand...
Click to collapse
Bought it from a shop that sells used phones. Asked the guy to give me another piece, he says he will in a couple of days when the phone is in stock again.
It is printed on the bottom backside of the phone XT1058 Designed and Assembled in the USA. So it is probably a case of improper flashing.
Also, what is SBF? And after unlocking the bootloader, do I need to root the phone to flash the 4.4.4 SBF?
mateen1994 said:
Bought it from a shop that sells used phones. Asked the guy to give me another piece, he says he will in a couple of days when the phone is in stock again.
Click to expand...
Click to collapse
That is the best thing to do. Get a replacement.
mateen1994 said:
It is printed on the bottom backside of the phone XT1058 Designed and Assembled in the USA. So it is probably a case of improper flashing.
Also, what is SBF? And after unlocking the bootloader, do I need to root the phone to flash the 4.4.4 SBF?
Click to expand...
Click to collapse
SBF = full Stock Motorola signed rom.
Root isn't needed to flash a ROM.
You don't NEED to unlock the bootloader, unless you feel you want to root at some point. Because you are on XDA, its usually expected you are looking to hack and customize your phone. Most of that needs rooting. The best way to root, and ensure you can root later, is unlock the bootloader. Hence the mention of it.
If you are going to get a replacement, I wouldn't mess with this phone. I wouldn't try sunshine (as its tied to the phone, so replace your phone and you'd have to pay for sunshine again). If you try and reflash it, you could screw it up, then the seller might not take it back.
"improper flashing" has been the cause of many bricks, either immediately or down the road. So if that is truly the case (that improper flashing is the cause, or even suspected cause), I would advise you to not mess with it if you are able to return/exchange it.
mateen1994 said:
1- Used. Also, don't know if it's important to mention or not, I live in Pakistan.
2- I just copy pasted the whole thing for you
AP Fastboot Flash Mode (NS)
30.70 (sha-88483d6, 2013-07-02 15:32:03)
eMMC: 16GB Toshiba RV=06 PV=00 TY=17
DRAM: 2048MB Elpida S4 SDRAM DIE=4Gb
Up Time: 5 minutes
Device is UNLOCKED. Status Code: 1
Battery OK
Connect USB Data Cable
Boot Mode Selection Menu
Vol Up Selects, Vol Down Scrolls
Normal Powerup
Recovery
Factory
Switch console (NULL: null)
Barcodes
BP Tools
Fastboot Reason: Key pressed.
3- Yes it is an AT&T branded XT1058. It doesnt have a logo on its back but when I plug in the phone it says XT1058.
Device is UNLOCKED. Status Code: 1 <--- Does this mean my bootloader is unlocked?
Click to expand...
Click to collapse
Yes , your device bootloader has been unlocked.
Whats interesting is that both @RafaySid and @mateen1994 bought the phones from the same country; probably even from the same seller.
I guess the seller bought used ATT phones from USA and tried to unlock them via flashing some different custom ROM and ended up messing it up.
I've found quite a few devices in the market with this problem.
usmanshahid said:
Whats interesting is that both @RafaySid and @mateen1994 bought the phones from the same country; probably even from the same seller.
I guess the seller bought used ATT phones from USA and tried to unlock them via flashing some different custom ROM and ended up messing it up.
I've found quite a few devices in the market with this problem.
Click to expand...
Click to collapse
I bought mine from a guy in Karachi
No, not from the same seller I'm pretty sure. I guess these phones are imported from abroad which have been improperly flashed or something. I sorted out my problem though.

S-ON with no system on! how to get out?!

Hello.. how are ya devs
I've asked this last night numerously and ended up with headaches.. yes.
I accidentally wiped EVERYTHING from my htc one and I have S-ON so I basically can't flash a firmware.. So I spent the last night looking at my beautiful blank white screen.. How do I fix it please? I'd appreciate a help..
Quick Help (might work 4 you)
Hey buddy,
I got myself a M7 working again by letting it get set back to stock from a RUU.exe which fit to my phone.
It was S-On and with an UNlocked bootloader.
At first is to say that I cant provide any guarantee for the workability of my solution, neither will I take any responsibiliry in case you mess your mess up even more
But here is how I went on the case:
I just got myself this quick installer here to set up my PC for adb and fastboot commands!
Second you will need the HTC Drivers ("Solo Driver Installer) and a working USB Cable of course
After connecting Phone I started my Phone into bootloader and swiched to the "fastboot" mode! I used the Windows "CMD" command tool to find out which Baseband version i need, by typing fastboot devices and fastboot getvar all. The second command gives you the needed infomation about your Baseband!
After finding out, find your fitting RUU.exe right here and load that 1,6 GB file
At last all you need is to make sure that your bootloader is (RE-)LOCKED, because else the RUU.exe wont work!
A simple fastboot lock oem will do the thing! Afterwards your Phone should be able to get reflashed with the Stock ROM and stuff that comes by the RUU! NOTE: Unlocking your Bootloader requires a working OS as far as i know, and cant be done by another "Fastboot oem UNlock" command
This link is describing the same procedure in case you're unsure..
Greetings, a happy owner of a working HTC M7

Help - OTA Update gave me a brick

Hey XDA,
I was rooted, unlocked and TWRP'd on I think 6.4? I realized I wanted to go back to locked and stock after seeing some of the security stuff come out. I used SPFT to flash the 6.1 Prime Rom, and everything was working great. Phone booted no problem, and seemed to work fine. I then tried to use the Wireless Update to update the phone. It looked liked it downloaded fine, but now I'm in a reboot loop, and recovery does absolutely nothing but reboot loop as well. I CAN get the phone into Fastboot mode, but fastboot flash recovery gives me a "failed to get permission" error.
I ran a getvar all, and here is what I have:
unlocked: yes
secure: yes
kernel 1k
bootloader: version-preloader 0.0.00
Version: 0.5
I've tried the SPFT tools again, but it gives me ERROR: S_BROM_DOWNLOAD_DA_FAIL.
ANY clue what I can try next to just get the dang thing to be bootable? I don't care root or recovery or what, I just want a working phone, and I'm running out of ideas.
Thanks!
brockwitting said:
Hey XDA,
I was rooted, unlocked and TWRP'd on I think 6.4? I realized I wanted to go back to locked and stock after seeing some of the security stuff come out. I used SPFT to flash the 6.1 Prime Rom, and everything was working great. Phone booted no problem, and seemed to work fine. I then tried to use the Wireless Update to update the phone. It looked liked it downloaded fine, but now I'm in a reboot loop, and recovery does absolutely nothing but reboot loop as well. I CAN get the phone into Fastboot mode, but fastboot flash recovery gives me a "failed to get permission" error.
I ran a getvar all, and here is what I have:
unlocked: yes
secure: yes
kernel 1k
bootloader: version-preloader 0.0.00
Version: 0.5
I've tried the SPFT tools again, but it gives me ERROR: S_BROM_DOWNLOAD_DA_FAIL.
ANY clue what I can try next to just get the dang thing to be bootable? I don't care root or recovery or what, I just want a working phone, and I'm running out of ideas.
Thanks!
Click to expand...
Click to collapse
don't panic. everything is as is should be in your situation.
you see when you did getvar all , it said
secure: yes.
that means it only wants to boot signed and secured partitions. Just get into fastboot and do "oem unlock".
you really cant (safely) relock the bootloader. If your boot loader was relock now, you wold be in a perminent boot loop condition not able to recover.
But you can save it with "oem unlock" from where you at now.
You rock. I thought since it said unlocked I didn't need to do it again, but that did the trick. Now I just need to figure out what to do with the phone. I wouldn't mind keeping root, but I want the B12 update.
brockwitting said:
You rock. I thought since it said unlocked I didn't need to do it again, but that did the trick. Now I just need to figure out what to do with the phone. I wouldn't mind keeping root, but I want the B12 update.
Click to expand...
Click to collapse
Here...
http://forum.xda-developers.com/r1-...om-6-5-flashed-via-twrp-t3455532/post68543624
Though if you have already updated, you're probably stuck, unless the dirtycow hack still works with newest OTA....
http://forum.xda-developers.com/r1-...irtycowed-f-amazon-root-t3490882/post69387241
kal250 said:
Here...
http://forum.xda-developers.com/r1-...om-6-5-flashed-via-twrp-t3455532/post68543624
Though if you have already updated, you're probably stuck, unless the dirtycow hack still works with newest OTA....
http://forum.xda-developers.com/r1-...irtycowed-f-amazon-root-t3490882/post69387241
Click to expand...
Click to collapse
The dirtycow thing was only needed to get to the unlocked point. He is already there, so his only issue should be the lack of sp flash tool. Until/ if he does the bootloader rollback.
Shouldn't be problem with the modded v7 to roll back either.
Because in order to install the modded version , you need to be unlocked and twrp anyway, right.?
mrmazak said:
The dirtycow thing was only needed to get to the unlocked point. He is already there, so his only issue should be the lack of sp flash tool. Until/ if he does the bootloader rollback.
Shouldn't be problem with the modded v7 to roll back either.
Because in order to install the modded version , you need to be unlocked and twrp anyway, right.?
Click to expand...
Click to collapse
Yes.... See what happens when you loose your R1, I'm out of touch lol.... I do miss the phone.....
mrmazak said:
don't panic. everything is as is should be in your situation.
you see when you did getvar all , it said
secure: yes.
that means it only wants to boot signed and secured partitions. Just get into fastboot and do "oem unlock".
you really cant (safely) relock the bootloader. If your boot loader was relock now, you wold be in a perminent boot loop condition not able to recover.
But you can save it with "oem unlock" from where you at now.
Click to expand...
Click to collapse
I presume he flashed factory original 6.1 from Colton's site.
I thought flashing original rom with SPFT should result in safely relocked bootloader, why not?
What if he relocked bootloader with 'fastboot oem relock' command after flashing 6.1 but before taking 7.4.2 OTA update? This would also leave him with:
unlocked: yes
secure: yes?
There must be some way to bring phone to original factory state with bootloader locked (meaning unlocked: no secure: yes).
BLU support also cannot do this?
kfn said:
I presume he flashed factory original 6.1 from Colton's site.
I thought flashing original rom with SPFT should result in safely relocked bootloader, why not?
What if he relocked bootloader with 'fastboot oem relock' command after flashing 6.1 but before taking 7.4.2 OTA update? This would also leave him with:
unlocked: yes
secure: yes?
There must be some way to bring phone to original factory state with bootloader locked (meaning unlocked: no secure: yes).
BLU support also cannot do this?
Click to expand...
Click to collapse
There is and I did it few times while testing my unlock script. Bit the chances of making a brick were so very high I cannot recommend doing it.
There are two other partitions that store the unlock state and they need to restored to really relock bootloader.
OEM relock does not work properly
mrmazak said:
There is and I did it few times while testing my unlock script. Bit the chances of making a brick were so very high I cannot recommend doing it.
There are two other partitions that store the unlock state and they need to restored to really relock bootloader.
OEM relock does not work properly
Click to expand...
Click to collapse
Can you tell what steps you did to relock?
I really want to bring device to original factory state because encryption does not work when bootloader is unlocked. I did first dirty cow method on original 6.6 ROM (one with newer preloader), then rolled back booloader, installed 6.1 from ColtonDRG site with SPFT and finally installed vampireinfo's 7.4.2 thru TWRP.
However when I encrypted phone, in settings it says encrypted but I can browse device on PC without entering PIN.
On factory state encrypted device (with locked bootloader) I was not able to this
kfn said:
Can you tell what steps you did to relock?
I really want to bring device to original factory state because encryption does not work when bootloader is unlocked. I did first dirty cow method on original 6.6 ROM (one with newer preloader), then rolled booloader, installed 6.1 from Coltron site with SPFT and finally installed vampireinfo's 7.4.2 thru TWRP.
However when I encrypted phone, in settings it says encrypted but I can browse device on PC without entering PIN.
On factory state encrypted device (with locked bootloader) I was not able to this
Click to expand...
Click to collapse
This will brick your phone, if you are not careful, and also if you are carefull. You can browse for help in encryption with unlocked bootloader before doing this, I'm sure there is a solution.
If you replace Seccfg.bin and Secro.bin from a backup from before unlocking bootloader you should be set to locked but I do not know of your phone will boot. You will be doing g that at your own risk.
But if you download the repair solution under the hidden tag(click to show content) in the roll back thread.
In that file it will restore you to 6.1 and it will be locked bootloader. I do not know about keeping v7 and relocked

Cannot Unlock Bootloader: Unlock Data unavailable

Well, I have been trying very hard to unlock my bootloader on device MotoG5s plus and had no luck.
Everytime I use command : fastboot oem get_unlock_data, I get error message Unlock Data Unavailable.
I have checked OEM unlocking and USB Debugging but problem still persists.
Also, I have been gone through Motorola forms and google but got no solution.
When I use fastboot getvar all I get, (bootloader) cid: 0x0000
Please Help:crying:
Same issue
Have you found any solution ?
Same issue comes in my device..... :crying:
I got same problem my Moto xt1804 stuck on dummy bootloader and I can't flash stock rom..
I think this error can fixed by blank flash.zip..
Sorry for my bad english
SuperSaket said:
Well, I have been trying very hard to unlock my bootloader on device MotoG5s plus and had no luck.
Everytime I use command : fastboot oem get_unlock_data, I get error message Unlock Data Unavailable.
I have checked OEM unlocking and USB Debugging but problem still persists.
Also, I have been gone through Motorola forms and google but got no solution.
When I use fastboot getvar all I get, (bootloader) cid: 0x0000
Please Help:crying:
Click to expand...
Click to collapse
Check it device drivers
Well I know it's quite late to reply, but after trying too many times I just wasn't able to unlock bootloader. Moto forums are totally ineffective. I waited for weeks for their answer and when they answer it doesn't help anyway. After a lot of research, one common theme comes out that this problem arises if your phone has been to servicing for any reason. Some one out there was saying that the problem is related to some jTag issue, it can be fixed if you have the hardware setup for jTag. But since I didnt have the h/w setup, so solution is not verified. So if someone is too keen to find the solution, he may look into it or otherwise switch to a new device as it would be easy and less painful.

Downgrade method still works after August patch

hey guys, been a painful 3 days lol( busy looking for a nokia 5 stock rom instead of a nb0 rom lmao!!).
The method works am now on 7. so guys go right ahead and downgrade if you wanna do it.
P.s 1. search for nbo and not stock rom
2. When the setting up comes what you need to do is click setup with no network. this way you will prevent the system from taking you straight to updates!.
Next step root and enjoy?
Please provide the link of nb0 ROM for Nokia 5 ta -1053
its also safe to downgrade Nokia ta-1024 from pie to nougat with nost bootloader will still be unlocker .
jason_l367 said:
its also safe to downgrade Nokia ta-1024 from pie to nougat with nost bootloader will still be unlocker .
Click to expand...
Click to collapse
Greetings;
I've been out from Android Modding and Development for quite some time and I'm a little bit lost at the moment.
Where do you guys find the nb0 files and how do you select them for your devices?
I'm looking for a source for several Nokia devices; but most specific for the TA-1024
Thanks in advance.
Best regards;
rgxHost said:
Greetings;
I've been out from Android Modding and Development for quite some time and I'm a little bit lost at the moment.
Where do you guys find the nb0 files and how do you select them for your devices?
I'm looking for a source for several Nokia devices; but most specific for the TA-1024
Thanks in advance.
Best regards;
Click to expand...
Click to collapse
Here is the nougat nb0 file that I use (with nost). It may fail midway through btw but don't worry if it does it happen to me often, just start again & select the wipe user data option
I m not sure you can downgrade with locked BL but I downgrade from pie with unlock easily
jason_l367 said:
Here is the nougat nb0 file that I use (with nost). It may fail midway through btw but don't worry if it does it happen to me often, just start again & select the wipe user data option
I m not sure you can downgrade with locked BL but I downgrade from pie with unlock easily
Click to expand...
Click to collapse
Greetings;
Thanks for the prompt reply.
Regarding that error, before you flash any room you should always clean Dalvik cache, Cache and Wipe user data. That prevents errors, and duplicate data or applications.
I couldn't find "unlock easy" to see if I can manage do unlock the bootloader. Is this a tool that can be found on the forum?
As far as I know without bootloader unlocked you're not able to flash anything, including recovery.
Fastboot will refuse any flashing options.
rgxHost said:
Greetings;
Thanks for the prompt reply.
Regarding that error, before you flash any room you should always clean Dalvik cache, Cache and Wipe user data. That prevents errors, and duplicate data or applications.
I couldn't find "unlock easy" to see if I can manage do unlock the bootloader. Is this a tool that can be found on the forum?
As far as I know without bootloader unlocked you're not able to flash anything, including recovery.
Fastboot will refuse any flashing options.
Click to expand...
Click to collapse
As far as I know this is the only way to unlock BL on the Nokia 5, if you wanna root on pie. See this thread for all the info you'll need. Good luck!
jason_l367 said:
As far as I know this is the only way to unlock BL on the Nokia 5, if you wanna root on pie. See this thread for all the info you'll need. Good luck!
Click to expand...
Click to collapse
Greetings;
Already tried that.
OEM Unlock option returns 0 (even when enabled and toggled on).
Bootloader Unlock option is not present.
I see that nowadays is quite difficult to get root & unlock the bootloader.
Fastboot OEM Report:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
...
The first thing that occurrs to me is that the phone is carrier locked (even though) I can use any SIM.
rgxHost said:
Greetings;
Already tried that.
OEM Unlock option returns 0 (even when enabled and toggled on).
Bootloader Unlock option is not present.
I see that nowadays is quite difficult to get root & unlock the bootloader.
Fastboot OEM Report:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
...
The first thing that occurrs to me is that the phone is carrier locked (even though) I can use any SIM.
Click to expand...
Click to collapse
That's wierd. My 1024 was piece of cake to root. I think you right that the carrier modél is a lot different to unlocked variant

Categories

Resources