Samsung Galaxy A7 reverting to stock ROM - Samsung Galaxy A3, A5, A7 (2017) Questions & Answe

I need some help reverting to the stock Rom since i changed to lineage because I thought it'd solve some battery issues but it didnt.
I tried to flash the stock Rom from Odin but i cant seem to do it properly, I either downloaded the incorrect rom (unlikely) or I'm not understanding how you flash a stock rom (very likely)
any help would be greatly appreciated

val_lyra said:
I need some help reverting to the stock Rom since i changed to lineage because I thought it'd solve some battery issues but it didnt.
I tried to flash the stock Rom from Odin but i cant seem to do it properly, I either downloaded the incorrect rom (unlikely) or I'm not understanding how you flash a stock rom (very likely)
any help would be greatly appreciated
Click to expand...
Click to collapse
Use odin patched ...
Since simple odin is no longer support latest devices so download patched odin from xda it will work

devil meru said:
Use odin patched ...
Since simple odin is no longer support latest devices so download patched odin from xda it will work
Click to expand...
Click to collapse
It worked! thank you very much!

Need Stock Rom
val_lyra said:
I need some help reverting to the stock Rom since i changed to lineage because I thought it'd solve some battery issues but it didnt.
I tried to flash the stock Rom from Odin but i cant seem to do it properly, I either downloaded the incorrect rom (unlikely) or I'm not understanding how you flash a stock rom (very likely)
any help would be greatly appreciated
Click to expand...
Click to collapse
Can you please give me link to stock rom TIA

Related

[Q] update of stock rom led to recovery failure

Hi,
I just got my Galaxy S III and decided to root it. I had done it before. I made a mistake and it wouldn't reboot, so, I had to put the stock rom on the device again. I found the stock rom, which was a 4.0.4 version and flashed it with no problem. But, then, the automatic update installed the 4.1.1 version. Here is when the problem starts: after installation, when I try to go into the recovery mode to clear the cache, the android is dead with a read triangle above it. I don't know what to do since I want to flash a custom rom.
Oh, a small detail that might be important. The stock rom is flashed using ODIN, but the reboot process is so lengthy, I have to remove the battery and then clear the cache before it fully reboots. At this stage (still 4.0.4) there is no problem with recovery mode and everything is fine. It is only after the update to 4.1.1 that the problem starts.
Your helps are much appreciated.:angel:
rezaasl2000 said:
Hi,
I just got my Galaxy S III and decided to root it. I had done it before. I made a mistake and it wouldn't reboot, so, I had to put the stock rom on the device again. I found the stock rom, which was a 4.0.4 version and flashed it with no problem. But, then, the automatic update installed the 4.1.1 version. Here is when the problem starts: after installation, when I try to go into the recovery mode to clear the cache, the android is dead with a read triangle above it. I don't know what to do since I want to flash a custom rom.
Oh, a small detail that might be important. The stock rom is flashed using ODIN, but the reboot process is so lengthy, I have to remove the battery and then clear the cache before it fully reboots. At this stage (still 4.0.4) there is no problem with recovery mode and everything is fine. It is only after the update to 4.1.1 that the problem starts.
Your helps are much appreciated.:angel:
Click to expand...
Click to collapse
So you can esily flash 4.0.4 with no hiccup but then you get the update (kies I assume) and it fails ?
Do you want to be rooted ?
if not just flash the stock 4.1.1 from Sammobile in Odin and update that way to avoid that Kies garbage
hednik said:
So you can esily flash 4.0.4 with no hiccup but then you get the update (kies I assume) and it fails ?
Do you want to be rooted ?
if not just flash the stock 4.1.1 from Sammobile in Odin and update that way to avoid that Kies garbage
Click to expand...
Click to collapse
Thanks for the reply. I do want to be rooted. Mine is an i747. Can you attach the link so I don't download the wrong one?
rezaasl2000 said:
Thanks for the reply. I do want to be rooted. Mine is an i747. Can you attach the link so I don't download the wrong one?
Click to expand...
Click to collapse
Find your carrier and flash one of these in Odin as they are pre-rooted.
http://forum.xda-developers.com/showthread.php?t=1739426
hednik said:
Find your carrier and flash one of these in Odin as they are pre-rooted.
http://forum.xda-developers.com/showthread.php?t=1739426
Click to expand...
Click to collapse
Thank you so much for the reply. After purchasing my g3 from AT&T, I used the same link you just sent me to flash the device. But it didn't work even though I changed the USB port. It installs SuperSU, but the recovery fails. I will try it one more time before and report back to you.
thanks again.
rezaasl2000 said:
Thank you so much for the reply. After purchasing my g3 from AT&T, I used the same link you just sent me to flash the device. But it didn't work even though I changed the USB port. It installs SuperSU, but the recovery fails. I will try it one more time before and report back to you.
thanks again.
Click to expand...
Click to collapse
It failed again (dead android with a red triangle above it). I have checked the ODIN version, whether the md5 file was downloaded correctly. I'm very frustrated.
rezaasl2000 said:
It failed again (dead android with a red triangle above it). I have checked the ODIN version, whether the md5 file was downloaded correctly. I'm very frustrated.
Click to expand...
Click to collapse
So you can't flash anything 4.1.1 or 4.1.2 ? That's odd that only 4.0.4 works. Does it fail with Kies too ?
What about just rooting using CF-auto root or casual and then flashing a rom ?
hednik said:
So you can't flash anything 4.1.1 or 4.1.2 ? That's odd that only 4.0.4 works. Does it fail with Kies too ?
What about just rooting using CF-auto root or casual and then flashing a rom ?
Click to expand...
Click to collapse
Okay, so, this method didn't work either. I went back to the link you sent me with the pre-rooted version and flashed it. Now, it has the same problem (dead android with red triangle), but RootChecker says that I'm rooted. I don't know what difference that makes.
Any thoughts?
rezaasl2000 said:
Okay, so, this method didn't work either. I went back to the link you sent me with the pre-rooted version and flashed it. Now, it has the same problem (dead android with red triangle), but RootChecker says that I'm rooted. I don't know what difference that makes.
Any thoughts?
Click to expand...
Click to collapse
So cf auto root worked but you can't flash ? You need to install a recovery. Can you flash a custom recovery in Odin or mobile Odin ?
Sent from my SGH-I747 using xda premium
hednik said:
So cf auto root worked but you can't flash ? You need to install a recovery. Can you flash a custom recovery in Odin or mobile Odin ?
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
So, I finally figured it out. I used the samsung galaxy s3 toolkit to install the stock firmware and then I updated it on the phone. Next, I went back to the toolkit and installed the most recent version of CWM on it and everything just worked beautifully. I have LiquidSmooth installed and it works just great.
thank you for the help hendik.
:good:

