anyone help me with stock rom wont boot and says use emergency recovery but i tried kies and the other software says phone unsupported
Hey have you ever figured out how to fix your phone....I had the same problem...I experimented with ODIN and I was able to successfully re-flash my Samsung Galaxy Express 3. There are some other options you need to check in ODIN to make it work...Please email me at [email protected]
I've just spent the last week messing around with a j120a. There 2 available firmwares on the net that you can download. J120AUCU1APC8 April 2016 and J120AUCU2APJ2 November 2016. There is a newer Jan 2017 but it's nowhere to be found on the net yet.
This is how I successfully installed the OEM Firmware.
1: Installed latest Samsung drivers
2: Downloaded & installed latest ODIN
3: Put phone in emergency mode (Vol down + Home + Power), then Vol up to select E-Mode
4: Run ODIN & plug your phone into the PC via a USB cable
5: Click the AP button and select your ROM(Firmware)
6: Click Start & it installs.
Possible errors & their solutions.
1: If your phone shuts off during the install process you need to swap USB ports. On a desktop use a rear USB port. DO NOT USE any extension cables or USB hubs or front USB ports. USB cable MUST be plugged directly into a rear USB port. Laptop, not sure. I never tried. Try swapping ports.
2: If while installing the firmware the install process errors then you are installing an older version of the firmware. It will not work. You must install the current version or newer. Start with J120AUCU1APC8, if it errors then try J120AUCU2APJ2. The J2 worked for me.
Note!!! J120AUCU2APJ2 comes in 2 versions the Oct. & Nov. versions. Every file I could find was the Oct. version. It is lacking a security update that the Nov. version has. Because of this the Samsung Galaxy App (Samsung App Store) will not work and you will most likely not be able to upgrade to the latest Jan. 2017 firmware via the OTA updates. It will just say you are already up to date. But your phone will function properly otherwise. Once someone uploads the Jan 2017 firmware the you can most likely use the above directions to install it.
Hope this helps.
Custom rom for j120a
Does anyone have a link to a working custom rom for this phone?
Root successful...........but at&t?
I was able to root with firmware version J120AUCS3AQE1 but because mine is an AT&T phone the bootloader is "locked and signed" meaning it's never going to unlock........? I have the latest version of firmware that came out in may 2017 and it will be available to you as soon as I can post an outside web address............ Every Recovery image that I flashed caused everything to fail and a big triangle that said AT&T detected software on your device that is not allowed on our device so I guess this one is never really your own........ but you can Root with Kingroot and supersume pro to get rid of bloatware and such but other than that no custom stuff on this one.
If Kingroot keeps freezing just restart phone and keep trying it took me a long while to obtain root.
Related
I bought a used phone which was previously locked to the UK Three network, and used a software utility to unlock it. It is now on T-Mobile. I also rooted the phone.
In doing the above, have I now lost the ability to receive OTA updates or updates via Kies?
If so, what's the best source of stock ROMs that I can use to keep up-to-date?
Fundamental element in order to be able to complete the update process of the Galaxy is to have a firmware entirely original. If you have on your phone a test version, root permissions enabled or a modified kernel installed (e.s , CF-Root) will be unable to update.
Kies in fact, in these cases will not be able to recognize the correct version of the software installed on the Galaxy s3.Finally, in order to be able to update without problems with the tool journal Samsung there is a requirement that many neglect themselves and to which do not lend themselves never attention.
Kies allows you to install updates only if the firmware currently installed on the device coincides with the one provided for your Product Code. For the person who has carried out a procedure of root In this case we can do nothing other than install the firmware manually through the tool Odin.
1.download ODIN :http://www.androidgalaxys.net/DWL/odin/
2.Extract the archive and place the executable of Odin inside C: \. Does not require installation, just run it. For a correct use of odin the suite Samsung Kies must not be active.
3.Now download the firmware you are interested in. If the downloaded file is compressed extract the contents until you will get files with the extension .tar or .tar.md5 (odin manages to only read these). Then copy these files in C: \.
4.Put your phone in Download Mode.
5.Start Odin and connect your phone to the USB port. (Start Odin before connecting your phone ). You will see that windows will load the drivers.
If the terminal is correctly recognized by Odin you will see in the first field ID: COM the name of the COM port on a yellow background (the com port number is indifferent).
If this is not the case or in case of problems try the following attempts in sequence: -
close Odin and then re-launch it
- remove the usb cable and riattaccatelo
- try changing USB port
- repeat the whole procedure from step 6 onwards
- try to connect it to another USB port
- try to reinstall the usb drivers of your Galaxy S 3
guide for user ODIN here ;http://forum.xda-developers.com/showthread.php?t=1671969
download firmware stock here ;http://www.sammobile.com/firmware/
Hello everyone, I have a problem with Bell sgs2 and I'm from Ukraine,so please sorry for my English.
A little bit of history: my sister from Canada closed her contract with bell and sent me the phone. As it turned out, device was still locked, so I tried to download the latest firmware and make unlock. Firstly I tried to unlock the phone running Android 2.3.3 with custom kernel by using galaxy_S unlock app, it was succesful, but I wanted latest firmware and tried to flash different unofficial ROMs. Every time I did it nothing happened because of different errors.
Problem starts here:
Then installed rooted official ROM Android ICS with Odin and noticed that in Kies there was an update for my device. Tried to install it, but it failed when the phone was in download mode (because of damaged usb cable maybe). In Kies they wrote that I should disconnect device and take out battery. I did it.
Now when I turn it on it stops on Samsung logo. I still can open download mode or stock recovery, which is great. But the problem is that Odin doesn't recognize the phone anymore while it is in download mode. Tried to uninstall,install drivers - nothing happened. The good thing is that I can see my phone with adb when it is in recovery, tried to install some zips from sideload or external sd card - nothing happened ( Error, status 7). So basically I can't install official md5 ROM from sammobile because of Odin and can't find normal zips for recovery.
Please help Will be grateful!!!
Hello i've been searching around 3 days and trying to find an solution for my GALAXY S6 DEVICE
1 month ago i have rooted my Galaxy s6 and after 2 weeks I tried to remove the root access from my device
i forgot that i had to flash ROM again and i just installed an app in Play Store for full unroot after i processed with the steps my phone restarted and stucked on Samsung Boot Logo .
I went to my PC and opened Odin again Downloaded Rom 6.0.1 but when i got it it said file is corrupted or something so i had to download Nougat 7.0 and i flashed Nougat 7.0 on my Galaxy s6 ,after the upgrade the phone seemed to work perfect in just one hour my phone just got restarted and im not able to charge it anymore on Power Supply
Only charges with PC USB , works with every charger on USB PC , but does not work on Power supply
I have tried Samsung Original Usb Cable but the same problem persists , but the other one problem is that when i connect the USB to my PC or another Pc "have tried many others " my Device is not being Detected i have tried in download mode but odin won't detect it .
So since i upgraded to Nougat 7.0 i got these problems and i have no idea how to go back there and flash 6.0.1 now
it does not allow me to detect my device to odin , it does not charge with power supply it charges only with USB AND VERY SLOWLY !
I contacted Samsung Support they were not able to help me , i went to Service Center they told me that the problem stands at the connector , but i dont think so this phone is brand new and i don't want to give them 200$ just for a connector because the LCD of galaxy is hard to be opened and closed again .
So all i need is some help from XDA DEVELOPERS because i have saw many posts and XDA found Solutions for everyone , but i need a solution for my Device Samsung Galaxy s6 {SM-G920F }
Please i need a solution assap thank you !
(A while searching to my phone i saw something at Open Source Licenses , /fake_packages and /root
and ROOTAP services
Are these a part of android system or something caused by nougat 7.0?)
Phone Information :
Device : Samsung Galaxy s6
Model Number : SM-G920F
Software Info :
Android Version : 7.0
Baseband Version : G920FXXU5EQAC
Kernel Version : 3.10.61-10531122
[email protected] #1
Wed Feb 1 10:39:50 KST 2017
Build Number : NRD90M.G920FXXU5EQAC
SE for android Status :
Enforcing
SEPF_SECMOBILE_7.0_0004
Security Software Version
MDF v3.0 Release 1
WLAN v1.0 Release 1
VPN v1.4 Release 8.1
ASKS v1.3_161228
Knox :
Knox 2.7.1
Standard SDK 5.7.1
Premium SDK 2.7.1
Customization SDK 2.7.1
Container 2.7.1
CEP 2.1.1
Enterprise Billing 1.2.0
OTP 2.6.0
SE for android 2.4.3
SSO 2.5.0
Shared Device 2.6.0
TIMA 3.3.015
VPN 2.3.0
No one is helping me right ?
charge your phone, flash back 6.0.1, go to recovery and wipe data and check if phone works on charger, in download mode you will see in your knox have been tripped, this could cause some issues on nougat firmware
AntonPres said:
charge your phone, flash back 6.0.1, go to recovery and wipe data and check if phone works on charger, in download mode you will see in your knox have been tripped, this could cause some issues on nougat firmware
Click to expand...
Click to collapse
Thank you for your Answer , but i have already charged my phone 100% , and wiped all cache and data , the phone works only on USB with PC , and i can't flash back to 6.0.1 because Odin does not detect my phone on Download Mode
Nougat caused this all , my phone only can be charged and not be recognized .
if you phone cannot be detected by odin it means you may have some hardware issues, even battery problem, my advice try to see if odin will detect it on other pc. If you would have some bootloader incompatibility your phone wouldn't power on.
AntonPres said:
if you phone cannot be detected by odin it means you may have some hardware issues, even battery problem, my advice try to see if odin will detect it on other pc. If you would have some bootloader incompatibility your phone wouldn't power on.
Click to expand...
Click to collapse
I already did that too , tried Odin in 5 or more other PC , using a samsung original CABLE
installed latest samsung usb drivers still nothing .
Here you go:
https://1drv.ms/u/s!AshkuG2cY1T0xPZArSsy6iO1e_UnPw
This is a zip file with all the tools and files you need and instructions on how to use them.
What it covers:
Restoring bricked device (as long as download mode still works)
Unlocking bootloader (firmware dependent)
Rooting (any firmware)
Installing a custom recovery (any firmware)
Installing a custom ROM (any firmware)
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
robles4242 said:
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
Click to expand...
Click to collapse
Did you read my guide? You can't flash TWRP unless you successfully unlocked your bootloader with Casual, otherwise you are limited to SafeStrap. Also you can't restore with Kies, you have to use Odin and the files I've included to restore.
yambag said:
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
Click to expand...
Click to collapse
Nice to see people still looking for something like this, so my guide wasn't for nothing!
I was geeked to see this!! but then i got "This item might not exist or is no longer available"
I take it back.. i let it sit on the "failed" page for like 2 min, and randomly it popped up with a download!
Well the auto bootloader didn't work, so now i'm at the root section. However i'm getting an error where ADB isn't detecting my phone. USB debug is on, and i'm definitely in media mode and not installer. The phone shows up in windows and looks good, but adb doesnt detect. I opened command prompt and ran adb /? and found adb devices -l, and it reports "list of devices" and theres nothing in the list. I can't imagine why it's not seeing it. I tried turning on and off debug mode, switching from camera mode to media, changing usb ports. still nothing comes up, but windows sees it fine. grrrr
*edit, well since we can't delete posts i'll leave this here, because i have to. But what i did was re-open the "no you verizon" and it showed DISCONNECTED also. I changed usb ports like 3 times, turned usb debug on and off, changed from installer mode, to camera, to media mode, restarted the phone and the computer multiple times.. and then it just all of a sudden was detected again. So i went with it and it seems to have worked.
-it took 3 times to actually work, you noted it may take multiples, and it sure did. I ran it through the command prompt so i could read the text, and it took 5 times longer and reported much more stuff when it actually worked.
-final edit: if you can't unlock your bootloader, you're still stuck with ditto or alliance from 2014, and lots of apps won't update on android that old. So if you thought this guide was some holy grail, it is not. But still useful if you need the assist, so thanks to the author.
Hi, total noob here, I just bought Verizon note 2 at a yard sale but there is a pin I don't know. When I went to do a factory reset it booted into TWRP, so I am assuming is rooted. Do I need to be able to get into the phone to use your tools? I know nothing about TWRP. I would like to install a newer Android version and unlock it so I can use TMobile. Thanks
Something wrong...
when i try to load this file from the packages folder i get an error message:
"md5 error! Binary is invalid"
none of the other three works for me. they all come back ailed.
any suggestions?
awesome! thanks for posting this, just found my old note 2 and want to get it up and running again for the kids.
Kudos!
Used this to get my Note 2 up and going again temporarily until the Pixel 4a release...
NOTE: I had strange issues with Odin on my modern X570 board (USB 3.2 Gen 2) where I did not receive any errors, yet the process would randomly seem to time out. Sometimes I'd get stuck at flashing boot.img, sometimes it would hang up at the start, once I got to flashing system.img and it seemed to hang....
Used an older PC circa 2013, no issues! Not the first time I've had issues with this newer motherboard and older USB flashing interfaces; had the same issue on my Note 8 (RIP) as well.
excited to try this.
I'm on some rooted 4.4.2 stock-looking rom. Recovery doesn't look custom.
Hoping to be able to install a working Oreo or Pie ROM
great post, bought a couple of these for almost nothing and am having fun playing with them. sadly they are both 4.4.2 but its great fun anyway.
SilentNightx said:
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Click to expand...
Click to collapse
Thank you for sharing. Always difficult to find those tools after a few years!!!
Hello, I am actually brand new to xda-developers, I have did something stupid I guess... So, I had stock firmware and I already have it rooted and installed twrp. At this point, I have tried many many things and it is telling me No OS now with TWRP (I boot-looped it by uninstalling bixby :v) and wiped the data, formatted it, and all of that and more. I keep getting errors with everything, the most common ones I seen is ERROR: 1 and ERROR: 7, I know this is useless information but I had one about updating dynamic partitions with trying to install Lineage OS. I tried installing GApps thinking that would fix it, it tells me that it is made for ROM 11.0.x and told me to download the one for my ROM: 11 (SDK 29). I have no clue what that means or anything, but to me, it seems I have pretty much screwed up my phone somehow all from uninstalling Bixby.
Odin will not work, I have installed the right Samsung drivers (my windows PC is ****ed too, majorly somehow. Might have something to do with it).
ADB will not recognize my device, in twrp recovery or download mode. ADB Sideload function of twrp does not load (sits there forever).
I really, really need help. Please.
TL;DR
Uninstalled Bixby with Lucky Patcher and System App Remover, phone decided to reboot hours later and got stuck in boot-loop.
I have not been able to do anything flashing wise. ADB does not work, so I am stuck transferring files to/from my PC with a USB stick w/ OTG Adapter. It seems to work ok, as I was successful in flashing TWRP recovery (updated it from somewhere).
I need my phone, and it does not function in its current state and I am clueless on what to do (I get all sorts of errors that seem unfixable).
I last had Android 11 (stock firmware) on my phone before it was boot-looped.
Exact Phone: [Excuse me if I am not allowed to post links, but it is just to amazon of the phone I bought if it helps anyone] https://www.amazon.com/dp/B082YF7WY5
TWRP Version: 3.5.0_10-A11_1b1
Samsung Galaxy A51 A515F 128GB DUOS GSM UnlockedUS Compatible LTEExynos 9611 Chipset
Fastest way to contact me: Cyberhound#5672 on Discord.
I will try to respond as fast as I can, but I am without a phone :/
NOTE: I have resolved this issue.
I flashed stock firmware using OTG (just the .img's) and then reinstalled Samsung USB Drivers, restarted my computer, connected an old phone that worked so I could verify if the USB Driver was working (and so ADB as well).
I reconnected in TWRP Recovery, and it worked and showed up on Odin.
I was able to flash stock firmware successfully.