I did a very very very stupid thing...
Hey,
Hundreds of times I did this with no problem. But when your head is away bad thing can happen.
I flashed RETUS 5.1 stock ROM over my XT1527 Latin American carrier (possibly Movistar Argentina) . Flash failed. As it turns out I completely forgot to UNLOCK BOOTLOADER first. So I get the code and try to unlock, but the damn ALLOW OEM UNLOCK setting is turned off.
So here I am with a dead phone and no way to boot back. I can only go to (stock) recovery buth nothing I do there really makes any difference. So far I've downloaded two Latin American stock ROM images with no success (Preflash validation failed). However I am concerned that even if I find the right ROM, it will not boot either because of the downgraded boot.
Any options, ideas? Im stuck....Thanks in advance!
Different reason but same problem...
Dang that sucks mate.
Rsd lite to get back to working phone
Sent from my XT1526 using XDA-Developers mobile app
dbx2r said:
I did a very very very stupid thing...
Hey,
Hundreds of times I did this with no problem. But when your head is away bad thing can happen.
I flashed RETUS 5.1 stock ROM over my XT1527 Latin American carrier (possibly Movistar Argentina) . Flash failed. As it turns out I completely forgot to UNLOCK BOOTLOADER first. So I get the code and try to unlock, but the damn ALLOW OEM UNLOCK setting is turned off.
So here I am with a dead phone and no way to boot back. I can only go to (stock) recovery buth nothing I do there really makes any difference. So far I've downloaded two Latin American stock ROM images with no success (Preflash validation failed). However I am concerned that even if I find the right ROM, it will not boot either because of the downgraded boot.
Any options, ideas? Im stuck....Thanks in advance!
Click to expand...
Click to collapse
If you can find someone with a working version of your phone, and in recovery push settings.db (I think) to the bricked phone and reboot into bootloader. then try OEM unlock
Or if you can find an official ROM for the device from Motorola, might be able to flash back to stock with the original firmware then try unlocking again.
sandix said:
If you can find someone with a working version of your phone, and in recovery push settings.db (I think) to the bricked phone and reboot into bootloader. then try OEM unlock
Or if you can find an official ROM for the device from Motorola, might be able to flash back to stock with the original firmware then try unlocking again.
Click to expand...
Click to collapse
I CAN get an identical phone to do whatever I wish with it. However the bricked phone has the stock recovery. Can I still push the file in that?
I have tried with several stock roms with no success. I can't seem to be able to get the correcto one. How do I figure out the correct CID and stuff? However my concern is that the correct stock firmware is XT1527_SURNIA_TEFLA-MSTCL_5.0.2_LXI22.50-53.8_cid12_subsidy-MOVSTLA_CFC and will not boot due to the bootloader being already updated to 5.1
same problem here with xt1528...
'Sup XDA,
I'm pretty new to this whole Flashing Thing going on.
My LG G5 is my first device where i flashed the Genysis Rom, TWRP and Root on.
Now i want to sell it to get myself a OnePlus 3.
Is there any way to completly get my LG G5 back to its Factory Mode?
Without TWRP, With Stock Firmware (even with the Vodafone Branding) and without the Text "Can't check for Device Corruption" on Startup?
Thanks and Greetings from Germany
~Panda
xPanda187 said:
'Sup XDA,
I'm pretty new to this whole Flashing Thing going on.
My LG G5 is my first device where i flashed the Genysis Rom, TWRP and Root on.
Now i want to sell it to get myself a OnePlus 3.
Is there any way to completly get my LG G5 back to its Factory Mode?
Without TWRP, With Stock Firmware (even with the Vodafone Branding) and without the Text "Can't check for Device Corruption" on Startup?
Thanks and Greetings from Germany
~Panda
Click to expand...
Click to collapse
Firstly you have to flash the LG Stock Firmware with LGUp, you can find it Here
Next thing to do is locking the bootloader, mind that this "lock" will only remove the startup message and lock the bootloader, it won't recover the warranty, you can find the method Here under FAQ
Hi guys,
I bough a used LG G5 back a couple of days because i have a lot of love for the LG G series. I got the phone after i had a quick look over the phone when i was with the seller and i was very happy about the external look of the phone so i bought it.
I had read that there is an official update for the LG G5 to Oreo so it was a big surprise when i realized that the one i got was still on 6.0.1. What i did was come back to the house, connect to the wifi and try to do a FOTA upgrade. No luck. It said that the phone was already at its latest update available. What i did then was to do a manual upgrade with LG Bridge. All went good and the phone was updated to 7.0. After the first reboot, i got the message "Current version is not available for user....". I didn't bother at the time because i thought that after a factory reset all would be ok. Well that didn't happen . I did notice something strange. The software version i had was referring to "EU" but now it says V20r-OPT2-SI. Perhaps the previous owner had the phone rooted and perhaps that version that it had was not the official EU.
Now the OS is full off bloatware and there isn't an update to Oreo available.
I want to:
- Find the appropriate OS version that my phone should have
- Get rid of the message that appears during the boot
- Get rid (if possible) from the bloatware when the correct OS is loaded
I want to use an official ROM with no root because of company regulations where i work so, rooting might be an issue. If i do have to root, i then have to unroot it again before use.
Because i have been away from the scene for a long time, please excuse my lack of information.
Regards,
If you don't mind loosing VoLTE support for the operators your rom was made for, just delete the /cust/ folder and you'll get rid of both error message and most of the bloatware.
tremalnaik said:
If you don't mind loosing VoLTE support for the operators your rom was made for, just delete the /cust/ folder and you'll get rid of both error message and most of the bloatware.
Click to expand...
Click to collapse
i am a noob, i didnt know this, thanks for the tip
tremalnaik said:
If you don't mind loosing VoLTE support for the operators your rom was made for, just delete the /cust/ folder and you'll get rid of both error message and most of the bloatware.
Click to expand...
Click to collapse
That is indeed a nice tip that i was not aware of but would it be possible to know if i am able to flash a rom carrier independent in order to be able to upgrade afterward to the Oreo? If so, how can i find out the version that i can flash without damaging the phone?
Thanx for the help so far.
You can flash whatever rom you want (of course an H850 one, never try to flash a H830 or H860 ROM on the H850!!!). If you want to upgrade to Oreo having an Open EU stock rom, follow these instructions: https://forum.xda-developers.com/lg-g5/development/stock-h850-30a-eu-rom-flashable-zips-t3850072
If you follow colsely the instructions and charge the phone before proceeding, there's virtually no risk of damage (avoid flashing form a desktop pc in a stormy night, of course).
Purchased a sim unlocked SM-T978U (Verizon Tab S7+ 5G) and am trying to flash the unlocked or Tmobile stock firmware to it. I've gotten "passed" flashes everything when flashing all of the files from the corresponding stock firmwares, but everything it boots back into the Verizon firmware. Any suggestions as to what I'm doing wrong that would cause this? I've probably flashed this thing 20 times at this point.
its a verizon tablet so thats normal.. u need to change csc is all
Thought that was part of flashing it with the patched version of Odin with a different CSC version of the firmware, but I've not done this before. Any suggestions or resources you can point to on how to do this? Thanks!
jmwfl2000 said:
Thought that was part of flashing it with the patched version of Odin with a different CSC version of the firmware, but I've not done this before. Any suggestions or resources you can point to on how to do this? Thanks!
Click to expand...
Click to collapse
patched odin only removes hash checks.. all the firmware has multi csc (all the usa csc) so simply flashing firmware doesnt change csc
Gotcha, so change the CSC first, then flash the matching firmware? What's the best method for changing the CSC on the S7+? This process? https://www.**********.com/how-to-change-csc-in-samsung-galaxy-phones/
Any suggestions on how to change the CSC? I've hit a wall and haven't been able to find a way to change it and then flash the desired firmware.
elliwigy said:
patched odin only removes hash checks.. all the firmware has multi csc (all the usa csc) so simply flashing firmware doesnt change csc
Click to expand...
Click to collapse
You need to flash with odin, wipe, then pop the other carrier sim in, on reboot it will boot with that carrier sw.
bs3pro said:
You need to flash with odin, wipe, then pop the other carrier sim in, on reboot it will boot with that carrier sw.
Click to expand...
Click to collapse
Ok, so SIM out, Odin flash with the TMB firmware. Then, what do you mean "wipe?" Is that just choosing the CSC file in Odin so that it resets all data, or some step after to wipe it?
So I tried again with these steps and had the same result, back into the Verizon firmware.
Removed Tmobile Sim
Odin flash TMB firmware
Tablet reboots automatically into VZW firmware
Then booted into recovery mode and performed a factory reset and cache wipe
Reinserted Sim and reboot
Tablet still boots into VZW firmware
I also tried this same process but with the unlocked "USC" firmware with the same results.
Am I supposed to somehow prevent the first boot after odin flash to perform the factory reset? I've tried that unsuccessfully but maybe I have the timing off or something.
jmwfl2000 said:
Ok, so SIM out, Odin flash with the TMB firmware. Then, what do you mean "wipe?" Is that just choosing the CSC file in Odin so that it resets all data, or some step after to wipe it?
Click to expand...
Click to collapse
jmwfl2000 said:
So I tried again with these steps and had the same result, back into the Verizon firmware.
Removed Tmobile Sim
Odin flash TMB firmware
Tablet reboots automatically into VZW firmware
Then booted into recovery mode and performed a factory reset and cache wipe
Reinserted Sim and reboot
Tablet still boots into VZW firmware
I also tried this same process but with the unlocked "USC" firmware with the same results.
Am I supposed to somehow prevent the first boot after odin flash to perform the factory reset? I've tried that unsuccessfully but maybe I have the timing off or something.
Click to expand...
Click to collapse
dunno wat ur flashing but all the firmware is the same.. theyre all multi csc.. so simply flashing different firmwares wont change csc lol
I don't know if this will help but on some samsung phones you can change the csc by opening the dailer and typing "*#272*IMEI number#"
edit: IMEI must me copied from the about tablet section in the settings. Press on the IMEI for a second and it will be copied to clipboard. Typing the IMEI will not likely not work.
After entering this in the dailer a menu pops up and you can select csc. Note this will usually factory reset the device.
Yes if you try this, please let me know if it works. I have the T878u 5g from Tmobile.
Any update on this? I purchased an SM-T978U (on Samsung website that is t-mobile S7+)
I expected it to not be carrier or network locked but it was locked to the t-mobile network.
Would love to flash an unlocked firmware but I can't find SM-T978U firmware, let alone U1 firmware...... I realize that flashing U1 firmware won't unlock the network but T-mobile support tells me the device can't possibly be truly carrier locked because the IMEI isn't even in their system. So I thought maybe the carrier lock is in their app tied to the system instead of the actual device??
Anyway has anyone found the firmware for these devices? Sammobile doesn't seem to list SM-T978 as a device
These devices don't have a dialer so entering the IMEI method mentioned above won't work unless there is a trick?
Guys, for cross flashing, you must factory reset from within the OS before you flash. the newer security measures will not allow the device to accept even a full flash if the device is activation locked to an account. that is likely why you are flashing and still getting the vzw stuff to come up.
@elliwigy , though the devices are all loaded with multiple csc's, and you can change them on demand (if you know how), that will not automatically load the carrier branded bloatware that comes with each firmware, and certain settings that may, or may not, be enabled or disabled by the carrier. An example being native video calling that the verizon firmware has and the unlocked firmware does not.
I almost always flash my Verizon devices with the U1 XAA unlocked software. Among other things, this lets me get security patches faster, as i get them when sammy releases them, not when vzw gets around to it. I say almost always because there are still a few devices, like my tab s6, that are vzw models with some minor hardware changes that prevent it. But in the case of my Tab S7+ and my Note20Ultra, they are both rocking U1 XAA firmware.
K3N422 said:
Guys, for cross flashing, you must factory reset from within the OS before you flash. the newer security measures will not allow the device to accept even a full flash if the device is activation locked to an account. that is likely why you are flashing and still getting the vzw stuff to come up.
@elliwigy , though the devices are all loaded with multiple csc's, and you can change them on demand (if you know how), that will not automatically load the carrier branded bloatware that comes with each firmware, and certain settings that may, or may not, be enabled or disabled by the carrier. An example being native video calling that the verizon firmware has and the unlocked firmware does not.
I almost always flash my Verizon devices with the U1 XAA unlocked software. Among other things, this lets me get security patches faster, as i get them when sammy releases them, not when vzw gets around to it. I say almost always because there are still a few devices, like my tab s6, that are vzw models with some minor hardware changes that prevent it. But in the case of my Tab S7+ and my Note20Ultra, they are both rocking U1 XAA firmware.
Click to expand...
Click to collapse
not sure y u tagged me lol.. i know hiw csc works.. in fact, in my last comment before this one you can see I clearly said just flashing firmware won't change the csc? seems like basically what you said but in a few words
K3N422 said:
Guys, for cross flashing, you must factory reset from within the OS before you flash. the newer security measures will not allow the device to accept even a full flash if the device is activation locked to an account. that is likely why you are flashing and still getting the vzw stuff to come up.
@elliwigy , though the devices are all loaded with multiple csc's, and you can change them on demand (if you know how), that will not automatically load the carrier branded bloatware that comes with each firmware, and certain settings that may, or may not, be enabled or disabled by the carrier. An example being native video calling that the verizon firmware has and the unlocked firmware does not.
I almost always flash my Verizon devices with the U1 XAA unlocked software. Among other things, this lets me get security patches faster, as i get them when sammy releases them, not when vzw gets around to it. I say almost always because there are still a few devices, like my tab s6, that are vzw models with some minor hardware changes that prevent it. But in the case of my Tab S7+ and my Note20Ultra, they are both rocking U1 XAA firmware.
Click to expand...
Click to collapse
Where is this U1 XAA firmware to download? Specifically for the SM-T978U?
RE: jmwfl2000 -I always untick the "Auto-Reboot" box when flashing new TWRP images to prevent stock recovery from being reapplied.After the first boot all should be well.
K3N422 said:
in the case of my Tab S7+ and my Note20Ultra, they are both rocking U1 XAA firmware.
Click to expand...
Click to collapse
I'm pretty stumped like OP. Where are you finding U1 XAA for Tab S7+? Doesn't seem to turn up anywhere. Would definitely appreciate it if you could provide a link. Thanks.
I tried resetting before flashing and unchecked the auto-reboot but mine still returns to Tmobile. I just want the call and text on other devices feature.
Edit: I go the feature to work without flashing a new firmware but I am still looking for U1 XAA for the tab if anyone found it.
jmwfl2000 said:
Purchased a sim unlocked SM-T978U (Verizon Tab S7+ 5G) and am trying to flash the unlocked or Tmobile stock firmware to it. I've gotten "passed" flashes everything when flashing all of the files from the corresponding stock firmwares, but everything it boots back into the Verizon firmware. Any suggestions as to what I'm doing wrong that would cause this? I've probably flashed this thing 20 times at this point.
Click to expand...
Click to collapse
I bought an unlocked Verizon Tab S7, probably same seller. Its brand new, stil has plastic on it. Are you wanting to unlock Tmobile 5G bands?
It may be related to this: https://forum.xda-developers.com/t/...etected-both-in-custom-rom-and-stock.4248919/
Every time I try to flash the EU firmware in my F1, SPFlashTools gives me an error, requiring to use Upgrade Firmware, which, among other things, would write the preloader, with the risk of permanently bricking the phone.
However:
I live in italy, EU, and bought the device from Amazon Italy, so, in theory, it should be using EU firmware
I'm 100% sure that my stock phone had the home button with a double circle, meaning an EU firmware: https://community.umidigi.com/forum.php?mod=viewthread&tid=18634&extra=&page=1
I never tried to flash anything with SPFlashTool before my first rom randomly broke and sent me to bootloop, therefore I never tested the og stock firmware with SPFlashTool
Could it be, therefore, that my og stock rom was EU, then the first round of modding "moved" to global firmware, and the device itself is actually able to boot from both?
If so, can anyone confirm that the EU phone is also able to boot a global firmware?