Can't enter fastboot, recovery nor OS. - OnePlus X Q&A, Help & Troubleshooting

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

Related

Odin won't detect i9100 in download mode after new kernel

Hi,
So I just purchased a Samsung Galaxy S II, and I've been trying a few different ROM's found on this site. The last thing I did was actually revert back to a stock Samsung Kernel and firmware. This worked fine, but it unrooted my device, which I knew would happen, but now I'm not able to root it again because when I put the device into download mode, ODIN, or better yet, my computer won't detect the device.
I have all the drivers installed, and I also deleted them all, and Kies, and started from scratch again after searching XDA for similar issues.
I don't believe this to be a driver issue, since I was able to root my device, and swap roms before I went back to the official kernel and firmware. I'm with Bell in Canada, so the versions I went back to were not the official Bell versions, since Samsung has not made them available.
I have a Mac, but I've been using Windows 7 and Odin under VMWare. I can connect my device to either OSX, or Windows 7 when the device is not in download mode, and everything works fine, and Odin detects the device (Not that that does any good of course)
When I connect the device under download mode, the Mac detects the device and asks me if I want to connect it to my Mac, or to Windows (As it should) but no matter which one I select, neither OS acknowledges the device after that point, where as when I'm not in Download mode, both OS's detect the device fine.
After all my troubleshooting with my computer based off of what I found online here, The only conclusion I have left is that there is something missing on the device that allows it to be found under download mode, but that aspect of all this is beyond my current skill level.
Anyone have any ideas?
Are you pressing the Volume Up button to continue in Download mode? Besides, Virtual machine isn't recommended I think.
Yes, Once the Custom ROM warning comes up, I press the Volume up button to continue.
That wasn't even necessary on the Stock Bell ROM. The warning didn't come up at all.
VM has been working fine up until now, so I don't think that's the problem, but I have been thinking of trying this on my old laptop that runs on windows if nothing else pans out.
Scott56 said:
Yes, Once the Custom ROM warning comes up, I press the Volume up button to continue.
That wasn't even necessary on the Stock Bell ROM. The warning didn't come up at all.
VM has been working fine up until now, so I don't think that's the problem, but I have been thinking of trying this on my old laptop that runs on windows if nothing else pans out.
Click to expand...
Click to collapse
Have you found anyway to Make Odin recognize to phone in download mode?? Im still struggling with that. my phone is on stock kernel and not rooted yet, ODIN finds it fine when the phone is on and USB Debugging is on, but once I put the phone on download mode it wont recognize it, I dont know why..
Could it be because of the ''SAMSUNG Mobile MTP Device'' driver failed to install correctly??
all other drivers are installed correctly.. I have tried to get the driver mentioned above to install correctly but it fails every time, with USB debugging on and off, i have wiped the phone and installed Kies and the drivers several times, Im clueless right.. anyone have any idea please help??
I myself am also suffering from this problem. However, USB seems to function fine while the phone is booted up or in recovery (For ADB). I'm wondering if necessary files may have become corrupted or deleted in reference to USB drivers (phone side mind you) that are used in download mode.
edit: It's also recognized in recovery mode.
Even if it can't be fixed I'd still like to understand why.
-Simply D
was looking for help on this and saw this thread, same problem too..
Connects to Odin and Kies fine when switched on "normally", can use USB mass storage mode Etc.
comes up with a USB device has malfunctioned message on PC when I connect USB cable when switched on and in download mode
EDIT:- just to add, if I try upgrading firmware via Kies it gets to the point where it switches the phone to download mode to upgrade it and has the same issue even with an official upgrade
Figuring download mode is outside the normal boot procedure, I hoped on an off chance that pulling my battery and sim for a few minutes would reset it. It did indeed. Download mode is now functional again, just to be certain I tested it right before pulling the battery to make sure it was still broken. And multiple flashes and reboots afterwards seem to confirm that it has returned to normal.
Anyone else who solves it with this method, please report back.
-Simply D
SimplyD said:
Figuring download mode is outside the normal boot procedure, I hoped on an off chance that pulling my battery and sim for a few minutes would reset it. It did indeed. Download mode is now functional again, just to be certain I tested it right before pulling the battery to make sure it was still broken. And multiple flashes and reboots afterwards seem to confirm that it has returned to normal.
Anyone else who solves it with this method, please report back.
-Simply D
Click to expand...
Click to collapse
Tried this and it didn't work for me :/ going to give it another try later, thanks for the suggestion either way

[Q] Install problems with NAND

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.

