Ok, here is the breakdown:
Tried to root my phone using Odin.
The .tar file uploaded successfully "passed"
Went to reboot the phone, and it got stuck in a boot loop (droid, mechanical eye, droid, etc)
Found out I loaded an old version of the .tar file.
Did a factory reset using volume up, home and power.
SO MY QUESTION IS, WELL VERIZON HAVE ANY KNOWLEDGE THAT I TRIED TO ROOT MY PHONE? I'M SENDING BACK FOR A FAULTY CHARGE PORT, THEY SENT ME A REPLACEMENT, AND I WANT TO MAKE SURE THEY WON'T KNOW I TRIED TO TAMPER WITH IT.
Once I factory reset my phone, it was trying to do automatic updates, and kept failing during the install... Didn't know if I have to remove the .tar using the Odin somehow.
Please help!
Thanks!
Most people say they never look and have returned stuff rooted. If your that worried about it re download the files and ODIN again shouldnt take very long and is easy to do. Ahh I read you did a factory reset, guess I should learn to pay attention. I would just return and not worry.
I would return it to stock EE4 and OTA to GB or flash that stock all in one rom... most likely they won't even see anything or notice, but I'd do it anyway since I wouldn't wanna risk getting slammed with the full cost of the phone
sent from my Acer Iconia A500 beast of a tablet via XDA app
How do I remove the rooted software and install the original EE4?
How can I insure that it is correct?
paku12 said:
How do I remove the rooted software and install the original EE4?
How can I insure that it is correct?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1111486
Pretty much explains it there. Follow the instructions step by step then ask if you need to.
I'm one of those people who think the don't check very closely. Think how many phones, not just charge, but all smart phones that go back every day. I can't imagine the line workers who receive the returns have much incentive to find rooted phones.
But just the same. . .
But if you are returning a phone there is no downside to going back to stock. It only takes a few minutes.
Sent from my SCH-I510 using xda premium
Related
I'm returning my current Captivate to ATT because it has way too many random shutdowns, it gets really annoying having to boot up the phone every 5 minutes. They sent me a replacement but currently I can't get ODIN to recognize the phone so I can flash it back to stock. I have Continuum running on it right now.
Could I just remove root and send the phone back? Or does anyone here have experience returning a phone with a custom ROM back to ATT? I don't want them to call me back and blame the custom ROM for the shutdowns and then in turn charge me for the replacement.
Thanks.
Yes you have to use one click and return to stock before returning phone. Custom roms and root void warranty.
Turn phone off. Plug in usb to pc. Hold volume up+down. Plug in usb to phone. Should go into dl mode and press start on one click odin.
Sent from my GT-I9000 using XDA App
I have a similar question, I have loaded GB continuum rom. If I return to stock with the one-click return to stock, will restore all GB boot loader?
Luckily I have an ATT return center not too far from me. I can walk in there and get a replacement. I am hoping to get one with better GPS performance (I know they exist).
random228 said:
I'm returning my current Captivate to ATT because it has way too many random shutdowns, it gets really annoying having to boot up the phone every 5 minutes. They sent me a replacement but currently I can't get ODIN to recognize the phone so I can flash it back to stock. I have Continuum running on it right now.
Could I just remove root and send the phone back? Or does anyone here have experience returning a phone with a custom ROM back to ATT? I don't want them to call me back and blame the custom ROM for the shutdowns and then in turn charge me for the replacement.
Thanks.
Click to expand...
Click to collapse
Removing root wont change the fact that you have a custom rom. Make sure your in download mode on your phone, make sure odin is open first then plug in your phone. If it wont recognize your phone, try other usb ports or restart your comp. Make sure you use one click odin.
hashish16 said:
I have a similar question, I have loaded GB continuum rom. If I return to stock with the one-click return to stock, will restore all GB boot loader?
Luckily I have an ATT return center not too far from me. I can walk in there and get a replacement. I am hoping to get one with better GPS performance (I know they exist).
Click to expand...
Click to collapse
If you use the one click odin and master clear it will look like you never modded your phone.
I just did this at lunch today. Was having so many problems with my phone. 100% Sure I had faulty hardware and nothing software related. So this is what I did. I Odin-1 Clicked back to stock. Well one of my issues I was having was that even with Odin I would get a boot loop. It did get past the sbin and bootloaders, and replaced the flash screen with ATT and those annoying 3G Bars. Didnt even waste my time going to a retail store, went straight to a warranty store. In the store I explained the boot issue, and I was out with a replacement within 10 minutes. Granted if your Odin-1 Click works, you should be fine.
Sweet guys, thanks! I'll probably do this sometime next week.
Cool, thanks for the replies. I'll give it a shot on another computer because I can't seem to get ODIN to recognize the phone. I've tried 3 different USB cables. ODIN does recognize the phone when its on and running but I know you can't do anything with ODIN if the phone is on.
Try reinstalling pc drivers for phone see if that works.
Sent from my GT-I9000 using XDA App
...and using the back USB connectors if you are using a desktop.
Thanks guys. I was really trying to do this and this thread confirms all my questions.
Sent from my Galaxy S captivate
I did the easy unroor because my usb port is broke. But the superuser app is still there and I cant get rid of it. Need to rma. Any ideas?
I know of a guaranteed way to return to stock, but it's done through NVFlash in which you will need your usb port. You could either...
1. Look into other ways to return to stock which doesn't involve using your usb port (not likely)
2. Go to asus's website and download the firmware and place onto an sd card and see if you can do it that way. Even still, I'm not sure if that will just update, or wipe and update.
3. Shut down your TF and boot up by holding the volume down + power until you get to the option to wipe data and see if that does the trick. Once you get to that option, you only have like 5 10 seconds to select to wipe. If you don't select to wipe, then it will timeout and reboot
cavsoldier19d said:
I know of a guaranteed way to return to stock, but it's done through NVFlash in which you will need your usb port. You could either...
1. Look into other ways to return to stock which doesn't involve using your usb port (not likely)
2. Go to asus's website and download the firmware and place onto an sd card and see if you can do it that way. Even still, I'm not sure if that will just update, or wipe and update.
3. Shut down your TF and boot up by holding the volume down + power until you get to the option to wipe data and see if that does the trick. Once you get to that option, you only have like 5 10 seconds to select to wipe. If you don't select to wipe, then it will timeout and reboot
Click to expand...
Click to collapse
I already installed the original stock rom. And also flashed the stock recovery. I wiped everything each time. But after all that superuser is still there.
Well that sucks. I know of a way to do a full wipe of everything by using a full wipe utility that is flashed by clockworkmod recovery. But then you would have to find a way to restore the stock recovery in order to flash the stock rom. If you do a full wipe without reflashing a rom, then you will have soft bricked it. You might be SOL on that.
cavsoldier19d said:
Well that sucks. I know of a way to do a full wipe of everything by using a full wipe utility that is flashed by clockworkmod recovery. But then you would have to find a way to restore the stock recovery in order to flash the stock rom. If you do a full wipe without reflashing a rom, then you will have soft bricked it. You might be SOL on that.
Click to expand...
Click to collapse
So you think if I wipe it so its in the initial setup. That asus will set it up and see superuser. I mean can they even prove anything just cause theres an app there.
lightsout said:
So you think if I wipe it so its in the initial setup. That asus will set it up and see superuser. I mean can they even prove anything just cause theres an app there.
Click to expand...
Click to collapse
Not sure about that. Ideally, when doing rma returns, to be on the safe side, you want to make it completely transparent that it was ever rooted/rom'ed. I've read posts where some people were successful with returns/exchanges while the device was rooted, without repercussions. It's all up to the return policies of where you bought it, as well as asus. Considering that asus has gone out of their way to change and lock down the bootloader on newer revisions, apparently asus does not want to be development friendly at this time, and may penalize you for returning a modified system.
cavsoldier19d said:
Not sure about that. Ideally, when doing rma returns, to be on the safe side, you want to make it completely transparent that it was ever rooted/rom'ed. I've read posts where some people were successful with returns/exchanges while the device was rooted, without repercussions. It's all up to the return policies of where you bought it, as well as asus. Considering that asus has gone out of their way to change and lock down the bootloader on newer revisions, apparently asus does not want to be development friendly at this time, and may penalize you for returning a modified system.
Click to expand...
Click to collapse
Yah I know man thats what I'm afraid of. I mean anyone can install superuser. But I guess though it wouldn't be there on a clean install
Kind of stuck here. Its too late to return tot he store. But I don't want to be stuck with a bad usb port forever. I guess the worst that can happen is they refuse it.
Or if they accept it at first, then asus realizes that its been rooted, they could send u a bill for full price of the replacement. Although I've never heard of that happening. Another extreme measure u could look into is seeing if u could order a motherboard or replacement parts and fix it yourself.
Sent from my Inspire 4G using XDA App
cavsoldier19d said:
Or if they accept it at first, then asus realizes that its been rooted, they could send u a bill for full price of the replacement. Although I've never heard of that happening. Another extreme measure u could look into is seeing if u could order a motherboard or replacement parts and fix it yourself.
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
Ouch that would suck, as far as doing it myself I really don't want to mess with popping it open. It still charges, but I can't hook it to a pc. So I would rather have it like that then broken because I opened it.
I guess I'll just put it off a little more.
True. If I were u, I would take my chances with returning it. Just make sure u have the cash just in case they decide to be dicks about it.
Sent from my Inspire 4G using XDA App
Yes, this may be the wrong thread. Yes I know I am a noob and I apologized.
But I seriously think I effed up my phone and I really need someone to help me fix it. I was trying to root it via this youtube vid:
How to Root Samsung Galaxy S 4G Gingerbread 2.3.6 Part 1
But now it's stuck in an infnite static boot loop and sometimes won't even turn on. Is there any possible way to fix this or at least get it back to it's original software
Please help!!!
can u get into download mode?
Yes I can. Is there a kill disc program or something I can download to completely reinstall my original android software? At this poinnt I just want it back to where it was
You will hv to download ur phone's firmware an use odin to restore it to factory defaults, just google search ur phone's firmware ul find it an use odin ul be good
hey i tried that and i have SU and CWM app. is that considered rooted?
RaptorF22 said:
Yes, this may be the wrong thread. Yes I know I am a noob and I apologized.
But I seriously think I effed up my phone and I really need someone to help me fix it. I was trying to root it via this youtube vid:
How to Root Samsung Galaxy S 4G Gingerbread 2.3.6 Part 1
But now it's stuck in an infnite static boot loop and sometimes won't even turn on. Is there any possible way to fix this or at least get it back to it's original software
Please help!!!
Click to expand...
Click to collapse
1. Get odin
2. Google search your phones factory firmware
3. Google search how to Factory Reset from boot cause im to lazy to go that far. its all over this forum.
and for the dude above me. just cause you have superuser on you phone does not mean it is rooted. have you used applications like setCPU, if so does it allow root access. if not you do not have a rooted phone. superoneclick. use it. its geat
Yeah, Odin is your best bet to go. Make sure you get the correct firmware. Whatever you do do some research on the stock Galaxy S 4G Gingerbread firmware if you make a mistake loading the wrong files and letting odin to go to work you will dead brick the phone. There will be a still chance on recovering it but you will need a person that can do that and there are some here, they will charge you like $30 for it at least. Good luck
If you have those on your phone then you are rooted
Sent from my VS910 4G using XDA
I'm a woman noob and in the process of trying to unroot my EVO I must've gotten the wrong img zip and it sent my phone back to dinosaur ages! I have android 1.3 running on it and I have no idea how to fix it. I am all over paying someone to help me. If interested please PM me!
Sent from my Droid using XDA
I'm back to stock. I used RUU. I lost root but that's ok. I'm still relieved.
Sent from my PC36100 using XDA
I screwed up my phone, I rooted it and was uninstalling some bloatware that came with it (sound hound, check-in app etc) but I deleted something important and for some reason I my internet browser was uninstalled and I cannot install CWM (will clarify below). Before my brower was uninstalled I was unable to install any more apps (things from the Market would download, but never install), so I tried a factory reset (being stupid since I uninstalled so much from the stock ROM) and then my browser was gone.
Being a total moron I did not back anything up, so I thought I could install CWM to just reflash the stock ROM. I rooted my phone successfully (following htc dev) but could not install CWM, after flashing the .img file and rebooting it just reboots as normal and shows no evidence of CWM being installed.
My phone is a Rogers HTC One X and I've been making sure to find the guides for Rogers/AT&T HTC's, but I'm still failing .
Use ADB to push the missing apps to the phone?
But it sounds like you want to restore the phone to the state it was before you removed apps?
If so, first step is to get a working recovery. Can you get Rom Manager on your phone? If so, you could flash CM from there.
If not, find a thread on flashing recovery. I have not yet rooted mine so can't be more specific.
And you do know how to get into recovery by holding volume down and power etc? Sorry if I underestimate your experience but sometimes people miss basic stuff.
Sent from my EPAD using Tapatalk 2
Whatever you do, don't flash an HTC official RUU (rom) over all of this.... The only hard bricks you read about are caused by people flashing manufacturers' roms after rooting.
Edit: I see from comments below it appears that some people think I was being sarcastic in making this post: however, see this thread:
http://forum.xda-developers.com/showthread.php?p=22897771
I have seen a number of other warnings over the years of inexperienced users who try to get out of trouble by simply applying manufacturers' updates or factory images to an unlocked phone with a custom recovery and make things much worse.
Sent from my EPAD using Tapatalk 2
How do I use ABD to push missing apps back? Don't worry about underestimating my knowledge at all, this is my first android phone.
I googled how to install custom ROMs and CWM and TWRP came up, I tried both and neither installed. I unrooted my phone successfully and started phone in fastboot, flashed the .img files and then restarted but nothing new was installed.
tangiers said:
Whatever you do, don't flash an HTC official RUU (rom) over all of this.... The only hard bricks you read about are caused by people flashing manufacturers' roms after rooting.
Sent from my EPAD using Tapatalk 2
Click to expand...
Click to collapse
Why are you saying that? Nobody is hard bricking a phone by flashing the correct RUU.
Whatever you do, don't flash an HTC official RUU (rom) over all of this.... The only hard bricks you read about are caused by people flashing manufacturers' roms after rooting. <br />
<br />
Sent from my EPAD using Tapatalk 2
Click to expand...
Click to collapse
Funny guy.
Sent from my HTC One X using xda premium
The FUD is strong in this one...
So what do you guys suggest I do? Should I just bring it back to the store? I got it like four days ago. How do I unroot it? I can't access the market (no brower or market app) so I can't get SU to unroot.
to get back to factory you can do the following
relock the bootloader.
reboot to bootloader and use the command fastboot oem lock
after that install the 1.85 RUU from here http://forum.xda-developers.com/showthread.php?t=1670238
it will take longer than the 10 minutes it says it will take so don't worry.
after that you can unlock again with that same token you used to unlock in the first place.
I'm at work right now so I can't do that yet
If I bring it in without doing that stuff will they know or even care? I have some BS story made up D). Also mine is a Rogers, but the AT&T stuff works with it right?
I appreciate your quick responses
Rogers phone would need rogers ruu loaded
ATM I still have the Rogers RUU, just broken XD
Would it be enough to just lock the blootloader again before returning it to the store?
bman3k said:
ATM I still have the Rogers RUU, just broken XD
Would it be enough to just lock the blootloader again before returning it to the store?
Click to expand...
Click to collapse
why do you want to return it? For this problem or is there something else?
Yes it is for this problem (and all the ones in the first post) I tried for several hours last night to fix it, but couldn't.
I followed the guides for how to install CWM and TWRP to the word and they would not install. If I cannot install them, I cannot reflash stock RUU right?
I still want the HTC One X... just one I didn't screw up XD.
This will put you back to stock and you won't need to return anything
http://forum.xda-developers.com/showthread.php?t=1658929
Ok, I'll try that when I get home, thanks for your help.
PJ83IMG_Evita_UL_Rogers_WWE_1.73.631.1_Radio_0.16a.32.0... from http://forum.xda-developers.com/showthread.php?t=1543593 is what I'll need right?
Correct.
Thanks for your help, that last guide you linked solved it. The first time I looked at it I misread "lock" for "unlock", but I got it to work now . Thanks for your patience and help gunny.
No problem. I'm glad you got it sorted.
I just got my rogers one x and, I'm fairly disappointed in the storage capacity. What advantages would I gain from routing a phone that is already as fast and responsive as it is?
Sent from my HTC One X using xda premium
Before you post, "BLAKDSKF READ OTHER FORUMS BLUSDFLU!!!!!!!111!!!", please, PLEASE, read the whole post. I am not illiterate or a fool. I've spent the last few days researching similar posts, both on xda and other sites, and as far as I've found, this is the only post of this kind on the Verizon SGSIII forums, though there are some that are somewhat similar in the other SGSIII forums (though I think the root of the problem is different). If you can prove me wrong, please redirect.
The Long Story:
ok. SO. I was trying to root my SGSIII, unlock the bootloader, and install CM10. Simple enough, right? Not so. I got through the rooting tutorial at Link 1 relatively smoothly. For the record, I did the composite root and bootloader combo, and I installed CWM Touch Recovery, as per the guide. I also restored the Jellybean Bootchain. I think it was at this point I downloaded Titanium Backup (because forethought is not my forte) and backed up all my apps. I also made a backup with CWM Recovery, but there were errors. I forget the reason, but it aborted backup. I then tried to make a backup onto my external sd card, and some other errors popped up. Mainly that it couldn't find /android.secure (something along those lines) or /sd-ext (might have been something else. I'm going off memory) and skipped them. It still made the backup, so my illiterate, foolish self decided to roll with it and go ahead.
I then went ahead to Link 2, and with it being 2 AM, I stupidly decided to screw trying to figure out how to use Heimdall 1.4rc1 and continue to use ODIN for flashing. After all what's the difference, I thought. One flashing program is the same as another. I flashed the first two files. Well, in truth, I'm not sure if I flashed the first file. Since I just made a single folder for all the SGSIII Verizon flashing stuff, I had two files with similar names at the time. One from Link 1 and one from Link 2. The only difference was one was a boot chain, the other was a boot loader. Also, one ended with .md5 while the other ended with .tar. Sadly I tiredly picked one and flashed it. I think it was the .md5 one, but I'm not sure. Around this point, my micro sd card reader broke, so I decided to just use my other phone (Motorola Photon 4g running Joker's CM9) as a reader of sorts. I swapped them, used my phone to put the zip from Link 2 on it, and swapped them back. I say this because I'm not sure if that is what broke my md5sums or not (more on that in a sec).
Well, surprise, surprise, my phone got stuck on the animated, colorful "4G LTE" boot screen, except it was fully black, though the noise was playing. I think to myself, "No biggie. I'll just restore my previous backup," so I go back to restore it when I get the error 'md5sum mismatch'. I look up the problem, and after extensive, 3AM research (read: clicked the first link on google and blindly followed), I went with one guys advice, which was to create a blank nandroid.md5 file to force the restore. I figured, "Hey. This is pretty risky. I think I'll just restore the bootloader instead of the whole restore." Or at least that's what was going through my head as I went through with restoring the whole backup. Lo and behold, /system was corrupted, I assume, and it aborted restoring it. I reboot my phone only to find out that my phone gets stuck on the SGSIII boot logo. This is where I am now. I would go through with flashing a stock rom onto it to undo everything I've done, but ODIN won't recognize my phone anymore. I can still get into Download and Recovery Mode. All my backups are useless at the moment.
In Short:
I tried to root, unlock the bootloader, and flash CM10 on it
I messed up and ended up restoring a broken backup, md5sums be screwed.
Now ODIN won't recognize my phone and it's stuck at the SGSIII boot screen.
Is there any way to fix this or at least return it back to stock so I can start again?
If there's any other information you need, just ask. I'd be happy to give it. :laugh: This is my first post on these forums, so I'm not sure what information is standard. If you have any idea of what it might be, please drop a comment or something rather than just leaving. I'd like to know that people are actually reading this post.
And on an unrelated note, every time I try to flash with Heimdall, I get an error about there not being a certain .dll file, even though I downloaded the package from Link 2. Am I doing something wrong?
EDIT: I've already tried factory resetting and wiping the cache/dalvik cache. Most of my info is backed up anyway.
Links:
Link 1: http://forum.xda-developers.com/showthread.php?t=2046439
Link 2: http://wiki.cyanogenmod.org/w/Install_CM_for_d2vzw
What happens when you plug your phone into your PC? Have you tried deleting the drivers then reinstalling them either from Samsung or from the Kies program? You really have to try to mess up this phone and it seems like you definitely tried very hard in this regard.
Edit: Idk anything about Heimdall, I use Odin only so I can't help you there.
SlimSnoopOS said:
What happens when you plug your phone into your PC? Have you tried deleting the drivers then reinstalling them either from Samsung or from the Kies program? You really have to try to mess up this phone and it seems like you definitely tried very hard in this regard.
Edit: Idk anything about Heimdall, I use Odin only so I can't help you there.
Click to expand...
Click to collapse
I hadn't noticed before, but my phone doesn't even show a charge screen when plugged in, but that might just be the settings on the phone pre-root. I'm not sure because I left the phone on to see if it was just a time thing. The phone died and I have to recharge it.
After goofing around with the phone while on the charger for a while, I can get a charge screen to show up for a second. The standard "battery with a loading circle" type symbol for this type of error.
I just reinstalled the drivers. I'll let the phone charge for about 10 minutes or so, then test the phone.
dudeman9199 said:
I hadn't noticed before, but my phone doesn't even show a charge screen when plugged in, but that might just be the settings on the phone pre-root. I'm not sure because I left the phone on to see if it was just a time thing. The phone died and I have to recharge it.
After goofing around with the phone while on the charger for a while, I can get a charge screen to show up for a second. The standard "battery with a loading circle" type symbol for this type of error.
I just reinstalled the drivers. I'll let the phone charge for about 10 minutes or so, then test the phone.
Click to expand...
Click to collapse
Well if it died you should leave it on the charger longer than ten minutes if it is charging. If Odin recognizes it, your first step would be to try flashing a stock image.
SlimSnoopOS said:
Well if it died you should leave it on the charger longer than ten minutes if it is charging. If Odin recognizes it, your first step would be to try flashing a stock image.
Click to expand...
Click to collapse
Thanks. It would seem that it now recognizes the phone, from what I can tell. As soon as I get a stock rom, I'll flash it and post an update.
dudeman9199 said:
Thanks. It would seem that it now recognizes the phone, from what I can tell. As soon as I get a stock rom, I'll flash it and post an update.
Click to expand...
Click to collapse
Great! Use Droidstyle's guide or MrRobinson's thread for the proper images. Should be a good starting point.
Sent from my SCH-I535 using xda app-developers app
I just wanted to add that THIS is how you do a first post or any help needed post! Great details and is obvious you researchedyour problem as well.
The errors in cwm are actually normal. I think the corrupt backups are unrelated.
Sent from my SCH-I605 (AKA NOTE 2)
SlimSnoopOS said:
Great! Use Droidstyle's guide or MrRobinson's thread for the proper images. Should be a good starting point.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I've finally booted up into the setup wizard. I guess from here on I can re-root, unlock the bootloader, and *hopefully* get a working backup and eventually flash CM10.
I guess this means Problem Solved? Again, Thanks.
kintwofan said:
I just wanted to add that THIS is how you do a first post or any help needed post! Great details and is obvious you researchedyour problem as well.
The errors in cwm are actually normal. I think the corrupt backups are unrelated.
Sent from my SCH-I605 (AKA NOTE 2)
Click to expand...
Click to collapse
Thanks. I'm just gonna assume that the problems stemmed from swapping the sd card and leave it at that.
dudeman9199 said:
Thanks. I've finally booted up into the setup wizard. I guess from here on I can re-root, unlock the bootloader, and *hopefully* get a working backup and eventually flash CM10.
I guess this means Problem Solved? Again, Thanks.
Thanks. I'm just gonna assume that the problems stemmed from swapping the sd card and leave it at that.
Click to expand...
Click to collapse
Perfect! Which thread did you end up using btw?
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Perfect! Which thread did you end up using btw?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I used droidstyle's thread for getting the stock rom.