Database Develop

[Q] USB Gone, Lost Root, need sys files gone

In a nutshell... I rooted with superoneclick...Verizon update un-rooted me...can't re-root. Tried using LGNPST to flash stock rom... initially found phone and all was well but got error- can't find USB in dload mode. Phone stuck on -do not remove cable- screen... I had to pull battery. Now my USB port is not working at all (No Icon... tried drivers, cables, 4 different computers, have a second revolution is recognized quickly) whereas before this it was intermittent and I would get it (USB) back after several battery pulls and reboots.
I would like to bring this phone in to have it checked out but since I'm not rooted I can't get rid of the files associated with the original root (such as superuser). I did a factory reset hoping to get USB back and/or get rid of these files to no avail.
I must add I am super new at all this... I've read a lot on the forums but I don't know what I am doing. I didn't install Rom's or do any flashes. Just Wifi Tether, and titanium backup. Which means I also don't have clockwork (I literally just rooted a day or two before update)
Can anyone get me out of this MESS?? I just want to clean up my phone to bring it in for service/exchange but fear they will realize that I rooted.
Please!!! And Thank You for all the great work you do here

Check your cable I had same problem when I used a usb not supplied by verizon. The retailler will do a swap they do not have the time or expertise to check for a root or rom change. Water damage is all they look for. I used to manage a vzn reseller.

So is the phone working or no? It sounds like either it works or that it is stuck in a download screen.

Many cables tried
Thanks for the response... But we have 3 LG phones in the house, 2 Revolutions and a Optimus. I tried all 3 (LG Branded) cables on my phone, which didn't work...but did on the other 2 phones. I think since the other revolution connects easily with a cable to the computer that it is probably not a cable or a driver issue. I may be wrong, but it seems to make sense???
Also, The phone works fine other than there being no USB communication. Thanks for asking...

I fairly new to this as well but I have a thought. If you still have superuser try to use ti to remove the apps you installed and then remove superuser. ti can be uninstalled from the market. No promises if this will work but it is a thought. Hope it helps.

Remove superuser
Can you remove superuser from the market?? If so, I need instructions please.

Try to use Titanium backup which you got from the market to uninstall anything not from the market and then uninstall that. That should get you squared away. I hope...

That's all they look at in the store but they then send the phone to Verizon and if Verizon sees that it was rooted they will send you a bill for full retail of the replacement phone you were given. (Seen it happen many time)
drutman said:
Check your cable I had same problem when I used a usb not supplied by verizon. The retailler will do a swap they do not have the time or expertise to check for a root or rom change. Water damage is all they look for. I used to manage a vzn reseller.
Click to expand...
Click to collapse
Sent from my VS910 4G using XDA App

squidder said:
That's all they look at in the store but they then send the phone to Verizon and if Verizon sees that it was rooted they will send you a bill for full retail of the replacement phone you were given. (Seen it happen many time)
Sent from my VS910 4G using XDA App
Click to expand...
Click to collapse
Quite the opposite for me I've sent back a fascinate rooted with community rom and wireless tether, 1 eris rooted with kaosfroyo and wireless tether on it, and 4 other eris' rooted with tethering and never had a problem. Of course that is not a guarantee for everyone, but I don't know anyone that has ever been charged.
Sent from my VS910 4G using XDA Premium App

Titanium Backup
I believe titanium backup requires you to be rooted... which I'm not since I lost it during the update?

peaveyone said:
I believe titanium backup requires you to be rooted... which I'm not since I lost it during the update?
Click to expand...
Click to collapse
Yea but if you still have super user you might be able to use it. I would give it a shot

Haro912 said:
Yea but if you still have super user you might be able to use it. I would give it a shot
Click to expand...
Click to collapse
Yeah, I tried...it's looking for root