[Q] Huawei Vision (U8850) bricked

Hello,
I have probably bricked my Huawei Vision by rewriting boot image.
However, I can connect* it to PC and it sees my phone as "Huawei Handset" (same with Windows and Linux). But Windows misses its drivers (non-bricked phone worked); Linux seems to work. No OS can connect to it using default (downloaded) ADB, nor Fastboot, nor SoftwareUpdateTool.
Its PCI ID is 12d1:c002.
How could I reflash it? I would prefer the ways without disassembling the phone.
Thanks
----How to boot the phone, so you can connect it to PC:
1. turn off my phone completely (vol up + power for 10 seconds - release power for a seconds and repeat it once again)
2. prepare USB cable, so you can connect it in few seconds
3. hold vol down + power and after ~1s, connect USB cable (still hold vol down)
4. when Huawei logo appears, release both buttons - your phone is connected now
petoxxx said:
Hello,
I have probably bricked my Huawei Vision by rewriting boot image.
However, I can connect* it to PC and it sees my phone as "Huawei Handset" (same with Windows and Linux). But Windows misses its drivers (non-bricked phone worked); Linux seems to work. No OS can connect to it using default (downloaded) ADB, nor Fastboot, nor SoftwareUpdateTool.
Its PCI ID is 12d1:c002.
How could I reflash it? I would prefer the ways without disassembling the phone.
Thanks
----How to boot the phone, so you can connect it to PC:
1. turn off my phone completely (vol up + power for 10 seconds - release power for a seconds and repeat it once again)
2. prepare USB cable, so you can connect it in few seconds
3. hold vol down + power and after ~1s, connect USB cable (still hold vol down)
4. when Huawei logo appears, release both buttons - your phone is connected now
Click to expand...
Click to collapse
mine is not working i think mine is bricked completly
bricked my mobile...Help!!!!
I had installed the latest rooted russian firmware and unknowingly installed the ICS..Now my device stuck at boot and while connecting with sutlr error(cannot identify device) occurs..What to do:crying:???
sivakarthick said:
I had installed the latest rooted russian firmware and unknowingly installed the ICS..Now my device stuck at boot and while connecting with sutlr error(cannot identify device) occurs..What to do:crying:???
Click to expand...
Click to collapse
The thread called 'Problem with huawei vision' still seems to be active. You may want to try asking your question over there.
Huawei (u8850) unbricked
I just wanted to relate my experiences in de-bricking this U8850 phone.
I installed 'Apps_2.6.35.7-perf+root+CWM_recovery 5.0.2.8' (firmware.nb0) using SUT to get CWM, and then installed Danile's 4.1.2
Good as far as it goes, but i could not for the life of me reproduce his kernel (my kernels are always unreliable), so after many days of playing, i decided to take the phone back to stock to see if i could reproduce the huawei stock kernel as a base to work on.
The problem was, how do you revert to stock; the phone was no longer recognised by SUT?
So I took a stock .nbo file and extracted the content (some java extractor found with google) in the hope that I could create a CWM flashable zip of the stock firmware.. a bit of research later, and i thought i had got the gist, put boot.img and system.img into a zip with a modified script file, and voila... a bricked phone.
At this point, i had CWM, but if the phone booted, it showed a flash of blue screen (I didn't know these ran windows ), and back to huawei logo. Also I think i had to dismantle to disconnect battery to run CWM, as it's not available just on the volume-up-power restart.
So then I did more research, and came across QPST, Qualcom's tools. It seemed this should know something about the files i had extracted. I could not correlate everything in the extracted fileset with what QPST seemed to expect, but the first challenge was to get QPST and the phone talking. using various drivers, QPST would sometimes see it, sometimes not, but nothing good seemed to be coming from it. I returned to trying to get SUT to work on my brick; again, with some drivers it would connect, but a flash always resulted in Error 4000 - DEVICE_NOT_CONFIGURED.
Then I read somewhere that someone had found a driver change made SUT work, so i investigated drivers more.
What I found was that if i ran up CWM, I got two Huawei devices in XP for which I could not find drivers.
The devices showed up as VID_12D1&PID_1022&MI_00 and VID_12D1&PID_1022&MI_01.
I took the Huawei USB drivers folder, and copied the qcser.inf then changed entries under [QcomSerialPort] to match my VID/PID values.
(the two that had matching MI_ values).
On driver update, I had a serial port, plus something I'd not seen before - a USB storage device which contained the phone's partitions!!!
This certainly seemed promising... so into SUT again, same error 4000...
So the I tried QPST; and yes, it could see the phone. Scared to do anything to brick it further, I thought, ok, try some memory diagnostics.
On running the 'Memory Debug' tool, as soon as I tried to get a list, QPST said 'this phones in diagnostic mode, it must be in download mode to do memory diagnostics', but even better 'Do you want to set it into download mode now?'!!!!!
Yeah! click the button, and I see a screen I've only seen once before (and i don't know why last time), black, with a line added every few seconds... which from all my reading I know is a good sign.
OK, then I closed all QPST apps, and ran SUT.
This time, the firmware flashed no problem. Was a bit worried as boot time is long (but it was effectively 'first ever' boot for the phone).
I hope this helps someone else with this or another Qualcom based phone.
Basic lesson is:
If you see Error 4000, it may be that the phone is in diagnostic mode rather than download mode.
If you don't have drivers, or don't have the right drivers, check you VID and PID, and try putting them into the .inf file
QPST may have a simple use after all... to force a phone into download mode when SUT fails.
how to turn off huawei u8850 completely
hey,could you please help me.i am stuck on huawei logo.how can i turn off the phone completely.i cant remove the battery obviously.the above trick isnot working.plz.help me
bikeshrt said:
hey,could you please help me.i am stuck on huawei logo.how can i turn off the phone completely.i cant remove the battery obviously.the above trick isnot working.plz.help me
Click to expand...
Click to collapse
it's actually not difficult to remove the battery...
but i read somewhere the 'volume-up + power for five seconds' will hard restart, but re-press power immediately will then turn it off (not tested myself; the back of mine is already off at the moment.)
Anyone here interested in developing a 3.x kernel? seems other phones with msm8255 have successfully got one...
u8850 power off
btsimonh said:
but i read somewhere the 'volume-up + power for five seconds' will hard restart, but re-press power immediately will then turn it off (not tested myself; the back of mine is already off at the moment.)
Click to expand...
Click to collapse
now i have tried it, and no success.
However, what i have found to work - if your non-boot is actually booting the kernel, but failing to initialise the phone, then you can still use adb with it... I ran adb shell, and then used 'poweroff' to power off my phone, which then meant i could boot into CWM recovery....
i HAVE THE SAME PROBLEME? PLEASE CAN U HELP ME TO SOLVE IT BY GIVING ME DETAILS.
it is working, thank you bro
btsimonh said:
I just wanted to relate my experiences in de-bricking this U8850 phone.
I installed 'Apps_2.6.35.7-perf+root+CWM_recovery 5.0.2.8' (firmware.nb0) using SUT to get CWM, and then installed Danile's 4.1.2
Good as far as it goes, but i could not for the life of me reproduce his kernel (my kernels are always unreliable), so after many days of playing, i decided to take the phone back to stock to see if i could reproduce the huawei stock kernel as a base to work on.
The problem was, how do you revert to stock; the phone was no longer recognised by SUT?
So I took a stock .nbo file and extracted the content (some java extractor found with google) in the hope that I could create a CWM flashable zip of the stock firmware.. a bit of research later, and i thought i had got the gist, put boot.img and system.img into a zip with a modified script file, and voila... a bricked phone.
At this point, i had CWM, but if the phone booted, it showed a flash of blue screen (I didn't know these ran windows ), and back to huawei logo. Also I think i had to dismantle to disconnect battery to run CWM, as it's not available just on the volume-up-power restart.
So then I did more research, and came across QPST, Qualcom's tools. It seemed this should know something about the files i had extracted. I could not correlate everything in the extracted fileset with what QPST seemed to expect, but the first challenge was to get QPST and the phone talking. using various drivers, QPST would sometimes see it, sometimes not, but nothing good seemed to be coming from it. I returned to trying to get SUT to work on my brick; again, with some drivers it would connect, but a flash always resulted in Error 4000 - DEVICE_NOT_CONFIGURED.
Then I read somewhere that someone had found a driver change made SUT work, so i investigated drivers more.
What I found was that if i ran up CWM, I got two Huawei devices in XP for which I could not find drivers.
The devices showed up as VID_12D1&PID_1022&MI_00 and VID_12D1&PID_1022&MI_01.
I took the Huawei USB drivers folder, and copied the qcser.inf then changed entries under [QcomSerialPort] to match my VID/PID values.
(the two that had matching MI_ values).
On driver update, I had a serial port, plus something I'd not seen before - a USB storage device which contained the phone's partitions!!!
This certainly seemed promising... so into SUT again, same error 4000...
So the I tried QPST; and yes, it could see the phone. Scared to do anything to brick it further, I thought, ok, try some memory diagnostics.
On running the 'Memory Debug' tool, as soon as I tried to get a list, QPST said 'this phones in diagnostic mode, it must be in download mode to do memory diagnostics', but even better 'Do you want to set it into download mode now?'!!!!!
Yeah! click the button, and I see a screen I've only seen once before (and i don't know why last time), black, with a line added every few seconds... which from all my reading I know is a good sign.
OK, then I closed all QPST apps, and ran SUT.
This time, the firmware flashed no problem. Was a bit worried as boot time is long (but it was effectively 'first ever' boot for the phone).
I hope this helps someone else with this or another Qualcom based phone.
Basic lesson is:
If you see Error 4000, it may be that the phone is in diagnostic mode rather than download mode.
If you don't have drivers, or don't have the right drivers, check you VID and PID, and try putting them into the .inf file
QPST may have a simple use after all... to force a phone into download mode when SUT fails.
Click to expand...
Click to collapse
it is working thanks bro
Stock rom download plz.
btsimonh said:
I just wanted to relate my experiences in de-bricking this U8850 phone.
I installed 'Apps_2.6.35.7-perf+root+CWM_recovery 5.0.2.8' (firmware.nb0) using SUT to get CWM, and then installed Danile's 4.1.2
Good as far as it goes, but i could not for the life of me reproduce his kernel (my kernels are always unreliable), so after many days of playing, i decided to take the phone back to stock to see if i could reproduce the huawei stock kernel as a base to work on.
The problem was, how do you revert to stock; the phone was no longer recognised by SUT?
So I took a stock .nbo file and extracted the content (some java extractor found with google) in the hope that I could create a CWM flashable zip of the stock firmware.. a bit of research later, and i thought i had got the gist, put boot.img and system.img into a zip with a modified script file, and voila... a bricked phone.
At this point, i had CWM, but if the phone booted, it showed a flash of blue screen (I didn't know these ran windows ), and back to huawei logo. Also I think i had to dismantle to disconnect battery to run CWM, as it's not available just on the volume-up-power restart.
So then I did more research, and came across QPST, Qualcom's tools. It seemed this should know something about the files i had extracted. I could not correlate everything in the extracted fileset with what QPST seemed to expect, but the first challenge was to get QPST and the phone talking. using various drivers, QPST would sometimes see it, sometimes not, but nothing good seemed to be coming from it. I returned to trying to get SUT to work on my brick; again, with some drivers it would connect, but a flash always resulted in Error 4000 - DEVICE_NOT_CONFIGURED.
Then I read somewhere that someone had found a driver change made SUT work, so i investigated drivers more.
What I found was that if i ran up CWM, I got two Huawei devices in XP for which I could not find drivers.
The devices showed up as VID_12D1&PID_1022&MI_00 and VID_12D1&PID_1022&MI_01.
I took the Huawei USB drivers folder, and copied the qcser.inf then changed entries under [QcomSerialPort] to match my VID/PID values.
(the two that had matching MI_ values).
On driver update, I had a serial port, plus something I'd not seen before - a USB storage device which contained the phone's partitions!!!
This certainly seemed promising... so into SUT again, same error 4000...
So the I tried QPST; and yes, it could see the phone. Scared to do anything to brick it further, I thought, ok, try some memory diagnostics.
On running the 'Memory Debug' tool, as soon as I tried to get a list, QPST said 'this phones in diagnostic mode, it must be in download mode to do memory diagnostics', but even better 'Do you want to set it into download mode now?'!!!!!
Yeah! click the button, and I see a screen I've only seen once before (and i don't know why last time), black, with a line added every few seconds... which from all my reading I know is a good sign.
OK, then I closed all QPST apps, and ran SUT.
This time, the firmware flashed no problem. Was a bit worried as boot time is long (but it was effectively 'first ever' boot for the phone).
I hope this helps someone else with this or another Qualcom based phone.
Basic lesson is:
If you see Error 4000, it may be that the phone is in diagnostic mode rather than download mode.
If you don't have drivers, or don't have the right drivers, check you VID and PID, and try putting them into the .inf file
QPST may have a simple use after all... to force a phone into download mode when SUT fails.
Click to expand...
Click to collapse
HOLY GOD! F**K ME!!! I finally did it! THANKS A LOT, BRO! YOU'RE AWESOME!!!

