BRICKED, assistance needed please - ONE Q&A, Help & Troubleshooting

Well I've been playing around with ROMs, and I screwed up. Ended up formating all aspects, but now adb is not recognizing the device. I have tried on two different machines, OPO will load into fastboot, but not been seen through ADB. I can boot into TWRP, but the internal storage does not mount in order to trasnfer a ROM and flash. Any ideas would be great, I don't even mind going back to stock. However with ADB not finding the device now sure how that can be done.
Thanks in advance,
Squeeky

Refresh the stock image's trough fastboot that should do the trick
---------- Post added at 08:43 PM ---------- Previous post was at 08:42 PM ----------
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541

I was attempting to do so, however when I enter fastboot. ADB does not recognize the device as connected, in reading the tutorials, it gets stuck waiting for device as it's no recognized.

Have you got the Google fastboot and adb drivers? If so have you tried connecting your phone and going to device manager>find your device, it could be listed as A0001 or OnePlus One and you should right click it>update device driver>and choose browse and pick the Google adb driver, it should let you. After this, you need to download the CM11S fastboot zip from here: http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH38R-bacon-signed-fastboot.zip and extract it, open up the file and double click flashall.bat. Hope this helps in some way.

Squeeky said:
I was attempting to do so, however when I enter fastboot. ADB does not recognize the device as connected, in reading the tutorials, it gets stuck waiting for device as it's no recognized.
Click to expand...
Click to collapse
Adb doesn't work in fastboot, only fastboot does. Are you using an adb command or a fastboot command?
Transmitted via Bacon

timmaaa said:
Adb doesn't work in fastboot, only fastboot does. Are you using an adb command or a fastboot command?
Transmitted via Bacon
Click to expand...
Click to collapse
Yes, forgot about that. Make sure you use a command like fastboot flash in fastboot and not adb flash whatever

Squeeky said:
Well I've been playing around with ROMs, and I screwed up. Ended up formating all aspects, but now adb is not recognizing the device. I have tried on two different machines, OPO will load into fastboot, but not been seen through ADB. I can boot into TWRP, but the internal storage does not mount in order to trasnfer a ROM and flash. Any ideas would be great, I don't even mind going back to stock. However with ADB not finding the device now sure how that can be done.
Thanks in advance,
Squeeky
Click to expand...
Click to collapse
Follow this guide and it should work.
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
As others have stated, make sure you have the proper drivers.
Good luck, I had mine bricked last weekend and was able to revive it following the guide above.

Working
Thank you everyone, got it working through fsatboot. Restored my Madhi rom and back up an running,

Related

Can't load fastboot??