O wow thats a lot. I've done it once on accident and got away with it as well. I shouldn't have said seen many times as I've only seen it happen once but have heard stories online. I guess it just depends which employee looks at it. When u root your phone your warranty is voided so if u recieve a warranty replacement and they see your phone was rooted then u are not entitled to the replacement so they ask for it back or say pay up.
mtmichaelson said:
Quite the opposite for me I've sent back a fascinate rooted with community rom and wireless tether, 1 eris rooted with kaosfroyo and wireless tether on it, and 4 other eris' rooted with tethering and never had a problem. Of course that is not a guarantee for everyone, but I don't know anyone that has ever been charged.
Sent from my VS910 4G using XDA Premium App
Click to expand...
Click to collapse
Sent from my VS910 4G using XDA App

Warranty voided by rooting ?
I am a little concerned about the report of a users phone root voiding a replacement. Think about it for a minute, Android is open source and freedom to write apps is encouraged by all manufact. When you root a phone, the software is not illegal Google market sells root apps for other phones. Do you think the manufacturers would allow the official marketplace to sell apps that could void warranties? BS, this sounds like Sony's attempt to deny PS3 owners replacements after their required sys updates would brick their consoles. I had a buddy whose console froze up and he had to get an attorney to file a complaint before they would warranty it. If that happened to me I would file with the BBB or protest loudly at VZN.

Bionic is Not Turning On.

It's not rooted and doesn't have anything on it. Pretty much stock. Sent a text msg this morning and checked my email from it. Came back to it abt 20 minutes later and it won't even turn on. Tried charging it. Won't turn on. Tried swapping with my regular battery (which was fully charged when I put it away. It could be dead by now.). Nothing. Tried removing the battery, waiting, replacing the battery. Nothing. I did briefly get the M Dual Core icon and then all went blank.
Suggestions?

Back to VZW. Sounds like a faulty handset.
Good Luck,
RMD

rduckwor said:
Back to VZW. Sounds like a faulty handset.
Good Luck,
RMD
Click to expand...
Click to collapse
I second this.

Without going through the pain of returning it, would you be able to connect it to your computer, and reflash the (is it TRZ?) file through the new RSD Lite through the stock bootloader? Definitely worth a try.

