I recently sent in my S3 for repairs via samsung because my usb port had gone bad. The usb port issue has been solved but now, roughly 1 hour into any factory reset i preform, the phone will lock up/crash when i lock the phone for any longer than 5 seconds. PLEASE help!
I just want to make sure I understand. Are you factory resetting from the stock recovery or a custom recovery?
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Wicked X v6.5, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
roirraW "edor" ehT said:
I just want to make sure I understand. Are you factory resetting from the stock recovery or a custom recovery?
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Wicked X v6.5, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
Click to expand...
Click to collapse
everything is stock; ive recently had to send this in for repairs and this is all happening right out of the box since ive gotten it back. was hoping i could fix this on my own rather than having to be without my phone for another 2 weeks.
doodlebird said:
everything is stock; ive recently had to send this in for repairs and this is all happening right out of the box since ive gotten it back. was hoping i could fix this on my own rather than having to be without my phone for another 2 weeks.
Click to expand...
Click to collapse
What version of stock TouchWiz is on your phone?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Wicked X v6.5, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
it's nd8 all the way. i've also tried different nd8 roms, different recoveries, different launchers etc etc etc. i can't seem to replicate the crashes from any one action but one thing that is consistent seems to be that if i reload the ROM onto the phone, the crashes go away for roughly an hour. after a while though it will randomly start doing it again. i've even reloaded the rom and let my phone just sit there completely fresh from being reset while occasionally locking/unlocking the phone to see if it has crashed, just for the phone to eventually give way to crashing every time i lock it after roughly an hour of use. the phone is not getting overheated either.
doodlebird said:
it's nd8 all the way. i've also tried different nd8 roms, different recoveries, different launchers etc etc etc. i can't seem to replicate the crashes from any one action but one thing that is consistent seems to be that if i reload the ROM onto the phone, the crashes go away for roughly an hour. after a while though it will randomly start doing it again. i've even reloaded the rom and let my phone just sit there completely fresh from being reset while occasionally locking/unlocking the phone to see if it has crashed, just for the phone to eventually give way to crashing every time i lock it after roughly an hour of use. the phone is not getting overheated either.
Click to expand...
Click to collapse
Argh. I sympathize with what must be very frustrating. I hate it when stuff like that happens and I know it doesn't help but at least it's consistent. I take it that the Knox counter has been tripped (go into Download mode and check the line that says Warranty = ??) and that you wouldn't be able to send it in for repairs again because of it? It seems they either missed or caused a second problem with your phone when they fixed the first.
roirraW "edor" ehT said:
Argh. I sympathize with what must be very frustrating. I hate it when stuff like that happens and I know it doesn't help but at least it's consistent. I take it that the Knox counter has been tripped (go into Download mode and check the line that says Warranty = ??) and that you wouldn't be able to send it in for repairs again because of it? It seems they either missed or caused a second problem with your phone when they fixed the first.
Click to expand...
Click to collapse
mine says warranty bit: 1, is that mean it has been tripped?
doodlebird said:
mine says warranty bit: 1, is that mean it has been tripped?
Click to expand...
Click to collapse
Yes, it's tripped and there's absolutely no way to un-trip it, so Samsung wouldn't repair it under warranty unless you just get lucky.
It got tripped when you put a custom recovery on.
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Wicked X v6.5, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
Related
So I have an S3 that I had CM11 on and I switched from sprint to ting and need to update the PLR Profiles. I installed what I thought was a Touchwiz ROM (MOAR) and it wouldn't boot. But it removed Clockwork Mod, I'm back to the stock downloader that says "Odin Mode" with a Warranty Bit: 1.
Before I go further and flash a stock ROM (from http://forum.xda-developers.com/showthread.php?t=2738533 ) with Odin I wanted to make sure this wouldn't brick (knowing brick anyway) my phone. Everything I read through search contradicts what I read before it. Some say that downgrading (CW11 is KitKat and I'm guessing this is JB or ICS since its from 2012) will brick your phone (Cant seem to find current stock ROMs), some say that flashing stock with "warranty bit: 1" will do it (I can't fix this bit count because phone wont boot), some say that flashing a stock ROM over a custom ROM will brick it. Of course for each rule there is 20 posts saying they are wrong.
TL;DR
Can I flash http://forum.xda-developers.com/showthread.php?t=2738533 over a MOAR install on a phone with a warranty bit : 1 condition?
Thanks in advance,
Omega
PS - Thanks to all the Devs, been lurking here for years and using your work since my first Droid.
The tar in that thread is nd8 kitkat 4.4.2 for touchwiz. Once that tar is flashed you CANNOT downgrade bootloader or modem, you can however flash any rom you desire. Again be sure NOT to downgrade bootloader or modem, because doing so will hard brick your phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 02:24 AM ---------- Previous post was at 02:20 AM ----------
TL;DR
Can I flash http://forum.xda-developers.com/showthread.php?t=2738533 over a MOAR install on a phone with a warranty bit : 1 condition?
Yes you can flash this tar via odin. It will restore your phone back to factory settings with 4.4.2 touchwiz.
Thank you for the help and quick response! I am about to flash it now. I did have one more dumb question that I thought other people might not know and find this thread in search: Is the N8 the version of the radio software? The bootloader? What does it represent? When I good a 2 or 3 letter word like that, its useless.
Again thank you so much for the quick help.
Edit: Worked like a damned charm. If I could, I'd buy ya a beer. Thanks again.
OmegaNine said:
Thank you for the help and quick response! I am about to flash it now. I did have one more dumb question that I thought other people might not know and find this thread in search: Is the N8 the version of the radio software? The bootloader? What does it represent? When I good a 2 or 3 letter word like that, its useless.
Again thank you so much for the quick help.
Edit: Worked like a damned charm. If I could, I'd buy ya a beer. Thanks again.
Click to expand...
Click to collapse
ND8 is just the build number by Samsung that they settled on as stable. I've seen am explanation of exactly what the letters and number means but basically I think it's just year, month and day but I don't remember precisely.
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Wicked X v6.5, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
roirraW "edor" ehT said:
ND8 is just the build number by Samsung that they settled on as stable. I've seen am explanation of exactly what the letters and number means but basically I think it's just year, month and day but I don't remember precisely.
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Wicked X v6.5, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
Click to expand...
Click to collapse
N =2014 - 14th letter of the alphabet (year)
D = April = 4th letter - 4th month
8 = Revision number/letter (I think)
I think that's right...it's late and I'm going from memory lol...
Sent from my SM-G900P using XDA Free mobile app
So back in December while updating to the newest version of MOAR, I made this mistake of taking the OTA update and getting Knox. I managed not to brick my phone at the time, but ended up with the Knox bit tripped and a lot of concern that further experimenting would result in a dead phone and a forced replacement. Anyway, fast forward to now and its time to update again (some apps are starting to get unstable because they have been updated but my ROM hasn't), but I want to make sure I don't risk bricking the phone thanks to Knox.
If I remember correctly, the fact that I'd contracted Knox and tripped the bit already meant that I was stuck with the same bootloader, but I could update everything else. Is this still the case, or has someone figured a way around the issue in the past six months so that I can get rid of Knox once and for all? Also, since I haven't looked at any of this in the last 7 months, what exactly would the process be to update to the newest version of MOAR without updating the bootloader (if that's still what needs to happen)?
Thanks
You can downgrade everything but bootloader and modem. You can upgrade everything.
Flashing custom ROMs don't include bootloaders or modems, so have no fear. Only Odining the stock ROM, taking an OTA, or specifically finding a way to flash those upgrade them.
Just flash the latest MOAR or whatever other ROM you want to, as always.
The only exception to this is to flash ND8 (TouchWiz 4.4.2) based ROMs you need to have taken the ND8 OTA or Odined the stock ND8 tar first, otherwise you may brick your phone.
You're welcome!
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
roirraW "edor" ehT said:
You can downgrade everything but bootloader and modem. You can upgrade everything.
Flashing custom ROMs don't include bootloaders or modems, so have no fear. Only Odining the stock ROM, taking an OTA, or specifically finding a way to flash those upgrade them.
Just flash the latest MOAR or whatever other ROM you want to, as always.
The only exception to this is to flash ND8 (TouchWiz 4.4.2) based ROMs you need to have taken the ND8 OTA or Odined the stock ND8 tar first, otherwise you may brick your phone.
You're welcome!
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
Click to expand...
Click to collapse
Ok, with all of that said, the ND8 is an upgrade, so if I Odin it in, I should still be fine? I really hate that this is even an issue... I am thinking of jumping ship from the company's products when I upgrade next specifically as a result of this
treblesum81 said:
Ok, with all of that said, the ND8 is an upgrade, so if I Odin it in, I should still be fine? I really hate that this is even an issue... I am thinking of jumping ship from the company's products when I upgrade next specifically as a result of this
Click to expand...
Click to collapse
Yes, you can upgrade everything.
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
treblesum81 said:
Ok, with all of that said, the ND8 is an upgrade, so if I Odin it in, I should still be fine? I really hate that this is even an issue... I am thinking of jumping ship from the company's products when I upgrade next specifically as a result of this
Click to expand...
Click to collapse
The only valid arguments against Knox (IMHO) are:
1. Once the warranty counter is tripped there is no way to reset it.
2. You do not have the ability to downgrade modems/bootloaders.
Myself, rode warrior and many others have had no issues directly related to Knox....
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
g_money said:
The only valid arguments against Knox (IMHO) are:
1. Once the warranty counter is tripped there is no way to reset it.
2. You do not have the ability to downgrade modems/bootloaders.
Myself, rode warrior and many others have had no issues directly related to Knox....
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
The problem is the way in which those issues manifested. Samsung essentially slipped Knox into the update almost without warning and with virtually no documentation. As a result many of those who were affected found out about it as a result of a bricked phone which was now permanently marked as ineligible for warranty work. Had Samsung made it clear what Knox was capable of and provided proper documentation of its function then I don't think many people would have had any problems with it.
Sent from my SPH-L710 using XDA Free mobile app
I installed the OTA 4.4.2 stock rom from the forums and ever since my notifications come sometimes hours later. I don't have cell service and haven't for awhile. I leave the phone on airplane mode but with wifi turned on. It's the same way I used it under Jellybean. However now I have to often open up Hangouts and Google Voice to check manually for messages. If I don't I'll sometimes get notifications of new messages 1 to 6 hours after the message was sent.
Even opening up the app and checking sometimes won't force me to get new messages. If I hit the refresh button on Google voice about 3 times then sometimes it'll force it to finally receive the message.
Wifi works fine though, I can surf the web, stream music, watch youtube, update apps perfectly. Never have a hiccup or stutter and never had this issue until I updated to KK. Before I flashed KK, I did a backup of my apps with Helium and restored them. I wondered if that could be the problem. Not sure why it would effect the messages I receive on Hangouts or Google Voice and nothing else though.
This is the rom and procedure I used, going from stock 4.3 rooted to KK.
http://forum.xda-developers.com/showthread.php?t=2738533
Just to be 100% sure nothing else is causing weird issues, I would backup everything from your internal storage and external SD card, reformat your SD card, Odin the stock ND8 tar and the latest Philz Touch Recovery, then try to reproduce your problem.
If you can't reproduce it, root the phone (Philz Touch Recovery / Settings /Re-Root), then breakup the apps with data you restore into half. Restore only that half and try to reproduce the problem. Each time the problem doesn't occur, do a nandroid backup and restore another half of what's not restored yet. Once you can reproduce the problem, you'll have narrowed it down.
Once you can reproduce the problem, restore the last nandroid and restore half of what you had previously tried, etc. Keep going until you narrow the problem down to one, or narrow it down enough to make an educated guess from what's left and try just that one and verify that it's the issue.
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
roirraW "edor" ehT said:
Just to be 100% sure nothing else is causing weird issues, I would backup everything from your internal storage and external SD card, reformat your SD card, Odin the stock ND8 tar and the latest Philz Touch Recovery, then try to reproduce your problem.
If you can't reproduce it, root the phone (Philz Touch Recovery / Settings /Re-Root), then breakup the apps with data you restore into half. Restore only that half and try to reproduce the problem. Each time the problem doesn't occur, do a nandroid backup and restore another half of what's not restored yet. Once you can reproduce the problem, you'll have narrowed it down.
Once you can reproduce the problem, restore the last nandroid and restore half of what you had previously tried, etc. Keep going until you narrow the problem down to one, or narrow it down enough to make an educated guess from what's left and try just that one and verify that it's the issue.
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
Click to expand...
Click to collapse
Thanks for the reply, I thought I had notifications setup for this thread, but I guess not. Anyways in the past 4 days I've flashed 2 different KK roms and still having the same issue. I've used Philz wipe and install option both times. I used a stock rooted rom first, and after a day of using it I still am not getting my notifications for Hangouts. I used another custom KK rom from the forum and flashed it as well using Philz wipe and install.
I've left the roms stock on both installs, except for signing into my Google account and letting the apps update. I'll send myself test messages and wait sometimes even an hour and not get any notification until I manually open the app and even then sometimes I cannot get it to load the message. Yet the internet connection is working and I can check email and browse websites without issue. The only way I can get it to load up any new messages is to reboot.
I want to try going back to Jellybean just to see if I'll have the same issue. Now that I've gone to KK though, is it possible for me to downgrade back to Jellybean? I know I've seen threads in the past saying downgrading will brick the device.
You can flash any ROM made for our SPH-L710 that you want without bricking. You just can't ever Odin anything older than ND8 or NDC.
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v5.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
I'm considering picking up a S3 off eBay, since they seem to be rather cheap nowadays ( under $100), and was thinking of it as an upgrade from my Galaxy Nexus.
I've seen people with Verizon S3s and S4s get stuck after updating so they couldn't install any ROMs anymore.
Of course I haven't really heard much about the Sprint phones being locked down so much, but could anyone tell me if (even with the newest update) if you can install CWM and CyanogenMod?
Thanks
GTRsdk said:
I'm considering picking up a S3 off eBay, since they seem to be rather cheap nowadays ( under $100), and was thinking of it as an upgrade from my Galaxy Nexus.
I've seen people with Verizon S3s and S4s get stuck after updating so they couldn't install any ROMs anymore.
Of course I haven't really heard much about the Sprint phones being locked down so much, but could anyone tell me if (even with the newest update) if you can install CWM and CyanogenMod?
Thanks
Click to expand...
Click to collapse
it would be better to install Philz Touch CWM advanced recovery from Odin and you can back up your stock rom when in the recovery then do the second option under wipe data to wipe everything but first make sure you have the Touchwiz rom and or AOSP rom + Gapps to flash in your internal storage then wipe cache and dalvik cache and your done so yes you can still install a custom recovery and custom rom like CyanogenMod
6th_Hokage said:
it would be better to install Philz Touch CWM advanced recovery from Odin and you can back up your stock rom when in the recovery then do the second option under wipe data to wipe everything but first make sure you have the Touchwiz rom and or AOSP rom + Gapps to flash in your internal storage then wipe cache and dalvik cache and your done so yes you can still install a custom recovery and custom rom like CyanogenMod
Click to expand...
Click to collapse
I don't think you read through my whole post, since I wasn't asking how to do it, since I'm already familiar with Heimdall flashing (have been flashing on early Verizon S3/S4, before updates blocked it).
But the big question is... If you were to go to 100% stock (or a 100% stock phone to begin with), and have the newest updates applied(I think it is 4.3 or 4.4), you can still flash stuff, and not have it brick, right?
I know if I were to try the same on a Verizon S3, it would almost certainly brick.
GTRsdk said:
I don't think you read through my whole post, since I wasn't asking how to do it, since I'm already familiar with Heimdall flashing (have been flashing on early Verizon S3/S4, before updates blocked it).
But the big question is... If you were to go to 100% stock (or a 100% stock phone to begin with), and have the newest updates applied(I think it is 4.3 or 4.4), you can still flash stuff, and not have it brick, right?
I know if I were to try the same on a Verizon S3, it would almost certainly brick.
Click to expand...
Click to collapse
but i did read through it i just answered the last part about CWM and CyanogenMod since that's what i know for sure
but you see for the rest of your words i have flashed on full stock 4.4.2 NDC since mine is the Boost variant with root and philz touch recovery....but only stuff made for touchwiz like the S5 ported apps just the worst i got after flashing is constant force closing of one or more apps for then i would have to boot back into recovery with the button method and flash a backup but i have done so and my s3 started with 4.4.2 stock update for the sprint variant even tho its the same model number i would wait to see if anyone else with it chimes in....but since it is the same basic model everything basically works the same way for them
Yes, you can still flash whatever you want besides modem. You just can't ever Odin anything older than ND8 (Sprint TouchWiz 4.4.2) or NDC (Boost / Virgin Mobile TouchWiz 4.4.2).
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v4.4, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
so got my s3 and all was good up till yesterday. i have this custom rom installed http://forum.xda-developers.com/showthread.php?t=2774902
went on the thread yesterday and grabbed the V7 update file. I went into recovery mode, cleared cache and flashed.
phone booted up, did that androiod app thing telling me it's installing i think.
then phone booted, i swiped the screen to unlock, then phone froze there.
i tried to hit the power button a few times but just stayed on home screen and not responding.
i pulled battery and when i put the battery back it phone started to boot up itself, got the the samsung screen, then the ktoonz kernal screen (i think) then screen goes black.
i got it into recovery mode, did a back up restore and same thing. phone gets to the same place a few times i could see the singularity flashing logo but then phone just goes to black.
I have tried to get into download mode but all if does is get to the yellow triangle screen, sits there for a few seconds, then goes to black.
i have been told might be a power button thing but, can't get it fixed i don't think seeing as sprint will see the kernal logo boot up screen and not fix.
any help or direction on what i can do to fix or suggestions.
thanks in advance
Let me know if you do try the electronics cleaner from Lowe's I suggested in the other thread. I hope you can solve it. I know it sucks.
roirraW "edor" ehT said:
Let me know if you do try the electronics cleaner from Lowe's I suggested in the other thread. I hope you can solve it. I know it sucks.
Click to expand...
Click to collapse
yeah i have to get that here... i took the phone apart last night to see if i was able to clean it with alcohol and a swab. phone still doing the same thing as you can tell by my post.
just wish it would stay in download mode so i can un root and have sprint deal with it but, oh well these are the chances we take.
thinking at some point heading to radio shack and getting elect cleaner and see if that help...
Someone responded in the other thread http://forum.xda-developers.com/showpost.php?p=54653284&postcount=274. Please respond to him in this thread if you do at all though.
roirraW "edor" ehT said:
Someone responded in the other thread http://forum.xda-developers.com/showpost.php?p=54653284&postcount=274. Please respond to him in this thread if you do at all though.
Click to expand...
Click to collapse
well that sort of worked.. thank god...
so, brought the phone to sprint was honest with them and told the repair dude i am rooted and just need it to stay in dload mode for me to un-root and take advantage of my warranty/insurance claim.
well dude was cool as fkcu he opened it up, cleaned up the button with elect spray and meh.. same issue.
then told me that insurance claim had to pay out the $150 for my upgrade. not having it i came home with my paper weight.
looked at that video above which i used last night, booted phone into dload mode and bam we are in business. phone was reconigzed via PC so did an odin flash back to stock. phone booted as it should **** was syncing updating then i seen didn't have external card in powered off and same issues as b4.. so, re did, got back into rom and now will just keep phone on and use the middle button to take out of sleep mode..
cheers to roirraW for all your help and McBadass for that link... followed it best i could and now have a working phone but powerbutton can't be used...
i think now i get better insurance coverage now that phone is not rooted.. either way hope it last until got the cash for an upgrade...
For Sprint and Best Buy, it doesn't matter if it ever was rooted, even with the Knox Warranty bit flipped to 1. Just use Triangle Away to reset download mode status, then immediately re-Odin the stock tar.md5.
I had to do that last week for Best Buy to replace my phone with broken USB OTG (would charge but wouldn't see USB devices anymore). They wouldn't authorize it to be exchanged until I did both steps.
Samsung won't repair it with the warranty bit flipped.
You're welcome for my part!
3Minit Battery Mod for Conquest: Singularity v7 with 1000+ animated battery icons
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v7.0, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
Triangle Away hmm.. if i do that im afraid that the power button wont work and have to go though it all over again. right now i just flashed the stock rom this http://forum.xda-developers.com/showthread.php?t=2741413 i felt to afraid to touch anything else.
is that fully stock un rooted so i can bring this back to sprint and have them replace it?!?!
cheers again for all your help and sorry all my questions. just trying to learn a little bit more and be more active here cuz the community here is awesome
killerhz said:
Triangle Away hmm.. if i do that im afraid that the power button wont work and have to go though it all over again. right now i just flashed the stock rom this http://forum.xda-developers.com/showthread.php?t=2741413 i felt to afraid to touch anything else.
is that fully stock un rooted so i can bring this back to sprint and have them replace it?!?!
cheers again for all your help and sorry all my questions. just trying to learn a little bit more and be more active here cuz the community here is awesome
Click to expand...
Click to collapse
You're welcome. The first post of the thread you linked to says whether it's rooted or not. It's rooted.
The easiest way to get to completely stock unrooted is to Odin the stock ND8 tar.md5. You can install quickboot, i think it's called, from the Play Store to get the phone to boot back into download mode in order to Odin it.
I would be tempted to try to take it in as is, though, since you don't know what will cause it to act unpredictably again.
Recovery FLASHABLE version now posted near the bottom of the first post of the 3Minit Battery Mod for Conquest-Singularity.
3Minit Battery Mod for Conquest: Singularity v7 with 1000+ animated battery icons
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v7.0, Ktoonsez' latest kernel and the latest Philz Touch Recovery.