Hello everybody!
Last night I say the new SlimRom post and decided to try it, I have to say that I didn't know if my bootloader was unlocked or locked, so I tried to install Phils Touch Recovery that was suggested. It didn't work, after that tried the CMW for locked bootloaders, it didn't work either. Just got the "security error" message when trying to enter recovery mode. After that I say the Unlocked Bootloader post and decided to give it a try, everything was fine until the phone restarted, after that it didn't boot, it would stay with a black screen vibrating. I decided to use the LG flash tool 2014 that a user named yunior suggested to use (saw this at the Unlocked Bootloader post) and it runned fined, but after that, the phone wont even vibrate neither get the black screen. When I read phone information from LG FT2014 I get this
IMEI Empty.
IMEI Auth fail....Please check IMEI value
Phone Mode :Normal
Phone Model :
Server Model :
Buyer :
Phone Version :
Server version :
**Phone sub version lenght is more than 2 digit
**Server version is empty
please check IMEI or S/W file status in CSMG
I would really appreciate your help! Really need my phone back:fingers-crossed:
Thank you!
Hi guys, so I seem to have scewed up my phone quite badly. I tried to deodex running the new nougat firmware (with drm-fix and ric-off) by flashing a zip in the nougat firmware thread. Somehow I ended up with not being able to fastboot anymore.
I found out that my bootloader seems to be locked again. Thus I am not able to approach the fastboot mode, but failed to do any flash, as it says [FAILED (remote: not allowed)].
I checked the service menu and found the [Bootloader unlock allowed:no] and [Remote Lock State: Locked] after reflashing the nougat firmware.
So I wanted to unlock the device, how ever I ended up with flashing back to Lollipop and the device boots and then power off after a few seconds of use.
Could this due to "remote lock state: not allowed"?
Try relocking via flashtool?
So. Tried to lock and relock via flashtool. Checked drivers which are working fine.
I was trying to relock and then unlock again using flashtool after updating to .305 Marshmallow firmware . However this does nothing to the bootloader states. The weird thing is that there are no errors showing up in flashtool when unlocking/relocking. I can't even unlock via OEM because when I tick OEM unlock in the developer options this doesn't do any change (Rooting status: Bootloader unlock allowed : No, Remote Lock State: Locked). My DRM keys are gone as well. However I do have a TA Backup but can't restore because after downgrading to lollipop the device shuts down after 30 seconds.
I'm really annoyed because I bought the device with an locked bootloader (without carrier costumizations) and unlocked it via OEM unlock then updated to . Is there any chance to unlock the device again? Restore TA? Any recommendations what I could have done wrong would be helpful.
iArvee said:
Try relocking via flashtool?
Click to expand...
Click to collapse
[solved ] Bootloader is now sucessfully relocked andBootloader states are back to [Bootloader unlock allowed: Yes] and [Remote Lock State: UnLocked].
I need to mention that I bought a phone without carrier lock with [Bootloader unlock allowed: Yes].
So, for anyone who is interested or might face the issue in the future, here's what I did.
You will need your backed up TA-Partition-Image to restore via iovyroot:
1. Downgrade to Lollipop (32.0.A.6.200 / R2B (STOREFRONT GENERIC)) using Flashtool .
->Therfore select/tick everything in the wipe section when selecting the Lollipop-tft
2. Unmount your SIM, reboot the device
3. Skip everything on the welcome/configuration screen as fast as you can to get beyond the Android configuration screen
(skip wif config, Google-Account setup, untick myXperia services! etc.)
The phone might power off only after a few seconds because of the downgrade. So be fast!!!
4. Once you end up on the home screen, unlock developer options, and activate ADB debugging, grant ADB access (check via cmd: fastboot devices)
again: be fast! --> Don't worry if the phone shuts down again. Just reboot if you were not fast enough.
5. Download iovy.root ( iovy.root. Place TA-backup.img in the iovyroot-folder.
Then I modified "tarestore. bat" to save some time regarding the shutdowns. I used notepad++:
...
set response=
set /p response=Type "y" if you want to restore this file:
if "%response%" == "y" (
echo Starting restore
echo.
adb push "root/iovyroot" "/data/local/tmp/iovyroot" > NUL 2> NUL
adb push "root/restore.sh" "/data/local/tmp/restore.sh" > NUL 2> NUL
...
5. Run CMD as admin. CD to Iovyroot folder.
Restore using tarestore.bat (tarestore.bat TA-2016-xxx.img) as soon as your device boots up to home screen and seems to be connected as ADB device.
( I checked this by running the windows device manager simultaniously)
Wait to end the process.
-->When the restore was sucessfull, the device shouldn't shutdown again.
6. Reboot. Your bootloader is now locked again (but able to unlock via OEM unlock). DRM keys/functionality is restored.
I have the same problem (after i had nougat working incl drm fix and root, also the deodex, tried flashing lower ftf files too when i got this problem, noticed the rebooting, which it does not do at 305 kernel or higher..
I would have hope in your solution, if I could find my ta backups (i have from some other phones, this one, may have been on a crashed laptop, already searched through old hdds)
Could this be because of fastboot flash recovery twrp.img (cause that is something i never done before on the z5c.)
If anyone has a solution other than restoring the ta partition, i would like to know. Because i am very uncertain that i can find those files again...
Same case here z5c unlocked since +/- 1 year and I don't have any TAbackup too
I will try to downgrade to .200 But with bootloader unlock allowed : no ... I don't have much hope
edit : no chance, I tried .200 but without tabackup, I can't do nothing
When I faced this problem I noticed it happened because I wiped TA options with Flashtool. Never do that if you don't want to lose TA partition and all other things connected to it. I could fix it only by flashing TA backup even though I hadn't the timing issue zegovernator had for flashing back TA.
I actually wonder why Flashtool allows to wipe these critical partitions/options
ric69 said:
Same case here z5c unlocked since +/- 1 year and I don't have any TAbackup too
I will try to downgrade to .200 But with bootloader unlock allowed : no ... I don't have much hope
edit : no chance, I tried .200 but without tabackup, I can't do nothing
Click to expand...
Click to collapse
I'm sorry for you. I would recommend updating back to MM since LP gives you immediate shut downs when recognising that your TA is lost/wiped. It's sometime a pain in the ass that stuff gets posted before testing. Nonetheless, you could still try to send in your device back to Sony Costumer Service if you are under warranty (after flashing .200, say that it is "broken" and keeps crashing). However, I would not trust on them sending you a new device.
jutphaas said:
I have the same problem (after i had nougat working incl drm fix and root, also the deodex, tried flashing lower ftf files too when i got this problem, noticed the rebooting, which it does not do at 305 kernel or higher..
I would have hope in your solution, if I could find my ta backups (i have from some other phones, this one, may have been on a crashed laptop, already searched through old hdds)
Could this be because of fastboot flash recovery twrp.img (cause that is something i never done before on the z5c.)
If anyone has a solution other than restoring the ta partition, i would like to know. Because i am very uncertain that i can find those files again...
Click to expand...
Click to collapse
I sorry to say that, but if you lost your TA-backup or didn't even back it up before unlocking the bootloader there is no hope at the moment. You simply can't fastboot because of the Remote State: Locked. It keeps you from accessing the bootloader.
I found my iovyroot TA-backup.img file, I did have a .200 storefront ftf and tried it on that one, which was very anoying as it wants to start a demo , i found an other .200 ftf online which I tried, and the iovyroot seems to work, at that time no reboot, in service menu, the drm keys now seem fine there, Bootloader unlock allowed : No, Remote Lock State: unLocked , fastboot boot or oem unlock still seemed not working well i think that is what it said, (flashtool unlock always seems to, i did try) now i flash a new ftf and try my luck there with the unlock status.
flashing ftf 5.11 flashtool says
03/005/2017 05:05:49 - INFO - Loader : S1_Root_f936 - Version : MSM8994_50 / Boot version : S1_Boot_MSM8994_LA1.2_119 / Bootloader status : ROOTED
And now in 5.11 it also says bootloader unlocked : Yes Lost my drm again
So I am back in flashing and rooting (with drmfix etc) Android 7 again Thanks for sharing this solution!!
So you confirm that TA backup is the only solution to solve the "unlock allowed" bad state, don't you?
This is good for other people because when I faced the problem I was really scared to have messed up my phone!!!
i want to confirm the solution here
i had the same problem and the only way back of it was to downgrade to Lollipop and restore the TA-Partition
i dont think there is a solution if you did not backup your TA and have an image of it.
Yes, the TA restore is the only known solution, and I am glad Zegovernator shared his solution here
Hello guys,
I'm not a noob when we speak about flashing ROMs and unlocking bootloaders. I've been doing that for some years. Yesterday I flashed the new stock ROM for LG G4 - v29a, android 7.0. Everything went fine. Later this day, I've seen a post claiming that it was possible to relock your bootloader with this specific ROM using the fastboot oem lock. And it worked indeed. The problem now is that when I turn on the phone the following message shows up on RED: "Your device is corrupt. It cannot be trusted and may not work properly".
So, here's the problem:
1 - Can't access recovery;
2- Can't access download mode;
3 - Can't boot normally;
4 - Can't re-unlock since (i guess) the IMEI is now 0;
5 - Can't flash stock ROM using LGUP;
6- Can't erase any partition via adb since the bootloader is now locked;
So, basically all my ways are locked. Any fix you know and want to share?
hi guys , got big problem .
tried to get a stock phone ... so deactivated oem in settings then locked bootloader , phone started to bootloop. i know that this can happen if your bootloader is unlocked, strange thing is that in fastboot mode it states as phone relock und frp lock .
i tried dc phoenix and here result of checked bootloader : OEM lock state info:
FB LockState: LOCKED
USER LockState: RELOCKED
OEM get bootinfo:
unlocked
Oem shouldn't have been toggled.
Phone state will remain relocked after relocking the bootloader.
Try dload method with stock firmwares and see if it makes a difference. If not, boot to erecovery and download full firmware.
erecovery = getting package info failed
dload = software install failed
Isnt there any Chance repairing it?
shisha106 said:
Isnt there any Chance repairing it?
Click to expand...
Click to collapse
I congratulate, your phone live
Hello guys! I want help about my case.Firstly i unlocked bootloader and installed custom recovery,everything went fine.So i decided to try custom rom.Flashed it via recovery and after it boots i saw that sim card is not working.Checked if there is imei but it wasnt, so i go in engineering mode to add imei in fm receiver,but this tab was grey and i cant enter it. Than i tried via terminal but without success.Also i got wifi and gps problems and decided to flash stock rom,so formated phone via sp flash tool and give it a clean os.Everything was fine till it start booting i saw it was too fast and phone started.There was the same bug i cant enter imei and baseband is unknown .I tried diffrent stock roms but no luck.Everytime after flash it was like nothing happend and booting super fast.BTW i cant lock the bootloader also,it says device unlocked.
flashing with mfastboot worked
here is the link with instructions : https://www.hardreset.info/devices/motorola/motorola-moto-e4-plus/faq/firmware-flash/