I have a AT&T Galaxy S3 and I have been searching the forums for a solution to this, and have come up with some answers. From what I've gathered I am by no means at the end of my ropes at recovering the device, but I'm having trouble actually making any ground on it.
I read that flashing back to stock using Odin would get me by the yellow triangle of death, but I can't find a stock download anywhere. All the links I've found link to hotfile, which isn't up anymore so that's been creating some problems. Maybe I'm wrong on that, but all I need is Samsung's stock 4.0.4, right?
I have a HTC Sensation and Nexus 10, both rooted, and I thought I had a pretty good grip on what direction was up from working on those devices but this S3 really has me stumped. Any help would be greatly appreciated.
It might be better if you could mention what exactly you did to get your device to the state it is in.
diablo009 said:
It might be better if you could mention what exactly you did to get your device to the state it is in.
Click to expand...
Click to collapse
Woops, sorry. I flashed CF-Root-SGS3-v6.3.tar using Odin and the process failed.
What OS were you running before trying to root? If it's 4.3, you won't find an AT&T stock 4.3 rom to re-flash your phone. Do not try and flash anything with a bootloader that is older than the phone's current bootloader as that will brick it.
audit13 said:
What OS were you running before trying to root? If it's 4.3, you won't find an AT&T stock 4.3 rom to re-flash your phone. Do not try and flash anything with a bootloader that is older than the phone's current bootloader as that will brick it.
Click to expand...
Click to collapse
Thankfully, I was running 4.0.4.
andrbrks said:
Thankfully, I was running 4.0.4.
Click to expand...
Click to collapse
Stock AT&T firmware files are here: http://www.sammobile.com/firmwares/1/?model=SGH-I747&pcode=ATT#firmware
In my opinion, don't go near 4.3.
I'm sorry, I feel like this should be obvious, but how do I know which of these I want to flash?
So you're sure you were on 4.04 when you tried to root? If that's the case, I would try the July version.
By flashing in Odin, you will wipe everything off the phone, including your data.
audit13 said:
So you're sure you were on 4.04 when you tried to root? If that's the case, I would try the July version.
By flashing in Odin, you will wipe everything off the phone, including your data.
Click to expand...
Click to collapse
100%. On the box the SW-VER is listed as I747UCDLK3, should I still go with the July version? And I use the PDA function in Odin for this, correct?
Wait, DLK3 is 4.1.1, not 4.0.4.
http://androidromupdate.com/2012/12...-s3-android-4-1-1-jelly-bean-official-update/
analysis higionu
Huh. I reset the phone to factory settings last night before I started tinkering with anything, and it was for sure listed as 4.0.4. I could be mistaken though, but I'm fairly certain. I'd rather not go against what's listed on it's box though. I'm sure the factory knows better than me.
I'm not sure what to do now. Does the imei # match the box?
That it does. I have to wait another 2 hours before I can even download the stock firmware, so it'll be awhile before I can even try flashing it.
andrbrks said:
That it does. I have to wait another 2 hours before I can even download the stock firmware, so it'll be awhile before I can even try flashing it.
Click to expand...
Click to collapse
I'm not sure what I would do in your situation since the box indicates you have 4.1.1 while your phone has 4.04.
You were right, I talked with someone who was there last night when I was working on it. The phone is 4.1.1, thanks for the catch.
Okay, at least it is definitely not 4.3 which is good.
What you can do is install a custom recovery and flash a custom ROM.
So should I not even worry about going back to stock then?
andrbrks said:
So should I not even worry about going back to stock then?
Click to expand...
Click to collapse
Did you try returning to stock using Kies?
Stock firmware is here: http://www.sammobile.com/firmwares/1/?model=SGH-I747&pcode=ATT#firmware
Running it right now.
I hope it works for you. Good luck:good:
Related
hey guys I'm having some issue changing my phone back to stock, i did some digging around and found some stuff on different models though. I'm on a t-mobile galaxy s3 sgh-t999, i rooted my phone to get WiFi tethering. found out later that the new jellybean firmware blocks it so its pretty much useless now. i unrooted my phone using mobile odin, triangle away to rest count and cwm recovery to do so. wiped cache partition and did a factory reset. the unroot was successful but my phone says modified now instead of normal or original like its supposed to. the stock rom that i flashed takes me back to 4.0.4 ics when it goes to download updates it stops at 4.1.1 after that i get a message saying my phone is modified and updates are not available. all i want is my phone back to normal like i just bought it, I'm thinking about exchanging it and I'm pretty sure they wont take it if the status reads modified. i read this thread about a root66_TMO_T889UVALL4 rom with odin that keeps everything stock and keeps the count at zero thought the whole wipe and boot process. is that something i could use on my phone? any info on how i can fix this is extremely appreciated guys thanks.
Do not flash anything.
Open the battery compartment of your phone, take the battery out, and tell us what the model number says.
Aerowinder said:
Do not flash anything.
Open the battery compartment of your phone, take the battery out, and tell us what the model number says.
Click to expand...
Click to collapse
tmobile SGH-T999
Use the firmware from this page, so you don't brick your phone: http://forum.xda-developers.com/showthread.php?t=1949687
Aerowinder said:
Use the firmware from this page, so you don't brick your phone: http://forum.xda-developers.com/showthread.php?t=1949687
Click to expand...
Click to collapse
one more question, like i said i just unrooted my phone do i have to root it again in order to flash the rom you liked me to?
You don't need to be rooted to flash a ROM.
Hey all,
I caught wind of the 4.4.2 update, so I decided to see how it is. I had used saferoot to gain root access to it, but all I did was use Xposed to modify my phone. No recoveries or anything, and the warranty bit is 0 on the download mode screen. Just to be safe, I wiped data/factory reset to make sure everything was gone, then I started the OTA download. All goes as it should until it reboots to install it, where it gets stuck at 25%, then says "update failed". Phone reboots, and then a window pops up saying the update was interrupted. Anyone else having this issue? Anyone know any workarounds? Because if this phone just won't update, there it no reason for my to keep my warranty bit, since I have less than a week on the warranty left anyhow.
TH3F4LL3N said:
Hey all,
I caught wind of the 4.4.2 update, so I decided to see how it is. I had used saferoot to gain root access to it, but all I did was use Xposed to modify my phone. No recoveries or anything, and the warranty bit is 0 on the download mode screen. Just to be safe, I wiped data/factory reset to make sure everything was gone, then I started the OTA download. All goes as it should until it reboots to install it, where it gets stuck at 25%, then says "update failed". Phone reboots, and then a window pops up saying the update was interrupted. Anyone else having this issue? Anyone know any workarounds? Because if this phone just won't update, there it no reason for my to keep my warranty bit, since I have less than a week on the warranty left anyhow.
Click to expand...
Click to collapse
Did you try re-downloading it?
BWolf56 said:
Did you try re-downloading it?
Click to expand...
Click to collapse
This is my 3rd attempt to re-download it. It's currently at 94%, so I'll let you know how it goes.
TH3F4LL3N said:
This is my 3rd attempt to re-download it. It's currently at 94%, so I'll let you know how it goes.
Click to expand...
Click to collapse
After my 3rd attempt, without my sd card inserted this time, the update failed again! This is starting to get irritating. Maybe I should just flash CM11 or something like that.
TH3F4LL3N said:
After my 3rd attempt, without my sd card inserted this time, the update failed again! This is starting to get irritating. Maybe I should just flash CM11 or something like that.
Click to expand...
Click to collapse
It's kinda odd that it still fails after so many downloads (and so close to being complete).
If there's only a week left to your warranty, you can start looking at custom ROM you might like (AOSP or TW). By the time you find one you really like and understand how to flash it (without any issue), you will have time to give the OTA another shot. Will be some good knowledge reading in the meantime
Little advice: Don't flash a custom ROM while annoyed/mad. That's how 80% of bricks happen.
BWolf56 said:
It's kinda odd that it still fails after so many downloads (and so close to being complete).
If there's only a week left to your warranty, you can start looking at custom ROM you might like (AOSP or TW). By the time you find one you really like and understand how to flash it (without any issue), you will have time to give the OTA another shot. Will be some good knowledge reading in the meantime
Little advice: Don't flash a custom ROM while annoyed/mad. That's how 80% of bricks happen.
Click to expand...
Click to collapse
Ok thanks for the advice, mate. I heard if I take it to Best Buy, they can update it. Do you know if it's free?
TH3F4LL3N said:
Ok thanks for the advice, mate. I heard if I take it to Best Buy, they can update it. Do you know if it's free?
Click to expand...
Click to collapse
Imo it should be but you can always give them a call to make sure.
Just make sure you aren't rooted when going there lol.
BWolf56 said:
Imo it should be but you can always give them a call to make sure.
Just make sure you aren't rooted when going there lol.
Click to expand...
Click to collapse
Haha I know the basics of rooting. If I go, my phone will be the way it is right now: stuck on stock 4.3 with nothing on it but the bloatware from Sammy and AT&T
TH3F4LL3N said:
Haha I know the basics of rooting. If I go, my phone will be the way it is right now: stuck on stock 4.3 with nothing on it but the bloatware from Sammy and AT&T
Click to expand...
Click to collapse
I just noticed that the device status is custom, even though I've wiped data. Is that what is causing this trouble? If so, is there a way to fix it?
Yea when you modify the system at all it trips the modified flag and that's probably where its failing (not the warranty bit flag that's at 0 but the one that's in the system itself) try to Odin to full stock and try it again this should revert it back to official
Sent from my ATT Samsung Galaxy SIII using TapaTalk
TH3F4LL3N said:
I just noticed that the device status is custom, even though I've wiped data. Is that what is causing this trouble? If so, is there a way to fix it?
Click to expand...
Click to collapse
You need to run Triangle Away whiule rooted to change it back to official
audit13 said:
You need to run Triangle Away whiule rooted to change it back to official
Click to expand...
Click to collapse
Will this work for 4.3?
I never tried it on 4.3, only on 4.1.2. Since you have Knox, rooting and installing SU may trip the knox counter. Did you try uninstalling Xposed and running the update?
TH3F4LL3N said:
I just noticed that the device status is custom, even though I've wiped data. Is that what is causing this trouble? If so, is there a way to fix it?
Click to expand...
Click to collapse
crazymonkey05 said:
Yea when you modify the system at all it trips the modified flag and that's probably where its failing (not the warranty bit flag that's at 0 but the one that's in the system itself) try to Odin to full stock and try it again this should revert it back to official
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
One thing, don't downgrade bootloaders doing so. That will result in a brick.
audit13 said:
I never tried it on 4.3, only on 4.1.2. Since you have Knox, rooting and installing SU may trip the knox counter. Did you try uninstalling Xposed and running the update?
Click to expand...
Click to collapse
I have, and I've wiped the phone at least 3 or 4 times!
BWolf56 said:
One thing, don't downgrade bootloaders doing so. That will result in a brick.
Click to expand...
Click to collapse
How would I go about this? I have the stock 4.1.1 tar file, and I can't get the 4.3 file because AT&T's update was OTA only, and I can't find the 4.3 tar file anywhere!
TH3F4LL3N said:
I have, and I've wiped the phone at least 3 or 4 times!
How would I go about this? I have the stock 4.1.1 tar file, and I can't get the 4.3 file because AT&T's update was OTA only, and I can't find the 4.3 tar file anywhere!
Click to expand...
Click to collapse
Is your current baseband LK3? If so, 4.1.1 should be fine.
BWolf56 said:
Is your current baseband LK3? If so, 4.1.1 should be fine.
Click to expand...
Click to collapse
I am in the about device section of the settings, and it says the baseband version is I747UCUEMJB. Is this the right one?
TH3F4LL3N said:
I am in the about device section of the settings, and it says the baseband version is I747UCUEMJB. Is this the right one?
Click to expand...
Click to collapse
That would be the 4.3. You can't downgrade from those bootloaders. Therefor, you need stock 4.3
BWolf56 said:
That would be the 4.3. You can't downgrade from those bootloaders.
Click to expand...
Click to collapse
Well that's just great. I'm stuck on 4.3. Could I possibly flash something like CM11 to get to kitkat? Of course, I'd like to back up the stock rom in case something goes wrong, but it would be wonderful if I could use CM on my phone again! I used the saferoot method to gain root access in the first place, which disabled KNOX if that means anything.
TH3F4LL3N said:
Well that's just great. I'm stuck on 4.3. Could I possibly flash something like CM11 to get to kitkat? Of course, I'd like to back up the stock rom in case something goes wrong, but it would be wonderful if I could use CM on my phone again! I used the saferoot method to gain root access in the first place, which disabled KNOX if that means anything.
Click to expand...
Click to collapse
Yes you can, it's fairly simple too. Just gotta follow their instructions (don't skip anything).
As for recovery, I recommend TWRP, which you can get on the Play Store.
These issues started with the upgrade to latest T-Mobile 4.3 software pack at the end of November. Phone operated perfectly before then. After the update, the phone would periodically not receive/place calls/texts/use data. The issue kept worsening daily. It is not related to the SIM card or location, as the card has been replaced and tested in an alternate phone where it performs perfectly.
The T999L was then consequently rooted, KNOX flagged (it's already past warranty, Samsung wouldn't give a rat's ass about it), flashed to CM11 M12 and later a variety of modems was tried. Same issues persisted. Restored to stock 4.1.2, same issues. Did 3 updates OTA to get to latest 4.3, same issues.
Messed around with 4636 menu, 2263 menu, etc. Some changes had a temporary result but nothing permanent. Calls to the phone are redirected to voicemail. When placing a call, it takes 5-10 seconds to either place it or disconnect it (as it can't connect to the network, I guess?). The bars on the phone show 3-4 bars typically, but the phone is rarely able to acquire a data connection. Again, this is not the case with other phones the SIM is tried on.
Any suggestions? I've spent probably close to 10 hours researching this and trying everything out and I am absolutely stumped. This is my mom's phone and a replacement Alcatel OneTouch Fierce 2 just "doesn't look nice", so I'm getting a fair bit of *****ing for trying to help solve this, even though it's not my fault. Would appreciate some help before Christmas.
Have you tried updating the modem?
systemcode said:
Have you tried updating the modem?
Click to expand...
Click to collapse
flashed to CM11 M12 and later a variety of modems was tried. Same issues persisted.
Click to expand...
Click to collapse
I'd say so. Used this thread: http://forum.xda-developers.com/showthread.php?t=1880987 and flashed the 4.3 basebands for T999L and T999N, total of 3. I'm thinking this is something to do with the 4.3 bootloader or basebands... any methods to go back to 4.1.2 without a brick?
tagging this for later use:
http://forum.xda-developers.com/showthread.php?t=2121736
http://forum.xda-developers.com/showthread.php?t=2258238
dwegiel said:
I'd say so. Used this thread: http://forum.xda-developers.com/showthread.php?t=1880987 and flashed the 4.3 basebands for T999L and T999N, total of 3. I'm thinking this is something to do with the 4.3 bootloader or basebands... any methods to go back to 4.1.2 without a brick?
tagging this for later use:
http://forum.xda-developers.com/showthread.php?t=2121736
http://forum.xda-developers.com/showthread.php?t=2258238
Click to expand...
Click to collapse
If you have a T999L stick to the designated T999L modems and nothing else, or you may damage the device. If you have a 4.3 bootloader there is no way back. Have you tried to use ODIN to flash the latest NF4 firmware for your T999L and then do a factory reset using the stock recovery? I posted NF4's link in this post. Good luck.
nirogu325 said:
If you have a T999L stick to the designated T999L modems and nothing else, or you may damage the device. If you have a 4.3 bootloader there is no way back. Have you tried to use ODIN to flash the latest NF4 firmware for your T999L and then do a factory reset using the stock recovery? I posted NF4's link in this post. Good luck.
Click to expand...
Click to collapse
Downloading right now, and will test. Pretty sure this is the firmware update after which this problem started occurring.
Any other ideas for what might be affecting this besides baseband? I have a feeling something else might be causing this. I'm not familiar with Samsung partitions though and what is flashed by OTA/Odin.
dwegiel said:
Downloading right now, and will test. Pretty sure this is the firmware update after which this problem started occurring.
Any other ideas for what might be affecting this besides baseband? I have a feeling something else might be causing this. I'm not familiar with Samsung partitions though and what is flashed by OTA/Odin.
Click to expand...
Click to collapse
Well, OTA updates can sometimes fail, that's why I gave you the ODIN firmware link. It's the best help I can offer.
After taking the APH1 update on my phone, I can no longer downgrade to PG5, and I also can't flash the PG9 U firmware. I don't know what Samsung/Verizon did, but it's ridiculous.
I'm now stuck on the APH1 firmware and can't get on the U firmware at all.
I haven't tried rooting, but there is no Odin firmware for APH1 yet, so I'm not going to try until there is, so that if I mess up my phone I can fix it.
FoxyDrew said:
After taking the APH1 update on my phone, I can no longer downgrade to PG5, and I also can't flash the PG9 U firmware. I don't know what Samsung/Verizon did, but it's ridiculous.
I'm now stuck on the APH1 firmware and can't get on the U firmware at all.
I haven't tried rooting, but there is no Odin firmware for APH1 yet, so I'm not going to try until there is, so that if I mess up my phone I can fix it.
Click to expand...
Click to collapse
It probably incremented the bootloader. I upgraded to it because I am just losing interest in root all together. Somebody will chime in with a more technical explanation.
DarkMidnight said:
It probably incremented the bootloader. I upgraded to it because I am just losing interest in root all together. Somebody will chime in with a more technical explanation.
Click to expand...
Click to collapse
Agreed. For some reason I just don't really care about rooting the S7. Maybe I've just rooted too many phones and lost interest.
nynativ said:
Agreed. For some reason I just don't really care about rooting the S7. Maybe I've just rooted too many phones and lost interest.
Click to expand...
Click to collapse
For me a lot of it is this is not the most conventional root, not very stable for me and battery life suffered a lot compared to stock, and flashing U firmware has not been very cooperative for me.
So thoughts.... I am on the latest U firmware on my 930V. Should I consider flashing back to the stock Verizon rom? Everything is working great. I do plan on jumping ship from Verizon in the next year or so. I am blown away at how well this phone runs stock and only flashed the U in preparation to take it to another carrier afterwards. Is this a bad idea?
Tried to live with root, but the battery and stability was horrible. Now, I am using the engboot to do any data back up or restore tasks in TiBU then flashing the AP again to unroot. Data is maintained, but now I have to live with ads. I use adguard, by it feel like it hurts battery life. Will try and quantify that soon.
Being able to count on my phone to make a call and hold a charge is too important to me. Rooting the phone to set it up after a reset saves me time. Unfortunately, rooting with our current method is too prohibitive for daily use.
nynativ said:
Agreed. For some reason I just don't really care about rooting the S7. Maybe I've just rooted too many phones and lost interest.
Click to expand...
Click to collapse
Same here.
I have a 930U that I use on Verizon. I use the 930V firmware because I like having visual Voicemail. I have rooted 3 different times and gone back to stock everytime. I suppose it because of the engineering kernel but root with the S7 is just not stable. The battery life sucks and you have to do so many things to fix the lag it has just become not worth it. Also the 2 latest updates from Verizon have been good on battery. I do like not having Verizon logos all over my phone.
nrage23 said:
I have a 930U that I use on Verizon. I use the 930V firmware because I like having visual Voicemail. I have rooted 3 different times and gone back to stock everytime. I suppose it because of the engineering kernel but root with the S7 is just not stable. The battery life sucks and you have to do so many things to fix the lag it has just become not worth it. Also the 2 latest updates from Verizon have been good on battery. I do like not having Verizon logos all over my phone.
Click to expand...
Click to collapse
Give stang5liter rom a whirl. Been on it since it was released and have no issues besides nearby devices not working for me.
craazy82013 said:
Give stang5liter rom a whirl. Been on it since it was released and have no issues besides nearby devices not working for me.
Click to expand...
Click to collapse
Been using the same ROM for almost a week with xposed and everything is fine. I feel great without seeing the ads again. haha! BTW, I didn't try the nearby devices so no comment on that.
I have the G930V and am running APH1 with root no problems. The lag was horrendous but after changing the CPU governor to "interactive" on BOTH CPU's (little and BIG) it's been running smooth. I'll run like this for a bit... but stang5liter looks like it will be my next move.
Has anyone with ph1 tried flashing another rom such as stang5litre?
dBunny said:
I have the G930V and am running APH1 with root no problems. The lag was horrendous but after changing the CPU governor to "interactive" on BOTH CPU's (little and BIG) it's been running smooth. I'll run like this for a bit... but stang5liter looks like it will be my next move.
Click to expand...
Click to collapse
So how did you root if you can't downgrade like the OP stated?
craazy82013 said:
Has anyone with ph1 tried flashing another rom such as stang5litre?
Click to expand...
Click to collapse
Yes it works just fine.
bart77 said:
So how did you root if you can't downgrade like the OP stated?
Click to expand...
Click to collapse
PH1 doesn't break root. You just can't downgrade to older firmware's or flash any U firmware's. PH1 is still completely rootable.
So you can't Odin flash back to a stock image if you get in trouble or want to unroot. I guess I'll stay on PG5 for now.
I'm not rooted now, but was able to disable system update notifications using
https://play.google.com/store/apps/details?id=com.hecorat.packagedisabler
By disabling:
System updates (com.samsung.sdm)
System updates (com.samsung.sdmviewer)
and securitylogagent
FoxyDrew said:
PH1 doesn't break root. You just can't downgrade to older firmware's or flash any U firmware's. PH1 is still completely rootable.
Click to expand...
Click to collapse
Thanks @FoxyDrew for clarifying that... and I agree.
I used the following GUIDE to root APH1 on my S7 Flat: http://forum.xda-developers.com/verizon-s7-edge/how-to/verizon-root-knox-t3410624
Im somewhat confused. Your saying you cant downgrade from ph1. Are you talking only with odin? Reason i ask is stang5litre rom is APE1. And as was stated a few posts up, this rom can be flashed on rooted APH1. Which would take you back to APE1. Therefor downgradable? Any help is appreciated.
craazy82013 said:
Im somewhat confused. Your saying you cant downgrade from ph1. Are you talking only with odin? Reason i ask is stang5litre rom is APE1. And as was stated a few posts up, this rom can be flashed on rooted APH1. Which would take you back to APE1. Therefor downgradable? Any help is appreciated.
Click to expand...
Click to collapse
Ph1 upgrades the boot image therefore you cannot Odin flash back to stock pe1 which is the older boot image.
You can still root and flash stang5litre which is the pe1 rom, but you still have the ph1 boot image.
Sent from my VS987 using XDA-Developers mobile app
bart77 said:
Ph1 upgrades the boot image therefore you cannot Odin flash back to stock pe1 which is the older boot image.
You can still root and flash stang5litre which is the pe1 rom, but you still have the ph1 boot image. So if something goes wrong, you have no means of recovery back to stock since there is no ph1 stock Odin image.
Sent from my VS987 using XDA-Developers mobile app
Click to expand...
Click to collapse
The ph1 image is available at this link (http://updato.com/firmware-archive-select-model?record=78F84FCD811E11E69B2DFA163EE8F90B). I have flashed with these files and they work perfect.
Seems bootloader was uograded to version 3. So may be possible to flash between tmo and vzw and vice versa. Both now have v3 bootloader.
Hi if anyone can help- I'm on the Verizon Samsung Galaxy Note 4 after 2 Note 7's and a Note 3 before that on Biggin's so I've sorta been out of the root game. I want to downgrade from 6.0.1 to 5.1.1. I am downloading the full firmware for the Note 4 from further back in this thread (N910VVRU2CPA1) and am currently on (N910VVRU2CPG2).
From what I understand, I need to do a factory reset, then go to Odin and flash the firmware. I have Odin 3.10.7 and am downloading the N910VVRU2CPA1 as we speak. I see 'hsbadr' firmwares in his thread and the PIT file TRLTE_USA_VZW.pit which I'm not sure is compatable pit file for the specific 5.1.1 firmware or the necessary pit file is included in the full firmware and can anyone tell me if these are the right steps?are these the right steps Any information would be greatly appreciated,
Thanks
@tjmethod by chance how did you process go, did you manage to root and unlock bootloader?
djisback said:
@tjmethod by chance how did you process go, did you manage to root and unlock bootloader?
Click to expand...
Click to collapse
I bought the phone already with 6.0.1 on it and read that you cannot unlock/ root it with mm on it and can only be done after downgrading to 5.1.1 so I haven't done anything yet
I'm in the same boat...Coming from a n7. Bought a n4 on eBay...It's got 601. Want to root...Guess we need to downgrade....Is it possible?
tjmethod said:
Hi if anyone can help- I'm on the Verizon Samsung Galaxy Note 4 after 2 Note 7's and a Note 3 before that on Biggin's so I've sorta been out of the root game. I want to downgrade from 6.0.1 to 5.1.1. I am downloading the full firmware for the Note 4 from further back in this thread (N910VVRU2CPA1) and am currently on (N910VVRU2CPG2).
From what I understand, I need to do a factory reset, then go to Odin and flash the firmware. I have Odin 3.10.7 and am downloading the N910VVRU2CPA1 as we speak. I see 'hsbadr' firmwares in his thread and the PIT file TRLTE_USA_VZW.pit which I'm not sure is compatable pit file for the specific 5.1.1 firmware or the necessary pit file is included in the full firmware and can anyone tell me if these are the right steps?are these the right steps Any information would be greatly appreciated,
Thanks
Click to expand...
Click to collapse
sudermatt said:
I'm in the same boat...Coming from a n7. Bought a n4 on eBay...It's got 601. Want to root...Guess we need to downgrade....Is it possible?
Click to expand...
Click to collapse
Before you can start rooting, you'll need to be on 5.1.1 BPA1. If you're currently on 6.0.1, just download the BPA1 firmware from Sammobile, factory reset on 6.0.1, then flash BPA1 stock via Odin.
quinciebee said:
Before you can start rooting, you'll need to be on 5.1.1 BPA1. If you're currently on 6.0.1, just download the BPA1 firmware from Sammobile, factory reset on 6.0.1, then flash BPA1 stock via Odin.
Click to expand...
Click to collapse
Hi thanks, I had called Samsung and talked to top tier tech support and was told that once the phone has been upgraded to 6.0.1., it cannot be downgraded. and that i need to search the rooting sites and try to find where someone has found a breach or workaround for unlocking the bootloader which will usually have a bounty but I dont know. top tier tech support has always been good. Do you think thats false it cannot be downgraded?
tjmethod said:
Hi thanks, I had called Samsung and talked to top tier tech support and was told that once the phone has been upgraded to 6.0.1., it cannot be downgraded. and that i need to search the rooting sites and try to find where someone has found a breach or workaround for unlocking the bootloader which will usually have a bounty but I dont know. top tier tech support has always been good. Do you think thats false it cannot be downgraded?
Click to expand...
Click to collapse
It's definitely false, when I rooted my phone, I downgraded from 6.0.1 to 5.1.1 without any issues.
quinciebee said:
It's definitely false, when I rooted my phone, I downgraded from 6.0.1 to 5.1.1 without any issues.
Click to expand...
Click to collapse
I will definately give it a go when I have the time, have you flashed a rom and if so which one, there must be some or some tweaks to get rid of the lag?
tjmethod said:
I will definately give it a go when I have the time, have you flashed a rom and if so which one, there must be some or some tweaks to get rid of the lag?
Click to expand...
Click to collapse
I'm currently using CM13 because of Xposed and overall stability, but there are newer roms out there.
quinciebee said:
I'm currently using CM13 because of Xposed and overall stability, but there are newer roms out there.
Click to expand...
Click to collapse
I am a little confused as to whether I've found the right firmwares but I've found the firmwares here:
https://forum.xda-developers.com/no...mware-firmware-kernel-modem-recovery-t2942937
If I am downgrading to 5.1.1. which this phone was obviously on before, I don't know what this phone was on since it currently is on the PL1 build which are not one of the two 6.0.1. builds on this page. I don't even know if that matters.. Anyway, the two 5.1.1. builds are PA1 and OK3. Do you know where any other firmwares out there that might show my current one and the previous build that it came from?
Thanks-
tjmethod said:
I am a little confused as to whether I've found the right firmwares but I've found the firmwares here:
https://forum.xda-developers.com/no...mware-firmware-kernel-modem-recovery-t2942937
If I am downgrading to 5.1.1. which this phone was obviously on before, I don't know what this phone was on since it currently is on the PL1 build which are not one of the two 6.0.1. builds on this page. I don't even know if that matters.. Anyway, the two 5.1.1. builds are PA1 and OK3. Do you know where any other firmwares out there that might show my current one and the previous build that it came from?
Thanks-
Click to expand...
Click to collapse
You want the PA1. It's really easy. Just sounds more complicated then it is. I am using the PaulPizz rom. It is very stable, good battery life, and spen and sview work. If you need any help, let me know.
ziggy71 said:
You want the PA1. It's really easy. Just sounds more complicated then it is. I am using the PaulPizz rom. It is very stable, good battery life, and spen and sview work. If you need any help, let me know.
Click to expand...
Click to collapse
Thanks bro I don't if I'll have time til this weekend to do this- Does this rom have tweaks to fix the aggravating galaxy lag? With a non rooted phone there's goin into recovery and deleting cache, DU speed and phone booster, cleaned but it's like they all have it- thanks again- lookin forward to rooting this damn thing
tjmethod said:
I am a little confused as to whether I've found the right firmwares but I've found the firmwares here:
https://forum.xda-developers.com/no...mware-firmware-kernel-modem-recovery-t2942937
If I am downgrading to 5.1.1. which this phone was obviously on before, I don't know what this phone was on since it currently is on the PL1 build which are not one of the two 6.0.1. builds on this page. I don't even know if that matters.. Anyway, the two 5.1.1. builds are PA1 and OK3. Do you know where any other firmwares out there that might show my current one and the previous build that it came from?
Thanks-
Click to expand...
Click to collapse
Yeah they're out there but that thread hasn't been updated recently. Basically the order after pf3 is pg2, pj2, and then cpl1. The one you want, if your planning on rooting, is bpa1. Also, as far as your question in the op about the pit file, it should really only be used if absolutely necessary. It's in case your partitions have been corrupted for some reason and you need to repartition your device.
Edit- I was going to link to those other firmwares but they are buried in the thread that your already looking in. Either way they aren't necessary for you to unlock your bootloader, you can go straight from cpl1 to bpa1.
kevintm78 said:
Yeah they're out there but that thread hasn't been updated recently. Basically the order after pf3 is pg2, pj2, and then cpl1. The one you want, if your planning on rooting, is bpa1. Also, as far as your question in the op about the pit file, it should really only be used if absolutely necessary. It's in case your partitions have been corrupted for some reason and you need to repartition your device.
Edit- I was going to link to those other firmwares but they are buried in the thread that your already looking in. Either way they aren't necessary for you to unlock your bootloader, you can go straight from cpl1 to bpa1.
Click to expand...
Click to collapse
Hey thanks for confirming all this. So all I need to download and install is the bpa1 firmware via Oden with the AP button I think- I've got a few different versions of Oden on my pc. It's been a while since I've flashed firmware on a phone but I remember it was easy. So just save my pictures, any files, etc. on the sd card, remove it, then do a factory reset or when I put the setting into usb download mode, and flash the firmware this will automatically factory reset the phone? Also earlier today Verizon has been trying to push an software upgrade. After I unlock the bootloader and install twrp then flash a rom, do I need to somehow disable the update notice. I remember having to do that once with another phone.
What rom are you on? Thanks again for the Info-
TJ
tjmethod said:
Hey thanks for confirming all this. So all I need to download and install is the bpa1 firmware via Oden with the AP button I think- I've got a few different versions of Oden on my pc. It's been a while since I've flashed firmware on a phone but I remember it was easy. So just save my pictures, any files, etc. on the sd card, remove it, then do a factory reset or when I put the setting into usb download mode, and flash the firmware this will automatically factory reset the phone? Also earlier today Verizon has been trying to push an software upgrade. After I unlock the bootloader and install twrp then flash a rom, do I need to somehow disable the update notice. I remember having to do that once with another phone.
What rom are you on? Thanks again for the Info-
TJ
Click to expand...
Click to collapse
Yeah that all sounds spot on. I would definitely do the factory reset before you start, but other than that your good. To block the updates, you can uninstall the SDM apps. There are 2 of those and you'll need root to remove them, but you can disable them without root with that debloater tool. The rom I'm currently using is kind of work in progress. I have a couple stock based roms in the dev section, one is stock_plus that has a stock feel with some mods added and the other is Modest Rom that is got some grace apps added and system ui mods. You can find them here and here if you want to check them out.
kevintm78 said:
Yeah that all sounds spot on. I would definitely do the factory reset before you start, but other than that your good. To block the updates, you can uninstall the SDM apps. There are 2 of those and you'll need root to remove them, but you can disable them without root with that debloater tool. The rom I'm currently using is kind of work in progress. I have a couple stock based roms in the dev section, one is stock_plus that has a stock feel with some mods added and the other is Modest Rom that is got some grace apps added and system ui mods. You can find them here and here if you want to check them out.
Click to expand...
Click to collapse
Awesome, I'm going to check those out but I forgot the biggest question of all... how to get rid of the Galaxy lag- is there a rom or tweak where this can be fixed since recovery cache delete and cleaning tools dont really do much?
Thanks again-
tjmethod said:
Awesome, I'm going to check those out but I forgot the biggest question of all... how to get rid of the Galaxy lag- is there a rom or tweak where this can be fixed since recovery cache delete and cleaning tools dont really do much?
Thanks again-
Click to expand...
Click to collapse
Custom kernels help a lot. The problem is it's kind of slim pickings for our specific model, but some of the international kernels work well too. Oscar kernel is made for the 910v so that's probably the most reliable but if your like me, I like to use a permissive kernel and Ram kernel is not a bad choice for that though it's not as feature rich.
kevintm78 said:
Custom kernels help a lot. The problem is it's kind of slim pickings for our specific model, but some of the international kernels work well too. Oscar kernel is made for the 910v so that's probably the most reliable but if your like me, I like to use a permissive kernel and Ram kernel is not a bad choice for that though it's not as feature rich.
Click to expand...
Click to collapse
I really dont know the difference... from what I remember a kernel is the layer between the software and the hardware- a key component of the os. I'm guessing the permissive ones can be used for different roms or firmware? You can probably tell I really don't that much about the root game. The last time I flashed a firmware was on my note 3 after I bricked it. Then rerooted and got on to biggins rom which was great ut I never understood or learned how to use xposed. Anyway, I downloaded Modest Rom, PJ2 _STOCK .tar and am downloading cpl1_tar but I know that once I flash bpa1 firmware which puts the phone back on 5.1.1. I see your roms are 6.0.1 roms, after I flash the bpa1, will the bootloader be unlocked? If so can I then just flash the cpla1_tar or is that not a full firmware? or use one of the two 6.0.1 firmwares from where I found the cpa1? Are the kernels different from 6.0.1 and 5.1.1 and where to find the downloads?? I appreciate the tips especially coming from a develpoer and i'm happy to make a donation- I'm not sure how?
Thanks again!
tjmethod said:
I really dont know the difference... from what I remember a kernel is the layer between the software and the hardware- a key component of the os. I'm guessing the permissive ones can be used for different roms or firmware? You can probably tell I really don't that much about the root game. The last time I flashed a firmware was on my note 3 after I bricked it. Then rerooted and got on to biggins rom which was great ut I never understood or learned how to use xposed. Anyway, I downloaded Modest Rom, PJ2 _STOCK .tar and am downloading cpl1_tar but I know that once I flash bpa1 firmware which puts the phone back on 5.1.1. I see your roms are 6.0.1 roms, after I flash the bpa1, will the bootloader be unlocked? If so can I then just flash the cpla1_tar or is that not a full firmware? or use one of the two 6.0.1 firmwares from where I found the cpa1? Are the kernels different from 6.0.1 and 5.1.1 and where to find the downloads?? I appreciate the tips especially coming from a develpoer and i'm happy to make a donation- I'm not sure how?
Thanks again!
Click to expand...
Click to collapse
Hey buddy, did you get it figured out? I broke my arm at work on Sunday and of course it's my right arm so I'm having some issues responding back on my note with one hand. I bet I've dropped this thing 20 times already.
kevintm78 said:
Hey buddy, did you get it figured out? I broke my arm at work on Sunday and of course it's my right arm so I'm having some issues responding back on my note with one hand. I bet I've dropped this thing 20 times already.
Click to expand...
Click to collapse
Oh man that sucks- hopefully they gave you some good pain meds. Anyway, I havent taken th plunge yet- once I get on to 5.1.1 then twrp, I want to go on to 6.0.1 but am unsure as to what point the bootloader is unlocked or exactly what to do to upgrade to 6.0.1 once I crack the bl. I just dont want to go through the dreaded set up everything twice.