I'm trying to get into fastboot
reboot while holding vol down
select the USB icon and press vol up
but I am stuck at "Starting Fastboot USB download protocol"
am i doing something wrong?
xdeslitx said:
I'm trying to get into fastboot
reboot while holding vol down
select the USB icon and press vol up
but I am stuck at "Starting Fastboot USB download protocol"
am i doing something wrong?
Click to expand...
Click to collapse
No you are doing it right. THAT IS IS FASTBOOT. If you run the fastboot commands from your pc you will see it working on the pc.
xdeslitx said:
I'm trying to get into fastboot
reboot while holding vol down
select the USB icon and press vol up
but I am stuck at "Starting Fastboot USB download protocol"
am i doing something wrong?
Click to expand...
Click to collapse
sbdags said:
No you are doing it right. THAT IS IS FASTBOOT. If you run the fastboot commands from your pc you will see it working on the pc.
Click to expand...
Click to collapse
The above is correct, you are in fastboot if you see this (similar to download mode on samsung devices for use with ODIN).
Be sure to add path to environmental variables so that you can use fastboot commands at prompt (if in NT (windows) environment)
sbdags said:
No you are doing it right. THAT IS IS FASTBOOT. If you run the fastboot commands from your pc you will see it working on the pc.
Click to expand...
Click to collapse
i tried running the command " fastboot devices" and it doesnt see my tf700
i have all drivers loaded
Poser said:
The above is correct, you are in fastboot if you see this (similar to download mode on samsung devices for use with ODIN).
Be sure to add path to environmental variables so that you can use fastboot commands at prompt (if in NT (windows) environment)
Click to expand...
Click to collapse
i added the path to environmental variables.
Fastboot works fine for me.
Suggest you go over to the nvflash thread and download the windows drivers.
---------- Post added at 07:54 PM ---------- Previous post was at 07:52 PM ----------
xdeslitx said:
i tried running the command " fastboot devices" and it doesnt see my tf700
i have all drivers loaded
Click to expand...
Click to collapse
Isn't that adb commands you are trying to run. I.e., adb devices. I think you are confusing fastboot.
What are you trying to do?
sbdags said:
Fastboot works fine for me.
Suggest you go over to the nvflash thread and download the windows drivers.
---------- Post added at 07:54 PM ---------- Previous post was at 07:52 PM ----------
Isn't that adb commands you are trying to run. I.e., adb devices. I think you are confusing fastboot.
What are you trying to do?
Click to expand...
Click to collapse
fastboot devices is also a fastboot command from what i understand...i was trying to run that command to see if the computer can even see my tablet in fastboot...which it doesnt.
and i actually did get the drivers from the nvflash thread because that's what i am trying to accomplish
what does your tablet look like when you are in fastboot mode?
because i am doubting the fact that mine is even in that mode...i get the feeling that it gets stuck when trying to load fastboot
xdeslitx said:
fastboot devices is also a fastboot command from what i understand...i was trying to run that command to see if the computer can even see my tablet in fastboot...which it doesnt.
and i actually did get the drivers from the nvflash thread because that's what i am trying to accomplish
what does your tablet look like when you are in fastboot mode?
because i am doubting the fact that mine is even in that mode...i get the feeling that it gets stuck when trying to load fastboot
Click to expand...
Click to collapse
It just says starting Fastboot mode. It never changes from that.
im going to try and uninstall/reinstall the drivers to see if thatll work
finally got it to work...had to reload my drivers
haha so i did the whole nvflash thing but i dont really know how it works
all i know is that itll keep me from bricking my tf700
xdeslitx said:
finally got it to work...had to reload my drivers
haha so i did the whole nvflash thing but i dont really know how it works
all i know is that itll keep me from bricking my tf700
Click to expand...
Click to collapse
You can still brick your device but it's 100% recoverable, at least if it's not a hardware failure. Just make sure to keep your backup files safe.
Pretoriano80 said:
You can still brick your device but it's 100% recoverable, at least if it's not a hardware failure. Just make sure to keep your backup files safe.
Click to expand...
Click to collapse
are there any instructions on how to recover using these files in case of brick?
i didnt see any on the thread under development
xdeslitx said:
are there any instructions on how to recover using these files in case of brick?
i didnt see any on the thread under development
Click to expand...
Click to collapse
There's no guide so far, but i'm sure you would get some help from xda users when needed.
cool thanks for the replies
I'm stuck at fastboot mode with my TF700. Windows XP recognizes my device but the command "fastboot devices" doesn't show up my TF700. I tried to reinstall drivers from univeral naked drivers package 0.7 with success - tried it three times. Bootet up TF700 in fastboot mode but still fastboot doesn't see my device.
Has anyone an idea what I can do? I tried it also in my virtual linux machine without succes. I want to flash new CWM recovery over old TWRP recovery to update to JB and after this to get proprietary files needed to build CM10 from sources.
As I understand, without fastboot, I can't update my bootloader to JB. Not a nice device...
thunderger said:
I'm stuck at fastboot mode with my TF700. Windows XP recognizes my device but the command "fastboot devices" doesn't show up my TF700. I tried to reinstall drivers from univeral naked drivers package 0.7 with success - tried it three times. Bootet up TF700 in fastboot mode but still fastboot doesn't see my device.
Has anyone an idea what I can do? I tried it also in my virtual linux machine without succes. I want to flash new CWM recovery over old TWRP recovery to update to JB and after this to get proprietary files needed to build CM10 from sources.
As I understand, without fastboot, I can't update my bootloader to JB. Not a nice device...
Click to expand...
Click to collapse
Try to use this command to check if fastboot it's working : " fastboot -i 0x0b05 reboot ". If your device reboot after sending that command it means you can use fastboot just fine.
To be honest i've seen many bricks reports from people that tried to only flash the JB bootloader so imo the best way to get the JB bootloader is to flash the official JB firmware, then install the latest TWRP OR CWM recovery via fastboot, use the custom recovery to make a backup of the stock rom. Once you've did all that you can install CM10 just fine but also you will have the opportunity to go back to stock JB in case you need to.
thunderger said:
I'm stuck at fastboot mode with my TF700. Windows XP recognizes my device but the command "fastboot devices" doesn't show up my TF700. I tried to reinstall drivers from univeral naked drivers package 0.7 with success - tried it three times. Bootet up TF700 in fastboot mode but still fastboot doesn't see my device.
Has anyone an idea what I can do? I tried it also in my virtual linux machine without succes. I want to flash new CWM recovery over old TWRP recovery to update to JB and after this to get proprietary files needed to build CM10 from sources.
As I understand, without fastboot, I can't update my bootloader to JB. Not a nice device...
Click to expand...
Click to collapse
Fastboot devices does not work on this device. I've used fastboot to swap recovery images several times and update to the JB bootloader by itself. It definitely works as a whole.
Pretoriano80 said:
Try to use this command to check if fastboot it's working : " fastboot -i 0x0b05 reboot ". If your device reboot after sending that command it means you can use fastboot just fine.
To be honest i've seen many bricks reports from people that tried to only flash the JB bootloader so imo the best way to get the JB bootloader is to flash the official JB firmware, then install the latest TWRP OR CWM recovery via fastboot, use the custom recovery to make a backup of the stock rom. Once you've did all that you can install CM10 just fine but also you will have the opportunity to go back to stock JB in case you need to.
Click to expand...
Click to collapse
I've tried this command many times, and all I ever get is < waiting for device > and nothing else. This is getting annoying as hell. I've tried so many different things, all with the same result. I guess I'll just have to wait until there is an exploit found to root the JB firmware without having to use fastboot, then use TWRP from Goomanager, and hopefully by then there will be a zip of CWM Recovery.

