Develop Bugs

[Q] Rooting, Roms and.. how to "avoid voiding my warranty?"

Information about my phone:
Bought my Phone Nov. 26th
SGH-T989
Android 2.3.5
Baseband Version - T989UVKID
Kernel version - 2.6.35.11
Build Number - Gingerbread.UVKID
Hello fellow sgs2 users and xda members.
After searching google and the XDA forums it would appear that rooting my phone is going to void the warranty, unless I can find a stock rom...
A few questions:
1. Is the above statement true or can I root my phone and install custom rom's without voiding the warranty?
2. Many of the sites / posts I found were not specific about the type of warranty - whether it be manufacturer or t-mobile. Can anyone shed some light on this?
3. Is there a place I can find a stock rom backup? I found an OP post in the dev forums, but the link is broken. EDIT: I found all the files for the stock restoration process here: http://forum.xda-developers.com/showthread.php?t=1321811&highlight=stock+rom+void+warranty
At this point the answer to these questions are the only thing I'm waiting for before I root my phone.
My primary motivations for rooting and installing a custom rom (by priority/importance):
1. Getting rid of CIQ
2. Removing carrier programs and customizations
3. Improving performance
Perhaps one of you overachievers can recommend a set of steps to follow. I've read through several rooting guides, and the "what's the best rom" thread. I'm starting to feel a bit overwhelmed, but will continue reading.
p.s.
This was the only thread I found in the t-mobile samsung galaxy s II sgh-t989 forum with the keyword "warranty" - http://forum.xda-developers.com/showthread.php?t=1385170&highlight=warranty perhaps I'm not searching properly?

Look at the thread like 2 above this one. It has all the answers. Here, let me help you.
http://forum.xda-developers.com/showthread.php?t=1385938
Sent from my SGH-T989 using Tapatalk

Thanks mikeyinid.
I'm having trouble getting the superuser.zip (su-3.0.5-efgh-signed.zip) installed. After installing it using CWM, I boot up the phone but superuser is nowhere to be found in my apps list, and ROM Manager doesn't work because it says it can't find superuser.... sigh...
A couple of things that the instructions from many rooting guides that I found were necessary and/or helpful:
When you need to power up into CWM: make sure you unplug the USB before you do it. All you have to do is hold down the volume keys and the power button at the same time until you feel the phone vibrate, or you see the samsung logo appear.

Okay here is the main answer you need: Yes, rooting your phone voids your warranty. Period. Some of us (myself included) go into all of this rooting stuff knowing that doing so means we're on our own. Some do it thinking they can game the system if/when **** goes down, and some don't know the risks at all.
Even though I have never nor would never think that someone owes me a new phone when I screwed it up (save for on my epic 4G because you needed to root to get usable GPS and that is pathetic) there is one way to guarantee that you'll be safe: buy the phone from bestbuy and get their insurance. It covers "accidental" damage meaning if it got bricked you could simply "accidentally" drop it down a few flights of stairs and when it is subsequently destroyed you get a new device. That and that alone is the only sure fire way to keep your device safe.
Sent from my Hercules with xda Premium.

sethbw said:
Thanks mikeyinid. I've moved forward to the process of rooting, but I'm having an issue with getting to the CMW recovery menu. When I take out my batter and put it back in.. I hold down the volume up and volume down buttons, and the power button for 2 seconds, but it takes me to the Warning! screen over again... what am I doing wrong?
Am I supposed to hold down the volume keys and the power button at the same time or separately? So confused
Click to expand...
Click to collapse
Did you flash cwm in Odin?
Sent from my SGH-T989 using Tapatalk

Thanks guys, I need help.
I go to cwm and install from zip (from my external SD) and select su-3.0.5-efgh-signed.zip
From there I get the following error:
E:Error in/sdcard/su-3.0.5-efgh-signed.zip
(status 0)
Installation aborted
I was told this is not a problem, so I reboot my phone from the cwm menu. No superuser in my apps list, ROM Manager does not work.

mikeyinid said:
Did you flash cwm in Odin?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Sorry that was an old post I was in the middle of editing it when you replied! I did use Odin.
I was able to get into CWM no problems after I removed the usb cable.
My problem now is that it wont take the superuser install from CWM. No idea what could have gone wrong...

