Related
Guys
I went to try to switch the runtime from Dalvik to ART. I was on CM11S 33....now my phone keeps rebooting into CM recovery. I tried factory reset but it keeps rebooting into CM recovery. I currently do not know on what to do next. Please assist me.
In cm revovery.. i tried adb sideload the lastest update.zip however while installing update...the error msg "assert failed: apply patch check...installation aborted
Unlock your bootloader and flash the CM11S fastboot images. Check my guide thread for details.
Transmitted via Bacon
timmaaa said:
Unlock your bootloader and flash the CM11S fastboot images. Check my guide thread for details.
Transmitted via Bacon
Click to expand...
Click to collapse
i cant get into fastboot mode as in your guide stated..just a black screen....i can only reboot into cm recovery...is there any way to unlock bootloader by adb commands instead?
i tried adb> fastboot device..now it is stuck in waiting for device
but if i type adb>adb devices ... the phone serial no appears
anyone with any help?
from adb...fastboot devices is not listing anyting...
Adb push a flashable version of CM11S to your phone while in recovery, then flash that.
Transmitted via Bacon
timmaaa said:
Adb push a flashable version of CM11S to your phone while in recovery, then flash that.
Transmitted via Bacon
Click to expand...
Click to collapse
i just tried adb push update.zip /sdcard however an error msg: device not found
You said you were able to communicate via adb earlier, what happened?
Transmitted via Bacon
i still can communicate via adb but only sideloads workds...fastboot and adb push is not working at all
i am trying the hard brick method with color.zip...my pc able to identify my phone as QLOADER 9008 but the Msm8974DownloadTool.exe is not identifying it at all..my phone is not detected..sigh...been trying to solve this since 8 hours ago...didnt knew that changing the runtime to ART could be so complicated
relaksua said:
i still can communicate via adb but only sideloads workds...fastboot and adb push is not working at all
i am trying the hard brick method with color.zip...my pc able to identify my phone as QLOADER 9008 but the Msm8974DownloadTool.exe is not identifying it at all..my phone is not detected..sigh...been trying to solve this since 8 hours ago...didnt knew that changing the runtime to ART could be so complicated
Click to expand...
Click to collapse
Did you have Xposed Framework installed?
Transmitted via Bacon
Nope it was on CM11S .. no xposed framework installed.....i only switch the runtime to ART.....it was rooted..unlocked bootloader....now before it reboot into Cyanogen recovery...i could see a glimpse of the android with the red triangle.
You still can't get the device into fastboot mode?
Transmitted via Bacon
timmaaa said:
You still can't get the device into fastboot mode?
Transmitted via Bacon
Click to expand...
Click to collapse
nope...from adb...it just stats waiting for device and that's it
relaksua said:
nope...from adb...it just stats waiting for device and that's it
Click to expand...
Click to collapse
Have you tried turning it off and using the button combination (power + volume up) to get into fastboot mode?
Transmitted via Bacon
timmaaa said:
Have you tried turning it off and using the button combination (power + volume up) to get into fastboot mode?
Transmitted via Bacon
Click to expand...
Click to collapse
yes i did that...just blank screen...now trying on another comp running vista though...will try to reformat the phone
I managed to flash ColorOS into my phone but now it keeps rebooting into ColorOS recovery...my PC cant identify the device...how i place a zip file into this phone...i tried using an OTG cable with a thumbdrive and it cant read from the recovery....i am so in bad luck
EDIT: Got my phone recognized by my PC but in adb command..adb devices..it rerturns this 123456789ABCDEF recovery ...seems wrong
Wow the second thread about this now:
http://forum.xda-developers.com/oneplus-one/help/phone-dead-arrival-video-link-post-t2869452
Very strange problem
timmaaa said:
Did you have Xposed Framework installed?
Transmitted via Bacon
Click to expand...
Click to collapse
I've the same problem and I had Xposed Framework on my device. What can I do?:crying:
I have same problem too
hello everybody,
so my phones speakers stopped working and I couldn't fix them so I went to twrp recovery and executed a factory reset. This resulted in the device hanging at the boot screen. I then spent half an hour trying to get the drivers working and when it finally saw the phone and I wanted to sideload the 33R zip it just gave me this long list with possible command (see screenshot attached).
in fastboot it's not seeing the phone for some reason
I have access to the following:
TWRP Recovery
Fastboot
Any idea on how to get my phone working again?
RacerBas said:
hello everybody,
so my phones speakers stopped working and I couldn't fix them so I went to twrp recovery and executed a factory reset. This resulted in the device hanging at the boot screen. I then spent half an hour trying to get the drivers working and when it finally saw the phone and I wanted to sideload the 33R zip it just gave me this long list with possible command (see screenshot attached).
in fastboot it's not seeing the phone for some reason
I have access to the following:
TWRP Recovery
Fastboot
Any idea on how to get my phone working again?
Click to expand...
Click to collapse
Do you have a backup or even a ROM zip on the phone you can install from TWRP?
bp328i said:
Do you have a backup or even a ROM zip on the phone you can install from TWRP?
Click to expand...
Click to collapse
If I had I wouldn't be here
RacerBas said:
If I had I wouldn't be here
Click to expand...
Click to collapse
First on your PC try typing adb devices it should return the device serial number in the command prompt.
If it does then in TWRP click advanced, ADB Sideload, then swipe the blue arrow.
Then on your PC command prompt type adb sideload "ROM/File Name.zip" without the quotes.
It should load from there.
bp328i said:
First on your PC try typing adb devices it should return the device serial number in the command prompt.
If it does then in TWRP click advanced, ADB Sideload, then swipe the blue arrow.
Then on your PC command prompt type adb sideload "ROM/File Name.zip" without the quotes.
It should load from there.
Click to expand...
Click to collapse
That's what I tried but it came up with what's shown in the screenshot
RacerBas said:
That's what I tried but it came up with what's shown in the screenshot
Click to expand...
Click to collapse
Ok try adb push "ROM/File.zip" /sdcard
That will put the rom zip on the root of your sdcard and you can flash from there.
bp328i said:
Ok try adb push "ROM/File.zip" /sdcard
That will put the rom zip on the root of your sdcard and you can flash from there.
Click to expand...
Click to collapse
I'm getting this now: error: closed
attached a screenshot of how the phone turns up in windows
RacerBas said:
I'm getting this now: error: closed
attached a screenshot of how the phone turns up in windows
Click to expand...
Click to collapse
After it shows my device id number it says recovery, yours says host? Are you doing this with TWRP booted?
Hold on it looks like you need to update your drivers...
bp328i said:
After it shows my device id number it says recovery, yours says host? Are you doing this with TWRP booted?
Hold on it looks like you need to update your drivers...
Click to expand...
Click to collapse
yea, I've been trying to get that working for a while, guess I got the wrong ones. That would explain everything though XD
RacerBas said:
yea, I've been trying to get that working for a while, guess I got the wrong ones. That would explain everything though XD
Click to expand...
Click to collapse
Try uninstalling the ones you have and installing this one.
https://github.com/koush/UniversalAdbDriver
Good luck man, I've got to get back to work.
I know the adb push "ROM/File.zip" /sdcard works because I tested on my phone prior to posting.
One last thought is your SDK might need to be updated as well.
bp328i said:
Try uninstalling the ones you have and installing this one.
https://github.com/koush/UniversalAdbDriver
Click to expand...
Click to collapse
Currently trying it on my laptop which has a fresh reinstall, removing the drivers completely will take too long.
Your driver saw it as a google galaxy nexus adb Interface, when I used adb devices it didn't see it.
EDIT: when I go to reboot it says that there is no os installed so yea...
Another Edit: I will try this driver when I get home and report back. OnePlus adb drivers windows
I managed to fix it using the oneplus one toolkit by manudroid
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
While recently trying to update my opo running cm11 I clicked install update but then it rebooted and just went to a black screen and did nothing. I rebooted it but it hadn't installed. I found my boot loader was locked and i had no recovery at all installed does anyone know how to fix this.
tom_clegg said:
While recently trying to update my opo running cm11 I clicked install update but then it rebooted and just went to a black screen and did nothing. I rebooted it but it hadn't installed. I found my boot loader was locked and i had no recovery at all installed does anyone know how to fix this.
Click to expand...
Click to collapse
Use fastboot & ADB guide for beginners. Download all required files so your PC can Connect to OPO VIA USB from PC. What PC OS do u use? Windows or Linux. Watch how to unlock boot loader, root, & install recovery tool or Return to stock OnePlus one YouTube video. Easiest start. Your phone will be OK. U need to down load drivers so u can use your PC to talk to your phone - pass instruction & activate 1+1 options. Install CM 11 or whatever ROM u want to use, as well as, 1+1 tools u may have lost is Recovery Tool.
Fstop said:
Use fastboot & ADB guide for beginners. Download all required files so your PC can Connect to OPO VIA USB from PC. What PC OS do u use? Windows or Linux. Watch how to unlock boot loader, root, & install recovery tool or Return to stock OnePlus one YouTube video. Easiest start. Your phone will be OK. U need to down load drivers so u can use your PC to talk to your phone - pass instruction & activate 1+1 options. Install CM 11 or whatever ROM u want to use, as well as, 1+1 tools u may have lost is Recovery Tool.
Click to expand...
Click to collapse
I use a mac and i tried to use a recovery tool however it says boot loader needed to be unlocked which mine wasn't and it wouldn't unlock because i had no recovery at all.
tom_clegg said:
I use a mac and i tried to use a recovery tool however it says boot loader needed to be unlocked which mine wasn't and it wouldn't unlock because i had no recovery at all.
Click to expand...
Click to collapse
You don't need a recovery to unlock the bootloader. Just boot it into fastboot mode, connect it to your Mac, and type 'fastboot oem-unlock' on the Terminal. Be careful, though, because you WILL lose ALL of your data!
Sent from my LG-V500 using Tapatalk
GXGOW said:
You don't need a recovery to unlock the bootloader. Just boot it into fastboot mode, connect it to your Mac, and type 'fastboot oem-unlock' on the Terminal. Be careful, though, because you WILL lose ALL of your data!
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
where do i find the files for mac with fast boot adb etc.
tom_clegg said:
I use a mac and i tried to use a recovery tool however it says boot loader needed to be unlocked which mine wasn't and it wouldn't unlock because i had no recovery at all.
Click to expand...
Click to collapse
Hmmm no recovery? When u hold down volume + power ?
Did u find the fastboot & adb tools for Mac?
What happens when u hold volume key up + power button at same time after turning device off?
What happens if u $fastboot devices -
Can u issue cmd "$fastboot oem unlock"
Know its frustrating but have to keep trying till u get in. Just have the rom files unzipped on your Mac ready to flash 1+1 when u get in. Its how I did it. When I wasn't able to but into recovery. Get on fastboot go thru OEM unlock, then flash 1+1. Follow the install script manually. Open script w plain text reader & just issue cmds following script. I don't trust scripts I + automation to get things unstuck.
tom_clegg said:
where do i find the files for mac with fast boot adb etc.
Click to expand...
Click to collapse
Use Google, there are plenty of guides available online. Once you have fastboot working the best thing to do is to flash the stock images with fastboot. I have detailed instructions in section 8a of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
Please note that fastboot commands are slightly different on a Mac but you'll see that when you view a guide on how to set it up and use it.
Heisenberg said:
Use Google, there are plenty of guides available online. Once you have fastboot working the best thing to do is to flash the stock images with fastboot. I have detailed instructions in section 8a of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
Please note that fastboot commands are slightly different on a Mac but you'll see that when you view a guide on how to set it up and use it.
Click to expand...
Click to collapse
would u be able to do a short one for mac that would help a lot with the commands
tom_clegg said:
would u be able to do a short one for mac that would help a lot with the commands
Click to expand...
Click to collapse
There's no point in duplicating my guide when all that's needed are a couple of extra characters prefixing each fastboot command.
Heisenberg said:
There's no point in duplicating my guide when all that's needed are a couple of extra characters prefixing each fastboot command.
Click to expand...
Click to collapse
is it just ./ then the command?
can i message you somehow maybe so it is quicker
tom_clegg said:
is it just ./ then the command?
can i message you somehow maybe so it is quicker
Click to expand...
Click to collapse
Dude, in the time it's taken you to ask these questions here you could have already found the answers online and completed the task. I'm here to help people but I'm not about spoon feeding, it doesn't benefit you in any way.
Heisenberg said:
Dude, in the time it's taken you to ask these questions here you could have already found the answers online and completed the task. I'm here to help people but I'm not about spoon feeding, it doesn't benefit you in any way.
Click to expand...
Click to collapse
fine then
tom_clegg said:
would u be able to do a short one for mac that would help a lot with the commands
Click to expand...
Click to collapse
at the point where i do fastboot oem unlock it reboots but stays at the boot screen.
tom_clegg said:
fine then
Click to expand...
Click to collapse
Don't get an attitude because I'm trying to help you help yourself.
tom_clegg said:
at the point where i do fastboot oem unlock it reboots but stays at the boot screen.
Click to expand...
Click to collapse
Issue the Mac equivalent of this command:
Code:
fastboot oem device-info
What does it return?
Heisenberg said:
Don't get an attitude because I'm trying to help you help yourself.
Issue the Mac equivalent of this command:
Code:
fastboot oem device-info
What does it return?
Click to expand...
Click to collapse
I type fastboot oem unlock and it is meant to reboot into android but however it stays stuck on the boot screen
tom_clegg said:
I type fastboot oem unlock and it is meant to reboot into android but however it stays stuck on the boot screen
Click to expand...
Click to collapse
That isn't what I asked you, if you want help you need to answer the questions that you're asked.
Heisenberg said:
That isn't what I asked you, if you want help you need to answer the questions that you're asked.
Click to expand...
Click to collapse
it says device tampered true
unlocked false
charge screen enabled false
tom_clegg said:
it says device tampered true
unlocked false
charge screen enabled false
Click to expand...
Click to collapse
Ok, try the unlock command again. What recovery did you previously have installed?
Heisenberg said:
Ok, try the unlock command again. What recovery did you previously have installed?
Click to expand...
Click to collapse
still the same thing sorry just stuck on boot screen.
i would have been able to do it its just this which i wasn't sure about :/
tom_clegg said:
still the same thing sorry just stuck on boot screen.
i would have been able to do it its just this which i wasn't sure about :/
Click to expand...
Click to collapse
You definitely can't boot into recovery? Most times not being able to get into recovery it's a case of user error. Hold volume down, then hold power (so you're holding them together), when you see the OnePlus boot logo let go of power but keep holding volume down until you reach recovery.
Hello,
i did this here
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
(unbrick device, install color os)
the fastboot of my device worked, after it, I did this here because i dont wanted the chinese color os, i wanted stock
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
(this dude tell how to get stock back, this here work only with adb...
...but by 'adb devices' my device dont got listened, so i followed this dude:
https://www.youtube.com/watch?v=kpUiIfAUNVU&feature=youtu.be
(how to install adb drivers)
I cant boot in my phone, i have only fastboot, before this yt video in device manager my phone in fastboot got listened under 'other', 'android', after this yt video my device is listened in device manager under 'android device', 'android adb interface'
why my device dont get listened under adb devices?
please help me guys i dont know anymore what to do...
#edit tested on my linux laptop(kubuntu(kde), 15.10), the self stuff... detected as 'android', dont get listened under adb devices...
#tested on windows 8.1 from my sister, the self...
Try booting into fastboot and flash stock CM again
@dabanhfreak ??? I already use fastboot, but my pc dont list it under adb devices
PlayersHeaders said:
@dabanhfreak ??? I already use fastboot, but my pc dont list it under adb devices
Click to expand...
Click to collapse
the command is
fastboot and not adb
dabanhfreak said:
Try booting into fastboot and flash stock CM again
Click to expand...
Click to collapse
DerRomtester said:
the command is
fastboot and not adb
Click to expand...
Click to collapse
thanks guy!!!
fastboot flash recovery twrp.img
worked!!!
thread can get closed
PlayersHeaders said:
thanks guy!!!
fastboot flash recovery twrp.img
worked!!!
thread can get closed
Click to expand...
Click to collapse
Why don't you just edit your first post and add [solved] or [resolved] to the title.