BFirebird101 said:
Without going through the pain of returning it, would you be able to connect it to your computer, and reflash the (is it TRZ?) file through the new RSD Lite through the stock bootloader? Definitely worth a try.
Click to expand...
Click to collapse
idefiler6 said:
I second this.
Click to expand...
Click to collapse
rduckwor said:
Back to VZW. Sounds like a faulty handset.
Good Luck,
RMD
Click to expand...
Click to collapse
Thanks, all.. Hauled my cookies 30 minutes over to Verizon. The sales rep assumed I hadn't bothered to charge my phone. When he realized it wasn't the battery, he was extremely helpful and replaced the phone on the spot. He said he'd never seen that before and with a phone less than 1 month old, I shouldn't have those kinds of issues. Kudos to Verizon for a pleasant experience. I've had some bad experiences in the past, but this gentleman was helpful and didn't try to sell me any accessories! ;p (They always try to sell me something when I'm there.)

BFirebird101 said:
Without going through the pain of returning it, would you be able to connect it to your computer, and reflash the (is it TRZ?) file through the new RSD Lite through the stock bootloader? Definitely worth a try.
Click to expand...
Click to collapse
This is referencing what one would do if the software had an issue, if it does this will fix it but kinda sounds like hardware. I have returned my Bionic to stock twice its fairly easy, computer does almost everything. Here is this to get you going if you wanna do it.
http://forum.xda-developers.com/showthread.php?t=1262540
Just remember, phone has to be in fastboot mode to be detected by RSD Lite and once its detected and the file starts flashing, if it seems like its not making progress while saying otherwise, dont unplug it just wait
Sent from my DROID BIONIC using xda premium

BFirebird101 said:
Without going through the pain of returning it, would you be able to connect it to your computer, and reflash the (is it TRZ?) file through the new RSD Lite through the stock bootloader? Definitely worth a try.
Click to expand...
Click to collapse
One would need the ability to turn the phone on in the first place for this to be attempted. That's why no one was mentioning the FXZ.

The phone booted to the dual core M logo, which with myself that happens to be as far as mine would go when i successfully flashed my FXZ. The phone needs to boot to the fastboot screen which can be done on many occasions that the phone can get to the first logo, as long as there is battery left.
....
But congrats on the new replacement i just saw that after i posted
Sent from my DROID BIONIC using xda premium

It hasn't happened to me but I have to pull the battery on my wifes Bionic at least once a week and twice in one day. It would just go away suddenly and act like it was dead. I may return it for a replacement.

if anyone has exchanged their Bionic for a replacement because of the BSOD defect, will you please provide feedback in this thread? thanks

hi all:
just bought a bionic off ebay for cheap ($20 + free ship) but it has problems
it was being sold as "battery with water damage but phone is not but wont power on"
he said one night he left it in his drawer and when he woke up it didn't work anymore he tried removing battery and all that.
to my understanding the battery was previously water damaged and he could still use it and then got the wont power on later on.
anyhow to my question
the phone comes today with just the phone, water damaged battery and wall charger.
should I cut the end off the charger and do the wires to the battery and insert battery into phone and plug usb cord from laptop to the phone?
isn't this the correct way for bsod and a non water damaged battery?
is there anyway to test the waterdamaged battery to see if it could still be good?
I have a multimeter

N1 + foam party = fail to boot

Hi, last week I was in a foam party... with my nexus one in the back pocket..
It was almost completely wet, I wait different hours and then I try to start it but it stuck at the boot ("X" symbol). Yesterday I came back at home, I change the battery, clean the phone with alcohol and put it in the rice for almost a day. I can enter into the bootloader (blackrose), I can use fastboot but the recovery (amonRa) and my rom do no boot. I flashed the radio and the recovery several times. It always bootloop when I start the recovery. With blackrose I check the internal memory, there are 2 bad blocks... not too much. The screen, all the buttons and the battery seems to work correctly but the led does not light up when I charge the N1 (but it charge the battery and without the battery but plugged in, if I try to power on the smartphone, the led blinks).
Do you have some suggestions?

ercoppa said:
Hi, last week I was in a foam party... with my nexus one in the back pocket..
It was almost completely wet, I wait different hours and then I try to start it but it stuck at the boot ("X" symbol). Yesterday I came back at home, I change the battery, clean the phone with alcohol and put it in the rice for almost a day. I can enter into the bootloader (blackrose), I can use fastboot but the recovery (amonRa) and my rom do no boot. I flashed the radio and the recovery several times. It always bootloop when I start the recovery. With blackrose I check the internal memory, there are 2 bad blocks... not too much. The screen, all the buttons and the battery seems to work correctly but the led does not light up when I charge the N1 (but it charge the battery and without the battery but plugged in, if I try to power on the smartphone, the led blinks).
Do you have some suggestions?
Click to expand...
Click to collapse
I mean, i guess this might not work since your N1 is now Liquid Damaged but try this:
Fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot erase cache
fastboot erase recovery
Note: you will need a recovery image and a rom zip so that you can test out if your N1 boots into recovery or not, if it does proceed to flashing the rom then reboot, and still Your phone has acquired Liquid Damage, nothing i have told you might work, it might not even get recognised by the Computer that is being used for the current operation, your phone might even end up in smoke...ok maybe not but you have been warned.

Hi, thank you for you reply. I tried what you said but without success, the recovery continues to bootloop (of course I re-flashed it).
Maybe I have to say goodbye to my N1 :crying:

ercoppa said:
Hi, thank you for you reply. I tried what you said but without success, the recovery continues to bootloop (of course I re-flashed it).
Maybe I have to say goodbye to my N1 :crying:
Click to expand...
Click to collapse
Not really, you can send your phone into a dealer to get a part changed well mainly the motherboard because that is dramatically cheaper than purchasing a new phone
Sent from my Nexus One using xda app-developers app

You should have stuck it in a bag of rice as soon as you got home.
Sent from my Nexus One using xda app-developers app

cpm said:
You should have stuck it in a bag of rice as soon as you got home.
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
Now that he powered it on I guess its already corroded, because water+electricity = corrosion and that equals to damaged electronics
Sent from my Nexus One using xda app-developers app

humzaahmed155 said:
Now that he powered it on I guess its already corroded, because water+electricity = corrosion and that equals to damaged electronics
Click to expand...
Click to collapse
That's true, but if you search online a lot of people (e.g. youtube v=FQAUncGSVT0) were very lucky with N1 & water.
You should have stuck it in a bag of rice as soon as you got home.
Click to expand...
Click to collapse
You are totally right... but I was in Palma de Mallorca... very drunk and stupid :silly:.
Not really, you can send your phone into a dealer to get a part changed well mainly the motherboard because that is dramatically cheaper than purchasing a new phone
Click to expand...
Click to collapse
I don't know yet but probably here in Rome they will ask me too much money (>100€) if it is the motherboard. Maybe I can upgrade to an used Samsung Galaxy Nexus (~200€-280€),

ercoppa said:
That's true, but if you search online a lot of people (e.g. youtube v=FQAUncGSVT0) were very lucky with N1 & water.
You are totally right... but I was in Palma de Mallorca... very drunk and stupid :silly:.
I don't know yet but probably here in Rome they will ask me too much money (>100€) if it is the motherboard. Maybe I can upgrade to an used Samsung Galaxy Nexus (~200€-280€),
Click to expand...
Click to collapse
Good luck on your transition!
Sent from my Nexus One using xda app-developers app

ercoppa said:
That's true, but if you search online a lot of people (e.g. youtube v=FQAUncGSVT0) were very lucky with N1 & water.
You are totally right... but I was in Palma de Mallorca... very drunk and stupid :silly:.
I don't know yet but probably here in Rome they will ask me too much money (>100€) if it is the motherboard. Maybe I can upgrade to an used Samsung Galaxy Nexus (~200€-280€),
Click to expand...
Click to collapse
While your at it I still need to see the toughness of the phone if you know what I mean, how's about a drop test which YouTube is yet to see as you will be the first one to do it on YouTube
Sent from my Nexus One using xda app-developers app

Made my own Factory cable/ Not Working

So I made my own factory cable but doesn't seem to work when I plug my kindle fire hd 7 device. It doesn't go into any fastboot mode, or anything.
I used a tutorial on youtube
I can not order one, I couldn't find any in my country.
Please see attachments, to see pictures of my work with the cable. Do you know what might be wrong?
The wire used is taken from a charger.
I have also tried to check device with the KFHD_SRT tool. It just says waiting for device
thanks

Yeah you didn't do it right...
http://forum.xda-developers.com/showthread.php?p=39569189
Sent from my XT907 using xda app-developers app

rajavan said:
So I made my own factory cable but doesn't seem to work when I plug my kindle fire hd 7 device. It doesn't go into any fastboot mode, or anything.
I used a tutorial on youtube
I can not order one, I couldn't find any in my country.
Please see attachments, to see pictures of my work with the cable. Do you know what might be wrong?
The wire used is taken from a charger.
I have also tried to check device with the KFHD_SRT tool. It just says waiting for device
thanks
Click to expand...
Click to collapse
I agree, you didn't do it right. The pins are located much closer to the tip of the widget. See those long legs running to the tip? those lead to the soldier joints.

Screw Up Stories?

I don't know if this will catch on or not, but I'd like to hear people's stories on how they screwed up or thought they screwed up their phone and fixed it? I think this could be an interesting thread with plenty of good stories and such

absoluterebirth said:
I don't know if this will catch on or not, but I'd like to hear people's stories on how they screwed up or thought they screwed up their phone and fixed it? I think this could be an interesting thread with plenty of good stories and such
Click to expand...
Click to collapse
I haven't screwed this phone up but I remember when I first started rooting phones I bricked my Vibrant (Galaxy S). I think I bricked it because I flashed the wrong radio or something. After that I have never bricked another phone. **Knock on wood**
Now I take extra caution and read extensively before rooting, flashing Roms, kernels etc.
sent from my neXus 5

Heres how i screwed my Nexus 5 on stock, I forgot to charge it and its now dead..
How i fixed it? I charged it :good:

I didn't because I actually read the stickies on the top of the general forum.
/Thread
Sent from my Nexus 5 using Tapatalk

Just took apart my Nexus 5 after it was unresponsive after a week of putting into rice/silica gels. No idea of what I am doing. I have never opened anything up in my life. Soaked motherboard into isopropyl and cleaned it with toothbrush, dropped it like 10 times, ripped a couple of cables. Should be all good though. Will post if it worked.

eastpac said:
Just took apart my Nexus 5 after it was unresponsive after a week of putting into rice/silica gels. No idea of what I am doing. I have never opened anything up in my life. Soaked motherboard into isopropyl and cleaned it with toothbrush, dropped it like 10 times, ripped a couple of cables. Should be all good though. Will post if it worked.
Click to expand...
Click to collapse
Yeah, ripping cables is probably not going to turn out "all good". Just my opinion

markdapimp said:
Heres how i screwed my Nexus 5 on stock, I forgot to charge it and its now dead..
How i fixed it? I charged it :good:
Click to expand...
Click to collapse
Please accept this Thanks as your post is very accurate and straight to the point.:good: Many of us have had that experience before whether it's forgetting to charge it over night by not plugging it into a charging source or it running out of battery power from heavy/extented usuage and not being able to charge it immediately after.:highfive:

DON`T USE TOOLKITS, these are related to most screwups Oh and get your rooting/flashing/adb skills up to par

FuMMoD said:
I didn't because I actually read the stickies on the top of the general forum.
/Thread
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Same!
Sent from my Nexus 5 using Tapatalk

I've only totally bricked one device, that was a sprint HTC evo (og evo). I got a replacement device via insurance and due to new firmware, I bricked it trying to root it/set s-off. No fix possible, only a new phone.
As far as nexi, nexus 5 specifically, I've soft bricked it a ton of times. But, one of the reasons I love the nexus brand, its never taken any more than a nandroid restore or only once a revert to stock. Unless you Dev test (and knowingly flash untested fw) or just start randomly picking zips and flash a modem or boot loader from a different device I've found it damn near impossible to make a nexus device unrecoverable.
I did initially flash the multi-boot mod w an incompatible ROM (beanstalk) and a kernel that really didn't like the multi-boot idea either (don't remember which ver of which kernel ATM). I was stuck on the "Google" boot loader screen for hours til I tried flashing a different ROM (which also changed the kernel) and trying again. Frustrated the hell out of me, kept phone unusable for almost a whole day, and wasted a ton of my time due to my laziness to read the whole thread.
Best advice ever given on XDA, whether you are a novice/learning/a noob or a android pro many years of experience or even a skilled developer.....
ALWAYS, ALWAYS, ALWAYS... did I say ALWAYS read the whole op or even better whole op and hopefully 90%+ of the thread before you try something you are unsure of.
Sent from my Nexus 5 using Xparent Skyblue Tapatalk 2

helioXverse said:
As far as nexi
Click to expand...
Click to collapse
Nexuses

Had the device perfectly set-up, with a few twrp backups as well and then for no reason...moved those backups from the device to the pc (probably in order to free some space). Then in a sequence of screw-ups, downloaded Flashify and wiped the cache and and dalvik cache from within the app (thinking it would be cool)...AND...bootloop! No backups...nothing! Booted to recovery...wiped cache/Dalvik the usual way, still nothing! Wiped data...nothing! Couldn't get ADB to work in the recovery. Finally -> Bootloader -> Fastboot Flash Stock ROM!
Did not stop though. in the next 5 minutes I was back with custom recovery, root and Titanium backup...ready to get back the device in shape (done and dusted as I type )

Reading the undervolting thread I decided to go -75 across the board. I succeeded but then tried to push it lower. Bootloops occurred. Backup copied back to SD card from PC failed to restore (said data failed. This was my first time restoring a ROM on the Nexus 5. If someone has insight as to why this happened it would be appreciated). Decided to go aosp and flash Rasta + trinity kernel but for some reason my mobile data wouldn't activate nor could I update PRL or profile by clicking on the usual option even after reboot and continuously clicking. Now I'm just getting my phone back to the original state it was in before I screwed up my UV values. Cataclysm + ElementalX #Life of a Phone Nerd
Sent from my Nexus 5 using XDA Premium 4 mobile app

gee2012 said:
DON`T USE TOOLKITS, these are related to most screwups Oh and get your rooting/flashing/adb skills up to par
Click to expand...
Click to collapse
I actually used a toolkit to return mine back to stock after i shipped it out to LG for repair after my son dropped. It was much easier for me than to write out the commands. took me about 10 minutes and that was because I locked the bootloader before flashing a zip. and i had to go back yada yada but worked out fine.

Screwed up 2 Galaxy S2's, first one because I didn't pay close enough attention to the brickbug, second one because it just died... Due to the brickbug. Other than those I've never killed a phone. I thought I had broken my friends Nexus 5 though, I unlocked it and went to root it for him but TWRP/CWM couldn't mount any partitions because it's "encrypted". Got it fixed though.
I've killed xbox's, PSP's, everything. It's all part of the learning process.

...When I first got my Nexus 5 in MTP on my Windows PC I had my phone hooked up to, on Internal Memory I saw a folder called sdcard that was not there before that was supposedly empty according to MTP. Deleted it. Turns out it was a symlink screwup in MTP, and it deleted my entire SD card including photos, luckily the important ones were already uploaded to Facebook and such. Now I backup my phone almost daily just in case.
I bricked my Archos Home Connect 35 once. Kinda my fault. I had set the bootloader to boot SDE firmware for it defaultly on boot. (Dev edition firmware from Google that was rootable). I updated from .82 firmware to .83 firmware, forgot to change that. It took the SDE firmware out, normally youd have to reinstall it, and since it was set to boot from that in Archos. mess of a firmware and bootloader, it would just bootloop because the SDE firmware wasnt there. No way to get out of it. RMA'd it and got a new one from Archos though. Never again, will always just manually select the SDE Dev Edition firmware when/if i ever reboot it. (Its just a Alarm clock mostly that plays Pandora occasionally. it last went 300 days without a reboot until it hard locked and I had to reboot. )
Never had a unrecoverable problem with my Galaxy S4, or my Nexus 5.Worst case with the S4 I Odin'd back to stock firmware. Nexus 5 got a corrupt data or cache partition once, i could have ran fsck but I flashed stock images instead.

I was having an issue having my phone seen on my PC. This is after I've rooted... Transferred music and pics from PC to phone, so I knew my drivers were installed. So I tried going back to stock. I downloaded the stock image and tried fastboot flashing. My download was corrupted. It got froze sending the radio. Froze for 30 min... Just kept saying sending. So I finally unplugged and rebooted to bootloader as everything else has been wiped. Tried again and it froze again at sending the boot loader. Froze for 30 min. I unplugged and tried rebooting. It never turned back on. No charging indication or anything. Officially bricked. I had tmo send me a new one and I'm returning the old one today. Wish me luck
First brick of my life and I've been rooting and modding since the OG Nex1
Sent from my Nexus 5 using Tapatalk

My GPS was working intermittently so I applied the cardboard fix and now its great. But in the process I damaged my back cover and now NFC and wireless charging don't work.
Really wishing I just RMA'd it.
Sent from my Nexus 5 using XDA Premium 4 mobile app