Related
I have a friend. We rooted her phone. All was well but apparently, somehow, the usb port on her phone got damaged (not b/c of software) and now the phone won't charge. She wants to send it for repair but she is paranoid since we rooted it that they won't fix it. She'd like me to un-root it. So here's my question:
I installed cyanogen's rom. Is it possible to update to Sprint's "official" 2.2 straight from that rom? Will accepting Sprint's update automatically un-root it, or is there a more complicated process needed?
Thanks!
I believe all you have to do I
Is run the stock ruu program which is run from your computer connected by usb look for it in the developers thread
Sent from my PC36100 using XDA App
deviouskater said:
I believe all you have to do I
Is run the stock ruu program which is run from your computer connected by usb look for it in the developers thread
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
with out the ability to use usb (if it doesnt work for charging, does it connect to the pc and get recognized?) you cant run the ruu.
however, if you run the OTA update. from home->settings->system updates, you should be able to query for update, not sure which, so try them all!
the OTA breaks root and removes recovery (please someone correct me if im wrong), bringing it back to stock.
you could always just brick it *shrug*
nenn said:
with out the ability to use usb (if it doesnt work for charging, does it connect to the pc and get recognized?) you cant run the ruu.
however, if you run the OTA update. from home->settings->system updates, you should be able to query for update, not sure which, so try them all!
the OTA breaks root and removes recovery (please someone correct me if im wrong), bringing it back to stock.
you could always just brick it *shrug*
Click to expand...
Click to collapse
Thanks for noticing that I can't plug it in USB. My concern about your post is the last line, "you could always brick it." Do you mean that if I try to update, it may brick b/c it was rooted? If it's bricked will the fact it was rooted or not come into question with repair place, or will they know it was rooted?
Thanks again.
pathtologos said:
Thanks for noticing that I can't plug it in USB. My concern about your post is the last line, "you could always brick it." Do you mean that if I try to update, it may brick b/c it was rooted? If it's bricked will the fact it was rooted or not come into question with repair place, or will they know it was rooted?
Thanks again.
Click to expand...
Click to collapse
meaning, you can brick it on purpose i have no idea if they can find out if you rooted it, or if the repair service would even care. theyre not the claims department, soooooooooooooooooooooo.
theres a thread there in q&a or general about someone who returned(attempted to) a phone because "the ota bricked it"
If I were your friend I would download a 2.1 rom right from the phone, use a file exploere to move it to the root of the sdcard, flash the 2.1 rom then do the official 2.2 ota update.
The only problem with this is if you can't charge it then I hope you can get it done by the time her battery dies.. however, if the battery dies and you can't charge it enough to finish this then what is Sprint gonna do anyways.
Actually I think that might be a real option. If you can't charge the phone just run it down till it dies and then take it in. They wont be able to power it on and see that it's rooted anyways..
nebenezer said:
If I were your friend I would download a 2.1 rom right from the phone, use a file exploere to move it to the root of the sdcard, flash the 2.1 rom then do the official 2.2 ota update.
The only problem with this is if you can't charge it then I hope you can get it done by the time her battery dies.. however, if the battery dies and you can't charge it enough to finish this then what is Sprint gonna do anyways.
Actually I think that might be a real option. If you can't charge the phone just run it down till it dies and then take it in. They wont be able to power it on and see that it's rooted anyways..
Click to expand...
Click to collapse
its not hard to swap out a battery for a test.
nebenezer said:
If I were your friend I would download a 2.1 rom right from the phone, use a file exploere to move it to the root of the sdcard, flash the 2.1 rom then do the official 2.2 ota update.
The only problem with this is if you can't charge it then I hope you can get it done by the time her battery dies.. however, if the battery dies and you can't charge it enough to finish this then what is Sprint gonna do anyways.
Actually I think that might be a real option. If you can't charge the phone just run it down till it dies and then take it in. They wont be able to power it on and see that it's rooted anyways..
Click to expand...
Click to collapse
This forum has the best people, I swear. I can put my battery in her phone. I like your idea. I actually have a backup in her phone of the stock rooted rom. So, if I flash back to it, do you think I can just download the official update and become "un-rooted"?
thanks.
yes
10char
Mine is NOT ROOTED & at day 21 the USB port &/or cable went buggy immediately after I purchased & used a car charger from the Sprint store (employee insisted it was the "correct" charger for EVO after telling me NOT to use my Palm Pre chargers & cables even though the ports were the same....he said the Pre equipment xfrd a diff current or wattage. Who knows if that's bad info or not, btw .)
The problem started off as totally non-functioning for charge, pc sync, et all, then after using the Sprint car charger exclusively for several days - just to be able to use the EVO at all- & freaking out about it to Sprint Tech Support & at the store, it just suddenly started charging if I touched or bent it a certain way, like it had a short or bad connection.
Next, I visited a Sprint repair store & they just reset the "USB debugging" option to ENABLE/ON (again) & then the USB cable would work for pc sync and sometimes charge as well.
After 6 weeks I'm left with having to ditch the wall outlet adapter plug from the orig box, put a cig lighter/USB plug from my iTouch on it & plug it into a cig lighter wall plug adapter to charge at home in the wall.
I'm pretty tech savvy & I still can't tell if it's a software issue with the cable or the EVO port, or a physical issue with the cable or the port, or some combo of all 4 options. I love my EVO so I adapted & moved on, but definitely logged my complaint loudly with Sprint, insisting they extend my 30 days until the issue is 100% resolved.
I hope that my experience solves your own mystery.
Sent from my EVO 4G - HTC SuperSonic
nenn said:
yes
10char
Click to expand...
Click to collapse
Ok, so I restored the 2.1 backup, checked for update, downloaded update. When I hit install, it went into recovery. Half way through installation, I got the little android with an exclamation mark. It just sat there for 5 to 10 minutes (saw a progress bar before this but it stopped halfway through). I pulled the battery and turned the phone back on. Thank God, it's not bricked but I don't know why the update stopped halfway through. I did install the newest radios when I flashed cyanogen's rom and I'm wondering if that had anything to do with it not completing installation. I'm wondering if I should install an older radio and try again.
Any ideas?
So I flashed the cm7 alpha that came out last night this morning. I wasn't getting calls so i turned it off and tried to reboot it into recovery. The phone never got into recovery (I told it to reboot into recovery from clockwork mod), and now it isnt powering on, at all. I've tried every key combination, recovery, download mode, letting it charge for HOURS, and still nothing.
If anyone has any ideas, please let me know. I'm trying to gather the files I need to see if odin will recognize it and possibly be able to restore it to stock. If I can't get it to work by tomorrow, I'm just going to go to the T-Mobile store.
aaronpaws said:
So I flashed the cm7 alpha that came out last night this morning. I wasn't getting calls so i turned it off and tried to reboot it into recovery. The phone never got into recovery (I told it to reboot into recovery from clockwork mod), and now it isnt powering on, at all. I've tried every key combination, recovery, download mode, letting it charge for HOURS, and still nothing.
If anyone has any ideas, please let me know. I'm trying to gather the files I need to see if odin will recognize it and possibly be able to restore it to stock. If I can't get it to work by tomorrow, I'm just going to go to the T-Mobile store.
Click to expand...
Click to collapse
Would it be possible that you tried so many combinations that the phone's battery has died? Have you tried plugging it in and seeing what happens?
charged for four hours and nothing.
Took it to a tmobile store and they're doing a warranty exchange since they couldn't get it to do anything either, even with a different battery.
Kind of curious as to what'll happen when I send it back since it has cyanogen mod 7 on it and its rooted. Then again, the phone won't boot, go into download mode, or recovery.
edit: I'm thinking the phone won't charge because of the custom kernel in cm7. Don't know how I would flash a kernel if I couldn't get it to boot though.
Dam,, too late
But for reference try!
Take the battery out and let it sit for a few min the put it back in and see if it boots.
If it still will not boot
Take the battery back out
Plug in the USB cable connected to the computer
Hold down the volume up and down then
Put the battery back in.
You should get the option: Volume UP / Volume Down for Reboot
Hit Volume UP and go get some Odin love!
I still have the phone, I'm gonna try this now. Will update with results.
aaronpaws said:
I still have the phone, I'm gonna try this now. Will update with results.
Click to expand...
Click to collapse
Cool man, keep us updated.
Well, I tried both suggestions to no avail. Anyone else have any ideas?
aaronpaws said:
Well, I tried both suggestions to no avail. Anyone else have any ideas?
Click to expand...
Click to collapse
I did not see you mention it, but did you try the "10 second" power button hold? You know it works when the phone vibrates 3 times. Simply hold the power button until it vibrates. It takes about 7-10 seconds (although when you think your phone is bricked, it feels like it is taking 5 minutes). If it vibrates, you are in the clear. You can usually get to recovery or odin from there. Try doing this on battery only first.
no cigar with the hold for ten seconds method on the power button.
aaronpaws said:
no cigar with the hold for ten seconds method on the power button.
Click to expand...
Click to collapse
It is really, REALLY difficult to brick a phone unless you are changing the radio (for example, flashing a wrong or corrupted radio). A kernel can hose your phone, but not brick it as you don't need a kernel to access recovery. A bad recovery could also brick your phone, but then you have download mode (Odin) to access that bypasses recovery. In other words, there are layers of protection or access points. We have not flashed any new radios for our phones yet, so you know that is not the problem. Having said all that, that does not mean you are not bricked.
To be clear on your position, you are getting no power response at all? Again, try this:
Unplug your phone;
take battery out (wait about a minute before replacing battery);
replace battery;
"10 second" hold until phone vibrates 3 times (or vibrates at all for that matter);
If you see no sign of life, then try the above process with phone plugged in (try plugged into computer and wall socket separately). Odin recognizes when you are plugged into computer and the boot process goes differently.
As for Odin bootup:
Load Odin;
Plug in your USB to computer;
try the volume/power boot up;
if that fails, try the "10 second" hold boot up with Odin running on your system and phone plugged in.
Outside of that, I can not think of any other way to get you to recovery or Odin.
I have flashed my android phones probably 150+ times in the last 2 and a half years and never made a brick. I thought I had, but was always able to get to recovery or bootloader (think Odin for HTC), and recover the phone. The only times I ever saw anyone truly brick the phone was when flashing the wrong or bad radio for their phone (radio is your 4G / cell receiver). So, walk through your processes to recover your phone in a methodical way and if that all fails, then return it. If you can't get it to go trying all these techniques, then T-mobile probably won't be able to as well and see that you rooted it.
Hope this helps.
Slightly off topic but if you send in a rooted phone for warranty (not insurance, warranty) they will charge you a full repair fee.
Sent from the Galaxy, 2 stars to the left.
What happens when you pull your battery, put it back in and attempt to turn your phone on?
Sent from my SGH-T989 using Tapatalk
@PorchSong, I've tried everything you said to no avail. I know its extremely hard to brick an android phone. Having had over 10 devices in the past year, all running custom roms, I've never bricked one either. This is why I find this so unbelievable, I usually don't make posts on XDA, not for lack of caring about the subject matter, but rather because I'd rather learn about it on my own to further my understanding on it.
Again, this is as bricked as I've ever seen something. The phone simply is unresponsive to every method I've tried.
@btyork, how would they know if the phone doesn't boot into recovery, download mode, or into regular android? I'm not saying that they couldn't. I'm just saying, what precautions could I take against them finding out. Trust me, if i could find a way to, I'd restore it to stock before I sent it back to them. (I still have the phone and will until december 6th, when they send me my new one, so we have a little bit of time to work on this)
@ mikeyinid, Nothing at all. Nothing in this thread has made the phone give even the slightest response.
The last thing I did was try to boot into clockwork mod, rather than boot with the key combination like I normally do, i did it directly from rom manager. Except, it never booted into recovery, so I pulled the battery and tried to start it again, from there it hasn't booted, or charged. I could've sworn the phone had at least a 30 percent charge when I was doing all this as well. Not the best for restoring from a backup in clockwork mod but I was in a bind as I was about to leave somewhere for roughly two hours and needed a functioning phone (cm7 did not let me make or receive calls, for whatever reason).
Are you seeing anything on the screen?
Sent from my SGH-T989 using XDA App
aaronpaws said:
@PorchSong, I've tried everything you said to no avail. I know its extremely hard to brick an android phone. Having had over 10 devices in the past year, all running custom roms, I've never bricked one either. This is why I find this so unbelievable, I usually don't make posts on XDA, not for lack of caring about the subject matter, but rather because I'd rather learn about it on my own to further my understanding on it.
Again, this is as bricked as I've ever seen something. The phone simply is unresponsive to every method I've tried.
@btyork, how would they know if the phone doesn't boot into recovery, download mode, or into regular android? I'm not saying that they couldn't. I'm just saying, what precautions could I take against them finding out. Trust me, if i could find a way to, I'd restore it to stock before I sent it back to them. (I still have the phone and will until december 6th, when they send me my new one, so we have a little bit of time to work on this)
@ mikeyinid, Nothing at all. Nothing in this thread has made the phone give even the slightest response.
The last thing I did was try to boot into clockwork mod, rather than boot with the key combination like I normally do, i did it directly from rom manager. Except, it never booted into recovery, so I pulled the battery and tried to start it again, from there it hasn't booted, or charged. I could've sworn the phone had at least a 30 percent charge when I was doing all this as well. Not the best for restoring from a backup in clockwork mod but I was in a bind as I was about to leave somewhere for roughly two hours and needed a functioning phone (cm7 did not let me make or receive calls, for whatever reason).
Click to expand...
Click to collapse
Are you sure you flashed cm7 for our phone? Sounds like a boot.img flashed to the wrong partition. I only know that because I bricked my first gs2 using the wrong mount point to flash a kernel. If it doesn't do anything at all, jig might work but idk. I just got a new one
Sent from my SGH-T989 using Tapatalk
Typically with Samsung phones, if you can get ANYTHING at all to show on the screen it is not bricked.
Do you have a G+ account? If I can see what is going on while I walk you through it it would be easier. Could possibly hold an open hangout so others can join in and help or just for informational purposes.
I have had soft bricks on my behold 2, vibrant and SGS2, over 100 times all together. Sometimes it takes a little fiddling, my SGS2 seemed a little more difficult only because of the relative simplicity of it compared to the others.
---------- Post added at 02:18 PM ---------- Previous post was at 02:15 PM ----------
mikeyinid said:
Are you sure you flashed cm7 for our phone? Sounds like a boot.img flashed to the wrong partition. I only know that because I bricked my first gs2 using the wrong mount point to flash a kernel. If it doesn't do anything at all, jig might work but idk. I just got a new one
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Well i think he said it did boot initially, so I doubt that is the problem.
---------- Post added at 02:19 PM ---------- Previous post was at 02:18 PM ----------
btyork said:
Slightly off topic but if you send in a rooted phone for warranty (not insurance, warranty) they will charge you a full repair fee.
Sent from the Galaxy, 2 stars to the left.
Click to expand...
Click to collapse
That depends if they can tell or not.
Okay, well I'm going to try and fix it in Odin one more time tomorrow on my friends computer (I use a mac), so I'll report back on what happens. I'm thinking I didn't put it into download mode the right way when I tried it the other night. I remember having to do it for rooting the phone, but hadn't done it since, and since this is my first samsung phone other than the nexus s, I wasn't all that familiar with it. The google + idea might be a good one. I'm not sure how to go about setting that up, but I should be at my friends around like 12est tomorrow, so if anyone wants to set something up we can do that, or I can just report back. Either way, I'll come back to this thread and give a conclusion on what's happened.
aaronpaws said:
Okay, well I'm going to try and fix it in Odin one more time tomorrow on my friends computer (I use a mac), so I'll report back on what happens. I'm thinking I didn't put it into download mode the right way when I tried it the other night. I remember having to do it for rooting the phone, but hadn't done it since, and since this is my first samsung phone other than the nexus s, I wasn't all that familiar with it. The google + idea might be a good one. I'm not sure how to go about setting that up, but I should be at my friends around like 12est tomorrow, so if anyone wants to set something up we can do that, or I can just report back. Either way, I'll come back to this thread and give a conclusion on what's happened.
Click to expand...
Click to collapse
Let me know, G+ is easy. Im out of class at 2est.
Just FYI. I ran into this exact same issue. After charging my phone all night and using it for about 5 minutes, I set it down then picked it up like 30 minutes later and received absolutely no responsiveness from the phone. It wouldn't even recognize the charger when I plugged it in.
I tried all the battery tricks, and reset tricks and nothing worked. So I took it into the T-Mobile store, assuming it was bricked, in an attempt to get it replaced. He simply plugged the phone into the stock charger that came with the phone and it indicated that the battery was just completely dead and needed a charge.
It turns out that the phone really didn't get a full charge after being plugged in all night to my GF's MT4G charger. Apparently this phone is picky about what charger is used. I'm sure you've already attempted this, but just make sure to plug it into the stock charger to see if you can at least get the charging battery image to pop up.
more like it wasn't plugged in properly to begin with
because that happened to me, even though it said "charging"... it was stuck at 43% for like 4+ hours, so i figured something must be wrong
and indeed it was, so i unplugged it, and plugged it back in, then voila! now it starts to charge as it was supposed to.
the phone is not picky by any means, i've used my old BB charges with it, the other HTC charger, the other samsung USB, the generic cheap chargers i get from Deal Extreme, etc
they all charges the phone just fine and fast
you do have to be careful when you plug it in, and make sure it's really charging
sn0warmy said:
Just FYI. I ran into this exact same issue. After charging my phone all night and using it for about 5 minutes, I set it down then picked it up like 30 minutes later and received absolutely no responsiveness from the phone. It wouldn't even recognize the charger when I plugged it in.
I tried all the battery tricks, and reset tricks and nothing worked. So I took it into the T-Mobile store, assuming it was bricked, in an attempt to get it replaced. He simply plugged the phone into the stock charger that came with the phone and it indicated that the battery was just completely dead and needed a charge.
It turns out that the phone really didn't get a full charge after being plugged in all night to my GF's MT4G charger. Apparently this phone is picky about what charger is used. I'm sure you've already attempted this, but just make sure to plug it into the stock charger to see if you can at least get the charging battery image to pop up.
Click to expand...
Click to collapse
Forgive me if this is the wrong forum for this but today I was just playing a game on phone when it just crashed,
I thought no big deal I'll just reboot so went to reboot, however it just went into a bootloop and would not reboot. Then I thought ok CWR but I could not boot into this. I then decided to use adb mode to flash back to stock. However in this process adb froze and would not respond anymore and kind of had a blue tearing around everything on the screen. I ended up having to pull the battery.
Now however the phone won't respond at all, Won't turn on, won't go into download mode or anything. I can get my computer and laptop to regonize it when I plug it on with no battery but just says searching for driver for OMAP 4440 then fails. I'm pretty sure I have bricked it and am quite sad. Just looking for confirmation.
Its still alive, I'm pretty sure someone with a bit more knowledge will stop by and help you, but it appears to just be a soft brick.
Sent from my Galaxy Nexus using XDA App
Just to possibly give you some hoe look into Odin. When I had my fascinate this was the way to fix things. Being made by Samsung I'm sure it'll be similar. Do some research into that. Just got my nexus two days ago so I'm still fresh
Sent from my Galaxy Nexus using Tapatalk
rctreadaway said:
Just to possibly give you some hoe look into Odin. When I had my fascinate this was the way to fix things.
Click to expand...
Click to collapse
I'm afraid that's a little bit different situation here:
signzero said:
the phone won't respond at all, Won't turn on, won't go into download mode or anything. I can get my computer and laptop to regonize it when I plug it on with no battery but just says searching for driver for OMAP 4440 then fails.
Click to expand...
Click to collapse
Not connected to PC - no ADB, no ODIN. Plus, his phone failed while playing game (under heavy load) which gives me a reason to think it's a hardware fault. I would say last chance is to try USB Jig.
If you can get to the bootloader, you should be able to flash a stock Google image
Sent from my Galaxy Nexus
signzero said:
Forgive me if this is the wrong forum for this but today I was just playing a game on phone when it just crashed,
I thought no big deal I'll just reboot so went to reboot, however it just went into a bootloop and would not reboot. Then I thought ok CWR but I could not boot into this. I then decided to use adb mode to flash back to stock. However in this process adb froze and would not respond anymore and kind of had a blue tearing around everything on the screen. I ended up having to pull the battery.
Now however the phone won't respond at all, Won't turn on, won't go into download mode or anything. I can get my computer and laptop to regonize it when I plug it on with no battery but just says searching for driver for OMAP 4440 then fails. I'm pretty sure I have bricked it and am quite sad. Just looking for confirmation.
Click to expand...
Click to collapse
It's a hard brick, mate...
How to fix?:
take the back cover off your phone!
Remove battery, then plug in via USB (computer)
Leave for 3 hours!!! (With battery still unplugged) This should, in a way, "reset" your phone.
Once the three hours are over, plug in battery, and unplug USB.
Press PWR+VOL Down
Wait untill hpone boots into Odin mode then flashstock firmware from Samsung website.I
If this doesn't work, then I'd send it to Mobile Tech Videos, they kann unbrick it via JTAG...
Let me know if it worked, pleasse
---------- Post added at 04:26 PM ---------- Previous post was at 04:24 PM ----------
MS. said:
I'm afraid that's a little bit different situation here:
Not connected to PC - no ADB, no ODIN. Plus, his phone failed while playing game (under heavy load) which gives me a reason to think it's a hardware fault. I would say last chance is to try USB Jig.
Click to expand...
Click to collapse
He didn't mean playing, as in games. He meant playing around with his phone, root etc....
Thanks for the advice guys, gives me a small amount of hope. I will try leaving it plugged into my computer for 3 hours + and see what happens. Will post back with results.
Otherwise I may try get my hands on a jig. Would it be the same one from the Galaxy SII?
It worked? I'll explain you what happened to me:
I was playing for 2 hours on the game cartoon wars. After that, the phone was a little hot, I went to the desktop and locked the phone. 20 minutes later, I try to unlock the phone and I see the Google logo, and nothing responds. I pulled out the battery several times, tried to enter recovery, fastboot, normal boot. Always freezes. Stock 100%, the mobile has one week.... I think I will have to send it to the SAT....
I have my old HTC magic awaiting me, I gave my galaxy S to my sister...
Brick is such a misused word...
hmm
well if your running with verizon, which i doubt many of you are (prob using the GSM Gnex) you could just as easily bring it to them, lie, and theyll replace your phone. had a droid X, cracked the screen, told verizon it had a hardware fault, and they replaced it with no questions. verizon employees are pretty stupid
jttate04 said:
well if your running with verizon, which i doubt many of you are (prob using the GSM Gnex) you could just as easily bring it to them, lie, and theyll replace your phone. had a droid X, cracked the screen, told verizon it had a hardware fault, and they replaced it with no questions. verizon employees are pretty stupid
Click to expand...
Click to collapse
You are a horrible person and one of the reasons why decent, hardworking people can't have nice things.
So none of the methods suggested have work so looks like I'm going to have to get a Jig and hope that will do the trick otherwise I'm doomed I think.
when you guys say jig do you mean using resistors on the micro usb port to boot like with the old captivate? i still have the resistors mirco usb plug for that phone, it saved me from a hard brick a few times.
familyguy59 said:
He didn't mean playing, as in games. He meant playing around with his phone, root etc....
Click to expand...
Click to collapse
First post says "i was playing a game"...
neotekz said:
when you guys say jig do you mean using resistors on the micro usb port to boot like with the old captivate? i still have the resistors mirco usb plug for that phone, it saved me from a hard brick a few times.
Click to expand...
Click to collapse
Yup.
So I am having an issue with my USB port, it seems loose, and will only charge if the cable is pushed upwards a bit. It is also unable to connect to a computer. My question is, is it possible for me to lock my bootloader without having usb access, or root (root got messed up when I decided to update without attempting to preserve it)? Or gain root without usb? I feel like I'll have to send it in to get repaired/replaced, and from what I've read it will need to be fully stock for that. Thanks
Depends how the usb is broken. May be easily repaired yourself. Any chance you can get a pic up so we can help better?
Hotkeys said:
So I am having an issue with my USB port, it seems loose, and will only charge if the cable is pushed upwards a bit. It is also unable to connect to a computer. My question is, is it possible for me to lock my bootloader without having usb access, or root (root got messed up when I decided to update without attempting to preserve it)? Or gain root without usb? I feel like I'll have to send it in to get repaired/replaced, and from what I've read it will need to be fully stock for that. Thanks
Click to expand...
Click to collapse
first try another usb cable
i faced the same problem and changed the cable and it worked
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
This app claims to unlock/lock the bootloader. I haven't used it,so can't say it works.
maschiosoosai said:
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
This app claims to unlock/lock the bootloader. I haven't used it,so can't say it works.
Click to expand...
Click to collapse
you need root to use that app
simms22 said:
you need root to use that app
Click to expand...
Click to collapse
Oops,didn't see that.Bad eyes,I guess.
---------- Post added at 10:42 PM ---------- Previous post was at 10:37 PM ----------
https://lh6.ggpht.com/9un6zjZ7yQUs9_J9h_MVYfRPTD1HnDyvGx0425DFWgIagTpuKSgj35bNOg_kYQmVCTU
I'm not rooted now,but if you updated via OTA maybe OTA RootKeeper can help.
Hotkeys said:
So I am having an issue with my USB port, it seems loose, and will only charge if the cable is pushed upwards a bit. It is also unable to connect to a computer. My question is, is it possible for me to lock my bootloader without having usb access, or root (root got messed up when I decided to update without attempting to preserve it)? Or gain root without usb? I feel like I'll have to send it in to get repaired/replaced, and from what I've read it will need to be fully stock for that. Thanks
Click to expand...
Click to collapse
Been having the same charging problem, can't get adb to recognize the nexus. I've uninstalled/reinstalled the drivers. Doesn't matter if I use another USB. If anyone has another solution I'd love to hear it.
Try cleaning the bottom of the opening with a sharpened toothpick or paperclip with the battery removed. If that doesn't help try gently prying the tongue inside the charging port away from the wall.
This worked for me.
Sent from my Galaxy Nexus using xda premium
Sorry for the lack of reply guys, been busy doing things with family due to Christmas and all that jazz.
063_XOBX said:
Depends how the usb is broken. May be easily repaired yourself. Any chance you can get a pic up so we can help better?
Click to expand...
Click to collapse
I don't have a camera nearby at the moment, but I'll do my best to get a picture up soon.
rabeaoghly said:
first try another usb cable
i faced the same problem and changed the cable and it worked
Click to expand...
Click to collapse
I already have tried 2 other cables, and have had no luck unfortunately. All exhibit the same issue, so it's most likely the port.
At the moment I'm able to charge my phone if I prop the cable on something or use some other method to sort of push the jack upwards slightly, so maybe something is loose?
Hotkeys said:
Sorry for the lack of reply guys, been busy doing things with family due to Christmas and all that jazz.
I don't have a camera nearby at the moment, but I'll do my best to get a picture up soon.
I already have tried 2 other cables, and have had no luck unfortunately. All exhibit the same issue, so it's most likely the port.
At the moment I'm able to charge my phone if I prop the cable on something or use some other method to sort of push the jack upwards slightly, so maybe something is loose?
Click to expand...
Click to collapse
google it....i'm finding a lot of info about it simply being dirty inside the charging port. makes sense when you think about it. mine's in my pocket all the time, the port doesn't ever get covered and lint/etc builds up. i watched a few youtube videos. one guy used a really small sewing needle. another used a bigger one but filed it down. both said their charger felt loose when they plugged it in and afterwards it would lock like it was brand new. haven't had a chance to see if i've got anything small enough to do this yet but i'm willing to bet that that's my problem, and maybe yours as well. soon as i get around to it i'll post back again. and if you try it, be careful not to damage the connection inside
I have two pieces of ZF2 ZE551ML at home. One is my and the other one belongs to my wife. My wife's phone had a broken mini USB port - the first 2 pins from the left were visible - the plastic had broken apart. Firstly, I did not relaise it could be the problem, luckily I managed to change the whole PCB including the broken USB port, however after this change the phone is not being detected by a PC, nor it is fast charging. As I have two phones at home, I checked performance with the other unit and unfortunately, the other one does quick charge and is detected by aPC, so it is not the cable, neither is it the missing software.
I bought another PCB and changed it as well, however still no joy. Does anyone have any brilliant idea how to fix it. I should also say that all other or most of the functions of the phone are working fine (at least those I managed to check: GPS, Wi-Fi, GSM+dual SIM, torch, bluetooth, and so on).
The only problem is that the phone loops on the SMMI Test #1 and is not going any further. I have also tried to detect phone by adb, still no joy. The phone is not rooted!
I have my personal suspects that it could be the faulty main board or a software bug. Any ideas how to fix it?
My phone is running LP 5.0, soft: LRX21V.WW-ASUS_Z00A-2.20.40.198_20160930_8756_user044030427_201501060109, kernel [email protected] #1 Fri Sept 30 15:31>23 CST 2016
Sdcard slot is working?
I would check the connections on both ends of the flex cable with the sim and sd slots on it.
I am having the same problems (because of the busted sd slot). I ordered a new flex cable. When it arrives (approx. 2 weeks) I'll know if that was the cause.
Yes, SD slot is working and both SIMs, so the phone itself works fine, only very long charging and is not detected by a PC.
Mattiii said:
I have two pieces of ZF2 ZE551ML at home. One is my and the other one belongs to my wife. My wife's phone had a broken mini USB port - the first 2 pins from the left were visible - the plastic had broken apart. Firstly, I did not relaise it could be the problem, luckily I managed to change the whole PCB including the broken USB port, however after this change the phone is not being detected by a PC, nor it is fast charging. As I have two phones at home, I checked performance with the other unit and unfortunately, the other one does quick charge and is detected by aPC, so it is not the cable, neither is it the missing software.
I bought another PCB and changed it as well, however still no joy. Does anyone have any brilliant idea how to fix it. I should also say that all other or most of the functions of the phone are working fine (at least those I managed to check: GPS, Wi-Fi, GSM+dual SIM, torch, bluetooth, and so on).
The only problem is that the phone loops on the SMMI Test #1 and is not going any further. I have also tried to detect phone by adb, still no joy. The phone is not rooted!
I have my personal suspects that it could be the faulty main board or a software bug. Any ideas how to fix it?
My phone is running LP 5.0, soft: LRX21V.WW-ASUS_Z00A-2.20.40.198_20160930_8756_user044030427_201501060109, kernel 3.10[email protected] #1 Fri Sept 30 15:31>23 CST 2016
Click to expand...
Click to collapse
may be the pcb you changed is for different version. try replacing it with your other phone if you have the same model. post if works.
sukhwant717 said:
may be the pcb you changed is for different version. try replacing it with your other phone if you have the same model. post if works.
Click to expand...
Click to collapse
Hi, I did changed both PCBs between phones. Firstly, I had the same problem on both phones, then I made better connections and the batteries started to warm up. Finally, the new one works with the other phone, the old one from the other phone still creates the problem. Probably, it is not the PCB then, or USB connection. It must be something else.
Anyone, any idea?
Mattiii said:
Hi, I did changed both PCBs between phones. Firstly, I had the same problem on both phones, then I made better connections and the batteries started to warm up. Finally, the new one works with the other phone, the old one from the other phone still creates the problem. Probably, it is not the PCB then, or USB connection. It must be something else.
Anyone, any idea?
Click to expand...
Click to collapse
try fashing raw firmware
on motherboard you can inspect or clean the connector where pcb connects. use magnifying glass to inspect connector
Ok, I actually would like to flash the raw firmware, however I need some guidance here, as the phone that has a problem, is not rooted, and it cannot be detected by any PC now, so I am stuck in the middle and do not know how to proceed...
sukhwant717 said:
try fashing raw firmware
on motherboard you can inspect or clean the connector where pcb connects. use magnifying glass to inspect connector
Click to expand...
Click to collapse
Ok, I actually would like to flash the raw firmware, however I need some guidance here, as the phone that has a problem, is not rooted, and it cannot be detected by any PC now, so I am stuck in the middle and do not know how to proceed...
and the connectors are clean
Mattiii said:
Ok, I actually would like to flash the raw firmware, however I need some guidance here, as the phone that has a problem, is not rooted, and it cannot be detected by any PC now, so I am stuck in the middle and do not know how to proceed...
and the connectors are clean
Click to expand...
Click to collapse
i am little confused here... you changed pcb on one mobile and fast charger do not works on that. you have other mobile which is working perfectly. both are same model.... if right!! do the following thing to find out...
Phone A:- changed PCB. no fast charge, not detected by pc.
Phone B:- working perfectly normal..
now we want to guess if pcb is faulty or there is issue with flex cable or any software related issue..
remove motherboard from phone A. and install it in Phone B.. if on Phone B. things works well then definitely its problem related to pcb.. if things don't works on phone B too. then it may be a firmware related problem..
raw cannot be installed without pc..... the thing you can ty is updating firmware from sd card via recovery mode.
sukhwant717 said:
i am little confused here... you changed pcb on one mobile and fast charger do not works on that. you have other mobile which is working perfectly. both are same model.... if right!! do the following thing to find out...
Phone A:- changed PCB. no fast charge, not detected by pc.
Phone B:- working perfectly normal..
now we want to guess if pcb is faulty or there is issue with flex cable or any software related issue..
remove motherboard from phone A. and install it in Phone B.. if on Phone B. things works well then definitely its problem related to pcb.. if things don't works on phone B too. then it may be a firmware related problem..
raw cannot be installed without pc..... the thing you can ty is updating firmware from sd card via recovery mode.
Click to expand...
Click to collapse
That is correct, I say it again - I have two phones, same model, same software, kernel, etc. One had a damaged mini USB port, so I purchased 2 PCBs which have mini USB port souldered onto them. I bought them twice, as I was not sure if the first one I got was the correct one. Now, after your first message I changed the PCBs between phones and the result is the same, phone A (which is ok) works with the replacement PCB, and the PCB from working phone still does not work with phone B (the one that has a problem).
As a second step I replaced motherboards between phones now, and the result is still the same, meaning the motherboard from phone B does not seem to work better while it is in phone A body. The symptoms I'm struggling with are: charging takes over 8-9 hours, so it is considerably extended charging (battery is original factory battery 3000 mAh), the phone does not fastcharge at all and it is not detected by any PC.
The phone is not roooted so, I'm afraid I cannot make any changes to firmware through recovery, as it needs to be connected by a cable to a PC, unless there is something else I can do about it, but how to get any further?
Mattiii said:
That is correct, I say it again - I have two phones, same model, same software, kernel, etc. One had a damaged mini USB port, so I purchased 2 PCBs which have mini USB port souldered onto them. I bought them twice, as I was not sure if the first one I got was the correct one. Now, after your first message I changed the PCBs between phones and the result is the same, phone A (which is ok) works with the replacement PCB, and the PCB from working phone still does not work with phone B (the one that has a problem).
As a second step I replaced motherboards between phones now, and the result is still the same, meaning the motherboard from phone B does not seem to work better while it is in phone A body. The symptoms I'm struggling with are: charging takes over 8-9 hours, so it is considerably extended charging (battery is original factory battery 3000 mAh), the phone does not fastcharge at all and it is not detected by any PC.
The phone is not roooted so, I'm afraid I cannot make any changes to firmware through recovery, as it needs to be connected by a cable to a PC, unless there is something else I can do about it, but how to get any further?
Click to expand...
Click to collapse
which firmware you are currently on? lolipop or MM? factory reset your device then apply latest lolipop update from sd card
sukhwant717 said:
which firmware you are currently on? lolipop or MM? factory reset your device then apply latest lolipop update from sd card
Click to expand...
Click to collapse
I was on lolipop, updated to MM now, but still no joy, charges very slowly like before and when connected to any PC it says one of the recently connected devices is not working properly, so I'm stuck ... I cannot root or apply any ADB sideloads ...
Mattiii said:
I was on lolipop, updated to MM now, but still no joy, charges very slowly like before and when connected to any PC it says one of the recently connected devices is not working properly, so I'm stuck ... I cannot root or apply any ADB sideloads ...
Click to expand...
Click to collapse
Is your ext. sd being seen in file manager ?
Can you get into 6.0 recovery ?
If yes , you can now downgrade which will reset your fone , With a factory reset in the process , check my signature below.
Your fone not being seen maybe driver issue if other zens too are not being seen...but ..let's see what happens after downgrade.
After downgrade if still slow charge, reboot while connected to charger.
If same prob ..hardware !
sukhwant717 said:
which firmware you are currently on? lolipop or MM? factory reset your device then apply latest lolipop update from sd card
Click to expand...
Click to collapse
timbernot said:
Is your ext. sd being seen in file manager ?
Can you get into 6.0 recovery ?
If yes , you can now downgrade which will reset your fone , With a factory reset in the process , check my signature below.
Your fone not being seen maybe driver issue if other zens too are not being seen...but ..let's see what happens after downgrade.
After downgrade if still slow charge, reboot while connected to charger.
If same prob ..hardware !
Click to expand...
Click to collapse
Thanks, I was not so deeply checking all available options. SD downgrading worked well for me, however the problem still is in the phone. However, I discovered a few positive and negative signs, which tell me that there is something else - could be the connection - after upgrading to MM before the phone was restarted at least 3-4 times the screen was not going to sleep mode after a minute, it was coming back on and on and on again. After 3-4 restarts it behaved normally again. The same thing happened after downgrade to L.
Another positive discovery is that the SMMI test now works well and everything is ok now, before it got stuck on the 1st or 2nd test and was not going any further ....
One more spot, which was very hard to catch as it popped up for a 0,1 second but dissappeared then quickly so I had to record it with the other phone and play very slowly on the PC - it looks like the Asus cover window pops up and it says - move your finger around the circle to get quick access to your preferable apps and there is also a blue button: Do not show again . This is flashing now and then and I do not have Asus Cover, so the behaviour is quite odd to me.
I have a feeling that there might be something with connections, but really I do not know what else - I checked it 30 times and made sure everything was properly alligned and tight when I was changing the PCB with micro USB port.
By the way the other phone works well on PCs, so I must have all drivers installed, it is just the second phone that is half bricked... I'm wondering now if maybe flashing CM 12 or 13 will help, however as it is not rooted probably it will not work via SD card... or? Am I looking in the right direction?
Buddy , its hardware so software tweaks will be useless .
Buddy, we are on the same ****ing boat.
I tried to go back to 6.0,but i got my phone bricked and now i cant reverse it back because i need usb connection to the computer and simply it isnt recognized.
I suggest you to send the phone to the asus assistance centre or to buy a new usb port for your phone,as it is clearly damaged like mine.I need to do it too so if you want to wait me first so i can check if it works,ill maybe save you some money.
RxDave said:
Buddy, we are on the same ****ing boat.
I tried to go back to 6.0,but i got my phone bricked and now i cant reverse it back because i need usb connection to the computer and simply it isnt recognized.
I suggest you to send the phone to the asus assistance centre or to buy a new usb port for your phone,as it is clearly damaged like mine.I need to do it too so if you want to wait me first so i can check if it works,ill maybe save you some money.
Click to expand...
Click to collapse
Well, my phone successfully reversed to Lolipop, and I changed the USB port, I talked to Asus authorised service centre and they said it will cost the price of the phone, so I just give up, as everything works, but not the phone with the computer via USB and not the quick charging. Asus centre said it is a motherboard failure, but I'm asking how is that possible if all other functions work well???
timbernot said:
Buddy , its hardware so software tweaks will be useless .
Click to expand...
Click to collapse
Yes, I see your point, but I cannot imagine how is this possible, when all other things work well on the phone and the SMMI test shows all sensors working properly?
Mattiii said:
Yes, I see your point, but I cannot imagine how is this possible, when all other things work well on the phone and the SMMI test shows all sensors working properly?
Click to expand...
Click to collapse
Ask yourself the same 2 questions again once more
Is your phone recognised by PC ?
Is fast charging working now ?
If answer is no after downgrade .
You know the answer
i changed mainboard and working
well, i have the same problem and i try the following possibility and all unsuccessful.
1. i tried 3 different pcb still no luck
2. i changed sim flex still no luck
3. i changed battery still no luck
4. i changed lcd and digitizer completely still no luck
5. i wiped cache from android recovery MM still no luck
6. i wiped data and factory reset from android recovery MM still no luck
7. i install same latest os (MM) for ze551ml from sd card still no luck
8. i use original ac adapter and cable and tried working different one for every step.
so i want to ask a questions. can it be ground connection somewhere on cases? or motherboard
i am tired but problem found. it is exactly motherboard problem. i bought used original mainboard and all is working.
Note: other mainboard using same android os version so it is not os failure.