Related
Hello, first timer here. I have never tried rooting or anything, but today I finally decided to... and messed it up.
Verizon Samsung Note 2 SCH-i605 (yes, still.)
Got it on July 2nd, 2013, so I believe it was build 4.1.1 kernel 3.1? Not too sure on the legalities
Completely unrooted and unmodded
I was using kingo root and everything was fine until it hit about 52% on the rooting process when my computer lost connection with my phone. Since, it gave me the "Firmware upgrade encountered an issue" problem. So then I google-fu'd and followed directions of:
http://forum.xda-developers.com/showthread.php?t=2040264
http://forum.xda-developers.com/showthread.php?t=2120726
http://forum.xda-developers.com/showthread.php?t=2582290
http://forum.xda-developers.com/showthread.php?t=2024207
etc.
and used Odin 3.10.7 (and 3.10.0 just in case, both on and off admin mode cause why not) on every single md5 available in all those links and the one from sammobile.com for sch-i605.
And each time, I would either received failure on "sboot.bin" or receive the "System Software Not Authorized" error if succeeded (it was stuck in bootload? too, kept flashing the logo then the error message). The VERY first time, however, it actually brought me to that page where I'm allowed to press things like erase cache, factory reset, or reboot my phone. There, I chose all those options in the order I've listed them. And ever since I haven't seen that screen again.
My issue seems to be every problem I can find put together, and can't seem to resolve it with my skills alone. I honestly don't care about recovering my data (which I believe is impossible now anyway) or rooting my phone. I just want it to turn on again.
Thanks in advance.
p.s. getting a new phone isn't an option currently
-edit-
Checked my verizon wireless software upgrade assistant for some info, and it says "Up to date" and "Version ND3" if that means anything to you pros out there.
jk1982 said:
Hello, first timer here. I have never tried rooting or anything, but today I finally decided to... and messed it up.
Verizon Samsung Note 2 SCH-i605 (yes, still.)
Got it on July 2nd, 2013, so I believe it was build 4.1.1 kernel 3.1? Not too sure on the legalities
Completely unrooted and unmodded
I was using kingo root and everything was fine until it hit about 52% on the rooting process when my computer lost connection with my phone. Since, it gave me the "Firmware upgrade encountered an issue" problem. So then I google-fu'd and followed directions of:
http://forum.xda-developers.com/showthread.php?t=2040264
http://forum.xda-developers.com/showthread.php?t=2120726
http://forum.xda-developers.com/showthread.php?t=2582290
http://forum.xda-developers.com/showthread.php?t=2024207
etc.
and used Odin 3.10.7 (and 3.10.0 just in case, both on and off admin mode cause why not) on every single md5 available in all those links and the one from sammobile.com for sch-i605.
And each time, I would either received failure on "sboot.bin" or receive the "System Software Not Authorized" error if succeeded (it was stuck in bootload? too, kept flashing the logo then the error message). The VERY first time, however, it actually brought me to that page where I'm allowed to press things like erase cache, factory reset, or reboot my phone. There, I chose all those options in the order I've listed them. And ever since I haven't seen that screen again.
My issue seems to be every problem I can find put together, and can't seem to resolve it with my skills alone. I honestly don't care about recovering my data (which I believe is impossible now anyway) or rooting my phone. I just want it to turn on again.
Thanks in advance.
p.s. getting a new phone isn't an option currently
-edit-
Checked my verizon wireless software upgrade assistant for some info, and it says "Up to date" and "Version ND3" if that means anything to you pros out there.
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the best possible assistance, I'm going to move this thread to your device's Q&A forum. Good luck!
install kies and try flashing rom. do you have rom from i.e. sammobile? use different odin versions and do not mark repartition
yaro666 said:
install kies and try flashing rom. do you have rom from i.e. sammobile? use different odin versions and do not mark repartition
Click to expand...
Click to collapse
KIES is unable to read my phone (tried the bottom 3 versions of it), and I've tried running Odin 3.07 and unchecked repartition for every stock and restore md5s I had for my phone... the ones that didn't fail sboot.bin are still giving me unauthorized error.
I'll keep trying all the combinations, but it seems moot at this point.
First things first. I surrender. I'm a noob with android. I had windows phone previously and only now came to android.
Here's the scenario:
1. My z2 force was properly rooted with magisk and twrp. I followed the guide in xda only.
2. My device was brought from India so carriers like sprint, t-mobile are not applicable I think.
What I Did:
0. Wanted to unroot my device. So, I decided to first uninstall the modules in magisk that I had installed.
1. Tried to uninstall magisk modules and rebooted from the magisk application.
2. Got into Boot loop, so went to recovery mod and wiped everything. Hard reset was done.
3. Installed magisk app again and clicked uninstall to remove root. I wanted to install the latest security update. Update kept failing so I decided to unroot. I choose uninstall completely option.
4. Rebooted the phone manually after clicking uninstall in magisk manager. Using the 'root checker' app I checked if unrooting was successful but it said, 'root was not properly installed' or something like that. So, I installed magisk manager again and again uninstalled root completely.
5. Still same issue. Root checker said the same thing again. So, installed magisk manager again and this time I wanted to remove root using ES file manager as I saw in an online guide. But I couldn't give it root permission because it was not properly installed as said by root checker. So, I decided to root my phone properly but stupid me, clicked 'install' in magisk manager and chose the recommended option (don't remember exactly what it was). It downloaded magisk zip and did some changes and asked to reboot. After rebooting, my phone went straight to the black screen with an android icon and 'no command' written below it. It kept going there again and again.
6. I assume that is the recovery mode. I press volume up and power button and choose the wipe everything again(Like I did before) to hard reset phone. Wiping was successful but it still kept booting to that black screen.
Additional Info:
1. Phone wasn't carrier version. It was bought in India. It is running Oreo 8.0.
2. In bootloader menu : (Not stating all)
BL: MBM-3.0-nash_retail-641a15b-180306
Product/Variant: nask xt1789-06 64GB PVT
Console[NULL] :null
Tools Mode Config: DISABLED
Power OK
flashing_unlocked
Software Status : Modified
Transfer Mode : USB Connected.
3. Yes, Bootloader menu is accessible.
4. Choosing recovery mode in bootloader menu reboots phone and takes me to that blank screen I mentioned before.
5. Connecting to USB to my PC when in bootloader menu, it connects as 'Fastboot nash S'. ADB terminal says no devices found.
What I want:
1. Boot into OS.
2. Remove root completely so I can install system update.
Please help or offer suggestions as I do not have a secondary device with me. If I have to absolutely go to a service center, I will.
You should flash it back to stock.
You posted that your phone is nash xt1789-06 64GB PVT, you can grab the latest firmware here.
The flashing instructions are here in post #5, and any question you might have is most likely answered in that thread.
Just download the firmware, boot into bootloader mode, and follow the instructions.
FYI in fastboot mode adb commands don't work, it's fastboot. To verify that you're connected and ready type
Code:
fastboot devices
and you should see your serial# like you do in adb.
That should put you back to stock and good to go.
41rw4lk said:
You should flash it back to stock.
You posted that your phone is nash xt1789-06 64GB PVT, you can grab the latest firmware here.
The flashing instructions are here in post #5, and any question you might have is most likely answered in that thread.
Just download the firmware, boot into bootloader mode, and follow the instructions.
FYI in fastboot mode adb commands don't work, it's fastboot. To verify that you're connected and ready type
Code:
fastboot devices
and you should see your serial# like you do in adb.
That should put you back to stock and good to go.
Click to expand...
Click to collapse
Thank you for the reply. I figured it out and went ahead with it. But now, I'm not seeing the May security update. The device shows it has March update and that no other update is available. Any idea why? Also, root checker still says 'root not properly installed'. How to unroot completely? Thanks a lot!
Sparkzz27 said:
You should flash it back to stock.
You posted that your phone is nash xt1789-06 64GB PVT, you can grab the latest firmware here.
The flashing instructions are here in post #5, and any question you might have is most likely answered in that thread.
Just download the firmware, boot into bootloader mode, and follow the instructions.
FYI in fastboot mode adb commands don't work, it's fastboot. To verify that you're connected and ready type
Thank you for the reply. I figured it out and went ahead with it. But now, I'm not seeing the May security update. The device shows it has March update and that no other update is available. Any idea why? Also, root checker still says 'root not properly installed'. How to unroot completely? Thanks a lot!
Click to expand...
Click to collapse
Did you look to see if the May Security Update has been released for your specific device? When you downloaded the stock firmware did you look to see what month security patch it contained? Have you tried to perform a system update to see if you can OTA to the latest security patch?
Now, if you completely flashed back to stock then root is removed. Root checker says that because root access is not installed at all. Flashing back to stock removes any trace of root, IIRC.
Sent from my Moto Z2 Force using XDA Labs
Don't forget, if you followed the flashing instructions from the other post they were omitting the gpt.bin and bootloader. So if you didn't flash those then that's why you're probably not seeing any updates, you need to be on full stock all matched up. Just reflash the firmware you downloaded in its entirety. @fast69mopar is right, once you flash a new boot.img root is gone, and since you flashed back to stock it's definitely gone.
Sparkzz27 said:
Thank you for the reply. I figured it out and went ahead with it. But now, I'm not seeing the May security update. The device shows it has March update and that no other update is available. Any idea why? Also, root checker still says 'root not properly installed'. How to unroot completely? Thanks a lot!
Click to expand...
Click to collapse
If you flash with factory image you should be unroot completely and root checker will keep telling you "root not properly installed" if you are not rooted just ignore root checker if you not planning to be rooted.
Hi there I have a xt1789-06 I was not getting updates and flashed the first Oreo update from here https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/
My phone now does the updates and everything works fine.
However I did try to flash a custom ROM and root I made a mistake and ended up both a hard brick, because I was on Oreo I thought that flashing the Oreo blank flash would rectify the problem, but it was not working so I tried flashing the N blank flash and it worked.
I've come from using Samsung phones so I'm use to Odin and have not used fastboot commands. After reading many threads I know what I had done was not decrypting my device which ended up with a hard brick I will in the future flash a custom ROM now I know a little bit more.
Blank flash files are here
https://mirrors.lolinet.com/firmware/moto/nash/blankflash/
Then once back to fastboot flash the flash all from the link at the top of my post.
41rw4lk said:
Don't forget, if you followed the flashing instructions from the other post they were omitting the gpt.bin and bootloader. So if you didn't flash those then that's why you're probably not seeing any updates, you need to be on full stock all matched up. Just reflash the firmware you downloaded in its entirety. @fast69mopar is right, once you flash a new boot.img root is gone, and since you flashed back to stock it's definitely gone.
Click to expand...
Click to collapse
Hi, sorry I was busy with work. I managed to use my phone that way. I didn't use the instructions in that post. Instead, I download flashallutilities (In how to return to stock post in xda for z2 force), then ran the batch file which did all the work. I noticed other problems too,
1. My Jio sim(4g LTE) does not show 'enhanced LTE mode' in options. Also when I call someone, it fails immediately saying 'call failed. try another method.' However, internet connection works from the sim. My other sim works fine for calls and data.
2. I'm seeing other keyboards in manage keyboards section. I don't recall seeing google pinyin input, zhuyin input, etc before. What's worse is my office's app shows option to switch to chinese version of the website for logging in. My language and time zone are set correctly though - English India and GMT +5:30.
3. The web browser I used before couldn't be found in the play store anymore. My launcher still shows the icon with a green arrow in left bottom of the icon to direct me to playstore to download it but playstore says item not found. The app name is simply 'browser'. I searched for it on desktop website too (without logging in), still couldn't find it. Guess it's a coincidence,
Also: Herehttps://www.getdroidtips.com/moto-z2-z2-play-z2-force-stock-rom/#Moto_Z2_Force_Android_80_Oreo_Firmware, the carrier global version says 'OCX' instead of 'OPX'. Any idead about that?
Sparkzz27 said:
Hi, sorry I was busy with work. I managed to use my phone that way. I didn't use the instructions in that post. Instead, I download flashallutilities (In how to return to stock post in xda for z2 force), then ran the batch file which did all the work. I noticed other problems too,
1. My Jio sim(4g LTE) does not show 'enhanced LTE mode' in options. Also when I call someone, it fails immediately saying 'call failed. try another method.' However, internet connection works from the sim. My other sim works fine for calls and data.
2. I'm seeing other keyboards in manage keyboards section. I don't recall seeing google pinyin input, zhuyin input, etc before. What's worse is my office's app shows option to switch to chinese version of the website for logging in. My language and time zone are set correctly though - English India and GMT +5:30.
3. The web browser I used before couldn't be found in the play store anymore. My launcher still shows the icon with a green arrow in left bottom of the icon to direct me to playstore to download it but playstore says item not found. The app name is simply 'browser'. I searched for it on desktop website too (without logging in), still couldn't find it. Guess it's a coincidence,
Also: Herehttps://www.getdroidtips.com/moto-z2-z2-play-z2-force-stock-rom/#Moto_Z2_Force_Android_80_Oreo_Firmware, the carrier global version says 'OCX' instead of 'OPX'. Any idead about that?
Click to expand...
Click to collapse
Your Z2 is a xt1789-06 correct? It's an international version, the flashall in the utilities zip from the return to stock thread is for US based phones, TMO and Sprint specifically. What was or wasn't flashed using that flashall I couldn't tell you, I don't have an international phone. That's why I linked to the post that deals with that version of the Z2 and has all the answers and links you need to sort your phone. Others in that thread might be better suited to help you along. This is the thread that deals with the xt1789-06.
As for calling and sim, might be related to how you flashed or simply an apn issue. You can go to network settings, mobile, access point names, and reset those to default. That should pull the apns from your sim so you'll have the correct apns.
As for keyboards and browsers, I don't know what is included in the international stock versions, but they are subject to change based on initial setup/default language and rom version. As for the OCX vs OPX, I'm not sure what the difference is. I know 'O' is for Oreo but for the rest I don't know. Maybe one is gsm one is cdma? I don't know. I do know that the thread I linked to will have more info and be able to help you better since it's for your version of the Z2. Sorry I can't help you more, but post any questions you have over there and they should be able to sort you out.
Greetings,
General
I've been all over the Internet trying to gain access to more information about how to repair my LG G4. Well... Let's start from the beginning.
Story
I have an LG G4, it's old and I've had it for over 4-5 years now... I can't exactly remember how long I had it for. It still works, just needs a new battery and cable (cats chewed the cable and batteries don't last when you forget to disconnect them from the device, leave it plugged in for weeks and let it completely die for longer then a week).
I recently saw a video about the Pine phone and the fact that it was able to run a linux mobile distribution and when I looked into installing a custom OS into LG G4, it was possible... If I manually ported it myself.
I actually got fairly far using my Xubuntu system with configuring and compiling, the trouble I ran into was that I couldn't root or fastboot my device.
So, now here's where the problem began, I have a LG G4 factory reset and when I load up the Recovery mode, it brings up the android guy with their chest open and an exclamation mark in a yellow triangle, no message. After attempting to boot into recovery mode, I wait a little while and the phone automatically resets back to normal. When I use ADB to force the phone into fast boot, it skips it and starts the phone normally.
Now I'm on a mission to find a way to either fix the boot or flash the firmware (in hopes that it fixes the boot/recovery).
I have already tried:
Installing LGFlashTool
Versions, 2.0.1.6, 2.0.1.9, Year: 2014 and 2.0.2.5. Other than year 2014, the other ones were installed from LGFlashTool.com
Since Xubuntu can't run these files properly, I just ran them on my wife's Windows computer
I installed the LG Mobile Drivers and LGFlashTool had registered that it was the correct DLL but, it didn't seem to find the phone
Year 2014 LGFlashTool had found the phone but, I may have had the incorrect kdz file.
The Flash starts and the phone goes to firmware update, but the phone stops at zero and sits there while the program crashes saying that there was an error (in which no means to read, understand or locate the description of this error) and to try again by unplugging and removing the battery.
This version was downloaded from xda-developers.com
Conclusion
Once I can get into fastboot, I'll be able to root my phone and attempt to install the mobile OS I have ready.
Otherwise, I think I might be able to install a microSD card with the OS but, I don't think that will work if I can't get into the option to boot from a separate location (I believe that's called fastboot). But, then again... I think the phone needs to be rooted first... Then that brings me to the previous issue.
Details and Information
The phone details (as far as I see) are:
When I remove the battery I can see:
FCC ID: ZMFH810
IC ID: 2703C-H812
Model Number: LG-H812
I'm not exactly sure what KDZ file I got but the name is: PR H810PR10a_02.kdz, I also have the _04.kdz
I'm using H815 as my compile for the mobile OS, I may switch to H810 when I get back to that point.
Useless information: I still have the original leather backing... Removed from the phone because I didn't like it. If I find it, I can ship it to someone.
That's about it... I am very terrible about research and using Google properly (I have no idea why, I think it's a terrible flaw to have but, I have it). So, if you find the solution by typing words I didn't use or finding a similar post, I am very sorry. Hope I have everything posted here to help solve the issue, linking to posts that can resolve the issue or posting questions on what I might be missing will help.
Thanks in advance for the support of this community,
Lilrock
Lilrock said:
Greetings,
General
I've been all over the Internet trying to gain access to more information about how to repair my LG G4. Well... Let's start from the beginning.
Story
I have an LG G4, it's old and I've had it for over 4-5 years now... I can't exactly remember how long I had it for. It still works, just needs a new battery and cable (cats chewed the cable and batteries don't last when you forget to disconnect them from the device, leave it plugged in for weeks and let it completely die for longer then a week).
I recently saw a video about the Pine phone and the fact that it was able to run a linux mobile distribution and when I looked into installing a custom OS into LG G4, it was possible... If I manually ported it myself.
I actually got fairly far using my Xubuntu system with configuring and compiling, the trouble I ran into was that I couldn't root or fastboot my device.
So, now here's where the problem began, I have a LG G4 factory reset and when I load up the Recovery mode, it brings up the android guy with their chest open and an exclamation mark in a yellow triangle, no message. After attempting to boot into recovery mode, I wait a little while and the phone automatically resets back to normal. When I use ADB to force the phone into fast boot, it skips it and starts the phone normally.
Now I'm on a mission to find a way to either fix the boot or flash the firmware (in hopes that it fixes the boot/recovery).
I have already tried:
Installing LGFlashTool
Versions, 2.0.1.6, 2.0.1.9, Year: 2014 and 2.0.2.5. Other than year 2014, the other ones were installed from LGFlashTool.com
Since Xubuntu can't run these files properly, I just ran them on my wife's Windows computer
I installed the LG Mobile Drivers and LGFlashTool had registered that it was the correct DLL but, it didn't seem to find the phone
Year 2014 LGFlashTool had found the phone but, I may have had the incorrect kdz file.
The Flash starts and the phone goes to firmware update, but the phone stops at zero and sits there while the program crashes saying that there was an error (in which no means to read, understand or locate the description of this error) and to try again by unplugging and removing the battery.
This version was downloaded from xda-developers.com
Conclusion
Once I can get into fastboot, I'll be able to root my phone and attempt to install the mobile OS I have ready.
Otherwise, I think I might be able to install a microSD card with the OS but, I don't think that will work if I can't get into the option to boot from a separate location (I believe that's called fastboot). But, then again... I think the phone needs to be rooted first... Then that brings me to the previous issue.
Details and Information
The phone details (as far as I see) are:
When I remove the battery I can see:
FCC ID: ZMFH810
IC ID: 2703C-H812
Model Number: LG-H812
I'm not exactly sure what KDZ file I got but the name is: PR H810PR10a_02.kdz, I also have the _04.kdz
I'm using H815 as my compile for the mobile OS, I may switch to H810 when I get back to that point.
Useless information: I still have the original leather backing... Removed from the phone because I didn't like it. If I find it, I can ship it to someone.
That's about it... I am very terrible about research and using Google properly (I have no idea why, I think it's a terrible flaw to have but, I have it). So, if you find the solution by typing words I didn't use or finding a similar post, I am very sorry. Hope I have everything posted here to help solve the issue, linking to posts that can resolve the issue or posting questions on what I might be missing will help.
Thanks in advance for the support of this community,
Lilrock
Click to expand...
Click to collapse
Well first of all you need to unlock your phone. H812 can't be unlocked officially though. Check my sig for the only unofficial one. Once unlocked you can flash custom ROMs but first of all you should read about ARB (antirollback) also in my sig and ensure you understand the risks all this brings. Gl.
steadfasterX said:
Well first of all you need to unlock your phone. H812 can't be unlocked officially though. Check my sig for the only unofficial one. Once unlocked you can flash custom ROMs but first of all you should read about ARB (antirollback) also in my sig and ensure you understand the risks all this brings. Gl.
Click to expand...
Click to collapse
Thanks for the positive feedback, I will attempt to fix my phone with your solution. This phone is technically almost garbage and when I fully update the phone, it runs like trash. So, if I can install a custom ROM, it may run a little better or have the tools I would personally like in a phone.
I'll let you know the details of my attempt,
Lilrock
You might be able to use:
GitHub - Lekensteyn/lglaf: LG Download Mode utility and documentation
LG Download Mode utility and documentation. Contribute to Lekensteyn/lglaf development by creating an account on GitHub.
github.com
It is more reliable then the factory tools when it works.
SkewedZeppelin said:
You might be able to use:
GitHub - Lekensteyn/lglaf: LG Download Mode utility and documentation
LG Download Mode utility and documentation. Contribute to Lekensteyn/lglaf development by creating an account on GitHub.
github.com
It is more reliable then the factory tools when it works.
Click to expand...
Click to collapse
Which is included in mAid (https://maid.binbash.rocks).. ... Even with a UI...
Thank you very much with your support. I was able to unlock, bootloader and install the image installer.
I'm on the verge of compiling and installing Ubuntu Touch on my LG G4 H812.
Hope you guys proceed with everything you're doing right!
Hi, I'm new to the forum and was wondering if someone could help me just clarify a few things specific to my S9 that I am trying to remove frp from.After trying a lot of the youtube guides on bypassing the FRP using the "easy tools" and failing I thought of reflashing the OS. Since that doesn't exactly just work and you need a combination file, I was looking to figure out what combo file I need. The number from recovery menu is 10/QP1A.###/G960WVLS7ETH1 and the IC on the back of the phone is 649E-SMG960U.I found a tutorial saying you can make the combination file from the official firmware, but after getting that from SamMobile I could not find the sboot.bin.Iz4 in BL section. Then I tried looking online for a faster download of my firmware but none had the exact numbers right or the correct files in BL. (They had the right Ap files though). I also tried looking for a combo file directly but the same problem is I don't know the exact numbers/version that I need to make sure its correct for me to apply it into ODIN.I found a few links to combo files but they are all usually for android 8
Samsung SM-G960W Combination File ROM (Flash File)
Download Samsung SM-G960W Combination File (original flash file, rom) without any password for Free. We also provide the combination file for all Samsung devices.
samsungcombinationfile.com
Samsung Galaxy S9 SM-G960W Combination Firmware
Samsung Galaxy S9 SM-G960W Combination Firmware Samsung G960W Galaxy S9 Combination Firmware is a stable
www.full-repair-firmware.com
I just need to figure out what the software version (or baseband version?). Some threads say your phone model number must be the same and others say it only matters for the processor to be the same. Can I download the G960U files instead of a G960W or am I reading the wrong thing. Also can someone help with the bootloader version / build version. I think it is bootloader version 7 but its in place of the U that is written in most guides. and then the revision would be 1 right?Just would like some confirmation that I am looking for the right file. By what I have looked into so far the combo file with version G960U + android 8, bootloader version 7, and revision 1 will work regardless of the other numbers. or does it have to be G960W? F? X? any letter that has the same processor? Anything else I need to make sure of, is there an easier way to remove frp?Any help is appreciated, Thanks!
Update: Finally got into my frp locked S9. For anyone wondering I went with the combination file titled: COMBINATION_FAC_FA80_G960USQU7ASJ1_FACFAC_CL13230190_QB26521439_REV01_user_mid_noship_MULTI_CERT.tar that I got from the second link above.
I can conclude that the version of android does not make a difference since the combination file is simply like entering safe mode on your device. I'm not an expert but the SM-G960U file worked on SM-G960W phone and I made sure to get a file with same boot loader version and revision number, ignoring the letters that tell dates. From there I was able to OEM unlock and then reinstall the latest firmware I got from SamMobile.
Hi, I also needed to remove the google frp on my phone. I've tried so many different solutions online but nothing would work. ive tried every file in the link you've posted. a lot would Fail when it was loading it into my phone through Odin. always got Auth Fail or some other failure. some would cause infinite boot loop. some i couldnt use because it had password protection to unzip, i doubt it would have worked anyway lol.
My phones recover screen code or PDA? was G960WVLU9FUE2 I do not know what any of the letters or numbers mean after G960w, but i assume the 9 and the 2 are what are important and no files online match those numbers in the same file. I actually didnt find any combination files for U9 without needing to pay for it.
In the end i ended up just guessing the pattern password. I found a glitch that lets me keep guessing without a timer cool down. Now idk if this glitch is caused by my attempts of using these combination files then restoring it with the files from sammobile. but the glitch is easy to do.
First i did a factory reset. then when it boots up it asks to enter a network then to enter the pattern or sign into google. i dont know both so i started guessing the pattern. after a few tries it starts giving a timer cool down. I noticed you can bypass this timer by simply turning the screen off and on, then u can attempt again. when you fail the timer is still counting down from the previous attempt. like a 30 second cool down, but after screen turn off and a failed guess, the timer would be counting from like 22 seconds. then another attempt the timer would be at like 8 seconds until it resets back to 30 seconds when the timer runs out after another failed attempt.
I hope this info helps others get into their phones if Odin can't help you. Even if guessing passwords is a long tedious task.
Here's a tip for guessing node patterns. most people start from the top left corner and usually only use 5 maybe 6 nodes.
I have a Samsung A50 that all of a sudden hung and after it restarted I'm stuck in the Samsung boot screen (with the "Secure by Knox" message). There's no backup and there was no SD card in the phone (I really thought there was tbh but I recall getting it out to put it in another device).
- can't get into recovery mode
- can't get into "safe mode" or whatever it's called (which I think is obvious since it doesn't seem to go past the bootloader)
- CAN get into copy mode
So I downloaded the firmware for the model and country from Sammobile and flashed it with latest Odin version.
After the flash it said that all was OK. The phone reboots and I get stuck in the exact same screen.
I was somewhat surprised flashing the device works but it can't boot.
I put it to the side for a few days to see if there are professional recovery companies but that's quite expensive (the phone itself is not important).
Now I start doubting myself if I used the CSC or the HOME_CSC in the CSC field. Since I thought this was confusing (in linux HOME is your user directory and so at first I thought that would overwrite the user directory).
What I did now is reflash with HOME_CSC. with the idea that if the system boots it won't overwrite user directory (so personal files).
Is this already too late and the data erased even when Android didn't seem to have started? I didn't set the "repartition" flag but perhaps Odin is just extracting files from a tarbal and one specific is written to the storage that instructs android to wipe user data. So when extracting the HOME_CSC over it that file is not deleted and the wipe will still be triggered. If so is there a method to remove this file?
Does the firmware and the user files go to the same storage chip?
Anyone know where I can find the chip socket (was looking into JTAG and other tools if that's an option to do recovery with chip-off method) to know which adapter would fit?
Anyone knows what Odin does internally during the HOME_CSC/CSC step? Is it just extracting files in a filesystem?
Anyone experience with chip-off or other data recovery methods on the hardware level? (chip-off seems the "easiest")
Is there encryption on the internal storage on a Samsung A50? I think not but I might be wrong.
In a chip-off scenario is the content of the storage just a matter of mounting a filesystem (after creating an image of it)? Or is there some magic to be done that I'll probably need professional software for (I saw softwares that costs over 5k for the cheapest package).
Any advice or help is greatly appreciated!
home_is_where_the_csc_is said:
I have a Samsung A50 that all of a sudden hung and after it restarted I'm stuck in the Samsung boot screen (with the "Secure by Knox" message). There's no backup and there was no SD card in the phone (I really thought there was tbh but I recall getting it out to put it in another device).
- can't get into recovery mode
- can't get into "safe mode" or whatever it's called (which I think is obvious since it doesn't seem to go past the bootloader)
- CAN get into copy mode
Click to expand...
Click to collapse
You mean download mode maybe?
home_is_where_the_csc_is said:
So I downloaded the firmware for the model and country from Sammobile and flashed it with latest Odin version.
After the flash it said that all was OK. The phone reboots and I get stuck in the exact same screen.
I was somewhat surprised flashing the device works but it can't boot.
I put it to the side for a few days to see if there are professional recovery companies but that's quite expensive (the phone itself is not important).
Now I start doubting myself if I used the CSC or the HOME_CSC in the CSC field. Since I thought this was confusing (in linux HOME is your user directory and so at first I thought that would overwrite the user directory).
What I did now is reflash with HOME_CSC. with the idea that if the system boots it won't overwrite user directory (so personal files).
Is this already too late and the data erased even when Android didn't seem to have started? I didn't set the "repartition" flag but perhaps Odin is just extracting files from a tarbal and one specific is written to the storage that instructs android to wipe user data. So when extracting the HOME_CSC over it that file is not deleted and the wipe will still be triggered. If so is there a method to remove this file?
Does the firmware and the user files go to the same storage chip?
Anyone know where I can find the chip socket (was looking into JTAG and other tools if that's an option to do recovery with chip-off method) to know which adapter would fit?
Anyone knows what Odin does internally during the HOME_CSC/CSC step? Is it just extracting files in a filesystem?
Anyone experience with chip-off or other data recovery methods on the hardware level? (chip-off seems the "easiest")
Is there encryption on the internal storage on a Samsung A50? I think not but I might be wrong.
Click to expand...
Click to collapse
The device is encrypted by default, this is how Knox works.
home_is_where_the_csc_is said:
In a chip-off scenario is the content of the storage just a matter of mounting a filesystem (after creating an image of it)? Or is there some magic to be done that I'll probably need professional software for (I saw softwares that costs over 5k for the cheapest package).
Any advice or help is greatly appreciated!
Click to expand...
Click to collapse
If you want firstly to recover your data without having the device the ability to boot again to the system then it is not highly probable, the all you can do now is trying to flash successfully the SAME firmware that was previously onto your device and hoping that this fix it.
If you flash the same firmware and if you flash the CSC_HOME file then your userdata was not overwritten but the other CSC file contained in your firmware does that.
In case you can't boot normally after to flash the correct firmware then you should take it to a repair center, usually they either unmount/disassemble the entire motherboard or pull out/backup the data with some expensive hardware tool.
SubwayChamp said:
You mean download mode maybe?
Click to expand...
Click to collapse
That is correct.
SubwayChamp said:
The device is encrypted by default, this is how Knox works.
Click to expand...
Click to collapse
I see methods where the chip is removed from the motherboard and they read it directly with something like JTAG. So the key to decrypt is in the chip itself?
SubwayChamp said:
all you can do now is trying to flash successfully the SAME firmware that was previously onto your device and hoping that this fix it.
Click to expand...
Click to collapse
So it has to be the exact same version as well? I mean you have firmware for a specific model and carrier (or with no Carrier). However it could be e.g. 11.0 before and now 11.1 and that is blocking it from booting? (downgrading firmware is not possible though) I took the latest version for my phone since I usually update almost immediately after an update is available.
SubwayChamp said:
If you flash the same firmware and if you flash the CSC_HOME file then your userdata was not overwritten but the other CSC file contained in your firmware does that.
Click to expand...
Click to collapse
Most important question here is if I first flashed with CSC and afterwards with CSC_HOME *without* the OS booting, does it actually clear that data right away? Or only when the OS starts? Any insight on how this works internally? HOME_CSC and CSC only have a very small size diff I believe so I don't think it overwrites right away and rather writes a file that triggers the process. Any reference somewhere that explains how this piece works?
SubwayChamp said:
In case you can't boot normally after to flash the correct firmware then you should take it to a repair center, usually they either unmount/disassemble the entire motherboard or pull out/backup the data with some expensive hardware tool.
Click to expand...
Click to collapse
Samsung service center wants to replace the mainboard, other board, screen which would of course get rid of all the data (they don't open the device until you're willing to pay to repair the full device).
There are data recovery companies but they're expensive (claiming 80% successful data recovery). The local repair shop says 20% of data recovery is successful so not going to send it there and I have to pay them to do the investigation. To me these phone repair shops seem mainly doing battery, mainboard, other board, screen and camera repairs (read: replace the part). I can do most of these myself since it's hardware swap. I doubt they're any good in more advanced repairs.
I actually wonder now if it could still be the battery. The phone doesn't seem to charge anymore. The moment I disconnect the charger it powers off. Someone said power output could be too low and that's why it doesn't continue booting.
home_is_where_the_csc_is said:
That is correct.
I see methods where the chip is removed from the motherboard and they read it directly with something like JTAG. So the key to decrypt is in the chip itself?
Click to expand...
Click to collapse
Yes, this is a kind of disassemble, it needs some hardware tools to do it, and after that the data can be pulled easily to another place but the JTAG does by communicating directly to the hardware cores.
home_is_where_the_csc_is said:
So it has to be the exact same version as well? I mean you have firmware for a specific model and carrier (or with no Carrier). However it could be e.g. 11.0 before and now 11.1 and that is blocking it from booting? (downgrading firmware is not possible though) I took the latest version for my phone since I usually update almost immediately after an update is available.
Click to expand...
Click to collapse
It has to be the same build number to avoid data loss, no matter the region, can your device enter to download mode and what is the letters there in the screen?
home_is_where_the_csc_is said:
Most important question here is if I first flashed with CSC and afterwards with CSC_HOME *without* the OS booting, does it actually clear that data right away? Or only when the OS starts? Any insight on how this works internally? HOME_CSC and CSC only have a very small size diff I believe so I don't think it overwrites right away and rather writes a file that triggers the process. Any reference somewhere that explains how this piece works?
Click to expand...
Click to collapse
As I said previously the CSC_HOME doesn't overwrite that partition but the other CSC present in the firmware it does.
You can flash the CSC_HOME or simply let it blank (without flashing it)
home_is_where_the_csc_is said:
Samsung service center wants to replace the mainboard, other board, screen which would of course get rid of all the data (they don't open the device until you're willing to pay to repair the full device).
There are data recovery companies but they're expensive (claiming 80% successful data recovery). The local repair shop says 20% of data recovery is successful so not going to send it there and I have to pay them to do the investigation. To me these phone repair shops seem mainly doing battery, mainboard, other board, screen and camera repairs (read: replace the part). I can do most of these myself since it's hardware swap. I doubt they're any good in more advanced repairs.
I actually wonder now if it could still be the battery. The phone doesn't seem to charge anymore. The moment I disconnect the charger it powers off. Someone said power output could be too low and that's why it doesn't continue booting.
Click to expand...
Click to collapse
Without counting the fact that it doesn't accept charging battery I would incline to think that is a software failure, the JTAG is not so expensive, basically you wouldn't need to back up nothing while you can flash the right firmware on it and device can boot normally, the JTAG also works to can share live (revive) to a device dead and not only to pull out some data.
SubwayChamp said:
It has to be the same build number to avoid data loss, no matter the region, can your device enter to download mode and what is the letters there in the screen?
Click to expand...
Click to collapse
Yes it goes in download mode. Do you mean you want the full output?
FRP lock and OEM lock is on. Current binary: Samsung Official
CARRIER_ID: PHN
WARRANTY_VOID: 0
RP SWREV: B:0 K:9 S:9
Anything specific you want to see?
SubwayChamp said:
Yes, this is a kind of disassemble, it needs some hardware tools to do it, and after that the data can be pulled easily to another place but the JTAG does by communicating directly to the hardware cores.
Click to expand...
Click to collapse
Do you have experience with this? Is it very tricky? I have some tools and could buy some extra and have a bit of experience with electronics. of course doing a chip-off seems like a non-trivial thing to do.
Or perhaps you'd immediately tell me that chances I'll be successful are very slim?
SubwayChamp said:
Without counting the fact that it doesn't accept charging battery I would incline to think that is a software failure, the JTAG is not so expensive, basically you wouldn't need to back up nothing while you can flash the right firmware on it and device can boot normally, the JTAG also works to can share live (revive) to a device dead and not only to pull out some data.
Click to expand...
Click to collapse
I feel like I flashed the right firmware actually. I just took the latest firmware available from Sammobile for this model SW-A505FN and the OEM lock allowed me to flash it. I update frequently (almost immediately after update comes out so the latest firmware seemed like the one to pick. Yet it's still not booting nor can I get into recovery mode.
Problem with the JTAG is that I would still need to know which socket would be needed to do either a chip-off or connect wires into the board itself. Or do you mean I need a JTAG to flash the device properly?
Thanks a lot for your time and effort!
home_is_where_the_csc_is said:
Yes it goes in download mode. Do you mean you want the full output?
FRP lock and OEM lock is on. Current binary: Samsung Official
CARRIER_ID: PHN
WARRANTY_VOID: 0
RP SWREV: B:0 K:9 S:9
Anything specific you want to see?
Click to expand...
Click to collapse
You triggered the FRP protection in the previous flashing you did, now device won´t boot flashing a normal "firmware"
home_is_where_the_csc_is said:
Do you have experience with this? Is it very tricky? I have some tools and could buy some extra and have a bit of experience with electronics. of course doing a chip-off seems like a non-trivial thing to do.
Or perhaps you'd immediately tell me that chances I'll be successful are very slim?
Click to expand...
Click to collapse
The tools used to recover the data are in some way expensive so they're intended for technical that makes of them a way of life I mean they work on this, and they earn repairing a lot of devices, the average cost could be something like 300 USD and the license are bought per year or so independently, not sure if this is good deal just to get the data for a single phone, if you are highly interested on that better take it to a repair center, although it could be a tricky thing for inexperienced people it's not so hard having these tools.
home_is_where_the_csc_is said:
I feel like I flashed the right firmware actually. I just took the latest firmware available from Sammobile for this model SW-A505FN and the OEM lock allowed me to flash it. I update frequently (almost immediately after update comes out so the latest firmware seemed like the one to pick. Yet it's still not booting nor can I get into recovery mode.
Problem with the JTAG is that I would still need to know which socket would be needed to do either a chip-off or connect wires into the board itself. Or do you mean I need a JTAG to flash the device properly?
Thanks a lot for your time and effort!
Click to expand...
Click to collapse
The JTAG does that, it's a kind of plug-and-play equipment, it would be less expensive taking it to a repair center and ask them if this will solve the issue...
And to my point of view the issue comes for:
- The OEM unlock and USB debugging seem not to been have enabled previously.
- Some of the firmware you flashed previously triggered the FRP protection.
If you consider taking it to a repair center, you could ask them if the JTAG would work with these two main disadvantages.
And by your own, the solution could be finding an engineer firmware and flash it through a patched/modded Odin.
SubwayChamp said:
You triggered the FRP protection in the previous flashing you did, now device won´t boot flashing a normal "firmware"
Click to expand...
Click to collapse
Fudge. I thought it meant that the protection is enabled. Not that it's locked. I believe DrFone triggered it. I thought the flashing just failed but not that it triggered a lock. For the DrFone it did give an error or something.
I would have expected that flashing the normal firmware would also have failed if it was actually locked. So wrong assumption there? It didn't give an error for the normal firmware.
So it does allow the flash but at next boot detects it and locks? Wouldn't the WARRANTY_VOID be non-zero in that case?
SubwayChamp said:
The tools used to recover the data are in some way expensive so they're intended for technical that makes of them a way of life I mean they work on this, and they earn repairing a lot of devices, the average cost could be something like 300 USD and the license are bought per year or so independently, not sure if this is good deal just to get the data for a single phone, if you are highly interested on that better take it to a repair center, although it could be a tricky thing for inexperienced people it's not so hard having these tools.
Click to expand...
Click to collapse
Yeah I've seen the devices for about 300$. I was thinking worst case I could still sell it afterwards. But I didn't count on a license for the software as well
So this will get expensive quite quickly. Problem with the data is that I probably don't need it but in case there's some damage somewhere I have some picture proof (it usually never happens but you never know). And some personal pictures. So it's difficult to put a value on
SubwayChamp said:
And to my point of view the issue comes for:
- The OEM unlock and USB debugging seem not to been have enabled previously.
- Some of the firmware you flashed previously triggered the FRP protection.
If you consider taking it to a repair center, you could ask them if the JTAG would work with these two main disadvantages.
And by your own, the solution could be finding an engineer firmware and flash it through a patched/modded Odin.
Click to expand...
Click to collapse
Today I went to a shop just to test if the battery is at fault. He swapped the battery and it's still the same behavior (although I couldn't trigger a reboot at the boot screen).
I indeed never unlocked the OEM and USB debugging since I know with these data can be more easily recovered when loosing the phone (which of course now is a disadvantage). Anyway in hindsight I could have enabled it flashed drfone on it and recover all the data easily ^^
In regards to modded/patched odin and "engineer" firmware: isn't this risky in itself as these will not be official releases of course.
Once again I appreciate you taking the time to bring some more clarity on what paths I can follow. Seems for now buying the JTAG is of the list.
EDIT: what I see from engineering firmware is that it will also trigger factory reset?
home_is_where_the_csc_is said:
Fudge. I thought it meant that the protection is enabled. Not that it's locked. I believe DrFone triggered it. I thought the flashing just failed but not that it triggered a lock. For the DrFone it did give an error or something.
I would have expected that flashing the normal firmware would also have failed if it was actually locked. So wrong assumption there? It didn't give an error for the normal firmware.
Click to expand...
Click to collapse
No,you can flash almost any firmware always that the compatibility allows it, FRP doesn´t play a role in that early stage.
home_is_where_the_csc_is said:
So it does allow the flash but at next boot detects it and locks?
Click to expand...
Click to collapse
Yes, FRP (in case it is) doesn't allow booting normally to protect the data BUT if you somehow can format data you should be allowed to boot at least to the settings menu prompting you to identify your self with the Google account that is in the device.
home_is_where_the_csc_is said:
Wouldn't the WARRANTY_VOID be non-zero in that case?
Click to expand...
Click to collapse
No, by flashing wrong firmware always that they are stock/official this wouldn't break the Knox security, the warranty is a different thing, it comes from the policy of a certain company and can be ruled in this or that way I mean if you take the device in this state obviously they will diagnose it like an attempt from the user and not an issue from the device itself.
home_is_where_the_csc_is said:
Yeah I've seen the devices for about 300$. I was thinking worst case I could still sell it afterwards. But I didn't count on a license for the software as well
So this will get expensive quite quickly. Problem with the data is that I probably don't need it but in case there's some damage somewhere I have some picture proof (it usually never happens but you never know). And some personal pictures. So it's difficult to put a value on
Today I went to a shop just to test if the battery is at fault. He swapped the battery and it's still the same behavior (although I couldn't trigger a reboot at the boot screen).
I indeed never unlocked the OEM and USB debugging since I know with these data can be more easily recovered when loosing the phone (which of course now is a disadvantage). Anyway in hindsight I could have enabled it flashed drfone on it and recover all the data easily ^^
In regards to modded/patched odin and "engineer" firmware: isn't this risky in itself as these will not be official releases of course.
Once again I appreciate you taking the time to bring some more clarity on what paths I can follow. Seems for now buying the JTAG is of the list.
EDIT: what I see from engineering firmware is that it will also trigger factory reset?
Click to expand...
Click to collapse
Sorry, this part is hard enough to predict completely, some ENG firmware could perform a factory reset BUT if you take a look on they, and it hasn't some other files than boot and system and if they are the same firmware release that was previously onto your device then it wouldn't factory reset it BUT to be honest you need some kind of luck on that, Why? ENG firmware are known to force a device to boot no matter what they have to do, and one of the first reason to not booting a device it is that the data is protected.
SubwayChamp said:
Yes, FRP (in case it is) doesn't allow booting normally to protect the data BUT if you somehow can format data you should be allowed to boot at least to the settings menu prompting you to identify your self with the Google account that is in the device.
Click to expand...
Click to collapse
I thought about this again and it seems kind of odd that the FRP lock would not allow the OS starting to the bit where it's actually asking to authenticate to your google account. And also that it wouldn't allow me to go to the recovery mode where I can factory reset the system after which FRP lock probably asks me for the details.
home_is_where_the_csc_is said:
I thought about this again and it seems kind of odd that the FRP lock would not allow the OS starting to the bit where it's actually asking to authenticate to your google account. And also that it wouldn't allow me to go to the recovery mode where I can factory reset the system after which FRP lock probably asks me for the details.
Click to expand...
Click to collapse
From what I followed your issue, this is what I think:
Your device did get a failed update by itself, of course, a failed update will take it to a boot loop, after that you flashed a firmware; at this point the better is formatting data, did you know if it was the same exactly firmware or newer? Because a downgrade is not allowed also as you couldn't enable previously the USB debugging and OEM unlock Samsung detected like an unofficial attempt to alter the firmware, at the time to flash through Odin you doesn't have to see in the download screen some warning message from RMM/KG prenormal state or similar, this is why Knox doesn't allow device to boot, the only way available in this condition will be download mode, not system, not safe mode, not recovery.
Formatting data, as I said to you previously, essentially is the main task assumed by Samsung/Google to protect the data, I don't think you can recover your device without get of rid of that. The better solution will be finding an engineer firmware and flash it.