kenvan19 said:
Okay here is the main answer you need: Yes, rooting your phone voids your warranty. Period. Some of us (myself included) go into all of this rooting stuff knowing that doing so means we're on our own. Some do it thinking they can game the system if/when **** goes down, and some don't know the risks at all.
Even though I have never nor would never think that someone owes me a new phone when I screwed it up (save for on my epic 4G because you needed to root to get usable GPS and that is pathetic) there is one way to guarantee that you'll be safe: buy the phone from bestbuy and get their insurance. It covers "accidental" damage meaning if it got bricked you could simply "accidentally" drop it down a few flights of stairs and when it is subsequently destroyed you get a new device. That and that alone is the only sure fire way to keep your device safe.
Sent from my Hercules with xda Premium.
Click to expand...
Click to collapse
Would you consider removal of CIQ a solid reason?

How about try to root using superoneclick method.
Look in the sticky "[ INDEX ] .☆.☆.☆. SEARCH HERE 1st .☆.☆.☆. most wanted topics, FAQ" of this forum, there is a link for Root via superoneclick v2.2 in that thread.

sethbw said:
Sorry that was an old post I was in the middle of editing it when you replied! I did use Odin.
I was able to get into CWM no problems after I removed the usb cable.
My problem now is that it wont take the superuser install from CWM. No idea what could have gone wrong...
Click to expand...
Click to collapse
just keep flashing it til you dont get an error. sometimes it takes 3 or 4 times.

Allright that appears to have worked Mikey. Rebooting now...

sethbw said:
Allright that appears to have worked Mikey. Rebooting now...
Click to expand...
Click to collapse
Next you should flash Juggernaut and the ics theme. Sick as hell
Sent from my SGH-T989 using Tapatalk

Thanks Already downloading J 3.7 - is this the version you recommend?

sethbw said:
Thanks Already downloading J 3.7 - is this the version you recommend?
Click to expand...
Click to collapse
i think the theme is only updated through 3.69 but i think it will work on 3.7 also

Waiting 10 minutes after reboot, 7 minutes to go... then another reboot.. and then I guess I'm done! Although I have a feeling I will need to verify that my network settings and connections all work... Very excited =-]

sethbw said:
Waiting 10 minutes after reboot, 7 minutes to go... then another reboot.. and then I guess I'm done! Although I have a feeling I will need to verify that my network settings and connections all work... Very excited =-]
Click to expand...
Click to collapse
youll be fine, juggernaut works very well.

Its really very early and i'm not sure that its worth the risk at this point. Everything is pretty early in development and if you are inexperienced the odds of getting your phone messed up or even bricked are very high. You MIGHT be able to cover up the evidence that you rooted but if you can do that much than your phone probably isn't bricked anyways. It's also fraud.
Like another poster said, get insurance if you just have to do this, but personally I really recommend waiting until the pros have it worked out and there's something really worth rooting for. I HATE CIQ just as much as the next guy but i'm waiting for a good ICS build before I root. I've lost too many phones to accidental physical damage to lose another to this.
Good luck.
Sent from my SGH-T989 using xda premium

Return to Stock - Without USB?

Hi folks. First post here and a bit of a weird one, I’m hoping some of you with more experience in rooting etc can point me in the right direction. I’ve got a GSM Galaxy Nexus which I previously rooted to get updates as I was stuck with some horrible build that had to go through Samsung and my carrier to update.
Now my USB port is faulty and I want to get it serviced under warranty but I don’t want them blaming the root access and trying to squirm out of it. I’m actually running a stock ROM of ICS so I don't need to change that - but I still have CWM installed along with its custom recovery mode(?), Superuser and the bootloader is unlocked.
Can anybody give me some suggestions on how I could undo this, preferably limiting my use of USB or eschewing it all together? It’s so unstable I’m really afraid of bricking the device. I want to just make it look as stock as possible so things go smoothly with the service or replacement.
I found suggestions in some threads for using 'Mobile ODIN'. Can anyone tell me if this would help? Thanks!

I've read on here multiple times that they will repair it even if rooted...maybe someone can confirm.

I think there is a apps on the market called adb wireless... May be it can help you!
Sent from my HTC Glacier using xda premium

Just get a stock ROM zip and you can use glados app to lock the boot loader when rooted then flash the stock fw after wiping system the stock system will wipe the custom recovery on boot enjoy
Sent from my Galaxy Nexus using xda premium

Sorry. At work. Post 3 of my guide.
Returning to stock and locked without USB.