Deleted more than I should

Apparently while doing a factory reset I managed to delete almost everything from internal storage. I've used cwm for years and made the switch to twrp recently. I could have sworn I checked everything BUT internal storage though. My data partition was showing something insane like 7 terabytes used so I wasn't able to make a nandroid. I instead deleted the data partition and somehow this happened.
Now I have no nandroids, and no more ROM zips. I attempted the procedure I used in the "how to unlock bootloader etc" thread, but when I try to push the ROM zip via the push command, it says no device found. I used Odin back in the day. Is it usable for any phone? Anyone know how to go about fixing this?
Odin is Samsung only. So, you can't adb push anything to the device?
Transmitted via Bacon
timmaaa said:
Odin is Samsung only. So, you can't adb push anything to the device?
Transmitted via Bacon
Click to expand...
Click to collapse
I thought Odin was device specific. I was hoping I was wrong though. Adb push isn't working, it just says no device found twice in a row. I can see it if I do fastboot devices though. I'll try reinstalling the Adb drivers when I get home.
Euphoria64 said:
I thought Odin was device specific. I was hoping I was wrong though. Adb push isn't working, it just says no device found twice in a row. I can see it if I do fastboot devices though. I'll try reinstalling the Adb drivers when I get home.
Click to expand...
Click to collapse
You have to be in recovery mode to do adb.
Fastboot devices is only while in fastboot mode.
Just adb sideload and not adb push. You have to go into ADB sideload in TWRP
zephiK said:
You have to be in recovery mode to do adb.
Fastboot devices is only while in fastboot mode.
Just adb sideload and not adb push. You have to go into ADB sideload in TWRP
Click to expand...
Click to collapse
I feel pretty dumb now. That's what I get for getting all pissed about all my data getting deleted and not reading instructions properly.
Euphoria64 said:
I feel pretty dumb now. That's what I get for getting all pissed about all my data getting deleted and not reading instructions properly.
Click to expand...
Click to collapse
Its okay, we all have our days enjoy your phone now. But yeah to elaborate more,
Odin is Samsung specific.
All other phones for the most part use fastboot. Which is pretty much our version of "Odin" but it is much better than Odin. Easier to use and less problems in my opinion.

