After upgrading to 5.1.1 using odin because 5.0.2 was rooted, my T-Mobile edge has issues. Dropping calls (I use AT&T it is unlocked), keyboard not working (Typing random letters that I dont even touch), and a bit laggy (I did have it factory reset). Also, I read this thread:
http://forum.xda-developers.com/tmo...recovery-twrp2-8-6-0-g925t-5-1-1-of6-t3143002
and it says:
"Unlocked Phones: If you have unlocked your phone, you might run into problems with 5.1.1. There have been reports of phones stuck in a boot-loop when upgrading from 5.0.2 -> 5.1.1 when the phone has been unlocked or EFS/IMEI has been tampered with. Combine this with the new "FRP LOCK" (Factory Reset Protection) in 5.1.1, and you might find yourself with a complete brick with no warranty. This issue may or may not have anything to do with rooting or custom firmware:"
So is it safe for me to root/get TWRP? My phone is unlocked but I am kind of afraid with this FRP Lock. And is there a way to fix my problems? Maybe all the bloatware is causing this or I can get some ROM to fix it
smoosani97 said:
After upgrading to 5.1.1 using odin because 5.0.2 was rooted, my T-Mobile edge has issues. Dropping calls (I use AT&T it is unlocked), keyboard not working (Typing random letters that I dont even touch), and a bit laggy (I did have it factory reset). Also, I read this thread:
http://forum.xda-developers.com/tmo...recovery-twrp2-8-6-0-g925t-5-1-1-of6-t3143002
and it says:
"Unlocked Phones: If you have unlocked your phone, you might run into problems with 5.1.1. There have been reports of phones stuck in a boot-loop when upgrading from 5.0.2 -> 5.1.1 when the phone has been unlocked or EFS/IMEI has been tampered with. Combine this with the new "FRP LOCK" (Factory Reset Protection) in 5.1.1, and you might find yourself with a complete brick with no warranty. This issue may or may not have anything to do with rooting or custom firmware:"
So is it safe for me to root/get TWRP? My phone is unlocked but I am kind of afraid with this FRP Lock. And is there a way to fix my problems? Maybe all the bloatware is causing this or I can get some ROM to fix it
Click to expand...
Click to collapse
There is no rom to fix this, bloat will not cause these symptoms, since you are on odin 5.1.1 you won't have an option to unlock bootloader (disable frp) .
Rooting or installing trwp could be risky and dangerous, one wrong flash and phone security can trigger frp, and that would be the end of your S6edge.
Your safest procedure would be to odin stock Samsung firmware and wait for appropriate official updates. Stock firmware will fix all your issues.
Pp.
PanchoPlanet said:
There is no rom to fix this, bloat will not cause these symptoms, since you are on odin 5.1.1 you won't have an option to unlock bootloader (disable frp) .
Rooting or installing trwp could be risky and dangerous, one wrong flash and phone security can trigger frp, and that would be the end of your S6edge.
Your safest procedure would be to odin stock Samsung firmware and wait for appropriate official updates. Stock firmware will fix all your issues.
Pp.
Click to expand...
Click to collapse
I did Odin stock 5.1.1. Ever since then its been happening. But for some reason when I did stock 5.1.1, my apps were still there. I would expect it to be a full wipe so I manually factory resetted after.
smoosani97 said:
I did Odin stock 5.1.1. Ever since then its been happening. But for some reason when I did stock 5.1.1, my apps were still there. I would expect it to be a full wipe so I manually factory resetted after.
Click to expand...
Click to collapse
I would reflash stock trough smartswitch that will wipe the phone clean before flashing
Sent from my SM-G925T using Tapatalk
PanchoPlanet said:
There is no rom to fix this, bloat will not cause these symptoms, since you are on odin 5.1.1 you won't have an option to unlock bootloader (disable frp) .
Rooting or installing trwp could be risky and dangerous, one wrong flash and phone security can trigger frp, and that would be the end of your S6edge.
Your safest procedure would be to odin stock Samsung firmware and wait for appropriate official updates. Stock firmware will fix all your issues.
Pp.
Click to expand...
Click to collapse
I wish I could offer any advice, but I just wanted to let you know that my experience with 5.1.1 echoes yours entirely, with the lovely addition of it getting so hot I cannot hold it and the battery draining within two hours.
**sigh**
-Collin-
papi5120 said:
I would reflash stock trough smartswitch that will wipe the phone clean before flashing
Sent from my SM-G925T using Tapatalk
Click to expand...
Click to collapse
Would I need to have OEM switched on or off? I hear some people that try flashing and screwed up their phone with it off? Like if I use SmartSwitch, will I run into any FRP issues and screw up my phone?
Related
Hello,
I just bought my first Galaxy device (had a CDMA LG for a while, and I have a Nexus Tablet), and I am looking at how to get this new phone set up right. I bought my i747 retail, so I was unable to unlock it. However, now I'm struggling with finding the right method for upgrading, rooting, etc. I know nothing about knox or any of these Samsung intricacies. Could someone please give me a little guidance on how to go about getting to the OS and status that I'm looking for? This is what I've done so far:
Came unrooted with 4.1.2 stock rom
Unlocked using legit unlock code
Tried OTA updates, but none were available (must be because of unlock)
Rooted w/ ODIN using 4.1.1 file based of MrRobinson method. (http://forum.xda-developers.com/showthread.php?t=1739426)
Now I keep getting popups like process. ... .acore,media, etc. stopped.
I'm looking to ideally get a custom recovery (either CWM or TWRP, whichever is better) and either kitkat Touchwiz or possibly kitkat nexus stock (I read somewhere that it was possible). Also, i just bought it, and have the code still, so I don't mind deleting everything if needed. Regardless, I'd like the ability to get it back to pure stock with no flash counter (I have a manufacturer's warranty I want to use if need be).
Could someone please just give me a little guidance? I'm pretty capable with rooting, etc., so you'd only need to lead me to other threads, etc. that will take me where I want to go. Thank you very much.
Before flashing or doing anything else, confirm the bootloader on your phone. Download and install the Samsung Phone Info app from the playstore and post your bootloader.
audit13 said:
Before flashing or doing anything else, confirm the bootloader on your phone. Download and install the Samsung Phone Info app from the playstore and post your bootloader.
Click to expand...
Click to collapse
Well, the bad news is I already flashed using MrRobinson's instructions, and now my phone is barely workable, as things like process.android.media and Touchwiz keep crashing. I was able to install the info app though, and my bootloader is listed as I747UCDLK3. Thanks again though, and let me know what else you need from me.
I recommend starting over by flashing the stock AT&T 4.1.1 firmware from sammobile. Once flashed, boot the phone and make sure your phone is sim unlocked. If it isn't sim unlocked, unlock it using the free method or your unlock code.
http://www.sammobile.com/firmwares/database/SGH-I747/
After sim unlocking, run OTA updates until you have the latest stock AT&T ROM on your phone. Upgrading the phone's bootloader and modem is the easiest way to do it for someone that is new to the phone and custom ROMs.
audit13 said:
I recommend starting over by flashing the stock AT&T 4.1.1 firmware from sammobile. Once flashed, boot the phone and make sure your phone is sim unlocked. If it isn't sim unlocked, unlock it using the free method or your unlock code.
http://www.sammobile.com/firmwares/database/SGH-I747/
After sim unlocking, run OTA updates until you have the latest stock AT&T ROM on your phone. Upgrading the phone's bootloader and modem is the easiest way to do it for someone that is new to the phone and custom ROMs.
Click to expand...
Click to collapse
Thank you, but wouldn't OTA updates install Knox, which would basically void my warranty if I tried to flash anything after that? And, I've checked for OTA updates twice, once on 4.1.2 and on 4.1.1, and both times it said my software was up to date.
I spoke with StoneyJSG about my situation, and he suggested that I go to stock 4.1, root w/ saferoot, then flash a kitkat custom rom without Knox through TWRP. That way, I could use triangle away and flash stock unrooted if I needed to send it in.
Although, I'm not sure if I should do that, as I thought I read that you need to update the radio and bootloader first before you can install a custom kitkat rom from jelly bean, but I'm still not entirely sure how that works.
The most recent release of many custom ROMs will not work but you may not have a signal without an updated modem and you should not be running updated modems on an older bootloader. Doing this could brick your phone.
With a rooted system, OTA updates will not work.
Thank you again for helping walk me through the minutia around this phone.
I think I have a much better understanding of everything now. I read the following article on Knox (http://omegadroid.co/wanted-knox-void-warranty-0x1/) and with an understanding of that, I get now that there is no way to load any custom rom on 4.3 or higher without losing my warranty.
So, basically my options are to stay at 4.1 and flash whatever, using triangle away to erase my tracks. Or, I could update to 4.3, but only be able to use saferoot/towelroot, otherwise I'd trip the warranty void. But, if all I did use was towelroot (no custom recovery or rom), then I could just unroot the phone using the full unroot option in SuperSU and send it on in for service if needed, right?
Also, I did unroot my phone and did a factory reset, so it's back at 4.1.1 and unrooted. Yet, I still do not see any software updates available from Samsung. I even plugged it into Kies, and nothing (http://i.imgur.com/E0xPGpf.png). Does anyone know why this could be? Does it have something to do with my not having a carrier for the phone yet? I'm sorry for all the questions, but I do appreciate your help.
jateed said:
Thank you again for helping walk me through the minutia around this phone.
I think I have a much better understanding of everything now. I read the following article on Knox (http://omegadroid.co/wanted-knox-void-warranty-0x1/) and with an understanding of that, I get now that there is no way to load any custom rom on 4.3 or higher without losing my warranty.
So, basically my options are to stay at 4.1 and flash whatever, using triangle away to erase my tracks. Or, I could update to 4.3, but only be able to use saferoot/towelroot, otherwise I'd trip the warranty void. But, if all I did use was towelroot (no custom recovery or rom), then I could just unroot the phone using the full unroot option in SuperSU and send it on in for service if needed, right?
Also, I did unroot my phone and did a factory reset, so it's back at 4.1.1 and unrooted. Yet, I still do not see any software updates available from Samsung. I even plugged it into Kies, and nothing (http://i.imgur.com/E0xPGpf.png). Does anyone know why this could be? Does it have something to do with my not having a carrier for the phone yet? I'm sorry for all the questions, but I do appreciate your help.
Click to expand...
Click to collapse
What is your cell service? If not AT&T, you will never get OTA.
Whether you get OTA can vary from carrier to carrier and phone to phone in my opinion.
I have a Rogers HTC One X that gets OTA updates from HTC even though I am on the Bell network.
I have a Bell S3 that is running on the Rogers network and it receives OTA updates from Bell even though it has a Rogers sim card in the phone.
I have a Telus Moto G running on the Bell network and it received the Telus KK OTA update while connected to the Bell network.
audit13 said:
Whether you get OTA can vary from carrier to carrier and phone to phone in my opinion.
I have a Rogers HTC One X that gets OTA updates from HTC even though I am on the Bell network.
I have a Bell S3 that is running on the Rogers network and it receives OTA updates from Bell even though it has a Rogers sim card in the phone.
I have a Telus Moto G running on the Bell network and it received the Telus KK OTA update while connected to the Bell network.
Click to expand...
Click to collapse
Well, I have an AT&T model which I unlocked and will be putting on Cricket at the end of the week (when my plan month is set to end). Right now there's no SIM in it, and I've been doing everything over wifi. I looked up whether the carrier had something to do with the OTAs, and I was told that Samsung sent the updates out, not AT&T, so I figured that the carrier info was irrelevant. I now wonder what my options are.
Can I manually flash 4.3 stock without tripping the knox warranty void?
Does Towelroot/Xposed framework trip the Knox void flag?
If I can update to 4.3/4.4 and root without tripping the knox flag, I might just manually update and just run towelroot and xposed to modify my OS the best I can until my warranty runs out.
If I can't root it at all once I'm on 4.3+, then I'll just sit on 4.1.1 for a few months until I can't stand it anymore and just void the warranty anyway.
Thanks again everyone. This whole knox/binary counter thing is not something I dealt with on my CDMA LG or Nexus, so I was totally in the dark about how it all worked. This is also my first GSM phone, so all those intricacies are new to me too. Once I know about manually flashing stock and running towelroot/xposed, I think I'll be in good shape.
Flashing the stock 4.3 ROM should not trip the counter as long as you do not need to install a custom recovery to flash it.
Apparently, the latest KK stock ROM cannot be rooted using Towelroot.
If you want a custom ROM, use one that will work with a 4.1.1 bootloader and modem. Once on 4.3 or higher, it's a little harder to recover from a soft brick.
audit13 said:
Flashing the stock 4.3 ROM should not trip the counter as long as you do not need to install a custom recovery to flash it.
Apparently, the latest KK stock ROM cannot be rooted using Towelroot.
If you want a custom ROM, use one that will work with a 4.1.1 bootloader and modem. Once on 4.3 or higher, it's a little harder to recover from a soft brick.
Click to expand...
Click to collapse
Excellent. If I did flash stock, i would just use ODIN, then factory reset to wipe the caches. And that's good to know about the KK rom, as I would probably update straight to 4.4 if at all (I've read a lot of bad things about 4.3 on the S3), but not if it means I cannot root safely and cleanly.
I'll check out the custom roms for 4.1.1. I know that flashing the rom and/or a custom recovery will trip the binary counter, but I can just use triangle away to clean that up. Do you know if there is a list of custom 4.1.1/4.1.2 roms somewhere, or do I need to scour the older threads here?
Thank you very much audit13 (thanks to StoneyJSG and pre4speed as well). You have been immensely helpful and really brought me up to speed on everything surrounding S3 customization. Needless to say it's way more complicated than what I've dealt with from LG and Google/Asus. (I mean, i could root my nexus with a single click using Wugfresh's toolkit)
4.1.1 is the only complete stock ROM that AT&T released for flashing via Odin.
4.3 ROMS and higher were prepared by XDA members for flashing in either a custom recovery or Odin.
audit13 said:
4.1.1 is the only complete stock ROM that AT&T released for flashing via Odin.
4.3 ROMS and higher were prepared by XDA members for flashing in either a custom recovery or Odin.
Click to expand...
Click to collapse
Oh, so what other way can you flash a stock rom, if not through ODIN or a custom recovery? Regardless, it seems as though I really should not dive into 4.3+ until I'm ready to concede that my warranty is over. There are just too many potential pitfalls and headaches.
On the lighter side, I've found a few 4.1.2 based custom roms that have some promise. I'm going to post them here in case anyone has opinions on them, or if someone else in my situation sees this thread and wants to go custom 4.1 too:
Hyperdrive RLS16
http://forum.xda-developers.com/showthread.php?t=2176793
Slim Bean-d2
http://forum.xda-developers.com/showthread.php?t=1865262
Jedi Academy
http://www.teamandroid.com/2013/12/...oid-412-jedi-academy-jelly-bean-custom-rom/2/
Jelly ‘Beans’
http://www.teamandroid.com/2013/04/...ndroid-412-att-galaxy-s3-sgh-i747-custom-rom/
I was also torn when I got my s3 that was running 4.1.2. I downgraded to 4.1.1, sim unlocked the phone, used it on stock 4.1.2 for about a week to make sure everything was working, hardware wise, upgraded to stock 4.4.2, installed a custom recovery and a custom ROM. I wasn't too concerned about the warranty since I got the phone as a free upgrade and had no intention of using the s3 as my daily phone. I kept it as a backup until my niece needed and phone and then it went to her. It's been over a year and there are still no problems with the phone.
Hello,
I'm a noob but usually try to fix this kind of issues on my own, looking at the boards, following tutorials, learning, but this time I think I'm not able to find a solution on my own so I'm asking for advice here.
Some time ago I installed cyanogenmod 10.1 on my Note 2 LTE and was happy with it for some month, than last week I tried to upgrade to cm12.1 It worked but there where some issues and bugs, mainly I wasn't able to swap internal/external sd cards.
So I decided to go back to latest available stock rom 4.4.2 from sammobile.
Here is where the problem starts. The stock 4.4.2 resulter in a bootloop, tried cache/dalvik/factory reset, flash again, whipe again.. nothing.
The phone is not able to get past the white label "Samsung Note 2 gt-n7105" screen. It goes black than the white label again and again.
It doesn't even get to the Samsung animated logo.
Ok bottloop, no problem, try to flash again something else.
I tried different Custom roms, different kernels, different flashing methods. I can flash anything with no problem but every time a get a bootloop.
During the various attempts knox fired, but I don't care. I don't know if this could be the cause.
Actually the only firmware that works is the original oldest STOCK 4.1.2, every other stock firmware past that or any custom rom is bootlooping the same way. To fix I only can reinstall stock 4.1.2 with odin.
I really need any advice or hint.
At the moment my goal is to get at least to stock 4.3 but I cant.........
Thanks!
When you first bought your phone, did it come with Knox?
ErnestChia said:
When you first bought your phone, did it come with Knox?
Click to expand...
Click to collapse
nope it doesn't existed before, but now I can see it when I boot in download mode "knox warranty void:1"
Try to get the latest firmware available via kies ,that worked for me
http://forum.xda-developers.com/showthread.php?t=2088809/[URL]
From what you've described, I think the Stock ROM 4.4.2 from Sammobile contained a bootloader update. So when you flashed this ROM, it updated your bootloader from the non-Knox version to the Knox version.
I am very unfamiliar with the technical details of Knox, but I think the new Knox bootloader is causing your bootloop problem.
However, I don't know why 4.1.2 works when everything else doesn't work!
Can you check the Stock ROM 4.4.2, and see whether it really contains a bootloader update?
mysuperdonghae said:
Try to get the latest firmware available via kies ,that worked for me
http://forum.xda-developers.com/sho...can flash cm10, 11 and 12 with no issue too..
Click to expand...
Click to collapse
misthero said:
I think so, there is a boot.im, anyway I also discovered that I can flash cm10, 11 and 12 with no issue too..
Click to expand...
Click to collapse
Since a boot.img is present, it means that it would flash your boot partition. So now we know for sure that when you attempted to flash the Stock ROM 4.4.2, your bootloader was changed to the Knox version.
So the lesson here is: before you flash anything via ODIN, always check to see if there is a bootloader update. Usually you don't want to be changing the bootloader on your phone.
***
So now there are 2 possible ways to reach your goal:
1) Keep your new bootloader and see whether you can get Stock 4.3 or Stock 4.4.2 running on your phone
2) Try to restore your old bootloader
As I said earlier, I'm not familiar with the technical details of Knox, so I'm not sure how to get Stock 4.3 or Stock 4.4.2 running on your phone when your Knox indicator is already 0x1. You need someone else to help you.
And you can only restore your old bootloader if you happen to have made a copy of your boot partition before you flashed the Stock ROM 4.4.2. Even if you did have a copy of your original boot partition, I'm not confident with helping you to restore your old bootloader. You need someone else to help you in this case too.
Conclusion: I don't think I can help you to solve your problem I'm sorry. Hopefully someone else who is more of a pro than me will come along to help you out.
Good luck!
Hey,
Still a bit of a noob to the whole rooting process and navigating XDA forums, so I'm having trouble finding the information *I think* I should be looking for. Basically, my phone's just begun crashing periodically, multiple times a day: anything from Camera, Process System, Touchwiz Home Launcher, or Samsung Apps have "stopped working" / "not responding" before. Of course, my phone's warranty has expired, but my contract isn't up so an AT&T Store wont re-image it for me :crying:
Even I can tell, at this point, that it's either my OS that's failing, or it's my hardware. I figured the easiest way to test this would be to put some stable CyanogenMod on it.
The information I'm looking for is: "is this possible?"
AT&T Samsung Galaxy Note 4
SM N910A UCU2DOI2
Currently @ 5.1.1
Thanks for reading,
~Vita.
No it is NOT possible to use any form of custom firmware or to root this device. It has a locked bootloader that has yet to be cracked open and the future of that happening os very bleak to non existant.
As for reimaging the device go to the note 4 at&t general section on the forum and read up on using odin and the 5.1.1 image posted there it will wipe the phone and format yhe system and data partitions and reinstall it like a new phone just like at&t would do or the manufacturer if you sent it to them.
Good luck
Thanks for the response.
Sorry for the dumb question, but isn't Odin able to flash any firmware onto a device? The "locked bootloader" means that only the stock OS may be reinstalled? Why is this...
Also, it seems unlock progress is being made on the N910V. Maybe hope?
Thanks for mentioning Odin, I'll try re-imaging the phone.
~Vita.
Ricovita said:
Thanks for the response.
Sorry for the dumb question, but isn't Odin able to flash any firmware onto a device? The "locked bootloader" means that only the stock OS may be reinstalled? Why is this...
Also, it seems unlock progress is being made on the N910V. Maybe hope?
Thanks for mentioning Odin, I'll try re-imaging the phone.
~Vita.
Click to expand...
Click to collapse
Well the problem is the kernel the bootloader prevents the devs from using an unsecure kernel (one not created and signed by at&t) on the phone if one is used the phone stops boot and says it is an unsecure non at&t kernel and to take thenphone to at&t store.
Odin can only write the firmware versiom that is currently on this phone in this case it is 5.1.1 if you flash any other note 4 versoin such as 4.2.2 it will brick.
Sm-910a flash example
Update ver Official at&t 5.1.1 / currently on phone 5.0.1 or 5.1.1 = good
Update ver (downgrade)oficcial at&t 4.2.2 / currently on phone 5.0.1 or 5.1.1 = brick not good or odin fail
Update from another carrier such as tmobile or verizon for 910t 910v 910g = fail (do not attempt)
Until oir boot loader is unlocked there is nothing we can do to mod or use custom firmware on this phone any attempt leads to a brick requiring using odin to re-flash the latest firmware (5.1.1 at this time) in order to make the phone functional again.
giga8547 said:
Until oir boot loader is unlocked there is nothing we can do to mod or use custom firmware on this phone any attempt leads to a brick requiring using odin to re-flash the latest firmware (5.1.1 at this time) in order to make the phone functional again.
Click to expand...
Click to collapse
So from what I understand, I could use Odin to flash the 4 files which correspond to the specific AT&T 5.1.1 SM-901A version of my phone (which is exactly what I have) to re-image the device and make it functional again. The problem is, I cannot find these devices on sammobile D:
Could someone direct me to these files? Or are they not out because AT&T sucks? Or, what.
~Vita.
Ricovita said:
So from what I understand, I could use Odin to flash the 4 files which correspond to the specific AT&T 5.1.1 SM-901A version of my phone (which is exactly what I have) to re-image the device and make it functional again. The problem is, I cannot find these devices on sammobile D:
Could someone direct me to these files? Or are they not out because AT&T sucks? Or, what.
~Vita.
Click to expand...
Click to collapse
Look in odin files in progress thread.
Sent from my SAMSUNG-SM-N910A using Tapatalk
Is it possible to downdraft from 5.1.1 to 5.0.1
firebird7880 said:
Is it possible to downdraft from 5.1.1 to 5.0.1
Click to expand...
Click to collapse
I think so, I don't know for sure but we've been able to Odin from various 5.0 Lollipop releases back to KitKat so should be fine.
downgrading from 5.1.1 or 5.0.1 to kitkat is possible but with many many problem but form 5.1.1 to 5.0.1 i don't know maybe phone will stuck or boot loop
thanks finitetime for your reply
other question are there any news about root for 5.1.1 n910a
help
my att note 4 is unlocked and it still won't let me install custom rom's
mouseman1 said:
my att note 4 is unlocked and it still won't let me install custom rom's
Click to expand...
Click to collapse
I am sure that you are referring to a sim unlock. A sim unlock and unlocked bootloader are two completely different entities. To flash a custom rom you will need to have your bootloader unlocked, which is something that a few of us are currently working on. Until then, no custom roms can be flashed on the att variant Note 4s. Take care
the boot loader says Qualcom secure boot : disabled ?
in the boot loader screen ?
mouseman1 said:
my att note 4 is unlocked and it still won't let me install custom rom's
Click to expand...
Click to collapse
Your phone is SIM UNLOCKED which has NOTHING to do with root, bootloader, or custom roms.
Sent from my SAMSUNG-SM-N910A using Tapatalk
mouseman1 said:
the boot loader says Qualcom secure boot : disabled ?
in the boot loader screen ?
Click to expand...
Click to collapse
Sorry, was off the forum for the weekend. Spexwood was correct, that is sim unlock. Qualcom is for the sim IE network. Take care.
Root is possible btw
Root is possible if youre willing to dedicate 10-30 hours of repititive root fails
How?
Press Buttons said:
Root is possible if youre willing to dedicate 10-30 hours of repititive root fails
Click to expand...
Click to collapse
How is root possible? What's the process ?
Reverting to stock for replacment (on "developer edition")? Revert CID/need for PIT?
Hey all,
I gotta send N4 to verizon for replacement (no 4G anymore) and I am trying to get back to as close to stock as possible. My big questions before I go about the final Odin restore flash are:
1. Will the fact that I changed it to developer edition (not developer options) by changing the CID matter at all? Do I need to undo my developer edition tweak as well? Worried about bricking by flashing the full stock images on a "developer edition".
2. Do I need to use a PIT during flashing, to really get it all fully stock?
3. With regards to TWRP, will flashing a stock image revert back to stock android recovery as well? Do I need to mess with TWRP before flashing via Odin?
4. Is it hopeless to try and remove the "custom" pad lock on boot? Is there any way to achieve that?
5. Is it better to use the "Stock" images from the community or should I use those from SamMobile?
Currently on a nandroid restore of my unrooted, fresh install of 6.0.1. Baseband ver CPF3, build CPD1 (using bootlader from hsbadr SafeUpgrade to MM).
Why do you need to send it to Verizon and to get fixed. Have you tried flashing back to a stock ROM and checking for 4g.
I lost my 4g a while back it turned out to be my sim tray and was a 5 dollar part and was 10 minutes to mix.
celticpride34 said:
Hey all,
I gotta send N4 to verizon for replacement (no 4G anymore) and I am trying to get back to as close to stock as possible. My big questions before I go about the final Odin restore flash are:
1. Will the fact that I changed it to developer edition (not developer options) by changing the CID matter at all? Do I need to undo my developer edition tweak as well? Worried about bricking by flashing the full stock images on a "developer edition".
2. Do I need to use a PIT during flashing, to really get it all fully stock?
3. With regards to TWRP, will flashing a stock image revert back to stock android recovery as well? Do I need to mess with TWRP before flashing via Odin?
4. Is it hopeless to try and remove the "custom" pad lock on boot? Is there any way to achieve that?
5. Is it better to use the "Stock" images from the community or should I use those from SamMobile?
Currently on a nandroid restore of my unrooted, fresh install of 6.0.1. Baseband ver CPF3, build CPD1 (using bootlader from hsbadr SafeUpgrade to MM).
Click to expand...
Click to collapse
never heard of a fried phone where 4G only does not work. Are you getting any signal? Try going back to a mostly stock Rom.
Plus if you ever rooted, you tripped knox and Efuse. Not likely that the would just overlook that
LumberjackZac said:
never heard of a fried phone where 4G only does not work. Are you getting any signal? Try going back to a mostly stock Rom.
Plus if you ever rooted, you tripped knox and Efuse. Not likely that the would just overlook that
Click to expand...
Click to collapse
Yeah, didnt make sense to me either. Odin'd back to CPD1 and signaling was fine again. As soon as I throw a ROM at it (any 7.0 AOKP and tried Jasmine which is 6.0), the radios get drunk. Seems like a common issue for some. Oddly enough Emotion build 109 worked flawlessly on 4G, once I updated to 328 I've been unable to get 4G back, where texts work). Yeah, Knox 0x1 tripped, I was thinking it was hardware so was toying with taking the gamble that they wouldn't check on such an old phone.
celticpride34 said:
Yeah, didnt make sense to me either. Odin'd back to CPD1 and signaling was fine again. As soon as I throw a ROM at it (any 7.0 AOKP and tried Jasmine which is 6.0), the radios get drunk. Seems like a common issue for some. Oddly enough Emotion build 109 worked flawlessly on 4G, once I updated to 328 I've been unable to get 4G back, where texts work). Yeah, Knox 0x1 tripped, I was thinking it was hardware so was toying with taking the gamble that they wouldn't check on such an old phone.
Click to expand...
Click to collapse
how close did they look ? triangle away is cosmetic and wont withstand a logcat but might fool dip**** behind the verizon counter
After downgrading from the 10 leaked beta to Pie by changing slots and factory resetting, I can't OTA update. I have a locked bootloader and model TA-1050. Do I need to "wipe" the other partition that 10 is installed on so that it can be used for upgrades?
Thanks in advance.
Yeah, i had the same problem after trying out some custom roms and after switching to the stock slot, i couldn't OTA anymore. The only way to fix it is to reflash the stock firmware and start updating again.. which, yes, requires a unlocked bootloader. I really recommend everyone to unlock it. I can't give you any links to the service unfortunately but all i can say is that's really easy and you don't have to anything except to accept the unlock on your phone.
Gravarty said:
Yeah, i had the same problem after trying out some custom roms and after switching to the stock slot, i couldn't OTA anymore. The only way to fix it is to reflash the stock firmware and start updating again.. which, yes, requires a unlocked bootloader. I really recommend everyone to unlock it. I can't give you any links to the service unfortunately but all i can say is that's really easy and you don't have to anything except to accept the unlock on your phone.
Click to expand...
Click to collapse
How can I reflash the stock firmware? Would it be enough to update through recovery to the leaked 10 build?