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.
Related
Hey guys,
I managed to f*** up my phone and don't know exactly what went wrong. I'm worried it's a hard brick, but don't know for sure. It won't turn on though, which is freaking me out. I hope one of y'all can help.
So I was running CM10.1 for a long time and everything was great. I eventually installed an update through the built-in CM updater app, decided I didn't like it, and attempted to re-install through the .zip I still had on my sdcard. I'm still not sure why, but doing so put me in a boot-loop. I was pretty busy at the time so just flashed back to stock. Wasn't ideal, but worked fine.
So now I have some free time and decided I'd try to re-install CM. Prior to the install attempt, I was running 4.1.2 stock, rooted and with an unlocked bootloader. Here's what I did:
1: Flashed the VRALEC bootloader, as recommended by the CM wiki, through Odin.
-At this point, everything still worked OK. I think this next step is where I went wrong.
2: Flashed the VRALF2 kernel through Odin.
-This is what I think I did wrong. After I flashed it, instead of booting up the phone got past the Galaxy S3 graphic then the LED just slowly changed from blue to light blue and back. Either way, I still was able to do the following steps.
3: Flashed CWM 6.0.1.2 through Odin.
4: Installed CM10.2 and gapps from recovery.
5: Rebooted, stuck in a boot-loop showing the CM logo.
So hindsight being 20/20, this is where I should have stopped and asked for help. Instead, I decided that I'd try to fix it myself and tried to flash back to stock. When I tried to do so, Odin said it failed. I then reflashed the VRALEC bootloader, again through Odin. This was successful, but after it rebooted, it showed the Galaxy S3 graphic for a bit and then went blank. Since then, I can't get the phone to turn on or enter download or recovery modes.
Can anyone help? I'm really worried I hard-bricked my phone. What do I need to do / where can I go from here?
Update - Maybe not hard-bricked!
berichardson13 said:
Since then, I can't get the phone to turn on or enter download or recovery modes.
Click to expand...
Click to collapse
So I've managed to get the phone into recovery mode, which is the factory recovery (not CWM). And I can also get into download mode. But when I start up the phone, it stops at the "Samsung Galaxy S III" graphic and just stays there. From that screen, I can only get it to turn off by taking out the battery.
Hopefully this means I'm not hard-bricked. Does anyone know what I can do from here to get it functional again?
berichardson13 said:
So I've managed to get the phone into recovery mode, which is the factory recovery (not CWM). And I can also get into download mode. But when I start up the phone, it stops at the "Samsung Galaxy S III" graphic and just stays there. From that screen, I can only get it to turn off by taking out the battery.
Hopefully this means I'm not hard-bricked. Does anyone know what I can do from here to get it functional again?
Click to expand...
Click to collapse
If you can get into recovery/download, you are definitely not hardbricked. Try to do a factory reset in recovery. If that doesn't work try to ODIN a full stock image.
*your internal storage will be wiped with a factory reset (obviously).
I'm pretty sure they recommend flashing the newer CM's from the MF1 base. I might be making that up though.
Sounds like you forgot to flash something, check the thread you used again
Sent from my SCH-I535 using XDA Premium 4 mobile app
---------- Post added at 08:30 PM ---------- Previous post was at 08:28 PM ----------
If you have a blue led light after the Samsung galaxy s3 screen when it goes black then you don't have the proper drivers for your screen which would be in the file you didn't flash
Sent from my SCH-I535 using XDA Premium 4 mobile app
BattsNotIncld said:
If you can get into recovery/download, you are definitely not hardbricked. Try to do a factory reset in recovery. If that doesn't work try to ODIN a full stock image.
Click to expand...
Click to collapse
Tried the factory reset, ended up in the same spot. So, next I'll try flashing back to stock.
I've done this before, but after the scare earlier I'm being overly paranoid - am I going to need to flash a different kernel? Or is it gonna be enough to just flash something like the VRBMF1 image?
Flash back to stock 4.1.2, use Casual to root and unlock, and get a recovery.
http://forum.xda-developers.com/showthread.php?p=42791826
Sent from my Last Ever Samsung Device.
0331 said:
use Casual to root and unlock, and get a recovery.
Click to expand...
Click to collapse
So this is another dumb question. But having just downloaded the newest version of Java to my Windows 7 computer, I still can't get Casual to open. Instead, this command prompt dialogue box pops up for a little bit then disappears. Nothing else happens after that. I'm opening it with JRE 1.7 - should I be doing something differently?
Edit - I just opened it in terminal, got it going fine, but can't get Casual to recognize my phone. I'm about to update the drivers, see if that does the trick.
berichardson13 said:
So this is another dumb question. But having just downloaded the newest version of Java to my Windows 7 computer, I still can't get Casual to open. Instead, this command prompt dialogue box pops up for a little bit then disappears. Nothing else happens after that. I'm opening it with JRE 1.7 - should I be doing something differently?
Edit - I just opened it in terminal, got it going fine, but can't get Casual to recognize my phone. I'm about to update the drivers, see if that does the trick
Click to expand...
Click to collapse
If it still doesn't work, try the slightly older version of Casual: http://rootzwiki.com/topic/44201-★-casualroot-unlock-recovery-1-click-all-otas★/
Sent from my SCH-I535 using Tapatalk 4
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.
Help Help Help :
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got TWRP cant install.Because. OEM locked.
It flashed. Great. But now IT STILL DOESNT BOOT. I'm stuck at NO COMMAND, it keeps restarting after 20-30 seconds of showing no command. and it's looping all over.*
i flashed stock firmware.It is flashed.Then reboot.Then install system update.Then Erasing.Then rebooting.Then NO COMMAND.Then reboot itselve recovery mode.Then i wiped factoory and cache.Then press rwboot to system.Then Samsung Galaxy S8 Plus.Then install system update.Erasing.No Command. etc. Keeps rebooting. its on NO command screen. It just restarts. Doesnt boot. I want to enable OEM Unlock. I installed combination binary. But not appear in Developer Mode.
i flash atock with Kies emergency.I flash different stock firmware from updato.com. But nothing happend.
I'm a little confused.
What state is your phone currently in, i.e. can you get into download mode, turn off... what?
JeffDC said:
I'm a little confused.
What state is your phone currently in, i.e. can you get into download mode, turn off... what?
Click to expand...
Click to collapse
KIES says that. (THR) Stock. i downloaded it and flashed with Odin. Then reboot. Then system install update. Then Erasing. Then reboot and No Command! 30 seconds keeps rebooting itself 30 seconds interval Random.
I did factory format, cache clear. then the same problem. i want to install twrp recovery with oden. It says Oem Lock. Not allowed. But i flashed Combinary file. I can get into system and i to developer mode but dosnt seem OEM UNLOCK that ll do enable it.
Ok mate, but if you press Vol- + Bixby + power for couple of seconds, can you access to download mode? If you can, I think you'll have to install the firmware all over again.
Try flashing using latest firmware from sammobile. Use Odin to flash all the files contained in firmware download. Make sure you get latest firmware for your carrier. Google how to flash using Odin. Hope this gets you in the right direction. Good luck finding what u need, do copious amounts of research before attempting any rooting of devices and if all steps aren't clear as day to you then do not attempt it unless you don't mind buying multiple expensive phones to tinker with.
Did OP find a fix to this problem?
I am experiencing a similar issue. Picked my phone up to find had randomly gone into a boot loop. Tried soft reset, cache wipe, factory reset - all successful but the phone would still reboot and be stuck on device model screen. Next I decided to flash the device with stock firmware. The flash passed in Odin, the phone then rebooted, loaded to device model screen, then a screen appeared saying "installing updates" which would make it to 25% then crash. After this the phone keeps booting, shows a screen with a dead android icon and says "no command" or "error". I have tried to flash the device using Oreo and Nougat firmware but have failed every time (although the flash did pass in Odin)
Any help would be greatly appreciated as I would rather not buy a new phone due to a random hardware fault which is out of my control.
southsideswaggar said:
Try flashing using latest firmware from sammobile. Use Odin to flash all the files contained in firmware download. Make sure you get latest firmware for your carrier. Google how to flash using Odin. Hope this gets you in the right direction. Good luck finding what u need, do copious amounts of research before attempting any rooting of devices and if all steps aren't clear as day to you then do not attempt it unless you don't mind buying multiple expensive phones to tinker with.
Click to expand...
Click to collapse
This is perfect if you have soft bricked your phone!
follow this video maybe it help you
https://forum.xda-developers.com/ga...g-aqg5-fix-t3636857/post73032395#post73032395
https://www.youtube.com/watch?v=VTi3uBkpJic&t=155s
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)
Hello guys
First of all, thanks to everyone who shares their knowledge and experiences here on XDA. I've been learning stuff here for years, and every time I made a mistake, I could find a solution, but I'm afraid this time the noob here has made too many mistakes.
My S7 G930F DBT stock is in a boot loop, with the "no command" screen, and the only thing I'm able to do is access download*mode. I would like your help to figure out if there's still something I can do on my own.
So, what happened was that I followed this tutorial about a year ago and converted*my S7 to dual sim. I encountered some issues, one of them being that I wasn't able to keep TWRP installed (the system removed it after the first boot), but in the end I was able to make the phone work again, dual sim. This week, I was having some issues with short battery life and wanted to boot into recovery to wipe cache. I tried that and the boot loop started, and when I tried to access recovery it said that there*was no recovery (I can't recall the exact*message). Since then I tried some things*and realized later I made things worse:
- I tried to flash the stock rom via Odin, but did so with the latest firmware (S8), not with the one on the phone (S4).
- Tried to flash all except the BL file on Odin- I tried to flash TWRP, but it failed because of FRP lock.
- I tried to flash a combination rom, but since I had flashed S8, I couldn't*because the latest combination available is U5
- I'm not sure if it's relevant or not, but when following the dual sim conversion tutorial last year and editing the cert file, the serial number was 00000. I kept it that way because I didn't realize it's written on the back of the phone (duh).
Nothing worked, the phone is still in boot loop, I can't access recovery (not even the "no recovery*message" shows up anymore) and I can only put it in download mode. I thought about maybe removing FRP Lock with the z3x 29.5 I used for the dual sim tutorial, flash TWRP and follow all the steps again, to put the serial number in the cert file, but I'm not sure it would be possible, since I flashed a newer firmware.
So, what do you think? Have I messed up beyond repair this time?
Thanks in advance
drlemmy said:
Hello guys
First of all, thanks to everyone who shares their knowledge and experiences here on XDA. I've been learning stuff here for years, and every time I made a mistake, I could find a solution, but I'm afraid this time the noob here has made too many mistakes.
My S7 G930F DBT stock is in a boot loop, with the "no command" screen, and the only thing I'm able to do is access download*mode. I would like your help to figure out if there's still something I can do on my own.
So, what happened was that I followed this tutorial about a year ago and converted*my S7 to dual sim. I encountered some issues, one of them being that I wasn't able to keep TWRP installed (the system removed it after the first boot), but in the end I was able to make the phone work again, dual sim. This week, I was having some issues with short battery life and wanted to boot into recovery to wipe cache. I tried that and the boot loop started, and when I tried to access recovery it said that there*was no recovery (I can't recall the exact*message). Since then I tried some things*and realized later I made things worse:
- I tried to flash the stock rom via Odin, but did so with the latest firmware (S8), not with the one on the phone (S4).
- Tried to flash all except the BL file on Odin- I tried to flash TWRP, but it failed because of FRP lock.
- I tried to flash a combination rom, but since I had flashed S8, I couldn't*because the latest combination available is U5
- I'm not sure if it's relevant or not, but when following the dual sim conversion tutorial last year and editing the cert file, the serial number was 00000. I kept it that way because I didn't realize it's written on the back of the phone (duh).
Nothing worked, the phone is still in boot loop, I can't access recovery (not even the "no recovery*message" shows up anymore) and I can only put it in download mode. I thought about maybe removing FRP Lock with the z3x 29.5 I used for the dual sim tutorial, flash TWRP and follow all the steps again, to put the serial number in the cert file, but I'm not sure it would be possible, since I flashed a newer firmware.
So, what do you think? Have I messed up beyond repair this time?
Thanks in advance
Click to expand...
Click to collapse
Hello, so if you've flashed a newer bootloader than the one in the tutorial then yes it's game over for dual SIM as there isn't a newer version of that bootloader and there isn't going to be. The S7 is getting on abit now.
The best you can now hope for is to install the latest German firmware and have your phone working as a single SIM again.
To exit no command press volume up + power.
When you install TWRP stock recovery is removed. When you uninstall TWRP stock recovery is still missing until you flash stock firmware, that's why you have No command.
cooltt said:
Hello, so if you've flashed a newer bootloader than the one in the tutorial then yes it's game over for dual SIM as there isn't a newer version of that bootloader and there isn't going to be. The S7 is getting on abit now.
The best you can now hope for is to install the latest German firmware and have your phone working as a single SIM again.
To exit no command press volume up + power.
When you install TWRP stock recovery is removed. When you uninstall TWRP stock recovery is still missing until you flash stock firmware, that's why you have No command.
Click to expand...
Click to collapse
Thanks for replying!
I have no problem loosing dual sim, as long as I can get it back up. When I press volume up + power, nothing happens, it only turns off completely. I flashed the the latest firmware again (G930FXXS8ETC6 - CSC file, not HOME_CSC). But the result was the same, "no command" screen and no access to recovery, I tried volume up + power and volume up + home button + power, at the same time and alternating.
I was able to get to were the recovery was supposed to be and this is the error it's showing:
{
"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 flashed the phone in Odin once again, this time with "nand erase" and "repartition" checked, and the pit file in the third tab. But it didn't work, afterwards the "no command" screen poped up and the same error showed up when trying to access recovery. Tried to flash TWRP again and got the FRP lock message. Nothing changed, basically.
I thought about finding a way to bypass FRP and install TWRP, but there's some shady stuff online on how to do it. The Z3x tool used in the dual sim tutorial has an option for that, but it shows "card error" when I try it and nothing happens.
So, I'm kinda lost here, any suggestion on the next steps would be much appreciated.
I tried to find a way to bypass FRP, tried many tools, like Z3X and Miracle, but it didn't work. The best I could get out of two of these softwares was a "Custom Binary(Userdata) Blocked by FRP Lock" line in download mode when the procedure was finished, not even a reboot. When I manually reboot the phone after getting this message, it shows something different, "An error has occurred while updating" blue screen saying to use SmartSwitch, but that obviously doesn't work either.
drlemmy said:
I tried to find a way to bypass FRP, tried many tools, like Z3X and Miracle, but it didn't work. The best I could get out of two of these softwares was a "Custom Binary(Userdata) Blocked by FRP Lock" line in download mode when the procedure was finished, not even a reboot. When I manually reboot the phone after getting this message, it shows something different, "An error has occurred while updating" blue screen saying to use SmartSwitch, but that obviously doesn't work either.
Click to expand...
Click to collapse
It's unlikely you'll be able to bypass FRP lock with any tool as most don't work anymore.
You just need to flash the latest firmware for your region with Odin. Boot into download mode to do this, can you still access download mode?
After a successful flash the FRP lock will still ask for the Google account and password used with the phone. Follow the steps and your phone should start normally.
It does not matter what modifications you have done prior, the default recovery is always flash latest firmware with Odin.
In future REMOVE Google account from phone BEFORE modification.
cooltt said:
It's unlikely you'll be able to bypass FRP lock with any tool as most don't work anymore.
You just need to flash the latest firmware for your region with Odin. Boot into download mode to do this, can you still access download mode?
After a successful flash the FRP lock will still ask for the Google account and password used with the phone. Follow the steps and your phone should start normally.
It does not matter what modifications you have done prior, the default recovery is always flash latest firmware with Odin.
In future REMOVE Google account from phone BEFORE modification.
Click to expand...
Click to collapse
It wasn't intentional, the phone was working fine and I was logged in my Google account, but the battery life was getting shorter. I just wanted to wipe cache to try and fix that. When I tried to boot to recovery, the boot loop started.
I think that happened because of the dual sim modification last year, I must have done something wrong and the phone lost the recovery mode or something. But the first thing I did was flashing the latest stock firmware, and after that I couldn't get into the system anymore. I probably should have flashed the same binary I had installed, at least it would give me the combination file option.
Download mode is the only thing working. The FRP lock bypass route was the best I could come up with, since it would allow to install TWRP, access to ADB, etc
drlemmy said:
It wasn't intentional, the phone was working fine and I was logged in my Google account, but the battery life was getting shorter. I just wanted to wipe cache to try and fix that. When I tried to boot to recovery, the boot loop started.
I think that happened because of the dual sim modification last year, I must have done something wrong and the phone lost the recovery mode or something. But the first thing I did was flashing the latest stock firmware, and after that I couldn't get into the system anymore. I probably should have flashed the same binary I had installed, at least it would give me the combination file option.
Download mode is the only thing working. The FRP lock bypass route was the best I could come up with, since it would allow to install TWRP, access to ADB, etc
Click to expand...
Click to collapse
I understand all that you've said the only solution is to install correct firmware with Odin via download mode then sign into Google account.