I managed to be get rooted by following this.
For some reason, I am have been completely unable to do anything via Odin, but the above method ended up working for some reason (I had to execute the .jar from my C:\ drive though).
In a moment of idiocy, I chose the "Advanced Wipe" option under "Wipe" from the homescreen menu in TWRP and wiped my System directory. I think that this effectively wiped my OS, so I have nothing to boot into (it gets stuck at the "Samsung Galaxy S4" logo).
I have and can still access TWRP recovery, I can send ADB commands--but I do not believe that TWRP allows me to 'push' anything and I have not had any success with 'sideloading'. Some ADB commands leave me hanging at "< waiting for device >". I attempted to install custom ROMs by putting the install .zips onto my external SD and having TWRP install them, but I keep getting failures. I can access download mode, but Odin (v. 1.85, 3.04, 3.07) doesn't want to cooperate with me and all it says is a write failure. No PIT errors, I unchecked everything except " Auto Reboot", PDA mode, I tried all combinations of installing and re-installing Kies with drivers and rebooting my PC, plugging and unplugging my device into front and rear USB ports with different OEM cables, killing Kies/ADB processes via task manager and starting Odin at various points in the process (before and after I plug in my device or press up on the volume rocker to enter download mode). Please let me know if there's any more Odin hocus-pocus I haven't tried.
I was hoping that Kies->Tools->Firmware Upgrade and Initialization would work, but when I entered my S/N it said that initialization was not available for my device.
I'm at my wit's end, at this point; I would welcome someone telling me that I haven't completely bricked my device beyond all repair. I want to blame TWRP for not being able to install a ROM from a .zip. I have attached a recovery log from TWRP.
It seems you have problem in partition table. Did you flash pit file with the firmware in odin?
Sent from my Galaxy using xda premium
I had the same problem when I once had my S3 and I assume it'll be the same. In TWRP mount your storage and move a random rom on to your phone.
samersh72 said:
It seems you have problem in partition table. Did you flash pit file with the firmware in odin?
Sent from my Galaxy using xda premium
Click to expand...
Click to collapse
I think you are right about the partition problem, because that is what TWRP is telling me. I didn't flash a pit file in Odin with firmware. Am I supposed to?
Shivammcool said:
I had the same problem when I once had my S3 and I assume it'll be the same. In TWRP mount your storage and move a random rom on to your phone.
Click to expand...
Click to collapse
I was hoping that this would be the solution, but TWRP gives me a partition error. I will definitely re-attempt this once I can resolve that issue.
ncovey said:
I think you are right about the partition problem, because that is what TWRP is telling me. I didn't flash a pit file in Odin with firmware. Am I supposed to?
Click to expand...
Click to collapse
ya, flash the appropriate pit file WITH the firmware, check F.reset, auto reboot, and re-partition (they will be ticked by default).
see my sig for pit file if you dont have it
---------- Post added at 09:34 PM ---------- Previous post was at 09:03 PM ----------
wait.... you have the I9505 or the I545 (verizon)???
if I545 then here is the pit http://forum.xda-developers.com/showthread.php?t=2290859
Edit: i check pit files.... they are the same :good:
samersh72 said:
ya, flash the appropriate pit file WITH the firmware, check F.reset, auto reboot, and re-partition (they will be ticked by default).
see my sig for pit file if you dont have it
---------- Post added at 09:34 PM ---------- Previous post was at 09:03 PM ----------
wait.... you have the I9505 or the I545 (verizon)???
if I545 then here is the pit http://forum.xda-developers.com/showthread.php?t=2290859
Edit: i check pit files.... they are the same :good:
Click to expand...
Click to collapse
I am downloading one of the official firmwares. Is it possible to install it through my SD card if I can't get ODIN to flash it?
I tried installing the pit file, but I get the "SECURE CHECK FAIL : PIT" error on my S4's display.
I am worried that even though I managed to get rooted through Loki's exploit (I think that's what CASUAL or motochopper uses) the exploit that was pushed to my phone was wiped from it. I have the AT&T GT-I9505, so it definitely has a locked bootloader. I'm not giving up yet though.
Now it's definitely bricked.
Well, I couldn't do any of the methods described above because no manner of Odin'ing got me anywhere except "SECURE CHECK FAIL : " for recovery, boot, kernel, pit, etc.
so i attempted to do adb commands to see the extent of what i could do:
Code:
dd if=i9505-cwm-recovery-6.0.3.2-4.tar of=/dev/block/mmcblk0p21
from here
I should have known that you cannot install a .tar instead of a .img... :crying:
So now there is no recovery. And it only boots into download mode with a message at the top that says: "Could not do normal boot."
Unfortunately under "CURRENT BINARY:" it says "Custom" so I'm fairly certain that AT&T will not do a warranty replacement.
Hooray for popping my brick cherry!
EDIT: since the only way I was able to ADB before was in recovery mode... now that I've fubar'd my recovery... no ADB
EDIT 2: I've only had this phone for ~55 hours, so I think I can still have it exchanged for a restocking fee from AT&T. According to this and this
EDIT 3: I went to the AT&T store, and I was naive to think that they wouldn't turn it on. When the salesperson saw the "unauthorized software" message, she asked if I had attempted to "jail-break" my phone lol. She wanted to factory reset it from recovery mode, but obviously that didn't work. She said, "I am not sure we can accept this, and my inventory manager would kill me if we got back a device like this." She ended asking me to come in tomorrow to talk to the manager. I am very, very certain this will NOT result in me getting a new device.
Also, I realize that in this post whenever I've said "brick" I was not using the term correctly, as I can still turn it on. My mistake.
can you tell me the exact product number (i337 or i9505....) and what is the firmware that you are trying to install?
Related
I have TWRP'd my MK2 build SGH-i337. Which now as i am reading kills recovery on the locked bootloader.
I have seen a bunch of threads getting people odin'd back to MF3 using the MF3.tar file, but i have tried this and it fails every time. I am guessing from what i am reading that i cant go back to MF3. Is there a mk2 stock tar file i can odin? I cant ADB or flash via recovery, at this point Odin seems to be my only option for interaction with the phone.
I have also seen people taking these phones up to Best Buy to use SMART tool from Samsung. Is this my only hope? This is my work phone and kinda feeling a little regretful at the moment, so can anyone can confirm my options at this point?
I know this is similar to previous posts about mf3 twrp'd phones but i didn't see anything about mk2, so sorry in advanced if this is to similar and i am missing something.
Follow These Instructions
Follow these instructions.
skip the MJ9 sideload update part and replace with the at&t full mk2 update file. Search the forums for it. :good:
http://forum.xda-developers.com/showpost.php?p=47604388&postcount=152
---------- Post added at 03:54 PM ---------- Previous post was at 03:36 PM ----------
joshzdad2013 said:
Follow these instructions.
skip the MJ9 sideload update part and replace with the at&t full mk2 update file. Search the forums for it. :good:
http://forum.xda-developers.com/showpost.php?p=47604388&postcount=152
Click to expand...
Click to collapse
Here is more info on the MK2 update file.
http://forum.xda-developers.com/showpost.php?p=47998793&postcount=819
I was able to get to recovery
I am at recovery now but still do not see a full mk2 update. There is the update file for 4.3 i tried to side load that but received E:Error in //tmp/update.zip (status 7).
Is this the mk2 file you are referring to it is about 700 meg? I couldn't find anyone with a full stock mk2. Any suggestions from here?
Yes its the 700 meg one. Side load that. It worked for me. Put it on your sd card then in stock recovery sise load from external sd.
Clarification
Are you wanting me to do this with these fix files?
Download and extract the following files...
mf3-emergency-part-1.tar.md5.7z
mf3-emergency-part-2.tar.md5.7z
And then these steps with the mk2 instead of mj9 update file instead?
Start Odin, connect your phone and boot into Download mode.
Flash mf3-emergency-part-1.tar.md5 which contains modem.bin, NON-HLOS.bin and system.img.ext4.
The flash of system.img.ext4 WILL FAIL at the end. That's OK.
Reboot the phone back into Download mode and restart Odin.
Flash mf3-emergency-part-2.tar.md5 which contains cache.img.ext4.
The flash WILL FAIL at the end. That's OK.
The phone should now reboot to recovery by itself and apply a small update. If it fails, stop and report.
The phone should now reboot to a black screen with the pulsing notification LED.
Reboot into recovery mode and flash mk2update.zip. I recommend sideloading instead of flashing from sdcard because the sdcard method reboots the phone whether the update was successful or not and you lose the error messages.
Reboot the phone and let it initialize.
You should now have MK2.
Yes
---------- Post added at 07:10 PM ---------- Previous post was at 07:00 PM ----------
Just make sure your flashing that 700mb file its the full mk2 update.
I'm stuck in the same boat after TWRP....will only boot to odin. No recovery, if I try it ony goes to a screen where it says to hook it up to Kies and update firmware that way(doesn't work though because Kies tries to download MDL). Will not be able to attempt this method til I get home from work so I'm staying glued to this post in the meantime. Appreciate the updates!
What version of Odin are you using? I have the same problem and cant get past emergency part 2. Phone does not auto reboot after cache flash.
sl1200md3 said:
What version of Odin are you using? I have the same problem and cant get past emergency part 2. Phone does not auto reboot after cache flash.
Click to expand...
Click to collapse
I used Odin 1.85
joshzdad2013 said:
I used Odin 1.85
Click to expand...
Click to collapse
Same here. Thanks. Phone is still stuck after flashing mf3-emergency-part-2.tar. I try and manually reboot and it takes me back into Odin mode.
After flashing mf3-emergency-part-2.tar, phone hangs and says:
Odin Mode
Product Name: SGH-I337
Current Binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x0
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
eMMC Burst Mode: enabled
Start [224,1440]
Bar [240,1440]
Secure Check Fail: cache
Just keep trying again, re-read the main post above. I literally sid it 3 times and it finally worked. I just kept reading thru the post till I found good info. Its in there ya just gotta find it.
Great Success Back at Stock!
I have gotten back to the stock from directions from gtj0, but big thanks to joshzdad2013 for leading me in the right directions :laugh::good:
Using Odin 3.07, I followed the directions except using the mk2 file 2400258.zip in the final adb sideload.
MK2 file
http://forum.xda-developers.com/show...&postcount=819
Also i forced reboot after step 6 by resetting odin and unplugging phone and plugging back in, then i just odin'd this file from this link
http://forum.xda-developers.com/showthread.php?t=1766399 Not sure if this helped any, but after forcing the reboot with the blank tar file it came back up in recovery and forced a small update. I then just used adb.exe to side load the 2400258.zip file after putting phone in adb sideload mode.
:good::good::good:
kevinpc said:
I have gotten back to the stock from directions from gtj0, but big thanks to joshzdad2013 for leading me in the right directions :laugh::good:
Using Odin 3.07, I followed the directions except using the mk2 file 2400258.zip in the final adb sideload.
MK2 file
http://forum.xda-developers.com/show...&postcount=819
Also i forced reboot after step 6 by resetting odin and unplugging phone and plugging back in, then i just odin'd this file from this link
http://forum.xda-developers.com/showthread.php?t=1766399 Not sure if this helped any, but after forcing the reboot with the blank tar file it came back up in recovery and forced a small update. I then just used adb.exe to side load the 2400258.zip file after putting phone in adb sideload mode.
:good::good::good:
Click to expand...
Click to collapse
That's awesome. . I managed to get the force reboot trick to work at Step 6. Now I'm at the blank screen flashing LED phase (Step 8). Better progress than where I was before, but I still cannot boot into recovery. I'll keep trying.
sl1200md3 said:
That's awesome. . I managed to get the force reboot trick to work at Step 6. Now I'm at the blank screen flashing LED phase (Step 8). Better progress than where I was before, but I still cannot boot into recovery. I'll keep trying.
Click to expand...
Click to collapse
Try flashing the recovery again after doing the emergency TAR's. I had to do that in order to fix mine, and then it restored nicely.
DeadlySin9 said:
Try flashing the recovery again after doing the emergency TAR's. I had to do that in order to fix mine, and then it restored nicely.
Click to expand...
Click to collapse
Thanks! :good: That got me back into Recovery mode. Now I'm getting Signature Verification Failed / Installation Aborted when I try and adb sideload this file http://forum.xda-developers.com/showpost.php?p=47998793&postcount=819 (2400258.zip) Looks like a bad download. Tried it twice.
I'm gonna try this file I found here http://forum.xda-developers.com/showthread.php?t=2573080 and see if that will work. DL is taking forever...
Nope. Both links didn't work. I'm also getting a CRC check error on both files if I try and unzip. Unexpected end of archive. Anyone know where I can get a good MK2 update file??
Got home and started with the instructions....flashed the first recovery-mj6.tar.md5 and the phone booted back up normally! I imagine that if I try to boot to recovery it'll soft brick again. Gonna leave it like this for now til the wife gets home and then see what happens.
SUCCESS!
Back on AT&T STOCK MK2 from a bricked TWRP'd install. I had to do the following:
1) Phone into download mode
2) Flash mf3-emergency-part-1.tar.md5 via Odin v1.85
3) Force Reboot
4) Flash mf3-emergency-part-2.tar.md5
5) Unplug phone / Reset Odin / plug phone back in
6) Flash recovery-mj6.tar.md5
7) Force Reboot in Odin using this file http://forum.xda-developers.com/showthread.php?t=1766399 Thanks kevinpc :good:
8) Manually enter recovery
9) ADB Sideload the file: update-mf3-mj9.zip found here: http://forum.xda-developers.com/showpost.php?p=47604388&postcount=152
10) ADB Sideload the file: update-MJ9-MK2.zip found here: https://docs.google.com/file/d/0B2iXrnZBB-MVYkYwNkYzU2FJaFk/edit
11) Reboot
Won't be flashing TWRP via Goo Manager again any time soon.
:good::good::good:
sl1200md3 said:
Back on AT&T STOCK MK2 from a bricked TWRP'd install. I had to do the following:
1) Phone into download mode
2) Flash mf3-emergency-part-1.tar.md5 via Odin v1.85
3) Force Reboot
4) Flash mf3-emergency-part-2.tar.md5
5) Unplug phone / Reset Odin / plug phone back in
6) Flash recovery-mj6.tar.md5
7) Force Reboot in Odin using this file http://forum.xda-developers.com/showthread.php?t=1766399 Thanks kevinpc :good:
8) Manually enter recovery
9) ADB Sideload the file: update-mf3-mj9.zip found here: http://forum.xda-developers.com/showpost.php?p=47604388&postcount=152
10) ADB Sideload the file: update-MJ9-MK2.zip found here: https://docs.google.com/file/d/0B2iXrnZBB-MVYkYwNkYzU2FJaFk/edit
11) Reboot
Won't be flashing TWRP via Goo Manager again any time soon.
:good::good::good:
Click to expand...
Click to collapse
Went ahead and completed using this method. PERFECT! Can't thank all of you enough!:good::good:
You guys are all lifesavers. This is gonna teach me to be more careful when flashing roms.
I own a Samsung Galaxy A9
I tried to update the firmware from the original lollypop to (maybe) marshmallow
I failed to update using the software, so i updated using smart switch
It went wrong, the update failed.
Now the blue screen with "An error has occured while updating the device software. Use the emergency recvery function in the Smart Switch PC software" appears..
I tried the emergency recovery but it also failed
The only button combination that worked is the power button + volume down --> It restarted, but the same screen appears
I even tried refresing the software with Odin, but it failed.
The phone says "FRP is enabled, not allow download non-FRP aboot binary"
Odin doesn't work
The samsung customer service in singapore (my country) is not able to help. Would really appreciate it if somebody could help me with this.
-Michael
Are you able to get into bootloader ? If so, you can try using ADB to remove OEM Unlock.. There should be bootloader unlock instructions for Samsung in these forums..
Sent from my SM-A9000 using XDA-Developers mobile app
I take it you tried to update via odin originally.
If you give more details if what part of the flashing process failed we may be able to help.
Was it a particular partition that failed to flash.
A screenshot of the failed flashing process with odin would be helpful.
Also you may be able to remove the blue error screen by flashing the stock recovery with odin.
Extract it from the stock firmware, convert it to a tar archive then flash it with Odin.
Boot to recovery and wipe cache.
That itself may get you booting.
There is also Twrp available for your device which could do the same thing.
I had the same issue.. i fixed it yesterday.. what i did was.. go to developer options.. enable OEM unlock.. download CROM from galaxy apps store.. it gives a warning msg regarding unlocking the device.. that isnt an issue..just press ok.. and it will say ur device is unlocked.. and then try reflashing firmware from ODIN.. and then i did root my A9 and its working pretty nice since yesterday..
Sent from my SM-A9000 using XDA-Developers mobile app
---------- Post added at 09:53 PM ---------- Previous post was at 09:51 PM ----------
and also.. if u try to update to marshmallow.. u may get errors.. i assume thats because that is an update from CHINA..NOT from HONGKONG.. i suggest everyone to wait untill hongkong version of Marshmallow is released.. even i flashed marshmallow..had some error and my device was not booting and just booting into recovery with some error like drm something like that.. and then i flashed a hongkong lollipop 5.1.1 version and then my device booted..
Sent from my SM-A9000 using XDA-Developers mobile app
---------- Post added at 09:56 PM ---------- Previous post was at 09:53 PM ----------
regarding the FRP locking system. do one thing.. first back up everything.. go to backup and reset option.. do a factory reset.. it will wipe everything so do make sure u backup everything.. it will reboot the device into recovery.. do full factory reset.. reboot again.. finish.. i did this.. FRP LOCK is gone.. am happy
Sent from my SM-A9000 using XDA-Developers mobile app
---------- Post added at 09:57 PM ---------- Previous post was at 09:56 PM ----------
do all the steps as i said.. Insha Allah all your problems and errors will be solved..
Sent from my SM-A9000 using XDA-Developers mobile app
Mikekaipas said:
I own a Samsung Galaxy A9
I tried to update the firmware from the original lollypop to (maybe) marshmallow
I failed to update using the software, so i updated using smart switch
It went wrong, the update failed.
Now the blue screen with "An error has occured while updating the device software. Use the emergency recvery function in the Smart Switch PC software" appears..
I tried the emergency recovery but it also failed
The only button combination that worked is the power button + volume down --> It restarted, but the same screen appears
I even tried refresing the software with Odin, but it failed.
The phone says "FRP is enabled, not allow download non-FRP aboot binary"
Odin doesn't work
The samsung customer service in singapore (my country) is not able to help. Would really appreciate it if somebody could help me with this.
-Michael
Click to expand...
Click to collapse
Pls help me, i bought samsung galaxy A9 SM-A9000 Hong Kong version in singapore. My phone got firmware update error, i try to flash all A9 firmware with odin but still got problem and showing volume size is too big 7372800 < 7979008 , odin: invalid ext4 image. I try to flash with china firmware also. But frp not allowed. Pls help me what should i do. my phone can do downloading mode only. i can't do recovery mode and i don't have back up. Any idea to help me, pls.
mriyaan said:
I had the same issue.. i fixed it yesterday.. what i did was.. go to developer options.. enable OEM unlock.. download CROM from galaxy apps store.. it gives a warning msg regarding unlocking the device.. that isnt an issue..just press ok.. and it will say ur device is unlocked.. and then try reflashing firmware from ODIN.. and then i did root my A9 and its working pretty nice since yesterday..
Sent from my SM-A9000 using XDA-Developers mobile app
---------- Post added at 09:53 PM ---------- Previous post was at 09:51 PM ----------
and also.. if u try to update to marshmallow.. u may get errors.. i assume thats because that is an update from CHINA..NOT from HONGKONG.. i suggest everyone to wait untill hongkong version of Marshmallow is released.. even i flashed marshmallow..had some error and my device was not booting and just booting into recovery with some error like drm something like that.. and then i flashed a hongkong lollipop 5.1.1 version and then my device booted..
Sent from my SM-A9000 using XDA-Developers mobile app
---------- Post added at 09:56 PM ---------- Previous post was at 09:53 PM ----------
regarding the FRP locking system. do one thing.. first back up everything.. go to backup and reset option.. do a factory reset.. it will wipe everything so do make sure u backup everything.. it will reboot the device into recovery.. do full factory reset.. reboot again.. finish.. i did this.. FRP LOCK is gone.. am happy
Sent from my SM-A9000 using XDA-Developers mobile app
---------- Post added at 09:57 PM ---------- Previous post was at 09:56 PM ----------
do all the steps as i said.. Insha Allah all your problems and errors will be solved..
Sent from my SM-A9000 using XDA-Developers mobile app
Click to expand...
Click to collapse
I have the exact same problem as michael's... The problem is that we cannot enter the ROM at all... It only stuck at either the blue screen, or the odin mode screen. So we cannot disable neither FRP or Oem unlock...
Well in my chase i think the Crom service is already unlocked, but still... When trying to flash with :
China marshmallow : odin process failed even from the beginning (aboot.mbn <-- bootloader)
Hongkong lolipop : odin process failed during system ext4, saying it's too large
---------- Post added at 05:31 AM ---------- Previous post was at 05:30 AM ----------
ashyx said:
I take it you tried to update via odin originally.
If you give more details if what part of the flashing process failed we may be able to help.
Was it a particular partition that failed to flash.
A screenshot of the failed flashing process with odin would be helpful.
Also you may be able to remove the blue error screen by flashing the stock recovery with odin.
Extract it from the stock firmware, convert it to a tar archive then flash it with Odin.
Boot to recovery and wipe cache.
That itself may get you booting.
There is also Twrp available for your device which could do the same thing.
Click to expand...
Click to collapse
When trying to flash with :
China marshmallow : odin process failed even from the beginning (aboot.mbn <-- bootloader)
Hongkong lolipop : odin process failed during system ext4, saying it's too large
Is the TWRP for A9 available? I cant find any.
and remember this.. DO NOT FLASH CHINA MARSHMALLOW AS OF NOW.. it creates a problem.. FLASH ONLY HONGKONG FIRMWARE using the latest odin..
---------- Post added at 10:42 AM ---------- Previous post was at 10:41 AM ----------
y do u need twrp? just flash via odin and its done..
Sent from my SM-A9000 using XDA-Developers mobile app
If odin won't flash and the bootloader is complaining about frp lock.
Then the firmware isn't meant for that device.
If it fails at aboot then it's likely nothing got flashed.
To remove the firmware error warning it's usually enough to flash the stock recovery or twrp with odin.
The stock recovery image can be pulled from the stock firmware and converted to tar with 7-zip then flashed with odin.
Note: twrp wont flash while frp lock is active.
ashyx said:
If odin won't flash and the bootloader is complaining about frp lock.
Then the firmware isn't meant for that device.
If it fails at aboot then it's likely nothing got flashed.
To remove the firmware error warning it's usually enough to flash the stock recovery or twrp with odin.
The stock recovery image can be pulled from the stock firmware and converted to tar with 7-zip then flashed with odin.
Note: twrp wont flash while frp lock is active.
Click to expand...
Click to collapse
"The stock recovery image can be pulled from the stock firmware and converted to tar with 7-zip then flashed with odin."
Which file do you mean by stock recovery image, and how to flash it with odin. I mean like which file should be converted to tar and should i put it into AP slot and then start odin like usual? thanks
jmarcus.w said:
"The stock recovery image can be pulled from the stock firmware and converted to tar with 7-zip then flashed with odin."
Which file do you mean by stock recovery image, and how to flash it with odin. I mean like which file should be converted to tar and should i put it into AP slot and then start odin like usual? thanks
Click to expand...
Click to collapse
Open the md5 firmware archive with 7zip and pull out recovery.img.
Use 7-zip to create a tar archive then flash with odin in AP slot.
ashyx said:
Open the md5 firmware archive with 7zip and pull out recovery.img.
Use 7-zip to create a tar archive then flash with odin in AP slot.
Click to expand...
Click to collapse
First of all thanks for this..
I tried this and able to access the recovery screen..
But still flashing the stock ROM after wipe/factory reset fail.
I found several problems in the recovery screen:
There is "dm-verity verification failed" error
and there is problem about mounting to /system and formating /sbfs thing..
When I tried flashing.. the problem is also always on the same point.. On the system.img.ext4 it failed, saying volume is too large, ODIN : invalid ext4... <-- Always this failure
I dont understand any of this.
jmarcus.w said:
First of all thanks for this..
I tried this and able to access the recovery screen..
But still flashing the stock ROM after wipe/factory reset fail.
I found several problems in the recovery screen:
There is "dm-verity verification failed" error
and there is problem about mounting to /system and formating /sbfs thing..
When I tried flashing.. the problem is also always on the same point.. On the system.img.ext4 it failed, saying volume is too large, ODIN : invalid ext4... <-- Always this failure
I dont understand any of this.
Click to expand...
Click to collapse
As previously stated the firmware is not intended for your device this is why you are seeing these issues.
Hi,
I have removed the blue screen, i tried flashing the stockrom after wipe/factory reset failed. I found several problems in the recovery screen. There is "dm-verity verification failed" error and error during wiping, there is a problem about mounting to / system and formatting/ sbfsthing. i don't understand any of this jargon.
Hope i can get some help for this, please.
Thanks
Mikekaipas said:
I own a Samsung Galaxy A9
I tried to update the firmware from the original lollypop to (maybe) marshmallow
I failed to update using the software, so i updated using smart switch
It went wrong, the update failed.
Now the blue screen with "An error has occured while updating the device software. Use the emergency recvery function in the Smart Switch PC software" appears..
I tried the emergency recovery but it also failed
The only button combination that worked is the power button + volume down --> It restarted, but the same screen appears
I even tried refresing the software with Odin, but it failed.
The phone says "FRP is enabled, not allow download non-FRP aboot binary"
Odin doesn't work
The samsung customer service in singapore (my country) is not able to help. Would really appreciate it if somebody could help me with this.
-Michael
Click to expand...
Click to collapse
Mikekaipas said:
Hi,
I have removed the blue screen, i tried flashing the stockrom after wipe/factory reset failed. I found several problems in the recovery screen. There is "dm-verity verification failed" error and error during wiping, there is a problem about mounting to / system and formatting/ sbfsthing. i don't understand any of this jargon.
Hope i can get some help for this, please.
Thanks
Click to expand...
Click to collapse
Don't worry about /sbfs other Samsung devices get the same warning.
Dm-verity is usually due to a modified system partition or just the wrong firmware.
Wipe issue is likely because of frp lock.
Thanks Ashyx.
Right now when i try turning on my phone, my phone just keeps restarting and the typical welcome screen appears. Nothing further happens.
ashyx said:
Don't worry about /sbfs other Samsung devices get the same warning.
Dm-verity is usually due to a modified system partition or just the wrong firmware.
Wipe issue is likely because of frp lock.
Click to expand...
Click to collapse
Mikekaipas said:
Thanks Ashyx.
Right now when i try turning on my phone, my phone just keeps restarting and the typical welcome screen appears. Nothing further happens.
Click to expand...
Click to collapse
Thanks and my phone also got same issue with mikekaipas
Hi, so anyone out there with any suggestions to remedy the situation? Or will i just have to give up on my phone?
Mikekaipas said:
Hi, so anyone out there with any suggestions to remedy the situation? Or will i just have to give up on my phone?
Click to expand...
Click to collapse
i also already tired to try on my phone; should i buy new A9?
Hi all
I want to flash odin a9000 hong kong version, and I am afraid of this looking this thread
I am on latest hong kong rom 5.1.1., unlocked bootloade by crom , rooted, twrp installed...
So, do I need to afraid of this @steberg @ashyx and other advanced users
thanks
Man... Oh maaaan.....
I have also got this problem with SM-A9000.
via smart switch my firmware detected as china built (BPE2). but the emergency recovery always failed at 100%
then i try ODIN, with china firmware ( i try with the newest & even the oldest & i have tried with both full AP instalation & the single instalation BL, AP, CP, CSC) the result:
"FRP is enabled, not allow download non-FRP aboot binary"
with PIT & Re-partition also fail. only add result:
"FRP is enabled, ignore PIT download"
when i try with HK firmware (either newest & all other) it's better while the full instalation fail.
the single instalation made it for BL, CP & CSC and i got into the boot loop which show black screen
and SAMSUNG GALAXY A9(6) logo and i can access recovery.
But AP instalation always fail ( i have tried PIT also), the screen said
"FRP is enabled, ignore PIT download"
"Volume Size is too big 7372800 < 7979008"
"ODIN : Invalid id ext4 image"
my question? is it really wrong firmware? because the BL, CP & CSC can be installed except the AP because of the system.img.ext4.
because with the China Firmware,none can be installed.
also in my recovery there log:
"dm-verity verification failed
E: failed to mount / system (Invalid argument)"
i tried to install TWRP, but still fail,its said:
"FRP is enabled, not allow download non-FRP aboot binary"
and as last resort i even try to tick "NAND erase all" but i just got the same result as above either with China and HK with PIT, with singular or full installation...
i've been working on this phone for several days and now kinda got confused.
1. i dunno how to disable this FRP (my phone no longer able to boot, so the developer option is out of question) is it possible with odin?
2. or is it because E: failed to mount? but i even try Nand erase all yet still no result.
3. or wrong firmware? i tried it all China and HK with PIT & re-partition, still no result.
4. is there a way to wipe everything and erase this FRP thingi ? ( i have tried to wipe all from recovery too) :crying:
Hi Guys,
today I wanted to flash the latest Stock ROM for my device via ODIN. I've done this many times before and (thought) I knew what I was doing. It is my third Phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly I wasn't aware that this particular device was locked.
After downloading the international firmware I tried to install it and ODIN got stuck while writing the system.img. After that my phone did not boot up (of course). After that I downloaded and tried to isntall the firmware of the carrier, but I had the exact same issue. When I turn my device on I get to an error screen which tells me to execute an "emergency recovery" via the Samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
FRP hinders me to install a custom recovery and the stock one does not allow any isntallations via ADB or SD card.
My qustion is: Does anyone know how I can install a rom from here?
I know that I had to have made some changes prior to the flashing, but as I said I was not aware and an Idiot for not double checking.
Since it is not bricked yet I suppose there must be an answer but I can't find anything.
Thanks in advance
Edit:
After only installing the stock bootloader, I am autmaticly entering it when I boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"
Fix
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
fabivons said:
hi guys,
today i wanted to flash the latest stock rom for my device via odin. I've done this many times before and (thought) i knew what i was doing. It is my third phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly i wasn't aware that this particular device was locked.
After downloading the international firmware i tried to install it and odin got stuck while writing the system.img. After that my phone did not boot up (of course). After that i downloaded and tried to isntall the firmware of the carrier, but i had the exact same issue. When i turn my device on i get to an error screen which tells me to execute an "emergency recovery" via the samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
Frp hinders me to install a custom recovery and the stock one does not allow any isntallations via adb or sd card.
My qustion is: Does anyone know how i can install a rom from here?
I know that i had to have made some changes prior to the flashing, but as i said i was not aware and an idiot for not double checking.
Since it is not bricked yet i suppose there must be an answer but i can't find anything.
Thanks in advance
edit:
After only installing the stock bootloader, i am autmaticly entering it when i boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"
Click to expand...
Click to collapse
have u solved your problem ? This problem i am facing on the s7edge nougat ? Plz help ?
Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might be worth a try!
Good luck!
Fabivons said:
Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might me worth a try!
Good luck!
Click to expand...
Click to collapse
y i have done that and the device boots up but some applications force close and when i insert the memory card , the phone gets restarted everytime
Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Tell us in detail now.
SjDU said:
Tell us in detail now.
Click to expand...
Click to collapse
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?
suhaibahmad said:
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?
Click to expand...
Click to collapse
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.
Fabivons said:
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.
Click to expand...
Click to collapse
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally
suhaibahmad said:
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally
Click to expand...
Click to collapse
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.
Fabivons said:
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.
Click to expand...
Click to collapse
thats your kindness , yes i have performed the factory reset several times from recovery , but when i trying to reset it from settings , it goes after restart to recovery with dm-verity error , then i wipe and factory reset from there
Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model
SjDU said:
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model
Click to expand...
Click to collapse
Well FRP has to be turned off (the button in the menu is called "OEM unlock, the button has to be set to on which deactivates FRP). You don't mention using a PIT file - did you use one?
So, I have here a great old Note 4.
It has the generic mmc errors that cause it issues when booting and sleeping so I decided to give it a new rom. I bumped it into developer options, enabled usb debugging and fastboot and turned it off. I opened up odin, found the right twrp file to flash as well as a stock rom. I loaded it up and fired. The issue then was that the PIT partition had issues. Pit partition failed on odin's side, and flash read failure as well as a pit error of some sort on the phone's side. So I did my homework. I then tried to flash a new .pit file, I made sure the boxes were filled out correctly, had the right pit file as well as a correct stock rom, and the right drivers. It failed again with exactly the same errors. I don't know how you can manage saying that you can't flash the file your trying to fix but whatever. So I did more research and continued to change the usb cable to the original one that came with the phone, change the usb port, change versions of odin, use administrator privileges, find another .pit file, and change the pc. None of these worked, they all gave the same errors no matter what I did. So I moved on to see what else I could do, there was only one more issue though, the phone wouldn't boot up to an OS, if I tried to boot up normally it would boot into recovery, and if I booted into recovery it would boot into download mode with a message saying that the mme error caused it to. SO I couldn't do anything like flashfire or rom manager nor could I do something like root the device! So I did more homework, I turned to adb, because I saw something about an alternative to odin. Unfortunately, the phone has to boot up so you can connect it properly before you boot into download mode. So I did more homework and can't get anywhere, I am completely lost as to what to do because I can't flash odin or adb and sd card can only flash .zip files. I have no idea where to find a .zip for cwm or twrp that will work for my phone and the 2 files that I thought would work only gave me errors. I definitely am drowning in error messages and hope someone who knows what in the world is going on can help me get out of this mess.
Sincerely,
TiffPiff
Hi!
My G-935F is bricked after I downloaded the latest update. Phone is all stock with no mods at all.
Tried to flash the whole phone with Odin, witch worked. But the phone is still stuck in start screen.
I also tried to flash different roms to it but since it is a uprooted phone, that never worked. Is said something like binary 4 device 2. Also tried to flash earlier BL but the phone won't downgrade. It also complains about FRP sometimes when trying to flash different roms.
Download mode is still avalible but I am unable to get in to recovery mode.
Is the phone hardbricked or is there a solution I haven't tried?
Very greatfull for any input.
Removed
ultimatepumperx1 said:
You are fine if you have access to Download mode, just download the Stock firmware from sammobile.com since you have international version just pick your country if you are unable to find exact same country firmware try like germany one but there might be firmware for example Nordic countries and it is just g935f firmware for nordic countries and take sammmobile site and if you are example from germany then get germany version if possible you can still use your phone but you might can't use samsung pay with different country firmware not sure but yea. I guess you are finnish because of the end of your name "lainen" im too
Click to expand...
Click to collapse
That is what I have done all ready. Several times. And there are no problems with the flashing process what so ever. But the phone won't continue to boot beyond the first start-up screen. It is stuck in the first logo that appears when I start the phone.
No I'm actually from Sweden. But neighbours then!
ultimatepumperx1 said:
Hmm, seems strange what we know that your phone isn't hard bricked. Try this
if you are unable to view it i can explain it here so flash whatever country' firmware i recommend your own which is this case sweden so put everything in the odin remember to put CSC instead of HOME_CSC then boot to recovery mode(VOLUME UP+HOME+POWER) hold until you see updating then you should see no command then just wait few seconds to let it think:highfive: think then go vol down to factory reset then power again vol down to the yes! then power again and then go boot to the system using power button and cross fingers!
Click to expand...
Click to collapse
Bro his frp lock is enabled so he can't factory reset it and flashing stock rom succeeds but no boot up. Also unable to flash twrp recovery or boot in normal recovery. We've been looking for a solution but so far no luck
ultimatepumperx1 said:
Okay, sir i know, that he can't flash twrp because of frp lock, but he actually can factory reset trough recovery system if he flashes latest stock rom he will get stock recovery whatever he does, also he has flashed many different firmwares already so i bet there must be recovery
---------- Post added at 07:08 AM ---------- Previous post was at 07:04 AM ----------
You need to factory reset your device, because you have old data of your system, sadly they are unrecoverable, but atleast you don't end up with brick
Click to expand...
Click to collapse
The problem is that I can't get in to recovery mode. If I Could, then I guess there wouldn't be a problem to get the phone up and running. But since I can't, there Is a bigger problem.
Yesterday, when trying different solutions. I tried to get in to recovery mode after a total flash. And then I booted in to a blue screen with the droid on it, and the text underneath it that was saying "erasing".
That was the only change I seen since the phone got bricked. Even if the system erased itself, and I did a total flash afterwards, the system won't boot, and I still can't get in to recovery mode.
Hi, I'm getting exactly the same issue here, almost tried everything, frp lock is enabled i can't acces to recovery menu and i'm unable to flash TWRP, frp lock blocked everything, i can just access to download mode
Please, I need some help with my SM-G9350 Hong-Kong Galaxy S7 edge on Binary 4
I got custom binary blocked by frp lock on SM-G9350 HK Hong-Kong Galaxy S7 edge, and then I flashed stock firmware via Odin and all was just fine and Odin succeed pass, but when installing system updates in recovery it was up to 32% then erasing and then it should boot up system, but it didn't it keeps rebooting to recovery with no options at all, just showing the android guy with no command below and then when I hard it to enter in recovery menu it shows a black screen with some lines that says couldn't open recovery cause unknown and no such file directory, and device is busy, and keep doing the same thing, I did same and flashed again with latest firmware but same thing happened, and then I tried to flash TWRP in order to flash a custom rom but Odin fails and says in download mode custom binary recovery blocked by frp lock, known that my device's bootloader is already unlocked and I flashed before this a whole of stuff, now, I can just access to download mode, otherwise I can't do anything else even no adb , there is no a combination file for the Hong-Kong variant G9350ZH, there is only for the Open-China variant G9350ZC which is not combatible with the device, even there are no adb enabled files, if someone has a solution for this, please kindly take care of this problem
THIS IS REALLY IMPORTANT: I watched too many videos on YouTube and in conclusion flashing stock firmware is enough to get rid of many issues including the frp lock, so, here there are two different S7 edge devices with two different processors and both got the same and exact problem with latest stock rom, what Samsung done with latest firmwares of the Galaxy S7 edge, they made a lot of new devices running pie, and S7 should be old according to them while a lot of S7 users are waiting for a Pie OneUI update, I got some problems earlier but flashing the Old CRH1 solved the issues and now with their latest firmwares all bricks up
Here's what it says in recovery .. attached below, with no usual selection menu at all
ultimatepumperx1 said:
okay so you can boot to recovery if you have stock recovery there, so go to download mode and type to adb "fastboot reboot recovery" and it will boot and you will see droid maybe saying "updating or smth" then no command and let it think for atleast minute and you should be inside recovery after that or just follow vol up and power and home button like i said then just wait minute again when you see the droid.
---------- Post added at 09:25 AM ---------- Previous post was at 09:22 AM ----------
Click to expand...
Click to collapse
I am trying to get adb to work. I dont know how it works but as soon as i open the ADB.EXE file,
the cmd flashes up really quick, with a lot of text in it, just to dissapear again.
I cant get it to stay to type in any commands. The phone, when i am
opening ADB.EXE, is plugged in and in download mode. Is it anything i am doing wrong
or is the phones firmware so corrupt so it doesent recognise it?
And does really ADB work on a phone where debuggning mode is untouched?
ultimatepumperx1 said:
okay so you can boot to recovery if you have stock recovery there, so go to download mode and type to adb "fastboot reboot recovery" and it will boot and you will see droid maybe saying "updating or smth" then no command and let it think for atleast minute and you should be inside recovery after that or just follow vol up and power and home button like i said then just wait minute again when you see the droid.
---------- Post added at 09:25 AM ---------- Previous post was at 09:22 AM ----------
then you have installed wrong firmware make sure to get latest firmware and install it with latest odin.
Latest odin: https://odindownload.com/
and Latest Firmware from https://www.sammobile.com/firmwares/galaxy-s7-edge/SM-G9350/
make sure to put your country if possible or what it came with,
Click to expand...
Click to collapse
I'm using the right firmware from sammobile and right latest odin, if it was not the right firmware Odin will never let me flash at all, and it is the country that it came with, unfortunately
So i found this file on the internet
Frp Lock disable flash with odin to ap
Maybe try this
https://www.mediafire.com/file/7du404j8hn8da9n/Exynos.tar/file
Reboot to download mode to check
I haven't tested it
gupt07ash said:
So i found this file on the internet
Frp Lock disable flash with odin to ap
Maybe try this
https://www.mediafire.com/file/7du404j8hn8da9n/Exynos.tar/file
Reboot to download mode to check
I haven't tested it
Click to expand...
Click to collapse
This did not do the trick! Odin fails ond i got a message in red
that said "custom binary (userdata) blocked by frp"
Im testing the other tip with ABD and fastboot. But no luck yet.
ultimatepumperx1 said:
No adb doesn't work but fastboot does which comes in the same folder so what you need to open cmd in the adb.exe file it is normal to flash if you do it like that but you have to navigate to the adb folder and then type fastboot reboot recovery what is basicly does is that it tells fastboot.exe to reboot recovery and this code won't work but you will understand what i mean so "fastboot.exe reboot recovery" don't put ".exe" and it will work like i said before.
Click to expand...
Click to collapse
Think i got he hang of it. But when i am trying to connect to my S7, it cant find y device.
Feels like i am not beeing able to connect to the phone while in download mode.
I have a S6 that i am experimenting with by the side, that is working. Abd are not able to connect
this device either when in download mode. Maybe there is another way around it with this program?
Dampalainen said:
This did not do the trick! Odin fails ond i got a message in red
that said "custom binary (userdata) blocked by frp"
Im testing the other tip with ABD and fastboot. But no luck yet.
Click to expand...
Click to collapse
I'm all out of ideas
Flashing stock rom always does the trick. Maybe try the one from sammobile for your country
gupt07ash said:
I'm all out of ideas
Flashing stock rom always does the trick. Maybe try the one from sammobile for your country
Click to expand...
Click to collapse
I can try. But it feels just like there is somtething wrong with the booting process. Is everything the phone needs to boot, in the BT file that you can flash in ODIN or is there anything else? I mean, if the boot file would work properly, then i would have gotten in to recovery menu.
Dampalainen said:
I can try. But it feels just like there is somtething wrong with the booting process. Is everything the phone needs to boot, in the BT file that you can flash in ODIN or is there anything else? I mean, if the boot file would work properly, then i would have gotten in to recovery menu.
Click to expand...
Click to collapse
Yes ofcourse
Is it the firmware you flashed?
gupt07ash said:
Is it the firmware you flashed?
Click to expand...
Click to collapse
Yes! Thats the one!
Have tried some different solutions this evening and got nothing.
Even used erase NAND option along with the correct PIT file.
Read alot about it before proceeding with NAND erase.
There is no change on the phone after NAND erase.
even though i have made a total flash of the phone afterwards.
Feels like it must be a hardware issue?
Dampalainen said:
Yes! Thats the one!
Have tried some different solutions this evening and got nothing.
Even used erase NAND option along with the correct PIT file.
Read alot about it before proceeding with NAND erase.
There is no change on the phone after NAND erase.
even though i have made a total flash of the phone afterwards.
Feels like it must be a hardware issue?
Click to expand...
Click to collapse
Can't be a hardware issue..
Maybe the old firmware was different than what you're trying to flash. Heck if I were you, I'd try all of them stock roms until it boots up
ultimatepumperx1 said:
Okay, sir i know, that he can't flash twrp because of frp lock, but he actually can factory reset trough recovery system if he flashes latest stock rom he will get stock recovery whatever he does, also he has flashed many different firmwares already so i bet there must be recovery
---------- Post added at 07:08 AM ---------- Previous post was at 07:04 AM ----------
You need to factory reset your device, because you have old data of your system, sadly they are unrecoverable, but atleast you don't end up with brick
Click to expand...
Click to collapse
gupt07ash said:
Can't be a hardware issue..
Maybe the old firmware was different than what you're trying to flash. Heck if I were you, I'd try all of them stock roms until it boots up
Click to expand...
Click to collapse
You mean all the others with different languages?
I was downloading a Norwegian version tonight. I am going to try that one tomorrow.
But since the recovery menu is still missing, it feels like the problem would be in the BL file?
Dampalainen said:
You mean all the others with different languages?
I was downloading a Norwegian version tonight. I am going to try that one tomorrow.
But since the recovery menu is still missing, it feels like the problem would be in the BL file?
Click to expand...
Click to collapse
Yes all the latest firmwares from different regions. Surely something should work
If you do fail, dm a developer. They might have a good solution.
http://forum.gsmhosting.com/vbb/f162/gsm-flasher-frp-reactivation-lock-remover-pro-2200193/
...
https://www.s7fanclub.com/gsm-flasher-pro-frp-tool-for-windows-pc-to-bypass-samsung-frp-lock.html
ultimatepumperx1 said:
I would try smart switch if it will get your recovery working but try everything
---------- Post added at 06:31 PM ---------- Previous post was at 06:30 PM ----------
Trying to unlock frp via download mode is last thing you should do, myself i would just find a way to get recovery working.
---------- Post added at 06:33 PM ---------- Previous post was at 06:31 PM ----------
i think your partitions are ****ed up somehow. i think there is way to restore them.
---------- Post added at 06:35 PM ---------- Previous post was at 06:33 PM ----------
have you tried flashing bl with pit file only or ap with pit file only,
---------- Post added at 06:37 PM ---------- Previous post was at 06:35 PM ----------
because pit file stands Partition Information Table (PIT) it might work.
Click to expand...
Click to collapse
I'm having the same and exact problem, nothing worked it sucks up, tried pit fle and even with some cracked boxes to reset frp but nothing worked