cnt flash rom from pc - Nexus 7 Q&A, Help & Troubleshooting

i had this issue with my nexus had to flash it back to stock and now for some reason it only recognizes it as a camera and it will flash everything but the rom it flashes the gaps and apks i thought it might be a bad rom but it always says the same thing about md5 . im totally stumped on this it work perfect when it didnt recognize it as camera . i could really use some help big time on this issue

Try deleting and reinstalling the drivers in device manager with USB debugging enabled on your tablet....this was what fixed the issue for me.

Related

XDA Mini S Screen problem

I've got a problem with my XDA Mini S. It's been sitting in a box in my shed for about a year, before I got it out yesterday to have a play around with it, and possibly try some software I found on it.
I put my sim card in, plugged it in to charge, and turned it on. It worked absolutely fine.
I haven't done anything with it yet, but I've turned it on now, and the colours are messed up on the screen. For example there is a red hue over the today screen, and on certain screens (like in bootloader mode) the colours appear to be inverted (I will post pictures later if needed).
I've tried reformatting the device, but this has not fixed the problem. I thought I would try reflashing the rom on it. I used to have the original o2 rom on my old laptop, but lost that when I had to reload windows.
I downloaded the original rom from here, along with the Rom Update Utility, and attempted to reflash it. It gets as far as 'verifying the information on your PDA phone', then crashes with the error: Rom update utility MFC application has stopped working.
I'm running windows vista on my laptop, and read that the RUU won't work until the drivers are updated. Following the instructions on mrvanx.org, I have downloaded the driver for vista and installed it, but i'm still getting the problem when I try and reflash the device.
I've also tried running the RUU in compatibility mode for XP as it worked fine on my old laptop which was running xp, but it still crashes, every time.
I'm beginning to wonder if reflashing it will even work though, since the colours are messed up in bootloader mode as well, which leads me to think it may be a hardware problem.
I know next to nothing about repairing these though, and probably wouldn't bother if it's a hardware problem, but until I can reflash the firmware, I won't know whether this is a case.
I'll get the photo's of what the screen is like uploaded to my server later on, and post the links here, so you can see what the problem is.
Show photos and specific error when reflashing arrangement.
sorry my english
photo's are in this thread: http://forum.xda-developers.com/showthread.php?t=384800
The original thread double posted for some reason.

Vega 1.09 ROM, installed USB mode switcher with odd results

Hi all,
I've been loving my Vega since getting it a few weeks ago, but have noticed a bit of an issue with the latest firmware. When I installed the Modaco USB Mode Switcher tool, gave it SU permissions and switched to host mode to allow usage of a thumb drive, it rebooted perfectly. I copied over the files from the vega that I needed, and removed the USB drive. Switched mode and rebooted and now when I go into wireless settings, under Wifi it shows Error, and MAC address shows Unavailable. This happened twice now, I reflashed the device thinking I had arsed about with something I shouldn't have changed then installed things one by one testing for a day or so after each install and no sooner had I installed the USB Mode Switch, it happened again.
Is it just me? Have I got a duffer, only it worked ok in 1.08.
Cheers
Pete
I have had some trouble with the usb switcher with my rom add-on, thats why i removed it from that thread. I seems to change the boot.img some how. Last time i tried it it changed my green android icon back to the old Booting..... Looks like it needs to be updated for v1.09 firmware.
original_ganjaman said:
I have had some trouble with the usb switcher with my rom add-on, thats why i removed it from that thread. I seems to change the boot.img some how. Last time i tried it it changed my green android icon back to the old Booting..... Looks like it needs to be updated for v1.09 firmware.
Click to expand...
Click to collapse
Thanks OG. Glad it isn't just me. Cheers for your hard work by the way.
So is it not possible to ennable usb host mode on the 1.09 firmware then? This is such a shame because i needed to use my usb pen drive with my vega...... will it be possible aanytime soon?
Thanks
Notch another one with troubles using the USB switcher ...
Yup, had the same thing last week. I installed a clean 1.09 and added OG's clean addon. As there was no usb mode switcher included I installed it from the modaco rom. After a reboot my wifi stopped working, too. I flashed the device and switched to the latest modaco rom (apparently that puts you back to 1.08, though), but dont have much of a choice because I really need the usb switcher.. Hope OG is able to find a fix for this issue..

[Q] darky 10.2 boot problem

