Hello,
Solution: https://forum.xda-developers.com/showpost.php?p=78923346&postcount=13
I have searched for this exact situation but all I got are questions on how to downgrade from a beta Pie build.
I have the official version OTA, but I have some big problems, thus I would like to downgrade back to Oreo.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A couple of problems I have:
1.Call recording no longer works.
2.My Mi Band 3 exhibits stranger behavior since Pie. When a call comes in and I answer the call, the band continues to vibrate for another ~5 seconds which is pretty annoying. Also, sometime the screen will not show an incoming call while the band will vibrate.
3. Menus are a mess and the large empty space on top of some applications like SMS just kills it for me.
So, the question is: is there any method I missed to revert to official Android Oreo from official Android Pie without rooting or loosing my warranty?
I am fine with loosing all data and settings.
Thank you
You can use Odin to flash Oreo. But yes, Wipe will be needed.
Изпратено от моят SM-G965F с помощта на Tapatalk
Leon said:
You can use Odin to flash Oreo. But yes, Wipe will be needed.
Изпратено от моят SM-G965F с помощта на Tapatalk
Click to expand...
Click to collapse
Where can you download the S9+ firmwares (oreo) for different carriers.
Well, try sammobile or samfirm.
Изпратено от моят SM-G965F с помощта на Tapatalk
Leon said:
Well, try sammobile or samfirm.
Изпратено от моят SM-G965F с помощта на Tapatalk
Click to expand...
Click to collapse
I see them all on sammobile except ATT. What am I missing.
Kind of new to this phone last one I rooted and played with was a S2 SGH-T989
It was a whole lot easier than this phone.
You don't have many choices. SamFirm will only allow you to download the latest firmware which is Pie, and most older Oreo firmwares cannot be flashed because your bootloader is now eFused to V2 and they are V1.
I'm about to try the same thing. Downloading the newet V2 firmware from sammobile (20 hour download lol) and hopefully it can be flashed.
Really hate how difficult rooting is these days.
Deepcuts said:
Hello,
I have searched for this exact situation but all I got are questions on how to downgrade from a beta Pie build.
I have the official version OTA, but I have some big problems, thus I would like to downgrade back to Oreo.
A couple of problems I have:
1.Call recording no longer works.
2.My Mi Band 3 exhibits stranger behavior since Pie. When a call comes in and I answer the call, the band continues to vibrate for another ~5 seconds which is pretty annoying. Also, sometime the screen will not show an incoming call while the band will vibrate.
3. Menus are a mess and the large empty space on top of some applications like SMS just kills it for me.
So, the question is: is there any method I missed to revert to official Android Oreo from official Android Pie without rooting or loosing my warranty?
I am fine with loosing all data and settings.
Thank you
Click to expand...
Click to collapse
I just downgraded my Samsung Galaxy S9+ (SM-G965U) from Pie to last official oreo and carrier unlocked it as well following this post https://forum.xda-developers.com/galaxy-s9-plus/how-to/sm-g965u-g965usqs3ari6-sm-g965u1-t3853429
But if you want to stay on carrier firmware, SamMobile will have it.
---------- Post added at 10:04 PM ---------- Previous post was at 10:00 PM ----------
What is the model number of your S9+? For example, SM-G965* with "*" being the last character of your model number? My was the "U" model. Not sure if it would work for other variants.
BLznFuN said:
I just downgraded my Samsung Galaxy S9+ (SM-G965U) from Pie to last official oreo and carrier unlocked it as well following this post https://forum.xda-developers.com/galaxy-s9-plus/how-to/sm-g965u-g965usqs3ari6-sm-g965u1-t3853429
But if you want to stay on carrier firmware, SamMobile will have it.
---------- Post added at 10:04 PM ---------- Previous post was at 10:00 PM ----------
What is the model number of your S9+? For example, SM-G965* with "*" being the last character of your model number? My was the "U" model. Not sure if it would work for other variants.
Click to expand...
Click to collapse
I have SM-G965F like shown in the image.
I have read through that topic and as far as I can see, even if I had SM-G965U I would loose warranty, because flashing would trip Knox.
Deepcuts said:
I have SM-G965F like shown in the image.
I have read through that topic and as far as I can see, even if I had SM-G965U I would loose warranty, because flashing would trip Knox.
Click to expand...
Click to collapse
Incorrect. I did not trip my Knox and I re-flashed 3 different times. Only way to trip knox is rooting your device or putting a different recovery on your device in attempt to root. The process shown in that post is not rooting. You're simply putting factory software back on. And since the bootloader is V3 for both oreo and pie I could downgrade. The longer I would wait, I risk the bootloader changing and getting firmware "locked" (would brick if I tried to downgrade) to where I can't downgrade.
Like you, my main reason for downgrading was call recording. Google completely removed the ability to record calls (including the API) and there is no foreseeable future that they will ever bring it back.
I have successfully downgraded to official Oreo.
Thank you .
Hello,
can you please explain how you did that?
Thank you.
Deepcuts said:
I have successfully downgraded to official Oreo.
Thank you .
Click to expand...
Click to collapse
Please tell us procedures please?
d_jaxx said:
Hello,
can you please explain how you did that?
Thank you.
Click to expand...
Click to collapse
It is pretty simple actually. I was afraid it was too complicated but it really isn't.
For example, for my SM-965F Samsung Galaxy S9+, the latest Android 8 Oreo is from December 2018 and the file would be named G965FXXS2BRL3
Found the file on https://androidfilehost.com/?fid=11410963190603878932 and downloaded it. Or search the site for your specific version.
Next downloaded Odin from https://odindownloader.com/download/odin3-v3-13-1
Decompress all downloaded files to one folder.
Backup everything you need because this method will wipe all data and settings.
Enable USB Debug in dev settings on your phone.
Ended up with Oreo official version. Knox did not trip. Warranty still intact.
Copy/Paste from other threads below:
Reboot to download mode:
Power off your Galaxy S9 Plus completely until it vibrates.
Press and hold the Volume Down + Bixby + Power buttons simultaneously. Release the buttons when you see the warning message.
Now just press Volume up button to continue.
Congratulations, you're now in download mode.
Connect your phone to your PC:
Start the patched Odin 3.13.1 that you downloaded from the provided link.
Plug the cord your phone came with into your phone and PC. Other cords may not work.
The Odin log will display a <ID:0/005> Added!! message once it connects.
Flash the firmware:
First, extract the compressed firmware to a folder on your PC.
In Odin, begin with the BL (bootloader) box, navigate to the firmware folder and select the file beginning with BL_.
Wait for each file to initialize and appear to the right of its corresponding box before attempting to proceed to the next step.
Now select the AP (Application Processor aka System) box, it should open the correct folder, then select the file beginning with AP_.
AP takes a while to initialize, don't worry.
Now select the CP (Core Processor aka modem) box, then select the file beginning with CP_.
Now select the CSC (Consumer Software Customization aka Carrier Settings) box, then select the file beginning with CSC_.
Optionally, select the userdata (User Data) box, then select the file beginning with USERDATA_.
Under Options, only two check boxes should be enabled: Auto Reboot and F. Reset Time. NOTHING ELSE.
Now, click start and wait for the magic.
Disconnect the cord when the phone reboots.
The phone should boot to recovery to automatically cleanup, then reboot again.
Remember to disable automatic system update and update check once back to Oreo
Thank you Deepcuts.
d_jaxx said:
Thank you Deepcuts.
Click to expand...
Click to collapse
its work???
umbash said:
its work???
Click to expand...
Click to collapse
One ? mark is enough. Never understood people using ???
Thanks buddy.
If you don't want to see the notice reminding you to update to Pie, you can search Software Update in APPS, then clear its data. That would clear the update notice.
I have a G965U sprint on android 9 pie.. i want downgrade to oreo? how do you do that? please tell me
bryanossiel said:
I have a G965U sprint on android 9 pie.. i want downgrade to oreo? how do you do that? please tell me
Click to expand...
Click to collapse
The process should be the same. You just obtain the necessary oreo firmware files for your phone and flash them accordingly with the patched odin...
Before you do check the following on your phone.
If the 5th character (starting at the end as number 1, count 5 characters to the left) of your baseband version on your phone right now has the number 4 you will not be able to downgrade.
That number represents the bootloader version. You can only flash bootloader versions equal too or higher then what is currently on your phone. Attempting to flash firmware with an older bootloader version will always fail.
scottusa2008 said:
If the 5th character (starting at the end as number 1, count 5 characters to the left) of your baseband version on your phone right now has the number 4 you will not be able to downgrade.
Click to expand...
Click to collapse
I can confirm, flashing will result in an error in bootloader. And that v4 bootloader (at least on my device) also prevents flashing custom image
Related
Is this at all possible? When attempting to downgrade with LGUP, it interrupts the flashing process (usually) around 9% with this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there a way to force-flash it regardless of this error? Or am I stuck without root forever?
Any answers are greatly appreciated.
At this moment in time the answer is NO. This is why you want to not do an upgrade until root is confirmed for the newer OS. Once recovery is available maybe you might be able to get root back.
I should correct myself you can't use the kdz files and go back to lolipop
details here :
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I was thinking about the TWRP method before, my bad.
LBJM said:
I should correct myself you can't use the kdz files and go back to lolipop
details here :
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I was thinking about the TWRP method before, my bad.
Click to expand...
Click to collapse
Thank you for the snappy reply! I have been very closely watching these forums on updates to either downgrade to lollipop, or root marshmallow. I sure hope we can get this resolved for people who's phone came with marshmallow
jingTongy said:
Thank you for the snappy reply! I have been very closely watching these forums on updates to either downgrade to lollipop, or root marshmallow. I sure hope we can get this resolved for people who's phone came with marshmallow
Click to expand...
Click to collapse
I had to downgrade using that same software when I purchased my Lg G3 and that alone sold me on the V10. With Samsung phones you are stuck if you have a newer OS.
The main reason you cannot downgrade is that the software won't flash an old version (as it checks your version stub), at all, on Verizon.
mcbeat257 said:
The main reason you cannot downgrade is that the software won't flash an old version (as it checks your version stub), at all, on Verizon.
Click to expand...
Click to collapse
So, with the way you termed it, it sounds like it's a software problem with LGUP?? If so, do you think it can be patched to ignore the version?
jingTongy said:
So, with the way you termed it, it sounds like it's a software problem with LGUP?? If so, do you think it can be patched to ignore the version?
Click to expand...
Click to collapse
The software itself makes it do this, and it is irrevocable and not able to do so in the builds, it reminds me of when I had my galaxy s4 and this happened as well.
According to this thread , you can:
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I normally do not root my phones, but I am having battery drain problems and I see no advantage to Marshmallow. I may downgrade if I cannot resolve my current problem.
mikekoz said:
According to this thread , you can:
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I normally do not root my phones, but I am having battery drain problems and I see no advantage to Marshmallow. I may downgrade if I cannot resolve my current problem.
Click to expand...
Click to collapse
Could you quote the part on that post where it talks about downgrading the firmware? As far as I can tell from the link you provided, that post only talks about returning the phone back to stock. And just to be clear, once you install the OTA update to the MM build, your stock is now the MM firmware. Please correct me if I am wrong.
zatanas33 said:
Could you quote the part on that post where it talks about downgrading the firmware? As far as I can tell from the link you provided, that post only talks about returning the phone back to stock. And just to be clear, once you install the OTA update to the MM build, your stock is now the MM firmware. Please correct me if I am wrong.
Click to expand...
Click to collapse
You may be correct, and hopefully somebody more knowledgeable than myself will chime in, but this text is part of the instructions from that thread:
TO GO BACK TO LP FROM MM - Open LGUP on your computer, click on FILE PATH and point it towards your LP KDZ. Close LGUP and re-open LGUP. Make sure you select REFURBISH this will do a FULL wipe, tick BIN file. Press Start. Make cup of tea and be patient
This does not work on the Verizon variant
Sent from my VS990 using XDA-Developers mobile app
mikekoz said:
According to this thread , you can:
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I normally do not root my phones, but I am having battery drain problems and I see no advantage to Marshmallow. I may downgrade if I cannot resolve my current problem.
Click to expand...
Click to collapse
I was having the same battery drain problem after the Marshmallow update on my V10. I let it go for a couple days to see if things would improve. Unfortunately, things weren't getting any better. While I've rooted a lot of Android phones in the past, I didn't really want to void the warranty on this phone yet.
I went ahead and did a factory reset and the battery is working better than ever. I usually use Titanium Root to backup, but had to rely on LG Backup this time. It worked well enough even though it took a long time to copy everything to the SD Card (about 3 hours for 4 GB). Only things that didn't come through after restoring were my home screen settings and the history for one game. No big deal, about an hour to get everything configured back to original (grab screenshots of your homescreen first).
Pretty thrilled to see the battery performing better than ever. Just got 16 hours out of it yesterday and had 35% left on somewhat light use.
burnsky05 said:
This does not work on the Verizon variant
Sent from my VS990 using XDA-Developers mobile app
Click to expand...
Click to collapse
The instructions say otherwise. There is even links to Verizon drivers. Where do you see that this method does not work for Verizon V10's?
http://forum.xda-developers.com/showthread.php?t=3344828
Sent from my VS990 using XDA-Developers mobile app
The thread also states its for certain models of LG V10 but the LGUP has a anti rollback built into it that will not allow you to go from marshmallow to lollipop on certain models...
burnsky05 said:
http://forum.xda-developers.com/showthread.php?t=3344828
Sent from my VS990 using XDA-Developers mobile app
The thread also states its for certain models of LG V10 but the LGUP has a anti rollback built into it that will not allow you to go from marshmallow to lollipop on certain models...
Click to expand...
Click to collapse
Thanks. :good:
So, maybe someone could come up with a anti rollback work around? Hopefully, or some other alternative.
hann1balk1ng said:
So, maybe someone could come up with a anti rollback work around? Hopefully, or some other alternative.
Click to expand...
Click to collapse
Possible if someone could reverse-engineer LGUP to allow downgrading. I have the lollipop KDZ file, now all I need is a way to flash it to my vs990.
In an attempt to downgrade an error was not seen in LGUP. As far as anyone could tell the phone and LGUP were in sync up until 85% or so and the reboot was initiated. The phone never came back on. LGUP made it to 100% but the phone stayed black. Maybe not,enough time was allowed to pass but the battery was then removed. The phone became a brick and wouldnt start in any mode. When plugged into a computer the computer sees something tries to install a driver then fails. Do not try and downgrade from Marshmallow with LGUP. It will not work.
AMCJUNGLE said:
In an attempt to downgrade an error was not seen in LGUP. As far as anyone could tell the phone and LGUP were in sync up until 85% or so and the reboot was initiated. The phone never came back on. LGUP made it to 100% but the phone stayed black. Maybe not,enough time was allowed to pass but the battery was then removed. The phone became a brick and wouldnt start in any mode. When plugged into a computer the computer sees something tries to install a driver then fails. Do not try and downgrade from Marshmallow with LGUP. It will not work.
Click to expand...
Click to collapse
Oh man that sucks.
Sent from my Nexus 7 using XDA-Developers mobile app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"Full Firmware" is firmware 4 file or 5 file (BL_ , AP_ , CP_ , CSC_ , EFS_ ,...), sometimes is a single file (All_...) and include the standard PIT files. When you flash "Full Firmware" & PIT files, all devices partitions will be repair, re-fomat and factory reset devices.
When do need "Full Firmware" ?
Soft brick
Failed to mount a partition: efs, data, system,...
Failed flash firmware via Odin (stop at a partition: HIDDEN, CACHE,...)
Bootloop
Factory reset
Mod Edit: * * * IT IS YOUR RESPONSIBILITY TO VERIFY WHAT YOU ARE FLASHING TO YOUR DEVICE IS SAFE AND FOR YOUR DEVICE * * *
Mod Edit
1. Samsung Galaxy Note 8 (SM-N950F)
VietNam: N950FXXU1AQI1_N950FOXM1AQHF_XXV_7.1.1_FULL.zip (3,6G)
UK: N950FXXU1AQI1_N950FOXM1AQHF_BTU_7.1.1_FULL.zip (3,6G)
2. Samsung Galaxy Note 8 (SM-N950N)
S: N950NKSU1AQI2_N950NOKR1AQI2_SKC_7.1.1_FULL.zip (3,1G)
L: N950NKSU1AQI2_N950NOKR1AQI2_LUC_7.1.1_FULL.zip (3,1G)
K: N950NKSU1AQI2_N950NOKR1AQI2_KTC_7.1.1_FULL.zip (3,1G)
3. Samsung Galaxy Note 8 (SM-N950U)
USA: N950USQU1AQI9_N950UOYN1AQI9_USC_7.1.1_FULL.zip (3,5G)
Verizon: N950USQU1AQI5_N950UOYN1AQI5_VZW_7.1.1_FULL.zip (3,6G)
T-Mobile: N950USQU1AQI5_N950UOYN1AQI5_TMB_7.1.1_FULL.zip (3,4G)
Sprint: N950USQU1AQH7_N950UOYN1AQH7_SPR_7.1.1_FULL.zip (3,5G)
4. Samsung Galaxy Note 8 (SM-N950U1)
AT&T: N950U1UEU1AQI5_N950U1OYM1AQI5_ATT_7.1.1_FULL.zip (3,0G)
5. Samsung Galaxy Note 8 (SM-N950W)
Canada: N950WVLU1AQI5_N950WOYV1AQI5_XAC_7.1.1_FULL.zip (3,6G)
6. Samsung Galaxy Note 8 (SM-N950X)
Updating…
Mod Edit
Hi Thank you for hosting the firmware
I have tried this N950U1UEU1AQI5_N950U1OYM1AQI5_ATT_7.1.1_FULL.zip (3,0G) but you posted that as ATT. (there is no ATT bloatware at all)
I figured it out by N950U1 = No Carrier and N950U is carrier like verzon/ATT/TMB
this is Unlocked US version Note 8 like SM-N950UZKAXAA and sold by Samsung Direct or best buy so far .
kt.thegioiso said:
"Full Firmware" is firmware 4 file or 5 file (BL_ , AP_ , CP_ , CSC_ , EFS_ ,...), sometimes is a single file (All_...) and include the standard PIT files. When you flash "Full Firmware" & PIT files, all devices partitions will be repair, re-fomat and factory reset devices.
When do need "Full Firmware" ?
Click to expand...
Click to collapse
There's already a thread for the SM-N950F/DS Model:
https://forum.xda-developers.com/galaxy-note-8/how-to/official-stock-firmware-update-odin-t3677072
The correct unlocked (SM-N950U1) version can be found here:
https://forum.xda-developers.com/ga...covery-odin-recovery-software-t3671615/page22
The carrier versions of the Unlocked (SM-N950U1) "aqh9"...only differ by including the product activation information that the SIM provides during provisioning. Flashing the XAA unlocked firmware and inserting SIM is the same as flashing any of the SM-N950U1 brand labeled firmware like SPR AQH9...
---------- Post added at 05:38 AM ---------- Previous post was at 05:33 AM ----------
car2carl said:
Hi Thank you for hosting the firmware
I have tried this N950U1UEU1AQI5_N950U1OYM1AQI5_ATT_7.1.1_FULL.zip (3,0G) but you posted that as ATT. (there is no ATT bloatware at all)
I figured it out by N950U1 = No Carrier and N950U1 is carrier like verzon/ATT/TMB
this is Unlocked US version Note 8 like SM-N950UZKAXAA and sold by Samsung Direct or best buy so far .
Click to expand...
Click to collapse
...
Canada firmware link points to AT&T firmware. Could someone please update that link? I will be sending my phone in for refund (to get the N950F), and want to completely reset it.
Side note, anyone know how they check airtime usage to determine return eligibility? I'm well under 30 minutes, but I'm curious regardless.
https://www.sammobile.com/firmwares/SM-N950F/SWC/download/N950FXXU1AQI1/189026/
Is it possible that anyone can download this for me?
Edit: obsolet, retourned to shop with light bleeding on the hole left side.
I keep getting failed message when trying to flash the verizon firmware. any ideas.
thunderbread said:
I keep getting failed message when trying to flash the verizon firmware. any ideas.
Click to expand...
Click to collapse
Edit config file for UMS/patch from 0 to 1...and if regular Odin fails...use Prince Comsy's Odin...if still fail download firmware again...if still fail, boot to recovery and perform factory reset then flash again
Could I flash SM-N950F firmware on SM-N950N device? I need to change csc from Korea to Vietnam
Can someone help me? I installed a firmware con my Note8 and my storage decreased from 128 gb to 32 gb.
D_Gabe said:
Can someone help me? I installed a firmware con my Note8 and my storage decreased from 128 gb to 32 gb.
Click to expand...
Click to collapse
Sounds like you might not have re-partitioned it properly?
seandop said:
Sounds like you might not have re-partitioned it properly?
Click to expand...
Click to collapse
Nope. Apparently, when I installed the Unlocked firmware, it automatically partitioned my device. I had to do a factory reset to recover my 128gb storage.
It actually worked. Thanks anyway. I'm actually learning a lot. First time customizing an Android device (just changed from an iPhone 6 Plus).
D_Gabe said:
Nope. Apparently, when I installed the Unlocked firmware, it automatically partitioned my device. I had to do a factory reset to recover my 128gb storage.
It actually worked. Thanks anyway. I'm actually learning a lot. First time customizing an Android device (just changed from an iPhone 6 Plus).
Click to expand...
Click to collapse
Glad you figured it out! Welcome to Android.
So, would I be able to use this process to load the Verizon firmware to my Unlocked Note 8? I bought an unlocked version from Samsung, but there are several features that seem to be unavailable (visual voicemail, accessing internet when on phone, etc.). Would loading the Verizon firmware fix that issue for me?
Verizon tech support has not been of much use trying to get these features working on my unlocked phone, so I'm hoping that if it "magically" becomes a Verizon phone, the features would start working.
Note that I have tried Shortcut Master to get around these limitations, but no luck so far.
Croq360 said:
So, would I be able to use this process to load the Verizon firmware to my Unlocked Note 8? I bought an unlocked version from Samsung, but there are several features that seem to be unavailable (visual voicemail, accessing internet when on phone, etc.). Would loading the Verizon firmware fix that issue for me?
Verizon tech support has not been of much use trying to get these features working on my unlocked phone, so I'm hoping that if it "magically" becomes a Verizon phone, the features would start working.
Note that I have tried Shortcut Master to get around these limitations, but no luck so far.
Click to expand...
Click to collapse
Yes, download and flash the latest VZW firmware in Odin (all four files) and all will be well.
Deleted.
I can't get back to stock as I used the first method of samfail and now my bootloader reflects aqh8 and my system/baseband reflects aq15. I tried using Odin and get device mismatch errors I tried using kies it doesn't recognize my phone even in emergency mode. Any ideas how to get back to complete stock aq15 or at least on how to get bootloader to match system as aq15?
See how bl reflects aqh8? Is there a way to get it to match the rest at aq15? Or does everyone who used samfail root method look this way? How would I go back to Stock since I'm getting device mismatches in odin.
Please any help would be greatly appreciated
See mismatch
kirschdog1 said:
I can't get back to stock as I used the first method of samfail and now my bootloader reflects aqh8 and my system/baseband reflects aq15. I tried using Odin and get device mismatch errors I tried using kies it doesn't recognize my phone even in emergency mode. Any ideas how to get back to complete stock aq15 or at least on how to get bootloader to match system as aq15?
See how bl reflects aqh8? Is there a way to get it to match the rest at aq15? Or does everyone who used samfail root method look this way? How would I go back to Stock since I'm getting device mismatches in odin.
Please any help would be greatly appreciated
Click to expand...
Click to collapse
Use Prince Comsey Odin. You won't get the device mismatch errors.
sprint sm-N950USQU1AQI5 flashing to use on another carrier
I tried flashing with the zip file. But, I see invalid sim when I insert different carrier. Detailed desc would help me.
Or, is there any alternative to flash the sprint note 8(N950USQU1AQI5) to use different carrier.
Thanks in advance.
Hi all,
First some details:
LG930DS
secure startup enabled
H930DS30s_00_OPEN_HK_DS_OP_0902.kdz installed via LG Bridge. It changed me from AU to HKG for reasons unknown to me.
rooted with TWRP and Magisk 20.1 installed
I'm having issues with VoLTE not working (actually no longer in settings of the hidden menu) since installing Pie and I want to rule out the HKG variant as the cause. To do this I will install H930DS30c_00_OPEN_AU_DS_OP_0902.kdz instead. I have downloaded this kdz but now I'm not sure if I can install it without having to wipe and re-do all the Magisk and TWRP (and setting up all my files and apps again). After reading the guides none seem to answer this question quite right as they are mostly aimed and either US, EU, or India with their TWRP flashable roms like this one https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99830a000704-kdz-t3952256
Can someone with a better idea of how this works let me know the best option for me to switch over to the AU variant.
Wibble Wobble said:
Hi all,
First some details:
LG930DS
secure startup enabled
H930DS30s_00_OPEN_HK_DS_OP_0902.kdz installed via LG Bridge.
It changed me from AU to HKG for reasons unknown to me.
Click to expand...
Click to collapse
LG Bridge will look for the KDZ intended for your IMEI, not the firmware you have on the phone right now. Was your phone imported from Hong Kong (China)? Or did you buy from Australian carrier or Australia LG authorized retailer? Did you buy the phone new or used? Have you updated it before using LG Bridge?
Any H930DS can be flashed to run any other H930DS firmware. Best guess is somehow the phone was originally Hong Kong variant and someone flashed it to Australian firmware. When you went to look for update via LG Bridge, then it updated to that region Pie meant for that IMEI.
Unless you have used LG Bridge successfully before and you are sure it is Australian IMEI H930DS?
Wibble Wobble said:
rooted with TWRP and Magisk 20.1 installed
I'm having issues with VoLTE not working (actually no longer in settings of the hidden menu) since installing Pie and I want to rule out the HKG variant as the cause. To do this I will install H930DS30c_00_OPEN_AU_DS_OP_0902.kdz instead. I have downloaded this kdz but now I'm not sure if I can install it without having to wipe and re-do all the Magisk and TWRP (and setting up all my files and apps again). After reading the guides none seem to answer this question quite right as they are mostly aimed and either US, EU, or India with their TWRP flashable roms like this one https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99830a000704-kdz-t3952256
Can someone with a better idea of how this works let me know the best option for me to switch over to the AU variant.
Click to expand...
Click to collapse
We haven't always had TWRP-flashable zips. Only thanks to generous, talented devs do we have the collection of TWRP flashable zips for US998, H931, H933, VS996, LS998, T-mobile H932, H930, India H930DS. That's only 8 of at least 20 variants and I'm not even counting all the different regional variants of H930DS...
So you will have to do what we all did before TWRP-flashable zips, and what we will have to do again when some of our TWRP flashable zip devs move onto other phones.
Method #1 -- Works some of the time on Oreo, not yet tried on Pie
This worked for many people in Oreo -- but some still had to reinstall TWRP, reformat data, reinstall the root files. Never could figure out the difference between success and not. Then we got TWRP-flashable zips and the issue became moot.
1) Make backup in TWRP AND make backup of all apps in Titanium Backup.
2) Flash new KDZ via Pie-compatible Dev Patched LGUP in Partition DL mode, but omit the Recovery partitions. Do NOT select "all partitions". This will let you keep TWRP.
3) Boot into TWRP via fastboot commands from your computer, just like when you first installed TWRP using the WTF instructions. (Best not to use the stupid hardware button dance.) Once in TWRP, then choose Reboot to Recovery (from within TWRP) to get the actual internal phone TWRP, instead of the PC TWRP.
4) Flash the Pie-compatible three root files (Magisk, encryption disabler, root check disabler, Magisk again). See attachments on this post to download those files.
5) Restore all Data from within TWRP. Do not choose any other categories.
6) Wipe all Caches.
7) Reboot
Restoring all TWRP data may or may not overcome the fact that you have re-flashed encrypted stock Pie on your phone. IF it does work, then after rebooting the phone if anything is still wonky, use Titanium Backup to restore all apps and data (this is in addition to the TWRP data restore you did).
Good luck.
Method #2 -- Works all the time, but yeah you have set up your phone again
1) Flash new KDZ via Pie-compatible Dev Patched LGUP in REFURBISH mode.
2) Your phone is now on the region KDZ you desire and you still have unlocked bootloader. You will need to reinstall TWRP, and then flash the three root files (Magisk, encryption disabler, root check disabler, Magisk again). This includes the step where you reformat all data with a "YES".
See instructions here:
REINSTALL TWRP on PIE stock KDZ with ALREADY-UNLOCKED BOOTLOADER
THAT POST ASSUMES YOU HAVE PREVIOUSLY UNLOCKED BOOTLOADER, AND THAT YOU HAVE NOW UPGRADED TO STOCK PIE KDZ. YOU HAVE UNLOCKED BOOTLOADER and are STILL on firmware which has FASTBOOT FLASH COMMANDS.
___________
Dev Patched LGUP
Dev Patched LGUP vs regular LGUP is necessary when cross flashing across regions or other variants. You will need this for either of the two methods above.
Here's how to flash with LGUP:
UPGRADING LG V30/V30+/V30S TO PIE KDZ FIRMWARE WITH LGUP
1) Go into download mode (power off completely, then hold volume up button while plugging in USB cable)
2) open Dev Patched LGUP and flash PIE KDZ either via PARTITION DL MODE (but omit Recovery Partitions for your purpose in this thread) for Method #1 or via REFURBISH for Method #2.
Use the attached patched LGUP in this post. If you get a ".dll error" you either didn't install correctly or are using the wrong version of Dev Patched LGUP. Read the installation instructions carefully. Some people have used OTHER versions of LGUP before and ignore the installation instructions -- they think they know how to install and they do NOT --- then complain about .dll error, which is their fault.
* NOTE: YOU CAN NOT USE LGUP "UPGRADE" MODE IF YOU HAVE TWRP CUSTOM RECOVERY. LGUP "Upgrade" is like a manual OTA and is only for pure stock (but you can have unlocked bootloader).
3) IF your bootloader is unlocked, it will remain unlocked after flashing KDZ.
_________________
HOW TO INSTALL DEV PATCHED LGUP
0. UNINSTALL any prior LGUP version. Seriously. Go to Programs folder and delete the LGUP folder if you must.
1. DOWNLOAD THIS DUAL VERSION OF DEV PATCHED LGUP, made by @tecknight:
https://androidfilehost.com/?fid=11410963190603845019
(Or use attached file from bottom of this post. Thanks to @tecknight! Please go here and click the THANK BUTTON!)
2. Extract LGUP_DualMode.zip to a folder on your PC.
3. Browse into the folder and launch LGUP_Store_Frame_Ver_1_14_3.msi.
Follow the prompts to complete the install.
4. In that folder, right click and select "Run as Administrator" on "SetDev.bat" to set LGUP to developer mode. < READ THAT AGAIN.
5. Launch LGUP using the desktop shortcut. NOT from folder icon!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING: In LGUP do NOT go messing with modes not mentioned in these instructions. Especially do NOT use Chip Erase.
I don't care what anyone else tells you. If you listen to them, let them help you recover from messing up your phone.
https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/
3) ChipErase: Dangerous, This will erase IMEI/efs, Do not try this if you do not have a NV backup.
Click to expand...
Click to collapse
It's all fairly easy. Most people breeze right through this. But if you have any problems, go through this list:
Make sure you in download mode BEFORE opening the patched LGUP file.
This is at the top of the list as some people forget to do that. The remainder are in no particular order. If that doesn't work,
Try different USB port,
Try different USB cable,
Try different computer.
Reinstall LG mobile drivers on your PC.
Reinstall dev patched LGUP again.
Reboot the computer.
If you ask for help, that's the list of items we are going to give you anyway.
ChazzMatt said:
LG Bridge will look for the KDZ intended for your IMEI, not the firmware you have on the phone right now. Was your phone imported from Hong Kong (China)? Or did you buy from Australian carrier or Australia LG authorized retailer? Did you buy the phone new or used? Have you updated it before using LG Bridge?
Any H930DS can be flashed to run any other H930DS firmware. Best guess is somehow the phone was originally Hong Kong variant and someone flashed it to Australian firmware. When you went to look for update via LG Bridge, then it updated to that region Pie meant for that IMEI.
Unless you have used LG Bridge successfully before and you are sure it is Australian IMEI H930DS?
Click to expand...
Click to collapse
Ahh thank you for explaining this. I imported mine from Hong Kong. As far as I know it was never sold new in AU.
I'm about to rush off to work for the day so I will have to try this when I get home tonight and let you know how it goes. Thank you so much for the detailed and fast response! This is much more than I was hoping for!
One last question. Do I need to disable secure startup or does the encryption work with the method #1?
Wibble Wobble said:
One last question. Do I need to disable secure startup or does the encryption work with the method #1?
Click to expand...
Click to collapse
Yes, I would do that.
---------- Post added at 10:43 PM ---------- Previous post was at 10:39 PM ----------
Wibble Wobble said:
As far as I know it was never sold new in AU.
Click to expand...
Click to collapse
I don't know the Australian market, but we have an Australian XDA moderator who has or had Australia H930DS. Since there is Australia H930DS firmware, I assume it was sold new back in 2017/2018 by some carrier or by LG authorized retailer.
He has Vodafone in his profile. @Redline.
ChazzMatt said:
I don't know the Australian market, but we have an Australian XDA moderator who has or had Australia H930DS. Since there is Australia H930DS firmware, I assume it was sold new back in 2017/2018 by some carrier or by LG authorized retailer.
He has Vodafone in his profile. @Redline.
Click to expand...
Click to collapse
This is correct. I bought one BNIB from an eBay seller, a H930DS and it was only a couple weeks old from the factory. Came pre-loaded with AU firmware and I updated it to the latest. Before going the LineageOS route.
Redline said:
This is correct. I bought one BNIB from an eBay seller, a H930DS and it was only a couple weeks old from the factory. Came pre-loaded with AU firmware and I updated it to the latest. Before going the LineageOS route.
Click to expand...
Click to collapse
Interesting to know. I bought mine back in 2017 but I couldn't find it in AU and read somewhere that imports were going to be the only option. To bad for me.
I know little of what IMEI's do. Is there any issues related to regional OS versions and the IMEI of a device? Is the hardware otherwise the same?
Wibble Wobble said:
Interesting to know. I bought mine back in 2017 but I couldn't find it in AU and read somewhere that imports were going to be the only option. To bad for me.
I know little of what IMEI's do. Is there any issues related to regional OS versions and the IMEI of a device? Is the hardware otherwise the same?
Click to expand...
Click to collapse
I could kind of answer is the question of if the hardware is otherwise the same, the rest might be a question for ChazzMatt.
AFAIK the modem on my H930DS was the same as other similar models, similar to the V20 you can flash a KDZ from another region if you wanted to (to for example, get less bloat or better coverage on a band you rely on for service). I remember on my V20 the region that had Claro-carrier firmware came with the least bloat out of the box vs other regions, but we also had KDZ Writer with the V20 that allowed us to flash specific parts of the KDZ *in* TWRP on the device itself, so you could have, say, Claro firmware with the AU modem.
As for what IMEIs do, they're similar to the MAC address on a piece of networking gear; it's a globally-unique identifier specific to your device, you can put it into IMEI lookup websites to get information about manufacture date, model etc.
If you have a carrier-model phone, they can also block your IMEI on their network if it is stolen and then attempted to be re-used.
I've had to opt with #2 as the encryption was a problem as you suspected. I'm puzzled though... while I was setting up for USB debugging I noticed that I had VoLTE in the drop down menu, however, calls still reverted back to 3G. I didn't pay much attention to it as I had to do a format in the steps to follow. Now that I'm back up and running I no longer have VoLTE in the drop down menu? It's the only icon missing. Calls still revert to 3G again. I'm on the boost network which uses Telstra and this phone is listed as compatible for VoLTE with them. I know that it worked in Oreo too.
Wibble Wobble said:
I've had to opt with #2 as the encryption was a problem as you suspected. I'm puzzled though... while I was setting up for USB debugging I noticed that I had VoLTE in the drop down menu, however, calls still reverted back to 3G. I didn't pay much attention to it as I had to do a format in the steps to follow. Now that I'm back up and running I no longer have VoLTE in the drop down menu? It's the only icon missing. Calls still revert to 3G again. I'm on the boost network which uses Telstra and this phone is listed as compatible for VoLTE with them. I know that it worked in Oreo too.
Click to expand...
Click to collapse
Hmmm.... Sorry, I don't know. But you are back on Australian firmware.
If you wish, you can use the same procedure to downgrade back to Australian Oreo to see if you can get VoLTE back.
H930DS20f_00_OPEN_AU_DS_OP_0408.kdz
https://lg-firmwares.com/downloads-file/19586/H930DS20f_00_OPEN_AU_DS_OP_0408
ChazzMatt said:
Hmmm.... Sorry, I don't know. But you are back on Australian firmware.
If you wish, you can use the same procedure to downgrade back to Australian Oreo to see if you can get VoLTE back.
H930DS20f_00_OPEN_AU_DS_OP_0408.kdz
https://lg-firmwares.com/downloads-file/19586/H930DS20f_00_OPEN_AU_DS_OP_0408
Click to expand...
Click to collapse
Out of frustration I started doing random things just to test there effect, much of it being in the hidden menu where I discovered VoLTE settings. Nothing was working until... I force stopped the carrier service and made a phone call. Presto! VoLTE now appears (though not listed under any setting in mobile networks, or in the drop down menu) and my calls say HD call. Finally to confirm 4G remains active and still works during a call!
Hi, does anyone know how I can flash the base, curt and preload of the p20 lite ane-lx3?
I got them with hisuite proxy but they give me an error when verifying update.
I need it because I can only go back to emui 8 from hi suite emui 9 does not appear, I had downloaded it to unlock the bootloader. I already unlocked them but I want to go back to the most updated emui or at least more than 9.1.0.142 since it still has the app drawer button.
I have seen that the multi tool 8 can be used to flash but I don't understand how to do it.
antonyx2016 said:
how I can flash the base, curt and preload of the p20 lite ane-lx3?
Click to expand...
Click to collapse
this can be done via modified TWRP, HuRupdater 0.4 or Multi-tool if you are running EMUI 9.1.
But these methods are risky when upgrading from 8.0 to 9.1 and are not recommended.
You can safely manually upgrade to 9.1 only by installing the service ROM using the dload method from the SD card.
What is your full build number? (settings > About phone).
Also check your vendor/country information via the Project Menu (*#*#2846579#*#*) and post the result.
Thank you for taking the time to respond, here I leave what you asked for. I would appreciate it if you could explain a little more how to do the process.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I thought you were currently on 8.0, sorry. So you can try the methods in my previous post.
For HuRupdater method use TWRP 3.2.1 "Gaguga edition".
Rename all three archives:
base -> update.zip
preload -> update_data_public.zip
cust -> update_all_hw.zip
It works on the P20 Pro, it should also work on the P20 Lite. Be aware that these methods are risky, especially when it comes to choosing the right firmware for your phone!
Personally, I prefer an update via eRecovery & wi-fi, or installing a service ROM via dload.
You can download Service ROM for your phone
Here
The dload process will erase all your data and lock your BL again!
-Alf- said:
I thought you were currently on 8.0, sorry. So you can try the methods in my previous post.
For HuRupdater method use TWRP 3.2.1 "Gaguga edition".
Rename all three archives:
base -> update.zip
preload -> update_data_public.zip
cust -> update_all_hw.zip
It works on the P20 Pro, it should also work on the P20 Lite. Be aware that these methods are risky, especially when it comes to choosing the right firmware for your phone!
Personally, I prefer an update via eRecovery & wi-fi, or installing a service ROM via dload.
You can download Service ROM for your phone
Here
The dload process will erase all your data and lock your BL again!
Click to expand...
Click to collapse
Good brief update: I tried all the stock roms of ane-l23 all with the same result in the case of emui 9 it stays at 9.1.0.046 and in emui 8 8.0.0.046 so far everything is fine after reading several forums here I have found one to see the files with root everything is fine up to here I enter /cust/hw and find two folders (la or latam) and normal. and in special cust only after all the props are fine, that is, it is 5.0.0.20.
Then looking for more information to see where the 8.0.0.046 was, I found it in version.prop. Additionally, enter splash2/cust.log and throw a lot of errors in the following post or answer. I leave you the images to see if we can solve something because the problem that bothers me is not being in emui 8 or 9 but that it is not so stable all that works if when installing any firm again the huawei id does not work first playstore and update hsm core after that everything works either themes etc etc.
but it lags a lot in emui 8 and in emui 9 google maps doesn't work so I don't care if I stay in emui 8 or 9 honestly but I do want the equipment to work correctly. Thank you very much for your willingness and willingness to help.
antonyx2016 said:
emui 9 it stays at 9.1.0.046 and in emui 8 8.0.0.046
Click to expand...
Click to collapse
It means wrong or incomplete FW. As I said before,
-Alf- said:
service ROM via dload.
You can download Service ROM for your phone
Click to expand...
Click to collapse
-Alf- said:
Here
Click to expand...
Click to collapse
Maybe you are doing something wrong...Follow instructions in ReleaseDoc folder.
antonyx2016 said:
I tried all the stock roms of ane-l23
Click to expand...
Click to collapse
you can only install the service ROM for your region (hw/la)!
But it is possible that with your current build number 9.1.0.046 you will not be able to flash via dload or eRecovery.
-Alf- said:
It means wrong or incomplete FW. As I said before,
Maybe you are doing something wrong...Follow instructions in ReleaseDoc folder.
you can only install the service ROM for your region (hw/la)!
But it is possible that with your current build number 9.1.0.046 you will not be able to flash via dload or eRecovery.
Click to expand...
Click to collapse
Yes I understand that, but what I wanted to say is that I already tried all the c605 firmware that there is, whether it is emui 8 and emui 9, they all install without error but apparently they do not install at all, I don't know if it is cust the oem partition or something like that but whatever the method, it always ends in .046 the only thing I know for sure is that it started to be like that a year ago when I used hisuite to go back and from there I could no longer update after what happened with hisuite I bought the code in dc to unlock the bootloader but I still can't remove the .046 in a few words hisuite screwed my phone xD because it was never rooted or unlocked until after what I told you
Okay, I don't know what the problem is, two last tips from me:
A) follow this method
https://ministryofsolutions.com/202...re-stock-rom-emui9-1-unlocked-bootloader.html
(reliable source)
B) rebrand to global version C432. But this requires downgrading to Oreo, and this is only possible through HiSuite (because there are no files needed for HuRupdater). It could help to get a fully working phone.
It could happen that before using hisuite you had a different region, not hw/la (claro/la etc.) hisuite couldn't recognize it and downgraded your phone to hw/la. Maybe you should try flashing oeminfo C605.
In fastboot mode run commands :
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the result.
If you decide to rebrand, I will give you instructions.
-Alf- said:
If you decide to rebrand, I will give you instructions.
Click to expand...
Click to collapse
If that helps me, ok, I tried option a) it was installed but it is incomplete with the pink background. If doing a rebrand will help me, ok
antonyx2016 said:
with the pink background
Click to expand...
Click to collapse
Now try to flash Service ROM.
Also try enter eRecovery and use option "Download latest version...".
As for rebrand, I can't give you any guarantee.
-Alf- said:
Now try to flash Service ROM.
Also try enter eRecovery and use option "Download latest version...".
As for rebrand, I can't give you any guarantee.
Click to expand...
Click to collapse
I think I achieved it in a while I'll tell you what happened but I'm hopeful something changed with the hisuite proxy
Ok, let me tell you, I managed to install firmware 9.1.0.355. I know it's not the latest and it didn't free me from system component 9.1.0.040 either, but at least now everything works correctly.
I'll tell you what I did in case it helps someone else:
1- I did the point a) that you sent me
2- I kept the pink wallpaper and I went to the proxy hisuite and downloaded the cust, preload and base .355
3- it marked an error when installing in the 1% of hisuite the proxy already warned me that it was going to fail and to cancel
4- cancel it and deactivate the 3 checks of point, cust and preload
5-I put in developer mode and look for the update in hisuite
6- This time I no longer throw any errors and it was completely flashed. I imagine that because of step a) the cust was updated and that is why it allowed the .355 to be installed
7-it was still half incomplete but I went into settings and updated and I got the same .355 version and it was installed correctly in quotes as I said I still have the .40 system but everything works now I imagine that if you keep messing around a bit that way it will I could install the .390 but I'm satisfied with the .355
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My s8+ had UAE firmware on it, settings showed FD version but all other apps like HW info and antutu, Samsung members said F only.
Moving forward I tried to flash a custom official noble rom, and I clicked install twrp too. Fast forward after installation my phone only is stuck in downloading screen, and holding down volume down and power button keeps taking me back to download mode, and it won’t even boot or do anything else. It’s just stuck. I tried to flash official firmware from Odin, i wasn’t sure what my csc was so I flashed and tried every single rom of UAE and I could not flash a single one. It keeps failing. My sister has exams, and I’m being held responsible, I’m poor and my mom can’t buy her a new phone let alone fix this from a shop. I beg any kind soul to please help me out of this.
shafin123 said:
View attachment 5894253My s8+ had UAE firmware on it, settings showed FD version but all other apps like HW info and antutu, Samsung members said F only.
Moving forward I tried to flash a custom official noble rom, and I clicked install twrp too. Fast forward after installation my phone only is stuck in downloading screen, and holding down volume down and power button keeps taking me back to download mode, and it won’t even boot or do anything else. It’s just stuck. I tried to flash official firmware from Odin, i wasn’t sure what my csc was so I flashed and tried every single rom of UAE and I could not flash a single one. It keeps failing. My sister has exams, and I’m being held responsible, I’m poor and my mom can’t buy her a new phone let alone fix this from a shop. I beg any kind soul to please help me out of this.
Click to expand...
Click to collapse
Alright, lets fix this. Looking at what firmware is available for your phone. Can you please give me your CSC? Dial *#1234#" to figure out what you're current CSC code is.
shafin123 said:
View attachment 5894253My s8+ had UAE firmware on it, settings showed FD version but all other apps like HW info and antutu, Samsung members said F only.
Moving forward I tried to flash a custom official noble rom, and I clicked install twrp too. Fast forward after installation my phone only is stuck in downloading screen, and holding down volume down and power button keeps taking me back to download mode, and it won’t even boot or do anything else. It’s just stuck. I tried to flash official firmware from Odin, i wasn’t sure what my csc was so I flashed and tried every single rom of UAE and I could not flash a single one. It keeps failing. My sister has exams, and I’m being held responsible, I’m poor and my mom can’t buy her a new phone let alone fix this from a shop. I beg any kind soul to please help me out of this.
Click to expand...
Click to collapse
Wait...you can't dial. Well, what country are you in?
ethical_haquer said:
Alright, lets fix this. Looking at what firmware is available for your phone. Can you please give me your CSC? Dial *#1234#" to figure out what you're current CSC code is.
Click to expand...
Click to collapse
Sir, the phone does not do anything but go in download mode, this is a screen shot I kept before starting the flashing process
ethical_haquer said:
Wait...you can't dial. Well, what country are you in?
Click to expand...
Click to collapse
I am in Bangladesh, this is a second hand phone and I’m not sure but I sense that this used to be a single sim phone and the previous owner put a dual SIM card tray and installed firmware for FD model, and somehow both sims did use to work just fine.
I’ll tell you where everything went wrong and what was the state of the device so that you can make a better judgement of where I ****ed up.
1. I used adb fast boot from cmd to reboot the phone into fastboot.
2. I installed linageos 19.1 android 12 version and the phone was working perfectly. The custom rom was installed.
3. Then I wanted to tweak the phone to increase battery life, stop over heating and screen flicker so I did some research and downloaded hadesRom v12.0 Pie S8/S8+/Note8 and stored it in my phone memory and flashed it in the similar way as linage OS. I also went ahead and tried to install a2n kernel. When trying to install, I received a message saying that I’m trying to install a wrong kernel where my g955 is “N” and not “F” which indicates that it’s a Korean variant but this contradicts everything I’ve done before, anyway that didn’t create a problem but I did this without even rebooting after the hades rom. Ever since then, I’ve been booted back to download mode and I’ve tried flashing official firmwares but nothing helped. It failed every time I’ve been up all night since yesterday and my mother is on the verge of kicking me out, I’m pulling my own hair to find out what is actually wrong but I can’t find anything.
All details of what has been done to the device***
ll tell you where everything went wrong and what was the state of the device so that you can make a better judgement of where I fvkd up.
1. I used adb fast boot from cmd to reboot the phone into fastboot.
2. I installed linageos 19.1 android 12 version and the phone was working perfectly. The custom rom was installed.
3. Then I wanted to tweak the phone to increase battery life, stop over heating and screen flicker so I did some research and downloaded hadesRom v12.0 Pie S8/S8+/Note8 and stored it in my phone memory and flashed it in the similar way as linage OS. I also went ahead and tried to install a2n kernel. When trying to install, I received a message saying that I’m trying to install a wrong kernel where my g955 is “N” and not “F” which indicates that it’s a Korean variant but this contradicts everything I’ve done before, anyway that didn’t create a problem but I did this without even rebooting after the hades rom. Ever since then, I’ve been booted back to download mode and I’ve tried flashing official firmwares but nothing helped. It failed every time I’ve been up all night since yesterday and my mother is on the verge of kicking me out, I’m pulling my own hair to find out what is actually wrong but I can’t find anything
shafin123 said:
it keeps failing.
Click to expand...
Click to collapse
How?
Also, what version of Android did you have with stock? - Right now it looks like I can only download A9 for your device.
ethical_haquer said:
How?
Click to expand...
Click to collapse
Secure check fail: (pit)
And then if I reboot the phone into download mode, and reset and start the process from scratch again, it fails and the error this time is write operation failed
ethical_haquer said:
Also, what version of Android did you have with stock?
Click to expand...
Click to collapse
Android 9 on stock, then installed linageOS with android 12 then flashed hades ported android 9 and that’s where it went wrong
I
shafin123 said:
Secure check fail: (pit)
And then if I reboot the phone into download mode, and start Odin, fails and the error is write operation failed
Click to expand...
Click to collapse
I’ve even tried multiple csc in both Odin 1.3 and the latest one. I haven’t left any stone unturned from my knowledge. All adb drivers and Samsung drivers are installed as well
shafin123 said:
Android 9 on stock, then installed linageOS with android 12 then flashed hades ported android 9 and that’s where it went wrong
Click to expand...
Click to collapse
So do you want to go back to stock A9 or LOS19, both are an option.
shafin123 said:
I’ve even tried multiple csc in both Odin 1.3 and the latest one. I haven’t left any stone unturned from my knowledge. All adb drivers and Samsung drivers are installed as well
Click to expand...
Click to collapse
Is this with F, or FD as the end of the model firmware?
It sounds like the PIT error happens when the firmware isn't the right version.
Also, do you want the BNG (Bangladesh) firmware or something else?
ethical_haquer said:
So do you want to go back to stock A9 or LOS19, both are an option.
Is this with F, or FD as the end of the model firmware?
It sounds like the PIT error happens when the firmware isn't the right version.
Also, do you want the BNG (Bangladesh) firmware or something else?
Click to expand...
Click to collapse
BNG firmware is fine, I don’t know if I should flash F or FD, as I’ve tried both and both have failed. I’d rather go back to A9 and then work my way around. And I have all the firmwares downloaded. I think I’ve messed up my boot loader somehow.
ethical_haquer said:
So do you want to go back to stock A9 or LOS19, both are an option.
Is this with F, or FD as the end of the model firmware?
It sounds like the PIT error happens when the firmware isn't the right version.
Also, do you want the BNG (Bangladesh) firmware or something else?
Click to expand...
Click to collapse
Beggars can’t be choosers, I just want the phone to work again, and somehow get out of the download mode
shafin123 said:
Beggars can’t be choosers, I just want the phone to work again, and somehow get out of the download mode
Click to expand...
Click to collapse
So, what exactly happens when you flash the firmware, a PID error?
Secure check fail: (pit)
And alternatively
Write operation failed, this is after I get pit fail and try again
shafin123 said:
Secure check fail: (pit)
And alternatively
Write operation failed, this is after I get pit fail and try again
Click to expand...
Click to collapse
Look at this tutorial. I've followed it before. Just make sure that you're flashing it properly with Odin, as you need to make sure you wipe the device:
As you can see, flashing the CSC file will wipe, whereas the HOME_CSC will not.
ethical_haquer said:
Look at this tutorial. I've followed it before. Just make sure that you're flashing it properly with Odin, as you need to make sure you wipe the device:
As you can see, flashing the CSC file will wipe, whereas the HOME_CSC will not.
Click to expand...
Click to collapse
Yes I’m aware and only using the CSC file not home.
shafin123 said:
Yes I’m aware and only using the CSC file not home.
Click to expand...
Click to collapse
Try looking at these solutions. Let me know if it still doesn't work.