Jubakuba said:
Sorry. At work. Post 3 of my guide.
Returning to stock and locked without USB.
Click to expand...
Click to collapse
Fantastic! Thanks to those above too. I'll check out part 3 of your guide as mentioned since it's in your sig. :good:

How do I root this thing (Arc S)

Yea sorry, I know there are tons of threads on rooting this stupid thing but I've been trying out so many different ways today and failed that I'm sick of and tired of this stupid piece of crap.
This is my brother's phone, and it's run out of internal memory (seriously 300 mb?), anyway he has like 10 apps installed on the internal memory, these plus all the updates have filled it up. So now I'm trying to root it so I can swap the SD cards (already got him a 32 gig microSD for that).
And oh boy am I sick of this thing, so far I've tried multiple options and none work, and some are too complicated with poor instructions for me to figure out.
Rooting my Galaxy W was so easy and this thing here just makes me hate everything.
Stuff I've tried:
Sony Xperia Flasher
ERoot
Flash tool
bootloader
I'm at the end of my wits here, completely frustrated and yea, if this where my phone I would have already smashed it with a hammer.
I really don't have time for this sh*t since I have to study for a big test, so I would appreciate something super simple and fast, like with the Galaxy W.
Again, sorry for sounding like a **** and creating yet another thread, but I'm desperate.
Thanks for any help.

dial *#*#7378423#*#* on your phone then go to service info then to configuration & at the bottom what does it say regarding your bootloader ?

Bootloader unlock allowed: Yes

Dead Metal said:
Bootloader unlock allowed: Yes
Click to expand...
Click to collapse
this is good,what version of android do you have ?

It says Android Version 2.3.4
But build number 4.02.A0.69

Dead Metal said:
It says Android Version 2.3.4
But build number 4.02.A0.69
Click to expand...
Click to collapse
ok i used this app to root my phone (google it or search this forum for it,easy to find):
DooMLoRD_v4_ROOT-zergRush-busybox-su
& i used this video to unlock bootloader:
http://www.youtube.com/watch?v=-crbhMFSuaQ

Thanks , I'll try that tomorrow, right now I'm just too tiered.

Dead Metal said:
Thanks , I'll try that tomorrow, right now I'm just too tiered.
Click to expand...
Click to collapse
if you need help send me PM & i will reply back in this thread. take care

If you want you can unlock the bootloader (loosing your warranty, of course), and then install a newer version of android up to 4.2.2, which is much more smoother than 2.3.4 and has much more features...

Madness, if you can't figure it out you're either not reading enough or just being lazy. There's about 4 or 5 links in my guide with how to root, add to that the amount of other threads there is, starting a new one means your lazy, because you've read nothing whilst signing up and just want to be spoon fed. Luck for you, there's some willing to do it.
Sent from Myushi

Rooting Tools
you can root using doomlord root script.
I have rooted several times after flashing few roms and the script works great.
Hope this helps..
http://forum.xda-developers.com/showthread.php?t=1321582

XperienceD said:
Madness, if you can't figure it out you're either not reading enough or just being lazy. There's about 4 or 5 links in my guide with how to root, add to that the amount of other threads there is, starting a new one means your lazy, because you've read nothing whilst signing up and just want to be spoon fed. Luck for you, there's some willing to do it.
Sent from Myushi
Click to expand...
Click to collapse
Had you taken a look at my join date and post count you may have noticed how I did not sign up to be spoon fed to root this device. And had you read my post you may have noticed how I stated that I've already rooted the Galaxy W, which is my phone, which was also real easy and straight forward.
I signed up to be able to hit the thanks button for Sir Arco's CM10 ROM, and give feedback should I notice bugs or other problems with it.
All I wanted was to root it without flashing a new ROM, since all my brother wants is more space on his phone, I don't think he'll want to check the forums constantly to check if there's a new version of a ROM out so he can flash it, so unlocking the bootloader and flashing a new ROM would be pretty pointless.

you can try to use the doomlord process, but you will always install a new rom, in that case will upgrade de phone to 4.0.3 and then you will be able to root the phone with de .bat file inside :good:

Dead Metal said:
Had you taken a look at my join date and post count you may have noticed how I did not sign up to be spoon fed to root this device.
Click to expand...
Click to collapse
But you still clearly hadn't read anything whilst signing up, otherwise you wouldn't have started a new thread on something as common as "how do I root". I assume you will have managed it by now?