Yesterday I needed to take a picture and used my Galaxy S. for it. After that I connected my phone to my laptop USB port and got an unknown device error. Assuming it was a driver problem I re-installed them keeping the same error.
I also got telephony problems before, after some minutes calling the other side couldn't hear me anymore and I needed to put the call on wait and back to continue the call.
Both problems together made me decide to update my Darky 10.1 Extreme edition to the latest 10.2 Extreme edition. I took my sd card out and copied the darky 10.2 zip to it using my laptop. Put it back in and used Astro filemanager to copy it to the internal sd. Because I can't use the usb port this was the only way.
Rebooted to recovery and flashed 10.2. After reboot the screen stayed at the boot screen with green Darky text for half an hour without doing anything. No vibrate or anything. I did read some info about 10.2 before i downloaded it but missed the lagfix point. Tried to get into recovery and luckily that worked. Turned on the lagfix, did hear the computer voice 2 or 3 times and last time it said lagfix was enabled. Rebooted to recovery again, checked lagfix was on, also for next boot, and flashed 10.2 again. Same problem, hangs at bootscreen.
Turned lagfix off again and flashed the old 10.1 again. Same problem again, this time only bootscreen with white SG text and both button lights on. Nothing for the rest. Flashed back, after lagfix enabled, to 10.2 again without luck. Again bootscreen only.
Someone knows how to fix this? Because of the usb problem I can't use Odin. I did read somewhere now there might be a cable problem or a dirty usb connector on the phone. Checked the connector visually and can't see any dirt, I also keep it closed when not using it.It does load the battery also when connected to my laptop. At least it did when I first got the unknown device error.
1) USB Error
I am not sure you have Only installed the USB driver alone or Kies it self. Anyway, try this http://support.microsoft.com/kb/315265. Scandisk with delete currupted file on your disk drive and replace with default window file. You can reinstall your driver/Kies on your laptop after scandisk complete.
2) First, you must come from JVP or JVQ base rom. JVO and older rom have older bootloader. What you need to do is to flash JVP or JVQ stock rom with bootloader into your phone. Then, flash over Darky 10.2 over the phone. Take note that Darky still have many problem and it is not that stable yet. I've run it over a week and decided to dump it. The rom is too big at 215MB where else others rom only 195MB. The startup is too slow, take 5-10min after reboot the phone. The initial start up takes nearly 15min after flash.
from.insider said:
2) First, you must come from JVP or JVQ base rom. JVO and older rom have older bootloader. What you need to do is to flash JVP or JVQ stock rom with bootloader into your phone. Then, flash over Darky 10.2 over the phone. Take note that Darky still have many problem and it is not that stable yet. I've run it over a week and decided to dump it. The rom is too big at 215MB where else others rom only 195MB. The startup is too slow, take 5-10min after reboot the phone. The initial start up takes nearly 15min after flash.
Click to expand...
Click to collapse
If your boot takes so long, you doing something wrong
First boot, yes... it takes some time. But then, the animation isn't finished yet and I'm already good to go (after media bla bla bla)
@OoZic
For darkys rom... i had the same problem.
First flash Ficetos resurection 10.2, then make shure lagfix is ON (full lagfix - check in voodoo control app) and then flash 10.2 extreme edition
For details go to
http://www.darkyrom.com/community/index.php?threads/v10-2-final-what-are-you-waiting-for.4253/
I had the problem too
Thank you for your reply from.insider
Problem is the phone can only do bootscreen and recovery. The device isn't recognized in any way. Tried it on 2 computers (laptop/PC) with different multiboots (Win7 X64 and Vista X86 on both). Maybe that is because the OS isn't loaded and can't go to MTP?
Is there a way to copy something from external SD to internal SD within recovery menu? Because that way I can copy a JVP or JVQ image to internal. Now there are only the 10.1 and 10.2 zips from Darky.
FSCK didn't find any problems btw.
Thanks again.
Problem solved, my Galaxy is unbricked and working again. Very happy now
Can't post a link because of low post count but the answer is on post-87372 on Darky.com.
The USB problem also went away, but after using Titanium to put my backup back the problem was here again. something in my settings or a service is screwing something up with the mtp I think. Used Android Booster to kill some things and it works again. As soon as I know what exactly is screwing up my mtp I will let you all know.
OoZic said:
Problem solved, my Galaxyd and working again. Very happy now
Can't post a link because of low post count but the answer is on post-87372 on Darky.com.
The USB problem also went away, but after using Titanium to put my backup back the problem was here again. something in my settings or a service is screwing something up with the mtp I think. Used Android Booster to kill some things and it works again. As soon as I know what exactly is screwing up my mtp I will let you all know.
Click to expand...
Click to collapse
Can you copy and paste the the answer and post it here man, i cant find the post your talking about and my phone has the exact same problem.

