Hi, A friend of mine just bought a s3 mini from another friend and we've found the phone has been rooted. After contacting our friend he doesn't even know what root is. But it was sent off for a screen repair a couple of months ago and came back with complete factory reset. Why would that have rooted the device (the insurance company) it seems unnecesary in order to replace a cracked screen.
I have two queries: a) can the phone be unrooted and how, none of us know how the phone was rooted or what was used.
or b) is there a way to still use the sky go app with the phone in its rooted state.
We also know next to nothing about rooting and not sure how to proceede from here.
you could try this..........
http://forum.xda-developers.com/showthread.php?t=1241517
Related
Bought the phone off ebay and it worked fine for about a month and today the screen will only work when slid out. If it is slid in place as normal the screen will only show the last thing on there but will not refresh. You have to slide it out partially to get it to respond to anything.
Is this a known issue?
that really weird. Is your phone rooted? If it is try to wipe and flash. If its not rooted do a factory reset to your phone. That might fix it. If it doesnt, then you should get a new phone hahaha OR just root it and it might fix it.
It's rooted but it also does it in recovery as well as booting up. I have talked to HTC and the phone is still under warranty so I am going to ship it off to them.
I guess I have to restore the device to stock now
decepticon said:
It's rooted but it also does it in recovery as well as booting up. I have talked to HTC and the phone is still under warranty so I am going to ship it off to them.
I guess I have to restore the device to stock now
Click to expand...
Click to collapse
decepticon, how easy was it to talk to HTC? I think (and am sure) my GPU/graphic memory area has corruptions and need to get it replaced too. I also bought it off ebay. I assume it was bought after June 2008 since some material was dated that and should be under warranty.
I remember I had a similar issue on a earlier version of Cyanogen (one of the versions before the Google legal scuffle) and a wipe and/or restore to an earlier backup fixed it. This might be a possible cure but again this is just for my instance.
You should try wiping rotation stats while in recovery mode.
Ok I have read about 50 different posts that are similar to my situation but none of them seem to be exactly what I'm looking for. Here is what is happening with a little background.
Running Stock 2.1 on a BELL Mobility Vibrant.
No Custom Roms.
I did have the OCLF installed (Almost 3 months ago without issue)
Phone is also Rooted
Last night I was at a friends place showing off my phone as they were ready to get a new one. I showed them all the cool apps, google maps, google Sky, Soundhound, Bar Code Scanner, etc.. They were sold and are no longer getting an iPhone.
I came home and went to bed. I woke up this morning and the phone was off.. I turned on the phone and once it booted up it said the battery was dead.. No problem.. Power the phone down.. Replace battery and reboot.
It would not reboot.. it gets stuck at the Galaxy S logo screen
My phone is one of these earlier models that doesn't have access to the 3 button recovery so I was using the ADB reboot-recovery to access the menu.. However, this no longer works.. it just reboots the phone and gets stuck at the logo.
I have tried ADB logcat and it just loops and loops.. (Thousands of lines of data)
I have tried a few different batteries.. I have tried powering it up connected to a wall outlet (power) as well as to the computer (it does detect the USB and makes the USB connect sounds (windows7))
Keis and ODIn both don't see the device.. (Not surprising)
Have tried 3-4 different methods to get to the download screen as suggested in other posts and none of them work.
Is there anything else I can try short of taking the phone back to Wireless Wave?
Just uploaded a dump of the logfile from AGB Logcat Cmd. In case that helps.
If you can't get the download screen, then your best bet is making a homemade jig. Search google for how to make one. I made mine when I encountered this problem and it works every time when I am unable to get a download screen.
I guarantee that it'll work for you as well. Good luck.
[HOWTO] [REF] Get Download Mode without 3-button combo using homemade JIG
Can you clarify? Are you unable to get into recovery AND download mode?
gtg2 said:
Can you clarify? Are you unable to get into recovery AND download mode?
Click to expand...
Click to collapse
Hey...my phone is currently stuck at a boot screen loop and it doesnt stop doing it. What can i do to fix this? I am able to get into download mode but not recovery mode. i know how to use odin, but can anybody guide me to which files i should use to put into odin to fix my phone? please help, thanks!! BTW, my phone is i9000 from BELL CANADA also!
Alright, follow this link and you'll get your three buttons working.
http://forum.xda-developers.com/showthread.php?t=785201
Make sure you get ODIN v1.3 and not v1.0 because the older one doesn't have a bootloader flash option.
zumi78878 said:
Hey...my phone is currently stuck at a boot screen loop and it doesnt stop doing it. What can i do to fix this? I am able to get into download mode but not recovery mode. i know how to use odin, but can anybody guide me to which files i should use to put into odin to fix my phone? please help, thanks!! BTW, my phone is i9000 from BELL CANADA also!
Click to expand...
Click to collapse
My Galaxy S from Bell is doing the same thing I spent 6 hours yesterday and so far 3 hours trying to get a replacement over the counter and so far its go to where you got the phone (Future Shop) they say only 14 day return window on this phone and mine started do it 16 days after i got it. Future shops says to go to Bell Store. Bell Store says Future shop should be handling this. now I am on my second call to Bell Corp and they are trying to keep me as a customer since I told them if this is not fixed today or replaced I am send the phone back and they can take their 3 year contract and stuff it.
so far looking good she is being very understanding and trying to help me
we shall see how this will go..
well 2 hours on the phone with them and the rep Named Laura is doing her best to get me a swapped phone today but she keeps hitting roadblocks between Future Shop and her own jobs corporate policies
with Bell this phone is 30 Days for straight across exchange but with Future Shop this is a 14 day policy since my phone died at day 16 its no longer covered by Future Shop and Bell hasn't been able to help me yet.
Laura is now trying to go above her bosses heads' and do good for me they have notes that my phone is considered DOA and should just be swapped by Bell Stores wont help me due to this phone being purchased at Future Shop
oh so frustrating...
UPDATE:
well after 2.5 hours on the phone with Laura and full of empty promises she cannot do anything for me Future shop has a 14 day policy Bell has a 30 Day policy and the phone is now 17 day old and nothing but a brick.
so I am heading to the nearest Bell store and dropping off the Phone and telling them to stuff the contract and all my bills good riddance.
nyk0n said:
so I am heading to the nearest Bell store and dropping off the Phone and telling them to stuff the contract and all my bills good riddance.
Click to expand...
Click to collapse
Let us know how that goes.
I predict the first murder in Canada inside a mobile phone dealership occurs in the next month over a Galaxy.
Are there any issues with this known, is there any tests that can be performed on the hardware? When I had WM6.5 I could test various hardware pieces such as the speaker, flash or display.
Non-Rooted
2.2.1
Baseband/32.36.00.28U_4.06.00.12_7
Kernel/[email protected]#1
Build/FRG83D
This is a phone that I bought my friend for his birthday. I have a Samsung Vibrant Galaxy S.
I actually plan to sell mine and get a Nexus One. I really like the phone better then my Vibrant.
If you haven't already, do a factory reset (settings>privacy>factory reset). Since your unrooted it's unlikely it's a software fault.
Second resort, call HTC. Warranty's are device based, not owner based, so if the device is still under warranty you can get a new one
As a last resort, if your warranty is expired, I would root it without unlocking the bootloader. Try a couple different ROM's and kernals and see if you get any results.
I actually had this problem a while back. I was getting FC's every time I tried to access the camera (through any app). I figured I dropped it and broke a connection or something inside. I finally called HTC and they sent me a new one.
I had to restore everything back to stock since it was running CM6. After everything was back to stock, the camera magically started working again (and I reverted to some nandroid backups from months before and the camera still didn't work then). I returned it for a new unit anyway and HTC didn't charge me or say anything.
Ok so this s6 i have had for less then 1 month is becoming a huge hassle. First it kept restarting by itself even during bootup. Sent in for repair samsung said nothing was wrng with it and sent it back... Got it back first startup it rebooted... Then after uaing it to 2% i charged it up and booted the phone, got a message "unauthorized att softwsre detected". Went to att they tried to reflash didnt help, told me to go to bestbuy samsung kiosk, they tried to reflash nothing... Told to call samsung and they would fix it, sent it in and they said thwy cant do anything cause its rooted. What can i do? And how did this even happen.
Did you buy it new, or used?
Brand new was orderd from att direct.
I actually have a video of the system saying it was custom then after i rebooted it went back to offical.
Actually starting to think samsung repair rooted the phone cause they couldnt repair it...
I'd contact Samsung again, explain the situation, and see if they'll replace it.
Tried they said cause its rooted they can't even touch it and since its rooted it voids the warranty and any connection to them... like WTF? My friend is on the phone with some manager at samsung right now :/. But my hopes are low. How does a company like this have such retarded policies. They can't even check the phone if its actually rooted...(they said they can't touch it cause the knox counter was tripped) I assume the binary somehow got messed up, hardware related? I bet if they just checked the software it would be official with chunks of code missing or something. I have video proof of it going from custom to official by itself without me having it plugged into anything. I have no clue who i can go to about this issue anymore, Phone is brand new (one month) and im still paying for it under ATT Next program...
Have AT&T check the serial and imei of the phone against your original order. Perhaps you got sent back the wrong phone from the repair depot? AoN
I checked the serial once i recieved it, it was the correct phone. I have video proof of it "rooting" it self. Basically the phone said it was custom then it a d it was offical after i rebooted it.(of course this was taken in two videos but u can see the time so no tampering could have occured.)
https://m.youtube.com/watch?v=WpxGI644OXA
https://m.youtube.com/watch?v=XJva5kmFLjE
So i figured out why it says i have a custom software... The BestBuy Samsung Rep flashed the wrong build to my device. They flashed "G925AUCU1AOE2" which i don't think is released yet or at least not pushed to my device. So any suggestions to what i can do? They cased my warranty to be voided and i still have the restarting issues.
Hello everyone,
I'm experiencing a pretty tough issue mith my beloved (and, so far, flawless) Nexus 6. It had root and a stock rom on it, 6.0.1 (MMB29V). I had unlocked the bootloader and rooted the phone right after buying it more than a year ago and I've been flashing new factory images a couple times (specifically when 6.0.0 and 6.0.1 were released). I usually do everything via Wugfresh's NRT, not because I can't use adb and fastboot, just because it works fine and I'm lazy.
Yesterday, while I was working, I used "Tiny Scanner Pro" to scan a document (legit copy bought on the store, as any other premium app in my phone) and it got stuck for a while, then a popup about Google Play Services came up. I dismissed it and another appeared, and it kept going like that. I was at a client's and I was in a hurry, so I took the pic with my tablet and forced the phone off. Later I turned it on, it seemed to boot regularly, but when the SIM unlock screen appeared and I entered the (right!) PIN, it said that no SIM was found, then the home screen appeared but after a while the screen went black and it started rebooting. Recovery (TWRP) and fastboot were working, so I decided to take it home and re-flash the stock rom: it had been a while since the last time anyway, a new version was out and the OTA update notification was getting annoying. I connected to my PC in recovery mode and transfered my pics and data via adb while I downloaded the latest stock rom (6.0.1 MOB30D). Then I user NRT to flash it (selecting "Soft-bricked/Bootloop" as current status). It appeared to work fine as it went through the usual copying and unpacking. Then, when the phone was supposed to reboot, it just blacked out. I waited a long time, in fact I went out and came back a few hours later, and it was still that way. Now it doesn't power up, no matter how long or hard I press any combination of the three buttons, adb and fastboot do not detect it in any way, of course, and it doesn't seem to charge either (i.e. I left it plugged to its original charger overnight and it still feels dead cold). By the way, the phone warranty shouldn't have expired, but I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
I've taken a look at similar threads but none of them describes the very same situation. Is there something, anything I can try to do before giving up? I hope somebody can help me. I thank you all very much in advance.
lupus
lupusyon said:
.... I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
Click to expand...
Click to collapse
Bricked!. When the phone is still under warranty send it for repair. Do not use arguments.
Just: phone will not switch on and does not charge.
Because this is a Nexus device, the custom recovery shouldn't affect your warranty. It is however, a moot point. The device is totally dead, and a call to Motorola is in order.
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
dahawthorne said:
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
Click to expand...
Click to collapse
I bought it on Amazon Italy Marketplace, I'm not sure if they're supposed to handle the thing or if I should contact Motorola. I'll just check with them first. Thank you everybody for the kind advice, I'll let you know how this turns out. :good:
I confirm what dahawthorne wrote above: it took them about a month but Motorola repaired my Nexus under warranty, no questions asked. It seems they replaced the Mainboard PCB.
Thanks everybody!