Apologies if something similar has already been posted on here already. I have had a look, but can't seem to find anything.
I was trying to root my oneplus one this evening, and was following a very useful link here....
https://forums.oneplus.net/threads/like-a-boss-how-to-root-your-oneplus-one.58493/
....and got to the bit that says "sudo fastboot oem unlock" - waited a minute, and the phone rebooted showing the android and 1+ logo. But before anything else happens it turns itself off, then back on again. And continues to do this indefinitely. I can get it into fastboot mode, but not recovery. When it is in fastboot mode the pc doesn't recognise it. Something obviously isn't right, but I'm not sure what. I'm guessing something is possibly corrupt.
What I think I need to do is firstly, get the pc to recognise the phone somehow. Secondly, install a recovery on to it and thirdly, flash a rom. I've been scratching my head all night trying to work out how to get the phone recognised, and Googling like a teenager who's just discovered porn is available on the Internet.
Is there anybody out there who is familiar with Linux who can possibly walk me through what I need to get my phone working again?
Thanks for taking the time to read this, and for any help that may be offered.
XDA Visitor said:
Apologies if something similar has already been posted on here already. I have had a look, but can't seem to find anything.
I was trying to root my oneplus one this evening, and was following a very useful link here....
https://forums.oneplus.net/threads/like-a-boss-how-to-root-your-oneplus-one.58493/
....and got to the bit that says "sudo fastboot oem unlock" - waited a minute, and the phone rebooted showing the android and 1+ logo. But before anything else happens it turns itself off, then back on again. And continues to do this indefinitely. I can get it into fastboot mode, but not recovery. When it is in fastboot mode the pc doesn't recognise it. Something obviously isn't right, but I'm not sure what. I'm guessing something is possibly corrupt.
What I think I need to do is firstly, get the pc to recognise the phone somehow. Secondly, install a recovery on to it and thirdly, flash a rom. I've been scratching my head all night trying to work out how to get the phone recognised, and Googling like a teenager who's just discovered porn is available on the Internet.
Is there anybody out there who is familiar with Linux who can possibly walk me through what I need to get my phone working again?
Thanks for taking the time to read this, and for any help that may be offered.
Click to expand...
Click to collapse
Hi and welcome to XDA.
Your device has a dedicated forum here:
OnePlus One > ONE Q&A, Help & Troubleshooting
All questions regarding your device belong in the forum linked above. You'll need to create an account first so you can post in the main forums.
Related
I really need some serious help and advice. Could anybody who is experienced it this filed please help me, or even put me in the right direction.
I am stuck in the qualcomm download mode with my device as QHSUSB_Dloader9008.
Yes it is a hard brick and 99% of the google searches have just confused me.
So here is the story.
I was developing for the Lg Vista D631, and trying to port a rom from the v10lte tablet due to the exact same architecture. The only main difference was the screen size.
Anyhow i was using fastboot to mess arount with the LG Security Error but nothing worked.
I didnt find out that much. So i just flashed back stock and then restored from cwm.
Well i went back to fastboot to try some more and i typed fastboot erase aboot, all went well. Then as i was in the middle of typing fastboot flash aboot my dang phone battery fell out my phone. And this is what i recieved... It Took it off my cmd prompt screen, i now have a nice crack in the screen, and a wonderful bricked phone....
It read up as Android Net USB, and it also came up as a removable disk with 64mb free on it. so i looked and i looked for something just to flash the aboot partiton back to the phone. But nothing came up. I even tried win32 imager.
I googled jtag and read that there are test points which would i could short to reset the devices bootloader to the wualcomm safe bootloader to flash the emmc chip and partition table back to stock. Which would thus repair the partition and open up recovery and or download mode.
I attempted to trace the circut to find out what point to short' and yea i even tried a few which only reset the phone. So i said screw it and formatted the removable disk....... And bam my pc detected a new device and installed the qhsusb dload9008 driver.
So now im in qpst fail safe download mode, i have it set to com41, and qpst detects it too.
And now th issue and question at hand.. I need the files to flash an msm8296. As the mbn, hex, and what nots are all not working with me. Do
When i try to use eMMC downloader I just kept getting the same response from qpst 4.0.2.
"Download failed could not communicate with flash programmer"
then in software download i keep recieving that the hex file is invalid, and could not detect the hex scrambling method. The file is invalid.
I have the lg d631 and have many unofficial kdz files i compiled. I could use the vs88010b for any other ones needed too. As i found out which ones are compatible through my testing phase.
When thia gets fixed though, the development for this phone will skyrocket, as anything will be possible.
So i am stuck. I messed up. And need to fix my mistake.
djacks222 said:
I really need some serious help and advice. Could anybody who is experienced it this filed please help me, or even put me in the right direction.
I am stuck in the qualcomm download mode with my device as QHSUSB_Dloader9008.
Yes it is a hard brick and 99% of the google searches have just confused me.
So here is the story.
I was developing for the Lg Vista D631, and trying to port a rom from the v10lte tablet due to the exact same architecture. The only main difference was the screen size.
Anyhow i was using fastboot to mess arount with the LG Security Error but nothing worked.
I didnt find out that much. So i just flashed back stock and then restored from cwm.
Well i went back to fastboot to try some more and i typed fastboot erase aboot, all went well. Then as i was in the middle of typing fastboot flash aboot my dang phone battery fell out my phone. And this is what i recieved... It Took it off my cmd prompt screen, i now have a nice crack in the screen, and a wonderful bricked phone....
It read up as Android Net USB, and it also came up as a removable disk with 64mb free on it. so i looked and i looked for something just to flash the aboot partiton back to the phone. But nothing came up. I even tried win32 imager.
I googled jtag and read that there are test points which would i could short to reset the devices bootloader to the wualcomm safe bootloader to flash the emmc chip and partition table back to stock. Which would thus repair the partition and open up recovery and or download mode.
I attempted to trace the circut to find out what point to short' and yea i even tried a few which only reset the phone. So i said screw it and formatted the removable disk....... And bam my pc detected a new device and installed the qhsusb dload9008 driver.
So now im in qpst fail safe download mode, i have it set to com41, and qpst detects it too.
And now th issue and question at hand.. I need the files to flash an msm8296. As the mbn, hex, and what nots are all not working with me. Do
When i try to use eMMC downloader I just kept getting the same response from qpst 4.0.2.
"Download failed could not communicate with flash programmer"
then in software download i keep recieving that the hex file is invalid, and could not detect the hex scrambling method. The file is invalid.
I have the lg d631 and have many unofficial kdz files i compiled. I could use the vs88010b for any other ones needed too. As i found out which ones are compatible through my testing phase.
When thia gets fixed though, the development for this phone will skyrocket, as anything will be possible.
So i am stuck. I messed up. And need to fix my mistake.
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
We cannot provide technical support nor can other members reply to your posts here on XDA Assist. There is no forum specifically for the LG Vista at this time but you may want to ask your question with all relevant details in the friendly general Android Q&A, Help & Troubleshooting forum at http://forum.xda-developers.com/android/help where you have already posted several times. Since your device is relatively uncommon, please be patient and give the experts plenty of time to respond. I also see a number of references to your model from a site search at http://forum.xda-developers.com/sitesearch.php?q=lg vista which might be worth reviewing.
Good luck!
This thread is closed.
I have a Xperia S running cm 12.1 with unlocked bootloaders TWRP installed and i tried to partition my SD card [http://forum.xda-developers.com/showthread.php?t=2584759] but clearly something went wrong and now the phone wont boot. I made a lot of research and tried everything but all the guides require to be able to boot into flashmode . My phone is dead the only sign of life is a red led when its charging which after some hours of charge will shut off. When the light is off and the phone connected on PC, the PC can recognize the device on unspecified devices (QHSUSB_DLOAD). i have installed all the needed drivers from Sony, google drivers from sdk, and adb drivers(adb wont see the device and i tried everything to do so, but nothing seem to work). I got a market for android on my pc called mobogenie that when i connect the phone it detects that a phone is connected but wont see what phone.The hardware reset buttons work but its useless in the current position. Concluding, the phone is bricked and wont open in fastboot-flashboot-bootloader-TWRP, its recognized as a device but not as "Xperia s" i got all the drivers and i want to flash the original firmware (already downloaded) to fix it. A possible problem is that the partition table is destroyed and after the flash it will hopefully be restored. The problem is not on the hardware but on software. I tried to trigger the download mode with the Samsung way (USB jig, 300k ohm ) but nothing happened as expected. Every solution i found required flash mode which is not accessible at the moment and i tried lots of things to go into fastboot(ever the rubber band trick,remove the battery etc). PLEASE help i dont know what to do, please help me flash it (i already got flashtool, Emma) or anohter solution. Thanks for the help in advance. (its my first thread in the forum, i hope to post it on the right section, i posted it here because i need the assistance of the developers i guess)
Hello,
Welcome to XDA.
The XDA Assist forum isn't what you think it is. We merely assist by helping to point users with issues in the right direction for their issue.
Try posting your question in the forum linked below.
http://forum.xda-developers.com/xperia-s/help?nocache=1&z=2025285740382969
The experts there may be able to help.
Register an XDA account to post and reply in the forums.
Hello friends,
You are my last resort, before I have to throw the device in the trash.
The device has not been hacked, has not been flashed, and has not been rotated.
I got up in the morning and saw the device stuck on this screen.
i tried to reboot the fastboot. its rebooting and coming back to this screen.
allso tried to replace battery, nothing work
The computer does not recognize it.
Attaching photo.
Thank in advance
yoad
yoadfe said:
Hello friends, You are my last resort, before I have to throw the device in the trash..........
Click to expand...
Click to collapse
I don't have this device myself but, I believe that one or both of the following threads should be helpful for what you are looking for that's specific to your device...
https://forum.xda-developers.com/showthread.php?t=3363040
https://forum.xda-developers.com/showthread.php?t=3363047
... Just be sure to follow the instructions provided on the first post (aka OP) and, if available, the following posts as well.
Don't be afraid to ask for some member guidance within one of them too.
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
thank you so much
yoadfe said:
thank you so much
Click to expand...
Click to collapse
i will ask here too
is there any way to rescue my phone from this?
my phone jsut starts into fastboot as soon as it turns on, even when i plug in the charging cable, it goes into fastboot in a second
i tried the adb method, instaleld it all, used the fastboot tools for "fastboot reboot", nothing
i used fastboot continue, nothing
i tried fastboot oem unlock, not recognised
the recovery mode for factory reset is working, but since i have seen in a german forum that this is not helping and i rather not loose my data because of the 2fa apps, i wont do that just now
i tried it all now but absolutely nothing works
i didnt enable the developer options in the 4 years i have that phone now, and i cant unlock it, even tho i got the unlock.bin from LG and everything
is there any solution? or is this phone now bricked and i can throw it against a wall out of frustration?
I have same problem, any someone can help me???
.
zeroiron said:
Hey guys!
i'm a bloody noob.
i never did something like unbricking my phone or wiping it or flashing it. It was my first time doing something like this because i just hate stock roms nowadays.
to unlocking the bootloader on my phone was no problem. but the problem was, that i updated my phone to adroid 11 and all the files i found in the past (half year ago) was for android 10, i think.
BUT I DIDN'T KNEW THAT BEFORE! I didn't knew that it would cause problems or that i had to be cautions about that.
Whatever. I tried to follow the instructions on this site: https://wiki.lineageos.org/devices/guacamole/upgrade
the twrp site i used was: https://eu.dl.twrp.me/guacamole/
Is the data "https://eu.dl.twrp.me/guacamole/twrp-3.6.0_11-0-guacamole.img.html" from 2021-11-22 know for adroid 11?
Because half year ago, i think, this all didn't work because there was no twrp for adroid 11 outside.
to be honest i don't know if i tried to install something else too in the past. i don't remember anymore.
I stuck half year ago on this bootloop problem. and i didn't worked again on this phone. i thought i could just wait for a new data for android 11 and try it later again.
Later is today but i made i worse!
I downloaded from this site https://download.lineageos.org/guacamole the file:
lineage-18.1-20220227-recovery-guacamole.img
after the command 'fastboot flash boot xxx.img' i reboot my phone.
Now my phone is displaying :
qualcomm crashdump mode
dm-verity device corrupted force dump
kernel-restart
what can i do now?
If i press the sound buttons + off-button i come the the boot screen which says:
blablabla
internetsite
press power button to pause boot
but this display won't stay long enough. after few seconds it's again on this crashdump mode
edit: i think i wiped in the past the whole os. And now? What should i do?
On this MSM Tool my phone isn't recognized. even with newest driver or other cable.
What should i do know? Is my phone lost now?
If some can help me please write exactly down what i should click / download etc.
If someone can german here and knows help, please help me in german. but don't have to. i'm glad if anyone can help me.
Click to expand...
Click to collapse
From what I can gather from your details I would try to get the MSM tool to work, it sounds like a driver issue, just make sure you uninstall previous driver first then go here
https://www.getdroidtips.com/download-qualcomm-qdloader-hs-usb-driver/
and get latest driver , follow all instructions,, also make sure your PC is installing all the optional drivers in the windows update section while your phone is connected to the PC, hth,, good luck
Hello to all,
I apologize in advance for this message.
I mistakenly bricked my phone,
It was running WW-18.0840.2201.226 (Android 11).
I'm not sure if I'm going to be able to use it again, but I'm sure I'll be able to use it again in the future.
The recovery mode does not work anymore. It remains stuck on the logo.
Concerning the device manager :
In Bootloader, nothing is detected
When I test the recovery mode, it detects 'Android Composite ADB interface'.
However, the ADB commands do not work (Unauthaurized)
This is a call for help, I don't know which tutorial to look at to help me.
Do I need to get a Deep Flash Cable to restore the phone?
Excuse my English, I'm French ^^'
Hi, I'm not sure, but I think you will have to delete this POST... It doesn't respect the forum rules... That said, you can follow this link for your problem. https://forum.xda-developers.com/t/...to-unlock-bootloader-to-modify-country-cn-to- ww.4353865/não lido
Hi Rico,
If I have to delete the post I will do it, it's not a problem.
Do you think I can put this post in the topic you gave me?
I had come across it in my research but I didn't know if it needed a Deep Flash Cable
I didn't know that my problem was similar to the one in the post because I don't have a 9008 mode
B.
Balmyr said:
Hi Rico,
If I have to delete the post I will do it, it's not a problem.
Do you think I can put this post in the topic you gave me?
I had come across it in my research but I didn't know if it needed a Deep Flash Cable
I didn't know that my problem was similar to the one in the post because I don't have a 9008 mode
B.
Click to expand...
Click to collapse
There is nothing wrong with your post at all.
Do you have access to see and send Fastboot commands to the phone when on the bootloader screen? You need to get that right first and get your driver on your PC sorted. Forget ADB, that's not going to help you here.
Once you have sorted the above, doing a RAW flash following one of the guides you can find on this form with a rom version that matches your device should get you back on track.
At this stage you shouldn't need EDL or a deep flash cable before exploring the above option.
Good luck.
Hello Andrologic,
Thanks for your reply
I only have access to the Bootloader with 'Start / Restart Bootloader / Recovery Mode / Power Off'.
I bought a Deep Cable, this one detects me when I connect it to the pc, previously my other cables did not want it
So I can indeed use the Fastboot commands whereas before I couldn't
Andrologic said:
There is nothing wrong with your post at all.
Do you have access to see and send Fastboot commands to the phone when on the bootloader screen? You need to get that right first and get your driver on your PC sorted. Forget ADB, that's not going to help you here.
Once you have sorted the above, doing a RAW flash following one of the guides you can find on this form with a rom version that matches your device should get you back on track.
At this stage you shouldn't need EDL or a deep flash cable before exploring the above option.
Good luck.
Click to expand...
Click to collapse
Thank you very much Andrologic!
The phone works like magic again, I can't believe it T_T
When I should do the updates, should I reflash the phone?
It doesn't offer me any new ones even though I'm on Android 11
B.
Balmyr said:
Thank you very much Andrologic!
The phone works like magic again, I can't believe it T_T
When I should do the updates, should I reflash the phone?
It doesn't offer me any new ones even though I'm on Android 11
B.
Click to expand...
Click to collapse
Nice. No, I would suggest updating the conventional way, i.e download ROM for ASUS and let the device pick it up and flash it. If you have TWRP installed, you can flash from there too, but there is no need for that unless the first method is not working