XperienceD said:
But you still clearly hadn't read anything whilst signing up, otherwise you wouldn't have started a new thread on something as common as "how do I root". I assume you will have managed it by now?
Click to expand...
Click to collapse
I did, which is why I apologized for posting another thread like it, there where also no I do I root this in this forum, since apparently I'm the only one who had trouble with the options that are posted in the guide threads.
And no, the doom script did not work, it did say it was successful but the phone remained unrooted. So after a couple more tries (and rectifying the "drivers out of date" error message) I unlocked the bootloader, tried again a couple of times still to no effect. So I want ahead and flashed a new ROM and Kernel. At first my brother wasn't too happy about that but he's starting to like the new ROM.
Man, it was easier flashing android onto the bloody HP Touchpad than this phone.

[Q] Backup with no access to screen

Had a few questions here. I researched and found this tool. However, I can't post in the thread to ask questions because of my noobtasticness and I searched and couldn't find a similar problem elsewhere.
My first question is, can I use the root and backup tools in the toolkit with no access to the screen whatsoever? I damaged my phone and the touch and lcd screens aren't functioning, but I can plug it in and access memory via usb.
Secondly, I've received the replacement phone. Is there an order I should do all of this in? My first guess is to root/backup the old phone (if possible), then activate the new phone, then root/restore on the new phone. Does that sound about right?

aolbites said:
Had a few questions here. I researched and found this tool. However, I can't post in the thread to ask questions because of my noobtasticness and I searched and couldn't find a similar problem elsewhere.
My first question is, can I use the root and backup tools in the toolkit with no access to the screen whatsoever? I damaged my phone and the touch and lcd screens aren't functioning, but I can plug it in and access memory via usb.
Secondly, I've received the replacement phone. Is there an order I should do all of this in? My first guess is to root/backup the old phone (if possible), then activate the new phone, then root/restore on the new phone. Does that sound about right?
Click to expand...
Click to collapse
The phone with the broken screen isn't rooted already? If it is rooted this may help: http://forum.xda-developers.com/showthread.php?t=2353828

Cosmic Phoenix said:
The phone with the broken screen isn't rooted already? If it is rooted this may help: http://forum.xda-developers.com/showthread.php?t=2353828
Click to expand...
Click to collapse
Thanks, I found that thread too actually, but this phone isn't rooted. I was mainly contemplating root, if it's an option, as a way to take advantage of the more expansive toolset/backup options available to rooted phones in the toolkit. I just wasn't sure if rooting was an option for a phone with a broken screen.

aolbites said:
Thanks, I found that thread too actually, but this phone isn't rooted. I was mainly contemplating root, if it's an option, as a way to take advantage of the more expansive toolset/backup options available to rooted phones in the toolkit. I just wasn't sure if rooting was an option for a phone with a broken screen.
Click to expand...
Click to collapse
Oh, ok. I hope someone comes along to answer your question because now I'm curious... lol.
Edit: Also posted your link in that thread to possibly grab someones attention

Cosmic Phoenix said:
Oh, ok. I hope someone comes along to answer your question because now I'm curious... lol.
Edit: Also posted your link in that thread to possibly grab someones attention
Click to expand...
Click to collapse
Awesome, thanks. I checked on that post and someone responded about having usb debugging on...which I don't. So it looks like I may have to just do the straight backup without rooting unfortunately. :/

You don't need root to use my method, you just need a custom recovery...and remember NOT to boot into the system at all, only recovery or else the stock recovery will be reflashed
Sent from my S3 on Sense 5 (you jelly?)

CNexus said:
You don't need root to use my method, you just need a custom recovery...and remember NOT to boot into the system at all, only recovery or else the stock recovery will be reflashed
Sent from my S3 on Sense 5 (you jelly?)
Click to expand...
Click to collapse
Followed the instructions on the post, and when I get to "./adb devices", I get "Permission denied" in terminal. This is with booting into recovery.

That means that the adb binary on your computer doesn't have executable permissions. Nothing to do with the phone.
Sent from my S3 on Sense 5 (you jelly?)

CNexus said:
That means that the adb binary on your computer doesn't have executable permissions. Nothing to do with the phone.
Sent from my S3 on Sense 5 (you jelly?)
Click to expand...
Click to collapse
Ok, so tried this again, as I'm less familiar with terminal on my Mac than I am on my PC. Got my device discovered, twrp.img loaded into tmp. But when attempting to install I get a "/dev/block/mmcblk0p18: cannot open for write: Permission denied"

[Q] Bricked T999L Failed Bootloader update