[Q] Advice Please - Mobile Odin - Could not detect device model - USB not recognizing

Hi all, hoping to get some advice in regards to a brick wall I've hit.
So background, my Galaxy S4 (i9505 running 4.2.2) has had ongoing USB recognition issues and thus I haven't been able to upgrade to a custom rom for a while. After following a couple of very detailed and useful guides on here, without success I had decided that it was likely one of two things:
A hardware problem (I have a third party charging port installed after the OEM stopped working)
Or when I was playing around with settings I derped and uninstalled the MTP application or some related core service.
So I left it for a while but today I decided to do something about it and discovered Mobile Odin (4.20), bought it and clean flashed SlimKat 4.4.4 (http%www%slimroms%net/index.php/downloads/dlsearch/viewcategory/1182-jflte). Took a while but the rom booted, really liked the look and I tried to install 3rd party apps and set up phone as usual but noticed that Google Play Store was missing. Manually installed V4.9 but it kept opening and closing so I uninstalled and the flashed the normal gapps and the AIO gapps through Mobile Odin (with and without clear cache), both processed OK but upon reboot none of apps ever installed.
So I decided to re-flash the SlimKat, I had to re download as I performed a factory restore in amongst things and had the original rom stored on internal. When I flashed inject root was checked as were all the other default options but upon reboot Mobile Odin is giving me "Could not detect device model" which after looking around basically means I lost root .
So my questions are: Without connecting via USB (because it's still not working) what are my options for flashing another rom or regaining root? Is there a way to get to stock 4.4.4 without USB?
Really appreciate any advice, currently the phone has network service and WiFi so in the mean time, without Google Play store it is just a significant inconvenience, but still operational.
Regards,
Marc
#Update
I don't know how but my root has been restored while I was playing around clearing app cache's etc. So now I have SlimKat 4.4.4 but unfortunately still no Google services/Store etc. When I manually install it, it has this issue where it automatically opens and then closes, so still working on fixing that. Again appreciate any input.
Hello, I've been flashing ROMs for a while now and I can't think of a way to regain root from within the ROM itself. How did you get root on your device in the first place to install mobile odin?
I have never used a play store application for any type of flashing, was never sure if it would be reliable or not. That being said, have you installed a custom recovery into your phone whilst you were playing around with it? If you did then you can fix this without fixing your USB connection.
However if you still have stock recovery, you probably need a USB connection to regain root. If that is the case, what have you actually tried to fix the USB problem?
lichking21st said:
Hello, I've been flashing ROMs for a while now and I can't think of a way to regain root from within the ROM itself. How did you get root on your device in the first place to install mobile odin?
I have never used a play store application for any type of flashing, was never sure if it would be reliable or not. That being said, have you installed a custom recovery into your phone whilst you were playing around with it? If you did then you can fix this without fixing your USB connection.
However if you still have stock recovery, you probably need a USB connection to regain root. If that is the case, what have you actually tried to fix the USB problem?
Click to expand...
Click to collapse
Hey @lichking21st. Mobile Odin is allegedly just odin without the need for USB. I have tried to fix the USB to no avail
Actually just about to update my original post, I don't know how but my root has been restored while I was playing around clearing app cache's etc. So now I have SlimKat but unfortunately still no Google services/Store etc. When I manually install it, it has this issue where it automatically opens and then closes, so still working on fixing that. Again appreciate any input.
Problems solved!
Clean flashed stock rom then clean flashed back to SlimKat. Google play and root carried over.
USB still not working have to put it down to a hardware issue now. Oh well, so happy
@MOD you can close this. Thanks again for the help LichKing
grinchenator said:
Problems solved!
Clean flashed stock rom then clean flashed back to SlimKat. Google play and root carried over.
USB still not working have to put it down to a hardware issue now. Oh well, so happy
@MOD you can close this. Thanks again for the help LichKing
Click to expand...
Click to collapse
Glad to see your problem is fixed, I would still advise you to get a custom recovery so you have some options if you really get stuck without root for next time. I recommend using TWRP but CWM works too.

Crazy USB

Well guys . This is my problem
I was using MOL 5.1.1 and life was perfect. So I decided to try something else and flashed Darklords. Becouse I was buggy I returned back using mybackup.
Problem:
1) charging from adapter(wall) not working
2) charging using PC goes perfect (really fast)
3) PC dont recognize phone so I cant use odin nor Kies to flash completely stock.
I tried a couple kernels and still the same
Any suggestions?
Thanks

Categories

Resources