Screwed [Solved]

Hello,
I screwed up while wiping and now my tab only boots to TWRP but wont mount anything.I found a similar case in this forum but Im too unfamilar with ADB/Fastboot to affect a solution.
Is ther a way to partition my tablet from fastboot?
The TF700t is unlocked.
adb and fastboot see the device.
TIA.....
DarkDarwin said:
Hello,
I screwed up while wiping and now my tab only boots to TWRP but wont mount anything.I found a similar case in this forum but Im too unfamilar with ADB/Fastboot to affect a solution.
Is ther a way to partition my tablet from fastboot?
The TF700t is unlocked.
adb and fastboot see the device.
TIA.....
Click to expand...
Click to collapse
What exactly did you wipe, and how did you screw up? To find out more about your situation, boot to your recovery (which version, btw?) and run these commands:
Code:
adb shell dmesg > dmesg.txt
adb shell cat /proc/partitions > partitions.txt
_that said:
What exactly did you wipe, and how did you screw up? To find out more about your situation, boot to your recovery (which version, btw?) and run these commands:
Code:
adb shell dmesg > dmesg.txt
adb shell cat /proc/partitions > partitions.txt
Click to expand...
Click to collapse
Im afraid I wiped everything.I think my mistake was wiping in stock recovery instead of TWRP..thus it only boots to TWRP now.
I tried those commands but my machine was hanging like it was waiting for the device so I am going to uninstall and reinstall the windows drivers and ADB/Fastboot and do the commands again ,Ive been at work since this morning so ive got some honey dos then I can start trying it again.
Thanks so much!
When I run the commands as shell I get the ` # <[6n in front of all entries ( I assume thats bc Im booted to recovery not fastboot) and the end result is always "not found" ie: shell not found , adb not found ect....
When I type adb shell sometimes it just hangs, the dmesg command actually writes a file but its an empty file and the terminal just hangs
Im pretty sure if I cant figure out a way to delete this TWRP Im never going to be able to properly use ADB/Fastboot ths never reinstall an OS and decent Recovery..
DarkDarwin said:
When I run the commands as shell I get the ` # <[6n in front of all entries ( I assume thats bc Im booted to recovery not fastboot) and the end result is always "not found" ie: shell not found , adb not found ect....
When I type adb shell sometimes it just hangs, the dmesg command actually writes a file but its an empty file and the terminal just hangs
Im pretty sure if I cant figure out a way to delete this TWRP Im never going to be able to properly use ADB/Fastboot ths never reinstall an OS and decent Recovery..
Click to expand...
Click to collapse
So am I correct in saying that you can get to fastboot ?
lj50036 said:
So am I correct in saying that you can get to fastboot ?
Click to expand...
Click to collapse
well i can run fastboot and adb commands from my pc but the T700t is in recovery (my only boot choice)
but technically yes I can get to fastboot
DarkDarwin said:
well i can run fastboot and adb commands from my pc but the T700t is in recovery (my only boot choice)
but technically yes I can get to fastboot
Click to expand...
Click to collapse
No - can you get the tablet into fastboot mode?
Either by holding Power and Volume down when booting up or, in recovery, issue
Code:
adb reboot-bootloader
What do you get with the command
Code:
adb devices
when in recovery, and if you can get into fastboot mode:
Code:
fastboot devices
Also, you still haven't told us which recovery version you are running.
We had to use _that's bootit.ko to get it out of recovery into fastboot...
Then it was a flash of the stock Asus blob ...
Got him up and running . :good:
@DarkDarwin can you add SOLVED to the thread title ...
Thx Josh
berndblb said:
No - can you get the tablet into fastboot mode?
Either by holding Power and Volume down when booting up or, in recovery, issue
Code:
adb reboot-bootloader
What do you get with the command
Code:
adb devices
when in recovery, and if you can get into fastboot mode:
Code:
fastboot devices
Also, you still haven't told us which recovery version you are running.
Click to expand...
Click to collapse
Thanks for trying to help me yesterday bro!
lj50036 said:
We had to use _that's bootit.ko to get it out of recovery into fastboot...
Then it was a flash of the stock Asus blob ...
Got him up and running . :good:
@DarkDarwin can you add SOLVED to the thread title ...
Thx Josh
Click to expand...
Click to collapse
Any chance we could get a step-bystep on that? Pleeeaaase?
berndblb said:
Any chance we could get a step-bystep on that? Pleeeaaase?
Click to expand...
Click to collapse
Yes, Give me a day or so and I will post it in the Q&A section as its own thread ...
Thx Josh
lj50036 said:
Yes, Give me a day or so and I will post it in the Q&A section as its own thread ...
Thx Josh
Click to expand...
Click to collapse
I went out and got a bigger SD card (64) to try and implement the DATA2SD script.I think I was successful as I now have new folders there named Android and Data that I didn't have before...However,I wonder if I was supposed to wipe anything before I re-flashed the ROM after inserting the formatted , partitioned SD...
I have to admit the I/O issue is extremely aggravating..I cant believe Asus marred an otherwise excellent device like that.
I was sent from this topic: http://forum.xda-developers.com/showthread.php?t=2179759&page=23
To this topic, I also have a similar problem.
Read my comment from last topic:
Ok, when I boot up in android, I can use adb command reboot bootloader to boot in the bootloader.
When i then try fastboot erase system, it's still hangs with waiting for device..
The bootloader is not stuck, i can again boot up android..
it's impossible to open terminal, because the touch is going crazy..
Hmm, i'm trying something else.
I still had 10x tf300 for repair. there are multiple cracked with 5184n version.
I installed the cracked display assembly on this one, then i just can normally use the keyboard.
Will try again in terminal
edit: what command to use in terminal?
Dont forget, i flashed the recovery, but didnt install supersu zip yet..
The strange thing is, when im in the bootloader, i can use fastboot flash recovery command, and write the right recovery.
It's also succesfull (sending recovery OK, writing recovery OK)
But, the transformer hangs in the bootloader after finished (freeze)
When trying to reboot, it's automaticaly going again booting up twrp (enter password)
So it didnt write the recovery, by example if i write twrp 2.7, it still gives me 2.6.3.0 (installed first time)
extra information:
If i'm booted up, and then adb reboot bootloader, then try fastboot commands, they don't work. it keeps saying waiting for devices.., the fastboot commands like flash works for 1 second then the tablet freezes.
Click to expand...
Click to collapse
So, fastboot commands are not working, how to get the bootloader normal again and that it reads fastboot commands?
Look in Device Manager on your PC and check that the Asus ADB interface drivers are there
Wow what a difference DATA2SD and ROM2SD make!
lvrijn said:
I was sent from this topic: http://forum.xda-developers.com/showthread.php?t=2179759&page=23
To this topic, I also have a similar problem.
Read my comment from last topic:
So, fastboot commands are not working, how to get the bootloader normal again and that it reads fastboot commands?
Click to expand...
Click to collapse
Hey there, I may have a solution, I am very busy right now working on a step by step for a few diff unbricking methods...
Yes this sounds like a windows driver issue.... Let me see if I can find some info on this topic ..
Thx Josh
DarkDarwin said:
Look in Device Manager on your PC and check that the Asus ADB interface drivers are there
Click to expand...
Click to collapse
Like I already told, I have flashed dozen of transformers. Adb commands are working (like adb reboot boot loader) it works when booted in android and when in twrp (password). Fastboot commands give waiting for device, but fastboor flash recovery works but the transformer then freezes..
After this problem I already have flashed 3transformers correctly.
---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------
lj50036 said:
Hey there, I may have a solution, I am very busy right now working on a step by step for a few diff unbricking methods...
Yes this sounds like a windows driver issue.... Let me see if I can find some info on this topic ..
Thx Josh
Click to expand...
Click to collapse
Why would it be a windows driver issue? Other transformers I can flash succesfully adb and fastboot fully working
lvrijn said:
Like I already told, I have flashed dozen of transformers. Adb commands are working (like adb reboot boot loader) it works when booted in android and when in twrp (password). Fastboot commands give waiting for device, but fastboor flash recovery works but the transformer then freezes..
After this problem I already have flashed 3transformers correctly.
---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------
Why would it be a windows driver issue? Other transformers I can flash succesfully adb and fastboot fully working
Click to expand...
Click to collapse
LOL, looking for help but you know what you got...
WOW
lj50036 said:
LOL, looking for help but you know what you got...
WOW
Click to expand...
Click to collapse
Sorry, I dont understand what you mean. What do you know I got?
lvrijn said:
Sorry, I dont understand what you mean. What do you know I got?
Click to expand...
Click to collapse
Sounds like you know more about this then any of us.
Not all Transformer tablets use the same drivers.
Window is very picky about what driver it will use for what device ...

