Hi guys!
I have tried to get Android onto my phone and I'm stuck. I'm using the files/instructions from this thread. (HSPL has been done and confirmed)
I noticed there's a similar thread, but they seem to be talking about a different problem, even though it happened at the same step.
Looking at the step-by-step list from that thread, I am stuck between step 10, step 11 and step 12:
- I successfully flashed RHODIMG.NBH
- Took out the battery, booted up with USB and there's the blue screen of the miniPoopLoader (tee-hee, it says poop ).
- Text scrolls by, ends with -- suspend --.
That's it, nothing happens. I can reboot, and it just goes there again. One of the snippets of text reads "flash_read_image: failed 0 errors"
I thought this might be all fine afterall and that I just had to use Fastboot erase blabla to go ahead. But obviously that doesn't work. Most likely because step 12 says install drivers, but no request to install any drivers comes up on my Windows (using Win 7 64 - also, drivers in the package are all Vista - will those work?), which I assume is either because the phone never boots up "far enough" for windows to detect the device, OR because I'm a retard to all major phone hackers here, because I just have to copy them somewhere. (didn't find anything on the boards to suggest the later is true, but then again, who knows).
So, where's the stupid newbie mistake that I overlooked? This isn't the first flash I'm doing, flashed win 6.1/6.5 onto my Touch Pro (1 ), using a fine how-to on this board, and constantly tweaking my S2 and S3, but this seems to be too much for me to figure out.
Thanks for any help!
What phone are you using?
Basic trouble shooting would be.
Task 29, re-download & reinstall minipooploader.
This video gives some idea of what you should expect.Useful info starts around 7:00
http://www.youtube.com/watch?v=_qNCHqGPofI
I have never heard of a suspend error/dialog. Perhaps someone else can chime in.
I think he just hasn't prepped for fastboot properly.
Sometimes I have to reboot a few times to get the cable plug timing or *something* right... Not sure what it is, but occasionally when doing a new flash to Android I had issues with fastboot not being recognized - and obviously you won't be able to flash recovery without fastboot being functional.
So before you task29 and reinstall OP - try a few different things - try plugging the cable in BEFORE you boot the phone. Try pulling the battery again, and do the plug in cable before you turn it on. I can't remember what the secret is here, I know for getting into recovery you have to start holding power as soon as you see the blue screen - but obviously this is beyond where you are at.
arrrghhh said:
I think he just hasn't prepped for fastboot properly.
Sometimes I have to reboot a few times to get the cable plug timing or *something* right... Not sure what it is, but occasionally when doing a new flash to Android I had issues with fastboot not being recognized - and obviously you won't be able to flash recovery without fastboot being functional.
So before you task29 and reinstall OP - try a few different things - try plugging the cable in BEFORE you boot the phone. Try pulling the battery again, and do the plug in cable before you turn it on. I can't remember what the secret is here, I know for getting into recovery you have to start holding power as soon as you see the blue screen - but obviously this is beyond where you are at.
Click to expand...
Click to collapse
To enter fast boot you need to have the phone totally off (not rebooted) with the usb cable removed. Then plug usb cable into the phone with the phone off. Then press and hold the power button until the blue screen is done. Sadly I have been doing this all morning trying to resolve a problem of my own.
Tried that, resulting in a slightly different screen (see attached image). Other than that, no difference. I still don't get any request for the HTC drivers and going Fastboot erase recovery results in "waiting for device".
Could you check the list at the thread I linked in the original posting and tell me if I somehow missed something?
Step 10 worked fine.
Step 11 I guess is what Wizardknight commented on.
Step 12 is what confuses me and what's possibly the culprit here?
I bet it's just that without the drivers my PC can't send the Fastboot commands to the phone.
Everything before that worked fine with no errors and everything after that, is just hammering away at the console.
Thanks guys!
Sent from my GT-I9300 using xda premium
Urgh, no idea why it uploaded the picture sideways, sorry.
When instead I press the power button as soon as I see blue (as opposed to hold it all the time), I get the following (see image)
Sent from my GT-I9300 using xda premium
Looks like it is working ok on the phone. I am assuming you installed fastboot and ADB on the PC.
What happens when you open a command prompt and type fastboot devices?
BTW here are the more official install directions.
Lists nothing. After hitting enter, I'm back at the \android-sdk\platform-tools promt.
Sent from my GT-I9300 using xda premium
Was the usb port on the phone working ok in WM? Could you sync and other data related activities?
Does any unknown devices show up in your device manager on the pc?
Have you tried any other usb cables?
Solved.
I tried different ports and a different cable before, even though my cable worked fine before (and so did the port). Guess I have two dead cables here, because the third one did the trick.
Drivers installed at once, Android installed and I feel very stupid now. Thank you very much for being so patient with something this stupid.
wizardknight said:
Was the usb port on the phone working ok in WM? Could you sync and other data related activities?
Does any unknown devices show up in your device manager on the pc?
Have you tried any other usb cables?
Click to expand...
Click to collapse
This might be where you're going to have to go next OP. Sounds like it's all OK - so try different cables, different USB ports on the PC, and if you can - an entirely different PC altogether.
Vortagh said:
Solved.
I tried different ports and a different cable before, even though my cable worked fine before (and so did the port). Guess I have two dead cables here, because the third one did the trick.
Drivers installed at once, Android installed and I feel very stupid now. Thank you very much for being so patient with something this stupid.
Click to expand...
Click to collapse
Had that problem before too. Glad you got it sorted.
Related
Hi all
I have a problem with my hero not being recognized by my PC. This happened after a weekend trip and i charged the phone with iphone USB adapter as i lost my one and now after returning from my trip i connect my hero to my PC to be greeted with the "USB Device Not Recognized" message.
Also my Amon_Ra recovery i used has been wiped and i cant get into recovery or install any rom at all.
I am thinking this might be the same USB brick that affected some Desire owners but i am not sure.
So please if anyone can help me, please do.
Thanks in advance.
fizzle101 said:
Hi all
I have a problem with my hero not being recognized by my PC. This happened after a weekend trip and i charged the phone with iphone USB adapter as i lost my one and now after returning from my trip i connect my hero to my PC to be greeted with the "USB Device Not Recognized" message.
Also my Amon_Ra recovery i used has been wiped and i cant get into recovery or install any rom at all.
I am thinking this might be the same USB brick that affected some Desire owners but i am not sure.
So please if anyone can help me, please do.
Thanks in advance.
Click to expand...
Click to collapse
this happen to me. What i did was switch my phone off, plug in the usb and switched it back on. then wait for windows to say it not recognised. then go to to device and printers and uninstall the drivers for the phone. Disconnect and reconnect the usb back to the phone and it it will pick it up.
Can you try booting in fastboot and tell me if that is recognized?
it still doesnt recognize it in fastboot
fc_Kuro said:
this happen to me. What i did was switch my phone off, plug in the usb and switched it back on. then wait for windows to say it not recognised. then go to to device and printers and uninstall the drivers for the phone. Disconnect and reconnect the usb back to the phone and it it will pick it up.
Click to expand...
Click to collapse
i have tried that and it doesnt help
fizzle101 said:
i connect my hero to my PC to be greeted with the "USB Device Not Recognized" message
Click to expand...
Click to collapse
Sounds like its just a driver issue. Have you tried plugging it in, when you get that message open DEVICE MANAGER,... Find the yellow "!", right click it, uninstall, unplug phone, reboot PC.
.... Then use BTDAG's [Guide] How to Setup Correct Hero Drivers (for x86 & x64 users)
I hav the same problem. In recover mode it works but then turn on the phone, there is no popup options as before. Tried around with drivers but didnt work either. But found a solution which is very convenient. I dont know if it works on other ROM versions but I'm on 2.1 (Villain10).
- Install extended control widget (dont remember where I got it but you can google, it seems I cannot find it on the market)
- Add this widget to the home screen: Menu/Add to Home/Widget/ Extended Control bar (you can choose the size from 1x1 to 1x4) then select "Mass storage" at the bottom, apply.
Now you have a widget to turn on/off USB storage. When you connect Hero to the PC, just click on this widget then the PC will connect to the SD card, and click one more to turn it off.
ok i will give that a try
crk23 said:
I hav the same problem. In recover mode it works but then turn on the phone, there is no popup options as before. Tried around with drivers but didnt work either. But found a solution which is very convenient. I dont know if it works on other ROM versions but I'm on 2.1 (Villain10).
- Install extended control widget (dont remember where I got it but you can google, it seems I cannot find it on the market)
- Add this widget to the home screen: Menu/Add to Home/Widget/ Extended Control bar (you can choose the size from 1x1 to 1x4) then select "Mass storage" at the bottom, apply.
Now you have a widget to turn on/off USB storage. When you connect Hero to the PC, just click on this widget then the PC will connect to the SD card, and click one more to turn it off.
Click to expand...
Click to collapse
that didnt work. o well i guess i am stock with the rom i have there.
fizzle101 said:
that didnt work. o well i guess i am stock with the rom i have there.
Click to expand...
Click to collapse
i've got this problem once and it was as simple as the cable was damaged...
i changed the cable and since then, everything works try that.
robocik said:
i've got this problem once and it was as simple as the cable was damaged...
i changed the cable and since then, everything works try that.
Click to expand...
Click to collapse
i have tried everything. changed the cable, used different pc but nothing works. i think is a hardware problem, something might be broken inside or something like that
Did you ever got this solved? I have the same problem only i use stock rom 2.1 Hero.. driving me nuts ...
baklap said:
Did you ever got this solved? I have the same problem only i use stock rom 2.1 Hero.. driving me nuts ...
Click to expand...
Click to collapse
No i havent and i gave up trying because i dnt think there is a fix for it. if yours is unrooted and the warranty is still valid you should consider returning it to HTC maybe they might replace it
got the same problem. Any solution so far ??
ddotpatel said:
Sounds like its just a driver issue. Have you tried plugging it in, when you get that message open DEVICE MANAGER,... Find the yellow "!", right click it, uninstall, unplug phone, reboot PC.
.... Then use BTDAG's [Guide] How to Setup Correct Hero Drivers (for x86 & x64 users)
Click to expand...
Click to collapse
Did you try that?..... You need to do the reboot PC/Laptop after uninstalling ALL HTC drivers! Then when you reboot PC, plug phone back in, should say "not recognised" again,... then follow BTDAG's guide. T'is definitely a driver issue!
tried flashing 3 roms, modaco, radug and now kimera... none working.
can connect in fastboot, it shows up in device manager as android 1.0
ive tried 3 different usb cables and 4 differet pcs, still there is no response on my phone !!!
using villian rom 10.0 rite now.
okay it boots up into fastboot and fastboot usb shows up on the screen in red,
BUT when i use the "adb devices" command in adb it doesnt show the device,
it is showing as android 1.0 in devices and printers (windows 7)
You need to use....
fastboot devices
....when your are in fastboot.
What happens when you go into your recovery, select "Toggle MS/USB" with USB connected to PC?
okay
fastboot devices command shows some serial number.
then i tried adb remount, it gave an error....
enabling usb-ms with cable attached gives no response
ok i think it might be USB driver like ddotpatel said but i am not sure.
i reinstalled my whole windows 7 to 32bit now instead of the 64bit version i was using before and today i just connected my hero to my PC and windows 7 did its thing and installed the drivers and finally my hero can mount the SD card in my PC again although i kept getting this can perform faster in USB 2.0 port or something like that i didn’t care as long as i can mount my SD card again.
now went into fastboot and used the fastboot device command and i could see my hero serial no. but when i try to flash the amonra recovery i got the permission error (i cant really remember). i tried flashing using the adb method but still no luck.
so i went to market and downloaded rom manager and used it to flash clockwork recovery and now i could boot to clockwork recovery.
from this recovery i can now flash any rom i want and although there are still a few more problems i am glad now that i can flash custom roms again.
the problem i can see so far but i can deal with is
1. i don’t think fastboot commands work even if the phone is detected.
2. SD card mounts at USB 1.1 speed. (i have tried different ports and cable but still the same thing and this is the ports i use for my N1, Desire and my other android phones with USB 2.0 speed)
PS: adb commands for pushing and removing apps is working.
Hope this can be helpful to those experiencing the same problem.
Instead of re-installing your entire OS just use usbdeview to remove the failing drivers.
Also remove any old HTC Sync installs and install the latest version.
I thought I would share this. I am kind of answering my own question but I am not really sure how I got into the state that I did.
Today I realized that I could no longer connect via USB to my PC. My phone has DietICS ROM. I tried the following:
New Cable
New USB port
Cache wipe
Dalvik wipe
Factory Reset
Rolling back to a previous nandroid that I knew worked
Reinstalling USB drivers
I still couldn't connect the phone as a media device and nothing was reported in Device Manager.
I ended up trying to put the phone in download mode and firing up Odin (to see if it would show as connected) and whalla. It saw the phone. I shut the phone down and rebooted it again and everything was working as it should.
If anyone has any insight on this, it would be appreciated. I am still not sure if it was the PC or the phone that had the hiccup.
Did you try rebooting the PC? I don't see that on your list.
Occasionally I have issues with Windows 7 (and 8) where it doesn't see that a USB device was unplugged, and if I try to use that same USB port for something else it just never detects anything.
It's rare in my case, but maybe something similar happened on your end and just having a different device ID show up (download mode shows up as a different device) kicked Windows in the pants and got your USB drivers working properly again?
dstruct2k said:
Did you try rebooting the PC? I don't see that on your list.
Occasionally I have issues with Windows 7 (and 8) where it doesn't see that a USB device was unplugged, and if I try to use that same USB port for something else it just never detects anything.
It's rare in my case, but maybe something similar happened on your end and just having a different device ID show up (download mode shows up as a different device) kicked Windows in the pants and got your USB drivers working properly again?
Click to expand...
Click to collapse
bah, yes. Rebooting the PC was one of the first things. I missed that on my list.
Weird... happened again.
1.) connected device to USB. Got the double beep and charging but no "MTP" connection message on phone and nothing detected in windows.
2.) Booted phone into download mode. Connected phone and windows saw it.
3.) Rebooted phone again and everything works fine
Happened again (updating this thread for no apparent reason).
Fully powering down the phone and then booting it back up (cold boot) seems to be fixing it.
camoto said:
Happened again (updating this thread for no apparent reason).
Fully powering down the phone and then booting it back up (cold boot) seems to be fixing it.
Click to expand...
Click to collapse
I have the gnex and although different phone i just have plain out usb issues. Does your phone and/or battery have nfc chip?
*Android is upgrading...*
JediNinjafication said:
I have the gnex and although different phone i just have plain out usb issues. Does your phone and/or battery have nfc chip?
*Android is upgrading...*
Click to expand...
Click to collapse
Yes it does
camoto said:
Yes it does
Click to expand...
Click to collapse
Ok, I download all roms and mods directly from phone browser so don't usually have it plugged into computer but have been having issue when trying to charge it with the factory plug. If phone is hot i have to reboot or it says "not charging" in stats. Might not even be related but i found out the battery also has an nfc inside it. Maybe it's something in the connection or the chip in battery between the port and battery..? Because when hooked to computer it also tries to charge right?
*Android is upgrading...*
ok guys, first things first. YES i did search, i read threads for hours. So if your just gonna come to bash on me... get off it.
So i had a bad flash, oh no. Phone was stuck in a bootloop, got it to download mode and put it thru odin. Well odin said FAILED. now i can still get into DL mode but its no longer a bootloop, now its a lil picture of a phone linked to a computer when i turn it on.
SO heres the prob, i can get into DL mode, but odin refuses to recognize my phone. Ive tried other usb ports, other cords, unistalled and reinstalled odin and the drivers. USB debugging is off says aio toolbox. So what do i do now? any suggestions im not thinking of?
Any help is greatly appreciated and will b thanked. =)
Phone to PC screen still should be able to flash through.
Have you tried a different computer? One that your phone has never been in contact with?
What was the FAILED error when you tried to ODIN initially?
Can you get into recovery by chance?
i have tried a different computer, but not one it has never been on b4.
And toast, i actually dont know if i can get into recovery. Im about to look up how and try that
WhiteBoyAwesome said:
i have tried a different computer, but not one it has never been on b4.
And toast, i actually dont know if i can get into recovery. Im about to look up how and try that
Click to expand...
Click to collapse
Gingerbread bootloader uses this combo:
For Recovery - Lower Volume Key + Power Button
For Download - Upper Volume Key + Power Button
If you have Froyo bootloader:
For Recovery - Both Volume Keys + Power Button
For Download - Both Volume Keys and Connect USB Cable
alright, i can use the hardware buttons to get into download just fine. But when i try to get into recovery it only gives me the Phone -- ! -- Computer icon. ITs getting annoying lol
Ok. I didn't figure that would work, but it wasn't going to hurt anything to try do you have any friends with Macs? You could try it on one of them with Heimdall. That would be another option to try.
Also, check out this thread: http://forum.xda-developers.com/showthread.php?p=8149503
Read all the posts, there is some good stuff in there.
+1 on recommended thread. It sounds just like your issue. Definitely try the Heimdall AIO one click t959 for Windows.
sent from the depths of helly bean
nothin yet :/
Google eugenes froyo that does not brick, read the op carefully, because after you odin the tar file, you will have an error message, thats ok, odin eclair and you should pass.
Read it 10 times, you'll reboot in cwm with an error message, ok, reboot, download, eclair.
stupid question sorry, but do you have sdk platform tools installed?
im not sure. i downloaded something called sdk manager, but it closes the moment u open it.
SDK platform tools is a large program, But if your computer has recognized your phone up till now, you probly have the right drivers, by the way have you cleaned your usb port? toothbrush and an electronics cleaner or alcohol very lightly, never know.
ok guys. heres the update. I tried all the links you guys have kindly tossed my way. nothin. Im on a different computer even and downloaded the drivers, odin, toolbox, etc. The phone still isnt recognized. I Have no clue why, is the reason cause usb debugging is off? the only 2 screens i can get to r download and phone ! computer. Am i bricked for good??? =(
WhiteBoyAwesome said:
ok guys. heres the update. I tried all the links you guys have kindly tossed my way. nothin. Im on a different computer even and downloaded the drivers, odin, toolbox, etc. The phone still isnt recognized. I Have no clue why, is the reason cause usb debugging is off? the only 2 screens i can get to r download and phone ! computer. Am i bricked for good??? =(
Click to expand...
Click to collapse
You are putting your phone into download mode before using odin right? You must have your phone in download mode for odin to recognize it. I'm guessing you have done this but I wasn't sure after reading through this thread, hope you get up and running again.
Sent from my SGH-T959 using Tapatalk 2
iTz KeeFy said:
You are putting your phone into download mode before using odin right? You must have your phone in download mode for odin to recognize it. I'm guessing you have done this but I wasn't sure after reading through this thread, hope you get up and running again.
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
yep. tried multiple combos as well
Hey I think you should follow this..
1. Connect your phone with computer without battery
2. Press volume down and power button simantaniously for getting download mod
3. After 30 or 60 second pull back battery into phon with holding buttons
4. Odin ditect your device almost surely...
Thanks..
Sent from my GT-I5510 using xda premium
Ok, I just went through this over the past weekend with a spare Vibe that I have. Odin would not recognize it at all for my. I would here the Ding and then nothing. No yellow COM box, no driver installation, nothing.
Here is what I did:
First I went into Device Manager and with the phone plugged in (needs to be plugged in so you can see the yellow!), I uninstalled everything with Samsung's name tagged to it (including my SGS3 and SGS2 drivers).
Then I went here and downloaded and installed Heimdall (take note that you have to make sure that libusb-1.0 is correctly installed). There is an exe file in there (might be in the Heimdall thread here in the Vibe section), that allows you to update the drivers. That is where you would replace the Windows with libusb-1.0.
Then I plugged in my USB to PC and to phone and put it in Download mode. Nothing. So I left it plugged into the phone still but unplugged from PC and move ports. I have 3 ports and believe it or not, the one farthest from the power source/MB was the one that work. As soon as I plugged it in, I heard the Ding and saw the box pull up auto-installing the drivers.
After that, I went to Utilities in Heimdall to make sure detected. It was and I flashed Mr_Psycho's package (no pun intended ) via the normal Heimdall instructions.
Believe me, I have spent a ton of time on this and troubleshooted everything from dead USB to dead motherboard. It was a real PITA.
Edit:: If you need any of the files, Heimdall version or Drivers, just PM me and I will send them to you. You are not Bricked, just your PC's vision is clouded a bit.
woodrube i greatly appreciate the mass amount of help. i will try all the above as soon as im home and report back to u
alright, i deleted everything, reinstalled, tried heimdall still nothing. I am in download mode but laptop wont recognize anything. it says the correct drivers are installed but then says usb device not recognized, this is killing me as i need my phone imma post a video tonight of what im doing, hopefully someone sees im doing something wrong
Hi
New on here so sorry if I don't know to much
I have a Nexus 7 2012. Install Timurs kernel and Rom on my tablet and installed it in my car, and it worked great for months, then the other day it shut down. When I rebooted it, it gets stuck on the Google logo.
If I try boot into recovery it once again gets stuck at the Google Boot logo
I can get it into Fastboot mode but it wont connect to the PC. I am sure the Drivers are ok as I have another nexus 7 and i have today flashed a new rom using the WUGs Nexus Toolkit
Any Ideas anyone as at the moment I would class this as bricked as it wont boot, wont go into recovery and wont connect to the PC
Any advice would be hugely appreciated
Cheers
Aaron
aaronthew said:
Hi
New on here so sorry if I don't know to much
I have a Nexus 7 2012. Install Timurs kernel and Rom on my tablet and installed it in my car, and it worked great for months, then the other day it shut down. When I rebooted it, it gets stuck on the Google logo.
If I try boot into recovery it once again gets stuck at the Google Boot logo
I can get it into Fastboot mode but it wont connect to the PC. I am sure the Drivers are ok as I have another nexus 7 and i have today flashed a new rom using the WUGs Nexus Toolkit
Any Ideas anyone as at the moment I would class this as bricked as it wont boot, wont go into recovery and wont connect to the PC
Any advice would be hugely appreciated
Cheers
Aaron
Click to expand...
Click to collapse
You can't go into your recovery?
Install ADB and try to connect your Nexus to your PC and enter "adb devices". See if your tablet is recognized like that.
How to setup ADB
Do not use toolkits with Nexus devices.
cheers for the advice but nope no luck still wont connect
aaronthew said:
cheers for the advice but nope no luck still wont connect
Click to expand...
Click to collapse
When you plug your tab in, does it even attempt to load drivers and just fails or does it not even recognize that you plugged anything in? Make sure by checking the Device Manager as you plug / unplug. If it just doesn't load correctly, then attempt to load the Naked Universal Drivers manually and then you should be able to get things back on track at least with fastboot flashing the stock img files back to it. If the Device Manager doesn't change or show any differences when you plug in the tab, then that's a bad thing... If you can boot to the bootloader still, most likely it can be fixed. If it only boots to a black screen and when plugged in shows the APX driver, you're boned. That problem IS fixable, but only if you would have saved your blob.bin and wheelie blobs before it went down, which I am certain you didn't do as it is not a common procedure.
es0tericcha0s said:
When you plug your tab in, does it even attempt to load drivers and just fails or does it not even recognize that you plugged anything in? Make sure by checking the Device Manager as you plug / unplug. If it just doesn't load correctly, then attempt to load the Naked Universal Drivers manually and then you should be able to get things back on track at least with fastboot flashing the stock img files back to it. If the Device Manager doesn't change or show any differences when you plug in the tab, then that's a bad thing... If you can boot to the bootloader still, most likely it can be fixed. If it only boots to a black screen and when plugged in shows the APX driver, you're boned. That problem IS fixable, but only if you would have saved your blob.bin and wheelie blobs before it went down, which I am certain you didn't do as it is not a common procedure.
Click to expand...
Click to collapse
Hi
I can get to the bootloader screen and it says Fastboot mode on the tablet.
When i plug the tablet into the Pc, device manger does not refresh and the computer makes no acknowledgement at all when I plug the device in
aaronthew said:
Hi
I can get to the bootloader screen and it says Fastboot mode on the tablet.
When i plug the tablet into the Pc, device manger does not refresh and the computer makes no acknowledgement at all when I plug the device in
Click to expand...
Click to collapse
Hmm. Very odd. Typically if the bootloader is still there, the rest is easily solvable. What happens when you choose the recovery option from bootloader? Unfortunately you have to test some more things to eliminate the easy stuff. These include trying different cords, ports, and computers. If possible, see if you can try a Linux PC as well or at least a Live CD. If TWRP still loads at all and supports USB OTG, you might be able to load something from it as a long shot.
es0tericcha0s said:
Hmm. Very odd. Typically if the bootloader is still there, the rest is easily solvable. What happens when you choose the recovery option from bootloader? Unfortunately you have to test some more things to eliminate the easy stuff. These include trying different cords, ports, and computers. If possible, see if you can try a Linux PC as well or at least a Live CD. If TWRP still loads at all and supports USB OTG, you might be able to load something from it as a long shot.
Click to expand...
Click to collapse
if i choose recover, to gets stuck on the google screen
Tried different cables, Pc and PC ports no luck
I could try get linux on vm when i get home? never used it thou
Sucks man. Such a random thing and not typical of most Nexus issues. This is the only other option I can think of then: http://mobiletechvideos.mybigcommerce.com/asus-nexus-7-2012/ - Brick service. These guys are legit. They have a great reputation and I've personally used their services twice (different devices) and one was fixed while the other was a lost cause, but Josh was nice enough to refund some of the money since it didn't work. I'm guessing they would need to do what's called a JTAG service where they hook up (usually solder) a special cable to a specific port on the board and it kind of circumvents the other issues and reloads the OS back on.
Thanks for all you hep mate will prob give them a try
No problem. Good luck!
hi there,
recently I was using Meldrak's stock rom, my device went dead so I plugged it in to charge it, I went to use it and nothing happened.
I noticed that when I tried to turn it on, it would vibrate on, and then vibrate off straight away.
I can get into apx mode, so I thought I would try and use nvflash/wheelie to see if i could recover it, but on the first step of
"wheelie --blob blob.bin"
it comes up with error 3 receiving response from command.
any ideas on this? I've noticed people have said use a different nvflash and all that but it didn't seem to work for me.
I'm using win7.
I've installed the newest naked drivers
thank's, I think i got all the details.
(my girlfriend is going to kill me if I cant get this going)
addtional info:
as I have somewhat given up for now, my girlfriend has come in and tried to turn it on, my laptop has picked it up like normal, its come up as a portal media drive.
edit#2: somehow managed to get into fastboot, I am able to do the reboot command, so thats something, I think I might just keep putting up my progess, not sure how much further i'll get though.
edit#3: seems i can write with fastboot, but not making any difference, but when i go "fastboot reboot" computer is finding it as a mpt device but drivers have an error by the looks of it. heres a thought, could my screen be broken? id really kick myself if it was.
edit#4: so i just did the steps off http://forum.xda-developers.com/showthread.php?t=2800506 post #5, only did the fist part, only getting 1 vibration now, and computer is picking it up as a mpt device but still no screen.
just realised its not going into fastboot now. oh no......
malgora said:
hi there,
recently I was using Meldrak's stock rom, my device went dead so I plugged it in to charge it, I went to use it and nothing happened.
I noticed that when I tried to turn it on, it would vibrate on, and then vibrate off straight away.
I can get into apx mode, so I thought I would try and use nvflash/wheelie to see if i could recover it, but on the first step of
"wheelie --blob blob.bin"
it comes up with error 3 receiving response from command.
any ideas on this? I've noticed people have said use a different nvflash and all that but it didn't seem to work for me.
I'm using win7.
I've installed the newest naked drivers
thank's, I think i got all the details.
(my girlfriend is going to kill me if I cant get this going)
addtional info:
as I have somewhat given up for now, my girlfriend has come in and tried to turn it on, my laptop has picked it up like normal, its come up as a portal media drive.
edit#2: somehow managed to get into fastboot, I am able to do the reboot command, so thats something, I think I might just keep putting up my progess, not sure how much further i'll get though.
edit#3: seems i can write with fastboot, but not making any difference, but when i go "fastboot reboot" computer is finding it as a mpt device but drivers have an error by the looks of it. heres a thought, could my screen be broken? id really kick myself if it was.
edit#4: so i just did the steps off http://forum.xda-developers.com/showthread.php?t=2800506 post #5, only did the fist part, only getting 1 vibration now, and computer is picking it up as a mpt device but still no screen.
just realised its not going into fastboot now. oh no......
Click to expand...
Click to collapse
If you can fastboot with no display on, there might be some hardware defect.
As a last resort you can try following:
1. reset tab physically (put needle in little hole above hdmi slot)
2. unplug battery for 10 min.
3. fastboot another recovery.img
4. try the hdmi out to an extern screen (your tv f.i.)
das chaos said:
If you can fastboot with no display on, there might be some hardware defect.
As a last resort you can try following:
1. reset tab physically (put needle in little hole above hdmi slot)
2. unplug battery for 10 min.
3. fastboot another recovery.img
4. try the hdmi out to an extern screen (your tv f.i.)
Click to expand...
Click to collapse
Thanks for the reply, unfortunately it will not go into fastboot anymore, as many times as I tried it will only come up as android mpt device, my computer wont even pick that up right, (yellow triangle next to the icon in device manager) only other thing is apx mode but as ive stated i cant wheelie --blob blob.bin just returns error 3. might save and upgrade, to a newer tablet.
thanks for your suggestions though, much appreciated.