[Q] Nexus wont boot

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!

Need help with bootloop -- A tricky bootloop.. Donation will be given!

Hi there peeps!
My Xperia Z2 has gone into a bootloop, with no recovery, no boot logo, not registering ADB / fastboot drivers anymore.. BUT.. the buttons seems to work, so i may reboot it some different ways. The only indication of life it got, is the red light when booting.
Someone want to tag team with me to find the solution?
Donation will be gived to a working solution
Best regards!
There is no solution for this atm. The best way to fix it is to send it to the service center.
kimocoder said:
Hi there peeps!
My Xperia Z2 has gone into a bootloop, with no recovery, no boot logo, not registering ADB / fastboot drivers anymore.. BUT.. the buttons seems to work, so i may reboot it some different ways. The only indication of life it got, is the red light when booting.
Someone want to tag team with me to find the solution?
Donation will be gived to a working solution
Best regards!
Click to expand...
Click to collapse
I may have a solution. Red light usually means it cannot boot the kernel.
I have a simple fix. Follow this guide and make sure to download the firmware of your exact model and current software version number.
When you get to this step, on the right side don't check anything under 'WIPE', leave them blank. And under 'EXCLUDE', check everything except 'KERNEL'. Leave Kernel blank and the rest under exclude check them.
Proceed and press 'volume down' and connect the usb cable at the same time. Let the flash finish and boot the phone back up. Let me know how it goes.
Thanks! I'm trying your solution now, but i dont think it works... none of the drivers are either so. Give me some hours, i will walkthrough here
I can say, it is NEARLY dead i would think, but there must be a way somehow..
Yeah, this will not work.. It gets stuck on "HOLD THE VOLUME DOWN + PLUG THE CABLE" and both ADB and Fastboot are missing so.. It won't do anything there. Holding the Volume UP + Power reboots (that works for some reason). And the orange reboot button in the charging is working but nothing that will help me i think.
kimocoder said:
Yeah, this will not work.. It gets stuck on "HOLD THE VOLUME DOWN + PLUG THE CABLE" and both ADB and Fastboot are missing so.. It won't do anything there. Holding the Volume UP + Power reboots (that works for some reason). And the orange reboot button in the charging is working but nothing that will help me i think.
Click to expand...
Click to collapse
When the device is connected in flash mode (USB + Vol down), go to device manager and see if the device is there (may be called 'Xperia Z2" or "Unknown Device", right click and go to properties and update drivers to this. Update me how it goes. I had the EXACT same issue and it took me some time to resolve, by solving the drivers issue you can flash the kernel again without losing data.
If that doesn't work, install these drivers: http://forum.xda-developers.com/showthread.php?t=2588979
Hi!
When my went to Bootloop the only thing that woked was using sony's Pc recovery tool.
sony's Pc recovery tool
Hope this helps you out
Try Software repair on the new Xperria Companion
http://support.sonymobile.com/global-en/xperiaz2/tools/xperia-companion/
Both Sony Companion and Sony Emma are not registering the devices, but after fiddling around with VOLUME UP, VOLUME DOWN and lots of trying, at some point the device manager finds a unknown device. "hiredantispammer" may got the solution, but i will try all posted solutions right away! Post update soon
1. On "VOLUME DOWN + PLUG" the Device Manager refreshes, and the Z2 got the "red light" -- but Device Manager does not show any connected devices nor drivers needed.
2. The Sony Companion does not find the device either.
But.. i was reading about some Windows 10 driver problems, so i will try switch to Windows 7 x32 to ensure the drivers are working correctly.
Another thought.. Is it some way to put a "update.zip" on a sdcard for force installation of new kernel or anything?
Yeah, the solution is right. Hopefully Win 7 solves your driver issues. I had to reformat my laptop and install Win10 again because of driver issues when I have the exact same issue as you. Hope you get your phone working again!
Sent from my D6503 using XDA-Developers mobile app
And no, there's no other safe way to reflash the kernel. Even with an unlocked bootloader, you need fastboot drivers.
This worked for me.
Grab your original cable and make sure the phone is charged to st least 80%.
Start the pc companion and the repair program.
Hold the down key and connect to the computer.
In around 20 minutes the phone is repaired
Hope this helps.
It is important to use proper cable and not any old thing laying around. Mine would not connect until i got the original one.
Ah, charge your device fully. Reboot Windows 10 in safe mode and disable driver signature. Install device drivers. Use Sony PC companion or flashtool to fully reflash the right firmware for you device. You are still able to turn it off and on, so it should work if you do it right.
Best to first flash just the kernel and see if it boots, if it doesn't since you have the firmware files, flash everything and don't wipe data.

Categories

Resources