[Q] Deleted my OS! | OnePlus One

Today was the worst day ever. I rooted my phone, and it worked perfectly until today. What happened was that when I updated the Google Play Services, I lost connection anything Google related (No connection) I factory reset my phone 4 times, wiped the internal storage, and it still said that I couldn't connect to the Play Store (E.X Could not establish a reliable connection). So I went into recovery and went to Advanced Wipe, and without knowing so, I deleted my OS! Im so stupid..
I FORGOT I WASN'T AN IT...
For the past two days I've been trying to get back the OS (33R). Heres what I've done
1. Downloaded the XNPH33R OS from their website and tried to install it (says NO MD5 Verification)
2. Tried doing everything about resetting OS.
3. HUGEST PROBLEM : Whenever I try and do (e.g adb sideload <rom.>.zip, or flashing) It just says Error: Device not found
4. Downloaded ADB from the Android Debug Bridge, all of my cmd commands return the same thing.
3. Also a huge problem: When I try to flash, it says (device not unlocked) and then I unlock the bootloader (Im guessing what that is will unlock it) and then I go back to the Recovery and do it again on CMD, it repeats it.
ANY SUGGESTIONS?
(If you need more information I will gladly give it to you)
BlaHBlaH525 said:
Today was the worst day ever. I rooted my phone, and it worked perfectly until today. What happened was that when I updated the Google Play Services, I lost connection anything Google related (No connection) I factory reset my phone 4 times, wiped the internal storage, and it still said that I couldn't connect to the Play Store (E.X Could not establish a reliable connection). So I went into recovery and went to Advanced Wipe, and without knowing so, I deleted my OS! Im so stupid..
I FORGOT I WASN'T AN IT...
For the past two days I've been trying to get back the OS (33R). Heres what I've done
1. Downloaded the XNPH33R OS from their website and tried to install it (says NO MD5 Verification)
2. Tried doing everything about resetting OS.
3. HUGEST PROBLEM : Whenever I try and do (e.g adb sideload <rom.>.zip, or flashing) It just says Error: Device not found
4. Downloaded ADB from the Android Debug Bridge, all of my cmd commands return the same thing.
3. Also a huge problem: When I try to flash, it says (device not unlocked) and then I unlock the bootloader (Im guessing what that is will unlock it) and then I go back to the Recovery and do it again on CMD, it repeats it.
ANY SUGGESTIONS?
(If you need more information I will gladly give it to you)
Click to expand...
Click to collapse
Could you post the fastboot and adb commands and results you get from executing them in CMD?
abde27 said:
Could you post the fastboot and adb commands and results you get from executing them in CMD?
Click to expand...
Click to collapse
I've been struggling the hole day long with the same problem.
Maybe you could read my thread. : )
Link
abde27 said:
Could you post the fastboot and adb commands and results you get from executing them in CMD?
Click to expand...
Click to collapse
CMD
cd C:\Users\xxxx\Desktop\android-sdk-windows\platform-tools
adb sideload ROM33R.zip <When the ADB sideload is on>
<Output>
* daemon not running. Starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Maybe I should try installing ADB drivers?
BlaHBlaH525 said:
CMD
cd C:\Users\xxxx\Desktop\android-sdk-windows\platform-tools
adb sideload ROM33R.zip <When the ADB sideload is on>
<Output>
* daemon not running. Starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Maybe I should try installing ADB drivers?
Click to expand...
Click to collapse
Go into Device Manager, and make sure your OPO is listed as under ADB Interface while the OPO is in bootloader mode. If it's not there then yes install or reinstall the adb driver but make sure you don't have any other devices with a triangle next to it as that may be your OPO.
abde27 said:
Go into Device Manager, and make sure your OPO is listed as under ADB Interface while the OPO is in bootloader mode. If it's not there then yes install or reinstall the adb driver but make sure you don't have any other devices with a triangle next to it as that may be your OPO.
Click to expand...
Click to collapse
My phone is listed as
Fastboot Interface (Google USB id)
BlaHBlaH525 said:
My phone is listed as
Fastboot Interface (Google USB id)
Click to expand...
Click to collapse
Does your OPO get listed when you enter "fastboot devices" ? When you had originally rooted and unlocked your OPO had you done it through CMD or a toolkit?
abde27 said:
Does your OPO get listed when you enter "fastboot devices" ? When you had originally rooted and unlocked your OPO had you done it through CMD or a toolkit?
Click to expand...
Click to collapse
Ill give you a screen shot of it being in fastboot mode. I also had rooted and unlocked my phone thru CMD
BlaHBlaH525 said:
Ill give you a screen shot of it being in fastboot mode. I also had rooted and unlocked my phone thru CMD
Click to expand...
Click to collapse
Ok so let me get this straight:
You had originally unlocked your bootloader and rooted through the cmd: "fastboot oem unlock" ?
Did you use this guide by any chance?: http://forum.xda-developers.com/showthread.php?t=2788632
Now you have no installed os and whenever you try to sideload or push stock 33R through adb it gives an error of the device not being found to the adb shell? Or does it complain that the bootloader is unlocked? If the second is happening you might need to reset the unlock and tamper bits,
Sorry if I'm asking something you already stated. I just want to be clear before I recommend anything or try to pull someone who's more experienced in for help.
abde27 said:
Ok so let me get this straight:
You had originally unlocked your bootloader and rooted through the cmd: "fastboot oem unlock" ?
Did you use this guide by any chance?: http://forum.xda-developers.com/showthread.php?t=2788632
Now you have no installed os and whenever you try to sideload or push stock 33R through adb it gives an error of the device not being found to the adb shell? Or does it complain that the bootloader is unlocked? If the second is happening you might need to reset the unlock and tamper bits,
Sorry if I'm asking something you already stated. I just want to be clear before I recommend anything or try to pull someone who's more experienced in for help.
Click to expand...
Click to collapse
Yeah I used that guide. And yes, what you stated is true. But another thing is that when I install the ROM, it says No MD5 file, but when I check the zip file, it says that there is a file called md5sum-fastboot.md5, I think that that is what TWRP is saying.
Are you able to use adb to push a zip to your internal storage?
Transmitted via Bacon
---------- Post added at 07:13 AM ---------- Previous post was at 07:02 AM ----------
If you can, just push a recovery flashable version of CM11S from here to your phone and flash it with TWRP. No sideload required.
Transmitted via Bacon
timmaaa said:
Are you able to use adb to push a zip to your internal storage?
Transmitted via Bacon
Click to expand...
Click to collapse
I have not tried, but I was able to view the internal storage and place the ROMs inside /sdcard/
timmaaa said:
Are you able to use adb to push a zip to your internal storage?
Transmitted via Bacon
---------- Post added at 07:13 AM ---------- Previous post was at 07:02 AM ----------
If you can, just push a recovery flashable version of CM11S from here to your phone and flash it with TWRP. No sideload required.
Transmitted via Bacon
Click to expand...
Click to collapse
BlaHBlaH525 said:
I have not tried, but I was able to view the internal storage and place the ROMs inside /sdcard/
Click to expand...
Click to collapse
He is right. If you can actually see the internal storage, you should be able to flash a flashable version of stock 33R from TWRP.
Actually if you are on the latest TWRP you can probably use the MTP functions and copy the file over without having to adb push it.
If you don't have the latest TWRP you can download the .img and flash it via the fastboot command. The latest is 2.8.0.1
abde27 said:
He is right. If you can actually see the internal storage, you should be able to flash a flashable version of stock 33R from TWRP.
Actually if you are on the latest TWRP you can probably use the MTP functions and copy the file over without having to adb push it.
If you don't have the latest TWRP you can download the .img and flash it via the fastboot command. The latest is 2.8.0.1
Click to expand...
Click to collapse
I have the latest version anyways
So, anything else?
Recovery flashable version is the easiest solution.
Transmitted via Bacon
timmaaa said:
Recovery flashable version is the easiest solution.
Transmitted via Bacon
Click to expand...
Click to collapse
Is that what I should do? If so, could you tell me how? Please xD
BlaHBlaH525 said:
Is that what I should do? If so, could you tell me how? Please xD
Click to expand...
Click to collapse
You just flash it like you would flash any ROM, using the install feature in TWRP. Download it from the link I provided before.
Transmitted via Bacon
timmaaa said:
You just flash it like you would flash any ROM, using the install feature in TWRP. Download it from the link I provided before.
Transmitted via Bacon
Click to expand...
Click to collapse
Are these different from the ones I downloaded from the offical CyanogenMOD OnePlus One page? Because when I try to flash it, it says MD5 file not found an then puts an error...
BlaHBlaH525 said:
Are these different from the ones I downloaded from the offical CyanogenMOD OnePlus One page? Because when I try to flash it, it says MD5 file not found an then puts an error...
Click to expand...
Click to collapse
Without you being more specific about exactly which zip you got from the CM site it's impossible to say. What's the filename?
Transmitted via Bacon
timmaaa said:
Without you being more specific about exactly which zip you got from the CM site it's impossible to say. What's the filename?
Transmitted via Bacon
Click to expand...
Click to collapse
The URL is
https://cyngn.com/products/oneplusone/
The name is
cm-11.0-XNPH33R-bacon-signed-fastboot.zip with the MD5 Checksum of 2c5bcbb3230501f2b841b56cac392bcb

