So I just got back from the sprint store for warranty issues with a nonworking gps. I had my phone rooted but here's what I did before I went there. 1. I used triangle away for my SII and checked to make sure it worked which it did. 2. I odined back to stock unrooted FI27 and did a factory reset to delete everything on the internal sd card. 3. I left my external sd card inside which I forgot to format (I had things related to rooting inside like custom roms and stuff but the phone itself was unrooted). When the sprint technician came out, he said my phone was rooted and that would void the warranty but he would overlook it just this once. He said the phone was fixed but it wasn't so sprint is sending me a new phone. How was he able to detect it was rooted when everything basically on the phone was unrooted? He said there were things on it like pimp my rom lol (I had that on my external sd card). When I get the new phone, should I root it after making sure everything is ok? I don't want the phone flagged or anything but I love installing custom roms.
Dont leave your sd card in. Its likely he looked inside saw it and knew you wouldn't need it unless you rooted. Check the phone out when you get it. If its good then root. If not return and make sure to keep your as card. When I hand in my phone for repairs I always have it completely wiped. I also tell them I have no sd card.
sent from MY BAD A$$ ET4G
Related
Okay, i'm new here but reading all of your threads is just confusing me.. there is so much conflicting information.
To begin, I bought my phone at the sprint store before i was even considering this thing called "rooting". I did the OTA update, didnt know any better at the time... however I did toast's root and I honestly have no idea if i got it to work or not but I was able to do the ad blocking thing and what not.....
I started having an Sd card error on my camera, telling me i had "insufficient rights" to the card...
and the video camera in Qik simply didnt acknowledge that there was a card at all and to insert one.
Now. I attempted the OTA, to fix the SD card, and i thought it worked at first but then it acted up again.....
Now i'm hearing this thing about Unrevoked?? if i have already done it toasts' way can i still run unrevoked or is it advised that i flash it back to stock rom and wipe all my data AGAIN....
anyways heres the funny thing...
i had an extra 8GB micro sd card from my Touch Pro 2, and I put in my EVO and formatted it... and.... now everything works fine....
my version is still 1.32.651.1
What should I do now? Since im not having any problems since i changed the card...
is there data on that card is necessary? or that i can just transfer over?
I dont want to perform the OTA again, but i know if i did it would answer alot of questions based on the result...
I need advice...
Moved as not Android Development.
ok, so I'm going to be selling my phone here soon and what i'd like to do is clear all of my items off the sd card by reformating it. I understand my backups will also be cleared off of it as well. My question is... once I'm on the rom I want and I do a reformat of the sd card that wont disable any of my rooting abilities will it? I understand it will remove the pc36img and all my stuff but if I'm on a rooted rom and I reformat the sd card will I will be able to go into recovery and perform a nandriod back up of the current rom I'm running as I normally would?
any input would be greatly appreciated.
thanks
p.s. also does anyone know how much the evo 3d will be if bought outright? Curious as to the answer because I was reading online it will be 499 however when I went into the local spring store the guy said 599....
thanks again!
Root will keep working fine.
thanks, and I will still be able to perform backups for the rom? kinda laymens questions but just being safe.
Yes you will
nvm............
hey since my screen went to crap and has lines all over it now, its gotta go back to t-mobile when i get my new one. so first off should i even unroot it? it still has stock rom on it, and second, if i do unroot it, does it delete anything from the sd card? cause if so ill back it up on my comp first.
Hi
I hope someone can help. I was trying to install kings 7.2 rom on my evo. It was already rooted and running a custom rom. During the install it failed. When I rebooted S was on. I think had to find an old ruu image 2.1 to install. Now the phone will not charge and I have lost custom recovery.
What can i do?
My mac and my pc do not see the phone.
I have tried several different pc36img files and all they each fail.
the phone sometimes vibrates 5 times on reboot.
sprint also told me there is no 2.3 update.
Thanks
do you have an sd card reader
can you just root it again, and start from scratch?
dont see how flash a custom rom can unroot you unless you flashed a ruu by mistake, but all of kings roms are named so that you cant mistake them for ruu's lol
it was a kings rom from one of those multiupload sites, but i may have made a bad copy to the sd card.
i have an sd card reader but the phone is not successfully installing any pc36img files.
sprint has agreed to send me a replacement phone. i might be screwed if it has the newest rom already in it and now way to root.
nolig2278 said:
it was a kings rom from one of those multiupload sites, but i may have made a bad copy to the sd card.
i have an sd card reader but the phone is not successfully installing any pc36img files.
sprint has agreed to send me a replacement phone. i might be screwed if it has the newest rom already in it and now way to root.
Click to expand...
Click to collapse
sprint will most likely give you a refurbished phone, whether or not it has the gingerbread update is up in the air. another guy in another post got one and it was 2.2 so you never know, might have a bad sd card, can you get into the bootloader? just the PC36IMG.zips wont update? if you can and the PC36IMG.zips are moving to sd card but not running like they should be (bootloader loads, reads, asks if you want to update, ask to reboot) then your either getting wrong PC36IMG.zip or something is getting lost on the way to your sd card.
So like the title says, I lost my SD card access today. I'm not blaming the nitest kernel, but it's the last thing I installed from TWRP so I'm at a loss for the cause. So far I've tried (without success):
Formatting SD card in PC
Using several different SD cards
Trying to mount in CWM and TWRP and Stock Recovery
Flash FC09 Stock from Odin
blow on it
Is there any other cause that could point to this? I didn't drop it or take a hit to it the day it happened, so i find it hard to believe the hardware just "died".
alexcu said:
So like the title says, I lost my SD card access today. I'm not blaming the nitest kernel, but it's the last thing I installed from TWRP so I'm at a loss for the cause. So far I've tried (without success):
Formatting SD card in PC
Using several different SD cards
Trying to mount in CWM and TWRP and Stock Recovery
Flash FC09 Stock from Odin
blow on it
Is there any other cause that could point to this? I didn't drop it or take a hit to it the day it happened, so i find it hard to believe the hardware just "died".
Click to expand...
Click to collapse
Very strange indeed. My gut says hardware failure, but I'd give this thread some time for others to read and give input.
Sent from my SPH-D700 using Tapatalk 2
Ok, this is really weird...
So I'm here on my freshly ODIN'd FC09 stock image, sitting still on my desk, nothing out of the ordinary.
I start installing apps remotely from the play store, and while the apps are downloading and installing I get a media scanner notification, followed by a mounted SD card.
CWM/TWRP now fully recognize the card, it seems like its seemingly back to normal.
While I'm happy it's working again, I'm no closer to actually figuring out what really happened. The physical contacts are all cleaned, and no physical deformities are seen. It seems I will be perpetually living in fear of my SD card randomly failing.
If anyone else has had this happen, I'd love to know the background on how it happened. I'm sorry to everyone else who googles this looking for a fix, it seems like I just got lucky...