Hi! I need some serious help. I accidentally bricked my phone while updating the Bootloader.
It's a Samsung Galaxy S3 SGH-T999L (T-Mobile, but it works with my Vodaphone SIM)
Absolutely nothing on the screen, no boot, no recovery mode (just installed CWM), no download mode. Just a red LED when plugged in via USB.
Device Manager shows this: "QHSUSB_DLOAD"
I live in Egypt so there's no such thing as 'insurance' or 'warranty'.
I tried the instructions here: http://forum.xda-developers.com/showthread.php?t=2439367
Didn't work.
Is this the end? Or is there yet hope for it?

Need to know the details of what you flashed and what steps you followed.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Need to know the details of what you flashed and what steps you followed.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I just installed the CWM custom recovery via Android Toolkit, and was preparing to flash Cyanogen. It said that an S3 needed a Bootloader update to install Cyanogen versions greater than 10.1, So I followed the links and I think I accidentally flashed the Bootloader for SGH-T999 (not the T999L).
CWM said it succeeded, rebooted the phone (did not fix root when it asked), and it just never turned on since (it's been a while)

P.s: Idk if this even matters when its as deep as the Bootloader, but the phone had been rooted for months before.
Oh, and I found this and am downloading the latest T999L in case I need it if ODIN can help: http://forum.xda-developers.com/showthread.php?t=2439367
And from yet more Google I found these drivers, but it won't let me post outside links
But Device Manager says "Driver is not intended for this platform."
That's all I got so far, will keep looking for a good driver and check this thread as often as I can

This is gonna probably sound stupid, but I tried an emergency recovery with Kies, but it needed me to get it in Recovery Mode.
No change so far. Any help finding the right drivers would be very helpful.

Kygies27 said:
This is gonna probably sound stupid, but I tried an emergency recovery with Kies, but it needed me to get it in Recovery Mode.
No change so far. Any help finding the right drivers would be very helpful.
Click to expand...
Click to collapse
YAY! Found working drivers here: http://forum.xda-developers.com/showthread.php?t=1536354&page=4
By: richardlibeau
ATTACHED FILES
File Type: zip QHSUSB_Drivers_(x64).zip - [Click for QR Code] (72.3 KB, 568 views)
File Type: rar qhsusb_dload_Drivers.rar - [Click for QR Code] (56.0 KB, 584 views)

More Google (Where is everybody?)
Found this: http://forum.gsmhosting.com/vbb/f824/karbonn-a9-dead-qualcomm-hs-usb-qdloader-9008-how-fix-1740061/
It seems if I can just find the corresponding hex files, etc, this could work.
Or I could somehow reprogram my CPU and make things even worse...
I'm really stuck now.
P.s: I've ofc by now seen nearly everyone go for a JTAG repair. I will check the shops around here when they open, but I don't know if they can do anything about it.

Jtag should be able to repair that kind of brick. Unfortunately, when its due to flashing a different devices firmware, our device methods won't usually work.
You can try the d ebrick method we have posted in development, but just don't expect much. (You never know though, you might get lucky).
I doubt following this instructions will work as they are for a different device. Big risk to try it imo. Might make it non-recoverable by any means. (The process might work, I don't know, but you'd likely need specific files for your device).
Jtag is probably your best option. And in the future, stay away from the toolkit! Its bricked a number of devices and the dev just ignores support requests, even from those who buy it...
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Jtag should be able to repair that kind of brick. Unfortunately, when its due to flashing a different devices firmware, our device methods won't usually work.
You can try the d ebrick method we have posted in development, but just don't expect much. (You never know though, you might get lucky).
I doubt following this instructions will work as they are for a different device. Big risk to try it imo. Might make it non-recoverable by any means. (The process might work, I don't know, but you'd likely need specific files for your device).
Jtag is probably your best option. And in the future, stay away from the toolkit! Its bricked a number of devices and the dev just ignores support requests, even from those who buy it...
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yeah, shops open soon so hopefully I can see what can be done.
I figured not to bother with the qualcomm tools, messing with things I didn't quite understand was how I got in this trouble in the first place.
But just to clarify something, the Android Toolkit wasn't what bricked it, I tried to install the firmware from a .zip on my SDcard viz CWM recovery, but it was the wrong one (I was so damn sure I was T999, not T999L).
Thank you guys for all the help, I'll post if the guy fixes it!

I know, I only mentioned it because you mentioned using it. Just warning you for the future is all.
Good luck!