Rooted Stock OC4 ROM stuck on Bootloop... Please, help! :( - AT&T Samsung Galaxy S 5

Hi there.
I managed to root my G900A (Lollipop 5.0 - OC4) using the Kingroot method.
At first, it was all fun and games... I added VIPER4Android, Dolby ATMOS, and deleted all of my phone's bloatware.
It was what I've always wanted since I first found out I could (and succeeded in rooting) my phone.
It got all out of hand once I tried to install a mod (through FlashFire) that (apparently) wasn't compatible with my phone (the "Xperience real Audio [SoundSignature]" mod, to be precise).
I tried flashing back the stock OC4 ROM using Odin3 v3.10 (which flashed successfully... *cough* -Ahem- the second time. ), but my phone's still stuck on the Galaxy S5 splash screen. :crying:
I did find it odd that the splash screen still said "Custom", despite having flashed the stock ROM.
So, what I did was wipe the cache partition... That didn't work.
Next, I did a factory reset along with wiping the cache partition... and still, nothing. :crying:
I thought that (maybe), since the phone splash screen still says "Custom" (I also checked the System Status on Download Mode; which also says "Custom", BTW), I'd have to do an ODIN flash of a pre-rooted OC4 Stock ROM.
Please, if anyone has any knowledge to what I should do in my situation, could you help me out?
Not only would I appreciate it, but your help could also benefit anyone out there with the same (or similar) situation as mine.
Thanks in advance
UPDATE:
I looked throughout the forums to see if I could find the pre-rooted stock ROM for OC4, but couldn't find it... :crying: :crying:
If anyone, by any chance knows of a working link to the file, I'd appreciate it if anyone could post it for me.

Related

[Q] My phone is stuck in a bootloader loop

I need some help here, and I need to stop bothering the guys in the ROM forum about it so I'm asking here instead.
It's a t-mobile note 4. I was running Dynamic Kat on it and it was suggested I update the modem and bootloader with a partial flash file. Now my phone is stuck in a bootloop.
I CAN get into both download mode and TWRP, however, so it seems like this should be fixable. I'd be happy with even going back to fully stock and rerooting it.
I found this thread: http://forum.xda-developers.com/not...to-downgrade-cod6-to-nk4-upgrade-nk4-t3095585 which seems to about flashing back to stock NK4 or cod6. I know those are bootloaders, but I don't really understand what they mean beyond that.
Or can I just flash to the new stock lollipop t-mobile put out this week? If so, how? If anyone has the time to help me with this, I would really appreciate it.
Edit: I found instructions on sammobile.com. Going to try them. *fixed
Caelrie said:
I need some help here, and I need to stop bothering the guys in the ROM forum about it so I'm asking here instead.
It's a t-mobile note 4. I was running Dynamic Kat on it and it was suggested I update the modem and bootloader with a partial flash file. Now my phone is stuck in a bootloop.
I CAN get into both download mode and TWRP, however, so it seems like this should be fixable. I'd be happy with even going back to fully stock and rerooting it.
I found this thread: http://forum.xda-developers.com/not...to-downgrade-cod6-to-nk4-upgrade-nk4-t3095585 which seems to about flashing back to stock NK4 or cod6. I know those are bootloaders, but I don't really understand what they mean beyond that.
Or can I just flash to the new stock lollipop t-mobile put out this week? If so, how? If anyone has the time to help me with this, I would really appreciate it.
Edit: I found instructions on sammobile.com. Going to try them.
Click to expand...
Click to collapse
Easy fix. ODIN flash the stock COD6 software. Then start over again with cf auto root. There is a thread that had all of the files you need in one zip.
Sent from my SM-N910T using XDA Free mobile app
Yayyy I think it worked! Stock Lollipop is booting up. It's in the Optimizing apps phase.
Caelrie said:
Yayyy I think it worked! Stock Lollipop is booting up. It's in the Optimizing apps phase.
Click to expand...
Click to collapse
Are you the same one who renamed the tar.md5 file to tar? If so, when you ask for help you really should mention all the steps you took to get there. Where it went wrong, etc.
When in doubt, Odin flash full firmware to get back to stock. There are other steps you could have taken as well but Odin is almost always a surefire bet.
(Also remember to hit the thanks button for those who have helped you get things sorted, like that fella above and the people who helped you in the rom thread- not me of course because I didn't do anything but for those who did I'm sure they would appreciate it)
absinthesummer said:
Are you the same one who renamed the tar.md5 file to tar? If so, when you ask for help you really should mention all the steps you took to get there. Where it went wrong, etc.
When in doubt, Odin flash full firmware to get back to stock. There are other steps you could have taken as well but Odin is almost always a surefire bet.
(Also remember to hit the thanks button for those who have helped you get things sorted, like that fella above and the people who helped you in the rom thread- not me of course because I didn't do anything but for those who did I'm sure they would appreciate it)
Click to expand...
Click to collapse
Yah, that was me. I came over here to ask for help instead because I shouldn't be bothering you guys in the ROM thread. I was making progress though. By the time I made this thread, I'd figured out that if I could get into TWRP or download mode, I could odin my way out of it. Just needed some help on that doing that, but then I figured that out too thanks to sammobile
Caelrie said:
Yah, that was me. I came over here to ask for help instead because I shouldn't be bothering you guys in the ROM thread. I was making progress though. By the time I made this thread, I'd figured out that if I could get into TWRP or download mode, I could odin my way out of it. Just needed some help on that doing that, but then I figured that out too thanks to sammobile
Click to expand...
Click to collapse
Cool, glad you got it sorted. Yeah as long as you can access download mode you're golden, and a bonus if you can get into recovery as well.
Excellent job actually searching and reading and fixing your problem, far too many people want answers just handed to them, so kudos to you for that.
Just for the future if you need help, try to remember and list all steps you took (even if you don't know where you went wrong) in excruciating detail because it helps us troubleshoot and figure out what the problem is. Without certain pertinent info it could take a lot longer to solve it.
Overall good job, glad you're up & running.
Go to rapture download the rom and load it to sd card. Then follow directions exactly and u will be ok. No loading anything. Fresh start
BAD ASS NOTE 4
I am in the same boat with the boot loop. I flashed the partial firmware file as well and I did not rename it and the flash went fine. After that it boot to the screen that says powered by Android then it reboots over and over. Currently downloading the stock cod so I can odin that.
ElAguila said:
I am in the same boat with the boot loop. I flashed the partial firmware file as well and I did not rename it and the flash went fine. After that it boot to the screen that says powered by Android then it reboots over and over. Currently downloading the stock cod so I can odin that.
Click to expand...
Click to collapse
Technically you shouldn't be flashing just the partial firmware. It sets up a base so that you can flash a lollipop rom in recovery without issues. I'm not sure why someone is recommending just flashing the partial firmware only. I guess they figured it wouldn't cause issues.
Anyway, here is how the partial firmware should be used:
Flash partial firmware in Odin
Flash flashable stock lollipop in recovery.
Set up rom, make a backup.
From here you can restore your old kitkat backups without the problems that some are seeing (those who Odin the full firmware are having problems restoring kitkat backups/flashing kitkat roms without Odining ank4 first). The partial firmware prevents that but it's designed to be flashed right before flashing a lollipop rom.
I hope that helps some of you who are having issues.

[Q] Softbrick due to attempted downgrade from 5.0 to 4.4.2

Hey guys,
Basically today I was getting tired of the android 5.0 install I had running on my S5 so I figured I would reinstall 4.4.2 via Odin - a process which I had done a few times previously. I didn't really think about the fact that I was going from one version of the OS to another, and whether this would create an issue, but it has. My phone now loads up the samsung logo, but doesn't finish the animation and then freezes. A few seconds later, the screen will go black and the LED on the top of the phone will just glow blue. The phone will sit like this forever, and never boot. I have tried re-installing the AP in Odin a few times, all of which show pass in Odin, but to no avail. I have also wiped all data and the cache within the recovery. I don't know where to go from here. Any suggestions?
Thanks
Philpro said:
Hey guys,
Basically today I was getting tired of the android 5.0 install I had running on my S5 so I figured I would reinstall 4.4.2 via Odin - a process which I had done a few times previously. I didn't really think about the fact that I was going from one version of the OS to another, and whether this would create an issue, but it has. My phone now loads up the samsung logo, but doesn't finish the animation and then freezes. A few seconds later, the screen will go black and the LED on the top of the phone will just glow blue. The phone will sit like this forever, and never boot. I have tried re-installing the AP in Odin a few times, all of which show pass in Odin, but to no avail. I have also wiped all data and the cache within the recovery. I don't know where to go from here. Any suggestions?
Thanks
Click to expand...
Click to collapse
I think you need to find the lollipop kernel. But I'm not 100 percent sure.
try opening kies with your phone connected and look for a menu option to the effect of restore/repair device
sent from my galaxy a5 (SM-G900AZ) on Cricket
I'm not sure if this helps you or not, but I did the same thing, trying to downgrade. I did not take the OTA update when I went from KitKat to Lollipop, instead I flashed one of the Lollipop ROMs, so be wary of that. If you took the OTA update, I don't know if this will work for you.
Anyways, I spent the better half of a day trying different kernels and stock ROMs using the factory recovery etc and nothing was working, each time I would either end up frozen at the Samsung screen or the initial splash screen when you power the phone on. I found this thread here:
http://forum.xda-developers.com/att...w-to-update-to-g900aoca-5-0-keeproot-t3076803
Under "notes", step 4 I downloaded the file G900A_Downgrade_to_NCE.tar and flashed through Odin. This is the file that got me out of this hole, so maybe it will work for you as well. After flashing, it rebooted and went past the Samsung screen to the initial first time setup screen. Looks like this put me back at stock UNrooted 4.4.2.
Good luck, hope this helps someone else out.
Wait, are you saying that you updated your phone using the stock recovery? Were you rooted? @mangomango
Its_Tim said:
Wait, are you saying that you updated your phone using the stock recovery? Were you rooted? @mangomango
Click to expand...
Click to collapse
I flashed through Odin, but yes I was rooted when I went from KK to LP.
I purchased an AT&T sm-g900a that was supposed to come with 4.4.2 according to info on site and sticker on the box indicated it originally had 4.4.2 on it too. I have no way of knowing if someone flashed it with the whole 5.0 file or just updated it. It was sold to me as a new and unlocked phone, and I got a good deal. The phone looks new with an AT&T screen cover attached, packaging, etc. and contents were still in sealed packaging. Will this work? https://www.androidpit.com/how-to-downgrade-galaxy-s5-from-lollipop-to-kitkat ? Is this the same file as the downgrade one referred to? Sammobile only has the 4.4.2 file. There is a significant cost difference in this model and the t-mobile version. Otherwise, I would just return it. I do not like the newer software at all.
I had the same thing happen today with my g870a. I tried 5.0, and 4.4.2 kernels, 4.4.2 firmware (which I knew wasn't corrupt) in Odin but nothing worked. The whole reason was to go redo my Alliance Rom and use FF beside Safestrap (the LP kernal would get rid of the SS). What I ended up doing was going into stock recovery and went to where it says "install update from ext SD". Then I went into my FF backup and found twrp.zip and selected it. It's did some things, said some stuff failed, then booted up enough to get me to FF to get it straight. One problem...my g870a thinks it's a 900, wtf?
Sent from my SAMSUNG-SM-G900A using Tapatalk

[Q] Unknown baseband/imei null after twrp install, ideas?

Today I made a first step towards custom ROM by installing the latest TWRP with Odin and taking a backup of all partitions. Rebooted and unfortunately now I have IMEI null and baseband null (it was originally I9305XXUFOA1 I believe)
Nothing else has been touched, I am still using stock ROM, and reset to factory default did not solve it...
I still have the IMEI number and a backup of the EFS partition. But when I restored this partition with TWRP, I still have No Signal.
I searched the forums and only thing closest is a post about the S4: http://forum.xda-developers.com/showthread.php?t=2370699
Is there any suggestion on what I can try to recover this problem?
If I type *#1234#, I get
AP I9305XXUFOB2
CSC I9305PHNFOB2
But no CP?
Now I did a total restore of the backup made with TWRP, but still "unknown baseband"
In case it helps others, here is what I learned
When flashing TWRP 2.8.7.0 on my 9305 with Odin, my modem becomes unusable every time.
It can be easily restored if you have the modem firmware, so that solved it. But it seems TWRP is very unreliable until I downgraded to an older version of it, 2.7.0.0. Now everything is working, although it can be tricky to get into the recovery mode (holding buttons for up to 30 seconds). I suppose this is normal behaviour...
Help please
cpct said:
In case it helps others, here is what I learned
When flashing TWRP 2.8.7.0 on my 9305 with Odin, my modem becomes unusable every time.
It can be easily restored if you have the modem firmware, so that solved it. But it seems TWRP is very unreliable until I downgraded to an older version of it, 2.7.0.0. Now everything is working, although it can be tricky to get into the recovery mode (holding buttons for up to 30 seconds). I suppose this is normal behaviour...
Click to expand...
Click to collapse
Hi, I'm going nuts reading for the past 5 hours all the info about this issue and the multiple solutions i have tried with no success, i just stumbled in your post which describes exactly my problem, after flashing twrp bam!!
I have no backups, i bought this phone yesterday, unrooted this morning , spent some hours customizing stuff, got to the point to install a recovery to do a nand backup as the phone had all the apps and settings i wanted and this just happened, i am now going to do a complete stock flash, will it repair my modem? If not can you please provide me with a link to the modem firmware? Is it country associated, will i need a specific for my country/operator?
Thanks,
Bruno
bpi_pt said:
Hi, I'm going nuts reading for the past 5 hours all the info about this issue and the multiple solutions i have tried with no success, i just stumbled in your post which describes exactly my problem, after flashing twrp bam!!
I have no backups, i bought this phone yesterday, unrooted this morning , spent some hours customizing stuff, got to the point to install a recovery to do a nand backup as the phone had all the apps and settings i wanted and this just happened, i am now going to do a complete stock flash, will it repair my modem? If not can you please provide me with a link to the modem firmware? Is it country associated, will i need a specific for my country/operator?
Thanks,
Bruno
Click to expand...
Click to collapse
Hi Bruno,
You should try to (re)flash only the modem with Odin. It's not so difficult, just take your time to familiarize with the steps.
To get a modem.bin, either you extract it yourself from a stock rom zip (see http://www.sammobile.com/firmwares/) or get one from the topics at xda (for the 9305 I got XXALK2 from http://forum.xda-developers.com/gal...05/modems-i9305-cwm-flashable-modems-t2010116).
I suppose you have no access to TWRP right now? If so, reflash it with Odin too. I recommend version 2.7.0; it works for me very well. Then immediately take backup of everything (EFS etc) and transfer it to your PC
Let us know how it goes,
SOLVED: Null IMEI and baseband
Hi all,
My problem is solved, after flashing the latest stock ROM for my model (I9300) I got my IMEI back and everything back to normal, as told I could have just the modem.bin flashed but I went for the full re-image.
Then i unrooted using cf-autoroot and flashed twrp version 2.8.6.0 instead of 2.8.7.0, rebooted and everything ok. I already performed a full nand backup and learned various lessons from this. I think guys at TWRP should know that their latest version for the galaxy s3 is causing this problem, i believe most people will send their phones for repair because there are so many possible causes for this problem and so many xdifferent possible solutions that most people will quit solving the problem and will try to return the phone for repair.
Thanks for your reply and for the help. I will send an email to twrp linking to this thread.
Melhores cumprimentos ( portuguese for Best regards)

Stuck on 5.1.1 badly!

Hey guys,
So I wanted to upgrade to 5.1.1 and I saw a couple of ROMs for 5.1.1 that I was interested in flashing. So I chose this one > http://forum.xda-developers.com/z3-compact/development/rom-one-solution-debloated-xposed-t3164221
When I wiped, and then went to install it gave me an error, md5 error or something, but it seems it had already wiped my stuff.
So my phone was bricked and I could not get it past the initial Sony Xperia screen AT ALL. The only solution I found was to use "Emma" and recover it by resetting to factory. In doing so however, Emma installed a Stock 5.1.1, which booted no problems at all. Fantastic. Now I am on 5.1.1, unrooted, and inability to install or boot into a recovery to flash my backup.
Here's my problem, every single time I try to downgrade my Firmware back to Lollipop 5.0.2, or KitKat even, it either freezes at random places, like this > http://puu.sh/jRHEj/f3da0dfcfa.png
OR it finishes the flash on some Firmwares I have tried, but then I'll be stuck in a boot loop. I just cannot seem to have ANY luck trying to get my recovery back!
Any ideas what I could be doing wrong to get no success at all in downgrading from 5.1.1? Are there any methods to get into recovery in 5.1.1? Mine doesn't seem to ever work.
Is there a way to flash or install a backup that I did in TWRP without a recovery menu or no? Just want it all back to normal for now, 5.1.1 can get lost for the time being, screwed me over bad.
DGJ1992 said:
Hey guys,
So I wanted to upgrade to 5.1.1 and I saw a couple of ROMs for 5.1.1 that I was interested in flashing. So I chose this one > http://forum.xda-developers.com/z3-compact/development/rom-one-solution-debloated-xposed-t3164221
When I wiped, and then went to install it gave me an error, md5 error or something, but it seems it had already wiped my stuff.
So my phone was bricked and I could not get it past the initial Sony Xperia screen AT ALL. The only solution I found was to use "Emma" and recover it by resetting to factory. In doing so however, Emma installed a Stock 5.1.1, which booted no problems at all. Fantastic. Now I am on 5.1.1, unrooted, and inability to install or boot into a recovery to flash my backup.
Here's my problem, every single time I try to downgrade my Firmware back to Lollipop 5.0.2, or KitKat even, it either freezes at random places, like this > http://puu.sh/jRHEj/f3da0dfcfa.png
OR it finishes the flash on some Firmwares I have tried, but then I'll be stuck in a boot loop. I just cannot seem to have ANY luck trying to get my recovery back!
Any ideas what I could be doing wrong to get no success at all in downgrading from 5.1.1? Are there any methods to get into recovery in 5.1.1? Mine doesn't seem to ever work.
Is there a way to flash or install a backup that I did in TWRP without a recovery menu or no? Just want it all back to normal for now, 5.1.1 can get lost for the time being, screwed me over bad.
Click to expand...
Click to collapse
Try flashing the firmware ( ftfs ) using a different computer. If that doesn't help you can consider one of two options
1) Unlock your bootloader, that way all you need to do is download a custom kernel that comes with a recovery and flash any rom you like therefore removing the need for flashtool
2) Send your phone to Sony if you prefer not to unlock the bootloader and let them fix it but it might cost you
*Also take note if you downgrade to Lollipop ( 5.0.2 ) as I know there are no methods on how to root it yet unless coming from Firmware .93 which is a Kitkat firmware.
Revontheus said:
Try flashing the firmware ( ftfs ) using a different computer. If that doesn't help you can consider one of two options
1) Unlock your bootloader, that way all you need to do is download a custom kernel that comes with a recovery and flash any rom you like therefore removing the need for flashtool
2) Send your phone to Sony if you prefer not to unlock the bootloader and let them fix it but it might cost you
*Also take note if you downgrade to Lollipop ( 5.0.2 ) as I know there are no methods on how to root it yet unless coming from Firmware .93 which is a Kitkat firmware.
Click to expand...
Click to collapse
Hey Revo, thanks a lot for your reply dude. Appreciate you taking the time out of your day. I managed to flash a .93 kit kat, when I go to install TWRP via adb fastboot, my phone boots up with no image. I can hear sound and touch screen works but I have no picture. Super weird, had to reflash again to kitkat to restore picture. My bootloader is Unlocked already, so how effectively, on kitkat .93, can I get TWRP installed to recover my old backup? What's the easiest way from here?
DGJ1992 said:
Hey Revo, thanks a lot for your reply dude. Appreciate you taking the time out of your day. I managed to flash a .93 kit kat, when I go to install TWRP via adb fastboot, my phone boots up with no image. I can hear sound and touch screen works but I have no picture. Super weird, had to reflash again to kitkat to restore picture. My bootloader is Unlocked already, so how effectively, on kitkat .93, can I get TWRP installed to recover my old backup? What's the easiest way from here?
Click to expand...
Click to collapse
If you have your bootloader unlocked, you can just flash custom kernel via Flashtool, that would be AndroPlus kernel and you'll have a custom recovery
Cirra92 said:
If you have yout bootloader unlocked, you can just flash custom kernel via Flashtool, that would be AndroPlus kernel and you'll have a custom recovery
Click to expand...
Click to collapse
Nice, got that done and just finished restoring my own backup, AHHHHHHHHHH my phone is back. Technology is freaky as hell man. Crazy crazy world we live in.
I really wish I could click one button and donate money evenly amongst all you insane people that write awesome awesome tutorials for what I assume is like, non-profit? It's mental. Wouldn't have my phone back right now if it wasn't for this forum. It's just unreal. SO happy right now.
So if anyone knows at all, million dollar question. What's now the safest possible option, if ANY, to get from 5.0.2 rooted, to 5.1.1 rooted? To keep all my data I am obviously going to have to backup up all my photos/music/contacts/sms etc onto my PC or online in a mysterious cloud, but what's the best steps now to safely get to 5.1.1 rooted, with no hassle? Or is it even worth it at this point?
DGJ1992 said:
What's now the safest possible option, if ANY, to get from 5.0.2 rooted, to 5.1.1 rooted?
Click to expand...
Click to collapse
Now you just have to download a prerooted 5.1.1 rom and flash it through recovery and that is all. Full wipe is recommended before that of course (data, cache, dalvik, system)