Bricked Device Help

Hello, my OPO device was bricked after I accidentally wiped the internal memory and it has no rom installed either. However, I have access to the fastboot mode and also TWRP. I've tried to use adb push to put in a rom but it says device not found when I try. Also while connected to my computer, the device doesn't show up, but in device manager it will show up as just "One".
When typing adb devices, nothing shows up, when typing fastboot devices my phone's ID will show with fastboot to the right.
Kogecha said:
Hello, my OPO device was bricked after I accidentally wiped the internal memory and it has no rom installed either. However, I have access to the fastboot mode and also TWRP. I've tried to use adb push to put in a rom but it says device not found when I try. Also while connected to my computer, the device doesn't show up, but in device manager it will show up as just "One".
When typing adb devices, nothing shows up, when typing fastboot devices my phone's ID will show with fastboot to the right.
Click to expand...
Click to collapse
You can do a couple things:
1. Flash COS12.1 from here via instructions in the linked thread
2. Download TWRP and flash it via fastboot commands, reboot to recovery and transfer a nightly and gapps and flash
You are not bricked at all, last time I managed to brick my phone the screen was black no matter what I did, you can easily get back from fastboot
Renosh said:
You can do a couple things:
1. Flash COS12.1 from here via instructions in the linked thread
2. Download TWRP and flash it via fastboot commands, reboot to recovery and transfer a nightly and gapps and flash
You are not bricked at all, last time I managed to brick my phone the screen was black no matter what I did, you can easily get back from fastboot
Click to expand...
Click to collapse
I can't transfer files into the phone as windows doesn't recognize the device anymore, and there is no device found when I try to use adb to push files into /sdcard/
I will try the first option and will let you know.
Edit: First option worked, phone is working fine now. Thanks for your help and I'll be more careful in the future.
Kogecha said:
I can't transfer files into the phone as windows doesn't recognize the device anymore, and there is no device found when I try to use adb to push files into /sdcard/
I will try the first option and will let you know.
Edit: First option worked, phone is working fine now. Thanks for your help and I'll be more careful in the future.
Click to expand...
Click to collapse
Twrp also has USB-OTG function .. Even if you don't have any ROM on phone .. You can download a rom to a usb pendrive and connect it to phone twrp will recognize the USB pendrice and then can install rom from that ..
sent from Bacon (OnePlus One)

Categories

Resources