[Q] Cant flash any roms with odin,all data deleted including rom,please help...

Was running stock knox free 4.3 rom and was trying to flash another rom ,because 4.3 stock was giving me horible battery life ,but by accident everything got deleted and didnt have no backup Odin says failed(auth).I can go to download mode and recovery mode also.
also I am running the tmobile s3
Firmware us flased in Odin.
Roms in recovery.
If you've fully updated to 4.3 fw, you can no longer odin flash any earlier builds.
So I can only flash same 4.3 now ? No older roms?
vladod said:
So I can only flash same 4.3 now ? No older roms?
Click to expand...
Click to collapse
You got it. Do not try older Stock roms. There lies a Brick!
Thank you both.That sucks since the battery life is very bad.Other than that everything else works great.Hope someone will come up with a solution to flash the older roms again.
For improving Battery, follow the suggestions in this thread and do this mod.

[Q] Samsung Galaxy S3 AT&T Possible Soft Brick?

So, i decide to root my s3 because i wanted to do some cool stuff. I got odin, got the tar file and tried flashing it. For some reason it didn't work :crying: On odin it gave me a fail. I was in download mode too. So, when i turn on my s3 it is in odin mode but it says "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." i did this in kies and when it was at like 99% it gives me an error. :crying:
so i tried flashing again in odin still fail, but i get on my s3 SV REV CHECK FAIL: Fused 2 > Binary 0. I have no clue what that means, So, i just want my phone to get working again i dont care about rooting anymore. JUST HELP ME FIX IT!!!!:crying:
BTW: I di root my Kindle Fire a while back so i thought I would have experience with this (i kind of do) but i guess I thought wrong.
Was your phone running a stock 4.3 AT&T ROM? What method did you use to try and root the phone?
audit13 said:
Was your phone running a stock 4.3 AT&T ROM? What method did you use to try and root the phone?
Click to expand...
Click to collapse
i think so and i tired using odin and i put the phone in download mode so i could flash the .tar file
Resistance225 said:
i think so and i tired using odin and i put the phone in download mode so i could flash the .tar file
Click to expand...
Click to collapse
Since your phone was running a stock 4.3 ROM, you can't use Odin to install a stock AT&T 4.3 ROM because it doesn't exist. There are leaked ROMs around that you could try flashing.
Alternatively, you could install a custom recovery and install a custom 4.4.2 ROM.
audit13 said:
Since your phone was running a stock 4.3 ROM, you can't use Odin to install a stock AT&T 4.3 ROM because it doesn't exist. There are leaked ROMs around that you could try flashing.
Alternatively, you could install a custom recovery and install a custom 4.4.2 ROM.
Click to expand...
Click to collapse
I will try to do this! Thanks for helping me though, i will keep you updated. :fingers-crossed:
audit13 said:
Since your phone was running a stock 4.3 ROM, you can't use Odin to install a stock AT&T 4.3 ROM because it doesn't exist. There are leaked ROMs around that you could try flashing.
Alternatively, you could install a custom recovery and install a custom 4.4.2 ROM.
Click to expand...
Click to collapse
I installed a recovery and guess what, it started working again! All my data was still there too! Thanks i really appreciate you taking the time to help me! I also was able to succsessfully root it by using the CF auto root .tar file. Once again, thanks a ton!
Resistance225 said:
I installed a recovery and guess what, it started working again! All my data was still there too! Thanks i really appreciate you taking the time to help me! I also was able to succsessfully root it by using the CF auto root .tar file. Once again, thanks a ton!
Click to expand...
Click to collapse
Glad you got it working. We're all here to help.

