Hello...
What I will ask maybe don't have an answer, but... let's go.
Reading about "security error" on LG phones, I noticied it don't have a "one reason" to happens. As far I read, some people get this error when:
Flash CWM;
Uninstall some system apps;
Uninstall Google Play Movies
Uninstall operator's apps;
Uninstall bloatware.
For me, it happens when I remove some bloatware and system apps, and when I integrate updates to ROM using Titanium Backup, too. Root is harmless, as far I know. And the only way to have phone working again is, for now, installing a stock ROM with KDZ Updater or LG Mobile Update Tool (when it detects the phone). Is a boring thing to do every time phone bricked...
Then.. Maybe I'm wrong, but... I think the reason for the error is only one: these LG phones checks for apps and/or settings that are removed when uninstalling something. I think this "check" is inside a script, like init.d or build.prop... But I'm not sure.
The question is: how I can "disable" the security check?
Unlocking bootloader or using a custom ROM (like TEAM)??
unlock
romulocarlos said:
Hello...
What I will ask maybe don't have an answer, but... let's go.
Reading about "security error" on LG phones, I noticied it don't have a "one reason" to happens. As far I read, some people get this error when:
Flash CWM;
Uninstall some system apps;
Uninstall Google Play Movies
Uninstall operator's apps;
Uninstall bloatware.
For me, it happens when I remove some bloatware and system apps, and when I integrate updates to ROM using Titanium Backup, too. Root is harmless, as far I know. And the only way to have phone working again is, for now, installing a stock ROM with KDZ Updater or LG Mobile Update Tool (when it detects the phone). Is a boring thing to do every time phone bricked...
Then.. Maybe I'm wrong, but... I think the reason for the error is only one: these LG phones checks for apps and/or settings that are removed when uninstalling something. I think this "check" is inside a script, like init.d or build.prop... But I'm not sure.
The question is: how I can "disable" the security check?
Unlocking bootloader or using a custom ROM (like TEAM)??
Click to expand...
Click to collapse
what phone is it ?
if its a error during booting up then unlocking bootloader will remove the error
IGGYVIP said:
what phone is it ?
if its a error during booting up then unlocking bootloader will remove the error
Click to expand...
Click to collapse
Is a E455f. L5 II Dual SIM. But, as I sayed, this error is very common. Happens when we play around system apps or operator's bloatware.
Root is harmless (I'm using Klingo), but because this error is almost useless. We can't uninstall bloatware or useless apps, change boot animation, or move apps to system/app, for example. Any change to system partition is a potential risk of "security error".
The error happens always at same time: power on phone, the LG logo appears, and when boot animation must appears, the security error comes up. About 3 seconds after, phone shutdown.
So, why bootloader will remove the "security check"
just does
romulocarlos said:
Is a E455f. L5 II Dual SIM. But, as I sayed, this error is very common. Happens when we play around system apps or operator's bloatware.
Root is harmless (I'm using Klingo), but because this error is almost useless. We can't uninstall bloatware or useless apps, change boot animation, or move apps to system/app, for example. Any change to system partition is a potential risk of "security error".
The error happens always at same time: power on phone, the LG logo appears, and when boot animation must appears, the security error comes up. About 3 seconds after, phone shutdown.
So, why bootloader will remove the "security check"
Click to expand...
Click to collapse
unlocked bootloader contains lines that pass firmware with custom security setting
i'm trying to unlock bootloader from l5 || single sim but no joy for now
because of your filesystem structure and the way of flashing it and part of system that is before recovery there is big chance for brick if file is not right
---------- Post added 17th May 2014 at 12:04 AM ---------- Previous post was 16th May 2014 at 11:59 PM ----------
romulocarlos said:
Is a E455f. L5 II Dual SIM. But, as I sayed, this error is very common. Happens when we play around system apps or operator's bloatware.
Root is harmless (I'm using Klingo), but because this error is almost useless. We can't uninstall bloatware or useless apps, change boot animation, or move apps to system/app, for example. Any change to system partition is a potential risk of "security error".
The error happens always at same time: power on phone, the LG logo appears, and when boot animation must appears, the security error comes up. About 3 seconds after, phone shutdown.
So, why bootloader will remove the "security check"
Click to expand...
Click to collapse
anyway
install cwm from HERE
then install this [L5 II, L3 II] SlimSystem V2.2 (Optima Team)
it works
just avoid SystemUI change as it was made for single sim model
IGGYVIP said:
unlocked bootloader contains lines that pass firmware with custom security setting
i'm trying to unlock bootloader from l5 || single sim but no joy for now
because of your filesystem structure and the way of flashing it and part of system that is before recovery there is big chance for brick if file is not right
---------- Post added 17th May 2014 at 12:04 AM ---------- Previous post was 16th May 2014 at 11:59 PM ----------
anyway
install cwm from HERE
then install this [L5 II, L3 II] SlimSystem V2.2 (Optima Team)
it works
just avoid SystemUI change as it was made for single sim model
Click to expand...
Click to collapse
Tried... But my phone don't detect the SIM with this ROM.
So, I will have to learn to live with all the things I wanna remove until a definitive bootloader unlock comes...
Thanks!
did you skip the systemui ?
romulocarlos said:
Tried... But my phone don't detect the SIM with this ROM.
So, I will have to learn to live with all the things I wanna remove until a definitive bootloader unlock comes...
Thanks!
Click to expand...
Click to collapse
give me a list of things you want to remove from your phone and i will make you a script to remove one by one to remove as much as possible
The problem isn't your ROM. Sorry.
The KDZ Updater changed my phone's IMEI (both of them). I'm trying to restore with MTKDroidTools and engeneer menu, but no success yet.
same trouble here with my e430
romulocarlos said:
The problem isn't your ROM. Sorry.
The KDZ Updater changed my phone's IMEI (both of them). I'm trying to restore with MTKDroidTools and engeneer menu, but no success yet.
Click to expand...
Click to collapse
nv read only ... YUK ...
IGGYVIP said:
nv read only ... YUK ...
Click to expand...
Click to collapse
I don't understand what is it!
Nv is where imei data is
romulocarlos said:
I don't understand what is it!
Click to expand...
Click to collapse
i have same problem on my e430
the part of filesystem that stores imei data is read only and gaining access to it is terrible (Yuk..[not nice] )
i did not manage to write anything to that sector on that phone
IGGYVIP said:
i have same problem on my e430
the part of filesystem that stores imei data is read only and gaining access to it is terrible (Yuk..[not nice] )
i did not manage to write anything to that sector on that phone
Click to expand...
Click to collapse
Well, I restored the IMEIs. Was simple. Worked for me. Maybe work for others!
You will need:
PuTYY: putty.org
LG United Drivers: Download the latest from LG homepage and install it.
The EXACT IMEI numbers from your phone, located at tag under battery space (don't try to 'clone' or use another: don't work and it's illigal).
Rooted phone (not sure about this, mine already rooted)
Preparing the arena. Let's go:
A1. Plug the phone and let windows recognize it.
A2. Make sure two devices are present: 'LGE AndroidNet USB Modem' under "Modems" section, and LGE 'Androidnet USB Serial Port' under "Ports" section.
A3. Unplug
A4. Activate USB Debbugin in Settins
A5. Plug again
A6. PC will recognize another device, make sure: 'AndroidNET Sooner Single ADB Interface' under "ADB Interface"
A7. Unplug
Now, the fun begins: lets write the IMEIs!
B1. Plug your phone to PC and select LG Software
B2. Go to Device Manager and get the COM number from 'LGE AndroidNET USB Serial Port'
B3. Dial 3845#*455# (the last 3 numbers depends on your model)
B4. Select Settings
B5. Seletc Diag Settings
B6. Seletc UART Set for Diag
B7. Go Back
B8. Select Data Settings
B9. Select UART Set for Data
B10. Go back
B11. Open Putty and select "Serial"
B12. Write the COM port you get on step B2 (ex.: COM6) in the proper field. Click OPEN
B13. Type AT and hit ENTER. You should get an 'OK'. If not, check the COM port number (If you don't get any letter while typing, type ATE1, hit ENTER. You should see 'OK')
B14. Type at%imei=x,x,x,x,x,x,x,x,x,x,x,x,x,x,x (with the commas), where x,x,x... is your orginal IMEI number. It should response IMEI WRITE OK
B15. Type at%imei2=x,x,x,x,x,x,x,x,x,x,x,x,x,x,x (with the commas), where x,x,x... is your orginal IMEI number. It should response IMEI WRITE OK
B16. Close PuTTy terminal
B17. Reboot phone
I still don't have the "efs" folder, so maybe this is only a workaround. Also, I don't know if I flash a firmware I will lost IMEIs again.
But phone is working now. Calls, SMS, 3G... everything!
Good luck!
Related
Expired
Access to doc-00-2k-docs.googleusercontent.com was denied
I cant access the page.
sorry ,, the for the useless google drive broken links ,, i will update the links now
I updated all,,links now u see
This is fantastic. I'm using the t-mobile version. It's excellent, but I'm having a problem with wifi. Does anyone have any recommendations?
change ur wifi region in router webpage to north america and see
i tested this,, this both zips 5 to 6 times ,,but there is no problem for me ,,
go to ur router webpage ,,,and change ur wifi region to north america ,,and then ur phone will start detecting ur region
even i use to change my wifi region in router page to north america,,the my wifi started working
u follow this link here for ur problem :- https://youtu.be/IJ6Vj9_S4QE
So, i was working on an lg k7 and was told to remove the factory reset protection. Which that is apart of the set up wizard for lg so I removed that. Yes it was rooted. But, when I rebooted the device It said security error, authentication error #9 (modification). Ok, so I researched and it is fixable, but the lg download tool will not find the device. The download driver screen goes to 100% and I left it there for a couple hours and theres nothing. and the same exit button remains. I have tried the kdz download and that didnt work either. tried odin or twrp, which twrp is already on the device, but I cannot access anything. Any help with this? been working on it for weeks and its nothing but a head ache.
one thing u did completely wrong process,, setup wizard is a part of LG OS ,,IF U REMOVE IT WILL BREAK UR OS
THE MAIN REASON WHY YOU ARE NOT ABLE TO BOOT INTO RECOVERY IS THIS ONE :- [KERNEL/RECOVERY IS NOT SEANDROID ENFORCING] ON BOOT ,, IF U REMOVE IT FROM BOOT IMG ,THEN IT WILL MAKE U TO BOOT INTO RECOVERY,, AS IT WILL PROTECT U TO BOOT INTO CUSTOM TWRP RECOVERY ,,SO ULTIMATELY U NEED ONE [KERNEL/RECOVERY IS NOT SEANDROID ENFORCING] ON BOOT ,,REMOVED BOOT IMG
So, how do I obtain that one kernal/recovery and flash it on that phone?
Thank you for the quick and detailed reply.
My router is set up correctly.
I also have two identical LG K7 devices. The only difference is that one has your rom and the other is rooted stock.
The one without your rom can connect to Wifi with no issue.
The other one cannot. I enable Wifi and it hangs, as does Bluetooth. The Wifi Icon flashes consistently. Bluetooth just gives an error and goes off.
I believe that another member is having a similar issue, as posted here.
First of all ,,u unlock it boot loader ,,,boot up it android
Go to settings
,,after that go to software info
,,then after go to about phone,and,, Tap the build number until u see you are a developer message
Get into developer options now
Then enable USB debbuging and OEM unlock
Then download Android SDK platform tools
After that open a command windows ,,on the directory where u extracted adb ,,now type adb devices ,,,u will get one pop up like allow RSA key in it phone,,u just allow it,,
Now type command :- adb reboot bootloader
After that it will reboot bootloader,,note bootloader unlock commands are present on the display of the mobile
Note if it device does not support bootloader unlock ,,then it will not allow ur phone into bootloader
After that root ur phone with kingroot or kingroot
Then use flashify to flah twrp
RahulMantha said:
Expired
Click to expand...
Click to collapse
Oh no!
Stuck on "Connect to the network to activate device" after flashing official ROM
So my phone started randomly rebooting a few days ago and after a few tries to fix it, I managed to brick it altogether (seemed dead except for the red EDL led flashing when on charger). After DIY'ing a deep flash cable, I was able to get the PC to recognize it and flash the latest official stable Kenzo MIUI. I'd tried Kate before, but that just led to bootloops. Anyway, finally the phone booted normally and I went through the regular initial setup, until I got to this one screen, which reads:
Connect to the network to activate device
Your device is associated with an existing Mi Account (#########). Connect to the network to verify the device.
Connect to Wi-Fi or insert a SIM card.
Click to expand...
Click to collapse
Then it eternally tries to connect to the network and never does. I have 2 options below: Connect to Wi-Fi and Search for SIM card. The problem is that the Wi-Fi option detects no networks (there's definitely a few available) and the SIM is already inserted (it asked me for a PIN) and is visibly detecting a signal, but no mobile data is activated. The installation even asked for permission to send an automated SMS at some point, which succeed (and I even got a reply, which I can't read) but that did nothing to remedy the situation.
I can't leave this screen at all and the device isn't activating either WiFi or mobile data.
What gives?
My bootloader is locked and TWRP isn't installed, btw. I'd never fiddled with the stock ROM before this little adventure and everything I've flashed since has been official.
Make sure you're connected to WiFi with reasonable speed.
You must use the same MI account to login which was used earlier, i.e. before the brick.
Try flashing with option clean all lock through EDL once again.
If none of the above options work, try these :
> Find help on this thread http://en.miui.com/thread-424945-1-1.html
> RBFsoft tool to unlock (Unofficial)(tested by me)
> Visit service center last resort.
VaibhavKumar07 said:
Make sure you're connected to WiFi with reasonable speed.
Click to expand...
Click to collapse
I'm not, I already mentioned the phone detects no networks.
VaibhavKumar07 said:
You must use the same MI account to login which was used earlier, i.e. before the brick.
Click to expand...
Click to collapse
I intend to, but I don't even get the option.
VaibhavKumar07 said:
Try flashing with option clean all lock through EDL once again.
Click to expand...
Click to collapse
It's what I did in the first place.
VaibhavKumar07 said:
If none of the above options work, try these :
> Find help on this thread
> RBFsoft tool to unlock (Unofficial)(tested by me)
> Visit service center last resort.
Click to expand...
Click to collapse
Thanks for trying to help, but I'm not trying to unlock the phone or skip the activation, I'm trying to go through with it. To clarify, my only issue is that my phone is not connecting to the internet.
Typing that out, I'm guessing I should attempt to flash a modem.
Akkuron said:
I'm not, I already mentioned the phone detects no networks.
I intend to, but I don't even get the option.
It's what I did in the first place.
Thanks for trying to help, but I'm not trying to unlock the phone or skip the activation, I'm trying to go through with it. To clarify, my only issue is that my phone is not connecting to the internet.
Typing that out, I'm guessing I should attempt to flash a modem.
Click to expand...
Click to collapse
Okay, I got it let me know the model number of your device 2015116 or 2015161.
It's written on the box of the device.
VaibhavKumar07 said:
Okay, I got it let me know the model number of your device 2015116 or 2015161.
It's written on the box of the device.
Click to expand...
Click to collapse
Sadly the box is 2500km away right now. I can PM you the product page that shows the exact make+ROM if that helps you identify the model.
edit: It is the Kenzo version according to the product page on the shop at least.
Akkuron said:
Sadly the box is 2500km away right now. I can PM you the product page that shows the exact make+ROM if that helps you identify the model.
Click to expand...
Click to collapse
Yeah send pm
So I've flashed a ROM that lets me bypass the initial activation screen and access the phone's settings. My fear has been confirmed that the phone has lost the IMEI/baseband info etc.
Is there a way to find the IMEI except the phone's box so I can follow a guide to fix this?
You have a Redmi note 3 pro aka Kenzo, LHOCNDD means it came with the Chinese version of the ROM installed.
But to recover your device first try to clean flash & lock the ROM you have, also mention the package name ( Try flashing Chinese developer )
I know you may feel this is an inappropriate solution but you'll require unlocked bootloader enter developer options to flash using fastboot commands.
So, right now you can't flash modem files NON-HLOS.bin or a full ROM with fastboot commands http://en.miui.com/thread-469662-1-1.html or http://en.miui.com/thread-250455-1-1.html
Now the only option you have is to unlock unofficially http://en.miui.com/thread-345728-1-1.html , after you recover your device you can lock it & factory reset.
But remember not to use commands Fastboot flash aboot emmc_appsboot.mbn & Fastboot flash abootbak emmc_appsboot.mbn if you have unlocked bootloader unofficially.
---------- Post added at 07:31 PM ---------- Previous post was at 07:19 PM ----------
Akkuron said:
So I've flashed a ROM that lets me bypass the initial activation screen and access the phone's settings. My fear has been confirmed that the phone has lost the IMEI/baseband info etc.
Is there a way to find the IMEI except the phone's box so I can follow a guide to fix this?
Click to expand...
Click to collapse
Okay, so which ROM did you flash MIUI 7? mention package name & http://en.miui.com/thread-375213-1-1.html use this guide to recover IMEI if you don't have the box I doubt if there's IMEI written on the label as our device has a non-removable battery.
So, you need the box & don't proceed in a hurry without proper instructions.
I've found the IMEI number and almost got through the instructions in the link you posted. My problem is when the time comes to use WriteDualIMEI(W+G_eMMC) it asks for 2 IMEI numbers and not one. Pressing start does nothing with only one of them typed in, but I my box has no second number on it.
edit: ROM that first let me in was official 7.2.3 which is apparently the only version that didn't require validation, now I'm on the rooted Sphinx ROM from that link though.
Akkuron said:
I've found the IMEI number and almost got through the instructions in the link you posted. My problem is when the time comes to use WriteDualIMEI(W+G_eMMC) it asks for 2 IMEI numbers and not one. Pressing start does nothing with only one of them typed in, but I my box has no second number on it.
edit: ROM that first let me in was official 7.2.3 which is apparently the only version that didn't require validation, now I'm on the rooted Sphinx ROM from that link though.
Click to expand...
Click to collapse
Don't make any changes to the current setup, let me gather some info & get back to you.
By the way, dual sim variant will have 2 IMEI numbers.
Edit: First, let me know the baseband & IMEI shows unknown or 0?
---------- Post added at 02:12 AM ---------- Previous post was at 01:27 AM ----------
If it shows 0, then write same IMEI in both slots & proceed.
Shows up as unknown. I've read it's supposed to have 2 IMEIs but only 1 is on the box (and the sticker inside the device).
Akkuron said:
Shows up as unknown. I've read it's supposed to have 2 IMEIs but only 1 is on the box (and the sticker inside the device).
Click to expand...
Click to collapse
Follow this guide & recover EFS
https://forum.xda-developers.com/redmi-note-3/how-to/flash-recover-efs-snapdragon-t3406789 then write IMEI same in both slots.
VaibhavKumar07 said:
Follow this guide & recover EFS
https://forum.xda-developers.com/redmi-note-3/how-to/flash-recover-efs-snapdragon-t3406789 then write IMEI same in both slots.
Click to expand...
Click to collapse
Flashing the 2 modemst files through fastboot just caused a bootloop.
edit: got out of the bootloop by flashing a stock developer ROM (miui9) and now my baseband is recognized. My IMEI numbers are a mix of unknowns and 0s. Problem is the phone isn't rooted now.
Should I flash TWRP and root it with that, or just try to flash that rooted Sphinx ROM again? Don't wanna brick it again now that we're getting somewhere.
Akkuron said:
Flashing the 2 modemst files through fastboot just caused a bootloop.
Click to expand...
Click to collapse
Can you run the command fastboot oem device-info & send the result?
Sent from my Redmi Note 3 using Tapatalk
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.008s]
Akkuron said:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.008s]
Click to expand...
Click to collapse
*Deleted*
---------- Post added at 05:25 AM ---------- Previous post was at 04:55 AM ----------
Please don't edit posts, just send a new reply.
As you're on MIUI 9 Global ROM, unlock right away if you have official permissions.
If not http://en.miui.com/thread-345728-1-1.html unlock unofficially & skip EFS restore, proceed to write IMEI.
when you flash a ROM provide the name of the package.
Writing the IMEI doesn't work because I don't have root permissions on the stock global ROM (kenzo_global_images_7.11.6_20171106.0000.00_6.0_global). Is there a way to enter diagnostic mode without it, or should I just root?
Update: Rooted, but WriteDualIMEI(W+G_eMMC) gives me a "No diag port" error, despite detecting the port (COM11) that the phone is connected on. Device Manager confirms as it recognizes it as "Qualcomm HS-USB Android DIAG 901D (COM11). Tools like QPST and RF NV Manager can interface with the phone normally. I tried writing the IMEI through RF NV Manager, but it only went into IMEI2. IMEI1 is "unknown" still.
Akkuron said:
Writing the IMEI doesn't work because I don't have root permissions on the stock global ROM (kenzo_global_images_7.11.6_20171106.0000.00_6.0_global). Is there a way to enter diagnostic mode without it, or should I just root?
Update: Rooted, but WriteDualIMEI(W+G_eMMC) gives me a "No diag port" error, despite detecting the port (COM11) that the phone is connected on. Device Manager confirms as it recognizes it as "Qualcomm HS-USB Android DIAG 901D (COM11). Tools like QPST and RF NV Manager can interface with the phone normally. I tried writing the IMEI through RF NV Manager, but it only went into IMEI2. IMEI1 is "unknown" still.
Click to expand...
Click to collapse
Hold on, you're making the situation worse.
Is the bootloader unlocked & USB debugging enabled?
type adb devices to check communication.
I'll try to find some other solution, so have patience.
Only proceed on your own if I'm dead.
VaibhavKumar07 said:
Hold on, you're making the situation worse.
Is the bootloader unlocked & USB debugging enabled?
type adb devices to check communication.
I'll try to find some other solution, so have patience.
Only proceed on your own if I'm dead.
Click to expand...
Click to collapse
Fastboot oem device-info says the bootloader is locked, but I'm pretty sure I'd unlocked it at some point.
USB debugging is enabled.
ADB devices detects the phone normally.
Akkuron said:
Fastboot oem device-info says the bootloader is locked, but I'm pretty sure I'd unlocked it at some point.
USB debugging is enabled.
ADB devices detects the phone normally.
Click to expand...
Click to collapse
ROM version, Bootloader unlock method & when did you unlock?
---------- Post added at 03:39 PM ---------- Previous post was at 03:32 PM ----------
Did you restore EFS before writing IMEI?
So basicaly I was being lazy and in a rush. I had done something like this before on much older phone(s) with no issues...
I backed up my working LG G5 in TWRP all partitions. I brought exactly the same model for my wife and wanted to restore my backup to that phone (I have made many customisations on my rom and didnt want to have to manually do it all again for her)
However after unlocking the bootloader, flashing TWRP and installing new base rom (all went fine) I then went to restore my old backup onto this new phone, stupidly I ticked all partitions to restore. I have a feeling that I should have only done the larger partitions. Once I rebooted I got the "cant be trusted" message, I reflashed in UPPERCUT but then the phone booted and then had secureboot enabled. I hit the wrong password (as there was none) 30 times which then forced a format. Now the phone boots fine and works 100% BUT...BUT....
I now can no longer unlock the bootloader as I think its trying to use MY phones bootloader (as its unlock.img says its the wrong one, I have tried both MY phones original unlock.img and my wifes new phones unlock.img but both dont work) I cannot relock the bootloader as it says its already locked... this also now means that through LG official software I cannot recover the phone. Only UPPERCUT can see the phone. I can get to download mode and fastboot.
Also the phones IMEI now says 0, this worried me however her SIM card is working 100% fine (I guess that the IMEI
is cached somewhere, but im worried that if I use some cleaning tools it may scrub it and then she will have no network access)
So basicaly if her phone starts to play up (or I want to upgrade it to Oreo / Lineage at a later date) can anyone offer me advice on how to...
A: Fix / Restore the bootloader (I dont mean recovery) Im confused as to if this is stored on a chip or can be reflashed from the kdz firmware images.
B: Resore the IMEI (I have it written down) incase we get any network issues in the future. Can it be resored or regenerated without some fancy hardware, ie only through software.
C: I dont have Root or TWRP access it seems, any way of Getting Magisk or Super SU on a phone without bootloader unlock, root access or TWRP?
I have had many years experience and never bricked a phone but almost did this time.
I decided to post a solution here, because it was one of the first Google results when I was looking for some help.
Long story short, I did exactly same mistake of restoring all partitions, including the EFS, between two same LG devices. Turns out it messes with IMEI, which is a big no no and phone locks. Now you can't unlock the device again, because there is no IMEI to use in unlocking. Also no flashing or erasing anymore, because it just fails.
So the IMEI needs to be restored first.
My phone was in a bootloop constantly showing the "cant be trusted" message, but I managed to fix that using LGUP. Apparently not all partitions are locked, because trying to flash the same system with LGUP fixed the bootloop, but failed to flash clean system and the data that TWRP flashed was still there. Trying to restore system to factory settings also fails, but it doesn't matter.
Fortunately I was able boot the system, which made fixing it easier than you'd expect:
1. Fixing the IMEI from booted system (no root or unlocking needed):
- Access the hidden menu on your device by dialing a proper number. For LG G5 H850 it is *#546368#*#850#
Where 850 in the last part is your phone model. The number will vary for different models.
- Go to SVC Menu -> CRCWIZARD Test
- Switch tab to Auto MID
- Here you can enter your new IMEI and WiFi and BT MAC addresses, or you can just generate it.
You can also use the generate option for all values and then manually change only the IMEI for the original one.
- Press MID Write button and reboot your device.
- That's it. IMEI issue should be fixed now.
2. Now that you restored your original IMEI, you can again unlock your device using the same unlock.bin file that you used to unlock bootloader the first time.
Voila. From now on the device is again unlocked and you can just go back to flashing whatever you need.
As in the title, I have an, Alcatel Tcl Lx A502dl, Android phone, originally purchased from Walmart with a Trackfone Sim card (Now there is no sim card insterted).
I have spent all day, up until now, figuring out how to link abd and fastboot to the phone using USB debugging, and I have been successful this far. I had downloaded latest "platform-tools_r29.0.1-windows" from here on XDA, and I downloaded latest "fatsboot" from "HighonAndroid.com", for a quicker experience, without wasting time and effort on Java downloads. In addition to all this, I let the computer search the network for updating driver software, for my Alcatel phone. I also downloaded "UniversalAdbDriverSetup", from the former link, @highonandroid.com.
I linked both file pathways for corresponding "Fastboot", and "platform-tools", into the environment variables, under the term: "Path", yes, using a ";" with no spaces to add the new pathways.
I had success linking my phone onto the "abd" program, the phone is listed under "abd devices" command. I could not seem to get a listing of my phone serial number, under the "fastboot devices" command?
I have tried to get "platform-tools" to put the phone into "fastboot/bootloader" mode, but the phone simply reboots, back to the lockscreen. I have also tried on "Fastboot", to "fastboot reboot bootloader", and my Alcatel again reboots to the lockscreen. All the while, I activated the OEM unlocking switch/setting in the "developer options" of my phone, from the beginning, before I ever gave any commands?
Why won't my Alcatel phone reboot into the "fastboot/bootloader" screen, where I could command "fastboot oem unlock"? Why does my phone respond to both programs, yet still she loads the lockscreen?
I am new to all this, not really a tech savvy individual, just wanted a liberated operating system for my line of work...
I need bootloader unlocked in order to root my device via computer, correct?
I can not check to see if my bootloader is unlocked, not by abd tools, or by numerical code in my "dialer app". The app crashes, and any time I attempt the "fastboot oem device-info" command, no device is listed, only a <looking for a device> prompt of sorts appears. I have been told this may be because, the drivers were not installed properly, or the device was not properly connected under some other issue, and I can try to fix this error by reinstalling drivers... what would the issue be?
I need help, and I would appreciate some guidance on rooting my Android, as there are not any threads in the forum, on this model of Alcatel, that I am aware of?
I am doing all of this on a Windows 7 computer, in a Library, just so you all know. I ask for administrative approval for most things.
Thank you.
tcl trackfone
Hello i was wondering if you ever got your phone rooted?
me to i have that problem on my tcl lx
to
Temporary mtk- root. Use init.d for always root
Sonjouten said:
Temporary mtk- root. Use init.d for always root
Click to expand...
Click to collapse
I can't possibly express how much I would love for you to elaborate on the 'use init.d for always root' part. Anyone else who knows, please jump in. Start by pretending I am an idiot. Then stop pretending and explain it to me as if I were an adult who needs a full-time minder. First one to help me achieve "always root" on this terrible, wretched, little excuse for an electronic device gets my undying gratitude and um, maybe some Google Play money? I am open to ideas here on that score. To reiterate, need help rooting my Tracfone TCL LX A502DL that has a castrated recovery (seriously, you can't flash anything from adb, the option is flat-out missing) and apparently no fastboot access AT ALL. I could do another seriously in parentheses, but you need to take my word for it w/o a bunch of examples. The bright spot is the vulnerability the device has to the mtk-su exploit. Get a # in like no time at all. Time elapsed from executing the file to getting the prompt is too short for my flesh computer to register (unless you -v, then about 1.5 seconds.) So how do I turn a root prompt into full root?
I can't possibly express how much I would love for you to elaborate....
Click to expand...
Click to collapse
WHAT HE SAID
+1
X2
etc
Thank you, H
Did he get that?
So did he earn that Google Play Store money or was he just full of it?
Just bumping this thread in case anyone has ideas for me. Seems like Alcatel has bootloader mode hidden on some phones. Here's my story: https://forum.xda-developers.com/showthread.php?p=81780645#post81780645
BTW - I am using mtk-su and have root and Magisk via init.d scripts, but still can't touch /system or flash recovery because of
Code:
/dev/block/dm-0' is read-only
which won't change unti bl unlocked...
I never did get her to root. Alas she is a broken phone now RIP. Sorry for the disappointments. But I move on more hopeful. ?
As posted by Viva La Android in another thread about the tcl a501dl:
The TCL A1 (A501DL) cannot be bootloader unlocked. Although the OEM Unlocking option can be enabled in the Developer Options menu, fastboot mode has been made inaccessible by TCL. Because the bootloader cannot be unlocked, it simply is not possible to flash a custom recovery or a patched boot image for systemless root support. System-wide root is not possible due to TCL's secure boot chain configuration and dm-verity. Until an exploit is found to bootloader unlock this device, rooting is not possible.
Click to expand...
Click to collapse
levone1 said:
Just bumping this thread in case anyone has ideas for me. Seems like Alcatel has bootloader mode hidden on some phones. Here's my story: https://forum.xda-developers.com/showthread.php?p=81780645#post81780645
BTW - I am using mtk-su and have root and Magisk via init.d scripts, but still can't touch /system or flash recovery because of
Code:
/dev/block/dm-0' is read-only
which won't change unti bl unlocked...
Click to expand...
Click to collapse
I have tried everything, and can't even get temporary root on my A502DL. How did you do this, if you don't mind? Thanks!
fliproc said:
I have tried everything, and can't even get temporary root on my A502DL. How did you do this, if you don't mind? Thanks!
Click to expand...
Click to collapse
Sorry, I honestly don't remember now - I just happened to have tje phone for a short time at that moment, so I was messing around with it... I remember there was nothimg special about it. I jist followed the instructions from the mtk-root thread and it worked.
Amazing Temp Root for MediaTek ARMv8 [2020-08-24] | XDA ...
Braadleyah said:
As in the title, I have an, Alcatel Tcl Lx A502dl, Android phone, originally purchased from Walmart with a Trackfone Sim card (Now there is no sim card insterted).
I have spent all day, up until now, figuring out how to link abd and fastboot to the phone using USB debugging, and I have been successful this far. I had downloaded latest "platform-tools_r29.0.1-windows" from here on XDA, and I downloaded latest "fatsboot" from "HighonAndroid.com", for a quicker experience, without wasting time and effort on Java downloads. In addition to all this, I let the computer search the network for updating driver software, for my Alcatel phone. I also downloaded "UniversalAdbDriverSetup", from the former link, @highonandroid.com.
I linked both file pathways for corresponding "Fastboot", and "platform-tools", into the environment variables, under the term: "Path", yes, using a ";" with no spaces to add the new pathways.
I had success linking my phone onto the "abd" program, the phone is listed under "abd devices" command. I could not seem to get a listing of my phone serial number, under the "fastboot devices" command?
I have tried to get "platform-tools" to put the phone into "fastboot/bootloader" mode, but the phone simply reboots, back to the lockscreen. I have also tried on "Fastboot", to "fastboot reboot bootloader", and my Alcatel again reboots to the lockscreen. All the while, I activated the OEM unlocking switch/setting in the "developer options" of my phone, from the beginning, before I ever gave any commands?
Why won't my Alcatel phone reboot into the "fastboot/bootloader" screen, where I could command "fastboot oem unlock"? Why does my phone respond to both programs, yet still she loads the lockscreen?
I am new to all this, not really a tech savvy individual, just wanted a liberated operating system for my line of work...
I need bootloader unlocked in order to root my device via computer, correct?
I can not check to see if my bootloader is unlocked, not by abd tools, or by numerical code in my "dialer app". The app crashes, and any time I attempt the "fastboot oem device-info" command, no device is listed, only a <looking for a device> prompt of sorts appears. I have been told this may be because, the drivers were not installed properly, or the device was not properly connected under some other issue, and I can try to fix this error by reinstalling drivers... what would the issue be?
I need help, and I would appreciate some guidance on rooting my Android, as there are not any threads in the forum, on this model of Alcatel, that I am aware of?
I am doing all of this on a Windows 7 computer, in a Library, just so you all know. I ask for administrative approval for most things.
Thank you.
Click to expand...
Click to collapse
I have heard elsewhere that it's not possible to unlock the bootloader of a Tracfone. Sorry. But at least we know why Tracfones are sold for so cheap lol
$cronos_ said:
I have heard elsewhere that it's not possible to unlock the bootloader of a Tracfone. Sorry. But at least we know why Tracfones are sold for so cheap lol
Click to expand...
Click to collapse
unlock bootloader and root with https://github.com/bkerler/mtkclient
This device cannot be rooted. To date, there has not been a single validated claim of a rooted TCL A509DL. The bootloader cannot be unlocked, preventing root, custom ROM installs,etc.
UPDATE: After hearing from some members regarding the Hydra Tool, and doing a little bit of research on the method, it appears that I was completely wrong on my.statement. Members here on XDA as well as Hovatek have confirmed that the A509DL bootloader can indeed be exploited with the Hydra Tool method, opening the door to systemless root with Magisk. Thanks guys for the info and guidance. I have one of these devices and look forward to unlocking & rooting soon. Thanks @PrivyetCyka for the info.
Yes it can .. it was extremely easy to do so also..i have a rooted one in my hand as we speak the only issue is I was stupid and tried to flash the magisk zip in twrp and it set off secureboot so in working on fixing that .. but .. if you just use MTKClient you can pull the entire firmware , magisk patch then reflash the boot.img using the same tool and you can even install twrp I have the entire firmware , twrp, and magisk patched boot imgs for the device saved ,. If someone knows how to disable secureboot I would really appreciate it
Viva La Android said:
This device cannot be rooted. To date, there has not been a single validated claim of a rooted TCL A509DL. The bootloader cannot be unlocked, preventing root, custom ROM installs,etc.
Click to expand...
Click to collapse
I sure would like to give it a whirl, but I haven't had that phone in over a year
Anyway, I decided to stop buying devices made deliberately less functional by their manufacturers.
PrivyetCyka said:
Yes it can .. it was extremely easy to do so also..i have a rooted one in my hand as we speak the only issue is I was stupid and tried to flash the magisk zip in twrp and it set off secureboot so in working on fixing that .. but .. if you just use MTKClient you can pull the entire firmware , magisk patch then reflash the boot.img using the same tool and you can even install twrp I have the entire firmware , twrp, and magisk patched boot imgs for the device saved ,. If someone knows how to disable secureboot I would really appreciate it
Click to expand...
Click to collapse
I stand corrected on my statement. I was incorrect. Out of curiosity, does the Hydra tool require the dongle in order to unlock the bootloader?
@PrivyetCyka send me the Magisk packed boot image and I will unpack it and disable secure boot. I can then pack it back up and link it to you. Are you referring to only secure boot or also AVB 2.0/dm-verity?
I didn't use hydra tool I used MTKClient from GitHub and did an entire system read back to have a backup then just renamed boot.bin to boot.img used magisk to patch it and then used the same MTKClient tool to reflash it... I have a twrp I made for it also but I don't know how functional it is as far as flashing things and backups , the only thing I tried to flash was the magisk zip just to see what would happen and that tripped the secureboot , I used the mediatek secureboot tool and it says it's disabled but it's still not booting past the secureboot fail screen.. when I get home I'll get the files and upload them tonight
Hi there!
I found an LG G6 with cracked screen in the trash. There was no SIM-Card and no SD-Card in there, but it still seems to work. It has encrypted userdata so I couldn't boot it to see if there's any contact info displayed.
I found I could factory reset the phone by getting into the stock recovery and switching to yes two times.
Now it boots but it will not allow me to enter the phone without giving it an internet connection and logging in with a previously used google account. Since I found this phone and was not able to find out who the previous owner was I of course do not have a google account that was used on the phone previously.
I also booted into fastboot but can't do anything because the bootloader is locked, and it of course was not left by the previous owner with the developer option to allow for unlocking set.
Is there some way to get this phone operational again so it can be used for something more than spare parts (minus the main-board)?
Thank you!
Why dont you flash kdz file? From lg-firware. Com . Oh wait if you cant see imei if you cant get inside phone...
Ah, that's an idea, I will try that. Thank you for the tip. Unsure if a stock ROM flash will reset that google account lock, but I guess it doesn't hurt to try.
hagekic548 said:
Ah, that's an idea, I will try that. Thank you for the tip. Unsure if a stock ROM flash will reset that google account lock, but I guess it doesn't hurt to try.
Click to expand...
Click to collapse
Does it work?
Sadly, no. I tried a few of the LG Tools.
"LG Mobile Support Tool" could connect and told me there is an update available and I should use "LG Bridge" to install that.
"LG Bridge" won't connect because it tells me it requires an MTP connection and I need to allow acccess to "telefon data" if Android 6 or later is installed (which quite certainly is).
Since the phone doesn't let me in (only shows me the first setup wizard which I can't pass without the google account of the previous owner) I can't enable file sharing or accept any requested permissions.
UPDATE: Ah, now I found an "correct update problems" button in "LG Bridge", with this he started downloading 3.28GB worth of firmware, let's see whether he will manage to flash that after downloading it and if so if that does remove the google account lock.
UPDATE2: So I've researched a bit more and found that what my problem is (phone locked to previous google account) is called "FRP Lock" = Factory Reset Protection.
There are a few guides that show how you can use the accesibility feature talkback to get to youtube which allows you to open chrome which allows you to open the phone app. This allowed me to get my IMEI using the *#06# code.
But so far I could not find a phone app code that opens a service menu on this LG G6 H870 which would be required to follow the FRP guides further.
UPDATE3: haha yes the "correct update problems" procedure from "LG Bridge" updated to a newer firmware while leaving my wifi config I've entered during the UPDATE2 step but removing the "FRP Lock".
deleted accidental post
hagekic548 said:
Sadly, no. I tried a few of the LG Tools.
"LG Mobile Support Tool" could connect and told me there is an update available and I should use "LG Bridge" to install that.
"LG Bridge" won't connect because it tells me it requires an MTP connection and I need to allow acccess to "telefon data" if Android 6 or later is installed (which quite certainly is).
Since the phone doesn't let me in (only shows me the first setup wizard which I can't pass without the google account of the previous owner) I can't enable file sharing or accept any requested permissions.
UPDATE: Ah, now I found an "correct update problems" button in "LG Bridge", with this he started downloading 3.28GB worth of firmware, let's see whether he will manage to flash that after downloading it and if so if that does remove the google account lock.
UPDATE2: So I've researched a bit more and found that what my problem is (phone locked to previous google account) is called "FRP Lock" = Factory Reset Protection.
There are a few guides that show how you can use the accesibility feature talkback to get to youtube which allows you to open chrome which allows you to open the phone app. This allowed me to get my IMEI using the *#06# code.
But so far I could not find a phone app code that opens a service menu on this LG G6 H870 which would be required to follow the FRP guides further.
UPDATE3: haha yes the "correct update problems" procedure from "LG Bridge" updated to a newer firmware while leaving my wifi config I've entered during the UPDATE2 step but removing the "FRP Lock".
Click to expand...
Click to collapse
So , you can use it now? If frp lock is removed....
Service menu i know is *#546368#*870# for you. Mine is h873 , but sadky i shouldnt factory reset at first , now i am stuck with no data or call . cannot get sim card configuration settings.
surfshark said:
So , you can use it now? If frp lock is removed....
Click to expand...
Click to collapse
yes, it can be used now, thank you for your help!
The "correct update problems" button in "LG Bridge" did the trick.
The stuff I've described in the "UPDATE2" block was just what I was trying while waiting for the huge download to finish, but it didn't lead to anything. Though it did allow me to get the IMEI by giving me access to youtube, chrome & the phone app.
hagekic548 said:
The "correct update problems" button in "LG Bridge" did the trick.
The stuff I've described in the "UPDATE2" block was just what I was trying while waiting for the huge download to finish, but it didn't lead to anything. Though it did allow me to get the IMEI by giving me access to youtube, chrome & the phone app.
Click to expand...
Click to collapse
Ahh ok! Not many ppl response here. I am new too here but couldnt get any answers i am looking for but. Good that it works for you.
yes, it seems XDA's best days lie behind it sadly. They seem to make it deliberately hard to actually reach the device specific forums instead of their curated blog stuff nowadays.
hagekic548 said:
yes, it seems XDA's best days lie behind it sadly. They seem to make it deliberately hard to actually reach the device specific forums instead of their curated blog stuff nowadays.
Click to expand...
Click to collapse
If you know or came across on this site about how to fix data signal blocked or in other words message and call blocked or how to flash any modem of the g6 without rooting do let me know.
surfshark said:
So , you can use it now? If frp lock is removed....
Service menu i know is *#546368#*870# for you. Mine is h873 , but sadky i shouldnt factory reset at first , now i am stuck with no data or call . cannot get sim card configuration settings.
Click to expand...
Click to collapse
Has anyone had difficulty bypassing from due to being unable to update YouTube? That's the issue I've been having