Related
Just was wondering. I'm more used to what clockworkmod has so I figured it would be easier to install that instead. But I wanted to make sure it was supported before I went ahead and installed it. Anyone know?
Yes. ClockworkMod works just fine on the Kindle Fiya. there is no looking back now.
androidcues said:
Yes. ClockworkMod works just fine on the Kindle Fiya. there is no looking back now.
Click to expand...
Click to collapse
awesome. so i'm ok with installing it straight from rom manager right?
i'm a little paranoid bc a lot of people seem to be posting about bricking their fires.
Unknown. But if you follow the "bricked fire" threads, you'll see that most people find ways to get them back. So I think a lot of folks are at times stuck, but not truly bricked. I think the most common problem, and the one that bit me too - is being stuck in fastboot and therefore having the device not accessible by adb. And they, like me, panic a bit and think they've bricked it. Granted, I'm sure there are ways of truly bricking it, but as long as you're patient, I think KFU and the fastboot command can get you out of most problems.
gadgetman13 said:
Unknown. But if you follow the "bricked fire" threads, you'll see that most people find ways to get them back. So I think a lot of folks are at times stuck, but not truly bricked. I think the most common problem, and the one that bit me too - is being stuck in fastboot and therefore having the device not accessible by adb. And they, like me, panic a bit and think they've bricked it. Granted, I'm sure there are ways of truly bricking it, but as long as you're patient, I think KFU and the fastboot command can get you out of most problems.
Click to expand...
Click to collapse
thanks man, gonna go ahead and do it in a bit. fingers crossed .
Where do you find the CWM files to download?
Sent from my Kindle Fire using Tapatalk
Bmcd37 said:
Where do you find the CWM files to download?
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
it installs when you start up rom manager for the first time
EDIT: Woops, just went to install it and it says it's not officially supported yet. Anyone know where to get it?
Looks like there's more to it. Guess I'm gonna be going by this guide to install early CM9:
http://liliputing.com/2011/12/how-to-install-cyanogenmod-7-on-the-amazon-kindle-fire.html
HeliosAI said:
it installs when you start up rom manager for the first time
EDIT: Woops, just went to install it and it says it's not officially supported yet. Anyone know where to get it?
Click to expand...
Click to collapse
I thought CWM required the use of hardware buttons?
HeliosAI said:
Looks like there's more to it. Guess I'm gonna be going by this guide to install early CM9:
http://liliputing.com/2011/12/how-to-install-cyanogenmod-7-on-the-amazon-kindle-fire.html
Click to expand...
Click to collapse
Go to the development section. It says beta but its solid, I did most of the alpha testing for it and doom lord did the port. Is not officially supported by koush. If you know how to use fastboot, you can't fastboot flash recovery.img if u can't figure it out pm me. I'll get u going.
Sent from my Amazon Kindle Fire using xda premium
smirkis said:
Go to the development section. It says beta but its solid, I did most of the alpha testing for it and doom lord did the port. Is not officially supported by koush. If you know how to use fastboot, you can't fastboot flash recovery.img if u can't figure it out pm me. I'll get u going.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Agreed. Doomlord's CWM recovery port is awesome. It's touch based and I've tried most every feature and it seems very solid. I installed it in a much easier fashion than most... I just copied it to my SD area and used the dd command to put a copy into the recovery partition. I did this during normal operation of the Kindle.... No fastboot necessary in using that method. Neall.
.
ndoren said:
Agreed. Doomlord's CWM recovery port is awesome. It's touch based and I've tried most every feature and it seems very solid. I installed it in a much easier fashion than most... I just copied it to my SD area and used the dd command to put a copy into the recovery partition. I did this during normal operation of the Kindle.... No fastboot necessary in using that method. Neall.
.
Click to expand...
Click to collapse
That method is sketch. Fastboot is the proper way to flash a recovery. Any other way you risk trouble. Wear your rubbers and use the fastboot binary.
androidcues said:
That method is sketch. Fastboot is the proper way to flash a recovery. Any other way you risk trouble. Wear your rubbers and use the fastboot binary.
Click to expand...
Click to collapse
its not sketch, just no room for error.
put recovery.img on the root of ur SD card, than open mobile terminal, than type these commands.
su (enter)
dd if=/sdcard/recovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery (enter)
just don't mistype it, all it does is make a copy directly to the /dev folder.
this is how, rom manager actually puts cwm on ur device.
or use this http://forum.xda-developers.com/showthread.php?t=1500935
Sent from my HTC Glacier using xda premium
I see a couple of different tools here to unlock and root my Nexus 7. What are the differences between them?
I do not want to flash ROMs; just unlock, root and install cwm recovery.
Nate2 said:
I see a couple of different tools here to unlock and root my Nexus 7. What are the differences between them?
I do not want to flash ROMs; just unlock, root and install cwm recovery.
Click to expand...
Click to collapse
fastboot oem unlock, fastboot flash cmm recovery, flash the su binaries, reboot and profit.
Search for wugfresh nexus root toolkit. Very simple to use.
Sent from my Nexus 7 using xda premium
frozenspark said:
Search for wugfresh nexus root toolkit. Very simple to use.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Don't use tools for rooting with the Nexus devices, it's useless in my opinion. Try to understand the basics behind rooting, recovery and fastboot, do it manually and you will be able to help yourself even if something is not working as expected.
Sent from my Nexus 7 using xda app-developers app
Use this: http://forum.xda-developers.com/showthread.php?t=1809195
This is the best tool for Nexus 7.
AndDiSa said:
Don't use tools for rooting with the Nexus devices, it's useless in my opinion. Try to understand the basics behind rooting, recovery and fastboot, do it manually and you will be able to help yourself even if something is not working as expected.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Even though I know how fastboot, recovery and rooting works, I still use this tool without any of those commands. And it serve the purpose for me quickly. Of course using such tools will not stop you from learning more afterwards.
I wouldn't say its useless.
Sent from my Nexus 7 using xda premium
frozenspark said:
Even though I know how fastboot, recovery and rooting works, I still use this tool without any of those commands. And it serve the purpose for me quickly. Of course using such tools will not stop you from learning more afterwards.
I wouldn't say its useless.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
then you should br helping out all the people that mess up their devices afyer using toolkits and dont know how to fix it. i havent seen you help out, yet you are still recommending toolkits. why is that?
I used the steps outlined at http://rootzwiki.com/topic/28544-guide-nexus-7-bootloadersrecoveriesrootback-to-stock/ to guide me.
I must say it might not be trivial for the non-software-developer types.
I was a Java developer for many years, so I didn't have much problems setting up Java,
Android-sdk, etc.
My N7 was recognized by adb when booted normally, but after I flashed cwm, I could not do 'adb shell' to mount the /system partition and rename the recovery-from-boot.p file to prevent the recovery from getting reset to stock each time.
I ended up installing the ROM Manager app to enable me to boot into cwm recovery.
I have done the obligatory cwm backup. I believe this is the nandroid backup?
Edit:
I used my Linux box to re-flash the bootloader and cwm recovery images to the Nexus 7, and I could 'adb shell' and rename the recovery-from-boot.p file. So I'm all set now.
I just needed to run 'adb start-server' and 'fastboot' using sudo, so it might have been a permissions issue on my Windows box.
Sent from my unrooted DroidX using Tapatalk
I used Wug's Root Toolkit. Both of the toolkits seem good, but that was just the first one I saw. The Wug's Toolkit is an application and the other one is in a CMD.
Sent from my SGH-T989 using xda premium
Linexus said:
Use this: http://forum.xda-developers.com/showthread.php?t=1809195
This is the best tool for Nexus 7.
Click to expand...
Click to collapse
+1
Absolutely brilliant ToolKit, very simple, fast and works like a charm.
I rooted my N7 with this, and had no issues to date.
Only took a couple of minutes.
BRILLIANT!
Looks like I'm not all set, after all Today, right before I plan to take the JB 4.1.2 OTA update, I notice my tablet won't boot into CWM, like it did a couple of days ago. I did rename the one file and things looked normal. What could have happened to my CWM?
Edit:
So there are 2 files that need to be renamed, not 1?
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
And there was a bug in JB 4.1.1 that prevented booting into cwm recovery unless the device was plugged into USB??
Sent from my Nexus 7 using Tapatalk
I re-flashed the same cwm recovery img, reinstalled the same su zip, and I'm back to normal
Gotta watch out for those OTA updates, I tell ya.
Use the fastboot commands
Good to see you alright!
This is like asking "Should I get an automatic or manual car?"
veeman said:
This is like asking "Should I get an automatic or manual car?"
Click to expand...
Click to collapse
In the early days, automatic transmissions were more problematic and much more expensive. Today they are pretty efficient, even though a manual transmission gives you better control over the car, which most people don't really need for everyday driving.
If you frequently get stuck in stop-and-go traffic, you'll wish you had an automatic transmission.
Look at these lazy people..
Beamed from my Grouper.
Nate2 said:
Looks like I'm not all set, after all Today, right before I plan to take the JB 4.1.2 OTA update, I notice my tablet won't boot into CWM, like it did a couple of days ago. I did rename the one file and things looked normal. What could have happened to my CWM?
Edit:
So there are 2 files that need to be renamed, not 1?
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
And there was a bug in JB 4.1.1 that prevented booting into cwm recovery unless the device was plugged into USB??
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes there was a bootloader bug on the nexus 7 and most people could not boot into CWM recovery without plugging it into their computer.
I however used TWRP back then [have since switched back to CWM touch, now that the bug is fixed] and had no issues. Now I have no issues with CWM touch, I can boot it directly from fastboot menu, or "reboot -> recovery" when booted.
Nate2 said:
I re-flashed the same cwm recovery img, reinstalled the same su zip, and I'm back to normal
Gotta watch out for those OTA updates, I tell ya.
Click to expand...
Click to collapse
exactly what I would have done! sounds like you're getting the hang of it. and yes, I definitely recommend manual rooting/fastbooting to a toolkit.
Wilks3y said:
+1
Absolutely brilliant ToolKit, very simple, fast and works like a charm.
I rooted my N7 with this, and had no issues to date.
Only took a couple of minutes.
BRILLIANT!
Click to expand...
Click to collapse
Yes that's my favorite too. It does it all and more. It slices, it dices, it'll even cut a can!
Nate2 said:
In the early days, automatic transmissions were more problematic and much more expensive. Today they are pretty efficient, even though a manual transmission gives you better control over the car, which most people don't really need for everyday driving.
If you frequently get stuck in stop-and-go traffic, you'll wish you had an automatic transmission.
Click to expand...
Click to collapse
Yeah, that's what I'm saying. They both have their ups and downs. If you're willing to learn a little about how Android works and learn some adb and fast boot commands then you should definitely do it manually.
If you just want to be a "1337 Haxorz" and aren't willing to learn then just use a toolkit.
OK, just one sub-question on rooting. I see no real reason to root except maybe to get more tablet interface than nexus has. Kinda like when the wifi indicator is at the bottom, since there are those !$#$$ back/home buttons already and a lot of wasted space Anyways, the question.
I bougth N7 16Gb and upgraded via forced OTA to 4.1.2. Do all these root methods work with 4.1.2?
Thanx,
D.
I've tried eveything, the Nexus toolbox, ADB, and even Chainfire's auto root. I've managed to unlock my bootloader, but whenever it comes to rooting (depending on which way I try to root) the command prompt will stay at "Downloading boot.img" or "Sending Recovery (7806 kb)" until i either reboot my Nexus or close cmd. How can i root this damn device? I'm going insane! Thank you!
AW: My nexus won't root!
Did you tried Wugs nexus root toolkit? Of not try it, you can't do something wrong it's sooo easy!
http://forum.xda-developers.com/showthread.php?t=2015469
Tell me if it worked or not
Swyped from my beast the Nexus 4
Fast boot devices , check if a device comes up
Sent from my Nexus 4 using Tapatalk 2
miniAndroidian said:
Did you tried Wigs nexus root toolkit? Of not try it, you can't do something wrong it's sooo easy!
http://forum.xda-developers.com/showthread.php?t=2015469
Tell me if it worked or not
Swyped from my beast the Nexus 4
Click to expand...
Click to collapse
Thank you. But it still sticks on "Booting modified boot.img to enable running privileged commands..."
I've just noticed that My Computer/Windows Explorer isn't showing my Nexus when its connected as MTP. Could that be the problem? And if so, do you know how to fix it? thanks.
okmijnlp said:
Thank you. But it still sticks on "Booting modified boot.img to enable running privileged commands..."
I've just noticed that My Computer/Windows Explorer isn't showing my Nexus when its connected as MTP. Could that be the problem? And if so, do you know how to fix it? thanks.
Click to expand...
Click to collapse
Try doing the whole process again from step one using the toolkit and install that will guide you step by step in installing the proper drivers and such. I usually do everything manually but I went into lazy mode and did everything just fine and with little time as well. :good:
UZ7 said:
Try doing the whole process again from step one using the toolkit and install that will guide you step by step in installing the proper drivers and such. I usually do everything manually but I went into lazy mode and did everything just fine and with little time as well. :good:
Click to expand...
Click to collapse
Thanks but I've even done that 3 times now. uninstalling & reinstalling drivers, unlocking & relocking. still, the sae problem persists :crying:
Try a new USB cord and port. Make sure USB debugging is on
Sent from my SPH-D710 using xda premium
Go to androidrootz.com and try his method. Worked for me on a Mac and I am not very computer savy. He also has windows version for rooting.
Ian B
Censura_Umbra said:
Try a new USB cord and port. Make sure USB debugging is on
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
+1 I'm betting usb debugging not turned on again after you unlocked bootloader.
clockcycle said:
+1 I'm betting usb debugging not turned on again after you unlocked bootloader.
Click to expand...
Click to collapse
Usb debugging is on .
Sent from my GT-I9100 using xda app-developers app
It's a long process but i ended up having to use a Linux virtual machine (luckily i had one for work anyway).
No matter what toolkit or manual step to install drivers, i couldn't get Win7 to detect the phone, however, attaching it in VmWare to an Ubuntu guest system worked straight away. I got the adb/fastboot files by following instructions in a thread here on XDA and was rooted in minutes
May be worth a shot
Toolkits are a waste of space. Do it manually, it's only like four steps and you will see exactly what is happening and where (if anywhere) you're going wrong.
Ok, tired of waiting for the OTA KitKat update for my Nexus 7 2012 tablet, I downloaded the OTA update and sideloaded it with adb. Got a status 7 error and now it's stuck on a bootloop. Thing is, my Windows 8 laptop won't recognize the device anymore (code 43 error on device manager) when on recovery or bootloader. There's even no way to instal google's usb drivers or anything because it says the device malfunctioned. I downloaded the factory image but, obviously, can't sideload it or do anything with it.
Please give me a hand with this, I'm really desperate.
More detail would be nice. What did the bootloop go between? Had you installed any custom recovery like CWM?
Are you still able to access fastboot mode?
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
More detail would be nice. What did the bootloop go between? Had you installed any custom recovery like CWM?
Are you still able to access fastboot mode?
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Sorry, wasn't sure what you needed. The bootloop esentially goes from recovery to off and then to recovery again. I am able to go to fastboot normally (power and volume down when off).
Wanting to root the device a while ago, I unlocked it and rooted it whitout issues. Since the 4.3 update though, it was a little more difficult to root so having no time to research I just left it at that. That's all that was done to the Nexus 7. No Custom Recovery, no ROM, no nothing. Now, waiting for 3 weeks for KitKat, decided to sideload the OTA update (I did check the version was my device's version) the status 7 error appeared and all hell broke loose with the computer not recognizing the device.
Well, since you still have access to your fastboot menu, there isn't anything to worry about. Once you resolve the driver issue, you must be able to re flash the image.
Sent from my GT-S5570 using xda app-developers app
Duplicate post. Please erase.
nobody_nowhere said:
Well, since you still have access to your fastboot menu, there isn't anything to worry about. Once you resolve the driver issue, you must be able to re flash the image.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Yeah, that's what relaxes me a bit, but I can't seem to fix it for 20 hours straight. I use this for studying.
Well, I suggest using another computer (a friend's or relatives') or installing a Linux distro like ubuntu. Oses other than Windows usually don't have such problems. I suggest you download something called adb gui which as I recall did a pretty fine job of 're installing the drivers for me.
But then, please do correct me if I'm wrong... I think that you must first use the device on adb and get the drivers installed and then only can you use it by the fastboot interface.
Sent from my GT-S5570 using xda app-developers app
I used Wug nexus root toolkit to install drivers (windows 8.1) there are clear instructions (if you click manual or something similar) how to get drivers to work.
Yeah, actually I did use the toolkit when I was trying to update to KitKat. Thing is, it doesn't work since the bricking occurred.
Yeah, I'll try on another pc, and I'll keep you posted.
Thanks
Sent from my Nexus 4 using xda app-developers app
I'm having a very similar issue. Mine will try and bootup but just stays on the boot animation for as long as I could wait, 10 minutes or more. bootloader is working just fine and I should be able to use fastboot commands to resolve the issue. I'm not able to get to recovery for one reason or another, but it is updated to the latest CWM.
The trouble I am having is the same though. I cannot for the life of me get the drivers to work. I have tried it on one win8 pc, and one win7 pc. I haven't tried any of the toolkits to help with driver installation on the win8 pc yet. I also have another pc that I am going to try also has win8 on it as well. If you can get the drivers installed, please post a reply as to what you did here, and I will do the same, from what I have been able to find you and I aren't the only ones that are having this issue.
If the windows route doesn't work, I have a copy of Ubuntu that will be going on the computer to see if that resolves my issues. Also, may want to try another cord, I have a couple that are charge cords only. Once getting the drivers working it should be a very simple job.
Johnson90512 said:
I'm having a very similar issue. Mine will try and bootup but just stays on the boot animation for as long as I could wait, 10 minutes or more. bootloader is working just fine and I should be able to use fastboot commands to resolve the issue. I'm not able to get to recovery for one reason or another, but it is updated to the latest CWM.
The trouble I am having is the same though. I cannot for the life of me get the drivers to work. I have tried it on one win8 pc, and one win7 pc. I haven't tried any of the toolkits to help with driver installation on the win8 pc yet. I also have another pc that I am going to try also has win8 on it as well. If you can get the drivers installed, please post a reply as to what you did here, and I will do the same, from what I have been able to find you and I aren't the only ones that are having this issue.
If the windows route doesn't work, I have a copy of Ubuntu that will be going on the computer to see if that resolves my issues. Also, may want to try another cord, I have a couple that are charge cords only. Once getting the drivers working it should be a very simple job.
Click to expand...
Click to collapse
Since you say that you do have ubuntu I suggest using that to fix your issue.... just download and execute the command fastboot from the terminal
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
Since you say that you do have ubuntu I suggest using that to fix your issue.... just download and execute the command fastboot from the terminal
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Johnson90512 said:
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Click to expand...
Click to collapse
It pretty much cancels out any problems with drivers.
It is easy to do.
It takes 5 minutes to boot up and test? Try it for yourself
Sent from my Nexus 5
Johnson90512 said:
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Click to expand...
Click to collapse
If I did have any driver issues, the first thing I'd do is reinstall drivers, and if necessary, Windows itself, because I like everything to be working perfectly.
But supposing that that was not an option and I needed my phone or tab real bad, ubuntu would be my first choice. Especially because the concept of installing 'drivers' doesn't exist in ubuntu.
No, that should be fine. As long as you have used terminal before and you know the basics.
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
If I did have any driver issues, the first thing I'd do is reinstall drivers, and if necessary, Windows itself, because I like everything to be working perfectly.
But supposing that that was not an option and I needed my phone or tab real bad, ubuntu would be my first choice. Especially because the concept of installing 'drivers' doesn't exist in ubuntu.
No, that should be fine. As long as you have used terminal before and you know the basics.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
I appreciate the advice, I will give it a shot this evening, and let you know if this works. I'm sure that it will.
Alright, so I got SDK up and running on Linux! It was a little bit of a pain, but it installed just fine. Once I got it all installed I was able to see the nexus 7 through fastboot! From there I was able to reinstall the bootloader. Then was able to get to recovery to do an adb push to get a rom of 4.4 on to it. 4.4 installed just fine. All problems are fixed Good suggestions guys!
I don't know how, but my S4's screen broke internally (Through pressure, according to AT&T saying they are "pressure cracks").
Beyond that
I upgraded to the S5 (Knowing if I get a replacement S4, it's likely to be upgraded which I don't want so might as well get the S5), and I would love to get my pictures and stuff back without having to repair the S4 screen. The only problem is that it has a pattern lock on it. I do not think it had USB debugging on it, but it was rooted with SS. Kies and Windows don't completely recognize the device, only that it's plugged in. Need help on getting the stuff off. Please help!!
If usb debugging is off there's not much you can do. You could try to boot into recovery and the use adb to pull files off. Try "adb devices" and see if it regonizes your device. If it does then use "adb pull/sdcard/ c:\sdcard"
Sent from my Nexus 5
jd1639 said:
If usb debugging is off there's not much you can do. You could try to boot into recovery and the use adb to pull files off. Try "adb devices" and see if it regonizes your device. If it does then use "adb pull/sdcard/ c:\sdcard"
Sent from my Nexus 5
Click to expand...
Click to collapse
Boot to stock recovery or SS recovery? Also, can you use the volume keys on SS? I haven't tried it, so if you can I could use screenshots so I can guide myself through and mount USB. Or do that through the stock recovery but I don't know if it has that option. Other than that, just booting into either recoveries doesn't detect the device....
Bumppp?
SkyAttacksX said:
Bumppp?
Click to expand...
Click to collapse
Try booting into ss and then use adb pull /sdcard/*·* c:\sdcard If it works it'll take a long time
Edited
Sent from my Nexus 5
jd1639 said:
Try booting into ss and then use adb pull /sdcard/*·* c:\sdcard If it works it'll take a long time
Edited
Sent from my Nexus 5
Click to expand...
Click to collapse
No devices attached....
SkyAttacksX said:
No devices attached....
Click to expand...
Click to collapse
Sorry man, I'm out of ideas.
Sent from my Nexus 5
You could probably send it off to mobiletechvideos who could probably pull the data off.
Brain fact! What about using Heimdall to do a partial flash. You might be able to get past that lockscreen then.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Red_81 said:
You could probably send it off to mobiletechvideos who could probably pull the data off.
Brain fact! What about using Heimdall to do a partial flash. You might be able to get past that lockscreen then.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Heimdall? Sorry for being a noob, I only had the S4 from September xD
Heimdall is an open source alternative to Odin. The MAC guys are forced to use it since Odin will not run on a MAC.
The part I was curious about is why your device does not mount as a hard drive when you plug it into your PC. Is that because of the lockscreen? I never use once personally.
It sounds like you may just have driver issues. You could even try downloading the Ubuntu LiveCD, booting to that, and then plug in your phone to see if it appears.
Red_81 said:
Heimdall is an open source alternative to Odin. The MAC guys are forced to use it since Odin will not run on a MAC.
The part I was curious about is why your device does not mount as a hard drive when you plug it into your PC. Is that because of the lockscreen? I never use once personally.
It sounds like you may just have driver issues. You could even try downloading the Ubuntu LiveCD, booting to that, and then plug in your phone to see if it appears.
Click to expand...
Click to collapse
Well, it does mount. The problem is that no files are shown since it has a lockscreen... And alright I think http://forum.xda-developers.com/showthread.php?t=2374441 that's it right?