Related
Hello,
I am sending my S2 back to Samsung because of the camera, and curently on 2.3.4 and rooted, are their anything i can do to tell them that i did not mess with the phone, and I bought the phone from Bell unlocked
lethal111 said:
Hello,
I am sending my S2 back to Samsung because of the camera, and curently on 2.3.4 and rooted, are their anything i can do to tell them that i did not mess with the phone, and I bought the phone from Bell unlocked
Click to expand...
Click to collapse
Revert it back to stock for a start means using Odin to flash the stock rom. Do you know what rom it was on when it was stock? Or did it have Bell Branding on it?
http://forum.xda-developers.com/showthread.php?t=1075278
Good Luck
I would remove root, but as long as you didnt flash the phone you should be fine.
I say flash because the system has an internal flash counter, samsung can tell if you've been flashing your phone
what do u guys mean flash? and it did not have a bell branding
Flash means install a firmware or part of a firmware.
Rooting voids warranty so you need to remove root by flashing a stock rom .
Reset the custom rom counter with USB jig .
jje
I had a similar problem, I'd rooted the phone and had the yellow warning triangle when turning the phone on.
So I flashed a stock rom (the original one that was installed when I bought the phone) using odin and this solved the problem, the warning triangle had gone, the phone was like new.
I too had to send one back for Warranty repair, it had been rooted and custom roms installed a number of times. I reset the counter using a USB jig (Download mode jig which resets the rom counter), and reinstalled the Stock Vodafone ROM. They did what they did and sent the phone back to me, no questions asked. If you have had custom roms on there rather than stock ones with non-stock kernels I would advise getting the jig.
S
I removed the Yellow triangle, is it still recommended for me to use the jig
lethal111 said:
I removed the Yellow triangle, is it still recommended for me to use the jig
Click to expand...
Click to collapse
Yes mate u have to, cause removing the triangle it's not going to reset the flash counter
Sent from my GT-I9100 using Tapatalk
can any1 show me the jig thread?
lethal111 said:
can any1 show me the jig thread?
Click to expand...
Click to collapse
Here is a video http://www.youtube.com/watch?v=Rdn5GoRjhn0
Link :http://forum.xda-developers.com/showthread.php?t=841512
I bought one off Ebay
Don't bother resetting Custom Binary counter!
I have done warranty replacement and was never asked a question why I had flashed custom ROM 7 times!
You just flash official ROM back and you should be good to go folks. Infact NOWHERE in Samsung's documentation it says you can't root or install custom ROM on the phone or it would void the warranty! Even when we get the warning while entering download mode, it never tells you that it will void the warranty!
So essentially there should be no worry for warranty claims even when you accidentally left custom ROM with root on the phone while doing warranty claims. Let me know if ANYONE out here had a different experience and I have NEVER seen claims getting rejected for these reasons!!!
Prankey said:
I have done warranty replacement and was never asked a question why I had flashed custom ROM 7 times!
You just flash official ROM back and you should be good to go folks. Infact NOWHERE in Samsung's documentation it says you can't root or install custom ROM on the phone or it would void the warranty! Even when we get the warning while entering download mode, it never tells you that it will void the warranty!
So essentially there should be no worry for warranty claims even when you accidentally left custom ROM with root on the phone while doing warranty claims. Let me know if ANYONE out here had a different experience and I have NEVER seen claims getting rejected for these reasons!!!
Click to expand...
Click to collapse
Agreed! I got my screen replaced even i was on custom rom. They flashed the stock rom back thou
But i quess you can't do warranty claims if you take your bootlooping phone to repair centre caused by flashing custom roms.
I've been way out of the loop on Android for a while and I'm just now getting back.
First of all, does flashing something that will get me KNOX mean anything if I don't care about my warranty and can I still flash custom ROMs as I please?
Once that's answered, I need an easy way to get back to a stock (Preferably rooted with TWRP) ROM so I can fix my data connection. I've tried a few ROMs so far but they all seem to be failing
Heya,
I need to returns my phone to as-purchased-state, which means if I am not missing anything - unroot, stock rom, stock recovery
I have rooted the phone, installed custom ROM (cloudy) and TWRP.
On my previous phone, samsung s2, the download mode had a flash counter that indicated how many times I flashed a rom.
On my LG G2, the download mode just says "rooted".
1) So where do I get a stock rom from?
2) Where do I get stock recovery?
3) How do I wipe any evidence of root?
4) In what order do I need to do everything?
I did google and came up with some of these answers, but I put my trust in XDA and hoping I won't f*ck my phone up by doing something in the wrong order.
Thanks!
Sorry this isn't an answer, but it might help you get an answer.
You may want to remove the part where you are admitting to warranty fraud.
Even though this is a hacking forum, people still disapprove of it.
Also, this might be what you're looking for:
http://forum.xda-developers.com/showthread.php?t=2432476
PoOoZaQ said:
Heya,
I need to activate my phone guarantee and wondering what are the steps one might take in order for them to not void my guarantee.
I have rooted the phone, installed custom ROM (cloudy) and TWRP.
On my previous phone, samsung s2, the download mode had a flash counter that indicated how many times I flashed a rom.
On my LG G2, the download mode just says "rooted".
1) So where do I get a stock rom from?
2) Where do I get stock recovery?
3) How do I wipe any evidence of root?
4) In what order do I need to do everything?
I did google and came up with some of these answers, but I put my trust in XDA and hoping I won't f*ck my phone up by doing something in the wrong order.
Thanks!
Click to expand...
Click to collapse
Use the kdz method to return to stock. Its in the dev forum. You need the drivers for your phone, the kdz firmware, lgflash tool. All can be found in the dev section.
Hello there,
So, I have a Samsung Galaxy S5 G900R4 with U.S. Cellular. I've heard of rooting your phone, and I decided I'd give it a try. Now, the rooting went fine, and the phone was working like a charm, until I started to have some issues. SuperSU needed to update its binary, and I allowed it to try, but it continued to tell me that it could not update it. Hence, I let it reboot when it offered. Now, for whatever reason, the phone won't boot past the U.S. Cellular 4G logo that appears, it just sits there on that screen.
Now so far, I haven't been able to find anyone that has encountered this specific problem, as most people say their soft-bricks are bootlooping and whatnot. I'm not sure if my specific case is technically a soft brick, or something else, but I wanted to just return it to stock format. I loaded up Odin again, downloaded the 1.5g firmware file, and I got the SW REV CHECK FAIL error.
I did some research, and I searched EVERYWHERE, and the closest I could find to a solution was http://forum.xda-developers.com/showthread.php?t=2798396 <-- this thread. Which makes sense, when I read it. I'm guessing the bootloader is locked on my phone, or something. The problem is that this thread is for the Galaxy S5 G900AU, and I don't have that phone.
Maybe I'm just not searching on the web enough, or I didn't search the site well enough, but I have not been able to locate a similar set of AP, CP and CSC files for my specific model.
I would really appreciate it if someone could point me in the right direction or, if the issue I'm actually having with my phone is NOT a soft-brick and there is another solution, suggest another way for me to fix the phone.
Thank you.
First off, I'd try clearing the caches from recovery
If that fails, factory reset from recovery
If that fails, (And I'm not sure about stock firmwares with ODIN & locked bootloaders) I'd try flashing stock from ODIN also
Grab stock ROMs from here
sammobile . com / firmwares / database /SM-G900R4/
Can't link it here, as SM links are not allowed - just remove the spaces
*Detection* said:
First off, I'd try clearing the caches from recovery
If that fails, factory reset from recovery
If that fails, (And I'm not sure about stock firmwares with ODIN & locked bootloaders) I'd try flashing stock from ODIN also
Grab stock ROMs from here
sammobile . com / firmwares / database /SM-G900R4/
Can't link it here, as SM links are not allowed - just remove the spaces
Click to expand...
Click to collapse
Well last night I went ahead and used recovery to clear cache, and then I did a factory reset. I just did it again, now, but I guess I'll have to download the file from SM to try. I already have a stock ROM, but I can't remember where I downloaded it from, so it may actually be a 4.4.2 ROM or something, which would explain why it won't work. I'll wait for the 5.0 ROM to download and give it a try, should take a little more than an hour and a half, then I'll report back.
Xeretius said:
Well last night I went ahead and used recovery to clear cache, and then I did a factory reset. I just did it again, now, but I guess I'll have to download the file from SM to try. I already have a stock ROM, but I can't remember where I downloaded it from, so it may actually be a 4.4.2 ROM or something, which would explain why it won't work. I'll wait for the 5.0 ROM to download and give it a try, should take a little more than an hour and a half, then I'll report back.
Click to expand...
Click to collapse
Try this link, if it works, it won't work for long
Code:
http://am4-r1f4-stor08.uploaded.net/dl/800e713b-624b-4a91-a57c-1639c6b5071e
*Detection* said:
Try this link, if it works, it won't work for long
Click to expand...
Click to collapse
It worked, it's downloading now, just have to give it some time.
nice one
*Detection* said:
nice one
Click to expand...
Click to collapse
I really hope this works, when it finishes >.>
Any idea what's happening with the phone to cause it to stay at the U.S. Cellular screen?
I never let SuperSU reboot when I let it update the binaries
Could be a number of things, possibly just corrupted a file necessary for boot, but as SuperSU has root, it could be anything
I don't know the ins and outs of how SuperSU works, but I know a few carrier specific US S5s have a locked bootloader, Verizon, AT&T etc - not sure if rebooting to allow the binary update requires an unlocked bootloader, maybe that bricked it, half assed attempt at a root process failed maybe
*Detection* said:
I never let SuperSU reboot when I let it update the binaries
Could be a number of things, possibly just corrupted a file necessary for boot, but as SuperSU has root, it could be anything
I don't know the ins and outs of how SuperSU works, but I know a few carrier specific US S5s have a locked bootloader, Verizon, AT&T etc - not sure if rebooting to allow the binary update requires an unlocked bootloader, maybe that bricked it, half assed attempt at a root process failed maybe
Click to expand...
Click to collapse
As far as I know, though, U.S. Cellular has confirmed that this device has an unlocked bootloader. And besides that, if it were locked, wouldn't that have come up as an issue when I rooted the device? I used the CWM custom recovery tool.
On a similar note, I'm not even sure if the problem was a locked bootloader. It's just that, from what I've read with other people having the same issue, they solved it by excluding the BL file from the flash and instead only using the AP, CP and CSC files.
Xeretius said:
As far as I know, though, U.S. Cellular has confirmed that this device has an unlocked bootloader. And besides that, if it were locked, wouldn't that have come up as an issue when I rooted the device? I used the CWM custom recovery tool.
On a similar note, I'm not even sure if the problem was a locked bootloader. It's just that, from what I've read with other people having the same issue, they solved it by excluding the BL file from the flash and instead only using the AP, CP and CSC files.
Click to expand...
Click to collapse
If you can flash anything custom from ODIN, bootloader is unlocked, afaik, locked bootloaders require a right mess on to get anything flashed to them
To root with a locked bootloader, is easily possible if you're on a certain KitKat ROM, and use Towelroot - other than that, (From what I've read), you need to use specific tools, so it sounds like your bootloader is indeed unlocked - which makes this next ROM flash, much more likely to work using only ODIN
Use ODIN 3.10.6 though
My experience with the S5 is with an unlocked bootloader (G900F), so I can only quote what I know about locked from what I've read, but it sounds like that doesn't matter in your case
*Detection* said:
If you can flash anything custom from ODIN, bootloader is unlocked, afaik, locked bootloaders require a right mess on to get anything flashed to them
To root with a locked bootloader, is easily possible if you're on a certain KitKat ROM, and use Towelroot - other than that, (From what I've read), you need to use specific tools, so it sounds like your bootloader is indeed unlocked - which makes this next ROM flash, much more likely to work using only ODIN
Use ODIN 3.10.6 though
My experience with the S5 is with an unlocked bootloader (G900F), so I can only quote what I know about locked from what I've read, but it sounds like that doesn't matter in your case
Click to expand...
Click to collapse
It worked! Thank you so much for the help, I really appreciate it.
Well, my warranty is now void. Is there a safer way to root the phone, or should I just leave it be?
Xeretius said:
It worked! Thank you so much for the help, I really appreciate it.
Well, my warranty is now void. Is there a safer way to root the phone, or should I just leave it be?
Click to expand...
Click to collapse
Great
Flashing a stock ROM won't void your warranty, but if it is indeed void (KNOX 0x1), then just flash this with ODIN
http://download.chainfire.eu/404/CF-Root1/CF-Auto-Root-klteusc-klteusc-smg900r4.zip
Tripping KNOX only happens when you flash something not signed by Samsung, IE: A custom recovery, ROM or Kernel etc
I have the same issue, same phone I ended up flashing a custom ROM because I luckily flashed twrp before it bricked on the us cellular screen.. How did you fix this I just want to get back to stock remove my root completely
Hi all,
It's been a few yrs since I've flashed a phone (the last being my SGS1 variant) and I'm very out of practice. That being said, I just need a little help in understanding how to flash my SGS4. So far, I've had this phone for yrs and I would've jumped to custom roms as I did normally but there was the whole KNOX debacle and I didn't want to do anything to damage my phone - while within warranty. I've been out of the loop for awhile, so I need a little help in my choices here.
My phone is still running on it's original software (that's right, I completely haven't updated in yrs), so it's a 4.2.2 and the build is I9505XXUBM4 (pre-KNOX). If I am going to root, I was thinking that I should use the method from this thread: [GT-I9505 + GT-I9505G] CF-Auto-Root. Would I be right in using this method or is there something better?
Secondly, I've only ever used CWM. I'm assuming the recovery to use currently is TWRP since I've seen it brought up in a good number of threads. Can I make a nandroid with TWRP the same way it was done with CWM or do I need to find another way to backup my data?
Lastly, this is the rom I'm leaning towards; [JDCTeam][6.0.1][9 July] The Android Open Source Project MOB30M. Could I just flash this on top of my stock or do I have to update first and then flash this?
TIA for your responses.
Oniyuri said:
Hi all,
It's been a few yrs since I've flashed a phone (the last being my SGS1 variant) and I'm very out of practice. That being said, I just need a little help in understanding how to flash my SGS4. So far, I've had this phone for yrs and I would've jumped to custom roms as I did normally but there was the whole KNOX debacle and I didn't want to do anything to damage my phone - while within warranty. I've been out of the loop for awhile, so I need a little help in my choices here.
My phone is still running on it's original software (that's right, I completely haven't updated in yrs), so it's a 4.2.2 and the build is I9505XXUBM4 (pre-KNOX). If I am going to root, I was thinking that I should use the method from this thread: [GT-I9505 + GT-I9505G] CF-Auto-Root. Would I be right in using this method or is there something better?
Secondly, I've only ever used CWM. I'm assuming the recovery to use currently is TWRP since I've seen it brought up in a good number of threads. Can I make a nandroid with TWRP the same way it was done with CWM or do I need to find another way to backup my data?
Lastly, this is the rom I'm leaning towards; [JDCTeam][6.0.1][9 July] The Android Open Source Project MOB30M. Could I just flash this on top of my stock or do I have to update first and then flash this?
TIA for your responses.
Click to expand...
Click to collapse
For first you MUST update your phone, if you have root, update with odin on the latest firmware version and then flash flash recovery(cwm, twrp, philz) and flash the rom, because firmware request of the rom is android lollipop stock. Try cyanogenmod 13 nighty for this smartphone
Alessandro's said:
For first you MUST update your phone, if you have root, update with odin on the latest firmware version and then flash flash recovery(cwm, twrp, philz) and flash the rom, because firmware request of the rom is android lollipop stock. Try cyanogenmod 13 nighty for this smartphone
Click to expand...
Click to collapse
Ok, so after I root the phone, can I go straight onto CM13 or do I still have to get lollipop first and then flash CM?
I'm still trying to avoid getting KNOX on the phone.
Oniyuri said:
Ok, so after I root the phone, can I go straight onto CM13 or do I still have to get lollipop first and then flash CM?
I'm still trying to avoid getting KNOX on the phone.
Click to expand...
Click to collapse
Then you install lollipop stock, make root , flash recovery and then flash cm13
Oniyuri said:
Ok, so after I root the phone, can I go straight onto CM13 or do I still have to get lollipop first and then flash CM?
I'm still trying to avoid getting KNOX on the phone.
Click to expand...
Click to collapse
Knox does matter once you're on a custom ROM.
Most content creators recommend to use the latest modem and bootloader in order to avoid problems.
You don't necessarily have to update the whole ROM to have the newest modem and bootloader, there are Odin flashable packages.
I don't know if CF-Auto-Root works with 4.2. I know it works for 4.4 and above.
As long as you do your wipes (this means system, data, cache, dalvik) you can flash anything over anything.
Yes, you can do nandroid backups, but TWRP and CWM backups are not compatible with each other. Also, TWRP has a problem with TouchWiz backups, meaning you can make and restore a TouchWiz backup, but it either won't boot or will give you lots of errors.
GDReaper said:
Knox does matter once you're on a custom ROM.
Most content creators recommend to use the latest modem and bootloader in order to avoid problems.
You don't necessarily have to update the whole ROM to have the newest modem and bootloader, there are Odin flashable packages.
I don't know if CF-Auto-Root works with 4.2. I know it works for 4.4 and above.
As long as you do your wipes (this means system, data, cache, dalvik) you can flash anything over anything.
Yes, you can do nandroid backups, but TWRP and CWM backups are not compatible with each other. Also, TWRP has a problem with TouchWiz backups, meaning you can make and restore a TouchWiz backup, but it either won't boot or will give you lots of errors.
Click to expand...
Click to collapse
Ok, so is there a way that I could at least get to lollipop w/o getting KNOX and have a nandroid that would work or should I just OTA all the way up to current and then root and flash?
Oniyuri said:
Ok, so is there a way that I could at least get to lollipop w/o getting KNOX and have a nandroid that would work or should I just OTA all the way up to current and then root and flash?
Click to expand...
Click to collapse
Why are you so obsessed with Knox? I just told you that it won't be an issue on custom ROMs. There is no knox on custom ROMs. Knox is a Samsung thing. So, unless you plan on staying stock, there is no reason to be concerned about it. Even if you stay stock, there still is no reason to be afraid of it, it's just some security crap, and it won't affect you in any way. Why are you so afraid of it?
My device came with Knox pre-installed and it didn't do jack.
Just update if you want to update or flash a recovery (flashing custom ROMs doesn't require root, just a custom recovery) and flash your desired ROM.
GDReaper said:
Why are you so obsessed with Knox? I just told you that it won't be an issue on custom ROMs. There is no knox on custom ROMs. Knox is a Samsung thing. So, unless you plan on staying stock, there is no reason to be concerned about it. Even if you stay stock, there still is no reason to be afraid of it, it's just some security crap, and it won't affect you in any way. Why are you so afraid of it?
My device came with Knox pre-installed and it didn't do jack.
Just update if you want to update or flash a recovery (flashing custom ROMs doesn't require root, just a custom recovery) and flash your desired ROM.
Click to expand...
Click to collapse
Well, I've been out of the loop for a while (the last time I was active was circa late 2013/ early 2014), but I do remember there was a lot of concern regarding warranty and the flags. I do admit that there was a lot of speculation from losing a section of memory from tripping the flag to actually burning the motherboard. I originally decided to wait until the dust settled but life took over and I ended up only sporadically checking the forums before disappearing for long periods of time. I actually don't know what the end of the story is to be honest.
Oniyuri said:
Well, I've been out of the loop for a while (the last time I was active was circa late 2013/ early 2014), but I do remember there was a lot of concern regarding warranty and the flags. I do admit that there was a lot of speculation from losing a section of memory from tripping the flag to actually burning the motherboard. I originally decided to wait until the dust settled but life took over and I ended up only sporadically checking the forums before disappearing for long periods of time. I actually don't know what the end of the story is to be honest.
Click to expand...
Click to collapse
The only concern is about the warranty. Since your phone is some years old, I doubt that is an issue for you anymore.
By losing memory you mean losing data or actually losing storage space?
Either way, I haven't heard of anyone with such a problem around here.
Nor about somebody with a fried motherboard.
There might have been some unfortunate cases, but this is to be expected when you modify your device. There always is a risk of damage, it doesn't matter if it's by rooting or by flashing a ROM.
I meant lose storage. As I understood it, KNOX worked like a container and once the flag was tripped, you'd lose whatever it contained - as in never being able to access that bit ever again.
Oniyuri said:
I meant lose storage. As I understood it, KNOX worked like a container and once the flag was tripped, you'd lose whatever it contained - as in never being able to access that bit ever again.
Click to expand...
Click to collapse
You have to use the knox app first for that to even be considered a risk.
Knox will not put anything in that container without user input.
GDReaper said:
You have to use the knox app first for that to even be considered a risk.
Knox will not put anything in that container without user input.
Click to expand...
Click to collapse
Ok, so to get the steps straight:
1. I'd need to get a lollipop bootloader & modem
2. root + nandroid (CWM) + titanium for app data (non-system app data)
3. change recovery to TWRP
4. flash rom + gapps
....and then I should be ready to go, correct?
Oniyuri said:
Ok, so to get the steps straight:
1. I'd need to get a lollipop bootloader & modem
2. root + nandroid (CWM) + titanium for app data (non-system app data)
3. change recovery to TWRP
4. flash rom + gapps
....and then I should be ready to go, correct?
Click to expand...
Click to collapse
1) Is not mandatory, it's just recommended. The only exception is if your device is a Verizon or AT&T phone, then don't - and I repeat - don't update or you risk losing the possibility of any custom ROM flashing or rooting due to the locked bootloaders.
2) and 3) CWM and TWRP backups do not have cross-compatibility. If you backup with CWM you have to restore with CWM.
Please tell me you haven't flashed anything yet. I can help with the entirety of the procedure.
robcore said:
Please tell me you haven't flashed anything yet. I can help with the entirety of the procedure.
Click to expand...
Click to collapse
No I haven't done anything yet. I found something else to occupy me for the last few nights - a chromecast that seems to hate me.
Oniyuri said:
No I haven't done anything yet. I found something else to occupy me for the last few nights - a chromecast that seems to hate me.
Click to expand...
Click to collapse
Haha I hear ya. I've been building a kernel for about a year now and finally (knock on wood) arrived at something I'm happy with. Lesson learned, electronics are definitely conspiring against us.
That said, please feel free to pm me when you're ready for the flashing process. Though it's a silly skill, it's become second nature to me and something about your situation flipped a helpful switch in me : P what's the Chromecast like?
robcore said:
Haha I hear ya. I've been building a kernel for about a year now and finally (knock on wood) arrived at something I'm happy with. Lesson learned, electronics are definitely conspiring against us.
That said, please feel free to pm me when you're ready for the flashing process. Though it's a silly skill, it's become second nature to me and something about your situation flipped a helpful switch in me : P what's the Chromecast like?
Click to expand...
Click to collapse
Well, so far, the chromecast is only plugged into my tv and basically did the setup by itself only for the google cast app on my phone to not recognize it when it said that it's ready to cast. I've ran out of things to do aside from going to the google forums (which I've already done). I'm starting to wonder if it's my phone that's causing all the issues.