[Q] Note 2 bricked

Today i flashed CM 11 with CWM and after rebooting the baseband and IMEI were gone. I tried to flash the baseband but nothing happened. I then tried to flash the stock rom touchwiz through ODIN and it failed. Now the phone reboots asking to connect to KIES and do a recovery which i can't perform.
Any clues about?
Thank you in advance,
Davide
you have back up of your phone..?
can you boot into recovery..?
which stock rom you tried to flash , 4.3..? 4.4
http://forum.xda-developers.com/showthread.php?t=2758855 See this might help you
caravaggio971 said:
Today i flashed CM 11 with CWM and after rebooting the baseband and IMEI were gone. I tried to flash the baseband but nothing happened. I then tried to flash the stock rom touchwiz through ODIN and it failed. Now the phone reboots asking to connect to KIES and do a recovery which i can't perform.
Any clues about?
Thank you in advance,
Davide
Click to expand...
Click to collapse
tnt4ever said:
you have back up of your phone..?
can you boot into recovery..?
which stock rom you tried to flash , 4.3..? 4.4
http://forum.xda-developers.com/showthread.php?t=2758855 See this might help you
Click to expand...
Click to collapse
Thanks for the prompt reply. The Rom I flashed is the 4.4.2 snapshot.
In the meantime i flashed this pit file from this link
http://forum.xda-developers.com/showthread.php?t=2137008
and now the CYM is back and working but still no baseband.
Is there any way i can reinstall the stock rom ? is the partition a problem?
I dont have a backup of the EFS folder (I made it once but i cant find it)
EDIT: CWM is installed and working
is your IMEI Same..?
i assume there are several reasons, it can be a simple fix by installing a stock 4.4 KK which will eliminate the problem you are facing, iin past week, i done alot of experiences on my bricked note 2, specially the failed PIT flashed, i tried couple of them but at the end the only thing turned the phone in right direction was stock KITKAT
you can find that in the the post i posted earlier.
i am 100% sure you will get your phone back to life.
also remember to when you are done flashing go to stock recovery and wipe data and cache. It is needed after re-partiton to form the partitions correctly
edit: best keep a nand of your current rom as well
4.4.2
https://mega.co.nz/#!2QRmCbyb!YkWs927BfvYxqL-vJiQHXkshqG3UtqHm4XIDbgLsEK0
best of luck
caravaggio971 said:
Thanks for the prompt reply. The Rom I flashed is the 4.4.2 snapshot.
In the meantime i flashed this pit file from this link
http://forum.xda-developers.com/showthread.php?t=2137008
and now the CYM is back and working but still no baseband.
Is there any way i can reinstall the stock rom ? is the partition a problem?
I dont have a backup of the EFS folder (I made it once but i cant find it)
EDIT: CWM is installed and working
Click to expand...
Click to collapse
tnt4ever said:
is your IMEI Same..?
i assume there are several reasons, it can be a simple fix by installing a stock 4.4 KK which will eliminate the problem you are facing, iin past week, i done alot of experiences on my bricked note 2, specially the failed PIT flashed, i tried couple of them but at the end the only thing turned the phone in right direction was stock KITKAT
you can find that in the the post i posted earlier.
i am 100% sure you will get your phone back to life.
also remember to when you are done flashing go to stock recovery and wipe data and cache. It is needed after re-partiton to form the partitions correctly
edit: best keep a nand of your current rom as well
4.4.2
https://mega.co.nz/#!2QRmCbyb!YkWs927BfvYxqL-vJiQHXkshqG3UtqHm4XIDbgLsEK0
best of luck
Click to expand...
Click to collapse
Exactly. Flashing the official stock rom based on kitkat 4.4.2 (which has been released few days ago I believe) solved the problem. I'll try to flash CM tomorrow (tonight get.cm is not reachable and can't download the android app).
Thank you!
Hello
very happy to see your problem is fixed
enjoy your galaxy note 2
this community is very helpful for every one my friend
caravaggio971 said:
Exactly. Flashing the official stock rom based on kitkat 4.4.2 (which has been released few days ago I believe) solved the problem. I'll try to flash CM tomorrow (tonight get.cm is not reachable and can't download the android app).
Thank you!
Click to expand...
Click to collapse
Just wanted to ask you something. I installed the Nordic version of the latest Android update which is at the moment the only one available and I have the impression that the voice quality is not that good. I was wondering if this may depend on the baseband version installed on this one. I'm from Italy and kitkat 4.4 is still not available in my country. Flashing a different baseband may change the situation? If so, Is there a baseband more compatible with this touchwiz version and the Italian telco providers?
Thank you again,
Davide
Sent from my GT-N7105 using XDA Free mobile app

