Related
hope someone can help me. have unlocked my bootloader and did an update kdz i did a hardreset and now when i boot up my phone it says
THIS DEVICE WAS RESET. TO CONTYNUE SIGN IN WITH A GOOGLE ACCOUNT THAT WAS PREVIOUSLY SYNCED ON THIS DEVICE.
i put my email address in and password and it just take me back to the wifi screen it just keeps looping back like this, ive read this in a new thing with android 5.1 and after 72 hours i can login but its been like 4 days now and still cant use my g4 is there anything i can do to get my phone working again.
any help would be great
Try to connect to different wifi if then your phone will sync with google account.
its been almost aweek now with out my g4 still cant get past this tried kdz updates 10b 10c and still no joy can anyone help sort this
gavo84 said:
its been almost aweek now with out my g4 still cant get past this tried kdz updates 10b 10c and still no joy can anyone help sort this
Click to expand...
Click to collapse
Call in for a replacement.
BAD ASS NOTE 4 & LG G4
ive gone and unlocked the bootloader
gavo84 said:
ive gone and unlocked the bootloader
Click to expand...
Click to collapse
...?
gavo84 said:
ive gone and unlocked the bootloader
Click to expand...
Click to collapse
So you probably unlocked it to be used on other carriers as only the H815 can have an unlocked bootloader.
Just a small sugestion. Have you tried to create a new google account and sync with it to see what happens?
tried that and just tried it again with new account still in a loop. i unlocked the bootloader for root now when u unlock the boot loader lg remove warranty
anyone out there that can help.
https://youtu.be/ukE0mA7yFIM
Did you try clearing cache all google related apps like google service framework ?
what i have done is hardreset not sure how i can clean cache all google related apps like google service framework, as thats the only screen i can see i posted a video of whats happening, i have been on the pgone to google then its not them ring lg, i spoke to lg and emailed them a video waiting for a call back off them.
Maybe try booting into recovery in order to wipe EVERYTHING (and I mean everything possible).
Then boot back into download mode and flash the STOCK .kdz file (the one that your phone came from your carrier with, 10a/b which it was depending on how long you have had your phone).
If that does not work maybe try to build or get a custom AOSP Rom that does not have the GAPPS and see if you can just by-pass the issue all together by booting with having to deal with google apps (you would still need a work around for getting Gapps to work, but at least you would know exactly what the problem is and could boot into a working phone in the mean time).
Weird. Might be that 72 hour sign in feature (cough* bug *cough) thing because it looks like it might be kicking it back on the server side.
1) Did you try signing in on mobile data?
2) Do you have a nandroid, TB, or LG backup that you can restore?
2) Try bypassing the setup screen (keep tapping Next or Skip) and just get to the home screen. Then goto Settings ---> Accounts and add your account. This way you can get a usable device.
ive tried STOCK .kdz 10a/10b/10c
i dont have a nand backup
ive tryed using other wifi and my mobile internet.
google say its not them and im still waiting for lg to even look at the video they asked for..
is there any roms even out there for the g4 i cant find any. over a week now with out my g4.
AOSP Rom i wouldnt know where to start on building one i no longer have root or TWRP after flashing kdz
cant get the phone in adb mode developer as i cant get past the wifi screen as seen in video and cant get USB debugging.
gavo84 said:
hope someone can help me. have unlocked my bootloader and did an update kdz i did a hardreset and now when i boot up my phone it says
THIS DEVICE WAS RESET. TO CONTYNUE SIGN IN WITH A GOOGLE ACCOUNT THAT WAS PREVIOUSLY SYNCED ON THIS DEVICE.
i put my email address in and password and it just take me back to the wifi screen it just keeps looping back like this, ive read this in a new thing with android 5.1 and after 72 hours i can login but its been like 4 days now and still cant use my g4 is there anything i can do to get my phone working again.
any help would be great
Click to expand...
Click to collapse
Did you buy phone new, from where?
the phone is on a 24 month contract from o2 i got the phone from the carphone warehouse
ive just got off the phone to LG still not looked at the video they asked for i have been told to wait 7 working days WHAT thats gonna be like two weeks with a none working phone.
Weird, it's like you got a refurbished phone, and the old google account was not removed the correct way (remove google account before the phone is reset). If you reset phone without removing your account you get exactly what has happened to your phone. I see it all the time on the Nexus 6 forum.
Hi everyone,
So my Verizon G4 VS986 recently had a bootloop issue and was sent in to LG to fix the phone. They sent it back and what they said they did was to replace the flash memory. Obviously the phone has been reset and all my data is wiped as warned before I sent the phone in. The phone now boots up but I'm stuck at verify your account. I logged in to my google account on this phone and after two step verification was a success, I still cannot move forward and am stuck at the verify your account.
I looked into this issue online and found that this is part of the Factory Reset Protection built into 5.1. In either case, I did not change my password to my google account at all, it is still the same password, so the 72 hour wait rule shouldn't apply here at all. I also can't bypass the protection either since some of the methods require that you go into the Accessibility as seen here through this link: http://forum.xda-developers.com/g4/general/tut-bypass-lg-lock-google-account-t3223518 . My issue is that that Accessibility menu is not present on the initial screen, only language and moving forward.
So what are my options now? Contact LG about my issue or is there a way I can contact Google? Is it possible that the original account information is stored on the flash memory which LG replaced and now the account I need to log in is of some different user? If that's the case, am I forever stuck on this screen and this phone is effectively dead? Or is there something I can do that I haven't discovered yet? If anyone could help, it'd be a great help, thank you.
falcon1ps2 said:
Hi everyone,
So my Verizon G4 VS986 recently had a bootloop issue and was sent in to LG to fix the phone. They sent it back and what they said they did was to replace the flash memory. Obviously the phone has been reset and all my data is wiped as warned before I sent the phone in. The phone now boots up but I'm stuck at verify your account. I logged in to my google account on this phone and after two step verification was a success, I still cannot move forward and am stuck at the verify your account.
I looked into this issue online and found that this is part of the Factory Reset Protection built into 5.1. In either case, I did not change my password to my google account at all, it is still the same password, so the 72 hour wait rule shouldn't apply here at all. I also can't bypass the protection either since some of the methods require that you go into the Accessibility as seen here through this link: http://forum.xda-developers.com/g4/general/tut-bypass-lg-lock-google-account-t3223518 . My issue is that that Accessibility menu is not present on the initial screen, only language and moving forward.
So what are my options now? Contact LG about my issue or is there a way I can contact Google? Is it possible that the original account information is stored on the flash memory which LG replaced and now the account I need to log in is of some different user? If that's the case, am I forever stuck on this screen and this phone is effectively dead? Or is there something I can do that I haven't discovered yet? If anyone could help, it'd be a great help, thank you.
Click to expand...
Click to collapse
Since no one has the answer, I'll chime in on my resolution. Call LG, send the phone back in, and they will get it fixed. In my case, they changed the motherboard this time, not only the flash memory. After that, no more verify your account issues. Still was in warranty, not sure if you get a bootloop out of warranty would they still fix it without charging you.
On Global ROM with Global Phone, TWRP successfully installed and rooted. Updated Magisk in apk and zip. Loaded and ran well many rooted apps over several days. Now, after backing up, then testing for a successful restore by formating the data partition and wiping other partitions as I have with previous TWRP installations on other Xiaomi phones (Redmi Note 5A, Redmi 5 Plus) from the SD card, I cannot successfully do so with RN 8 Pro. Backup and Restore is the main reason I have installed TWRP on all my previous phones, and I have saved myself huge problems just by restoring backups when needed. I can certainly wait for an official version, but are there any steps that must be taken to do a corredt backup and then restore on this phone with either of the 2 TWRP unofficial versions? Thanks for reading this.
Just more observations: the TWRP version posted on September 25 is now good-to-go for my backup/restore procedures: backup boot, data, system, system image and vendor and vendor image. The later TWRP version fom Agent_fabulous has continued to baffle me (Good to see all this development, and looking forward to future succeses). I restored wiping only dalvik and cache as well as system partition. It seems important, and I am not sure why, that data is NOT formated (did this a number of times, resulting in failures) , as there is an error when trying to restore the backup, after it was formated. Restoring, in any event, wipes data in its own restore process, so formating here is not necessary. This TWRP version, after following the detailed installation instructions, does work after some trial and error. Many iterations of building up from factory installation to what I wanted, losing it, building it up again. Now the warning from MIUI that any more requests for unlocking (which I seemed to need) will be met with a permanent lockout!! NOt sure about how to get around that, but I don't want to test it again ...
Thanks for reading this
Okay, bad news, as I have bricked this otherwise excellent phone: upgraded to beta 11 by using TWRP to flash Global V11, no red lines in what seemed successful, but the phone did not reboot. Tried to downgrade and flash V10 with TWRP, again seemed successful - no red lines, but when trying to reboot, the phone went completely dead. No response from any button (Volume +, - or Power). Tried flashing with SP_flash and received this message:
ERROR : STATUS_SEC_AUTH_FILE_NEEDED (0xC0030012)
[HINT]:
Please select a valid authentication file or ask for help
Xiaomi refused to help but said to contact the seller, who is on Ali Express and has not responded from 2 requests. I have since read that Xiaomi does NOT permit any downgrade on its newer phones. Is a bricking what happens when the attempt is made?
Then sent off the phone to a Xiaomi reseller here in Canada, and have yet to have any result. I assume that a ROM can be reinstalled, but my concern would be if the IMEI numbers would be lost, and unable to flash them on the NVRAM partition. Jeez ... my ignorance has caught up in a bad way ...
Ouch, I hope your device gets unbricked.
Okay, this link http://https://c.mi.com/thread-2173190-1-0.html has been referred to for getting Xiaomi authorization to unbrick their dead phones, with only a LED showing a connection to a USB port. I tried 2 weeks ago to apply for this authorization, but the final part to select and send a request to Xiaomi seemed not to work, so I abandoned the exercise. Instead, the phone was sent to a Xiaomi reseller and in such a downward and surprising turn, the phone has disappeared in Canada's postal delivery system. It has never arrived at the reseller's. The package was insured, Canada Post is looking into the problem, but nothing has been found. I went back to the first link mentioned here out of curiosity to see what I may have missed, and retraced the steps to have my computer get the authorization to unbrick the phone. To my surprise, the final step binding my computer to authorization to flash the phone allowed me to do just that. I have permission. There was no e-mail with the code sent (as was mentioned in the steps of the procedure in the link above), and I have no idea how long this permission had been granted. I also have no idea how Xiaomi sent permission to my computer without me knowing about it. In any event, I sent the phone off too soon, obviously, and now it is lost somewhere. For those who have a bricked RN 8 Pro, the link seems a best option to flash with Miflash with a wait time for authorization, and it may not be given by e-mail, but done right on the computer without your knowledge. H'mmm ... It has been a convoluted journey through a successful root and then a bricked Redmi Note 8 Pro. Hope to get the phone back, eventually, or a new one from the insurance. Will let you know .... Hey, thanks for reading this story.
ppthom said:
Okay, this link http://https://c.mi.com/thread-2173190-1-0.html has been referred to for getting Xiaomi authorization to unbrick their dead phones, with only a LED showing a connection to a USB port. I tried 2 weeks ago to apply for this authorization, but the final part to select and send a request to Xiaomi seemed not to work, so I abandoned the exercise. Instead, the phone was sent to a Xiaomi reseller and in such a downward and surprising turn, the phone has disappeared in Canada's postal delivery system. It has never arrived at the reseller's. The package was insured, Canada Post is looking into the problem, but nothing has been found. I went back to the first link mentioned here out of curiosity to see what I may have missed, and retraced the steps to have my computer get the authorization to unbrick the phone. To my surprise, the final step binding my computer to authorization to flash the phone allowed me to do just that. I have permission. There was no e-mail with the code sent (as was mentioned in the steps of the procedure in the link above), and I have no idea how long this permission had been granted. I also have no idea how Xiaomi sent permission to my computer without me knowing about it. In any event, I sent the phone off too soon, obviously, and now it is lost somewhere. For those who have a bricked RN 8 Pro, the link seems a best option to flash with Miflash with a wait time for authorization, and it may not be given by e-mail, but done right on the phone without your knowledge. H'mmm ... It has been a convoluted journey through a successful root and then a bricked Redmi Note 8 Pro. Hope to get the phone back, eventually, or a new one from the insurance. Will let you know .... Hey, thanks for reading this story.
Click to expand...
Click to collapse
Thanks for sharing. I usually go full on guns blazing root mode the second i get a new phone, even in muddy waters but this time around i'm going to be patient for a while until some good news surfaces. I can't afford to lose this phone at the moment. I have your post to thank for that.
Well, my error of the address of the repair shop on the package contributed completely to the disappearance of this phone in the Canada Post system. There should be little problem in correcting it, however the service says they will "try" to deliver it by Jan. 2, 2020. I can give Canada Post the correct address, however, I cannot find any web page to do so - keep going in circles. The phone number puts me in a long queue. Seemingly I can't ask to have it returned now, the rules of delivery must be followed. Will keep trying. Oh my, so far away from Backup/Restore and bricking ...
Helhound0 said:
Thanks for sharing. I usually go full on guns blazing root mode the second i get a new phone, even in muddy waters but this time around i'm going to be patient for a while until some good news surfaces. I can't afford to lose this phone at the moment. I have your post to thank for that.
Click to expand...
Click to collapse
Spoke (Wrote) too soon. This approach has been tried and failed for the "deep flash" requirement. It seems what is needed is an "Authorized Service Account". Back to square one ... Thanks for reading this.
Greetings,
General
I've been all over the Internet trying to gain access to more information about how to repair my LG G4. Well... Let's start from the beginning.
Story
I have an LG G4, it's old and I've had it for over 4-5 years now... I can't exactly remember how long I had it for. It still works, just needs a new battery and cable (cats chewed the cable and batteries don't last when you forget to disconnect them from the device, leave it plugged in for weeks and let it completely die for longer then a week).
I recently saw a video about the Pine phone and the fact that it was able to run a linux mobile distribution and when I looked into installing a custom OS into LG G4, it was possible... If I manually ported it myself.
I actually got fairly far using my Xubuntu system with configuring and compiling, the trouble I ran into was that I couldn't root or fastboot my device.
So, now here's where the problem began, I have a LG G4 factory reset and when I load up the Recovery mode, it brings up the android guy with their chest open and an exclamation mark in a yellow triangle, no message. After attempting to boot into recovery mode, I wait a little while and the phone automatically resets back to normal. When I use ADB to force the phone into fast boot, it skips it and starts the phone normally.
Now I'm on a mission to find a way to either fix the boot or flash the firmware (in hopes that it fixes the boot/recovery).
I have already tried:
Installing LGFlashTool
Versions, 2.0.1.6, 2.0.1.9, Year: 2014 and 2.0.2.5. Other than year 2014, the other ones were installed from LGFlashTool.com
Since Xubuntu can't run these files properly, I just ran them on my wife's Windows computer
I installed the LG Mobile Drivers and LGFlashTool had registered that it was the correct DLL but, it didn't seem to find the phone
Year 2014 LGFlashTool had found the phone but, I may have had the incorrect kdz file.
The Flash starts and the phone goes to firmware update, but the phone stops at zero and sits there while the program crashes saying that there was an error (in which no means to read, understand or locate the description of this error) and to try again by unplugging and removing the battery.
This version was downloaded from xda-developers.com
Conclusion
Once I can get into fastboot, I'll be able to root my phone and attempt to install the mobile OS I have ready.
Otherwise, I think I might be able to install a microSD card with the OS but, I don't think that will work if I can't get into the option to boot from a separate location (I believe that's called fastboot). But, then again... I think the phone needs to be rooted first... Then that brings me to the previous issue.
Details and Information
The phone details (as far as I see) are:
When I remove the battery I can see:
FCC ID: ZMFH810
IC ID: 2703C-H812
Model Number: LG-H812
I'm not exactly sure what KDZ file I got but the name is: PR H810PR10a_02.kdz, I also have the _04.kdz
I'm using H815 as my compile for the mobile OS, I may switch to H810 when I get back to that point.
Useless information: I still have the original leather backing... Removed from the phone because I didn't like it. If I find it, I can ship it to someone.
That's about it... I am very terrible about research and using Google properly (I have no idea why, I think it's a terrible flaw to have but, I have it). So, if you find the solution by typing words I didn't use or finding a similar post, I am very sorry. Hope I have everything posted here to help solve the issue, linking to posts that can resolve the issue or posting questions on what I might be missing will help.
Thanks in advance for the support of this community,
Lilrock
Lilrock said:
Greetings,
General
I've been all over the Internet trying to gain access to more information about how to repair my LG G4. Well... Let's start from the beginning.
Story
I have an LG G4, it's old and I've had it for over 4-5 years now... I can't exactly remember how long I had it for. It still works, just needs a new battery and cable (cats chewed the cable and batteries don't last when you forget to disconnect them from the device, leave it plugged in for weeks and let it completely die for longer then a week).
I recently saw a video about the Pine phone and the fact that it was able to run a linux mobile distribution and when I looked into installing a custom OS into LG G4, it was possible... If I manually ported it myself.
I actually got fairly far using my Xubuntu system with configuring and compiling, the trouble I ran into was that I couldn't root or fastboot my device.
So, now here's where the problem began, I have a LG G4 factory reset and when I load up the Recovery mode, it brings up the android guy with their chest open and an exclamation mark in a yellow triangle, no message. After attempting to boot into recovery mode, I wait a little while and the phone automatically resets back to normal. When I use ADB to force the phone into fast boot, it skips it and starts the phone normally.
Now I'm on a mission to find a way to either fix the boot or flash the firmware (in hopes that it fixes the boot/recovery).
I have already tried:
Installing LGFlashTool
Versions, 2.0.1.6, 2.0.1.9, Year: 2014 and 2.0.2.5. Other than year 2014, the other ones were installed from LGFlashTool.com
Since Xubuntu can't run these files properly, I just ran them on my wife's Windows computer
I installed the LG Mobile Drivers and LGFlashTool had registered that it was the correct DLL but, it didn't seem to find the phone
Year 2014 LGFlashTool had found the phone but, I may have had the incorrect kdz file.
The Flash starts and the phone goes to firmware update, but the phone stops at zero and sits there while the program crashes saying that there was an error (in which no means to read, understand or locate the description of this error) and to try again by unplugging and removing the battery.
This version was downloaded from xda-developers.com
Conclusion
Once I can get into fastboot, I'll be able to root my phone and attempt to install the mobile OS I have ready.
Otherwise, I think I might be able to install a microSD card with the OS but, I don't think that will work if I can't get into the option to boot from a separate location (I believe that's called fastboot). But, then again... I think the phone needs to be rooted first... Then that brings me to the previous issue.
Details and Information
The phone details (as far as I see) are:
When I remove the battery I can see:
FCC ID: ZMFH810
IC ID: 2703C-H812
Model Number: LG-H812
I'm not exactly sure what KDZ file I got but the name is: PR H810PR10a_02.kdz, I also have the _04.kdz
I'm using H815 as my compile for the mobile OS, I may switch to H810 when I get back to that point.
Useless information: I still have the original leather backing... Removed from the phone because I didn't like it. If I find it, I can ship it to someone.
That's about it... I am very terrible about research and using Google properly (I have no idea why, I think it's a terrible flaw to have but, I have it). So, if you find the solution by typing words I didn't use or finding a similar post, I am very sorry. Hope I have everything posted here to help solve the issue, linking to posts that can resolve the issue or posting questions on what I might be missing will help.
Thanks in advance for the support of this community,
Lilrock
Click to expand...
Click to collapse
Well first of all you need to unlock your phone. H812 can't be unlocked officially though. Check my sig for the only unofficial one. Once unlocked you can flash custom ROMs but first of all you should read about ARB (antirollback) also in my sig and ensure you understand the risks all this brings. Gl.
steadfasterX said:
Well first of all you need to unlock your phone. H812 can't be unlocked officially though. Check my sig for the only unofficial one. Once unlocked you can flash custom ROMs but first of all you should read about ARB (antirollback) also in my sig and ensure you understand the risks all this brings. Gl.
Click to expand...
Click to collapse
Thanks for the positive feedback, I will attempt to fix my phone with your solution. This phone is technically almost garbage and when I fully update the phone, it runs like trash. So, if I can install a custom ROM, it may run a little better or have the tools I would personally like in a phone.
I'll let you know the details of my attempt,
Lilrock
You might be able to use:
GitHub - Lekensteyn/lglaf: LG Download Mode utility and documentation
LG Download Mode utility and documentation. Contribute to Lekensteyn/lglaf development by creating an account on GitHub.
github.com
It is more reliable then the factory tools when it works.
SkewedZeppelin said:
You might be able to use:
GitHub - Lekensteyn/lglaf: LG Download Mode utility and documentation
LG Download Mode utility and documentation. Contribute to Lekensteyn/lglaf development by creating an account on GitHub.
github.com
It is more reliable then the factory tools when it works.
Click to expand...
Click to collapse
Which is included in mAid (https://maid.binbash.rocks).. ... Even with a UI...
Thank you very much with your support. I was able to unlock, bootloader and install the image installer.
I'm on the verge of compiling and installing Ubuntu Touch on my LG G4 H812.
Hope you guys proceed with everything you're doing right!
Edit 3: USIC, after further investigation, has confirmed the tablet was actually one lost in shipment and compensated for by insurance, the sale was legitimate (not a stolen device) and they unenrolled it from KNOX before I could ask if they would do so. So, overall a satisfactory outcome, even if the tech part of me wanted to find a way to defeat a technical challenge.
EDIT 2: The device may not be stolen after all, seller has given a plausible explanation. Withholding further judgement until more information comes in.
EDIT: I was originally thinking of 'USIC' as a subsystem of Android or KNOX. A user on Reddit suggested I reach out to the company USIC and see if the tablet was stolen from them. I did. It was. Will be getting the tablet back into their hands and pursuing a refund from the eBay seller. Will leave this post up in case anyone has a use for the technical rabbit hole I went down.
Backstory: Found a good deal on a new Galaxy Tab Active Pro from an IT liquidator company on eBay, it was listed as locked and price reduced because of that. I thought along the lines of 'hardware access is total access' and figured I would be able to wipe / reset it.
Device arrived today, the crippleware (MDM or administration software actually, but I'm feeling ornery at it) installed is Soti Mobicontrol. I can boot into the OS but a bunch of stuff is disabled. First I initiated a factory reset from Settings - it resets and during setup lists "This tablet is protected by Knox Cloud Service. To continue setup, connect to a Wi-Fi or mobile network." From there it states "Your admin can monitor and manage settings".... a bunch of stuff ending with "USIC will manage and monitor this device using the following app: MobiControl" with the only option being 'Accept & continue'.
Tried another factory reset through the boot menu (hold down vol down and power to reboot followed by hold down vol up) - same result.
Found and downloaded the same version firmware the tablet currently has: SM-T540_XAR_T540XXU2BTG5_fac.zip where XAR appears to be the US/Canada region code and T540XXU2BTG5 is the exact version of firmware the tablet currently has installed (verified by going to 'Software information' in settings).
Downloaded latest version of Odin (3.13), booted the tablet into the correct mode and flashed clean firmware (just the AP firmware) to the device. Went through first install sequence to no change in behavior, still installs Soti Mobicontrol as a device admin.
I've looked into maybe getting TWRP installed (so I can delete KNOX from TWRP file browser perhaps as demonstrated here:
) but as far as I can tell there isn't a build for this version of the tablet - closest I can get is for the SM-T547 XDA forum post on it here: https://forum.xda-developers.com/t/...alaxy-tab-active-pro-10-1-snapdragon.4284347/. Also not sure how I would get it installed since I can't enter dev options in the tablet (tapping on Build number, even in safe mode, results in a popup: Action not allowed This action is disabled by MobiControl. Contact your organization's administrator to learn more.)
I've found someone on YouTube (
) who removed the software just by intentionally entering a wrong password until a factory reset tripped - but I am already able to use the factory reset option and the software comes back. I'm thinking Soti Mobicontrol and the KNOX service are separate issues and in this person's example he was only dealing with Soti and not KNOX Enrollment.
Next I found this gentleman on Youtube:
who specifically mentions using the 'Nand erase' option in Odin along with flashing all files in the stock firmware to remove management software. Tried that, no luck. Same as each install I get the message 'Updating... Updating Knox Enrollment Service... X%' after being required to connect to wifi to continue setup with the 'Skip' option greyed out.
So, that's where I am right now with it, and I refuse to give up. Ideas?
@studentoflife don't know this device but might be a chance to flash the multiple part stock ROM you can get via Samfirm_reborn.
bmwdroid said:
@studentoflife don't know this device but might be a chance to flash the multiple part stock ROM you can get via Samfirm_reborn.
Click to expand...
Click to collapse
I am unfamiliar with Samfirm_reborn. What is this project? I can't seem to find much in the way of descriptive notes.
Edit: apologies, did some googling and now know what Samfirm_reborn is. I'm pretty sure I've already flashed all parts of the stock ROM - downloaded the T540XXU2BTG5 version firmware and flashed the BL, AP and CSC images. No CP image given this version of the device does not have a cellular modem.
Hm. I suddenly wonder what will happen if I reflash with the earliest version instead of the current one. I know I don't want to update it to the latest firmware in case that applies some security patch that can't be downgraded and locks out some workaround I haven't found yet, but downgrading... maybe.
I have a similar tablet with mobicontrol. I can't unlock OEM so all the methods of flashing new firmware I tried, failed. Have you had any luck since your last post?