Dear XDA community
I recently bought a LG G4 from an online retailer. According to their website they said it was a UK model, which according to the back of the phone beneath the battery it is: LGH815. But then after booting the phone the ROM being used was: LGH815T. Then I typed in the IMEI number and found out it was a: Verizon US model??
Basically I am having trouble identifying my model. The phone apparently came unlocked and rooted, but the person who sent it must have done something wrong because when I flashed a TWRP recovery image to the phone it comes up saying: secure boot error code: 1002.
The good thing is, is that I can boot into the device and still operate it as per usual. But what I want to do is bring the recovery back to normal. I was searching around and apparently there are some KDZ files that can be used just to flash the recovery? Is this correct? If so could you assist me in what I have to do to fix my issue which is: secure boot error 1002.
I would really appreciate any help regarding the matter. :crying:
Tried posting photos, but forum would not let me, all they showed was the model numbers.
Jesse
Higsley said:
Dear XDA community
I recently bought a LG G4 from an online retailer. According to their website they said it was a UK model, which according to the back of the phone beneath the battery it is: LGH815. But then after booting the phone the ROM being used was: LGH815T. Then I typed in the IMEI number and found out it was a: Verizon US model??
Basically I am having trouble identifying my model. The phone apparently came unlocked and rooted, but the person who sent it must have done something wrong because when I flashed a TWRP recovery image to the phone it comes up saying: secure boot error code: 1002.
The good thing is, is that I can boot into the device and still operate it as per usual. But what I want to do is bring the recovery back to normal. I was searching around and apparently there are some KDZ files that can be used just to flash the recovery? Is this correct? If so could you assist me in what I have to do to fix my issue which is: secure boot error 1002.
I would really appreciate any help regarding the matter. :crying:
Tried posting photos, but forum would not let me, all they showed was the model numbers.
Jesse
Click to expand...
Click to collapse
On the play store there is this https://play.google.com/store/apps/details?id=com.peamoon.phoneproductioninfo
This may help you I'd the device it it is a h815t you may not have the ability to unlock the boot loader......
Also try this *#546386#815#*.
This may also help.......
https://forum.xda-developers.com/tmobile-g4/help/twrp-installation-secure-boot-error-1003-t3168385
Use LGUP-NEW to install/flash ...
Higsley said:
Dear XDA community
I recently bought a LG G4 from an online retailer. According to their website they said it was a UK model, which according to the back of the phone beneath the battery it is: LGH815. But then after booting the phone the ROM being used was: LGH815T. Then I typed in the IMEI number and found out it was a: Verizon US model??
Basically I am having trouble identifying my model. The phone apparently came unlocked and rooted, but the person who sent it must have done something wrong because when I flashed a TWRP recovery image to the phone it comes up saying: secure boot error code: 1002.
The good thing is, is that I can boot into the device and still operate it as per usual. But what I want to do is bring the recovery back to normal. I was searching around and apparently there are some KDZ files that can be used just to flash the recovery? Is this correct? If so could you assist me in what I have to do to fix my issue which is: secure boot error 1002.
I would really appreciate any help regarding the matter. :crying:
Tried posting photos, but forum would not let me, all they showed was the model numbers.
Jesse
Click to expand...
Click to collapse
Use LGUP-NEW ( https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803 ) to install/flash ... the appropriate stock KDZ for your specific model once you ascertain it (LGUP - NEW may recognize your model and you can use that info to find the right KDZ). You will have to re-root the phone if you still wish to have root.
If you do root, suggest you might want to check out steadfasterX's [LOCKED][G4][TWRP][UNOFFICIAL] TWRP-in-FIsH for all locked G4 devices at: https://forum.xda-developers.com/g4/development/locked-twrpinfish-locked-g4-devices-t3573048
It has been tested on locked devices AND unlocked devices. Version 3 Beta 4 and 5 seem very stable and the links are available in the later posts on the site. It works like a charm and has been tested on a quite a number of devices now.
Addendum: I'm wondering if the online retailer may have meant it was carrier unlocked (i.e., so you could use other service provider's sim cards), not bootloader unlocked? That could account for the secure boot error getting TWRP to load.
S.
NB: Don't forget to click the Thanks button when members try to answer your questions and/or solve issues you have encountered.
I had bought a GS3 a few years back but never used it. Had some carrier issues as all the SIMs here in India were not supported. Ever since I bricked my Moto E, I decided to start using it again.
I realised that the sticker on the rear of my phone says it's I9300 (International Version) of the S3 but the firmware and bootloader in downloader mode shows it as SGH-747 which I believe is the d2att device. I decided to try and flash the I9300 bootloader and flash the I9300 firmware using Odin to sort my carrier network issues (modem difference issues maybe). Ended up causing a hard brick on my phone didn't turn on properly.
I used the bootloader debrick image from: https://androidfilehost.com/?fid=23501681358549813 and was able to boot my phone into download mode. I assume it's the I747 image which helped me turned on my phone although the battery and rear panel says it's I9300. Nevertheless, I downloaded the 4.0.4 firmware from AndroidMTK.com to flash on my bootloader to completely debrick the device. Downloaded the I747 as the debrick I downloaded earlier bootloader is I747 one.
I tried flashing the firmware and get the below error:
Code:
WARRANTY BIT: 1
BOOTLOADER AP SWREV: 3
SW REV CHECK FAIL: Fused 3 > Binary 0
Is my bootloader a Kitkat Bootloader? Am I flashing the wrong firmware? Should I flash the 4.4.2 firmware and see if it works? Would really appreciate if anyone could guide me here. I really want to unbrick my phone.
I can access my TWRP by using the debrick image from a SD Card. I tried booting into TWRP and Flashing CM 12.1, Lineage 14.1 and Slim 6. I have previously used these three roms on the device. Now, they won't boot after getting installed. I'm stuck at bootlogo when rebooting. Would appreciate any help.
Can anyone help out with this?
Are you able to determine the model # with the phone in download mode?
Since there is mention of "warranty bit", the phone must be running a 4.3 or newer bootloader which cannot be downgraded.
AT&T never released a full Odin-flashable firmware after 4.1.1.
audit13 said:
Are you able to determine the model # with the phone in download mode?
Since there is mention of "warranty bit", the phone must be running a 4.3 or newer bootloader which cannot be downgraded.
AT&T never released a full Odin-flashable firmware after 4.1.1.
Click to expand...
Click to collapse
The phone model is the SGH-747. It's the AT&T variant. Which firmware should I flash then?
Flash this: https://forum.xda-developers.com/ga...ile-sgh-i747ucufne4v4-4-2attall-odin-t3305899
I apologize in advance for the new/dumb questions.
My roomate bought a Samsung Galaxy S8+ a few months ago. It was unlocked. It's on the T-Mobile network.
I have a screenshot from the phone when it booted into recovery mode.
Says:
Android Recovery
samsung/dream2qlteue/dream2qlteue
7.0/NRD90M/G955U1UES2AQL1
Long story short:
Phone got wet. Sent to a cell phone repair place, (bought an offiical T-Mobile branded S8+ in the meantime), they fixed the phone and tested as best they could (but they didn't have SIM, etc.)
Anyway, got the phone back and it wanted to do a firmware upgrade as the new rollout is happening. Phone updated, but now it won't see 5Ghz WiFi.
I can't seem to figure out how to back-rev the firmware (it could be damaged phone, due to the water, but the 2Ghz WiFi works fine).
Anyway, boot into Recovery and it says:
7.0/NRD90M/G955USQS2BRB1
Down further, I notice in the boot stuff it'll say:
#MANUAL MODE v1.0.0#
-- Appling Multi-CSC...
blah blah
Applied the CSC-code: TMB
Successfuly applied multi-CSC
However, if I boot into download mode (Power, Vol Down, Bixby) it'll say the carrier is: XAA
I have the G955U1UES2AQL1 firmware for:
TMB
CSC
and
XAA
downloaded
Odin 3.12.10
But it won't apply the firmware as it'll give the model mismatch error
Did the latest firmware change the bootloader?
Again, sorry for the stupid questions, it's been a while since I've hacked a phone and stuff.
Thanks!
What combo file did you use? I have same model G955U1UES2AQL1 and I flashed G955USQU2AQK2 and get same error when ai try to flash back.
Disclaimer: I am not responsible for any bricks/ issues you may encounter following this guide. Although, I will do my best to try to help you if something were to go wrong.
MAKE SURE OEM UNLOCK IS ENABLED UNDER DEV SETTINGS BEFORE YOU DO ANYTHING BELOW
Update 2: 3/11/2021 : I see maybe deleting the .ta files may help avoid soft bricking, feel free to try it I have not personally tested yet to see if it works.
Update#3 3/13/2021 : If you are following this guide recently make sure you update to Android 11 first! Do not do any updates after the first one to Android 11! Then the flashing should work just fine. Tested and verified this on Taiwan XQ-AT52 to 51 firmware
Hello, I've managed to successfully flash AT51 firmware on my AT52 without issue using Newflasher.
Step 1 download = the US firmware/ whatever region is needed for you and new flasher/ the sony xperia drivers needed to flash the firmware to your device. Extract it to your desktop. Install the Xperia driver from newflasher if you need to/ haven't yet. Newflasher needs to be extracted into the same folder where the firmware files are that you downloaded from Xperifirm. This step is crucial!
Step 2 : Power off your Xperia and put it in flash mode by pressing down on the volume and connecting it to your PC via usb. (Do not use the USB C cable that came with the phone use a different one if you have one) You'll know it is in flashmode if the notification LED turned green and the screen remains off.
Step 3 : Open newflasher.exe
Step 4: type n then press enter
Step 5: type n again and press enter
Step 6 : This is when you should get to the flashing stage. Press Y and enter to everything you are prompted to. type y for yes to. This for me resulted in a successful conversion over to AT51.
Step 7: Once everything is done and it says you are safe to disconnect your phone please do so and then press and hold your power button until the phone boots up.
At this point you should have a fully working AT51 firmware!
Bare with me as I"m working on getting developer access for androidfilehost and will upload the files asap. In the meantime you can download newflasher and the firmware files yourself using Xperifirm if you don't wanna wait for me to upload.
Xperifirm: https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
Newflasher: https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
Can you please help? I followed and i got a corrupted message and power off in 5 second.
I tried xperia companion, failed.
I tried to reflash newflasher with original firmware again, failed.
Please help.
tiunilohmu said:
Can you please help? I followed and i got a corrupted message and power off in 5 second.
I tried xperia companion, failed.
I tried to reflash newflasher with original firmware again, failed.
Please help.
Click to expand...
Click to collapse
Can you tell me the model of your xperia phone? If you can still get it into flash mode when the notification LED turns green you may still be able to recover it.
Hi, I finally managed to restore it. I have to remove all the ta files to flash it, then it booted up.
Thanks for your respond.
my device is corrupted please help
blegs said:
my device is corrupted please help
Click to expand...
Click to collapse
what did you do to corrupt it?
Lennyuk said:
what did you do to corrupt it?
Click to expand...
Click to collapse
I have using newflasher
After using 3 time xperia companion it work normal again
Hi, I didn't find this thread until after I made an attempt at flashing the device. I followed the instructions from the link below and ended up with the device saying it's corrupted.
https://www.xperiablog.net/2018/01/...-firmware-for-xperia-xz-premium-xz1-and-more/
I tried redownloading newflasher as well as redownloading the firmware I wanted as well as a new cable and that did not help. I reflashed it with this procedure listed above and it did not help.
Xperia companion won't let me do anything because it says the device is locked even though the device was not locked and there doesn't appear to be a way to unlock it. edited to add that I did get xperia companion to repair it successfully
edit again to advise I succeeded only after doing n and enter a third time then hitting y and enter for the final flashing step and that was successful in getting it updated correctly
Would it work to unlock my phone
Thanks for the guide!
Can I ask few questions please?
First is do I need to have my bootloader unlocked? I enabled OEM unlock setting in developer settings but that is only one thing I did.
And the second one is could this flash unlock my phone?
I am in this situation where my AT51 won't work with other sims except for Vodafone. UK.
I stayed with them for 30 days, (required time frame to get your phone unlocked) requested unlock code and it has been more than 10 working days but still have not received the code.
So today I did some searching online and found the service code to check if my phone is locked to a network and to my surprise it says it's not. So I am guessing that they have limited my phone to using only their sim through some other means andnot buy locking my modem. But this is ofc just a guess.
I kept chatting with the customer support and he keeps saying wait for the code which I do not believe is going to come, they have to unlock it on their end. But I am not sure about that. I don't think they are sure either..
Basically I'll wait fem more days maybe they will unlock it but if they won't when I am thinking maybe my modem is not locked and I could unlock it by flashing different ROM?
Or do you think this won't work?
Sorry for a rambling post. Looking forward to your reply. Thanks!
Mazvydelis said:
Thanks for the guide!
Can I ask few questions please?
First is do I need to have my bootloader unlocked? I enabled OEM unlock setting in developer settings but that is only one thing I did.
And the second one is could this flash unlock my phone?
I am in this situation where my AT51 won't work with other sims except for Vodafone. UK.
I stayed with them for 30 days, (required time frame to get your phone unlocked) requested unlock code and it has been more than 10 working days but still have not received the code.
So today I did some searching online and found the service code to check if my phone is locked to a network and to my surprise it says it's not. So I am guessing that they have limited my phone to using only their sim through some other means andnot buy locking my modem. But this is ofc just a guess.
I kept chatting with the customer support and he keeps saying wait for the code which I do not believe is going to come, they have to unlock it on their end. But I am not sure about that. I don't think they are sure either..
Basically I'll wait fem more days maybe they will unlock it but if they won't when I am thinking maybe my modem is not locked and I could unlock it by flashing different ROM?
Or do you think this won't work?
Sorry for a rambling post. Looking forward to your reply. Thanks!
Click to expand...
Click to collapse
You do not need the bootloader unlocked as you are flashing official firmware.
Anyone know if you can flash a XQ-AT52 to a XQ-AT51 and then back to the XQ-AT52 firmware?
Sent from my XQ-AT52 using Tapatalk
I know this thread is a few months old at this point but I'm really struggling to flash to XQ-AT51. I've successfully flashed from XQ-AT52 Hong Kong (my original firmware) to the Taiwan version which is slightly better because of the messaging compatibility but I really want to get the US version. I have tried at least 20 times over the course of a full day and I have not been able to flash the US firmware without getting an error saying "Your device is corrupt It can't be trusted and will not boot" every time. I have repaired it back to the Hong Kong firmware (back when that was the one I had) and to the Taiwan version once I had that installed. But I have never gotten the US firmware to take without the "Device is corrupt" error.
My phone is the Sony xperia 1 mark 2 running the then default XQ-AT52 Hong Kong, and now running the default XQ-AT52 Taiwan. I've been trying to flash to XQ-AT51 US. I've been using newflasher v39 and the US firmware downloaded for xperifirm v 5.5.0.
So I was able to flash from the hong kong version to the Taiwan version and back with no issues at all. But I'm still unable to flash to the US version without the "Your device is corrupt It can't be trusted and will not boot" error that seems to happen every single time I try to install the US firmware.
Can someone make me a favor and can upload the latest ftf of Android 10 for the Xperia 1ii Single SIM?
ProjectBlitz said:
So I was able to flash from the hong kong version to the Taiwan version and back with no issues at all. But I'm still unable to flash to the US version without the "Your device is corrupt It can't be trusted and will not boot" error that seems to happen every single time I try to install the US firmware.
Click to expand...
Click to collapse
The 1 II has downgrade protection, so as long as the firmware version of the US version isn't the same or newer than the highest version you've ever used you're gonna get the corruption error.
What you could try is flashing the newer EU version and then flashing only the older US customisation image. That's what I did for a while since US firmware was older than EU firmware, and it worked. Not sure if it'll work with Android 11.
ProjectBlitz said:
I know this thread is a few months old at this point but I'm really struggling to flash to XQ-AT51. I've successfully flashed from XQ-AT52 Hong Kong (my original firmware) to the Taiwan version which is slightly better because of the messaging compatibility but I really want to get the US version. I have tried at least 20 times over the course of a full day and I have not been able to flash the US firmware without getting an error saying "Your device is corrupt It can't be trusted and will not boot" every time. I have repaired it back to the Hong Kong firmware (back when that was the one I had) and to the Taiwan version once I had that installed. But I have never gotten the US firmware to take without the "Device is corrupt" error.
My phone is the Sony xperia 1 mark 2 running the then default XQ-AT52 Hong Kong, and now running the default XQ-AT52 Taiwan. I've been trying to flash to XQ-AT51 US. I've been using newflasher v39 and the US firmware downloaded for xperifirm v 5.5.0.
Click to expand...
Click to collapse
im in the us and was looking to the 256gb version (i think its taiwan). is the hong kong or taiwan version missing anything? or is the only reason to flash to US to get better coverage with us carriers?
GreeleyXda said:
im in the us and was looking to the 256gb version (i think its taiwan). is the hong kong or taiwan version missing anything? or is the only reason to flash to US to get better coverage with us carriers?
Click to expand...
Click to collapse
It's for better coverage and for VoLTE and Wi-Fi calling support. Also if you get a HK one with Android 11 you will be unable to flash the US firmware, because it is still on Android 10; and the phone has anti-rollback protection.
it arrived on 10 still, but its bugging me to update.
THISISINSANE said:
It's for better coverage and for VoLTE and Wi-Fi calling support. Also if you get a HK one with Android 11 you will be unable to flash the US firmware, because it is still on Android 10; and the phone has anti-rollback protection.
Click to expand...
Click to collapse
This isn't the case now since the US models have Android 11 too now
Can anyone confirm that this process has to be done using USB 2.x? I've read in a separate post that newflasher isn't compatible with USB 3.x, which is currently what all my computer use. Also, should I be using the newest version newflasher?
EDIT: Tried on USB 2.0 and it worked perfectly.
I feel like I've done a big door.
I work in a cell repair shop and we had an ATT unlocked S20 FE that came in and I liked it so I bought it.
Long story short. I did some reading that you can install the XAA software using patched Odin. This was essential because I'm on Tmobile and didnt get 5G on the ATT firmware.
Easy enough. The device now has 5G access on Tmobile, and identifies itself as SM-G781U1/DS in settings.
The issue I'm facing is now unlocking the bootloader. The XAA firmware doesn't have the option and I'm unable to flash back to ATT firmware without (auth) fail errors in Odin and 'Secure boot check fail: PIT' on download mode.
Here's what I've tried that's failed so far:
- show option using time/date change
- software updating (I do receive OTA)
- flashing stock ATT firmware
- flashing stock TMB firmware
- Fastboot oem unlock (command not found)
- fastboot getvar unlocked (unlocked: no)
I'm about out of ideas, could use some guidance on where to begin looking next, I really like the power of this phone and wanna see what custom roms bring.
Device stats:
Galaxy S20FE SM-G781U (with U1 XAA flash)
CSC: ATT
Build: G781U1UESAGWC7
Service provider info:
G781U1_OYM_TMB_13_0011
TMB/TMB/ATT
Android 13, One UI 5.1
To be honest the custom rom screne for this phone is not so great yet. I imagine once the official support ends we will be getting some well developed custom roms.
As for the bootloader unlock issue, try using smartswitch to restore stock firmware, or try changing only the CSC if the firmware is multi-csc, the oem unlock option might reapper.
What kind of patched odin did you use to flash the XAA firmware? stock odin should be able to flash it too. As far as i am aware north american samsung phones do not offer oem unlock. The option probably dissapeared for good. There was etoken but since you are on android 13 i imagine the exploits have been already patched. You're basically stuck on XAA now. You can try using samkey to change the csc but i doubt that even that can help you oem unlock it.
hoptockets said:
I feel like I've done a big door.
I work in a cell repair shop and we had an ATT unlocked S20 FE that came in and I liked it so I bought it.
Long story short. I did some reading that you can install the XAA software using patched Odin. This was essential because I'm on Tmobile and didnt get 5G on the ATT firmware.
Easy enough. The device now has 5G access on Tmobile, and identifies itself as SM-G781U1/DS in settings.
The issue I'm facing is now unlocking the bootloader. The XAA firmware doesn't have the option and I'm unable to flash back to ATT firmware without (auth) fail errors in Odin and 'Secure boot check fail: PIT' on download mode.
Here's what I've tried that's failed so far:
- show option using time/date change
- software updating (I do receive OTA)
- flashing stock ATT firmware
- flashing stock TMB firmware
- Fastboot oem unlock (command not found)
- fastboot getvar unlocked (unlocked: no)
I'm about out of ideas, could use some guidance on where to begin looking next, I really like the power of this phone and wanna see what custom roms bring.
Device stats:
Galaxy S20FE SM-G781U (with U1 XAA flash)
CSC: ATT
Build: G781U1UESAGWC7
Service provider info:
G781U1_OYM_TMB_13_0011
TMB/TMB/ATT
Android 13, One UI 5.1
Click to expand...
Click to collapse
for some reason Samsung doesn't allow bootloader unlocks in the US anymore. if as a phone repair guy you have the means force older firmware onto the device then you could pay someone to get an unlock token on the DL from a contact of theirs.
downgrading isn't something we can do at all hence me mentioning you maybe having access to resources others don't.
if you could get it onto the very first firmware you'd have a chance, if you can't there's no chance.