G870A, Soft Bricked, Need 4.4.4 or 5.1.1 completely stock "Unrooted" firmware file

G870A, Soft Bricked, Need 4.4.4 or 5.1.1 completely stock "Unrooted" firmware file
EDITED 12-27-15:
XDA Assist has sent me to this forum (Thanx). Info and questions follow, here are the basic details:
G870A variant of the samsung S5 (Active)
Stock, unrooted, carrier locked
interrupted power during OTA update from AT&T (most likely 5.1.1)
forced phone into "download mode" and attempted to flash 4.4.2 (NE4) instead of update (actual file used: G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5)
Phone stuck in bootloop with freeze/repeat at AT&T logo
unable to locate completely stock firmware file for 4.4.4 (G870AUCU1AOA1 or OA2) to flash back to most recent functional OS.
still currently able to force recovery mode or download mode.
**update:
As far as i know, the OTA for 5.1.1 did completely download but i dont think it "installed" because i removed battery during initial auto-reboot. The existing ROM would have been 4.4.4 mentioned above, updated and active official firmware from AT&T.
Basic Explanation of actions: I do fully realize that my actions and subsequent "incomplete" attempt to patch the software were unwise but i was merely weeks away from paying off the phone, owning it, having it unlocked by AT&T, properly rooting and installing a custom ROM (as i had successfully done to my wife's G900A). In a moment of panic, not wanting to be locked out of my phone forever by Lolipop, I ripped out the battery during the reboot that was loading Lolipop... every time I put the battery back in and hit power, the phone still attempted to load and write 5.1.1. So I thought maybe, the official firmware copy from 4.4.2, which my phone shipped with in 2014, might flash, even though i was not rooted or unlocked. Clearly i was mistaken but it was all i could think of under pressure.
At this point, I am Completely unconcerned about almost all data on phone or even the hardware EXCEPT for some extensive "memo" notes, which i desperately want to recover. I also dont care anymore about avoiding Lolipop because the memo data is more important to me. I am literally willing to rip the internal memory from this phone and send the SD to a data forensics company if that's what it takes, i no longer care about the phone at all... Having said that, recovering it myself and keeping the phone might be nice also.
Question: where might i find a completely stock firmware for 4.4.4 factory, UN-rooted,to flash; or what procedure might i use to directly pull data from the phone, while soft bricked, before doing a full factory reset?
Alternately, any advice on directions i may not have thought of yet?
I have looked pretty deep into the existing XDA forums for this info but i am only finding "custom ROMs" which are rooted or factory stock ROMS for 4.4.2 and most advice deals with rooting, then flashing. I am not rooting but simply flashing fully unrooted stock firmware AND starting in a bootloop/soft brick state. This is why i did a fresh thread.
Thanks in advance to anyone who might be able to help!
rtlarkin said:
Hello XDA Assist! After reading the stickies, i see that you may be able to direct me to the correct forum in which to post my main question. Here are the basic details:
G870A variant of the samsung S5 (Active)
Stock, unrooted, carrier locked
interrupted power during OTA update from AT&T (most likely 5.1.1)
forced phone into "download mode" and attempted to flash 4.4.2 (NE4) instead of update (actual file used: G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5)
Phone stuck in bootloop with freeze/repeat at AT&T logo
unable to locate completely stock firmware file for 4.4.4 (G870AUCU1AOA1 or OA2) to flash back to most recent functional OS.
still currently able to force recovery mode or download mode.
Completely unconcerned about all data on phone or even the hardware EXCEPT for some extensive "memo" notes, which i want to recover.
Question: where might i find a completely stock firmware for 4.4.4 to flash; or what procedure might i use to directly pull data from the phone before doing a full factory reset?
Alternately, advice on directions i may not have thought of yet.
Thanks a bunch!
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the expert help you need, I'm going to move this thread to the most relevant Q&A forum for your device. Good luck!
Hello,
I am not an expert or anywhere close but I understand the basics of Android flashing / rooting, etc.
I happened to have rooted my G870A from AT&T successfully using a thread from XDA and I noticed they also provided the original firmware for G870A in case of problems:
http://forum.xda-developers.com/att...to-root-g870aucu1aoa1-4-4-4-2-7-2015-t3025119
So I thought this may help you considering you're looking for an original firmware for your G870A.
What I suggest is to try to flash "G870AUCU1ANE4_Full_Odin.tar" (available from the thread I linked above, I didn't want to rip the links out of the thread) using Odin v3.09+.
I did not use this firmware to root my G870A (only used the updates) but everything worked on the first try.
Follow instructions in the thread I provided. If that still doesn't work, you may need an Android expert on the case.
I wish you good luck in your data recovery. And yes, I registered just to post a reply to your thread.
(also: if you want to root your G870A, the thread explains the proper way to do it!)
Appreciate the thought
dapr0b said:
I happened to have rooted my G870A from AT&T successfully using a thread from XDA and I noticed they also provided the original firmware for G870A in case of problems:
http://forum.xda-developers.com/att...to-root-g870aucu1aoa1-4-4-4-2-7-2015-t3025119
So I thought this may help you considering you're looking for an original firmware for your G870A.
What I suggest is to try to flash "G870AUCU1ANE4_Full_Odin.tar"
Click to expand...
Click to collapse
Really appreciate the thought, however, that particular file is the file that i had originally used before posting. i think since my phone was factory locked and unrooted i did not have the permissions needed to basically "roll back" my phone to 4.4.2 but i am not educated enough to be sure of the exact problem flashing that file.
Thanks again for suggesting it though! I am nearing the time when I will just have to give up and send off the internal memory for physical extraction and data recovery
Hello,
I am also not an expert or anywhere close but I understand the basics of Android flashing / rooting, etc.
With that said: Let the OTA happen. You will not lose the files unless you already started a factory reset. Then your sol. You will not be able to root but you have a better chance of retrieving the files you are looking for. The phone is not like a computer. You can't just pull the HD and sent it out. You either already had the 5.0 kernel or the 5.1 kernel loaded before you stopped the process. This makes it impossible to go back. You can only go forward.
Good luck and let us know how you make out.
re: take the OTA
Sgt.CM said:
With that said: Let the OTA happen. You will not lose the files unless you already started a factory reset.
Click to expand...
Click to collapse
Thanks for that idea. the trouble at this point is that im stuck in a bootloop that catches on the att logo. I agree that the only option now is to continue forward. i just need a fully official software newer than 4.4.4 to load through kies or odin. at least i "hope" the newer file will work.
so far i have only been able to find stock ROMs that are rooted, and i dont think i can load a rooted stock ROM onto a carrier locked un-rooted phone.
The part you mentioned about the kernal is probably true. i had not thought of that before.

Categories

Resources