Related
Dear XDA Developers,
As a new member of this amazing thriving community, I tried to root my device, a first time experience for me. Being one of those people who does not exactly read manuals or instructions, I happened to learn how to do about 99% of rooting, with a fatally wrong one percent. I lost my device and have now been pressing buttons, and doing all kinds of stuff, incluing the following, teenybins, recovery mode, deleting everything (this was probably my biggest mistake as I lost my recovery). Let me start from the beginning, I originally set up a recovery with Clockworkmod's helium, and then installed Clockworkmod's ROM Manager, after thinking I had rooted my phone through command prompt. I had not. After quite a few errors when it tried to install the Recovery I tried to also install TWRP. Then, I went and reset it to the factory settings, and rerooted using another tool, also don't remember exactly which one, since I had to try multiple times, with multiple different rooting softwares before it worked. Then, I installed Clockworkmod Recovery, seemingly successfully, moved CM 10.2 RC onto my phone, and the corresponding google apps package. I tried to install both, but I came across the Rom Manager saying I could only install one zip file at a time, which led me to only try to install CM 10.2 RC, thinking I could later download the google apps package. My phone then turned off, and upon restarting, it said Secure Boot error, and some other text, whatever I tried. Then upon searching for an hour or so, I found a website talking about teenybins, on XDA, which I followed to the letter. http://forum.xda-developers.com/showthread.php?t=2249500 . During this, at first, my computer said that the usb was not recognized, so I got AutoLGNPST-tSilenzio, which allowed me to get LGNPST working. I then proceeded with the instructions, and everything went to plan, and it stopped at 67%, then went to 85% as I disconnected my phone. Then, it showed a white google logo, with an unlocked lock. For a while, I could not get it to do anything, but then I got it to go to download mode again, and redid the process in hopes of the second time working. It did not. however, after this, by holding the power and the raise volume buttons, I got to an android laying down, with its stomach open, A big green start arrow pointed at my power button, two arrows, up and down, by my volume buttons, and the following information:
FASTBOOT MODE
PRODUCT_NAME - mako
VARIANT - mako 32 GB
HW VERSION - rev_11
BOOTLOADER VERSION - MOKOZ10f
BASEBAND VERSION - N/A
CARRIER INFO - None
SERIAL NUMBER - 018e8dcb52d6a343
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked
Then I played around with it, in recovery mode, not really doing anything, wondering why It was TWRM instead of CWR, until I finally got ADB working, upon which I first tried Sideloading CM 10.2
Which resulted in the following:
Starting ADB sideload feature. . .
Installing '/data/media/sideload.zip'. . .
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found.
It also says adb sideload complete, with a red Failed underneath, and has one option below, to reboot system
and then I pushed CM 10.2 along with google apps, onto my phone, and tried to install. which resulted in the following:
Uploading partition details . . .
E: Unable to mount '/system
Installing '/sdcard/cm-110.2.0-RC1-E975(1).zip'. . .
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found.
Error Flashing zip '/sdcard/cm-110.2.0-RC1-E975(1).zip'
Uploading partition details. . .
E: Unable to mount '/system
Installing '/sdcard/apps.zip'. . .
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found.
************************************************
Google Apps for Android 4.3.0
************************************************
Installing files. . .
Cleaning up. . .
Installation complete!
Installing '/sdcard/cm-110.2.0-RC1-E975(1).zip'. . .
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found.
Error Flashing zip '/sdcard/cm-110.2.0-RC1-E975(1).zip'
Uploading partition details. . .
E: Unable to mount '/system
And below the command window, it says failed, and three actions, home, reboot system, and wipe cache/dalvik, of which I have tried all three, which all work.
I understand I may not be the smartest person to make such a litany of mistakes, but I hope that some of the great developers here could somehow help unbrick my device, as I have no way to get a new (smart)phone in the next year, so this is really my only hope. If someone could please tell me how to fix it, with phone terminology explained, but I have no problems using any command prompt or any other methods, as I do do a lot of work with computers. Thank you in advance for what I know will be a good reply, and I wish you all a good day.
PS: Could someone please tell me how to successfully flash CM from where it ends up as I could not find a way from stock except for the one that led to this unfortunate situation.
@kimitza
This post is your farewell. Help him out
Sent from my LG-E975 using Tapatalk
)...like i said, some like to complicate the simplest things.If you can still enter download mode(turn off phone, pres vol down and plug the phone to pc)...use kdz updater to flash a stock rom.
And click the damn FAQ thread,i don't know how i could simplify it more.Rooting is easy,but,if there are so many ways to root, there is ONLY ONE WAY TO UNLOCK THE BOOTLOADER AND FLASH CWM. Don't play smartass and try anything else than FREEGEE...it can be done,but the hell would someone try to unlock with adb,when this magical app is available(kudos shelnutt2).?
Reply
kimitza said:
)...like i said, some like to complicate the simplest things.If you can still enter download mode(turn off phone, pres vol down and plug the phone to pc)...use kdz updater to flash a stock rom.
And click the damn FAQ thread,i don't know how i could simplify it more.Rooting is easy,but,if there are so many ways to root, there is ONLY ONE WAY TO UNLOCK THE BOOTLOADER AND FLASH CWM. Don't play smartass and try anything else than FREEGEE...it can be done,but the hell would someone try to unlock with adb,when this magical app is available(kudos shelnutt2).?
Click to expand...
Click to collapse
@kimitza I do appreciate the information, but for the life of me, I cannot find a working kdz file, I am a starhub customer in singapore, because it always says Access denied to the file. On top of this, the other file I tried which was in the instructions I found, ends up with Error LParam: 100 WParam 72, and switches from download mode to that little laying down android if I attempt to start the upload. Could you please give a working link or file, and possibly more precise instructions, or a link to some
http://lg-phone-firmware.com/
if one is not available try other. open europe ones work just fine.
seems you are on nexus bootloader, if thats true, when while using kdz you turn to bootloader, simply either using volume keys return to download mode or manualy turn to download mode it will resume.
sorry forgot what exactly i did. not on custom rom for some time now.
there is a small tool,called kdz downloader. insert the imei and that tool will automagically find the latest firmware available for yout phone....
It's also in my FAQ.
Hey,
I tried to update the OS because it was 4.1.X
I accidentally deleted the OS and I tried the Firmware emergency recovery on Kies but it asks for "recovery code from previous PC to run emergency recovery" and I don't know/have it.
I also tried running sdk sideloader and I dont know why it doesn't recognized.....
Please please please help me
You are not CLEAR with your problem
breitman1 said:
Hey,
I tried to update the OS because it was 4.1.X
I accidentally deleted the OS and I tried the Firmware emergency recovery on Kies but it asks for "recovery code from previous PC to run emergency recovery" and I don't know/have it.
I also tried running sdk sideloader and I dont know why it doesn't recognized.....
Please please please help me
Click to expand...
Click to collapse
i dont know what do you mean by "deleted my OS"!
i can help you though,
download this if you are on south cellularthen download this: http://www.sammobile.com/firmwares/3/?download=35050
else download this: http://www.sammobile.com/firmwares/3/?download=22062
and when you had downloaded it then follow this:
1. Extract (unzip) the firmware file
2. Download Odin v3.09
3. Extract Odin zip-file
4. Open Odin v3.09
5. Reboot phone in Download Mode (press and hold Home + Power + Volume Down buttons)
6. Connect phone and wait until you get a blue sign in Odin
7. Add the firmware file to AP / PDA
8. Make sure re-partition is NOT ticked
9. Click the start button, sit back and wait a few minutes
after this, phone will reboot automaticaly and will go to some installation process and then straight to android
the whole process(from step one to booting to android) will take about 20 minutes and step 9 will take around 10 minutes itself
first boot can take upto 5 minutes to compleate, so dont panic
hope this helped
READ EVERYTHING CAREFULLY!
1.Your phone warranty will be void after this tutorial!
2.Any small mistake and your phone is bricked/bootlooped!
3.All of your data will be lost so back it up somewhere
Click to expand...
Click to collapse
(Fixed the tutorial my bad.)
Click to expand...
Click to collapse
Hey Guys Im Back! Thank you for the support and how it blew up. I have tested this on Android 10 UI 2.0 and it works better then ever!
Also installed lineage os : https://forum.xda-developers.com/galaxy-a10/development/rom-lineage-os-a10-a105f-t4078093
So i tried using afaneh92's tutorial which will be linked here : https://forum.xda-developers.com/galaxy-a10/how-to/magisk-root-galaxy-a10-series-t3963822
Which lead to me bootlooping or softbricking and my storage was reduced from 32 gb to 16Gb so i decided to work on my own method!
Credits go to afaneh92 for the Twrp!
BEFORE YOU START YOU SHOULD HAVE
1.Samsung Drivers installed
2.Odin Installed
3.7zip Installed
4.A data transfer cable
5.A Proper working brain
If you have all of those lets start!
A: Phone settings
1.Go in settings>about phone>software information>build number tap that 5 times until it says "You are a developer now" then you will have Developer options unlocked
2.Then go in developer functions and find OEM unlocking tick that on scroll down until you see Usb Debugging and tick that also Disable Auto Updates option
B: Download TWRP and 2 other important files
1.Dial *#1234# and it will show the AP and some others, focus on AP paste it on google and get the download for it
2.After downloaded move the AP to your download folder in your android device
3.You will get a magisk_patched.tar after its been offically converted
4.Get the twrp for a10
Download the twrp file here : https://mega.nz/#!OU1WhSDZ!vQz5K1wpqBhg0hCD59aziaHPxFlUsT_2WG8SgT8p6iY
5.After you got everything open the .tar archive and extract vbmeta.img, boot.img and you should already have recovery.img on your Desktop
6.Grab all the 3 .img files and archive them into a .tar using 7zip, Now continue to step C,
C :Unlocking The Bootloader and Getting Into Download Mode (THE PART WHERE YOU RESET YOUR PHONE)
1.Turn Off your phone
1.2.Put your data cable into your PC(dont connect your phone to it yet)
1.3.Hold Volume Up and Down then insert the cable into your phone
1.4.When you see a bluescreen let go
1.5.Hold vol up until you see another screen then let go for 1 second and hold vol up again
2.Your device will reset itself and reboot
2.1.After the device has booted in into the setup take the cable out after Turn off your phone
2.2.Hold Vol Up and Down again and connect the cable
2.3.Let go when a blue screen appears then press vol up until you are in download mode
D: Flashing TWRP
1.Open Odin
2.Press on AP then find Desktop.tar and press open
3.Press start and let it do its thing
4.After your Phone has rebooted you oficially have TWRP installed
5.If you want to know hoe to root go to step E
E: Installing Magisk
Since magisk is counted as the best rooting option rn i will be using it in this tutorial(Sorry supersu fans)
1.Install Magisk Manager
2.Press on Install (first one) then press install again and after that press Install Zip Only
3.Then go into Twrp by doing the steps below
3.1.Turn off your device
3.2.Hold vol up and power button untill you see TWRP logo
4.Press install
4.1.Find magisk-v20.4(20400).zip
4.2Swipe right on the bottom to flash it then press reboot system now.
5.Now you have TWRP,Root and Magisk Congratulations!
What happens if something goes wrong.
1.SV Error Device 1 library 0 - You installed the wrong firmware look for the right firmware.To check go in recovery mode and look at the A105XXXXXX and then look for a download. Remider AP->AP BL->BL CP->CP HOME_CSC->CSC
2.vbmeta.img error - you have the wrong vbmeta.img file. Redownload the original firmware and take out the right vbmeta.img next time you try flashing. Reminder AP->AP BL->BL CP->CP HOME_CSC->CSC
3.A blue screen telling you to use samsung switch emergency update. That wont work so just flash the original firmware and try flashing twrp again.
4.When i try to boot in it gets me into TWRP - Thats just because that your data is corrupted and to fix it while in TWRP mode press wipe then swipe after its done press Reboot To System. That should be a fix
5.My internal storage is just full of weird numbers and I can't download anything on it! Go in TWRP then wipe,press advanced wipe, click on internal storage and data, swipe. That should fix the error
6.Boootlooping or Bricked! Installed corrupted firmware or the recovery was f-ed up. Then install the right firmware and redo the steps!
If you have issues during the process send it in the comment ill try to respond as fast as i can!
i notice thread title says exynos only.. u do know they are all exynos including a102u and a102u1 right?
Oh. Alright thanks for telling me.
Press on app? I have nothing in odin saying that, do you mean ap?
Edit: guess not....i'm bricked, stuck on galaxy logo, device not recognized by pc, holoding power button wont force reboot, nothing lol.
Edit2: can force reboot holding volume down and power but instantly stuck on logo again, cannot power off or enter download, nothing...bricked. Followed this guide to the letter. I assumed when you said app in odin you meant ap since there is no app button. My bootloader unlocked then I went to flash in odin the tar i made with patched boot and vbmeta, along with recovery linked. I used matching firmware to what my A10 has also. Would not mind if i could get back into download mode, but that looks impossible now.
Edit3: Managed to get download mode but had to be so quick...hopefully I can reflash stock now.
Cupcake 1.5 said:
Press on app? I have nothing in odin saying that, do you mean ap?
Edit: guess not....i'm bricked, stuck on galaxy logo, device not recognized by pc, holoding power button wont force reboot, nothing lol.
Edit2: can force reboot holding volume down and power but instantly stuck on logo again, cannot power off or enter download, nothing...bricked. Followed this guide to the letter. I assumed when you said app in odin you meant ap since there is no app button. My bootloader unlocked then I went to flash in odin the tar i made with patched boot and vbmeta, along with recovery linked. I used matching firmware to what my A10 has also. Would not mind if i could get back into download mode, but that looks impossible now.
Edit3: Managed to get download mode but had to be so quick...hopefully I can reflash stock now.
Click to expand...
Click to collapse
Im sorry for that and yes i meant AP.
If you wanted to reboot you had to hold vol up vol down and power at the same time and you sure that you unlocked the bootloader and used the right firmware?
Also tell me the AP and from which source have you downloaded it :laugh:
cmz6996 said:
Im sorry for that and yes i meant AP.
If you wanted to reboot you had to hold vol up vol down and power at the same time and you sure that you unlocked the bootloader and used the right firmware?
Also tell me the AP and from which source have you downloaded it :laugh:
Click to expand...
Click to collapse
All sorted now, back on stock with twrp and root It was a schoolboy error by me, the firmware downloaded was corrupted lol.
Cupcake 1.5 said:
All sorted now, back on stock with twrp and root It was a schoolboy error by me, the firmware downloaded was corrupted lol.
Click to expand...
Click to collapse
Oh! Im happy to hear that!
Cupcake 1.5 said:
All sorted now, back on stock with twrp and root It was a schoolboy error by me, the firmware downloaded was corrupted lol.
Click to expand...
Click to collapse
Could you also tell me from where have you downloaded the corrupted firmware so i can warn the others?
cmz6996 said:
Could you also tell me from where have you downloaded the corrupted firmware so i can warn the others?
Click to expand...
Click to collapse
The corruption was my side, I was using a download manager, but when I downloaded through chrome it was all good. As I said, schoolboy error on my part for not checking md5. I used sammobile site for the firmware.
Cupcake 1.5 said:
The corruption was my side, I was using a download manager, but when I downloaded through chrome it was all good. As I said, schoolboy error on my part for not checking md5. I used sammobile site for the firmware.
Click to expand...
Click to collapse
Alr thanks.
Can you upload it to Mediafire? Mega marks a "temporal error"...
Kyua said:
Can you upload it to Mediafire? Mega marks a "temporal error"...
Click to expand...
Click to collapse
At me it works?
Works on a105m?
Axeggus said:
Works on a105m?
Click to expand...
Click to collapse
Yes
i receive message that i running samsumg not official firmware after odin install recovery.tar
not work
cmz6996 said:
So i tried using afaneh92's tutorial which will be linked here : https://forum.xda-developers.com/galaxy-a10/how-to/magisk-root-galaxy-a10-series-t3963822
Which lead to me bootlooping or softbricking and my storage was reduced from 32 gb to 16Gb so i decided to work on my own method!
Credits go to afaneh92 for the Twrp!
BEFORE YOU START YOU SHOULD HAVE
1.Samsung Drivers installed
2.Odin Installed
3.7zip Installed
4.A data transfer cable
5.A Proper working brain
If you have all of those lets start!
A: Phone settings
1.Go in settings>about phone>software information>build number tap that 5 times until it says "You are a developer now" then you will have Developer options unlocked
2.Then go in developer functions and find OEM unlocking tick that on scroll down until you see Usb Debugging and tick that also Disable Auto Updates option
B: Download Your firmware and TWRP
1.Go in your calls app and dial *#1234# Then You will receive some details about your AP, CP etc. look at the AP then download the firmware by searching it on google and (download it from sites like sammobile etc)
2.After you got your firmware connect your device to your pc after its connected send the entire firmware to the device in the Downloads folder
2.1. Install Magisk Manager
3.After you're in magisk manager press on install (first one) then press install again then press Select and Patch a File
3.1.Chose the firmware you saved on the Downloads folder
3.2.After you tap on it it should've already started modifying it
4.After it finished go back to your pc and move the magisk_patched.tar back to your desktop (It should be located in Downloads)
5.From the magisk_patched.tar extract boot.img and vbmeta.img to your desktop
5.1.Download the twrp file here : https://mega.nz/#!OU1WhSDZ!vQz5K1wpqBhg0hCD59aziaHPxFlUsT_2WG8SgT8p6iY
5.2.After recovery.img(TWRP) has been downloaded move it to your desktop
5.3.Select all those three items(vbmeta.img,recovery.img,boot.img) right click then Find 7Zip then press add to archive
5.4.Rename the Archive name to recovery.tar and make sure the archive format is .tar
6.After the Archive has been downloaded follow the steps in C
C :Unlocking The Bootloader and Getting Into Download Mode (THE PART WHERE YOU RESET YOUR PHONE)
1.Turn Off your phone
1.2.Put your data cable into your PC(dont connect your phone to it yet)
1.3.Hold Volume Up and Down then insert the cable into your phone
1.4.When you see a bluescreen let go
1.5.Hold vol up until you see another screen then let go for 1 second and hold vol up again
2.Your device will reset itself and reboot
2.1.After the device has booted in into the setup take the cable out after Turn off your phone
2.2.Hold Vol Up and Down again and connect the cable
2.3.Let go when a blue screen appears then press vol up until you are in download mode
D: Flashing TWRP
1.Open Odin
2.Press on AP then find recovery.tar and press open
3.Press start and let it do its thing
4.After your Phone has rebooted you oficially have TWRP installed
5.If you want to know hoe to root go to step E
E: Installing Magisk
Since magisk is counted as the best rooting option rn i will be using it in this tutorial(Sorry supersu fans)
1.Install Magisk Manager
2.Press on Install (first one) then press install again and after that press Install Zip Only
3.Then go into Twrp by doing the steps below
3.1.Turn off your device
3.2.Hold vol up and power button untill you see TWRP logo
4.Press install
4.1.Find magisk-v20.4(20400).zip
4.2Swipe right on the bottom to flash it then press reboot system now.
5.Now you have TWRP,Root and Magisk Congratulations!
What happens if something goes wrong.
1.SV Error Device 1 library 0 - You installed the wrong firmware look for the right firmware.To check go in recovery mode and look at the A105XXXXXX and then look for a download. Remider AP->AP BL->BL CP->CP HOME_CSC->CSC
2.vbmeta.img error - you have the wrong vbmeta.img file. Redownload the original firmware and take out the right vbmeta.img next time you try flashing. Reminder AP->AP BL->BL CP->CP HOME_CSC->CSC
3.A blue screen telling you to use samsung switch emergency update. That wont work so just flash the original firmware and try flashing twrp again.
4.When i try to boot in it gets me into TWRP - Thats just because that your data is corrupted and to fix it while in TWRP mode press wipe then swipe after its done press Reboot To System. That should be a fix
5.My internal storage is just full of weird numbers and I can't download anything on it! Go in TWRP then wipe,press advanced wipe, click on internal storage and data, swipe. That should fix the error
6.Boootlooping or Bricked! Installed corrupted firmware or the recovery was f-ed up. Then install the right firmware and redo the steps!
If you have issues during the process send it in the comment ill try to respond as fast as i can!
Click to expand...
Click to collapse
hi guy... very good guide but it not work for my galaxy a10 ....i only have unlock the bootloader... if i try to get patched recovery ... it not work.... i have device blocked black screen for samsung software... or i cant go recovery mode it say me a error of vbmeta)
andrea2o18 said:
hi guy... very good guide but it not work for my galaxy a10 ....i only have unlock the bootloader... if i try to get patched recovery ... it not work.... i have device blocked black screen for samsung software... or i cant go recovery mode it say me a error of vbmeta)
Click to expand...
Click to collapse
You installed the wrong fir.ware check your right firmware.
BlueFolks said:
i receive message that i running samsumg not official firmware after odin install recovery.tar
Click to expand...
Click to collapse
Be cause you modified the firmware ignore that message
have you fixed the storage reduced to 16gb problem?
I have a Samsung galaxy sm-a10. I've tried everything here, even combination files. The error I ALWAYS get is 'failed flashing ROM... OEM lock'
Of course I have unlocked OEM in developer options, but still I get this error in the bootloader.
Any ideas?
Hi,
Phone; SM-AF520F
My phone has been restarting on its own from the past month and I ignored it. It showed me occasionally Google services failed or system UI is not responding.
I factory resetted the phone as any noob would do and the restart occurrence went to only at night, which I was unbothered with. A little time passed and the phone went to the downloading sky blue screen.
I'm aware with flashing roms and stuff but I never really tried it. I tried everything;
i) Used Odin, three different versions
ii) Used Stock firmware, three different versions
iii) Used Smart switch
The phone only went in download phase and than in the phase where you press home button, volume and power and it shows fonts in the left hand corner. Odin always giving me errors, sometimes stucking on setting up connection.
Two errors:
i) There is no PIT partition
ii) Write operation failed
There are always these things happening.
When I restarted with volume down and power key, the system showed, there was an error and try smart switch, updated my drivers but when I go in the settings to emergency recover my phone, it does not show my phone.
After restarting the phone couple of time, Im in downloading mode again, in between the screen also turns full sky blue with no text.
I tried installing custom recovery but the image didn't load, ( I dont know what i am doing at this point, even if this was a good idea).
I have scavanged every forum, every post, everything on the internet but I just can't seem to fix it, I tried every possible thing and it just dosent work. I know it can be fixed but I don't know how. I know I'm doing something stupidly wrong but I can't seem to figure it out.
This is an old phone, I'm going to buy another one soon but I just hope it works for another week? Can I wipe the whole system and start from scratch (Which i dont know how to do).
Any type of help would be greatly appreciated, or just tell me to give up hope on it so I can just throw it away and move on.
1-Install 7zip application in windows
Then using 7zip, try to open file (in stock ROM files) -⇾ "CSC_ODD_***"
2-There is your phone pit file for a520f.
Extract that file and keep it between your stock Rom files.
3-Download the Odin from this link and open it:
https://dl2018.sammobile.com/Odin3-v3.14.4.zip
4-Go to download mode (blue screen) in your phone!
Add 4 part of your ROM to Odin.
Then in pit tab of Odin add your phone pit file!
5-In option tab of Odin toggle Re-Partition option.
6-click on start and wait until it shows a green icon and phone restarting!
It must be fixed!
matkali said:
1-Install 7zip application in windows
Then using 7zip, try to open file (in stock ROM files) -⇾ "CSC_ODD_***"
2-There is your phone pit file for a520f.
Extract that file and keep it between your stock Rom files.
3-Download the Odin from this link and open it:
https://dl2018.sammobile.com/Odin3-v3.14.4.zip
4-Go to download mode (blue screen) in your phone!
Add 4 part of your ROM to Odin.
Then in pit tab of Odin add your phone pit file!
5-In option tab of Odin toggle Re-Partition option.
6-click on start and wait until it shows a green icon and phone restarting!
It must be fixed!
Click to expand...
Click to collapse
Thank you for your response.
I did what you exactly said, previously it failed at the instant, now it moved one tab and than failed.
I tried the provided Odin, than tried two roms with, with the pit filed extracted and enabled re partition.
The error occurred: Complete(write) operation failed.
The error occurred every time I tried to flash, it never worked.
Do you think there is anything else to do?
Try this way to go download mode:
Press vol-down + power until phone restart
Then instantly press vol-up + Home + Power to going to download mode!
If it not works for you! You can use (eMMC programmer or easy JTAG) to writing rom on your phone memory (Last Option)!
I gave up on it and asked for professional help. Idk what he did, but he fixed the phone. It was sluggish at first but it works like a charm now.
It took 7 minutes to turn it on, than It said, there was an authorized user who tried to access your phone, use your previous email password to access your phone. I put it on my previous details and the works okay after some updates.
I wonder what he did? And i never knew android has a feature where if somone tries to reset your phone, google account locks it? Wow.
Is flashing a custom os a good idea? I'm afraid I'll brick it or something or just keep running one ui and wait for it to die again.
Thank you for your help btw, made me learn alot.
matkali said:
1-Install 7zip application in windows
Then using 7zip, try to open file (in stock ROM files) -⇾ "CSC_ODD_***"
2-There is your phone pit file for a520f.
Extract that file and keep it between your stock Rom files.
3-Download the Odin from this link and open it:
https://dl2018.sammobile.com/Odin3-v3.14.4.zip
4-Go to download mode (blue screen) in your phone!
Add 4 part of your ROM to Odin.
Then in pit tab of Odin add your phone pit file!
5-In option tab of Odin toggle Re-Partition option.
6-click on start and wait until it shows a green icon and phone restarting!
It must be fixed!
Click to expand...
Click to collapse
im having the exact same problem this guy has, installing a pit file will erase my data? if i use HOME_CSC will the pictures stay? i only care about the photos.
Welcome to this easy guide.
Time needed: 15 / 60min (depends on your internet connection)
Ease of operation: Very easy
Don't be fooled by the length of this guide ... the operations to be done are quick and easy.
NB: I state immediately that this procedure does not restore the state of Knox to 0x0 if by chance you have brought it to 0x1.
To date, this is an irreversible process.
In the next lines we will see how to restore our Samsung device to its original factory conditions, after unlocking the Bootloader, rooting and installing various types of custom installations, such as custom OneUI, AOSP or Google ROM.
It may happen that you want to go back to the original firmware of our Samsung, after trying various custom ROMs, after having rooted and modified the recovery, missing with the phone partitions, lost EFS folder or corrupt IMEI. The reasons can be many. This guide is aimed at all those who, with the classic Odin procedure to install the stock rom, are unable to restore the phone to normal operating conditions.
But it can happen to fail in this thing, even using Odin to put back the original software, Odin himself or the phone can crash to the BOOT partition or generate other errors, with VBMeta or generic errors, including partition ones.
So let's see how to solve all the inconveniences due to modding on our Samsungs to 99%. Let's begin!
- MATERIAL REQUIRED:
Latest version of Frija link
Latest version of Odin link
Samsung USB Driver link
File Manager zip (example 7zip) link
PC with Microsoft Windows 7-8-8.1-10-11
USB type C cable
1 - Download the latest stock firmware for our Samsung:
Download the latest version of Frija and once the program has started, enter the model code of your device and the abbreviation of your CSC.
Make sure the "Auto" checkbox is checked.
Once you have checked everything, click on "Check Update" and click on "Download". Wait for it to download.
{
"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"
}
Once you have downloaded the zip containing the various parts that make up the stock software (see image below), extract it to a folder of your choice. We will have 5 files in total.
2 - Retrieve the original PIT file
To recover the PIT file (partition list) for our device, go to the firmware folder you just downloaded with Frija, locate the "tar.md5" file with the words CSC_OXM_N............., right click on the it and select rename, adding ".zip" at the end to "transform" it into a compressed file that can be opened. This way you will have something like
"CSC_OXM_N975...............REV01_user_low_ship.tar.md5.zip"
Give the Ok and confirm the change of the file extension.
You should now have the same situation as you see in the image below. Total 5 files of which one is a ".zip" files.
Now open the file you just renamed with 7zip, the main window of the 7zip program will open with various files inside:
Now copy the "D2S_EUR_OPEN.pit" file by right clicking and selecting the "copy to ..." item and giving the ok without changing anything. The .PIT file will be copied to the same folder as the previously downloaded firmware.
Once this is done, the folder that appears will look like this (Now, the total files are 6 of which one is a ".zip" files):
Now just put the CSC_OXM ... file back to the previous condition, renaming it one more time and eliminating the ".zip" extension at the end of the name, in order to find an MD5 file again. This will be the file we will have:
"CSC_OXM_N975...............REV01_user_low_ship.tar.md5."
Now we have everything we need. If we have done everything correctly this is the final result (Total 6 files).
3 - Prepare and Configure Odin
Now open the latest version of Odin (as of May 2022 the latest version is 3.14.4), load the corresponding downloaded firmware files in the various slots (BL, AP, CP and CSC) as usual.
In the CSC box, upload the file labeled "CSC_OXM_N975 ............... REV01_user_low_ship.tar.md5."
Did you know that....
The CSC_OXM file is used to restore the internal memory as factory, this will delete all personal data in the phone memory, all applications and data associated with it.
The HOME_CSC_OXM file, on the other hand, will not act in any way on the internal memory. Useful if you want to update while remaining in the same type of ROM. Not recommended if your phone has a Custom ROM installed, as it may not start or give errors in previously installed applications.
If you want to do a clean install of the original ROM, always use the CSC_OMX file!
Click to expand...
Click to collapse
Once this is done, move (still in Odin) to the "Option" tab and check the following items:
Auto Reboot
Nand Erase
Re-partition
F. Reset time
The rest of the items MUST NOT BE SELECTED!
Again in Odin, this time go to the PIT tab, a warning message will appear, give the ok and select the first extracted file which has the unique name "D2S_EUR_OPEN.pit"
If you have done everything right you should have the same situation as the image below:
4 - Return the phone to the original firmware
Connect the USB type C cable to your phone and restart your phone in "Download mode" (check the right combination for your model), or use the Custom Rom to do this, usually all coustom roms or custom recovery offer reboot in Download mode (or Booloader).
In odin in the "Log" tab, you should see the word "Added" with the number of the port to which it is connected (example "0: [COM3]"), if so, press the START key of Odin and wait for the restart (this procedure will delete all data on your device).
If nothing appears, install the Samsung USB drivers and repeat step 4.
5 - Relock the BootLoader
To get rid of that fatal warning message when starting the phone that tells us that the BootLoader is unlocked once and for all, let's put it back in place, relocking the BootLoader.
(Image for demonstration purposes)
Turn off the phone, reconnect the USB cable and immediately press the Volume + and Volume- keys at the same time.
Return to Download mode (albeit a little different), with various options (actually only 3).
In this case, follow the second option (Volume up long press: Device unlock mode) hold down the Volume + key for a few moments until the message "Lock Bootloader?" Appears. To confirm everything, make a single click on Volume + (also in this case the phone will be formatted by the system again) and wait for a complete restart.
6 - Relock OEM (optional but recommended if you want to stick with the Samsung ROM)
Once your phone has restarted and the initial setup is complete, you can also disable the OEM unlock capability and reuse the security features.
To do this, go to Settings / Phone Information / Software Information and tap several times on the wording "Build version" in order to unlock the "Developer options". If prompted, unlock your smartphone with your PIN or sign.
Now go back to the main Settings page, open the Developer Options and check that the "OEM Unlock" item is disabled, otherwise disable it and restart the device.
Well now you have your Samsung with Original firmware again. Enjoy
ExileTM said:
Welcome to this easy guide.
Time needed: 15 / 60min (depends on your internet connection)
Ease of operation: Very easy
Don't be fooled by the length of this guide ... the operations to be done are quick and easy.
NB: I state immediately that this procedure does not restore the state of Knox to 0x0 if by chance you have brought it to 0x1.
To date, this is an irreversible process.
In the next lines we will see how to restore our Samsung device to its original factory conditions, after unlocking the Bootloader, rooting and installing various types of custom installations, such as custom OneUI, AOSP or Google ROM.
It may happen that you want to go back to the original firmware of our Samsung, after trying various custom ROMs, after having rooted and modified the recovery, missing with the phone partitions, lost EFS folder or corrupt IMEI. The reasons can be many. This guide is aimed at all those who, with the classic Odin procedure to install the stock rom, are unable to restore the phone to normal operating conditions.
But it can happen to fail in this thing, even using Odin to put back the original software, Odin himself or the phone can crash to the BOOT partition or generate other errors, with VBMeta or generic errors, including partition ones.
So let's see how to solve all the inconveniences due to modding on our Samsungs to 99%. Let's begin!
- MATERIAL REQUIRED:
Latest version of Frija link
Latest version of Odin link
Samsung USB Driver link
File Manager zip (example 7zip) link
PC with Microsoft Windows 7-8-8.1-10-11
USB type C cable
1 - Download the latest stock firmware for our Samsung:
Download the latest version of Frija and once the program has started, enter the model code of your device and the abbreviation of your CSC.
Make sure the "Auto" checkbox is checked.
Once you have checked everything, click on "Check Update" and click on "Download". Wait for it to download.
View attachment 5628035
Once you have downloaded the zip containing the various parts that make up the stock software (see image below), extract it to a folder of your choice. We will have 5 files in total.
View attachment 5629259
2 - Retrieve the original PIT file
To recover the PIT file (partition list) for our device, go to the firmware folder you just downloaded with Frija, locate the "tar.md5" file with the words CSC_OXM_N............., right click on the it and select rename, adding ".zip" at the end to "transform" it into a compressed file that can be opened. This way you will have something like
"CSC_OXM_N975...............REV01_user_low_ship.tar.md5.zip"
Give the Ok and confirm the change of the file extension.
You should now have the same situation as you see in the image below. Total 5 files of which one is a ".zip" files.
View attachment 5629261
Now open the file you just renamed with 7zip, the main window of the 7zip program will open with various files inside:
View attachment 5628037
Now copy the "D2S_EUR_OPEN.pit" file by right clicking and selecting the "copy to ..." item and giving the ok without changing anything. The .PIT file will be copied to the same folder as the previously downloaded firmware.
View attachment 5629463
Once this is done, the folder that appears will look like this (Now, the total files are 6 of which one is a ".zip" files):
View attachment 5629465
Now just put the CSC_OXM ... file back to the previous condition, renaming it one more time and eliminating the ".zip" extension at the end of the name, in order to find an MD5 file again. This will be the file we will have:
"CSC_OXM_N975...............REV01_user_low_ship.tar.md5."
Now we have everything we need. If we have done everything correctly this is the final result (Total 6 files).
View attachment 5629265
3 - Prepare and Configure Odin
Now open the latest version of Odin (as of May 2022 the latest version is 3.14.4), load the corresponding downloaded firmware files in the various slots (BL, AP, CP and CSC) as usual.
In the CSC box, upload the file labeled "CSC_OXM_N975 ............... REV01_user_low_ship.tar.md5."
Once this is done, move (still in Odin) to the "Option" tab and check the following items:
Auto Reboot
Nand Erase
Re-partition
F. Reset time
The rest of the items MUST NOT BE SELECTED!
View attachment 5628039
Again in Odin, this time go to the PIT tab, a warning message will appear, give the ok and select the first extracted file which has the unique name "D2S_EUR_OPEN.pit"
If you have done everything right you should have the same situation as the image below:
View attachment 5628043
View attachment 5628045
4 - Return the phone to the original firmware
Connect the USB type C cable to your phone and restart your phone in "Download mode" (check the right combination for your model), or use the Custom Rom to do this, usually all coustom roms or custom recovery offer reboot in Download mode (or Booloader).
In odin in the "Log" tab, you should see the word "Added" with the number of the port to which it is connected (example "0: [COM3]"), if so, press the START key of Odin and wait for the restart (this procedure will delete all data on your device).
If nothing appears, install the Samsung USB drivers and repeat step 4.
View attachment 5628041
5 - Relock the BootLoader
To get rid of that fatal warning message when starting the phone that tells us that the BootLoader is unlocked once and for all, let's put it back in place, relocking the BootLoader.
View attachment 5629449
(Image for demonstration purposes)
Turn off the phone, reconnect the USB cable and immediately press the Volume + and Volume- keys at the same time.
Return to Download mode (albeit a little different), with various options (actually only 3).
In this case, follow the second option (Volume up long press: Device unlock mode) hold down the Volume + key for a few moments until the message "Lock Bootloader?" Appears. To confirm everything, make a single click on Volume + (also in this case the phone will be formatted by the system again) and wait for a complete restart.
6 - Relock OEM (optional but recommended if you want to stick with the Samsung ROM)
Once your phone has restarted and the initial setup is complete, you can also disable the OEM unlock capability and reuse the security features.
To do this, go to Settings / Phone Information / Software Information and tap several times on the wording "Build version" in order to unlock the "Developer options". If prompted, unlock your smartphone with your PIN or sign.
Now go back to the main Settings page, open the Developer Options and check that the "OEM Unlock" item is disabled, otherwise disable it and restart the device.
View attachment 5629493
Well now you have your Samsung with Original firmware again. Enjoy
Click to expand...
Click to collapse
Hi there. I tried it and didn't work for me.
Tried with differents CSC too, but my phone doesn't start the system. Just starts the download and recovery mode
It doesn't even show up the charging screen when powered off
Tried so many things and I can't boot my system...
I made a post with the info about what happened:
Need help with semi-bricked Note 10 Plus (SM-N975F) - Stuck on recovery/download mode
Didn't know where to post this exactly, to be honest. This will be a long post I was flashing AOSP roms in the phone. Tried to go back to One UI for the VoLTE thing In one of the AOSP roms I couldn't install it in Lineage Recovery (older version...
forum.xda-developers.com
Please help...
Ok, tell me where you get stuck ... or can you follow the whole guide but then the phone doesn't start?
Is the model number of your Note10+ is SM-N975F?
What original CSC did you have before you root?
RedSpikeJr said:
Hi there. I tried it and didn't work for me.
Tried with differents CSC too, but my phone doesn't start the system. Just starts the download and recovery mode
It doesn't even show up the charging screen when powered off
Tried so many things and I can't boot my system...
I made a post with the info about what happened:
Need help with semi-bricked Note 10 Plus (SM-N975F) - Stuck on recovery/download mode
Didn't know where to post this exactly, to be honest. This will be a long post I was flashing AOSP roms in the phone. Tried to go back to One UI for the VoLTE thing In one of the AOSP roms I couldn't install it in Lineage Recovery (older version...
forum.xda-developers.com
Please help...
Click to expand...
Click to collapse
ExileTM said:
Ok, tell me where you get stuck ... or can you follow the whole guide but then the phone doesn't start?
Is the model number of your Note10+ is SM-N975F?
What original CSC did you have before you root?
Click to expand...
Click to collapse
I followed the full guide, but I got stuck after flashing the firmware in Odin. It shows the screen of "Erasing data", and after that, nothing more
Even after locking again the bootloader
And yes, I ticked what's needed in Odin and used the .pit file
My model it's SM-N975F
The original CSC it's ZTO. Flashed the latest firmware
Ok so with Odin it didn't give you any problem. Let's say he freezes when he does the first boot that does the factory reset. Right?
Well odd, because once the original firmware is installed, I don't see why it should crash on boot ... unless there is a hardware problem in the phone's internal memory.
I know it may sound trivial, but the usb cable you use is good and did you use the latest version of Odin?
Have you checked maybe if the internal memory is right for you. If it is 256Gb or 512Gb
You could try this, if you see that it does not start try to enter the recovery (the original one) and delete everything you can, like cache and do a reset data directly from the recovery. Then try restarting and see if it starts.
If it still doesn't boot, try this thing.
Install TWRP custom recovery and enter once installed.
Go to Wipe Section in TWRP, Repair or Change partition, System and Data, and Changed Ext4 to EXTFAT. And changed back to Ext4. Eventually rerun the guide again.
ExileTM said:
Ok so with Odin it didn't give you any problem. Let's say he freezes when he does the first boot that does the factory reset. Right?
Well odd, because once the original firmware is installed, I don't see why it should crash on boot ... unless there is a hardware problem in the phone's internal memory.
I know it may sound trivial, but the usb cable you use is good and did you use the latest version of Odin?
Have you checked maybe if the internal memory is right for you. If it is 256Gb or 512Gb
Click to expand...
Click to collapse
The USB it's the original from Samsung.
The device is 256GB
ExileTM said:
You could try this, if you see that it does not start try to enter the recovery (the original one) and delete everything you can, like cache and do a reset data directly from the recovery. Then try restarting and see if it starts.
Click to expand...
Click to collapse
Tried this already. Didn't work
ExileTM said:
If it still doesn't boot, try this thing.
Install TWRP custom recovery and enter once installed.
Go to Wipe Section in TWRP, Repair or Change partition, System and Data, and Changed Ext4 to EXTFAT. And changed back to Ext4. Eventually rerun the guide again.
Click to expand...
Click to collapse
I tried this but not in the process of "Do the format and then do the Odin process" so I can try
I'm trying now with USB OTG to know if I can flash the system.img (and know if from there I can solve this)
ExileTM said:
If it still doesn't boot, try this thing.
Install TWRP custom recovery and enter once installed.
Go to Wipe Section in TWRP, Repair or Change partition, System and Data, and Changed Ext4 to EXTFAT. And changed back to Ext4. Eventually rerun the guide again.
Click to expand...
Click to collapse
Tried from reset data on official recovery to doing the change of format in TWRP and the doing all of the process again. No success.
Also tried with USB OTG with system, vendor, product and boot image. Neither
One thing that happened is that when trying to change the system partition to exFAT, it gave an error (system is not mounted) but changed the format to vFAT. Changing it to another option doesn't give that error, so I tried to do with another option and back to ext4.
I don't think it's a physical issue, if turns on, there is some hope at least
There is almost certainly a solution to your problem. (have you tried to do "format data" and typed "yes" in TWRP recovery?). Anyway, it's night at my place now, I'll see tomorrow to think of some other solution.
Tried already. Also tried to format the data with fastboot (Lineage Recovery gives the option to fastboot in Samsung)
I have the exackt same problem with my note10+ with 256GB and dual sim. and the problem you describe is also 100% what i experienced and still have as an issue... If you get to the point where you can solve the issue then please write me my friend. I will do the same ofcourse... btw can you use your pen in TWRP? i can only mark the files but not click them to run...? i have the idea that the TWRP for our model isnt built right somehow..
I assume you haven't solved the problem yet. In these days I have looked around but I have not found much ...
I saw a video, which through the ADB shell a guy was able to find the list of all partitions with the numbers of all the blocks and information and practically managed to rebuild the system partition from scratch, but I don't know if it works on samsung.
This is video:
Then another thing, what procedure did you follow for rooting? You may have had problems during the rooting process.
I followed this guide:
To update the situation
The battery of the phone inflated like a balloon, so I needed to go to a technician. I don't know for sure if that was caused by something physical, but will update when have some news
Ok, let me know if the technician can get you to restart the phone, and out of curiosity, he can bring the knox back to 0.
Hi, I was trying this today and I'm stuck at "An error has occured while updating the device software."
Odin was stuck at product.img for over an hour so I restarted the phone using volume down and power.
I tried again and it keeps getting stuck at product.img while the phone shows this error. Please could you help me out?
I followed all the steps exactly as you said, but I noticed while in download mode that it showed Warranty Void: 1
I did not root the phone, only flashed Pixel Experience and now trying to go back to OneUI
aaaajwedk said:
Hi, I was trying this today and I'm stuck at "An error has occured while updating the device software."
Odin was stuck at product.img for over an hour so I restarted the phone using volume down and power.
I tried again and it keeps getting stuck at product.img while the phone shows this error. Please could you help me out?
I followed all the steps exactly as you said, but I noticed while in download mode that it showed Warranty Void: 1
I did not root the phone, only flashed Pixel Experience and now trying to go back to OneUI
View attachment 5647587
Click to expand...
Click to collapse
Hello, then, the Warranty Void at 1 is triggered when you install a non-original firmware (in this case the PixelExperience), or when you change Recovery (ex: the TWRP) or you run the ROOT.
Any other software that is not in original firmware triggers the Knox to 0x1 irreversibly.
In your specific case, by installing the LineageOS Recovery and the PixelExperence ROM you have triggered the Knox at 0x1.
I am sorry.
Coming to your problem, the model of your phone what it is (ex: SM-N975F) and the CSC (ex: ITV). Did you download the original software for your exact model? Did you extract the PIT file from the original firmware and put it in the Option tab in Odin?
ExileTM said:
Hello, then, the Warranty Void at 1 is triggered when you install a non-original firmware (in this case the PixelExperience), or when you change Recovery (ex: the TWRP) or you run the ROOT.
Any other software that is not in original firmware triggers the Knox to 0x1 irreversibly.
In your specific case, by installing the LineageOS Recovery and the PixelExperence ROM you have triggered the Knox at 0x1.
I am sorry.
Coming to your problem, the model of your phone what it is (ex: SM-N975F) and the CSC (ex: ITV). Did you download the original software for your exact model? Did you extract the PIT file from the original firmware and put it in the Option tab in Odin?
Click to expand...
Click to collapse
Hello, I got it working just now by using a different cable and USB port. The procedure completed and the phone restarted by itself, and now its perfectly fine. Thank you so much for your help.
Yes, the phone is an SM-N975F. Despite Knox being tripped, my banking and payment apps are still working so I'm happy
I'm sure your article will be helpful to many more users. Thank you!
aaaajwedk said:
Hello, I got it working just now by using a different cable and USB port. The procedure completed and the phone restarted by itself, and now its perfectly fine. Thank you so much for your help.
Yes, the phone is an SM-N975F. Despite Knox being tripped, my banking and payment apps are still working so I'm happy
I'm sure your article will be helpful to many more users. Thank you!
Click to expand...
Click to collapse
OK well. Glad it was helpful. Yes, however, until you root all the apps will work. The only one are some applications by Samsung that will no longer work because they are based on the knox.
Otherwise like Google Pay, all banking and account apps, software updates should work smoothly.
Hi, is this guide usable for the S22 snapdragon version? My device is rooted, and I want to back to original firmware.