To fix an issue, I flashed my original ROM by downloading it from this thread and following the instructions: http://forum.xda-developers.com/showthread.php?t=1469635
Now Kies doesn't let me try to update my firmware. Is there any way to fix this? or am I permanently stuck?
I had this problem too, Kies saying that I cannot update my Tab through Kies after flashing another ROM. I followed that same guide and it worked.
What you need to do is to boot into Recovery, but NOT the CWM Recovery.
It's the one that says "Android system recovery < 3e >" at the top.
Upon booting into this, it run a script that starts with # MANUAL MODE #, it then goes on to " -- Updating application... " and " -- Applying Multi-CSC... ".
That last bit is the step that 'resets' your Region I think to follow whatever ROM you last flashed, and in turn enabling it to play again nicely with Kies.
Hope that helps.
Related
hey guys im sorry if i post this on the wrong section but i followed this tutorial: droidviews(dot)com/root-galaxy-s6-and-s6-edge-on-android-6-0-1-marshmallow-update/ to root my s6 edge+ and it went black... after some research i found out the tutorial wasnt for my device(SM-G2928F) so i flashed it with cf-autoroot and then it boot looped for like an hour. I downloaded the original greek firmware from sammobile but it brings me up this error: SECURE CHECK FAIL : (BOOTLOADER).. any help?
UPDATE: changed the port and run Odin as admin now it says: SECURE CHECK FAIL : (RADIO) Odin log: pastebin(dot)com/4w1943HF
UPDATE: now when I exit recovery mode it doesnt start and tells me: An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software.(I can still go into recovery mode)
Let me check you have flashed a firmware not for your device with odin or just a zip? First I would try flashing the most recent firmware you can find for your device with odin, some bootloaders can't be downgraded. If that doesn't work then the emergency firmware recovery will work, I've used kies emergency firmware a few times.
Hopefully someone with your device will point you in the right direction if you are stuck
I flashed a firmware not for my device but I found a solution on another XDA post thank you
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.
Yo dudes!
So I've somehow f**ked up my J320FN, I'ts stuck in Firmware upgrade, I recieve this message> "firmware upgrade encountered an issue please select recovery mode in kies & try again", almost no matter how I launch the phone, the only alternative is Home+VolDown+Lock wich drags me to the Download thing page u use for Odin (I'm new to all this lol).
It all started with me recieving the phone the other day and i wasn't able to get past the "setup menu" , not even after factory-reset/wipe whatever, so I couldn't change the OEM and Usb stuff, aaand somehow when I entered kies I managed to start firmware upgrade wich didnt work out so well.. haha.
And now here i am, unrooted phone uncapable of accessing anything else than "firmware upgrade encountered an issue please select recovery mode in kies & try again".
And I really don't know what to do here haha =D, any help is appreciated! Thanks.
sooo is this the right category for this haha?
First, download odin for flashing your phone. You canf find it here in this forum . Just search it. Install the latest drivers. Go to sammobile or other site and download latest firmware for j320fn according to your country. Then , open ODIN v3.xx and select pda, csc and the rest according to files in zip file downloaded. If it's only one file select pda and find it. DO NOT CHECK NAND ERASE ALL. IT WILL MAKE YOUR PHONE A BRICK. Just check auto reboot and you'll be fine. After flashing phone will reboot and you can setup it ! If i helped tell me !
What Frost said or download Twrp 3.0.1-2 for the FN and flash that via Odin...If it enters recoverybwith Twrp just wipe dalvik cache data and system reboot...you also have adb and file manager with twrp..Good luck
Hello. I tried downgrading from the latest ASUS firmware to Android 6.0.1
I used this tutorial to install the raw firmware: http://www.asus-zenfone.com/2016/12/asus-zenfone-3-raw-firmware-and-asus.html
Went all the way to the last step when the app hanged. ASUS Flash tool went all the way saying
Code:
Run flash image script ...
It was hanged there. And as per this video, went all the way to the end where it showed the "code bar" on the right (https://www.youtube.com/watch?v=P8xg7A-P7Ak)
This is when the "Android" uninstalled driver showed up in Windows. This is under "Other devices - Android". I tried updating this driver using the ASUS_Android_USB_drivers_for_Windows found here: https://www.asus.com/Phone/ZenFone-3-ZE552KL/HelpDesk_Download/ but it wouldn't install the drivers.
Note that I used these ASUS USB drivers to get the ASUS ADB Interface installed. As per the tutorial I showed in the very first paragraph, I never got the "ASUS Android Bootloader Interface". This is what I think this "Other devices - Android" is found under Computer - Manager - Device Manager.
Most tutorials on the internet shows that the "ASUS Android Bootloader Interface" should be installed using these drivers found on ASUS website, the ASUS_Android_USB_drivers_for_Windows.
Now of course because I unplugged the phone, it will continously stay on the Android splashpage showing the loading circle infinitely.
As a last attempt I tried installing the "stock", not "raw" firmware (the one I wanted to install WW_13.16.5.49 but ASUS would not let you downgrade using the recovery "power+volume down" and using "Apply update from microSD card". It would give the
Code:
Warning- No file-contexts. This package is for "ww-phone" devices, this is a E:error in /side load/ package.zip (status 7) Installation aborted.
)
Well, after it brinked, I tried it again and this time it DID install WW_V13.16.5.49. Was succesfull. But after the ASUS splashscreen it's still stuck in the booting process.
I am very sorry if my post is convoluted but I tried explaining everything I did. Any way to un-brink it? I think maybe if I figure out how to properly install the ASUS Android Bootloader Interface, I can try again ASUS Flash tool and install the raw image and maybe that will fix it?
Please help. Any questions if my thread is too confusing, please let me know and I will answer it. I can't even turn off the phone. While it's stuck into the load splash screen, if I press the power button it just restarts, not turn off.
I still have access to fastboot (pwr + volume up) or recovery (pwr + volume down)
EDIT: Phone won't get recognized anymore in ASUS Flash Tools. Serial number won't show up to select
Factory reset and delete cache/dalvik through recovery and post back. It'll take 5-10min to boot up after that. You should always delete cache/dalvik after flashing.
wang1chung said:
Factory reset and delete cache/dalvik through recovery and post back. It'll take 5-10min to boot up after that. You should always delete cache/dalvik after flashing.
Click to expand...
Click to collapse
Thank you, this actually worked!!
Aaaand, it's actually on the version 13.16.5.49!!!! THIS IS EXACTLY WHAT I WANTED!
So apparently by brinking my latest nougat 7.0 update from ASUS via the ASUS Flash Tool trying to flash the .RAW 13.20.10.137, the standard recovery system (power+volume down) allowed me to install the 13.16.5.49 version. Then I assume remnants files didn't allow to properly boot, and your idea to wipe cache and factory reset fixed that!
What is so great is that I was scared that because the .RAW firmware was newer than the version I needed (13.16.5.49), I wouldn't have been able to install it. It was the same problem initially, when I tried to install 13.16.5.49 directly via recovery over the latest nougat 7.0 version from ASUS, but it was giving me
Code:
Warning- No file-contexts. This package is for "ww-phone" devices, this is a E:error in /side load/ package.zip (status 7) Installation aborted.
I think this error was due to the fact that ASUS won't allow older firmwares to be installed over newer ones, as per their webpage
https://www.asus.com/support/faq/1009748
Code:
You can not change the SKU from one to another, e.g., WW -> TW, and also can not downgrade your firmware, e.g., V2.20.40.13 -> V2.19.40.18
So in the end, what allowed the 13.16.5.49 stock firmware to be succesfully installed? The installer not detecting a proper firmware anymore because of the damaged update due to ASUS Flash Tools hanging because my computer won't install ASUS Android Bootloader Interface?
Glad you got it going :good:
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