This is relating to a friend's Eris. Awhile back he went to the Kaos rom and had been enjoying it. Wanted to switch to the newer version of it, but after he finished the upgrade USB functionality disappeared.
When connected it still charges, but that's it. You can't see the phone or USB storage via a computer. Tried this on a couple of computers which I normally connect phones to, as well as a brand new XP install. USBDview showed no USB device connectivity from the phone.
Found out some basic terminal commands weren't working, neither was SU so I took the phone and flashed it back to stock (FlashBack 2.1), wiped everything, as if the phone was right out of the box. Got everything back up and running in pure Eris Verizon stock mode. Still no USB.
Used the famous "1 click" Eris root, burned the rootme.zip, and verified root/SU/terminal commands were working. Then tried USB. Nothing. Installed a couple of different roms. Still nothing. Installed the new Kaos one.. nope, no dice. Cleared Dalvik each time. I got ADB to work but only through wifi since there's no USB connection.
We spent probably 4 hours on this. Searched all the places I could think of, nobody seems to have a similar problem.
Something is whacked on the phone, either USB service files or USB hardware (such as the connector on the phone).. or maybe you guys can lend a hand. Tried different PC's, different USB cables. Nothing worked.
Did you try rebooting both the phone and the PC, with the phone disconnected?
Could be that the hardware (connector or electronics) is fried and the occurrence of that and the ROM flashing was merely coincidental. That seems like the highest probability given that you've tried the phone out on multiple PCs and also replaced the software with the factory software.
Does the PC make any noises ("ker-dunk" or "ker-donk") when you plug the phone in via USB?
When it is plugged in, have you looked in the (Windows) device manager at each of the devices underneath each "Universal Serial Bus Controller", to see if any of them have VID_/PID_ pairs such as:
0BB4:0C98 (USB Debugging On - Composite allows ADB and/or Mass Storage)
0BB4:0FFF (Fastboot/HBOOT/RUU modes)
0BB4:0FF9 (USB Debugging Off - Mass Storage only)
See this post for a little background on how to poke around with Windows drivers.
Frankly though, from the way you've described things, it sounds like a hardware problem.
If you can get hold of a Mac or a Linux PC, I'd see if it works there. With my Mac, anyway, I need no drivers to communicate with the Eris - it just works. Windows just seems to be a PITA sometimes with Erises.
roirraW "edor" ehT said:
Did you try rebooting both the phone and the PC, with the phone disconnected?
Click to expand...
Click to collapse
Aye
bftb0 said:
Could be that the hardware (connector or electronics) is fried and the occurrence of that and the ROM flashing was merely coincidental. That seems like the highest probability given that you've tried the phone out on multiple PCs and also replaced the software with the factory software.
Does the PC make any noises ("ker-dunk" or "ker-donk") when you plug the phone in via USB?
When it is plugged in, have you looked in the (Windows) device manager at each of the devices underneath each "Universal Serial Bus Controller", to see if any of them have VID_/PID_ pairs such as:
0BB4:0C98 (USB Debugging On - Composite allows ADB and/or Mass Storage)
0BB4:0FFF (Fastboot/HBOOT/RUU modes)
0BB4:0FF9 (USB Debugging Off - Mass Storage only)
See this post for a little background on how to poke around with Windows drivers.
Frankly though, from the way you've described things, it sounds like a hardware problem.
Click to expand...
Click to collapse
Yeah been through all of that, no noises. I had the Hardware tree expanded and had USBDeviceView running (application which gives you every nook & cranny detail on USB connections) and it showed nothing.
The second I plugged anything else in, it instantly showed up.
I think the next step is to grab some probes and check the data pins on the phone.
Thanks for the helpful replies so far.
Try rebooting into recovery and enabling usb ms toggle. Worked for me and I was having the same problem. Once the SD card loaded on the PC I backed up everything important (including the rom i wanted to use next), deleted everything else, and then formatted the card to Fat32 (not changing the name and using full format NOT quick). Afterwords I put the rom back onto the freshly wiped SD, hit the trackball to disable USB ms, and then i wiped the data and dalvik, flashed the rom, let it load and sync for a few, plugged it in and eureka!! USB woked again on the phone and PC.
Sent from my RedGlassV2 using XDA App
settlethestorm said:
Try rebooting into recovery and enabling usb ms toggle. Worked for me and I was having the same problem. Once the SD card loaded on the PC I backed up everything important (including the rom i wanted to use next), deleted everything else, and then formatted the card to Fat32 (not changing the name and using full format NOT quick). Afterwords I put the rom back onto the freshly wiped SD, hit the trackball to disable USB ms, and then i wiped the data and dalvik, flashed the rom, let it load and sync for a few, plugged it in and eureka!! USB woked again on the phone and PC.
Sent from my RedGlassV2 using XDA App
Click to expand...
Click to collapse
Good suggestion. Now that you mention it, I think I've seen this work to get some people going again.
We tried the MS toggle switch, one of the first things actually. Here's what happened. When he pressed it, it said it successfully unmounted. In doing so it took away the option on the menu to 'return' to the previous menu (paraphrasing here). The only way the option would return is if you re-mounted it.
Here's the tricky one though, if you didn't remount the memory it didn't matter anyhow because it would re-mount itself in a bout a minute or so of idle time at the screen. We tried simply taking the battery out after receiving the success screen, but found out it was still mounted anyhow afterward.
One thing you pose which does interest me is formatting the SD card again. Even though I ran a check and it comes up fine and we've been copying files to/from it, I wonder if a good thorough formatting would help. Sometimes that's fixed problems in the past. Definitely will try that next, and before using it will wipe the cache and see if that helps. Thanks for the tip!
We'll post up our findings once we can re-try this stuff.
Well I'm glad to offer any help, after all, I was having a wicked similar problem to yours. I believe your correct about the SD. I think it was the fresh format that did the trick. From what I've heard, the stock Eris SD card just isn't that great. There not meant for constant writing and I think just my regular usage (apps2sd, flashin roms frequently, downloading torrents, and heavy data usage) all played a role in screwing up the SD card. Beause as you flash roms, unless its 2.2 to 2.1 or vice-versa, the SD card never gets touched. I consistently had about 4.5gb filled out of the 7 at all time, sometimes more. I would open up the SD and not even recognize half the folders or files. I have a feeling some of those files were telling my phone NOT to connect via USB or install or uninstall ANY apps. That was my exact problem, and the format cleared it all up perfectly first try. After days of troubleshooting, tweaking in adb, flashing multiple froyo roms only to find nothing would install, and more or less being p*ssed off at my eris u can imagine how happy I was lol.
Sent from my RedGlassV2 using XDA App
Related
My phone wouldn't connect to my computer, like when I plug it in, the LED on the phone turns on, but it wouldn't have the little USB icon in the notification bar, and on my computer, it would say "Device Not Recognized".
I tried different computers, different cables, uninstalling USB drivers, and nothing worked, so I decided to do Factory Reset. Unfortunately, I forgot I deleted the stock Home Launcher (did the whole app cleanup thing), so when I turned my phone on, there was just a black screen with only the notification bar. I could receive messages and texts, but that was it.
I tried restarting my phone, and now it gets stuck at the Sony Ericsson logo. Is there any way to fix it? -- This was on X10a Generic rom.
I also have 2.2. installed in dual boot, but it has some bugs (none of the radios worked, no market, screen keeps flashing).
Will appreciate ANY suggestions on how to fix. Thanks in advance.
EDIT: Anyone have similar experiences/know if Rogers will fix it under warranty?
I highly doubt Rogers will agree that it is covered under warranty... I'm not sure how the 2.2 build works.. perhaps you could try install the stock home launcher through that and then factory reset? (But what the launcher has to do with USB I have no idea)
Did you do something specific that caused it to stop working? Maybe you can try reverse that
I deleted the stock launcher and used LauncherPro instead...but when I did factory reset, it deleted all my apps. Not sure if that matters though, because it gets stuck at the Sony Ericsson logo screen now..
chris_knows said:
I deleted the stock launcher and used LauncherPro instead...but when I did factory reset, it deleted all my apps. Not sure if that matters though, because it gets stuck at the Sony Ericsson logo screen now..
Click to expand...
Click to collapse
Will it go into flash mode?
When I connect while holding down the back button, the LED on the phone goes to green like it's in flash mode, but on my computer, if I use flasher, it says "Unable to open channel", and if I try with PC Companion or SEUS, they don't recognize that the phone's connected.
try to put the home launcher apk on the SD card and then boot on android 2.2 and copy it to the specified folder for that, that should work.
ellokomen said:
try to put the home launcher apk on the SD card and then boot on android 2.2 and copy it to the specified folder for that, that should work.
Click to expand...
Click to collapse
I don't have any file managers installed though. Also no internet or USB, so I can't put any apps on...Unless Android has some sort of built in file manager?
Hmm...When I try booting into 2.1, it gets stuck at the Sony Ericsson logo, but if I swipe my finger across the bottom, it vibrates a little, like when you're unlocking it...
Can you still boot into the 2.2? If so then attatch a usb cable and enable usb debugging. Open up adb and, type
Adb shell
Killall servicemanager
This will reset your phone and fix the flashing screen and radio.
As for your 2.1, I recommend reflashing. Your open channel error is from having the wrong dev Id. There are threads about flashing your phone. I suggest you read carefully, or stick to sony ericsson update service, because you don't seem to be reading threads properly, and we don't want you to break your phone
Sent from my X10i using XDA App
Thanks everyone for the help. It looks like it was an issue with the SD Card, because I just tried putting a new one in and everything works fine.
*By fine, I mean I can connect through USB and just reflash it.
chris_knows said:
Thanks everyone for the help. It looks like it was an issue with the SD Card, because I just tried putting a new one in and everything works fine.
*By fine, I mean I can connect through USB and just reflash it.
Click to expand...
Click to collapse
I have the same issue, i tried another sd card (from a Desire), but still was the same: cannot mount via usb.
What means it was a new one? Have you formatted the sd card?
That's strange...I was able to connect yesterday with the new SD card (like brand new from store), but now it won't work...Tried reformatting, un/re-installing drivers.
I'll keep looking at it, I guess something else I did yesterday must've fixed it...
Tried reformatting the sd, uninstalling drivers too, without success. There are some forums appearing the same issue, i think it is NOT hardware related.
We should investigate this.
What of these programs did you use, before the issue started?
My suspicious programs are:
-Root explorer (starting JiT-toggle-0.1 - with no luck)
-Terminal Emulator (starting JiT-toggle-0.1 - ok)
-ES Security Manager (Thread detector)
I'm very disappointed, we need some good advice.
To check if your SD card is ok, you can buy an USB to SD card adapter AND Micro-SD card adapter. You will get both for about $5 (you don't need high value stuff, beat the eBay monster ).
mck3ni said:
-ES Security Manager (Thread detector)
Click to expand...
Click to collapse
Don't use such crap, it's highly useless and cause much more bugs than helps
I have the same problem. Windows show me the xperia like "unknown device" but the cell charge without problems. It seems to be the connector micro usb.
Obviously, I'm new to this site, as I imagine most are when they have their first big issue.
Right off the bat, I want to admit that this is solely my fault, and I have been trying to fix it for the past day... To make matters worse, the phone was a gift from my wife for our anniversary, so, I feel pretty bad about it...
The situation:
I rooted my phone yesterday with RazrBlade. I had to do a factory reset to get it to stick, but that was fine. I then installed Boot Menu Manager. I set up the necessary partitions, system_3 system.img (300mb), cache.img (300mb), and data.img (2Gb). I realize I probably should have given system more room... but I didn't think that was app related. I then flashed Liquid-JB-v2.8-OFFICIAL-spyder and gapps-jb-20130301-signed from goo.im. It didn't tell me the system partition was out of memory, so I assumed (like a fool) that everything was OK...
After a few reboots to the wrong system, namely the stock system, I decided to go into BMM and change the default to system_3, and then I did the dumbest thing possible: I thought to myself, "Wow, it would be a pain to see this bootloader each time my phone reboots. I'll turn the delay to 0!" So... I did...
The Problem:
My phone now boots straight past the recovery to system_3, which seems to have no space allocated for applications at all, including system ones. I attached a picture of the storage details. It goes through the setup process each time I reboot, and wipes any changes I make. I can't download apps, and I can't install them via APK because the phone thinks there is no space left. I don't have BMM installed in this system so I can't turn the delay up, to my knowledge. There is no file explorer on this system, so I can't go into the app files directly. I have tried connecting with "Android Commander" but it doesn't want to detect my device. I installed the ADT bundle for windows to get the usb driver, but still nothing... I also tried a factory reset again, but that does the same thing as rebooting for me now.
The Challange:
To my knowledge, I'm out of options, but I know most of you guys do this to see what you are capable of. I'm sure you've dealt with bigger issues. Can anyone help? Would Verizon techs be smart enough/have the right software to actually reset the phone?
Thanks!
RustyRazr said:
Obviously, I'm new to this site, as I imagine most are when they have their first big issue.
Right off the bat, I want to admit that this is solely my fault, and I have been trying to fix it for the past day... To make matters worse, the phone was a gift from my wife for our anniversary, so, I feel pretty bad about it...
The situation:
I rooted my phone yesterday with RazrBlade. I had to do a factory reset to get it to stick, but that was fine. I then installed Boot Menu Manager. I set up the necessary partitions, system_3 system.img (300mb), cache.img (300mb), and data.img (2Gb). I realize I probably should have given system more room... but I didn't think that was app related. I then flashed Liquid-JB-v2.8-OFFICIAL-spyder and gapps-jb-20130301-signed from goo.im. It didn't tell me the system partition was out of memory, so I assumed (like a fool) that everything was OK...
After a few reboots to the wrong system, namely the stock system, I decided to go into BMM and change the default to system_3, and then I did the dumbest thing possible: I thought to myself, "Wow, it would be a pain to see this bootloader each time my phone reboots. I'll turn the delay to 0!" So... I did...
The Problem:
My phone now boots straight past the recovery to system_3, which seems to have no space allocated for applications at all, including system ones. I attached a picture of the storage details. It goes through the setup process each time I reboot, and wipes any changes I make. I can't download apps, and I can't install them via APK because the phone thinks there is no space left. I don't have BMM installed in this system so I can't turn the delay up, to my knowledge. There is no file explorer on this system, so I can't go into the app files directly. I have tried connecting with "Android Commander" but it doesn't want to detect my device. I installed the ADT bundle for windows to get the usb driver, but still nothing... I also tried a factory reset again, but that does the same thing as rebooting for me now.
The Challange:
To my knowledge, I'm out of options, but I know most of you guys do this to see what you are capable of. I'm sure you've dealt with bigger issues. Can anyone help? Would Verizon techs be smart enough/have the right software to actually reset the phone?
Thanks!
Click to expand...
Click to collapse
I like to see you getting out of that one anyway,have you tried switching default storage? I mean try that I think that way the phone "thinks" your external sd is your internal memory and vice versa that might give you a chance to install BMM or a root explorer and debloat system..you got nothing to loose give it a try man,go to settings/advance and switch default storage,good luck.
Sent from my XT910 using xda premium
FIXED!
AztekSoul said:
go to settings/advance and switch default storage,good luck.
Click to expand...
Click to collapse
Unfortunately, I tried that. The problem was that it requires a reboot, which wiped any settings
HOWEVER, the fix was along that line, it just required me to go into android shell and tell it manually.
I followed these steps to make the phone install to the SD card (internal phone app partition really) by default (because I'm a newb, I can't post links, so just google "how-to-install-android-apps-to-the-sd-card-by-default-move-almost-any-app-to-the-sd-card").
After doing so, I still had a problem downloading BMM from the market, but I think that was due to the market being outdated and troublesome, so I had to find an apk version instead.
I installed it, and restored the boot delay to 30 secs.
I then immediately booted to system_1 to feel safe.
I may try loading the Liquid Smooth rom again once I've fixed the partitions, but I will NEVER turn BMM's boot delay to 0 s EVER again...
It just stopped working. When I plug into PC, it just says it's charging? No idea what I could have done. I even tried restoring my backed up stock rom, but that made no difference. Tried two different PC's. What settings should I look for? Can I get to it via reboot, and pressing something. I seem to remember one time when my phone wouldn't boot, that I still had USB access.
big_dog1968 said:
It just stopped working. When I plug into PC, it just says it's charging? No idea what I could have done. I even tried restoring my backed up stock rom, but that made no difference. Tried two different PC's. What settings should I look for? Can I get to it via reboot, and pressing something. I seem to remember one time when my phone wouldn't boot, that I still had USB access.
Click to expand...
Click to collapse
If you have CWM installed then yes, you *should* be just fine. In mounts and storage menu, the last option i think is "mount USB storage" and it will show up in windows as removable storage then. If this doesn't work I can guess two things, one, your cable only has the power pins still connected, and not data. So try another cable. Or, on the USB connector inside your phone its not connecting both data pins, only power.
Should be able to visually check for damage to the micro usb port. Best of luck.
[r.]GimP said:
If you have CWM installed then yes, you *should* be just fine. In mounts and storage menu, the last option i think is "mount USB storage" and it will show up in windows as removable storage then. If this doesn't work I can guess two things, one, your cable only has the power pins still connected, and not data. So try another cable. Or, on the USB connector inside your phone its not connecting both data pins, only power.
Should be able to visually check for damage to the micro usb port. Best of luck.
Click to expand...
Click to collapse
I have TWRP. Does that change the suggestion?
big_dog1968 said:
I have TWRP. Does that change the suggestion?
Click to expand...
Click to collapse
not if there is an option to enable storage, I haven't used twrp in forever, so I can't tell you definitively. You could download CWM on your device and flash it in TWRP though.
USB port appears fine. Tried different cable that works on my son's phone and it still didn't work. Is there an app that is good for troubleshooting usb connections someone could recommend. Thanks.
big_dog1968 said:
USB port appears fine. Tried different cable that works on my son's phone and it still didn't work. Is there an app that is good for troubleshooting usb connections someone could recommend. Thanks.
Click to expand...
Click to collapse
According to google TWRP does have an option to mount usb storage, have you tried seeing if windows can recognize your phone storage in recovery?
An alternative solution could be to use a shared folder in windows and ES file explorer to connect to that share, and send and receive files that way, so at least you have some ability to manage the device. *through WiFi on the phone to the LAN that your PC is on*
I would suggest deleting all the drivers for your device in windows but you already said you tried on a second computer. I'm stumped on this one at the moment.
[r.]GimP said:
According to google TWRP does have an option to mount usb storage, have you tried seeing if windows can recognize your phone storage in recovery?
An alternative solution could be to use a shared folder in windows and ES file explorer to connect to that share, and send and receive files that way, so at least you have some ability to manage the device. *through WiFi on the phone to the LAN that your PC is on*
I would suggest deleting all the drivers for your device in windows but you already said you tried on a second computer. I'm stumped on this one at the moment.
Click to expand...
Click to collapse
Thanks for the suggestions. So far, none have worked. I wonder if there is an android app, that can check if the usb ports are working or not?
I had the same problem on SlimBean, Beanstalk and maybe another I can't remember. Switching to dvhexer's CM 10.2 fixed it. I THINK my problem was that those other ROMs require the phone to have been on stock 4.1.2 before flashing and dvhexer's CM 10.2 doesn't. I'm not sure, but that seems likely to me. In any case, make a backup of your current ROM and flash CM 10.2 to see if that fixes the issue. I really like Beanstalk but the ability to connect to my PC is vital to me so I'm on 10.2 for now. Hope this helps.
Sent from my Optimus G using XDA Premium 4 mobile app
Removed
Have the same problem :/ it randomly happened to me, haven't found any sort of fix.
I think I'm going to go back to stock, take it to a service center and say, "it aint workin". Still under warranty. Doubt they'll do much snooping if it appears to be running stock Rom.
Can you even flash back to stock? I tried flashing it once and it wouldn't boot, completely wiped everything and reinstalled and it still wouldn't boot, so I'm stuck on custom roms apparently with no connection to pc so no lgnpst possible
Sent from my LG Optimus G using Tapatalk 4
I installed Cyanogenmod 10.1 on my Galaxy S2 which is working fine except when I try to connect it to a PC through USB. I plug in the cable and nothing, absolutely nothing, happens. Not even a sound or an unrecognized device.
However, when I reboot into Download mode, I hear a sound when connected and Zadig can see it. When I disconnect, I hear the disconnect sound. This has led me to believe it has something to do with the ROM.
I have tried different PCs, same results. Installed the USB Switcher app from Play Store, nothing changed. Downloaded and installed the latest Samsung USB drivers from here, reboot and still no signs of life. :crying:
Not sure if this is related but when I go to System Settings>Storage>USB STORAGE the "Mount USB card" option is grayed out. Even though I have an microSD card installed and I can listen to the music that's stored on it. Furthermore, I can access it in the CM File Manager app but only with superuser privileges where it is mounted as sdcard1 (I can only browse sdcard0 in safe mode). Don't know how relevant this is but I thought I'd put it out there.
I'm sure there is someone smarter than me out there with the answer to my problem. Any help is greatly appreciated
Given what you've already tried (going back to stock, different PC's, etc, etc), and given how quick/easy/cheap it is to do yourself, I'd be replacing the USB board/port. KeithRoss39 has a guide in the General section; search for it. Has all the info you need to get it done without fuss. These things often don't die completely & will often show a few faults like you're seeing (I presume you can still charge the phone normally ?)
Well, you can always buy a card reader. They are like super cheap. I live in India where it costs around 30INR (which is less than half a dollar). So until you change your USB port, you can still transfer your files by removing the sd card and putting it in the card reader. Easy peasy!
Do hit the thanks button if i helped!
Or maybe it's the extSD bug from CM 10.x kernel, have you tried switching rom/kernel?
Inviato dal mio GT-I9100 utilizzando Tapatalk
Thanks for the replies! :good:
I don't think the USB board is broken because it worked when I used Heimdall to flash and ADB to push the CM.zip to the microSD card, two days ago. I bought the phone used where it was factory reset and I installed CM (10.1 stable) straight away. When I reboot into Download mode and connect the phone to my PC, it works. Then I can mount the microSD card through ADB so that's not really the problem. What I want is to connect my phone through USB to my computer without Download mode + ADB. Like "normal".
Aello, could you give me further info about this bug? I can't seem to find any reference to it through Google. No, I haven't tried switching ROMs beside my switch from stock (which I didn't use at all) to CM 10.1.
Any further tips would help
I would suggest you to try some different custom/unofficial ROMs, since CM used to have some issues on mounting the extSD in 10.1 and 10.2 kernel.
I think I'll just try that. Any suggestions?
Thanks!
I would firstly try to flash a different, compatible, kernel, such as dorimanx's or gustavo's or apolo's, try to go under the storage managment and see if any new menu pops up. If this doesn't fix the problem, I'd move to a kitkat rom with either built in kernel or switch to one of the mentioned (kitkat version).
Inviato dal mio GT-I9100 utilizzando Tapatalk
After researching quite a bit I have decided to go with Dorimanx's kernel. However, I'm just a little bit paranoid about bricking my phone and it would really help to get a clarification on some things beforehand.
According to the Dorimanx's installation guide I should reboot into recovery and install the zip from sdcard. Is CWM the right tool for this and how would I do it? Is it as simple as installing gapps, just install zip from sdcard? Boom, done! No need for any wipe/factory reset/etc?
Thanks for all the help so far!
I had the same issue when I flashed latest omniROM today, turns out the phone was in USB debugging mode so didn't connect. Go to developer options in settings and check it is not in USB debugging mode!
If you have no developer mode go to settings - about phone and then click lots on build number until it says you are a developer (or something like that), then the developer option will appear.
Hopefully that will fix it for you!
Dom
Kernel flashing is boom, done yes, tho caches (NO need to wipe data/factory) wiping doesn't hurt. CWM is the right tool and the new kernel will bring his custom recovery along (it will or will not change, depens on which recovery you are on). Make sure to get the right kernel for your rom!
Inviato dal mio GT-I9100 utilizzando Tapatalk
From what I've learned online, when rooting a device the changes that are done to the system are done on the ROM file. If true then is it possible to encrypt or overwrite on top of the ROM file to hide any past rooting information?
Reason: I've been having a USB port issue with my PC not being about to recognize the device when plugged into a PC using the micro USB cable. Searched online and found many different ways to troubleshoot the connectivity issue, but couldn't get it to work. Hit the MAYDAY button and said "no, it's not rooted", and yes it did update firmware to 13.3.2.1 so technically no, "it's not rooted"... anymore...
Question: Any ideas on how to "hide" this information to keep warranty?
I already have a replacement on it's way so I can side load through USB once again instead of using a cloud drive to transfer files back and forth. I personally think the current device I have has a corrupted file (some where) when the device died of having no battery power. Read it happening to other people, so I believe it. Used many cables, and many PC's including a Linux PC. Nothing, so Amazon support gave up, and decide to send me a replacement HDX since they concluded it's a physical hardware issue. As if one of the ports are not working to load drivers to the PCs using the pug-and-play method. I think that makes sense but I AM NOT 100% SURE OF THIS. I think it makes sense, but I'm not an expert yet. I don't know completely, so don't ask me.
What do you guys think? Am I pretty much screwed and need to forget about replacing this HDX? And probably wait for a better hardware-wise tablet to come out for a reasonable price? Or can I get the replacement, no questions asked?
H0B0onDRUGS2 said:
From what I've learned online, when rooting a device the changes that are done to the system are done on the ROM file. If true then is it possible to encrypt or overwrite on top of the ROM file to hide any past rooting information?
Reason: I've been having a USB port issue with my PC not being about to recognize the device when plugged into a PC using the micro USB cable. Searched online and found many different ways to troubleshoot the connectivity issue, but couldn't get it to work. Hit the MAYDAY button and said "no, it's not rooted", and yes it did update firmware to 13.3.2.1 so technically no, "it's not rooted"... anymore...
Question: Any ideas on how to "hide" this information to keep warranty?
I already have a replacement on it's way so I can side load through USB once again instead of using a cloud drive to transfer files back and forth. I personally think the current device I have has a corrupted file (some where) when the device died of having no battery power. Read it happening to other people, so I believe it. Used many cables, and many PC's including a Linux PC. Nothing, so Amazon support gave up, and decide to send me a replacement HDX since they concluded it's a physical hardware issue. As if one of the ports are not working to load drivers to the PCs using the pug-and-play method. I think that makes sense but I AM NOT 100% SURE OF THIS. I think it makes sense, but I'm not an expert yet. I don't know completely, so don't ask me.
What do you guys think? Am I pretty much screwed and need to forget about replacing this HDX? And probably wait for a better hardware-wise tablet to come out for a reasonable price? Or can I get the replacement, no questions asked?
Click to expand...
Click to collapse
just wipe the kindle from inside the rom like a return to factory setting and it will wipe your root and everything on the device including sdcard well internal sdcard anyway ,and you will be fine
jjrizzelcincy said:
just wipe the kindle from inside the rom like a return to factory setting and it will wipe your root and everything on the device including sdcard well internal sdcard anyway ,and you will be fine
Click to expand...
Click to collapse
Sounds good. I'll give feed back after they have received it, and again when they OK it. I was thinking that the factory reset only deals with the data on the "hard drive" portion, as in personal data or files like apps and books. I read that the ROM file of the HDX device is on the motherboard so I felt that there was no need to have to "delete", technically ignore/hide, the data of the old ROM file. I was wondering if there was a way to be sneaky and put a file that was the stock ROM and set the day the file was put there around the time the update 13.3.2.1 came out. I just don't want the issue of them saying that the warranty is void when the device is not rooted anymore .
Plus I can deal with a device that can not be recognized by a PC still. Just upload to a cloud my files using the Internet and all is good if they see it was rooted before and I have to deal with this old HDX.
H0B0onDRUGS2 said:
Sounds good. I'll give feed back after they have received it, and again when they OK it. I was thinking that the factory reset only deals with the data on the "hard drive" portion, as in personal data or files like apps and books. I read that the ROM file of the HDX device is on the motherboard so I felt that there was no need to have to "delete", technically ignore/hide, the data of the old ROM file. I was wondering if there was a way to be sneaky and put a file that was the stock ROM and set the day the file was put there around the time the update 13.3.2.1 came out. I just don't want the issue of them saying that the warranty is void when the device is not rooted anymore .
Plus I can deal with a device that can not be recognized by a PC still. Just upload to a cloud my files using the Internet and all is good if they see it was rooted before and I have to deal with this old HDX.
Click to expand...
Click to collapse
it will work just wipe it