I lost my stock firmware

I have lost my stock firmware after flashing a custom rom. I went and download many stock firmware for my phone, flashed with Odin ,get error massage binary 5 and etc. I downloaded the binary u5 stock firmware but same happens again ,I wasn't able to back on stock firmware. Pls help me
Zodiacx said:
I have lost my stock firmware after flashing a custom rom. I went and download many stock firmware for my phone, flashed with Odin ,get error massage binary 5 and etc. I downloaded the binary u5 stock firmware but same happens again ,I wasn't able to back on stock firmware. Pls help me
Click to expand...
Click to collapse
Can you sent the entire error message, and which custom rom you flashed before.
We need more information to help you.
purpleish said:
Can you sent the entire error message, and which custom rom you flashed before.
We need more information to help you.
Click to expand...
Click to collapse
Thanks
But i successfully return to my stock firmware
I relock the bootloader but still i am not able to use samsung pass
It showing your device rooted
Good to heard you flashed stock firmware. But there is NO way to use any samsung-exclusive features.
As unlocking bootloader tripped Samsung knox, the protection layer that Samsung uses. Which Samsung pass is an app requires Samsung knox.
For more: https://www.google.com/search?q=samsung+knox+explained
but I search though the forum and found this, although it from 2017 and things might change since then. You may want to try this with a rooted phone.
https://forum.xda-developers.com/t/samsung-pass-on-knox-tripped-devices.3687977/
Zodiacx said:
I relock the bootloader but still i am not able to use samsung pass
It showing your device rooted
Click to expand...
Click to collapse
found another piece of software that might help you (requires magisk)
https://forum.xda-developers.com/t/module-smali-patcher-7-4.3680053/
Edit, might not work for newer device

Categories

Resources