Hi All,
I've gone through all the different threads but I am going nowhere so I have decided to start a new one and track steps I have done so far. I have a Samsung Galaxy Note 10.1 Wifi-Only (GT-N8010) and it just stays stuck on the "Samsung Galaxy Note 10.1" Splash Screen.
Premise
#1: My tablet is not rooted.
#2. I am no longer interested in recovering any files in it. I just want it working again.
#3. I cannot access Recovery mode
#4. Fashed with Stock Rom from Sammobile using Odin (v3.10.7, v3.07, and v1.85): Says "PASS", restarts then > same issue. Attempted to go to Recovery using Power+Up Button on Splash screen> Still can't go to Recovery, can still access Download mode.
Any help would be greatly appreciated.
Can you access recovery?
Just flash stock 8010 rom via Odin .
JJEgan said:
Just flash stock 8010 rom via Odin .
Click to expand...
Click to collapse
I have looked everywhere but I can't seem to get a stock rom. I'll look further..is there any specific options that I might need to check/uncheck e.g F.Reset etc?
DroidTwe4kz said:
Can you access recovery?
Click to expand...
Click to collapse
No. I can access download but not recovery mode...
Update
Currently downloading stock firmware from SAMMOBILE
Model GT-N8010
Model name GALAXY Note 10.1
Country Australia
Version Android 4.1.2
Changelist 805288
Build date Wed, 20 Nov 2013 07:29:39 +0000
Product code XSA
PDA N8010XXUCMK2
CSC N8010XSACNA2
Marcel41 said:
Currently downloading stock firmware from SAMMOBILE
Model GT-N8010
Model name GALAXY Note 10.1
Country Australia
Version Android 4.1.2
Changelist 805288
Build date Wed, 20 Nov 2013 07:29:39 +0000
Product code XSA
PDA N8010XXUCMK2
CSC N8010XSACNA2
Click to expand...
Click to collapse
Flash it via Odin.
DroidTwe4kz said:
Flash it via Odin.
Click to expand...
Click to collapse
Still no Go. It says PASS, it restarts then same issue.
{
"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"
}
Comment boots un gas
Marcel41 said:
Still no Go. It says PASS, it restarts then same issue.
Click to expand...
Click to collapse
Uncheck auto reboot in Odin. Reboot manually into recovery mode and boot system
DroidTwe4kz said:
Uncheck auto reboot in Odin. Reboot manually into recovery mode and boot system
Click to expand...
Click to collapse
Yesterday, my stock, unrooted 8013 rebooted itself from sleep mode and I found it stuck at the splash screen when I went to pick it back up after a long conference call. I also can only get into download mode since Kies doesn't recognize my tablet. I found the only 8013 ROM on Sammobile and flashing it with Odin did nothing. I then downloaded the PIT file for the 8013 from a thread in this forum and retried with Odin, repartitioning and reflashing the ROM. I'm still stuck at the splash screen and only able to download. (I ran Odin again with your suggestion of turning Auto-Reboot off, didn't make a difference.) I'm seeing many users with the first gen notes experiencing this issue. Although I'm not seeing any errors when using Odin, do we have defective NAND memory? This problem seems to be increasing as our tablets age. Anyone have any other suggestions of potential fixes?
Well, I found a copy of official KK 4.4.2 and flashed it, since I had that version on my tablet and bootloaders supposedly don't work with earlier versions. Unfortunately, it didn't help. Installing other recoveries haven't worked. I still can't get into recovery mode, only download mode. Tomorrow, I'll try Nand Erase. I keep reading posts in various forums. It seems this is a common problem, even for stock, unrooted tablets. Some are saying Samsung is saying it's hardware related. I have a battery saver program that has a different battery icon when charging. My tablet can still see data because it switches to the 3rd party battery icon a few seconds after I put the tablet on charge. I'm hoping that if I have a file that's been corrupted in the cache or bootloader and can't be written to that Nand Erase will delete it and then be able to re-partition and properly flash a standard ROM. I've got a headache from reading so many posts that I'm quitting for the night. Samsung should make various standard ROMs available even for products at end of life. They overcharge and don't support their hardware very well. It's frustrating trying to find official ROMs for various models.
DroidTwe4kz said:
Uncheck auto reboot in Odin. Reboot manually into recovery mode and boot system
Click to expand...
Click to collapse
Same thing.. I restarted manually holding POWER+VOLUME UP. When the Samsung Galaxy Note screen appears, I release the power button while holding VOLUME UP. It blinks but goes back to the Samsung Galaxy Note 10.1 screen.
Marcel41 said:
Same thing.. I restarted manually holding POWER+VOLUME UP. When the Samsung Galaxy Note screen appears, I release the power button while holding VOLUME UP. It blinks but goes back to the Samsung Galaxy Note 10.1 screen.
Click to expand...
Click to collapse
Did you already try to flash PhilZ kernel or recovery?
DroidTwe4kz said:
Did you already try to flash PhilZ kernel or recovery?
Click to expand...
Click to collapse
I tried installing both recoveries, inluding PhilZ's, which were included in the official KK 4.4.2 ROM zip from XDA forums. Didn't work. There are far more dicussions of this issue--soft brick with no access to recovery mode on all Samsung devices--on other forums. I think those who are speculating that a corrupted cache file or partition file has become read only and is preventing successful flashing are right. Without access to recovery, we're totally stuck. There are some suggesting that those of us with non-removable batteries carefully access our batteries, remove the cables (plugins, not soldered) for 12 seconds and see if we can then boot into recovery mode. That's the easy fix for Samsung phones with removable batteries. This weekend, I'm going to remove the back of my Note 10.1 and unplug the battery connectors for 12 seconds and then see if I can boot into recovery. I've asked a senior member with experience with Odin Nand Erase some questions and may go that route if the battery disconnect doesn't work to get me into recovery. If Odin can still write to the Note after Nand Erase and rewrite the Pit file an official ROM that may be the only way to get rid of the corrupted file that's become read only.
mke1973 said:
I tried installing both recoveries, inluding PhilZ's, which were included in the official KK 4.4.2 ROM zip from XDA forums. Didn't work. There are far more dicussions of this issue--soft brick with no access to recovery mode on all Samsung devices--on other forums. I think those who are speculating that a corrupted cache file or partition file has become read only and is preventing successful flashing are right. Without access to recovery, we're totally stuck. There are some suggesting that those of us with non-removable batteries carefully access our batteries, remove the cables (plugins, not soldered) for 12 seconds and see if we can then boot into recovery mode. That's the easy fix for Samsung phones with removable batteries. This weekend, I'm going to remove the back of my Note 10.1 and unplug the battery connectors for 12 seconds and then see if I can boot into recovery. I've asked a senior member with experience with Odin Nand Erase some questions and may go that route if the battery disconnect doesn't work to get me into recovery. If Odin can still write to the Note after Nand Erase and rewrite the Pit file an official ROM that may be the only way to get rid of the corrupted file that's become read only.
Click to expand...
Click to collapse
I think that you wiped /boot partition and then rebooted your phone. That's what causing that you can't access recovery
DroidTwe4kz said:
I think that you wiped /boot partition and then rebooted your phone. That's what causing that you can't access recovery
Click to expand...
Click to collapse
No, i,m till soft=bricked and boot to the splash logo. what most people don't understand who haven't experienced this is not being able to get to recovery to wipe cache seems to cause Odin to be unable to flash anything even though it doesn't give error messages. Those with phones that have removable batteries are generally able to remove their batteries and then get to recovery and wipe cache. Doing that, they are able to flash ROMs. This has led many to speculate that a file or files have become corrupted and read only, preventing successful flashing. This is a long standing issue with most Samsung devices.
mke1973 said:
No, i,m till soft=bricked and boot to the splash logo. what most people don't understand who haven't experienced this is not being able to get to recovery to wipe cache seems to cause Odin to be unable to flash anything even though it doesn't give error messages. Those with phones that have removable batteries are generally able to remove their batteries and then get to recovery and wipe cache. Doing that, they are able to flash ROMs. This has led many to speculate that a file or files have become corrupted and read only, preventing successful flashing. This is a long standing issue with most Samsung devices.
Click to expand...
Click to collapse
Maybe you can disassemble your device and remove battery manually.
DroidTwe4kz said:
Maybe you can disassemble your device and remove battery manually.
Click to expand...
Click to collapse
I won't need to completely remove the battery, just unplug the connector cables. If the battery disconnect doesn't work, then I may try Nand Erase--apparently, Odin can flash Pit files and ROMs after it does Nand Erase. If none of this works, then my Nand memory is totally corrupted and unrepairable. What surprises me is how often this happens on totally stock Samsung devices. Samsung's Nand may be inferior and easily corrupted.
---------- Post added at 11:28 AM ---------- Previous post was at 10:57 AM ----------
I looked at the iFixit teardown of the Note 10.1 just to see if the Nand chip is soldered. Its not, it's plugged in and the board is screwed down and easy to remove. Replacement Nand (Samsung KLMAG2GE4A NAND flash memory) costs $25 USD. Should battery disconnect or Nand Erase not work, I'll replace the Nand chip.
mke1973 said:
I won't need to completely remove the battery, just unplug the connector cables. If the battery disconnect doesn't work, then I may try Nand Erase--apparently, Odin can flash Pit files and ROMs after it does Nand Erase. If none of this works, then my Nand memory is totally corrupted and unrepairable. What surprises me is how often this happens on totally stock Samsung devices. Samsung's Nand may be inferior and easily corrupted.
---------- Post added at 11:28 AM ---------- Previous post was at 10:57 AM ----------
I looked at the iFixit teardown of the Note 10.1 just to see if the Nand chip is soldered. Its not, it's plugged in and the board is screwed down and easy to remove. Replacement Nand (Samsung KLMAG2GE4A NAND flash memory) costs $25 USD. Should battery disconnect or Nand Erase not work, I'll replace the Nand chip.
Click to expand...
Click to collapse
Try disconnecting cables on the battery. It will hopefully fix the problem. I own Note 10.1 and I haven't ever had this kind of problem before. Every time when I get into bootloop, I used PhilZ recovery and that fixed my problem.
Related
k0nane presents...
Odin: Return to Stock, fix soft brick
Sponsored by k0nane.info. Have you tipped your devs today?
DO NOT CHECK REPARTITION! YOU HAVE BEEN WARNED!
Why the big red warning? Far too many people have broken their devices by not following these instructions! Search the forums, or drop by IRC - you'll see plenty of examples.
These instructions should fix your soft-bricked or broken phone as long as you can get it into download mode. Make sure you have drivers already installed on your Windows computer before starting. Please read them all the way through and then begin.
Code:
#include <external/cyanogenmod/std_disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Instructions
Download Odin 1.85 - see section below.
Download the stock TAR for your device - see section below.
Extract the contents of odin-185.zip and the 7zip archive.
Run Odin 1.85.exe, and prepare Odin:
Check "auto-reboot", and uncheck all other options.
Click PDA and select the TAR you downloaded. Click PIT and select the PIT your downloaded.
Put your device into Download Mode:
Connect the USB cable to your PC, but NOT your device.
Remove the battery.
Reinsert the battery.
Hold down Volume Up + Volume Down + Power.
You should now be at Download Mode. Make sure Odin looks similar to the following:
{
"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"
}
Click Start in Odin.
Wait! When complete, Odin should appear like the following:
That's it! Your device will autoreboot, and your phone should be working properly again. Be sure to wipe data in recovery after completing this process if you have further issues.
Downloads
Download Odin 1.85
Download PIT
Download Stock TAR
Download Stock TAR (Mirror)
Credits:
DrTaru: stock device, remote access, lots of testing, screenshots, patience
Shabbypenguin: Shabbypenguin (do I need to say more?)
P-O-S-T :: R-E-S-E-R-V-E-D
Original artwork by Pendulum via Gasolin3.
...for future use.
Follow me on Twitter @k0nane and @publik0!
boom! once again
No 4G or Wifi Afterwards...
I just did the Factory Recovery on my phone 'cause I messed something up and now I can't get the 4G or Wifi to work... I'm connected to the Wifi Network and 4G icon is on my phone but there's no internet connection...any help please?
Hi
I need 2 folder app and framework to build some app then send to my friend because my friend don't know how to copy it from system. Please use root explore to copy it then upload for me .
Thanks
Desertstorm00 said:
I just did the Factory Recovery on my phone 'cause I messed something up and now I can't get the 4G or Wifi to work... I'm connected to the Wifi Network and 4G icon is on my phone but there's no internet connection...any help please?
Click to expand...
Click to collapse
Wipe cache and data in factory recovery.
doantri said:
Hi
I need 2 folder app and framework to build some app then send to my friend because my friend don't know how to copy it from system. Please use root explore to copy it then upload for me .
Thanks
Click to expand...
Click to collapse
Extract them from the system image yourself.
stuck at param.lfs
anyone else stuck at param.lfs when trying to restore to stock??
mayesmwhite said:
anyone else stuck at param.lfs when trying to restore to stock??
Click to expand...
Click to collapse
Use a non-stock USB cable, and switch ports on your PC. If you continue to have issues, redownload the TAR or use another computer.
Ok, yes this is my first post and yes, the "don't check Re-Partition!" is in red everywhere... and I am a relatively experienced at rooting devices (this is the second Blaze I was doing, first one rooted with zero problems... That being said: What are the recovery options if one does open a new tar using oden and forgets to un-check re-partition (like I did earlier today)?
I have since flashed both the recovery rom and CWM, however the phone still prompts me for a password and after I input the correct password it goes into a boot loop.
Steps taken:
1. Flashed the k0nane root kernel and forgot to uncheck re-partition. ( Yes I know... laugh it up... )
2. Dropped the F-bomb in front of the kids about 1 second after pressing "Start" once I realized what I had done...
3. Followed the "THE ODIN THREAD: Return to stock instructions, fix soft brick"
4. At the hard reset part where you go into recovery mode I received the green/red dot screen response
5. Successfully flashed the CWM, therefore fixing the green/red dot recovery mode issue
6. Performed a hard reset using CWM, however...
After all this I still am getting the prompt for password (I would have expected a factory reset would make this go away) and subsequent boot loop upon entering the correct password.
Would saving a CWM recovery rom to my sd card of my "good' Blaze and transferring/flashing it to my broken blaze fix the issue?
Edit:
- I tried it (flashing my other blaze's recovery rom) and no it does not fix the password prompt to boot loop issue... (It didn't make anything worse either... how is it I can flash a rom and still have a password prompt (my working droid is not password protected...)?
chlor3 said:
Ok, yes this is my first post and yes, the "don't check Re-Partition!" is in red everywhere... and I am a relatively experienced at rooting devices (this is the second Blaze I was doing, first one rooted with zero problems... That being said: What are the recovery options if one does open a new tar using oden and forgets to un-check re-partition (like I did earlier today)?
I have since flashed both the recovery rom and CWM, however the phone still prompts me for a password and after I input the correct password it goes into a boot loop.
Steps taken:
1. Flashed the k0nane root kernel and forgot to uncheck re-partition. ( Yes I know... laugh it up... )
2. Dropped the F-bomb in front of the kids about 1 second after pressing "Start" once I realized what I had done...
3. Followed the "THE ODIN THREAD: Return to stock instructions, fix soft brick"
4. At the hard reset part where you go into recovery mode I received the green/red dot screen response
5. Successfully flashed the CWM, therefore fixing the green/red dot recovery mode issue
6. Performed a hard reset using CWM, however...
After all this I still am getting the prompt for password (I would have expected a factory reset would make this go away) and subsequent boot loop upon entering the correct password.
Would saving a CWM recovery rom to my sd card of my "good' Blaze and transferring/flashing it to my broken blaze fix the issue?
Edit:
- I tried it (flashing my other blaze's recovery rom) and no it does not fix the password prompt to boot loop issue... (It didn't make anything worse either... how is it I can flash a rom and still have a password prompt (my working droid is not password protected...)?
Click to expand...
Click to collapse
This thread might help you out. Brick 2 Fix
I was hoping i had stumbled upon a new way to fix my "soft brick" since not everyone has access to two phones..
-chlor3
chlor3 said:
I was hoping i had stumbled upon a new way to fix my "soft brick" since not everyone has access to two phones. I am still considering installing dropbear to the good phone using CWM and flashing to the broken phone in an attempt to get shell.
-chlor3
Click to expand...
Click to collapse
Do you have a working Blaze? If so, I only need two partitions... Anyone? Our only Blaze owner on IRC returned his.
I'm thinking of returning mine too. Its really a let down coming from my vibrant
k0nane said:
Do you have a working Blaze? If so, I only need two partitions... Anyone? Our only Blaze owner on IRC returned his.
Click to expand...
Click to collapse
I can attempt to help you get what you need. I'm fairly new to this stuff but would be happy to help if I can.
So I tried out the CM7 alpha and it froze at the loading screen. I'm doing it wrong and can't figure out how to get a logcat.
I'm trying to get back to stock and it seems to work other that the 'market' app is greyed out and it says that it's not installed on my phone. I've tried re-rooting and cwm and still the market app is greyed and doesn't show up anywhere other than the app drawer.
When I flash back to stock via Odin, I'm already past the gmail login part.
Even after adding cwm, I can't figure out how to get to recovery via hardware buttons to wipe or whatever.
Anybody have any ideas?
Nevermind maybe. I added a Google Play apk and now things are syncing up. I'm not sure what happened though.
So it looks like I may be the only one messing this up...
I flashed the cm7 alpha a bit ago. It's making progress.
Now that I'm trying to get back to stock I'm getting a loop between the Samsung logo and the Android blasting off.
I flashed the cwm but can't for the life of me figure out how to boot into recovery using hardware keys.
Anybody have any ideas? I'm lost w/ a useless phone ha.
Try this
1. Turn off phone
2. Remove battery
3. Plug USB from computer to phone
4. Insert battery
5. Hold volume up + volume down
6. While still held push and hold the power button keeping all three pressed
7. Wait for Samsung logo to appear
8. When screen goes black wait half a second and release all buttons
9. In a second or 2 should be in recovery
If that doesn't work please leave outcome, I have another method if that fails
Sent from my SGH-T769 using xda premium
xArcane1x said:
Try this
1. Turn off phone
2. Remove battery
3. Plug USB from computer to phone
4. Insert battery
5. Hold volume up + volume down
6. While still held push and hold the power button keeping all three pressed
7. Wait for Samsung logo to appear
8. When screen goes black wait half a second and release all buttons
9. In a second or 2 should be in recovery
If that doesn't work please leave outcome, I have another method if that fails
Sent from my SGH-T769 using xda premium
Click to expand...
Click to collapse
im boot looping like in the above thread between the samsung logo and the android screen - ive tried 2 different cables/and downloads
im coming from root and cwm - but needed to go back to stock...
...im not a noob but im stuck and kinda shrugging - help? lol
---------- Post added at 02:57 PM ---------- Previous post was at 02:56 PM ----------
of course im using odin - all succeeding - not failing as odin reports
getting to root and cwm were simple seems this should be but just looping
---------- Post added at 03:52 PM ---------- Previous post was at 02:57 PM ----------
well - nevermind my post although its apparently happening to some devices.
i found a nandroid backup on my SDCARD thankfully i hadnt deleted (as im going back to my g2x lol) - and after i ran it everythings fine; did a factory reset on it and it appears to be good; not sure if it's kept root and wont know until i install tb again on it - but thanks for now guys!
The stock tar file isn't being recognized by Odin b/c it's not a "tar" file. Can someone please advise how I can get Odin to recognize it? I really need to get back to stock.
Thanks
Did you unzip and extract the contents of the zip? Hopefully that will help you
Sent from my SGH-T769 using xda app-developers app
Good Morning
I have spent all night trying to determine how to unbrick my brand new Note 5. I was able to use Odin to root the device, but then when I rebooted after trying to install TWRP, it is just plain bricked. I cannot get Odin to install any firmware, i can boot into recovery mode, but wiping data and cache does nothing. I get a constant bootloop that says Kernel is not SEAndroid and Custom Binary blocked by FRP.
Every time i plug the phone into the laptop, it says that the USB device is unrecognizable. I have installed Samsung USB drivers. I am just at a loss, Odin fails every time.
I will admit that I am a pathetic noob and should have waiting a longer time to do this. I had just given up my iPhone on Sunday.
Any help would be appreciated.
Delete the Samsung drivers and then reinstall them, that may get your computer to recognize your device. As far as the rest idk
Trizen said:
Delete the Samsung drivers and then reinstall them, that may get your computer to recognize your device. As far as the rest idk
Click to expand...
Click to collapse
I have done that several times so far. The thing is, the system says not reco. but Odin sees it. I can boot into both download and recovery. So is this considered soft or hard bricked?
molodoko said:
I have done that several times so far. The thing is, the system says not reco. but Odin sees it. I can boot into both download and recovery. So is this considered soft or hard bricked?
Click to expand...
Click to collapse
You can't brick your phone. That terminology is silly.
What Odin are you using? You have to use 10.0.7.1 something like that.
Also make sure you are flashing your device model firmware.
Try another computer if Odin fails on your current computer.
Brava27 said:
You can't brick your phone. That terminology is silly.
What Odin are you using? You have to use 10.0.7.1 something like that.
Also make sure you are flashing your device model firmware.
Try another computer if Odin fails on your current computer.
Click to expand...
Click to collapse
I have used Odin 3.09 and 3.10.7. I got my firmware from Sammobile and search by my device model SM-N920T. I have tried this on two different machines, Win8 and Win10. Someone on another thread asked me to try a few different ways to attempt so I will try this:
One "trick" that might work:
Without your phone plugged-in to your PC,
Set up ODIN w/the firmware of choice,boot-up your phone,plug-in to PC,then,boot into download mode while plugged-in.
Try this,or several variations of it.
I had to do this using ODIN on my Note5 to get programs/ROMS to load up.
This isn't common,but,I've seen a few other people have to do this,it's likely a PC-Driver related thing (I have a somewhat uncommon PC,a Gateway,that may explain it)............from Kolio on AndroidForums
molodoko said:
I have used Odin 3.09 and 3.10.7. I got my firmware from Sammobile and search by my device model SM-N920T. I have tried this on two different machines, Win8 and Win10. Someone on another thread asked me to try a few different ways to attempt so I will try this:
One "trick" that might work:
Without your phone plugged-in to your PC,
Set up ODIN w/the firmware of choice,boot-up your phone,plug-in to PC,then,boot into download mode while plugged-in.
Try this,or several variations of it.
I had to do this using ODIN on my Note5 to get programs/ROMS to load up.
This isn't common,but,I've seen a few other people have to do this,it's likely a PC-Driver related thing (I have a somewhat uncommon PC,a Gateway,that may explain it)............from Kolio on AndroidForums
Click to expand...
Click to collapse
If it's bootlooping, you must go into stock recovery and wipe data, factory reset!
{
"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"
}
Brava27 said:
If it's bootlooping, you must go into stock recovery and wipe data, factory reset! View attachment 3569513
Click to expand...
Click to collapse
I have gone into recovery and wiped data however that does nothing. here are the steps I have done:
Power phone on holding the volume up, home and power buttons - it installs system update
-wipe data/factory reset
I get red line: E: failed to mount /preload (No such file or directory)
then using what was suggested in prior post
When trying to flash with Odin it gets to cm.bin and then fails.
Have you tried re-downloading the firmware from sammobile.com? Try a different build number?
Sent from my SM-N920T using Tapatalk
Brava27 said:
Have you tried re-downloading the firmware from sammobile.com? Try a different build number?
Yes i have. i grabbed the latest and the one before that. Maybe I should go one further.
I also tried using nobleltetmStockRecovery.tar.md5
I have gotten most success from this though it just hangs after NAND Write Start!!
Click to expand...
Click to collapse
molodoko said:
Brava27 said:
Have you tried re-downloading the firmware from sammobile.com? Try a different build number?
Yes i have. i grabbed the latest and the one before that. Maybe I should go one further.
I also tried using nobleltetmStockRecovery.tar.md5
I have gotten most success from this though it just hangs after NAND Write Start!!
Click to expand...
Click to collapse
That method given to me earlier was the key, it was the order in which i plugged it in, turned it on and boom it worked!!
I am not going to do this again until i am much more well versed in the Android world. Thank you to everyone who helped! :laugh::laugh::laugh::good::good::good:
Click to expand...
Click to collapse
molodoko said:
Good Morning
I have spent all night trying to determine how to unbrick my brand new Note 5. I was able to use Odin to root the device, but then when I rebooted after trying to install TWRP, it is just plain bricked. I cannot get Odin to install any firmware, i can boot into recovery mode, but wiping data and cache does nothing. I get a constant bootloop that says Kernel is not SEAndroid and Custom Binary blocked by FRP.
Every time i plug the phone into the laptop, it says that the USB device is unrecognizable. I have installed Samsung USB drivers. I am just at a loss, Odin fails every time.
I will admit that I am a pathetic noob and should have waiting a longer time to do this. I had just given up my iPhone on Sunday.
Any help would be appreciated.
Click to expand...
Click to collapse
It happened to me too i was scared i thought ihad messed my phone up but I found a solution
You can try different usb port and different cable too. And which tab you use for the installing the stock firmware? FRP lock is here because you didnt open the oem unlock before the installing customized file. You have to install stock with odin. and then factory reset and then you can open the device get the development settings and disable the oem unlock.
SM-N920I cihazımdan Tapatalk kullanılarak gönderildi
Brava27 said:
You can't brick your phone. That terminology is silly.
What Odin are you using? You have to use 10.0.7.1 something like that.
Also make sure you are flashing your device model firmware.
Try another computer if Odin fails on your current computer.
Click to expand...
Click to collapse
Sure you can brick your phone, and the only thing silly about the term brick is the over use of it.
I went ahead and exchanged my Note 5 under warranty. I got my new phone, flashed TWRP, flashed TEKHD, phone worked great until the battery died. I turned it back on and it was stuck on the Start Up screen with an error. I did not record the error code but it was on the top left hand corner in Red. Something about not being able to verify something. So I weant ahead and flashed stock rom and the unit keeps restarting into stock recovery. I've wiped data and cache and continues to be stuck. I flashed G1 firmware again and same thing. Any ideas what the problem might be? After restarting the phone in stock recovery, it reboots into recovery but with an error at the bottom in red. It reads:
Support APU: 3 <--------This is in white
dm-verity verification failed... <------This is in red
Need to check DRK first... <----------Also in red.
ANy ideas? Flashing back to stock, clearing data does not seem to help.
F9zSlavik said:
I went ahead and exchanged my Note 5 under warranty. I got my new phone, flashed TWRP, flashed TEKHD, phone worked great until the battery died. I turned it back on and it was stuck on the Start Up screen with an error. I did not record the error code but it was on the top left hand corner in Red. Something about not being able to verify something. So I weant ahead and flashed stock rom and the unit keeps restarting into stock recovery. I've wiped data and cache and continues to be stuck. I flashed G1 firmware again and same thing. Any ideas what the problem might be? After restarting the phone in stock recovery, it reboots into recovery but with an error at the bottom in red. It reads:
Support APU: 3 <--------This is in white
dm-verity verification failed... <------This is in red
Need to check DRK first... <----------Also in red.
ANy ideas? Flashing back to stock, clearing data does not seem to help.
Click to expand...
Click to collapse
First thing, You are flashing the correct firmware version correct? i had the dm verity issue with my wifes note 5. I fixed it by extracting the boot.img and system.img from the odin file and flashing system.img then boot.img and it booted. Supposedly if you do this and take an update or factory reset, you will have to perform these steps again. I just flashed twrp and rooted and she has been happily flashing away again without issue.
Yes, I believe it is the correct. I was running G1. It was working fine as I said it just suddenly stop working after the battery drained.
How do you flash the system and boot? Same way? Odin -> AP flash?
Does anyone have a solution for this? Can't use my Note 5 ;/ I tried doing as suggested but Odin will not see either the boot or img. Also, I can not flash TWRP. Which does not make sense as I was able to before. Something about FAP Lock.
Took a picture of it.
{
"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"
}
So I did some more google searching and was lead to this thread
http://forum.xda-developers.com/note5/help/how-to-solve-dm-verity-verification-t3293306
Says extract original firmware and delete cache and repackage it. Which I went ahead and deleted but when I try to repackage it, it gives me an error saying it is missing the cache.rfs. The tutorial uses a difference version of TAR.MD5 PACKAGER. The latest version I have has different options. It will not let me create a full rom unless the cache.rfs is there.
I am confuse and I need help.
These are the options I am presented with
https://scontent.fsan1-2.fna.fbcdn.net/t31.0-8/14444752_10209691582821769_8183071702963249499_o.jpg
and these are the options that are present in the tutorial.
They are different.
Sorry, I didn't get any notification for this thread. I actually took the boot img and system img and using 7zip added them to a new archive with the .tar extension and it worked. Thought it would be more difficult then that but it wasnt. Then I flashed them individually through Odin the same way you flash any Odin using the ap slot.
Sent from my SM-N920T using Tapatalk
---------- Post added at 08:39 PM ---------- Previous post was at 08:38 PM ----------
F9zSlavik said:
Does anyone have a solution for this? Can't use my Note 5 ;/ I tried doing as suggested but Odin will not see either the boot or img. Also, I can not flash TWRP. Which does not make sense as I was able to before. Something about FAP Lock.
Took a picture of it.
Click to expand...
Click to collapse
Also, fap lock happened to me also, flashing the Odin files like I stated previously worked to boot up stock, then go to settings make sure all unlocking options are checked and your good. Some reason it reset everything on her and we still don't know why or what.
Sent from my SM-N920T using Tapatalk
I downloaded 7zip, added the boot and system into a new archive file, removed the 7 zip extention and replaced it with .TAR. I started Odin, loaded it under AP, and it does nothing. It loads but either sits and does nothing or it crashes. Phone simply stays in download mode. I don't understand why this phone refuses to return back to stock!!!
Any other ideas? I tried the latest firmware with the latest Odin and still nothing.
This is @#$%*[email protected] BS!!! I received my replacement phone and I restored my TWRP back up I had made and the moment I restarted the phone I has the same bull**** error!!!! Boots into Recovery mode (stock) with the same god damm error! WTF!!!!
I went through the proper steps of installing twrp and then restored from a back up. I had to restart the phone and got an error code saying FRP blocked something, went into Recovery, and is now stuck on there again. How the hell am I getting the same error code on 2 different phones! I'm so pist!
I tried, like before, to restore G1 firmware, goes through everything fine in Odin, then it restarts, you see the little android in the back saying it is updating, then erasing, then abruptly restarts before it reaches 100 percent, restarts to the same android screen and errors out with the following message "no command", then boots into Recovery.
Does anyone have any idea wtf is going on and how to fix this god forsaken issue? I was really hoping to use this phone tonight. Otherwise I have to order another phone -_-
Were you trying to write something?
I made a video of me trying to install stock firmware and what happens as a result.
https://www.youtube.com/watch?v=QBYdsJWqFw8
I had never seen this case, I saw your video and in the same YouTube saw some videos explaining the solution with a program. check out these tutorials can be the solution or see where some expert if you are unsure ...
F9zSlavik said:
I downloaded 7zip, added the boot and system into a new archive file, removed the 7 zip extention and replaced it with .TAR. I started Odin, loaded it under AP, and it does nothing. It loads but either sits and does nothing or it crashes. Phone simply stays in download mode. I don't understand why this phone refuses to return back to stock!!!
Any other ideas? I tried the latest firmware with the latest Odin and still nothing.
Click to expand...
Click to collapse
So your not getting the red text with the error anymore? That lock happened to me but i also had the dm-verity and drk errors. I flashed the systme.img and boot.img like I stated ealrier, except you have to do them individually. First the system then the boot. Then it will let you in. That FAP lock is in settings and has to be turned off before flashing twrp.
I got my solution from the same thread except I followed post #18. Not sure if it would help you. Do you know what firmware it was on when you got it? If i'm not mistaken you may have to go backto the exact firmware you had before you tried twrp and all.
scrappy610 said:
So your not getting the red text with the error anymore? That lock happened to me but i also had the dm-verity and drk errors. I flashed the systme.img and boot.img like I stated ealrier, except you have to do them individually. First the system then the boot. Then it will let you in. That FAP lock is in settings and has to be turned off before flashing twrp.
I got my solution from the same thread except I followed post #18. Not sure if it would help you. Do you know what firmware it was on when you got it? If i'm not mistaken you may have to go backto the exact firmware you had before you tried twrp and all.
Click to expand...
Click to collapse
Hey thanks for responding back. I am still getting the red text error. I did as you mentioned, I did the system followed by the boot. Still the same error. I did the system and allowed it to boot. Same error. Went into download mode and loaded boot in AP. Same thing. So then I went and did System again, but did not allow to to boot, restarted phone and instantly went into Download Mode, loaded the Boot, restarted the phone, same error.
I don't understand this error.
At first I thought this happened because I did not enable ‘OEM Unlock’. So when I got my new phone, I made sure of turning that on. Then I installed TWRP with no problems. Restarted the phone and bam, red text error. The one thing I did not enable, was ‘USB debugging’. Could this have cause the red text error this time around?
I don't know what else to do
Its possible, but i doubt it seeing as how your going into download mode.
I never got the red text to go away. It was there every time i did a factory reset or ota upgrade. But i always got it to boot using the system and boot. So, you have fap turned off now? If so, you should be able to flash twrp. That was the only thing keeping me from flashing twrp. After i got it to boot, then turned on oem unlock, i rebooted to download mode, flashed twrp and then custom rom and kernel and never saw the text or had an issue with it again.
Sent from my SM-G935P using Tapatalk
scrappy610 said:
Its possible, but i doubt it seeing as how your going into download mode.
I never got the red text to go away. It was there every time i did a factory reset or ota upgrade. But i always got it to boot using the system and boot. So, you have fap turned off now? If so, you should be able to flash twrp. That was the only thing keeping me from flashing twrp. After i got it to boot, then turned on oem unlock, i rebooted to download mode, flashed twrp and then custom rom and kernel and never saw the text or had an issue with it again.
Sent from my SM-G935P using Tapatalk
Click to expand...
Click to collapse
I can't flash TWRP so I am assuming it is on. The way its turned off is via debug mode off and oem off right? But I was able to flash it before this problem happened. That is what confuses me
Yeah. If its on it should tell you when your in download mode. And if it is only way to get it off is flash bone stock.
Sent from my SM-G935P using Tapatalk
I've done stock flash. I don't know where I went wrong. I just got my 3rd replacement. I am going to try and install TWRP, nothing else. Debugging mode on and OEM Unlock on.
Have you tried going back to stock com and then reset from within the rom ? Worked for me once after I did an at from flash on my Sprint phone
Hav you tried full wipe? once you ODIN back to stock then you should be fine. if you are still having trouble you should do a full wipe and restart.
I have Galaxy S6 and when i tried to install new ROM via usb-otg stick something strange happened and now my whole phone is unusable.
TWRP just says 0mb for internal storage and i cannot install anything since i cannot mount anything. I have looked pretty much all the "fixes" but nothing has helped so far :\ I have tried to format, wipe, change partition type, install, etc. And nothing has helped me so far. So if there are any ideas left please help :]
I think i still have root and when entering TWRP it does not ask password since i have done dm-verify long time ago.
Here is video showing some of the things: https://youtu.be/wXVVRBmRROU
go to download mode and flash stock firmware with ODIN. than flash twrp, enter recovery (twrp) before system. and boot to stock.
than try again.
HowJesNo said:
go to download mode and flash stock firmware with ODIN. than flash twrp, enter recovery (twrp) before system. and boot to stock.
than try again.
Click to expand...
Click to collapse
Hi!
I got stock firmware from Updato and then began to flash with Odin and it seemed that it would work since it was actually doing something at first (while trying to flash ROM's Odin crashes) but then it gave an error and stopped :\ Here is an picture of Odin's log.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I guess you had better restore factory image, make sure the system comes back. then flash updated version OS.
You can trying to use ODIN to do that. or using fastboot flash .....
https://gs6.gadgethacks.com/how-to/unroot-restore-samsung-galaxy-s6-back-stock-0162155/
Hope to it is helpful.
DARKKi said:
I have Galaxy S6 and when i tried to install new ROM via usb-otg stick something strange happened and now my whole phone is unusable.
TWRP just says 0mb for internal storage and i cannot install anything since i cannot mount anything. I have looked pretty much all the "fixes" but nothing has helped so far :\ I have tried to format, wipe, change partition type, install, etc. And nothing has helped me so far. So if there are any ideas left please help :]
I think i still have root and when entering TWRP it does not ask password since i have done dm-verify long time ago.
Here is video showing some of the things: https://youtu.be/wXVVRBmRROU
Click to expand...
Click to collapse
Okay, i have new problem. After i tried to flash with odin now i got only one place i can boot into and it looks like this:
I downloaded Smart Switch and entered emergency recovery but i was met with this screen and i have no idea from where to get the code.
in smart switch emergency upgrade and initialization, if will ask model and S/N.
model is SM-G920F and S/N in on the back of the phone. all caps.
HowJesNo said:
in smart switch emergency upgrade and initialization, if will ask model and S/N.
model is SM-G920F and S/N in on the back of the phone. all caps.
Click to expand...
Click to collapse
Smart Switch did not even have that option but i tried it with Kies and got this
smart switch should have same option. I found googling that in never versions that option was not functional due to Samsung not wanting people to debrand their phone. so older version is needed.
just got mine in a similar bootloop.
can u get into download mode?
If phone can't turn off do this:
- hold volume down + power, (that is reboot)
- as the screen goes black move finger to volume up + home key.
that should get you to download mode. now use odin to flash stock firmware.
HowJesNo said:
smart switch should have same option. I found googling that in never versions that option was not functional due to Samsung not wanting people to debrand their phone. so older version is needed.
just got mine in a similar bootloop.
can u get into download mode?
If phone can't turn off do this:
- hold volume down + power, (that is reboot)
- as the screen goes black move finger to volume up + home key.
that should get you to download mode. now use odin to flash stock firmware.
Click to expand...
Click to collapse
I tried that before and i tried it now again and same result:
is that firmware higher version than one previously installed?? i had that issue once!
G920FXXE5EQJ1........ try with any other with higher number. UK (BTU) is G920FXXU6ERC9
The problem is hidden.img file.
Search in google "galaxy s6 hidden.img fail" and solved.
HowJesNo said:
is that firmware higher version than one previously installed?? i had that issue once!
G920FXXE5EQJ1........ try with any other with higher number. UK (BTU) is G920FXXU6ERC9
Click to expand...
Click to collapse
Hi! I got the Model name but for some reason i cannot find S/N in the box or anywhere else
vindau said:
The problem is hidden.img file.
Search in google "galaxy s6 hidden.img fail" and solved.
Click to expand...
Click to collapse
Thanks a lot for this! I was able to install stock rom.
---
But then trouble started again. Boot screen came up and then text and mount problems like "failed to mount efs (no such file or directory)" :crying:
Here is the video about it, anything i could do now? I installed TWRP and it still says internal storage 0mb and formatting has no effect.
Video - https://youtu.be/OBfhTRWUZeU
I got little progress. I found the S/N from back of the phone with torch which i could not see without (Thanks for Augustin @ XDA Discord for this!) and then i tried to use Smart Switch but it does not recognize the phone and only option is "Emergency Firmware Recovery" and it needs some recovery code.
Then i tried Kies and it does not detect the device either and i tried the option "Firmware Upgrade and Initialization" and typed out model and S/N and after that it said "SM-G920F" does not support initializing"
So anyone knows what i could do now? Seems like i am running out of options here
Augustin also said that i should try pit but i have never used that feature in Odin so help with that would be awesome if it can remedy this situation somehow
You need the .pit file according to your csc. Found it here: https://forum.xda-developers.com/galaxy-s6/general/g920f-pit-file-banded-firmwares-t3118459
allensd.cordero said:
You need the .pit file according to your csc. Found it here: https://forum.xda-developers.com/galaxy-s6/general/g920f-pit-file-banded-firmwares-t3118459
Click to expand...
Click to collapse
Thanks a lot! I will begin investigating and learning!
Hopefully this would solve this damn problem
And thanks a lot for this info!
allensd.cordero said:
You need the .pit file according to your csc. Found it here: https://forum.xda-developers.com/galaxy-s6/general/g920f-pit-file-banded-firmwares-t3118459
Click to expand...
Click to collapse
Thanks a lot! Finally using pit got the partitions right and phone is working like a charm now! :]
This might be a bit late but I am also currently in the same situation with my S6. Somewhere in the thread it said something about pit files but I don't really understand what to do. For reference, my issue is the exact same as OP's with the unmountable partitions and unbootable system. Would someone be kind enough to help out? My device is a SM-G920F from Vodafone (UK)
hi i flashed j3 2017 with odin.the final result was passed but the phone dont boot.it goes only to odin download mode. any solution
ntamvakeras said:
hi i flashed j3 2017 with odin.the final result was passed but the phone dont boot.it goes only to odin download mode. any solution
Click to expand...
Click to collapse
Well, I'm no expert on booting, but I would try this. First, pull the battery to shut off the phone. Second, reinstall the battery and Press and hold "Volume Up+Home+Power" buttons at the same time till your phone is on,then your Samsung will enter Recovery Mode. It takes a while to get to the recovery screen so be patient. You may see the dead android for a while, but after a few minutes you will get the recovery menu. From there you can try reboot system and see if it will boot for you.
Good Luck!
BigZ1 said:
Well, I'm no expert on booting, but I would try this. First, pull the battery to shut off the phone. Second, reinstall the battery and Press and hold "Volume Up+Home+Power" buttons at the same time till your phone is on,then your Samsung will enter Recovery Mode. It takes a while to get to the recovery screen so be patient. You may see the dead android for a while, but after a few minutes you will get the recovery menu. From there you can try reboot system and see if it will boot for you.
Good Luck!
Click to expand...
Click to collapse
Forgot to ask you a question. I have a J3 that I'm trying to unlock the boot loader. If you get yours working, would you mind checking your developer options to see if you have the button for OEM unlocking? I would appreciate it. Thanks
BigZ1 said:
Forgot to ask you a question. I have a J3 that I'm trying to unlock the boot loader. If you get yours working, would you mind checking your developer options to see if you have the button for OEM unlocking? I would appreciate it. Thanks
Click to expand...
Click to collapse
I did that but nothing is happening. Only volume down home end power combination works
{
"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"
}
Did you hold the keys down continuously? That is to say, until you either get recovery mode (or in your case bootloader mode)? If you let go of the key combo after seeing the Samsung J3 screen, you let go too soon. I've always had success with getting into recovery that way. Try it again.
If you truly can't start up in recovery mode, I think you may have wiped out your recovery partition. I'd suggest you use Odin to flash it again.
I just tried booting into recovery mode and then reboot to system. If you can get to that point, you are home free. If you can't get to recovery mode, I think your best bet is to try to reflash with Odin. Maybe you got a bad download. Consider getting a fresh download and reflashing with Odin.
One more thing you might be able to do. IF you had usb debugging enabled, you could connect the phone to your pc, and issue a fastboot command "fastboot reboot" which would reboot you into the system.
This reqires some level of technical skill and some setup work to get fastboot installed (on windows) or if you have a Linux computer, fastboot is probably already installed.
The above is only going to work if you had the developers option for usb debugging turned on before you flashed the phone, and even then it may or may not work, depending on how far the phone gets while booting.
I think at this point, your best option is downloading a fresh copy of your system image from Samsung, and reflashing it with Odin. Hoperfully it will still connect to Odin, since it's already in bootloader mode.
This phone was fully functional but had broken screen as you see. I left it and I ordered a new from aliexpress. After one month the new screen came. I took the phone for charging but it gave a signal that battery not charged. And the phone not opened. I placed a new battery for charging but still couldn't get to menu and I did a wipe data factory reset but nothing happened so I decided to flash it with odin but while the flash is OK the phone don't boot. When I try to charge it is gives a green screen
ntamvakeras said:
This phone was fully functional but had broken screen as you see. I left it and I ordered a new from aliexpress. After one month the new screen came. I took the phone for charging but it gave a signal that battery not charged. And the phone not opened. I placed a new battery for charging but still couldn't get to menu and I did a wipe data factory reset but nothing happened so I decided to flash it with odin but while the flash is OK the phone don't boot. When I try to charge it is gives a green scree
Click to expand...
Click to collapse
After you flashed it, and rebooted the phone, how long did you wait for the phone to boot into system? It takes a long time (like maybe 15 minutes) for it to get to the point where you do the initial configuration. If you can try flashing with Odin again, give it at least 15 minutes to get through it's initialization process. That might be what went wrong. Just a guess on my part, but that's what I think. Let me know if it works.
VID_20220727_202947.mp4
drive.google.com
ntamvakeras said:
VID_20220727_202947.mp4
drive.google.com
Click to expand...
Click to collapse
I did all this but nothing happens I don't see the Samsung logo only a green screen. I upload a video to see what I doing
I wish I could help you. I think you are doing everything right. This problem exceeds my knowledge. Maybe someone else smarter can help you.
OK thanks a lot for your assistance
ntamvakeras said:
OK thanks a lot for your assistance
Click to expand...
Click to collapse
I don't know if you are still trying to fix your phone. If so, you might try experimenting with the ODIN option for reboot after flash. Try turning it off, flash with ODIN, unplug cable, pull battery and re-insert, see if it will boot (be patient, it will be slow). If that doesnt work, pull and reinsert battery, then try to boot into recovery with keys.
Just an idea... might get lucky.
BigZ1 said:
I don't know if you are still trying to fix your phone. If so, you might try experimenting with the ODIN option for reboot after flash. Try turning it off, flash with ODIN, unplug cable, pull battery and re-insert, see if it will boot (be patient, it will be slow). If that doesnt work, pull and reinsert battery, then try to boot into recovery with keys.
Just an idea... might get lucky.
Click to expand...
Click to collapse
I did it but nothing happened. The matter is that the phone don't power on after flash. I don't know what else to do
Hello ntamvakeras, on the first video I tell you that in option you manipulate in pit. I have an old j3 2017 I managed to install official Firmware and then install TRWP, the J3 cable is the good one I didn't have the good is we change it worked.
When you use in option pit these why you do this, I flash I don't touch pit.
ntamvakeras said:
View attachment 5669359
Click to expand...
Click to collapse
Will never boot FRP lock and OEm are On i think a account is hanging to the phone , boot in recovery samsung mode and wipe data factory reset from there , reboot
meric57 said:
Hello ntamvakeras, on the first video I tell you that in option you manipulate in pit. I have an old j3 2017 I managed to install official Firmware and then install TRWP, the J3 cable is the good one I didn't have the good is we change it worked.
When you use in option pit these why you do this, I flash I don't touch pit.
Click to expand...
Click to collapse
HI I did that because I have done a lot of experiments in this phone. I know that is wrong but I did that as last way to recover the phone