Hey guys,
I tried to root my gf's S5 with CF-AutoRoot's package. I got this for the specific version which I double-checked
Included in the package was Odin and the image with an "installer".
Everything was fine, device detected in Odin, selected image in AP and let it rip... Except I got an error after it was in the process, under UDC start, can't remember exactly as I had restarted the device with the loading bar at like 30% of the way... it stated something dev_state
After I restarted, I got the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I would've thought it was going to be pretty straight forward and decided not to do a backup but I'm so getting killed if I'm going to lose the data!!!
Any insight? thanks
I tried to get Samsung Kies for the recovery but under the list of devices requiring emergency recovery it won't detect it...
I managed to retry the Odin flash with the same outcome.
The error message is unsupport dev_type if that makes any sense to someone
Well issue seems to have fixed itself by flashing latest TWRP... The Odin flash went smooth and phone booted normally...
must've been something off with the AutoRoot
Related
I have a Verizon Samsung Galaxy S4 (SCH-I545) which I previously rooted via the Open1Your1Eyes0 pwn script. Everything was great except I wanted to update to the latest version and my phone failed with each attempt. I tried to unroot it using Odin to flash the VRUAMDK_NoWipe.tar.md5 stock ROM image.
That failed and now it's stuck on the ODIN MODE "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." message screen. The phone won't boot. If I hold Vol Down I can still go to the Downloading firmware screen, but I've tried flashing 3 other stock ROM's and nothing will work.
Any suggestions?
You are in the wrong forum. You need to go the verizon part.
I was trying to install an Official Stock Samsung Galaxy S4 GT-I9505 firmware, from SAMMOBILE Link for the firmware I tried to use: http://www.sammobile.com/firmwares/3/?download=26516. So while flashing it with ODIN, I think it just randomly disconnected, but that just bricked my phone. I don't know whether it is a soft brick or a hard brick, but this is what happens to my phone, every time I turn on my phone whether it's done normally, the download mode or recovery mode method I will be stuck on that screen.
So now I typed in the error on Google to see how it can be fixed. Link to the method to fix the error: http://androidcentral.us/2013/09/how-to-fix-firmware-upgrade-encountered-an-issue-on-kies/
Firstly, my computer (running Windows 7 ULTIMATE 64-BIT) can detect my phone, saying the drivers have been installed successfully. However KIES doesn't detect mine. Anyways I still try to do this method where I have to go to Tools -> Firmware Upgrade and Initialization on KIES. I type in my model name: GT-I9505, that works, now I have to do my S/N or Serial Number: RF1DXXXXXXX, so when I press OK it says GT-I9505 doesn't support 'Intialising', so I am stuck have no idea what to do.
Also, while flashing I tried repartition my S4, to remove all of the stuff I had, none important, except my music which I transferred to my PC. Solved, just flashed Official firmware, it now works.
Just separately repartitioned my S4, it works but S4 is now stuck on boot loop, so have to flash a 4.4.2 Official Firmware.
Harnessful said:
I was trying to install an Official Stock Samsung Galaxy S4 GT-I9505 firmware, from SAMMOBILE Link for the firmware I tried to use: http://www.sammobile.com/firmwares/3/?download=26516. So while flashing it with ODIN, I think it just randomly disconnected, but that just bricked my phone. I don't know whether it is a soft brick or a hard brick, but this is what happens to my phone, every time I turn on my phone whether it's done normally, the download mode or recovery mode method I will be stuck on that screen.
So now I typed in the error on Google to see how it can be fixed. Link to the method to fix the error: http://androidcentral.us/2013/09/how-to-fix-firmware-upgrade-encountered-an-issue-on-kies/
Firstly, my computer (running Windows 7 ULTIMATE 64-BIT) can detect my phone, saying the drivers have been installed successfully. However KIES doesn't detect mine. Anyways I still try to do this method where I have to go to Tools -> Firmware Upgrade and Initialization on KIES. I type in my model name: GT-I9505, that works, now I have to do my S/N or Serial Number: RF1DXXXXXXX, so when I press OK it says GT-I9505 doesn't support 'Intialising', so I am stuck have no idea what to do.
Also, while flashing I tried repartition my S4, to remove all of the stuff I had, none important, except my music which I transferred to my PC.
Just separately repartitioned my S4, it works but S4 is now stuck on boot loop, so have to flash a 4.4.2 Official Firmware.
Click to expand...
Click to collapse
Hi,
Can you get into recovery?
Can you still see your phone in odin?
If so , disable kies (task manager) and try to flash the firmware again.
Wipe data and cache before and after flashing firmware.
Hello guys,
I need extremely technical help as no longer know what to do.
I have a Galaxy S7 Edge device, which installed the rom BobCat and everything went well until then.
Later I decided to install another rom to test KingRom that left me unsatisfied, because I thought it had some bugs. Had the TWRP 3.0.0 recovery and decided to upgrade to 3.0.2, everything went well.
At one point I do not remember when or how if was when install back, downgrade to TWRP3.0.0, I do not remember if it was via Odin or TWRP, it happens that the installation stopped halfway. Then unplug the device, restarted in recovery mode and got the following message "E: falied to mount EFS (Invalid Argumen)", I could not restart the device (Boot Loop, and stucked at Samsung Logo) except in Recovery Mode, which also made to stay without IMEI number and Serial Number.
I googled until I came to this tutorial:
http://forum.xda-developers.com/s7-e...ssues-t3379516
I followed all the steps explained, I back up EFS_backup and RADIO_bakcup partitions.
Installed FACTORY BINARY G935, everything went well. After restarted, already had the correct IMEI number but still did not present the S / N.
After all that, i tried to install Stock Firmware via Odin, from here started the problems that could not solve.
In the first attempt Odin stucked in "System" (also used the PIT file with the same CSC ... .i do not know if I was right using PIT?). Restarted the device forcibly, entered the stock Recovery, did a complete wipe and always get this message "E: falied to mount System (Invalid argument), I returned to install Factory Binary, then reboot in Recovery and the same message no longer appeared.
Again I try to install the Stock Firmware and Odin always stucks in System, or NAND writing, or Partition, etc. I've tried various Stock Firmware, with and without PIT files, always without success.
Only Factory Binary that successfully installs. The TWRP via Odin also but when device restarts to enter Recovery Mode always get the message at the top of the display:
"Recovery image signature check Fail"
"Reboot to avoid Warranty bit set."
1. Does the partitions are in good shape? how can I check it?
2- I did good or bad using PIT file?
3- Does the problem is running Windows XP through a Virtual Machine?
4 What else can I do?
In all actions used and am using a Macbook 4.1, OsX Lion 10.7.5, Odin 3.11 Windows XP Professional 32bit through Oracle VM VirtualBox 3.4.38
Device:
Galaxy S7 Edge (SM-G935F) CSC = SWC SwissCom
1st Original Firmware: (I guess was 1?) G935FXXS1APG5_G935FVFG1APF3_SWC
Need help Please
Thank you so very much!
Hi,
I recently got me a Galaxy S5 (SM-G900F) and the first thing i wanted to do was installing CM13 as I always do with my new phones. However, when i followed te steps on CM wiki using Heimdall to flash TWRP the blue bar of the downlaod mode increases a small bit, then stops and in the command promt it says something about error with finding PIT. After trying this for three times i decided to go with Odin, which I do prefer anyways.
I tried flashing TWRP , the blue bar is filling to 100% but then on the little screen where Odin usually states FAIL! or PASS! it just says RESET! and my phone is restarting. Shortly after it restarded you can see the RESET! turning to PASS!, but when I tried checking in TWRP is installed, it wasn't. I tried it again and then Odin suddenly says FAIL! After restarting my phone it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". I couldnt even enter download mode anymore till I tried if getting out the battery would work. I could enter download mode again and flashed the same TWRP on my phone again, and aigain it says RESET! but after that my phone worked again. I tried flashing with another version of Odin and TWRP but same thing happened - First run it said RESET!, second run FAIL!.
I thought maybe rooting the device and installing TWRP via their app afterwards could do the trick. So i tried flashing Autoroot with Odin but it made my phone showing a screen with Samsung logo and in the upper left corner something about recovery mode, seemed to be a loop/freeze. So i took out the battery again and flashed TWRP and that solved the problem again. At last I tried rooting by using TowelRoot but it says the service is not available for my device, even though S5 is listed as a supported device.
I really have no idea what to do anymore, would be very grateful if someone could come up with a solution.
BTW: Is it possible to flash CM13 without using custom recovery by using stock recovery?
Greetings
Khalitas
Khalitas said:
Hi,
I recently got me a Galaxy S5 (SM-G900F) and the first thing i wanted to do was installing CM13 as I always do with my new phones. However, when i followed te steps on CM wiki using Heimdall to flash TWRP the blue bar of the downlaod mode increases a small bit, then stops and in the command promt it says something about error with finding PIT. After trying this for three times i decided to go with Odin, which I do prefer anyways.
I tried flashing TWRP , the blue bar is filling to 100% but then on the little screen where Odin usually states FAIL! or PASS! it just says RESET! and my phone is restarting. Shortly after it restarded you can see the RESET! turning to PASS!, but when I tried checking in TWRP is installed, it wasn't. I tried it again and then Odin suddenly says FAIL! After restarting my phone it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". I couldnt even enter download mode anymore till I tried if getting out the battery would work. I could enter download mode again and flashed the same TWRP on my phone again, and aigain it says RESET! but after that my phone worked again. I tried flashing with another version of Odin and TWRP but same thing happened - First run it said RESET!, second run FAIL!.
I thought maybe rooting the device and installing TWRP via their app afterwards could do the trick. So i tried flashing Autoroot with Odin but it made my phone showing a screen with Samsung logo and in the upper left corner something about recovery mode, seemed to be a loop/freeze. So i took out the battery again and flashed TWRP and that solved the problem again. At last I tried rooting by using TowelRoot but it says the service is not available for my device, even though S5 is listed as a supported device.
I really have no idea what to do anymore, would be very grateful if someone could come up with a solution.
BTW: Is it possible to flash CM13 without using custom recovery by using stock recovery?
Greetings
Khalitas
Click to expand...
Click to collapse
RESET! is basically the same thing as PASS! What version of TWRP are you installing? The keis screen you got is the same as download mode. Why are you using heimdal? your idea to go with Odin was a good one. Anyways, download TWRP 3.0.2 (not 3.0.2-1 or 3.0.2-2 as they are buggy) and flash it in Odin, reboot to recovery and install the ROM you like, of course following its specific install instructions. No, you cant install a custom rom with stock recovery
Thanks for your answer, meanwhile i managed to fix this problem. Had to flash the latest Firmware because twrp (could just install the oldest version otherwise I had no option to boot into recovery at all) said no OS installed. After rooting via Odin worked like it's supposed to.
Why did I use Heimdall? Because I wanted to stick to CM-wikis instruction and they used Heimdall.
I've successfully rooted some of my previous androids, and currently have a rooted LG tablet. Today I was trying to root my Galaxy S7 and I bricked it and couldn't figure out how to unbrick it. I was following this guide devs-lab .com/root-Samsung-galaxy-s7-s7-edge.html. Everything looked like it worked Odin said pass but my phone got stuck in a boot loop. I tried to root it with a tar.md5 from a different site but it failed. When I put it into recovery mode it showed a big circle said "Installing updates" and then it went to a black screen showing the droid with a red caution sign and said "No command". From there I was able to get into the recovery menu and I tried wiping the cache and that didn't work, I then tried the factory reset and that didn't work. I then downloaded the "Stock_DeOdexed_Debloated" ROM from here and tried to sideload it using adb but that failed saying "E:footer is wrong. E:Signature verification failed" I tried to install it from the SD card but got the same message. In the recovery menu it said "No Support SINGLE-SKU, Supported API:3, # MANUAL MODE #, -- Appling Multi-CSC..., Applied the CSC-code : TMB, Successfully applied multi-CSC., Successfully verify for dmverity hash tree". I downloaded a stock firmware zip file I found on a different site and flashed the files inside using Odin and got my phone back up and running. I can’t figure out how to attach files so I've included links to the stock firmware I used as well as the version of Odin I used.
Stock firmware - downloadmirror. co/Urs/G930TUVU4APK1_G930TTMB4APK1_TMB.zip?download_token=20ae1b122f8519d6cfc69c0ef013b3f4c6856d15149bdc46bc3bcfecfb91ee1f
Odin - dropbox. com/s/go43hspdcbg9rld/Odin3_v3.12.5.rar?dl=0
brick s7 edge
gilbojr said:
I've successfully rooted some of my previous androids, and currently have a rooted LG tablet. Today I was trying to root my Galaxy S7 and I bricked it and couldn't figure out how to unbrick it. I was following this guide devs-lab .com/root-Samsung-galaxy-s7-s7-edge.html. Everything looked like it worked Odin said pass but my phone got stuck in a boot loop. I tried to root it with a tar.md5 from a different site but it failed. When I put it into recovery mode it showed a big circle said "Installing updates" and then it went to a black screen showing the droid with a red caution sign and said "No command". From there I was able to get into the recovery menu and I tried wiping the cache and that didn't work, I then tried the factory reset and that didn't work. I then downloaded the "Stock_DeOdexed_Debloated" ROM from here and tried to sideload it using adb but that failed saying "E:footer is wrong. E:Signature verification failed" I tried to install it from the SD card but got the same message. In the recovery menu it said "No Support SINGLE-SKU, Supported API:3, # MANUAL MODE #, -- Appling Multi-CSC..., Applied the CSC-code : TMB, Successfully applied multi-CSC., Successfully verify for dmverity hash tree". I downloaded a stock firmware zip file I found on a different site and flashed the files inside using Odin and got my phone back up and running. I can’t figure out how to attach files so I've included links to the stock firmware I used as well as the version of Odin I used.
Stock firmware - downloadmirror. co/Urs/G930TUVU4APK1_G930TTMB4APK1_TMB.zip?download_token=20ae1b122f8519d6cfc69c0ef013b3f4c6856d15149bdc46bc3bcfecfb91ee1f
Odin - dropbox. com/s/go43hspdcbg9rld/Odin3_v3.12.5.rar?dl=0
Click to expand...
Click to collapse
i have the same problem on my s7 dge. i havent find the solution yet. im desperate mine is from tmobile