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.
Related
not sure whats going on with my gtab....was surfing the net, battery was around 30% so I shut it off and put it on the charger. Came back about 15 minutes later to play on it. Hit the power button and the lock screen came on and then flashed red for a second and then black. Since then, I cant do anything...hit the power button, screen stays black...hold power and volume +, screen stays black...opened it up, disconnected the battery, hit the internal reset....screen stays black. hook it up to the PC and it recognizes the Gtab as tegra 2 drives, but I cant explore anything on either sd or internal. Trying to get to APX mode, but that isnt happening either....Is this thing dead?
ok...got it to NVFlash with the laptop...thats good. However, I cannot get the screen to come on. I can power the gtab on but the screen stays black...no 3 birds no nothing. any clues on bringing this back?
The cable to the LCD display might have come loose. Open it up and have a look around. Search for posts by user "aabbondanza" where he makes specific suggestions for this kind of problem.
thanks for the reply, I read all his posts and also reseated the cables....I dont know if something on the board got fried or the the screen is burnt out
rheller219 said:
I dont know if something on the board got fried or the the screen is burnt out
Click to expand...
Click to collapse
If you can set up adb (there are a couple of sticky threads on the board here for this--on Linux, you just need the adb binary and not the whole Android SDK--it might be the same on Windows), you can try going (blindly) into recovery mode with Power and Vol+, and then try to see if the system booted and if the kernel reported any errors.
Code:
C:\> [B]adb shell dmesg > dmesg.txt[/B]
Post the dmesg.txt file here.
You can also run this command--again while booting blind into the regular system--to get the Android system logs:
Code:
C:\> [B]adb logcat -v time > logcat.txt[/B]
Kill the adb after about 5 mins or so and post the logcat.txt. Collect the dmesg output before you collect the Android logs, though.
I havent done any adb stuff yet...i will try it and see if I can get some info
I cant get adb to find the device? All I am getting is NVIDIA Tegra 2 USB Device in the Device Manager. nothing under Other devices or Universal Serial Bus Controllers. After NVFlashing which works, I am unable to put the tablet in USB Debugging cause the screen dont come on...is this have something to do with it or does NVFlash turn USB Debugging on somehow? All I want to know is if the screen took a dump or something on the motherboard did...but I cant log anything with ADB currently cause the device is not found in ADB... anyone know what contacts to check with a voltmeter to see if I have power going to the screen atleast?
rheller219 said:
After NVFlashing which works, I am unable to put the tablet in USB Debugging cause the screen dont come on...is this have something to do with it or does NVFlash turn USB Debugging on somehow?
Click to expand...
Click to collapse
Most custom ROMs may have USB debugging enabled by default, and CWM always has it enabled. If Windows doesn't recognize the gTab, try Linux.
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.
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 Guys!
The last day I wiped my ADB sideload cache and factory reset my device.
After that, my OPX keeps rebooting and I was only able to enter fastboot mode (but the device isn't listed when i type: fastboot devices).
I've tried following the guide for hard bricked OPX but couldn't do it because i'm running linux, so i installed W7 into a virtual box.
The tool didn't work becouse i cant seem to allow installation of unsigned drivers in a virtualbox and i am running out of ideas.
On top of all that, the battery is drained and now i can't even enter fastboot. It just says "the battery is too low, charge for a while before power on!" and I can't charge it because it keeps rebooting in an interval of 3-4 seconds.
I have CyanogenMod 13 installed and since i factory reset it, i assume that debugging is not enabled.
Up until now, i was always able to figure something out when i scerwed my device up, but this time i have no clue what to do.
Could anyone here help me?
All help appreciated!.
Will it charge if you leave it in fastboot mode? I'm not sure how virtual windows works but normally you can press F8 on startup and select allow unsigned drivers.
First of all, you should charge the device, otherwise worse things could happen.. Can't you just keep it in charge when switched off?
After you reach a reasonable level of battery, you should be able to fix it: if properly set up, fastboot works very well on Linux and Mac also, so you don't need VirtualBox etc.
Maybe check your installation with other phones.
If everything ok, you should then flash both bootloader and sys using fastboot: be sure to download proper images (this especially goes for OS), ie recovery ones.
dr.prodigy said:
First of all, you should charge the device, otherwise worse things could happen.. Can't you just keep it in charge when switched off?
After you reach a reasonable level of battery, you should be able to fix it: if properly set up, fastboot works very well on Linux and Mac also, so you don't need VirtualBox etc.
Maybe check your installation with other phones.
If everything ok, you should then flash both bootloader and sys using fastboot: be sure to download proper images (this especially goes for OS), ie recovery ones.
Click to expand...
Click to collapse
The main problem right now it that i can't charge it. It turns on automatically when i so plug it in and then starts rebooting, so i can't even charge it to the point when i cant enter fastboot.
I'm still not sure about the state that is mentioned in the hard-brick guide, when i need to hold the volume up button for 10 seconds and then plug it in without letting go of the button. When i do that, it doesn't turn on, but also doesn't charge.
Whew.. Bad thing :-S
Honestly, this goes out of my knowledge: looks something related more to onyx itself than android internals..
If you can't find a special button procedure to stop the bootloader and start charge, I fear you'll need to have it serviced...
But before giving up I'd suggest you to wait for some more valuable opinions..
dr.prodigy said:
Whew.. Bad thing :-S
Honestly, this goes out of my knowledge: looks something related more to onyx itself than android internals..
If you can't find a special button procedure to stop the bootloader and start charge, I fear you'll need to have it serviced...
But before giving up I'd suggest you to wait for some more valuable opinions..
Click to expand...
Click to collapse
Thank you nonetheless!
I've managed to succesefully run through the unbrick guide and managed to repair it.
Okay I read sth on unbricking.
I found that win xp is the best option for driver compatibility (no surprises here, Win7+ are far more restrictive on unsigned ones: Ms politics) ..
So find an original Ms xp setup iso (a home would suffice, pro is better.. Still an optimal OS IMHO.. So sad it's been abandoned) and install it on VirtualBox.. It should be able to bind to your onyx via USB (warn: this is not automatic: you have to enable usb bind from VM lower icons - warn2: you can do it only with the device attached).
VirtualBox virtual HW is very well supported in xp with its guest additions (even direct3d works fine, for instance), so you shouldn't have problems with onyx drivers.
If you can start the phone in "unbrick mode" and link it to Xp, it should work I think ..
Otherwise prepare yourself to format your beloved Pc
Hi all,
I wonder if somebody could help me.
At the moment I have a Z5 compact with a broken screen (totally black) and touch. I know it still can boot, because it responds to my fingerprint when booted up. However, it does respond to my finger, but still needs a patern on first boot, which I cannot do on account of the broken touch screen. Also, my computer detects the phone.
I want to access my data, but for that I would have to use the onscreen menu which pops up when I connect the phone with usb. That's impossible.
I looked around on the internet and it is possible to remotely control the screen or access via adb. However, for that I either need to install some app on the phone, enable usb-debugging or authorise access via adb. All of those are impossible.
My phone has un unlocked bootloader and is rooted, so as a last resort I've tried to flash a modified kernel to enable usb debugging by default. This fails. Probably because I make some mistake in modifying the kernel, but I don't know. There's not a lot of response from my phone, as you understand ... Besides, I've absolutely no experience modding myself.
Anybody any idea, please?
So I just fixed the same issue you're having this week. It required opening up the phone.
Basically the ribbon cable that connects the screen to the motherboard had become unseated and needed to be plugged back in for me.
The Z5C isn't the easiest phone to take apart but it's not that difficult either. Just requires some basic tools (Hair dryer, tweezers and some precision screw drivers). There's a bunch of videos showing you how on ifixit or youtube. You just have to go all the way to the part where they flip over the motherboard and unplug the two ribbon cables, one of those two will be the culprit.
This is the first and only phone I've taken apart so any amateur can do this.
Boot to recovery and connect your phone to PC
Nutchos said:
So I just fixed the same issue you're having this week. It required opening up the phone.
Basically the ribbon cable that connects the screen to the motherboard had become unseated and needed to be plugged back in for me.
Click to expand...
Click to collapse
Yes, actually I've had problems with a broken backlight before and opening the phone and re-adjusting the cable solved that. Not in this case however. Thanks for your suggestion, anyways.
mlleemiles said:
Boot to recovery and connect your phone to PC
Click to expand...
Click to collapse
Would recovery provide me with some way to enter my pattern via a PC, e.g. with ADB?
Actually, I'm not sure I had any recovery installed at all. I've tried this before and just tried it again. I press the on/off-button while holding volume down. After that no response whatsoever. My computer does not see any device when connected. I suppose my recovery does not work properly, but without screen I can't be certain.
mlleemiles, you are a _hero_!
After reading your post I decided to try flashing another recovery to try if that might work. Now I can access my files without ever having entered any pattern .
Nevermind that it turns out my files weren't encrypted and I thought they were.
If anyone has a similar problem in the future, this is what worked for me:
My exact situation:
- My phone runs a stock rom (downloaded from XperiCheck) with version 32.4.A.1.54. When my phone was still running ok I had the bootloader unlocked and my device rooted with Rootkernel.
Working solution:
- I downloaded Twrp, version 3.2.1, from this page:
https://forum.xda-developers.com/z5-compact/development/twrp-twrp-3-2-1-z5-compact-t3748952
- Shut down my phone by disconnecting the battery and reconnecting it again
- Started my phone in fastboot mode and flashed recovery to my phone with:
Code:
fastboot flash recovery recovery_suzuran_220218_2.img
- Booted my phone in recovery with volume down + on/off-button.
- Connected my phone to my PC, et voila.
Turns out I can also access my phone with ADB as root, so after backing up the entire internal memory, I might try to get some remote screen tool working.
So thanks for the help and if I find something interesting and new, I'll post that too.
Small update:
After successfully flashing Twrp I backed up the internal memory, so must of the important stuff was safe by then.
However, it turned out that my phone now wouldn't boot into anything other then Twrp. I decided to flash my rom again. First I installed my apb keys using Twrp:
Code:
adb push adbkey.pub /data/misc/adb/adb_keys
It turned out I already had usb debugging enabled.
I then flashed my original firmware again, and connected with adb. This time it connected correctly, without me having to click any dialogue on my phone. I fiddled with several remote control Android tools most of which didn't work. Finally, it turned out Vysor does exactly what I want to do. It is a bit unstable, but workable.
Anyways, I've finally managed to copy all the stuff I wanted from my phone.