Related
I picked up this GS6. Here is what is on the about phone:
Status
Legal Information
Model Number: SM-G9200
Android Version: 5.0.2
Baseband Version: MOLY.WR8.W1315.MD.WG.MP.V34
Kernal Version: 3.10.0-2828982
[email protected] #1
Tue Jul 28 10:17:25 CST 2015
Build Number: KTU84P.N9100ZCU1ANIF
Custom build version:I9296_FW_A.B-V4.0_0804
Now one thing I noticed in the about phone section is that there is no update button. What I want to do is be able to root this or update the OS on it some way. I've tried Smart Switch and Kies 3 and neither can detect the phone. My computer can detect the phone so I have access to the phone via the comp. Any help or ideas would be appreciated. Thank you.
At least some of that info looks fishy to me - not like Samsung nomenclature. My first thought is this is a clone. Did you get it through a reputable channel?
Sent from my SAMSUNG-SM-G920A using Tapatalk
I did get it from a site called dhgate.com. The phone works fine. Everything seems to be working right but there are a few quirks though.
dandrumheller said:
At least some of that info looks fishy to me - not like Samsung nomenclature. My first thought is this is a clone. Did you get it through a reputable channel?
Sent from my SAMSUNG-SM-G920A using Tapatalk
Click to expand...
Click to collapse
Torroth said:
I did get it from a site called dhgate.com. The phone works fine. Everything seems to be working right but there are a few quirks though.
Click to expand...
Click to collapse
Are you able to boot into download mode? The information you gave hints that either it is counterfeit, or it is the Chinese variant. When you boot into download mode you should know immediately if it is legit or not. If it is real, download mode will show a bluish screen with a warning message. If it is counterfeit, you will get a black screen with Chinese text.
UIt goes straight into system recovery.
Torroth said:
UIt goes straight into system recovery.
Click to expand...
Click to collapse
When you tried to boot into download mode you booted into recovery? Did you use the proper combination of buttons?
yes. down volume, home, power key after turning phone off
Bizarre. Could you share a screen shot?
I can't seem to find a way to insert a image.
Torroth said:
I can't seem to find a way to insert a image.
Click to expand...
Click to collapse
There is a workaround for such issue.
If for some reason you cannot share an image on xda,
post the image on the website imgur.com then share the link to the page that has the photo.
That is just one workaround. Another is to save the picture to google drive, then share a link to the drive folder.
Did you understand that?
here are the images (hope this works): http://imgur.com/a/sVJh9
The first image I get is with the droid the second after pressing power is the recovery screen.
Torroth said:
here are the images (hope this works): http://imgur.com/a/sVJh9
The first image I get is with the droid the second after pressing power is the recovery screen.
Click to expand...
Click to collapse
Tragic news for you.
That is the recovery screen you will only find on a counterfeit phone.
Your phone is absolutely fake
no way to flash a different rom or anything?
Torroth said:
no way to flash a different rom or anything?
Click to expand...
Click to collapse
I have never heard of anyone flashing a different ROM on a counterfeit phone.
I would not even recomend you use it.
Everything about it is inferior to the real thing.
What I would do with it is destroy it.
Hi,
I have a problem with Samsung ATIV S, if possible i would like to solve.
During the start-up phase, when the logo appears, you see the writing "Not For Resale" at the bottom left,
does anyone know if it can be solved?
Thanks in advance to everyone
It is boot loader unlocked?
Yes, It has unlocked, is it possible to solve?
Relock bootloader
I re-locked the bootloader but unfortunately the problem remains
Anyone has news about this problem? Thanks
paljamp said:
Hi,
I have a problem with Samsung ATIV S, if possible i would like to solve.
During the start-up phase, when the logo appears, you see the writing "Not For Resale" at the bottom left,
does anyone know if it can be solved?
Thanks in advance to everyone
Click to expand...
Click to collapse
That's an engineering model. Probably.
DO NOT REFLASH IT. You won't get that text back again for sure. Keep it safe - but I'm probably late.
Reflash with WDRT probably or thor2. I just noticed this is often.
EDIT 4: Or live as is, maybe.
EDIT 5: you have to live as is - you can reflash with the so-called "SMD downloader" but I never owned Windows phones other than Lumias, so won't be able to help much. If you wanna take a shot - you decide:
EDIT 6: if you brick - it was your idea.
no111one said:
That's an engineering model. Probably.
Click to expand...
Click to collapse
Hi, thanks for the video guide, I already knew how to flash the phone I've done it many times the reflash but it doesn't solve anything. windows phones are no longer needed, they can only be used as a paperweight or as an alarm clock. Thanks, bye bye
Hi there,
after flashing an ebw version (since there seems to be no androind 10 ua version) on my v405ua i get this error/warning message everytime i boot up the phone, which says "current Version is not available for user. Can't find matched carrier. Check NT-Code ....."
How do i fix this Warning ? Since basically everything seems to work as usual, my lte wifi 5 etc. all work just fine. Except for when im in the NL i cant get an internet connection through the mobile network, is says something is wrong with my apn settings.
Help is much appreciated, and thanks in advance.
Gurkenbeat said:
Hi there,
after flashing an ebw version (since there seems to be no androind 10 ua version) on my v405ua i get this error/warning message everytime i boot up the phone, which says "current Version is not available for user. Can't find matched carrier. Check NT-Code ....."
How do i fix this Warning ? Since basically everything seems to work as usual, my lte wifi 5 etc. all work just fine. Except for when im in the NL i cant get an internet connection through the mobile network, is says something is wrong with my apn settings.
Help is much appreciated, and thanks in advance.
Click to expand...
Click to collapse
The NT-Error code thing has been discussed quite a bit, as it's very common to anyone that has cross-flashed. There are various things people have done and some have worked for some, but not others.
First, it's not a problem, it's just something that shows up when u boot up, after that it's inconsequential. *But*, I found that if I did a Lgup partition DL of the rom (that I wanted to cross flash to), let it boot up, then shut it off. Then do a 'Refurbish' with the exact same rom. Then I'd no longer have the NT-Error code show up.
As far as the mobile data goes, just verify what the apn settings should be, it may be as simple as that.
cheers
Would a "reflash" to an ua version solve the problem ?
for example there seems to be a verizon version of the 405ua available, would that solve the nt warning ?
Gurkenbeat said:
Would a "reflash" to an ua version solve the problem ?
for example there seems to be a verizon version of the 405ua available, would that solve the nt warning ?
Click to expand...
Click to collapse
No
AsItLies said:
The NT-Error code thing has been discussed quite a bit, as it's very common to anyone that has cross-flashed. There are various things people have done and some have worked for some, but not others.
First, it's not a problem, it's just something that shows up when u boot up, after that it's inconsequential. *But*, I found that if I did a Lgup partition DL of the rom (that I wanted to cross flash to), let it boot up, then shut it off. Then do a 'Refurbish' with the exact same rom. Then I'd no longer have the NT-Error code show up.
As far as the mobile data goes, just verify what the apn settings should be, it may be as simple as that.
cheers
Click to expand...
Click to collapse
Unfortunatley, this didn't work for me but I'm planning on LOS where the error goes away. I just wonder if this causes my SafetyNet to fail?
FreeSoftwareServers said:
Unfortunatley, this didn't work for me but I'm planning on LOS where the error goes away. I just wonder if this causes my SafetyNet to fail?
Click to expand...
Click to collapse
No, it doesn't cause safetynet to fail, they are completely different things.
AsItLies said:
The NT-Error code thing has been discussed quite a bit, as it's very common to anyone that has cross-flashed. There are various things people have done and some have worked for some, but not others.
First, it's not a problem, it's just something that shows up when u boot up, after that it's inconsequential. *But*, I found that if I did a Lgup partition DL of the rom (that I wanted to cross flash to), let it boot up, then shut it off. Then do a 'Refurbish' with the exact same rom. Then I'd no longer have the NT-Error code show up.
As far as the mobile data goes, just verify what the apn settings should be, it may be as simple as that.
cheers
Click to expand...
Click to collapse
What partitions do I select?
blowtorchhonor said:
What partitions do I select?
Click to expand...
Click to collapse
If you're doing a part D/L select all but ftm. After it reboots, go to Lgup mode again and do a 'refurbish' with the same kdz.
Most of the time that gets rid of the nt code thing.
cheers
AsItLies said:
If you're doing a part D/L select all but ftm. After it reboots, go to Lgup mode again and do a 'refurbish' with the same kdz.
Most of the time that gets rid of the nt code thing.
cheers
Click to expand...
Click to collapse
Thank you so much for the quick reply! I flashed to the latest OPEN_EU ROM and now I can't flash back to anything else, hopefully I don't have to if the NT message can be removed.
blowtorchhonor said:
Thank you so much for the quick reply! I flashed to the latest OPEN_EU ROM and now I can't flash back to anything else, hopefully I don't have to if the NT message can be removed.
Click to expand...
Click to collapse
I was unable to do a refurbish after the DL. It said unable to cross flash V405UA to V405. Message is still present.
blowtorchhonor said:
I was unable to do a refurbish after the DL. It said unable to cross flash V405UA to V405. Message is still present.
Click to expand...
Click to collapse
When u get that crossflash issue u have to use a different version of lgup. If you look in the 'guides' forum, there will be links to (I believe it's) ver 1.16, a newer version that will work with newer versions of the roms.
cheers
AsItLies said:
When u get that crossflash issue u have to use a different version of lgup. If you look in the 'guides' forum, there will be links to (I believe it's) ver 1.16, a newer version that will work with newer versions of the roms.
cheers
Click to expand...
Click to collapse
I was using an outdated common DLL, thanks for helping me! Let's see if this works!
blowtorchhonor said:
I was using an outdated common DLL, thanks for helping me! Let's see if this works!
Click to expand...
Click to collapse
Nope
I have this message that pops up on my V450VM. I assume it was related to Navigation Gestures that I used, and loved, on my V405QA7. When activating and setting it up, my V50 downloaded Nav Gestures from backup and when the phone updated to A11 I found the app was incompatible. I deleted the app and key. Ever since, rebooting has brought up the notification and I assume something didn't delete from the app. Guess I may have been wrong. I'm living with it and it doesn't seem to cause any issues but my OCD flares everytime :/
* Disclaimer: I've only tested this on a G998B/DS Exynos S21 Ultra 5G, knox tripped and rooted with Magisk *
* DO NOT TRY ON ANY VARIANT OTHER THAN G998B/DS Exynos S21 Ultra 5G, I will be no responsible if you do *
* If it works for you on other variants, please report it so I can add it to the post, thanks *
As we all know, Samsung phones render a large, ugly disclaimers on the initials bootscreens/bootlogo when booting the phone, after it has been bootloader-unlocked (e.g. to root it via Magisk, to install TWRP, etc.)
Flashing this tweaked up_param partition on Odin will restore back a nice, clean bootscreen that won't scare the hell out of you every time you turn it on
How to install
1. Open Odin 3.14
2. Select the attached clean_bootlogo.tar into the BL box (you can use any slot, really, but suggesting BL here as a best practice)
3. Start flashing
4. Enjoy!
If you like this, leave your or thanks!
Hello there, firstly, I would like to thank you for your hard work into coming up with this, and yes it works great on my S21 Ultra Exynos G99B/DS.
I would love to suggest a feature/addon: Remove the press power button to continue text. (If it is possible)
Also just to point out, this post would get so much more attention if it was under "How To Guides" instead of "Development".
Anyways thanks you so much for your hard work
DaGalaxySheep said:
Hello there, firstly, I would like to thank you for your hard work into coming up with this, and yes it works great on my S21 Ultra Exynos G99B/DS.
I would love to suggest a feature/addon: Remove the press power button to continue text. (If it is possible)
Also just to point out, this post would get so much more attention if it was under "How To Guides" instead of "Development".
Anyways thanks you so much for your hard work
Click to expand...
Click to collapse
I intentionally left the "press the power button..." text on the screen, because once the bootloader is unlocked, and the phone takes you thru these screens, it will wait those ~8 seconds on that screen, unless you press the pwr button. So leaving there, lets the end user know they can skip it and get the system booted up faster.
However, I'll upload another version without the label
Works a treat bud! Thanks!
Thank you so much
rodrigofd said:
I intentionally left the "press the power button..." text on the screen, because once the bootloader is unlocked, and the phone takes you thru these screens, it will wait those ~8 seconds on that screen, unless you press the pwr button. So leaving there, lets the end user know they can skip it and get the system booted up faster.
However, I'll upload another version without the label
Click to expand...
Click to collapse
Hi has the version without the label been posted?
AAAAAA help me By mistake i flash it to SM-G996B/DS
My phone cant boot now, PC cant detect it.
It is possible to charge it but its drain battery continuously
So can I somehow recover my hard bricked s21+?
rodrigofd said:
* Disclaimer: I've only tested this on a G998B/DS Exynos S21 Ultra 5G, knox tripped and rooted with Magisk *
* DO NOT TRY ON ANY VARIANT OTHER THAN G998B/DS Exynos S21 Ultra 5G, I will be no responsible if you do *
* If it works for you on other variants, please report it so I can add it to the post, thanks *
As we all know, Samsung phones render a large, ugly disclaimers on the initials bootscreens/bootlogo when booting the phone, after it has been bootloader-unlocked (e.g. to root it via Magisk, to install TWRP, etc.)
Flashing this tweaked up_param partition on Odin will restore back a nice, clean bootscreen that won't scare the hell out of you every time you turn it on
How to install
1. Open Odin 3.14
2. Select the attached clean_bootlogo.tar into the BL box (you can use any slot, really, but suggesting BL here as a best practice)
3. Start flashing
4. Enjoy!
If you like this, leave your or thanks!
Click to expand...
Click to collapse
Hey buddy thank you so much for creating this... It is really scary indeed every time we boot to see that fear mongering screen.
I also wanted to ask if you have created the version without the "press the power button screen". Although I am not sure if it possible to bypass that 8 second screen.
Thank you and I hope you are well!
Ziomus said:
AAAAAA help me By mistake i flash it to SM-G996B/DS
My phone cant boot now, PC cant detect it.
It is possible to charge it but its drain battery continuously
So can I somehow recover my hard bricked s21+?
Click to expand...
Click to collapse
Did you manage to overcome it and fix your phone?
Yep, i send it to warranty. It is back to me with new motherboard, also new backplate without imei number on it.
Haha phone was knox 0x0 with new mobo
Just for one Day XD
So this file break hardware in other models xddd
Whole repair took 9 days.
Ziomus said:
Yep, i send it to warranty. It is back to me with new motherboard, also new backplate without imei number on it.
Haha phone was knox 0x0 with new mobo
Just for one Day XD
So this file break hardware in other models xddd
Whole repair took 9 days.
Click to expand...
Click to collapse
Well i'm glad it all worked out bud
I do know how to fix these warning images...
Is it okay to do it like this:
Edit param.bin (or up_param.bin)
Compress the bin file to a .img file instead of .tar file and flash it in TWRP, not Odin
TESTED!, THIS PARAM FILE WORKS NICELY ON ALL GALAXY S20 SERIES TOO.
Is there a similar fix available for the regular S21 G991B
mrao said:
Is there a similar fix available for the regular S21 G991B
Click to expand...
Click to collapse
You should ask that in a thread there... The dev. of this mod here has disappeared from the face of XDA for a long time now, and no one else will answer here unfortunately.
Is it possible to customize the boot logo? (e.g. place own one instead "Samsung Galaxy")
Ziomus said:
Yep, i send it to warranty. It is back to me with new motherboard, also new backplate without imei number on it.
Haha phone was knox 0x0 with new mobo
Just for one Day XD
So this file break hardware in other models xddd
Whole repair took 9 days.
Click to expand...
Click to collapse
Here the same .. flashing seems be fine but directly after reboot black screen of death …. Buttons doesn’t react on any combination seems is death lol … also Samsung smart switch doesn’t see the phone anymore no change too reflash it back …
Samsung s21 send back for warranty 4 days old lol
MichelH1973 said:
Here the same .. flashing seems be fine but directly after reboot black screen of death …. Buttons doesn’t react on any combination seems is death lol … also Samsung smart switch doesn’t see the phone anymore no change too reflash it back …
Samsung s21 send back for warranty 4 days old lol
Click to expand...
Click to collapse
Strange, could you post all the steps of what you did to reach a brick?
It must be something wrong you did at some point and it went sideways, or you just missed something?
babyboy3265 said:
Strange, could you post all the steps of what you did to reach a brick?
It must be something wrong you did at some point and it went sideways, or you just missed something?
Click to expand...
Click to collapse
I downloaded this tar file , reboot my phone in download mode insert in BL slot the tar file start enable reboot boem phone was death … really nothing more
How hard would it be to port this to the G998U?
MichelH1973 said:
I downloaded this tar file , reboot my phone in download mode insert in BL slot the tar file start enable reboot boem phone was death … really nothing more
Click to expand...
Click to collapse
So you had you bootloader unlocked, you were rooted and etc?
UPDATE AS OF 16 OF MAY 2023
This project isn't working right now, but I am still working on it.
However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get to functional state.
If anyone has any idea please contact me, any hell is welcome!
______________________________________________________
Hi!
So I decided I wanted to flash custom software into my phone, but it's bootloader was locked so I figure a way to unlock it!
I am going to leave 2 methods:
1. It's the most risky but has more chance of working. The idea is to flash the whole firmware again to the phone, but from an unlocked model.
This is posible using the EDL mode and Sahara protocol.
The EDL mode is an emergency mode which allows user to flash firmware in case fastboot and ADB fails. It's also available in all Qualcomm devices.
It is also completly independent from the rest of the phone, and it's the first bootloader we have. If everything is ok it triggers the second bootloader(fastboot) which then boots the system(See the diagram if you want).
As we want to reflash the firmware keep in mind this could brick your phone and I won't take any resposability if it happen
Materials:
-QPST
-Qualcomm Driver
-Working USB Cable
-Fastboot and ADB set up and working
-knoledge on using ADB
Procedure:
1. Download and install Qualcomm drivers
2. Download and install QPST
4.Downlaod the MBN file
3. Reboot
4. Connect the phone to the PC, then open cmd and run "adb reboot edl".
If you are on fastboot mode, then try "fastboot oem edl", "fastboot reboot-edl", "fastboot reboot edl". One of this should work
5. Go to C:\Program Files\Qualcomm\QPST\bin\
6.Open QPST Config(it's a blue phone, see picture)
7. Click on "Start clients" and then "Software download". A new window should open
8. Now we need to select the phone image using the browser button
9. Click on start to flash ⚡️
Please be aware the method wasn't tested, so this could brick your phone.
If you decide to try it, and have questions or ru into problems during the process, please let me know.
Also remember to take a backup of your data, as it is goig to be lost. ℹ
____________________________________________________________________________
As for the second method, I tried it and it didn't work for me, but is completly safe so you may want to give it a try.
1. Enrrol on the android 12 beta program, AND MAKE A BACKUP OF YOUR DATA
2. Install the update
3. Now exit from the beta program
4. Now you should have an update, it's a rollback to the stable version of android 12. After you installed the update the phone will restart and factory reset.
5. Do the setup as normal
In the end you may have unlocked the bootloader, to check just go to developer options and check if it is enabled or not.
Can we get a video of how to do this?
trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
So you attempted one of these methods and did it work or not work.What device did you use?
trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
That seems to be a probelm with the drivers. Did you install everything properly?
You may want to uninstall them and reinstall again to see if we solve the problem. Also try to run the app with admin privileges
Let me know how if you have more issues or if this doesn;t solve the problem at all.
AtrixHDMan said:
Can we get a video of how to do this?
Click to expand...
Click to collapse
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
#mcl said:
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
Click to expand...
Click to collapse
I understand thanks
#mcl said:
这似乎是驱动程序的问题。您是否正确安装了所有内容？
您可能需要卸载它们并重新安装，看看我们是否能解决问题。还尝试以管理员权限运行该应用程序
如果您有更多问题，或者这根本无法解决问题，请告诉我
MOD EDIT: You may need to uninstall them and reinstall to see if we can fix the problem. Also tried running the app with admin rights
Let me know if you have more questions, or if this doesn't solve the problem at all.
Click to expand...
Click to collapse
同样的问题，无法解决。
MOD Edit: Same problem, can't solve it.
Looks like this is a common issue, I will look the documentation of QPST and see if I see the cause of the problem. Thank you guys for helping up this project
So I found that that version of QPST is outdated(it's the 2.7 build 140 and the latest version is 2.7 build 460). I am leaving a zip with it here.
Try and see if this time around we manage to unlock the bootloader
MOD EDIT:
This is the latest version
这是最新版本
#mcl, I have the same problem as you have, I live in Portugal and bought a used Pixel 4 but apparently it's origin is the US, Verizon. From your original post I take it that you didn't try this method yourself and hope others will try? Or were you successful?
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
gentle_giant said:
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
Click to expand...
Click to collapse
Hey I am quite busy recently so I haven't really had time to look more on the thread, though I believe there will always be a way, it may be hard to find but no OS is perfect, and Android is no exception. As it turns out, even if this method worked, when it connect to the internet there will be a high chance that using the IMEI of the phone it will "remember" it's a locked model and won't allow you to flash new firmware.
However I am working on a new method, which is also safer, though I have still work to do, so when It is ready I am going to publish another guide.
Good luck all untill them
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
gentle_giant said:
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
Click to expand...
Click to collapse
Hahah yeah we are definitely neighbors.
Well I do want to become a software engineer though right now I am just a busy enthusiastic.
I also really enjoy custom OS, when I had my Galaxy S9 I used to have custom ROMs.
Hope I manage to find a new solution as soon as posible for all if you guys!!!
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
any luck with that? can I backup my firmware before doing it?
darknmy said:
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
Click to expand...
Click to collapse
We are not doing physical atack, so that is not a problem for us.
Also, I don't believe the pixel 4 XL is perfect, for sure there are errors and security vulnerabilities. We just need to find them.