Hello,
I've Samsung Galaxy SM-J701F/DS and i did factory reset and started getting into panic mode. So, I tried to flash stock ROM through odin and I only selected AP and left other files like Bl, CP and CSC. Thus it took longer time without any result so, I closed the odin. Since then my phone only boots in download mode.
And while trying recovery or normal boot I get " Error Cannot Update Software ".
I used this ROM:
https://www.sammobile.com/firmwares/...-nxt/SM-J701F
And now my phone is showing as Samsung USB Modem while plugging in PC.
Related
Phone specs:
Samsung Galaxy S3 Verizon SCH-i535
It was already running KitKat 4.4.2 before I rooted
This is my first time rooting and flashing ROMs to my Samsung Galaxy s3 and I have bricked it. I'm pretty sure it can be salvaged but have yet to find anything that works.
I have written the long version for those who need it, but the short version is that I screwed up and can no longer boot into recovery mode or normal mode, I'm not even sure if Download mode is working, and my device isn't recognized by Kies or Odin on my PC so I cannot yet do a recovery from there.
As of now my phone only boots into Odin Mode and gives the following info:
ODIN MODE
PRODUCT NAME: SCH-I535
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
QUALCOM SECUREBOOT: ENABLE
BOOTLOADER AP SWREV: 2
and displays the yellow triangle error and says: Firmware upgrade encountered an issue. Please use Software repair Assistant & try again.
I tried to use Samsung Kies which has an emergency firmware tool but my device will not connect and become recognized by the program.
This is pretty much where I'm stuck.
Keep reading if you need additional info.
Steps leading up to problem:
I was able to Root the device succesfully
I then downloaded the latest CM11 package (cm-11-20140217-NIGHTLY-d2vzw.zip) and Gapps
I also downloaded the TWRP recovery img (openrecovery-twrp-2.7.1.0-d2vzw.img)
Once I had these downloaded I got the app [ROOT] Rashr - Flash Tool
I opened the app and tried to do a backup but I'm pretty sure it failed, or at least it said it failed. I couldn't find out how to check, but was not worried since I have already backed up my important files to the verizon cloud.
On the app I went to recover using other file and found the TWRP recovery img I downloaded.
From here I booted into recovery manually, but it did not bring up the TEAMWIN screen for TWRP like I've seen in other video tutorials so I rebooted into normal mode went to the Rashr app again and followed the prompt to do a Recovery boot using the TWRP img.
THIS IS WHERE THE PROBLEMS BEGAN:
It began to lead into recovery mode but it gave a message that said something along the lines that I have tried installing a custom OS and to take my phone to the nearest verizon store.
I turned it off and tried to boot back normally but got the same error.
I tried to boot into Download mode and was successful! So I thought yaay!
Read a tutorial to reload a stock version of android here: http://forum.xda-developers.com/showthread.php?t=2586319
I followed all the steps but when i got to 7. which said You should see your phone under ID:COM (you should also see it has been added in message) I was not seeing my phone there. I figured it may be OK since I was able to install the drivers so that meant the USB was working so I went ahead and ran Odin to recover Jelly Bean 4.3 onto the device.
My thoughts and guesses as to what the problem is:
I think that it may be because I was already running 4.4.2 and/ or didn't have the proper bootloader when I tried to do the TWRP recovery.
Am I on the right track? Thanks for any help!
Please ask. In correct forum this is int'l s3 (i9300) forum
Hi i had tried to go back to stock ROM on my galaxy s4 but i ended up getting a failed error in the middle of it flashing the firmware getting a device removed error then my phone went off and rebooted in Odin mode saying that software update failed i tried using Odin and Verizon wireless repair assistant but my phone is not being recognized in either program i usually get my phone to be recognized by going into recovery first and going to the bootloader but i can't get into recovery mode now is there a way i can get my phone to be recognized on my computer without going into recovery mode
Let me start off by saying I have already scoured this forum and other sources for a solution to this problem. I should add that I am somewhat bound by the confines of my experience, also.
Like many others here, my Samsung S4 mini GT-I9195 is stuck in a boot loop, unable to get into recovery mode. It can get to download mode, but is not recognized by my PC.
Things I've done so far:
1. tried to boot in recovery mode - doesn't work, says "Recovery starting..." then restarts into boot loop
2. checked battery - not it
3. dissasembled phone and checked power button - works fine
4. tried Samsung Kies - "Device is not responding. To resolve the issue, reboot the device." - no can do (note that I only just installed Samsung Kies on my PC for the first time after the boot loop started)
5. flashed firmware using Odin - PASS! - still in bootloop w/no recovery mode
6. flashed firmware again using Odin w/Auto-Reboot unchecked - PASS! - then attempted to reboot into recovery - no go, still in bootloop w/no recovery mode
The firmware I successfully flashed was Poland/T-Mobile version 4.4.2 downloaded from sammobile.
The one thing I have NOT tried is to repartition the pit file. Would this possibly make any difference? If it's worth a try, can I do this using the tar.md5 package above, or do I need a separate .pit file and if so, how do I know I have the right one???
After doing a little reading, I downloaded CSB_signed_SERRANOLTE_ONEPIT_OPEN_130523.pit, which was included in a 'repair firmware' .zip file that also included separate bootloader, code, csc and modem files. I actually did try flashing those files (except for the pit file) and that failed (of course) with error "Device 2, Binary 1", so I flashed the firmware above again and it passed again.
What else?
- Phone is not rooted
- I have no idea if USB debugging is turned on or not
- I was doing nothing with the phone when it first died. I figured the battery might have somehow rapidly drained to zero even though it should have been around 70%. I had last touched the phone about an hour earlier, to shut off my alarm. I tried plugging in to wall charger but phone would not turn on even after an hour or more of charging. I really don't remember exactly how or when the bootloop started.
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB:0x30
BOOTLOADER AP SWREV: 2
WRITE PROTECTION: Enable
Anyone out there feel like helping out a noob today?
i have same problem
Actually , only one diferrent
KNOX WARRANTY VOID: 0x1
exactly same ,but i tried with pit 2 pit files and 2 diferent roms , and no result. Pleace help us!!!
Hello androids, I have a big problem or a good challenge, depends on your optimism. I've been looking for and trying solutions for hours and hours, but I think I've come across a wall and I need your help:
Originally I wanted to root my s7 Edge / SM - G935F (OS Marshmallow 6.0.1) by following a tutorial using an autoroot ROM for this phone. I remember I had USB debugging and OEM unlock enabled. I also installed the USB / ADB drivers correctly.
I used Odin v3.11, since they recommended using it for this mobile and MM 6.0.1. According to Odin, the rom was installed successfully, but my phone entered a loop with the Samsung logo and "RECOVERY IS NOT SEANDROID ENFORCING". Something failed in the process and I decided to install a S7 Edge stock ROM in 8.0.0 from SAMMobile (this one) with Odin v3.13 using HOME_CSC so that I don't lose certain data
Unfortunately everything was going well until just at the end when "hidden.img" did not process correctly and resulted in FAIL. I've been since then stuck with this error:
"An Error has occurred while updating the device software. Use the Emergency Recovery in the Smart Switch PC Software."
It won't even turn off. From there I can only access the Download Mode and neither the Smart Switch or the ADB & Fastboot console won't detect the device. Odin does recognize the phone, but every time I try to install a rom, the log gets stuck in "SetupConnection ..".
I have tried a bunch of solutions such as removing the "hidden.img" from the package, reinstalling the drivers, changing the USB port, changing Odin's version, installing only the BL, etc., but nothing shows progress...
I'm sorry if during the process I managed to do some stupidity that I am not aware of. Other phones I have never had problems, but now I feel defeated and lost. I need a savior! :crying:
Any way to make Odin work, ADB detect my device or access a working bootload? Thanks in advance!
Hi folks,
I've got a new A52 5G and wanted it to root. TWRP couldn't be used, because each and every possible solution failed. I even got stuck at boot with a message that the recovery couldn't get startet, even if I just restarted the phone without pressing the keys and without plugged USB cable.
Even flashing the original firmware was not possible. Then I tried to lock the bootloader again and flashing of the firmware was going on with odin. Puh... Then I used the Magisk method without TWRP to change die boot.img with magisk and load it in Odin. Success! I had now root on the phone. Yesterday I read about uninstall Magisk and install it afterwards on the B partition for updating the firmware over OTA. But accidentally I pressed the button below "uninstall" and it performed imediately. Now my phone is dead again... With unlocked Bootloader it is stuck in a bootload and I can start the Samsung recovery mode to wipe the cache for example. I wiped the phone completely, but it is still stucked in a bootloop.
Then I tried my first method: Just lock the Bootloader again (in the download mode) and then flash the new firmware with odin. But Odin either crashes or is giving me instantly the message "failed".
When I'm trying to start the phone (it happened also after locking the bootloader) i'm getting the download screen and the message with a big red !
"partition boot
Reason boot: Hash of data does not match digest in descriptor. [2nd] (3)
Calculated Hash of (boot) : 23B8CFD554, (VEMETA) : D23E59ACD6
CUSTOM boot
VBMETA A526BXXU1AUCA, 38851814R"
Now I unlocked the bootloader again, to access the recovery mode so I can turn it off. Otherwise its stuck in the damn bootloop. Can't flash and wipe doesn't help either.
Please help me somehow -.-
why did you u
Insomnium_D said:
Hi folks,
I've got a new A52 5G and wanted it to root. TWRP couldn't be used, because each and every possible solution failed. I even got stuck at boot with a message that the recovery couldn't get startet, even if I just restarted the phone without pressing the keys and without plugged USB cable.
Even flashing the original firmware was not possible. Then I tried to lock the bootloader again and flashing of the firmware was going on with odin. Puh... Then I used the Magisk method without TWRP to change die boot.img with magisk and load it in Odin. Success! I had now root on the phone. Yesterday I read about uninstall Magisk and install it afterwards on the B partition for updating the firmware over OTA. But accidentally I pressed the button below "uninstall" and it performed imediately. Now my phone is dead again... With unlocked Bootloader it is stuck in a bootload and I can start the Samsung recovery mode to wipe the cache for example. I wiped the phone completely, but it is still stucked in a bootloop.
Then I tried my first method: Just lock the Bootloader again (in the download mode) and then flash the new firmware with odin. But Odin either crashes or is giving me instantly the message "failed".
When I'm trying to start the phone (it happened also after locking the bootloader) i'm getting the download screen and the message with a big red !
"partition boot
Reason boot: Hash of data does not match digest in descriptor. [2nd] (3)
Calculated Hash of (boot) : 23B8CFD554, (VEMETA) : D23E59ACD6
CUSTOM boot
VBMETA A526BXXU1AUCA, 38851814R"
Now I unlocked the bootloader again, to access the recovery mode so I can turn it off. Otherwise its stuck in the damn bootloop. Can't flash and wipe doesn't help either.
Please help me somehow -.-
Click to expand...
Click to collapse
why did you OTA update the rooted phone
it is clearly written that your phone might brick.
what happened to you is your boot.img file is replaced with the newer version try replacing with the boot.img file of previous version.
I didn't, because I get (as always, this is not my first rooted phone) the message, that the system has been changed. OTA is not working and I read that uninstall magisk, update the phone and BEFORE reboot install magisk again on partition B. But I accidentaly pressed the second option in magisk, complete uninstall or how its name is. Didn't expected, that its start instantly without a "Caution" message.
Uninstalling Magisk should not bring my phone into a bootloop anyway, even if I wipe the cache. Or am I wrong?
raja0408 said:
what happened to you is your boot.img file is replaced with the newer version try replacing with the boot.img file of previous version.
Click to expand...
Click to collapse
That is the problem how do I do that, when everything with odin stops imediately or odin crashes.
Does Odin give you any error messages? Are you patching all of the files for the firmware AP BL CP & CSC? Are you making sure to use the non home CSC? Have you tried using Samsung Smart Switch to recover your phone?
Smart Switch didn't recognize the phone. The only error on Odin was "succeed 0 / failed 1).
It worked with Windows 10 notebook and the USB C Port. However it didn't worked on Win 7 and regular USB Ports. Very strange. Well, but now I have the original firmware and again lots of bloatware. TWRP doesn't work, impossible to boot with it. How can I root the A52 with Magisk that way, to deactivate it - if needed - for firmware updates? The phone doesn't has A/B partition.
Same happened to me.
So, I have an A52 Indian version and want to flash the Canadian firmware. I downloaded different versions of the Canadian firmware and used Odin to flash. I followed the instructions on downloading the files, loading them into Odin,hit Start and it kept failing. It was giving an error message regarding a repartitioning error. Could this be due to having to tick "OEM Unlocking" in developer options which I hadn't done?
Hey, is your phone still stuck ?
SHAREit​